• Journal of patient safety · Dec 2013

    Comparative Study

    Automated adverse event detection collaborative: electronic adverse event identification, classification, and corrective actions across academic pediatric institutions.

    • David C Stockwell, Eric Kirkendall, Stephen E Muething, Elizabeth Kloppenborg, Hima Vinodrao, and Brian R Jacobs.
    • From the *Children's National Medical Center; †The George Washington University School of Medicine, Washington, District of Columbia; ‡Cincinnati Children's Hospital Medical Center, Cincinnati, Ohio; and §Center for Pediatric Informatics, at Children's National Medical Center, Washington, District of Columbia.
    • J Patient Saf. 2013 Dec 1;9(4):203-10.

    BackgroundHistorically, the gold standard for detecting medical errors has been the voluntary incident reporting system. Voluntary reporting rates significantly underestimate the number of actual adverse events in any given organization. The electronic health record (EHR) contains clinical and administrative data that may indicate the occurrence of an adverse event and can be used to detect adverse events that may otherwise remain unrecognized. Automated adverse event detection has been shown to be efficient and cost effective in the hospital setting. The Automated Adverse Event Detection Collaborative (AAEDC) is a group of academic pediatric organizations working to identify optimal electronic methods of adverse event detection. The Collaborative seeks to aggregate and analyze data around adverse events as well as identify and share specific intervention strategies to reduce the rate of such events, ultimately to deliver higher quality and safer care. The objective of this study is to describe the process of automated adverse event detection, report early results from the Collaborative, identify commonalities and notable differences between 2 organizations, and suggest future directions for the Collaborative.MethodsIn this retrospective observational study, the implementation and use of an automated adverse event detection system was compared between 2 academic children's hospital participants in the AAEDC, Children's National Medical Center, and Cincinnati Children's Hospital Medical Center. Both organizations use the EHR to identify potential adverse events as designated by specific electronic data triggers. After gathering the electronic data, a clinical investigator at each hospital manually examined the patient record to determine whether an adverse event had occurred, whether the event was preventable, and the level of harm involved.ResultsThe Automated Adverse Event Detection Collaborative data from the 2 organizations between July 2006 and October 2010 were analyzed. Adverse event triggers associated with opioid and benzodiazepine toxicity and intravenous infiltration had the greatest positive predictive value (range, 47%- 96%). Triggers associated with hypoglycemia, coagulation disturbances, and renal dysfunction also had good positive predictive values (range, 22%-74%). In combination, the 2 organizations detected 3,264 adverse events, and 1,870 (57.3%) of these were preventable. Of these 3,264 events, clinicians submitted only 492 voluntary incident reports (15.1%).ConclusionsThis work demonstrates the value of EHR-derived data aggregation and analysis in the detection and understanding of adverse events. Comparison and selection of optimal electronic trigger methods and recognition of adverse event trends within and between organizations are beneficial. Automated detection of adverse events likely contributes to the discovery of opportunities, expeditious implementation of process redesign, and quality improvement.

      Pubmed     Full text   Copy Citation     Plaintext  

      Add institutional full text...

    Notes

     
    Knowledge, pearl, summary or comment to share?
    300 characters remaining
    help        
    You can also include formatting, links, images and footnotes in your notes
    • Simple formatting can be added to notes, such as *italics*, _underline_ or **bold**.
    • Superscript can be denoted by <sup>text</sup> and subscript <sub>text</sub>.
    • Numbered or bulleted lists can be created using either numbered lines 1. 2. 3., hyphens - or asterisks *.
    • Links can be included with: [my link to pubmed](http://pubmed.com)
    • Images can be included with: ![alt text](https://bestmedicaljournal.com/study_graph.jpg "Image Title Text")
    • For footnotes use [^1](This is a footnote.) inline.
    • Or use an inline reference [^1] to refer to a longer footnote elseweher in the document [^1]: This is a long footnote..

    hide…