Key Takeaways
ICD-10 code M36.4 describes arthropathy in hypersensitivity reactions classified elsewhere, a billable 2026 ICD-10-CM code effective October 1, 2025
M36.4 is a manifestation code: the underlying hypersensitivity condition must always be coded first before M36.4
Common coding errors include using M36.4 alone without the required etiology code and confusing it with drug-induced arthropathy codes
Pabau’s claims management software supports accurate ICD-10-CM code selection and dual-code validation to reduce claim denials
ICD-10 code M36.4 covers arthropathy that develops from a hypersensitivity reaction diagnosed elsewhere in the chart. It’s a manifestation code, so it can never stand alone on a claim. The underlying hypersensitivity condition has to be coded first, or the claim bounces back. That single sequencing rule causes more denials on this code than anything else. Get it right before you submit.
You’ll see M36.4 most often in rheumatology, immunology, and internal medicine. It also shows up in musculoskeletal specialties such as physical therapy and osteopathic practice. That happens whenever a patient’s joint symptoms trace back to a systemic immune reaction rather than a standalone joint problem.
The 2026 ICD-10-CM edition, effective October 1, 2025, keeps the code active and billable for exactly that presentation.
What ICD-10 code M36.4 actually covers
ICD-10 code M36.4 has a single official description: Arthropathy in hypersensitivity reactions classified elsewhere. It’s a billable, specific code valid for reimbursement in the 2026 ICD-10-CM edition. The code became effective on October 1, 2025. It replaces any prior-year version for claims with service dates on or after that date.
Where M36.4 sits inside the M36 code family
M36.4 sits inside the M30-M36 block covering systemic connective tissue disorders within the larger M00-M99 musculoskeletal chapter. The parent code M36 is non-billable, so coders must always use a specific subcode. The M36 group’s other subcodes, including M36.8 for less specific presentations, appear in the table below.
Each subcode in the M36 group follows the same structural rule. The underlying disease responsible for the systemic or joint manifestation must be coded first. M36.4 is not unique in this respect. The etiology-manifestation convention applies across the entire M36 category.
What arthropathy in a hypersensitivity reaction looks like
Arthropathy in hypersensitivity reactions means joint inflammation or damage that shows up as a consequence of a systemic immune hypersensitivity condition. It’s not a standalone joint disease. The joint involvement is secondary. The hypersensitivity disorder is the primary diagnosis, and the arthropathy is simply where it lands in the body.
The phrase “classified elsewhere” in the code description signals that the underlying hypersensitivity condition has its own ICD-10-CM code in a different chapter. That’s typically Chapter 19 or Chapter 20. M36.4 captures only the joint manifestation, never the reaction itself.
Is there an official synonym list for M36.4?
No, despite what some reference pages imply. ICD-10-CM doesn’t publish an approximate-synonym list for M36.4 the way it does for many more common codes. What follows is plain-language phrasing drawn from how coders and clinicians actually describe this presentation, not an official index entry:
- Arthropathy due to hypersensitivity reaction
- Joint disorder in serum sickness
- Hypersensitivity arthropathy
- Arthritis in hypersensitivity disorder
- Joint disease in immune hypersensitivity reaction
If the chart uses language like this, M36.4 is still the right code for the joint component. That holds as long as the underlying hypersensitivity condition is documented as a separate diagnosis. Just confirm it against the code’s tabular list description, not a synonym list that doesn’t actually exist.
How to sequence M36.4 correctly on a claim
The etiology-manifestation coding convention is the most important rule governing M36.4, and it isn’t unique to this code. I32 follows the identical logic for pericarditis diagnosed alongside another disease. The CMS ICD-10-CM guidelines define the convention clearly. When a condition has both an underlying etiology and a manifestation, the etiology code comes first, and the manifestation code follows.
Why the underlying disease has to be coded first
M36.4 carries a “Code first” instruction in the ICD-10-CM tabular list, and that instruction isn’t optional. The coder has to identify the underlying hypersensitivity condition and code it first, before listing M36.4. Submitting M36.4 alone as the primary diagnosis is incorrect, and it’s a common reason claims get denied.
Correct sequencing for musculoskeletal compliance requirements in this code category follows a simple order:
- Step 1: Identify the underlying hypersensitivity condition from clinical documentation
- Step 2: Assign the ICD-10-CM code for that underlying condition (from the appropriate chapter)
- Step 3: List M36.4 as a secondary code to capture the arthropathy manifestation
- Step 4: Verify that the clinical documentation supports both the underlying diagnosis and the joint involvement
The CDC/NCHS ICD-10-CM web tool confirms the etiology-manifestation convention applies wherever a “Code first” note appears in the tabular list. M36.4 is one of many codes that carries it.
When M14 codes should be used instead of M36.4
M36 itself, the parent category, carries a Type 2 Excludes note (Excludes2) pointing to M14, arthropathies in other diseases classified elsewhere. An Excludes2 note works differently than people expect. It means the M14 conditions aren’t part of M36. A coder can still report both together when the documentation supports it. That’s the opposite of a hard exclusion.
The note that actually points to M36.4 lives under M14, not M36. M14 carries its own Excludes1 note. None of the conditions on that list should ever be coded under M14, because a more specific code already exists for each one:
- Diabetes mellitus → E08–E13 with the .61- subcode
- Hematological disorders → M36.2- or M36.3
- Hypersensitivity reactions → M36.4
- Neoplastic disease → M36.1
- Neurosyphilis → A52.16
- Sarcoidosis → D86.86
- Enteropathic arthropathy → M07.-
- Juvenile psoriatic arthropathy → L40.54
- Lipoid dermatoarthritis → E78.81
The practical rule is simple. When a hypersensitivity reaction is driving the joint problem, M36.4 replaces an M14 code, not the other way round. The same logic applies to every other cause on that list. Each one has its own specific code instead of M14.
Pro Tip
Run a documentation check before assigning M36.4. Confirm the chart names a hypersensitivity reaction as the cause of the joint involvement, not diabetes or another endocrine condition. If the cause is ambiguous, query the provider before submitting the claim.
Related arthropathy codes coders confuse with M36.4
Differential coding for M36.4 means knowing the neighboring arthropathy codes too. M14.88 covers arthropathies tied to other diseases classified elsewhere, when no more specific match applies. The table below maps the most relevant sibling and adjacent codes for arthropathy presentations.
M36.4 vs the other arthropathy codes: How to choose
The distinguishing factor for M36.4 is the nature of the underlying cause: a hypersensitivity or immune-mediated reaction. Here’s the decision logic coders need.
Use M36.4 when: the clinical documentation explicitly links joint inflammation or damage to a hypersensitivity reaction, such as serum sickness or a drug hypersensitivity response. The underlying condition also needs its own code in another ICD-10-CM chapter.
Do not use M36.4 when the arthropathy traces back to one of these causes instead. The underlying cause determines the code, not the joint symptoms.
- Diabetes mellitus (route to E08–E13 with the .61- subcode)
- A metabolic condition such as gout (route to M10.-)
- A malignancy (route to M36.1)
- A psoriatic skin condition (route to L40.5-)
Ambiguous presentations need extra care. If the notes document joint pain during a drug reaction but don’t explicitly attribute the joint involvement to that reaction, query the provider. Presuming the link without documentation creates audit risk. M36.4 requires documented causation, not coincidence.
Simplify ICD-10 coding in your clinical workflow
Pabau embeds ICD-10-CM code selection directly into your charting and billing workflow, so coders spend less time switching between reference tools and more time getting claims right the first time.
What payers expect before they’ll reimburse M36.4
M36.4 is billable, meaning it can be submitted on a claim for reimbursement, but billable status doesn’t guarantee payment. Payer-specific coverage policies vary. M36.4 gets denied when the sequencing rules aren’t followed. It also gets denied when the documentation doesn’t support both the underlying hypersensitivity condition and the joint manifestation.
Key billing requirements for claims management software users and billing teams:

- Dual-code sequencing: The etiology code must appear before M36.4 in the diagnosis code field. Many clearinghouses will flag or reject claims where a “Code first” manifestation code appears without a corresponding etiology code.
- Documentation specificity: The clinical record must name the hypersensitivity condition and describe the joint involvement as a consequence of it.
- Medical necessity: Payers expect the treating diagnosis to justify the procedure codes billed. If the visit is for managing the joint symptoms, both the etiology and M36.4 should appear in the claim.
- Payer-specific policies: Some Medicare Administrative Contractors and commercial payers have specific Local Coverage Determinations that affect reimbursement for secondary manifestation codes. Verify payer policy before submitting.
Good medical documentation forms and templated clinical notes go a long way toward reducing coding ambiguity at billing time. Structured intake and progress note templates help. When they prompt clinicians to document the causal relationship between conditions, the resulting records support M36.4 correctly.
For practices that want documentation and billing in the same system, practice management software can connect the two. That closes the manual handoff where these errors typically occur.
Pro Tip
Flag M36.4 claims for documentation review before submission. Confirm the chart contains a provider statement linking the joint disorder to the specific hypersensitivity reaction. A one-sentence note from the clinician explicitly connecting the two diagnoses is enough to satisfy most payer auditors.
How Pabau keeps etiology and manifestation codes in sync
Coders using standalone reference tools have to context-switch constantly. They move between the lookup page, the EHR, and the billing system every time they assign a code like M36.4. That three-step process is where sequencing errors happen. Pabau addresses this through EHR integration for coding workflows. It keeps the code selection, the clinical record, and the claim in the same system.
For connective tissue and musculoskeletal cases involving manifestation codes, Pabau’s client record and documentation tools help. Clinicians can document the underlying diagnosis and its joint manifestation in structured fields during the visit. That documentation flows directly into the billing workflow, so the etiology code is less likely to get missed at submission.
The AAPC Codify ICD-10-CM lookup is a useful external reference for code validation alongside any workflow tool.
The takeaway on coding M36.4 correctly
M36.4 is one of those codes where getting the sequence wrong is the real coding risk. The code is billable, current for 2026, and straightforward in its clinical meaning. The problem is always the same. Either the claim gets submitted without the etiology code first. Or the code gets applied when the joint involvement actually comes from a metabolic, endocrine, or neoplastic cause instead of a hypersensitivity reaction.
Practices that connect their clinical documentation to billing in a single system are better positioned to avoid that error. Practice management software like Pabau keeps the etiology and manifestation codes tied to the same patient record at the point of care. That beats leaving it as something a coder has to reconstruct later.
If claim denials on manifestation codes are a recurring headache, it’s worth seeing how that connected workflow fits your practice.
Continue your research
Confusing M36.4 with the neoplastic-disease variant? M36.1 covers the same manifestation pattern when the arthropathy is driven by cancer instead of a hypersensitivity reaction.
Coding a blood-disorder case instead? M36.3 is the sibling code for arthropathy tied to other blood disorders.
Need the wider connective-tissue picture? M35.4 covers a related systemic connective tissue presentation in the same M30-M36 block.
Working a straightforward joint case instead? M16.9 is the code for unspecified osteoarthritis of the hip, without an underlying systemic cause.
Frequently asked questions
What is ICD-10 code M36.4?
M36.4 is a billable ICD-10-CM code for arthropathy, a joint disorder, that develops as a manifestation of a hypersensitivity reaction diagnosed and coded elsewhere in the chart.
What conditions are excluded from M36.4?
M36 carries an Excludes2 note for M14, arthropathies in other diseases classified elsewhere, meaning M14 conditions aren’t part of M36 but can still be coded alongside it. The note that matters for M36.4 sits under M14 itself: an Excludes1 note there redirects hypersensitivity-driven arthropathy to M36.4, diabetes-related arthropathy to E08–E13.61-, and blood-disorder arthropathy to M36.2- or M36.3. Use M36.4 specifically when a hypersensitivity reaction, not another cause, is documented as driving the joint involvement.
Does M36.4 need a laterality or 7th character?
No. M36.4 is complete at five characters. Unlike many musculoskeletal codes, it doesn’t take a laterality digit or a 7th character, so the same code applies regardless of which joint or side is affected.
How is M36.4 different from a drug-reaction T-code?
T-codes capture the adverse drug reaction or hypersensitivity event itself. M36.4 captures only the joint damage that results from it. The two get reported together, with the T-code sequenced first, not used interchangeably.