Homecare AppHome care software › Georgia
Home care software · Georgia EVV

Home care software built for Georgia Medicaid EVV.

Georgia routes EVV through Netsmart Mobile Caregiver+. Homecare App captures every Medicaid visit with GPS clock-in and clock-out, coded reasons and an audit trail, and its Netsmart connector is built to the published specification — the certification is completed with your agency as the sponsoring provider, at no cost to you.

GPS clock-in & out Phone-line clock by PIN Offline queue Coded reasons & audit trail
Web-based, nothing to install. Hosted on AWS under a Business Associate Agreement.
Where this standsStatus in Georgia: the Netsmart connector is built to the published specification and tested against it and against a faithful mock of the aggregator. It is not yet certified in Georgia; certification is completed with the first Georgia agency as sponsoring provider, before any production visit is sent.
Home care software for Georgia agencies

Built for how Georgia actually receives EVV

Georgia agencies live inside two sets of rules: Georgia Department of Community Health's, and Netsmart's. The software was built to both — the state's EVV requirements in the visit record, Netsmart's interface in the connector — so the agency does the work once and the aggregator gets it in its own format. Open vendor model.

  • ProgramGeorgia Department of Community Health
  • Servicespersonal support, community living support, home health and the CCSP, SOURCE and NOW/COMP waivers
  • Serving agencies inAtlanta, Augusta, Savannah, Columbus, Macon and Athens
How EVV works in Georgia

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.

Georgia specifics

A third-party attestation is signed by the provider (to DCH) and by the vendor (to Netsmart), followed by full Netsmart integration.

Requirements

What Netsmart wants, and where the app gets it

Every element the state names, the record it comes from in the app, and where it lands.

ElementWhere the app gets itWhere it lands
Visit rowProvider Medicaid ID, member ID, caregiver ID, service code and modifier, start/end timesrendered services file
Type codesJurisdiction, payer, plan, delivery system, time zoneaccount config
VerificationGPS at each end, or telephony; who signed / unable to signrendered services file
Manual entriesEdit code and reasonrendered services file
Overnight visitsSplit at midnight into two rowsrendered services file
VerdictResponse file per upload, read back per visitresponse file
In the software

What the office and the caregiver actually see

An EVV visit detail with GPS pins at clock-in and clock-out
A visit's EVV record — server times, GPS at both ends, the caregiver, the reason if a time was typed
The Finance → Claims page listing claim batches by payer
Finance — the aggregator queue lives beside the claims it backs
Getting started

Your first month in Georgia

Sponsor and credentialsYour 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 presetFinance → 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.
CertifyWe 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 liveFlip 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.

Want to see this on your own visits? Twenty minutes on a screen-share, in Georgia's format.

Book the demo
Questions

Questions Georgia agencies ask

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.

Which Georgia programs does this cover?

Personal support, community living support, home health and the CCSP, SOURCE and NOW/COMP waivers — every service Georgia Department of Community Health requires EVV for. A third-party attestation is signed by the provider (to DCH) and by the vendor (to Netsmart), followed by full Netsmart integration.

Sources

The Georgia documents this page is written from

Read the state's own words; the page above is our summary of them as of 2026-09-21.

See a visit become a Netsmart file row.

Twenty minutes on a screen-share: clock-in, clock-out, and the Netsmart record for that visit. If it is not a fit you will know in five.

Tell us where to reach you

Thank you.We will call to set a time, usually within one business day.