Key result
Review summarizes evidence and guidelines for optimal reperfusion strategies in STEMI with multivessel disease.
Why the study?
The optimal reperfusion strategy in patients with STEMI and multivessel coronary artery disease remains uncertain despite primary PCI being the gold standard treatment.
This review summarizes current evidence and guideline recommendations for managing multivessel disease in patients presenting with STEMI.
Comprehensive non-IRA evaluation may refine STEMI risk assessment; leaves open optimal management of multivessel disease.
Acute ST-segment elevation myocardial infarction (STEMI) typically arises from total occlusion of an epicardial coronary artery, most often due to atherosclerotic plaque rupture/erosion and subsequent thrombus formation. Granted this, important angiographic information for patients presenting with STEMI is not only about the status of infarct-related artery (IRA) but also about the atherosclerotic disease burden and disease severity of non-IRA vessels. Previous studies have reported that multivessel coronary artery disease is found in approximately 50% of patients with STEMI undergoing primary percutaneous coronary intervention (PCI). Primary PCI is now considered the gold standard in the treatment for patients with STEMI; however, the optimal reperfusion strategy in patients with STEMI and multivessel disease (MVD) remains uncertain. In this review, we summarize the available evidence on treatment options for patients with STEMI and MVD and highlight current guideline recommendations on this topic.
No takes yet. Share an insight, caveat, or question.
D’Amico et al. (2018) conducted a review in STEMI with multivessel disease. Revascularization strategies was evaluated. This review summarizes the available evidence and current guideline recommendations on treatment options and optimal reperfusion strategies for patients with STEMI and multivessel disease.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: