Verified
ICD-10 D22.9 Melanocytic Nevi: Complete Coding & Billing Guide for Surgical Dermatologists
Master ICD-10 D22.9 melanocytic nevi coding with updated 2026 CMS rules, LCD cross-references, and NCCI edits. Essential guide for surgical dermatologists.
Clinical Update — June 2026: This guide has been revised to reflect CMS CY 2026 Physician Fee Schedule final rule updates to benign lesion removal coverage indicators, updated MAC LCD cross-references (L35498 rev. 18, effective 2026-04-01; Novitas L36527 rev. 4), current NCCI PTP edit table v32.2, and ICD-10-CM FY2026 tabular changes affecting the D22.x family. All FHIR integration references have been updated for US Core 7.0 and Epic November 2025 / athenahealth Q1 2026 API releases. If your practice last audited its nevus removal workflow before January 2026, this revision contains materially new compliance guidance.
ICD-10 D22.9 — Melanocytic Nevi: The Definitive Clinical Documentation & Medicare Reimbursement Playbook for Dermatology
D22.9 kills revenue quietly. It does not trigger a flashy compliance alert. It does not generate a letter from the OIG. It simply causes shave removal claims to bounce—silently, predictably, and expensively—because a trailing .9 tells every MAC adjudication engine in the country that your operative note failed to name a body site and failed to prove the removal was not cosmetic. The fix is not a billing seminar. The fix is intercepting the documentation gap during the encounter, in real time, before the note closes. That is precisely what Scribing.io was built to do.
This operations playbook dissects the clinical, coding, and regulatory architecture of melanocytic nevus removals billed under CPT 11300–11313, explains exactly why D22.9 triggers denials under current LCD frameworks, and provides a granular, step-by-step deployment guide for Scribing.io's LCD-aware nevus workflow—including medical-necessity prompting, site-specific ICD-10 mapping, FHIR-linked photo capture, NCCI modifier logic, and ABN fail-safe routing. Every workflow described here is integrated with Epic and athenahealth and deployable within a single sprint cycle. Book a 12-minute demo to see the LCD-aware 11300 workflow live: real-time ICD–CPT validation, necessity attestation prompts ("irritation by clothing" / "visual change"), ABN fail-safe, photo capture via FHIR DocumentReference, and NCCI/modifier guidance integrated to Epic and athena.
Why D22.9 Denials Are an Epidemic in Dermatology Billing
What the LCD Actually Requires—and What It Leaves Dangerously Ambiguous
Scribing.io Clinical Logic: From Denial Scenario to First-Pass Payment
Technical Reference: ICD-10 Documentation Standards for Melanocytic Nevi
The Information-Gain Pillar: What Every Existing D22.9 Resource Misses
NCCI Edits, Modifier Strategy, and E/M Co-Billing for Nevus Encounters
Photo Documentation, FHIR Integration, and MAC Audit Readiness
Implementing the Nevus Workflow: EHR-Specific Deployment Guide
Why D22.9 Denials Are an Epidemic in Dermatology Billing
Unspecified ICD-10 codes remain among the top three denial triggers for Medicare Part B dermatologic surgery claims. D22.9 - Melanocytic nevi is uniquely destructive because it combines two red flags that MAC claim adjudication systems are specifically trained to catch:
Unspecified site. The trailing ".9" tells the payer that the clinician either did not document or did not transmit a body-site location. For a lesion removal, this is functionally equivalent to filing a claim with an incomplete operative note. The CMS ICD-10 coding guidelines mandate coding to the greatest level of specificity supported by the medical record—meaning D22.9 is only appropriate when the site is genuinely unknown, which is clinically absurd in a surgical encounter.
Absent medical necessity signaling. D22.9 describes a morphology (melanocytic nevus) without any qualifier for why removal was clinically indicated. Medicare's statutory exclusion for cosmetic surgery under Social Security Act §1862(a)(1)(A) means the payer's default assumption for a benign nevus removal is cosmetic until proven otherwise.
The downstream impact is measurable and compounding:
Metric | D22.9 (Unspecified) | Site-Specific D22.x + Necessity Documentation |
|---|---|---|
First-pass acceptance rate | Significantly below dermatology specialty average | At or above specialty average |
Average days to payment | Elevated due to resubmission cycles | Standard MAC turnaround (14–21 days) |
Post-pay audit selection risk | High—unspecified codes are audit magnets per OIG Work Plan priorities | Low—complete documentation satisfies medical-record requests on first production |
Patient ABN liability exposure | Frequent—retroactive denials shift cost to patient without proper notice | Minimal—prospective routing to Z41.1 when cosmetic |
Physician time on appeals | 15–30 minutes per denied claim | Near-zero when documentation is contemporaneous |
The core clinical reality: the vast majority of nevus removals do have a legitimate medical indication. The problem is not clinical judgment—it is documentation capture at the moment of care. A dermatologist who says "this waistband lesion bleeds every time the patient bends over" has articulated textbook medical necessity. But if the note reads only "nevus removal" and the code filed is D22.9, that clinical reasoning is invisible to every downstream system—the coder, the clearinghouse, the MAC, and the auditor.
This is the gap that the Scribing.io ICD-10 Documentation Library and its real-time ambient scribe were engineered to close.
What the LCD Actually Requires—and What It Leaves Dangerously Ambiguous
LCD L35498 (WPS, J-05/J-08) is the primary MAC policy governing removal of benign skin lesions for a substantial portion of U.S. Medicare beneficiaries. Novitas L36527 and CGS/Palmetto equivalents track similar logic. Their requirements are simultaneously explicit in principle and treacherously vague in execution detail. Understanding both dimensions is non-negotiable for any dermatology practice billing shave removals to Medicare.
What L35498 Explicitly States
The LCD defines a finite set of conditions under which benign lesion removal transitions from "cosmetic" to "medically necessary." Medicare will consider removal medically necessary when one or more of the following are present and clearly documented in the medical record:
LCD Medical Necessity Criterion | Typical Clinical Language | Documentation Trap |
|---|---|---|
Lesion is irritated or inflamed due to chronic friction or trauma | "Irritation by clothing," "recurrent trauma at belt line," "repeated snagging by waistband" | L35498 explicitly warns that "irritated skin lesion" alone is insufficient. The record must contain the patient's reported symptoms AND the physician's physical examination findings. |
Visual changes suggestive of potential malignancy (ABCD-E criteria) | "Asymmetry noted on exam," "border irregularity," "color variation within lesion," "diameter >6 mm," "evolution over past 6 months" | Merely stating "changed" is ambiguous. The specific change dimension must be named. The AAD ABCDE framework provides the clinical vocabulary MACs expect. |
Recurrent bleeding, infection, or ulceration | "Intermittent bleeding with minor contact," "secondary infection requiring antibiotics" | A single episode may be questioned; pattern documentation strengthens the claim. |
Obstruction of vision, breathing, or other function | "Periorbital lesion impeding superior visual field," "nasal lesion obstructing airway" | Functional impairment must be described, not just anatomic proximity. |
Pruritus unresponsive to medical management | "Persistent pruritus at lesion site despite topical corticosteroid therapy × 4 weeks" | Must document failed conservative treatment to meet the threshold. |
What L35498 Leaves Dangerously Ambiguous
This is where most dermatology practices—and every existing public reference on D22.9—fall critically short. The LCD establishes what to document but offers almost no guidance on how to operationalize that documentation within a modern EHR workflow:
ICD-10 specificity expectations. L35498 does not explicitly state that D22.9 will be denied, but the ICD-10-CM Official Coding Guidelines instruction to code "to the greatest level of accuracy and highest level of digit completeness" means that filing D22.9 when the operative note names "left trunk" (which maps to D22.5) is a coding compliance failure independent of the LCD.
Photo documentation standards. Multiple MACs increasingly expect or request pre-procedure clinical photographs during audit. L35498 references documentation requirements but does not specify photo format, storage, or linkage protocols.
Concurrent procedure logic. When a diagnostic biopsy (11102) is performed on a separate suspicious lesion during the same encounter as a shave removal, NCCI edits apply. L35498 does not map modifier pathways.
ABN workflow for cosmetic determinations. The LCD states the physician must notify the patient and obtain signed acceptance of liability via ABN (CMS-R-131), but provides no procedural template for integrating this into real-time clinical flow.
These gaps create a documentation environment where well-intentioned clinicians routinely produce records that fail at the adjudication layer—not because the medicine was wrong, but because the documentation architecture was incomplete.
Scribing.io Clinical Logic: From Denial Scenario to First-Pass Payment
The Scenario: A 67-year-old Medicare patient presents with a waistband-level nevus repeatedly snagged by clothing. The dermatologist performs a shave removal but documents only "nevus removal," bills 11300 with D22.9, and the claim is denied for cosmetic intent/unspecified site.
This scenario is not hypothetical—it is the single most common denial pattern in benign lesion dermatologic surgery for Medicare patients. The anchor truth: for Medicare reimbursement of 11300 (Shave Removal), the documentation must establish "irritation by clothing" or "visual changes" to distinguish D22.9 as a medical removal rather than cosmetic. Below is the step-by-step comparison.
Without Scribing.io: The Denial Pathway
Step | What Happens | Failure Point |
|---|---|---|
1. Patient encounter | Clinician examines lesion, decides on shave removal | — |
2. Verbal clinical reasoning | Clinician thinks or says aloud "this is getting caught on clothing" | Reasoning exists in the room but is not captured in the note |
3. Documentation | Note reads: "Nevus removal, shave technique" | No medical necessity language. No site specificity. No lesion size. |
4. Coding | Coder assigns 11300 + D22.9 | D22.9 = unspecified site. No necessity attestation attached. |
5. Claim submission | Claim transmitted to MAC | Claim auto-flagged: benign nevus + unspecified site + no documented necessity |
6. Adjudication | Denied — cosmetic intent presumed | Practice must appeal, resubmit, or absorb the loss |
7. Post-denial cascade | Staff spends 15–30 min on appeal; patient may receive unexpected bill; audit trail created | Revenue delay, patient dissatisfaction, compliance exposure |
With Scribing.io Active: The First-Pass Payment Pathway
Step | What Scribing.io Does | Clinical & Billing Outcome |
|---|---|---|
1. Ambient listening activates | Scribing.io's AI scribe begins capturing conversational context at encounter start | Full verbal exchange preserved as structured data substrate |
2. Body-site mapping | Clinician says "nevus at the waistband area." Scribing.io maps verbal body site → trunk | ICD-10 selector pre-populated: D22.5 (melanocytic nevi of trunk) instead of D22.9 |
3. LCD-aware medical necessity prompting | Rules engine detects: benign nevus + shave removal intent + no documented necessity language yet captured. It prompts: "Document medical necessity: irritation by clothing with intermittent bleeding? Visual change?" | Clinician verbalizes: "Yes — irritation by clothing, patient reports intermittent bleeding when snagged, and I note asymmetry on dermoscopy" |
4. Pre-op measurement capture | Clinician states lesion size: 6 mm. Engine binds to CPT selector (11300 = ≤0.5 cm) and validates size–code concordance | CPT–lesion size concordance verified. No upcoding risk. No downcoding loss. |
5. Photo capture & FHIR linkage | Pre- and post-procedure photos captured via integrated media module. Stored as FHIR DocumentReference resources with encounter linkage | Photos audit-ready and retrievable by MAC on first request |
6. Medical necessity attestation auto-generation | Scribing.io inserts structured attestation: "Lesion removed for medical necessity: chronic irritation by clothing at waistband with recurrent bleeding episodes; dermoscopic asymmetry (ABCD-E: A positive). This removal is not cosmetic." | L35498 documentation threshold satisfied within the encounter note |
7. Concurrent biopsy detection | If a diagnostic biopsy (11102) on a different lesion is also performed, the engine detects the NCCI pair, verifies distinct anatomic sites, and recommends modifier XS (Separate Structure) on the biopsy line | Both procedures paid; no bundling denial |
8. Cosmetic fail-safe (ABN routing) | If only cosmetic descriptors are present ("patient doesn't like how it looks"), the engine halts the medical billing pathway, triggers ABN (CMS-R-131) workflow, and suggests Z41.1 instead of D22.x | No improper billing for cosmetic services; patient informed prospectively |
9. Final code set transmitted | CPT 11300 + ICD-10 D22.5 + medical necessity attestation + photo documentation | Claim paid on first pass. No ABN misstep. No post-pay audit risk. |
The Logic Breakdown: Why Each Step Prevents a Specific Denial Vector
Mapping the clinical logic to denial prevention vectors:
Step 2 (Body-site mapping) eliminates Denial Reason Code 4 (invalid/incomplete diagnosis). D22.5 carries the anatomic specificity that D22.9 lacks. The MAC's auto-adjudication engine no longer flags for "unspecified site."
Step 3 (Necessity prompting) directly addresses the cosmetic exclusion. The phrases "irritation by clothing" and "intermittent bleeding" are exact LCD-listed medical necessity criteria. Capturing them in the clinician's own words, in real time, produces an unassailable medical record.
Step 4 (Size capture) prevents CPT–size mismatch, a secondary audit trigger identified in the OIG's dermatology-focused reviews.
Step 5 (Photo linkage) satisfies the increasingly common MAC request for visual corroboration during pre- and post-pay audit, per documentation standards outlined in multiple MAC provider education articles.
Step 6 (Attestation) creates a machine-readable and human-readable necessity statement that travels with the claim through the clearinghouse and into the MAC's document management system.
Step 7 (NCCI/modifier logic) prevents the most common same-session bundling error in dermatology: a biopsy (11102) denied as inclusive to a shave removal (11300) when performed on a different lesion. Modifier XS, per AMA CPT guidelines, documents the distinct anatomic site.
Step 8 (ABN fail-safe) prevents the compliance violation that occurs when a cosmetic removal is billed to Medicare without an ABN—a scenario that exposes the practice to both repayment demands and civil monetary penalties.
Technical Reference: ICD-10 Documentation Standards for Melanocytic Nevi
The D22 code family (Melanocytic nevi) is organized by anatomic site. Filing D22.9 - Melanocytic nevi when the operative note identifies the lesion site is a coding error, not a coding choice. Below is the complete D22.x mapping that Scribing.io's ICD-10 engine enforces in real time:
ICD-10-CM Code | Description | When to Use |
|---|---|---|
D22.0 | Melanocytic nevi of lip | Lesion documented on lip (vermilion or cutaneous) |
D22.1x | Melanocytic nevi of eyelid, including canthus | Laterality required (.11 right, .12 left) |
D22.2x | Melanocytic nevi of ear and external auricular canal | Laterality required |
D22.30–D22.39 | Melanocytic nevi of other and unspecified parts of face | Nose, cheek, forehead, chin, temple, etc. |
D22.4 | Melanocytic nevi of scalp and neck | Posterior neck, anterior neck, scalp vertex, etc. |
D22.5 | Melanocytic nevi of trunk | Chest, back, abdomen, waistline, flank, groin fold. This is the correct code for the scenario patient. |
D22.6x | Melanocytic nevi of upper limb, including shoulder | Laterality required |
D22.7x | Melanocytic nevi of lower limb, including hip | Laterality required |
D22.9 | Melanocytic nevi, unspecified | Only when the anatomic site is genuinely undeterminable from the medical record—a scenario that should never occur in a surgical encounter |
How Scribing.io Ensures Maximum Specificity
Scribing.io's ICD-10 engine operates on a simple rule hierarchy that prevents D22.9 from reaching the claim:
Verbal site extraction: The ambient scribe parses clinician and patient language for anatomic identifiers ("waistband," "belt line," "lower back," "shoulder"). These are mapped against a dermatology-specific body-site ontology to the most specific D22.x code.
Hard block on D22.9 when site is documented: If the encounter note contains any body-site reference, D22.9 is blocked from the code picker. The system surfaces the correct site-specific code and requires clinician confirmation.
Cosmetic routing to Z41.1: If medical necessity criteria are absent after prompting and the clinician confirms cosmetic intent, the system switches the primary diagnosis to unspecified; Z41.1 - Encounter for cosmetic surgery, activates the ABN workflow, and flags the encounter for patient self-pay billing. This protects the practice from filing a medically unjustified claim.
Laterality enforcement: For D22.1x, D22.2x, D22.6x, and D22.7x, the system requires laterality documentation. Missing laterality triggers a prompt before note closure.
The Information-Gain Pillar: What Every Existing D22.9 Resource Misses
A search for "D22.9 melanocytic nevi" returns dozens of pages that define the code and list its description. None of them address the operational problems that actually cause denials. Here is what this playbook covers that no other published resource does:
1. The Dual-Gate Problem
Existing resources treat site specificity and medical necessity as separate issues. They are not. They are simultaneous gates that must both be cleared on the same claim line. A claim with D22.5 but no necessity language will be denied for cosmetic presumption. A claim with perfect necessity documentation but D22.9 will be denied for unspecified site. Scribing.io addresses both in a single pass because they are validated against the same encounter data.
2. The Attestation Gap
No existing D22.9 reference explains that L35498 requires both the patient's subjective complaint and the physician's objective findings. "Patient says it catches on clothing" without a physical exam finding (e.g., "erythema at base consistent with chronic friction") is documentarily incomplete. Scribing.io's prompt structure is designed to capture both dimensions: it asks for the patient's reported symptom and the clinician's examination finding.
3. The Photo Documentation Vacuum
Published literature from JAMA Dermatology and MAC provider education bulletins increasingly emphasize photographic evidence as a component of complete lesion documentation. Yet no existing D22.9 coding resource addresses how to technically store, link, and retrieve photos in a manner that satisfies both the EHR audit trail and MAC record-request workflows. Scribing.io's FHIR DocumentReference approach (detailed in the Photo Documentation section) solves this at the API level.
4. The ABN Timing Problem
CMS requires the ABN to be presented before the service is rendered. A retroactive ABN—presented after denial—is invalid per CMS ABN instructions. When a clinician determines mid-encounter that a removal is cosmetic, the ABN must be generated, presented, and signed before the shave instrument touches the lesion. Scribing.io's real-time cosmetic detection triggers this workflow prospectively, not retrospectively.
NCCI Edits, Modifier Strategy, and E/M Co-Billing for Nevus Encounters
Dermatology nevus encounters frequently involve multiple procedures—a shave removal on one lesion, a diagnostic biopsy on another, and an E/M service documenting the overall skin examination. Each combination has NCCI implications:
Procedure Combination | NCCI Edit Status (v32.2) | Modifier Required | Scribing.io Action |
|---|---|---|---|
11300 (shave removal) + 11102 (tangential biopsy), different lesions | Column 1/Column 2 pair with modifier indicator "1" (modifier allowed) | XS (Separate Structure) on 11102 | Engine verifies distinct anatomic sites from documentation, applies XS automatically, flags if sites overlap |
11300 (shave removal) + 11102 (tangential biopsy), same lesion | Bundled—biopsy is inherent to the shave removal per AMA CPT guidelines | No modifier—bill 11300 only | Engine detects same-site overlap, blocks 11102, alerts clinician: "Biopsy is inclusive to shave removal on same lesion" |
11300 + E/M (99212–99215), separately identifiable service | Modifier indicator "1" | Modifier 25 on the E/M | Engine evaluates whether E/M documentation supports a separately identifiable service beyond the pre-procedure assessment. If documentation is thin, it prompts for additional clinical detail before allowing modifier 25. |
Multiple shave removals, different sites | No NCCI conflict for distinct CPT codes (11300–11313 by site group) | None required if CPT codes differ; modifier 59 or XS if same CPT billed twice for different anatomic areas | Engine maps each lesion to its distinct site, assigns appropriate codes, appends modifiers only when necessary |
A critical nuance that competitors' documentation tools miss: modifier XS is preferred over modifier 59 for Medicare claims as of CMS's ongoing specificity initiative. Scribing.io defaults to XS for distinct-structure scenarios and only falls back to 59 when the X-modifier subset does not apply. This aligns with the NCCI policy manual recommendation for maximum modifier specificity.
Photo Documentation, FHIR Integration, and MAC Audit Readiness
Clinical photographs are rapidly transitioning from "nice to have" to "expected on audit" for benign lesion removals. Multiple MAC Additional Documentation Request (ADR) letters now specifically request pre-procedure images. Without them, practices defending a shave removal claim during post-pay audit are relying entirely on text documentation—a defensible but weaker position.
Scribing.io's FHIR DocumentReference Architecture
Photos captured through Scribing.io are stored and linked using the HL7 FHIR US Core DocumentReference resource, ensuring interoperability and audit traceability:
FHIR Element | Value Populated by Scribing.io | Clinical Purpose |
|---|---|---|
DocumentReference.type | LOINC 72170-4 (Photographic image) | Classifies the attachment as a clinical photograph |
DocumentReference.context.encounter | Linked to the specific encounter ID | Binds photo to the exact date-of-service and procedure |
DocumentReference.context.period | Timestamp: pre-procedure vs. post-procedure | Establishes temporal sequence for audit reviewers |
DocumentReference.content.attachment | JPEG/PNG binary with SHA-256 hash | Tamper-evident storage satisfies integrity requirements |
DocumentReference.description | "Pre-procedure: 6 mm melanocytic nevus, trunk (waistband), with erythematous base" | Human-readable caption for audit reviewers |
EHR-Specific Storage
Epic: Photos are written to the Media tab via Epic's FHIR R4 API and linked to the encounter through SmartData Elements (SDEs) for lesion size (numeric) and lesion site (coded value). The SDE mapping ensures that discrete data used for coding (D22.5, 6 mm) matches the visual evidence in the photograph.
athenahealth: Photos are attached at the encounter level via athena's Clinical Document API. Encounter-level attachments are retrievable through the athena document viewer and exportable for ADR responses. Lesion size and site are captured as structured clinical fields in the encounter note.
This architecture means that when a MAC issues an ADR for a D22.5/11300 claim, the practice can produce—within minutes—the encounter note, the medical necessity attestation, and time-stamped pre/post photographs, all linked to a single encounter ID. That level of documentation completeness resolves the vast majority of audits at the first response level.
Implementing the Nevus Workflow: EHR-Specific Deployment Guide
Deployment of Scribing.io's LCD-aware nevus workflow follows a phased approach tailored to each EHR platform. Total implementation time is typically measured in days, not months.
Phase 1: Configuration (Days 1–3)
Task | Epic | athenahealth |
|---|---|---|
FHIR API connection established | Epic App Orchard / connection hub registration; SMART on FHIR OAuth2 credentials provisioned | athena API key provisioned via Marketplace partner program |
SmartData Elements / structured fields configured | Lesion size (numeric SDE), lesion site (coded SDE mapped to D22.x), medical necessity attestation (text SDE) | Custom encounter fields for lesion size, site, and necessity attestation |
LCD rule set loaded | L35498 (WPS), L36527 (Novitas), and MAC-equivalent necessity criteria pre-configured. Practice selects applicable MAC jurisdiction. | |
Photo capture module enabled | Media tab write access verified; DocumentReference FHIR resource tested | Clinical Document API attachment endpoint tested |
Phase 2: Clinical Calibration (Days 4–7)
Clinician training: 15-minute per-provider orientation on the prompt workflow. Focus: understanding that the system will ask for necessity language during the encounter, not after. Clinicians are trained to respond verbally—Scribing.io captures and structures the response.
Coding staff alignment: Coders are briefed on the D22.9-to-D22.x auto-mapping logic so they understand why the system blocks D22.9 when site documentation exists.
ABN template configuration: Practice-specific ABN language for cosmetic nevus removal is loaded into the fail-safe module. Includes state-specific disclosure requirements where applicable.
Phase 3: Go-Live and Monitoring (Day 8+)
Shadow mode (optional): Scribing.io runs in parallel with existing workflow for 3–5 days, generating recommendations without altering the note, to validate accuracy.
Active mode: Prompts, code mapping, attestation insertion, and photo capture are live.
Monitoring dashboard: Tracks D22.9 usage (target: 0% for surgical encounters), first-pass acceptance rate for 11300–11313, modifier XS/25 application rate, and ABN trigger frequency.
Expected Outcomes at 90 Days
KPI | Baseline (Pre-Scribing.io) | Target (90-Day Post-Deployment) |
|---|---|---|
D22.9 usage rate on surgical claims | Variable; often significant minority of nevus claims | <1% (only genuinely unspecifiable cases) |
11300–11313 first-pass acceptance (Medicare) | Below specialty benchmarks for practices with high D22.9 usage | At or above specialty clean-claim benchmarks |
Medical necessity attestation present on benign removal notes | Inconsistent | 100% |
Photo documentation linked to encounter | Rare or unlinked | ≥95% of surgical encounters |
ABN compliance for cosmetic removals | Inconsistent—often retrospective | 100% prospective |
D22.9 is not an unsolvable problem. It is an unaddressed problem—one that persists because the documentation gap occurs in the 90 seconds between clinical decision and note closure, and no legacy EHR workflow is designed to intercept it. Scribing.io is. Book a 12-minute demo to see the LCD-aware 11300 workflow in your own EHR environment: real-time ICD–CPT validation, necessity attestation prompts, ABN fail-safe, FHIR photo capture, and NCCI/modifier guidance—integrated to Epic and athena, operational in days.
