Key result
Emergency clinical pathway system linked to ~13-point drop in in-hospital complications in STEMI survivors.
Why the study?
Rapid treatment within a limited time window is critical for acute STEMI, and there is a need to evaluate clinical pathways supported by specific information systems for emergency management.
Cohort (n=243)
No
Absolute Event Rate: 18% vs 31.4%
p-value: p=0.019
May support emergency pathway systems in STEMI care; leaves open confirmation in randomized trials.
Acute ST elevation myocardial infarction (STEMI) is a common acute and critical disease that requires rapid treatment within a limited window of time. In this study, we attempt to introduce a clinical pathway for the whole-process management of emergency STEMI based on the creation of a specific information system that matches the characteristics of emergency clinical work and evaluates their clinical value by quality control analysis. We deployed this system for 3 years and found that complications, heart failure, and medical costs during hospitalization were significantly reduced (p = 0.019) in patients with STEMI. By analyzing each link in the clinical pathway, our research indicates the clear clinical importance of developing methods to continuously improve data quality. Collectively, out research led to the optimization of an information system that will facilitate the clinical management of patients with STEMI.
No takes yet. Share an insight, caveat, or question.
Cao et al. (2022) conducted a cohort in Acute ST-segment elevation myocardial infarction (STEMI) (n=243). Emergency clinical pathway information system vs. Standard care prior to pathway implementation (2015-2017) was evaluated on Complications (survivors) (p=0.019). Implementation of an emergency clinical pathway information system significantly reduced the incidence of in-hospital complications from 31.4% to 18.0% among surviving patients with acute STEMI.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: