Healthcare Data System with Blockchain and Microservices

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The healthcare industry faces unsustainable costs due to inefficiencies in data exchange, storage, and processing across non-uniform systems, necessitating a system that is interoperable, secure, efficient, and scalable for improved data management and transaction processing.

Innovation Solution

A networked computing system comprising a front end and back end with smart card authentication, API gateway, and blockchain data servers, enabling secure, efficient, and transparent data storage and processing, with microservices for specific healthcare functions and interoperability with third-party systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If non-uniform and incompatible systems are used for data exchange and storage, then existing systems can be maintained with minimal changes, but efficiency and interoperability deteriorate

Engineering Contradiction:

ImproveinteroperabilityVSAvoiddata processing efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal data exchange standard that enables different healthcare systems (providers, payers, TPAs) to communicate through a common interface. This standardization layer allows the system to work with multiple incompatible systems simultaneously, improving interoperability without sacrificing the ability to maintain existing systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary data exchange platform that sits between incompatible healthcare systems. This mediator translates and standardizes data from various sources into a unified format, enabling efficient processing while maintaining compatibility with existing non-uniform systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If centralized data storage is used, then data access and processing are simplified, but security and fault tolerance deteriorate

Engineering Contradiction:

Improvedata access simplicityVSAvoidsystem fault tolerance

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized data storage into multiple distributed nodes across different locations. Each node stores portions of the healthcare data, and the system uses distributed consensus mechanisms to maintain data integrity. This segmentation provides fault tolerance while maintaining simplified access through a unified interface.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing different nodes to have specialized storage capabilities optimized for specific types of data access patterns. Each node can be tuned for particular query types or data formats, while the overall system presents a simplified access interface to users.

Inventive Principle:

Principle #3Local quality

3Device complexity

If manual data exchange processes are used, then system complexity is reduced, but processing time and costs increase

Engineering Contradiction:

Improvesystem architecture complexityVSAvoidtransaction processing time

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical data exchange processes with automated electronic data interchange systems. The standardized interface enables automatic translation, validation, and routing of data between systems, dramatically reducing processing time while the modular architecture keeps system complexity manageable.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent implements preliminary action by pre-configuring data exchange rules, validation schemas, and routing logic in the standardized interface. This preparation work is done beforehand, allowing data to flow automatically through the system without real-time manual intervention, reducing processing time while maintaining manageable complexity.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If legacy healthcare systems are maintained, then existing investments are protected, but scalability and modern functionality are limited

Engineering Contradiction:

Improvesystem stabilityVSAvoidscalability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent adds another dimension to legacy systems by introducing a standardized data exchange layer that operates above the existing system architecture. This allows legacy systems to maintain their stable core while gaining access to modern scalability and functionality through the new interface layer, enabling both reliability and adaptability simultaneously.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11863609B2System for storing, processing, and accessing medical data

Publication Date: 2024.01.02 HEALTH IN TECH INC

AI summary

A system is disclosed for storage, processing, and accessing of data. The system includes a front end system and a back end system communicatively connected to the front end system. A front end system is configured to provide one or more user interfaces configured to store, process, and access data in a first data server, in response to user input, by sending messages to the back end system. The back end system includes the first data server and one or more processing servers. The one or more processing servers are configured to process messages received from the front end system by accessing in the first data server to perform one or more operations specified by the messages. The back end system also includes a blockchain server configured to maintain a record of changes made to data in the first data server by the one or more processing servers.