Explore the intricate landscape of EHR integration as revealed by a recent JAMIA study. With 73% of digital health companies utilizing standards-based APIs, the research underscores the industry’s progress toward interoperability. However, a significant 57% still employ a hybrid approach, incorporating proprietary APIs. The study highlights the challenges faced, including high fees and a lack of crucial data elements. Recommendations call for federal policy support to streamline API adoption. A collaborative, inclusive approach involving diverse industry stakeholders is seen as crucial. The findings emphasize the need for an iterative process, incorporating industry feedback, to propel the evolution of standards-based APIs in sync with developer needs.
In the ever-evolving landscape of healthcare technology, a recent study published in the Journal of the American Medical Informatics Association (JAMIA) sheds light on the integration practices of digital health companies with Electronic Health Records (EHRs). The study, aimed at capturing the experiences of these companies, reveals a dynamic scenario where standards-based Application Programming Interfaces (APIs) play a pivotal role in enhancing interoperability.
API Integration Landscape:
The study, conducted through a national survey targeting digital health companies involved in the development of tools facilitating interaction with EHR APIs, produced intriguing insights. A noteworthy 73% of respondents reported the utilization of standards-based APIs for EHR integration. This reflects a positive trend towards adherence to federally regulated standards-based API policies designed to propel interoperability within the healthcare ecosystem.
While the majority of companies embrace standards-based APIs, the study also brought to light that approximately 57% of respondents employ a hybrid approach. These companies integrate both standards-based and proprietary APIs to establish connections with EHR systems. Despite this, the prevalence of standards-based APIs over proprietary ones suggests their heightened significance in ensuring successful integration.
Challenges and Opportunities:
The findings underscore a dual reality in the digital health landscape. While strides are being made towards the adoption of standards-based APIs, a substantial number of companies still rely on non-standards-based APIs to varying extents. The survey reveals that, on average, standards-based APIs pose a lesser burden than proprietary counterparts in terms of setup and maintenance. However, certain barriers impede the widespread adoption of standards-based APIs.
Challenges such as high fees, a dearth of realistic clinical testing data, and a lack of data elements deemed valuable are reported by companies as hindrances. To overcome these challenges, the study recommends a multi-pronged approach involving federal policy support. This includes measures such as cost controls, testing and validation support, and an expansion of the set of data elements deemed crucial for effective standards-based API integration.
Recommendations for Improvement:
The study’s respondents emphasized the need for further private-sector support and federal policy interventions to ensure the availability of APIs without imposing excessive entry barriers. The authors advocate for a collaborative effort that involves industry stakeholders, not limited to EHRs but also encompassing the digital health and app developer community. This inclusive approach aims to address the technical and functional aspects of standards-based APIs, aligning them with the evolving needs of developers.
Opportunities for Industry and ONC:
The study findings reveal an opportune moment for industry players and the Office of the National Coordinator for Health Information Technology (ONC) to gather input on high-value use cases. These use cases, not currently adopted in the United States Core Data for Interoperability (USCDI) standard and standards-based APIs, present an avenue for refining and expanding existing standards.
The authors highlight the importance of an iterative and inclusive approach, emphasizing the incorporation of industry feedback beyond EHRs. By engaging the broader digital health and app developer community, the aim is to propel the technical and functional properties of standards-based APIs forward in sync with the evolving needs of developers.
As digital health companies navigate the complexities of EHR integration, the study’s nuanced findings underscore both progress and challenges. While standards-based APIs dominate, the prevalence of a hybrid approach signals a transitional phase. Overcoming obstacles such as high fees and data element shortages demands collaborative efforts. Recommendations for federal policy support highlight the need for cost controls and expanded data elements. The study advocates an inclusive approach, involving not just EHRs but the broader digital health community. Ultimately, an iterative process, incorporating industry feedback, emerges as pivotal to shaping the trajectory of standards-based API integration, fostering competition, and enhancing healthcare interoperability.
