Home health and hospice agencies run on the same clinical record concepts as any other provider, but almost nothing about their operating environment matches the clinic. Care happens in patients' homes, often without connectivity. Documentation is driven by federally mandated assessment instruments with their own data specifications and submission deadlines. Payment depends on episodes, timing, and certification paperwork rather than on visits and codes alone. And the workforce is mobile every hour of every day. An EHR built for an office will strain under all of this. This guide covers what agencies should look for and the questions that separate a true home-based care platform from an ambulatory product with a mobile app.
How home-based care differs from the clinic
Three differences drive most of the requirements. First, the unit of care is an episode or a benefit period, not a visit, and the record must track admission, recertification, discharge, and transfer events with the dates and reasons that regulators and payers require. Second, the care team is interdisciplinary by regulation: nursing, therapy, aides, social work, chaplaincy in hospice, and the physician or allowed practitioner who certifies eligibility and signs the plan of care. The record must support a shared plan across those roles and coordinate visits among them. Third, clinicians are in the field, so the record must work on a tablet in a basement with no signal and reconcile cleanly when the device reconnects.
OASIS, HIS, and regulatory assessment data
Medicare-certified home health agencies must collect and submit the Outcome and Assessment Information Set (OASIS) at defined time points: start of care, resumption of care, recertification, transfer, discharge, and others. Hospices must submit the Hospice Item Set (HIS) at admission and discharge, with the HOPE assessment instrument replacing HIS for admissions beginning in late 2025. Each instrument has a detailed data specification, item-level logic, and electronic submission requirements to the federal iQIES system, with timeliness thresholds that affect quality reporting and payment.
For the EHR, this means the assessment must be native, not bolted on. Look for item-level validation as the clinician documents, scrubbing against the current data specification before submission, tracking of submission status and rejections, and automatic updates when the specification changes. Ask the vendor how many specification releases they have implemented on time in the past three years and how they communicate changes to agencies. A vendor that is chronically late forces the agency into manual workarounds during the most compliance-sensitive part of the workflow.
Point-of-care mobile charting and offline mode
The clinician's tablet is the primary interface, so test it as such. Offline mode should allow the full visit note, assessment, medication reconciliation, vital signs, wound documentation with photographs, and patient signature capture without connectivity, then synchronize without losing or duplicating data. Ask what happens when two clinicians document on the same patient offline on the same day and both synchronize; conflict handling is where weak products fail.
Evaluate the visit note for speed. Field clinicians document in cars and kitchens, and every extra tap costs them time at the end of a long day. Look for assessment items that flow into the note, care plan problems that pre-populate interventions, and medication reconciliation that pulls from the prior visit. Wound photography should attach to the wound record with measurements, not sit in a generic document folder.
Test in airplane mode. Have a nurse complete a full start-of-care assessment on the demo tablet with connectivity disabled, then reconnect. Watch the synchronization, then check the record from a desktop. This one test tells you more than an hour of slides.
Plans of care, orders, and physician certification
The Medicare home health conditions of participation require an individualized plan of care established and periodically reviewed by the certifying physician or allowed practitioner, with all services furnished according to that plan. Hospice conditions of participation require an interdisciplinary group to develop and update the plan of care with the patient and family. The EHR must generate the plan from the assessment, route it for signature, track verbal orders and their authentication deadlines, and record the face-to-face encounter documentation that supports certification.
Ask how the system handles physician signatures. Electronic signature workflows with certifying physicians who are not agency employees are a persistent bottleneck; look for a physician portal, e-signature integration, and a dashboard of outstanding certifications sorted by days pending. Late certifications delay billing, so this is a revenue issue as much as a compliance one.
Scheduling, visit verification, and staffing
Agency scheduling is a routing problem across disciplines, geography, patient preference, and frequency orders on the plan of care. The system should flag when scheduled visits fall short of or exceed ordered frequencies, support recurring visit patterns, and show drive time between visits. For Medicaid-funded personal care and home health services, electronic visit verification is federally required under the 21st Century Cures Act; the EHR or an integrated module must capture the type of service, the individual receiving and providing it, the date, the location, and the start and end times. Ask whether verification data flows to your state's aggregator without manual re-entry.
Billing under PDGM and the hospice benefit
Home health payment under the Patient-Driven Groupings Model is based on thirty-day periods, with case-mix derived from OASIS items, diagnosis coding, admission source, and timing. Hospice is paid per diem by level of care, with the notice of election, benefit period tracking, and the service intensity add-on all affecting claims. An agency EHR should compute the expected payment grouping from the assessment, flag coding that will not group, manage the notice of admission and notice of election deadlines, and produce compliant claims with the required occurrence and value codes. Confirm which clearinghouses the vendor supports and ask for a reference agency of similar size that bills the same payer mix.
Security for a workforce that is always off-site
An agency's entire clinical workforce is remote, and its devices travel through cars, homes, and coffee shops. The HIPAA Security Rule's device and media controls and access control standards apply to every one of those tablets. Require full-device encryption, remote wipe, automatic screen lock, multi-factor authentication on every login, and no local storage of patient data beyond the synchronized cache the application manages. Ask how the vendor handles a lost device: can the agency revoke the device's access and confirm the cache was encrypted and wiped? Document the answer in your risk analysis, because a lost unencrypted tablet with a day's visits on it is a reportable breach.
Selection questions specific to agencies
- Is the OASIS or HOPE assessment native, with item-level validation and tracked iQIES submission status?
- Does the mobile app support a full visit offline, and how are synchronization conflicts resolved?
- How are verbal orders, plan-of-care signatures, and face-to-face documentation tracked against deadlines?
- Does scheduling enforce ordered frequencies and support electronic visit verification where required?
- Does the system compute PDGM groupings and manage hospice notice-of-election and benefit periods?
- What device controls, encryption, and remote-wipe capabilities are built in?
- Which state survey and accreditation reports can the system produce on demand?
- What is the data export path if the agency changes vendors, and in what format?
Agencies live under more prescriptive federal rules than most ambulatory practices, and their clinicians work in harder conditions. The right EHR treats assessments, plans of care, and mobile documentation as the center of the product rather than as modules added to an office system. Test for that directly, in the field conditions your staff face, before you sign.
Common questions
Can a general ambulatory EHR with a mobile app work for a home health agency?
Rarely. Agencies need native OASIS or HOPE assessments with validation and submission tracking, offline charting, plan-of-care certification workflows, and episode-based billing that ambulatory products do not include.
What is electronic visit verification and does it apply to us?
Electronic visit verification captures the service, provider, recipient, date, location, and times of a visit. Federal law requires it for Medicaid-funded personal care and home health services; check your state's program for scope and aggregator requirements.
How should we test a vendor's offline mode?
Have a clinician complete a full start-of-care assessment on the demo tablet in airplane mode, reconnect, and verify the record from a desktop. Also ask how the system resolves two clinicians documenting offline on the same patient.
What happens if a clinician's tablet is lost?
The agency should be able to revoke access and remotely wipe the device, and the application's local cache should be encrypted. If the device was unencrypted and held patient data, the loss is likely a reportable breach.