SB26-077 · Bill · 2026 Regular Session · Colorado

Epilepsy-Related Mortality Awareness

Concerning epilepsy-related mortality awareness.

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.

The act requires that, beginning July 1, 2027, a death certification professional ensure that they are aware of the most recent epilepsy-related death certification recommendations from a nationally recognized and reputable organization. On or before June 1, 2027, the department of public health and environment (department) must electronically notify all registered medical certifier users of the Colorado vital events system of this requirement. If a death certification professional determines that the cause of an individual's death is consistent with known or suspected sudden unexpected death in epilepsy, the act requires the professional to ensure that the individual's death certificate identifies epilepsy as a contributing cause or a suspected cause of death. The act allows the department to provide online guidelines for clinicians and medical certifiers for death certificates regarding epilepsy-related deaths, including sudden unexpected death in epilepsy. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-077, oldest first
DateLocationAction
01/28/2026SenateIntroduced In Senate - Assigned to Health & Human Services
03/05/2026SenateSenate Committee on Health & Human Services Refer Amended - Consent Calendar to Senate Committee of the Whole
03/10/2026SenateSenate Second Reading Passed with Amendments - Committee
03/11/2026SenateSenate Third Reading Laid Over to 03/12/2026 - No Amendments
03/12/2026SenateSenate Third Reading Passed - No Amendments
03/13/2026HouseIntroduced In House - Assigned to Health & Human Services
03/25/2026HouseHouse Committee on Health & Human Services Refer Amended to House Committee of the Whole
03/27/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
03/30/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/02/2026HouseHouse Third Reading Passed - No Amendments
04/06/2026SenateSenate Considered House Amendments - Result was to Concur - Repass
04/07/2026SenateSigned by the President of the Senate
04/07/2026HouseSigned by the Speaker of the House
04/08/2026GovernorSent to the Governor
04/20/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (2 proposed amendments)

Amendments proposed to SB26-077, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.005Committee amendment — Health & Human Services (Senate)03/05/2026PassedView official document
L.006Committee amendment — Health & Human Services (House)03/25/2026PassedView official document

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

Full text

Official record

View SB26-077 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

ea84cbe0594a1f528a37c5e7e1d36a1d4ac2ba3e79804974d79d3925e5c995b3

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.