Dynamic Patient Overview Message Generation via Central Broker

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge in the healthcare sector is to efficiently exchange and aggregate large volumes of decentralized medical data while ensuring data security and compliance with access authorization rules, as existing methods are resource-intensive and complex, especially when generating overview documents for patient summaries.

Innovation Solution

A system comprising an extraction service and a central broker service that reads data from local sources, selects relevant parameters, and generates an overview message dynamically, ensuring compliance with access authorizations by using a standardized platform, thereby reducing the computational load and improving data exchange efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is stored in decentralized repositories across multiple enterprises, then data security and compliance with access authorization rules are improved, but the complexity of extracting and aggregating relevant data increases significantly

Engineering Contradiction:
Improvedata securityVSAvoiddata extraction complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a central registry as an intermediary component that mediates between decentralized repositories and clients. The registry stores metadata and pointers to data locations without containing the actual sensitive data, thereby maintaining security while enabling efficient data discovery and aggregation across enterprises.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments data storage and management into distinct components: decentralized repositories hold actual data, the central registry holds metadata and access information, and extraction services handle data retrieval. This segmentation allows each component to specialize its function, improving both security and extraction efficiency.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If all medical data is centralized in one location, then data extraction and aggregation become simpler, but data security and compliance with access authorization rules deteriorate

Engineering Contradiction:
Improvedata extraction complexityVSAvoiddata security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The central registry acts as an intermediary that provides centralized coordination for data extraction without centralizing the actual sensitive medical data. It manages metadata, pointers, and access authorization information, enabling simplified extraction processes while keeping data distributed and secure in original repositories.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts only the essential metadata and access information from the actual medical data, placing it in the central registry. This allows the system to work with lightweight reference data for extraction operations while the full sensitive data remains securely stored in decentralized repositories.

Inventive Principle:
Principle #2Taking out (Extraction)

3Loss of information

If extensive data volumes are searched to find relevant information, then complete patient information is obtained, but the time and computational resources required increase significantly

Engineering Contradiction:
Improveinformation completenessVSAvoiddata retrieval time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-storing metadata, indexes, and pointers in the central registry that describe the location, content, and accessibility of data in decentralized repositories. This preliminary organization enables rapid data retrieval without searching through entire data volumes when extraction requests are made.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates lightweight copies of metadata and access information in the central registry that reference the actual data in decentralized repositories. These copies enable efficient data location and retrieval without requiring access to or copying of the entire extensive data sets.

Inventive Principle:
Principle #26Copying

4Loss of information

If data extraction services process all available data, then comprehensive overview messages are generated, but the computational load and resource consumption increase

Engineering Contradiction:
Improveinformation completenessVSAvoidcomputational energy
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The extraction services apply partial action by processing only the specific data subsets that are relevant to each extraction request, rather than processing all available data. The central registry enables this by providing targeted metadata and pointers that guide extraction services to only the necessary data portions.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The central registry mediates between extraction requests and data repositories by filtering and directing extraction services to only those data elements that match the request criteria. This intermediary function eliminates the need for comprehensive data processing by providing intelligent routing based on metadata.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11295837B2Dynamic creation of overview messages in the healthcare sector
Publication Date: 2022.04.05 SIEMENS HEALTHINEERS AG
  • US11295837B2 patent drawing
  • US11295837B2 patent drawing
  • US11295837B2 patent drawing

AI summary

A method, a system and different nodes are for the provision of an overview message for a patient. The overview message summarizes all relevant data records stored on the previous treatment of the patient and contains references for accessing the respective documents containing the components of the overview message, and for which it has been possible to validate access authorizations. As such, only permissible access to sensitive databases is provided.