Medical Device Software Upgrade With Persistent Data Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current continuous glucose monitoring devices face challenges in software and firmware upgrades, leading to potential data loss and requiring manual setting adjustments when switching devices, which is time-consuming and inefficient.
Innovation Solution
A method and system for establishing a connection between a medical device and a remote computing device to store and convert persistent data and executable code formats, allowing for seamless upgrades and data preservation, enabling automatic transfer and execution of upgraded software and settings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software or firmware is upgraded in continuous glucose monitoring devices, then device functionality and performance are improved, but user data and settings may be lost
Solution Approach 1:
The system performs preliminary actions by backing up persistent data to a remote computing device before the upgrade process begins. This ensures that user data is preserved outside the medical device prior to any potential data loss during the upgrade.
Solution Approach 2:
A remote computing device serves as an intermediary between the medical device and the upgrade process. The persistent data is transferred to and stored on this intermediary device, protecting it from being lost during the upgrade while allowing the medical device to be updated.
2Productivity
If a patient switches from one continuous glucose monitoring device to another, then device availability is maintained, but manual setting adjustments are required
Solution Approach 1:
The system creates a copy of the persistent data (including all settings and configuration) from the old device and transfers it to the new device. This copying process eliminates the need for manual setting adjustments, saving time while maintaining device availability.
Solution Approach 2:
The persistent data is prepared and converted in advance on the remote computing device before the patient switches devices. This preliminary preparation ensures that when the patient switches to the new device, all settings are already configured and ready to use immediately.
3Adaptability or versatility
If persistent data is converted between different formats for upgraded executable code, then compatibility is improved, but data format complexity increases
Solution Approach 1:
The remote computing device acts as an intermediary that handles the complex format conversion process. It converts persistent data from the first format associated with the old executable code to the second format compatible with the upgraded executable code, managing the complexity externally rather than within the medical device itself.
Solution Approach 2:
The complex data format conversion operation is extracted from the medical device and performed on the remote computing device. This separates the conversion complexity from the medical device, allowing the device to remain simple while still achieving format compatibility through the external conversion process.
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.