Home Health Software Development: EVV, OASIS, Scheduling and Cost
Key Takeaways
- Home health software development splits into three builds: a caregiver visit app ($60K–120K), an agency operations platform ($150K–300K) and a Medicare-certified clinical and billing system ($300K+).
- Electronic visit verification is federal law for Medicaid personal care and home health visits, and your EVV data has to land in each state’s aggregator in its format.
- Since January 2025, Medicare-certified agencies collect OASIS-E1 for every adult skilled patient regardless of payer, so OASIS is a core module rather than an add-on.
- Offline-first mobile design matters more than any feature on the roadmap, because caregivers document in basements, rural homes, and apartment blocks with no signal.
- Buy WellSky, Axxess, or AlayaCare if you run a standard Medicare agency. Build when your care model (foster care, private-pay, hybrid nursing) doesn’t fit their workflow.
Most agencies that approach us for home health software development already use several tools. They have a scheduling system, a separate EVV app provided by the state, a billing service, a shared drive full of scanned care plans, and a group chat where most of the coordination happens. They usually ask the same question: “Can we get everything together in one place that our caregivers will actually use?”
That question is harder than it sounds. This is because home health needs to consider two regulatory systems at once. Medicaid rules drive visit verification and state reporting.
A private-pay companion care agency may not need either, while an adult foster care provider mainly follows state licensing rules. Custom healthcare software development is worth building only when it matches the type of care your organisation provides.
This guide covers what a home health platform has to do, how electronic visit verification and OASIS shape the architecture, when custom healthcare software beats an off-the-shelf agency system, and what each tier costs to build in 2026.
What Is Home Health Software Development?
Home health software development means building the systems an agency uses to deliver care in patients’ homes. This includes intake and referrals, caregiver scheduling, visit documentation, electronic visit verification, clinical assessments, billing and the compliance reporting that ties them together.
It helps to separate three business models, because they need different software:
| Model | Who pays | What drives the software |
|---|---|---|
| Skilled home health (nursing, therapy) | Medicare, Medicare Advantage, commercial | OASIS assessments, plans of care, PDGM billing periods |
| Personal care / home care (non-medical) | Medicaid waivers, private pay, long-term care insurance | EVV, caregiver scheduling, timesheets, payroll |
| Adult foster care and group homes | Medicaid HCBS waivers, state programs | State licensing records, medication administration, incident reports |
A home care agency software stack for a private-pay companion service can be a scheduling app with GPS check-in and invoicing. Whereas, Medicare-certified home health agency software stack needs clinical documentation that survives a survey. Many agencies run two of these models under one roof, which is where off-the-shelf systems become difficult to use.
Which Features Does Home Health Software Need?
The core modules repeat across almost every build. What changes is how deep each one goes. Below are the features needed by home health software:
Referral intake and patient onboarding
Referrals arrive by fax, e-referral portals, email and phone. The intake module captures demographics, payer, physician orders and face-to-face documentation. It further checks eligibility before the first visit is scheduled. Agencies that skip eligibility checks at intake spend the next month chasing denied claims.
Home health scheduling software
Scheduling in home care is a constraint problem. It is impacted by a lot of factors such as caregiver skills and certifications, patient preferences, travel time between homes, overtime thresholds and continuity of care (families want the same aide). A good caregiver scheduling app handles open shifts, shift swaps and last-minute call-offs by pushing the gap to qualified staff nearby, instead of leaving a coordinator to go through a list.
Visit documentation and care plans
Caregivers complete task checklists (bathing, meals, medication reminders) and nurses complete clinical notes against the plan of care. Documentation must work offline and sync later. It should also capture signatures and attach photos of wounds or incidents.
Electronic visit verification
EVV proves the visit happened. Below you can find in detail criteria on this , because it shapes your data model.
Billing, payroll and reporting
Visits become billable units and payable hours. For Medicaid this means state specific billing codes and units. For Medicare, it means 30 day payment periods. The billing module either feeds a clearinghouse directly or exports clean data to your billing service. The claims process, including handling denials and resubmitting claims, works much like any healthcare claim management system development project.
Family and physician communication
Family portals and secure messaging reduce inbound calls, which in most agencies consume hours of coordinator time each week.
How Does Electronic Visit Verification Work in Home Care Software?
According to the Section 12006 of the 21st Century Cures Act, it is mandatory for the states to use electronic visit verification for Medicaid-funded personal care services and home health care services. The personal care deadline was January 2020 (most states took extensions). The home health care deadline was January 2024. CMS publishes the requirements and state status on its electronic visit verification guidance page.
Every EVV record has to capture six data points:
- Type of service performed
- Individual receiving the service
- Date of service
- Location of service delivery
- Individual providing the service
- Time the service begins and ends
Although the federal EVV rule is only one page long, states handle it in very different ways. Some require agencies to use the state’s own system, while others let agencies choose their own EVV software. In these open models, a state aggregator like Sandata or HHAeXchange collects the data, provided it meets the state’s format requirements. So, before building your software, check the state’s rules. A closed model means connecting to the state system, while an open model may allow your caregiver app to manage EVV directly.
Technically, an EVV system needs to track when caregivers arrive and leave. It can be either through GPS or phone check-ins. It should handle geofence tolerance for large properties and offer another option for caregivers without smartphones. For example, something as simple as IVR from the patient’s landline. It must also let staff correct visit records and explain why each change was made. Since states closely check manual edits, every change needs to be recorded rather than allowing coordinators to quietly alter times.
We used the same check-in, geolocation, and supervisor verification pattern when we built a field staff tracking app for 1,500 workers for a facility management company. The domain was cleaning, not care, but the engineering problem (proving who was where, and when, without trusting a paper log) is still the same one EVV solves.
What Is OASIS Software, and Do You Need It?
The Outcome and Assessment Information Set (OASIS) is the patient assessment Medicare-certified home health agencies must complete at start of care, resumption, recertification, transfer and discharge. OASIS-E1 took effect on January 1, 2025, and CMS now requires OASIS collection for all adult skilled patients regardless of payer, with narrow exceptions such as maternity-only or personal-care-only patients. You can find these on the CMS OASIS data sets page.
OASIS affects your build in three ways:
- Payment. OASIS functional items feed the Patient-Driven Groupings Model (PDGM), which sets Medicare payment for each 30-day period. Errors in OASIS become payment errors.
- Quality reporting. OASIS data drives Home Health Quality Reporting Program measures and star ratings.
- Submission. Assessments are submitted to CMS through iQIES, which means your system must export valid submission files and track acceptance.
If you run a non-medical home care agency, you don’t need OASIS software at all. However, if you’re a Medicare-certified agency, OASIS is where most custom builds get expensive. This is because the item logic, skip patterns, and validation rules change with each CMS release. This is the strongest reason certified agencies usually buy a clinical core and customize around it.
How Should Home Health App Development Handle Offline Caregivers?
The caregiver app can make or break your platform. Coordinators may put up with a clunky admin screen, but caregivers with only 15 minutes between visits and a phone battery at 20% won’t work with a slow app for long.
Four design rules we apply to every home care app:
- Offline-first data. Store the day’s schedule, care plans and checklists on the device. Queue check-ins, notes and signatures locally with timestamps, then sync when a signal returns. Resolve conflicts on the server with clear rules.
- Short task flows. A personal care visit shouldn’t need more than a few taps to document. Checklists with defaults beat free-text notes.
- Multilingual UI. Home care workforces are multilingual. Spanish at minimum in most US markets.
- Low-end device support. Many caregivers use older Android phones. Test on them.
A cross-platform framework makes sense here because one codebase serves iOS and Android caregivers. Moreover, the offline storage libraries are mature on both. Our React Native app development team typically pairs it with SQLite or WatermelonDB for local storage and a sync service on the backend.
Does Home Care Software Development Fit Foster Care and Group Homes?
Adult foster care and group home providers are often poorly served by mainstream home health products, which assume a caregiver visits many patients. In foster care, the caregiver lives with a small number of residents, and the records look different. This includes daily logs, medication administration records (MARs), behavior and incident reports, house meetings, and the documentation state licensing reviewers ask for.
What these providers usually need:
- A medication administration record with scheduled doses, PRN tracking and refusal reasons
- Incident reporting with required notification timers (states often require reporting within 24 hours)
- Task assignments and reminders so each staff member knows what’s due today
- Case manager access for the county or managed care organization
This is where home care software development pays off most clearly. The workflow is specific, the off-the-shelf fit is poor, and the build is smaller than a Medicare clinical system. Most of the value comes from replacing paper and manual follow-ups with automatic notifications. This is the same kind of healthcare workflow automation that removes the “did anyone call the family?” problem.
Should You Build or Buy Home Health Agency Software?
| Situation | Recommendation |
|---|---|
| Standard Medicare-certified agency, single state | Buy, integrate what’s missing |
| Private-pay or companion care with a premium service model | Build a lighter custom platform |
| Adult foster care, group homes, IDD services | Build, or extend a small platform |
| Multi-state personal care with open-model EVV states | Build the caregiver app and EVV layer, buy billing |
| Hybrid nursing plus care coordination startup | Build, the vendors won’t fit |
Which Compliance Rules Apply to Home Healthcare Software Development?
Home healthcare software development handles protected health information on personal devices in uncontrolled locations, which increases the stakes on security and calls for relevant compliance rules.
- HIPAA. Encrypt data at rest on the device and in transit, enforce device PINs or biometrics, support remote wipe, and log every access. Every cloud vendor that touches PHI needs a business associate agreement. A HIPAA-compliant software development process builds these controls in from the first sprint rather than adding it later.
- EVV state specifications. Treat each state’s EVV spec as a versioned integration with its own test cases.
- Medicare Conditions of Participation. Clinical records must support survey requirements, including plan of care updates and supervisory visits for aides.
- Labor rules. Travel time between visits, overtime and meal breaks are wage-and-hour issues. Your scheduling and payroll logic must follow federal and state rules, and caregivers need access to their own hours.
How Much Does Home Health Software Development Cost?
Below are illustrative planning ranges for US-market builds with HIPAA controls. Actual quotes depend on integrations, clinical requirements, and delivery assumptions. The number of states you operate in changes it the most.
| Build | Scope | Planning estimate | Timeline |
|---|---|---|---|
| Caregiver visit app | Scheduling view, GPS check-in/out, task checklists, offline sync, admin web panel | $60K–120K | 3–5 months |
| Agency operations platform | Above plus intake, scheduling engine, EVV aggregator submission, family portal, payroll export | $150K–300K | 6–9 months |
| Certified clinical and billing system | Above plus OASIS-E1, plans of care, PDGM billing, iQIES submission, clinical QA | $300K–600K+ | 10–16 months |
You need to budget ongoing costs for state EVV spec updates, annual OASIS changes, cloud hosting under a BAA, app store maintenance, and support for caregiver devices. Plan for 15–20% of the build cost per year.
How to Choose a Home Health Software Development Partner
In order to choose a Home Health Software Development partner, ask these questions:
- Have you built offline-first mobile apps that sync clinical data? Ask for a demo in airplane mode.
- Which state EVV aggregators have you integrated with, and how do you handle spec changes?
- How do you test with real caregivers, not just coordinators?
- What’s your approach to HIPAA on personal devices?
- Who owns the code and the data model at the end of the engagement?
Also ask how they plan to test visit edge cases such as split shifts, missed check-outs and two caregivers in one home. A partner with a structured healthcare software testing process will have those scenarios written before development starts. If you mainly need staff communication and task tracking, Tech Exactly’s employee management mobile app solutions for healthcare cover that without a full platform build.
Home health software works best when it fits the way caregivers work in the field and includes the right compliance rules for your care model from the start.
Frequently Asked Questions
For standard Medicare-certified agencies, WellSky, Axxess and Homecare Homebase are the most widely used. For personal care and private-pay agencies, AlayaCare and AxisCare are common. Custom software is a better choice when your care model or the states you operate in don't fit what these products offer.
A caregiver visit app with EVV check-in and offline sync typically costs 60K–120K. Whereas, a full agency platform with scheduling, EVV submission and billing costs 150K–300K. A Medicare certified clinical system with OASIS costs $300K or more.
No, it is not. The federal EVV mandate applies to Medicaid funded personal care and home health services. Many private-pay agencies still use GPS check-in because families and long-term care insurers ask for proof of visits.
No, they do not. OASIS applies only to Medicare certified home health agencies providing skilled services. Personal-care-only patients are excluded from OASIS collection.
It should ideally. An offline-first app stores schedules and care plans on the device. It records visits with timestamps and syncs when a connection returns. Apps that require a live connection lose data in rural areas and large buildings.
A caregiver app MVP takes 3–5 months. An agency operations platform takes 6–9 months. A certified clinical and billing system takes 10–16 months, mainly because of OASIS and payer testing.
