ICD-10-CM · Multi-region

M02.19

Reactive joint inflammation affecting multiple anatomical sites, occurring as a sequela of dysenteric gastrointestinal infection — classified under postinfective and reactive arthropathies.

Verified May 8, 2026 · 4 sources ↓

Status
Billable
Chapter
13
Related CPT
10
Region
Multi-region
Drawn from CDCICD10DataAAPC

Documentation tips

What should appear in the chart to support M02.19.

Source · Editorial brief grounded in 4 cited references ↓

  • Name every affected joint explicitly — knee, ankle, wrist, etc. — so the multi-site selection is defensible on audit rather than defaulting to unspecified.
  • Document the triggering enteric infection by pathogen when known (e.g., Yersinia enterocolitica, Shigella species) to support the required 'code first underlying disease' sequencing instruction.
  • Record the timeline: onset of GI illness, resolution or persistence of infection, and emergence of joint symptoms — this distinguishes reactive arthropathy from primary inflammatory arthritis.
  • Note the sterile nature of joint involvement (negative cultures or clinical reasoning) to differentiate from septic arthritis, which would fall under M00.x codes.
  • If prior conservative management has been trialed (NSAIDs, physical therapy), document that history to support medical necessity for advanced imaging or specialist referral.

Related CPT procedures

Procedure codes commonly billed with M02.19. 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 M02.19 and adjacent codes.

Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓

  • Failing to sequence the underlying enteric infection code first — M02.19 is a manifestation code with a 'code first' instruction; leading with M02.19 alone will trigger a sequencing flag.
  • Using M02.19 when only one joint is involved — if the record documents a single site, drop to the appropriate site-specific M02.1x code (e.g., M02.161 for right knee).
  • Confusing postdysenteric arthropathy with other reactive arthropathies in M02 — postimmunization (M02.2x) and arthropathy following intestinal bypass (M02.0x) are separate subcategories with distinct etiologies.
  • Defaulting to M02.10 (unspecified site) when multi-site involvement is clearly documented — use M02.19 for multiple sites, not the unspecified-site code.
  • Omitting ICD-10 codes for active or recent enteric infection when still clinically relevant, leaving payers without a complete picture of the episode of care.

Clinical context

Source · Editorial summary grounded in 4 cited references ↓

M02.19 applies when a patient develops arthropathy at multiple joint sites following a dysenteric illness (e.g., Shigella, Salmonella, Campylobacter, or Yersinia enterocolitica infection). The joint involvement is sterile — no organism is present in the joint — but the immune response to the enteric infection drives synovial inflammation. Use M02.19 only when two or more distinct joint regions are documented as affected; if involvement is limited to a single named joint, select the site-specific code within M02.1x instead.

ICD-10-CM sequencing rules require you to code first the underlying disease. Common underlying codes include A04.6 (enteritis due to Yersinia enterocolitica), the appropriate Shigella code from A03.x, or other enteric infection codes. M02.19 is listed as an additional diagnosis, not the principal diagnosis, when the triggering infection is still active or documented. If the infectious episode is resolved and only the joint sequela remains, clinical judgment guides sequencing — document the reasoning.

M02.19 sits within the M02.1 subcategory (Postdysenteric arthropathy). The full M02.1 family offers laterality-specific codes for shoulder, elbow, wrist, hand, hip, knee, ankle/foot, and vertebrae. Use M02.19 only when the clinical record explicitly documents polyarticular or multi-site involvement that cannot be adequately captured by a single site-specific code. Unspecified-site claims at M02.10 should be avoided if the record names the joints involved.

Sibling codes

Other billable codes under M02.1 (laterality / anatomic variants).

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 4 cited references ↓

01Can I use M02.19 as the principal diagnosis?
Generally no. The ICD-10-CM Tabular List carries a 'code first underlying disease' instruction for M02.1x codes. The enteric infection code (e.g., A04.6, A03.x) should sequence first when the infection is active or documented. If the infection has fully resolved and only the arthropathy remains, clinical documentation must support leading with M02.19 — but this is the exception, not the rule.
02What distinguishes M02.19 from M02.10?
M02.10 is unspecified site — use it only when the record does not name any specific joints. M02.19 is multiple sites — use it when two or more distinct joint regions are explicitly documented. If the chart names the joints, the unspecified-site code is not appropriate and may trigger a specificity query on audit.
03Which enteric pathogens are typically associated with postdysenteric arthropathy?
Shigella, Salmonella, Campylobacter, and Yersinia enterocolitica are the most commonly documented triggers. The specific organism determines which underlying infection code you sequence first (e.g., A04.6 for Yersinia, A03.x for Shigella). If the pathogen is unidentified, use the most specific enteric infection code supported by the documentation.
04How does M02.19 differ from reactive arthritis (M02.3x)?
Both fall under M02, but reactive arthritis (formerly Reiter's syndrome, M02.3x) is typically triggered by urogenital infections (Chlamydia trachomatis) and classically presents with the triad of arthritis, urethritis, and conjunctivitis. Postdysenteric arthropathy (M02.1x) follows gastrointestinal dysenteric illness. Pathogen history and clinical presentation drive the distinction.
05Should I code each individual joint separately in addition to M02.19?
No. M02.19 is the single billable code for multi-site postdysenteric arthropathy. You do not stack individual site-specific M02.1x codes alongside it. Use M02.19 when the clinical picture is polyarticular and the record supports multiple joint involvement.
06Does M02.19 require a 7th character extension?
No. M02.19 is a 5-character M-code. The 7th-character extension convention (A/D/S) applies to injury S-codes, not to M-category musculoskeletal codes. M02.19 is valid as coded.
07What imaging or lab findings should be documented to support M02.19?
Document joint effusion or synovitis on imaging, negative joint cultures (ruling out septic arthritis), and positive or presumptive enteric infection history (stool culture, serology, or clinical diagnosis). Elevated inflammatory markers (ESR, CRP) support reactive arthropathy but are not required for the code itself.

Sources & references

Editorial content was developed using the following public sources. Last verified May 8, 2026.

  1. 01CDC ICD-10-CM Tabular List 2026
  2. 02
    icd10data.com
    https://www.icd10data.com/ICD10CM/Codes/M00-M99/M00-M02/M02-/M02.19
  3. 03
    aapc.com
    https://www.aapc.com/codes/icd-10-codes/M02.1
  4. 04
    icd10data.com
    https://www.icd10data.com/ICD10CM/Codes/M00-M99/M00-M02/M02-

Mira AI Scribe

Mira captures the documented joint sites (e.g., bilateral knees, right ankle, left wrist), the precipitating enteric illness with pathogen if identified, symptom onset relative to GI infection, and any workup ruling out septic or primary inflammatory arthritis. This prevents sequencing errors, supports the multi-site code selection over unspecified, and ensures the required underlying infection code is queued for correct claim ordering.

See how Mira captures M02.19 documentation

Related ICD-10 codes

Ready?

Ready to transform your orthopedic practice?

See how orthopedic practices are running documentation, billing, and operations on a single voice-first platform.

Get started for free