Effective drug-allergy checking: methodological and operational issues

Adverse drug events cause a large number of injuries, and adverse events caused by medications administered in the face of known allergies represent an important preventable cause of patient harm. Computerized systems can effectively prevent reactions due to known allergies, but building an effective allergy prevention feature is challenging and presents many interesting informatics issues that have both methodological and operational implications. In this paper, we present the experiences from one large delivery system in delivering allergy-related decision support, discuss some of the different approaches that we have used, and then propose a future approach. We also discuss the methodological, behavioral, and operational issues that have arisen which have a major impact on success. Key factors in drug-allergy checking include storing patient allergy data in a single common repository, representing allergy data using suitable terminologies and creating groups of allergies for inferencing purposes, being judicious about which allergy warnings to display, conveying the reaction that the patient has experienced when exposed to the drug to inform the provider of the importance of the warning, and perhaps most important, implementing strategies to optimize the likelihood that allergy information will be entered.

[1]  Michael M. Wagner,et al.  Review: Accuracy of Data in Computer-based Patient Records , 1997, J. Am. Medical Informatics Assoc..

[2]  A. Wall,et al.  Book ReviewTo Err is Human: building a safer health system Kohn L T Corrigan J M Donaldson M S Washington DC USA: Institute of Medicine/National Academy Press ISBN 0 309 06837 1 $34.95 , 2000 .

[3]  Jonathan M. Teich,et al.  Improving allergy alerting in a computerized physician order entry system , 2000, AMIA.

[4]  D. Bates,et al.  Effect of computerized physician order entry and a team intervention on prevention of serious medication errors. , 1998, JAMA.

[5]  John J. Marciniak,et al.  Encyclopedia of Software Engineering , 1994, Encyclopedia of Software Engineering.

[6]  Thomas H. Payne,et al.  Characteristics and override rates of order checks in a practitioner order entry system , 2002, AMIA.

[7]  J. McCulloch,et al.  CHAPTER 7 – Implications for Prevention , 1972 .

[8]  G J Kuperman,et al.  Patient safety and computerized medication ordering at Brigham and Women's Hospital. , 2001, The Joint Commission journal on quality improvement.

[9]  N. Laird,et al.  Incidence of adverse drug events and potential adverse drug events , 1995 .

[10]  D. Bates,et al.  Systems analysis of adverse drug events. ADE Prevention Study Group. , 1995, JAMA.

[11]  Jonathan M. Teich,et al.  The Brigham integrated computing system (BICS): advanced clinical systems in an academic hospital environment , 1999, Int. J. Medical Informatics.

[12]  N. Dickey,et al.  Systems analysis of adverse drug events. , 1996, JAMA.

[13]  Alastair Baker,et al.  Crossing the Quality Chasm: A New Health System for the 21st Century , 2001, BMJ : British Medical Journal.

[14]  Judy Edworthy,et al.  Warning design : a research prospective , 1996 .

[15]  E. Patterson,et al.  Cognitive Engineering : Issues in User-Centered System Design , 2000 .

[16]  David W Bates,et al.  Medication errors observed in 36 health care facilities. , 2002, Archives of internal medicine.

[17]  Robert Grundmeier,et al.  Housestaff attitudes toward computer-based clinical decision support , 1999, AMIA.

[18]  S D Small,et al.  Incidence of adverse drug events and potential adverse drug events. Implications for prevention. ADE Prevention Study Group. , 1995, JAMA.

[19]  John W. Senders,et al.  Human Error: Cause, Prediction, and Reduction , 1991 .

[20]  N. Laird,et al.  Incidence of Adverse Drug Events and Potential Adverse Drug Events: Implications for Prevention , 1995 .

[21]  E. Cook,et al.  Drug complications in outpatients , 2000, Journal of general internal medicine.