Key result
Recurrent myocardial infarction following acute coronary syndrome is associated with a higher risk of cardiovascular events and mortality, requiring complete revascularization and secondary prevention.
Why the study?
Recurrent myocardial infarction is common and carries higher cardiovascular risk after ACS, but controversy remains regarding its definition and management, with no dedicated studies conducted to date.
Recurrent MI after ACS is associated with high mortality and cardiovascular risk, highlighting the need for complete revascularization and optimal secondary prevention despite a lack of dedicated trials.
Recurrent MI flags high-risk ACS patients for closer surveillance; leaves open whether complete revascularization improves outcomes in prospective trials.
Recurrent myocardial infarction (re-MI) is a common event following acute coronary syndrome (ACS), especially during the first year. According to epidemiological studies, patients who experience re-MI are at higher risk of all-cause cardiovascular events and mortality. The cornerstones of re-MI prevention include complete functional coronary revascularization, effective dual antiplatelet therapy and secondary prevention strategies. Notwithstanding this, some controversy still exists on the definition and management of re-MI, and no dedicated studies have been designed or conducted so far in this setting. We here provide an overview of epidemiological and prognostic data on ACS patients experiencing re-MI, along with current available treatment and preventive options.
No takes yet. Share an insight, caveat, or question.
Luca et al. (2021) conducted a review in Recurrent myocardial infarction (re-MI) following acute coronary syndrome (ACS). Recurrent myocardial infarction following acute coronary syndrome is associated with a higher risk of cardiovascular events and mortality, requiring complete revascularization and secondary prevention.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: