Revenue Integrity Was Built for Hospitals. Health Centers Are Paying for That.

There is a professional association called NAHRI — the National Association of Healthcare Revenue Integrity — that has spent decades building career frameworks, certification tracks, and operational standards for a single discipline: the systematic identification and recovery of revenue that hospitals are entitled to but not collecting. Dedicated departments. Defined roles. A body of practice.

No equivalent exists in the safety-net world. No FQHC-specific revenue integrity framework. No community health career track. No standard methodology for an FQHC, rural health clinic, or CCBHC to measure what it is owed versus what it receives. The hospital world industrialized the problem and built the discipline. The safety-net world largely inherited the billing infrastructure hospitals discarded.

The result is measurable. Median health center operating margins were −2.1% in the most recent UDS data analyzed by KFF. Health centers lost an average of $595,000 each during the Medicaid unwinding, per a NACHC and George Washington University analysis. These are not numbers from a bad policy year in an otherwise stable industry. They reflect a structural revenue problem that has no dedicated discipline to find it.

Health centers are not mismanaging revenue. They are managing revenue through tools and frameworks that were not designed for their economics. That is a different problem — and it points toward a different solution.

The Hospital Playbook Doesn't Run on Safety-Net Economics

Hospital revenue integrity departments focus heavily on the chargemaster — the master list of prices, codes, and charges that drives fee-for-service billing. They audit charge capture against services rendered, validate coding against documentation, and reconcile payments against contracted rates. The infrastructure assumes a fee-for-service world where the price, the service, and the payment share a common logic.

An FQHC operates under a fundamentally different architecture. Medicaid pays a Prospective Payment System rate — a per-visit amount set in advance, based on the center's own historical cost data, that covers the scope of services regardless of what was actually billed. Managed-care plans pay a negotiated rate that may be lower than the PPS rate; a wraparound payment from the state is supposed to make up the difference. Sliding-fee discounts reduce self-pay revenue according to a schedule the center is required to maintain. The 340B drug-pricing program creates a separate revenue stream tied to outpatient drug dispensing. UDS reporting drives grant compliance and influences future funding.

None of this looks like a hospital chargemaster. A hospital revenue-integrity audit that focuses on charge capture and coding optimization will find some things — but it will miss the wraparound reconciliation gaps, the eligibility-driven PPS exclusions, the sliding-fee schedule misapplications, and the 340B tracking failures that represent the largest actual leakage for a health center.

The discipline that exists was built for a different set of economics. Importing it without modification is not revenue integrity. It is hospital consulting in a safety-net setting, which is a different thing.

Three Ways Revenue Disappears

The better frame starts from first principles: health centers lose revenue in three distinct ways, and the three ways require different data, different questions, and different interventions.

Revenue never earned is the invisible bucket. The care or the billable record never came into existence. A patient was seen but the encounter was not documented. A qualifying service was provided but never coded — a behavioral health screen embedded in a primary care visit, a care coordination touchpoint that met billing criteria, a preventive service that was delivered but omitted from the claim. In some cases, scheduled visits that should have generated a billable encounter resulted in no claim at all, because the workflow that connects scheduling to charge capture has a gap.

This bucket does not appear in your remittance data. A claim was never submitted, so there is no denial, no payment, no record. Finding it requires comparing what was scheduled or encountered against what was billed — a reconciliation that most centers do not run systematically, because no one's job description requires it.

Revenue earned but not captured is where the encounter happened and a claim was submitted, but the claim understates what the center was entitled to bill. Documentation gaps that prevent higher-level coding. Eligibility failures at the time of service that should have been caught before the visit and were not — resulting in a claim submitted for a patient whose coverage had lapsed. Charge capture breakdowns where services rendered in the visit were not reflected in what was sent to the payer. This bucket lives partly in remittance data and partly in the gap between the encounter record and the claim.

Revenue captured but not collected is the most visible bucket and the one most centers are already tracking — imperfectly. Denials. Underpayments. Wraparound payments that did not reconcile correctly to the PPS rate. CO-27 and similar eligibility-related denial codes that appear in the 835 remittance file and signal that coverage was not verified or not valid at the date of service. This bucket is fully visible in remittance data, but most centers view it through a claims-management lens rather than an integrity lens — which means they are measuring the symptom rather than tracing the cause.

Each bucket has a different locus. Each requires a different question. Treating all three as a single "revenue cycle problem" means none of them gets the analysis it needs.

Claims Reveal Leakage. They Don't Create It.

The standard framing in denial management is to start with the claim — the denial code, the payer, the provider, the denial reason — and work backward from there. This is a reasonable approach for operational triage. It is a poor approach for revenue integrity.

A claim denial is not where revenue leakage begins. It is where leakage becomes visible.

A CO-27 denial — patient not eligible for coverage on the date of service — may look like a billing problem. It is an eligibility verification problem that originated in scheduling, surfaced in patient registration, persisted through the visit, and finally appeared as a denial code in the 835. By the time a biller sees the denial, the appointment has been kept, the provider's time has been spent, and the revenue is at risk. Denial management that starts at the claim is archaeology: excavating the evidence of something that already happened.

An underpayment against the PPS rate may look like a payer error. It may be a payer error. It may also be a managed-care contract term that was never reconciled against the wraparound calculation, a rate schedule that was not updated after a cost report, or a payment posted incorrectly against the wrong service category. Each of those has a different root cause and a different fix.

The question "why was this claim denied?" is useful for individual claim resolution. The question "what organizational process produced this denial rate?" is the integrity question — and it points upstream, not at the claim.

Denial management is a revenue cycle function. Revenue integrity is a measurement and process function. The first resolves claims. The second changes the conditions that create the claims.

Measuring Integrity, Not Productivity

The metrics most centers track are not integrity metrics. They are productivity metrics.

Claims per biller measures how fast the billing team is working. Days in accounts receivable measures how long money sits uncollected. Clean claim rate measures the percentage of claims that pass edits on first submission. These are useful operational indicators. None of them tells you how much revenue the organization was entitled to and did not collect.

The distinction matters because productivity metrics can improve while integrity worsens. A billing team that resolves denials quickly and closes out aged balances is highly productive. If those denials originate in systemic eligibility verification failures, the denials will keep coming regardless of how fast the team resolves them. The productivity metric improves. The leakage continues.

An integrity metric asks a different question: against the revenue the organization was entitled to earn, how much was actually collected? Not against what was billed — against what was owed. That number requires knowing what was owed, which is the hard part. For the earned-but-not-captured and captured-but-not-collected buckets, it can be approximated from remittance and eligibility data. For the never-earned bucket, it requires encounter-level data.

Write-off classification is part of this. If write-offs are recorded as a single line item rather than classified by root cause — eligibility failure, no authorization, timely filing, contractual adjustment, bad debt — the organization cannot distinguish between acceptable adjustments and preventable losses. If that classification does not exist in your system today, the write-off total is the only number available, and the only number available is not an integrity measurement.

The Questions That Locate Each Bucket

The following are not diagnostic criteria. They are questions whose unanswerability is itself the finding. If a CFO asks these questions this week and no one can answer them, the gap that prevents the answer is the revenue integrity gap.

What share of denials trace to eligibility lapses at time of service — if you can produce this number by payer, by site, and by month, you have the data to know whether your eligibility verification process is working. If the number does not exist, eligibility-related denials are not being measured as a category, which means they are not being prevented as a category.
What the wraparound variance was last quarter — the wraparound payment is supposed to bring managed-care reimbursement up to the PPS rate; the delta between what managed-care paid and what the state wraparound paid should account for all of it. If no one is calculating that variance by plan and by period, there is no way to know whether the reconciliation is correct.
Whether write-offs are classified by root cause — write-offs represent revenue the center submitted a claim for and did not collect; the reason matters as much as the amount. A write-off classified only as "adjustment" or "contractual" is not information about what went wrong. Without root-cause classification, write-off totals are a financial reporting figure, not an improvement signal.
Whether anyone reconciles scheduled visits against billed claims — for the never-earned bucket, the core question is whether visits that happened generated claims. A center that cannot run this reconciliation — scheduled encounters against submitted claims, filtered by provider, date, and payer — cannot measure the never-earned bucket at all. The gap does not appear in remittance data. It appears only in the comparison.
What the denial rate is by denial code, by payer, by provider — aggregate denial rates are a compliance metric. Denial rates disaggregated by denial reason, by payer contract, and by ordering provider are an integrity metric. The disaggregation shows whether a high denial rate is a billing problem, an eligibility problem, a documentation problem, or a contract problem. Without it, the rate is a number with no actionable structure.
Whether the sliding-fee schedule is being applied consistently — a sliding-fee write-down applied inconsistently across sites or providers creates both compliance exposure and revenue measurement problems; if the sliding-fee adjustment is misclassified, the apparent revenue picture is distorted.

What the Data Can and Cannot Show

An honest account of what is findable from claims data is required here, because the temptation to overstate is real.

The 835 remittance file and eligibility response files — data that every health center already produces — are the starting point for the captured-but-not-collected bucket. Denial codes, payment amounts, contractual adjustments, eligibility responses at the date of claim: this is all in the 835. Comparing payments against expected rates by payer, by service category, and by period surfaces underpayment patterns. Sorting denial codes by CO-27 and similar eligibility indicators shows the eligibility-failure contribution. The captured-but-not-collected bucket is fully visible in this data.

The earned-but-not-captured bucket is partially visible. Some eligibility failures surface in the 835 — the claim was submitted and denied for eligibility-related reasons. But documentation gaps that prevented higher-level coding, or charge capture failures where a service was omitted from the claim, do not appear as denials — they appear as absences. Identifying them requires comparing the claim against the encounter record. Remittance data alone cannot surface these gaps; it can indicate where to look.

The never-earned bucket is not visible from claims data at all. A visit that generated no claim produces no 835. No denial. No payment. Nothing. Finding this bucket requires encounter-level data — scheduling logs, encounter records, provider productivity — and a reconciliation process that compares what was documented against what was billed. This is a different analysis, with a different data requirement, and a different process to conduct it.

Stating this plainly is not a limitation. It is the accurate scoping of the problem. A center that starts with remittance and eligibility data will find material issues in two of the three buckets. That is a starting point, not the complete picture.

Semi-Annual Redeterminations Make This Structural

Starting in late 2026, per the 2025 reconciliation law, Medicaid redeterminations will occur semi-annually rather than annually — a change that NACHC has flagged as creating a persistent, structurally elevated eligibility churn rate.

This matters for the earned-but-not-captured and captured-but-not-collected buckets specifically. More frequent redeterminations mean more eligibility transitions, more periods of lapsed coverage between renewal cycles, and more opportunities for a patient to be seen while coverage has technically lapsed. CO-27 denials and similar eligibility-related adjustments are not an artifact of the unwinding. They are becoming a permanent feature of the operating environment.

A center that does not have a systematic eligibility-at-time-of-service process — not just batch eligibility checks, but point-of-service verification tied to the visit — will see this bucket grow as the redetermination schedule tightens. The unwinding loss of $595,000 per center was an acute event. Semi-annual redeterminations are the chronic version of the same mechanism.

What Revenue Integrity Looks Like Here

The thesis of this post is not that health centers need to replicate hospital revenue integrity departments. The thesis is that the three buckets exist, that they are itemizable from data the center already produces, and that no single department is currently responsible for seeing all three.

Billing manages denials. Finance tracks write-offs and days in AR. Compliance monitors sliding fee and 340B. Quality tracks UDS denominators. No role is looking at the intersection — the question of whether the organization is collecting the revenue it is entitled to earn, across all three buckets, measured against entitled revenue rather than billed revenue.

That intersection is what revenue integrity means for a health center.

The entry point into this analysis is the center's own remittance and eligibility files. The Medicaid Revenue Diagnostic is a fixed-scope analysis of exactly that data — itemizing the captured-but-not-collected and earned-but-not-captured buckets from files the center already produces, with honest scoping of what encounter-level data would add for the never-earned bucket. The output is a structured view of where revenue is going and what it would take to recover it. Not a billing engagement. Not an ongoing service. A bounded analysis that tells the CFO where to look. Learn more about the Medicaid Revenue Diagnostic.

LumenHealth provides revenue diagnostics and advisory for community health organizations. This post reflects our current thinking and is not a substitute for organization-specific analysis.