Skip to content

CMS & Regulatory Compliance

Colorado SB 24-205 Standards

Colorado SB 24-205: Multi-Specialty AI Scribe Rules

Human review, audit logs, and impact assessments for Colorado multi-specialty notes. Book your audit at https://cal.com/merryai/demo.

Executive Key Takeaways

  • C.R.S. § 6-1-1703 requires deployers of high-risk AI to maintain a risk management program, annual impact assessments, and human-review appeal pathways
  • Clinician attestation safeguards: every draft requires explicit, context-bound confirmation before EHR insertion, logged in an append-only audit trail
  • Specialty criteria (DSM-5-TR, NYHA/LVEF, ROM, Bright Futures) are presented as hypotheses and never asserted without clinician confirmation
  • G2211 and NCCI modifier 25/59/XE/XS distinctness is tagged at the narrative-segment level for audit defense
  • Validation via Access Clinical Prompts at templates.scribing.io
Regulatory Verification Framework
2026 Audit Ready
C.R.S. § 6-1-1703(2)Verified Compliant

Deployer Risk Management Program

Deployer Risk Management Policy and Program for High-Risk AI Systems

C.R.S. § 6-1-1703(3)Verified Compliant

Annual Impact & Discrimination Assessment

Pre-Deployment and Annual Impact Assessments for Algorithmic Discrimination

C.R.S. § 6-1-1703(4)Verified Compliant

Consumer Notice & Human Review Appeal

Consumer Notice, Data Correction, and Human-Review Appeal of Adverse Consequential Decisions

C.R.S. § 6-1-1704Verified Compliant

AI Interaction Disclosure

Disclosure of Consumer Interaction with Artificial Intelligence Systems

Statutory Compliance Architecture for Colorado SB 24-205 Standards

Documenting multi-specialty clinical encounters under Colorado SB 24-205, codified at C.R.S. §§ 6-1-1701 through 6-1-1707, requires that ambient documentation be evaluated as a potential high-risk artificial intelligence system. When a generated note materially influences a consequential decision, such as coding, reimbursement, eligibility, prior authorization, or risk stratification, the deployer assumes a duty of reasonable care to protect patients from algorithmic discrimination. The Attorney General enforces violations as deceptive trade practices under the Colorado Consumer Protection Act.

Deployer obligations are layered and cumulative. Section 6-1-1703(2) requires a documented risk management policy and program that is reviewed throughout the system's lifecycle. Section 6-1-1703(3) requires an impact assessment before deployment, annually thereafter, and within ninety days of any intentional and substantial modification. Section 6-1-1703(4) requires several protections for the consumer: notice, an explanation of adverse decisions, an opportunity to correct inaccurate personal data, and an appeal via human review where technically feasible.

Operative dates have shifted repeatedly. The 2025 extraordinary session moved the effective date to June 30, 2026. Subsequent proposals have contemplated small-business exemptions and revised enforcement timing. Compliance officers should verify the current statutory text before relying on any date. An architecture built to the strictest reading remains defensible under any amendment. Section 6-1-1706 also provides an affirmative defense for deployers aligned with the NIST AI Risk Management Framework or ISO/IEC 42001.

Human-Directed Review Across Specialty Diagnostic Frameworks

Merry AI enforces two-step insertion. Every draft is generated in a side panel and bound to the patient, encounter, note template, and specialty context read from the EHR DOM or URL. Insertion into textarea, contenteditable, or iframe-hosted editors is blocked if the context changes between generation and confirmation. This prevents wrong-chart injection in multi-tab workflows. The clinician's explicit confirmation becomes the human-review artifact on which § 6-1-1703(4) appeals depend.

Specialty criteria are presented as hypotheses, never as assertions. The AI output identifies candidate findings, and the clinician confirms, edits, or rejects each element before the note is committed. This distinction carries statutory weight. An impact assessment must describe known limitations, and fabricated criteria are precisely the failure mode that produces uneven documentation quality across patient populations.

Behavioral Health and Cardiology Criteria Integrity

In behavioral health, DSM-5-TR diagnoses require explicit criteria clusters, onset, duration, severity, and functional impairment, alongside a complete Mental Status Examination. Merry AI does not auto-populate diagnoses from conversation alone. Any inferred content on suicidality, violence, or substance use is labeled AI-suggested and held for mandatory clinician review.

In cardiology, NYHA class and LVEF are never inferred. LVEF is captured as a numeric value with its modality source: echocardiography, cardiac MRI, or nuclear imaging. When no value is stated, the note reads "LVEF not documented." ACC/AHA heart failure stage and CHA₂DS₂-VASc scores follow the same confirmation rule.

Orthopedics and Pediatrics Measurement Fidelity

Orthopedic notes demand measured values. Templates prompt for range-of-motion degrees, manual muscle testing grades from 0 to 5, and named maneuvers such as Lachman, McMurray, and straight leg raise with explicit results. Historical ROM values cannot carry forward into the current encounter without clinician confirmation.

Pediatric well-child visits follow Bright Futures age bands. Growth percentiles, developmental milestones, and screening results for vision, hearing, depression, and autism are surfaced for confirmation. Omitted elements are written explicitly, for example "Hearing screening not performed today," so that completion is never implied.

Audit Logging, Impact Assessments, and CMS Coding Defensibility

Every AI interaction is logged as an append-only, time-stamped event keyed to patient, encounter, note ID, specialty, user, and model version. Logged events include audio capture, transcript, draft generation, each clinician edit, and each DOM write. Inserted content carries machine-readable metadata and a visible note-header marker indicating AI assistance. This design is consistent with the disclosure principles of § 6-1-1704 and supports downstream detection of synthetic content.

These logs feed the annual impact assessment directly. Merry AI stratifies documentation completeness and complexity capture by specialty and demographic cohort. Deployers can therefore detect systematic under-documentation or overstated severity for any protected group before it influences a consequential decision.

G2211 and NCCI Modifier Distinctness

HCPCS G2211 rewards documented longitudinal complexity. CMS denies G2211 when the base office/outpatient E/M service is reported with modifier 25. The exception applies when the same-day service is an Annual Wellness Visit, vaccine administration, or a Medicare Part B preventive service. Beginning January 1, 2026, that exception extends to home or residence E/M codes. The note must articulate continuity, multimorbidity, and care coordination rather than restate the visit.

NCCI 2026 PTP edits require documented distinctness. Modifier 25 requires a significant, separately identifiable E/M service. Modifiers 59, XE, XS, XP, and XU require distinct sessions, sites, lesions, or practitioners. One example is CPT 45385 reported with 45380 for a separate lesion. Merry AI tags the supporting narrative segments so that coders never infer distinctness the clinician did not document. Incorrect coding accounted for 49.1% of 2024 E/M improper payments, so this traceability carries real financial weight.

Statutory Comparison and Implementation Sequence

Compliance DimensionManual ChartingStandard Generic AI ScribesMerry AI Compliance Architecture
Human review (§ 6-1-1703(4))Inherent but unloggedOptional, often post-insertionMandatory two-step confirmation, logged
Impact assessment evidence (§ 6-1-1703(3))Not applicableModel accuracy metrics onlySpecialty and cohort discrimination analysis
AI disclosure (§ 6-1-1704)Not applicableInconsistent or absentMachine-readable metadata plus visible header
Audit trail granularityEHR timestamp onlyTranscript and final noteAppend-only event log per DOM write
Specialty criteria integrityClinician-dependentGeneric language modelDSM-5-TR, NYHA/LVEF, ROM, Bright Futures prompts
Modifier distinctnessCoder inferenceUnflagged narrativeTagged segments for 25, 59, XE, XS

Implementation proceeds in four stages. First, adopt a risk management policy mapped to the NIST AI RMF. Second, complete baseline impact assessments for each specialty. Third, enable context-bound insertion and event logging. Fourth, set the cadence for annual review. Peer-reviewed evidence on ambient documentation accuracy is indexed at https://www.ncbi.nlm.nih.gov/pmc/. To map your EHR stack to these controls, Schedule a 15-Minute Workflow Audit.

Regulatory & Compliance FAQ

Does an ambient scribe qualify as a high-risk AI system under Colorado SB 24-205?

Classification depends on whether the output is a substantial factor in a consequential decision under C.R.S. § 6-1-1701. Notes used for coding, eligibility, prior authorization, or risk stratification can meet that threshold. Section 6-1-1705 narrows coverage for certain HIPAA-covered recommendations that require provider action, but multi-specialty groups should assess each workflow individually. Merry AI documents the classification rationale for each specialty so deployers can defend their determination before the Attorney General.

What must the annual impact assessment contain under C.R.S. § 6-1-1703(3)?

The assessment must state the system's purpose and intended use cases and analyze known or reasonably foreseeable risks of algorithmic discrimination. It must also describe the categories of data processed, performance metrics and limitations, transparency measures, and post-deployment monitoring. Assessments recur annually and within ninety days of any substantial modification. Merry AI exports specialty-stratified completeness and complexity metrics from its append-only logs, giving compliance officers reproducible evidence.

How does the human-review appeal right in § 6-1-1703(4) apply to clinical documentation?

Consumers facing an adverse consequential decision must receive an explanation, an opportunity to correct inaccurate personal data, and an appeal via human review where technically feasible. Every Merry AI draft requires explicit clinician confirmation, and every edit is logged. Deployers can therefore reconstruct which content was AI-suggested and which was clinician-authored. They can also trace how a correction propagated to coding or eligibility records.

How does SB 24-205 interact with G2211 and NCCI modifier audits?

The two frameworks operate independently but require similar evidence. CMS denies G2211 with modifier 25 except alongside an Annual Wellness Visit, vaccine administration, or Part B preventive services, and this exception extends to home or residence E/M from January 1, 2026. NCCI modifiers 59, XE, and XS require documented distinctness. Merry AI's tagged segments and event logs support both Colorado reasonable-care evidence and Medicare audit defense.

Where can clinics verify compliant templates?

Specialty templates for DSM-5-TR criteria, NYHA and LVEF capture, orthopedic ROM measurement, and Bright Futures well-child elements are available for review at https://templates.scribing.io. Each template presents diagnostic criteria as clinician-confirmed fields, states omitted elements explicitly, and preserves machine-readable AI markers. Compliance teams can compare these prompts against their own impact assessment findings before enabling them across Colorado and other multi-specialty locations.

Explore More Knowledge

Related Clinical Rules & Compliance Guides

View all clinical rules & compliance
Illinois Eavesdropping Act: Family Medicine Scribing
CMS & Regulatory Compliance

Illinois Eavesdropping Act: Family Medicine Scribing

Capture all-party verbal consent under 720 ILCS 5/14-2 in every family medicine visit. Book your audit at https://cal.com/merryai/demo.

Dr. Sarah Chen, MD•7 min read
Read guide
Washington MHMDA Compliance for Psychiatry Scribing
CMS & Regulatory Compliance

Washington MHMDA Compliance for Psychiatry Scribing

Separate RCW 19.373.030 consent before psychiatric recording; zero audio retention. Book your audit at https://cal.com/merryai/demo.

Dr. Sarah Chen, MD•7 min read
Read guide
Illinois Eavesdropping Act: Multi-Specialty Compliance
CMS & Regulatory Compliance

Illinois Eavesdropping Act: Multi-Specialty Compliance

Timestamp all-party verbal consent in chart before capture; audio shreds from RAM at 0 days. Book your audit at https://cal.com/merryai/demo.

Dr. Sarah Chen, MD•7 min read
Read guide