Medical device update system

• US 9,594,875 B2
• Filed: 10/19/2012
• Issued: 03/14/2017
• Est. Priority Date: 10/21/2011
• Status: Active Grant

• Current Assignee: ICU Medical Incorporated
• Original Assignee: Hospira Incorporated (Pfizer Inc.)
• Inventors: Arrizza, John, Shults, James R., Vaccaro, Thomas J., Ward, Patrick A.
• Primary Examiner(s): St Leger, Geoffrey
• Application Number:
  US13/655,690
• Publication Number:
  US 20130104120A1
• Time in Patent Office: 1,607 Days
• US Class Current: 1/1
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/14212 Pumping with an aspiration and an expulsion action
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 70/40 relating to drugs, e.g. their side effects or intended usage

Abstract

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.

Claims

1. A method of providing updates to a medication administering device, the method comprising:

a server sending an update message to the medication administering device relating to one or more update files available to the medication administering device, the update message containing a manifest, the manifest including the location of the update files available to the medication administering device, update file version information, and update file integrity verification information;

receiving the update message at the medication administering device;

while the medication administering device is being used to administer medication, downloading one or more update files identified by the update message;

using the update file integrity verification information to verify that the one or more update files were successfully downloaded;

storing the one or more update files on the medication administering device in a first memory location for installation at a future time;

storing a currently used device software file and a currently used drug library file of the medication administering device in a second memory location on the medication administering device for recovery purposes;

prompting a user of the medication administering device to update the medication administering device;

upon the user accepting the update prompt, installing the one or more update files on the medication administering device;

wherein the update files include one or more of updated device software and an updated drug library, and the step of prompting the user of the medication administering device to update the medication administering device includes the sub-steps of

     1) prompting the user to install the updated device software, and then

     2) prompting the user to install the updated drug library only upon successful installation of the updated device software.

2. The method of claim 1, wherein updates are provided to a plurality of medication administering devices, the method further comprising:

selecting one or more medication administering devices to be updated; and

receiving an update message at the selected medication administering devices.

3. The method of claim 2, wherein the one or more medication administering devices are selected based on one or more of:

the physical location of a device, the model of the device, the type of device, and the way the device is being used.

4. The method of claim 1, wherein the downloaded update files are stored in a storage location of the medication administering device, and wherein the first memory location or second memory location also stores one or more previous versions of the update files to be updated.

5. The method of claim 1, wherein the update files include a script used for orchestrating an update process.

6. The method of claim 1, wherein the update message is sent and the update files are retrieved using a communications network.

7. The method of claim 1, wherein the update message is sent and update files are retrieved by the medication administering device using one or more portable storage devices.

8. The method of claim 1, further comprising providing status messages to a server, the status messages relating to downloading and installing of updates.

9. The method of claim 1, wherein the update message received at the medication administering device is a message unique to that device.

10. The method of claim 1, wherein the medication administering device includes at least one infusion pump.

11. The method of claim 1, comprising the medication administering device determining whether the medication administering device is connected to AC power, prompting the user to connect the medication administering device to a source of AC power, and then continuing with installing the one or more update files once the medication administering device is connected to a source of AC power.

12. The method of claim 1, comprising attempting installation of an update file multiple times before declaring an installation activity unsuccessful.

13. The method of claim 12, comprising prompting the user to send the medication administering device to a biomedical engineer upon three consecutive failed attempts of installing the updated device software.

14. A medical device system comprising:

a server;

a communication network; and

a plurality of medical devices in communication with the server over the communication network, the plurality of medical devices each having a first storage location and a second storage location, and a control unit for controlling the operation of the medical device, wherein the control units are configured to;

receive an update message from the server, the update message containing a manifest, the manifest including the location of update files available to the medical device, update file version information, and update file integrity verification information;

while the medical device is being used to administer medication, pull the update files in response to the update message received from the server;

using the update file integrity verification information to verify that the update files were successfully downloaded;

store the update files in the first storage location on the medical device for installation at a future time; and

store a currently used device software file and a currently used drug library file of the medical device in a second storage location on the medical device for recovery purposes;

prompt users of respective medical devices to update the respective medical device, wherein the control units are configured to manage the installation of downloaded update files upon acceptance of the update prompt by the user, and wherein the update files include one or more of updated device software and an updated drug library, and the step of prompting the user of the medical device to update the medical device includes the sub-steps of

     1) prompting the user to install the updated device software, and then

     2) prompting the user to install the updated drug library only upon successful installation of the updated device software.

15. The medical device system of claim 14, wherein the medical device system is configured such that a user can select one or more of the medical devices to be updated.

16. The medical device system of claim 15, wherein medical devices are selected based on one or more of:

the physical location of a device, the model of the device, the type of device, and the way the device is being used.

17. The medical device system of claim 14, wherein each respective first storage location stores downloaded update files and each respective second storage location is adapted to store one or more previous versions of files to be updated.

18. The medical device system of claim 14, wherein each respective update file of the update files includes a script used for orchestrating an update process.

19. The medical device system of claim 14, wherein the control units are configured to provide status messages to the server, the status messages relating to downloading and installing update files.

20. The medical device system of claim 14, wherein the plurality of medical devices includes at least one infusion pump.