Why Is "Services Not Covered" Now the Top Denial Reason, and What Should Coding, CDI and RCM Teams Change?

Jessica Miller, MHA, CPC, CPC-I

8 min read · November 18, 2026

Photograph of two hospital revenue-cycle colleagues comparing a closed claim folder with a coverage-policy binder at a claims desk, representing why services not covered is now the top denial reason.

Written by Jessica Miller · Published 18 November 2026 · Last reviewed 18 November 2026

In Experian Health's State of Claims 2026 survey of 204 provider revenue cycle leaders, 53 percent put "services not covered" in their top three denial reasons, the first time it ranked first. That is a survey ranking, not claims data. Most of the fix starts before the claim drops.

Survey finding, State of Claims 2026What it measures
53 percent named "services not covered" in their top three denial reasonsShare of 204 respondents, not share of denied claims
31 percent named frequently changing payer policiesRanked second
25 percent each named code inaccuracy and prior authorization difficultyTied for third
40 percent said 10 percent or more of their claims are denied41 percent said so in 2025, so the level is flat
30 percent recover 80 to 100 percent of denied revenue, 52 percent recover only 50 to 70 percentRecovery buckets reported by respondents

Figures come from the Experian Health State of Claims 2026 report (PDF) . The second column is our reading.

What did the State of Claims 2026 survey find?

Experian Health released the report on October 28, 2026, with its State of Claims blog post . The survey ran August 5 to 23, 2026, among 204 finance, billing, registration and claims leaders, from directors to chief officers. An HFMA page dated November 13 recaps the same findings. It is sponsored content bylined by Experian Health, not HFMA research.

"Services not covered" ranked first for the first time. The report's footnote says the chart counts how often each reason appeared in respondents' top three choices. So 53 percent is the share of respondents who named it, not the share of denials it causes.

Coding is not the top cause. Code inaccuracy tied for third, behind payer policy changes, and 78 percent of respondents said those policy changes are more frequent. Denial levels held flat. Treat these figures as a direction signal, not a benchmark, and measure your own denials by reason code, payer and policy.

What does "services not covered" mean on a remittance?

"Services not covered" is a survey label, not one code. Respondents may group benefit exclusions and medical necessity denials under it. On the remittance it tends to arrive under several X12 claim adjustment reason codes :

  • CARC 50: "These are non-covered services because this is not deemed a 'medical necessity' by the payer."
  • CARC 96: "Non-covered charge(s)," which must carry at least one remark code that explains why.
  • CARC 204: "This service/equipment/drug is not covered under the patient's current benefit plan."

Each has a different owner. CARC 204 is benefit design, caught by patient access before the visit. CARC 50 is a payer's medical necessity criteria, where documentation matters. CARC 96 depends on its remark code. Experian does not tie its category to any code, so don't map the 53 percent onto one.

For the coding-error codes, see coding-related denial reasons and CARC codes .

What did UnitedHealth's medical policy review cover, and what did it leave out?

UnitedHealth Group retained FTI Consulting and Rubrum Advising, a physician-led coverage policy firm, to review how UnitedHealthcare develops and maintains medical policies. The full report is dated October 8, 2026. UnitedHealth Group released it on November 12, 2026.

The reviewers examined nine sample policies, three in each of three clinical evidence categories. The UnitedHealth Group CEO letter says "all nine sample medical policies met the review criteria and were found to be supported by clinical research."

The report states its limits. "For policies within the scope of the review, the Review Team did not test or evaluate the specific content of UnitedHealthcare's medical policies, how medical policies are applied in individual coverage decisions, or the completeness of the literature review." Policies on drugs and behavioral health sat outside the Medical Policy team's remit and were not reviewed.

The executive summary also names gaps: no explicitly documented criteria for new policy development or for vetting subject matter experts. It recommends a policy template that would standardize how each policy presents its evidence and coverage rationale.

The review and the Experian survey are separate items, and neither measures the other. The review looked at how policies are written. Proving that a claim meets a policy still falls to the provider.

What can coding, CDI and RCM teams change before the claim drops?

These steps are MediCodio's operations reading, not findings of the survey or the review.

  1. Patient access confirms the benefit and any authorization requirement before the service. A benefit exclusion is not a coding problem.
  2. CDI lists the documentation elements a payer policy names for your most-denied services, and queries when the record is silent. Never query to fit a policy.
  3. Coding assigns codes from the record. If a documented diagnosis is not on a payer's covered list, that is a coverage outcome, not a reason to change the code.
  4. Billing checks Medicare coverage rules before the claim goes out.
  5. Denials staff trend these codes by payer and by the policy named in the remittance, then route each by root cause. Use how to identify and prevent medical coding denials to separate coding denials from the rest.
  6. Leadership reviews payer policy bulletins monthly and assigns each change an owner.

This is general operations guidance, not legal advice.

Where does MediCodio AI fit?

MediCodio AI does not check eligibility, benefits or prior authorization, and it cannot make a non-covered service payable. Its role is narrower: when a payer cites medical necessity, coding teams need to see that the chart supports the codes billed.

Complete charts flow through AutoPilot for fully autonomous coding. Charts where the documentation is thin or contradictory stay in CoPilot, where certified coders review and finalize the output. Every code ships with its documentation passage and the compliance rule behind it. That is how AI medical coding supports CDI and coding teams on the documentation side of a coverage denial.

Frequently asked questions

What does a "services not covered" denial mean?

It is a broad label for denials where the payer says it will not pay for the service, not that the claim was coded wrong. On the remittance it can appear as CARC 50 for medical necessity, CARC 96 for non-covered charges with a remark code, or CARC 204 for services outside the benefit plan.

Is a "services not covered" denial a coding error?

Not by default. A benefit exclusion points to plan design, and a medical necessity denial points to payer policy criteria. Coding still matters, because codes must reflect the record and the documentation must show what the policy requires. Coding teams should never change a diagnosis to fit a covered list.

Is the Experian ranking based on claims data?

No. It comes from a survey of 204 provider revenue cycle staff, from directors to chief officers, fielded in August 2026. The ranking counts how often each reason appeared in respondents' top three choices. It is not a share of denied claims.

Did UnitedHealth's November 2026 review examine denials?

Not directly. FTI Consulting and Rubrum Advising reviewed how UnitedHealthcare develops and maintains medical policies and examined nine sample policies. The report says it did not evaluate how policies are applied in individual coverage decisions. UnitedHealth Group retained both firms and released the report on November 12.

Can AI medical coding stop "services not covered" denials?

No. Many of these denials come from benefits, eligibility or authorization, which coding does not control. AI coding can help on the documentation side by tying each code to the passage that supports it, so CDI and coding teams can see whether the record meets a payer's medical necessity criteria.

See how this works on your own charts. Book a Demo and we will code a sample of your own charts, so your coding and CDI leads can see the documentation passage behind every code. Book a Demo

Sources

See it in action

Ready to transform your medical coding?

See how MediCodio's AI platform delivers 98%+ accuracy across deployments since 2023, with turnaround under 24 hours at enterprise volume, inclusive of coder review, across 35+ specialties.

About the Author

JM
Jessica MillerMHA, CPC, CPC-I

Founding Member & Product Evangelist

Jessica Miller is the Head of Coding Operations at MediCodio, where she leads our AI-powered medical coding services with over a decade of experience in medical coding, compliance, and healthcare management. She specializes in developing innovative medical coding workflows that combine human expertise with cutting-edge technology to deliver exceptional accuracy and efficiency for healthcare organizations.

LinkedIn

Loading posts...