RESUMEN
Introduction: Code status discussions are poorly understood by patients and variably performed by admitting providers, yet they are used as a quality metric. Surgical specialties, such as Vascular Surgery, admit patients with urgent and life-threatening illness. Surgical trainees are less likely to receive communication skills interventions when compared with nonsurgical specialties. Without a documented code status, nurses and physicians lack guidance on patient preference in the case of cardiopulmonary arrest and may deliver unwanted measures, which may also result in poor outcomes. Methods: We conducted a before-after Plan-Do-Study-Act quality improvement project between May 2018 and May 2019. A needs assessment included baseline code status documentation rates for the Vascular Surgery department admissions. A communication skills training (CST) and documentation intervention was provided to all Vascular Surgery trainees and advance practice providers (APPs). Departmental e-mails were sent over the 12-month intervention period, which demonstrated the code status documentation rates and served as reminders to document code status. Results: A total of 29 vascular surgery trainees and APPs received the intervention. At completion of the intervention, learners reported increased comfort initiating a code status discussion, making a recommendation for cardiopulmonary resuscitation (CPR) status, and having a strategy to discuss code status. A total of 2762 patient admissions were reviewed, with 1562 patient admissions occurring during the 12-month intervention period. The average code status documentation rate for the three months before the intervention was 7.8%. At the end of the 12-month intervention, documentation rates were 44.9% and 6 months after completion of the study period, average rates remained 45.2%. There was no change in admission rates during the study period. Discussion: CST and regular reminders increased vascular surgery residents' and APPs' comfort in engaging in code status discussions. After intervention, documentation of code status discussions increased with persistence up to six months after the intervention.