What are the Colorado EVV requirements?

Colorado follows the federal 21st Century Cures Act standard. Every applicable personal care and home health visit must capture the type of service performed, the individual receiving service, the caregiver providing service, the date of service, the location of service delivery, and the visit start and end times. Those records are transmitted to the state's Sandata aggregator.

Is Sandata required in Colorado?

Every provider's visit data has to reach the state aggregator, but agencies are not required to use the state-supplied data collection app. Under Provider Choice, an agency can use its own EVV system as long as that system transmits conforming visit records to the aggregator.

What is a Provider Choice EVV system?

A Provider Choice (sometimes called alternate or third-party) EVV system is an agency-selected platform that collects visit data in its own app and sends it to the state aggregator through an approved interface. Agencies pick this route when they want scheduling, documentation, billing, and EVV in a single workflow.

What happens if an EVV visit is rejected?

A rejected visit does not count as verified, and claims tied to it are exposed to denial or recoupment. The visit has to be corrected — usually a missing caregiver ID, an unmatched client, an out-of-range GPS point, or an overlapping time span — and retransmitted before billing.

Does EVV apply to CDASS attendants in Colorado?

Consumer-directed programs are also within scope of the federal EVV mandate, but the workflow differs: the attendant is employed by the member acting as employer of record, and time capture typically runs through the program's financial management services partner rather than an agency scheduler.

Colorado EVV Requirements 2026: Sandata & Provider Choice Guide

Short answer: Colorado EVV requires every applicable personal care and home health visit to record six data elements — service type, member, caregiver, date, location, and start/end time — and to transmit them to the state's Sandata aggregator. Agencies may use the state-supplied app or their own Provider Choice system, as long as the data conforms.

Electronic visit verification stopped being a project and became plumbing. The rules are settled, the aggregator is live, and the agencies still struggling are rarely struggling with the regulation itself. They are struggling with the gap between what happens in the field and what arrives at the state.

This guide walks through what Colorado actually requires, where the two compliance paths differ, and the operational habits that keep transmission rates near 100%.

What Colorado EVV requires

The requirement traces back to the 21st Century Cures Act, which obligated states to verify Medicaid-funded personal care and home health visits electronically. Colorado's Department of Health Care Policy & Financing (HCPF) implemented it with Sandata as the state aggregator.

Every in-scope visit must capture:

Data element	What it means in practice
Type of service	The billable service code delivered during the visit
Individual receiving service	The Medicaid member, matched to a state ID
Individual providing service	The caregiver or DSP, matched to a valid worker record
Date of service	The calendar date the visit occurred
Location of service	Where delivery began and ended, captured at clock-in and clock-out
Time of service	Start and end times, not a rounded shift block

Two details trip up new providers. First, location means the location of service delivery, not the caregiver's home base or the agency office. Second, times are event timestamps, not scheduled times. A visit scheduled 9:00–11:00 that actually ran 9:12–10:58 must be transmitted as 9:12–10:58.

Who is in scope

In-scope services generally include personal care, homemaker, and home health services delivered in a member's home or community. Services delivered in a licensed facility setting, and services that are not Medicaid-funded personal care or home health, generally fall outside the mandate. Because waiver service definitions change, the safest approach is to map your active service codes against current HCPF billing guidance once a year and re-check whenever you add a program.

The two compliance paths

Path 1: the state solution

HCPF makes a state-supplied data collection app available at no cost to providers. It captures the six elements and sends them straight to the aggregator. It is a reasonable choice for small agencies with a handful of caregivers and no complex scheduling.

The tradeoff is that it is an EVV app and nothing more. Your scheduling lives somewhere else, your documentation lives somewhere else, and your billing lives somewhere else. Every reconciliation between those systems is manual.

Path 2: Provider Choice

Colorado permits agencies to use their own EVV system — the Provider Choice model — provided the system transmits conforming records to the aggregator. This is the path most agencies take once they pass roughly fifteen to twenty caregivers, because it collapses four workflows into one.

With a Provider Choice system such as OutcomeGrid's EVV module, the caregiver clocks in once. That single event creates the verified visit, opens the session note, stamps the payroll hours, and seeds the claim line. Nothing is re-keyed, so nothing drifts.

	State solution	Provider Choice system
Cost	No provider cost	Vendor subscription
Setup effort	Low	Moderate — interface testing required
Scheduling integration	None	Native
Documentation in same app	No	Yes
Claim pre-population	No	Yes
Best fit	Very small providers	Growing multi-program agencies

A deeper comparison of the two routes lives on our Colorado EVV and Provider Choice page.

Why visits get rejected

Almost every failed transmission comes from one of five causes:

Worker record mismatch. The caregiver's identifier in your system does not match an active worker in the aggregator. New hires are the usual culprit — the record has to exist on the state side before the first shift, not after it.
Member mismatch. A Medicaid ID typo, or a member whose eligibility span does not cover the visit date.
Location outside tolerance. GPS captured from a parking lot, a building with poor signal, or a device with location permissions denied.
Overlapping visits. The same caregiver clocked into two visits at once, or a live-in schedule expressed as overlapping blocks.
Missing clock-out. The caregiver forgot, the app lost connectivity, or the shift was closed manually with no end event.

None of these are exotic. What separates a 99% agency from an 85% agency is not fewer errors — it is how fast errors are found. Our EVV compliance checklist breaks the daily and weekly routine down step by step.

Building an EVV operation that holds up

Verify eligibility before the shift, not after the claim

Run an eligibility check when the authorization is entered and again at the start of each month. A member who lost coverage mid-month generates verified visits that will never pay.

Watch the exception queue daily

Give one person the job of clearing exceptions every morning. A rejected visit found the same day is a two-minute fix. The same rejection found at month-end billing is a research project across three systems and two staff memories.

Treat manual edits as a metric

Manual visit edits are permitted and sometimes necessary, but a high edit rate is what auditors look for. Track edits per hundred visits by caregiver and by supervisor. If one team's rate is triple the agency average, that is a training issue or a device issue — find out which.

Prove connectivity is not the problem

Rural Colorado has real coverage gaps. Offline capture that stores the visit on the device and syncs when signal returns is not a nice-to-have; it is the difference between a verified visit and a manual entry. Verify your system does this before you sign anything.

Keep the audit trail intact

Retain the original captured values alongside any correction, plus who made the correction and why. A clean, explainable audit trail is more persuasive during review than a perfect-looking record with no history behind it. Our security and data handling practices describe how we retain that history.

What good looks like

Agencies running a healthy EVV operation tend to hit these marks:

Transmission acceptance above 98% within 24 hours of the visit
Exception queue cleared to zero every business day
Manual edits under 5% of visits, with documented reasons
No claim submitted against an unverified visit — ever

That last rule is the one worth writing on the wall. Billing ahead of verification is how agencies end up returning money two years later.

Where to go next

If you are evaluating whether to move off the state app, the practical question is not really about EVV. It is whether your scheduling, documentation, billing, and payroll are already sharing one record — and if they are not, how many hours per week your team spends making them agree.

Talk to our team for a walkthrough of how Colorado agencies run EVV, notes, and claims from a single clock-in.

Colorado EVV Requirements in 2026: A Provider's Guide to Sandata and Provider Choice