Excludes1 in Medical Coding: Meaning, Examples & Rules
Excludes1 is one of the most important — and most misunderstood — notes in ICD-10-CM medical coding. Understanding what Excludes1 means, how to identify it, and when it applies can prevent claim denials and compliance issues. This complete guide covers everything medical coders need to know.
In This Article
1. What Does Excludes1 Mean in Medical Coding?
In ICD-10-CM, an Excludes1 note means that the excluded code and the code it appears under are mutually exclusive — they represent conditions that cannot occur in the same patient at the same time. The full meaning of Excludes1 is “NOT CODED HERE.”
❌ Excludes1 = Mutually Exclusive
When a code has an Excludes1 note, you should NEVER report that code together with the excluded code on the same claim. These two conditions cannot coexist in the same patient.
The Centers for Medicare and Medicaid Services (CMS) includes Excludes1 notes in the official ICD-10-CM Tabular List to guide coders when two conditions are clinically incompatible. For example, a patient cannot have both Type 1 and Type 2 diabetes simultaneously — these are biologically distinct conditions.
Excludes1 notes are updated annually each October 1st as part of the new fiscal year code update. Always use the current year’s guidelines when coding.
2. Excludes1 vs Excludes2 — Key Difference
Many coders confuse Excludes1 and Excludes2. The difference is critical:
| Feature | Excludes1 | Excludes2 |
|---|---|---|
| Meaning | NOT CODED HERE | NOT INCLUDED HERE |
| Can conditions coexist? | No — never | Yes — if documented |
| Code together? | NEVER | Yes, if both exist |
| Claim impact | Denial if coded together | Accepted if documented |
The simplest way to remember: Excludes1 = never together, Excludes2 = can be together if both conditions are documented.
3. Excludes1 Examples in ICD-10-CM
Here are real Excludes1 examples from the ICD-10-CM 2026 Tabular List:
Example 1 — Diabetes (Most Common)
Code E11 (Type 2 diabetes mellitus) has an Excludes1 note for E10 (Type 1 diabetes mellitus).
This means you can never report E11.9 and E10.9 together on the same claim.
This is an inherited rule — it applies to all child codes under E11 (E11.0, E11.1, E11.9, etc.)
Example 2 — Acute vs Chronic Conditions
Some acute condition codes have Excludes1 notes for their chronic counterparts because a condition cannot be both acute and chronic at the same time in the same episode.
Example 3 — Congenital vs Acquired
Many congenital condition codes have Excludes1 notes for their acquired counterparts. A condition is either congenital (present at birth) or acquired (developed later) — not both.
4. Inherited Excludes1 Rules
One of the most commonly missed aspects of Excludes1 is inheritance. In ICD-10-CM, Excludes1 notes placed on a category code (like E11) automatically apply to all child codes within that category.
⚠️ Critical Rule for Coders
Always check parent category notes — not just the specific code you are assigning. A code like E11.65 may not have a visible Excludes1 note, but its parent E11 does. That inherited rule still applies to E11.65.
This is why manual code lookup is risky. A coder checking only the leaf code may miss the inherited Excludes1 rule sitting on the parent category, leading to a claim denial.
The ICD10Check Excludes Checker automatically walks up the entire parent chain for each code entered, checking for both direct and inherited Excludes1 rules — so nothing is missed.
5. How Excludes1 Affects Claim Submission
Submitting two codes with an Excludes1 relationship on the same claim will almost always result in a claim denial. Here’s what happens at each stage:
Clearinghouse edit
Many clearinghouses run automated Excludes1 checks before submitting to payers. Claims with Excludes1 conflicts may be rejected before they even reach the payer.
Payer adjudication
If the claim passes the clearinghouse, the payer's system will flag the Excludes1 conflict during adjudication and deny the claim with a CO-4 or similar denial code.
Audit risk
Repeated Excludes1 violations can trigger a coding audit. This is a compliance issue, not just a billing issue.
Revenue impact
Denied claims require rework — resubmission, appeals, or write-offs. Preventing Excludes1 errors before submission is far more efficient.
6. Common Excludes1 Mistakes
Only checking the specific code
Coders often check only the leaf code for Excludes1 notes and miss inherited rules from parent categories. Always check the full hierarchy.
Confusing Excludes1 with Excludes2
Excludes2 notes allow both codes if both conditions are documented. Treating an Excludes2 note as Excludes1 leads to unnecessary undercoding.
Using outdated code references
Excludes1 rules change annually. A code combination that was valid last year may have a new Excludes1 restriction this year.
Not validating before submission
Many Excludes1 errors are caught only after denial. Pre-submission validation using a tool like ICD10Check can prevent this entirely.
Assuming Excludes1 means the condition cannot exist
Excludes1 means you cannot code both conditions together — not that the patient cannot have a related condition. Code only the primary documented diagnosis.
7. How to Check Excludes1 Conflicts
Manually checking Excludes1 rules for every code combination is time-consuming and error-prone, especially when inherited rules are involved. The most reliable approach is to use a dedicated validation tool.
🧪 Free Excludes1 Checker Tool
The ICD10Check Excludes Checker validates Excludes1 conflicts instantly. Enter multiple ICD-10-CM codes and the tool automatically checks both direct and inherited Excludes1 rules across the full code hierarchy.
Open Excludes Checker →The checker supports both single-code search mode and batch entry — paste up to 50 codes at once and get instant validation results. No login required.
- • Which two codes conflict
- • Whether the rule is direct or inherited from a parent category
- • The exact CMS Tabular List note text
- • The ancestor code where the rule originates
Summary
Excludes1 in medical coding means two codes are mutually exclusive and can never be reported together on the same claim. Always check both direct Excludes1 notes and inherited rules from parent categories. Pre-submission validation prevents claim denials and compliance issues.
Use the free ICD10Check Excludes Checker to validate your code combinations against the official CMS ICD-10-CM 2026 dataset — including all inherited Excludes1 rules.
Related Articles & Tools