How Therap EVV works for home care agencies
3 states use Therap 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.
3 jurisdictions route Medicaid EVV through Therap: Alaska, Kentucky, South Dakota. In each of them an agency can use the state's own Therap tools or its own EVV system, and an agency's own system has to deliver its visits to Therap in the aggregator's format. This page covers what is the same in every Therap state. Each state's page covers what is different there - its programs, its dates and its extra rules.
One aggregator: Therap's third-party API
A REST API with a token
Each visit is posted as JSON to Therap's endpoint with a bearer token; Therap answers per visit. The field names follow the state's data dictionary and are configurable on the account.
Vendor approval
Therap approves the vendor and issues the base URL, token and data dictionary under a sponsoring provider; the state then lists the system as approved.
Near-real-time
States on Therap expect visits within a day; the software queues every closed visit at clock-out and sends within minutes.
What Therap wants, and where the app gets it
Every element Therap names, the record it comes from in the app, and where it lands. The format is the Therap third-party EVV REST API + the state data dictionary; each state adds its own addendum on top.
| Element | Where the app gets it | Where it lands |
|---|---|---|
| Visit | Provider ID, recipient Medicaid ID, staff ID, service code and modifier, authorization | visits endpoint |
| Times | Start/end in UTC, capture method at each end | visits endpoint |
| Locations | Latitude/longitude at each end, or the phone for telephony; service address | visits endpoint |
| Manual entries | The state's reason code and note | visits endpoint |
| Identity | Our stable visit id and sequence, so a resend updates | visit_id / sequence |
| Verdict | Per-visit response, read back | response |
Getting started in a Therap 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 Therap 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 Therap EVV
Do our caregivers have to use Therap's app?
No. Therap's app is the state's free option; an approved third-party system sends the same visits into the Therap aggregator. Caregivers use one app.
What does approval involve?
Therap reviews the integration, issues credentials and the data dictionary under a sponsoring provider, and the state records the approval. We do this with your agency as sponsor, at no cost to you.
Can we start before approval is done?
Yes. Everything but the send works from day one; visits queue 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.