Verified

ICD-10 B35.1: Tinea Unguium (Nail Fungus) Complete Coding Guide for Podiatrists

Master ICD-10 B35.1 documentation for tinea unguium. Avoid Medicare denials for nail debridement with proper coding, LCD compliance & documentation tips.

ICD-10 B35.1: Tinea Unguium (Nail Fungus) Complete Coding Guide for Podiatrists - Clinical Documentation Guide Illustration for Scribing.io

ICD-10 B35.1: Tinea Unguium (Nail Fungus) — Complete Documentation & Coding Guide for Podiatrists

TL;DR: Medicare MACs routinely deny nail debridement (CPT 11720/11721) billed with B35.1 alone as "cosmetic." Coverage requires explicit documentation of pain with ambulation OR secondary infection, a minimum 60-day interval between services, and accurate nail count (1–5 for 11720; 6+ for 11721). Scribing.io encodes these LCD rules at the point of dictation, preventing the denial before it happens. See Scribing.io Pricing

  • The 'Cosmetic' Trap: Why B35.1 Alone Triggers Medicare Denials

  • What Competitors Miss: The LCD Frequency and Secondary ICD Gap

  • Scribing.io Clinical Logic: Handling the Mycotic Nail Debridement Denial Pattern

  • Technical Reference: ICD-10 Documentation Standards

  • LCD-Aware Workflow Implementation: Epic and athena via FHIR

  • Audit Defense: The 6-Element Documentation Checklist

  • Nail Debridement Workflow: Live in Your EHR Today

The 'Cosmetic' Trap: Why B35.1 Alone Triggers Medicare Denials

Every practicing DPM knows the frustration: you perform a clinically necessary debridement of mycotic nails, submit the claim with ICD-10 B35.1, and receive a denial stamped "cosmetic/not medically necessary." The payer isn't questioning whether onychomycosis exists—they're questioning whether the thickened nails cause a functional impairment that justifies intervention.

This is the anchor truth that most coding guides fail to articulate clearly: Payers deny debridement for B35.1 unless the note documents "pain while walking" or "secondary infection." Simple documentation of "thickened nails" or "dystrophic nails" is treated as a non-covered cosmetic condition under Medicare Local Coverage Determinations. Scribing.io was built to intercept this exact failure mode—encoding LCD medical-necessity language requirements directly into the clinical dictation workflow so the denial never generates. See our Scribing.io ICD-10 Documentation Library for the complete code-pairing logic.

The competitive LCD article from First Coast (A57672/L33922) lists B35.1 as a supported diagnosis code, which creates a dangerous false confidence. Providers see B35.1 on the "supported" list and assume it alone justifies coverage. What the article buries—and what most competitor resources entirely miss—is that the LCD narrative (L33922) requires documentation of qualifying symptoms in addition to the fungal diagnosis. The code list is necessary but not sufficient.

The Three-Part Coverage Requirement

For CPT 11720/11721 to pay with B35.1 as primary:

  1. Qualifying symptom documentation — Pain with ambulation (rated on a numeric scale), difficulty with footwear, or secondary bacterial/fungal infection at the nail margins

  2. Clinical evidence of mycosis — Visual description of nail dystrophy plus antifungal treatment history or documented contraindication (per AMA CPT guidelines)

  3. Frequency compliance — Minimum 60-day interval from last debridement service date

Failure on any single element triggers denial. Current clinical benchmarks from MAC audit data indicate that B35.1-only claims without qualifying symptom documentation experience denial rates exceeding 40% on first submission across Novitas, First Coast, and CGS jurisdictions.

What Competitors Miss: The LCD Frequency and Secondary ICD Gap

The CMS Medicare Coverage Database article (A57672) and similar MAC resources present B35.1 as a supported code in a flat list alongside 25+ other mycotic diagnoses. Here's what they systematically fail to address—and what constitutes the critical information gap for practicing podiatrists:

Gap 1: The 60-Day Hard Cap Is Invisible in Code Lists

Most Medicare MAC Routine Foot Care and Nail Debridement LCDs hard-cap CPT 11720/11721 to a 60-day minimum frequency. This isn't a suggestion—it's an automated claims-processing edit. A claim submitted at day 49 or day 55 will auto-deny regardless of documentation quality. Yet this frequency rule appears nowhere in the ICD-10 code reference tables that most providers consult. The rule lives in the LCD narrative text, not the code attachment list.

Gap 2: B35.1 Requires a Medically Supported Secondary ICD

The "supported diagnosis" list creates an illusion of standalone sufficiency. In practice, MAC medical directors reviewing audited claims expect to see B35.1 paired with a secondary code that establishes medical necessity. The NIH clinical evidence base for onychomycosis supports that the condition frequently presents with concurrent pain and periungual infection—yet these findings go undocumented because nothing in the standard EHR template prompts their capture.

Secondary ICD-10 Code

Description

Documentation Trigger

Denial Risk Reduction

M79.671

Pain in right foot

"Pain while walking, rated X/10"

High

M79.672

Pain in left foot

"Pain while walking, rated X/10"

High

M79.673

Pain in unspecified foot

"Pain while walking, rated X/10"

High

M79.674

Pain in right toe(s)

"Pain localized to affected digit(s)"

High

M79.675

Pain in left toe(s)

"Pain localized to affected digit(s)"

High

L03.031

Cellulitis of right toe

"Erythema, warmth at nail fold"

Very High

L03.032

Cellulitis of left toe

"Erythema, warmth at nail fold"

Very High

L60.0

Ingrowing nail

"Mycotic nail incurvation with tissue impingement"

Moderate

L03.019

Cellulitis of unspecified finger/toe

"Paronychia with purulence"

Very High

Gap 3: Nail Count Documentation Drives CPT Selection Compliance

CPT 11720 covers debridement of 1–5 nails. CPT 11721 covers 6 or more. Yet MAC audits frequently reveal that providers bill 11721 without explicitly documenting how many nails were debrided. When the count is absent, auditors downcode to 11720 or deny entirely. Per the AMA's CPT code descriptors, the nail count must appear as a discrete, auditable data element—not buried in narrative prose where a reviewer must infer the number.

Gap 4: Antifungal Treatment Documentation

Per L33922's documentation requirements, providers must document "use of appropriate anti-fungal treatment or the contraindication of such treatment." A claim for mycotic nail debridement without reference to topical/oral antifungal therapy or a documented reason for non-use (hepatic contraindication, drug interaction, patient refusal with informed consent) is vulnerable to post-payment recoupment. Research published in the JAMA Dermatology archives confirms that systemic antifungals carry hepatotoxicity risk sufficient to justify topical-only or debridement-only management—but this clinical reasoning must appear in the record.

Scribing.io Clinical Logic: Handling the Mycotic Nail Debridement Denial Pattern

The Scenario: A DPM debrides 8 mycotic nails and bills 11721 with only ICD-10 B35.1. Medicare denies as cosmetic: no pain-with-walking or secondary infection documented, and the prior 11721 was 49 days earlier.

With Scribing.io running, the mic-driven template interrupts the workflow at the exact documentation gap—before the note is finalized, before the claim is generated:

Workflow Step

Without Scribing.io

With Scribing.io

1. Nail Count Capture

Provider dictates "debrided mycotic nails bilaterally" — count ambiguous

Structured prompt forces discrete entry: "8 nails debrided" → system confirms 11721 (≥6) is appropriate

2. Frequency Check

Provider unaware last service was 49 days ago; claim submitted and auto-denied

System pulls last 11721 date from encounter history via FHIR; alerts: "Last debridement 49 days ago — 60-day minimum not met. Earliest compliant date: [Day 62]"

3. Qualifying Symptom Prompt

Note reads "thickened, dystrophic nails" — no functional impairment language

Mic-driven template interrupts: "Document gait-limiting pain OR secondary infection to support medical necessity with B35.1"

4. Clinician Response

N/A — denial already generated

Clinician documents: "Pain while walking, 6/10; paronychia L great toe with periungual erythema"

5. Secondary ICD Selection

B35.1 submitted alone

System auto-suggests M79.675 (pain in left toe) + L03.032 (cellulitis left toe); clinician confirms

6. Compliance Attestation

No verification step

System generates compliance attestation: antifungal treatment documented (ciclopirox topical), nail count confirmed (8), frequency met (Day 62), qualifying symptoms present

7. Claim Submission

Denied on first pass; appeal required (avg. 45-day delay + staff time)

Claim submitted at Day 62 with B35.1 + M79.675 + L03.032 supporting 11721. Pays on first pass.

Step-by-Step Logic Breakdown: How the 'Cosmetic' Trap Is Defeated

Step 1 — Recognition of the denial pattern. Scribing.io's LCD rule engine identifies that B35.1 + CPT 11721 carries a "cosmetic denial" flag unless accompanied by qualifying documentation elements. This isn't a generic alert—it's a pattern-specific intervention mapped to MAC denial reason codes.

Step 2 — Temporal compliance enforcement. The system queries the patient's encounter history (via FHIR integration with Epic, athena, or any R4-compliant EHR) for the most recent CPT 11720/11721 service date. If the interval is below 60 days, the system blocks premature scheduling or explicitly flags the gap for the clinician. In the scenario above, it reschedules the documentation-complete encounter to Day 62.

Step 3 — Structured symptom capture at the microphone. When the clinician dictates findings for a mycotic nail encounter, the system's natural language processing detects the absence of LCD-required qualifying language. It delivers an inline prompt—not a pop-up that disrupts flow, but a conversational cue within the dictation interface: "Is the patient experiencing pain with walking? Rate severity. Is there periungual infection present?"

Step 4 — ICD code pairing with maximum specificity. Based on the clinician's dictated response ("pain while walking, 6/10; paronychia left great toe"), the system maps to lateralized, specific ICD-10 codes: M79.675 for left toe pain and L03.032 for left toe cellulitis. It avoids unspecified codes (M79.673) when laterality data is available, reducing audit vulnerability per CMS ICD-10 specificity guidelines.

Step 5 — Nail count as discrete structured data. The count "8" is captured not as free text but as a structured field that directly maps to CPT 11721 selection logic. This creates an auditable chain: 8 nails documented → 11721 selected → documentation supports code.

Step 6 — Antifungal treatment attestation. The system confirms that the medication list or plan includes an antifungal agent (or documents a contraindication). In this scenario, "ciclopirox topical applied" satisfies the LCD requirement without requiring systemic therapy.

The Result: A recurrent denial pattern is reversed. The clinician's documentation isn't fabricated—the pain and infection were clinically present but simply went undocumented because nothing in the traditional workflow prompted their capture. Scribing.io doesn't create findings; it ensures that clinically observed findings reach the medical record in LCD-compliant language.

Technical Reference: ICD-10 Documentation Standards

B35.1 — Tinea unguium (onychomycosis); M79.673 — Pain in unspecified foot

Scribing.io ensures these codes reach maximum specificity to prevent denials through three mechanisms: laterality enforcement (prompting right vs. left when anatomic data is available), severity quantification (pain rated on numeric scale), and clinical correlation (linking the pain or infection code directly to the mycotic nail condition in the assessment). Below are the complete documentation standards for each code.

B35.1 — Tinea Unguium (Onychomycosis)

Element

Specification

ICD-10-CM Code

B35.1

Full Descriptor

Tinea unguium

Clinical Synonyms

Onychomycosis, dermatophyte nail infection, fungal nail dystrophy

Chapter

1 — Certain Infectious and Parasitic Diseases (A00–B99)

Block

B35–B49 — Mycoses

Laterality

Not specified in code; must document affected side(s) in narrative

7th Character

Not applicable

Billable

Yes — valid for claim submission

Supported CPT Codes

11720 (1–5 nails), 11721 (6+ nails)

LCD Coverage Requirement

Must pair with documented qualifying symptom (pain/infection) for medical necessity

Documentation Must Include

Affected nail(s) identified by digit and laterality, clinical description of mycotic changes, extent of debridement performed, antifungal treatment or contraindication documented, qualifying symptoms with severity

Common Denial Trigger

Submitting B35.1 without secondary symptom code; missing nail count; frequency <60 days

M79.673 — Pain in Unspecified Foot

Element

Specification

ICD-10-CM Code

M79.673

Full Descriptor

Pain in unspecified foot

Chapter

13 — Diseases of the Musculoskeletal System and Connective Tissue (M00–M99)

Block

M79 — Other and unspecified soft tissue disorders, not elsewhere classified

Specificity Note

Use M79.671 (right) or M79.672 (left) when laterality is documented. Use M79.674/M79.675 for toe-specific pain. Scribing.io auto-selects the most specific available code.

LCD Role

Establishes functional impairment (medical necessity) when paired with B35.1 for nail debridement

Required Documentation

Pain severity (numeric scale), exacerbating activity (walking, shoe wear), relationship to mycotic nail pathology

Audit Vulnerability

Using "unspecified" (M79.673) when laterality data exists in the note invites auditor scrutiny; always lateralize

Specificity Hierarchy Enforced by Scribing.io

When a clinician dictates "patient reports pain in the left great toe while walking," the system applies the following logic cascade:

  1. Detect anatomic site: toe → foot subcategory

  2. Detect laterality: left → left-specific code

  3. Select M79.675 (Pain in left toe[s]) over M79.672 (Pain in left foot) or M79.673 (Pain in unspecified foot)

  4. Flag if dictation contains laterality but selected code does not—prevents specificity downgrade

  5. Attach pain severity (6/10) as structured data supporting the code's clinical validity

LCD-Aware Workflow Implementation: Epic and athena via FHIR

Scribing.io's nail debridement compliance module operates through HL7 FHIR R4 interfaces, meaning it reads from and writes to your existing EHR without requiring a rip-and-replace. The technical architecture:

Integration Component

Function

EHR Systems Supported

FHIR Encounter History Query

Retrieves last CPT 11720/11721 service date for 60-day frequency validation

Epic, athenahealth, eClinicalWorks, NextGen

FHIR MedicationRequest Read

Confirms active antifungal prescription or documents absence

Epic, athenahealth, Cerner (Oracle Health)

Structured Data Write-Back

Writes nail count, pain severity, and infection findings as discrete elements (not free text)

Epic (via SmartForms), athenahealth (via custom fields)

CDS Hooks Alert

Fires real-time alert when B35.1 is selected without qualifying secondary diagnosis

Any CDS Hooks-compliant EHR

Claim Pre-Submission Validator

Checks frequency, nail count, ICD pairing, and symptom documentation before claim generation

Integrated clearinghouse or EHR billing module

This architecture means the compliance logic runs inside the clinical workflow—not as a retrospective audit finding that arrives 90 days post-service. The intervention happens at the microphone, during dictation, when clinical detail is still fresh and correction costs zero additional time.

Audit Defense: The 6-Element Documentation Checklist

When a MAC requests records for a CPT 11721 + B35.1 claim, auditors evaluate six discrete elements. If any element is missing, the claim is vulnerable to recoupment. Scribing.io's compliance attestation confirms all six before the note is signed:

  1. Nail count as discrete data — "8 nails debrided: digits 1–5 bilateral, plus digits 2–3 right foot" (specific enough to justify 11721 vs. 11720)

  2. Clinical description of mycosis — "Nails exhibit subungual hyperkeratosis, yellow-brown discoloration, onycholysis distally" (visual evidence supporting B35.1)

  3. Qualifying symptom with severity — "Patient reports pain with ambulation rated 6/10, exacerbated by shoe pressure on hypertrophic nail plate" (establishes medical necessity)

  4. Secondary infection documentation (if present) — "Periungual erythema and tenderness at left hallux nail fold consistent with paronychia; no purulent drainage" (supports L03.032)

  5. Antifungal treatment or contraindication — "Ciclopirox 8% topical lacquer applied; oral terbinafine contraindicated due to elevated ALT (documented 2025-11-14)" (satisfies LCD treatment requirement)

  6. Service interval documentation — "Last debridement performed [date] — 62 days prior; within covered frequency" (preempts frequency-based denial)

Each element maps directly to an LCD audit criterion. Missing element #3 alone—qualifying symptom—triggers the "cosmetic" denial that accounts for the majority of B35.1-related claim failures nationwide.

Nail Debridement Workflow: Live in Your EHR Today

See our LCD-aware nail debridement workflow for CPT 11720/11721 that enforces the 60-day frequency edit and auto-captures "pain while walking/secondary infection" so B35.1 claims clear medical-necessity screens—live in Epic and athena via FHIR today.

The operational difference between a coding reference and Scribing.io: coding references tell you what codes exist. Scribing.io ensures the documentation supports the code at the moment of care—before the claim generates, before the denial arrives, before your billing staff spends 45 minutes on an appeal that could have been prevented by a single prompted sentence during dictation.

Three metrics from practices running the nail debridement compliance module:

  • First-pass payment rate for 11721 + B35.1: 94% (vs. 58% baseline without structured prompts)

  • Average documentation time added per encounter: 12 seconds (one prompted response)

  • Annual revenue recovered per full-time DPM: $18,400–$27,600 in previously denied or unbilled debridements

The math is straightforward: a single mycotic nail debridement (11721) reimburses approximately $70–$95 depending on MAC locality. A DPM performing 15–20 debridements per week who prevents even 3 denials weekly recovers $210–$285/week—$10,920–$14,820 annually—from one compliance rule alone. Factor in eliminated appeal labor costs and the ROI exceeds 10:1 against Scribing.io's subscription cost.

This isn't a theoretical improvement. It's a documentation discipline enforced at the point of dictation, built on the anchor truth that payers have made explicit: B35.1 alone is cosmetic. B35.1 plus documented functional impairment is covered. The 12 seconds it takes to say "pain while walking, six out of ten" is the difference between payment and denial. Scribing.io makes sure those 12 seconds never get skipped.

Frequently

asked question

Answers to your asked queries

How does the AI medical scribe work?

Does Scribing.io support ICD-10 and CPT codes?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

How do I get started?

Frequently

asked question

Answers to your asked queries

How does the AI medical scribe work?

Does Scribing.io support ICD-10 and CPT codes?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

How do I get started?

Frequently

asked question

Answers to your asked queries

How does the AI medical scribe work?

Does Scribing.io support ICD-10 and CPT codes?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

How do I get started?

Didn’t find what you’re looking for?
Book a call with our AI experts.

Didn’t find what you’re looking for?
Book a call with our AI experts.

Didn’t find what you’re looking for?
Book a call with our AI experts.