Why the study?
While the 2020 ESC 0-hr/1-hr algorithm using hs-cTnI is well-established in controlled studies, real-world implementation remains challenging.
Does the 2020 ESC 0-hr/1-hr algorithm using hs-cTnI accurately diagnose NSTE-ACS and stratify risk in patients with chest pain?
Does the 2020 ESC 0-hr/1-hr algorithm using hs-cTnI accurately diagnose NSTE-ACS and stratify risk in patients with chest pain?
The 2020 ESC 0-hr/1-hr hs-cTnI algorithm is highly accurate and safe for rapid triage of suspected NSTE-ACS in real-world practice.
Background: The 2020 European Society of Cardiology (ESC) 0-hr/1-hr algorithm using high-sensitivity cardiac troponin I (hs-cTnI) for non-ST-segment elevation acute coronary syndrome (NSTE-ACS) aims at early diagnosis and shorter emergency department (ED) stays. While this algorithm has been well-established in controlled studies, real-world implementation remains challenging. We evaluated the algorithm's clinical performance and risk stratification capability in patients with chest pain or discomfort. Methods: We measured hs-cTnI in 4,678 patients suspected of NSTE-ACS between August 2022 and July 2023, using an Atellica IM Analyzer (Siemens Healthineers, Erlangen, Germany). We categorized patients into rule-in, observe, or rule-out groups according to the algorithm and assessed its diagnostic performance for NSTE-ACS. The final diagnosis of NSTE-ACS was adjudicated by two independent physicians. Additionally, we evaluated 30-day all-cause mortality, hazard risk, and ED length of stay across the three groups. Results: <0.001). Conclusions: The 2020 ESC 0-hr/1-hr algorithm demonstrates excellent diagnostic accuracy without false rule-outs and effective risk stratification, and contributes to efficient ED throughput, supporting its clinical utility in real-world emergency settings.
No takes yet. Share an insight, caveat, or question.
Ha et al. (2025) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: