Why the study?
Elevated cardiac troponin is common in critically ill patients, but data on the impact of cardiology consultation on outcomes in this population without signs of ACS were lacking.
Does routine cardiology consultation improve mortality in critically ill medical ICU patients with elevated troponin levels and no signs of ACS?
Does routine cardiology consultation improve mortality in critically ill medical ICU patients with elevated troponin levels and no signs of ACS?
Routine cardiology consultation for critically ill medical ICU patients with elevated troponin but no ACS does not improve mortality and is associated with increased downstream testing, new medications, and higher 30-day readmission rates.
Elevated cTn may complicate ACS diagnosis in the ICU; leaves open its prognostic value in critically ill patients.
Cardiac troponin (cTn) is used to diagnose acute coronary syndrome (ACS). However, cTn can also be elevated in critically ill patients secondary to demand ischaemia or myocardial injury. In a meta-analysis of 20 different studies involving critically ill patients, cTn was found to be elevated in 43% of patients.1 Prior studies have evaluated the significance of cTn as a prognostic factor and mortality predictor in different clinical entities in intensive care units (ICU).2,3 However, the data on the impact of cardiology consultation on the outcomes in this specific context of critical care patients are limited. While prior studies have addressed such an impact on the outcomes among different groups of surgical patients,4,5 to the authors’ knowledge, no prior studies have examined that impact on critically ill patients with elevated cTn. This study aimed to investigate the impact of cardiology consultation on critically ill patients in the medical ICU with elevated cTn and no signs of ACS.
No takes yet. Share an insight, caveat, or question.
Kousa et al. (2020) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: