ICD-10 Coding for Non-ST Elevation Myocardial Infarction(E11.9, I21.4, I21.4B)
Learn about ICD-10 coding for non-ST elevation myocardial infarction (NSTEMI), including primary codes, documentation requirements, and common pitfalls.
Complete code families applicable to Non-ST Elevation Myocardial Infarction
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| I21.4 | Non-ST elevation (NSTEMI) myocardial infarction | Use when NSTEMI is explicitly documented with elevated troponin and no ST elevation on ECG. |
|
| I21.A1 | Myocardial infarction type 2 | Use when MI is secondary to another condition causing an imbalance in oxygen supply and demand. |
|
| I22.2 | Subsequent non-ST elevation (NSTEMI) myocardial infarction | Use for NSTEMI occurring within 28 days of a previous MI. |
|
Clinical Decision Support
Always review the patient's clinical documentation thoroughly. When in doubt, choose the more specific code and ensure documentation supports it.
Key Information
Essential facts and insights aboutNon-ST Elevation Myocardial Infarction
Alternative codes to consider when ruling out similar conditions
Documentation & Coding Risks
Avoid these common issues when documenting Non-ST Elevation Myocardial Infarction.
Failure to document MI type
Impact
Clinical: Inaccurate treatment plans., Regulatory: Non-compliance with coding standards., Financial: Potential claim denials.
Mitigation
Educate clinicians on documentation requirements., Use templates to ensure completeness.
Misclassifying Type 2 MI as NSTEMI
Impact
Reimbursement: Incorrect coding may lead to denied claims., Compliance: Non-compliance with coding guidelines., Data Quality: Inaccurate clinical data representation.
Mitigation
Ensure documentation specifies Type 2 MI and underlying cause.
Incorrect sequencing of subsequent MI codes
Impact
Reimbursement: Incorrect DRG assignment., Compliance: Violation of coding rules., Data Quality: Misleading patient history.
Mitigation
Always sequence I22.2 after the initial MI code.
Incorrect MI Type Coding
Impact
Risk of coding NSTEMI when Type 2 MI is present.
Mitigation
Implement regular training and audits.