An Agency Guide to Electronic Visit Verification
Summary: Federal law establishes an EVV requirement for specified Medicaid-funded in-home services, but implementation varies. Agencies should evaluate verification, state and aggregator fit, exception work, transmission evidence, and downstream use—not a generic “compliant” label.
The federal baseline
CMS explains that section 12006 of the 21st Century Cures Act requires states to implement EVV for Medicaid-funded personal care services and home health care services that require an in-home visit. The law identifies six required data elements: type of service, individual receiving the service, date of service, location of service delivery, individual providing the service, and time the service begins and ends. (CMS EVV, retrieved 2026-08-11.)
That is the federal floor. State programs determine important implementation details, and those details can change.
EVV is a lifecycle
1. Schedule and eligibility
The visit begins with the correct client, caregiver, service, payer or program, authorization context, and planned time.
2. Verification
The caregiver records arrival and departure through a supported method, which may include a mobile application, telephony, fixed device, or another state-approved approach.
3. Documentation
The agency captures required service, task, note, signature, or exception context. Do not assume every state or program requires the same fields or workflow.
4. Exception review
Late, missing, overlapping, location-mismatched, manually entered, or changed records need a defined owner, reason, evidence, correction, and approval path.
5. Transmission
Required data moves to the state, payer, managed care organization, or aggregator through the applicable model.
6. Response and correction
Accepted, rejected, pending, corrected, and resubmitted states should remain visible. A successful local clock event does not prove successful external acceptance.
7. Billing and audit
The verified and reviewed visit supports the appropriate claim or payment workflow and remains available with its history.
Questions that matter more than “Are you compliant?”
Ask a vendor:
- Which state, program, payer, and service combinations are supported today?
- Which EVV model and aggregator apply?
- Which verification methods are supported?
- What works offline, and how does sync failure appear?
- How are manual entries and corrections identified and approved?
- Can the agency see outbound, accepted, rejected, and resubmitted states?
- Which rejection reasons can be resolved in the platform?
- How do authorizations and service plans affect scheduling and billing?
- What data reaches claims, payroll, reporting, and audit evidence?
- Which responsibilities remain with the agency?
Mobile and offline are not yes-or-no labels
Ask what happens for each action when connectivity is poor:
- open today’s schedule;
- start and end a visit;
- capture location or alternate verification;
- complete tasks;
- write or dictate a note;
- collect a signature;
- attach supporting information;
- review submission requirements;
- sync, retry, and resolve a conflict.
A product may support one action offline and not another. The website and contract should say which.
Exception management is the operational heart
An EVV exception queue should show:
- the affected visit and program;
- the detected issue and source evidence;
- downstream effect on billing or payroll;
- urgency and owner;
- allowed correction or attestation;
- approver and change history;
- transmission or resubmission state.
Without that structure, EVV produces data while staff still manage compliance work in email and spreadsheets.
Avoid two costly assumptions
“The federal rule is the state rule”
It is not enough to implement the six federal data elements and assume every state’s workflow, aggregator, edit policy, or program requirement is covered.
“A vendor integration logo proves our workflow works”
Ask which data is exchanged, in which direction, how often, for which programs, with which status feedback, and who supports a failure.
Build a dated support matrix
For every state and program, record:
- program and service scope;
- EVV model and aggregator;
- supported verification methods;
- integration state and certification where applicable;
- required setup;
- known limitations;
- source URL and verification date;
- internal owner and next review date.
The most trustworthy EVV page is not the one with the broadest claim. It is the one that makes fit and limitations easiest to verify.
Next: Explore the Ethiya care-delivery and EVV draft.