Medical Device Firmware Upgrade With Remote Data Format Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current continuous glucose monitoring devices face challenges in upgrading software or firmware, 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 updating medical devices by establishing a connection with a remote computing device to store and convert data formats, allowing seamless upgrades and data transfers between devices while ensuring integrity and compatibility.
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 settings and analyte related data may be lost
Solution Approach 1:
The system performs preliminary actions by automatically backing up user settings and analyte related data to a remote computing device before the software or firmware upgrade process begins. This ensures that if the upgrade fails or causes data loss, the original data can be restored from the backup.
Solution Approach 2:
A remote computing device serves as an intermediary between the continuous glucose monitoring device and the upgrade software. This intermediary handles the data backup, storage, and restoration processes, isolating the medical device from direct exposure to potential upgrade failures while ensuring data preservation.
2Productivity
If a patient switches from one continuous glucose monitoring device to another, then device availability is maintained, but manual configuration of settings is required which is time-consuming
Solution Approach 1:
The system creates a digital copy of user settings and device configuration data from the original continuous glucose monitoring device and stores it on a remote computing device. When switching to a new device, this copied data is automatically transferred and applied, eliminating the need for manual reconfiguration.
Solution Approach 2:
The system performs preliminary data transfer and configuration setup before the patient actually switches devices. By preparing the new device with the necessary settings in advance, the transition between devices becomes seamless and requires minimal user intervention.
3Adaptability or versatility
If data is transferred between devices with different software versions, then device compatibility is improved, but data format conversion complexity increases
Solution Approach 1:
The remote computing device acts as an intermediary that handles all data format conversion processes. It receives data from the first device format, converts it to the second device format, and transfers it to the new device. This isolates the complexity of format conversion from the medical devices themselves.
Solution Approach 2:
The system automatically performs data format conversion without requiring manual intervention from the user or complex configuration on the devices. The remote computing device self-manages the entire conversion process based on the identified device types and their respective data formats.
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.