The Revenue Per Patient That Most Home Health Agencies Leave on the Table

Your agency provides excellent care. Your documentation is solid. Your clinicians are competent. But your revenue per patient may be lower than it should be — not because of care quality, but because of how your claims are coded, when your eligibility is checked, and whether your PDGM grouping is optimized.

Most home health agencies leave revenue on the table in three places. Each one is fixable without changing how you deliver care.

Revenue Leak 1: Eligibility Denials

This is the most expensive leak because the revenue is permanently unrecoverable. When a patient loses coverage and you continue providing services, every visit after the coverage lapse is a write-off. You cannot rebill. You usually cannot collect from the patient. The money is gone.

The scale depends on your payer mix and verification frequency. Agencies with a high Medicaid census are most exposed because Medicaid coverage is inherently volatile — roughly 8% of beneficiaries experience a coverage gap in any given year, per MACPAC. But Medicare Advantage plan switches, coordination of benefits errors, and dual-eligible misassignments all create eligibility risk across every payer type.

The fix is straightforward: verify eligibility on a rolling schedule, not just at intake. Agencies that check weekly catch coverage changes within days. Agencies that check only at intake or monthly can accumulate weeks of unbillable services before discovering a lapse. For a full breakdown of how denial rates vary by payer, see Home Health Claims Denial Rate in 2026.

Revenue Leak 2: Suboptimal PDGM Coding

Under CMS’s Patient-Driven Groupings Model, the primary ICD-10 diagnosis code determines which of 12 clinical groups the episode falls into, and each clinical group has a different case-mix weight. A higher weight means higher payment for the same 30-day period of care.

Revenue leakage happens when the primary diagnosis is not the code that maps to the highest appropriate clinical group. This is not about gaming the system. It is about ensuring that the primary diagnosis accurately reflects the primary reason for home health services and maps to the clinical group that correctly represents the patient’s care needs.

Common scenarios where coding leaves money on the table:

• Defaulting to a catch-all code. Coders under time pressure sometimes use a general code when a more specific diagnosis is documented and would map to a higher-paying group.
• Not evaluating secondary diagnoses. A patient with both a wound and diabetes might have the diabetes code listed as primary, grouping the episode into Endocrine. If wound care is the primary reason for services, the Wounds clinical group (with a higher typical weight) may be more appropriate.
• Using terminated codes. A code that was valid last year but terminated in the current CMS update will cause a denial, not just a lower payment.

For a detailed explanation of how the 432 payment groups work, see PDGM Explained: How 432 Payment Groups Determine Your Revenue.

Revenue Leak 3: Missed Comorbidities

PDGM applies a comorbidity adjustment — None, Low, or High — based on the secondary diagnosis codes on the claim. CMS has defined specific diagnosis pairs that, when present as secondary diagnoses, trigger an upward adjustment to the case-mix weight.

If your coding does not capture all clinically documented comorbidities as secondary diagnosis codes, the adjustment defaults to “None” even when the patient qualifies for a higher tier. This is not overcoding. It is accurately reflecting the patient’s clinical complexity.

Common reasons comorbidities go uncaptured:

• OASIS assessments that do not fully reflect the patient’s conditions. If a comorbidity is in the physician orders but not in the OASIS, it may not make it onto the claim.
• Coders who focus on the primary diagnosis only. Under time pressure, secondary diagnoses get less scrutiny.
• Lack of awareness of CMS comorbidity pairs. Not every coder knows which diagnosis combinations trigger a comorbidity adjustment.

Quantifying the Revenue Impact

The revenue impact of these three leaks varies by agency size, payer mix, and current processes. But even conservative estimates are significant:

• Eligibility denials: For a 200-patient agency with 50% Medicaid census, the expected annual exposure from coverage lapses is tens of thousands of dollars. Each lapse caught before the next visit prevents a write-off. For the full cost breakdown, see What Happens If You Bill a Patient Who Lost Medicaid Coverage.
• Coding optimization: Moving even a fraction of episodes from a lower clinical group to a higher one — when clinically appropriate — increases average revenue per episode. The CY2026 standardized 30-day payment is approximately $2,034, so small weight differences translate to meaningful dollars.
• Comorbidity adjustments: The jump from “None” to “Low” comorbidity adjustment adds to the case-mix weight. For patients who genuinely have documented comorbidities, this is revenue you have already earned but are not collecting.

How ClientCare Captures Revenue You Are Already Earning

ClientCare’s Revenue Intelligence platform addresses all three leaks in a single dashboard:

• Revenue Protected: Automated eligibility monitoring catches coverage lapses before services are provided, preventing the most unrecoverable category of revenue loss.
• Revenue Assured: Billing code validation checks ICD-10 codes against the CMS unacceptable diagnosis list, verifies HCPCS code currency, and flags terminated codes before submission. See Billing Code Compliance Checklist for the full validation workflow.
• Revenue Optimized: PDGM optimization identifies resequencing opportunities and flags missing comorbidity adjustments. Every recommendation is tied to clinical documentation and includes the estimated revenue delta.

No EHR integration required. Upload your patient roster as a CSV from any system. Monitoring begins immediately.