I literally cannot imagine any circumstances where the replacement of VistA was not troublesome. VistA was custom designed for the…
Future Health Solution
By Toby Samo, MD
Health information technology (HIT) has made significant advances over the last two decades. While adoption is not necessarily a good marker for successful EHR usage, adoption of office-based physicians with EHR has gone from about 20 percent to over 80 percent and more that 95 percent of all non-federal acute care hospitals possess certified health IT. HIT implementation has led to improvements in quality and patient safety.
However, many of the goals of increased HIT implementation have been stymied by social and technical roadblocks. A “one type fits all” approach may help reduce training and configuration costs, but there are many approaches to patient care and unique workflows between specialties and among individual users.
Most EHRs are burdened with three major legacy issues:
- Technology. Present EHR systems are mostly built on what would now be considered old technology. Some of the ambulatory products and small acute care products have moved onto cloud-based architecture, but most are client-server. While hosting instances of a product reduces the technical expertise needed by the client and can lead to better standardization of implementation, it does not necessarily deliver the advantages of a native, cloud-based architecture.
- Encounter-based. EHRs have been built on the concept that interactions with patients (or members or clients) are associated with a specific encounter. This functions well for face-to-face visits and for specific events, but is limiting where longitudinal care is required.
- User experience. The user experience has for the most part taken a back seat to functionality in HIT software development. A quick view of most HIT systems shows the interface to be cluttered and does not draw the user’s attention to the areas that need the most attention. Most users access only a small percentage of the functionality that is present within the system, but vendors continue to add functionality rather than clean up the interface.
Platforms have revolutionized the way business is conducted in many industries. Numerous examples have made household names out of companies like Airbnb, Uber, Facebook, YouTube, Amazon and many more. A platform is not just a technology, but also “a new business model that uses technology to connect people, organization, and resources in an interactive ecosystem.”
There is a need for a HIT platform that would support the multitude of components necessary to move the delivery of HIT into the next generation. The future health solution needs to use contemporary technology that will have the flexibility to adapt to ever-changing requirements and use cases of modern healthcare. Some of the characteristics of the future health solution are:
- Open. One of the biggest complaints of users and regulators is the closed nature of many HIT systems. The future health solution needs to be built as a platform that is able to share and access not only data, but also workflows and functionality through APIs
- Apps and modules. A modular structure will enable components to be reused in different workflows and encourage innovation and specialization.
- True, cloud-based architecture. Cloud computing delivers high performance, scalability, and accessibility. Upfront costs are reduced or eliminated and minimizes the technical resources needed by the client. Management, administration, and upgrading of solutions can be centralized and standardized.
- Multi-platform. Users expect access to workflows on their smartphones and tablets. Any solution must develop primary workflows for the mobile worker and ensure that the user interface supports these devices
- Scalable (up and down). To meet the needs of small and large organizations, the future health solutin will need to scale to accommodate changes in client volumes.
- Analytics, reporting, and big data. HIT systems have collected massive amount of data. The challenge is not just mining that data, but presenting the information in a way that can be quickly absorbed by the individual user.
- Searchable at the point of use. All the data that is being collected needs to be readily accessible. Using universal search capabilities and the ability to filter and sort on the fly will facilitate the easy access to information at the point of care.
- Privacy and security. The core platform will need to be primarily responsible for the security and privacy of the data. The other modules built on the platform will need to comply to the platform security and privacy practices, but will not need to primarily manage these issues.
- Interoperable. Need to adopt all present and future (FHIR) standards of data sharing. The open nature of the platform will facilitate access to data.
- Internationalization and localization. Internationalization ensures that the system is structured in such a way that supports different languages, keyboards, alphabets, and data entry requirements. Localization uses these technical underpinnings to ensure that the cultural and scientific regional differences are addressed to help with implementation and adoption.
- Workflow engine. Best practices can change and can be affected by national and regional differences. An easy-to-use workflow engine will be a necessity to help make changes to the workflow as needed by the clients.
- Task management. Every user has tasks that need to be identified, prioritized, and addressed. Therefore, a task management tool that extends beyond a single module or workflow will be needed.
- Clinical decision support. Increasingly sophisticated decision support needs to be supported, including CDS, artificial intelligence, and diagnostic decision support. These capabilities need to be embraced by the platform, allowing external decision support engines to interface easily with the other modules.
- Adaptable on the fly by the end user. Allowing the end user with proper security to make changes to templates and workflows would help improve adoption.
- User experience. Probably the most significant barrier to adoption of HIT is the user experience. Other industries are way ahead of healthcare in the adoption of clean, easy-to-use interfaces. It is vital that a team of user experience experts be integrally involved in the development process. All user-facing interactions, screens, and workflows need to be evaluated by user experience experts who can recommend innovative ways the user interacts with the system and how information is displayed.
The HIT industry has hit a wall that is preventing it from developing innovative products that use the newest technology and have an exemplary user experience. A new platform has the potential to support a robust, flexible, and innovative series of products that can adapt to meet the needs of the various healthcare markets globally. Such a project would have to build slowly over time, as does any disruptive technology. The legacy systems and other HIT systems that exist do not have to be excluded, but rather can be integrated into this new platform.
Identifying technology that, at its core, has the privacy, security, data management, and open structure could lead to the next generation of healthcare management systems. While some of these characteristics are obvious to developers and users alike, it is the sum of the parts that is important. Integrating most if not all of these characteristics into a single model is what can lead to enhancing the value of HIT and the delivery of care.
Toby Samo, MD is chief medical officer of Excelicare of Raleigh, NC.