ArticleBMC medical informatics and decision making2024
Strategy for scheduled downtime of hospital information system utilizing third-party applications.
Article in BMC medical informatics and decision making, 2024. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
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.
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.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
9 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
backgroundThe widespread adoption of Hospital Information Systems (HIS) has brought significant benefits in healthcare quality and workflow efficiency. However, downtimes for system maintenance are inevitable and pose a considerable challenge to continuous patient care. Existing strategies, including manual prescription methods, are no longer effective due to increasing reliance on digital systems.
methodThis study implemented two main strategies to mitigate the impact of scheduled downtimes. First, we created an "Emergency query program" that switches to a read-only backup server during downtimes, allowing clinicians to view essential patient data. Second, an "Emergency prescription system" was developed based on the Microsoft Power Platform and integrated into Microsoft Teams. This allows clinicians to perform digital prescriptions even during downtimes.
resultsDuring a planned 90-minute downtime, 282 users accessed the Emergency Prescription System, resulting in 22 prescriptions from various departments. Average times for prescription confirmation and completion were 8 min and 3 s, and 18 min and 40 s, respectively. A post-downtime evaluation revealed high user satisfaction.
conclusionEssential maintenance-induced HIS downtimes are inherently disruptive to patient care process. Our deployment of an emergency query program and a Microsoft Teams-integrated emergency prescription system demonstrated robust care continuity during HIS downtime.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
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.