Prevalence of wireless smart-pump drug library update delays

Poching DeLaurentis, Kang Yu Hsu, Yuval Bitan

Research output: Contribution to journalArticlepeer-review

5 Scopus citations


Purpose. Results of a study to estimate the prevalence and severity of delays in wireless updates of smart-pump drug libraries across a large group of U.S. hospitals are reported. Methods. A prolonged smart-pump drug library update may result in patient harm if a pump is programmed with an incorrect limit setting at the time of drug administration. A retrospective study was conducted using smart-pump alert data extracted from the Regenstrief National Center for Medical Device Informatics (REMEDI) database. The study sample consisted of 49 hospitals in 5 states across the Midwest and Kentucky operated by 12 health systems; all the facilities used a specific brand of smart pump (BD Alaris, Beckton, Dickinson and Company) capable of generating alert data and had consistently contributed alert data to the REMEDI database over a 2-year period. An update delay was defined as the interval from the time a drug library version was replaced to the time of the last infusion alert triggered by the previous version during the study period. Results. Of the 12 health systems, 11 were found to have had drug library update delays during the study period, with delay medians ranging from 22 to 192 days. The overall delay minimum and maximum durations were 0 and 661 days. Conclusion. Substantial delays in completion of wireless updates of smart-pump drug libraries were common across a group of hospitals of various sizes.

Original languageEnglish
Pages (from-to)1140-1144
Number of pages5
JournalAmerican Journal of Health-System Pharmacy
Issue number15
StatePublished - 1 Aug 2018


  • Infusion pumps
  • Medical informatics
  • Patient safety

ASJC Scopus subject areas

  • Pharmacy
  • Pharmacology
  • Health Policy


Dive into the research topics of 'Prevalence of wireless smart-pump drug library update delays'. Together they form a unique fingerprint.

Cite this