LUPA Management
LUPA Tracking That Warns You Before the Payment Collapses
Under PDGM, falling below the LUPA visit threshold converts a full 30-day period payment into per-visit rates - often a difference of thousands of dollars. EMRxAI monitors every period's visit count against its group-specific threshold and alerts your team in time to act.
Built specifically for Medicare-certified home health agencies. HIPAA-compliant by design.
LUPA thresholds vary - and nobody watches them manually
Every PDGM payment group carries its own LUPA threshold (2 to 6 visits). A missed visit, a patient refusal, or a scheduling gap late in the period can silently drop a period below threshold - and the difference between a full period payment and per-visit LUPA payment is frequently several thousand dollars.
Spreadsheet tracking across dozens of active periods with different thresholds and different end dates is exactly the kind of work humans miss and software should not.
How LUPA monitoring works
Group-specific thresholds
Each 30-day period is tracked against its own PDGM payment group's threshold - not a generic visit count.
Real-time visit tracking
Completed, scheduled, and missed visits update the period's threshold status continuously.
Early-warning alerts
Scheduling and clinical leadership are alerted while there is still time in the period to complete clinically appropriate visits.
Missed-visit follow-through
Missed visits trigger reschedule workflows immediately, with the LUPA impact of the gap made explicit.
Watching every period, automatically
- 1
Period opens
The PDGM group and its LUPA threshold are set from the claim grouping.
- 2
Visits tracked
Every completed and scheduled visit counts against the threshold in real time.
- 3
Risk flagged early
Periods trending below threshold surface on the dashboard with days remaining.
- 4
Team acts
Clinically appropriate visits are scheduled, or the LUPA is anticipated in billing.
Visit integrity matters
LUPA alerts inform scheduling of clinically appropriate, physician-ordered visits. The system pairs threshold visibility with order and frequency tracking - visits must always be medically necessary and consistent with the plan of care.
Clinical necessity comes first
- LUPA alerts are financial visibility tools. Visit decisions must be driven by clinical need and physician orders - never by threshold management alone.
- Some LUPAs are clinically appropriate. The goal is eliminating accidental LUPAs caused by scheduling gaps and missed visits, not eliminating LUPAs entirely.
Frequently asked questions
How much revenue does an accidental LUPA cost?
It varies by payment group and wage index, but the gap between a full 30-day period payment and per-visit LUPA payment is commonly several thousand dollars per period.
When does EMRxAI raise a LUPA alert?
Alerts fire when a period's completed-plus-scheduled visit count trends below its group threshold with enough days remaining to act - not after the period has already closed.
Does it account for the threshold changing at recertification?
Yes. Each new 30-day period is tracked against the threshold for its own payment group, which can change as the patient's clinical grouping changes.
See it on your agency's workflows
A walkthrough tailored to your census, payer mix, and current baseline - with any savings estimate documented, assumptions included.
Request a Demo