Most home health agencies don’t start shopping for new EHR software because someone had a slow afternoon to think about it — they start because a clinician lost an hour of notes when a tablet dropped signal mid-visit, or an OASIS assessment came back kicked for a formatting error nobody caught until the reimbursement was already at risk. If that’s the moment you’re in, a generic clinic-EHR buyer’s guide won’t help much. Home health doesn’t happen in one building with dependable Wi-Fi — it happens in dozens of different homes a day, on a schedule built around drive time, often on hardware that’s a few years old. That changes which features actually matter, and it’s worth evaluating home health EHR software against that reality instead of a checklist written for a clinic down the street.
Does it document visits offline, without losing notes when the signal drops?
A home health visit note has to get written somewhere with no guaranteed connection — a basement, a rural address, a building with dead cell coverage. Software that assumes an always-on connection either blocks the clinician from finishing the note or, worse, silently loses what they typed. What actually matters is an app built offline-first from the ground up: full charting functionality with no connection at all, and an automatic, conflict-free sync the moment a signal comes back. That’s a different engineering problem than bolting “offline mode” onto a web app after the fact, and it shows up in the field the first time a clinician hits a dead zone. A native, offline-capable field documentation app built for the tablets your agency already issues — not a browser tab that assumes it’s always connected — is the baseline, not a premium feature.
Does it handle OASIS assessments as part of the same visit, not a separate form?
OASIS timelines carry real reimbursement and compliance stakes, and clinicians already do enough documentation without re-keying the same patient data into a second form. Good home health EHR software builds structured OASIS data collection directly into the visit workflow — the same fields the clinician is already charting against, validated as they go, instead of a standalone assessment bolted on afterward that has to be reconciled by hand. If your current system treats OASIS as a separate module clinicians open only when the recertification window forces them to, expect the errors and missed deadlines that come with it to keep happening.
Does scheduling account for travel time and clinician territories?
A home health scheduler isn’t just an appointment calendar — it’s routing software wearing a healthcare hat. Visits are spread across a territory, drive time between them is real cost, and a scheduling tool that treats every slot as interchangeable will book routes no clinician can actually drive in the time allotted. What to look for: scheduling that’s aware of clinician territories and travel time between addresses, not just open time slots on a grid. That single feature difference is often the gap between a schedule that holds up on a Tuesday and one that falls apart by the third visit.
Can family caregivers get limited, permissioned access without compromising the record?
Home health is one of the few care settings where a family member is routinely present for — and often participating in — the care being documented. A system that can’t offer limited, permissioned visibility to a caregiver forces staff into workarounds: printed summaries, verbal updates, or no visibility at all. The right answer isn’t opening the full clinical record to a family member — it’s role-scoped access that shows what a caregiver needs (visit schedule, care plan highlights) without exposing the full chart. If your current software only offers all-or-nothing access, that’s a scoping problem the vendor hasn’t solved, not something your agency can configure around.
Is it actually HIPAA compliant, or just labeled that way?
“HIPAA compliant” appears on a lot of marketing pages without much behind it, and the stakes are higher here than in a single-location clinic: every field tablet is a potential point of exposure if it’s lost, stolen, or shared between staff. What actually matters is whether patient data is encrypted both on the device and in transit, whether access is scoped by role instead of one shared login per agency, and whether the system logs who viewed or changed a record and when — including from the field, not just the office. Those are architecture decisions made at the start of a build, not settings turned on later, which is exactly the ground we cover in our HIPAA-compliant app development guide. If a vendor can’t explain clearly how encryption, access control, and audit logging work on their own field app, that’s a real gap, not a formality.
What should you do if your current system is missing these?
If your current software is missing several of the things above, there are three realistic paths. You can ask the vendor for a roadmap fix, which tends to move slowly for a specialty that’s a small piece of a general-EHR vendor’s customer base. You can layer manual workarounds on top — printed OASIS backups, phone-relayed schedule changes, a spreadsheet tracking which caregivers have which access — which costs staff time every week it continues and adds real error risk in the field. Or, once the workaround cost is clearly outweighing what a build would cost, you can build home health EHR software shaped around offline documentation, OASIS, and travel-aware scheduling from the start. A custom build doesn’t have to mean a blank page or a multi-year project — most agencies are better served starting with a focused first version covering field charting, OASIS, and scheduling, with billing and family-portal access added once that core is live and working.
The bottom line
Home health EHR software should be judged against how the work actually happens: offline-first field documentation that survives a dead zone, OASIS assessments built into the same workflow clinicians already use, scheduling that understands travel time and territory, permissioned access for family caregivers, and encryption, access controls, and audit logging that hold up on a field tablet — all of it genuinely HIPAA compliant, not just labeled that way. If your current system is missing more of these than it’s getting right, or you want a straight opinion on whether a custom build would pay off for your agency, talk to us.