Accenture's experience indicates that hospitals and health systems will face some fundamental architectural problems with existing technologies as they move towards developing electronic methods of storing and tracking clinical information. These include scalability, reliability, recoverability, interchangeable vocabularies and integration. Scalability Health organizations need to determine if a single EHR system will be big enough to support all users with the functionality they want. Architectures in use today do not scale (or at least have not demonstrated scalability) to the EHR requirements. Vendor systems can only be reliably measured by their "largest live implementation." EHR systems scale well until their single online data store develops unacceptable spikes of peak congestion. The numbers of simultaneous sessions and active interfaces correlate to online systems performance. Reliability At least in part, health organizations have a goal of replacing paper records that are currently used for the administration of clinical and business processes. Paper processes may technically exist as a downtime procedure. But classic downtime paper procedures are ineffective when procedures have been redesigned to make best use of information technology. And paper charts are frequently misplaced or for some other reason unavailable. Yet, unlike an electronic environment where access to records depends upon system availability, paper charts (if they have not been misplaced) can be available, even though it may require time and effort to find them. The issue of reliability is one that few health organizations have ever truly encountered. Recoverability EHR systems need to be instantly recoverable in the event of downtime, or if a failure occurs. Health organizations will need to develop backup plans to provide clinicians with access to critical clinical information that is only available in an electronic form if systems become suddenly unavailable. Emergency care, scheduling and registration, order entry, and clinical documentation are just a few of the work processes that would need to continue seamlessly, even with a primary systems interruption. Interchangeable vocabularies Health organizations are frequently challenged by a variety of code sets or master files that have proliferated across their facilities. Most often, this is due to acquisitions that were never optimized. The US government is starting to prescribe specific vocabularies that will need to be used for HIPAA attachments transactions and the future exchange of electronic patient information between health care organizations. To support a portable, interoperable electronic health record, health organizations will need to replace their local vocabularies and synchronize their use of government-specified code sets. Integration Most electronic record systems do not integrate with those of other vendors (and some systems offered by the same vendor aren't even integrated with each other). True interoperability will require that all features and functions work across all applications. The term "semantic interoperability" is now being used to describe a level of integration that facilitates the movement of data between systems. A practical definition of "semantic interoperability" is the interchange of data where not only can the information be transmitted between/among systems, but the receiving system can understand and reuse the information in many different contexts, across all health care information application domains. Next: Recommendations |