As a revenue integrity director, Paige runs a tight operation. Her team works the queues. They file the appeals. They track overturn rates and report recovered dollars every month. By every conventional metric, they are performing.
And her organization is still leaving millions on the table.
Not because Paige is doing her job wrong. Because the frame she was handed for that job is wrong. And until that changes, no amount of operational excellence will close the gap.
The Question Nobody Asks Paige
Walk into almost any health system in America and ask where the denial management team sits. Revenue cycle. Working queues, filing appeals, tracking metrics.
Now ask the harder question: why does that team exist at all?
The reflexive answer is that denials are an unavoidable part of doing business with payers. They happen. You work them. You move on.
That framing is costing health systems billions of dollars a year. And it is letting payers off the hook for conduct that, in any other contract relationship, would be treated as a performance failure.
Paige has been handed an administrative workflow problem. What she is actually sitting on is a contract enforcement problem. Those are not the same thing, and they do not have the same solution.
A Denial is a Contractual Failure
When a payer denies a claim that meets the clinical criteria, the billing requirements, and the coverage terms of a negotiated contract, that is not a routine business occurrence. It is a breach of a contractual obligation.
The language matters because it changes everything downstream: how Paige staffs her function, how she reports on it, how she escalates it, and how seriously her payer counterparts take it when she raises it across the table.
An organization that frames denials as an administrative workflow problem builds administrative workflow solutions. Better technology. Faster appeals. More FTEs working queues. These are not bad investments. But they are investments in managing a symptom rather than addressing the underlying condition.
It is the organizational equivalent of taking a painkiller while your foot is nailed to the floor. It manages the discomfort. It does not fix the problem.
An organization that frames denials as a contract enforcement failure asks a different set of questions entirely.
Which payers are failing to honor their contractual obligations at a rate that exceeds any reasonable threshold?
What does the contract say about dispute resolution and remedies?
What is being done, systematically, to make the cost of non-performance visible and consequential?
Those are the questions Paige should be driving. They belong in a different conversation than queue management, and they belong at a different table than the one she is currently sitting at.
What Paige's Denial Data is Actually Telling Her
Her denial data is one of the most valuable payer intelligence assets her organization holds. Most organizations are using it almost entirely for operational reporting. Paige has the raw material for something far more powerful.
A payer whose medical necessity denial rate on a specific DRG has climbed 40 percent over 18 months without a corresponding change in clinical documentation has changed how they are applying coverage criteria. The contract may give grounds to challenge that formally.
A payer whose appeals overturn rate runs above 60 percent on a specific denial category is communicating, in the clearest possible language, that their initial denial decisions are not defensible. That is not a documentation issue on Paige's end. That is a systematic payment integrity failure on theirs.
When Paige reads her denial data through a contract enforcement lens rather than an operational one, the picture changes. So does the conversation she is equipped to have with her payer counterparts and with her own leadership.
Three Moves Paige Can Make to Shift the Framing
Rename the function and mean it. A denial management team manages denials. A payment integrity team enforces contracts. The difference in how each approaches its work, reports its findings, and engages with payer counterparts is not semantic. It is structural. The name signals the mandate. Start there, and build the expectations around it.
Build a payer performance scorecard anchored in denial data. Track denial rates, overturn rates, days to adjudication, and payment variance by payer on a rolling basis. When a payer crosses a defined threshold, the response is not more appeals. It is a formal conversation at the contract and relationship level about what is driving the pattern. Paige should be bringing that scorecard to her managed care counterparts, not keeping it inside revenue cycle.
Connect the denial analytics to the next negotiation. Systematic denial patterns, prompt payment violations, and unilateral policy changes that reduced reimbursement are not operational grievances. They are negotiating leverage. The managed care team negotiating the next renewal needs what Paige's data contains. If that handoff is not happening, it is one of the most expensive disconnects in the building.
The Bottom Line
Paige did not design the frame she inherited. But she is the one positioned to change it. The health systems that will win the next decade of managed care contracting are not the ones with the most sophisticated denial workflows. They are the ones that stop managing denials and start enforcing contracts. The data to do it is already sitting in Paige's system.
The question is whether her organization is reading it for the right purpose. And whether Paige is the one who changes that answer.
About the Author
Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com
Disclaimer: This article is provided for general informational and educational purposes only. It reflects my personal views and observations based on professional experience in healthcare finance, managed care, payer relations, and revenue cycle operations. It should not be interpreted as legal, financial, regulatory, actuarial, or reimbursement advice. The content is not intended to represent the official position of my employer, any payer, provider, professional association, or other organization with which I may be affiliated. Readers should consult their own legal, financial, compliance, actuarial, or operational advisors before making decisions based on the issues discussed. Any references to payers, providers, regulations, market trends, or reimbursement practices are intended for discussion and education only and should not be construed as a statement about any specific contract, negotiation, patient matter, or confidential business arrangement.