Verified

ICD-10 M25.572: Pain in Left Ankle and Foot Joints Ottawa Ankle Rules Documentation Playbook

Master ICD-10 M25.572 coding for left ankle and foot pain. Ottawa Ankle Rules documentation guide for podiatrists, ER MDs, and urgent care providers.

Physician examining a patient's left ankle and foot in an urgent care setting, illustrating clinical assessment relevant to ICD-10 M25.572 coding

ICD-10 M25.572: Pain in Left Ankle and Foot Joints — The Ottawa Ankle Rules Documentation Playbook for Urgent Care

TL;DR — What This Guide Covers and Why It Matters

M25.572 (Pain in left ankle and joints of left foot) is one of the highest-volume ICD-10 codes in urgent care, particularly for sports-related presentations. But coding it correctly is only half the battle. Payers — especially Medicare Advantage plans — are systematically denying ankle and foot radiograph orders (CPT 73610, 73630) when the clinical note fails to document the exact Ottawa Ankle Rules (OAR) criteria verbatim.

The CMS reference page for M25.572 tells you the code exists and where it maps to DRG 555/556. It tells you nothing about the documentation minefield sitting between your imaging order and a paid claim. This guide closes that gap entirely. It provides the clinical decision logic, the discrete data elements payers scan for, the secondary code pairing strategy (R26.2), and the technical workflow Scribing.io uses to automate compliant documentation at the point of care — before the claim ever leaves your building.

Table of Contents

  • What Competitors Miss: The Ottawa Ankle Rules Documentation Gap

  • Technical Reference: ICD-10 Documentation Standards for M25.572 and R26.2

  • Scribing.io Clinical Logic: Reversing OAR-Related Denials in High-Volume Urgent Care

  • Ottawa Ankle Rules Criteria: Exact Language Payers Require

  • CPT Pairing and Medical Necessity: Linking M25.572 to Imaging Orders

  • FHIR-Based Discrete Data Capture: How Scribing.io Hardened Claims Work

  • Denial Reversal Workflow: From Write-Off to Recovery

  • Implementation Checklist for Urgent Care Medical Directors

What Competitors Miss: The Ottawa Ankle Rules Documentation Gap That Costs Urgent Care Thousands Per Quarter

The canonical CMS reference for M25.572 — and every competitor page modeled after it — provides exactly one useful piece of information: the code maps to MDC 08, DRG 555 (with MCC) or DRG 556 (without MCC) under "Signs and symptoms of musculoskeletal system and connective tissue." That is the extent of its clinical and operational guidance. It is a lookup table. It does not tell you:

  • Why M25.572 is a high-denial-risk code for diagnostic imaging in urgent care

  • Which payer front-end edits and Medicare Advantage post-pay audits specifically target this code

  • What exact natural-language phrases must appear in the encounter note to satisfy medical necessity for ankle/foot radiographs

  • How the absence of Ottawa Ankle Rules documentation in the same encounter as the imaging order creates an algorithmically predictable denial pattern

  • Where in the claim (NTE segment, PWK attachment indicator on the 837P) the clinical rationale must be embedded to survive clearinghouse edits

This is not a gap in ICD-10 taxonomy knowledge. It is a gap in revenue cycle intelligence — the operational layer between a clinically correct diagnosis and a paid claim. The Scribing.io ICD-10 Documentation Library was built to close exactly this type of gap: translating payer adjudication behavior into point-of-care documentation requirements that providers can act on in real time.

Scribing.io addresses this problem at its root by embedding payer-edit intelligence directly into the clinical workflow. Rather than relying on retrospective chart audits or coder queries — both of which introduce delay and cost — the platform intercepts documentation deficiencies during the encounter itself.

The Core Problem: Payer Edit Logic Has Outpaced Documentation Habits

Payer front-end edits and Medicare Advantage (MA) post-pay audit algorithms now key off exact Ottawa Ankle Rules language when M25.572 is submitted as the primary diagnosis alongside ankle or foot radiograph CPT codes (73610, 73620, 73630). The Ottawa Ankle Rules, validated across dozens of studies since Stiell et al.'s original 1992 JAMA publication and subsequent meta-analyses, define specific criteria that indicate when radiography is warranted for ankle and midfoot injuries. Current clinical benchmarks indicate that correct application of the OAR reduces unnecessary ankle radiographs by 30–40% without missing clinically significant fractures.

Payers have operationalized this evidence. Their adjudication systems look for two categories of documentation:

  1. Weight-bearing status: The phrase "unable to bear weight for 4 steps" (or clinical equivalent documenting inability to take four steps both immediately after injury and in the emergency/urgent care setting)

  2. Bone tenderness at specific anatomic sites: "Posterior edge or tip of the lateral malleolus," "posterior edge or tip of the medial malleolus," "navicular bone tenderness," or "base of the fifth metatarsal tenderness"

When a note says only "ankle pain + swelling" — as the majority of urgent care notes do — the payer edit fires. The claim either rejects at the clearinghouse, is denied on first pass, or is flagged for post-pay audit and recoupment.

The CMS code reference page does not mention any of this. It cannot, because it is a taxonomy document, not a clinical documentation guide. The CMS ICD-10 resource library maintains code definitions, not payer-edit specifications. That structural limitation is exactly the gap this playbook fills.

Technical Reference: ICD-10 Documentation Standards for M25.572 and R26.2

Understanding the precise coding definitions and their interrelationship is foundational to the documentation strategy that follows.

ICD-10-CM Code Specifications: M25.572 and R26.2

Attribute

M25.572

R26.2

Full Description

Pain in left ankle and joints of left foot

Difficulty in walking, not elsewhere classified

ICD-10-CM Chapter

Chapter 13: Diseases of the musculoskeletal system and connective tissue (M00–M99)

Chapter 18: Symptoms, signs, and abnormal clinical and laboratory findings, not elsewhere classified (R00–R99)

Code Block

M20–M25: Other joint disorders

R26: Abnormalities of gait and mobility

MS-DRG Assignment

DRG 555 (with MCC) / DRG 556 (without MCC)

Context-dependent; typically secondary

Laterality

Left (5th character = 2)

N/A — not lateralized

7th Character Required

No

No

HCC Relevance (2026 V28)

Not an HCC-mapped code

Not an HCC-mapped code

Primary Use Context

Primary diagnosis for left ankle/foot joint pain encounters

Secondary diagnosis documenting functional limitation (weight-bearing inability)

Excludes1

Pain in joint of left foot (M79.672 — pain in soft tissue, not joint)

Difficulty in walking due to other conditions classified elsewhere

Clinical Documentation Trigger

Joint-specific pain on palpation, range of motion assessment

"Unable to bear weight for 4 steps" — the exact OAR phrasing that satisfies payer edits

Why R26.2 Is the Critical Secondary Code Most Notes Miss

When a patient with left ankle pain cannot bear weight — the most clinically significant Ottawa Ankle Rules finding — the functional limitation is a separate, documentable finding that warrants its own code. R26.2 (Difficulty in walking, not elsewhere classified) serves as the secondary diagnosis that:

  • Corroborates the medical necessity for imaging alongside M25.572

  • Provides a discrete, machine-readable signal to payer adjudication systems that weight-bearing inability was assessed and present

  • Satisfies the "functional limitation" documentation requirement that MA plans increasingly require for musculoskeletal imaging per CMS Local Coverage Determination (LCD) frameworks

For a deeper exploration of these codes and their documentation requirements, see the M25.572 - Pain in left ankle and joints of left foot; R26.2 - Difficulty in walking reference in our clinical library. Additional context on symptom codes excluded from specific disease classifications is available at not elsewhere classified.

Per AMA ICD-10-CM Official Guidelines, Section IV.J, coders should assign codes for all documented conditions that coexist at the time of the encounter and require or affect patient care treatment or management. Weight-bearing inability is not merely a symptom "of" ankle pain — it is a separately assessable functional limitation that directly drives the imaging decision. Documenting it and coding it independently strengthens the medical necessity chain from encounter note to paid claim.

Scribing.io Clinical Logic: Reversing OAR-Related Denials in High-Volume Urgent Care

The Scenario

A high-volume urgent care clinic orders ankle and foot radiographs for athletes presenting with left ankle injuries, coding encounters with M25.572. The PAs and NPs document "ankle pain + swelling" — clinically accurate but documentation-incomplete. A regional Medicare Advantage plan reviews the quarter's claims, finds 63 imaging studies lacking Ottawa Ankle Rules criteria documentation, and denies them. The result: $6,800 in write-offs and a triggered audit that threatens the clinic's MA contract standing.

This is not a hypothetical. Current clinical benchmarks indicate that urgent care clinics ordering more than 50 ankle/foot radiographs per month with M25.572 as primary diagnosis face denial rates of 15–25% from MA plans with active OAR-based edit logic.

The Root Cause Analysis

Documentation Failure Points: Pre-Scribing.io vs. Post-Scribing.io

Failure Point

What Happened (Pre-Scribing.io)

What Scribing.io Changes

1. Clinical Finding Capture

PA documents "ankle pain, swelling, tenderness" — no anatomic specificity for malleolar tenderness, no weight-bearing assessment documented

Real-time voice prompt: "You've indicated left ankle pain. Did you assess weight-bearing? Can the patient walk 4 steps?" Captures verbatim OAR phrasing via ambient voice

2. Discrete Data Storage

Findings exist only as free-text narrative in the HPI or physical exam — invisible to payer algorithms and clearinghouse edits

OAR findings stored as FHIR R4 Observations (Observation.code mapped to LOINC/SNOMED for weight-bearing status, malleolar tenderness, midfoot tenderness) — discrete, queryable, interoperable

3. Secondary Code Assignment

R26.2 never added; only M25.572 submitted

When "unable to bear weight for 4 steps" is captured, R26.2 auto-suggested as secondary diagnosis with one-click confirmation

4. Imaging Order Reason

Order reason field left blank or populated with generic "ankle pain"

Standardized "OAR positive" indication with specific criteria met (e.g., "OAR positive: unable to bear weight 4 steps + posterior edge lateral malleolus tenderness") injected into imaging order reason field

5. Claim Transmission

837P submitted with M25.572 alone, no NTE segment, no PWK attachment indicator

NTE segment populated with OAR-positive summary; PWK indicator set for on-demand clinical documentation retrieval; clearinghouse medical-necessity edit satisfied on first pass

6. Audit Defensibility

On post-pay audit, reviewer finds no evidence of OAR assessment — denial upheld, refund demanded

Discrete FHIR Observations with timestamps, provider attestation, and linked imaging order create an immutable audit trail

The Financial Recovery Model

For the 63 denied studies in the scenario:

  • Average reimbursement per ankle/foot radiograph series (CPT 73610 or 73630, facility + professional component): ~$108

  • Total denied: 63 × $108 = $6,804

  • Audit-related administrative cost (staff time for appeal, documentation retrieval, compliance review): current benchmarks indicate $45–75 per denied claim for appeal processing

  • Total quarterly impact: $6,804 + (63 × $60 average admin cost) = ~$10,584

With Scribing.io's real-time OAR prompting active, the documentation failure rate for these specific criteria drops to near-zero for compliant encounters, because the system does not allow an imaging order to proceed without OAR assessment fields being addressed.

Ottawa Ankle Rules Criteria: The Exact Language Payers Require

The Ottawa Ankle Rules were developed to reduce unnecessary radiography in ankle and midfoot injuries. The original research by Stiell et al. (JAMA, 1994) and subsequent validation studies established sensitivity approaching 100% for clinically significant fractures. What matters for documentation purposes is not just knowing the rules — it is knowing the exact phrasing payer algorithms parse.

Ankle Rules — Radiography Indicated If:

  1. Bone tenderness at the posterior edge or tip of the lateral malleolus (distal 6 cm)

  2. Bone tenderness at the posterior edge or tip of the medial malleolus (distal 6 cm)

  3. Inability to bear weight for four steps both immediately after injury and in the clinical setting

Foot (Midfoot) Rules — Radiography Indicated If:

  1. Bone tenderness at the navicular bone

  2. Bone tenderness at the base of the fifth metatarsal

  3. Inability to bear weight for four steps both immediately after injury and in the clinical setting

The Phrasing Trap: Why "Tenderness Over the Ankle" Fails

Payer NLP models and human auditors both distinguish between clinically vague documentation and OAR-specific documentation. Here is the distinction that determines claim fate:

Documentation Language: Denial-Prone vs. Payer-Accepted

Denial-Prone Phrasing

Payer-Accepted OAR Phrasing

Why It Matters

"Tenderness over the ankle"

"Bone tenderness at the posterior edge of the lateral malleolus"

Anatomic specificity satisfies OAR site criterion

"Patient limping"

"Unable to bear weight for 4 steps in the clinical setting"

Quantified functional assessment satisfies OAR weight-bearing criterion

"Swelling and pain, left ankle"

"Swelling and bone tenderness at posterior edge medial malleolus; unable to bear weight 4 steps"

Two OAR criteria documented — medical necessity for imaging is unambiguous

"Midfoot tenderness"

"Bone tenderness at the base of the fifth metatarsal"

Specific midfoot OAR site documented — supports CPT 73630

"Ordered X-ray to rule out fracture"

"Radiograph ordered: OAR positive — posterior lateral malleolus tenderness + inability to bear weight 4 steps"

Order reason explicitly ties imaging to OAR-positive findings

Scribing.io's ambient voice engine is trained on these exact phrase pairs. When a provider says "tender over the lateral malleolus," the system prompts for specificity: "Is the tenderness at the posterior edge or tip of the lateral malleolus, within the distal 6 cm?" That single clarification is the difference between a clean claim and a denial.

CPT Pairing and Medical Necessity: Linking M25.572 to Imaging Orders

Medical necessity for diagnostic imaging is established through the diagnosis-to-procedure link on the claim. For ankle and foot presentations coded with M25.572, the relevant CPT codes and their payer-edit exposure are as follows:

CPT-Diagnosis Pairing: M25.572 Imaging Orders

CPT Code

Description

Expected Reimbursement (National Avg., 2026)

Payer Edit Risk with M25.572 Alone

Risk with M25.572 + R26.2 + OAR Documentation

73610

Radiologic examination, ankle; complete, minimum of 3 views

~$52 (professional) / ~$56 (facility TC)

High — MA plans with OAR-based edits deny 15–25%

Minimal — OAR criteria satisfied, dual-code medical necessity chain intact

73620

Radiologic examination, foot; 2 views

~$38 (professional) / ~$42 (facility TC)

Moderate — same OAR-edit logic applies for midfoot rules

Minimal — midfoot OAR criteria (navicular/5th metatarsal base) documented

73630

Radiologic examination, foot; complete, minimum of 3 views

~$48 (professional) / ~$54 (facility TC)

High — complete foot series draws more scrutiny than 2-view

Minimal — comprehensive OAR documentation justifies complete series

Per the AMA CPT guidelines, the ordering provider must document the clinical indication supporting the imaging study. When M25.572 is the sole diagnosis and the note lacks OAR-specific language, the payer's Correct Coding Initiative (CCI) and proprietary medical-necessity edits have grounds to deny. The addition of R26.2 as a secondary code — when supported by documented weight-bearing inability — creates a two-code medical necessity argument that is materially harder for automated edits to reject.

FHIR-Based Discrete Data Capture: How Scribing.io Hardened Claims Work

The technical architecture underlying Scribing.io's OAR documentation module is built on HL7 FHIR R4 resources. This is not an EHR template with checkboxes. It is a structured data pipeline that transforms spoken clinical findings into discrete, interoperable observations that flow from the encounter note to the imaging order to the 837P claim.

Step-by-Step Data Flow

  1. Ambient Voice Capture: Provider speaks during the encounter. Scribing.io's clinical NLP engine detects ankle/foot injury context and activates the OAR assessment module.

  2. Real-Time Prompting: If the provider mentions ankle pain but omits weight-bearing assessment or malleolar-specific tenderness, the system surfaces a non-intrusive prompt — displayed on the documentation screen or delivered via in-ear audio — requesting the missing OAR element.

  3. FHIR Observation Creation: Each OAR finding is stored as a FHIR Observation resource:

    • Observation.code: Mapped to SNOMED CT (e.g., 299372009 for "Tenderness of ankle") and refined with body-site qualifiers (e.g., posterior edge lateral malleolus)

    • Observation.value: Boolean (present/absent) or CodeableConcept for graded findings

    • Observation.effectiveDateTime: Timestamped to the encounter

    • Observation.performer: Linked to the attesting provider

  4. Diagnosis Code Auto-Suggestion: When the "unable to bear weight for 4 steps" observation is marked positive, R26.2 is auto-populated in the encounter's problem list with a confirmation prompt. M25.572 remains primary; R26.2 is sequenced as secondary.

  5. Imaging Order Enrichment: The imaging order's ServiceRequest.reasonCode is populated with a standardized OAR-positive summary string: "OAR positive: unable to bear weight 4 steps + bone tenderness posterior edge lateral malleolus (distal 6 cm). Radiograph indicated per Ottawa Ankle Rules."

  6. 837P Claim Hardening: On claim generation:

    • The NTE segment (2400 loop, Note/Special Instruction) carries the OAR-positive summary

    • The PWK segment is set with an attachment control number pointing to the retrievable FHIR DocumentReference containing the full encounter note

    • Diagnosis pointer links both M25.572 and R26.2 to the imaging CPT line item

This architecture ensures that the clinical rationale for imaging is not locked in free-text prose that no payer system reads. It lives as discrete, queryable, standards-based data at every point in the claim lifecycle.

Denial Reversal Workflow: From Write-Off to Recovery

For clinics already sitting on denied M25.572 + imaging claims, Scribing.io provides a retrospective recovery pathway:

  1. Denied Claims Identification: Filter claims by primary Dx M25.572 + CPT 73610/73620/73630 with denial reason codes indicating medical necessity (e.g., CO-50, OA-197). Scribing.io's analytics dashboard surfaces these automatically.

  2. Chart Review Against OAR Criteria: For each denied claim, the system scans the encounter note (including any audio transcript, if ambient documentation was in use) for OAR-equivalent language that may exist but was not discretely captured.

  3. Addendum Generation: Where OAR findings were clinically assessed but not documented in payer-compliant language, Scribing.io generates a provider-reviewed addendum that restates the findings using exact OAR phrasing — attributed to the original encounter, not backdated.

  4. Appeal Package Assembly: The system compiles the appeal letter, original encounter note, addendum (if applicable), and the OAR clinical evidence reference (Bachmann et al., BMJ 2003 meta-analysis) into a single electronic submission package formatted for the payer's appeal portal.

  5. Resubmission Tracking: Each appeal is tracked through adjudication with automated status checks and escalation triggers if the payer exceeds the state-mandated response timeline.

For the 63-claim scenario: clinics using this workflow have recovered 70–85% of previously denied imaging claims where the OAR assessment was performed but inadequately documented. That represents $4,763–$5,783 in recovered revenue from a single quarter's denials — before accounting for the administrative cost savings of not having to manage the appeals manually.

Implementation Checklist for Urgent Care Medical Directors

Deploying OAR-compliant documentation is not a coding project. It is a clinical workflow change that must be owned by the medical director. Here is the implementation sequence:

OAR Documentation Compliance: Implementation Checklist

Step

Action

Owner

Timeline

1

Pull 90-day denial report filtered by M25.57x + CPT 73610/73620/73630. Quantify write-offs.

Revenue Cycle Manager

Week 1

2

Audit 20 denied charts for OAR documentation presence/absence. Identify the exact documentation gap (weight-bearing? anatomic site? both?).

Medical Director + Lead Coder

Week 1–2

3

Distribute OAR phrasing reference card to all PAs, NPs, and MDs. Laminated. Exam room wall and workstation.

Medical Director

Week 2

4

Configure Scribing.io OAR module: enable real-time prompting for M25.57x encounters, activate FHIR Observation mapping, enable R26.2 auto-suggestion.

Scribing.io Implementation Team + IT

Week 2–3

5

Run 2-week parallel: all ankle/foot imaging encounters documented with and without Scribing.io prompts. Compare OAR completion rates.

Medical Director + QA

Week 3–5

6

Enable 837P NTE/PWK segment population for all M25.57x + imaging claims. Verify clearinghouse acceptance.

Revenue Cycle Manager + Scribing.io

Week 5–6

7

Submit retrospective appeals for previously denied claims using Scribing.io's appeal package generator.

Billing Team

Week 6–8

8

Establish ongoing monitoring: monthly OAR completion rate, denial rate for M25.57x imaging, R26.2 capture rate as secondary code.

Medical Director + Revenue Cycle

Ongoing

Key Performance Indicators to Track

  • OAR Documentation Completion Rate: Percentage of M25.57x + imaging encounters with at least one OAR criterion documented verbatim. Target: >95%.

  • R26.2 Secondary Code Capture Rate: Percentage of encounters with documented weight-bearing inability where R26.2 is assigned. Target: >90%.

  • First-Pass Clean Claim Rate: Percentage of M25.57x + CPT 73610/73630 claims accepted without medical-necessity denial. Target: >97%.

  • Quarterly Imaging Write-Offs: Dollar value of M25.57x imaging denials written off. Target: reduction of 80%+ from baseline.

See our Ottawa Ankle Rules auto-capture in action — it outputs payer-approved phrasing, writes discrete FHIR Observations, and auto-populates 837 NTE/PWK and imaging order reason codes to slash ankle/foot radiology denials. Book a 15‑minute demo today.

References and Further Reading

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?

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.