Disruptive behavior in the operating room: prevalence, consequences, prevention, and management

Purpose of review Disruptive workplace behavior can have serious consequences to clinicians, institutions, and patients. There is a range of disruptive behaviors, and the consequences are often underappreciated. The purpose of this manuscript is to review the definition, prevalence, consequences, prevention, and management of disruptive behavior in the operating room. Recent findings Although a small minority of operating room clinicians act disruptively, 98% of clinicians report having recently been exposed to disruptive behavior, with the average being 64 events per clinician per year. The causes include intrapersonal factors, workplace relationships, workplace logistics, and broader contextual factors. Disruptive behavior undermines patient care by decreasing individual and team clinical performance. It decreases clinician well being, sets a poor example for medical students who are susceptible to negative role models, and decreases hospital efficiency. The way that clinicians respond to disruptive behavior may either exacerbate or reduce the consequences of the behavior. In order to prevent disruptive behavior, the causes must be addressed. Institutions must have robust policies to deal with disruptive behavior and have preventive measures that include regular staff education. Whenever disruptive behavior does occur, it must be expeditiously addressed, which may include graded discipline. Summary Disruptive intraoperative behavior is prevalent and harms multiple parties in the operating room. Institutions require comprehensive measures to prevent the behavior and to mitigate consequences. Correspondence to Dr Eric Jacobsohn, MBChB, MHPE, FRCPC, AE215, Harry Medovy House – 671 William Avenue, Winnipeg, MB R3E 0Z2, Canada. Tel: +1 204 787 1518; e-mail: EJacobsohn@exchange.hsc.mb.ca Copyright © 2018 YEAR Wolters Kluwer Health, Inc. All rights reserved.

from Anaesthesiology via xlomafota13 on Inoreader https://ift.tt/2J7JXet
via IFTTT