HB26-1378 · Bill · 2026 Regular Session · Colorado

Repeal Behavioral Health Resources

Concerning the repeal of certain behavioral health resources administered by the behavioral health administration, and, in connection therewith, reducing an appropriation.

Official status: Became Law

2 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.

Current law requires the general assembly to annually appropriate $50,000 to provide vouchers to individuals living in rural and frontier communities in need of behavioral health-care services. The bill repeals the requirement to appropriate money for that purpose. The act: Repeals the requirement that the BHA contract with an independent third party to provide services and supports to behavioral health providers seeking to become behavioral health safety net providers; Repeals the building substance use disorder treatment capacity in underserved communities grant program; Repeals the recovery support services grant program; Transfers the balance of the high-risk families cash fund (fund) to the general fund and repeals the fund on July 1, 2026; and Reduces appropriations to the behavioral health administration for the affected programs and services. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1378, oldest first
DateLocationAction
04/02/2026HouseIntroduced In House - Assigned to Appropriations
04/06/2026HouseHouse Committee on Appropriations Refer Unamended to House Committee of the Whole
04/08/2026HouseHouse Second Reading Special Order - Laid Over Daily - No Amendments
04/09/2026HouseHouse Second Reading Special Order - Passed with Amendments - Floor
04/10/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/11/2026HouseHouse Third Reading Passed - No Amendments
04/13/2026SenateIntroduced In Senate - Assigned to Appropriations
04/14/2026SenateSenate Committee on Appropriations Refer Amended - Consent Calendar to Senate Committee of the Whole
04/15/2026SenateSenate Second Reading Special Order - Passed - No Amendments
04/15/2026SenateSenate Second Reading Special Order - Passed with Amendments - Committee
04/16/2026SenateSenate Third Reading Passed - No Amendments
05/28/2026HouseSigned by the Speaker of the House
05/28/2026SenateSigned by the President of the Senate
05/28/2026GovernorSent to the Governor
05/29/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (2 proposed amendments)

Amendments proposed to HB26-1378, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.002
Sponsor: Representative Johnson
Floor amendment — Second Reading (House)04/09/2026PassedView official document
L.004Committee amendment — Appropriations (Senate)04/14/2026PassedView official document

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

Full text

Official record

View HB26-1378 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

bff5a67b342af61af80aae4571f66c928742db6a80111ff41032f1787a31887b

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.