Show Summary Details
Page of

Adverse Event Prevention and Management 

Adverse Event Prevention and Management
Chapter:
Adverse Event Prevention and Management
Author(s):

Patrick J. Guffey

and Martin Culwick

DOI:
10.1093/med/9780199366149.003.0009
Page of

PRINTED FROM OXFORD MEDICINE ONLINE (www.oxfordmedicine.com). © Oxford University Press, 2020. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy and Legal Notice).

date: 30 November 2020

Adverse events are an unfortunate reality of caring for patients in our current healthcare system. Preventing and mitigating these events are an important part of quality improvement. First, an understanding of what events occur and how often they are occurring is critical to planning improvements. Incident reporting systems are one way of gathering this information. Then, events should be categorized and analyzed for improvement. The failure mode and effects analysis (FMEA) and bow-tie diagram are two tools for this purpose. Once an event has occurred, consideration should be given to the caregivers as well as the patient when managing and resolving adverse events. Prevention requires strong analysis of events and recognition of both latent (system) and human causes. Interventions have different degrees of effectiveness, ranging from highly effective forcing functions, to marginally effective encouraging statements. There are four steps to event management: mitigation, immediate management, refractory management, and follow-up.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.