Skip to main content

M10.332 vs M10.339

M10.332 (Gout due to renal impairment, left wrist) compared with M10.339 (Gout due to renal impairment, unspecified wrist), from the official CMS tabular data. M10.332 and M10.339 code the same condition on opposite sides. MedCoder-derived

Relationship

Review

Laterality relationship

M10.332
Left
Gout due to renal impairment, left wrist
M10.339
Unspecified
Gout due to renal impairment, unspecified wrist

Same condition; these differ only in which side is documented.

These codes share a category and title and differ only in the side affected. The documentation decides which applies, and a bilateral code is reported only where the code set provides one.

Source: ICD-10-CM tabular list (laterality variant derived from the code title)

Can these codes be reported together?

Same condition, opposite side. M10.332 and M10.339 name the same condition on opposite sides of the body.

Same category and title, differing only in which side is affected — the documentation decides which one applies, and a bilateral code is reported only where the code set provides one.

Side by side

M10.332Gout due to renal impairment, left wristM10.339Gout due to renal impairment, unspecified wrist
Billing statusBillableBillable
ClassificationM00-M99 — Diseases of the musculoskeletal system and connective tissueM00-M99 — Diseases of the musculoskeletal system and connective tissue
DefinitionGout due to renal impairment, left wrist is a billable ICD-10-CM diagnosis code (M10.332).Gout due to renal impairment, unspecified wrist is a billable ICD-10-CM diagnosis code (M10.339).
Use additional code
code to identify:
Autonomic neuropathy in diseases classified elsewhere (G99.0)
Calculus of urinary tract in diseases classified elsewhere (N22)
code to identify:
Autonomic neuropathy in diseases classified elsewhere (G99.0)
Calculus of urinary tract in diseases classified elsewhere (N22)
Code first
associated renal disease
associated renal disease

Derived from the official CMS ICD-10-CM tabular data (FY2026). Not billing advice; verify sequencing rules for the encounter. All data sources