The federal requirement is identical everywhere: six data points per Medicaid-funded personal care or home health visit. Everything else is a state decision, and that is why an agency crossing a state line finds the same visit accepted in one place and rejected in another. This page is a working map for an agency owner: what varies, where to read the authoritative answer, and which questions to ask a vendor before you agree that they cover your state.
Three models, and which one you are in
States run open models (bring your own vendor, transmit to the state aggregator), closed models (use the state's system) and hybrid models (the state provides a system but you may use your own). Your model decides whether EVV is a purchase or an enrolment. Agencies in Pennsylvania, Ohio, Michigan, Missouri, Colorado, Georgia, Virginia, Indiana and Minnesota each answer this differently, and the answer moves when a state re-lets its aggregator contract.
What actually differs between states
Four things, reliably: which aggregator receives the file, how long you have to correct an exception before the claim is affected, what counts as an acceptable manual entry reason, and which services are in scope beyond the federal minimum. The last one catches agencies out most: some states extend EVV to programmes the Cures Act never named, so a service you bill without verification in one state is a rejected claim in the next.
How to check your own state properly
Read the state Medicaid agency's EVV page, not a vendor's summary, and read it again each year. States publish the aggregator, the provider enrolment route, the exception reason codes and the training they require. If your vendor cannot point you at that page and tell you the date they were last certified against it, they are describing their roadmap rather than your compliance.
Running more than one state
Multi-state agencies should expect two of everything until they choose a system that abstracts it: two portals, two exception queues, two reason-code vocabularies. The practical test for a vendor is not whether they claim national coverage but whether one scheduler can work both states' exceptions in a single screen at nine in the morning. Ask to see that screen with real state data in it.
Questions people ask about evv requirements by state
Is there one national EVV standard we can build to?
There is one federal data standard, the six points, and no national implementation. The Cures Act deliberately left the mechanism to states, so an agency's compliance is always read against its own state Medicaid agency's rules.
Our vendor says they support all fifty states. Is that meaningful?
Only if they can name your aggregator and the date of their last certification against it. Support is a claim about integrations, and integrations expire when a state changes contracts or file formats.
Does EVV apply to Medicare home health visits?
The mandate is Medicaid-funded. Medicare-certified agencies still capture visits electronically for their own documentation and billing, but the EVV requirement itself rides on Medicaid personal care and home health services.
How often do state EVV rules change?
Materially every few years, when an aggregator contract is re-let or a programme is added to scope. Put a calendar reminder against your state's EVV page rather than waiting for a rejection to tell you.