Problem-Centric EHR GUI Inversion for Diagnosis Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional electronic health record (EHR) systems present patient health records in a SOAP note format, making it time-consuming and resource-intensive for healthcare workers to access diagnosis and treatment plans, especially when dealing with extensive records, as they often need to scroll or navigate through multiple pages.
Innovation Solution
A client computing device receives a patient identifier and transmits a query to a server EHR, which retrieves a computer-readable file containing patient encounter data, presenting a GUI with the healthcare issue at the forefront, allowing easy access to diagnosis and treatment plans without scrolling or page refreshes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If patient health records are presented in traditional SOAP note format, then complete medical documentation is maintained, but healthcare workers experience increased time consumption and computing resource usage due to scrolling and navigation requirements
Solution Approach 1:
The patent inverts the traditional SOAP note structure by presenting the Assessment and Plan components (diagnosis and treatment plans) at the top of the health record instead of at the bottom. This structural inversion allows healthcare workers to immediately view the most critical information without scrolling, directly resolving the contradiction between maintaining complete documentation and reducing access time.
Solution Approach 2:
The patent implements preliminary action by pre-positioning the diagnosis and treatment plan information at the beginning of the health record display. This allows healthcare workers to immediately access the most important information upon opening the record, eliminating the need to scroll through subjective and objective components first, thus reducing time loss while preserving complete documentation.
2Productivity
If patient health records are presented in traditional SOAP note format, then complete medical documentation is maintained, but computing resources are wasted due to multiple page refreshes and scrolling operations
Solution Approach 1:
By inverting the display structure to show Assessment and Plan first, the system eliminates the need for healthcare workers to scroll through extensive subjective and objective components, reducing computing resource consumption associated with scrolling and page rendering operations while maintaining complete documentation.
Solution Approach 2:
The patent extracts the most critical information (diagnosis and treatment plans) and positions it separately at the top of the display, allowing healthcare workers to access key information immediately without the computational overhead of scrolling through or rendering the entire SOAP note structure, thus improving productivity while reducing energy consumption.
3Loss of information
If diagnosis and treatment plans are placed at the end of SOAP notes, then structured documentation is maintained, but healthcare workers must navigate through multiple pages to locate critical information
Solution Approach 1:
The patent applies structural inversion by repositioning the Assessment and Plan sections from the end of SOAP notes to the beginning of the display. This ensures that critical information about diagnosis and treatment plans is immediately accessible without requiring navigation through multiple pages or sections, reducing both information loss and device complexity.
Data Source
AI summary
An improved graphical user interface (GUI) for displaying patient health records is described herein. A computing device transmits a query to a server computing device executing an electronic health records application (EHR). The EHR retrieves a computer-readable file for a patient comprising a plurality of file records, the plurality of file records including a file record reflective of a patient encounter with a healthcare worker for a healthcare issue. The EHR transmits data which causes the computing device to present a GUI including a first portion comprising an identity of the healthcare issue and a second portion comprising a treatment plan for the healthcare issue, patient symptoms, and observations made by the healthcare worker during the patient encounter. The first portion is oriented above the second portion such that the healthcare issue can be identified without scrolling through the GUI or refreshing the GUI.