Remote flashing during infusion

• US 9,871,866 B2
• Filed: 07/18/2016
• Issued: 01/16/2018
• Est. Priority Date: 01/13/2014
• Status: Active Grant

• Current Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Original Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Inventors: Borges, Gregory, Halbert, Donald, Gaetano, Jeffrey L.
• Primary Examiner(s): Wu, Daxin
• Application Number:
  US15/213,325
• Publication Number:
  US 20160381142A1
• Time in Patent Office: 547 Days
• Field of Search: None
• CPC Class Codes: A61B 2560/045 with a separable interface unit, e.g. for communication
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/02 Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
• CPC Class Codes: A61B 5/082 Evaluation by breath analysis, e.g. determination of the chemical composition of exhaled breath A61B5/083, A61B5/091 take precedence
• CPC Class Codes: A61B 5/145 Measuring characteristics of blood in vivo, e.g. gas concentration, pH value; Measuring characteristics of body fluids or tissues, e.g. interstitial fluid, cerebral tissuemeasuring of blood pressure or blood flow A61B5/02; non-radiation detecting or locating of foreign bodies in blood A61B5/06
• CPC Class Codes: A61B 5/14552 Details of sensors specially adapted therefor
• CPC Class Codes: A61M 2005/1405 Patient controlled analgesia [PCA]
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 2205/3569 sublocal, e.g. between console and disposable
• CPC Class Codes: A61M 2205/3584 using modem, internet or bluetooth
• CPC Class Codes: A61M 2205/3592 using telemetric means, e.g. radio or optical transmission
• CPC Class Codes: A61M 2205/50 with microprocessors or computers
• CPC Class Codes: A61M 2205/502 User interfaces, e.g. screens or keyboards
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 2205/6054 Magnetic identification systems
• CPC Class Codes: A61M 2205/6072 Bar codes
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/14216 Reciprocating piston type
• CPC Class Codes: A61M 5/14228 with linear peristaltic action, i.e. comprising at least three pressurising members or a helical member
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G16H 10/00 : ICT specially adapted for the handling or processing of patient-related medical or healthcare data for medical reports G16H15/00; for therapies or health-improving plans G16H20/00; for the handling or processing of medical images G16H30/00
• 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: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 : specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring

Abstract

A medical device controller operating in conjunction with a medical device determines one or more current versions of executable code associated with one or more processors in a medical device. Medical devices may include infusion pumps, other patient treatment devices as well as vital signs monitors. The medical device controller determines one or more current versions of executable code and configuration information associated with the one or more processors in the medical device. The medical device controller further determines which of the processors in the medical device require updated executable code, and which of the processors in the medical device require updated configuration information. The medical device controller distributes to the medical device as required at least one of the updated executable code and the updated configuration information. The medical device deploys the distributed updates, and activates the updates at a clinically appropriate time.

Claims

1. A method comprising:

determining, at a medical device controller, one or more current versions of executable code associated with one or more processors in a medical device, wherein the medical device controller operates in conjunction with the medical device;

determining, at the medical device controller, one or more current versions of configuration information associated with the one or more processors in the medical device, the configuration information including patient treatment information;

determining, at the medical device controller, which of the one or more processors in the medical device require updated executable code, and which of the one or more processors in the medical device require updated configuration information associated with the updated executable code; and

distributing, from the medical device controller to the medical device, at least one of the updated executable code and the updated configuration information as required by the one or more processors in the medical device;

activating at least one of the updated executable code and the updated configuration information at the medical device at a clinically appropriate time based on the patient treatment information.

2. The method as in claim 1, wherein the executable code comprises at least one of an operating system and an application.

3. The method as in claim 1, wherein the configuration information comprises values that can be modified by a user, wherein the values affect the functioning of the medical device.

4. The method as in claim 1, wherein at least one communications interface wirelessly couples the medical device controller to the medical device.

5. The method as in claim 1, wherein at least one of the medical device comprises a fluid infusion pump.

6. The method as in claim 5, wherein the fluid infusion pump is at least one of:

a syringe pump, a patient controlled infusion pump, a large volume infusion pump, and a peristaltic pump.

7. The method as in claim 1, wherein the medical device comprises at least one of:

a patient-controlled analgesia (PCA) system, a vital signs monitor, a blood analyte monitor, a cardiac output monitors, a gastric tonometers, an SpO2 sensor, an EtCO2 sensor, an identification module, a barcode scanner, and a radio frequency identification (RFID) scanner.

8. The method as in claim 4, wherein the at least one communications interface is a wired or wireless network connection.

9. A method comprising:

receiving, at a medical device from a medical device controller, at least one update comprising one or more of updated executable code and updated configuration information associated with the updated executable code for one or more processors in the medical device;

deploying, at the medical device, the received at least one update by determining the appropriate processor in the medical device associated with the at least one update and transferring the at least one update to an appropriate storage associated with the appropriate processor; and

activating, at the medical device and at a clinically appropriate time, the deployed update by selecting to use the at least one update at the appropriate processor during operation of the medical device.

10. The method as in claim 9, wherein the executable code comprises at least one of an operating system and an application.

11. The method as in claim 9, wherein the configuration information comprises values that can be modified by a user, wherein the values affect the functioning of the medical device.

12. The method as in claim 9, wherein at least one communications interface wirelessly couples the medical device controller to the medical device.

13. The method as in claim 9, wherein the medical device comprises a fluid infusion pump.

14. The method as in claim 13, wherein the fluid infusion pump is one of:

a syringe pump, a patient controlled infusion pump, a large volume infusion pump, and a peristaltic pumps.

15. The method as in claim 9, wherein the medical device comprises one of a patient-controlled analgesia (PCA) system, a vital signs monitor, a blood analyte monitor, a cardiac output monitors, a gastric tonometers, an SpO2 sensor, an EtCO2 sensor, an identification module, a barcode scanner, and a radio frequency identification (RFID) scanner.

16. The method as in claim 12, wherein the at least one communications interface is a wired or wireless network connection.