Unified Database for Multi-System Data Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face inefficiencies in accessing and analyzing data stored across multiple systems, such as hemodynamic and cardio reporting systems, as they need to generate separate queries for each system, which is time-consuming and difficult to consolidate insights from disparate results.
Innovation Solution
A system and method for generating a combined database by extracting data changes from multiple systems, including a hemodynamic system and a cardio reporting system, using an electronic processor to determine and insert data changes, process markup language documents, and execute queries across the combined database, allowing for unified query execution and result output.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If separate queries are generated for each system to access data, then data can be retrieved from individual systems, but time and effort are consumed and it is difficult to consolidate insights from disparate results
Solution Approach 1:
The patent combines multiple separate database systems (hemodynamic system, cardio reporting system, etc.) into a single unified database that stores data from all source systems. This allows users to query all data through a single interface rather than generating separate queries for each system, directly reducing time loss and query complexity.
Solution Approach 2:
The patent introduces an intermediary component that extracts data from multiple source systems, transforms it into a standardized format, and loads it into a unified database. This intermediary layer handles the complexity of data integration, shielding users from the underlying system complexity while enabling efficient single-query access to all data.
2Adaptability or versatility
If data is stored in multiple separate systems, then each system can maintain its own data structure and processing logic, but users cannot easily gain insight from combined results across systems
Solution Approach 1:
The patent merges data from multiple specialized systems into a unified database while preserving the original data structures through separate tables or schemas. This allows the system to maintain adaptability to each source system's data format while enabling cross-system analysis and insight generation through unified queries.
Solution Approach 2:
The unified database is segmented into separate tables or schemas corresponding to each source system (hemodynamic data, cardio reporting data, etc.). Each segment maintains its original structure and characteristics, allowing the system to adapt to different data types while enabling integrated analysis across all segments through single queries.
3Ease of operation
If a unified database is created to combine data from multiple systems, then users can query all data through a single interface, but the complexity of extracting and integrating data from different systems increases
Solution Approach 1:
The patent introduces an intermediary data extraction and integration layer that handles the complexity of accessing multiple source systems, transforming their data into a standardized format, and loading it into the unified database. This intermediary component shields users from the underlying extraction and integration complexity while providing easy single-interface query access to all combined data.
Solution Approach 2:
The patent performs preliminary data extraction, transformation, and loading operations to populate the unified database before users need to query it. By pre-processing and integrating data from multiple systems in advance, the system eliminates the need for users to perform complex extraction and integration operations when querying, significantly improving ease of operation.
Data Source
AI summary
A non-transitory computer readable medium storing instructions that, when executed by an electronic processor, perform a set of functions. The set of functions include extracting a report including a markup language document from a system. The set of functions also includes, for each of a plurality of processing tasks, determining whether the markup language document includes a path contained in a virtual table assigned to the processing task. The set of functions also includes, in response to the markup language document including the path contained in the virtual table, extracting data from the markup language document and executing the processing task to manipulate and queue the data for insertion into the combined database. The set of functions further includes, in response to each of the plurality of processing tasks completing without failure, inserting the data queued into one or more tables included in a database.