Medical Device Pull Updates for Continuous Clinical Operation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing medical device update systems are inefficient and resource-intensive, requiring manual disassembly, staggered updates, and server overload, leading to lengthy deployment times and high labor costs.
Innovation Solution
A 'pull' update mechanism where medical devices download and install updates independently over a network or using a USB flash drive, allowing them to remain on the clinical floor and reducing server load, with verification and caching to ensure seamless integration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual update deployment is used, then update reliability is improved, but deployment time and labor cost increase significantly
Solution Approach 1:
The medical device automatically performs update operations including downloading update packages, verifying integrity through checksums, and installing updates without requiring manual intervention. The device autonomously manages the entire update lifecycle, eliminating the need for technicians to physically handle each device while maintaining reliable update deployment.
2Reliability
If server pushes updates to all devices, then update completeness is improved, but server resource consumption increases
Solution Approach 1:
Instead of the server actively pushing updates to all devices, the medical device initiates the update process by contacting the server to check for available updates and then downloading them autonomously. This inverted approach shifts the active role from server to device, reducing server resource consumption while ensuring all devices receive updates.
Solution Approach 2:
Each medical device independently manages its own update process by automatically checking the server for available updates, downloading relevant update packages, and installing them without requiring server-side initiation or management of individual update operations.
3Reliability
If devices are removed from clinical floor for updates, then update safety is improved, but operational continuity deteriorates
Solution Approach 1:
The medical device performs update operations continuously without interruption to its clinical function. The device maintains its therapeutic operation throughout the update process, downloading and installing updates in the background or during appropriate intervals without being removed from the clinical floor, thus ensuring both update safety and operational continuity.
Data Source
AI summary
A system and method for providing updates to medical devices is disclosed. In one example, the medical devices are configured to pull update files in response to the reception of an update message from a server. Once the update files are downloaded by a medical device, the update files can be installed. While the medical device pulls the update files, the medical device can continue with its normal operation. If desired, a user can select which medical devices should be updated, based on any desired factors, such as the physical location of the device, the model of the device, the type of device, and the way the device is being used.


