Skip to main content

I21.9 vs I5A

I21.9 (Acute myocardial infarction, unspecified) compared with I5A (Non-ischemic myocardial injury (non-traumatic)), from the official CMS tabular data.

Current data releases:ICD-10-CM FY2027 · ICD-10-PCS FY2027 · HCPCS October 2026 · MS-DRG v44 · Medicare Code Editor v44.0 · NCCI PTP Q4 2026 · MUE Q4 2026 · NCD code lists 2026-01 · LCD export September 28, 2026 · All releases and sources

Summary

These codes should not be reported together because I5A’s tabular entry lists I21.9 under Excludes1.

Official rule
What is different?

The conditions named.I21.9 is “Acute myocardial infarction, unspecified”; I5A is “Non-ischemic myocardial injury (non-traumatic)”.

Registry fact

Can these codes be reported together?

No.I5A’s entry carries an Excludes1 note covering I21.9: “acute myocardial infarction (I21.-)”. Both may be reported only when the documentation shows the two conditions are unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes1 relationship?

Yes.I5A’s tabular entry: “acute myocardial infarction (I21.-)”. The note covers I21.9.

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes2 relationship?

None.Neither entry carries an Excludes2 note that names the other code. I21.9 carries 3 Excludes2 notes and I5A carries 1 Excludes2 note covering other codes; the side-by-side table quotes them.

Official rule

Is one more specific?

Not comparable.The codes sit in different categories; specificity is only comparable within one category.

Is one a parent or header code?

No.Both are billable codes, and neither contains the other.

Registry fact

Are there sequencing instructions?

None.Neither entry carries a Code First or Use Additional Code note that names the other.

Official rule

Are there other coding relationships?

None found.No laterality, encounter-phase, Table of Neoplasms, Table of Drugs and Chemicals, or history-versus-active-disease relationship links these codes.

MedCoder-derived

Official rule: a tabular instructional note or a section of the ICD-10-CM Official Guidelines, quoted as published. Registry fact: the codes’ own published attributes (titles, billable status, position in the hierarchy, code set). MedCoder-derived: a reading MedCoder computes from those facts; it is not itself a rule. How to read the labels

Can these codes be reported together?

Excludes1 — generally not reported together

Excludes1 conflict

I5A
Non-ischemic myocardial injury (non-traumatic)
↔
I21.9
Acute myocardial infarction, unspecified

What we found

No — do not report together.I5A carries an Excludes1 note covering I21.9: “acute myocardial infarction (I21.-)”

Sole exception: when the two conditions are documented as unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

What to review

Report one of the two. Both may be reported only when the documentation shows the two conditions are unrelated to each other.

Guide: Excludes1 vs Excludes2Check these on a claim

Why it matters

An Excludes1 note means the two conditions are not ordinarily reported together for the same encounter, because the classification treats them as mutually exclusive forms of the same condition. The documented exception is when the two conditions are unrelated to each other.

Source / rule

CMS ICD-10-CM tabular instructional notes; ICD-10-CM Official Guidelines, Section I.A.12.a

Official guidance behind these answers

  • Section I.A.12.a — Excludes1 · applies to: Excludes1

    A type 1 Excludes note is a pure excludes note. It means “NOT CODED HERE!” An Excludes1 note indicates that the code excluded should never be used at the same time as the code above the Excludes1 note. An Excludes1 is used when two conditions cannot occur together, such as a congenital form versus an acquired form of the same condition. An exception to the Excludes1 definition is the circumstance when the two conditions are unrelated to each other. If it is not clear whether the two conditions involving an Excludes1 note are related or not, query the provider. For example, code F45.8, Other somatoform disorders, has an Excludes1 note for "sleep related teeth grinding (G47.63)," because "teeth grinding" is an inclusion term under F45.8. Only one of these two codes should be assigned for teeth grinding. However psychogenic dysmenorrhea is also an inclusion term under F45.8, and a patient could have both this condition and sleep related teeth grinding. In this case, the two conditions are clearly unrelated to each other, and so it would be appropriate to report F45.8 and G47.63 together.

    ICD-10-CM Official Guidelines FY2027

Quoted from the ICD-10-CM Official Guidelines for Coding and Reporting in effect for the release shown. The tabular notes above are the code-level instruction; these sections are the convention that says how such a note is applied. Source document (CMS PDF) · Release and checksum

Side by side

Similar descriptions do not make codes interchangeable. The documentation and the official instructions decide which code applies.

Official descriptionDiffers
I21.9

Acute myocardial infarction, unspecified

I5A

Non-ischemic myocardial injury (non-traumatic)

StatusSame for both
Billable
Excludes1Differs
I21.9

None at this code

I5A
  • acute myocardial infarction (I21.-)
  • injury of heart (S26.-)
Excludes2Differs
I21.9
  • old myocardial infarction (I25.2)
  • postmyocardial infarction syndrome (I24.1)
  • subsequent type 1 myocardial infarction (I22.-)
I5A
  • other acute ischemic heart diseases (I24.-)
Code firstDiffers
I21.9

None at this code

I5A
  • the underlying cause, if known and applicable, such as:
  • acute kidney failure (N17.-)
Use additional codeDiffers
I21.9
  • code, if applicable, to identify:
  • exposure to environmental tobacco smoke (Z77.22)
  • history of tobacco dependence (Z87.891)
I5A

None at this code

Code alsoDiffers
I21.9
  • the presence of hypertension (I10-I1A)
I5A

None at this code

CategoryDiffers
I21.9

I21 Acute myocardial infarction

I5A

Is itself a category

ChapterSame for both

I00-I99 — Diseases of the Circulatory System (I00-I99)

IncludesDiffers
I21.9
  • cardiac infarction
  • coronary (artery) embolism
  • coronary (artery) occlusion
  • coronary (artery) rupture
I5A
  • Acute (non-ischemic) myocardial injury
  • Chronic (non-ischemic) myocardial injury
  • Unspecified (non-ischemic) myocardial injury

No 7th character note at either code.

Notes are the code’s own tabular entry, quoted as published. A note that names the other code is the one the verdict above rests on. In a row that differs, notes every code shares are dimmed.

Editorial explanation — not an official CMS/CDC rule. Official coding instructions and source material are identified below. How to read the labels

The distinction

Both describe damaged myocardium, and a raised troponin is common to each — but I21.9 asserts an infarction, meaning ischemia caused the damage, while I5A asserts myocardial injury that is explicitly non-ischemic and non-traumatic. Because acute myocardial infarction is an Excludes1 on I5A, exactly one of them describes a given event.

The deciding question

Does the provider attribute the myocardial damage to ischemia?

An ischemic mechanism — documented infarction, whether or not the type is specified — selects the I21.- family, with I21.9 as the unspecified form. A troponin elevation the provider attributes to something else entirely (sepsis, heart failure, renal failure, myocarditis, takotsubo syndrome, pulmonary embolism, hypertensive urgency, and the rest of I5A’s Code First list) is non-ischemic myocardial injury, and I5A sequences that underlying cause first. Traumatic cardiac injury is neither: S26.- covers it, also by Excludes1.

Worked examples

Landing on I21.9

A patient presents with chest pain and rising troponin, and the provider documents an acute myocardial infarction without specifying the type.

  1. I21.9 — Acute myocardial infarction, unspecified (first-listed)

A documented type (STEMI/NSTEMI with site) selects the more specific I21.- code instead; I21.9 is the unspecified floor.

Landing on I5A

A septic patient has an elevated troponin the provider documents as non-ischemic myocardial injury due to the sepsis.

  1. A41.9 — Sepsis, unspecified organism (sequenced first (the underlying cause))
  2. I5A — Non-ischemic myocardial injury (non-traumatic) (secondary)

Sepsis is named on I5A’s Code First list; the specific organism code replaces A41.9 when the record identifies one.

Why coders confuse them

The troponin result is the same signal in both, and for years the classification had no home for “elevated troponin, not an MI” — so the reflex was to reach for an infarction code or an unspecified heart-disease code. I5A exists to end that, and its Excludes1 against I21.- is what makes the choice binary rather than additive.

The other trap runs through acuity. I5A’s inclusion terms cover acute, chronic, and unspecified injury alike, so there is no acute-versus-chronic decision to make on this code — while on the infarction side the acuity and site drive the code selection entirely.

FAQ

Can I5A and an acute MI code be reported together?

Not for the same event — acute myocardial infarction (I21.-) is an Excludes1 on I5A. The documented mechanism decides which one applies.

What code covers a troponin rise from trauma?

Neither of these. Injury of heart (S26.-) is also an Excludes1 on I5A, and I5A’s own title says non-traumatic, so a traumatic cardiac injury is coded in Chapter 19.

Does I5A need a code for the cause?

Yes when the cause is known and applicable: I5A carries a Code First note listing acute kidney failure, myocarditis, cardiomyopathy, chronic kidney disease, heart failure, hypertensive urgency, nonrheumatic aortic valve disorders, paroxysmal tachycardia, pulmonary embolism, pulmonary hypertension, sepsis and takotsubo syndrome.

A41.9 — Sepsis, unspecified organism (a Code First cause)

Derived from the official CMS ICD-10-CM tabular data (FY2027). A coding-rule comparison, not billing advice: payer-specific edits and medical-necessity policy are outside its scope. All data sources