A patient arrives with chest pressure, an abnormal troponin result and an electrocardiogram that does not show persistent ST-segment elevation. The cardiology team diagnoses a non-ST elevation myocardial infarction (NSTEMI). For the medical coder, the obvious next step may be to enter I21.4. Often that is right. But a second line in the discharge summary—“Type 2 myocardial infarction due to severe anemia”—would change the answer.
The ICD-10-CM code for a Type 1 NSTEMI is I21.4, while a documented Type 2 myocardial infarction is coded I21.A1, even if the clinician calls it an NSTEMI. A new infarction shortly after an earlier one introduces a different set of rules. This guide explains those distinctions using the U.S. FY 2027 ICD-10-CM Official Guidelines for Coding and Reporting, effective October 1, 2026, through September 30, 2027.
The discussion is intended for medical coders, billers, clinical documentation integrity professionals and readers learning cardiovascular terminology. It does not replace a clinician’s diagnosis or the official code set. Someone experiencing possible heart attack symptoms should seek emergency medical attention rather than use a coding guide to interpret symptoms.
What Is the ICD-10-CM Code for NSTEMI?
I21.4 — Non-ST elevation (NSTEMI) myocardial infarction is the standard ICD-10-CM diagnosis code for a Type 1 NSTEMI and certain documented nontransmural myocardial infarctions. It is a billable, specific diagnosis code within Chapter 9, Diseases of the Circulatory System, under ischemic heart diseases.
| Code detail | FY 2027 information |
| ICD-10-CM code | I21.4 |
| Official description | Non-ST elevation (NSTEMI) myocardial infarction |
| Classification | Chapter 9: Diseases of the circulatory system |
| Code family | I21: Acute myocardial infarction |
| Status | Billable/specific diagnosis code |
| Appropriate context | Type 1 NSTEMI and qualifying nontransmural MI documentation |
| Code-set period | October 1, 2026–September 30, 2027 |
The CMS FY 2027 ICD-10-CM guidelines state that I21.4 applies to Type 1 NSTEMI and nontransmural infarctions. The corresponding classification also includes terms such as acute subendocardial MI and non-Q-wave MI not otherwise specified. These terms reflect coding conventions, not permission to establish an infarction from a single test result.
One practical point: I21.4 is not a newly introduced 2027 code. The fiscal-year label identifies which annual version of the code set and its instructions are in effect. The clinically significant choice remains whether the provider has documented an appropriate MI diagnosis and, where relevant, its type.
Where I21.4 fits in the diagnosis code set
ICD-10-CM identifies what condition is diagnosed. It is different from CPT or HCPCS coding, which generally describes professional services, procedures, supplies or other billable items. A diagnosis code alone does not tell a payer which service was performed, why it was medically necessary or whether payment will be approved. For a fuller comparison, see MedIntelHub’s guide to ICD-10, CPT and HCPCS code sets.
In practice, a coder should consult both the Alphabetic Index and the current Tabular List before finalizing I21.4, including any applicable instructional notes. An isolated search result or electronic health record suggestion is a starting point, not the entire coding decision.
What Does NSTEMI Mean?
NSTEMI stands for non-ST-segment elevation myocardial infarction. It is a heart attack diagnosed without the characteristic persistent ST-segment elevation pattern on a standard electrocardiogram (ECG or EKG). NSTEMI remains an acute, potentially life-threatening event; the absence of ST elevation does not make it harmless.
An infarction means that heart muscle has been injured because of inadequate blood supply. In a typical Type 1 NSTEMI, an unstable plaque in a coronary artery ruptures or erodes and a blood clot develops, interfering with oxygen delivery. The obstruction may be partial, intermittent or otherwise insufficient to create a classic STEMI ECG pattern. These clinical patterns overlap, which is one reason the treating team evaluates more than the ECG tracing.
Clinical assessment can include symptoms, serial ECGs, cardiac troponin results, imaging and, in selected cases, coronary angiography. According to the 2025 ACC/AHA acute coronary syndromes guideline, non-ST-elevation acute coronary syndromes can have a normal or nonspecific ECG, ST depression, T-wave inversion or transient changes. A normal-looking initial ECG therefore does not automatically rule out serious ischemia.
NSTEMI versus STEMI versus unstable angina
These terms can appear near one another in cardiology records but do not mean the same thing.
| Condition | General clinical distinction | Coding implication |
| NSTEMI | Acute MI without persistent diagnostic ST elevation | I21.4 in the appropriate Type 1 setting; type-specific exceptions apply |
| STEMI | Acute MI with a qualifying ST-elevation pattern or STEMI-equivalent presentation | Relevant site-specific or unspecified Type 1 STEMI code, based on documentation |
| Unstable angina | Acute coronary ischemia without evidence meeting the diagnostic definition of MI | Do not assign an acute MI code when MI has not been established |
A patient can have serious chest pain without an MI, and an MI can sometimes occur without the textbook symptoms. Clinical labels must come from qualified providers, not from a coder’s independent interpretation of the tests.
Warning signs deserve immediate action
Chest pressure, discomfort spreading to the arms, jaw or back, shortness of breath, unexplained sweating, nausea or lightheadedness may signal a heart attack. Symptoms are variable and can be less obvious in some people. The American Heart Association’s warning-sign guidance recommends calling emergency services when a heart attack is suspected. Do not wait to determine whether symptoms would be classified as NSTEMI or STEMI.
When Should Code I21.4 Be Used?
The cleanest case is straightforward: the treating clinician documents an acute Type 1 NSTEMI, and the diagnosis meets the reporting requirements for that encounter. Here, I21.4 is the appropriate diagnosis code under FY 2027 guidance.
Other qualifying documentation may describe an acute nontransmural or subendocardial MI. CMS explicitly directs coders to report a documented nontransmural or subendocardial MI as such, even when an anatomical infarct site is identified. Merely naming a coronary artery does not automatically transform a nontransmural MI into a STEMI code.
If a record says only “NSTEMI,” without identifying a different type or a conflict in the clinical documentation, the Index generally leads to I21.4. But where the same record also describes oxygen supply–demand mismatch, Type 2 MI, non-ischemic injury or a conflicting final diagnosis, clarification may be necessary before choosing the code. Documentation integrity is more valuable than forcing the most familiar code onto an ambiguous case.
What if NSTEMI progresses to STEMI?
The official guidelines distinguish evolution from treatment response. If a Type 1 NSTEMI develops into a STEMI, assign the appropriate STEMI code. Conversely, a Type 1 STEMI that no longer shows ST elevation after thrombolytic therapy is still coded as STEMI. In both situations, the record should support the final diagnostic characterization.
This is a useful reminder that ICD-10-CM coding does not simply preserve the first ECG label entered in the emergency department. The final established diagnosis and the applicable setting-specific reporting rules govern the claim.
Type 1 vs. Type 2 NSTEMI: I21.4 or I21.A1?
The phrase “non-ST elevation” describes an ECG presentation. Type 1 and Type 2 describe different mechanisms of myocardial infarction. Both can appear in records involving elevated troponin and no persistent ST elevation, but they are not interchangeable for coding purposes.
A Type 1 MI generally results from an acute coronary atherothrombotic event—for example, rupture or erosion of an atherosclerotic plaque with clot formation. A Type 2 MI results from a mismatch between myocardial oxygen supply and demand that is not caused by acute coronary plaque rupture with thrombosis. Possible contributing stressors include severe anemia, significant hypoxemia, sustained rapid arrhythmia, hypotension or marked hypertension. These stressors do not themselves establish Type 2 MI; clinical evidence of infarction and a provider diagnosis are still required.
| Coding question | Type 1 NSTEMI | Type 2 MI described as NSTEMI |
| Common mechanism | Acute coronary plaque disruption and thrombosis | Oxygen supply–demand imbalance without acute atherothrombosis |
| ICD-10-CM code | I21.4 | I21.A1 |
| Does the NSTEMI wording determine the code by itself? | It usually points to I21.4 when no contradictory type is documented | No; Type 2 classification overrides the NSTEMI/STEMI label |
| Underlying condition | Code additional conditions when reportable and supported | Code underlying cause first, if applicable, according to CMS |
| Key documentation | Provider-established MI and classification | Provider-established Type 2 MI and contributing cause, when known |
The distinction is spelled out in Section I.C.9.e of the official FY 2027 guidelines. When Type 2 MI is described as NSTEMI or STEMI, only I21.A1 is assigned for that Type 2 infarction—not an additional I21.4 or STEMI code to describe its ECG pattern.
Why does Type 2 MI require I21.A1?
Imagine an inpatient being treated for severe gastrointestinal bleeding and profound anemia. During the admission, serial troponin measurements change and the clinician documents acute myocardial ischemia due to an oxygen supply–demand mismatch, with a final diagnosis of Type 2 MI. The infarction diagnosis is I21.A1. The bleeding or other causal condition must be assessed under the applicable code-first and sequencing instructions.
The provider might write “Type 2 NSTEMI” in the same note. That extra word does not justify I21.4. CMS also instructs coders not to separately assign I24.89 for demand ischemia in this Type 2 MI situation.
Do not reverse the logic. Anemia, infection or a fast heart rate plus an elevated troponin does not authorize the coder to create a Type 2 MI diagnosis. Some patients have acute myocardial injury without enough evidence for an infarction. The clinical conclusion belongs to the responsible provider.
Does Type 2 MI always involve blocked coronary arteries?
No. A patient can have underlying coronary artery disease and develop an oxygen supply–demand imbalance without acute plaque rupture. Other patients may have no obstructive coronary lesion. The Fourth Universal Definition of Myocardial Infarction emphasizes the mechanism of ischemic injury, not a simplistic “blocked versus unblocked” distinction.
Because this distinction may affect clinical evaluation and treatment as well as coding, the medical record should clearly separate the provider’s final MI type from tentative explanations in progress notes. Coders should not infer plaque rupture, anatomic stenosis or a Type 2 mechanism from imaging alone.
A useful code table is not simply a list of diagnoses. It should show when an alternative becomes relevant and when it must not be substituted for I21.4.
| ICD-10-CM code | Description or context | Coding caution |
| I21.4 | Non-ST elevation myocardial infarction | Typical Type 1 NSTEMI and qualifying nontransmural MI |
| I21.A1 | Myocardial infarction Type 2 | Use for documented Type 2 MI even when called NSTEMI |
| I22.2 | Subsequent NSTEMI | Use only under qualifying subsequent-MI rules; requires applicable I21 code |
| I21.9 | Acute MI, unspecified | Used when acute MI type or characterization is unspecified as directed by guidelines |
| I21.3 | STEMI of unspecified site | Not a generic alternative to I21.4; Type 1 STEMI context applies |
| I21.A9 | Other myocardial infarction type | Relevant to documented Types 3, 4a, 4b, 4c and 5 |
| I21.B | MI with coronary microvascular dysfunction | Special documented microvascular disease context; verify current Tabular notes |
| I25.2 | Old myocardial infarction | Healed or old MI not requiring further related care, when appropriate |
| I5A | Non-ischemic myocardial injury (non-traumatic) | Not a default code for elevated troponin or a diagnosed infarction |
These are examples, not a substitute for the current Alphabetic Index, Tabular List and setting-specific guidelines. The exact relationship among conditions may determine which codes are reportable together and in what order.
A special FY 2027 topic: I21.B and microvascular dysfunction
Section I.C.9.e.6 of the FY 2027 CMS guidelines addresses I21.B, myocardial infarction with coronary microvascular dysfunction. The guidance includes MI associated with coronary microvascular disease or dysfunction and MI with non-obstructive coronary arteries (MINOCA) with microvascular disease.
It would be misleading to infer I21.B from the term MINOCA alone. MINOCA describes a working clinical presentation with multiple possible mechanisms. A documentation-supported microvascular diagnosis is central to this specific code, and its use should be checked against the Tabular List and any accompanying type documentation. I21.B already existed before FY 2027; its presence in the guidelines should not be presented as an entirely new NSTEMI code for 2027.
Subsequent NSTEMI and the Four-Week Coding Rule
A repeat infarction can occur while the first event is still recent. The official ICD-10-CM framework uses four weeks (28 days) when determining the applicable acute-MI and subsequent-MI reporting rules. This is more precise than saying that every return visit within a month requires a subsequent-MI code.
I22.2 identifies a subsequent NSTEMI under the appropriate circumstances. Section I.C.9.e.4 says category I22 applies when a patient with an initial Type 1 or unspecified AMI has a new Type 1 or unspecified AMI within four weeks. A category I22 code is used together with a code from I21, with sequencing determined by the encounter circumstances.
Consider a patient with a documented Type 1 NSTEMI who experiences a distinct, newly diagnosed Type 1 NSTEMI 12 days later. Assuming both diagnoses meet the relevant reporting requirements, the coding pattern involves I21.4 and I22.2. This is not a case where I22.2 automatically replaces every I21 code.
When I22.2 should not be used
A second increase in troponin during recovery does not necessarily represent a second MI. Neither does a follow-up appointment after an uncomplicated first infarction. The new event must be clinically established and the temporal and MI-type criteria must be satisfied.
Three limits are especially important:
- A subsequent Type 2 MI is assigned A1, not I22.2.
- A subsequent Type 4 or Type 5 MI is assigned A9, rather than an I22 code.
- If a new MI of one type occurs within four weeks of an MI of a different type, assign the appropriate I21 codes for the types involved and do not use I22.
These details prevent two common mistakes: applying I22.2 to any recurrent ischemic event and assuming that Type 1 and Type 2 MI follow identical reinfarction rules.
How long can an acute MI code remain reportable?
For encounters occurring while the infarction is no more than four weeks old, I21 codes may continue to be reported if the encounter and diagnosis meet applicable reporting requirements. CMS mentions transfers between acute settings and postacute settings within that period.
After four weeks, if the person is still receiving care related to the MI, the appropriate aftercare code is used instead of continuing an I21 code solely for the old event. When the infarction is old or healed and no further related care is needed, I25.2 may be appropriate. There is no universal aftercare code that should be assigned without examining the actual reason for the encounter.
Documentation Requirements for Accurate NSTEMI Coding
Accurate NSTEMI coding begins in the medical record, not in a lookup window. A coder may see troponin curves, an ECG interpretation and a catheterization report. Those findings help support clinical decision-making, but the provider who is accountable for the diagnosis must establish the condition.
A useful documentation review asks whether the record identifies:
- The final diagnosis: acute NSTEMI, another MI type, myocardial injury, unstable angina or a different condition.
- The MI type: Type 1, Type 2 or another documented type, especially when progress notes are inconsistent.
- The context: evidence and description of acute ischemia, where clinically relevant.
- The mechanism or cause: acute coronary plaque-related event versus demand-related stressor when applicable.
- Timing: onset, date of a previous MI and whether a distinct new infarction occurred within four weeks.
- The encounter purpose: acute treatment, hospital transfer, postacute care, later aftercare or an unrelated visit.
- Final reconciliation: whether initial “rule out” statements were replaced by confirmed discharge conclusions.
A compliant provider query should be clinically supported, non-leading and consistent with organizational policy. For example, if one cardiology note states “Type 1 NSTEMI” but a final summary states “Type 2 MI due to tachyarrhythmia,” the task is to resolve the discrepancy. Selecting whichever code seems to pay more is neither a clinical nor a coding rationale.
Elevated troponin is not the same as NSTEMI
This distinction deserves its own review because it changes the diagnosis itself. Cardiac troponin is a marker of myocardial cell injury. A rise or fall above the assay’s 99th-percentile upper reference limit can indicate acute myocardial injury, but diagnosing MI additionally requires evidence of acute myocardial ischemia in the appropriate clinical setting.
Troponin may rise in patients with heart failure, kidney disease, severe systemic illness, myocarditis or other conditions. Some have a true Type 2 MI; others have ischemic or non-ischemic injury without infarction. The Universal Definition of Myocardial Infarction explains the criteria and why these categories must be distinguished.
I5A, non-ischemic myocardial injury (non-traumatic), is a separate code when that diagnosis is documented and the classification directs its use. It should not be added reflexively to every elevated troponin result. The coder must follow the final provider diagnosis, applicable exclusions and reporting rules.
Inpatient and outpatient uncertainty rules are not identical
An additional trap lies in the setting. In qualifying inpatient discharge coding, certain diagnoses documented as probable or suspected at discharge may be coded as established under Section II.C of the official guidelines. That rule does not apply broadly to outpatient office visits or emergency department encounters. Outpatient claims generally do not code an uncertain diagnosis as though confirmed; report the documented signs, symptoms or other established conditions when appropriate.
For example, an ED discharge note stating “possible NSTEMI—evaluation incomplete” does not by itself authorize outpatient reporting of I21.4. The actual documentation, setting and final disposition matter. This is why a hospital inpatient claim and a professional outpatient claim may require different diagnosis reporting even when some of the clinical notes overlap.
NSTEMI ICD-10 Coding Examples
The examples below are fictional and simplified to illustrate diagnosis-code selection. They are not complete claims, and they do not establish actual reimbursement eligibility or principal-diagnosis sequencing for every admission.
Example 1: Confirmed Type 1 NSTEMI
A patient presents with worsening chest pressure. Serial troponin concentrations rise, the ECG shows ischemic changes without diagnostic persistent ST elevation, and the final cardiology assessment states “acute Type 1 NSTEMI due to plaque rupture.”
Code focus: I21.4. The documentation identifies a Type 1 NSTEMI. Additional diagnosed conditions may also be reportable, depending on the record and applicable rules.
Example 2: Type 2 NSTEMI during severe anemia
A hospitalized patient has severe blood-loss anemia. The physician documents acute myocardial ischemia with a rise and fall in troponin and finalizes “Type 2 NSTEMI related to oxygen supply–demand mismatch.”
Code focus: I21.A1. The NSTEMI wording does not make I21.4 appropriate. Code the underlying cause first if applicable, following the official sequencing rules.
Example 3: New Type 1 NSTEMI within 28 days
A patient treated for a Type 1 NSTEMI has a second clinically distinct Type 1 NSTEMI 10 days later. Both acute infarctions meet the applicable coding/reporting criteria.
Code focus: I21.4 with I22.2. Determine the proper sequence from the encounter circumstances; do not assign I22.2 alone without considering the required I21 code.
Example 4: Elevated troponin without diagnosed MI
A patient with decompensated heart failure has mildly elevated troponin levels. After evaluation, the clinician documents non-ischemic myocardial injury rather than an MI.
Code focus: not I21.4. I5A may apply for documented non-ischemic myocardial injury, along with other reportable diagnoses and applicable sequencing rules. The lab value does not independently establish NSTEMI.
Example 5: Prior infarction, no active care for MI
At a routine visit, the chart documents an infarction from several years earlier. The patient is not receiving treatment or follow-up specifically for an active or healing MI. The provider describes an old, healed MI.
Code focus: I25.2 may apply. The acute NSTEMI code should not be carried forward automatically just because it appeared in an older hospitalization record.
Example 6: Progression from NSTEMI to STEMI
A patient initially has a documented Type 1 NSTEMI but subsequently develops a Type 1 STEMI during the same acute event. The discharge documentation establishes the evolution.
Code focus: the appropriate Type 1 STEMI code. CMS instructs coders to use the STEMI code when Type 1 NSTEMI evolves to STEMI, rather than preserving I21.4 simply because it was the initial label.
Example 7: Ambiguous clinical wording
An ED note calls an event “NSTEMI,” while the inpatient progress notes attribute the troponin elevation to critical illness. The discharge summary does not reconcile Type 1 MI, Type 2 MI and non-ischemic injury.
Code focus: clarification before a confident code choice. The coder should use an appropriate documentation-query process when the conflicting diagnosis affects accuracy. A troponin trend cannot resolve the type independently.
Common NSTEMI Coding Mistakes and Denial Risks
The errors that matter most often start before claim submission. A code may be syntactically valid but unsupported by the record, inconsistent with other diagnoses or sequenced contrary to an official instruction.
Treating every NSTEMI as I21.4. The shorthand overlooks documented Type 2 MI and other specific infarction contexts. The most reliable safeguard is to read the final provider documentation instead of coding from an encounter summary or problem-list entry alone.
Assigning an MI solely from cardiac biomarkers. Elevated troponin is not sufficient to diagnose a heart attack. When the clinician documents injury rather than infarction, the code selection changes.
Using I22.2 for an old MI or a follow-up visit. A new and qualifying acute infarction must be established. Merely having had an MI less than four weeks earlier does not mean every new visit represents reinfarction.
Ignoring sequencing instructions for Type 2 MI. When an underlying condition is identified and the official guideline calls for it first, reporting I21.A1 as the first diagnosis without reviewing the cause can create a sequencing problem.
Confusing diagnosis code validity with coverage. ICD-10-CM identifies diagnoses; it does not guarantee a service meets a payer’s medical-necessity or documentation requirements. Denial analysis should separate eligibility, authorization, coding, missing records, bundling and payer-specific claim rules. MedIntelHub’s claim denial prevention and follow-up checklist offers a broader operational framework for investigating those failures.
Carrying the acute code forward indefinitely. Once an event moves outside the acute coding window, the diagnosis should be reconsidered based on whether active MI care, aftercare or only a healed history is documented.
A basic claim edit that catches inappropriate I21.4/I21.A1 combinations helps, but it cannot replace skilled chart review. The core question remains what the provider actually diagnosed and which official rules apply to this encounter.
FY 2027 ICD-10-CM Rules for NSTEMI
The fiscal year is not a cosmetic label. CMS states that the FY 2027 ICD-10-CM files apply to discharges and patient encounters from October 1, 2026, through September 30, 2027. If an organization relies on an older code book or a search page displaying an earlier fiscal year, it risks missing revised notes or code-set instructions even where the familiar code I21.4 remains unchanged.
For NSTEMI and related conditions, Section I.C.9.e is the main chapter-specific reference. The portions most relevant to everyday coding include the Type 1 NSTEMI rule; conversion between NSTEMI and STEMI; the acute-MI four-week framework; I22 subsequent infarction reporting; Type 2 MI coding and underlying-cause sequencing; other MI types; and the documented coronary microvascular dysfunction context for I21.B.
A practical 2027 code-selection sequence
- Confirm the applicable code-set year and encounter setting. The fiscal year and inpatient/outpatient status can change the applicable reporting approach.
- Read the final responsible provider diagnosis. Identify NSTEMI, STEMI, MI type, myocardial injury or another condition.
- Resolve contradictory documentation. Do not use troponin, ECG interpretation or catheterization findings to independently determine the MI type.
- Select the appropriate code family. In a typical Type 1 NSTEMI, I21.4 applies; a Type 2 MI uses I21.A1; a qualifying subsequent NSTEMI may involve I22.2 and I21.4.
- Check the Tabular List and required sequencing. Review exclusions, code-first instructions, additional diagnoses, timing and circumstances of the encounter.
- Validate claim-level reporting. Confirm diagnosis support, encounter relevance, payer instructions and any medically necessary supporting documentation.
There is a useful distinction between a coding update and a new diagnostic category. For example, the 2027 guidance continues to address I21.B; this does not mean every patient with nonobstructive coronary arteries now receives that code, or that the code first appeared in 2027. Consult the actual published release rather than interpreting an annual article headline as a list of brand-new codes.
The CMS ICD-10 code files page is the primary location to check the current release. For a workflow that includes other payer and policy changes, see MedIntelHub’s guide to tracking healthcare policy and payer updates.
Frequently Asked Questions About NSTEMI ICD-10 Codes
1. What is the ICD-10 code for NSTEMI in 2027?
I21.4 is the ICD-10-CM code for Type 1 NSTEMI and qualifying nontransmural MI in FY 2027. When the provider documents a Type 2 MI, however, use I21.A1, even if it is also called NSTEMI.
2. What does ICD-10-CM code I21.4 mean?
I21.4 is the billable diagnosis code for non-ST elevation myocardial infarction. It sits within category I21, acute myocardial infarction, and is used according to the official Type 1 and nontransmural MI rules.
3. Is I21.4 a billable code?
Yes. I21.4 is a specific, billable ICD-10-CM diagnosis code. Billable status means it is sufficiently detailed for diagnosis reporting; it does not guarantee reimbursement for a service.
4. What is the difference between I21.4 and I21.A1?
I21.4 generally represents Type 1 NSTEMI, while I21.A1 represents Type 2 MI from oxygen supply–demand imbalance. A Type 2 MI described as NSTEMI is coded I21.A1, not both codes for the same event.
5. Can Type 2 NSTEMI be billed as I21.4?
Not when the documentation establishes Type 2 MI. FY 2027 CMS guidance directs coders to assign only I21.A1 for that Type 2 infarction even if NSTEMI or STEMI wording appears.
6. What is the ICD-10 code for demand ischemia with a diagnosed Type 2 MI?
The Type 2 MI diagnosis uses I21.A1. CMS says the underlying cause is coded first if applicable and that I24.89 should not be added merely for demand ischemia in this situation. Do not infer Type 2 MI from demand ischemia alone.
7. What is the code for a second NSTEMI within four weeks?
I22.2 may apply when a new, qualifying Type 1 or unspecified NSTEMI occurs within four weeks of an initial Type 1 or unspecified MI. An applicable I21 code is also required, and sequencing depends on the encounter.
8. Is an elevated troponin level enough to code NSTEMI?
No. Troponin elevation indicates myocardial injury, not necessarily infarction. Evidence of acute ischemia and a provider-established diagnosis are needed to identify MI clinically, and coders must follow the documented final diagnosis.
9. Does NSTEMI mean the artery is only partly blocked?
Not necessarily. Many Type 1 NSTEMIs involve reduced coronary blood flow from a plaque-related clot, but angiographic findings and mechanisms vary. The term refers to the ECG presentation, not a guaranteed degree of blockage.
10. Are NSTEMI and STEMI both heart attacks?
Yes. Both are forms of acute myocardial infarction. They differ in their ECG presentation and frequently in their immediate evaluation and treatment pathways, but either can be serious or life-threatening.
11. What if the record documents NSTEMI but not the MI type?
The ICD-10-CM Index generally leads to I21.4 for NSTEMI when no different type or contradiction is documented. If the record contains conflicting statements suggesting Type 2 MI or myocardial injury, clarification may be needed.
12. What if a Type 1 NSTEMI evolves into a STEMI?
The FY 2027 guideline directs assignment of the appropriate STEMI code when Type 1 NSTEMI evolves into STEMI. A Type 1 STEMI does not become an NSTEMI for coding merely because thrombolytic treatment resolves ST elevation.
13. How long can I21.4 remain appropriate after an acute NSTEMI?
I21 codes may continue to be reported within the first four weeks when the encounter and diagnosis satisfy applicable reporting rules. After that period, use the appropriate aftercare or old-MI reporting approach based on the patient’s situation.
14. Is I25.2 used for a history of NSTEMI?
It may be used for an old or healed myocardial infarction that no longer requires care, if the documentation supports that status. It should not replace coding of an active acute event.
15. Is I21.B another code for every NSTEMI with clear coronary arteries?
No. I21.B concerns documented myocardial infarction with coronary microvascular dysfunction, including certain MINOCA presentations with microvascular disease. Nonobstructive coronary arteries alone do not justify that specific diagnosis.
16. Can a suspected NSTEMI be coded in the emergency department?
Do not automatically apply inpatient uncertain-diagnosis rules to an ED or other outpatient encounter. A suspected NSTEMI that remains unconfirmed is generally not coded as an established MI for outpatient reporting; code the established findings and conditions as applicable.
17. Does assigning I21.4 guarantee a claim will be paid?
No. Accurate code selection supports claim integrity, but payment depends on the service, medical necessity, documentation, coverage and payer-specific rules. Coding the diagnosis correctly is necessary in many workflows, not a payment promise.
Putting the Code in Context
A quick lookup answers the opening question: I21.4 is the NSTEMI ICD-10-CM code in the usual Type 1 setting. The difficult work begins when the chart describes a different MI type, a second acute infarction, myocardial injury without infarction or a healed event. Those are not minor wording differences. They can change the code family and the reporting sequence.
For FY 2027 claims, check the provider’s final diagnosis, use the current CMS classification, and distinguish Type 1 NSTEMI from Type 2 MI before submitting I21.4. When the record is contradictory, an appropriate clinical documentation query is safer than a guess based on a troponin value or an EHR suggestion.
Resources
Centers for Medicare & Medicaid Services — FY 2027 ICD-10-CM Official Guidelines
The primary federal reference for acute MI coding, Type 1 and Type 2 distinctions, I22 reinfarction rules, four-week reporting, and I21.B guidance. Review Section I.C.9.e and the general rules for the relevant care setting.
Read the FY 2027 ICD-10-CM Official Guidelines
Centers for Medicare & Medicaid Services — ICD-10 Code Files
Official ICD-10-CM releases and code-set files, including FY 2027 tabular and index materials and applicable dates.
View the current CMS ICD-10 releases
American College of Cardiology and American Heart Association — 2025 Acute Coronary Syndromes Guideline
Current cardiology guidance discussing NSTEMI, STEMI, acute evaluation, ECG interpretation and the use of cardiac troponin in suspected acute coronary syndromes.
Review the 2025 acute coronary syndromes guideline
ESC/ACC/AHA/WHF Task Force — Fourth Universal Definition of Myocardial Infarction
International clinical consensus defining myocardial injury, infarction and the distinctions among Type 1, Type 2 and other MI categories.
Read the Fourth Universal Definition of Myocardial Infarction
American Heart Association — Fourth Universal Definition: Key Points
A concise professional overview of how clinical symptoms, ECG findings, biomarkers and imaging contribute to myocardial infarction classification.
Explore the AHA clinical summary
American Heart Association — Warning Signs of a Heart Attack
Patient-facing guidance on recognizing possible heart attack symptoms and seeking emergency evaluation without delay.
Read the AHA heart attack warning signs
Editorial Guidelines & Medical Disclaimer
This MedIntelHub article is for education and general information. It is not a diagnosis, a substitute for professional medical advice, or a recommendation to start, stop or change medication or treatment. NSTEMI and other acute coronary syndromes require assessment by qualified healthcare professionals. If symptoms suggest a heart attack, contact emergency services immediately.
The coding discussion is based primarily on the FY 2027 U.S. ICD-10-CM guidelines and current authoritative cardiology references. ICD-10-CM classifications, documentation standards, claims rules and payer reimbursement policies may change. Before submitting a claim, verify the code in the current Alphabetic Index and Tabular List, check the date of service or discharge, review setting-specific guidelines and follow applicable payer rules. A valid diagnosis code does not guarantee coverage or payment. The information does not replace medical coding compliance advice for a particular claim.
MedIntelHub prioritizes primary sources, context and corrections when information changes. See the site’s Editorial Policy for its approach to medical and healthcare-information publishing.
David Bennett
David Bennett is an author at MedIntelHub, where he creates clear, practical, and well-researched content about healthcare, medical billing, insurance, and patient education. His goal is to make complex healthcare topics easier for readers to understand and use in everyday situations. David emphasizes accuracy, transparency, and reliable sourcing, using information from trusted organizations and official healthcare resources whenever possible. Content published by David is intended for educational purposes and should not replace advice from qualified medical, legal, or healthcare professionals.