Code Generator for Multi-System EHR Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current applications for accessing Electronic Health Records (EHRs) face limitations in interoperability due to different data formats and APIs used by various health care provider facilities, making it difficult to extract and process data from disparate EHR systems, which hinders continuity of care across multiple facilities.

Innovation Solution

A system that allows users to build custom applications with little to no coding, using an application builder that generates code for accessing and processing EHR data from multiple systems by leveraging standards like FHIR, enabling extraction and presentation of user-selected data across different EHR systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications are designed to access specific EHR systems with fixed data formats and APIs, then access to that specific system is reliable and efficient, but the application cannot access data from other EHR systems with different formats and APIs

Engineering Contradiction:
Improveaccess to multiple EHR systemsVSAvoidapplication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (code generator system) that translates between different EHR system formats and a standardized internal representation. This mediator handles the complexity of multiple APIs and data formats, allowing applications to access diverse EHR systems without increasing their own complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The code generator creates universal access mechanisms that can work across multiple EHR systems. By generating adaptive code that implements standardized interfaces, a single application architecture can universally access different EHR systems through their respective APIs, eliminating the need for system-specific custom applications.

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

2Adaptability or versatility

If applications are customized for each EHR system to handle specific data formats, then data extraction is precise and reliable, but multiple applications are needed to access different EHR systems

Engineering Contradiction:
Improvemulti-system access capabilityVSAvoidnumber of applications
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments the complexity of EHR system access into separate, generatable code components. Instead of building complete custom applications for each system, the system generates only the necessary access layer (code modules) that can be dynamically assembled, reducing the total quantity of applications needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The code generator creates reusable access patterns and templates that can be copied and adapted across different EHR systems. By storing and reusing proven access patterns for common EHR systems, the system avoids redundant application development and reduces the overall number of applications required.

Inventive Principle:
Principle #26Copying

3Reliability

If developers write custom code for each EHR system integration, then the application can be optimized for that specific system, but the development time and coding effort increase significantly

Engineering Contradiction:
Improvesystem-specific optimizationVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-defining standardized access patterns, data formats, and error handling procedures for common EHR systems. The code generator retrieves and adapts these pre-prepared patterns rather than creating everything from scratch, significantly reducing development time while maintaining system-specific optimization through targeted customization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of rewriting entire applications for different EHR systems, the system changes parameters such as API endpoints, data format mappings, and authentication methods while maintaining the core application logic. The code generator dynamically adjusts these parameters to match the target EHR system, preserving optimization without requiring full redevelopment.

Inventive Principle:
Principle #35Parameter changes

4Ease of manufacture

If applications use standardized interfaces for EHR access, then code reusability and interoperability improve, but the ability to handle diverse and evolving EHR systems decreases

Engineering Contradiction:
Improvecode reusabilityVSAvoidhandling diverse EHR systems
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic code generation that creates standardized interfaces adapted to the specific EHR system being accessed. Rather than using a fixed static interface, the system generates the appropriate interface layer at runtime based on the target system's capabilities, maintaining both standardization for reusability and flexibility for handling diversity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The code generator employs a nested architecture where standardized access patterns are contained within adaptable wrappers. The nested structure allows standardized reusable components to be embedded within system-specific adaptation layers, enabling both code reusability at the core level and adaptability at the interface level.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS20240331816A1Code generator for accessing differing health record systems
Publication Date: 2024.10.03 CERNER INNOVATION INC
  • US20240331816A1 patent drawing
  • US20240331816A1 patent drawing
  • US20240331816A1 patent drawing

AI summary

Techniques for enabling a user, having little or no code-writing experience, to build and configure a user-customized software application configured to extract, process, and display information associated with user-selected health records or portions of health records is disclosed. The techniques may include operations such as receiving a selection of a first resource defined by a first EHR system, analyzing metadata associated with the first resource to identify a first set of characteristics corresponding to the first resource, identifying configuration fields associated with the first resource based on the first set of characteristics, presenting the configuration fields associated with the first resource, receiving configuration values for the configuration fields, and generating code for executing API calls to extract data associated with the first resource in accordance with the configuration values and for presenting the data associated with the first resource.