Best for
Manual portal upload
A single-state agency with very low Medicaid visit volume and staff time to spare.
Home care agencies can upload to a state portal, use the state-provided EVV system, rely on their EMR, build an integration in-house, or use a dedicated transmission service like EVV Bridge. Here is how they differ and when each one fits.
If your EMR already connects reliably to every aggregator you bill through, you may not need anything else. EVV Bridge fits agencies in several states, agencies whose EMR lacks a dependable aggregator connection, and franchise systems or EMR vendors that want to hand off transmission maintenance. It keeps your EMR as the system of record and sends one feed to each state aggregator.
Approaches, not vendors. Capabilities of a specific EMR or state system vary, so confirm the details for yours.
| Consideration | Manual portal upload | State-provided EVV system | EMR built-in interface | Build in-house | EVV Bridge |
|---|---|---|---|---|---|
| Keep your current EMR and caregiver app | Yes, with re-keying or file export | Often no: caregivers use the state app, or staff double-enter | Yes | Yes | Yes |
| Who keeps up with aggregator specification changes | Your office staff | The state vendor | Your EMR vendor, on its own roadmap | Your engineering team | Syndech |
| Validation against aggregator rules before submission | Manual review | Inside the state system | Varies by vendor | Whatever you build | Every record, with issues surfaced to your team |
| Several states or aggregators from one data source | One portal per state | One system per state | Only the aggregators your EMR supports | One integration per aggregator | One feed, routed to each aggregator |
| Acknowledgement and rejection tracking | Checked by hand | In the state system | Varies by vendor | Whatever you build | Per-record status and audit log |
| Cost model | Staff hours | Usually no license fee, plus staff time | Included or an add-on fee | Engineering build plus ongoing support | Per transmission, no monthly minimum |
| VA community care EVV (2027) | Depends on contractor process | Medicaid systems do not cover VA | Depends on vendor roadmap | A new integration to build | Being added as regional contractor specifications are published |
A single-state agency with very low Medicaid visit volume and staff time to spare.
An agency without its own EMR that is comfortable using the state app for visit capture.
An agency whose EMR already connects reliably to every aggregator it bills through, with good rejection reporting.
An organization with dedicated integration engineers that wants to own every aggregator connection long term.
Agencies in several states, agencies whose EMR lacks a reliable aggregator connection, and franchise systems or EMR vendors that want to hand off transmission maintenance while keeping their EMR as the system of record.
No. Sandata and HHAeXchange run the aggregators that many states use to receive EVV data. EVV Bridge is a transmission service that sends your visit data to those aggregators, so it works alongside them rather than replacing them.
Not necessarily. If your EMR connects reliably to every aggregator you bill through and reports rejections clearly, it may be enough. EVV Bridge helps when the EMR does not support one of your aggregators, when rejections are hard to see, or when you operate in several states.
For some agencies, yes. The trade-off is usually double entry: caregivers clock in on the state app while the agency schedules and bills in its own EMR. EVV Bridge lets agencies keep their EMR as the single source and transmit from it.
An all-in-one platform replaces your scheduling, billing, and caregiver app. EVV Bridge does one job, EVV transmission, and sits beside the system you already use, so there is no platform migration.
When you have integration engineers dedicated to it for the long term. Each aggregator has its own specification, certification process, and change cycle, so the ongoing maintenance usually costs more than the first build.