Distributed Multi-Model Database for Medical Data Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management of medical data across multiple, independently operated hospitals with different data architectures and standards is complex and inefficient, often requiring manual access and extraction of patient records, which can compromise privacy and security, and is costly in terms of time and resources.

Innovation Solution

A distributed multi-model database architecture with user microservices that create and manage user-specific graph databases, a centralized management system with a user interface, profile microservices, a key-value database, and middleware for secure data access and communication, ensuring high security and ownership retention by data owners, utilizing encryption and blockchain for secure data storage and access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data integration is performed at application level across multiple hospitals with different data architectures, then data can be accessed and analyzed, but the system complexity increases and costs become very expensive due to the necessity of configuring caches, intermediate data lakes and scaling databases and processing servers

Engineering Contradiction:
Improvedata integration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a standardized data exchange format and protocol as an intermediary layer between heterogeneous hospital information systems. This intermediary enables data integration without requiring complex application-level configurations, caches, or intermediate data lakes, thereby reducing system complexity while maintaining adaptability across different data architectures

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data integration function into independent, standardized data exchange modules that can be deployed at each hospital independently. This segmentation eliminates the need for centralized scaling of databases and processing servers, reducing overall system complexity while preserving the ability to integrate diverse data sources

Inventive Principle:
Principle #1Segmentation

2Reliability

If patient data is stored in distributed hospital systems with different standards, then data ownership and security are maintained locally, but data retrieval and analysis become complex and inefficient

Engineering Contradiction:
Improvedata securityVSAvoiddata retrieval efficiency
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent creates standardized data copies or representations that conform to a universal exchange format, allowing efficient retrieval and analysis without compromising the security and ownership of original data stored in distributed hospital systems. The standardized copies enable cross-hospital data operations while the original data remains protected in its source systems

Inventive Principle:
Principle #26Copying

3Ease of manufacture

If conventional relational databases are used to store and query patient records with complex relationships, then data can be stored systematically, but multilevel joins become difficult to scale horizontally and are too complex for large datasets

Engineering Contradiction:
Improvedata storage organizationVSAvoidquery scalability
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent changes the fundamental data model parameter from relational tables to a graph-based structure where patient records and their relationships are represented as nodes and edges. This parameter change enables horizontal scaling of queries across large datasets by eliminating the need for complex multilevel joins, while maintaining systematic data organization through the graph model

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12135735B2Management system and method for a distributed multi-model database architecture
Publication Date: 2024.11.05 ALMA IT SYST SL
  • US12135735B2 patent drawing
  • US12135735B2 patent drawing
  • US12135735B2 patent drawing

AI summary

A distributed multi-model database architecture comprises a plurality of user microservices configured to create, store and manage graph databases with sensitive data of pre-existing conventional databases. A management system for the distributed multi-model database architecture comprises a user interface, a plurality of profile microservices, a key-value database and a middleware. The distributed multi-model database architecture is managed by a method for managing the distributed multi-model database architecture.