Guide · 10 min read

ICD-10 Specificity:
Laterality, 7th Characters, and Excludes Notes Explained

Using an unspecified code when a specific one exists is the fastest way to get a denial. Here is how to nail specificity every time.


The Short Version

ICD-10 specificity is the single most important factor in clean claim submission. Every code has a defined level of specificity — some require laterality (right vs left), others require a 7th character (initial vs subsequent encounter), and many have Excludes notes that tell you which codes can and cannot be paired together.

This guide covers the three specificity rules that trip up coders most often: laterality, 7th characters, and Excludes1 vs Excludes2. Use the icd10free code browser to verify specificity before every submission — search any code to see its full descriptor, chapter structure, and includes/excludes notes.

1,3, 2

Right, Left, Bilateral

A, D, S

7th Character Codes

Excludes1

Do Not Code Both

Excludes2

May Code Both


Why Specificity Matters

I once audited a practice where 35% of the diagnosis codes submitted to Medicare were unspecified. Diabetes without complications (E11.9). Hypertension (I10). Osteoarthritis of the knee (M17.9). Each code was technically valid — but each one was less specific than the documentation allowed. The practice was leaving specificity on the table, and every unspecified code carried the risk of a medical necessity denial.

Payers look at specificity for a simple reason: they cannot determine medical necessity from a vague code. 'Unspecified diabetes' does not tell the payer whether the patient has renal complications, ophthalmic complications, or neither. 'Unspecified osteoarthritis of the knee' does not say which knee or whether it is primary or secondary. When a payer sees an unspecified code, their options are to deny the claim, request additional documentation (delaying payment), or pay it and flag it for post-payment audit.

The CMS 2026 guidelines continue the decade-long push toward specificity. The message is clear: if a specific code exists, use it. If the documentation does not support it, improve the documentation. Unspecified codes should be the exception reserved for the rare case where the clinical picture genuinely lacks the detail for a more specific code.


How to Verify ICD-10 Specificity

ICD-10 code browser chapter view showing code structure, includes and excludes notes, and laterality requirements

Check Laterality First

ICD-10 uses the sixth character for laterality in many musculoskeletal, eye, and ear codes. 1 = right, 2 = left, 3 = bilateral. For example, M17.11 (unilateral primary osteoarthritis, right knee) vs M17.12 (left knee). If the condition is bilateral but the documentation only specifies one side, query the provider. If the side is not documented, you may need to use the unspecified code (e.g., M17.10) — but only as a last resort.

Apply the Correct 7th Character

Many ICD-10 codes in Chapter 19 (Injury, Poisoning) and Chapter 20 (External Causes) require a 7th character extension that describes the episode of care: A (initial encounter), D (subsequent encounter), or S (sequela). Using the wrong 7th character — or omitting it — is a guaranteed denial. For example, S82.001A (fracture of right patella, closed, initial encounter) vs S82.001D (subsequent encounter).

Respect Excludes1 vs Excludes2 Notes

Excludes1 means 'do not code both' — the two conditions cannot occur together (e.g., congenital vs acquired absence of a body part). Excludes2 means 'may code both if both exist' — the two conditions are related but can coexist (e.g., diabetes with foot ulcer). Using the icd10free Excludes Checker, you can test whether your code pair has a conflict before submitting the claim.

Use the Code Browser to Verify Specificity

Open the icd10free code browser at /diagnoses and navigate to the code you're considering. The code detail page shows the full descriptor, the chapter structure, the includes and excludes notes, and the Medicare payment data. If the code has laterality or 7th character requirements, you will see them listed. Use the browser as your specificity checklist before every submission.


Real Specificity Scenarios

Laterality: Right vs Left vs Bilateral

A patient presents with knee pain. The X-ray shows osteoarthritis. The physician documents 'primary osteoarthritis, left knee.' The coder selects M17.0 (primary osteoarthritis, unspecified site) instead of M17.12 (unilateral primary osteoarthritis, left knee). The difference matters: M17.0 is a nonspecific code that payers flag for medical necessity review. M17.12 tells the exact clinical story — it is left knee, primary, unilateral. If the claim is for a left knee arthroscopy, M17.12 supports the procedure. M17.0 invites a denial for insufficient specificity. Always use the laterality-specific code when the documentation supports it.

7th Character: Initial vs Subsequent vs Sequela

A patient falls and fractures their right femur. In the ED, the physician documents S72.001A (fracture of unspecified part of right femur, initial encounter for closed fracture). Six weeks later, the patient returns for a follow-up X-ray. The follow-up note should use S72.001D (subsequent encounter). If the coder uses 'A' again for the follow-up, the claim will deny — the 'A' character is only for the initial encounter when the patient is receiving active treatment. The 'D' character covers routine healing. If the patient develops a complication like malunion, a different code with different 7th character options applies. The 7th character tells the story of where the patient is in the treatment timeline.

Excludes1: The 'Do Not Code Both' Trap

A patient with type 2 diabetes is admitted for a foot ulcer. The physician documents E11.621 (type 2 diabetes with foot ulcer) and L97.509 (non-pressure chronic ulcer of unspecified foot with unspecified severity). The coder submits both. The Excludes1 note on E11.621 states: 'Do not code both. The diabetes code with foot ulcer includes the foot ulcer.' The L97 code is redundant and will be denied or recouped on audit. The correct approach is E11.621 alone — the diabetes code with the foot ulcer manifestation already covers the ulcer. Use the Excludes Checker to catch these redundant pairings before submission.


Tips from the Trenches

Three things I have learned about ICD-10 specificity from audits and denial reviews.

Unspecified Codes (XXX.X) Should Be the Exception, Not the Rule

I have audited records where 40% of diagnosis codes were unspecified. Every unspecified code is a denial risk. Payers increasingly auto-deny unspecified codes for certain conditions (diabetes, hypertension, CKD). The CMS 2026 guidelines continue the push toward specificity. If the documentation does not support a specific code, query the provider. If you cannot get the specificity, document why in the record — 'laterality not specified in clinical note, no further detail available' — so the audit trail is clear.

Use the Code Browser as Your Specificity Checklist

Before you submit a diagnosis code, search it in the icd10free code browser. The code detail page tells you: the full descriptor with all specificity requirements, the chapter and category, the includes and excludes notes, and the payment data. It also shows the parent code and child codes — letting you verify that you have chosen the most specific code available. I train coders to do this as a two-second habit before every claim.

Build a 'Common Specificity Mistakes' Bookmark Folder

Every coder has codes they get wrong. Maybe it is M17.1 vs M17.0 (laterality on osteoarthritis), or S82.001A vs S82.001D (7th character on fractures). Create a folder in the extension called 'Specificity — Watch List' and bookmark the codes you or your providers frequently miss. Review the folder before each shift. After two weeks, the pattern will be internalized — and the bookmarks become a record of how your coding accuracy improved.


Frequently Asked Questions

What coders ask about ICD-10 specificity and denial prevention.


Ready to Verify Your Code Specificity?

Search any ICD-10 code in the browser to see its full descriptor, laterality requirements, 7th character options, and includes/excludes notes.