ICD-10-CM · Multi-region

M66.29

M66.29 captures spontaneous rupture of extensor tendons occurring at more than one anatomical site simultaneously, where no external traumatic force caused the failure — the tendons themselves are inferred to have subnormal structural integrity.

Verified May 8, 2026 · 5 sources ↓

Status
Billable
Chapter
13
Related CPT
9
Region
Multi-region
Drawn from CDCAAPCICD10DataHealthMdclarity

Documentation tips

What should appear in the chart to support M66.29.

Source · Editorial brief grounded in 5 cited references ↓

  • Identify each affected anatomical site by name in the clinical note — e.g., 'right hand extensor tendons and left forearm extensor tendons' — so that M66.29 (multiple sites) is clearly justified over a single-site code.
  • Document the mechanism as non-traumatic: explicitly state there was no acute injury or abnormal external force. Reference any underlying systemic condition (rheumatoid arthritis, prolonged corticosteroid use, chronic renal failure) that explains tendon vulnerability.
  • Record imaging findings that confirm rupture at each site — MRI or ultrasound report with findings such as tendon discontinuity, retraction, or gap formation supports medical necessity and withstands audit.
  • Note conservative care history or prior treatment attempts before surgical repair is planned; payers may require documentation of functional impairment and failed conservative management for repair CPT authorization.
  • If the patient has a relevant underlying condition (e.g., rheumatoid arthritis M06.9), code that diagnosis alongside M66.29 to establish clinical causality.

Related CPT procedures

Procedure codes commonly billed with M66.29. Linking the right diagnosis to the right procedure is what establishes medical necessity.

Source · CMS LCDs · AAOS specialty guidance · claims-pattern analysis

Common coding pitfalls

The recurring mistakes coders make with M66.29 and adjacent codes.

Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓

  • Assigning M66.29 for a traumatic tendon rupture — if an abnormal external force caused the rupture, the correct path is an S-code injury by body region, not M66.29. The non-traumatic mechanism must be documented explicitly.
  • Defaulting to M66.29 when only a single site is ruptured — if documentation identifies one location only, use the site-specific M66.2x code (e.g., M66.241 for right hand). M66.29 requires multiple sites.
  • Confusing extensor and flexor tendon codes — M66.2x covers extensor tendons; M66.3x covers flexor tendons. Verify the specific tendon type in the operative or clinical note before selecting the subcategory.
  • Omitting the underlying systemic diagnosis — coding M66.29 without a co-coded condition like rheumatoid arthritis when that condition is documented leaves clinical context on the table and can trigger payer queries.
  • Using M66.29 for rotator cuff rupture — the Excludes2 note at M66 directs rotator cuff syndrome to M75.1x; while both codes can coexist if clinically appropriate, rotator cuff pathology alone should not drive M66.29.

Clinical context

Source · Editorial summary grounded in 5 cited references ↓

Use M66.29 when the clinical record documents non-traumatic rupture of extensor tendons at two or more distinct body sites in the same patient. The M66 category, per the ICD-10-CM Tabular List, is reserved for ruptures caused by normal forces applied to abnormally weakened tissue — not injuries from excessive external force. The classic clinical backdrop is a systemic condition that degrades connective tissue: rheumatoid arthritis, chronic corticosteroid use, gout, or dialysis-related amyloidosis. If the rupture is traumatic (abnormal force on normal tissue), do not use M66.29 — code to the appropriate S-code injury category by body region instead.

Within the M66.2 subcategory, site-specific codes exist for the shoulder (M66.21x), upper arm (M66.22x), forearm (M66.23x), hand (M66.24x), thigh (M66.25x), lower leg (M66.26x), ankle and foot (M66.27x), and other site (M66.28). M66.29 is the correct selection only when multiple distinct sites are affected and a single site-specific code cannot capture the full picture. If only one site is involved, assign the corresponding site-specific code instead.

Note the Excludes2 at the M66 category level: rotator cuff syndrome (M75.1-) is excluded, meaning it can be coded alongside M66.29 if both are present, but rotator cuff pathology itself is not the basis for M66.29. Also confirm that any imaging — MRI or ultrasound — is documented in the record, as payer scrutiny on spontaneous rupture claims is elevated given the non-traumatic mechanism.

Sibling codes

Other billable codes under M66.2 (laterality / anatomic variants).

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 5 cited references ↓

01What is the difference between M66.29 and M66.28?
M66.28 is for spontaneous extensor tendon rupture at a single 'other' site not listed elsewhere in M66.2. M66.29 requires documented rupture at two or more distinct anatomical sites. If only one atypical site is affected, use M66.28.
02Can M66.29 be used for a traumatic extensor tendon rupture?
No. M66.29 is restricted to non-traumatic ruptures — those where a normal force is applied to structurally compromised tissue. Traumatic ruptures caused by abnormal external force must be coded with the appropriate S-code injury by body region.
03Should I code the underlying condition (e.g., rheumatoid arthritis) alongside M66.29?
Yes, when documented. The underlying systemic disease explains tendon vulnerability and supports medical necessity. Code it as an additional diagnosis using the appropriate M-code for the condition (e.g., M06.9 for rheumatoid arthritis, unspecified).
04Does M66.29 apply to rotator cuff ruptures?
No. The M66 category carries an Excludes2 for rotator cuff syndrome (M75.1-). Rotator cuff pathology is coded to M75.1x. Both codes can appear on the same claim if clinically distinct conditions are present, but rotator cuff rupture alone does not justify M66.29.
05What imaging documentation supports M66.29 on audit?
MRI or musculoskeletal ultrasound reports identifying tendon discontinuity, retraction, or gap formation at each affected site are the strongest audit-defense documentation. X-rays alone are generally insufficient to confirm tendon rupture.
06Which CPT codes are commonly paired with M66.29 for surgical repair?
Common pairings include 26418 (extensor tendon repair, hand), 25270 (extensor tendon repair, forearm/wrist), and 24341 (tendon repair, upper arm/elbow). Site-specific repair CPT codes should match each anatomical site documented in M66.29.
07Is M66.29 valid for FY2026 coding?
Yes. M66.29 is a valid, billable ICD-10-CM code in the FY2026 code set (effective October 1, 2025), per the CDC ICD-10-CM Tabular List 2026.

Sources & references

Editorial content was developed using the following public sources. Last verified May 8, 2026.

  1. 01CDC ICD-10-CM Tabular List 2026 (FY2026, effective Oct 1, 2025)
  2. 02
    aapc.com
    https://www.aapc.com/codes/icd-10-codes/M66.29
  3. 03
    icd10data.com
    https://www.icd10data.com/ICD10CM/Codes/M00-M99/M65-M67/M66-/M66.29
  4. 04
    health.mil
    https://www.health.mil/Reference-Center/Publications/2016/11/01/Tendon-Rupture
  5. 05
    mdclarity.com
    https://www.mdclarity.com/icd-codes/m66-29

Mira AI Scribe

Mira's AI scribe captures the non-traumatic mechanism, each affected anatomical site by name, any documented underlying systemic condition (e.g., rheumatoid arthritis, corticosteroid history), and imaging confirmation of rupture at multiple locations. That documentation prevents downcoding to an unspecified or single-site code, blocks erroneous reassignment to a traumatic S-code, and satisfies payer audit criteria for spontaneous rupture claims.

See how Mira captures M66.29 documentation

Related ICD-10 codes

Ready?

Ready to transform your orthopedic practice?

See how orthopedic practices are running documentation, billing, and operations on a single voice-first platform.

Get started for free