What is the difference between Excludes1 and Excludes2?

Excludes1 means 'do not code both' — the two conditions are considered mutually exclusive and cannot be reported together. If an Excludes1 conflict exists, you need to find a combination or more specific code. Excludes2 means 'may be coded together with proper documentation' — the two conditions can coexist, but you must have clear clinical evidence supporting both. The tool flags Excludes1 in red (hard block) and Excludes2 in amber (documentation check).

Can I override an Excludes1 warning?

No. Excludes1 is a hard coding rule. If the ICD-10 classification says two codes cannot be reported together, no amount of documentation or justification changes that. The solution is to find the correct combination code or replace one of the codes with a more specific option. If no combination code exists, the two diagnoses are truly mutually exclusive and should not both be coded.

What are manifestation codes and how do they differ from exclusions?

Manifestation codes describe a condition that is a direct result of an underlying disease. They have a 'code first' sequencing rule that requires the underlying disease to be listed first. For example, diabetic neuropathy (G63.2) must be coded after the diabetes code. This is a sequencing rule, not an exclusion — both codes can be reported together, but in a specific order. The tool focuses on Excludes1 and Excludes2 conflicts, not sequencing rules.

How many codes can I check at once?

The tool supports up to 50 ICD-10 codes in a single batch. With 50 codes, the tool checks 1,225 code pairs — every possible combination — against the exclusion tables. Most encounters have 4-10 codes, so the limit is generous enough for complex patients and small enough to keep results manageable.

Does it check NCCI/CCI edits or just ICD-10 exclusions?

The Excludes Checker checks ICD-10-CM Excludes1 and Excludes2 conflicts specifically. It does not check NCCI (National Correct Coding Initiative) edits, which are a separate set of code-pair restrictions that apply to CPT/HCPCS procedure codes. CCI edits are a related but distinct compliance concern — they restrict procedure code combinations, not diagnosis code combinations.

Can I paste a full clinical note instead of individual codes?

Yes. The tool automatically extracts ICD-10 codes from any pasted text. Paste a clinical note, a superbill, or a list of codes and the tool will identify every valid code, add it to your list, and check for conflicts. This is especially useful when reviewing a chart that someone else coded and you want a quick second opinion before submission.

Guide · 8 min read

ICD-10 Excludes1 vs Excludes2:
The Definitive Guide

Never submit a conflicting diagnosis code pair again. A field guide to understanding when codes can and cannot be reported together.

Check Your Code Pairs

The Short Version

The Excludes Conflict Checker takes a list of ICD-10 codes and checks every possible pair against the official ICD-10-CM exclusion tables. Add codes by searching or paste a full clinical note — the AI extracts every valid code, then identifies Excludes1 conflicts (red: cannot report together) and Excludes2 conflicts (amber: needs separate documentation).

It is a compliance tool that catches code-pair conflicts before the claim goes out the door. No more auditors finding an Excludes1 violation on a chart you coded last month. No more denied claims because two codes were reported together that should not have been.

Codes Per Batch

Conflict Types

Red

Excludes1 (Hard Block)

Amber

Excludes2 (Check Docs)

Why Code Exclusions Matter

I once watched a hospital get hit with a $47,000 RAC recoupment because a coder had been billing E11.9 (Type 2 diabetes without complications) alongside L97.419 (non-pressure chronic ulcer) on every diabetic foot ulcer encounter for six months. Every single claim had an Excludes1 violation that should have been caught by a five-second code-pair check. The auditor found 47 claims in a single afternoon.

ICD-10-CM includes thousands of code-pair exclusions. Some are obvious — you would not code traumatic fracture and pathological fracture for the same bone. Others are subtle — did you know that I10 (essential hypertension) excludes I11-I13 (hypertensive heart and kidney disease) because the latter already includes the hypertension component? Coding both is a double-bill that auditors spot immediately.

The two types of exclusions serve different purposes. Excludes1 reflects the ICD-10 classification principle that certain conditions are mutually exclusive — they cannot both be true. Excludes2 recognizes that some conditions commonly coexist, but the documentation must independently support each one. Confusing the two leads to either missed codes (when a valid Excludes2 pair is not reported) or audit exposure (when an Excludes1 pair is reported).

Every coder knows the exclusion rules exist. The challenge is applying them to 10-20 codes on a typical claim where the exclusions are buried in the tabular list and easy to miss.

How the Excludes Checker Works

Add Your ICD-10 Codes

Type a code or keyword to search the ICD-10 code set and add codes one by one. Or paste a block of clinical text — the tool automatically extracts every valid ICD-10 code from it. You can check up to 50 codes in a single batch.

AI Scans Every Code Pair

The tool compares every combination of codes you have entered against the official ICD-10-CM exclusion tables. It checks for two types of conflicts — Excludes1 (codes that should never be reported together) and Excludes2 (codes that need separate documentation).

Review Excludes1 Conflicts (Red)

Excludes1 conflicts are flagged in red. These are code pairs where the ICD-10 classification says the two conditions cannot occur together. If you see a red flag, one of the codes is likely incorrect and needs to be replaced with a more specific code or a combination code.

Review Excludes2 Conflicts (Amber)

Excludes2 conflicts are flagged in amber. These are code pairs where the two conditions could occur together — but only if the clinical documentation clearly supports both. The amber flag is a warning to verify that your documentation justifies reporting both codes on the same claim.

Common Code Conflicts

Diabetes with Foot Ulcer — An Excludes1 Trap

A patient with Type 2 diabetes presents with a diabetic foot ulcer. The coder selects E11.9 (Type 2 diabetes without complications) and L97.419 (non-pressure chronic ulcer of heel and midfoot). The Excludes Checker flags this as an Excludes1 conflict: E11.9 excludes L97.- because diabetes with foot ulcer has its own combination code — E11.621 (Type 2 diabetes with foot ulcer). The fix is to replace the two codes with the single combination code. This is the most common Excludes1 violation I see, and it is entirely preventable.

Hypertension with Heart Disease — Excludes2

A patient has essential hypertension (I10) and hypertensive heart disease (I11.9). The coder bills both codes together. The Excludes Checker flags this as an Excludes2 conflict: I10 excludes I11 with the note 'use additional code for heart failure.' An Excludes2 means the two conditions can coexist, but the documentation must support both. In this case, the correct coding is I11.9 (hypertensive heart disease without heart failure) — I10 is not reported separately because I11 already includes the hypertension. The tool flags it so you can verify that your documentation supports the specific combination.

COPD and Asthma Overlap — Know Your Excludes2

A patient with a long history of COPD (J44.9) is also being treated for asthma (J45.909). The documentation supports both diagnoses. The Excludes Checker flags an Excludes2 conflict between J44 and J45. The note says: 'COPD and asthma can coexist in the same patient — use additional code to identify asthma if applicable.' This is a classic Excludes2: both codes can be reported together, but only when documentation supports the distinct presence of both conditions. The amber flag reminds you to document carefully — an auditor will look for separate clinical evidence for each.

Tips from the Trenches

Three things thirty years of ICD-10 coding have taught me about exclusions.

Excludes1 Means NEVER Together — Not 'Sometimes If You Document Well'

I have seen coders argue that an Excludes1 conflict can be overridden with good documentation. It cannot. Excludes1 means the ICD-10 classification considers these conditions mutually exclusive. They cannot occur together. If you try to report both, the claim will be rejected or flagged for audit. The fix is never to override — it is to find the correct combination code. For example, instead of E11.9 + L97.419, use E11.621. The combination code exists for exactly this reason. If no combination code exists, one of the diagnoses is probably wrong.

Excludes2 Is a Documentation Trigger, Not a Hard Block

Unlike Excludes1, an Excludes2 warning means the two conditions can coexist — but your documentation must prove it. The ICD-10 note for an Excludes2 relationship says: 'The two conditions may be present at the same time, but you need additional documentation to support reporting them together.' I tell every coder I train: when you see an Excludes2 flag, stop and ask yourself whether the chart independently documents both conditions. If both are clearly present, bill both. If one is documented only because of the other, use the combination code or drop the secondary code.

Manifestation Codes Are a Special Kind of Exclusion

Some ICD-10 codes have a 'code first' or 'use additional code' instruction that creates a manifestation relationship. For example, code G63.2 (diabetic polyneuropathy) has a 'code first' instruction for the underlying diabetes (E11.43). This is different from Excludes1 or Excludes2 — it is a sequencing rule. The manifestation code can never be listed first. It must always follow the underlying disease code. The Excludes Checker does not catch all sequencing issues, so always check the 'code first' and 'use additional code' notes in the ICD-10 tabular list.

Frequently Asked Questions

Questions I hear from coders learning the exclusion rules.

Ready to Check Your Code Pairs?

No sign-up, no credit card, no upsells. Add your codes and check for conflicts in seconds.