Clinical Update — June 2026: This guide has been revised to reflect the CMS FY2026 OPPS final rule updates to musculoskeletal prior authorization requirements, the Da Vinci PAS Implementation Guide STU 2.1.0 ballot (HL7, March 2026), eviCore's updated MSK Clinical Decision Support Pathways v14.2 (effective April 1 2026), and InterQual 2026.1 shoulder imaging criteria. SNOMED CT US Edition 2026-03-01 and LOINC 2.78 concept mappings have been verified throughout.

ICD-10 M25.512: Pain in Left Shoulder — Orthopedic Documentation, Prior Authorization & Coding Playbook for Shoulder Specialists

TL;DR: M25.512 (Pain in left shoulder) is one of the most frequently coded — and most frequently under-documented — ICD-10 codes in orthopedic shoulder practice. Payers routinely deny MRI authorizations when notes stop at "left shoulder pain" without capturing functional deficits, failed conservative therapy timelines, and objective exam findings. This guide shows shoulder and elbow surgeons exactly how to document M25.512 and its companion code M75.42 (Impingement syndrome of left shoulder) to satisfy ACR Appropriateness Criteria and InterQual benchmarks, avoid eviCore/Cohere denials, and accelerate advanced imaging authorization. Scribing.io automates this entire workflow — from ambient capture of exam findings to real-time gap detection to payer-ready X12 278/FHIR PAS packet generation — so you spend zero extra clicks on documentation and prior auth.

Table of Contents

• Understanding M25.512 in Orthopedic Shoulder Practice

• Technical Reference: ICD-10 Documentation Standards for M25.512 and M75.42

• Why Payers Deny Shoulder MRIs — And What Competitors Miss About Conservative Care Validation

• Functional Deficit Documentation: The Missing Link in MRI Authorization

• Scribing.io Clinical Logic: From Denied MRI to Same-Day Approval

• Conservative Therapy Timeline Construction: A Step-by-Step Workflow

• Payer-Ready Output: X12 278, FHIR PAS & the Evidence Packet

• Frequently Asked Questions: M25.512 Coding, Documentation & Authorization

Understanding M25.512 in Orthopedic Shoulder Practice

ICD-10-CM code M25.512 — Pain in left shoulder sits within Chapter 13 (Diseases of the musculoskeletal system and connective tissue), block M20–M25 (Other joint disorders). It is classified as a symptom-level code: it describes what the patient reports, not a confirmed structural or pathologic diagnosis. For the orthopedic shoulder and elbow surgeon, this distinction carries enormous downstream consequences — most critically, it determines whether a utilization management (UM) nurse at eviCore or Cohere Health approves or denies your MRI request before the patient leaves your office.

Scribing.io was built around this exact pain point. The platform's ambient clinical intelligence layer listens to your encounter, identifies when M25.512 is the operative code, and immediately begins assembling the structured evidence elements — functional deficits, objective exam findings, conservative therapy timelines — that payers require but that symptom-level codes alone cannot convey. The result is documentation that works for clinical care and for authorization simultaneously, without requiring you to modify your workflow or click through templated forms. Explore the full taxonomy in the Scribing.io ICD-10 Documentation Library.

When M25.512 Is — and Is Not — the Right Code

M25.512 is appropriate as a primary diagnosis in two narrow clinical windows:

1. Initial evaluation when the etiology of left shoulder pain has not yet been determined and advanced imaging has not been performed.

2. Symptom documentation when pain persists despite a known structural diagnosis and the pain itself is the reason for the encounter (e.g., pain management visit for a patient with a previously documented rotator cuff tear).

In most orthopedic shoulder encounters, M25.512 should be paired with or replaced by a more specific etiology code once clinical evaluation is complete. Per CMS ICD-10-CM Official Guidelines for Coding and Reporting (Section I.A.19), symptom codes are acceptable when no definitive diagnosis has been confirmed, but coders must assign the highest-specificity code supported by the documentation. The most common companion and successor codes include:

The coding trap: When a surgeon documents only "left shoulder pain" (M25.512) without specifying the clinical impression — even when the exam clearly suggests impingement or cuff pathology — payers interpret the note as lacking medical necessity for advanced imaging. Analysis of eviCore's musculoskeletal management program data indicates that MRI denials linked to nonspecific shoulder pain codes exceed those for etiology-specific codes by approximately 2:1.

Laterality and Specificity Requirements

ICD-10-CM mandates laterality for all M25.5x codes. Using M25.519 (Pain in unspecified shoulder) when the affected side is documented triggers audit flags and may result in claim rejection per AMA ICD-10-CM coding guidance. Scribing.io automatically enforces laterality by extracting the affected side from the clinician's spoken narrative during the encounter, eliminating the most common specificity failure in shoulder coding.

Technical Reference: ICD-10 Documentation Standards for M25.512 and M75.42

This section serves as a definitive coding and documentation reference for the two ICD-10 codes most relevant to the left shoulder pain–to–MRI authorization pathway.

M25.512 — Pain in Left Shoulder

Documentation minimum for M25.512:

• Laterality (left) explicitly stated

• Onset and duration

• Character of pain (sharp, dull, aching, burning)

• Aggravating/alleviating factors

• Functional impact — this element is nearly universally absent in competitor coding guides, yet it is the single data element most likely to determine authorization outcomes

M75.42 — Impingement Syndrome of Left Shoulder

Documentation minimum for M75.42:

• At least one positive provocative test (Neer, Hawkins-Kennedy, Jobe's)

• Range-of-motion measurements (active and passive) in degrees

• Strength assessment of rotator cuff muscles with MMT grades

• Functional limitations attributable to impingement

For a complete walkthrough of both codes, associated modifiers, and payer-specific documentation thresholds, see M25.512 — Pain in left shoulder; M75.42 — Impingement syndrome of left shoulder.

Why Payers Deny Shoulder MRIs — And What Competitors Miss About Conservative Care Validation

Standard guidance for securing shoulder MRI authorization — found in CMS reference documents, payer portals, and competitor coding resources — reduces to a single sentence: "Document 6 weeks of conservative therapy (physical therapy and NSAIDs) and include the clinical indication." That guidance is not wrong. It is dangerously incomplete.

The Gap Nobody Addresses: How Payers Actually Validate Conservative Care

When eviCore, Cohere Health, or a plan's internal UM nurse reviews an MRI prior authorization request for a patient coded under M25.512, they do not simply scan for the phrase "patient has undergone 6 weeks of conservative therapy." They perform a structured validation against discrete data points, cross-referencing the clinical note against ACR Appropriateness Criteria for Chronic Shoulder Pain and InterQual 2026.1 imaging criteria. Here is what they check:

The Anchor Truth

To secure MRI authorization, documentation must capture Functional Deficits (e.g., inability to perform ADLs or overhead reach) alongside a documented 6-week failure of Conservative Therapy (PT/NSAIDs). Neither element alone is sufficient. Payers deny when either is absent — and competitor coding guides address neither with the granularity required to survive utilization review. A 2024 JAMA Health Forum analysis of prior authorization denials in musculoskeletal care found that 42% of initial imaging denials were overturned on appeal when structured functional deficit data and conservative care timelines were added — evidence that the clinical data existed but was not captured in the original note.

What Scribing.io Does Differently

Scribing.io reconstructs a verifiable Conservative Care Timeline by parsing EHR medication orders (with start dates and fill history via NCPDP/eRx data) and ingesting external PT notes via C-CDA interoperability to auto-count sessions, dates, modalities, and NSAID duration. The system then maps functional deficits — captured from the clinician's own spoken narrative during the encounter — to SNOMED CT concepts and quantifies ROM and MMT as structured LOINC Observations (e.g., LOINC 41950-7 for shoulder abduction ROM).

This is not summarization. It is structured evidence assembly. The difference matters because payer algorithms increasingly ingest authorization data as structured fields, not free-text PDFs. Scribing.io's diarization engine filters background noise and patient speech so that only clinician-asserted findings populate the authorization payload — preventing denials rooted in ambiguous patient quotes like "I think I can lift my arm okay sometimes" being interpreted as intact function.

Functional Deficit Documentation: The Missing Link in MRI Authorization

The single most common reason shoulder MRI authorizations are denied for patients coded under M25.512 is the absence of documented functional deficits in the clinical note. Pain severity alone — even 10/10 pain — does not establish medical necessity for advanced imaging under ACR Appropriateness Criteria or InterQual clinical evidence frameworks.

What Constitutes a Functional Deficit?

A functional deficit is a specific, measurable limitation in a patient's ability to perform a defined activity. For shoulder pathology, payer-recognized functional deficits include:

Why Pain Severity Is Not a Functional Deficit

Documenting "patient reports 8/10 pain" tells the UM reviewer that the patient is in pain. It does not tell them what the patient cannot do. The distinction is not semantic — it maps directly to different authorization pathways in eviCore's clinical decision trees. A note that says "8/10 left shoulder pain" routes to a "symptom only" branch that requires imaging justification escalation. A note that says "Unable to reach overhead shelves required for warehouse duties, active abduction limited to 80 degrees, supraspinatus 4/5 with positive Neer and Hawkins" routes to a "functional impairment with clinical correlation" branch that aligns with shoulder MRI authorization criteria.

Scribing.io's real-time gap-detection engine monitors the encounter audio and fires contextual prompts when the clinician has documented pain but has not yet articulated a functional deficit. The prompt is not a generic "add functional status" — it is contextually specific: "Overhead reach limitation detected in patient history. Confirm: can patient perform overhead work tasks? Active abduction measurement needed."

Scribing.io Clinical Logic: From Denied MRI to Same-Day Approval

Below is a granular, step-by-step breakdown of how Scribing.io converts a denied-by-default clinical scenario into a same-day MRI authorization. This is not a marketing vignette — it is a clinical logic walkthrough that maps every data element to a specific payer requirement.

The Scenario

A 47-year-old warehouse worker presents with 8 weeks of atraumatic left shoulder pain. He was previously denied MRI by eviCore because the referring provider's notes lacked explicit functional deficits and proof of failed PT/NSAIDs. He has been referred to your shoulder clinic for evaluation.

Step-by-Step Logic Breakdown

Step 1: Ambient Encounter Capture with Diarization

Scribing.io's ambient microphone activates at encounter start. The diarization engine separates the surgeon's voice from the patient's voice and from background clinic noise (other conversations, equipment). Only clinician-asserted findings and clinician-confirmed patient statements are tagged as attestable data elements. When the patient says, "I can kind of reach up if I really try," this is captured as patient-reported subjective data. When the surgeon says, "Active abduction is 80 degrees with pain, unable to reach overhead," this is captured as a clinician-asserted objective finding. The distinction prevents payer reviewers from citing ambiguous patient language as evidence of preserved function.

Step 2: Structured Exam Data Extraction

As the surgeon performs the physical exam and narrates findings, Scribing.io extracts and structures the following data elements in real time:

Step 3: Real-Time Gap Detection

Scribing.io's authorization-rules engine runs a continuous comparison between the data elements captured so far and the requirements of eviCore MSK Clinical Pathway v14.2 for shoulder MRI (CPT 73221/73222). At this point, the system has objective findings and functional deficits. It checks for conservative care documentation. Finding no PT or NSAID timeline in the current note, it queries the patient's EHR chart.

Step 4: Conservative Care Timeline Reconstruction

The platform performs three automated queries:

1. Medication order history: Parses the EHR medication list and finds ibuprofen 800mg TID ordered 8 weeks ago with pharmacy fill data confirming 6 weeks of dispensing via NCPDP records. This is mapped as: NSAID trial: ibuprofen 800mg TID, 6 weeks duration, pharmacy-verified fill.

2. PT referral and notes ingestion: Locates an outbound PT referral from 7 weeks ago. Via C-CDA document exchange, ingests progress notes from the external PT clinic. Auto-counts: 8 supervised sessions over 6 weeks, interventions included rotator cuff strengthening, posterior capsule stretching, subacromial mobilization, and ultrasound modality. Home exercise program prescribed at session 2 with documented compliance through session 8.

3. Non-response validation: The PT discharge note indicates "patient plateaued at session 6, continued pain with overhead activities, recommends orthopedic reassessment." Scribing.io flags this as a documented failure of conservative therapy and generates the explicit non-response statement: Patient completed 8 sessions of supervised PT and 6 weeks of scheduled NSAID therapy (ibuprofen 800mg TID) with home exercise program compliance. Symptoms persist without meaningful improvement. Conservative therapy has failed.

Step 5: Code Assignment and Dual-Code Strategy

Based on the captured exam (positive Neer, positive Hawkins, subacromial tenderness, painful arc), Scribing.io suggests M75.42 (Impingement syndrome of left shoulder) as the primary assessment code, with M25.512 listed as a secondary code reflecting the presenting symptom. This dual-code strategy is critical: M75.42 establishes an etiology-level diagnosis that aligns directly with ACR's "usually appropriate" MRI indication for suspected impingement with failed conservative care, while M25.512 preserves the symptom trail for longitudinal tracking and payer audits.

Step 6: InterQual/ACR Criteria Checklist Assembly

Scribing.io auto-generates a payer-ready evidence checklist mapped to InterQual 2026.1 shoulder MRI criteria:

• ☑ Duration ≥6 weeks — 8 weeks documented

• ☑ Functional deficit present — Overhead reach limitation, occupational impairment (warehouse work)

• ☑ Objective ROM deficit — Active abduction 80° (<90° threshold)

• ☑ Provocative tests positive — Neer positive, Hawkins-Kennedy positive

• ☑ Strength deficit — Supraspinatus 4/5

• ☑ Conservative therapy completed — 8 PT sessions over 6 weeks + ibuprofen 800mg TID × 6 weeks

• ☑ HEP compliance documented — Confirmed in PT notes

• ☑ Non-response documented — PT discharge note: plateaued, persistent symptoms

• ☑ Radiographs obtained — AP/axillary/scapular Y views reviewed, no fracture, mild subacromial spurring

Step 7: X12 278/FHIR PAS Packet Export

The system packages all structured data elements into both an X12 278 Health Care Services Review transaction and a Da Vinci FHIR Prior Authorization Support (PAS) Bundle, with a human-readable PDF attachment containing the checklist above and supporting clinical documentation. The packet is transmitted directly to eviCore's electronic submission portal from within the EHR. Same-day MRI approval is returned, averting a repeat visit, lost workdays for the patient, and a peer-to-peer call for the surgeon.

Conversion Hook: See our Shoulder MRI Prior-Auth Auto-Builder: conservative-care timeline extractor + SNOMED/LOINC mapping + InterQual-aligned checklist with X12 278/FHIR PAS export inside your EHR. Book a 12-minute live demo →

Conservative Therapy Timeline Construction: A Step-by-Step Workflow

This section provides the exact documentation framework surgeons and their staff need to construct a payer-verifiable conservative care timeline — whether using Scribing.io's automated pipeline or building it manually.

The Five Required Timeline Elements

1. NSAID Documentation: Drug name, dose, frequency, start date, duration, and outcome. "Ibuprofen 800mg TID started 4/1/2026, continued through 5/13/2026 (6 weeks). Minimal relief of symptoms. No GI adverse effects." Per NIH clinical pharmacology reference, NSAID trial adequacy requires documentation of both dose and duration to differentiate sub-therapeutic use from true treatment failure.

2. PT Session Count and Date Range: Number of supervised sessions (minimum 6), date of first and last session, name of facility. "8 sessions at ABC Physical Therapy, 4/3/2026 – 5/15/2026."

3. PT Interventions Performed: Specific modalities and exercises. "Rotator cuff strengthening (IR/ER theraband, prone Y/T/W), posterior capsule stretching (cross-body adduction, sleeper stretch), subacromial joint mobilizations, therapeutic ultrasound."

4. Home Exercise Program Compliance: Was a HEP prescribed? Did the patient comply? "HEP prescribed at session 2 (IR/ER strengthening, pendulum exercises). Patient reports daily compliance through session 8. No improvement in overhead function."

5. Non-Response Statement: An explicit, unambiguous statement that conservative therapy has failed. Avoid equivocal language. Do not write: "Patient may benefit from continued PT." Write: "Patient has completed a 6-week course of supervised PT (8 sessions) and concurrent NSAID therapy without meaningful improvement in pain, ROM, or function. Conservative treatment has been exhausted. Advanced imaging is indicated to evaluate for structural pathology."

Scribing.io Automation vs. Manual Workflow

Payer-Ready Output: X12 278, FHIR PAS & the Evidence Packet

Once Scribing.io has captured clinical findings, reconstructed the conservative care timeline, and assembled the InterQual-aligned checklist, the final step is transmission to the payer in a format that their systems can ingest, parse, and adjudicate without human re-entry.

X12 278 Health Care Services Review

The X12 278 transaction standard — mandated under HIPAA for electronic prior authorization — encodes the service request, diagnosis codes (M25.512, M75.42), CPT code (73221 for MRI shoulder without contrast or 73222 with contrast), and clinical justification data. Scribing.io populates every required segment: subscriber identification (Loop 2010A), provider information (Loop 2010B), service-level detail (Loop 2000E), and diagnosis codes (HI segment). The clinical justification data — ROM values, MMT grades, PT session counts — is structured within the PWK (paperwork) and HI (health information) segments rather than relegated to an unstructured attachment, increasing the probability of automated adjudication.

Da Vinci FHIR Prior Authorization Support (PAS)

For payers participating in the HL7 Da Vinci PAS Implementation Guide (which CMS is expanding under the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)), Scribing.io generates a FHIR PAS Bundle containing:

• Claim resource: CPT 73221/73222 with M75.42 as primary diagnosis, M25.512 as secondary

• Condition resources: Each diagnosis code with onset date, clinical status, and evidence references

• Observation resources: ROM (LOINC 41950-7: 80° abduction), MMT (LOINC 83058-1: 4/5 supraspinatus), provocative tests (SNOMED-coded positive Neer/Hawkins)

• Procedure resources: PT sessions (SNOMED 91251008 — Physical therapy procedure) with date range and session count

• MedicationStatement resources: Ibuprofen 800mg TID with effectivePeriod documenting 6-week duration

• DocumentReference: Human-readable PDF of the InterQual-aligned checklist for reviewers who prefer narrative format

This dual-format approach — X12 278 for legacy payer systems, FHIR PAS for modern API-enabled payers — ensures compatibility across the entire payer landscape in 2026.

Frequently Asked Questions: M25.512 Coding, Documentation & Authorization

Can I use M25.512 as the primary code when ordering a shoulder MRI?

You can, but it significantly increases denial risk. M25.512 is a symptom code. Payers prefer etiology codes (M75.42 for impingement, M75.12 for rotator cuff tear) because they map more directly to imaging appropriateness criteria. Best practice: use M25.512 as a secondary code alongside the most specific etiology code your clinical evaluation supports. Scribing.io auto-suggests this dual-code strategy when exam findings support an etiology-level diagnosis.

What is the minimum number of PT sessions required before a payer will approve shoulder MRI?

There is no universal CMS-mandated minimum. However, eviCore's MSK pathways and InterQual 2026.1 criteria both benchmark at 6–8 supervised sessions over a minimum of 6 weeks. Documenting fewer than 6 sessions triggers a "conservative care insufficiency" flag in eviCore's automated decision engine. Scribing.io auto-counts sessions from ingested PT notes and fires a warning if the count falls below the threshold.

Does documenting "decreased ROM" satisfy the functional deficit requirement?

No. "Decreased ROM" without a degree measurement is an unquantified observation, not a functional deficit. Payers require: (a) ROM in degrees (e.g., "active abduction 80°") and (b) a functional translation (e.g., "unable to reach overhead shelves required for warehouse duties"). Both elements are needed. Scribing.io extracts degree-level ROM from the surgeon's spoken exam and automatically generates the functional correlation statement based on the patient's documented occupation.

What if the patient's PT records are unavailable at the time of the visit?

This is the most common bottleneck in manual prior-auth workflows. Without PT records, the surgeon must either (a) document the patient's self-reported PT history (which payers discount) or (b) delay the MRI request until records are obtained (which costs the patient a return visit). Scribing.io's C-CDA ingestion pipeline queries connected PT facilities in real time. If records are not available electronically, the system generates a structured records request with the specific data fields needed (session count, dates, modalities, HEP status, discharge status) so that the PT clinic can respond with targeted information rather than sending an entire chart.

Is M25.512 appropriate for workers' compensation shoulder claims?

Workers' compensation carriers follow state-specific treatment guidelines (e.g., California MTUS, ACOEM guidelines) that generally require more granular injury-mechanism documentation than commercial payers. M25.512 can be used as an initial encounter code, but WC carriers expect rapid transition to mechanism-specific and pathology-specific codes. Additionally, the functional deficit documentation must reference occupational tasks, not generic ADLs. Scribing.io detects WC payer class from the patient's coverage data and adjusts its documentation prompts accordingly — shifting from "can you dress yourself" ADL prompts to "can you perform your essential job duties" occupational prompts.

How does Scribing.io handle the Neer and Hawkins tests specifically?

When the surgeon says "Neer is positive" or "positive Hawkins," the NLP engine maps these to SNOMED CT concepts (710041003 and 710042005, respectively) and tags them as clinician-asserted positive provocative tests in the authorization evidence packet. If the surgeon performs the tests but does not verbalize the result, the system prompts: "Neer test performed — please state result." This prevents the common documentation gap where the surgeon tested but forgot to dictate the outcome.

Ready to eliminate MRI denials for shoulder pain? See the Shoulder MRI Prior-Auth Auto-Builder in action: conservative-care timeline extractor + SNOMED/LOINC mapping + InterQual-aligned checklist with X12 278/FHIR PAS export inside your EHR. Book a 12-minute live demo →