LUPA (Low Utilization Payment Adjustment)

A Low Utilization Payment Adjustment (LUPA) occurs when the number of visits in a 30-day payment period falls below the threshold for the period's case-mix group. Instead of the full period payment, Medicare pays national per-visit rates for the visits actually delivered, which typically totals a fraction of the case-mix amount.

How the LUPA threshold works under PDGM

Every case-mix group under the Patient-Driven Groupings Model (PDGM) has its own LUPA threshold, ranging from 2 to 6 visits per 30-day period. Deliver at least the threshold number of visits and the period pays the full case-mix amount; deliver fewer and every visit is paid at a wage-adjusted national per-visit rate for its discipline. The determination is made per period, so the first period of a certification can pay in full while the second becomes a LUPA. Thresholds are recalibrated annually, most recently in the CY2026 final rule using CY2024 data. When a LUPA occurs in the first or only period of a sequence, Medicare adds a LUPA add-on payment to the first skilled visit to reflect assessment costs.

Why LUPAs matter for agency margins

The gap between full period payment and per-visit LUPA payment is large, while the agency's costs barely change: the comprehensive assessment, OASIS, coding, care planning, and billing work happen either way. A LUPA period often costs more to serve than it pays. A few LUPAs are clinically appropriate, but an elevated LUPA rate is usually an operations signal, not a clinical one. Agencies should track LUPA rate by period position, discipline mix, team, and referral source, and treat unexplained variation as a scheduling and visit-completion problem to solve.

How to reduce avoidable LUPAs

Avoidable LUPAs are mostly a visibility and follow-through problem:

  • Surface each period's threshold and running visit count to schedulers and clinical managers in real time
  • Reschedule missed visits within the period instead of letting them disappear
  • Watch period boundaries: a visit delivered on day 31 counts toward the next period, not the one that needed it
  • Plan frequencies so medically necessary visits are not bunched at the start of a certification, leaving the second period thin
  • Confirm weekend and on-call coverage for patients sitting one visit above threshold

The guardrail: never add a visit without clinical justification. Padding visits to dodge a LUPA is a program integrity problem.

LUPA vs. PEP

Both adjustments reduce a period's payment, but they answer different situations. A LUPA is about volume: too few visits in the period, paid per visit. A Partial Episode Payment (PEP) adjustment is about interruption: the patient transferred to another home health agency or was discharged and readmitted within the same 30-day period, so the payment is prorated for the portion of the period the agency was responsible for. A LUPA is often preventable with better scheduling discipline; a PEP usually reflects patient events outside the agency's control, though intake and discharge decisions influence both.

Frequently asked questions

Does a LUPA affect the episode's OASIS requirements?

No. The comprehensive assessment, OASIS submission, plan of care, and physician orders are required regardless of how the period pays. The LUPA only changes the payment methodology from case-mix to per-visit.

Is a LUPA always a bad outcome?

No. Some patients legitimately need only a visit or two in a period, such as a patient nearing discharge. The problem is the avoidable LUPA, where missed or poorly distributed visits pushed a clinically appropriate plan below threshold.

How do I know a period's LUPA threshold?

The threshold is set by the period's case-mix group, identified by its HIPPS code, and ranges from 2 to 6 visits. CMS publishes thresholds with the annual payment rule, and grouper software returns the threshold when the period is grouped.

Related terms