Demand Ischemia ICD-10: A Complete Coding Guide for Type 2 Myocardial Infarction

Accurate coding of demand ischemia ICD-10 requires a clear understanding of how ICD-10-CM classifies this condition — particularly in the context of Type 2 myocardial infarction — and how documentation must support the code selected to avoid claim denials, DRG reclassification, and compliance issues that compound silently across every qualifying inpatient admission.

What Is Demand Ischemia?

Demand ischemia, also known as supply-demand mismatch ischemia, occurs when myocardial oxygen demand exceeds available supply without the underlying cause being a primary coronary artery occlusion or plaque rupture. Common causes include severe anemia, tachyarrhythmias (such as rapid atrial fibrillation), hypotension, sepsis, respiratory failure, hypertensive crisis, and profound hemodynamic stress. In these cases, the heart undergoes ischemic injury as a secondary consequence of a systemic condition.

Demand ischemia is the clinical substrate of what ICD-10-CM classifies as a Type 2 Myocardial Infarction (Type 2 MI) — a distinction formally incorporated into ICD-10-CM in 2018. Choosing the right code depends on whether the ischemia meets criteria for myocardial infarction or is better described as myocardial injury or ischemia without infarction.

Primary ICD-10 Codes for Demand Ischemia

I21.A1 – Type 2 Myocardial Infarction

This is the primary ICD-10-CM code for demand ischemia when the clinical presentation meets criteria for myocardial infarction. Type 2 MI (I21.A1) is defined as a myocardial infarction secondary to an ischemic imbalance — specifically, a mismatch between oxygen supply and demand not attributable to acute coronary artery thrombosis. This code was introduced in ICD-10-CM FY2018 and replaced the prior use of I21.4 (non-ST elevation MI) for many demand ischemia cases.

To assign I21.A1 correctly, the provider’s documentation must clearly state “Type 2 myocardial infarction” or “demand ischemia with myocardial infarction.” Troponin elevation alone is not sufficient — the underlying cause must be identified, and the physician must explicitly designate the event as a Type 2 MI.

I24.8 – Other Forms of Acute Ischemic Heart Disease

When demand ischemia is documented but does not rise to the level of myocardial infarction — for example, when troponin elevation is present but the physician does not diagnose an MI — I24.8 may be an appropriate alternative. This code captures acute ischemic heart disease not classified elsewhere and is useful when the documentation supports ischemia but not infarction.

I25.110 – Atherosclerotic Heart Disease with Unstable Angina

In patients with known coronary artery disease who develop demand ischemia in the context of existing atherosclerosis, this code may be applicable if the presentation is consistent with unstable angina rather than infarction.

I51.89 – Other Ill-Defined Heart Diseases (Myocardial Injury)

For cases where the cardiac biomarker elevation represents myocardial injury (not ischemia or infarction), I51.89 may be reported. The Fourth Universal Definition of Myocardial Infarction distinguishes between myocardial injury and myocardial infarction, and ICD-10-CM coding must reflect the physician’s clinical determination.

Coding the Underlying Cause of Demand Ischemia

One of the most important coding principles for demand ischemia is that the underlying cause must always be coded as an additional diagnosis. ICD-10-CM guidelines state that when a Type 2 MI occurs secondary to another condition, the underlying condition is coded first if it is the reason for admission, or is coded additionally when the MI is the reason for admission.

Common underlying cause codes reported alongside demand ischemia include:

• D64.9 – Anemia, unspecified (when severe anemia is the precipitating cause)
• I48.0–I48.19 – Atrial fibrillation (when rapid ventricular response drives the demand ischemia)
• A41.9 – Sepsis, unspecified organism
• J96.00 – Acute respiratory failure, unspecified whether with hypoxia or hypercapnia
• I10 – Essential hypertension (as a contributing factor in hypertensive crisis)
• J18.9 – Pneumonia, unspecified organism
• K92.1 – Melena (acute blood loss leading to demand ischemia)

The Sequencing Rule That Determines Your DRG Weight

I21.A1 is never the principal diagnosis. When a hospitalist manages a patient admitted for sepsis (A41.xx), hypoxemic respiratory failure (J96.00), or severe anemia (D64.9) with a secondary T2MI event, the demand trigger is sequenced first — I21.A1 follows as a secondary condition. Reversing this sequence, or defaulting to unspecified NSTEMI code I21.4 when the physician has documented Type 2 MI, triggers an immediate DRG reclassification. The reimbursement differential between DRG 282 with MCC and a mid-tier DRG assignment on the same encounter ranges from $4,200 to $8,800 per admission — compounding silently across every qualifying case in your census.

Denial root-cause engineering at the sequencing level is the only intervention point where this loss is fully recoverable. By the time a reclassification surfaces in your AR Aging report, the primary adjudication window has closed.

Type 1 vs. Type 2 MI: The Critical Coding Distinction

Distinguishing between Type 1 and Type 2 MI is essential for accurate ICD-10 coding and has significant implications for reimbursement, quality reporting, and risk adjustment. A Type 1 MI (coded as I21.0–I21.4 based on location and type) results from plaque rupture, erosion, or acute coronary artery thrombosis. A Type 2 MI (I21.A1) occurs due to supply-demand mismatch without primary coronary artery disease as the immediate cause.

Coders should never independently distinguish between Type 1 and Type 2 MI based on clinical findings or troponin values alone. This determination must be based on the attending physician’s documentation. If the physician documents “NSTEMI” without specifying type, coding guidelines instruct coders to query the physician for clarification rather than defaulting to I21.4.

Where the Volume Loss Concentrates

Demand ischemia events in hospitalist programs cluster in three admission profiles: sepsis with hemodynamic compromise, acute respiratory failure with hypoxemia, and severe anemia with troponin elevation. These three trigger categories account for 70 to 80 percent of all T2MI encounters in a high-volume inpatient program — and each carries a distinct ICD-10 sequencing requirement that generalist coders without inpatient comorbidity training routinely misapply.

Without payer variance detection embedded in your coding workflow, these encounters pass initial adjudication and are retroactively reclassified 60 to 90 days post-payment. By the time the variance appears, old AR recovery resources are absorbing claims that should never have been underpaid.

Documentation Requirements for Demand Ischemia Coding

Precise physician documentation is the cornerstone of accurate demand ischemia coding. The medical record should contain an explicit statement of the diagnosis — ideally “Type 2 myocardial infarction” or “demand ischemia” — along with the identified precipitating cause. The documentation should also include the cardiac workup results (troponin trends, EKG findings, echocardiography if performed) and a clear clinical narrative explaining why the ischemia was deemed a supply-demand mismatch rather than a primary coronary event.

Hospitalists and cardiologists should be educated that vague terminology such as “troponin leak,” “demand ischemia by enzyme,” or “possible Type 2 MI” creates coding ambiguity. Coding guidelines permit coding of uncertain diagnoses for inpatient encounters (using “probable” or “suspected”), but the clinical documentation must be sufficiently specific to allow accurate code selection.

The Documentation Gap Payers Are Auditing

When documentation does not explicitly state “Type 2 myocardial infarction” or “demand ischemia with myocardial infarction,” coders cannot defensibly assign I21.A1, and the encounter defaults to a lower-complexity code. This is not a clinical failure — it is a Revenue Integrity failure at the documentation layer. Payers are actively auditing this gap, treating vague terminology as insufficient support for I21.A1 and reclassifying DRGs accordingly.

Billing Implications and Common Errors

Demand ischemia coding errors are among the most common in cardiology and hospitalist billing. Frequent mistakes include assigning I21.4 (NSTEMI) when the physician has documented Type 2 MI — which understates disease complexity and may affect DRG assignment and reimbursement. Conversely, upcoding to I21.A1 when the physician has not specifically documented a Type 2 MI creates compliance risk.

Under MS-DRG grouping, Type 2 MI coded as I21.A1 typically groups to DRG 282 (Acute Myocardial Infarction with MCC), 283, or 284 depending on complication status. Accurate capture of secondary diagnoses — particularly the precipitating condition — directly impacts DRG complexity and case mix, making documentation improvement programs for demand ischemia a high-value RCM initiative.

What Your 90-Day Diagnostic Will Surface

A structured review of 90 days of T2MI encounters in a 400-admission hospitalist program consistently uncovers $90,000 to $180,000 in suppressed reimbursement tied to three root causes: reversed sequencing on sepsis-driven T2MI admissions, unspecified MI code defaults on respiratory failure encounters, and comorbidity documentation gaps that payers use to justify DRG downgrades on multi-system admissions.

MBC’s Strategic Revenue Diagnostic identifies which payers are systematically reclassifying your demand ischemia DRGs, which trigger categories carry the highest miscoding frequency in your specific census, and what denial management infrastructure is required to eliminate recurrence. This is what converts reactive billing into a proactive Enterprise Revenue Integrity program — and what your current vendor is not delivering if T2MI sequencing has never been audited.

FAQs: Demand Ischemia ICD-10 Coding