Chapter 8 Information Technology in Critical Care
The Electronic Health Record
The computer-based patient record (CPR) or electronic health record (EHR) is defined as a comprehensive database of personal, health-related information that is accessed and updated across a health care network.1 Its potential and real benefits include the following:
Data Acquisition
The complete EHR acquires data from a variety of sources, including hospital registration, nursing and physician input, laboratory services, radiology and other test interpretations, therapist and nutrition services, monitoring devices, and physicians’ orders. The most important system that feeds the database is the “enterprise-wide master patient index,” which ensures that each patient is identified properly and uniquely. All other systems must have the correct identifier in order to deliver their data to the correct patient record. A multimedia database can include images such as radiographs, electrocardiograms, fetal monitoring, sonography, magnetic resonance images, computerized tomograms, and even paper-based documents such as consent forms, questionnaires, and, sometimes, handwritten notes and hand-drawn diagrams. Data acquisition is organized in a manner that minimizes duplicative effort and maximizes data consistency.2
Data Access
The system should be capable of providing a full, seamless view of the patient over time and across points of care. Views should be configurable so that a given user’s information needs and workflow can be accommodated. Both detailed and summary views that juxtapose relevant data allow the clinician to acquire the information required to optimize expedient decision making. Displays should be configured to highlight key information while suppressing clutter but making all pertinent data readily accessible. Dynamic linkages should exist between the computerized patient record and supporting functions such as expert systems, clinical pathways, protocols, policies, reference material, and the medical literature.
Clinical Decision Support
Decision support systems are an integrated set of programs and databases that provide users with the ability to interrogate those databases and analyze information, retrieving data from external sources, if necessary, to assist in decision making.3
An effective decision support system must have accurate data, a user-friendly interface, a reliable knowledge base, and a good inferencing mechanism. The knowledge base can include information regarding risks, costs, disease states, clinical and laboratory findings, and clinical guidelines. The inference engine determines how and when to apply the appropriate knowledge while carefully minimizing disruptions of workflow.4,5
Patient Safety
Patient safety concerns remain paramount in any hospital system, including clinical information systems.6,7
To the extent possible, redundant systems should be in place to minimize the effect of the failure of a single component. Robust down-time contingency plans must be developed should the clinical information systems cease normal function in either planned or unplanned situations. These contingency plans must account for continued data acquisition and retrieval and provide for mechanisms for communication among health care providers and services. Users should be informed about recovery procedures and what they mean to the clinical database. Do backlogged data generated during the down time ever enter the system? How are they timed? Or is there a gap in the clinical information that the clinicians must fill in for themselves if they want the whole picture?
Automated Adverse Event Detection
Children are at significant risk for adverse drug events, and recent studies have begun to describe the frequency and epidemiology of medication errors and adverse events in pediatric inpatients.8–10 In 2006, The Institute of Medicine released guidelines urging improved surveillance systems to detect adverse events.11 Traditional methods used to detect adverse events in children included manual chart review and voluntary incident reporting. These detection systems are inefficient and significantly underestimate the number and prevalence of adverse events.12,13
Another manual detection strategy relies on trigger methodology where an occurrence, found on manual chart review, triggers further investigation to determine the presence of an adverse event.11,14 For example, the administration of flumazenil may trigger the detection of benzodiazepine-induced respiratory depression. Automated adverse-event detection relies on the generation of a trigger report from the EHR, which indicates the possibility that an adverse event has occurred requiring further investigation. This methodology has been proven an efficient and cost effective way to detect adverse events.15–19
Promises and Limitations
Information technology in the form of an EHR promises improved patient care.20,21 Potential benefits of information technology include providing rapid access to integrated clinical data and extant medical knowledge, eliminating illegibility, improving communication, and issuing applicable reminders and checks for appropriate medical actions.22
A number of studies show that information technology can provide various benefits, including increasing adherence to guidelines (particularly in the outpatient arena) and decreasing some medication errors.23,24 However, the majority of these studies come from a very small number of institutions with homegrown clinical information systems that were developed by devoted groups of clinicians.25 Very few studies show that the commercially available systems confer similar benefits, and even if they do, it is unclear that their success can be migrated from one implementation to another.26–28 In fact, any benefit may be outweighed by new problems introduced by the systems themselves. In effect, one set of problems may be traded for another.29,30
Despite considerable progress, the sentiment expressed by G. Octo Barnett in 1966 is often echoed today, “It is frustrating to meet with repeated disappointments when the objectives are superficially so simple.”31 The medical information space is vastly more complicated than it seems at first. EHR software programs are enormously complex, are built by large teams of programmers with input by numerous clinicians, demand high-speed processors and high-bandwidth networks, and rely on often fragile interfaces with other hospital systems. Implementation currently requires tremendous effort by both clinicians and technical specialists to configure these systems according to the specific needs of an institution and in ways that will enhance care rather than impede it. An often unappreciated complicating factor is that the technology does not simply replace paper; it also reengineers care—deliberately or not. (See Unfavorable Alteration of Workflow.)
Numerous other unintended consequences result from implementing an EHR, including the creation of new kinds of errors, an increase in work for clinicians, an untoward alteration of workflow and change in communication patterns, an increase in system demands, a continuation of the persistence of paper use, and the fostering of potential overdependence on the technology.32–34
New Kinds of Errors
While some errors can be avoided by using an EHR with computerized physician order entry (CPOE), other errors may be created or propagated.35,36 Many “new” errors are a result of poorly designed interfaces. For example, clinicians can easily make “juxtaposition errors,” intending to select one item but selecting another close to it on a long, dense pick list in a small font. A similar kind of error is mistaking an open chart of one patient to be that belonging to another or picking the wrong patient from a long list of patients.
Rigid interpretation of policies and procedures can be configured into the EHR but may lead to difficulties in clinical practice when dealing with ambiguous circumstances and exceptions. Sometimes the process of care is incompletely understood and codification can be disastrous. Policies at most institutions include automatic stop orders that require rewriting medication orders in a specified time frame. Compliance to this rule can be forced with programming, but implementing this rule without safeguards could lead to automatic discontinuation of medications and missed doses.
Increased Work for Clinicians
Clinical alerts can help clinicians make decisions, e.g., when penicillin is mistakenly ordered for an allergic patient, but persistent interruptions of work by alerts can increase the workload of the clinician who must decipher their meaning and assess the risk in each specific circumstance. The frequency of these alerts can become intolerable when they are not delivered to the right clinician with the right information and at the right time and place. When these alerts become too frequent and too predictable, clinicians often adapt by “response chaining”: dismissing the alerts with rote keystrokes much as a pianist plays a familiar tune. Alerts that evoke this response cannot be effective and may be counterproductive.37
Untoward Changes in Communication Patterns
Many care providers blame clinical information systems for unsatisfactory reductions in face-to-face communication. Some users complain that the EHR creates an “illusion of communication,”38 where users believe that information entered into the system will be somehow communicated to the relevant personnel. This assumption can result in missed or delayed execution of orders or failure to appreciate the recommendations of a consultant. Users may erroneously assume that allergies entered into the system will adequately protect patients from receiving offending food or drugs.
High System Demands and Frequent Changes
No installed EHR can remain static for long. Maintenance, revisions, and upgrades of both software and hardware contribute to constant flux. Consequences should be expected with every change, and many changes require testing that can become onerous. While minor changes can occur without supplemental training of personnel, failure to provide training for some changes can cause significant user frustration and errors. Some configuration changes requested by one group may also adversely affect other users in unexpected ways. Mechanisms must be developed to resolve conflicts of this nature. As clinicians become increasingly dependent on the system, pressure to keep the system operational mounts, requiring around-the-clock technical support. One analogy likened system maintenance to “repairing a jet engine in flight.”38
Human Factors Engineering
Cognitive science, computer science, and human factors engineering are among many disciplines that can facilitate development of a successful EHR system. Human factors engineering investigates human capabilities and limitations and applies that knowledge in the design of systems, software, environments, training, and personnel management. Application of human factors considerations in developing an EHR, particularly regarding CPOE, can maximize successful design and implementation of these systems. Some human factors principles may seem self-evident but can be overlooked when not approached systematically. Developers must understand the users, undertake detailed task analyses, and assess computer-supported cooperative work—the study of how people work within organizations and how technology affects them and their work. Three principles that may improve clinical information systems are accounting for incentive structures, understanding workflow, and promoting awareness of the activities of other group members. Institutional and personal incentives for using an EHR differ, but only the latter will effectively influence use. Awareness of the roles played by other team members enhances collaboration. Improving collaboration may decrease the incidence of medical errors.39,40
User satisfaction is an important predictor of system success. Satisfaction is enhanced when the systems are designed with the users’ needs and preferences in mind. Peers who serve as advocates for their groups during development and subsequently teach other users generally increase acceptance of the systems. Ease of use, rapid response times, flexibility and customizability, mobile workstations, implementation of effective decision support tools, access to reference information, and adequate training and support are all important factors in enhancing both user satisfaction and system success.41
Continued Promise
The Institute of Medicine, in its report, “Crossing the quality chasm: a new health system for the 21st century,”2 stated that health care should be safe, effective, patient-centered, timely, efficient, and equitable. The Institute further noted that these goals could be more easily reached through judicious application of IT. Automated order entry systems can improve safety. The use of automated reminders based on clinical practice guidelines, computer-assisted diagnosis or management, and evidence-based medicine (EBM) can improve the effectiveness of medical care. IT can enhance patient-centered care that is respectful of and responsive to patient preferences, needs, and values by recording them and appropriately reminding the health care professional. It can facilitate access to clinical knowledge through web sites and online support groups. Clinical decision-support systems can be used to tailor information and disease management messages based on the patient’s individual needs. Timeliness can be improved by e-mail, telemedicine, and direct and immediate access to diagnostic test results and other clinical information. IT can improve efficiency by using clinical decision-support systems to reduce redundant and unnecessary tests and procedures, by improving communication among multiple providers of care to individual patients, and by supplying data for performance and outcome measures. Enhancing equity among patients and across socioeconomic, geographic, race, and ethnic lines can be achieved if IT can improve access to clinicians and clinical knowledge, although it would depend upon equitable access to the technology infrastructure. IT is playing the starring role in the drive to improve the quality of health care today, and the Institute called for a national commitment to build the information infrastructure to support health care.
Design and Implementation
Implementation of an EHR system requires an investment of additional staff, hardware, software, and an expanded communications infrastructure or network. For large hospital networks, the costs can be exorbitant.42
Developing an EHR requires careful planning and phased implementation. The specific needs of the institution must be examined, particularly with regard to the existing technology and practices. The process should be viewed as an opportunity to enhance care, rather than simply to replace the paper, and requires reassessment of existing practices and re-engineering of healthcare delivery. As each incremental phase of implementation is approached, the focus should be on overcoming specific barriers to care rather than on the nebulous goal of “creating a paperless process.”43
The first phase generally provides a patient-centric repository of clinical test results, including laboratory, radiology, pathology, and other textual data. A subsequent phase can include capture of paper document images, radiology images, and other nontextual data. A key phase is the capture of clinical data at the point of care, including vital signs, intake and output, nursing documentation, and physician notes. Implementation of a physician order-entry system is another key phase that requires careful coordination among services and interdigitating systems.44–46
Ensuring that the EHR satisfies every need involves considerable planning, designing, and testing. Even well-designed, off-the-shelf EHR systems can satisfy only 80% of the complex requirements of any multipractitioner organization. The remainder must be either adapted from other content or created from scratch. Substantial “expert” direction from teams of physicians, nurses, other allied healthcare providers, and medical records and financial staff is required to assist in developing the design and implementation of all EHRs.47 If clinicians abdicate their responsibility in participating in this tedious process, they are virtually ensuring that the resulting system will fail to satisfy their needs. Physician acceptance and participation can be enhanced by acknowledging the importance of physicians in the process, training them early and often, frequently and routinely eliciting their feedback, and demonstrating responsiveness to their needs and concerns.