M21.20 identifies an acquired flexion deformity without documentation of a specific anatomical site. Use this code only when the affected joint or limb region is genuinely unspecified in the clinical record.
Verified May 8, 2026 · 6 sources ↓
- Status
- Billable
- Chapter
- 13
- Related CPT
- 5
- Region
- General
Documentation tips
What should appear in the chart to support M21.20.
Source · Editorial brief grounded in 6 cited references ↓
- Document the specific joint involved (e.g., knee, hip, elbow) by name to enable a site-specific M21.2x code rather than M21.20.
- Record laterality explicitly (right or left) — this prevents mismatches with unilateral procedure modifiers and laterality edits.
- Distinguish acquired from congenital origin; congenital flexion deformities map to Q65–Q74, not M21.20, and the Excludes1 note makes the two mutually exclusive.
- Note degree of contracture, range-of-motion measurements, and functional impact to support medical necessity for associated therapy or surgical procedures.
- If conservative treatment such as serial casting or dynamic splinting has been attempted, document that history to support surgical or intensive rehabilitative intervention.
Related CPT procedures
Procedure codes commonly billed with M21.20. 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 M21.20 and adjacent codes.
Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓
- Defaulting to M21.20 when a site-specific child code exists — check M21.21 (shoulder), M21.22 (elbow), M21.23 (wrist), M21.24 (finger joints), M21.25 (hip), M21.26 (knee), and M21.27 (ankle/foot) before using the unspecified code.
- Pairing M21.20 with a congenital deformity code from Q65–Q74 violates the Excludes1 rule at the M21 category level; these cannot be reported together.
- Using M21.20 alongside an acquired finger or toe deformity code (M20.-) on the same claim line without clinical justification — M20.- is an Excludes2, so both codes are only appropriate when the conditions are genuinely separate.
- Submitting M21.20 with a lateralized procedure modifier (RT or LT) when the diagnosis itself carries no laterality — this triggers a diagnosis-to-modifier mismatch denial under payer laterality edits.
- Applying M21.20 to post-traumatic contractures without also coding the underlying cause when an etiology code is available and instructed by the Tabular List.
Clinical context
Source · Editorial summary grounded in 6 cited references ↓
M21.20 is the catch-all code under the M21.2 flexion deformity subcategory when the treating provider has not documented — or the coder cannot determine — which joint or limb segment is affected. In orthopedic practice, a flexion deformity is a fixed or functional inability to fully extend a joint, most commonly seen at the knee (flexion contracture), hip, elbow, or fingers. Each of those sites has a more specific M21.2x child code; M21.20 should be a last resort, not a default.
The M21 category covers other acquired deformities of limbs. Critical Excludes1 notes at the M21 level prohibit coding M21.20 alongside acquired absence of limb (Z89.-), congenital absence of limbs (Q71–Q73), and congenital deformities and malformations of limbs (Q65–Q66, Q68–Q74). Acquired deformities of fingers or toes fall under M20.- and are excluded via an Excludes2 note — meaning both codes can coexist if the conditions are distinct and documented. Coxa plana (M91.2) is also excluded.
In orthopedic and physical medicine billing, this code groups into MS-DRG v43.0 clusters 564–566 (Other musculoskeletal system and connective tissue diagnoses with/without MCC/CC). Because it carries no laterality or site specificity, it is audit-vulnerable when paired with a unilateral procedure code or a laterality modifier. Query the provider before submitting M21.20 if any clinical documentation references a specific joint.
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 6 cited references ↓
01When is M21.20 appropriate versus a more specific M21.2x code?
02Can M21.20 be coded alongside a congenital limb deformity from the Q65–Q74 range?
03Can M21.20 and an M20.- finger or toe deformity code appear on the same claim?
04What DRGs does M21.20 map to for inpatient encounters?
05Will a payer deny a claim if M21.20 is submitted with a lateralized modifier like RT or LT?
06Does M21.20 require a 7th-character extension?
07Can M21.20 be used for a post-surgical knee flexion contracture?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01CDC ICD-10-CM Tabular List 2026 (effective Oct 1, 2025)
- 02icd10data.comhttps://www.icd10data.com/ICD10CM/Codes/M00-M99/M20-M25/M21-/M21.20
- 03aapc.comhttps://www.aapc.com/codes/icd-10-codes/M21.20
- 04icd10data.comhttps://www.icd10data.com/ICD10CM/Codes/M00-M99/M20-M25/M21-
- 05cms.govhttps://www.cms.gov/Medicare/Coding/ICD10/Downloads/2019-ICD10-Coding-Guidelines-.pdf
- 06emblemhealth.comhttps://www.emblemhealth.com/providers/claims-corner/coding/correct-laterality-icd-10-cm-diagnosis-coding-policy
Mira AI Scribe
Mira AI Scribe captures the affected joint by name, the side of the body, measured range-of-motion deficit, acquired versus congenital etiology, and any prior conservative treatment from the encounter note. This prevents the provider from landing on M21.20 when a site-specific M21.2x code is justified, avoiding payer laterality denials and audit flags tied to unspecified diagnosis codes paired with lateralized procedures.
See how Mira captures M21.20 documentation