How HHAeXchange EVV works for home care agencies
7 states use HHAeXchange as their EVV aggregator. What the aggregator requires is the same in all of them - here it is once, with a link to each state's own rules.
7 jurisdictions route Medicaid EVV through HHAeXchange (EVV Data Aggregator API): Illinois, Michigan, Minnesota, Mississippi, New Jersey, South Carolina, West Virginia. In each of them an agency can use the state's own HHAeXchange tools or its own EVV system, and an agency's own system has to deliver its visits to HHAeXchange in the aggregator's format. This page covers what is the same in every HHAeXchange state. Each state's page covers what is different there - its programs, its dates and its extra rules.
One aggregator: the HHAeXchange Data Aggregator API
A REST API with a token
OAuth client credentials, a caregiver record, visits in batches of up to a hundred, and a transactions endpoint that gives each visit its verdict. Members come from the payer's feed; the visit names them by Medicaid ID.
Ten published test cases
HHAeXchange publishes its interface test: authenticate, create and update a caregiver, five visits in a batch, one visit, a missed visit, an edit, a delete, and two that must fail. The software passes all ten against a faithful mock today, and runs them against the real implementation environment with one command.
Edits and missed visits carry codes
A corrected time carries the state's edit reason and action codes; a cancelled scheduled visit can be reported as a missed visit with its own codes.
What HHAeXchange wants, and where the app gets it
Every element HHAeXchange names, the record it comes from in the app, and where it lands. The format is the HHAeXchange EVV Data Aggregator API (state specification); each state adds its own addendum on top.
| Element | Where the app gets it | Where it lands |
|---|---|---|
| Caregiver | providerTaxID, qualifier and identifier (NPI or custom), name, hireDate, licence | caregivers endpoint |
| Visit | office, member (MedicaidID), caregiver, payerID, procedure code and modifiers, UTC schedule and visit times | visits endpoint |
| Clocks | clockIn / clockOut with call type, coordinates or originating phone, service address | evv{} |
| Edit | edited = true with reason and action codes and a note | editVisit{} |
| Missed visit | missed = true with reason and action codes | missedVisit{} |
| Identity | Our external visit id with the '~' prefix, so a resend updates rather than duplicates | evvmsId |
| Verdict | Transaction status per visit, at most five reads a second | transactions endpoint |
Getting started in a HHAeXchange state
- Sponsor and credentials. Your agency is the sponsoring provider: one attestation to the state and one to the aggregator, and the aggregator issues test credentials. We prepare both with you.
- Configure from the preset. Finance → EVV aggregators: the state's preset fills qualifiers, reason codes and config from the published addendum; the issued ids and credentials go on top. The account says Ready when nothing is missing.
- Certify. We run the aggregator's test cases against their test environment with your test patients, fix anything they flag, and ask for their review. Then production credentials.
- Go live. Flip the account to production and turn the worker on. From then on every closed Medicaid visit is queued at clock-out and reaches the aggregator within minutes, with its verdict read back.
Status: the HHAeXchange connector is built to the published specification and tested against it. Certification is completed state by state, with the first agency in that state as sponsoring provider, before any production visit is sent.
Questions about HHAeXchange EVV
Do our caregivers have to use HHAeXchange's app?
No. The free HHAeXchange app is the state's default; an agency with its own system sends the same visits into the aggregator through the API. Caregivers use one app.
What does the certification involve?
HHAeXchange issues implementation credentials and test patients under a sponsoring provider, we run their ten published test cases, and they review their logs before issuing production credentials. We do this with your agency as sponsor, at no cost to you.
Do we still have to use HHAeXchange for billing?
That depends on the state: some route claims through HHAeXchange, most do not. In every case the visit record the aggregator holds is the one the claim is checked against, and this software produces both.
Can we start before the certification is done?
Yes. Scheduling, documents, billing and the caregiver app work from day one; Medicaid visits queue for the aggregator and go the day the account is live.
See how your state's EVV comes out of a real visit.
Twenty minutes on a screen-share, end to end, in your state's format. No obligation.