Payer-Provider Connect Engine for Healthcare Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Inefficient payer-provider connectivity in healthcare settings leads to delays in closing gaps in care, improper risk adjustment scores, and inadequate collaboration, primarily due to antiquated methods for sharing medical records and lack of proper infrastructure for clinical data exchange.

Innovation Solution

A payer-provider connect framework that analyzes medical information from both payer and provider systems to reconcile gaps in care, enabling real-time data sharing and automatic scheduling of medical tests, and facilitating accurate Risk Adjustment Score calculations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If antiquated methods are used to retrieve and share medical records, then system complexity is reduced, but significant delays occur in closing gaps in care

Engineering Contradiction:
Improvedelay in closing gaps in careVSAvoidinfrastructure complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

A Health Information Exchange (HIE) infrastructure is introduced as an intermediary system that enables seamless data exchange between payers and providers. The HIE acts as a mediator that reconciles data from multiple sources (payer systems, provider systems, labs, imaging) and distributes relevant information to appropriate parties, eliminating the delays associated with antiquated direct connection methods while managing complexity through standardized interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The HIE infrastructure is designed as a universal platform that serves multiple functions: data collection from diverse sources, data reconciliation, gap identification, information distribution to payers and providers, and support for various healthcare operations. This multi-functional approach consolidates multiple specialized systems into a single infrastructure, reducing overall system complexity while enabling timely information sharing.

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

2Reliability

If proper infrastructure and standards are implemented for clinical data sharing, then data accuracy and collaboration improve, but implementation complexity and cost increase

Engineering Contradiction:
Improveaccuracy of risk adjustment scoresVSAvoidinfrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The HIE implements standardized data parameters and formats for clinical information exchange, transforming diverse data from different sources into a unified structure. By establishing consistent parameters for patient demographics, clinical data, diagnoses, and treatments, the system ensures accurate risk adjustment score calculations while managing complexity through standardization rather than custom integrations.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The HIE serves as a mediating infrastructure that handles the complexity of data standardization and reconciliation, allowing payers and providers to benefit from accurate data exchange without each organization needing to implement complex standalone solutions. The intermediary manages the transformation and validation of data according to established standards.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If real-time data sharing is implemented between payers and providers, then closure of gaps in care is accelerated, but system complexity and data integration requirements increase

Engineering Contradiction:
Improvespeed of closing gaps in careVSAvoiddata integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The HIE enables continuous, real-time data exchange between payers, providers, and other healthcare entities through standardized interfaces. Rather than periodic batch processing, the system maintains continuous connectivity and data flow, allowing immediate identification and closure of care gaps as new information becomes available, while the standardized architecture manages integration complexity.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The HIE provides a universal data exchange platform that handles multiple types of communications (clinical data, billing information, gap notifications, scheduling) through a single integrated infrastructure. This multi-functional approach enables real-time productivity improvements without requiring separate complex integration systems for each data type.

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

4Ease of operation

If manual processes are used for retrieving and sharing medical records, then technology infrastructure is simplified, but collaboration efficiency between payers and providers decreases

Engineering Contradiction:
Improvecollaboration efficiencyVSAvoidtechnology infrastructure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The HIE replaces manual, mechanical processes of record retrieval and sharing with automated electronic data exchange. Instead of manual requests, paper-based record transfer, or phone communications, the system uses automated electronic interfaces to collect, reconcile, and distribute clinical data, dramatically improving collaboration efficiency while the standardized architecture manages the technological complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11455690B2Payer provider connect engine
Publication Date: 2022.09.27 VVC HOLDING CORP
  • US11455690B2 patent drawing
  • US11455690B2 patent drawing
  • US11455690B2 patent drawing

AI summary

Systems, methods and computer program products to identify and close gaps in care are provided. Aspects of the present disclosure disclosed and described herein enable a payer may identify gaps in care based on information in the payer database. The payer can send this information to the provider prior to patient scheduling. The scheduling system at the provider can use this information to schedule patients and their medical needs (e.g., medical test, lab tests, imaging tests, etc.) before the next patient appointment. Primary care providers (PCPs) can then be made aware of the gaps in care information, as well as Hierarchical Condition Category (HCC) coding gap information, so they can perform a complete diagnosis using all available clinical data. PCP notes along with the treatment the patient receives can be combined with the RAF (Risk Adjustment Score) shared by the payers to ensure patient is assessed for all relevant conditions during the visit. Payers can then be informed electronically that the gap in care has been closed; the payer can also receive the resultant claims such that correct RAF scores can be computed and HCC coding gaps can be closed.