Development and Deployment of the OpenMRS-Ebola Electronic Health Record System for an Ebola Treatment Center in Sierra Leone.

BACKGROUND: Stringent infection control requirements at Ebola treatment centers (ETCs), which are specialized facilities for isolating and treating Ebola patients, create substantial challenges for recording and reviewing patient information. During the 2014-2016 West African Ebola epidemic, paper-based data collection systems at ETCs compromised the quality, quantity, and confidentiality of patient data. Electronic health record (EHR) systems have the potential to address such problems, with benefits for patient care, surveillance, and research. However, no suitable software was available for deployment when large-scale ETCs opened as the epidemic escalated in 2014. OBJECTIVE: We present our work on rapidly developing and deploying OpenMRS-Ebola, an EHR system for the Kerry Town ETC in Sierra Leone. We describe our experience, lessons learned, and recommendations for future health emergencies. METHODS: We used the OpenMRS platform and Agile software development approaches to build OpenMRS-Ebola. Key features of our work included daily communications between the development team and ground-based operations team, iterative processes, and phased development and implementation. We made design decisions based on the restrictions of the ETC environment and regular user feedback. To evaluate the system, we conducted predeployment user questionnaires and compared the EHR records with duplicate paper records. RESULTS: We successfully built OpenMRS-Ebola, a modular stand-alone EHR system with a tablet-based application for infectious patient wards and a desktop-based application for noninfectious areas. OpenMRS-Ebola supports patient tracking (registration, bed allocation, and discharge); recording of vital signs and symptoms; medication and intravenous fluid ordering and monitoring; laboratory results; clinician notes; and data export. It displays relevant patient information to clinicians in infectious and noninfectious zones. We implemented phase 1 (patient tracking; drug ordering and monitoring) after 2.5 months of full-time development. OpenMRS-Ebola was used for 112 patient registrations, 569 prescription orders, and 971 medication administration recordings. We were unable to fully implement phases 2 and 3 as the ETC closed because of a decrease in new Ebola cases. The phase 1 evaluation suggested that OpenMRS-Ebola worked well in the context of the rollout, and the user feedback was positive. CONCLUSIONS: To our knowledge, OpenMRS-Ebola is the most comprehensive adaptable clinical EHR built for a low-resource setting health emergency. It is designed to address the main challenges of data collection in highly infectious environments that require robust infection prevention and control measures and it is interoperable with other electronic health systems. Although we built and deployed OpenMRS-Ebola more rapidly than typical software, our work highlights the challenges of having to develop an appropriate system during an emergency rather than being able to rapidly adapt an existing one. Lessons learned from this and previous emergencies should be used to ensure that a set of well-designed, easy-to-use, pretested health software is ready for quick deployment in future.

Design and development of an EMR for Ebola Treatment Centers in Sierra Leone using OpenMRS.

Ebola treatment presents unique challenges for medical records because strict infection control requirements rule out most conventional record-keeping systems. We used the OpenMRS platform to rapidly develop an EMR system for the recently opened Kerry Town, Sierra Leone Ebola Treatment Centre. This system addresses the need for recording patient data and communicating it between the infectious and non-infectious zones, and is specifically designed for maximum usability by staff wearing cumbersome protective equipment. This platform is interoperable with other key eHealth systems in the country, and is extensible to other sites and diseases.

Clinical Decision Support in the Management of Patients With Suspected Ebola Infection.

Patients with suspected public health threats, such as Ebola, must be quickly identified and isolated on presentation to health care facilities. Patients can be screened by intake staff or other health care providers; however, perfect compliance is difficult to achieve. Well-designed, carefully placed clinical decision support (CDS) within the electronic health record can be a reliable partner in helping to rapidly identify, isolate, and care for patients with suspected Ebola infection and other emerging public health threats. We describe how different types of CDS can be applied in the clinical workflow and share how we implemented CDS to force Ebola screening upon patient presentation to our emergency department.

The Boston Marathon Bombings Mass Casualty Incident: One Emergency Department's Information Systems Challenges and Opportunities.

Emergency department (ED) information systems are designed to support efficient and safe emergency care. These same systems often play a critical role in disasters to facilitate real-time situation awareness, information management, and communication. In this article, we describe one ED's experiences with ED information systems during the April 2013 Boston Marathon bombings. During postevent debriefings, staff shared that our ED information systems and workflow did not optimally support this incident; we found challenges with our unidentified patient naming convention, real-time situational awareness of patient location, and documentation of assessments, orders, and procedures. As a result, before our next mass gathering event, we changed our unidentified patient naming convention to more clearly distinguish multiple, simultaneous, unidentified patients. We also made changes to the disaster registration workflow and enhanced roles and responsibilities for updating electronic systems. Health systems should conduct disaster drills using their ED information systems to identify inefficiencies before an actual incident. ED information systems may require enhancements to better support disasters. Newer technologies, such as radiofrequency identification, could further improve disaster information management and communication but require careful evaluation and implementation into daily ED workflow.

Structured representation for core elements of common clinical decision support interventions to facilitate knowledge sharing.

At present, there are no widely accepted, standard approaches for representing computer-based clinical decision support (CDS) intervention types and their structural components. This study aimed to identify key requirements for the representation of five widely utilized CDS intervention types: alerts and reminders, order sets, infobuttons, documentation templates/forms, and relevant data presentation. An XML schema was proposed for representing these interventions and their core structural elements (e.g., general metadata, applicable clinical scenarios, CDS inputs, CDS outputs, and CDS logic) in a shareable manner. The schema was validated by building CDS artifacts for 22 different interventions, targeted toward guidelines and clinical conditions called for in the 2011 Meaningful Use criteria. Custom style sheets were developed to render the XML files in human-readable form. The CDS knowledge artifacts were shared via a public web portal. Our experience also identifies gaps in existing standards and informs future development of standards for CDS knowledge representation and sharing.

Drug-drug interactions that should be non-interruptive in order to reduce alert fatigue in electronic health records.

OBJECTIVE: Alert fatigue represents a common problem associated with the use of clinical decision support systems in electronic health records (EHR). This problem is particularly profound with drug-drug interaction (DDI) alerts for which studies have reported override rates of approximately 90%. The objective of this study is to report consensus-based recommendations of an expert panel on DDI that can be safely made non-interruptive to the provider's workflow, in EHR, in an attempt to reduce alert fatigue. METHODS: We utilized an expert panel process to rate the interactions. Panelists had expertise in medicine, pharmacy, pharmacology and clinical informatics, and represented both academic institutions and vendors of medication knowledge bases and EHR. In addition, representatives from the US Food and Drug Administration and the American Society of Health-System Pharmacy contributed to the discussions. RESULTS: Recommendations and considerations of the panel resulted in the creation of a list of 33 class-based low-priority DDI that do not warrant being interruptive alerts in EHR. In one institution, these accounted for 36% of the interactions displayed. DISCUSSION: Development and customization of the content of medication knowledge bases that drive DDI alerting represents a resource-intensive task. Creation of a standardized list of low-priority DDI may help reduce alert fatigue across EHR. CONCLUSIONS: Future efforts might include the development of a consortium to maintain this list over time. Such a list could also be used in conjunction with financial incentives tied to its adoption in EHR.

Grand challenges in clinical decision support.

There is a pressing need for high-quality, effective means of designing, developing, presenting, implementing, evaluating, and maintaining all types of clinical decision support capabilities for clinicians, patients and consumers. Using an iterative, consensus-building process we identified a rank-ordered list of the top 10 grand challenges in clinical decision support. This list was created to educate and inspire researchers, developers, funders, and policy-makers. The list of challenges in order of importance that they be solved if patients and organizations are to begin realizing the fullest benefits possible of these systems consists of: improve the human-computer interface; disseminate best practices in CDS design, development, and implementation; summarize patient-level information; prioritize and filter recommendations to the user; create an architecture for sharing executable CDS modules and services; combine recommendations for patients with co-morbidities; prioritize CDS content development and implementation; create internet-accessible clinical decision support repositories; use freetext information to drive clinical decision support; mine large clinical databases to create new CDS. Identification of solutions to these challenges is critical if clinical decision support is to achieve its potential and improve the quality, safety and efficiency of healthcare.

A roadmap for national action on clinical decision support.

This document comprises an AMIA Board of Directors approved White Paper that presents a roadmap for national action on clinical decision support. It is published in JAMIA for archival and dissemination purposes. The full text of this material has been previously published on the AMIA Web site (www.amia.org/inside/initiatives/cds). AMIA is the copyright holder.

Recommendations for clinical decision support deployment: synthesis of a roundtable of medical directors of information systems.

BACKGROUND: Ample evidence exists that clinical decision support (CDS) can improve clinician performance. Nevertheless, additional evidence demonstrates that clinicians still do not perform adequately in many instances. This suggests an ongoing need for implementation of CDS, in turn prompting development of a roadmap for national action regarding CDS. OBJECTIVE: Develop practical advice to aid CDS implementation in order to improve clinician performance. METHOD: Structured group interview during a roundtable discussion by medical directors of information systems (N = 30), with subsequent review by participants and synthesis. RESULTS: Participant consensus was that CDS should be comprehensive and should involve techniques such as order sets and facilitated documentation as well as alerts; should be subject to ongoing feedback; and should flow from and be governed by an organization's clinical goals. CONCLUSION: A structured roundtable discussion of clinicians experienced in health information technology can yield practical, consensus advice for implementation of CDS.

Clinical decision support in electronic prescribing: recommendations and an action plan: report of the joint clinical decision support workgroup.

Clinical decision support (CDS) in electronic prescribing (eRx) systems can improve the safety, quality, efficiency, and cost-effectiveness of care. However, at present, these potential benefits have not been fully realized. In this consensus white paper, we set forth recommendations and action plans in three critical domains: (1) advances in system capabilities, including basic and advanced sets of CDS interventions and knowledge, supporting database elements, operational features to improve usability and measure performance, and management and governance structures; (2) uniform standards, vocabularies, and centralized knowledge structures and services that could reduce rework by vendors and care providers, improve dissemination of well-constructed CDS interventions, promote generally applicable research in CDS methods, and accelerate the movement of new medical knowledge from research to practice; and (3) appropriate financial and legal incentives to promote adoption.

Conversion from intravenous to oral medications: assessment of a computerized intervention for hospitalized patients.

BACKGROUND: Many hospitalized patients continue to receive intravenous medications longer than necessary. Earlier conversion from the intravenous to the oral route could increase patient safety and comfort, reduce costs, and facilitate earlier discharge from the hospital without compromising clinical care. We examined the effect of a computer-based intervention to prompt physicians to switch appropriate patients from intravenous to oral medications. METHODS: This study was performed at Brigham and Women's Hospital, an academic tertiary care hospital at which all medications are ordered online. We targeted 5 medications with equal oral and intravenous bioavailability: fluconazole, levofloxacin, metronidazole, ranitidine, and amiodarone. We used the hospital's computerized order entry system to prompt physicians to convert appropriate intravenous medications to the oral route. We measured the total use of the targeted medications via each route in the 4 months before and after the implementation of the intervention. We also measured the rate at which physicians responded to the intervention when prompted. RESULTS: The average intravenous defined daily dose declined by 11.1% (P =.002) from the preintervention to the postintervention period, while the average oral defined daily dose increased by 3.7% (P =.002). Length of stay, case-mix index, and total drug use at the hospital increased during the study period. The average total monthly use of the intravenous preparation of all of the targeted medications declined in the 4 months after the intervention began, compared with the 4 months before. In 35.6% of 1045 orders for which a prompt was generated, the physician either made a conversion from the intravenous to the oral version or canceled the order altogether. CONCLUSIONS: Computer-generated reminders can produce a substantial reduction in excessive use of targeted intravenous medications. As online prescribing becomes more common, this approach can be used to reduce excess use of intravenous medications, with potential benefits in patient comfort, safety, and cost.

Automating complex guidelines for chronic disease: lessons learned.

There is scant published experience with implementing complex, multistep computerized practice guidelines for the long-term management of chronic diseases. We have implemented a system for creating, maintaining, and navigating computer-based clinical algorithms integrated with our electronic medical record. This article describes our progress and reports on lessons learned that might guide future work in this field. We discuss issues and obstacles related to choosing and adapting a guideline for electronic implementation, representing and executing the guideline as a computerized algorithm, and integrating it into the clinical workflow of outpatient care. Although obstacles were encountered at each of these steps, the most difficult were related to workflow integration.

The informatics response in disaster, terrorism, and war.

The United States currently faces several new, concurrent large-scale health crises as a result of terrorist activity. In particular, three major health issues have risen sharply in urgency and public consciousness--bioterrorism, the threat of widespread delivery of agents of illness; mass disasters, local events that produce large numbers of casualties and overwhelm the usual capacity of health care delivery systems; and the delivery of optimal health care to remote military field sites. Each of these health issues carries large demands for the collection, analysis, coordination, and distribution of health information. The authors present overviews of these areas and discuss ongoing work efforts of experts in each.