Index Server Referencing for Distributed Patient Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the context of distributed patient-related data storage across multiple medical entities, existing systems face challenges in quickly identifying the existence and location of patient data records without accessing the data, especially when providing access beyond institutional boundaries.

Innovation Solution

A method and system for referencing patient-related data records in a distributed network, involving the conversion of original identifiers into search criteria, using index servers to detect and output references to the data records, allowing for cross-network analysis without accessing the data content, and utilizing dynamic identification mechanisms based on different entities' requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If patient-related data are stored in a distributed manner across multiple medical entities, then data availability and accessibility are improved, but the complexity of identifying and locating data records increases

Engineering Contradiction:
Improvedata availabilityVSAvoididentification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary indexing system that mediates between data storage entities and query requests. Index servers maintain reference structures that map patient identifiers to data record locations across distributed medical entities, enabling efficient location identification without requiring direct access to or traversal of the entire distributed data storage network.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the distributed data storage system into independent medical entities (hospitals, clinics, practices) each maintaining their own data records, while introducing a separate indexing layer that operates independently. This segmentation allows data to remain distributed for availability while the indexing layer simplifies the identification complexity by providing a unified search interface.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If comprehensive search across distributed networks is performed to locate patient data, then data location accuracy is improved, but search time and system resources increase

Engineering Contradiction:
Improvedata location accuracyVSAvoidsearch time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing index structures at multiple levels before actual data queries are executed. Index servers maintain reference indices that pre-map patient identifiers to data record locations, enabling rapid query resolution without performing comprehensive searches across the entire distributed network at query time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent adds a dimensional layer by introducing index servers that operate at a different level from the actual data storage entities. Instead of searching through data records directly (one dimension), the system searches through index references (another dimension), significantly reducing search time while maintaining location accuracy.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Adaptability or versatility

If data records are made accessible beyond institutional boundaries, then healthcare cooperation and data sharing are improved, but security risks and data protection challenges increase

Engineering Contradiction:
Improvecross-institutional accessVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent uses index servers as intermediaries between authorized users and distributed data records. The indexing system provides a secure layer that enables cross-institutional data access while maintaining control over data locations and access permissions, thereby reducing direct security risks associated with unrestricted data sharing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the identification and location function from the data storage function itself. By separating the indexing/reference mechanism from the actual data records, the system enables secure cross-institutional access to data locations without exposing or transferring the data content, thereby minimizing security risks.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If multiple identification mechanisms are used across different entities, then system adaptability is improved, but identifier conversion and compatibility complexity increases

Engineering Contradiction:
Improveidentifier compatibilityVSAvoidconversion complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by introducing a standardized reference mechanism that serves multiple functions: it stores original identifiers from different entities, maintains converted identifiers for various systems, and provides unified search capabilities. The indexing system acts as a universal interface that handles diverse identification mechanisms without requiring direct conversion logic at the data storage level.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9020828B2Referencing of patient-related information in a distributed medical system
Publication Date: 2015.04.28 SIEMENS HEALTHINEERS AG
  • US9020828B2 patent drawing
  • US9020828B2 patent drawing

AI summary

A method, a system and a computer program product are disclosed for referencing medical electronically available patient-related data records which are stored in a distributed manner in a computer-based network, including a multiplicity of computer-based entities. In at least one embodiment, a request for patient-related data records is generated on the basis of an original identifier and is sent to an index server. By accessing a table, the index server checks whether entries or data records are stored for the respective patient in the respective repository. If so, it inserts this reference to the storage location into the result. The request is forwarded from index server to index server until all index servers have been processed, so that the end result can be forwarded to the requesting workstation with all references to requested patient-related data records.