Security features for a medical infusion pump
US-9192712-B2 · Nov 24, 2015 · US
US11626205B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11626205-B2 |
| Application number | US-201715435230-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 16, 2017 |
| Priority date | Oct 21, 2011 |
| Publication date | Apr 11, 2023 |
| Grant date | Apr 11, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A system for updating software including a drug library of an infusion pump system, the system comprising: a first memory location configured to store a first drug library; a network communication interface configured to communicate with a server; a communication subsystem configured to facilitate communications between the infusion pump system and the server, wherein the communication subsystem comprises a communication subsystem memory; a display configured to display a plurality of user interfaces; and a controller configured to: receive an update message from the server, said update message including a location of update data on the server; request, from the server, update data including a second drug library using a network operating system level interface after receipt of the update message, wherein the infusion pump system instead of the server is responsible for requesting the update data; receive, from the server, the requested update data including the second drug library; store the received update data including the second drug library locally in the communication subsystem memory; process a first command from a user to turn off the infusion pump system; generate a first user interface in response to the first command, the first user interface comprising a first input corresponding to installation of the second drug library received from the server; determine that the first input indicates that a user has selected to proceed with the installation of the second drug library; and in response to the determination that the first input indicates that the user has selected to proceed with the installation of the second drug library: access the second drug library from the communication subsystem memory; install the second drug library in a second memory location based on the determination of the first input, the second memory location different than the first memory location, thereby maintaining both the first drug library and the second drug library; determine that the second drug library was successfully installed; set the second drug library as a current drug library based on the determination of successful installation of the second drug library; and erase the first drug library from the first memory location. 2. The system of claim 1 , wherein the controller is further configured to store a backup of a current software configuration prior to installation of a software update received from the server. 3. The system of claim 1 , wherein the controller is further configured to use the first drug library as the current drug library based on a determination that the second drug library was not successfully installed. 4. The system of claim 1 , wherein the controller is further configured to: install a software update before the installation of the second drug library, and disable the infusion pump system after a determination that the second drug library was not successfully installed and that the first drug library is a default drug library. 5. The system of claim 1 , wherein the controller is further configured to: install a software update before the installation of the second drug library, wherein the second drug library is installed only after successful installation of the software update. 6. The system of claim 1 , wherein the controller is further configured to determine power connection status of the infusion pump system and generate a second user interface including a notification for a user to connect the infusion pump system to an AC power source based on the determined power connection status indicating that the infusion pump system is not connected to the AC power source. 7. An electronic method for updating software including a drug library of an infusion pump system, the electronic method comprising: using a first drug library stored in a first memory location as a current drug library; receiving an update message from a server, said update message including a location of update data on the server; requesting, from the server, update data including a second drug library using a network operating system level interface after receipt of the update message, wherein the infusion pump system instead of the server is responsible for requesting the update data; receiving, from the server, the requested update data including the second drug library; storing the received update data including the second drug library locally in a communication subsystem memory, said communication subsystem memory included in a communication subsystem configured to facilitate communications between the infusion pump system and the server; processing a first command from a user to turn off the infusion pump system; generating a first user interface in response to the first command, the first user interface comprising a first input corresponding to installation of the second drug library received from the server; determining that the first input indicates that a user has selected to proceed with the installation of the second drug library; and in response to the determination that the first input indicates that the user has selected to proceed with the installation of the second drug library: installing the second drug library in a second memory location based on the determination of the first input, the second memory location different than the first memory location, thereby maintaining both the first drug library and the second drug library; determining that the second drug library was successfully installed; and setting the second drug library as the current drug library based on the determination of successful installation of the second drug library. 8. The electronic method of claim 7 , further comprising erasing the first drug library from the first memory location after the successful installation of the second drug library. 9. The electronic method of claim 7 , further comprising storing a backup of a current software configuration prior to installation of a software update received from the server. 10. The electronic method of claim 7 , further comprising using the first drug library as the current drug library based on a determination that the second drug library was not successfully installed. 11. The electronic method of claim 7 , further comprising installing a software update before the installation of the second drug library, and disabling the infusion pump system after a determination that the second drug library was not successfully installed and that the first drug library is a default drug library. 12. The electronic method of claim 7 , further comprising installing a software update before the installation of the second drug library, wherein the second drug library is installed only after successful installation of the software update.
relating to drugs, e.g. their side effects or intended usage · CPC title
for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades · CPC title
delivered via infusion or injection · CPC title
local, e.g. within room or hospital · CPC title
Pressure infusion, e.g. using pumps · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.