Router-Based Data Interoperability for Microservice Architecture

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data interoperability standards, such as FHIR™ and SMART on FHIR, primarily focus on enabling data exchange between systems but lack a conducive schema for internal processing and utilization by functional or capability modules, leading to decreased scalability and reliability due to independent data schemas within encapsulated services or microservices.

Innovation Solution

A data processing system architecture that utilizes a router to unify functional modules into a single, distributed server, enforcing access permissions and routing data packets based on interoperability standards, allowing modules to maintain autonomy and improve scalability and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If functional modules use independent data schemas for encapsulation, then module autonomy and flexibility are improved, but data interoperability and system reliability deteriorate

Engineering Contradiction:

Improvemodule autonomyVSAvoiddata interoperability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a router as an intermediary component that mediates between functional modules with independent data schemas. The router receives data from various modules, translates their independent schemas into a unified FHIR standard schema, and routes the standardized data to appropriate destinations. This mediator enables modules to maintain their autonomy while ensuring reliable interoperability through standardization at the routing layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data is processed in multiple independent schemas across encapsulated services, then system flexibility is improved, but processing complexity and scalability worsen

Engineering Contradiction:

Improvesystem flexibilityVSAvoidprocessing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the data processing system into independent functional modules (capsules) that each handle specific business logic, while the router handles schema translation and routing as a separate concern. This segmentation allows modules to be developed and maintained independently with their own data schemas, while the router provides centralized schema management, reducing overall system complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The router serves multiple functions: it receives data from various functional modules with different schemas, translates all incoming data to a universal FHIR standard schema, enforces access permissions based on scopes, and routes data to appropriate destinations. This multi-functionality reduces processing complexity by consolidating schema translation and routing logic in a single universal component.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Reliability

If a unified data schema is enforced across all functional modules, then data interoperability is improved, but module autonomy and development flexibility worsen

Engineering Contradiction:

Improvedata interoperabilityVSAvoiddevelopment flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The router acts as an intermediary that allows functional modules to use their own preferred data schemas for internal processing while ensuring that data exchanged between modules and external systems is standardized to FHIR. This mediator enables development flexibility at the module level while maintaining interoperability at the system level.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If functional modules operate independently with their own data schemas, then development speed is improved, but data consistency and trustworthiness worsen

Engineering Contradiction:

Improvedevelopment speedVSAvoiddata consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The router serves as a mediator that receives data from independently developed functional modules, validates and translates their data to a consistent FHIR schema, and ensures data consistency before routing. This allows rapid development of independent modules while maintaining data consistency through standardized translation at the routing layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250209196A1Processing data formatted in accordance with an interoperability standard for electronic exchange of data

Publication Date: 2025.06.26 LEAGUE

AI summary

An architectural pattern for a data processing system that utilizes a router to unify all individual instances of functional or capability modules into a single, distributed server. The router in such an architecture is generally configured based on a federated model in which all functional modules are responsible for maintaining their own data stores and communicate with one another indirectly through the router. To facilitate communication between functional modules, the router leverages parameters of the interoperability standard in order to enforce access permissions on and allow for efficient routing of data packets between sources and destinations. Through operation of the router, the functional modules included within the capability layer achieve degrees of autonomy of encapsulation that are advantageous from a design productivity and operational standpoint. By intrinsic processing of data formatted according to the interoperability standard, the functional modules are compatible with both internal and external networked resources.