Demand Ischemia ICD-10-CM Coding Guide: Type 2 Myocardial Infarction, Key Codes, and Documentation
The chart says “demand ischemia.” The lab sheet shows an elevated troponin. The patient also had sepsis and a fast heart rate. A high-value myocardial infarction code is one search away, and it is tempting to connect the dots.
That is exactly where demand ischemia ICD-10-CM coding goes wrong. Coders code what the provider documents, not what the lab values imply. This guide explains how demand ischemia, Type 2 MI, and non-ischemic myocardial injury are classified, what documentation supports each, and when a compliant query is the right move.
I24.89 Index code for demand ischemia when no MI is documented | I21.A1 Reported only when Type 2 MI is documented | I5A Non-ischemic myocardial injury, a separate concept |
Key coding distinction Demand ischemia is not automatically a Type 2 MI. If the provider documents demand ischemia without a myocardial infarction, the index leads to I24.89. If the provider documents MI due to demand ischemia or a Type 2 MI, the code is I21.A1. |
What Is Demand Ischemia?
Demand ischemia describes a mismatch between the heart muscle’s oxygen supply and its oxygen needs, often driven by a stressor such as a fast heart rate, anemia, low blood pressure, or low oxygen. It is a clinical diagnosis made by the treating provider.
Coders work with the documented diagnosis. Findings that may suggest ischemia or myocardial injury, including troponin, ECG changes, tachycardia, or sepsis, are clinical indicators. They do not become diagnoses on their own, and coders should not diagnose or upgrade a condition.
Demand Ischemia ICD-10-CM Code
The Alphabetic Index entry “Ischemia, demand (coronary)” leads to I24.89, Other forms of acute ischemic heart disease. Note that I24.8 itself is now a non-billable header with two child codes, I24.81 and I24.89, so I24.89 is the code to report. The entry “with myocardial infarction” leads to I21.A1 instead.
The Tabular List adds an Excludes1 note at I24.8 for myocardial infarction due to demand ischemia (I21.A1), meaning the two are not reported together. The final assignment depends on the Index, the Tabular, the current Official Guidelines, and the provider’s wording.
Demand Ischemia vs. Type 2 Myocardial Infarction
Consideration | Demand ischemia | Type 2 myocardial infarction |
Clinical meaning | Supply-demand mismatch causing ischemia, without a documented infarction | Infarction (myocardial injury with clinical evidence of acute ischemia) from supply-demand imbalance, not an acute plaque event |
Diagnostic support | Provider’s documented diagnosis with supporting clinical context | Provider must document myocardial infarction, supported per accepted clinical criteria |
Troponin | Rise alone does not establish the diagnosis | Elevation alone does not establish MI; it also appears in non-ischemic injury |
Coding implications | I24.89 when no MI is documented | I21.A1, with the underlying cause coded first when known |
Coder responsibility | Code the documented diagnosis | Do not infer MI; query when unclear |
Terminology alone does not settle every case. CMS’s quality contractor Livanta notes that no index path reaches Type 2 MI unless a myocardial infarction is documented.
Key ICD-10-CM Codes and Coding Considerations
Code | Official description | When it may apply | Documentation considerations |
I24.89 | Other forms of acute ischemic heart disease | Demand ischemia documented without myocardial infarction | Provider states demand ischemia; no MI documented. Confirm Excludes1 and Excludes2 notes in the Tabular |
I21.A1 | Myocardial infarction type 2 | MI due to demand ischemia or secondary to ischemic imbalance is documented | Explicit MI statement. Code first the underlying cause, if known. If described as NSTEMI or STEMI, only I21.A1 applies |
I5A | Non-ischemic myocardial injury (non-traumatic) | Provider documents non-ischemic myocardial injury | Do not use when ischemia or MI is documented as the diagnosis. Code first the underlying cause, if known |
I24.81 | Acute coronary microvascular dysfunction | Only when that specific condition is documented | Not a synonym for demand ischemia |
The Index points you to a code, the Tabular List confirms it and supplies notes such as code first, Excludes1, and Excludes2, and the guidelines add rules. The classification’s own instructions take precedence over the guidelines. Where official guidance does not give one answer for a scenario, query rather than assume. Per Livanta, I24.89 carries CC status and I21.A1 carries MCC status for MS-DRG purposes. Severity impact must never drive code selection.
Inpatient vs. outpatient Inpatient guidelines (Section II.H) allow uncertain diagnoses such as “probable” or “suspected” documented at discharge to be coded as if established. Outpatient guidelines (Section IV.H) do not. A “possible MI” in an outpatient record is not coded as MI. Do not apply one setting’s rule to the other. |
Documentation Requirements
Use this as a documentation review aid, not a substitute for clinical judgment. Look for:
• The responsible provider’s final diagnosis
• Whether myocardial infarction is actually diagnosed
• The clinical context and documented cause of the supply-demand imbalance
• Supporting evidence, as clinically appropriate
• A clear distinction between ischemia, myocardial injury, and infarction
• Conflicting terms across progress notes, discharge summary, and final assessment
• A compliant query when the record is ambiguous or inconsistent
Common Coding Errors
Error | How to avoid it |
Automatically coding demand ischemia as Type 2 MI | Require a documented myocardial infarction |
Treating elevated troponin as proof of MI | Code the provider’s diagnosis; query if only lab values appear |
Assigning a diagnosis from lab findings alone | Use labs as indicators, not diagnoses |
Ignoring official code instructions | Read every Tabular note and the guidelines |
Overlooking conflicting documentation | Compare notes and the final assessment; query conflicts |
Using an outdated code set | Use the FY in effect on the discharge or service date |
Mixing inpatient and outpatient rules | Apply the correct setting’s guidelines |
Practical Coding Scenarios
These are educational examples, not treatment advice or definitive code assignments.
Scenario | What the record establishes | What to review |
A. Provider documents demand ischemia during tachycardia; no MI diagnosed | Demand ischemia without MI | The Index entry leading to I24.89, the Excludes1 note, and whether the final summary mentions MI. Clarification is likely unnecessary if consistent |
B. Provider documents Type 2 MI with supporting clinical context and cause | Type 2 MI | I21.A1 and its code-first note for the underlying cause; confirm no conflicting terms |
C. Troponin elevated, sepsis present, final note does not state injury, ischemia, or MI | Clinical indicators only | No diagnosis can be assumed. Review the guidelines, then consider a compliant, non-leading query |
D. Outpatient note lists “possible MI” | An uncertain diagnosis | Section IV.H: uncertain diagnoses are not coded as established in outpatient settings. Review for confirmed diagnoses or symptoms |
Coding Review Before Claim Submission
Tick each item as you complete it.
☐ Has the responsible provider documented a final diagnosis?
☐ Is demand ischemia distinguished from Type 2 MI?
☐ Is myocardial infarction explicitly documented when an MI code is being considered?
☐ Have elevated troponin and other clinical indicators been interpreted appropriately rather than used as independent diagnoses?
☐ Have conflicting statements in the record been reviewed?
☐ Has the current ICD-10-CM Tabular List been checked?
☐ Have applicable sequencing and additional-code instructions been reviewed?
☐ Have the relevant inpatient or outpatient coding rules been considered?
This checklist supports coding review. It does not replace the official guidelines or provider clarification.
How Accurate Coding Supports Revenue Cycle Management
Diagnosis codes feed claim quality, audit readiness, and payer review. A code that the record does not support can invite denials, adjustments, or recoupment, and rework costs time. Structured coding reviews and compliant clarification workflows can help catch inconsistencies before submission. No process guarantees payment or claim acceptance.
Sirius Solutions Global offers medical billing, medical coding, denial management, and billing audits, along with eligibility verification, prior authorization support, credentialing, and accounts receivable support. We combine AI-assisted workflows with human verification to help organizations review coding consistency and claim quality.
Frequently Asked Questions
▸ What is the ICD-10-CM code for demand ischemia?
I24.89, via the Index entry “Ischemia, demand (coronary),” when no MI is documented. I24.8 is a non-billable header.
▸ Is demand ischemia the same as Type 2 MI?
No. Type 2 MI requires a documented myocardial infarction. Demand ischemia alone does not.
▸ Can elevated troponin alone establish Type 2 MI?
No. Troponin is a clinical indicator. The provider must document the diagnosis.
▸ What is the code for Type 2 MI?
I21.A1, Myocardial infarction type 2, with the underlying cause coded first when known.
▸ What is the difference between myocardial injury and infarction?
Injury is cell damage that may be non-ischemic (I5A). Infarction requires evidence of acute ischemia, and it must be documented as such.
▸ When should a coder request clarification?
When documentation is conflicting, incomplete, or relies on labs without a diagnosis. Follow your organization’s compliant query policy.
▸ Can demand ischemia be coded without a documented MI?
Yes. When the provider documents demand ischemia and no MI, the Index leads to I24.89.
▸ Why check the current guidelines?
Codes, notes, and guidelines change each October 1. FY 2027 applies from October 1, 2026.
▸ How does accurate coding support compliant billing?
It keeps claims consistent with the record and supports audit readiness.
Disclaimer: This article is educational, published by Sirius Solutions Global for general information. It is not clinical, coding, legal, or compliance advice, does not diagnose any condition, and does not replace the official ICD-10-CM Tabular List, Index, Official Guidelines, AHA Coding Clinic, payer policy, or provider clarification. It guarantees no coverage, reimbursement, or audit outcome. Sirius Solutions Global is not affiliated with CMS or the CDC. Consult qualified coding and compliance professionals about specific records.
