Evidence map›Paper›PMID 28575417›Full record

ArticleJournal of the American Medical Informatics Association : JAMIA2018

Implications of electronic health record downtime: an analysis of patient safety event reports.

Ethan Larsen, Allan Fong, Christian Wernz, Raj M Ratwani

Abstract read
In one paragraph

Article in Journal of the American Medical Informatics Association : JAMIA, 2018. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 18 papers, 1 of them a synthesis that pooled it.

0numbers the graph read from it
0cells of the map it votes in
18citing papers in PubMed, 1 pooled it
–field-weighted citation impact
1 · What the graph read from it

What it found

Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.

The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.

2 · The registry

The trial behind it

Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.

Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.

3 · Its place in the literature

Who cites it

18 citing papers in PubMed, 1 synthesis or guideline pooled it.

  1. EARS to cyber incidents in health care.Journal of the American Medical Informatics Association : JAMIA · 2019
    Pooled it
  2. Article
  3. Review
  4. Article
  5. Article
  6. Article
  7. Article
  8. Article
  9. Review
  10. Article
  11. Article
  12. Article
  13. Article
  14. Article
  15. Article
  16. Clinical impact of intraoperative electronic health record downtime on surgical patients.Journal of the American Medical Informatics Association : JAMIA · 2019
    Article
  17. Article
  18. Cyber-resilient Intensive Care Unit: Ransomware is a Patient-safety Crisis-A Resource-stratified Approach for India.Indian journal of critical care medicine : peer-reviewed, official publication of Indian Society of Critical Care Medicine
    Article
4 · The record

Corrections and comments

PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.

5 · Who and what money

Authors and funding

4 authors.

Ethan LarsenGrado Department of Industrial and Systems Engineering, Virginia Tech, Blacksburg, VA, USA.
Allan FongNational Center for Human Factors in Healthcare, MedStar Health, Washington, DC, USA.
Christian WernzDepartment of Health Administration, Virginia Commonwealth University, Richmond, VA, USA.
Raj M RatwaniNational Center for Human Factors in Healthcare, MedStar Health, Washington, DC, USA.

Funding

No grant is acknowledged in the PubMed record.

6 · The paper itself

Abstract

Objective: We sought to understand the types of clinical processes, such as image and medication ordering, that are disrupted during electronic health record (EHR) downtime periods by analyzing the narratives of patient safety event report data. Materials and Methods: From a database of 80 381 event reports, 76 reports were identified as explicitly describing a safety event associated with an EHR downtime period. These reports were analyzed and categorized based on a developed code book to identify the clinical processes that were impacted by downtime. We also examined whether downtime procedures were in place and followed. Results: The reports were coded into categories related to their reported clinical process: Laboratory, Medication, Imaging, Registration, Patient Handoff, Documentation, History Viewing, Delay of Procedure, and General. A majority of reports (48.7%, n = 37) were associated with lab orders and results, followed by medication ordering and administration (14.5%, n = 11). Incidents commonly involved patient identification and communication of clinical information. A majority of reports (46%, n = 35) indicated that downtime procedures either were not followed or were not in place. Only 27.6% of incidents (n = 21) indicated that downtime procedures were successfully executed. Discussion: Patient safety report data offer a lens into EHR downtime-related safety hazards. Important areas of risk during EHR downtime periods were patient identification and communication of clinical information; these should be a focus of downtime procedure planning to reduce safety hazards. Conclusion: EHR downtime events pose patient safety hazards, and we highlight critical areas for downtime procedure improvement.

Indexed as

Electronic Health RecordsPatient SafetyEquipment FailureHealth FacilitiesHumansMedical Errorsdowntime, EHRelectronic health recordspatient safety

Identifiers

PMID28575417
PMCPMC7647128

What OpenQuestion holds

Textmetadata
Read underepoch 390

Registered trials

None linked

Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.