Operational Intelligence Platform for Dynamic EHR Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Healthcare information systems using MUMPS-based hierarchical data models face challenges in data accessibility and flexibility, leading to labor shortages, increased costs, and reduced innovation due to their inflexibility and incompatibility with modern database technologies.
Innovation Solution
The Operational Intelligence Platform dynamically extracts electronic health records from MUMPS-based systems, translating them into a relational format that preserves the hierarchical structure, enabling real-time relational access and facilitating modern development tools and technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If MUMPS-based hierarchical data model is used to store electronic health records, then data can be stored in a simple key-value format, but data accessibility and flexibility are reduced
Solution Approach 1:
The patent introduces an intermediary layer (data extraction and translation system) between the MUMPS hierarchical database and the relational database. This intermediary extracts data from MUMPS, transforms it into relational format, and loads it into a relational database, allowing modern applications to access data flexibly without changing the legacy MUMPS system.
Solution Approach 2:
The patent creates a copy of the MUMPS data in relational format. Instead of modifying the original MUMPS system or requiring applications to speak MUMPS, the system copies data into a relational database that can be accessed using modern SQL-based tools and languages.
2Stability of the object's composition
If MUMPS-based hierarchical data model is used, then existing health records can be maintained, but compatibility with modern database technologies is lost
Solution Approach 1:
The patent adds a new dimension to the data architecture by creating a parallel relational database layer. The original hierarchical MUMPS data structure is preserved in its own dimension, while a new relational dimension is added that provides modern access patterns without interfering with the original structure.
3Adaptability or versatility
If ETL process is used to convert MUMPS data to relational format, then data can be accessed using modern tools, but access is delayed by 24 hours or more
Solution Approach 1:
The patent performs preliminary actions by continuously maintaining the relational database with up-to-date data through ongoing ETL processes. Rather than waiting 24 hours for batch processing, the system proactively extracts and loads data in near-real-time, so when applications need data, it is already available in relational format.
Solution Approach 2:
The patent implements continuous data extraction and loading operations rather than single batch operations. The ETL process runs continuously or at frequent intervals, ensuring the relational database is continuously updated with the latest MUMPS data, eliminating the 24-hour delay.
4Stability of the object's composition
If MUMPS-based systems are used, then legacy health records can be preserved, but development costs increase due to labor shortages
Solution Approach 1:
The patent introduces an intermediary translation layer that allows modern developers to work with relational databases using standard SQL and modern tools, while the legacy MUMPS system continues to operate unchanged. This intermediary eliminates the need for developers to learn MUMPS, addressing the labor shortage issue.
Solution Approach 2:
The patent makes the data system universal by providing dual access: the original MUMPS system maintains its functionality while the new relational layer provides universal access compatible with modern development tools, programming languages, and frameworks that any developer can use.
Data Source
AI summary
Techniques for dynamically extracting electronic health records are described. Some embodiments provide an Operational Intelligence Platform (“OIP”) that is configured to dynamically extract electronic health record data from a source customer database that represents health records in a hierarchical format, and store the extracted data in a clinical data engine that represents the health records in a manner that logically preserves the hierarchical format while providing a relational access model to the health records. The OIP may extract health-record data in substantially real-time by performing on-the-fly capture and processing of data updates to the source customer database. Such real-time extraction may be performed in cooperation with large scale, batch extraction of records from the source customer database.


