M50.90 identifies a cervical disc disorder where neither the specific type of disorder (myelopathy, radiculopathy, displacement, degeneration) nor the precise cervical region (high cervical, mid-cervical, cervicothoracic) is documented or determinable from available clinical information.
Verified May 8, 2026 · 6 sources ↓
- Status
- Billable
- Chapter
- 13
- Related CPT
- 10
- Region
- Spine
Documentation tips
What should appear in the chart to support M50.90.
Source · Editorial brief grounded in 6 cited references ↓
- Document the specific cervical region by name (high cervical C2-4, mid-cervical C4-7, cervicothoracic C7-T1) to support upgrading from M50.90 to a level-specific code.
- Record whether neurological findings are present — radiculopathy (dermatomal sensory loss, positive Spurling's, reflex changes) justifies M50.1x; myelopathic signs (hyperreflexia, gait disturbance, hand clumsiness) justifies M50.0x.
- Tie imaging results directly to the clinical impression — note which disc level shows pathology on MRI or CT and state the finding type (herniation, degeneration, displacement) explicitly in the assessment.
- If conservative treatment history is relevant to medical necessity, document modalities tried, duration, and response to support prior-authorization requirements for injections or surgery.
- When documentation is incomplete at the time of coding, issue a provider query rather than defaulting to M50.90 permanently — most records can support a more specific M50 code once the level is confirmed.
Related CPT procedures
Procedure codes commonly billed with M50.90. 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 M50.90 and adjacent codes.
Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓
- Assigning M50.90 when MRI is already on file identifying the affected disc level and pathology type — that record supports a specific M50 code and M50.90 will draw payer scrutiny.
- Coding M50.90 alongside a separate radiculopathy code (e.g., M54.12) when the correct approach is a combination code such as M50.12, which captures both the disc disorder and radiculopathy in a single code.
- Confusing M50.90 (unspecified disorder, unspecified region) with M50.80 (other cervical disc disorders, unspecified region) — M50.80 is for documented disc disorders that don't fit myelopathy, radiculopathy, displacement, or degeneration subcategories but are still characterizable.
- Failing to reassess and update M50.90 after diagnostic workup is complete — leaving an unspecified code on an established patient's claim when imaging results have since defined the level and disorder type is a compliance risk.
Clinical context
Source · Editorial summary grounded in 6 cited references ↓
M50.90 is the fallback code within the M50 category when documentation supports a cervical disc disorder diagnosis but lacks two key specifics: the nature of the disorder and the spinal level involved. The M50 family includes far more precise options — M50.00–M50.03 for myelopathy, M50.10–M50.13 for radiculopathy, M50.20–M50.23 for disc displacement, and M50.30–M50.33 for disc degeneration, each further subdivided by region (occipito-atlanto-axial, mid-cervical, cervicothoracic). M50.90 should only survive coding review when the record genuinely cannot support any of those more specific codes.
In practice, M50.90 appears most often at initial encounters before advanced imaging is available, or when a referring provider's documentation is incomplete and a query is not yet resolved. If MRI confirms a herniated disc at C5-6 with arm numbness, that's M50.122 (mid-cervical, radiculopathy, C5-6 level) — not M50.90. If the note says only 'cervical disc disease' with no imaging and no neurological findings documented, M50.90 may be appropriate temporarily, but the goal is always to upgrade specificity as documentation matures.
MS-DRG v43.0 groups M50.90 into DRGs 551 (Medical back problems with MCC) and 552 (Medical back problems without MCC). Payers increasingly flag unspecified cervical codes when imaging is on file, so using M50.90 after an MRI has been read and a level identified creates an audit exposure that a simple provider query or addendum would eliminate.
Sibling codes
Other billable codes under M50.9 (laterality / anatomic variants).
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 6 cited references ↓
01When is M50.90 actually appropriate versus a more specific M50 code?
02Can M50.90 be used alongside a radiculopathy code like M54.12?
03What cervical regions does the M50 category recognize for level specificity?
04Does M50.90 require a 7th character?
05Which DRGs does M50.90 map to under MS-DRG v43.0?
06Is M50.90 valid for FY2026 claims?
07What approximate synonyms map to M50.90 in the ICD-10-CM index?
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/M50-M54/M50-/M50.90
- 03cms.govhttps://www.cms.gov/medicare/coding/icd10/downloads/icd10clinicalconceptsorthopedics1.pdf
- 04outsourcestrategies.comhttps://www.outsourcestrategies.com/blog/icd-10-coding-for-cervical-disc-disorders-displacements/
- 05icdcodes.aihttps://icdcodes.ai/diagnosis/cervical/documentation
- 06aapc.comhttps://www.aapc.com/codes/icd-10-codes/M50.90
Mira AI Scribe
Mira's AI scribe captures cervical region specificity (high, mid, or cervicothoracic), documented neurological findings (Spurling's test result, dermatomal pattern, reflex changes), and any imaging impressions naming the disc level and pathology type. That capture prevents the scribe from defaulting to M50.90 when the encounter record actually supports a level-specific M50 code — protecting specificity and reducing the audit flag that unspecified cervical disc codes draw when imaging is on file.
See how Mira captures M50.90 documentation