TL;DR — Colorado SB 26-091 AI Telehealth Consent

• The Law in brief: Colorado's 2026 amendment (SB 26-091) classifies AI-mediated healthcare recording as subject to all-party consent. The moment a "telehealth modality" is present, the stricter consent tier is triggered.

• The gap CMS misses: The CMS MLN901705 guidance defines billing mechanics (POS 10/02, modifiers 93/95) but says nothing about the consent-to-recording obligation that Colorado now imposes on AI scribes.

• What Scribing.io encodes: Consent lives in FHIR R4 (Consent resource plus policy URI referencing SB 26-091), modality auto-classifies via the HL7 virtualService backport extension, claims metadata derives from that modality, and an immutable Provenance plus AuditEvent binds to the Consent.

• The operational outcome: Compliant capture, clean claims, no recoupment, and a defensible audit trail for Clinical Operations Directors.

• Where All-Party Consent Meets AI Telehealth

• What CMS MLN901705 Does Not Cover

• Encoding SB 26-091 Consent in FHIR R4

• Clinical Logic: The Denver Behavioral Follow-Up

• Operational Rollout for Clinical Operations Directors

• Frequently Asked Operational Questions

Colorado SB 26-091: Where All-Party Consent Meets AI Telehealth

CLINICAL UPDATE 2026: Revised for new CMS CPT G2211 standards, SB 1120 compliance, and FHIR interoperability.

For Clinical Operations Directors managing Colorado telehealth panels, the operative shift in 2026 is jurisdictional, not just technical. Colorado's SB 26-091 explicitly classifies AI-mediated healthcare recording as subject to all-party consent.

This is the anchor truth that reframes every AI scribe deployment in the state. The ambient assistant is no longer a passive productivity tool. It is a recording party whose activation legally requires the affirmative consent of every participant, and Scribing.io treats it that way by design.

The critical operational nuance is modality sensitivity. Scribing.io auto-tags the Telehealth Modality on the encounter, and the presence of a telehealth modality is precisely what triggers the stricter consent tier.

A patient's home behavioral-health follow-up conducted over audio-video is treated as a recorded, all-party-consent event the instant the scribe engages. This is where the federal guidance and the state statute operate on entirely different planes.

What the CMS Telehealth Guidance (MLN901705) Does Not Cover

CMS MLN901705 remains the authoritative reference for Medicare telehealth billing and coverage. It confirms several 2026-relevant facts every Clinical Operations Director should treat as settled.

• POS 10 designates telehealth provided in the patient's home.

• POS 02 designates telehealth provided other than in the patient's home.

• Behavioral and mental health telehealth may be audio-only when the patient is in their home.

• Audio-only is permitted broadly when the patient cannot or does not consent to video.

• Behavioral health requires an in-person visit within 6 months of the initial telehealth visit and annually thereafter (42 CFR 410.78(b)(3)(xiv)(B)).

What MLN901705 does not address — because it sits outside CMS scope — is the consent-to-recording obligation SB 26-091 places on AI scribes. CMS tells you how to bill the modality. It is silent on whether you are legally permitted to have an AI record the encounter.

The two systems must reconcile programmatically, or a practice produces a clean claim on top of an illegal recording. That is the exact failure mode Scribing.io eliminates.

For context on how consent regimes vary by state, review the Scribing.io Florida All Party Consent Rules Reference and the narrower Scribing.io Florida Spousal Consent Rules Reference.

Encoding SB 26-091 Consent Directly in FHIR R4

The information-gain differentiator is not simply that we get consent. It is that Scribing.io encodes SB 26-091 as machine-enforceable clinical data, so consent, modality, billing, and auditability form a single coherent chain rather than four disconnected manual steps.

1. Persist a FHIR R4 Consent resource with a policy URI referencing SB 26-091, category = patient-privacy, and dual verification captured via Consent.verification. Recording is gated behind this resource's active status.

2. Classify the modality using the HL7 R5 virtualService backport extension applied to Encounter and Communication, distinguishing audio-video from audio-only in real time, including mid-visit downgrades.

3. Derive claims metadata programmatically from the classified modality to set POS 10/02 and the correct CPT modifier — 93 for audio-only, 95 for audio-video — for 2026 telehealth billing.

4. Bind Provenance plus an immutable AuditEvent to the Consent, linking note and media artifacts so the practice holds auditable proof capture was compliant at the moment it occurred.

The result is that the same modality signal satisfying Colorado's consent tier also drives the billing code. This eliminates drift between how we recorded and how we billed.

Clinical Logic: A Denver Follow-Up That Drops to Audio-Only

This is the scenario Clinical Operations Directors lose sleep over. Consider a Denver behavioral health follow-up intended to support a 99214, started over video, that drops to audio-only mid-visit.

The presenting diagnosis in this encounter is F41.1 (ICD-10-CM), with a comorbid I10 (ICD-10-CM) noted for medication interaction review.

Without Scribing.io: The Cascade Failure

1. The visit starts as audio-video but connection quality forces a drop to audio-only.

2. An AI scribe records the encounter without explicit all-party consent, an SB 26-091 violation the moment the telehealth modality is present.

3. Billing submits POS 10 with modifier 95 (audio-video), because the workflow never re-classified the downgrade.

4. A payer post-pay review flags the encounter as audio-only, denies for missing modifier 93, and recoups the payment.

5. The patient files an SB 26-091 consent complaint, triggering an AG inquiry and potential roughly $5,000 exposure.

With Scribing.io: The Compliant Path

1. A dual-verified FHIR Consent is captured before any recording, with policy URI referencing SB 26-091.

2. The Encounter is auto-tagged audio-only via the virtualService extension the instant the modality downgrades.

3. The claim emits POS 10 plus modifier 93, matching the actual delivered modality.

4. Provenance and AuditEvent link the note and media to the Consent, producing auditable proof.

5. Time-based documentation preserves the 99214, since total qualifying time is captured against the encounter regardless of modality.

Operational Rollout for Clinical Operations Directors

Deployment across a Colorado panel follows a predictable sequence. The goal is to make the consent gate non-optional at the workflow layer, not a checkbox clinicians can skip.

• Map every telehealth service line to its default modality and expected POS code before go-live.

• Configure the Consent gate so recording cannot initialize without an active dual-verified resource.

• Enable mid-visit modality re-classification so downgrades emit corrected claim metadata automatically.

• Confirm EHR write-back paths in the Scribing.io integration guides for Provenance and AuditEvent persistence.

• Review specialty-specific templates via the Scribing.io specialty library for behavioral health encounters.

To quantify the financial case for your panel, run the numbers with the AI Medical Scribe ROI Calculator and compare tiers on Scribing.io Pricing & Plans.

Frequently Asked Operational Questions

Does SB 26-091 apply to audio-only visits?

Yes, the statute triggers on the presence of a telehealth modality, not on video specifically. Audio-only behavioral health encounters remain within the all-party consent tier when an AI scribe is present.

What happens if a patient declines recording?

The Consent resource never reaches active status, so recording cannot initialize. The clinician documents manually while the encounter proceeds under standard billing rules.

How does the modifier get corrected mid-visit?

The virtualService extension re-classifies the modality in real time. Claims metadata derives from the final delivered modality, emitting modifier 93 or 95 accordingly.