When a patient receives a stent to open a blocked coronary artery, precise ICD 10 coding captures the clinical story and drives reimbursement. Status post stent placement describes the healed or healing state after the procedure, and correct sequencing affects both clarity and compliance.
This guide walks through key documentation scenarios, code choices, and practical workflow tips specific to status post stent placement in ICD 10, supported by a focused summary table and real-world queries from clinicians.
Summary Of Common ICD 10 Scenarios For Status Post Stent
| Clinical Scenario | Primary ICD 10 Code | Status Post Modifier Needed | Additional Coding Notes |
|---|---|---|---|
| Routine status post drug-eluting stent in stable coronary artery disease | I25.810 | No | May include history of PCI targeting the lesion |
| Status post bare metal stent with chest pain evaluation | I25.810 | No | Use additional code for any current symptoms |
| Status post stent with documented restenosis | I25.829 | No | Specify type of restenosis if available in documentation |
| Status post multiple stents including bifurcation lesions | I25.810, I25.829 | No | Sequence for the principal reason for the encounter |
Status Post Stent Placement In The Encounter
During an outpatient or inpatient visit, clinicians document the anatomical status and functional impact following stent placement. Using I25.810 for known coronary artery disease with an angioplasty or stent component allows clinicians to reflect the ongoing management of atherosclerotic disease without active thrombosis or embolism. When the reason for the visit is surveillance testing or medication adjustment, explicitly stating status post stent placement clarifies that the lesion has been treated and the focus is on maintenance and monitoring.
Sequencing depends on the encounter context. If the patient presents for evaluation of ischemia related to the stented segment, I25.810 may be sequenced before symptom codes, underscoring the relationship between the treated lesion and current findings. Coders should verify that documentation confirms the stent is not the site of an acute complication such as thrombosis, which would require different coding and potentially stronger clinical documentation.
Laterality and target vessel information are typically not captured in the code itself but may appear in procedural notes; these details support clinical specificity and audit clarity. Consistent use of status post language in progress notes, operative reports, and discharge summaries reduces ambiguity and supports accurate code assignment across encounters.
Differentiating Stable Disease From Complications
Stable Status Post Stent Versus In-Stent Thrombosis
Stable status post stent placement assumes the stent is in place and functioning, whereas acute in-stent thrombosis represents a critical complication. Documentation of thrombosis requires distinct coding, often involving acute myocardial infarction or acute coronary thrombosis codes, depending on clinical details. Coders should query clinicians when the timeline between stent placement and the current event is unclear or when procedural reports do not explicitly rule out acute stent related events.
Restenosis And Reintervention
Restenosis within a previously stented segment is captured with I25.829, and any reintervention performed during the same encounter can be sequenced based on medical necessity. When restenosis drives the current ischemia or revascularization, linking the code for restenosis with procedural codes enhances the diagnostic justification. Clear documentation of surveillance findings, functional testing results, and intervention intent supports precise code assignment and reduces the risk of denials.
Documentation Best Practices For Coders
Accurate coding for status post stent placement begins with detailed provider documentation that specifies the type of stent, date of placement, current functional status of the treated vessel, and any ongoing antiplatelet therapy. When notes reference history of percutaneous transluminal coronary angioplasty with stent, coders should map this to I25.810 and sequence based on the encounter purpose. Detailed operative reports and device level descriptions provide the specificity needed for secondary diagnoses and for tracking complications over time.
Cross referencing with procedural data such as CPT codes for PCI and imaging results adds another layer of verification, ensuring that billed diagnoses align with performed services. Flagging ambiguous phrases like stent occlusion without further clarification prompts timely clinician queries and reduces the likelihood of incorrect code linkage. Standardized templates in the electronic health record that prompt for stent type, target vessel, and current clinical status can streamline documentation and coding accuracy.
Key Takeaways For Clinicians And Coders
- Use I25.810 to represent stable status post coronary stent placement in known coronary artery disease without active thrombosis.
- Sequence based on the encounter purpose, linking symptom codes when chest pain or ischemia drives the visit.
- Document stent type, date of procedure, target vessel, and current vessel status to support accurate coding.
- Query providers when documentation is ambiguous about acute thrombosis, restenosis, or the relationship to current symptoms.
- Align ICD 10 codes with corresponding CPT and Z codes to reflect procedures, long term therapy, and ongoing management.
FAQ
Reader questions
What code should I use when a patient is seen for medication adjustment and follow-up after a drug-eluting stent placed three years ago?
I25.810, with possible Z79.821 if the provider documents continued dependence on antiplatelet therapy, reflects the known coronary disease status post stent and captures the ongoing management context.
How do I code a visit where the patient has chest pain and a documented history of coronary stents, but the workup shows no acute ischemia at the stented segment?
Assign I25.810 for the known coronary artery disease with stent history, then list the symptom code for chest pain, such as R07.9, to represent the current evaluation while clarifying the clinical relationship.
Can I25.829 be used alongside I25.810 in the same encounter for a patient with documented restenosis after a prior stent placement?
Yes, I25.829 may be reported with I25.810 when documentation supports restenosis as a distinct condition being managed during the encounter; sequence based on the primary reason for the visit and clinical severity.
What documentation elements are essential to support accurate coding for status post stent placement with percutaneous coronary intervention?
Provider notes should specify stent type, implantation date, target vessel, procedural results, current ischemia status, ongoing antiplatelet regimen, and any restenosis or complications to ensure precise code assignment and audit readiness.