Semi-autonomous hot-swap infusion module

Patent metadata

Field	Value
Publication number	US-11738141-B2
Application number	US-202217579473-A
Country	US
Kind code	B2
Filing date	Jan 19, 2022
Priority date	Apr 26, 2018
Publication date	Aug 29, 2023
Grant date	Aug 29, 2023

Abstract

A method that includes receiving, in a medication delivery module, a command to start a medication delivery from a first control module coupled to the medication delivery module, is provided. The command to start the medication delivery is based on clinical information received at the first control module. The method includes recording, in a memory of the medication delivery module, an update of the medication delivery, receiving an indication that the medication delivery module was decoupled from the first control module, and receiving an indication that the medication delivery module has become coupled with a second control module. The method also includes communicating, in response, with the second control module, to update the clinical information. A system and a non-transitory, computer readable medium storing instructions to perform the above method are also provided.

First claim

What is claimed is:

1. A medical device control module, comprising:
a non-transitory memory storing instructions; and
one or more processors coupled with the memory and configured to execute the instructions to cause the medical device control module to:
receive an indication that a medication delivery module became physically coupled, via a connector, to the medical device control module configured to provide power to the medication delivery module when the medication delivery module is physically coupled to the medical device control module;
receive, when and based on the medication delivery module becoming physically coupled to the medical device control module, clinical information pertaining to a medication delivery facilitated by the medication delivery module and received by the medication delivery module when the medication delivery module was physically coupled to a different control module before the medication delivery module became physically coupled to the medical device control module, and delivery data obtained by the medication delivery module after the medication delivery module was physically decoupled from the different control module and before the medication delivery module became physically coupled to the medical device control module; and
facilitate operation of the medication delivery module to continue the medication delivery based on the clinical information and the delivery data.

2. The medical device control module of claim 1 , wherein the one or more processors further cause the medical device control module to:
receive the clinical information and the delivery data from a server, wherein the delivery data comprises progress information pertaining to a medication of the medication delivery, the medication being administered by the medication delivery module.

3. The medical device control module of claim 2 , wherein the one or more processors further cause the medical device control module to:
update the delivery data to include a delivery progress of the medication while the medication delivery module is coupled to the medical device control module; and
provide the updated delivery data to the server.

4. The medical device control module of claim 2 , wherein the medical device control module is configured by the server to operate the medication delivery module based on the clinical information and the delivery data.

5. The medical device control module of claim 1 , wherein the one or more processors further cause the medical device control module to:
cause, by the medical device control module, the medication delivery module to continue the medication delivery based on the clinical information and the delivery data.

6. The medical device control module of claim 5 , wherein the one or more processors further cause the medical device control module to, before causing the medication delivery module to continue the medication delivery:
display an indication of the medication delivery and at least a portion of the clinical information in a display device associated with the medical device control module; and
request confirmation from a user to continue with the medication delivery using the medication delivery module.

7. The medical device control module of claim 1 , wherein the one or more processors further cause the medical device control module to:
validate, responsive to indication that a medication delivery module became physically coupled to the medical device control module, the clinical information; and
send, by the medical device control module, a command to the medication delivery module to continue the medication delivery responsive to validating the clinical information.

8. The medical device control module of claim 7 , wherein the one or more processors further cause the medical device control module to:
validate the clinical information with a server, wherein the validating comprises:
verify a patient ID, a drug to be delivered, a dosage, for a delivery rate for the medication delivery with data stored in a medication history log stored at the server or in a database associated with the server.

9. A system, comprising:
a memory storing instructions; and
one or more processors coupled with the memory and configured to execute the instructions to cause the system to:
receive an indication that a medication delivery module became physically coupled, via a connector, to a first control module configured to provide power to the medication delivery module when the medication delivery module is physically coupled to the first control module;
receive, when and based on the medication delivery module becoming physically coupled to the first control module, clinical information pertaining to a medication delivery facilitated by the medication delivery module and received by the medication delivery module when the medication delivery module was physically coupled to a second control module before the medication delivery module became physically coupled to the first control module, and delivery data obtained by the medication delivery module after the medication delivery module was physically decoupled from the second control module and before the medication delivery module became physically coupled to the first control module; and
facilitate operation of the medication delivery module by the first control module, to continue the medication delivery, based on the clinical information and the delivery data.

10. The system of claim 9 , wherein the system is further caused to:
receive the clinical information and the delivery data from a server, wherein the delivery data comprises progress information pertaining to a medication of the medication delivery, the medication being administered by the medication delivery module;
update the delivery data to include a delivery progress of the medication while the medication delivery module is coupled to the first control module; and
provide the updated delivery data to the server.

11. The medical device control module of claim 10 , wherein the one or more processors further cause the medical device control module to:
update the delivery data to include a delivery progress of the medication while the medication delivery module is coupled to the medical device control module; and
provide the updated delivery data to the server.

12. The medical device control module of claim 10 , wherein the medical device control module is configured by the server to operate the medication delivery module based on the clinical information and the delivery data.

13. The medical device control module of claim 9 , wherein the one or more processors further cause the medical device control module to:
cause, by the medical device control module, the medication delivery module to continue the medication delivery based on the clinical information and the delivery data.

14. The medical device control module of claim 13 , wherein the one or more processors further cause the medical device control module to, before causing the medication delivery module to continue the medication delivery:
display an indication of the medication delivery and at least a portion of the clinical information in a display device associated with the medical device control module; and
request confirmation from a user to continue with the medication delivery using the medication delivery module.

15. The medical device control module of claim 9 , wherein the one or more processors further cause the medical device control module to:
validate, responsive to indication that a medication delivery module became physically coupled to the medical device control module, the c

Assignees

• Carefusion 303 Inc

Inventors

• Gaetano Jeffrey L
• Borges Gregory
• Rozell Eugene A
• Bloom Mark P
• Salem Mooneer T

Classifications

• A61M5/16831 Primary

  Monitoring, detecting, signalling or eliminating infusion flow anomalies (low-level float-valves causing cut-off A61M5/40; indicating or recording presence, absence or direction of flow in general G01P13/0066) · CPC title

• A61M5/172

  electrical or electronic {(A61M5/16804, A61M5/16831 take precedence)} · CPC title

• G16H20/17 Primary

  delivered via infusion or injection · CPC title

• A61M5/365

  Air detectors (A61M5/1684 takes precedence; in extracorporeal blood circuits A61M1/3626) · CPC title

• A61M2005/16868

  Downstream occlusion sensors · CPC title