How AuthentiCare EVV works for home care agencies
3 states use AuthentiCare 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 AuthentiCare (Fiserv): Arkansas, Kansas, New Hampshire. In each of them an agency can use the state's own AuthentiCare tools or its own EVV system, and an agency's own system has to deliver its visits to AuthentiCare in the aggregator's format. This page covers what is the same in every AuthentiCare state. Each state's page covers what is different there - its programs, its dates and its extra rules.
One aggregator: AuthentiCare, by daily file
A daily file over SFTP
AuthentiCare takes a daily pipe-delimited file of completed visits over SFTP and answers with a response file; the software builds, uploads and reads it back.
The interface guide's columns
Field names and rules come from Fiserv's Data Aggregator Interface Guide, delivered at onboarding; the column order lives on the account.
Declaration and attestation
The agency declares its system to the state, the vendor attests its configuration, and a single test run per vendor precedes production.
What AuthentiCare wants, and where the app gets it
Every element AuthentiCare names, the record it comes from in the app, and where it lands. The format is the AuthentiCare Data Aggregator Interface Guide (daily file over SFTP); each state adds its own addendum on top.
| Element | Where the app gets it | Where it lands |
|---|---|---|
| Visit row | Provider ID, member ID, caregiver ID, service code and modifier, start/end times | daily file |
| Locations | Latitude/longitude at each end, or the client's phone for telephony | daily file |
| Manual entries | The state's reason code and note | daily file |
| Identity | Our stable visit id, so a re-send updates | visit id |
| Transport | SFTP with a key pair; the state's file name pattern; completed visits only | SFTP |
| Verdict | Response file per upload, read back per visit | response file |
Getting started in a AuthentiCare 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 AuthentiCare 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 AuthentiCare EVV
Do our caregivers have to use AuthentiCare's app?
No. AuthentiCare's app is the state's free option; a declared third-party system sends a daily file into the same aggregator. Caregivers use one app.
What does onboarding involve?
The state's declaration and attestation, SFTP credentials and the interface guide from Fiserv under a sponsoring provider, then one test run. We do this with your agency as sponsor, at no cost to you.
Can we start before onboarding 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.