PDGM Made Simple: How Automatic HIPPS Coding Protects Your Home Health Revenue

If you bill home health under Medicare, your entire payment for a 30-day period comes down to five characters: the HIPPS code. Get it right and you’re paid correctly. Get it wrong — or build it from incomplete OASIS data — and you either leave money on the table or invite a downcode on review.

The trouble is that the HIPPS code isn’t something a biller types in. Under the Patient-Driven Groupings Model (PDGM), it’s calculated from clinical data your nurses already collect. The agencies that bill cleanly are the ones whose EMR builds that code automatically from the chart. Here’s how it works.

The five characters of a HIPPS code

Every PDGM HIPPS code encodes four payment decisions plus a placeholder:

1. Admission source & timing — Was the 30-day period early (the first period in a sequence) or late? And did the patient come from the community or from an institution (a hospital or SNF stay in the 14 days before admission)? Institutional admissions and early periods generally pay more, because they reflect higher expected resource use.
2. Clinical group — The EMR maps your primary diagnosis to one of 12 clinical groups: MMTA (the medication-management/teaching-and-assessment subgroups for cardiac, endocrine, GI/GU, infectious, respiratory, and “other”), Neuro/Stroke Rehab, Wound, Complex Nursing Interventions, MS Rehab, Behavioral Health, and Surgical Aftercare. If your primary code isn’t a valid PDGM primary, the claim won’t group — a “questionable encounter” that has to be fixed before it can be paid.
3. Functional impairment level — Low, Medium, or High, scored from a specific set of OASIS items (the functional/ADL questions). This is where documentation discipline turns directly into dollars.
4. Comorbidity adjustment — None, Low, or High. The grouper reads your secondary diagnoses and checks them against the CMS comorbidity subgroup list — and, for the High adjustment, against the list of interaction pairs that are known to drive cost when they appear together.
5. A placeholder character that CMS reserves.

Four of those five characters are decided by clinical documentation — OASIS and diagnosis coding — not by the billing office. That’s the core insight of PDGM: billing accuracy is a documentation problem.

Where agencies lose money

In practice, revenue leaks at predictable spots:

• An invalid primary diagnosis. Codes that are too vague (or that CMS designates as unacceptable as a principal diagnosis) leave the claim ungrouped. If nobody catches it, the claim sits — or goes out wrong.
• Under-captured functional level. If the OASIS functional items don’t reflect the patient’s real status, a High-impairment patient gets billed as Low. The visit happened; the payment didn’t follow.
• Missed comorbidities. A qualifying secondary condition — or a qualifying pair of them — that never makes it onto the claim means the comorbidity adjustment silently drops from High to Low to None.
• Wrong timing or source. Misreading early vs. late, or community vs. institutional, shifts the whole rate.

None of these are exotic. They’re everyday data-entry gaps. And on review, the same gaps that cost you on the front end invite downcoding on the back end.

How an EMR that calculates the code changes the math

When the billing engine lives inside the same system as the chart, the HIPPS code stops being a guess. In Home Health Engine, the grouper:

• Validates the primary diagnosis the moment it’s entered and flags codes that won’t group as a PDGM primary — before the claim is built.
• Scores functional level directly from OASIS, so the impairment level on the claim is the one the assessment actually supports.
• Detects comorbidities and interaction pairs from the secondary diagnosis list, applying the correct None/Low/High adjustment automatically.
• Determines timing and admission source from the patient’s episode history and any institutional stay in the look-back window.
• Assembles the 5-character HIPPS code and carries it straight onto the RAP/NOA and the final claim — no re-keying into a separate billing system.

The point isn’t to replace your coder’s judgment. It’s to make sure that once the judgment is made, the claim reflects it exactly — and that the obvious mistakes get caught while they’re still cheap to fix.

A quick self-check for your agency

Ask yourself three questions about your current workflow:

1. When a clinician enters a primary diagnosis that won’t group under PDGM, how soon does anyone find out — at intake, or at billing?
2. Is your functional impairment level on the claim derived from OASIS, or re-entered by hand?
3. When was the last time you measured how many claims went out at a lower comorbidity adjustment than the chart could support?

If the answers make you wince, the problem usually isn’t your billers — it’s the gap between where the data is captured and where the claim is built. Closing that gap is exactly what an integrated EMR is for.

---

Home Health Engine builds the HIPPS code from your OASIS and diagnoses automatically, then generates and submits the RAP/NOA and final claims from inside the chart. Prefer to hand it off entirely? Our team runs the full revenue cycle for a flat $2 per patient per day. Get a quote.