ICD-10 D22.9: Melanocytic Nevi (Moles) Documentation — The Definitive Clinical & Coding Playbook for Dermatology

TL;DR: ICD-10 code D22.9 (Melanocytic nevi, unspecified) is one of the most denial-prone codes in dermatology when paired with excision CPTs 11400–11446. Payers routinely classify these removals as cosmetic unless the clinical note contains discrete ABCDE atypia findings, documented patient symptoms (itching, bleeding, evolution), precise millimeter dimensions with margins, and—when malignancy cannot be excluded—a crosswalk to D48.5 (Neoplasm of uncertain behavior of skin). This playbook details exactly how to document melanocytic nevi at the specificity level payers and LCDs demand, how Scribing.io automates every critical data element as structured FHIR resources, and why the CMS competitor article (A57113) leaves dermatologists exposed to preventable denials.

• Why D22.9 Is the Most Dangerous "Default" Code in Dermatology

• Technical Reference: ICD-10 Documentation Standards for D22.9 and D48.5

• The ABCDE Documentation Imperative: What Payers Actually Require

• What the CMS LCD Article Misses — And What It Costs You

• Scribing.io Clinical Logic: Preventing Cosmetic Denials for Excised Nevi in Real Time

• CPT Excision-Size Rules: The Margin Math That Breaks Claims

• FHIR-Native Structured Data: How Scribing.io Encodes Medical Necessity at the Resource Level

• Implementation Roadmap for Board-Certified Dermatologists

Why D22.9 Is the Most Dangerous "Default" Code in Dermatology

D22.9 — Melanocytic nevi, unspecified — appears on a claim when a clinician documents "mole removal" without anatomic specificity or clinical justification. The code is technically valid under CMS ICD-10-CM guidelines. It is also, in practice, a denial trigger that board-certified dermatologists cannot afford to ignore.

Dermatology excision claims paired with unspecified neoplasm codes experience denial rates 2–3× higher than claims using site-specific or behavior-upgraded codes such as D48.5. The mechanism is structural: Medicare Administrative Contractors (MACs) and commercial payers map their Local Coverage Determinations (LCDs) against discrete documentation elements. When D22.9 appears alongside CPT 11400–11446 (excision of benign lesion), automated claim scrubbers search for medical-necessity justifiers. If those justifiers are absent, the claim is flagged as cosmetic before a human reviewer touches it. Scribing.io exists to eliminate that gap—structuring ABCDE atypia findings, patient symptoms, and dimensional data as machine-readable FHIR resources that satisfy payer logic at the point of care, not after denial.

For comprehensive documentation guidance across the full ICD-10 dermatology code set, visit the Scribing.io ICD-10 Documentation Library.

The Core Problem: What D22.9 Tells a Payer vs. What the Payer Needs

D22.9 tells the payer nothing about why this nevus required excision. That burden falls entirely on the clinical note — and when the note is unstructured free text, the claim fails.

Technical Reference: ICD-10 Documentation Standards for D22.9 and D48.5

D22.9 — Melanocytic Nevi, Unspecified

D22.9 — Melanocytic nevi classifies benign melanocytic neoplasms when the anatomic site is not specified in the clinical record. Per ICD-10-CM Official Guidelines for Coding and Reporting (2026), this code should only be used when a more specific D22.x code cannot be assigned. The 2026 guidelines mandate code selection "carried out to the highest level of specificity available." Using D22.9 when the note states "shoulder" is a coding error—D22.5 (trunk, which includes shoulder per ICD-10 anatomy conventions) should be assigned.

Code Hierarchy Within D22

This specificity failure alone contributes to denial, as MACs expect anatomic concordance between the note narrative and the submitted code. Scribing.io's ambient documentation engine parses the clinician's dictated body site and auto-maps to the most granular D22.x code—D22.9 is never selected when site data exists anywhere in the encounter.

D48.5 — Neoplasm of Uncertain Behavior of Skin

D48.5 — Neoplasm of uncertain behavior of skin is assigned when clinical features suggest the lesion's behavior (benign vs. malignant) cannot be determined prior to histopathologic examination. This code carries substantially more medical-necessity weight than any D22.x code because it explicitly communicates clinical uncertainty—the uncertainty that justifies excision over observation.

When D48.5 Is Appropriate

• Clinical ABCDE criteria are present (asymmetry, border irregularity, color variegation, diameter > 6 mm, evolution)

• Dermoscopic features are atypical (irregular pigment network, blue-white veil, regression structures)

• The clinician documents that malignancy cannot be excluded pending pathology

• The lesion demonstrates recent change reported by the patient or documented on serial photography

When D48.5 Is NOT Appropriate

• Pathology has already returned a definitive benign result

• The lesion is clinically and dermoscopically classic for benign nevus with no atypical features

• The removal is purely patient-requested with no clinical indication

The D22.9 → D48.5 Decision Boundary

This is the single most consequential coding decision in benign-lesion dermatology. The threshold is clinical suspicion, not pathologic confirmation. Per AMA CPT guidelines, if the clinician's pre-excision assessment documents features that cannot exclude malignancy, D48.5 is the accurate code at the time of service—regardless of what pathology later reveals. Scribing.io's real-time coding engine evaluates documented ABCDE findings against this threshold and presents D48.5 as the recommended primary diagnosis when two or more atypia criteria are captured, with a one-click override for the clinician to accept or modify.

The ABCDE Documentation Imperative: What Payers Actually Require

The ABCDE mnemonic (Asymmetry, Border irregularity, Color variation, Diameter, Evolution) is not merely a clinical screening tool from the American Academy of Dermatology. It is the documentation framework that Medicare LCDs and commercial payers use to adjudicate medical necessity for mole excisions. When a note lacks discrete ABCDE elements, the payer has no structured basis to distinguish a medically necessary excision from a cosmetic one.

Element-by-Element Documentation Requirements

Patient-Reported Symptoms: The Missing Documentation Element

Beyond ABCDE morphology, payers specifically look for symptom documentation as independent medical-necessity justifiers. Research published in JAMA Dermatology consistently demonstrates that patient-reported symptoms correlate with atypical histology and strengthen the clinical rationale for excision. The critical symptoms to capture:

• Bleeding: "Patient reports intermittent spontaneous bleeding from the lesion, occurring 3 times in the past month without trauma"

• Itching/pruritus: "Persistent pruritus localized to the lesion for the past 8 weeks, not responsive to topical emollients"

• Pain/tenderness: "Point tenderness on palpation of the lesion; patient reports pain with clothing contact"

• Ulceration: "Central ulceration measuring 2 mm, noted on clinical exam"

These symptoms correspond to supporting ICD-10-CM codes (R23.8, L29.8, R52) listed in the CMS LCD Article A57113 Group 1 supporting diagnoses—yet A57113 never explains how to document them in a format that claim scrubbers can parse. That gap is where denials originate.

What the CMS LCD Article Misses — And What It Costs You

CMS LCD Article A57113 ("Billing and Coding: Removal of Benign Skin Lesions") is the primary reference document that dermatologists and coders consult for benign lesion excision coverage rules. It lists 80+ ICD-10-CM codes in Group 1, 60+ in Group 2, and provides CPT-to-diagnosis mapping. It states, correctly, that "appropriate code selection for lesion removal is determined by measuring the greatest clinical diameter of the apparent lesion plus that margin required for complete excision." What it does not do—and what costs dermatology practices thousands of dollars monthly in preventable denials—is address five critical gaps.

Gap 1: No Guidance on the D22.9-to-Excision Denial Pattern

The article lists D22.x codes as medically necessary for excision CPTs but does not warn clinicians that D22.9 specifically, paired with 11400–11446, is a high-denial combination. The code is technically covered, but claim scrubbers at major MACs and commercial payers flag unspecified-site codes paired with excision codes because excision implies a clinical decision that should be supported by specific anatomic and clinical documentation.

Gap 2: No ABCDE Documentation Framework

The article's documentation requirements section contains three generic bullet points: maintain documentation, include patient identification and legible signature, and ensure the medical record supports the selected ICD-10-CM code. These are administrative minimums, not clinical documentation standards. The article never mentions the ABCDE framework, never specifies what clinical findings constitute medical necessity for a melanocytic nevus excision, and never differentiates between a cosmetic removal and a medically necessary one at the documentation level.

Gap 3: No D48.5 Upgrade Pathway

D48.5 appears in the article's Group 1 code list as a covered diagnosis. The article provides zero guidance on when a clinician should use D48.5 instead of D22.x—the precise decision that determines whether a claim is adjudicated as medically necessary or cosmetic.

Gap 4: No CPT Margin-Math Validation

The article references the CPT margin rule but provides no methodology for ensuring the documented excision size (lesion + margins) maps to the correct CPT size tier. CPT size-tier miscoding is a leading cause of dermatology excision downcodes, independent of medical-necessity denials.

Gap 5: No Structured Data or Interoperability Guidance

The article was written for a paper-chart era. It contains no guidance on how to encode ABCDE findings, lesion measurements, or clinical photos in structured EHR formats. In 2026, payers increasingly ingest HL7 FHIR-formatted clinical data for real-time and prior-authorization adjudication. Documentation that exists only as unstructured narrative cannot be consumed by these systems—and Scribing.io is purpose-built to close that interoperability gap.

Scribing.io Clinical Logic: Preventing Cosmetic Denials for Excised Nevi in Real Time

Here is the scenario that makes the problem concrete: A dermatology NP excises a changing 7 mm shoulder nevus. The note lacks ABCDE specifics and omits the patient's report of intermittent bleeding; it also fails to document total excision size with margins. The payer classifies it as cosmetic and denies.

This is the exact denial pattern Scribing.io's real-time clinical logic was engineered to prevent. Below is the step-by-step breakdown of how the system intervenes at each failure point.

Step 1: Ambient Capture of Anatomic Site → Automatic D22.5 Assignment

The clinician says "shoulder nevus" during the encounter. Scribing.io's ambient speech engine captures "shoulder" and maps it to ICD-10 anatomic conventions: shoulder = trunk = D22.5, not D22.9. The unspecified code is never generated. This single step eliminates the first claim-scrubber flag.

Step 2: ABCDE Smart-Prompt Activation

When the system detects a nevus-related encounter with an excision intent, it activates the ABCDE smart-prompt panel. This is not a passive checklist—it is a structured data-capture workflow that prompts the clinician for each element with pre-populated LCD-compliant language templates:

• Asymmetry: The system prompts "Describe asymmetry" and offers structured options: "Asymmetric along one axis / both axes / none observed"

• Border: "Border characteristics" with options including "notched," "ill-defined," "scalloped," mapped to clock-face positions

• Color: "Color variation" with a palette selector capturing the number of distinct color zones and their descriptors (tan, dark brown, blue-black, red, white)

• Diameter: Numeric field requiring entry in millimeters—the system blocks note finalization if this field is blank when an excision CPT is selected

• Evolution: Timeline-structured prompt: "Change reported over [duration]: size increase / color change / shape change / new symptoms"

In our scenario, the NP documents asymmetry along one axis, border irregularity at 3 o'clock, two-color variation, 7 mm diameter, and evolution from 4 mm over 6 months. Each element is captured as a discrete FHIR Observation resource.

Step 3: Patient Symptom Capture — Bleeding Documentation

The NP mentions the patient reported intermittent bleeding. Scribing.io's symptom-capture module prompts for specificity: frequency (3 episodes), duration (past month), provocation (spontaneous, no trauma), and associated factors. The system generates the documentation string: "Patient reports intermittent spontaneous bleeding from the lesion, occurring 3 times in the past month without trauma." This is stored as a FHIR Observation linked to the lesion's anatomic site and cross-referenced to supporting ICD-10-CM code R23.8.

Step 4: FHIR-Linked Lesion Photo Attachment

The clinician captures a dermoscopic image. Scribing.io encodes this as a FHIR Media resource linked to the encounter, the lesion's FHIR Condition resource (D48.5 or D22.5), and the ABCDE Observation resources. When the payer's adjudication system requests supporting documentation via the CMS Prior Authorization Interoperability Rule (CMS-0057-F) FHIR API, the photo and all structured clinical data are available as a machine-readable bundle—not a faxed PDF that sits in a queue.

Step 5: D48.5 Recommendation Engine

With three ABCDE atypia criteria documented (asymmetry, border irregularity, evolution) plus patient-reported bleeding, Scribing.io's coding engine evaluates the clinical picture against the D22.x → D48.5 decision boundary. The system presents a recommendation: "Clinical findings meet threshold for uncertain behavior. Recommend D48.5 as primary diagnosis. Clinical rationale: Asymmetry (1 axis), border irregularity, evolution over 6 months, patient-reported spontaneous bleeding. Malignancy cannot be excluded pending histopathology." The clinician accepts with a single click. If the clinician overrides to D22.5, the system flags this as a documentation-code discordance requiring attestation.

Step 6: Excision Size Calculator and CPT Validation

The system prompts: "Enter narrowest planned margin in mm." The NP enters 2 mm. The built-in excision size calculator computes: 7 mm (lesion) + 2 mm (margin × 2 sides) = 11 mm total excision diameter. This maps to CPT 11402 (excision, benign lesion, trunk, 1.1–2.0 cm). The system validates that the documented dimensions match the selected CPT tier and blocks submission of a mismatched code—preventing the downcode that would occur if the NP accidentally selected 11401 (0.6–1.0 cm).

Step 7: Pre-Submission LCD Validation

Before the claim is released, Scribing.io runs a final LCD compliance check against the rules encoded from A57113 and MAC-specific addenda. The check confirms: (1) D48.5 is in Group 1 covered diagnoses for CPT 11402, (2) supporting symptom code R23.8 is present, (3) ABCDE documentation elements are complete, (4) excision dimensions are concordant with the CPT size tier, and (5) a linked clinical photo exists. The claim passes all five checks and submits clean—paying on first submission.

Conversion Hook: See our ABCDE + symptom smart-prompt with FHIR-linked photos and a built-in excision size calculator that blocks cosmetic denials before you submit.

CPT Excision-Size Rules: The Margin Math That Breaks Claims

Per AMA CPT guidelines, excision codes 11400–11446 are selected based on the excised diameter: the greatest clinical diameter of the lesion plus the narrowest margin required for complete excision, measured in centimeters. This is not the specimen size measured by pathology—it is the pre-excision clinical measurement documented by the surgeon.

CPT Size Tier Reference: Trunk, Arms, Legs (11400 Series)

The Three Margin-Math Errors That Cause Downcodes

1. Documenting only lesion diameter without margins: A 7 mm lesion documented as "7 mm excision" maps to 11401 (0.6–1.0 cm). But if 2 mm margins were taken, the actual excision is 11 mm → 11402. The practice loses the difference in reimbursement.

2. Confusing clinical diameter with pathology specimen size: Specimen shrinkage in formalin can reduce dimensions by 10–20% (NIH/PubMed literature). The CPT code must be based on the pre-excision clinical measurement, not the pathology report.

3. Failing to document margins at all: When no margin is documented, coders must use only the lesion diameter. A 7 mm lesion with no margin documentation maps to 11401, not 11402—even if the surgeon clinically took 2 mm margins. This is the most common and most preventable error in dermatology excision coding.

Scribing.io's excision size calculator requires both lesion diameter and planned margin width as mandatory fields before an excision CPT can be finalized. The system computes the total excised diameter, maps to the correct CPT tier, and displays the calculation transparently in the note: "Excised diameter: 7 mm (lesion) + 2 mm × 2 (margins) = 11 mm (1.1 cm). CPT 11402 selected." This documentation string satisfies auditor requirements and eliminates the margin-math errors described above.

FHIR-Native Structured Data: How Scribing.io Encodes Medical Necessity at the Resource Level

Unstructured clinical notes are invisible to modern payer adjudication systems. The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) mandates that payers implement FHIR-based APIs for prior authorization and claims attachment exchange. Documentation that exists only as narrative text in a progress note cannot be consumed by these APIs—which means the clinical justification you carefully documented may never reach the adjudicator.

Scribing.io generates every clinical data element as a discrete HL7 FHIR R4 resource. Here is how the nevus excision encounter maps to FHIR:

Every FHIR Observation is linked to the parent Condition (D48.5) via focus references. When a payer system queries the encounter via FHIR API, it receives a complete, machine-readable bundle that includes the diagnosis, every ABCDE finding, the patient symptom, the photo, and the dimensional data—all structured, all queryable, all satisfying the LCD medical-necessity criteria without human review of a narrative note.

This is not a theoretical architecture. Scribing.io's FHIR export is operational with major EHR platforms conformant to the ONC USCDI v4 standard, including Epic, Oracle Health (Cerner), and MEDITECH Expanse.

Implementation Roadmap for Board-Certified Dermatologists

Deploying Scribing.io's nevus documentation workflow in a dermatology practice follows a structured four-phase implementation. Each phase has discrete milestones and measurable outcomes tied to denial reduction.

Phase 1: Baseline Denial Audit (Weeks 1–2)

• Pull all D22.x and D48.5 claims paired with CPT 11400–11446 from the past 12 months

• Categorize denials by reason: cosmetic classification, missing documentation, code specificity, CPT-size mismatch

• Identify the percentage of claims submitted with D22.9 vs. site-specific D22.x codes

• Calculate the revenue impact of denied and downcoded excision claims

Phase 2: Scribing.io Configuration and EHR Integration (Weeks 3–4)

• Configure the ABCDE smart-prompt panel for dermatology encounter types

• Set mandatory fields: lesion diameter (mm), margin width (mm), body site, at least one ABCDE finding

• Enable the D48.5 recommendation engine with the two-or-more-atypia-criteria threshold

• Establish FHIR Media integration for dermoscopic photo linking

• Map MAC-specific LCD rules (A57113 and regional addenda) into the pre-submission validator

Phase 3: Clinician Training and Workflow Adoption (Weeks 5–6)

• Train dermatologists and NPs/PAs on the ABCDE smart-prompt workflow using the shoulder-nevus scenario detailed in this playbook

• Conduct mock encounters with deliberate documentation gaps to demonstrate real-time intervention

• Establish the attestation workflow for D48.5 override scenarios

• Review the excision size calculator with margin-math examples from each CPT tier

Phase 4: Monitoring and Optimization (Ongoing)

• Track first-pass clean claim rate for D22.x/D48.5 + excision CPT combinations weekly

• Monitor D22.9 usage—target: < 2% of all melanocytic nevi codes submitted

• Measure denial rate reduction against Phase 1 baseline; target: 60–80% reduction within 90 days

• Review LCD updates quarterly and push rule changes to the pre-submission validator

Expected Outcomes

Every denied nevus excision claim costs your practice between $150 and $400 in lost reimbursement plus $25–$50 in rework labor. A practice performing 50 nevus excisions monthly with a 20% cosmetic denial rate loses $18,000–$108,000 annually in preventable revenue leakage. Scribing.io's structured documentation and pre-submission validation eliminate the documentation gaps that cause those denials—not after the fact, but in real time, at the point of care where clinical decisions are made and clinical language is spoken.

The standard is no longer "document enough to justify." The standard is document in the structured format that payer adjudication systems can consume. That is what Scribing.io delivers.