Home Health EHR

A home health electronic health record (EHR) is a software platform built for the workflows of Medicare-certified home health agencies: referral intake, OASIS assessments, visit documentation, scheduling, physician orders, quality reporting, and claims. Unlike hospital EHRs, it is organized around episodes of care delivered in the patient's home by mobile clinicians rather than around facility encounters.

How a home health EHR differs from a hospital EHR

Hospital and ambulatory EHRs are organized around encounters that happen inside a facility. Home health runs on a different chassis: 60-day certification periods, 30-day PDGM payment periods, OASIS assessments at defined time points, and clinicians who document in patients' homes with unreliable connectivity. A home health EHR has to handle things a hospital system never touches, including OASIS-E2 data collection and submission through iQIES, HIPPS code generation, Notice of Admission (NOA) deadlines, plan of care (CMS-485) generation, and per-visit scheduling across a dispersed field staff. Agencies that try to run home health on a general-purpose EHR usually end up with spreadsheets and workarounds for exactly these regulatory mechanics.

Core capabilities to expect

A complete platform covers the episode end to end:

  • Intake and eligibility: referral capture, insurance verification, and homebound and skilled-need screening
  • Clinical documentation: OASIS, visit notes, plans of care, and medication reconciliation, usable offline in the field
  • Orders management: tracking physician orders from creation through signature
  • Billing: NOA submission, final claims, sequential billing rules, and denials workflows
  • Quality and compliance: OASIS scrubbing, QAPI reporting, and survey-readiness documentation
  • Scheduling: matching visit frequencies ordered on the plan of care to field capacity

Why the EHR choice shapes compliance and cash flow

In home health, documentation is the payment. The OASIS drives the HIPPS code, the HIPPS code drives the 30-day period payment, and unsigned orders or late NOAs directly reduce or delay revenue. An EHR that surfaces missing signatures, flags OASIS inconsistencies before submission, and tracks NOA deadlines protects margin in ways that have nothing to do with clinical features. The same is true for survey readiness: when a state surveyor asks for evidence that the comprehensive assessment was completed within 5 days of the start of care, the EHR either produces it in seconds or the agency scrambles.

What good looks like when evaluating a platform

Look past the demo and test the unglamorous paths. Can a nurse complete an OASIS-E2 start of care offline and sync later? How many clicks from referral to scheduled first visit? Does the system hard-stop a final claim when orders are unsigned? Ask for the vendor's OASIS submission error rate and NOA timeliness data from live customers. Check how quickly the vendor shipped support for recent regulatory changes such as OASIS-E2, which took effect April 1, 2026. A vendor's regulatory release history predicts how painful the next CMS rule cycle will be.

Frequently asked questions

Can an agency use a hospital EHR like Epic or Cerner for home health?

Some health systems extend their enterprise EHR to home health divisions, but most Medicare-certified agencies use purpose-built home health platforms. Hospital EHRs generally lack native OASIS workflows, HIPPS grouping, NOA tracking, and per-visit field scheduling, so agencies either buy a specialty system or bolt on third-party tools.

What does a home health EHR need to support for OASIS?

It should collect the current OASIS version (OASIS-E2 as of April 1, 2026), run consistency and completeness checks before export, and submit assessments to CMS through iQIES. Strong systems also show how OASIS responses affect the functional impairment level and expected payment before the assessment is locked.

How does the EHR affect billing performance?

Nearly every home health billing failure traces back to data upstream in the EHR: late NOAs, unsigned orders, OASIS not submitted, or visit documentation that does not support the claim. An EHR that enforces these dependencies before claim release shortens days sales outstanding and reduces denials.

Related terms