DICOM Metadata Backup and Recovery via Database Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating and restoring DICOM objects are inefficient and performance-intensive, particularly when managing large numbers of DICOM objects, as they involve manual updates and complex recovery processes that can lead to performance issues during network downtime.
Innovation Solution
A system and method for backing up and restoring metadata updates by entering changes into a database table, generating a backup file, creating a recovery table, and applying updates to corresponding files based on identifiers, allowing for seamless and efficient restoration of DICOM objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If updates are written to each image file individually in the patch area, then data integrity is maintained, but the updating process becomes long and arduous when managing hundreds or thousands of DICOM objects
Solution Approach 1:
The patent segments the updating process into two distinct phases: (1) bulk metadata updates applied to all DICOM objects simultaneously, and (2) selective patch area updates only for objects that actually changed. This segmentation allows the system to maintain data integrity through controlled update application while dramatically improving productivity by avoiding individual file updates for all objects.
Solution Approach 2:
The patent performs preliminary bulk metadata updates across all DICOM objects before applying patch area updates. By pre-applying metadata changes at the database level and then selectively updating only the necessary patch areas afterward, the system achieves both high productivity through batch processing and reliability through controlled application of changes.
2Reliability
If the traditional restoration process is used to recover lost or destroyed DICOM objects, then complete recovery is achieved, but the process generates new GUIDs and requires complex repopulation of database tables
Solution Approach 1:
The patent uses backup metadata stored in database tables as templates to recreate lost DICOM objects. Instead of generating entirely new objects with new GUIDs, the system copies existing metadata from backup tables and applies it to restored objects, preserving original identifiers and maintaining database consistency while simplifying the restoration process.
Solution Approach 2:
The patent introduces database metadata tables as an intermediary layer between the restoration process and the actual DICOM objects. This intermediary layer stores all necessary metadata information that can be quickly copied and applied during restoration, eliminating the need for complex GUID generation and database repopulation logic while ensuring complete and accurate recovery.
3Productivity
If metadata updates are stored in database tables and restored using backup files, then restoration speed is improved, but additional storage space is required for backup files
Solution Approach 1:
The patent extracts only the essential metadata information from complete DICOM objects and stores it in separate database tables. This extraction process creates compact backup representations that contain only the critical metadata needed for restoration, significantly reducing storage space requirements compared to storing complete backup copies of all DICOM objects while maintaining fast restoration capability.
Data Source
AI summary
A system and methods for backing up and restoring updates to metadata of files stored in a database are disclosed. One example embodiment of the method includes entering the updates to the metadata of the one or more files into a first database table; generating a backup file of the first database table; and restoring the updates to the metadata to the one or more files using the backup file. Restoring the updates may include creating a recovery table populated with data from the backup file; determining the one or more files to apply the updates to by searching the recovery table for an identifier of the one or more files; and adding the updates to the metadata from the recovery table to the corresponding one or more files that matches the identifier identified from the recovery table.