To configure Health First Colorado PBT telemedicine controls, verify that the service is covered, clinically appropriate for telemedicine, delivered by an enrolled provider within scope, and supported by the current prior authorization. Record both locations, required consent, place of service, documentation, and claim route. Apply the current EVV manual's telehealth treatment only to the pediatric behavioral therapy services it actually covers.
Define a Colorado telehealth release
Vesper treats telehealth as a service-date configuration. One row identifies the member, program or plan, service, billing and rendering providers, supervisor when applicable, member and practitioner locations, modality, authorization, clinical decision, access supports, platform, note, claim rule, and emergency plan. The row receives a new version when any controlling fact changes.
Read the current Health First Colorado PBT authority
Colorado HCPF's telemedicine page says Health First Colorado members may use telemedicine for covered services, while in-person care remains necessary when clinically indicated. The current telemedicine billing manual requires an enrolled provider, appropriate scope, covered service, correct place of service, and consent at the specified cadence. Telemedicine does not change prior-authorization rules.
Separate program coverage from payer routing
The PBT billing manual supplies the program's PAR and billing rules. The current EVV program manual says select pediatric behavioral therapy delivered by telehealth may use place of service 02 or 10 and does not require EVV. Vesper treats that EVV result as a service and modality rule, while every other coverage, PAR, clinical, note, and claim gate remains active.
Use one release gate for every required fact
Vesper requires current member and payer route; covered PBT service; enrolled and qualified provider; valid PAR; both physical locations; allowed modality; documented consent at the required cadence; choice and assent when applicable; clinical fit; access; complete note; correct POS and claim receiver; applicable EVV treatment; and emergency plan. A failed gate holds the session or claim at the affected point. The register shows the source, owner, checked time, effective period, exception path, and next action. Clinical, legal, payer, technical, and claim facts retain separate owners and evidence.
Keep clinical decisions with qualified clinicians
Vesper routes case-specific modality, risk, treatment, supervision, and clinical-fit decisions to an appropriately qualified clinician. Operations verifies evidence, coordinates scheduling, and surfaces conflicts. Software can check fields and deadlines. A payer coverage action remains separate from the treating clinician's recommendation.
Verify location at every encounter
The member and practitioner locations can change between sessions. Vesper asks for the member's physical location at check-in and records the practitioner's physical location from the responsible professional. Those facts drive licensure, payer, emergency, privacy, and place-of-service analysis. Profiles and prior visits serve as reference data rather than the current encounter record.
Preserve choice, consent, assent, and communication
Vesper gives the person an understandable modality choice when the governing source allows it and records required consent from the legally authorized person. Assent is monitored when applicable. Speech, AAC, sign, gesture, writing, interpreters, captions, and other effective forms remain available. The person has an accessible way to request a pause or another supported setting.
Decide whether the session can work remotely
A qualified clinician reviews the purpose, response forms, observation needs, prompting, caregiver role, safety, privacy, environment, technology, fatigue, and alternatives. Vesper identifies which components need direct observation or in-person care and when to switch. Staffing pressure, distance, or payer approval supplies no clinical-fit conclusion.
Build technical and emergency readiness
Vesper tests the approved platform, audio, video when required, device power, bandwidth, camera view, communication system, backup contact, privacy, and outage route. The record names the person's physical location, local emergency contact, responsible adult when applicable, nearest response route, and stop condition. Staff pause when a connection failure prevents safe or meaningful care.
Match authorization and documentation
Vesper compares the authorized service, provider, setting, modality, dates, units, and stated conditions with the planned encounter. The note records actual locations, modality, start and stop time when required, participants, accessible communication, interventions, responses, interruptions, supervision, and clinically relevant outcome. The record describes the delivered session.
Release the claim from completed evidence
Vesper derives code, units, modifier, place of service, rendering and billing identities, location, authorization reference, and payer route from verified records and current instructions. A telehealth flag supplies one field, while the completed source record supplies the claim evidence. Claim acceptance, adjudication, remittance, and payment remain later states.
Work through Vesper's fictional cohort
Vesper locks 20 fictional Denver encounters. Thirteen initially contain current telemedicine and PBT rules, provider enrollment, PAR, both locations, clinical decision, consent, access, note, POS, EVV treatment, receiver, and response plan. One uses POS 11, one unnecessarily requires EVV for a supported telehealth service, one waives EVV for an in-person service, two PARs name another modality, one consent is stale, and two lack location evidence. Five repair. Two remain held. The example is synthetic. It tests release and denominator logic and establishes no coverage, authorization, clinical, legal, privacy, licensure, claim, or payment conclusion for a real person or practice.
Calculate Vesper's measures
Health First Colorado PBT telemedicine readiness is 13 of 20, or 65.0%. Eighteen encounters reach release or accountable hold, or 18 of 20, or 90.0%. Report holds by coverage, authority, location, choice, consent, assent, access, clinical fit, technology, authorization, documentation, claim, and emergency reason. Preserve counts beside percentages and age every unresolved item from its defined start event. Every failed or pending item remains visible in its declared cohort.
Address the main Colorado failure mode
The EVV exception can spread beyond its scope. Vesper applies it only after confirming the service, telehealth delivery, current manual, and place of service. The exception affects EVV collection; it does not establish coverage, PAR, clinical appropriateness, claim acceptance, or payment.
Test Vesper's controls
Vesper tests POS 02, POS 10, incorrect POS 11, telehealth EVV exception, in-person EVV requirement, stale consent, PAR mismatch, managed-care route, changed location, and failed video. Each scenario records the starting facts, expected action, source, observed result, owner, correction, retest, and disposition. A successful connection proves technical access for that test. Coverage, clinical fit, authorization, documentation, and payment need their own acceptance evidence.
Run independent acceptance
Vesper gives an independent reviewer the locked cohort, sources, locations, provider records, authorizations, clinical decisions, access plans, consent and assent evidence, platform results, notes, claims, and payer responses. The reviewer reproduces one release and one hold. A changed cohort, hidden failure, unsupported rule, or unexplained calculation fails acceptance.
Maintain the Health First Colorado PBT telemedicine and EVV register
Vesper reviews sources monthly and after program, plan, law, rule, manual, code, modifier, place-of-service, form, platform, authorization, contract, or contact changes. Each source keeps an owner, effective and checked dates, scope, supersession state, and next review. This Colorado page remains draft and noindex until every named expert review finishes.
Related resources
- Configure Florida Medicaid BA Telemedicine and Plan Controls
- Configure California Medi-Cal BHT Telehealth and Plan Controls
- Configure TennCare ABA Telehealth and MCO Controls
- Configure Arizona AHCCCS ABA Telehealth and Coding Controls