GUI Generator Using HTTP POST for Secure FHIR Data Transmission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing healthcare IT systems face security risks and sub-optimal performance due to the need for EHRs to expose their FHIR API layers and the limitations of HTTP GET requests, which restrict the use of certain security tokens and result in inefficient data transmission.
Innovation Solution
The proposed solution involves using a client computing device to transmit an HTTP POST request to a server EHR, which includes resources and a security token, allowing for secure and efficient data transmission without exposing the FHIR API layer, and enabling the use of larger security tokens and data payloads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If HTTP GET request is used to transmit data between EHR and GUI generator component, then the communication follows SMART standard protocols, but the payload size is limited and certain security tokens cannot be used
Solution Approach 1:
The patent changes the HTTP request method from GET to POST, which fundamentally alters the parameter constraints. POST requests do not have the same payload size limitations as GET requests, allowing larger security tokens and data to be transmitted while maintaining SMART standard compatibility through proper implementation
2Ease of operation
If FHIR API layer is exposed to allow GUI generator component to request resources, then the component can retrieve necessary data, but security risks increase
Solution Approach 1:
The patent extracts the security token authentication mechanism from the resource retrieval process. Instead of exposing the FHIR API layer which handles both authentication and data retrieval, the system uses a separate authentication endpoint that issues security tokens. These tokens are then used in subsequent resource requests without requiring the FHIR API to be directly exposed, thereby separating security functions from data access functions
Solution Approach 2:
The patent introduces a security token as an intermediary between the EHR system and the GUI generator component. The security token acts as a mediator that carries authentication information without requiring direct exposure of the FHIR API layer. The token can be embedded in POST request bodies or headers, allowing secure resource retrieval while maintaining API security
3Reliability
If additional API calls are made to retrieve resources for GUI feature generation, then the GUI can be updated with current data, but communication efficiency decreases
Solution Approach 1:
The patent combines multiple API calls into a single POST request. Instead of making separate calls for authentication, resource retrieval, and GUI generation, the system transmits the security token and resource requests in one consolidated POST request body. This merging of operations maintains data currency while significantly improving communication efficiency by reducing the number of round trips between EHR and GUI generator component
Data Source
AI summary
A client computing device transmits a resource that conforms to a healthcare interoperability standard to a server computing device that executes a GUI generator component, and the GUI generator component generates GUI markup based upon the resource. The GUI generator component returns the GUI markup to the client computing device, which presents the GUI features on the a display based upon the GUI markup.