Drug Library Snapshot Versioning to Reduce Storage Footprint
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing drug library editor applications face challenges in efficiently managing large storage footprints and processing capacity due to the need to store multiple versions of drug library entries, infusion parameters, and other records, which can exceed available resources.
Innovation Solution
A method for managing drug library entries involves generating snapshot records with version identification values, updating these values to track changes, and storing these records with medical devices, allowing efficient storage and access to different versions without duplicating entire libraries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple complete copies of drug library versions are stored to support change logs and resolve configurations, then version tracking and reliability are improved, but storage footprint and device complexity increase beyond available capacity
Solution Approach 1:
The patent segments the drug library into individual change records, each representing a single modification event. Instead of storing complete library copies, the system stores discrete change records that can be applied sequentially to reconstruct any version. This segmentation reduces storage requirements while maintaining full version tracking capability.
Solution Approach 2:
The patent uses selective copying by storing only the differential change records rather than complete copies. Each change record captures the essence of a modification (addition, deletion, or update) without duplicating the entire library structure. This allows efficient storage and reconstruction of any library version on demand.
2Ease of operation
If complete drug library versions are stored to enable access to historical configurations, then version accessibility is improved, but processing capacity and storage resources are exceeded
Solution Approach 1:
The patent implements a dynamic version retrieval mechanism where the system can reconstruct any library version by applying the appropriate sequence of change records to a base version. This dynamic approach allows flexible access to any historical version without storing complete static copies, reducing processing and storage requirements.
Solution Approach 2:
The patent performs preliminary action by pre-processing and storing changes in a standardized, normalized format that captures only the essential modification information. This preliminary structuring of change data enables efficient later retrieval and application of specific versions without requiring complex processing of complete library copies.
Data Source
AI summary
The disclosed systems and methods provide an efficient solution to manage the entries of versioned libraries. A method includes receiving a request to modify an entry corresponding to a numerically-versioned library or a related master. The method includes obtaining a first snapshot record for the entry corresponding to the library or the master. The method includes receiving user changes to data of the entry. The method also includes generating a second snapshot record for the entry. The second snapshot record capturing the user changes and having an assigned second plurality of version identification values. The method further includes updating the first plurality of version identification values of the first snapshot record based on assigned values of the second plurality of version identification values of the second snapshot record. The first and second plurality of version identification values indicating that the first snapshot record precedes the second snapshot record.