Supplement Application Context Data Intermediary for EHR Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Many electronic health record (EHR) systems do not support integration standards like HL7 CCOW, rendering supplement applications inoperable and preventing them from providing contextually relevant information to healthcare workers, even though these applications can offer valuable data.
Innovation Solution
A computer-executable supplement application that receives data from an EHR through an API call, even if the EHR does not support integration standards, allowing it to provide contextually relevant information by constructing queries based on context data and retrieving data from multiple sources, and displaying this information concurrently with the EHR GUI.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If supplement applications are tightly integrated with EHRs using integration standards like HL7 CCOW, then the supplement applications can provide contextually relevant information to healthcare workers, but many legacy EHRs do not support these integration standards, rendering the supplement applications inoperable
Solution Approach 1:
The patent introduces an intermediary component that sits between the supplement application and the EHR system. This intermediary captures context data from the EHR through available integration methods (even simple ones like copying data from the EHR interface) and relays it to the supplement application, enabling operation without requiring the EHR to support complex integration standards like HL7 CCOW.
Solution Approach 2:
The supplement application is designed to work with multiple types of EHR systems through a universal interface approach. Rather than requiring each EHR to implement specific integration standards, the system uses a universal method of capturing context data that can adapt to different EHR implementations, making the supplement application broadly compatible across legacy and modern systems.
2Productivity
If the EHR issues an API call to a supplement application, then the supplement application can receive context data and provide supplemental information, but the supplement application must be launched in response to the API call if it is not currently being executed
Solution Approach 1:
The system performs preliminary actions by pre-loading or pre-positioning the supplement application in a state where it can be quickly activated. The application may be kept in memory or in a suspended state ready to resume, so that when the EHR issues an API call, the supplement application can begin processing context data with minimal delay, reducing both launch time and maintaining productivity.
Solution Approach 2:
The supplement application employs dynamic behavior by adjusting its execution state based on system conditions. It can transition between suspended and active states, and may pre-initialize certain components or data structures when system resources are available, allowing it to respond quickly to API calls while optimizing resource utilization.
Data Source
AI summary
Described herein are various technologies pertaining to displaying contextually relevant supplemental content retrieved from population data concurrently with data presented to a healthcare worker in a graphical user interface of an electronic health record application (EHR). Also described herein are graphical user interface features pertaining to concurrent display of a graphical user interface of the EHR and a graphical user interface of a supplement application.