A LUPA — a Low Utilization Payment Adjustment — is what happens when a home health 30-day period does not deliver enough visits to earn its full Patient-Driven Groupings Model (PDGM) payment. When the number of visits falls below the period's LUPA threshold, Medicare stops paying the case-mix-adjusted period amount and instead pays a flat per-visit rate for each visit provided. The difference is not small: a period that would have paid roughly $2,000–$3,000 as a full episode can collapse to a few hundred dollars in per-visit payments. For agencies running on thin home health margins, unmanaged LUPAs are one of the quietest and most avoidable sources of lost revenue.
This guide explains what a LUPA is under PDGM, how the 2-to-6-visit thresholds actually work, why they differ from one patient to the next, and how home health agencies protect the revenue LUPAs put at risk — without ever adding a visit a patient does not clinically need. Every payment rule below traces to CMS's own guidance so your clinical and billing teams can verify it directly.
What Is a LUPA Under PDGM?
A LUPA is a payment method, not a penalty. Under the Home Health Prospective Payment System, most 30-day periods are paid a single, predetermined amount based on the period's case-mix group. But when a period is provided very few visits, paying the full case-mix amount would over-reimburse the care actually delivered. So CMS pays those low-utilization periods per visit instead — that is the Low Utilization Payment Adjustment.
Before PDGM took effect on January 1, 2020, LUPA was simple and uniform: any 60-day episode with four or fewer visits was paid per visit. PDGM replaced that flat rule with a variable, group-specific threshold applied to each 30-day period. CMS documents the model on the Home Health Prospective Payment System page, which is the authoritative reference every agency's billing team should work from.
How LUPA Thresholds Work (2 to 6 Visits per 30-Day Period)
Under PDGM, every 30-day period is grouped into one of hundreds of case-mix groups based on five dimensions: admission source, timing, clinical grouping, functional impairment level, and comorbidity adjustment. Each of those groups carries its own LUPA threshold, ranging from 2 to 6 visits.
- If the period's total visits are at or above its threshold, the period pays the full case-mix-adjusted amount.
- If the period's total visits fall below its threshold, the period is a LUPA and pays per visit.
CMS sets each group's threshold at the 10th percentile of visits for that group and recalculates the thresholds every year in the annual Home Health PPS rulemaking. That means a threshold that was 3 visits last year can shift, and a group your agency treats routinely may sit right on the edge. The practical takeaway is that there is no single "safe" visit count — the number that avoids a LUPA depends entirely on which group the period lands in.
Why the Threshold Varies by Payment Group
The threshold varies because expected utilization varies. A period grouped into a complex clinical category with high functional impairment is expected to require more visits, so its threshold sits higher. A period in a lower-acuity group is expected to need fewer visits, so its threshold sits lower. This is why the same raw visit count — say, four visits in a 30-day period — can be a fully paid period for one patient and a LUPA for another. The visit count only has meaning relative to that specific period's threshold.
Because the threshold is a function of the case-mix group, coding accuracy directly controls LUPA exposure. An incorrect primary diagnosis, a mis-scored functional level, or a missed comorbidity can push a period into a different group with a different threshold — turning a paid period into a LUPA (or masking a real one) without anyone touching the visit schedule. A focused coding & OASIS review is often the fastest way to find periods that are being grouped — and therefore LUPA-flagged — incorrectly.
The LUPA Add-On Payment
CMS recognizes that the first visit in a low-utilization period carries extra cost, because that visit often includes the comprehensive assessment work. So for a LUPA period that is the first or only period in a sequence of adjacent 30-day periods, Medicare applies a LUPA add-on factor to the first skilled visit, increasing its payment. It does not make a LUPA whole, but billing teams should confirm their software is applying the add-on correctly so the agency captures every dollar a LUPA period is actually owed.
Why LUPAs Quietly Drain Home Health Revenue
The danger of LUPAs is that they are invisible until the remittance arrives. A scheduling gap, a patient who repeatedly refuses visits, a missed reassessment, or a therapy discipline that discharges early can each drop a period below its threshold — and no one notices until the period pays per-visit weeks later. Multiply a handful of avoidable LUPAs across a month of episodes and the leakage rivals what many agencies lose to outright denials.
Worse, LUPAs cluster in predictable places: short-stay patients, periods interrupted by hospitalization, and the second period of a sequence where the plan of care tapers. Agencies that do not watch visit counts against thresholds *during* the period — while there is still time to act clinically — are structurally exposed. Treating LUPA management as part of the broader revenue cycle rather than a billing afterthought is what turns this from a recurring surprise into a controlled metric.
How to Avoid Unnecessary LUPAs
Every step below is about delivering and documenting medically necessary care on time — never about padding visits.
- Know each period's threshold early. Ensure your EHR surfaces the period's LUPA threshold and running visit count so care teams can see, mid-period, whether a period is trending toward a LUPA.
- Front-load and protect the assessment. Complete the Start of Care comprehensive assessment on time and schedule the plan-of-care visits so an early discharge or a single missed visit does not tip the period under its threshold.
- Manage patient refusals and no-shows actively. A pattern of refused visits is the most common avoidable LUPA cause. Document refusals, re-engage the patient and physician, and adjust the plan of care where clinically appropriate.
- Coordinate across disciplines. When nursing and therapy plan independently, a discipline discharging early can quietly drop the period under threshold. Shared visibility prevents it.
- Get the coding right the first time. Because the threshold follows the case-mix group, accurate primary-diagnosis selection, functional scoring, and comorbidity capture keep periods in the correct group. A home health review of assessments before billing catches grouping errors while they are still fixable.
- Reconcile before the claim drops. A pre-billing check that flags any period sitting one visit below its threshold gives the clinical team a last chance to confirm whether a medically necessary visit was delivered but not documented.
The LUPAs You Should Not "Fix"
It is essential to draw the line clearly: the goal is to avoid unnecessary LUPAs caused by scheduling, documentation, or coding failures — not to manufacture visits. Adding a visit that is not supported by the patient's condition and plan of care to clear a threshold is a program-integrity problem, the kind of pattern CMS and its contractors specifically look for. Legitimate LUPA management means making sure every clinically appropriate, ordered visit is actually delivered, documented, and coded correctly. When a patient genuinely needs only two visits, that period *should* be a LUPA, and billing it as one is the compliant outcome.
Handled this way, LUPA management protects revenue and compliance at the same time: you stop losing money on periods that should have paid in full, while never chasing money on periods that should not.
Frequently Asked Questions
What is a LUPA in home health?
A LUPA (Low Utilization Payment Adjustment) is how Medicare pays a home health 30-day period that has fewer visits than its case-mix group's LUPA threshold. Instead of the full case-mix-adjusted period payment, the period is paid a flat per-visit rate for each visit provided. It is a payment method for low-utilization periods, not a penalty.
How many visits are needed to avoid a LUPA under PDGM?
It depends on the period's case-mix group. Under PDGM, each group has its own LUPA threshold ranging from 2 to 6 visits, set at the 10th percentile of visits for that group and recalculated annually by CMS. A period avoids a LUPA when its total visits meet or exceed its specific threshold — so there is no single number that applies to every patient.
Are LUPA thresholds the same for every patient?
No. The threshold is assigned by the period's PDGM case-mix group, which is built from admission source, timing, clinical grouping, functional impairment level, and comorbidity adjustment. Higher-acuity groups carry higher thresholds and lower-acuity groups carry lower ones, so the same visit count can be a full-pay period for one patient and a LUPA for another.
Does avoiding a LUPA mean adding visits a patient does not need?
No — and it should not. LUPA management means delivering, documenting, and coding the medically necessary, physician-ordered visits correctly so periods are not pushed below threshold by scheduling gaps, refusals, or coding errors. Adding clinically unnecessary visits to clear a threshold is a compliance risk. When a patient truly needs only a few visits, the period should be billed as a LUPA.
Medeoan helps home health agencies find and fix the avoidable LUPAs draining their revenue — validating PDGM grouping and coding, checking assessments before billing, and building the visit-tracking discipline that keeps clinically appropriate periods paid in full. If unexplained LUPAs are showing up on your remittances, our revenue cycle management and coding & OASIS review teams can help you close the gap. For the full picture of how periods are grouped and paid, start with our PDGM guide.