How CareBridge EVV works for home care agencies
2 states use CareBridge 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.
2 jurisdictions route Medicaid EVV through CareBridge: Tennessee, Wyoming. In each of them an agency can use the state's own CareBridge tools or its own EVV system, and an agency's own system has to deliver its visits to CareBridge in the aggregator's format. This page covers what is the same in every CareBridge state. Each state's page covers what is different there - its programs, its dates and its extra rules.
One aggregator: CareBridge, by file
A file, not an API
CareBridge takes a pipe-delimited visit file over SFTP and answers with a response file. The software writes the file in the state's column order, uploads it, and reads the response back into each visit.
Column order from the state spec
CareBridge's field names and rules are public; the exact column order for a state is in its technical specification, handed over at onboarding. It goes on the account, not into code.
Free integration, one attestation
The state's CareBridge integration is free to the provider; onboarding is an attestation, SFTP credentials and a sample file review.
What CareBridge wants, and where the app gets it
Every element CareBridge names, the record it comes from in the app, and where it lands. The format is the CareBridge third-party vendor file (pipe-delimited over SFTP), state technical specification; each state adds its own addendum on top.
| Element | Where the app gets it | Where it lands |
|---|---|---|
| Visit row | Provider ID, member Medicaid ID, caregiver ID, service code and modifiers, start/end times | visit file |
| Locations | Latitude/longitude at start and end, or the client's phone for telephony | visit file |
| Manual entries | The state's reason code and a note | visit file |
| Identity | Our stable visit id, so a re-upload updates the same visit | ApptID |
| Transport | SFTP with a key pair; the state's file name pattern | SFTP |
| Verdict | Response file per upload, read back per visit | response file |
Getting started in a CareBridge 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 CareBridge 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 CareBridge EVV
Do our caregivers have to use CareBridge's app?
No. CareBridge's app is the free default; an agency with its own system sends a visit file into the same aggregator. Caregivers use one app.
What does onboarding involve?
An attestation, SFTP credentials and the state's column specification from CareBridge under a sponsoring provider, then a sample file they review. We do this with your agency as sponsor, at no cost to you.
How often do visits go?
Every closed visit is queued at clock-out and the file goes on the cadence the state sets — typically daily. The response file comes back and each visit shows accepted or rejected with the reason.
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.