Healthcare providers are
moving forward with their digital initiatives, pursuing intranet development, implementing e-prescribing software, and deploying
EHR systems and patient portals to enhance patient care, maximize staff
efficiency, and improve the bottom line.
However, while medical professionals
are largely enthusiastic about digital healthcare solutions, the disparity
between the rate of clinical support and patient utilization of some of this
software, patient portals in particular, is enormous. Even though patient
self-service solutions have become ubiquitous in medical facilities nation-wide,
over 62% of US hospitals report that their patient portal systems are used by less than a quarter of all patients.
Patients still don’t see
enough value in patient portals, voicing concerns over the steep learning curve,
lack of training, anxiety regarding data security and confidentiality, and
other issues. Addressing these challenges is critical to encouraging patient
buy-in and getting more patients involved in their health.
Since most medical
facilities in the country already have patient portals in place, the next step
to overcome barriers to their adoption is to expand these systems to deliver
features that will get more patients involved.
The opioid crisis in the United States is having a devastating impact on individuals, their families, and the health care industry. This multi-part series will focus on the role technology can play in addressing this crisis. Part one of the series proposed a strategic framework for evaluating and pursuing technical solutions.
A Framework for Innovation
As noted in part one of our series, we believe the opioid crisis is an “All Hands-On Deck” moment and health IT (HIT) has a lot to offer. Given the many different possibilities, having a method for organizing and prioritizing potential IT innovations is an important starting point. We have proposed a framework that groups opportunities based on an abstract view of five types of functionality. In this article we will explore the role of technologies that provide clinical decision support.
This week a host of organizations responded to a Senate Finance Committee request for feedback on how to better use healthcare data.
The inquiry is timely, given the widespread frustration providers have with health information technology (HIT), and electronic health records (EHR) systems in particular. This frustration stems from many HIT/EHR systems are locked in proprietary systems. This hinders technology’s ability to connect and exchange information freely between disparate systems, devices and sensors along the care continuum, thus undermining the overall goal of using HIT to improve efficiencies and reduce costs.
An example illustrates the point. Because HIT systems don’t work together, most hospitals use nurses to manually double check input from disparate “smart” devices. For instance, an infusion pump reports the level of pain medication being administered to a patient, as does the EHR. But these numbers sometimes don’t match, and must be double checked by at least two nurses to confirm the right dosing. Not only is this a step back for efficiency, but it’s also another manual process that has the potential to create errors and patient safety issues.
There are also economic consequences of data fragmentation. According to the Office of the National Coordinator (ONC), U.S. providers are spending $8 billion a year due to the lack of interoperability.
To address this problem and reduce the unnecessary fragmentation of healthcare data, it’s time to require the use of open and secure applications programming interfaces (APIs).
In April, a group of America’s leading scientists, named JASON, published a report that found the current lack of interoperability among HIT data sources is a major impediment to the exchange of health information. They recommended that EHR vendors be required to develop and implement APIs that support health data architecture. The recommendation was also endorsed by the President’s Council of Advisors on Science and Technology (PCAST) in May. Requiring open APIs as a foundational standard for healthcare data would reverse the current legacy of locked systems and enable the real-time exchange of information in EHR systems to reduce costs and improve patient safety.