Key result
Quantitative results regarding the use of coronary angiography to assess cardiac complication risk were not reported due to abstract truncation.
Why the study?
Does coronary angiography assess cardiac complication risk in patients undergoing planned intermediate and high-risk non-cardiac interventions?
Observational (n=397)
Does coronary angiography assess cardiac complication risk in patients undergoing planned intermediate and high-risk non-cardiac interventions?
This retrospective analysis evaluates the prevalence of coronary atherosclerosis using coronary angiography to assess cardiac risk prior to intermediate and high-risk vascular surgeries.
No quantitative data from this Level 3 cohort; leaves open whether coronary angiography predicts complications before non-cardiac surgery.
Aim. To study the prevalence of coronary atherosclerosis in patients referred to planned non-cardiac interventions of intermediate and high risk. Material and methods. This retrospective analysis included 397 medical histories of patients who underwent planned interventions on aorta, carotid arteries, and peripheral arteries, PA (341 men and 56 women; mean age 60,0±13,0 years). Carotid endarterectomy (CEA) was performed in 161 patients (40,6%); PA intervention in 160 (40,3%); and abdominal aortic reconstruction in 76 (19,1%). Comparisons were performed by coronary angiography (CAG) results and immediate intervention results. Results. According to the CAG data, coronary artery (CA) stenosis
No takes yet. Share an insight, caveat, or question.
Сумин et al. (2013) conducted an observational in Planned non-cardiac interventions of intermediate and high risk (n=397). Coronary angiography was evaluated on Prevalence of coronary atherosclerosis and immediate intervention results. Quantitative results regarding the use of coronary angiography to assess cardiac complication risk were not reported due to abstract truncation.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: