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

Home care software built for Kansas Medicaid EVV.

Kansas routes EVV through AuthentiCare (Fiserv). Homecare App captures every Medicaid visit with GPS clock-in and clock-out, coded reasons and an audit trail, and its AuthentiCare 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 Kansas: the AuthentiCare 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 Kansas; certification is completed with the first Kansas agency as sponsoring provider, before any production visit is sent.
Home care software for Kansas agencies

Built for how Kansas actually receives EVV

Kansas agencies live inside two sets of rules: KanCare (Kansas Department of Health and Environment)'s, and AuthentiCare's. The software was built to both — the state's EVV requirements in the visit record, AuthentiCare's interface in the connector — so the agency does the work once and the aggregator gets it in its own format. Provider choice with state approval — restrictive.

  • ProgramKanCare (Kansas Department of Health and Environment)
  • Servicespersonal care, HCBS waivers under the KanCare MCOs, and home health
  • Serving agencies inWichita, Kansas City, Overland Park, Topeka, Lawrence and Manhattan
How EVV works in Kansas

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.

Kansas specifics

Third-party vendors must be authorized by the State and integrate with AuthentiCare. Since March 1, 2025 original claims must be submitted through AuthentiCare, so the integration must feed its claim path.

Requirements

What AuthentiCare 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 ID, member ID, caregiver ID, service code and modifier, start/end timesdaily file
LocationsLatitude/longitude at each end, or the client's phone for telephonydaily file
Manual entriesThe state's reason code and notedaily file
IdentityOur stable visit id, so a re-send updatesvisit id
TransportSFTP with a key pair; the state's file name pattern; completed visits onlySFTP
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 Kansas

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 Kansas's format.

Book the demo
Questions

Questions Kansas agencies ask

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.

Which Kansas programs does this cover?

Personal care, HCBS waivers under the KanCare MCOs, and home health — every service KanCare (Kansas Department of Health and Environment) requires EVV for. Third-party vendors must be authorized by the State and integrate with AuthentiCare. Since March 1, 2025 original claims must be submitted through AuthentiCare, so the integration must feed its claim path.

Sources

The Kansas 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 an AuthentiCare file row.

Twenty minutes on a screen-share: clock-in, clock-out, and the AuthentiCare 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.