Infusion management platform with infusion data grouping logic

• US 9,390,235 B2
• Filed: 03/13/2013
• Issued: 07/12/2016
• Est. Priority Date: 03/13/2013
• Status: Active Grant

• Current Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Original Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Inventors: Naker, Sachin B., Riddle, Tim
• Primary Examiner(s): Lin, Jerry
• Application Number:
  US13/802,397
• Publication Number:
  US 20140278122A1
• Time in Patent Office: 1,217 Days
• Field of Search: 702/19
• US Class Current: 1/1
• 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 5/14 Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
• CPC Class Codes: A61M 5/1409 in series, e.g. first substance passing through container holding second substance, e.g. reconstitution systems needle sets A61M5/162
• CPC Class Codes: G01F 22/00 Methods or apparatus for measuring volume of fluids or fluent solid material, not otherwise provided for
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 20/30 relating to physical therapies or activities, e.g. physiotherapy, acupressure or exercising
• CPC Class Codes: G16H 20/40 relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

An infusion management platform can determine, based on one or more infusion events, whether to group infusions or segments of infusions. Related apparatus, systems, techniques and articles are also described.

Claims

1. A computer-implemented method:

receiving data characterizing a first infusion of fluid into a patient from a container by an infusion module, the first infusion having an associated first order identifier and an associated first volume infused;

identifying an infusion event interrupting or terminating the infusion;

receiving data characterizing a second infusion of fluid into the patient by the infusion module, the second infusion having an associated second volume to be infused;

determining whether the second volume to be infused is less than a pre-defined percentage of the first volume infused;

assigning the first order identifier to the second infusion if the second volume to be infused is less than a pre-defined percentage of the first volume infused, or

assigning a second order identifier, different from the first order identifier, to the second infusion if the second volume to be infused is greater than a pre-defined percentage of the first volume to be infused; and

infusing fluid into a patient pursuant to at least one of the first infusion and the second infusion of fluid into the patient by the infusion module.

2. A method as in claim 1, further comprising:

determining whether the second infusion has characteristics matching the first infusion.

3. A method as in claim 2, wherein the characteristics comprise:

a profile name.

4. A method as in claim 2, wherein the characteristics comprise:

a patient name.

5. A method as in claim 2, wherein the characteristics comprise:

an infusion module identifier.

6. A method as in claim 2, wherein the characteristics comprise a patient care unit identifier.

7. A method as in claim 2, wherein the characteristics comprise an infusion type.

8. A method as in claim 2, wherein the characteristics comprise a drug name.

9. A method as in claim 1, further comprising:

providing data characterizing the order identifier assignment.

10. A method as in claim 9, wherein providing data comprises at least one of:

displaying the data in a graphical user interface, loading the data, storing the data, and transmitting the data to a remote computing system.

11. A method as in claim 1, wherein at least one of the receiving, identifying, determining, and assigning are implemented by at least one data processor forming part of at least one computing system.

12. A non-transitory computer program product storing instructions which, when executed by at least one data processor, result in operations comprising:

receiving data characterizing a first infusion of fluid into a patient from a container by an infusion module, the first infusion having an associated first order identifier and an associated first volume infused;

identifying an infusion event interrupting or terminating the infusion;

receiving data characterizing a second infusion of fluid into the patient by the infusion module, the second infusion having an associated second volume to be infused;

determining whether the second volume to be infused is less than a pre-defined percentage of the first volume infused;

assigning the first order identifier to the second infusion if the second volume to be infused is less than a pre-defined percentage of the first volume infused, or

assigning a second order identifier, different from the first order identifier, to the second infusion if the second volume to be infused is greater than a pre-defined percentage of the first volume to be infused; and

infusing fluid into a patient pursuant to at least one of the first infusion and the second infusion of fluid into the patient by the infusion module.

13. A computer program product as in claim 12, further comprising:

determining whether the second infusion has characteristics matching the first infusion.

14. A computer program product as in claim 13, wherein the characteristics comprise:

a profile name.

15. A computer program product as in claim 13, wherein the characteristics comprise:

a patient name.

16. A computer program product as in claim 13, wherein the characteristics comprise:

an infusion module identifier.

17. A computer program product as in claim 13, wherein the characteristics comprise a patient care unit identifier.

18. A computer program product as in claim 13, wherein the characteristics comprise an infusion type.

19. A computer program product as in claim 13, wherein the characteristics comprise a drug name.

20. A method comprising:

receiving first data characterizing a first infusion of fluid into a patient from a container by an infusion module, the first infusion having an associated first order identifier and an associated first volume infused, the first data comprising one or more characteristics selected from a group consisting of;

a profile name, a patient name, an infusion module identifier, a patient care unit identifier, an infusion type, and a drug name;

identifying an infusion event interrupting or terminating the infusion;

receiving second data characterizing a second infusion of fluid into the patient by the infusion module, the second infusion having an associated second volume to be infused, the second data comprising one or more characteristics selected from a group consisting of;

a profile name, a patient name, an infusion module identifier, a patient care unit identifier, an infusion type, and a drug name;

determining that at least one of the characteristics in the first data matches at least one of the characteristics in the second data;

determining whether the second volume to be infused is less than a pre-defined percentage of the first volume infused;

assigning the first order identifier to the second infusion if the second volume to be infused is less than a pre-defined percentage of the first volume infused, or

assigning a second order identifier, different from the first order identifier, to the second infusion if the second volume to be infused is greater than a pre-defined percentage of the first volume to be infused; and

infusing fluid into a patient pursuant to at least one of the first infusion and the second infusion of fluid into the patient by the infusion module.