Understanding the financial impact of LUPAs—and why they occur—can help turn a familiar utilization metric into a meaningful management tool.
Most home health agencies know their Low Utilization Payment Adjustment (LUPA) rate.
Far fewer understand the financial impact those LUPAs may have on their organization—or how significantly that impact can vary from one patient encounter to another.
The financial difference can be substantial.
To better understand the potential financial impact, I analyzed LUPA payment scenarios across the 477 CBSAs used for Medicare home health reimbursement. The results were significant: approximately 94% of those CBSAs have at least one payment scenario in which a single LUPA could result in more than $3,000 in lost Medicare revenue in a single 30-day payment period. More than half have at least one scenario exceeding $3,500, approximately 14% have at least one exceeding $4,000, and in 10 CBSAs, the potential lost revenue can exceed $5,000.
That makes LUPAs more than a billing or utilization statistic.
They are something management should understand.
Not Every LUPA Is the Same
An agency cannot—and should not expect to—eliminate every LUPA.
Some Low Utilization Payment Adjustment (LUPAs) result from circumstances largely outside the agency’s control. A patient may be unexpectedly hospitalized. A patient may refuse scheduled visits. A patient’s condition or circumstances may change. Other events may prevent the agency from providing the number of clinically appropriate visits originally anticipated.
We refer to these as Uncontrollable LUPAs.
They need to be understood, but their occurrence does not necessarily indicate an operational problem.
Other LUPAs deserve a different question:
Could this LUPA reasonably have been prevented?
A missed visit that was never rescheduled. A scheduling or communication breakdown. Failure to recognize that a patient was approaching the applicable LUPA threshold. A breakdown in coordination among clinicians, scheduling, operations, and billing.
These circumstances do not mean an additional visit should be provided simply to avoid a LUPA. Clinical need must determine the care provided.
But when clinically appropriate care was intended and could reasonably have been provided, yet operational circumstances prevented it from occurring, the resulting LUPA may represent an avoidable loss of Medicare revenue.
We refer to these as Controllable LUPAs.
And that distinction matters.
A LUPA Percentage Tells You What Happened—not Why
A low LUPA rate is not necessarily evidence of good management, just as a higher LUPA rate does not, by itself, demonstrate poor performance.
The percentage tells you what happened.
It does not tell you why it happened.
The more useful management objective is to understand the LUPAs occurring within the organization, distinguish those that were reasonably controllable from those that were not, and determine whether recurring operational patterns are contributing to avoidable LUPAs.
For every LUPA, management should ultimately be able to ask:
Why did it happen?
Was it reasonably controllable?
If it was, what should we do differently?
And there is another question that often receives considerably less attention:
What did it cost us?
Putting a Dollar Amount on the LUPA
For several years, I have received inquiries from home health professionals asking about the availability of a tool that could calculate the financial impact of an individual LUPA encounter.
I have maintained a working model for some time. With the launch of the newly redesigned IFS4hh website, this seemed like the right opportunity to expand that model and make the capability broadly available to the home health industry at no cost.
The result is the IFS4hh LUPA Calculator.
For a selected HIPPS Code, CBSA, and visits provided by discipline, the Calculator first determines whether the encounter falls below the applicable Low Utilization Payment Adjustment threshold. When it does, the Calculator:
- Calculates the applicable post-sequestration, wage-adjusted full 30-day Medicare payment;
- Calculates the post-sequestration, wage-adjusted LUPA payment based on the visits entered by discipline; and
- Calculates the difference—the estimated Medicare revenue lost as a result of the LUPA.
If the applicable LUPA threshold has been met, the encounter is not a LUPA and no LUPA calculation is displayed.
Why post-sequestration?
Because the objective is to compare the estimated cash the agency would receive under the two payment scenarios.
The Calculator does not incorporate potential revenue impacts attributable to the Home Health Value-Based Purchasing Model (HHVBP), the LUPA add-on payment when applicable, or other claim-specific payment adjustments. It is intended to provide a straightforward estimate of the core Medicare revenue difference between the applicable full 30-day payment and the LUPA payment.
The Calculator evaluates revenue only. It does not incorporate the agency’s cost of providing care or calculate encounter-level profitability.
In other words, it helps quantify the lost Medicare revenue associated with the LUPA.
And there is no single dollar value associated with a LUPA.
The financial impact depends on the applicable HIPPS Code, wage index, and visits actually provided. That is why one LUPA may have a very different financial consequence from another—and why simply knowing the number or percentage of LUPAs does not tell management the entire story.
Multiply those differences across multiple Controllable LUPAs during a month or year, and something that may have been viewed primarily as a utilization statistic can become a meaningful financial and operational issue.
The Objective Is Not to Avoid LUPAs at the Expense of Patient Care
This distinction is important.
The purpose of quantifying the financial impact of a LUPA is not to encourage unnecessary visits simply to reach a LUPA threshold.
Patients should receive every clinically appropriate visit that contributes meaningfully to their care—no more and no less.
Clinical need must determine the care provided.
But agencies should also have the operational processes necessary to ensure that clinically appropriate care that was planned is actually delivered.
If a clinically appropriate visit does not occur because of an avoidable scheduling problem, communication breakdown, missed-visit process, or other operational failure—and that failure results in a LUPA—the organization should understand both why it happened and what it cost.
That is where a LUPA moves from being merely a reimbursement outcome to becoming a management issue.
From Measurement to Management
The return of the Home Health PEPPER in August 2026 provides another reason for agencies to take a fresh look at their LUPA experience.
LUPA encounters are among the areas reviewed within the Home Health PEPPER. The information can help agencies identify patterns that may warrant closer examination.
But identifying a metric is only the beginning.
PEPPER can help identify the question. Management still has to find the answer.
For LUPAs, that means moving beyond an agency-wide percentage and examining individual encounters, causes, financial consequences, and recurring patterns.
The objective should not be zero LUPAs.
Nor should the objective simply be to achieve a particular LUPA percentage.
The objective should be to understand why LUPAs occur and continually work to minimize those that are reasonably within the organization’s control.
An Uncontrollable LUPA may simply reflect circumstances that could not reasonably have been prevented.
A Controllable LUPA may be telling management something very different.
What Did Your Last LUPA Really Cost You?
In the example above, the applicable LUPA threshold is four visits. With three visits provided, the encounter falls just one visit short of the threshold—resulting in an estimated $3,582.82 in lost Medicare revenue.
That is the kind of financial impact that can remain largely unseen when management knows an encounter resulted in a LUPA, but does not know what that LUPA actually cost.
The LUPA was already known. The $3,582.82 financial consequence may not have been.
The IFS4hh LUPA Calculator is currently available at no cost to help home health agencies estimate the Medicare revenue impact of an individual LUPA encounter.
It won’t tell you why the LUPA occurred.
It won’t tell you whether it was controllable.
But it can answer an important question:
What did it cost?
And sometimes a percentage identifies an issue, while putting a dollar amount on it helps establish the priority.
For organizations that want to go beyond calculating the revenue impact after a LUPA occurs, the IFS4hh Case-Mix Planner™ provides both proactive and reactive visibility into individual patient encounters—LUPA and full-payment encounters alike. By incorporating an agency’s discipline-specific Costs Per Visit (CPVs) and applicable revenue adjustments, including HHVBP, the Case-Mix Planner brings together patient acuity, Case-Mix Weights, LUPA thresholds, planned utilization, reimbursement, and costs to help evaluate encounter-level profitability prospectively as care is planned and delivered, and retrospectively to better understand the financial and utilization results that occurred.
Somebody asked me how many CBSA/Service Areas have 100 or more HIPPS Code/Case-Mix Weights with an estimated lost Medicare revenue of $2,500.00 or more in a LUPA situation?
The answer is 167 CBSA/Service Areas could!
That means 167 CBSA/Service Areas will have AT LEAST 100 HIPPS Codes that could create a LUPA encounter with lost Medicare revenue (the difference between the full 30-day payment and the LUPA revenue) of at least $2,500 for that 30-day period. It doesn’t take many LUPA encounters for the lost Medicare revenue to really start adding up.
And the lower we set that $ threshold, the more CBSA/Service Areas will fall under those parameters.