Healthcare Doesn’t Have a Denial Problem. It Has a Learning Problem.

By Mubashir Hanif, Founder and CEO, TechMatter
LinkedIn: Mubashir Hanif
LinkedIn: TechMatter

The most expensive denial isn’t the first one. It’s the one we have already seen. If you work in revenue cycle, you know exactly which one I mean. Most of us treat denials like weather. They arrive, we rework them, we appeal the ones worth the effort, and we brace for the next front. A 2022 federal review found that 13 percent of the Medicare Advantage prior authorization denials it sampled met Medicare coverage rules. I think we have quietly decided that this is simply what billing feels like. But I strongly believe healthcare doesn’t have a denial problem. It has a learning problem.

That’s because of what happens after a denial. A denial is a message. Something in the process, whether registration, authorization, eligibility, documentation, coding, or payer policy, did not go as expected. In too many organizations, I suspect, that message goes to the billing team, which fixes the claim and moves on, while the person or process responsible for the original error never sees what happened.

The good news is that learning can be low-tech. You do not need a bigger billing team to start. One simple approach is to give registration staff report cards that show their own accuracy, so the people who enter the data can see how their work holds up further down the line. The fix is not more rework at the back end. It is telling the people who made the error what happened, while it is still fresh enough to change.

I’m wary of calling every denial a lesson. Some denials are legitimate, payer rules can change faster than any report card can keep up, and learning takes time that an overstretched team may not have. None of that changes the point. A denial that nobody reads is a cost. A denial that somebody reads is information. I believe behind every repeated denial is someone who would fix it tomorrow if only they knew.

So, how do you start? I call it the second-denial rule. The first time a denial happens, it may belong to the payer or to bad luck. The second time, for the same reason, it belongs to us. Every repeat reason gets an owner and a fix, and the team that creates the error gets to see its own numbers. Measure it simply: of this month’s denials, how many carry the same reason as last month’s? In practice, I’d keep the routine small: a short weekly review of the top three repeat reasons, one named person for each, one fix, and a check the following week on whether it held. None of that needs new software to start. A good report card is not a way to assign blame. It shows people their own pattern, kindly and early, so they can change it.

If you own a practice, ask your billing lead which three denial reasons repeat most, and whether the people behind them have been told. If you manage the front desk, ask to see your own denials, because you are the only person who can prevent them. If you’re a clinician, ask what your own denials say about your documentation, because the chart is where some of them begin. If you’re a CFO, fund the feedback loop before you fund another appeals team. And if you pay claims, treat every denial that gets overturned as a lesson of your own.

I expect that within a few years, the best revenue cycle teams will report their repeat-denial rate as readily as they report days in accounts receivable. The organizations that stop treating denials as a cost of doing business and start treating them as information will not just recover more revenue. They will lose less of it. I’m hopeful about that, because a problem we can learn from is a problem we can fix. I believe every denial is a message, and a message nobody reads is the most expensive kind.