Dynamic Data Object Processing for Healthcare Information Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for managing and processing healthcare information/data fail to streamline multiple messages related to a single healthcare event into a coherent, computationally efficient, and user-friendly format, leading to resource strain and inconsistent data presentation.

Innovation Solution

A method and system that dynamically switch between real-time and deferred data processing based on message volume and resource availability, storing data objects in a first store until a user interaction event is detected, and then processing and storing them in a second store associated with an entity identifier.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If real-time data processing is used for all incoming messages, then data is processed immediately and user experience is responsive, but system resource strain increases significantly under high message volume

Engineering Contradiction:
Improvedata processing speedVSAvoidsystem resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system dynamically adjusts the data processing mode between real-time and deferred processing based on incoming message volume thresholds and resource availability thresholds. When message volume exceeds the threshold or resources are insufficient, the system switches from real-time processing to deferred processing, thereby adapting processing speed and resource consumption to current system conditions.

Inventive Principle:
Principle #15Dynamics

2Reliability

If all data objects are processed immediately upon receipt, then data consistency is maintained, but system productivity decreases due to continuous processing under high message volume

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of continuous real-time processing, the system implements periodic processing by batching data objects and processing them together when a user interaction event occurs. This periodic action reduces the frequency of processing operations while maintaining data consistency, thereby improving system throughput during high message volume periods.

Inventive Principle:
Principle #19Periodic action

3Use of energy by moving object

If deferred processing is used for all messages, then system resource consumption is reduced, but user experience suffers due to delayed data availability

Engineering Contradiction:
Improvesystem resource consumptionVSAvoiddata processing delay
Core Design Contradiction:
Use of energy by moving objectVSLoss of time

Solution Approach 1:

The system dynamically selects between real-time and deferred processing modes based on current message volume and resource availability. When message volume is low and resources are充足, real-time processing is used to minimize delay. When message volume is high or resources are constrained, deferred processing is used to reduce resource consumption, thus dynamically optimizing the trade-off between speed and resource usage.

Inventive Principle:
Principle #15Dynamics

4Productivity

If multiple data stores are used for deferred processing, then data management becomes more complex, but data retrieval efficiency improves when user interaction events occur

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoiddata store management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments data objects into different data stores based on their processing status: incoming data objects are stored in a first data store for deferred processing, while processed data objects are stored in a second data store associated with entity identifiers. This segmentation enables efficient retrieval during user interaction events while organizing data management through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12026154B2Managing data objects for graph-based data structures
Publication Date: 2024.07.02 UNITEDHEALTH GROUP INC
  • US12026154B2 patent drawing
  • US12026154B2 patent drawing
  • US12026154B2 patent drawing

AI summary

Various embodiments provide methods, systems, apparatus, computer program products, and/or the like for managing, ingesting, monitoring, updating, and/or extracting/retrieving information/data associated with an electronic record (ER) stored in an ER data store and/or accessing information/data from the ER data store.