Medical Device Update Workflow for Preserving User Settings
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 persistent data and executable code formats, allowing for seamless upgrades and data transfer between devices while maintaining user 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 settings and analyte related data may be lost
Solution Approach 1:
The system performs a preliminary backup of user settings and analyte related data to a remote computing device before initiating the software or firmware upgrade process. 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 medical device and the upgrade source. It receives and stores backup data, facilitates the upgrade process, and can restore data if needed, acting as a mediator that protects against data loss during upgrades.
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 copies user settings and analyte related data from the old device to the new device through a remote computing device. This digital copying process replaces manual configuration, significantly reducing the time required to set up the new device while maintaining full functionality.
Solution Approach 2:
The remote computing device provides a universal interface that can transfer data between different device models and versions. It handles format conversion and compatibility issues, making the data transfer process universally applicable across different device types without requiring manual reconfiguration.
3Adaptability or versatility
If executable code format is changed during upgrade, then compatibility with new software version is achieved, but data format conversion is required which increases complexity
Solution Approach 1:
The remote computing device acts as an intermediary that handles the complex data format conversion process. It receives data in the old format, converts it to the new format required by the upgraded executable code, and transfers it to the medical device. This isolates the complexity from the medical device itself.
Solution Approach 2:
The data format conversion functionality is extracted from the medical device and implemented in the remote computing device. This separation allows the medical device to focus on its core medical functions while the complex format conversion is handled externally by the remote system.
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.