Miss a filing deadline by one day and Medicare doesn't send a warning letter — it just quietly takes money off your next check. For home health agencies, that deadline is five calendar days, the money is the Notice of Admission penalty, and most owners don't find out it happened until they're staring at a claim that paid less than expected.
That's the reality of billing under the Patient-Driven Groupings Model (PDGM), the payment system Medicare has used for home health since 2020. PDGM doesn't just change a rate table — it changes how quickly you have to move, how precisely your clinical documentation has to match your billing codes, and how much cash actually lands in your account per patient. For an industry where the average agency brings in about $1.6 million a year and the smallest operators run on net margins closer to 2%, getting PDGM's timing rules wrong isn't a paperwork problem. It's a solvency problem.
Here's how the model actually works, where agencies lose money without realizing it, and what to track so it stops happening.
The 30-Day Period Is the Whole Game
Before PDGM, Medicare paid home health agencies in 60-day episodes. PDGM cut that window in half: every unit of payment is now a 30-day period, and each period is priced independently based on a fresh look at the patient's condition and care history.
That single change is why PDGM feels so much less forgiving than the old system. A 60-day episode gave you time to average out a slow start. A 30-day period gives you two, sometimes three, separate payment calculations per month of care — each one graded on its own documentation.
Every 30-day period is sorted into one of 432 case-mix groups, and the group determines the payment. Four factors decide which group a period falls into:
- Admission source and timing — was the patient referred from the community or from an institution (hospital, skilled nursing facility), and is this the early period (the first 30 days of a care sequence) or a later period (everything after)?
- Clinical group — one of twelve categories based on the patient's principal diagnosis (e.g., wound care, neuro/stroke rehabilitation, complex nursing interventions).
- Functional impairment level — low, medium, or high, scored from eight OASIS activities-of-daily-living items.
- Comorbidity adjustment — whether secondary diagnoses on file add a low or high additional payment bump.
Why "Early vs. Late" Is Worth Real Money
The early/late distinction exists because PDGM assumes — correctly, in most cases — that patients need more intensive services in the first 30 days after a hospital stay or new referral, then taper off. Institutional, early-period admissions are typically weighted and paid higher than late-period, community-admitted ones.
The practical implication: if your intake team miscodes an admission source, or a gap in care accidentally resets what should have been a "later" period back to "early" (or vice versa), you're not making a clerical error — you're picking the wrong price on a menu with 432 items.
A Worked Example: Same Patient, Two Very Different Payments
Say two patients each need 30 days of wound-care visits at similar acuity. Patient A is referred straight from a hospital discharge — an institutional, early-period admission. Patient B is a self-referral from the community, already several 30-day periods into an ongoing plan of care — a community, late-period admission.
Even with comparable visit counts and functional scores, Patient A's period is priced meaningfully higher than Patient B's, because PDGM's case-mix weights assume institutional, early-period patients need more clinical intensity. Bill Patient A's period as if it were a later, community-sourced one — an easy mistake if the referral source field gets copied over incorrectly during intake — and you've discounted a legitimately higher-value period down to a lower one, with no error message to flag it. The claim still pays; it just pays less than it should have, and nothing downstream will tell you unless you're comparing expected case-mix pricing against what actually posted.
The 5-Day Notice of Admission Deadline
Since 2022, agencies no longer submit a Request for Anticipated Payment (RAP) at the start of care. Instead, every first 30-day period requires a Notice of Admission (NOA) filed within five calendar days of the start-of-care date.
Miss it, and the penalty isn't a flat fee — it's a per-day reduction calculated as 1/30th of the period's payment for every day the NOA is late, deducted straight from the eventual claim. On a $3,500 period, that's roughly $117 gone for every day past the deadline — so submitting on day 6 instead of day 5 already costs you, and a week's delay can wipe out 20% or more of that period's revenue. There's no grace period and no appeal path once it's late; the reduction is baked directly into the final payment calculation.
The most common reason agencies get caught by this isn't ignorance of the rule — it's workflow. RAPs used to tolerate a slower handoff between clinical staff finishing the OASIS assessment and billing staff filing paperwork. NOA doesn't. If your start-of-care documentation isn't finalized and handed to billing within a day or two, five calendar days (which include weekends) disappears fast.
LUPA: When a Period Pays Per Visit Instead of Per Episode
Every case-mix group has its own Low Utilization Payment Adjustment (LUPA) threshold — the minimum number of visits a period needs to earn the full 30-day case-mix payment. Thresholds are set agency-wide at the 10th percentile of visits for that group, with a floor of two visits, and typically land somewhere between two and six visits depending on the group.
Fall short of the threshold, and Medicare doesn't pay the full period rate — it pays a flat per-visit rate instead, which is almost always far less than the case-mix payment would have been. A patient who was supposed to generate a $2,800 period payment but only received three visits against a five-visit threshold might net a few hundred dollars in per-visit reimbursement instead. Agencies that don't track LUPA thresholds by case-mix group in real time often don't discover the shortfall until the remittance advice arrives — well after the visits could have been scheduled.
Where the Money Actually Leaks
Across billing consultants and revenue-cycle firms working with home health agencies, the same handful of mistakes show up repeatedly:
- Coding a symptom as the principal diagnosis. Using an "always secondary" code, or a symptom code that isn't allowed as primary, causes an instant grouping failure — the claim doesn't just pay less, it can reject outright.
- Comorbidities documented but never billed. A physician's chart may list five relevant secondary diagnoses, but if only two make it into the OASIS and billing record, the comorbidity adjustment — real money — never gets claimed.
- Weak homebound or functional documentation. OASIS answers that understate functional impairment quietly downgrade a period's case-mix group.
- Slow clinical-to-billing handoff. The single biggest driver of late NOAs isn't confusion about the rule — it's that nobody owns the trigger the moment start-of-care documentation is complete.
None of these are billing-system failures. They're process and recordkeeping failures, which means they're fixable without new software — just tighter tracking.
Building an Intake Workflow That Can't Miss the Clock
Since the failure point is almost always the handoff between clinical documentation and billing, not the billing software itself, the fix is a workflow with an explicit, timestamped trigger rather than an informal "someone will get to it" habit. A few habits that consistently keep agencies inside the 5-day window:
- Start the NOA clock at start-of-care, not at OASIS completion. The five calendar days begins on the start-of-care date itself — treat day one as already spent before anyone opens a laptop.
- Assign one named owner for same-day handoff. The moment a clinician signs off on start-of-care documentation, one specific person — not "billing" as a department — should be responsible for filing the NOA that day.
- Build a standing Friday check, since the five-day window runs on calendar days and swallows weekends whether or not staff are in the office.
- Verify admission source and comorbidities before submission, not after a denial. A two-minute cross-check against the physician's chart catches the missing secondary diagnosis or misclassified referral source while it still costs nothing to fix.
- Reconcile every posted period against its expected case-mix payment, not just against the invoice total. A period that pays "close enough" to what you expected can still be quietly underpriced by one wrong classification.
Tracking Cash Flow Under a 30-Day Payment Cycle
PDGM effectively doubles your billing cycle frequency compared to the old 60-day model, which means your books need to reflect revenue in 30-day increments too — not just when cash arrives, but when it was earned and at what expected rate. Agencies that record revenue only when the remittance lands, instead of accruing an expected case-mix payment at admission, lose visibility into which specific periods underpaid and why. That visibility is exactly what you need to catch a systemic NOA delay or a comorbidity documentation gap before it repeats across dozens of patients.
Plain-text, version-controlled bookkeeping makes that kind of period-by-period reconciliation straightforward: each 30-day period becomes its own transaction you can tag by case-mix group, admission timing, and actual vs. expected payment, then diff against your NOA filing dates to spot patterns — all in a format you can audit and query rather than dig through a black-box dashboard.
Simplify Your Financial Management
Between 30-day payment periods, NOA deadlines, and LUPA thresholds, home health billing generates a lot of small, time-sensitive numbers that are easy to lose track of in a spreadsheet. Beancount.io offers plain-text accounting that's transparent, version-controlled, and AI-ready — so you can reconcile every period's expected payment against what Medicare actually sent, without vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.