How Netsmart EVV works for home care agencies
3 states use Netsmart 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 Netsmart Mobile Caregiver+: Georgia, Montana, Nebraska. In each of them an agency can use the state's own Netsmart tools or its own EVV system, and an agency's own system has to deliver its visits to Netsmart in the aggregator's format. This page covers what is the same in every Netsmart state. Each state's page covers what is different there - its programs, its dates and its extra rules.
One aggregator: Netsmart Mobile Caregiver+, by file
Rendered-services feed over SFTP
Netsmart takes a rendered-services file over SFTP in the state's format and answers with a response file. The software builds it — including overnight visits split at midnight the way the guide prescribes — uploads it, and reads the verdicts back.
The state's type codes
Jurisdiction, payer, plan, delivery system and time-zone codes come from the state's quick reference guide; the column order comes from the data dictionary delivered at onboarding. Both live on the account.
Attestations on both sides
The provider attests to the state, the vendor attests to Netsmart, and the integration is tested on a sample file.
What Netsmart wants, and where the app gets it
Every element Netsmart names, the record it comes from in the app, and where it lands. The format is the Netsmart Alternate EVV Vendor Implementation Guide + the Rendered Services data dictionary; each state adds its own addendum on top.
| Element | Where the app gets it | Where it lands |
|---|---|---|
| Visit row | Provider Medicaid ID, member ID, caregiver ID, service code and modifier, start/end times | rendered services file |
| Type codes | Jurisdiction, payer, plan, delivery system, time zone | account config |
| Verification | GPS at each end, or telephony; who signed / unable to sign | rendered services file |
| Manual entries | Edit code and reason | rendered services file |
| Overnight visits | Split at midnight into two rows | rendered services file |
| Verdict | Response file per upload, read back per visit | response file |
Getting started in a Netsmart 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 Netsmart 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 Netsmart EVV
Do our caregivers have to use Mobile Caregiver+?
No. It is the state's free option; an agency with its own system sends a rendered-services file into the same aggregator. In some states the billing provider still keeps a Mobile Caregiver+ login to release visits.
What does onboarding involve?
The two attestations, SFTP credentials and the data dictionary from Netsmart under a sponsoring provider, then a sample file review. 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.