Guide
EVV requirements by state
Every state has to verify Medicaid personal care and home health visits electronically. What differs is the system. In 44 of the 50 states and DC the state offers an EVV system and agencies may use their own software instead, as long as it sends each visit to the state’s aggregator. In 5 more there is no state system and every agency picks a vendor. Maryland requires its own app. The table below gives each state’s system, whether you can use your own, CMS’s compliance finding and the source for every row.
Updated October 28, 2026
State by state
| State | State EVV system or aggregator | Can agencies use their own EVV software? | Home health EVV (CMS) | Notes and source |
|---|---|---|---|---|
| Alabama | HHAeXchange (aggregator) | Yes, via the aggregator | Compliant | Provider choice model; agencies on another system file an EVV attestation.State source |
| Alaska | Therap | Yes, via the aggregator | Compliant | Third-party systems must meet state requirements and upload to the state system.State source |
| Arizona | AHCCCS aggregator | Yes; no state system | Compliant | Moved from a hybrid to an open model on 1 Oct 2025; the Sandata contract ended and agencies contract with a vendor directly.State source |
| Arkansas | Sandata (home health); AuthentiCare (personal care) | Yes, via the aggregator | Not compliant | Alternate systems need a signed attestation.State source |
| California | CalEVV (Sandata) | Yes, via the aggregator | Compliant | Alternate vendors certify with Sandata; agencies still self-register in CalEVV.State source |
| Colorado | Sandata | Yes, via the aggregator | Compliant | The state lists alternate vendors already connected to Sandata.State source |
| Connecticut | Sandata | Yes, via the aggregator | Compliant | Open model since 2024; alternate systems certify with Sandata.State source |
| Delaware | HHAeXchange (formerly Sandata) | Yes, via the aggregator | Compliant | Open model; alternate systems need a provider and vendor attestation. Unmatched EVV claims denied since 1 Jul 2025.State source |
| District of Columbia | Sandata | Yes, via the aggregator | Compliant | Sandata is free to providers; an alternate system is at the provider’s expense.State source |
| Florida | HHAeXchange | Yes, via the aggregator | Compliant | HHAeXchange for fee-for-service home health since 1 Oct 2024; managed care plans run their own arrangements.State source |
| Georgia | Tellus (Netsmart) | Yes, via the aggregator | Not compliant | Alternate systems feed the Tellus aggregator at least daily; third-party attestation required.State source |
| Hawaii | Sandata | Yes, via the aggregator | Compliant | Agencies may use a Sandata-certified system; self-directed services must use Sandata.State source |
| Idaho | Sandata (aggregator) | Yes, via the aggregator | Compliant | Provider choice model; we could not find a state page describing it.Vendor documentation |
| Illinois | HHAeXchange | Yes, via the aggregator | Compliant | Open vendor model; other systems integrate with HHAeXchange.State source |
| Indiana | Sandata | Yes, via the aggregator | Compliant | Alternate vendors are certified through FSSA and Sandata.State source |
| Iowa | CareBridge | Yes, via the aggregator | Compliant | Other systems must integrate with CareBridge.State source |
| Kansas | AuthentiCare (Fiserv) | Yes, via the aggregator | Compliant | Third-party systems need state approval and an interface to AuthentiCare.State source |
| Kentucky | Therap | Yes, via the aggregator | Compliant | Open model; third-party systems integrate with Therap.State source |
| Louisiana | LaSRS | Yes, via the aggregator | Compliant | Alternate systems must pass LaSRS data integration and sign an attestation.State source |
| Maine | Sandata | Yes, via the aggregator | Compliant | Integrating another system takes at least eight weeks.State source |
| Maryland | LTSSMaryland | No, state system only | Compliant | Staff clock in and out in the LTSSMaryland app, with a phone line as backup.State source |
| Massachusetts | Sandata | Yes, via the aggregator | Not compliant | Alternate (Alt-EVV) systems integrate with Sandata.State source |
| Michigan | HHAeXchange | Yes, via the aggregator | Not compliant | Open vendor model; other systems send data through HHAeXchange’s EDI.State source |
| Minnesota | HHAeXchange | Yes, via the aggregator | Compliant | One system per provider number; third-party systems connect to HHAeXchange.State source |
| Mississippi | HHAeXchange | Yes, via the aggregator | Not compliant | All EVV claims go through HHAeXchange since 1 Dec 2025; other systems import visits by EDI.State source |
| Missouri | Sandata (aggregator) | Yes, via the aggregator | Compliant | Agencies choose their EVV vendor; the state lists vendors connected to the aggregator.State source |
| Montana | Netsmart (Mobile Caregiver+) | Yes, via the aggregator | Compliant | Alternate systems must be certified and send data to Netsmart.State source |
| Nebraska | Netsmart | Yes, via the aggregator | Compliant | Alternate vendors and agencies sign compliance attestations.State source |
| Nevada | Sandata | Yes, via the aggregator | Compliant | Replaced AuthentiCare on 15 Dec 2023; every agency registers with Sandata whichever system it uses.State source |
| New Hampshire | AuthentiCare (Fiserv) | Yes, via the aggregator | Compliant | Open model; third-party systems send data to the AuthentiCare aggregator.State source |
| New Jersey | HHAeXchange (aggregator) | Yes, via the aggregator | Compliant | Managed care plans offer EVV tools; all visit data reaches HHAeXchange.State source |
| New Mexico | AuthentiCare (Fiserv) | Yes, via the aggregator | Compliant | Was the only allowed system; open/hybrid from 30 Sep 2025 (fee-for-service) and 20 May 2026 (managed care).Health plan notice |
| New York | eMedNY (aggregator) | Yes; no state system | Compliant | Provider choice; the Department of Health does not certify EVV products.State source |
| North Carolina | Sandata | Yes, via the aggregator | Compliant | Some managed care plans offer HHAeXchange or CareBridge; alternate systems register with Sandata.State source |
| North Dakota | Therap; Sandata (aggregator) | Yes, via the aggregator | Not compliant | Therap is the default; agencies on another system still use Therap for authorizations and incident reports.State source |
| Ohio | Sandata | Yes, via the aggregator | Compliant | The state publishes a list of certified alternate vendors.State source |
| Oklahoma | AuthentiCare (aggregator) | Yes, via the aggregator | Compliant | Open vendor model; a move away from AuthentiCare has been reported but we could not confirm it with the state.Health plan notice |
| Oregon | Varies by program | Yes, via the aggregator | Compliant | Home health agencies may use their own EVV if it records start and end to the minute.State source |
| Pennsylvania | Sandata | Yes, via the aggregator | Compliant | The state publishes a list of certified vendors.State source |
| Rhode Island | Sandata | Yes, via the aggregator | Compliant | Alternate systems follow the RI Alternate EVV Specification.State source |
| South Carolina | AuthentiCare (Phoenix) | Unclear | Not compliant | State notices in 2026 still point to AuthentiCare; HHAeXchange describes an open model with its system. Confirm with SCDHHS.State source |
| South Dakota | Therap | Yes, via the aggregator | Compliant | Third-party systems connect to the Therap aggregator at the provider’s cost.State source |
| Tennessee | Each managed care plan’s EVV | Yes, via the aggregator | Compliant | Agencies use the member’s plan solution or a vendor that feeds that plan’s aggregator.State source |
| Texas | HHAeXchange | Yes, via the aggregator | Compliant | Other systems need HHSC approval as a proprietary system.State source |
| Utah | UEVV (aggregator) | Yes; no state system | Compliant | No state-offered system; vendors submit by API or web portal.State source |
| Vermont | Sandata | Yes, via the aggregator | Compliant | Alternate systems are credentialed through Sandata.State source |
| Virginia | Managed care plan aggregators | Yes; no state system | Compliant | Provider choice model; the state does not endorse a vendor, and plans set where data goes.State source |
| Washington | ProviderOne (claims carry EVV data) | Yes; no state system | Compliant | Provider choice model; home health EVV is set by the Health Care Authority.State source |
| West Virginia | HHAeXchange | Yes, via the aggregator | Compliant | Other systems import visits into HHAeXchange by EDI.State source |
| Wisconsin | Sandata | Yes, via the aggregator | Compliant | Alternate certification can take up to three months.State source |
| Wyoming | CareBridge | Yes, via the aggregator | Compliant | Another system needs state approval and must integrate with CareBridge.State source |
The same data is available as a CSV file (free to reuse with a link back to this page).
How to read the table
- State EVV system or aggregator. The system the state offers agencies, usually at no cost, or the aggregator that collects visit data from every system. Sandata, HHAeXchange, AuthentiCare, Therap, Netsmart (Tellus) and CareBridge are vendors the states contract with.
- Yes, via the aggregator. An “open” or “hybrid” model: use the state system, or use your own if it passes the state’s testing and sends every visit to the aggregator.
- Yes; no state system. A “provider choice” model with no state-offered app: every agency chooses a vendor that submits to the state.
- No, state system only. A “closed” model: visits are recorded in the state’s own system.
- Home health EVV (CMS). Whether CMS found the state’s home health EVV compliant with the 21st Century Cures Act on 1 January 2024. It describes the state, not individual agencies. See the CMS table.
How we built it
Each row was checked on October 28, 2026 against the state Medicaid agency’s own pages, provider bulletins and FAQs. Where no state page could be found, the row cites a health plan notice or a vendor’s documentation and says so. Where sources disagree, the row says “Unclear” instead of guessing.
States change vendors and rules: Arizona, New Mexico, Mississippi and Delaware have all changed theirs since mid-2025. Confirm with your state before choosing or switching EVV software. To report a change, use the contact options on our support page.
Frequently asked questions
Is EVV required for home health as well as personal care?
Yes. The 21st Century Cures Act requires EVV for Medicaid personal care services and for Medicaid home health care services. Home health came second, with a federal deadline of 1 January 2023 that states could extend to 1 January 2024.
Can I use my own EVV software instead of the state’s?
In most states, yes. 49 of 51 jurisdictions allow it, usually after your vendor passes testing with the state’s aggregator and you sign an attestation. Maryland requires its own system, and in South Carolina the sources disagree.
What is an EVV aggregator?
The state-run or state-contracted database that collects visit records from every EVV system used in the state, so Medicaid can match each claim to a verified visit. In most states a claim without a matching visit in the aggregator is denied.
What does it mean if my state is listed as not compliant?
It is CMS’s finding about the state’s EVV program as of 1 January 2024, which can reduce the federal share of the state’s Medicaid spending on those services. It does not exempt agencies: states still require EVV from providers.
Keep reading
What is EVV?The six data points every visit must record.Home care and Medicaid billingHow verified visits become paid claims.What home care CRM software is, and how to choose oneWhat a home care CRM covers end to end, and what to look for when you compare them.What is a plan of care?What a plan of care contains, and how it guides every visit.HIPAA compliance for home care agenciesWhat HIPAA asks of an agency, and the safeguards that cover most of it.
All guides and features