ICD-10-CM · Multi-region

M66.89

Spontaneous rupture of tendons at more than one anatomical site, where the tendons involved do not fall under the extensor (M66.2x) or flexor (M66.3x) classifications and the rupture occurs through normal force applied to structurally compromised tissue.

Verified May 8, 2026 · 5 sources ↓

Status
Billable
Chapter
13
Related CPT
7
Region
Multi-region
Drawn from CDCAAPCU.S. DepartmentICD

Documentation tips

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

Source · Editorial brief grounded in 5 cited references ↓

  • Name each ruptured tendon explicitly (e.g., 'patellar tendon and peroneal tendon') — 'multiple tendons' alone is insufficient for audit defense.
  • Specify laterality for each involved site; the code itself is non-lateral, but procedure codes and operative reports will require right/left designation.
  • Document the clinical basis for spontaneous (non-traumatic) classification: absence of acute injury mechanism, imaging findings (MRI/ultrasound showing degeneration or full-thickness tear without acute trauma), and any predisposing conditions such as fluoroquinolone use, rheumatoid arthritis, gout, or chronic corticosteroid therapy.
  • Record whether ruptures are acute, subacute, or chronic at each site — this affects surgical planning and may affect payer medical necessity review.
  • If a predisposing systemic condition (e.g., rheumatoid arthritis M05.x, renal failure N18.x) is present and treated concurrently, code it as an additional diagnosis to support medical necessity.

Related CPT procedures

Procedure codes commonly billed with M66.89. 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.89 and adjacent codes.

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

  • Using M66.89 for extensor or flexor tendon ruptures at multiple sites — those belong to M66.29 (extensor, multiple sites) or M66.39 (flexor, multiple sites), not M66.89.
  • Applying M66.89 when only a single 'other' tendon site is ruptured — use the appropriate single-site code (M66.80–M66.88) instead.
  • Coding M66.89 for a traumatic rupture where abnormal force was applied to normal tissue — traumatic tendon ruptures are coded from the injury chapter (S-codes by body region), not M66.
  • Omitting the Excludes2 note: rotator cuff syndrome (M75.1x) is excluded from M66 by an Excludes2 notation, meaning both codes can be reported if both conditions are independently documented, but the rupture must not be the same pathology as the rotator cuff syndrome already captured under M75.1x.
  • Failing to distinguish M66.89 from M66.9 (spontaneous rupture of unspecified tendon) — M66.89 requires documented identification of multiple 'other' tendon sites; M66.9 is appropriate only when tendon type and site are genuinely unspecified.

Clinical context

Source · Editorial summary grounded in 5 cited references ↓

M66.89 applies when a patient sustains spontaneous (non-traumatic) rupture of tendons classified under 'other tendons' — meaning neither the dedicated extensor nor flexor tendon subcategories — and the ruptures occur at multiple anatomical sites simultaneously or are documented together in a single encounter. The defining feature of any M66 code is that normal physiologic force caused the rupture, implying underlying tendon weakness (e.g., from systemic disease, medication effect such as fluoroquinolone use, metabolic disorder, or chronic degeneration). This is not a traumatic rupture code.

Use M66.89 only when two conditions are met: (1) the affected tendons are 'other' tendons not captured by M66.2x (extensor) or M66.3x (flexor) at specific site codes, and (2) multiple sites are involved. If only one site is affected, use the corresponding single-site code in the M66.8x series (e.g., M66.88 for a single 'other' site). If the tendon is an extensor or flexor, move to M66.2x or M66.3x respectively. Rotator cuff syndrome is an Excludes2 condition — M75.1x may be coded alongside M66.89 if both are present and documented.

Common clinical scenarios include multi-tendon ruptures in patients with rheumatoid arthritis, chronic corticosteroid use, dialysis-related tendinopathy, or fluoroquinolone toxicity affecting tendons across regions. Document the specific tendons and locations involved; vague multi-site language without specifying which tendons were ruptured will not support this code at audit.

Sibling codes

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

Frequently asked questions

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

01What makes a tendon rupture 'spontaneous' for M66.89 coding purposes?
The ICD-10-CM includes clause for M66 defines spontaneous rupture as one that occurs when normal force is applied to tissue with less than normal strength. If the patient reports no acute trauma and the clinical picture supports underlying tendon vulnerability (degeneration, systemic disease, medication toxicity), the rupture qualifies as spontaneous.
02Can M66.89 be used for bilateral Achilles tendon ruptures?
No. Achilles tendon ruptures are flexor tendon ruptures and belong under M66.3x. Bilateral spontaneous Achilles ruptures would be coded M66.372 and M66.371 (or M66.379 if unspecified side), or M66.39 for multiple flexor tendon sites — not M66.89.
03When should M66.89 be used instead of M66.88?
Use M66.88 when a single 'other' tendon site outside the named anatomical subcategories (shoulder, upper arm, forearm, hand, thigh, lower leg, ankle/foot) is involved. Use M66.89 when two or more such 'other' tendon sites are involved in the same encounter.
04Does M66.89 require a 7th character extension?
No. M66.89 is a 5-character M-code and does not use 7th-character extensions. Those are reserved for injury (S-code) and fracture encounters.
05Can rotator cuff syndrome (M75.1x) be coded alongside M66.89?
Yes, under the Excludes2 rule. Excludes2 means the two conditions are not the same thing and may coexist. If the rotator cuff syndrome is separately documented and clinically distinct from the spontaneous 'other' tendon ruptures, both codes may be reported.
06What CPT procedures are commonly paired with M66.89 on a claim?
Tendon repair procedures vary by site. Common pairings include 27385/27386 (quadriceps or hamstring rupture repair), 27380/27381 (infrapatellar tendon repair), 23410/23412 (rotator cuff repair if applicable), and 20924 (tendon graft harvesting). The specific CPT must match the tendon(s) and site(s) documented.
07Is M66.89 valid for encounters after the initial repair or injury, such as follow-up visits?
Yes. Unlike S-codes, M-codes do not carry encounter-type extensions (A/D/S). M66.89 is appropriate for any encounter — initial presentation, post-operative follow-up, or chronic management — as long as the spontaneous multi-site tendon rupture remains the reason for the visit.

Sources & references

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

  1. 01CDC ICD-10-CM Tabular List 2026 — icd10data.com/ICD10CM/Codes/M00-M99/M65-M67/M66-/M66.89
  2. 02AAPC Codify — M66.89 code page (2025)
  3. 03U.S. Department of Defense / Defense Health Agency: Tendon Rupture Non-Traumatic Case Definition, November 2016 — health.mil
  4. 04AAPC Codify — M66.8 parent code page (2025)
  5. 05ICD10data.com — M66 category tabular, 2026

Mira AI Scribe

The Mira AI Scribe captures tendon names, anatomical sites (with laterality), mechanism of rupture (spontaneous vs. traumatic), imaging findings supporting structural compromise, and any predisposing diagnoses. This prevents assignment of the unspecified M66.9 or wrong-subcategory codes (M66.29, M66.39), both of which trigger specificity downcoding and payer audit flags.

See how Mira captures M66.89 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