Proximity Patient Check-In With Cached EHR Queueing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional patient check-in systems in electronic health records (EHRs) face inefficiencies such as patient data updates being cumbersome due to highly normalized data structures, inability to automatically reschedule appointments based on patient proximity, and lack of patient access to appointment status on their devices.

Innovation Solution

A distributed EHR system with server-side and client-side functionalities that utilizes a cache to store patient information in denormalized form, allows for automatic appointment rescheduling based on patient location, and enables patients to view appointment status on their devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If patient information is stored in highly normalized forms in the data store, then data integrity and consistency are improved, but updating patient data becomes cumbersome and time-consuming

Engineering Contradiction:
Improvedata integrityVSAvoidtime to update patient data
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining a cache of patient information in denormalized form before actual check-in occurs. This allows patient data to be pre-loaded and prepared, so when check-in needs to occur, the information is already readily available, eliminating the need for time-consuming updates to the normalized data store.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of patient information in the cache in a denormalized format that is easier to update. This copy can be modified quickly without affecting the integrity of the original normalized data in the data store, allowing rapid check-in operations while preserving data integrity.

Inventive Principle:
Principle #26Copying

2Reliability

If conventional patient check-in systems are used, then existing EHR functionality is maintained, but automatic rescheduling based on patient proximity is not achieved

Engineering Contradiction:
Improveappointment schedulingVSAvoidautomatic rescheduling
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system implements feedback by continuously monitoring patient location data and automatically adjusting appointment schedules based on real-time proximity information. When a patient's location indicates they will be late, the system automatically reschedules the appointment, creating a closed-loop control system that adapts to changing conditions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-service by automatically rescheduling appointments without requiring manual intervention from healthcare workers. The EHR system monitors patient proximity and autonomously makes scheduling decisions, reducing the need for human involvement in the rescheduling process.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If patients manually relay information to healthcare workers, then patient check-in is performed, but the process is time-consuming and requires manual data entry

Engineering Contradiction:
Improvepatient check-in processVSAvoidcheck-in time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables self-service by allowing patients to automatically check themselves in through the mobile application. The app retrieves patient information from the cache and completes the check-in process without requiring manual interaction with healthcare workers, making the process easier and faster for patients.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces the mechanical process of manual data entry with automated electronic data retrieval. Instead of patients verbally providing information or filling out paper forms, the mobile application electronically retrieves and submits patient data from the cache, eliminating manual labor in the check-in process.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If the EHR accesses the data store frequently to retrieve patient information, then accurate patient data is obtained, but resource usage increases

Engineering Contradiction:
Improvepatient data accuracyVSAvoidcomputational resource usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary action by pre-loading patient information into the cache before it is needed for check-in. This allows the EHR to retrieve data from the fast cache memory rather than repeatedly accessing the slower data store, reducing computational resource usage while maintaining data accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The cache serves as an intermediary between the EHR and the data store. It holds copies of patient information that can be quickly accessed by the EHR without requiring direct access to the data store, reducing the frequency of expensive data store operations while ensuring accurate patient data is available.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12494282B1Proximity-based patient check-in computing system
Publication Date: 2025.12.09 ALLSCRIPTS SOFTWARE LLC
  • US12494282B1 patent drawing
  • US12494282B1 patent drawing
  • US12494282B1 patent drawing

AI summary

An improved patient check-in system for healthcare appointments is disclosed herein. Prior to a datetime of a healthcare appointment of a patient, an electronic health records application (EHR) receives a first message originating from a patient computing device of the patient. The first message includes a location of the patient and patient information for the patient. Responsive to receiving the first message, the EHR stores the patient information in a cache. The EHR also places a placeholder for the patient in a queue that indicates an order in which healthcare appointments for patients at the healthcare facility are to occur. Subsequently, the EHR receives a second message generated by the patient computing device indicating that the patient has arrived at the healthcare facility for the healthcare appointment. The EHR transfers the patient information from the cache to a data store accessible to the EHR.