Why the study?
Recommendations concerning antiplatelet therapy were published across various separate ESC guidelines, creating a need to compile them into a single document with a practical decision algorithm.
This review consolidates multiple ESC guidelines into a unified algorithm to guide the type and duration of dual antiplatelet therapy following PCI.
May streamline post-PCI DAPT decisions using ESC guidance; extends guideline synthesis but leaves open prospective outcome validation.
This review is a summary of the European Society of Cardiology (ESC) guidelines focused on dual antiplatelet therapy in patients after percutaneous coronary interventions (PCI). Given a large number of recommendations concerning antiplatelet therapy published in various ESC guidelines, the main goal of this paper was to compile these separate recommendations into one document. In addition, we set out to present the current state of knowledge and create an algorithm that would be based on all of these guidelines in hope that it would allow quick navigation when selecting the type and duration of dual antiplatelet therapy (DAPT) depending on the clinical scenario with a special emphasis on evaluating both ischemic and bleeding risks. The review is based on the ESC guidelines on the diagnosis and management of chronic coronary syndromes (2019), revascularization (2018), acute myocardial infarction in patients presenting with ST-segment elevation myocardial infarction (STEMI) (2017), DAPT (2017), and acute coronary syndromes in patients presenting without persistent ST-segment elevation (NSTE-ACS) (2020). The review also provides brief information on the most important studies and meta-analyses in this area, as well as practical pointers for management in the case of bleeding complications and before urgent surgery in patients on DAPT.
No takes yet. Share an insight, caveat, or question.
Hudzik et al. (2022) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: