ICD-10 Code M10.9: Gout, unspecified

Key Takeaways

ICD-10 Code M10.9 (Gout, unspecified) is a billable FY2026 diagnosis code, effective October 1, 2025, used when gout type or joint site is not documented

Use M10.9 only when the provider cannot or does not specify gout type (primary, secondary, drug-induced) or anatomical site — more specific M10.0x-M10.4x codes are preferred when documentation allows

Payers increasingly flag unspecified codes for scrutiny — supporting documentation must confirm gout diagnosis, absence of site specificity, and relevant labs (serum uric acid)

Pabau’s clinical documentation and claims management tools help practices capture the specificity needed to support accurate ICD-10 coding at the point of care

ICD-10 Code M10.9 (Gout, unspecified) is a valid, billable ICD-10-CM diagnosis code for FY2026, effective October 1, 2025. According to the CDC/NCHS ICD-10-CM web tool, the code applies when a provider diagnoses gout but cannot specify the type or the affected joint site.

Gout is one of the most common forms of inflammatory arthritis in the United States, and it’s also one of the most frequently miscoded diagnoses in outpatient and inpatient settings. This reference covers the code hierarchy, coding guidelines, documentation requirements, associated CPT codes, and common errors.

M10.9 is confirmed active for FY2026, effective October 1, 2025, and valid for all HIPAA-covered electronic transactions.

ICD-10 Code M10.9: Definition, billable status, and FY2026 validity

M10.9 in the ICD-10-CM hierarchy

M10.9 sits at the bottom of the M10 block as the residual “unspecified” code. The M10 category covers all gout types and joint sites, structured as a hierarchy of increasingly specific codes. The same pattern, specificity codes preceding the unspecified catch-all, repeats throughout ICD-10-CM, including in codes like M72.0.

The M10 block organizes gout by type first, then site. Each type uses a fifth digit to capture the joint involved (0 = unspecified site, 1 = shoulder, 2 = elbow, 3 = wrist, 4 = hand, 5 = hip, 6 = knee, 7 = ankle and foot, 9 = multiple sites). M10.9 bypasses both dimensions entirely.

When to use M10.9 vs more specific gout codes

The ICD-10-CM official guidelines require the highest level of specificity supported by the clinical documentation. M10.9 is only appropriate when the provider’s note genuinely cannot support a more specific code. This is the single biggest compliance risk with gout coding.

Practices managing complex musculoskeletal caseloads benefit from physical therapy EMR workflows that prompt documentation specificity at the point of care, before coding occurs.

ICD-10-CM coding guidelines for M10.9

The official CMS ICD-10-CM guidelines include specific instructional notes for the M10 category. These notes aren’t optional. Payers use them to validate claim submissions alongside the diagnosis code.

Practices that rely on external reference tools rather than point-of-care systems risk missing these instructions when coding in real time. The same principle applies to codes like M25.9, where these instructional notes need to be built into the clinical workflow rather than applied retroactively.

Use-additional-code instructions

When M10.9 is the primary diagnosis, the tabular list instructs coders to assign additional codes for associated conditions where documented:

• G99.0 – Autonomic neuropathy in diseases classified elsewhere. Assign if the provider documents autonomic involvement secondary to gout.
• N22 – Calculus of urinary tract in diseases classified elsewhere. Assign if uric acid kidney stones are documented alongside the gout diagnosis.
• I43 – Cardiomyopathy in diseases classified elsewhere. Assign when the provider links a cardiomyopathy diagnosis to the underlying gout.
• H61.1-, H62.8- – Disorders of external ear in diseases classified elsewhere. Assign if gout-related involvement of the external ear is documented.
• H22 – Disorders of iris and ciliary body in diseases classified elsewhere. Assign if the provider documents ocular involvement secondary to gout.
• N08 – Glomerular disorders in diseases classified elsewhere. Assign if gout-related kidney involvement affecting the glomeruli is documented.

Hyperuricemia (E79.0) doesn’t appear on this official tabular list, but it’s commonly documented alongside gout. When elevated serum uric acid is confirmed by lab testing, coding E79.0 separately captures that finding and supports the gout diagnosis.

Excludes notes

M10 (and by inheritance M10.9) carries a Type 2 Excludes note for chronic gout (M1A.-). A Type 2 Excludes note means the excluded condition isn’t part of M10.9’s concept, but both codes may be reported together for the same patient when the documentation supports it.

That’s different from a Type 1 Excludes note, where the two codes can never be used together on the same claim.

There is no Type 1 Excludes note under M10. When the clinical picture describes chronic tophaceous gout rather than an acute or undetermined presentation, code M1A.9 (chronic gout, unspecified) instead of M10.9.

Documentation requirements for M10.9

Payers increasingly scrutinize unspecified diagnosis codes. An M10.9 claim without supporting documentation is a denial waiting to happen. The clinical record must clearly justify the absence of specificity, not just state the diagnosis.

Transitioning to digital intake forms and structured clinical notes helps practices capture the specificity coders need before the encounter is over. Pairing those forms with HIPAA-compliant documentation practices ensures the record meets both coding and regulatory standards.

• Confirmed gout diagnosis: the provider’s note must state gout as the working or confirmed diagnosis, not just “joint pain” or “possible gout.”
• Absence of site or type specificity: the record must reflect that the site or type could not be determined, or that the provider did not document it. A note that mentions “right knee pain” but codes M10.9 is a documentation-coding mismatch.
• Laboratory results: serum uric acid level (CPT 84550) supports the diagnosis. Hyperuricemia (E79.0) should be coded additionally if documented.
• Joint assessment: documentation of which joint was examined, even if inconclusive, strengthens the record and may prompt a more specific code upon review.
• Clinical reasoning: a brief note explaining why gout type could not be determined (for example, first presentation without crystal confirmation) provides audit protection for M10.9.

Associated CPT codes for gout management

Gout management typically spans evaluation, laboratory testing, and procedural intervention. According to the AAPC ICD-10-CM code reference, M10.9 pairs with a predictable set of CPT codes depending on the clinical scenario. Each CPT-to-ICD-10 pairing must be medically necessary and supported by the encounter documentation.

Struggling with ICD-10 coding accuracy?

Pabau helps clinical teams capture the documentation specificity needed to support accurate ICD-10 coding, reducing denials and streamlining claim submission from a single platform.

Book a demo

Common coding errors with M10.9

The most costly mistakes with gout coding are systematic, not occasional. They arise from workflow breakdowns where documentation specificity is available but not captured at the coding stage.

• Using M10.9 when site is documented: if the provider’s note references a specific joint (even informally, such as “right big toe swelling”), a site-specific M10 code is required. M10.9 is not a safe default when the record contains joint information.
• Omitting E79.0 for hyperuricemia: elevated serum uric acid is documented in most gout encounters. Failing to add E79.0 as a secondary code leaves a clinically relevant finding uncaptured and may trigger medical necessity reviews.
• Confusing gout with pseudogout: pseudogout (calcium pyrophosphate crystal deposition) is coded M11.20-M11.29, not M10.9. The clinical distinction requires crystal analysis. When crystal type is unconfirmed, the documentation should reflect that uncertainty before coding either condition.
• Skipping code-first sequencing for drug-induced gout: when gout is caused by a specific medication, the adverse effect or external cause code must sequence before M10.2x. Using M10.9 bypasses this sequencing requirement and obscures the underlying cause from the claim.
• Applying M10.9 to chronic gout with tophi: chronic tophaceous gout belongs under the M1A category. Chronic and acute presentations are coded differently, and M10.9 is not appropriate for established tophaceous disease.

Differential diagnosis codes: gout vs related conditions

Gout shares clinical features with several other inflammatory arthropathies. When the diagnosis is uncertain or when coders encounter notes that reference multiple differential diagnoses, distinguishing these conditions in the ICD-10 system matters for both coding accuracy and payer compliance. The same specificity requirement applies to codes like M94.0, across specialties throughout the classification system.

Billing and reimbursement considerations for ICD-10 Code M10.9

Billing with M10.9 carries a specific reimbursement risk: payers consider it an unspecified code and may apply additional scrutiny to claims that use it when the encounter documentation could support greater specificity. Using the right claims management software helps practice teams catch these issues before submission rather than after denial.

MS-DRG groupings

For inpatient admissions, gout-related diagnoses may group to MS-DRG 555 (signs and symptoms of musculoskeletal system and connective tissue, with MCC) or 556 (without MCC), according to CMS MS-DRG grouper logic. This is a two-tier split. MS-DRG 557 is a separate grouping for tendonitis, myositis, and bursitis with MCC, and it doesn’t apply to gout coding.

The specific DRG assignment depends on the full diagnosis cluster and comorbidities, not M10.9 alone. Verify against the current CMS FY2026 grouper tables for your patient population.

Payer behavior with unspecified codes

Many payers, including Medicare Advantage plans, publish local coverage determinations (LCDs) that flag unspecified codes for prepayment review. M10.9 may trigger a medical records request where a more specific M10 code would not. Building compliance management tools into the coding workflow reduces this exposure by prompting documentation completeness before the claim is submitted.

How Pabau supports accurate ICD-10 Code M10.9 documentation

Standalone coding reference tools tell coders what a code means. They cannot enforce documentation completeness at the point of care. That disconnect, where the provider finishes the encounter and the coder works from an incomplete note, is where most M10.9 misuse originates.

Pabau’s clinical notes and charting tools help providers structure their documentation around the specificity coders need: joint site, gout type, associated labs, and clinical reasoning. The platform supports paperless clinical documentation that travels with the patient record rather than sitting in a disconnected reference system.

When the note is complete before the patient leaves, coding M10.9 vs a specific M10 code becomes a clinical decision, not a documentation workaround.

For practices managing clinical records and charting, Pabau integrates diagnosis coding context into the encounter workflow. Supporting EHR integration across clinical practices allows coding teams to work from structured clinical data rather than freeform notes, reducing transcription errors and improving code specificity across the patient caseload.

Conclusion

M10.9 is a legitimate, billable code for genuine clinical uncertainty, not a convenience code for incomplete documentation. Payers know the difference, and so do post-payment auditors.

Practices that build documentation specificity into their clinical workflow, before coding begins, see fewer denials, faster reimbursement, and cleaner audit trails. Pabau’s clinical records and claims tools help practices get there without adding administrative burden to the clinical team. To see how Pabau supports coding accuracy across your practice, book a demo.

Continue your research

Need a structured approach to musculoskeletal documentation? Sports medicine software shows how structured clinical workflows support accurate condition coding and follow-up care.

Managing compliance across your practice? Physiotherapy compliance requirements covers the documentation and regulatory requirements that apply to musculoskeletal practices.

Exploring how EHR tools support better coding? Practice management vs EMR explains how integrated platforms close the disconnect between documentation and coding that causes unspecified code overuse.

Frequently Asked Questions