| Literature DB >> 34642622 |
Tanya Pankhurst1, Jolene Atia1, Felicity Evison1, Suzy Gallier1,2, Joshua M Lewis1, Deborah McKee1, Steve Ryan1, Elizabeth Sapey1,2, Simon Ball1,2, Jamie J Coleman1,3.
Abstract
BACKGROUND: The COVID-19 pandemic created unprecedented pressure on hospitals globally. Digital tools developed before the crisis provided novel aspects of management, and new digital tools were rapidly developed as the crisis progressed. In our institution, a digitally mature NHS Trust in England which builds software systems, development during the early months of the crisis allowed increased patient safety and care, efficient management of the hospital and publication of data. The aim of this paper is to present this experience as a case study, describing development and lessons learned applicable to wider electronic healthcare record development.Entities:
Keywords: COVID-19; Clinical decision support systems; EHR; Electronic health records; Medical informatics
Year: 2021 PMID: 34642622 PMCID: PMC8498783 DOI: 10.1016/j.hlpt.2021.100568
Source DB: PubMed Journal: Health Policy Technol ISSN: 2211-8837
Fig. 1Admissions to University Hospitals Birmingham; emergency admissions (orange), elective admissions (blue), admissions to intensive care (navy), suspected COVID-19 (green), and COVID-19 positive admission (purple). (For interpretation of the references to color in this figure legend, the reader is referred to the web version of this article.)
Fig. 2Number of new admissions to ICU and overall ICU bed occupancy (the number of patients in ICU at 12:00 midnight each day).
Fig. 3Example of Dashboards built for COVID-19. Data represented for University Hospitals Birmingham (Queen Elizabeth Hospital, Heartlands Hospital, Good Hope Hospital and Solihull Hospital).
Fig. 4Daily number of "Communication with relatives" inpatient noting.
Fig. 5Number of inpatients with an active structured prescription for EOL medications (as a percentage all hospital inpatients).
Organisational functions relevant to adapt a digital programme to a crisis; lessons learned and generalization.
| Organisational Function | Characteristics from this experience and generalisation |
|---|---|
| Clinical leadership | In a crisis many conflicting ideas and requests arise. Requests must be triaged for clinical relevance and evidence of benefit to patients |
| Executive oversight | Clear leadership is required; conflicting requirements, lack of sight of the overall picture and relative importance of each request for change will undermine effective delivery without authority |
| Responsive digital provider able to respond rapidly to clinical need | In crises changes must be timely but well thought out and evidenced |
| Intuitive build with clinically useful functions | Digital systems must be helpful and easy to use. There must be effective data flows to prevent siloed information and careful attendance to logic. Data must be easy to enter and be relevant. Presentation of data must be easy to interpret |
| Avoidance of support alert and data entry fatigue | Multiple alerts will result in important information being missed. Overall impact of combined functionality must be considered; alerts must be clinically important and only used if evidenced patient advantage. |
| Provide relevant information to clinicians in the right place at the right time | Alerts shown to the wrong user will cause alert fatigue. Disruption of work processes will lead to error. |
| Require data collection only if it is clinically relevant (and it must be brief) | Overburdening clinicians with data entry that does not result in immediate patient benefit will lead to disengagement. |
| Encourage and listen to feedback | Clinicians will help build EHR that they are engaged in especially if changes are immediately apparent. This leads to useful EHR and increased engagement |