EVV requirements are driven by the 21st Century Cures Act for Medicaid personal care services and home health care services that require in-home visits, but state programs, aggregator models, exception workflows, and claim-matching rules vary.
Last reviewed June 15, 2026. Operational workflow context only — not legal, clinical, billing, or compliance advice.
How agency leaders should use this guide
Treat this page as an operating-readiness worksheet, not legal, clinical, billing, payer, or compliance advice.
Use the guide to name the workflow owner, the upstream inputs, the downstream handoffs, and the software proof you need to see before changing systems. For each topic, ask which department owns the work today, where handoffs break, what evidence is needed before billing or leadership review, and what the agency needs visible without exposing PHI.
HELIX public examples stay demo-safe. The goal is to help owners, administrators, clinical leaders, schedulers, billers, and QAPI teams evaluate whether an EMR can organize the work, surface blockers, and route follow-up. Final regulatory, payer, clinical, coding, billing, and compliance decisions remain with the agency and its qualified advisors.
Name the accountable department and owner
Identify the work queue, evidence, deadline, and handoff
Ask for no-PHI product proof before implementation scope is accepted
Official-source context
Medicaid.gov EVV guidance and state Medicaid EVV program materials
Map the six Cures Act visit data elements
State Medicaid program and aggregator requirements review
Track clock, location, schedule, and service-code exceptions
Review supervisor resolution before billing
Separate public workflow support from state certification claims
Agency operating guide
Use this section to turn the topic into practical evaluation criteria, workflow ownership, and implementation questions for a home health or home care agency.
Agency guide
Why state EVV pages need more than a national summary
Medicaid.gov explains the federal EVV mandate, but states implement EVV through different program rules, aggregator relationships, payer expectations, edits, and exception workflows. A state hub should therefore help agencies ask better state-specific questions instead of implying one universal certification. The useful framework is: which services are in scope, what data is captured, where it is sent, what exceptions are allowed, who reviews them, and how billing is held or released.
Document PCS and HHCS scope by state and payer context
Name aggregator or submission model only when verified for the implementation
Separate workflow support from state certification or compliance advice
Medicaid.gov EVV guidance and state Medicaid EVV program materials.
Agency guide
The practical state EVV checklist
Agencies should maintain a state EVV checklist that covers service codes, provider identifiers, caregiver identifiers, mobile capture rules, location expectations, allowed manual edits, exception reasons, supervisor review, payer or aggregator submission, rejection handling, and billing release. A state hub becomes useful when it turns those variables into a repeatable implementation worksheet, not when it repeats the same EVV definition for every state.
Map service codes, payer rules, aggregator flow, and exception reasons
Audit manual edits and supervisor approvals
Connect rejected EVV records to rework before billing proceeds
EVV implementation scoping checklist for Medicaid home care operations.
Agency guide
How HELIX should be evaluated for EVV state readiness
A buyer should ask whether HELIX can organize state-specific EVV work even when the final connection pattern depends on payer, aggregator, or implementation scope. The visible proof should include schedule-to-visit matching, missing clock review, location exceptions, service-code review, supervisor queue, billing hold, and leadership trend reporting. That is more credible than a blanket claim that every state is already solved.
Ask which state, payer, and aggregator workflows are in implementation scope
Ask how exceptions move from caregiver to supervisor to billing
Ask how trend reporting shows recurring EVV risk by team or service line
HELIX public workflow support framing; no state certification claim.
Make this resource best-in-class
Guide depth
EVV state-hub detail agencies search for
This hub turns EVV from a generic feature page into a state-aware workflow resource: six Cures Act data elements, aggregator variation, exceptions, supervisor review, and billing handoffs.
Must cover
Six Cures Act EVV data elements
Personal care and home health care services that require in-home visits
State Medicaid program and aggregator differences
Clock, location, schedule, and service-code exception review
Billing hold resolution after supervisor review
Related buyer questions
state EVV requirementsMedicaid EVV softwarehome care EVV aggregator
Official sources
Verify the regulatory specifics directly at the official source. This page is operating-readiness context, not advice.
Want this guide and the relevant HELIX workflow walkthrough by email? Leave a work email — no sales call required, and you can see the product and the $299/mo starting price without a login wall.
HELIX support
HELIX supports operational visibility and workflow management. It does not provide legal, payer, clinical, or compliance advice.
Does HELIX provide legal, payer, clinical, or compliance advice?
No. HELIX provides workflow software and operational tooling. Agencies remain responsible for regulatory and payer obligations.
Are resource pages certification claims?
No. Resource pages explain operational workflow context and avoid unsupported certification or outcome claims.
See HELIX in action
Request a demo with skilled and non-skilled care workflows.
Walk through intake, documentation, care plans, scheduling, EVV, authorizations, billing, QAPI, reporting, and mobile workflows without routing through a login wall.