Understanding the scope of downtime threats: A scoping review of downtime-focused literature and news media

Ethan P. Larsen, Arjun H. Rao, Farzan Sasangohar

Research output: Contribution to journalArticle

Abstract

Electronic health record downtimes are any period where the computer systems are unavailable, either for planned or unexpected events. During an unexpected downtime, healthcare workers are rapidly forced to use rarely-practiced, paper-based methods for healthcare delivery. In some instances, patient safety is compromised or data exposed to parties seeking profit. This review provides a foundational perspective of the current state of downtime readiness as organizations prepare to handle downtime events. A search of technical news media related to healthcare informatics and a scoping review of the research literature were conducted. Findings ranged from theoretical exploration of downtime to empirical direct comparison of downtime versus normal operation. Overall, 166 US hospitals experienced a total of 701 days of downtime in 43 events between 2012 and 2018. Almost half (48.8%) of the published downtime events involved some form of cyber-attacks. Downtime contingency planning is still predominantly considered through a top-down organizational focus. We propose that a bottom-up approach, involving the front-line clinical staff responsible for executing the downtime procedure, will be beneficial. Significant new research support for the development of contingency plans will be needed.

Original languageEnglish (US)
Pages (from-to)2660-2672
Number of pages13
JournalHealth Informatics Journal
Volume26
Issue number4
DOIs
StatePublished - Dec 2020

Keywords

  • downtime
  • electronic health records
  • healthcare informatics
  • hospitals
  • patient safety

ASJC Scopus subject areas

  • Health Informatics

Fingerprint Dive into the research topics of 'Understanding the scope of downtime threats: A scoping review of downtime-focused literature and news media'. Together they form a unique fingerprint.

Cite this