Recurrent instability of the atlantoaxial joint (C1–C2) that has produced spinal cord compression or injury, resulting in myelopathy — documented as a recurring pattern, not a single acute event.
Verified May 8, 2026 · 5 sources ↓
- Status
- Billable
- Chapter
- 13
- Related CPT
- 12
- Region
- Spine
Documentation tips
What should appear in the chart to support M43.3.
Source · Editorial brief grounded in 5 cited references ↓
- Explicitly state 'recurrent' in the clinical note — a single prior episode documented in the record supports this but the current note must reflect the recurring pattern, not an initial dislocation.
- Document myelopathy with objective findings: upper motor neuron signs (Babinski, clonus, hyperreflexia), gait ataxia, Lhermitte's sign, or bowel/bladder dysfunction tied to cord-level involvement at C1–C2.
- Record MRI or CT myelographic findings showing spinal cord signal change, cord compression, or canal compromise at the atlantoaxial level — these imaging results are the strongest audit anchor.
- If an underlying condition (rheumatoid arthritis, Down syndrome, os odontoideum) drives the instability, document it and sequence appropriately; M43.3 may be secondary.
- Distinguish from radiculopathy: if the patient has only neck pain or C2 dermatomal symptoms without cord signs, M43.3 is not supported — myelopathy must be clinically established.
- For operative notes, document the approach, the levels addressed (C1–C2), instrumentation used, and whether decompression was performed — these drive CPT selection and support medical necessity for the M43.3 diagnosis.
Related CPT procedures
Procedure codes commonly billed with M43.3. 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 M43.3 and adjacent codes.
Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓
- Assigning M43.3 without documented myelopathy — recurrent atlantoaxial instability alone without cord involvement does not meet the specificity of this code; use M43.4 or M43.5X– instead.
- Co-assigning M47.1 (Other spondylosis with myelopathy) with M43.3 for the same encounter — the Type 1 Excludes at M47.1 prohibits this combination; M43.3 is the correct code when instability is the mechanism.
- Using M24.4 (Recurrent dislocation of joint) for atlantoaxial instability — the Type 2 Excludes at M24.4 redirects recurrent vertebral dislocations to M43.3–M43.5, making M24.4 incorrect here.
- Failing to append a secondary code for the underlying etiology (e.g., rheumatoid arthritis, trisomy 21) when it is the documented cause of the ligamentous incompetence — incomplete coding can trigger medical necessity denials.
- Applying a 7th-character extension to M43.3 — this is an M-code and does not use 7th-character injury extensions (A/D/S); those apply to S-code trauma encounters only.
Clinical context
Source · Editorial summary grounded in 5 cited references ↓
M43.3 applies when the C1–C2 articulation repeatedly dislocates or subluxates and that instability has caused myelopathy — upper motor neuron signs, gait disturbance, hand clumsiness, hyperreflexia, or bowel/bladder dysfunction attributable to cord involvement at the craniocervical junction. The diagnosis requires both elements: recurrence (not a first-time event) and myelopathy (not just pain or radiculopathy). If myelopathy is absent, look at M43.4 (other recurrent atlantoaxial dislocation) instead.
Common underlying etiologies include rheumatoid arthritis with transverse ligament destruction, Down syndrome (ligamentous laxity), os odontoideum, and post-traumatic ligamentous incompetence. When the atlantoaxial instability is a manifestation of an underlying systemic disease, code that condition as well — for example, rheumatoid arthritis (M06.–) coded first if it is the reason for the encounter.
M43.3 groups into MS-DRGs 564–566 (Other musculoskeletal system and connective tissue diagnoses with/without MCC/CC), so MCC and CC documentation directly affects reimbursement tier. The Type 1 Excludes at M47.1 bars you from assigning both M43.3 and M47.1 for the same episode; the instability-driven myelopathy is captured here, not under spondylosis. M24.4 (Recurrent dislocation of joint) has a Type 2 Excludes cross-reference pointing to M43.3, confirming this is the correct code for recurrent vertebral dislocation with cord involvement.
Sibling codes
Other billable codes under M43 (laterality / anatomic variants).
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 5 cited references ↓
01What distinguishes M43.3 from M43.4?
02Can M43.3 and M47.1 be coded together on the same claim?
03Is M43.3 used for the initial dislocation event or only for recurrent episodes?
04Which MS-DRGs does M43.3 group to and how does documentation affect the tier?
05Should the underlying cause of atlantoaxial instability be coded separately?
06Does M43.3 require a 7th-character extension?
07What imaging documentation best supports M43.3 at audit?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01CDC ICD-10-CM Tabular List 2026 (FY2026, effective Oct 1, 2025)
- 02icd10data.comhttps://www.icd10data.com/ICD10CM/Codes/M00-M99/M40-M43/M43-/M43.3
- 03aapc.comhttps://www.aapc.com/codes/icd-10-codes/M43.3
- 04ecgwaves.comhttps://ecgwaves.com/icd-code/m43-3-recurrent-atlantoaxial-dislocation-with-myelopathy-icd-10-code-in-m40-m54-dorsopathies/
- 05CMS MS-DRG v43.0 Grouper — DRGs 564, 565, 566
Mira Scribe
The Mira AI Scribe captures the documentation that locks in M43.3: the word 'recurrent' tied to prior dislocation episodes, objective myelopathy findings (upper motor neuron signs, gait ataxia, cord signal change on MRI), and the specific C1–C2 level. That documentation prevents downcoding to the nonspecific M43.4 or an incorrect M47.1 assignment — both of which can trigger claim edits or audit flags given the Type 1 and Type 2 Excludes relationships at those codes.
See how Mira captures M43.3 documentation