Medical Device Software Update With Persistent Data Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current continuous glucose monitoring devices face challenges in upgrading software or firmware, with potential data loss during failures or when switching devices, requiring manual adjustments of settings.
Innovation Solution
A method and system for updating medical devices, including establishing a connection between the device and a remote computing device, storing current data, converting and transmitting it for upgrading, and executing the new software and data formats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software or firmware is upgraded in continuous glucose monitoring devices, then device functionality and performance are improved, but data loss and system failure risks increase
Solution Approach 1:
The system performs preliminary actions by creating a backup of the current firmware image and persistent data to a remote computing device before initiating the upgrade process. This backup is stored separately from the device memory, ensuring that original data is preserved even if the upgrade fails or corrupts the device storage.
Solution Approach 2:
A remote computing device serves as an intermediary between the user and the medical device during the upgrade process. The intermediary handles firmware validation, manages the backup creation, and coordinates the upgrade execution, thereby isolating the medical device from direct user operations that could cause failures and protecting data integrity.
2Productivity
If a patient switches from one continuous glucose monitoring device to another, then device availability is maintained, but manual configuration time increases
Solution Approach 1:
The system creates a digital copy of the persistent data (including patient settings, preferences, and configuration information) from the old device and transfers it to the new device. This copying process automatically replicates all device settings, eliminating the need for manual reconfiguration and significantly reducing the time required when switching devices.
3Reliability
If firmware validation is performed before upgrade, then upgrade reliability is improved, but upgrade process time increases
Solution Approach 1:
The firmware validation process is performed as a preliminary action before the actual upgrade is executed. The system validates the firmware image integrity and compatibility checks are completed in advance, ensuring that only validated firmware proceeds to the upgrade stage. This prevents failed upgrades and reduces the need for rework, ultimately saving time despite the initial validation delay.
Data Source
AI summary
The present disclosure includes methods, devices and systems for establishing a connection between a medical device and a remote computing device, receiving an upgrade command at the medical device, storing a current version of persistent data and a current version of executable code in a first storage area of the medical device, transmitting at least the current version of the persistent data to the remote computing device, receiving a second format of the current version of the persistent data and an upgraded version of executable code at the medical device, storing the second format of the current version of the persistent data and the upgraded version of the executable code in a second storage area of the medical device, and executing the upgraded version of the executable code with the second format of the current version of the persistent data.