NSTEMI ICD 10: A Practical Guide to Accurate Code Selection

September 18, 2026

The ICD-10-CM diagnosis code assigned for NSTEMI is usually extended with additional code(s) to create a more accurate reflection of the patient’s condition. Additional codes may be assigned to reflect the presence of Type 2 MI, other infarctions, or myocardial injury.

Acute type 2 NSTEMI is assigned code I21.A1. In the case of a subsequent NSTEMI, code I22.2 is assigned in addition to the initial type 2 NSTEMI code (I21).

As mentioned previously, the objective of assigning codes is to represent the conditions documented in a manner that is in line with the guidelines and address any ambiguity.

Read the Diagnosis Before Accepting the Suggested Code

An EHR search can find I21.4 quickly. It cannot decide whether the provider is describing an acute infarction, continued treatment, a separate event, or a diagnosis that has been ruled out.

Start by checking:

The final diagnostic statement.
Any specifically documented MI type.
Whether the encounter concerns the same infarction or a new one.
Whether the diagnosis is confirmed, uncertain, or conflicting.
The reporting rules for the setting and claim type.

A problem-list entry should not override a clarified diagnosis. Likewise, a test result should not replace the provider’s clinical interpretation.

When the record tells a consistent story, code selection becomes much simpler. When it does not, identify the exact point that needs clarification.

I21.4 Is Assigned for Certain Types of NSTEMI

Non-ST elevation myocardial infarction (NSTEMI) represents a situation where there is evidence of myocardial infarction but there is no ST segment elevation on the electrocardiogram. I21.4 is assigned for the ICD-10-CM implementation of acute NSTEMI, if there is not sufficient information to assign another myocardial infarction (MI) type or an MI of a subsequent event.

I21.4 also includes Type 1 NSTEMI, acute subendocardial MI, and various types of nontransmural/Q-wave MI.

Anterior or inferior location, with regard to myocardial infarction, is not represented in I21.4. In addition, I21.4 does not distinguish MI based upon the involved coronary artery.

In some cases of NSTEMI, the myocardial infarction location may be documented. Location of the infarct does not necessarily mean the event is of the STEMI type.

NSTEMI and STEMI Represents Different Classifications

Differentiating Type 1 and Type 2 of myocardial infarction refers to how the infarction occurred, while NSTEMI and STEMI concern the classification of ST segment elevation. Therefore, coding for NSTEMI and STEMI does not replace one another.

Not every NSTEMI is related to a supply/demand imbalance. In addition, the presence of NSTEMI does not negate the possibility of a Type 2 MI.

Keep These NSTEMI-Related Codes Separate

Documented condition	Code	Key consideration
Acute NSTEMI, including Type 1 NSTEMI	I21.4	Confirm the documented classification and event circumstances.
Type 2 MI, including Type 2 NSTEMI	I21.A1	Code the underlying cause first, if applicable.
Qualifying subsequent NSTEMI	I22.2	Report with the appropriate I21 code and apply subsequent-MI requirements.
Old or healed MI requiring no further care	I25.2	Confirm that the documentation supports a healed or historical infarction.
Acute MI without further specification	I21.9	Use only the specificity supported by the record.

These codes are alternatives for different circumstances, not a standard bundle to assign together.

Also distinguish subsequent NSTEMI from subsequent STEMI. I22.1, I22.8 and I22.9 describe subsequent STEMI classifications by site. They are not wall-specific versions of I22.2.

Selecting and Sequencing Type 2 NSTEMI Codes

In the case of Type 2 NSTEMI, assign code I21.A1 for code assignment and selection. Additional code I21.4 should not be assigned solely because the diagnosis contains NSTEMI.

Once the code assignment and selection process for I21.A1 has been completed, follow the instructions for code assignment and selection for any additional codes for the remaining conditions represented in the documentation.

Example: Anemia with Type 2 NSTEMI

Let’s say Type 2 NSTEMI is documented to be caused by severe anemia. In this case, anemia is also coded to ICD-10-CM code I21.A1 and the applicable instructions for code assignment and selection are also followed.

In the absence of documentation indicating the final diagnosis of Type 1 NSTEMI, the presence of NSTEMI in a chart is not sufficient to warrant the assignment of a Type 1 MI code.

Type 2 NSTEMI may not be assigned solely on the basis of the presence of anemia, sepsis, hypotension, and/or tachycardia.

Procedure-related MI require a separate review.

Absence of ST segment elevation does not rule out an MI.

Types 3, 4A, 4B, 4C and 5 MI are also to be assigned and sequenced based on instructions for code assignment and selection for I21.A9. Coronary Microvascular Disease also has specific instructions.

When a diagnosis documents the presence of a mechanical/procedural event, and NSTEMI is also documented, the code review should be for the specific event as opposed to a general NSTEMI code.

Different Diagnoses: Demand Ischemia, Myocardial Injury, and NSTEMI

Demand Ischemia
The presence of Demand Ischemia, without the documentation of Myocardial Infarction (MI), prevents assigning a Type 2 MI code. An unspecified code from the Robotic pathway may be assigned, e.g. I24.89. Demand Ischemia that results in Type 2 MI is coded to I21.A1; the demand Ischemia, in this case, is not coded.

Myocardial Injury
Myocardial Injury that is neither ischemic nor traumatic is classified as I5A and contains instructions for underlying causes. It should not be assigned in lieu of a documented Myocardial Infarction, nor should it be assigned in the absence of Myocardial Infarction.

NSTEMI
An elevated troponin level does not allow the coder to assign a diagnosis of NSTEMI.

The interpretation of the provider is considered. In the absence of resolution of the discrepancy, i.e. Myocardial Infarction vs. Myocardial Injury, a diagnosis of higher financial impact, should not be assigned.

Code Assignment and Clinical Validation

In the case of a conflict between the statement of the provider and the supporting documentation, both responsibilities of the coder, representing the diagnosis of the patient and resolving the conflict, should be considered. The supporting documentation should not be disregard in consideration of the statement of the provider.

The Four-Week Rule Separates Continued Care From a Subsequent Event

MI coding requires an interval-based distinction. The four-week, or 28-day, rule cannot be replaced by the number of visits or admissions.

During the applicable acute interval, I21 reporting may continue for the same infarction when reporting requirements are met. A transfer or readmission alone does not establish another MI.

I22 applies to a qualifying new infarction within four weeks when both the initial and subsequent events are Type 1 or unspecified. Report the appropriate I22 code with an I21 code; sequencing depends on the encounter.

Subsequent Type 2 MI follows I21.A1 guidance. Mixed-type events require review of the appropriate I21 codes rather than automatic use of I22.

Similar Encounters Can Produce Different Coding Decisions

These examples are hypothetical.

Scenario	Coding approach
A patient with Type 1 NSTEMI transfers for continued treatment of the same infarction.	Review continued I21.4 reporting. Transfer alone does not support I22.2.
A patient experiences a separately documented new Type 1 NSTEMI within four weeks of an initial Type 1 NSTEMI.	Review I22.2 with I21.4 and sequence according to the encounter.
A patient returns with symptoms, but no new infarction is established.	Do not assign a subsequent-MI code merely because the patient returned.

The record should establish the original onset, any separate event, and the reason for the encounter.

Aftercare and Old MI Should Not Be Chosen Automatically

Beyond the acute interval, assess whether the patient is still receiving treatment for the infarction, or if the myocardial infarction (MI) is old or healed. Old or healed MI’s do not require additional treatment and should be assigned code I25.2.

Coding a case in which the patient has received treatment for a myocardial infarction should include the appropriate after-care codes.

The chronological position of a diagnosis in a patient’s record is not always an indication that the physician views the condition as acute. A physician may have recorded a healed condition in a patient’s history.

When a patient is receiving treatment for more than one condition, the code assigned should be for the condition that is the reason for the current visit.

NSTEMI That Evolves to STEMI Has Specific Guidelines

A type 1 NSTEMI becomes a STEMI and is therefore coded as a STEMI.

If a type 1 STEMI becomes an NSTEMI as a result of thrombolytic therapy, it is to remain coded as a STEMI.

Always refer to the documented progression of the case and the treatment applied.

Do not generically apply the concept of always selecting the more serious diagnosis.

SUSPECTED NSTEMI VARIES BASED ON CARE SETTING

Although there are no outright exceptions for inpatient settings, established diagnostic criteria may not always be required for discharges to outpatient settings. If uncertain diagnoses are communicated for outpatient settings (e.g., emergency department (ED), observation services, etc.) it is appropriate to assign the diagnosis to the highest level of certainty.

An admission diagnosis may not always be the diagnosis documented at the time of the patient’s discharge from an inpatient facility.

Separate the provision of professional services from inpatient facility claims.

Generally, healthcare services provided in a hospital do not always equate to inpatient facility healthcare services.

Documentation That Supports a Clear Coding Decision

A defensible record answers the questions that affect classification. It does not need repetitive descriptions of the same finding.

Look for:

The final diagnosis and any specifically documented MI type.
The event history, including onset and any separate infarction.
The underlying cause, when established.
The provider’s assessment of relevant symptoms, laboratory findings, ECG and imaging.
The reason for care, including treatment and monitoring.
Resolution of conflicting documentation across the record.

Missing wall location alone does not automatically justify an NSTEMI query because I21.4 is not divided by site.

Identify Clinical Conflicts Without Promoting a Diagnosis

If separate notations are made for NSTEMI and for non-ischaemic myocardial injury for example, determine the reconciling/conflicting statements and supporting clinical data.

Questions to the responsible provider, when sought through the employer’s defined query process, should be open-ended to solicit the most information and not be biased to promote a specific diagnosis.

Ensure the express purpose of the query is to clarify the diagnosis. Be conscious of the sequence of queries. For example, do not request clarification of NSTEMI to support billing; clarification of the diagnosis should precede any queries regarding reimbursement. The rationale for the query should be documented in the medical record and retained in the medical record workflow to support and facilitate review of the record by a peer.

Medicare and Private Insurance Require Separate Payment Reviews

The NSTEMI ICD 10 code does not change because the patient’s insurance changes. Coverage and reimbursement requirements are separate from diagnosis classification.

For Medicare, review the billed service and any applicable national or local coverage requirements. A valid diagnosis code does not establish medical necessity for every test or procedure.

For private insurance, consult the specific plan’s instructions. Do not assume that documentation requests, authorization rules, or appeal requirements are identical across insurers.

A claim review should answer three questions:

Does the code match the documented diagnosis?
Does the record support the diagnosis and service?
Does the claim meet the applicable payer requirements?

When a denial occurs, address its stated basis. A coding error may call for a corrected claim; a missing-record request may require supporting documentation; a clinical-validation dispute may require a focused appeal.

Do not change a diagnosis solely to obtain payment or assume that every claim needs the complete medical record attached.

Shortcuts That Support NSTEMI Claims

Reporting each related code: While I21.4 and I21.A1 are related and I22.2 is unrelated, they will often appear in look up lists together. This does not allow for combined reporting.

Accepting duplication: Confirm the diagnosis was not clarified and/or documented in the visit.

Reporting a code without reviewing the rules: For Example, Other comorbid conditions,symptoms, tobacco related codes, and other status codes must be evaluated.

Falsifying details: A more specific code is not better than a less specific code if there is no documentation to support the more specific code.

Applying outdated rules: Educational materials are still required to be integrated with Rules and Instructions pertaining to adjudication of the claim.

NSTEMI Coding FAQs

Can I assign I21.4 when the provider documents only NSTEMI?

Generally, yes, for acute NSTEMI without documentation directing to another MI type or subsequent-event category. Review the complete record and event circumstances before finalizing the code.

Does Type 2 NSTEMI require I21.4 and I21.A1 together?

No. Assign I21.A1 for the same documented Type 2 event and follow applicable underlying-cause sequencing. NSTEMI wording alone does not justify adding I21.4.

Can elevated troponin establish an NSTEMI diagnosis for coding?

No. A laboratory result alone does not authorize the coder to diagnose an infarction. Review the provider’s assessment and clarify genuine uncertainty or contradictions.

Does a hospital transfer qualify for I22.2?

Not by itself. I22.2 requires a qualifying new NSTEMI. Continued treatment of the same infarction does not become a subsequent event because the facility changes.

Is I21.4 complete without an artery or wall specified?

Yes. I21.4 does not require a site extension. A complete diagnosis code still needs appropriate documentation and does not guarantee reimbursement.

Should a healed NSTEMI remain coded as I21.4?

Not automatically. Distinguish acute MI care, ongoing aftercare, and an old or healed infarction requiring no further care. The record should support the classification selected.

Before You Release the Claim

Confirm the provider’s final diagnosis and specifically documented MI type.
Resolve genuine conflicts in the medical record.
Establish whether the encounter concerns the same infarction or a separate event.
Apply the acute and subsequent-MI interval rules.
Distinguish facility, professional, inpatient and outpatient reporting requirements.
Verify the complete code, exclusions and sequencing instructions.
Add other diagnoses and status codes only when applicable.
Match the code release to the claim and address the payer’s actual requirements.

Aftercare and Old MI Should Not Be Chosen Automatically Beyond the acute interval, assess whether the patient is still receiving treatment for the infarction, or if the myocardial infarction (MI) is old or healed. Old or healed MI’s do not require additional treatment and should be assigned code I25.2. Coding a case in which the patient has received treatment for a myocardial infarction should include the appropriate after-care codes. The chronological position of a diagnosis in a patient’s record is not always an indication that the physician views the condition as acute. A physician may have recorded a healed condition in a patient’s history. When a patient is receiving treatment for more than one condition, the code assigned should be for the condition that is the reason for the current visit. NSTEMI That Evolves to STEMI Has Specific Guidelines A type 1 NSTEMI becomes a STEMI and is therefore coded as a STEMI. If a type 1 STEMI becomes an NSTEMI as a result of thrombolytic therapy, it is to remain coded as a STEMI. Always refer to the documented progression of the case and the treatment applied. Do not generically apply the concept of always selecting the more serious diagnosis. SUSPECTED NSTEMI VARIES BASED ON CARE SETTING Although there are no outright exceptions for inpatient settings, established diagnostic criteria may not always be required for discharges to outpatient settings. If uncertain diagnoses are communicated for outpatient settings (e.g., emergency department (ED), observation services, etc.) it is appropriate to assign the diagnosis to the highest level of certainty. An admission diagnosis may not always be the diagnosis documented at the time of the patient’s discharge from an inpatient facility. Separate the provision of professional services from inpatient facility claims. Generally, healthcare services provided in a hospital do not always equate to inpatient facility healthcare services. Documentation That Supports a Clear Coding Decision A defensible record answers the questions that affect classification. It does not need repetitive descriptions of the same finding. Look for: The final diagnosis and any specifically documented MI type. The event history, including onset and any separate infarction. The underlying cause, when established. The provider’s assessment of relevant symptoms, laboratory findings, ECG and imaging. The reason for care, including treatment and monitoring. Resolution of conflicting documentation across the record. Missing wall location alone does not automatically justify an NSTEMI query because I21.4 is not divided by site. Identify Clinical Conflicts Without Promoting a Diagnosis If separate notations are made for NSTEMI and for non-ischaemic myocardial injury for example, determine the reconciling/conflicting statements and supporting clinical data. Questions to the responsible provider, when sought through the employer's defined query process, should be open-ended to solicit the most information and not be biased to promote a specific diagnosis. Ensure the express purpose of the query is to clarify the diagnosis. Be conscious of the sequence of queries. For example, do not request clarification of NSTEMI to support billing; clarification of the diagnosis should precede any queries regarding reimbursement. The rationale for the query should be documented in the medical record and retained in the medical record workflow to support and facilitate review of the record by a peer. Medicare and Private Insurance Require Separate Payment Reviews The NSTEMI ICD 10 code does not change because the patient’s insurance changes. Coverage and reimbursement requirements are separate from diagnosis classification. For Medicare, review the billed service and any applicable national or local coverage requirements. A valid diagnosis code does not establish medical necessity for every test or procedure. For private insurance, consult the specific plan’s instructions. Do not assume that documentation requests, authorization rules, or appeal requirements are identical across insurers. A claim review should answer three questions: Does the code match the documented diagnosis? Does the record support the diagnosis and service? Does the claim meet the applicable payer requirements? When a denial occurs, address its stated basis. A coding error may call for a corrected claim; a missing-record request may require supporting documentation; a clinical-validation dispute may require a focused appeal. Do not change a diagnosis solely to obtain payment or assume that every claim needs the complete medical record attached. Shortcuts That Support NSTEMI Claims Reporting each related code: While I21.4 and I21.A1 are related and I22.2 is unrelated, they will often appear in look up lists together. This does not allow for combined reporting. Accepting duplication: Confirm the diagnosis was not clarified and/or documented in the visit. Reporting a code without reviewing the rules: For Example, Other comorbid conditions,symptoms, tobacco related codes, and other status codes must be evaluated. Falsifying details: A more specific code is not better than a less specific code if there is no documentation to support the more specific code. Applying outdated rules: Educational materials are still required to be integrated with Rules and Instructions pertaining to adjudication of the claim. NSTEMI Coding FAQs Can I assign I21.4 when the provider documents only NSTEMI? Generally, yes, for acute NSTEMI without documentation directing to another MI type or subsequent-event category. Review the complete record and event circumstances before finalizing the code. Does Type 2 NSTEMI require I21.4 and I21.A1 together? No. Assign I21.A1 for the same documented Type 2 event and follow applicable underlying-cause sequencing. NSTEMI wording alone does not justify adding I21.4. Can elevated troponin establish an NSTEMI diagnosis for coding? No. A laboratory result alone does not authorize the coder to diagnose an infarction. Review the provider’s assessment and clarify genuine uncertainty or contradictions. Does a hospital transfer qualify for I22.2? Not by itself. I22.2 requires a qualifying new NSTEMI. Continued treatment of the same infarction does not become a subsequent event because the facility changes. Is I21.4 complete without an artery or wall specified? Yes. I21.4 does not require a site extension. A complete diagnosis code still needs appropriate documentation and does not guarantee reimbursement. Should a healed NSTEMI remain coded as I21.4? Not automatically. Distinguish acute MI care, ongoing aftercare, and an old or healed infarction requiring no further care. The record should support the classification selected. Before You Release the Claim Confirm the provider’s final diagnosis and specifically documented MI type. Resolve genuine conflicts in the medical record. Establish whether the encounter concerns the same infarction or a separate event. Apply the acute and subsequent-MI interval rules. Distinguish facility, professional, inpatient and outpatient reporting requirements. Verify the complete code, exclusions and sequencing instructions. Add other diagnoses and status codes only when applicable. Match the code release to the claim and address the payer’s actual requirements.

Blog Grid