HB26-1019 · Bill · 2026 Regular Session · Colorado

Kidney Screening Mandatory Preventive Coverage

Concerning mandatory health-care coverage for preventive kidney function screening services.

Official status: Became Law

3 proposed amendments

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

The act adds kidney function screening services as mandated preventive health-care services for which insurance policies or contracts in the state must provide total-cost coverage. Coverage for kidney function screening services will be implemented for all large employer health benefit policies or contracts issued or renewed in this state on or after January 1, 2027, and coverage will be implemented for all individual and small group health benefit plans issued or renewed in this state on or after January 1, 2028, as long as the state is not required to defray the cost of the coverage of the kidney function screening services. The act permits the exclusion of the 'State Employees Group Benefits Act' from this mandate and exempts certain high deductible plans from having to provide total-cost coverage for such services. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1019, oldest first
DateLocationAction
01/14/2026HouseIntroduced In House - Assigned to Health & Human Services
03/11/2026HouseHouse Committee on Health & Human Services Refer Amended to House Committee of the Whole
03/13/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
03/16/2026HouseHouse Third Reading Passed - No Amendments
03/19/2026SenateIntroduced In Senate - Assigned to Health & Human Services
04/08/2026SenateSenate Committee on Health & Human Services Refer Unamended to Senate Committee of the Whole
04/10/2026SenateSenate Second Reading Laid Over to 04/27/2026 - No Amendments
04/27/2026SenateSenate Second Reading Special Order - Passed with Amendments - Floor
04/28/2026SenateSenate Third Reading Passed - No Amendments
04/29/2026HouseHouse Considered Senate Amendments - Result was to Laid Over Daily
05/04/2026HouseHouse Considered Senate Amendments - Result was to Concur - Repass
05/20/2026HouseSigned by the Speaker of the House
05/20/2026SenateSigned by the President of the Senate
05/20/2026GovernorSent to the Governor
05/26/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (3 proposed amendments)

Amendments proposed to HB26-1019, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.002Committee amendment — Health & Human Services (House)03/11/2026PassedView official document
L.003
Sponsor: Representative Bradley
Floor amendment — Second Reading (House)03/13/2026LostView official document
L.004
Sponsor: Senator Roberts
Floor amendment — Second Reading (Senate)04/27/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

View HB26-1019 on leg.colorado.gov

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

fa9dc76e11dd64d11a351260fad2b09b12cbd5c8d03a34de3d95acb866050111

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-11-06 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.