Health Information Exchange System with Global Identifier Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current healthcare information exchange systems face challenges in efficiently managing and securing the exchange of physical and behavioral health care information due to evolving privacy requirements and varying technical systems, lacking effective mechanisms for consent management and data routing across different healthcare providers.

Innovation Solution

A system comprising a master patient database, exchange partner database, sub-network database, and global identifier database, with modules for managing consents, data routing, and communication protocols, ensuring secure and compliant data exchange by verifying active contracts and consents between healthcare providers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a centralized health information exchange system is implemented to enable data sharing across multiple healthcare providers, then the ability to exchange health information is improved, but the complexity of managing consent and contract validation across diverse providers increases

Engineering Contradiction:
Improveability to exchange health informationVSAvoidcomplexity of managing consent and contract validation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a Health Information Exchange (HIE) system that acts as an intermediary between multiple healthcare providers. The HIE receives, validates, and routes health information requests according to consent and contract rules, mediating the exchange between providers without requiring direct point-to-point agreements. This centralizes the complexity of consent management while enabling versatile data exchange across the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The HIE system provides universal functionality for validating consents and contracts across diverse healthcare providers with varying technical systems. A single platform handles multiple data types, communication protocols, and provider configurations, making the system adaptable to different providers while maintaining consistent validation rules through standardized processes.

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

2Reliability

If comprehensive consent validation is performed to ensure privacy compliance before data exchange, then patient privacy protection is improved, but the time required to process data exchange requests increases

Engineering Contradiction:
Improvepatient privacy protectionVSAvoidtime required to process data exchange requests
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary validation of consent and contract status before initiating data exchange. The HIE checks whether valid consent exists and whether the requesting provider has appropriate contractual rights before processing the actual data request. This preliminary action ensures privacy compliance is established upfront, preventing unauthorized exchanges and reducing rework.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The HIE implements feedback mechanisms that track consent validation status and contract effectiveness dates. When consent or contracts expire, the system provides feedback to stop further exchanges automatically. This continuous monitoring ensures ongoing compliance without requiring manual intervention for each data request, reducing processing time while maintaining reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11017886B2Health information exchange system and method
Publication Date: 2021.05.25 PETER CHANG ENTERPRISES INC D B A PCE SYST
  • US11017886B2 patent drawing
  • US11017886B2 patent drawing
  • US11017886B2 patent drawing

AI summary

A system, method and program product, the system comprising: memory comprising one or more non-transitory computer-readable media comprising: a master patient database; an exchange partner database; a sub-network database; and a global identifier database storing a plurality of global identifiers; and one or more computers configured with: an inbound module for receiving incoming request data or results data from an exchange partner, including a sub-process to determine when one of a plurality of methods is identified by the incoming data, a sub-network and/or one or more responding exchange partners, a requested data type, and whether a patient is identified; a sub-process to create when the incoming data is destined for a different exchange partner, a respective communication manager sub-process for each of the one or more or responding exchange partners; an outbound request module that has a multi-level consent determination process, and a sub-process to create, by the one or more computers, a global identifier comprising a link between the respective responding exchange partner and the requesting exchange partner for an initial transfer of the data.