Granted Patent B2

US 12,380,997 · App. 18/651,439 · Granted Aug 5, 2025

Inventors: John Arrizza (Oceanside, CA); James R. Shults (Ramona, CA); Thomas J. Vaccaro (Encinitas, CA); Patrick A. Ward (San Diego, CA)

Assignee: ICU Medical, Inc.

G16H40/40A61M5/142G06F8/65G16H20/17G16H70/40A61M5/14212A61M2205/3561G06F8/61

Abstract

Claims (34)

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

receiving an update message at a medication administering device, wherein the update message includes information relating to one or more update files available to the medication administering device;

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

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; and

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 said prompting the user of the medication administering device to update the medication administering device comprises 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: a physical location of a device, a model of a device, a type of device, and a way a 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 the 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. A medical device system comprising:

a plurality of medical devices in communication with a server over a communication network, the plurality of medical devices each having a first storage location and a second storage location, and a controller for controlling an operation of the medical device, wherein the controller is configured to:

receive an update message from the server, wherein the update message includes information relating to one or more update files available to a medical device of the plurality of medical devices;

download one or more update files identified by the update message while the medical device is in operation;

store the one or more update files on the medical device in a first memory location for installation at a future time;

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

prompt a user of the medical device to update the medical device; and

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

wherein the update files include one or more of updated device software and an updated drug library, and said prompting the user of the medical device to update the medical device comprises 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.

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

13. The medical device system of claim 12 , wherein medical devices are selected based on one or more of: a physical location of a device, a model of a device, a type of device, and a way that a device is being used.

14. The medical device system of claim 11 , 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.

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

16. The medical device system of claim 11 , wherein the controller is configured to provide status messages to the server, the status messages relating to downloading and installing update files.

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

Assignments (1)

Continuity (5)

References Cited (400)