Home health care app development succeeds or fails on one thing. Can a caregiver clock a visit in 10 seconds, with no signal, and have it pass your state's EVV checks? Get that right and scheduling, billing and payroll follow. Get it wrong and you get denied claims and caregivers back on paper.

We have built visit capture, scheduling and documentation software for agencies that bill Medicaid and Medicare. This guide covers the features you need and the rules that shape the build. It also covers integrations, cost, and the mistakes we see most.

The five features every home health app needs

Most agency software tries to do everything. The apps that caregivers actually use do five things well.

1. Electronic visit verification that matches your state

EVV is not just a clock-in button. It must record six data points: service type, client, caregiver, date, location, and start and end times. If one is missing or mismatched, the aggregator rejects the visit and the claim stalls.

Build three capture methods. Use GPS on the phone, a telephony (IVR) fallback from the client's landline, and a manual edit path with reason codes. Supervisors will use that edit path every week, and auditors will want every edit logged.

2. Scheduling that knows the rules

A schedule is a matching problem. The system has to weigh skills, licenses, language, client preferences, drive time and overtime limits. A scheduler who sees that a shift pushes an aide past 40 hours, before booking it, saves real money.

Under the Department of Labor's 2015 home care rule, most agency-employed aides are owed minimum wage and overtime. Travel time between clients in the same workday generally counts as hours worked. Your scheduler should show those costs, not hide them.

3. Point-of-care documentation

Caregivers chart at the bedside or in the car. Care-plan tasks, vitals, notes and client signatures belong on the phone. Skilled Medicare agencies also need OASIS assessments, which feed quality scores and payment.

Keep forms short for aides. A personal care visit typically needs a task checklist and a note, not a 40-field form.

4. Offline mode that does not lose data

Rural routes, basements and apartment blocks kill signal. The app must store the visit locally, record device time, and sync when it can. Conflicts, like an office edit to a visit the aide just changed offline, need clear rules rather than last-write-wins.

5. Billing and payroll handoff

Verified visits should become claim lines and payroll hours with no retyping. Every manual re-key risks a mismatch between what you billed and what EVV shows. That mismatch is exactly what Medicaid auditors look for.

Secure messaging, family portals and route maps are useful. They are phase-two features. Ship the five above first.

If you want a second opinion before you commit budget, you can talk to an engineer who has built in your industry.

Compliance rules that shape the build

Regulation decides your architecture more than your feature list does. These are the rules we design around from day one.

21st Century Cures Act, Section 12006 (EVV)

The Cures Act requires states to use EVV for Medicaid personal care and home health care services. The deadlines were January 2020 for personal care and January 2023 for home health. Some states received one-year extensions. CMS publishes guidance and state status on Medicaid.gov.

The caveat is that federal law sets the data points, but each state picks its own model. Some mandate a single vendor. Others run an open model where your app sends data to a state aggregator. Medicare-only home health does not currently require EVV, though many agencies use it anyway.

HIPAA Privacy and Security Rules

Every visit record is protected health information. The HIPAA Security Rule requires access controls, audit controls, a documented risk analysis and safeguards such as encryption. In practice, that means encrypted device storage, remote wipe, role-based access and an audit trail on every read and edit.

You also need a business associate agreement (BAA) with every vendor that touches the data. That includes your cloud host, SMS provider and error-logging tool. AWS, Google Cloud, Azure and Twilio offer BAAs, but only for specific services you must configure correctly. NIST Special Publication 800-66 Revision 2 is a practical guide to implementing the Security Rule.

HITECH breach notification

A lost phone with unencrypted visit notes can become a reportable breach. Breaches affecting 500 or more people must be reported to HHS and local media within 60 days of discovery. Device encryption and remote wipe are what turn a lost phone into a non-event.

Medicare Conditions of Participation

Skilled agencies must meet the home health Conditions of Participation in 42 CFR Part 484. They govern care plans, clinical records and OASIS submission through CMS's iQIES system. Your records need signed, time-stamped entries that cannot be silently edited, so they survive a state survey.

Location permissions

EVV needs location, and app stores police it closely. Apple requires a clear purpose string for location access, covered in its Core Location documentation. Capture location at clock-in and clock-out only. Continuous tracking drains batteries, draws review questions and invites labor complaints.

Integrations you will almost certainly need

  • State EVV aggregator. Sandata and HHAeXchange are common state-selected vendors. Each has its own data spec and a certification test before go-live.
  • EHR or agency platform. If you run WellSky, Axxess, MatrixCare or HomeCare HomeBase, decide early whether your app extends it or replaces part of it.
  • Clearinghouse. Claims typically go out as X12 837 files through Availity or Waystar, with 835 remittances coming back.
  • Payroll. ADP, Paychex or Gusto, fed with verified hours, overtime and mileage.
  • Telephony and SMS. An IVR line for EVV fallback and shift reminders, from a provider that signs a BAA.
  • Mapping. Google Maps or Mapbox for drive-time estimates in scheduling.

The aggregator is usually the long pole. Certification typically takes 4 to 10 weeks, and you cannot speed up the state's test queue. Start it in month one, not month five.

What home health care app development costs and how long it takes

These are typical ranges for US-based builds. Scope, state count and existing systems move the number.

Caregiver app plus office scheduling, one state: $120K to $250K, 5 to 8 months

This covers a caregiver app, a web admin for schedulers, and EVV with GPS and IVR fallback. It also includes offline sync, one aggregator integration and a payroll export. It is what a single-state personal care agency typically needs.

Full platform, multiple states: $300K to $600K, 9 to 14 months

This adds clinical documentation and OASIS, clearinghouse claims, several aggregators, a family portal and reporting. Each extra state typically adds 3 to 6 weeks of aggregator work.

Running costs

Budget 15% to 25% of the build cost per year for maintenance, OS updates, spec changes and hosting. States revise EVV specs more often than most founders expect. A missed spec update can stop claims within weeks.

A cross-platform framework such as Flutter or React Native typically saves 25% to 35% on mobile versus two native apps. A caregiver app is mostly forms, lists and location. For that workload, the trade-off is usually worth it.

Three mistakes first-time buyers make

1. Designing for the office, not the caregiver

Owners demo the app on a laptop. Aides use it on a three-year-old Android phone, between visits, sometimes in gloves. If clock-in takes more than three taps, aides call the office instead and your EVV compliance rate drops.

Test with real aides on their own phones before you sign off on design.

2. Assuming EVV works the same everywhere

A build that passes in one state can fail in the next. Service codes, location tolerance, reason codes and submission windows all differ. Ask for a per-state integration layer from the start, so a new state means configuration and testing, not a rewrite.

3. Treating HIPAA as a hosting choice

"We host on a HIPAA-compliant cloud" is not compliance. The cloud provider covers its own layer only. Your app still needs device encryption, session timeouts, audit logs, a risk analysis and BAAs with every third-party SDK.

Crash-reporting and analytics tools are the usual leaks. Some capture screen data or form fields by default.

Two questions to ask any agency before you hire them

"Walk me through a visit clocked in offline that syncs four hours later."

A good answer covers device time versus server time and how the app detects clock tampering. It should also cover what the aggregator receives and when, and what happens if the office edited the visit meanwhile. A vague answer means they have not built this before.

"Which state aggregators have you certified against, and who runs the test?"

You want named aggregators and a clear owner for certification. If the agency expects your staff to run the state's test cycle, add that time to the plan.

FAQ

Is EVV required for Medicare home health visits?

Not under current federal rules. The Cures Act mandate covers Medicaid personal care and home health services. Many agencies still use EVV for Medicare visits because one workflow is simpler than two.

Can we build our own app and keep our existing EHR?

Yes, if the EHR offers an API or a supported data export. Many agencies keep the EHR for clinical records and billing, then add a custom caregiver app for scheduling and EVV. Confirm API access and fees with your EHR vendor before scoping.

How long does it take to build a home health app?

A focused single-state caregiver and scheduling app typically takes 5 to 8 months. A multi-state platform with clinical documentation and billing typically takes 9 to 14 months. State aggregator certification often sets the final launch date.