Coding a Patient's Past Heart Attack Without Overcomplicating Things
Coding for personal history of NSTEMI comes up more often than you'd think in outpatient settings. A patient walks in for a routine physical or a specialist follow-up, and their chart shows they had a non-ST elevation myocardial infarction three years ago. You need to document that accurately. The official code is Z86.718, which reads as personal history of other diseases of the circulatory system. It's not intuitive at first, because there's no standalone code that says "personal history of NSTEMI" specifically. That's the first thing to understand before you go digging through the tabular list. Here's the straightforward breakdown. ICD-10-CM doesn't have a unique code specifically labeled for personal history of NSTEMI. Instead, it falls under the broader Z86.718 category. This code sits in Chapter 21, which covers factors influencing health status and contact with health services. The "Z" codes aren't diagnoses in the traditional sense — they're secondary codes that provide context about the patient's medical background. That distinction matters because it affects how you sequence them on a claim form. The code description covers personal histories that don't have their own specific classification. People miss this constantly. I once had a coder argue with me for twenty minutes because the code book didn't have a dedicated "history of NSTEMI" entry. I showed them the index entry under "History, personal — of — disease — circulatory system" and pointed directly to Z86.718. They were still not satisfied until they looked it up themselves. This is a well-known pain point in the coding community, and it's why many providers end up using Z86.79 instead, which is the catch-all for personal history of other diseases of the circulatory system. That's technically incorrect if Z86.718 applies, but the confusion is real and widespread.
Now, the practical part. When you're assigning this code, you need to confirm that the patient's NSTEMI is in the past and not active. If they're currently being treated for NSTEMI, you code the acute condition using I21.4, not a Z code. The difference between coding an active event versus a personal history code can change the entire DRG or APC assignment on an inpatient claim, which is where the revenue impact actually shows up. In my experience, about a third of the time this code gets pulled, the documentation doesn't clearly distinguish between an active issue and a resolved one. Always check the clinical notes before finalizing your assignment. There's also the sequencing question that nobody talks about enough. In the outpatient setting, Z86.718 typically goes as a secondary diagnosis. But if the reason for the visit is specifically related to the cardiac history — say the patient is there for a cardiology follow-up after their NSTEMI — some payers prefer you list it differently. Medicare and most commercial payers follow the same general rule: the reason for the encounter comes first, followed by the personal history code. But I've seen denial letters come back from regional Medicaid plans questioning the placement, so I always make sure my coding software generates the claim in the order the payer's guidelines specify rather than relying on default sequencing. One edge case that trips people up regularly: if the patient had both an STEMI and an NSTEMI at different points in their history, you still use Z86.718. There's no separate personal history code for STEMI either, so both fall under the same classification. I learned this the hard way when a patient came in with a documented history of both, and I initially tried to stack codes. The clearinghouse rejected it outright. One Z86.718 covers all prior myocardial infarction events, regardless of type. Simple in retrospect, but not obvious from the code descriptor alone.
The real friction point I deal with is documentation from physicians who write "history of NSTEMI" in the assessment without specifying the timeframe or whether it's resolved. The code itself doesn't require a date of the original event, but auditors will sometimes ask for it. I recommend pushing back gently on providers and asking them to clarify "remote" versus "recent" history. It doesn't change the code, but it creates a cleaner audit trail. I started doing this about two years ago after an internal audit flagged three claims where the personal history code lacked supporting documentation. Since then, I've had my team add a brief note confirming the event was in the past, and audit hit rate dropped to nearly zero on those cases. If you need to look this up quickly, the official ICD-10-CM index directs you to check "History, personal" under "disease, circulatory system." From there, you land on Z86.718. The tabular list confirms the inclusion terms and cross-references. It's not a complicated code once you know where to find it, but the lack of specificity in the descriptor is what causes the most errors in practice. One more thing that isn't covered in any coding manual: this code should not be used as a primary diagnosis on an outpatient claim unless the encounter is specifically for the management of the patient's personal history, which is extremely rare. Most encounters are for something else entirely — a hypertension check, a diabetes follow-up, a routine physical — and the NSTEMI history is just part of the clinical picture. Putting Z86.718 as primary is an automatic red flag for most payer edit checks.
Get the Full Details
