Adverse events targeted by drug-drug interaction alerts in hospitalized patients

James Gatenby, Magnus Blomqvist, Rosemary Burke, Angus Ritchie, Kathy Gibson, Asad E. Patanwala

Research output: Contribution to journalArticlepeer-review

2 Scopus citations

Abstract

Objective: To identify the types of adverse drug events (ADEs) that drug-drug interaction (DDI) alerts are trying to prevent in hospitalized patients. Methods: This was a retrospective cross-sectional study conducted in a tertiary referral hospital in Australia. All DDI alerts encountered by prescribers during a 1-month period were evaluated for potential ADEs targeted for prevention. If the same DDI alert occurred for the same patient multiple times during hospitalization, it was counted only once (i.e. first alert). This was termed a ‘unique DDI alert’ for a given patient. The primary outcome was the type of ADE the alerts were trying to prevent. Results: There were 715 patients who had 1599 unique DDI alerts. The two most common potential ADEs (not mutually exclusive) that the alerts attempted to prevent were QTc prolongation or torsades de pointes (n = 1028/1599, 64 %), followed by extrapyramidal symptoms or neuroleptic malignant syndrome (n = 463/1599, 29 %). Either of these two potential ADEs were present in 83 % (n = 1329/1599) of unique DDI alerts. Conclusion: Alerting systems are primarily trying to prevent two types of potential ADEs, which were included in more than 80 % of DDI alerts. This has important implications for patient monitoring in hospitals.

Original languageEnglish (US)
Article number104266
JournalInternational Journal of Medical Informatics
Volume143
DOIs
StatePublished - Nov 2020

Keywords

  • Decision support systems clinical
  • Drug interactions
  • Electronic health records
  • Medication errors
  • Patient safety

ASJC Scopus subject areas

  • Health Informatics

Fingerprint

Dive into the research topics of 'Adverse events targeted by drug-drug interaction alerts in hospitalized patients'. Together they form a unique fingerprint.

Cite this