Back to Blog
Healthcare

Excludes1 Denials: The Coding Rule Costing Hospitals Millions

A widely ignored ICD10 convention is suddenly being enforced. Healthcare organizations are losing revenue they didn't know was at risk.

Jan 11, 20264 min read

Somewhere in your claims data, there's a problem you probably can't see. It's not a dramatic billing error or a flagged audit finding. It's a quiet, technical coding rule called "Excludes1" that most providers have never heard of until they start seeing unexplained denials pile up.

Over the past several years, commercial payers have begun enforcing Excludes1 edits in their claims adjudication systems. The result: millions of dollars in denied claims for conditions that were legitimately diagnosed and treated, rejected simply because two diagnosis codes appeared together on the same claim. Industry estimates suggest 1-2% of claims contain Excludes1 violations. At large health systems, the financial impact can reach tens of millions of dollars annually in lost revenue [1].

The rules aren't new. But the enforcement is. And most healthcare organizations aren't prepared.

What Is Excludes1?

ICD10 CM includes two types of "excludes" notes that define relationships between diagnosis codes. Excludes1 is the stricter of the two. It means "NOT CODED HERE" and indicates that two codes are mutually exclusive. If a patient has condition A, they cannot simultaneously have condition B on the same claim. The codes represent diagnoses that, by clinical definition, cannot coexist.

Consider a straightforward example: major depressive disorder. ICD10 CM distinguishes between a single episode (F32.x codes) and recurrent episodes (F33.x codes). These are mutually exclusive by definition. A patient experiencing their first depressive episode cannot simultaneously be coded as having recurrent depression. The Excludes1 note prevents both from appearing on the same claim.

These rules exist for clinical accuracy. They ensure that coded diagnoses reflect medically plausible combinations and that claims data can be used reliably for quality measurement, risk adjustment, and population health analytics. The problem isn't the rules themselves. It's that enforcement has been inconsistent, and many billing systems were never built to catch violations before claims go out the door.

Why This Matters Now

For years, many payers accepted claims with Excludes1 violations without issue. Providers had little incentive to validate diagnosis combinations, and EHR systems rarely flagged potential conflicts. That's changing.

Industry estimates suggest 1-2% of claims contain Excludes1 coding conflicts. While that may sound small, applied to the billions of claims submitted annually, it represents substantial revenue at risk. According to HFMA, hospitals lose an average of 4.8% of net revenue to denials, translating to tens of millions of dollars annually for large health systems [2].

The financial stakes are significant. The average cost to rework a denied claim ranges from $25 to $118 depending on complexity, with HFMA reporting average costs of $47.77 for Medicare Advantage denials and $63.76 for commercial denials [2]. Up to 65% of denied claims are never resubmitted at all, representing permanent revenue loss [3]. With coding related denials surging more than 125% in 2024 compared to the prior year, the problem is accelerating [4].

What makes Excludes1 denials particularly difficult to manage is that no standardized denial code exists for them. There's no designated Claim Adjustment Reason Code (CARC) that identifies an Excludes1 violation, which means these denials get lumped into generic "coding error" categories. Without clear tracking, revenue cycle teams often don't realize the scope of the problem until it's substantial.

Which Payers Are Enforcing Excludes1?

The enforcement landscape is fragmented. Some payers implemented Excludes1 edits years ago; others are just rolling them out. Here's what we know from public documentation:

PayerEnforcement StatusImplementation DateSource
Anthem/ElevanceActiveMarch 2019[5]
UnitedHealthcareActive, expandingJan 2024; Full March 2026[6]
Aetna (PA Medicaid)ActiveNovember 2017[7]
Empire BCBS (NY)ActiveApril 2021[8]
Medicare FFSNot enforcedN/A[9]
Medicare AdvantageVia commercial payerVariesVaries

More payers are adding Excludes1 edits each year. UnitedHealthcare's March 2026 expansion is particularly significant. It will extend enforcement to all outpatient and professional claims, affecting a substantial portion of commercial volume [6].

One critical distinction: traditional Medicare fee for service does not enforce Excludes1 edits in its claims processing. The Medicare Code Editor (MCE) validates for age/sex conflicts, manifestation code sequencing, and other edits, but not diagnosis exclusivity [9][10]. However, Medicare Advantage plans operated by commercial payers do enforce Excludes1, since they use commercial claims editing systems. With over 54% of Medicare beneficiaries now enrolled in MA plans, the distinction matters less than it once did [11].

Why It's Hard to Fix

The Excludes1 rules themselves are publicly available. CMS publishes the complete ICD10 CM code set, including all exclusion notes, through the CDC's National Center for Health Statistics [13]. The challenge is that the data is buried in files with nested hierarchies, code ranges, and inheritance rules that require significant processing to extract into usable validation logic [14].

Most EHR systems don't have built in Excludes1 validation. Industry observers note that "many electronic health records are not designed to alert providers to potential discrepancies" and "even billing software often does not contain the database required to prevent mutually exclusive codes" [12]. Major EHR vendors typically rely on external encoders or clearinghouse rejections to catch these errors, by which point the claim has already been submitted and denied.

Manual rule maintenance can't keep up with the scale. With thousands of ICD10 CM codes and complex exclusion hierarchies, the number of potential code combinations requiring validation runs into the millions. Annual ICD10 CM updates add and modify codes every October, with midyear updates in April, requiring continuous maintenance that few organizations have the resources to sustain.

Enterprise solutions from companies like 3M, Cotiviti, and Change Healthcare incorporate Excludes1 validation into their platforms, but these are typically bundled into comprehensive (and expensive) claim editing services [13][14]. There's no clean, standalone Excludes1 dataset available on the market for organizations that want to build validation into their own systems.

Who's Most Affected

Certain specialties and claim types see disproportionate impact from Excludes1 enforcement:

  • High volume claims processors including clearinghouses, RCM companies, and large health systems, where even a small percentage of affected claims translates to significant revenue
  • Organizations with aging EHR systems that lack modern validation capabilities
  • Multi-specialty practices where diverse diagnosis combinations increase the likelihood of code conflicts
  • Physical therapy practices are frequently affected due to musculoskeletal diagnosis combinations [15]
  • Behavioral health providers face frequent violations due to the complexity of mental health diagnosis coding

The Path Forward

Addressing Excludes1 denials requires proactive validation before claims are submitted, not reactive rework after denials come back. The foundation is clean, structured data: code pairs that are explicitly prohibited, updated with each CMS release, and accessible in formats that integrate with existing billing workflows.

Through our work with healthcare organizations, we've developed comprehensive Excludes1 validation datasets that transform complex CMS source files into actionable, API accessible code pair data. Our approach focuses on making the rules usable, not just available.

Getting Started

If Excludes1 denials are impacting your revenue cycle, or you want to prevent them before they start, we can help. Our healthcare data solutions are designed to reduce coding related denials through accurate, up to date validation data.

Interested in Excludes1 or other complex data extraction for your organization? Contact us to learn more.

References