How to Reduce LUPAs: A Practical Playbook for Home-Health Agencies

If you run a home-health agency, you already know the feeling: a 30-day period closes, the biller pulls the claim, and you find out the patient only had four visits when they needed six. The agency just lost somewhere between $1,200 and $2,000 on a single patient. Multiply that across a 240-patient census, and a 10% LUPA rate quietly bleeds six figures a year.

A LUPA — Low Utilization Payment Adjustment — is what happens when a 30-day home-health period falls below the visit threshold CMS sets for that clinical group under PDGM. Instead of getting the full case-mix payment, you get paid a per-visit rate. The gap is brutal: a standard episode might reimburse $2,800, while a LUPA on the same patient pays out $600.

The good news? LUPAs are one of the most controllable losses in home health. They are not a clinical mystery — they are a scheduling and visibility problem. This playbook walks through the seven plays we have seen work across hundreds of agencies on the EaseEHR platform.

1. Understanding LUPA Thresholds Under PDGM

Under the Patient-Driven Groupings Model, every 30-day period falls into one of 432 case-mix groups. Each group has its own LUPA threshold — anywhere from 2 to 6 visits — based on historical utilization patterns. Drop below the threshold and the entire period is paid per-visit.

Two things make this trickier than it sounds:

• Thresholds change. CMS recalibrates them annually. The threshold you memorized in 2024 may be different in 2026.
• Thresholds are not patient-by-patient — they are period-by-period. The same patient can have a non-LUPA first 30 days and a LUPA second 30 days if utilization drops.

The first move for any agency: pull the current CMS LUPA threshold table at the start of every PDGM year and bake it into your scheduling system. If your scheduler is eyeballing a paper grid, you are already losing money.

2. The Top 5 Causes of LUPAs in Real Agencies

Across the agencies we work with, the same five root causes show up over and over again. If you have not audited yours in the last 90 days, start here.

Missed visits that were never rescheduled

A patient cancels Tuesday. The clinician makes a note. Nobody calls back to reschedule. By Friday, the period is one visit short and nobody noticed. This is the single most common cause we see.

Scheduling gaps in week 3 and week 4

Most agencies front-load visits in week 1 and 2. By week 3, attention drifts to new admissions. The original patient drops below threshold quietly. A simple "week-3 audit" prevents this — but only if someone owns it.

Clinician no-shows and call-outs

When a PT calls in sick on Friday afternoon, the visit often just gets dropped instead of reassigned. Each unassigned visit is a step closer to a LUPA.

EVV (Electronic Visit Verification) failures

The visit happened — but the clinician forgot to clock in, the GPS ping failed, or the device timed out. From CMS's perspective, the visit does not exist. EVV failures cause "phantom LUPAs" on periods that should have been fine.

Documentation lag

Visits documented more than 48 hours late tend to fall off the radar entirely. By the time the biller catches it, the claim has already been submitted as a LUPA.

3. How to Predict LUPA Risk Before It Happens

The single biggest mindset shift: stop reporting LUPAs and start predicting them. By the time a LUPA shows up in your monthly report, the money is gone. You need to know about it on day 14, not day 31.

A working LUPA-prediction system needs three signals:

1. Visits-completed-to-date against the threshold for that patient's clinical group.
2. Days remaining in the 30-day period.
3. Scheduled-but-not-yet-completed visits, with a confidence score based on the assigned clinician's historical no-show rate.

If a patient is at 2 visits with 10 days left and a 4-visit threshold, that is not a yellow flag — that is a red flag. Someone needs a phone call today.

4. The Role of Real-Time Visit Funnels and Proactive Scheduling

The agencies that operate at sub-3% LUPA rates all share one operational habit: they look at a real-time "visit funnel" every single morning. The funnel shows every active 30-day period bucketed by risk:

• Green: on track or ahead of threshold
• Yellow: at threshold but with limited buffer
• Red: below threshold with fewer than 10 days remaining

The scheduler's only job each morning is to clear the red and yellow buckets. Not work the inbox. Not answer staff emails. Clear the buckets. When that becomes the discipline, LUPAs collapse.

5. What AI-Powered EHRs Can Do That Legacy Systems Can't

Legacy home-health EHRs were built to chart visits. They were not built to predict them. That is the architectural gap.

An AI-powered EHR built for home health does three things a legacy system cannot:

• It scores LUPA risk in real time. Not at month-end. Every morning, every patient, ranked by urgency.
• It auto-flags EVV failures within an hour so the clinician can re-verify before the visit becomes uncountable.
• It learns each clinician's behavior. If your PT has a 14% no-show rate on Fridays, the AI bakes that into the risk score and surfaces a backup visit recommendation.

This is the core idea behind how EaseEHR approaches LUPA prevention — turn the EHR from a passive chart into an active scheduler.

6. An Action Checklist for the Next 30 Days

If you read nothing else in this article, run this checklist with your DON and biller this week:

• Pull the current CMS LUPA threshold table and load it into your scheduling tool.
• Run a LUPA root-cause audit on the last 60 days of LUPAs. Tag each one as missed visit, EVV failure, doc lag, or other.
• Assign one scheduler to a daily "LUPA clearance" review — 20 minutes every morning, no exceptions.
• Set a 48-hour documentation rule. Visits not charted within 48 hours get escalated to the clinical manager.
• Turn on real-time LUPA risk scoring (if your EHR supports it).
• Review week-3 of every active period — that is where most LUPAs are still preventable.
• Track LUPA rate as a board-level KPI alongside census and claim rejection rate.

7. Frequently Asked Questions

What is a LUPA in home health?

A LUPA is when a 30-day home-health period falls below the CMS visit threshold under PDGM. Instead of the full case-mix payment, the agency is paid per-visit — typically 60-80% less than a standard episode.

What is the average LUPA threshold under PDGM?

Thresholds range from 2 to 6 visits per 30-day period depending on the clinical grouping. CMS recalibrates them annually, so always pull the current table at the start of each PDGM year.

What is a healthy LUPA rate for a home-health agency?

Industry benchmarks put a healthy LUPA rate under 5%. Best-in-class agencies operate at 1-3%. Anything above 8% indicates systemic problems worth fixing.

Can an EHR actually reduce LUPAs?

Yes — but only if it surfaces LUPA risk in real time. Legacy EHRs report LUPAs after the period closes, which is too late. EaseEHR predicts LUPA risk on day 7, 14, and 21 so schedulers can intervene while there is still time to add the visits.