Encoded EHR Data Mapping for Direct File Manipulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data encoding methods require decoding and subsequent reencoding, which is computationally expensive and inefficient.
Innovation Solution
A system and method that processes encoded data without the need for decoding, using a dictionary file and mappings to manipulate encoded data files, allowing operations such as computation, search, append, split, join, and concatenate directly on encoded data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is encoded (compressed or encrypted) to save storage space or secure the data, then storage efficiency or security is improved, but any manipulation of the data requires decoding and subsequent reencoding which increases computational overhead and time
Solution Approach 1:
The patent introduces an intermediary layer consisting of mapping files and dictionary files that bridge the encoded data and the processing system. Instead of directly manipulating encoded data or fully decoding it, the system uses these intermediary files to enable operations on encoded data through indirect addressing and transformation, thereby maintaining security while reducing computational overhead
Solution Approach 2:
The patent segments the data processing workflow into distinct components: encoding/decoding operations are separated from manipulation operations. By creating separate mapping files that divide the encoded data into manageable segments with associated metadata, the system allows partial processing without requiring complete decoding, thus reducing computational complexity while maintaining security
2Quantity of substance
If data is encoded to transform from a larger form to a smaller form for saving storage space, then storage efficiency is improved, but accessing and manipulating the data requires expensive decoding and reencoding operations
Solution Approach 1:
The patent performs preliminary actions by pre-computing and storing mapping relationships between encoded data segments and their corresponding dictionary entries. This preprocessing creates a lookup structure that enables rapid access and manipulation without requiring real-time decoding, thus reducing data access time while maintaining compact storage
Solution Approach 2:
The patent substitutes the mechanical decoding process with a lookup-based system using mapping files. Instead of performing computationally intensive decoding operations to access or manipulate data, the system uses pre-computed mappings to directly reference encoded segments, replacing the mechanical decoding mechanism with a more efficient information retrieval approach
3Ease of operation
If the encoded data is decoded, manipulated, and then reencoded to achieve data manipulation tasks, then the manipulation operations can be performed, but the process is computationally expensive and inefficient
Solution Approach 1:
The patent extracts the essential manipulation capabilities from the decode-manipulate-encode cycle by separating the manipulation logic from the encoding/decoding process. Through mapping files that capture the structural relationships, the system extracts only the necessary transformation information, allowing operations to be performed on encoded data representations without requiring full decoding and reencoding
Solution Approach 2:
The patent creates a universal processing framework that handles multiple data manipulation operations (search, computation, append, split, join, concatenate) through a common mechanism using mapping files. This multi-functional approach eliminates the need for separate decode-manipulate-encode pipelines for each operation type, thereby improving processing efficiency while maintaining ease of operation across diverse manipulation tasks
Data Source
AI summary
A computer-implemented method, computer program product and computing system for: processing an unencoded data file to identify a plurality of file segments, wherein the unencoded data file is a dataset for use with an EHR process; mapping each of the plurality of file segments to a portion of a dictionary file to generate a plurality of mappings that each include a starting location and a length, thus generating a related encoded data file based, at least in part, upon the plurality of mappings; receiving a request to manipulate the unencoded data file from the EHR process; and processing the related encoded data file based, at least in part, upon the plurality of mappings and the dictionary file to generate a modified encoded data file that represents the requested manipulations of the unencoded data file.