A pattern across recent revenue cycle engagements: high-volume denials that look procedural but actually trace to documentation gaps the agency can recover on appeal — if the appeals team knows where to look.
The pattern we keep seeing
Most revenue cycle teams categorize denials by remit code. Reason 16 is missing information. Reason 22 is coverage criteria not met. Reason 50 is non-covered services. The team works each category with a corresponding appeal strategy, the recovery rate is tracked, and the dashboard moves up or down quarter over quarter.
The pattern Precisian sees across engagements is that one of the most recoverable categories is hiding inside the codes that look procedural. Specifically: medical necessity denials that arrive coded as documentation insufficiency. The denial reads as a paperwork problem. The appeal gets worked as a paperwork problem. And the appeal frequently fails — not because the documentation is missing, but because the documentation present in the record is not surfaced in the appeal in the way the contractor reviewer needs to see it.
Why this category is invisible inside most denial dashboards
Denial dashboards roll up by reason code. Reason code categorization is what the contractor said the denial was about. It is not always what the denial was actually about. When a contractor reviewer sees medical necessity documentation that is present but not clearly linked to the billed service, the denial code that gets applied is often a documentation code — missing information, missing supporting documentation, or insufficient documentation.
The appeals team reads the code, pulls the chart, sees the documentation exists, attaches it to the appeal, and submits. The contractor reviews the appeal and upholds the denial — because the documentation is still not surfaced in the way that links it to the medical necessity standard. The appeal team marks the denial as “procedural denial confirmed” and moves on.
The denial was never procedural. It was medical necessity all along.
A concrete example
In a recent post-acute revenue cycle engagement, we reviewed 90 days of denied claims across a three-site agency. The agency’s denial dashboard showed 312 denials in the period. 89 of those denials carried reason codes the team had categorized as “documentation insufficiency.” The team had worked the 89 denials with standard documentation appeals. The recovery rate on that category was 23 percent.
We reviewed the underlying contractor adjudication notes on a sample of 25 of those 89 denials. In 18 of the 25 cases — 72 percent — the contractor’s actual rationale referenced medical necessity standards. The denial code was documentation. The denial reason was medical necessity. The appeal had been worked as documentation. The appeal had failed.
We reworked appeals on 12 of those 18 cases, surfacing the medical necessity linkage explicitly. Recovery rate on that subset: 75 percent.
What the appeal looks like when it is written for the actual standard
The appeals team had been doing the right work, just not surfacing it the right way. A medical necessity appeal needs three things visible to the reviewer:
- The clinical condition or diagnosis that creates the need for the service, documented in the chart with specificity that meets the coverage standard (not just the diagnosis code, but the underlying clinical picture).
- The clinical reasoning that ties the service to the condition — why this service, at this frequency, in this setting, is reasonable and necessary for this patient.
- The reference to the applicable coverage standard — LCD, NCD, Medicare Benefit Policy Manual chapter, or contractor article that defines what reasonable and necessary means for the service.
The appeals the team had been submitting included the documentation. They did not always include the linkage and the reference. The contractor reviewer is not going to do the work of connecting the chart to the standard. The appeal has to do that work.
How to surface this category in your own data
Three diagnostic moves separate agencies that recover this category from agencies that miss it:
- Pull the contractor adjudication notes. Not just the denial code. The contractor explanation that came with the denial. When the explanation references medical necessity, level of care, frequency standards, or coverage criteria, the denial is medical necessity even if the code is documentation.
- Cross-check denial categorization quarterly. Run a sample of denials marked as documentation insufficiency against the contractor explanation. The pattern usually surfaces fast.
- Train appeals to write to the actual standard. Medical necessity appeals need the three elements above. Documentation appeals need a different structure. The agencies that win this category at scale have their appeals team trained to recognize the difference and write to the actual standard, not the coded one.
The upstream fix
The pattern fix sits upstream of the appeals team. When clinical documentation routinely surfaces the medical necessity linkage at the point of care — clinician notes that explicitly connect the service to the condition and the standard — the denials drop and the appeals that do arrive are easier to win. The clinical documentation integrity (CDI) work that supports this is well-known in the inpatient setting and underdeveloped in most outpatient and post-acute settings.
Most RCM departments are measured on recovery rate. The measurement should be recovery rate plus the upstream pattern. Same denials, same recovery rate, every quarter is not progress — it is treading water at a higher denial volume.
What this means for the operating cycle
Two practical implications:
- If your denial dashboard shows a stubborn documentation-insufficiency category that does not move quarter over quarter, the category is probably mis-categorized. A sample pull of contractor notes will tell you.
- If your recovery rate is below 40 percent on that category, the appeals are likely being written to the wrong standard. The fix is at the appeal-writing layer, not the documentation layer — though the documentation layer matters too.
The pattern, once surfaced, recovers real revenue. In the engagement referenced above, our recommendation produced an estimated $340,000 in recovery across the 90-day claim period that had been written off as procedural. That money was in the chart all along. The appeal just needed to be written for the contractor that wrote the denial. Open a case file with us if your denial recovery pattern looks like the one in this article.