Medical Device Firmware Upgrade With Persistent Data Conversion
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 setting adjustments which is time-consuming.
Innovation Solution
Establishing a connection between the medical device and a remote computing device to store and convert data formats, allowing for seamless software and firmware upgrades, data preservation, and automatic setting transfers between devices.
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 during the upgrade process
Solution Approach 1:
The system performs preliminary actions by creating a backup of the current firmware image and storing it in a second storage area before initiating the upgrade process. This backup is made in advance to ensure that if the upgrade fails, the original firmware can be restored, thus preventing data loss and maintaining reliability during the upgrade process.
Solution Approach 2:
The system implements beforehand cushioning by verifying the integrity of the upgraded firmware image through checksum validation before actually executing it. Additionally, the backup firmware serves as a cushion against upgrade failures. These preventive measures are put in place before the upgrade is finalized to protect against potential failures and data loss.
2Productivity
If a patient switches from one continuous glucose monitoring device to another, then device availability is maintained, but manual setting transfer becomes time-consuming
Solution Approach 1:
The system uses copying by transferring user settings, calibration data, and historical glucose data from the first device to the second device through a communication interface. The settings are copied automatically during the device pairing process, eliminating the need for manual re-entry and significantly reducing the time required for device switching while maintaining productivity.
3Reliability
If firmware verification is performed before execution, then system reliability is improved, but upgrade process complexity increases
Solution Approach 1:
The system implements self-service by automatically performing checksum verification of the firmware image and comparing it against the expected checksum value stored in the upgrade data. The microcontroller autonomously determines whether the firmware is valid without requiring manual intervention. This automated verification process maintains reliability while minimizing the perceived complexity for the user.
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.