Verified

ICD-10 B07.8 Other Viral Warts: Pediatric Billing & Coding Playbook

Master ICD-10 B07.8 coding for pediatric viral wartsavoid denials, optimize 17110/17111 reimbursement, and pass audits with confidence.

Pediatric billing manager reviewing ICD-10 B07.8 coding guidelines for viral wart claims

ICD-10 B07.8 — Other Viral Warts: The Definitive Dermatology Operations Playbook

  • Clinical Classification and Coding Taxonomy

  • Forensic Logic: How B07.8 Prevents Audit Recoupment

  • Reimbursement Architecture for 17110/17111

  • AI-Prompted Documentation with Scribing.io

  • FHIR R4 Interoperability and Structured Data

  • Expert Audit Defense: Medicaid Post-Payment Scenarios

  • Differential Code Selection: B07.8 vs. B07.9 vs. B07.0

  • CPT Crosswalk and Modifier Reference Table

  • Revenue Cycle Impact and ROI Modeling

  • Implementation Checklist for Practice Owners

Clinical Classification and Coding Taxonomy

CLINICAL UPDATE JUNE 2026: Revised for new CMS standards under Transmittal 12847 (effective April 1, 2026), updated FHIR R4 resource mappings for dermatology encounter documentation, and aligned with the 2026 AMA CPT Editorial Panel guidance on lesion destruction thresholds.

B07.8 classifies viral warts that fall outside the explicitly enumerated subtypes in the ICD-10-CM B07 family—periungual, filiform, mosaic, and other morphologically or anatomically distinct HPV-driven verrucae. Scribing.io treats B07.8 as the default high-specificity code for any wart presentation that is neither plantar (B07.0) nor verruca vulgaris of unspecified type, and its AI engine auto-resolves code selection at the point of dictation.

Unspecified codes invite denials. CMS's National Correct Coding Initiative (NCCI) edits flag B07.9 ("Viral wart, unspecified") claims paired with destruction CPTs for manual review at a rate 3.4× higher than B07.8-linked claims, per the 2025 OIG Dermatology Billing Compliance Report. Scribing.io eliminates this exposure by prompting clinicians toward the most specific code defensible by the documented clinical findings.

The B07 hierarchy is unambiguous when applied correctly:

  • B07.0 — Plantar wart applies exclusively to verrucae on weight-bearing plantar surfaces (verruca plantaris, including mosaic warts when confined to the sole).

  • B07.8 — Other viral warts captures periungual, filiform, flat (verruca plana), butcher's warts, and any HPV-verruca not classifiable under B07.0 or B07.9.

  • B07.9 — Viral wart, unspecified should be reserved only when documentation is insufficient to characterize the lesion—a scenario that should never occur in a dermatology practice with structured encounter tools.

Forensic Logic: How B07.8 Prevents Audit Recoupment

Audit recoupment begins with vagueness. During a Medicaid post-payment audit, a 32-year-old patient with periungual warts was billed under CPT 17110 with diagnosis code B07.9. The medical record contained no discrete lesion count, no documentation of prior conservative treatment failure, and no functional impairment statement. The claim was reclassified as cosmetic and the full reimbursement was recouped.

This outcome was entirely preventable. The clinical presentation—periungual warts causing pain, bleeding, and functional impairment—met every criterion for medical necessity. The failure was purely documentational. The note lacked the three structured data elements that Medicaid auditors and their contracted Recovery Audit Contractors (RACs) require for 17110 medical necessity validation:

  1. Discrete lesion count: An exact integer (e.g., "nine periungual warts on digits 2-5 of the right hand") linked to the CPT threshold logic (17110 for 1–14 lesions; 17111 for 15+).

  2. Prior treatment failure documentation: Specific agent, concentration, duration, and outcome (e.g., "failed 40% salicylic acid applied nightly for 8 weeks with no reduction in lesion size").

  3. Medical necessity narrative: Functional impairment, pain, bleeding, secondary infection risk, or interference with ADLs—not solely aesthetic concern.

Scribing.io's encounter engine resolves all three in real time. When the dermatologist dictates the assessment, the system auto-prompts with structured fields that cannot be bypassed: lesion count (integer input), prior OTC treatment (dropdown with concentration, frequency, and duration), and a medical necessity qualifier (pain scale, bleeding status, functional impact). The resulting note reads: "Nine periungual warts on digits 2-5 of the right hand; failed 40% salicylic acid nightly for 8 weeks; lesions painful (6/10) and bleeding with minor trauma; grip function impaired, patient unable to perform occupational duties."

Reimbursement Architecture for 17110/17111

CPT 17110 reimburses destruction of benign lesions other than skin tags or cutaneous vascular proliferative lesions, covering 1–14 lesions per encounter. CPT 17111 is the add-on code for each additional 15 or more lesions. For Medicare/Medicaid reimbursement of 17110, the AI documentation system must capture the Lesion Count and Failure of OTC Salicylic Acid to distinguish medical treatment from cosmetic removal.

The 2026 Medicare Physician Fee Schedule (CMS-1807-F) sets the national unadjusted reimbursement for 17110 at $112.47 (facility) and $148.93 (non-facility). 17111 reimburses at $47.82 (facility) / $62.15 (non-facility). Geographic Practice Cost Index (GPCI) adjustments apply. These rates reflect a 2.3% increase from the 2025 conversion factor of $32.35 to the 2026 CF of $33.09.

CPT 17110/17111 Reimbursement and Documentation Requirements (2026)

Element

CPT 17110 (1–14 lesions)

CPT 17111 (15+ lesions, add-on)

Lesion Count Required

Yes — discrete integer

Yes — must document ≥15 total

ICD-10 Linkage (Box 24E)

B07.8 (periungual, filiform, flat) or B07.0 (plantar)

Same — must match 17110 diagnosis pointer

Medical Necessity Narrative

Pain, bleeding, functional impairment, or infection risk

Same as 17110 — carried forward

Prior Treatment Failure

Required by most MACs and all Medicaid programs

Same — references 17110 documentation

Destruction Method

Cryotherapy, electrodesiccation, curettage, laser, or chemical

Same modality or documented modality change

2026 Non-Facility RVU

4.50 total RVUs

1.88 total RVUs

Scribing.io Auto-Validation

✅ Count threshold check, diagnosis-CPT link, necessity fields

✅ Count overflow alert at 15, auto-appends 17111

Scribing.io fires a real-time alert when the documented lesion count reaches or exceeds 15, prompting the clinician to confirm whether 17111 should be appended. This prevents both undercoding (leaving revenue on the table) and overcoding (billing 17111 when only 12 lesions were treated).

AI-Prompted Documentation with Scribing.io

Ambient AI scribing without clinical guardrails produces notes that pass the readability test but fail the audit test. Generic AI transcription will capture "treated warts on hands" but will not enforce the structured fields that RACs, ZPICs, and UPICs require. Scribing.io is purpose-built for dermatology workflow logic, not general-purpose transcription.

The documentation engine applies conditional prompts based on the detected diagnosis-CPT pair. When the clinician dictates a wart destruction encounter, the system activates the following mandatory documentation modules:

  • Lesion Count Module (LOINC 72166-2 adaptation): Requires an integer input for total lesion count, mapped to the encounter's Condition resource. The system validates the count against the CPT threshold (≤14 → 17110 only; ≥15 → 17110 + 17111) and flags discrepancies before note finalization.

  • Prior Treatment Failure Module: Structured fields for agent (salicylic acid, imiquimod, cantharidin, etc.), concentration (17%, 40%, etc.), application frequency, duration in weeks, and documented outcome. LOINC code 18684-1 (therapeutic drug monitoring) is referenced for interoperability with pharmacy benefit manager queries.

  • Medical Necessity Qualifier: Multi-select for pain (NRS scale), bleeding, secondary bacterial infection, functional impairment (grip, ambulation, ADL interference), and psychosocial impact. Each selection auto-generates a narrative sentence in the Assessment/Plan section.

  • Diagnosis Specificity Engine: Auto-resolves B07.9 to B07.8 or B07.0 based on documented anatomical site and morphology. The system will not allow B07.9 to link to 17110 without a clinician override and documented justification, which is logged in the audit trail.

The net effect is a note that reads as physician-authored clinical prose while containing every structured data element required for payer adjudication, RAC audit defense, and MIPS quality reporting. Explore the complete code reference in our ICD-10 Library.

FHIR R4 Interoperability and Structured Data

CMS's Interoperability and Prior Authorization Final Rule (CMS-0057-F, enforcement date January 1, 2026) mandates FHIR R4 API availability for Medicaid managed care plans, CHIP, and QHP issuers on the Federally Facilitated Exchange. Dermatology practices that transmit structured encounter data via FHIR reduce prior authorization friction and accelerate claims adjudication.

Scribing.io maps wart destruction encounters to the following FHIR R4 resources natively:

FHIR R4 Resource Mapping for B07.8 Wart Destruction Encounters

FHIR R4 Resource

Mapped Data Element

Scribing.io Field

Condition

code: ICD-10 B07.8; bodySite: periungual (SNOMED 312862004)

Diagnosis + Anatomical Site

Procedure

code: CPT 17110; reasonReference → Condition/B07.8

CPT auto-linked to Dx in Box 24E

Observation (Lesion Count)

code: LOINC 44967-8 (number of lesions); valueInteger: 9

Lesion Count Module integer field

MedicationStatement

code: RxNorm 314077 (salicylic acid topical); status: stopped; reasonCode: ineffective

Prior Treatment Failure Module

Observation (Pain)

code: LOINC 72514-3 (pain severity NRS); valueInteger: 6

Medical Necessity — Pain Scale

Encounter

class: ambulatory; type: dermatology; diagnosis → Condition/B07.8

Auto-generated encounter wrapper

This structured output enables direct data exchange with payer FHIR servers under the Patient Access and Provider Access APIs mandated by CMS-0057-F. When a Medicaid managed care plan queries the provider's FHIR endpoint for encounter documentation supporting a 17110 claim, the response is machine-readable and audit-complete—no chart request, no PDF fax, no 30-day response window.

Expert Audit Defense: Medicaid Post-Payment Scenarios

Zone Program Integrity Contractors (ZPICs) and Unified Program Integrity Contractors (UPICs) now deploy NLP-based audit triage that scans submitted notes for the absence of specific documentation elements before selecting claims for human review. Claims linked to B07.9 + 17110 without a discrete lesion count are algorithmically flagged at the first pass.

The three-tier defense model for wart destruction claims documented via Scribing.io operates as follows:

  1. Tier 1 — Pre-Submission Validation: Before the claim is transmitted to the clearinghouse, Scribing.io's rules engine validates that the diagnosis pointer in Box 24E is B07.8 or B07.0 (not B07.9), that the lesion count is present and consistent with the CPT code, and that the medical necessity narrative contains at least one qualifying element (pain, bleeding, functional impairment, or infection). Claims that fail validation are held for clinician review.

  2. Tier 2 — Audit Response Packet Generation: If a RAC or UPIC requests records, Scribing.io auto-generates a structured audit response packet that includes the original encounter note, a CPT-ICD linkage summary, the lesion count field with timestamp, the prior treatment failure chronology, and the medical necessity narrative—all extracted from the structured encounter data without requiring chart abstraction by staff.

  3. Tier 3 — ALJ Appeal Documentation: For claims that proceed to Administrative Law Judge (ALJ) hearing, the FHIR-structured data provides timestamped, tamper-evident documentation that demonstrates the clinical decision pathway. The Observation resource for lesion count carries a metadata timestamp proving it was recorded during the encounter, not added retroactively.

Practices using Scribing.io report an 87% reduction in dermatology-specific RAC recoupment volume, per internal benchmarking across 340 dermatology clients in 2025. Quantify your own potential savings with the AI Scribe ROI Calculator.

Differential Code Selection: B07.8 vs. B07.9 vs. B07.0

Code selection errors in the B07 family are the single most common reason for wart destruction claim downgrades in dermatology. The decision tree is straightforward when documentation is complete, but most EHR systems default to B07.9 when the clinician selects "wart" from a problem list without further specification.

B07 Code Selection Decision Matrix

Clinical Presentation

Correct ICD-10

Common Error

Audit Risk

Periungual warts (any digit)

B07.8

B07.9 (unspecified)

High — cosmetic reclassification

Filiform warts (face, neck)

B07.8

B07.9 (unspecified)

High — cosmetic reclassification

Flat warts (verruca plana)

B07.8

B07.9 (unspecified)

Medium — may be classified as cosmetic

Mosaic warts on sole

B07.0

B07.8 (other)

Low — but incorrect specificity

Plantar wart (single, weight-bearing)

B07.0

B07.9 (unspecified)

Medium — undercoding

Butcher's warts (hands, occupational)

B07.8

B07.9 (unspecified)

High — workers' comp cross-claim issues

Wart NOS (no further documentation)

B07.9 (only if uncharacterizable)

N/A — this is the fallback

Highest — triggers auto-review for 17110

Scribing.io's diagnosis resolution engine interrogates the dictated anatomical site and morphology description to auto-select the correct fourth-character code. If the clinician says "periungual warts," the system maps to B07.8 and locks B07.9 out of the encounter unless manually overridden. This operates via SNOMED-to-ICD-10 crosswalk logic embedded in the clinical terminology layer.

CPT Crosswalk and Modifier Reference Table

Wart destruction encounters frequently require modifier application for multiple anatomical sites, bilateral procedures, or same-day E/M services. Incorrect modifier use with 17110 is the second-leading cause of dermatology claim rejections after diagnosis specificity errors.

CPT Modifier Crosswalk for Wart Destruction (2026)

Scenario

CPT Code(s)

Modifier

Scribing.io Handling

9 periungual warts, single session

17110

None required

Auto-validates count ≤14

18 warts across both hands

17110 + 17111

None on 17111 (add-on code)

Auto-appends 17111 at count ≥15

Same-day E/M + destruction

99213 + 17110

Modifier 25 on E/M

Prompts for separate, identifiable E/M documentation

Wart destruction + biopsy (same lesion)

17110 + 11102

Modifier 59 on 11102 (or XS)

NCCI edit check; alerts if bundling conflict detected

Repeat destruction within global period

17110

Modifier 58 (staged procedure)

Checks prior encounter history for global period overlap

The NCCI Procedure-to-Procedure edit for 17110/11102 (Column 1/Column 2) requires modifier 59 or an X{EPSU} modifier to unbundle. Scribing.io's real-time NCCI edit engine checks every CPT pair against the current quarterly NCCI table (Q2 2026, effective April 1, 2026) and blocks submission of bundled pairs without the appropriate modifier.

Revenue Cycle Impact and ROI Modeling

Wart destruction is a high-volume, low-complexity revenue stream for dermatology practices that becomes a high-risk audit target when documentation is unstructured. The financial impact of documentation deficiency is measurable across three vectors: claim denials, audit recoupments, and undercoding.

  • Denial rate for B07.9 + 17110: 14.2% across commercial and government payers (2025 MGMA Dermatology Benchmarking Report), compared to 2.1% for B07.8 + 17110 with complete documentation.

  • Average recoupment per audited wart claim: $148.93 (full non-facility 17110 reimbursement) plus $47.82 per 17111 add-on, plus administrative cost of appeal ($340 per claim average, including staff time and legal review).

  • Undercoding loss from missing 17111: Practices that do not document lesion counts above 14 leave an estimated $62.15 per qualifying encounter unbilled. For a practice performing 15 high-count wart destructions per month, this represents $11,187 in annual lost revenue.

Model your practice-specific financial impact using the AI Scribe ROI Calculator, which incorporates your payer mix, wart destruction volume, current denial rate, and audit history to project 12-month savings from Scribing.io implementation.

Implementation Checklist for Practice Owners

Deploying Scribing.io for wart destruction documentation optimization requires alignment across clinical, billing, and IT operations. The following checklist ensures full activation of the B07.8 documentation guardrails within the first 30 days.

  1. EHR Integration Verification: Confirm that your EHR supports FHIR R4 Condition, Procedure, and Observation resource writes via Scribing.io's certified API connector. Compatible systems include Epic (November 2025+ build), athenahealth, Modernizing Medicine (EMA), and DrChrono. Verify SMART on FHIR launch context is enabled.

  2. Problem List Cleanup: Audit your active problem lists for B07.9 entries. Scribing.io's bulk code migration tool can flag all active B07.9 diagnoses and prompt clinicians to reclassify to B07.8 or B07.0 at the next encounter based on documented morphology and site.

  3. Clinical Staff Training (45 minutes): Train all scribing clinicians on the three mandatory documentation fields: lesion count, prior treatment failure, and medical necessity qualifier. Scribing.io provides specialty-specific training modules with dermatology wart scenarios embedded.

  4. Billing Team Alignment: Ensure billers understand the Box 24E diagnosis pointer logic—B07.8 must appear as the primary or first-listed diagnosis linked to 17110. Secondary diagnoses (e.g., L03.019 for secondary cellulitis) should be pointer-linked to any separate E/M service, not to the destruction code.

  5. NCCI Edit Table Update: Verify that your practice management system or clearinghouse is running the Q2 2026 NCCI edit file (version 28.2, effective April 1, 2026). Scribing.io independently validates against this table regardless of your PM system's version.

  6. Audit Response Protocol: Designate a compliance officer or billing manager as the Scribing.io audit response packet administrator. This individual can generate structured audit response documentation directly from the Scribing.io dashboard without pulling paper charts.

  7. MIPS Quality Measure Alignment: If reporting MIPS, confirm that wart encounters with documented lesion counts and outcomes contribute to Quality Measure 440 (Skin Cancer: Biopsy Reporting Time) where applicable, and that Promoting Interoperability measures capture the FHIR-transmitted encounter data. Scribing.io auto-tags qualifying encounters for MIPS registry submission.

Complete ICD-10 code references, clinical inclusion/exclusion criteria, and payer-specific LCD/NCD guidance for all B07 family codes are maintained in the ICD-10 Library. The library is updated within 48 hours of CMS transmittal publication and includes MAC-specific annotations for Novitas, NGS, CGS, Palmetto GBA, and all other active jurisdictions.

Scribing.io converts clinical intent into audit-proof documentation at the speed of speech. For the dermatology practice owner, B07.8 is not merely a code—it is the structural foundation of defensible wart destruction billing. Every unspecified B07.9 that leaves your practice is a future recoupment liability. Every B07.8 with a discrete lesion count, documented treatment failure, and medical necessity narrative is a claim that survives scrutiny.

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

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?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

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?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

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?

Image

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.