US8172798B2

Movatterモバイル変換

Info

Publication number: US8172798B2
Application number: US12/464,297
Authority: US
Inventors: Roger L. Hungerford; Tuan Bui; Gary COLISTER
Original assignee: Sigma International General Medical Apparatus LLC
Current assignee: Baxter Healthcare SA; Baxter International Inc
Priority date: 2009-05-12
Filing date: 2009-05-12
Publication date: 2012-05-08
Also published as: WO2010132077A1; EP2429610A4; US20100292645A1; CA2760806A1; EP2429610A1; CA2760806C

Abstract

A system for managing an infusion therapy, including: a server in communication with a central server; and an infusion pump in wireless communication with the server and for: uploading respective label data from respective labels for at least one medication, the respective label data including respective label pump programming data for infusion of the at least one medication by the pump; wirelessly transmitting the uploaded label data to the server; and wirelessly transmitting pump data identifying the pump to the server. The server is for transmitting the pump data and the respective label data to the server; and receiving, from the central server and in response to receipt of the pump data and the respective label data by the central server, second pump programming data regarding a second medication. The server is for comparing the first pump programming data with the second pump programming data.

Description

FIELD OF THE INVENTION

The invention relates generally to a system and method for controlling an infusion pump having access to a central server. In particular the invention relates to a system and method including a server connected to the central server and in wireless communication with the pump.

BACKGROUND OF THE INVENTION

To control dispensing of medications, the prior art teaches systems or methods using a centralized server to acquire and compare patient, medication, and prescription information. The prior art also teaches systems or methods using a bed-side point of care device to perform comparisons regarding control of medications. For example, a scanner for a computer is used to scan patient, medication, and prescription information into the computer and the computer performs comparison functions.

SUMMARY OF THE INVENTION

In one embodiment, when the first pump programming data is the same as the second pump programming data, the server is for generating and wirelessly transmitting to the pump an authorization signal; or when the first pump programming data is the same as the second pump programming data, the server is for generating and wirelessly transmitting to the pump an authorization signal and the pump is for infusing the first medication only if the authorization signal is received in the pump.

In another embodiment, when the first pump programming data is different than the second pump programming data, the server is for generating and wirelessly transmitting to the pump a difference signal regarding the difference between the first and second pump programming data; or when the first pump programming data is different than the second pump programming data, the server is for generating and wirelessly transmitting to the pump a difference signal regarding the difference between the first and second pump programming data; and wirelessly transmitting to the pump the second pump programming data.

In one embodiment, the respective label programming data includes first medication data identifying the single medication or the first medication, and the second pump programming data includes second medication data identifying the second medication and the server is for comparing the first and second medication data and when the first and second medication data match, generating and wirelessly transmitting to the pump an authorization signal. In another embodiment, the respective label programming data includes first medication data identifying the single medication or the first medication, and the second pump programming data includes second medication data identifying the second medication, the server is for comparing the first and second medication data and when the first and second medication data match, generating and wirelessly transmitting to the pump an authorization signal. The pump is for infusing the first medication only if the authorization signal is received by the pump.

In one embodiment, the first programming data includes first medication data identifying the first medication and the second pump programming data includes second medication data identifying the second medication, the server is for comparing the first and second medication data and when the first and second medication data are different, generating and wirelessly transmitting to the pump a difference signal regarding the difference between the first and second medications.

The invention also broadly comprises a system for managing an infusion therapy, including: at least one server in communication with a central server; and a plurality of infusion pumps in wireless communication with the at least one server. Each pump in the plurality of infusion pumps is for: uploading respective label data from a respective label for a respective medication, the respective label data including respective pump programming data for infusion of the respective medication by said each pump; and, wirelessly transmitting respective pump data identifying said each pump to the at least one server. The at least one server is for: transmitting the respective pump data to the central server; receiving, from the central server and in response to receipt of the respective pump data by the central server, respective server pump programming data regarding a respective prescribed medication; and for said each pump, comparing the respective pump programming data with the respective server pump programming data.

The invention broadly comprises a method for managing an infusion therapy.

It is a general object of the present invention to provide a system and method for managing infusion therapies that ensures proper application of infusion therapies while minimizing latency delays and equipment cost and complexity.

These and other objects and advantages of the present invention will be readily appreciable from the following description of preferred embodiments of the invention and from the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The nature and mode of operation of the present invention will now be more fully described in the following detailed description of the invention taken with the accompanying drawing figures, in which:

FIG. 1 is a schematic block diagram of a present invention system for managing an infusion therapy;

FIG. 2 is a schematic block diagram of a present invention system for managing an infusion therapy; and,

FIG. 3 is a flow chart of a present invention method for managing an infusion therapy.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

At the outset, it should be appreciated that like drawing numbers on different drawing views identify identical, or functionally similar, structural elements of the invention. While the present invention is described with respect to what is presently considered to be the preferred aspects, it is to be understood that the invention as claimed is not limited to the disclosed aspects.

Furthermore, it is understood that this invention is not limited to the particular methodology, materials and modifications described and as such may, of course, vary. It is also understood that the terminology used herein is for the purpose of describing particular aspects only, and is not intended to limit the scope of the present invention, which is limited only by the appended claims.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood to one of ordinary skill in the art to which this invention belongs. Although any methods, devices or materials similar or equivalent to those described herein can be used in the practice or testing of the invention, the preferred methods, devices, and materials are now described.

It should be understood that the use of “or” in the present application is with respect to a “non-exclusive” arrangement, unless stated otherwise. For example, when saying that “item x is A or B,” it is understood that this can mean one of the following: 1) item x is only one or the other of A and B; and 2) item x is both A and B. Alternately stated, the word “or” is not used to define an “exclusive or” arrangement. For example, an “exclusive or” arrangement for the statement “item x is A or B” would require that x can be only one of A and B.

FIG. 1 is a schematic block diagram ofpresent invention system100.System100 includesinfusion pump102 in wireless communication withserver104. The wireless communication can be by any means known in the art, for example,radio frequency link105. Pump102 can be any infusion pump known in the art having wireless communications capabilities and programming capabilities sufficient for the operation ofpump102 as described infra.Server104 can be any server known in the art having wireless communications capabilities and programming capabilities sufficient for the operation ofserver104 as described infra.

Server

104 is connected tocentral server106 by any means known in the art, including, but not limited to, a hardwire connection, an optical connection, an Internet connection, or a radio frequency connection.Central server106 can be any server or plurality of servers known in the art. In one embodiment,pump102,server104, andserver106 are located in a medical care facility (not shown), for example, a hospital or clinic. In one embodiment (not shown),pump102 andserver104 are located in one medical care facility, for example, a hospital or clinic andserver106 is in a different/remote location.Server106 performs centralized data storage and manipulation operations, for example, for a hospital or clinic, as is well known in the art.Server106 could perform centralized data storage and manipulation for all medical operations in a facility or could be limited to specific portions of the medical operations in a facility. For example,server106 could be limited to pharmacy operations for the facility. Data described infra with respect to the central server can be entered into the central server and stored or configured within the central server by any means known in the art.

In one embodiment (not shown), more than oneserver104 is located in a building or facility and linked withserver106. For example, depending on the size and configuration of the building or facility, the receiving power ofserver104, and the transmitting power ofpump102, more than oneserver104 may be required for a building or facility.

In one embodiment, the pump is for uploading, that is to say, the pump uploads, respective label data from respective labels for at least one medication. The respective label data including respective label pump programming data for infusion of the at least one medication by the pump. For example, in one embodiment,label data112 fromlabel114 formedication116 inmedication dispensing container118. That is, the at least one medication consists of a single medication. The description that follows is directed to the case of a single medication to be infused using the pump. Other example, embodiments directed to more than one medication to be infused by a pump are described infra. The label data includes labelpump programming data120 for infusion ofmedication116 by the pump. Parameters included in label pump programming data described herein, and other pump programming data described infra, can include, but are not limited to: medication identification, medication dosing, time to start infusion, volume to be infused, and patient weight.Data120 also can include prescription information formedication116. The pump wirelessly transmits the uploaded label data and pumpdata121, identifying the pump, toserver104.Server104 is for transmitting the pump data to the central server and receiving, from the central server and in response to receipt of the pump data by the central server, serverpump programming data122 for infusion of a medication, presumably, but subject to verification as described infra,medication116. The central server selectsdata122 by a linkage of the pump data in the central server as described infra. For example, a specific set of data, includingdata122 is associated withpump102, viapump data121, in the central server. The server then compares

data

120 and122.

The preceding paragraph describes a process for confirming that the pumping program onlabel114 is accurate and up-to-date. For example, it is possible that one or more of the parameters noted supra formedication116 have been revised sincelabel114 was created. In this instance,data122 includes the revised parameters andserver104 is able to determine that pump programming data including revised parameters is available. As another example, an error may have occurred during the generation oflabel114, resulting in an error inprogram120. In this instance,server104 detects the error by comparing

data

120 and122.

In one embodiment, whenserver104 determines that

data

120 and122 are the same,server104 generates and wirelessly transmits, to the pump,authorization signal126. In one embodiment, the pump displays a message regarding the match of

data

120 and122 in response to receiving the authorization signal. The message provides verification for a caregiver (not shown) operating the pump. In one embodiment, the pump infusesmedication116 only if the authorization signal is received in the pump. This arrangement automatically prevents operation of the pump is there is a problem withprogram data120, preventing possible harm to a patient (not shown) receiving an infusion ofmedication116.

In one embodiment, whenserver104 determines that

data

120 and122 are different,server104 generates and wirelessly transmits, to the pump,difference signal128. In one embodiment, the pump displays a message regarding the difference between

data

120 and122 in response to receiving the difference signal. The message provides a warning to a caregiver operating the pump. In one embodiment, the pumping capability of the pump is disabled upon receipt of the difference signal. That is, the pump cannot automatically operate if the difference signal is received. This arrangement automatically prevents operation of the pump is there is a problem withprogram data120, preventing possible harm to a patient receiving an infusion ofmedication116. In one embodiment, a caregiver is able to manually override the disablement of the pumping capability.

In one embodiment, whenserver104 determines that

data

120 and122 are different, and thatdata122 is a correct update ofdata120,server104 wirelessly transmitsdata122 to the pump. The pump generates and displaysmessage123 informing a caregiver that correct updated programming data (data122) has been downloaded into the pump and provides a prompt to begin infusion based ondata122. This arrangement enables a caregiver to quickly start an infusion based on the updated programming data.

In one embodiment,data112 includesmedication data124 identifyingmedication116 anddata122 includesmedication identification data132.Data132 identifies a medication to be infused usingdata122 and that is presumably the same asmedication116, but subject to confirmation as described infra. The server compares

data

124 and132. In one embodiment, when

data

124 and132 match (the respective medications identified in

data

124 and132 are the same),server104 generates and wirelessly transmits to the pump,authorization signal134. In one embodiment, the pump displays a message regarding the match of the respective medications in response to receivingauthorization signal134. The message provides verification for a caregiver (not shown) operating the pump. In one embodiment, the pump infusesmedication116 only ifauthorization signal134 is received in the pump. This arrangement automatically prevents operation of the pump if there is a problem withmedication116, preventing possible harm to a patient (not shown) scheduled to receive an infusion ofmedication116.

In one embodiment, whenserver104 determines that the respective medications identified in

data

124 and132 are different,server104 generates and wirelessly transmits, to the pump,difference signal136. In one embodiment, the pump displays a message regarding the difference between the medications in response to receivingdifference signal136. The message provides a warning to a caregiver operating the pump. In one embodiment, the pumping capability of the pump is disabled upon receipt ofdifference signal136. That is, the pump cannot automatically operate ifdifference signal136 is received. This arrangement automatically prevents operation of the pump if there is a problem withmedication116, preventing possible harm to a patient (not shown) scheduled to receive an infusion ofmedication116. In one embodiment, a caregiver is able to manually override the disablement of the pumping capability.

In one embodiment,data112 includeslabel patient identity138 identifying a patient for whommedication116 has been prescribed. The central server stores list140 of patients including respective list patient identification data142 and respective list pump programming data144 for patients in the list. The respective list pump programming data includes respective list medication data146 identifying a medication or medications to be infused using the respective pump programming data. The central server is arranged to receive, frombedside scanning device148,pump data121 andpatient data150 identifying a patient in whom pump102 is intended to infusemedication116.Data121 can be made available fordevice148 by any means known in the art, for example, by a barcode (not shown) on the pump.Device148 can be any device known in the art, anddata150 can be implemented by any means known in the art, for example,barcode152 on a bracelet (not shown) for the patient mentioned above.

The central server also is arranged to identify, usingpatient data150, listpatient identification data142A from data142 and listpump programming data144A from data144. The central server matchespatient data150 with listpatient identification data142A, that is, the identification of the patient for

data

150 and142A are the same. The central server also: correlatespatient identification data142A and pumpprogramming data144A withpump data121, for example, flags the data as being related to pumpdata121; selectspump programming data144A aspump programming data122, using the correlation ofpatient identification data142A and pumpprogramming data144A withpump data121; and selects,patient identification data142A using the correlation with the pump data. For example, the central server selects the pump programming data and patient identification data that have been flagged with the pump data. The server receives, from the central server,patient identification data142A and comparesdata138 withpatient identification data142A. In other words, the server determines if the patient to be infused by the pump is the same patient for whommedication116 has been prescribed according to the label data. Thus,system100 provides a means for linking, through the pump data, the identification of a patient intended to be infused with a medication with the identification of a patient for whom the medication has been prescribed. In one embodiment (not shown), the scanner is part ofpump102.

In one embodiment, when

data

138 and142A are the same (identify the same patient);server104 generates and wirelessly transmits to the pump,authorization signal154. In one embodiment, the pump displays a message regarding the match of

data

138 and142A in response to receivingauthorization signal154. The message provides verification for a caregiver (not shown) operating the pump. In one embodiment, the pump infusesmedication116 only ifauthorization signal154 is received in the pump. This arrangement automatically prevents operation of the pump if there is a problem with matchingmedication116 to the proper patient, preventing possible harm to a patient (not shown) who might otherwise be incorrectly infused withmedication116.

In one embodiment, when

data

138 and142A are different,server104 generates and wirelessly transmits to thepump difference signal156. That is, the patient intended to be infused with a medication is not the patient for whom the medication has been prescribed. In one embodiment, the pump displays a message regarding the difference between

data

138 and142A in response to receivingdifference signal156. The message provides a warning to a caregiver (not shown) operating the pump. In one embodiment, the pumping capability of the pump is disabled upon receipt ofdifference signal156. That is, the pump cannot automatically operate ifdifference signal156 is received. This arrangement automatically prevents operation of the pump if there is a problem with matchingmedication116 to the proper patient, preventing possible harm to a patient (not shown) who might otherwise be incorrectly infused withmedication116. In one embodiment, a caregiver is able to manually override the disablement of the pumping capability.

In one embodiment, pump102 is adapted for infusing a plurality of medications. In another embodiment, the medications are to be infused sequentially, that is, not concurrently. For example, the pump is adapted to infusemedication116 incontainer118 beforemedication113 incontainer115. The determination of which medication is to be infused is based on any criterion known in the art, for example, information on

labels

114 and117. It should be understood that the pump can be arranged to sequentially infuse any number of medications, not just the two medications shown inFIG. 1. The pump uploads label data for the first medication to be infused, for example,label data112 fromlabel114 formedication116 inmedication dispensing container118. The label data includes labelpump programming data120 for infusion ofmedication116 by the pump. The pump wirelessly transmits the uploaded label data and pumpdata121, identifying the pump, toserver104.Server104 is for transmitting the pump data to the central server and receiving, from the central server and in response to receipt of the pump data by the central server, serverpump programming data122 for infusion of a medication, presumably, but subject to verification as described infra,medication116. The central server selectsdata122 by a linkage of the pump data in the central server as described infra. For example, a specific set of data, includingdata122 is associated withpump102, viapump data121, in the central server. The server then compares

data

120 and122.

The discussion supra regardingauthorization signal126,difference signal128, the updating ofdata120, andmessage123 is applicable to the embodiment under discussion.

data

124 and132. The discussion supra regardingauthorization signal134 anddifference signal136 is applicable to the embodiment under discussion.

As noted supra, the central server stores list140 of patients including respective list patient identification data142 and respective list pump programming data144 for patients in the list. The respective list pump programming data includes respective list medication data146 identifying a medication or medications to be infused using the respective pump programming data. As described supra, when the pump is associated with only a single medication to be infused, the pump data uploaded by the pump is sufficient input from the pump for the process of correlatinglist140 with the pump. However, whenpump102 is associated with two or more medications to be infused, for example,

medications

116 and113, an additional parameter is needed for the process of correlatinglist140 with the pump. In one embodiment,data112 includeslabel patient identity138 identifying a patient for whommedication116 has been prescribed and labelmedication identification data147 identifyingmedication116. For example,list140 includesdata142A for the single patient,

pump programming data

144A and144B, for

medications

116 and113, respectively, and

medication identification data

146A and146B, for

medications

116 and113, respectively.

The central server is arranged to receive, frombedside scanning device148, the pump data andpatient data150 identifying a patient in whom pump102 is intended to infusemedication116. The central server also is arranged to identify, usingpatient data150 listpatient identification data142A from data142. The server matchespatient data150 with listpatient identification data142A, that is, the identification of the patient for

data

138 and142A are the same. However, in the example, in which the pump is associated with

medications

116 and113, there are two list pump programming data and two list medication identification data for the patient. Therefore, in one embodiment, the central server is arranged to identify, usingdata147, listmedication identification data146A and listpump programming data144A from data144. The server matchesdata147 with listmedication identification data146A, that is,

data

147 and146A are the same.

The central server also: correlatespatient identification data142A and pumpprogramming data144A with the pump data, for example, flags the data as being related to the pump data; selectspump programming data144A aspump programming data122, using the correlation ofpatient identification data142A and pumpprogramming data144A with the pump data; and selects,patient identification data142A using the correlation with the pump data. For example, the central server selects the pump programming data and patient identification data that have been flagged with the pump data. The server receives, from the central server,patient identification data142A and comparesdata138 withpatient identification data142A. In other words, the server determines if the patient to be infused by the pump is the same patient for whommedication116 has been prescribed according to the label data.

The discussion supra regardingauthorization signal154 and pumpdifference signal156 is applicable to the embodiment under discussion.

In one embodiment, pump102 is adapted for infusing a plurality of medications concurrently. For example, the pump is adapted to infuse

medications

116 and113 concurrently. For example, the pump is a multi-channel pump, for example, with

channels

160 and162 for

medications

116 and113, respectively. It should be understood that the number of medications concurrently infusible, for example, the number of channels in the pump, according to the present invention is not limited to the number shown inFIG. 1 and that other numbers of concurrently infusible medications/channels are included in the spirit and scope of the claimed invention. The discussion supra ofpump102 is applicable to a multi-channel pump, with the exception that instead of uploading pump identification data, for example,pump data121, identifying the pump, respective channel identification data identifying each channel in the pump is uploaded. For example,

channel identification data

164 and166, identifying

channels

160 and162, respectively, is uploaded. Thus, the channel identification data, for example,

channel identification data

164 and166, is uploaded into the wireless server via the pump, and is uploaded to the central server via the bedside scanner. The operations described supra usingpump identification data121 in the wireless server and in the central server are then performed using the channel identification data, for example,

channel identification data

164 or166. For example, the verification of medications, pump programs, and patient identifications are carried out using the channel identification data, for example,

channel identification data

164 or166. Alternately stated, each channel of the pump is treated as a single pump with a single medication.

In one embodiment, the functions described supra for the central server are performed byserver104. For example,server104 downloads list140 from the central server and the bedside scanner transmits

data

121 and150 toserver104, rather than to the central server. For example, server104: identifiespatient identification data142A,pump programming data144A, andmedication identification data146A fromlist140; correlatespatient identification data142A,pump programming data144A, andmedication identification data146A with the pump data; selectspump programming data144A aspump programming data122, and compareslabel patient identity138 withpatient identification data142A.

FIG. 2 is a schematic block diagram ofpresent invention system100. InFIG. 3,system100 includes a plurality of infusion pumps, for example, pumps302A and302B in wireless communication with at least one server, for example,server304. It should be understood thatsystem100 is not limited to a particular number of pumps and that other numbers of pumps are included in the spirit and scope of the claimed invention. In particular,FIG. 3 depicts a situation in which a single patient is being infused or will be infused using more than one pumps, for example, two separate pumps such as

pumps

302A and302B. The wireless communication can be by any means known in the art, for example, radio frequency links305 and307.

Pumps

302A and302B can be any infusion pumps known in the art having wireless communications capabilities and programming capabilities sufficient for the operation of

pumps

302A and302B as described supra and infra. In general, the description ofpump102 in the discussion ofFIG. 1 is applicable to

pumps

302A and302B inFIG. 3. In general, the description of

servers

104 and106 in the discussion ofFIG. 1A is applicable to

servers

304 and306 inFIG. 3.

In one embodiment, pumps302A and302B upload, respective label data, for example,

label data

312A and312B, from respective labels, for example, labels314A and314B, for respective medications, for example,

medications

316A and316B, in respective medication dispensing containers, for example,

containers

318A and318B. The respective label data includes respective pump programming data, for example,

data

320A and320B, for infusion of

medications

316A and316B by

pumps

302A and302B, respectively. Parameters included in the respective pump programming data described herein can include, but are not limited to: medication identification, medication dosing, time to start infusion, volume to be infused, and patient weight.

Data

320A and320B also can include prescription information for

medications

316A and316B. The pumps wirelessly transmits the uploaded label data and respective pump data, for example, pump

data

321A and321B, identifying the respective pump, toserver304.Server304 is for transmitting the respective pump data to the central server and receiving, from the central server and in response to receipt of the pump data by the central server, respective pump programming data, for example,

data

322A and322B, for infusion of a respective medication, presumably, but subject to verification as described infra,

medications

316A and316B. The central server selects

data

322A and322B by a linkage, correlation, or association of the respective pump data in the central server as described infra. For example, a specific set of data, includingdata322A is associated withpump302A, viapump data321A, in the central server. The server then compares

data

320A and322A and320B and322B.

The preceding paragraph describes a process for confirming that the pumping program on respective labels is accurate and up-to-date. For example, it is possible that one or more of the parameters noted supra for

medications

316A or316B have been revised since the respective label was created. In this instance,

data

322A and322B include the revised parameters andserver304 is able to determine that pump programming data including revised parameters is available. As another example, an error may have occurred during the generation of a respective label, resulting in an error in

data

320A or320B. In this instance,server304 detects the error by comparing

data

320A and322A and

data

320B and322B.

In one embodiment, whenserver304 determines that

data

320A and322A or

data

320B and322B are the same,server304 generates and wirelessly transmits, to

pumps

302A and302B, respectively,

authorization signals

326A and326B. In one embodiment, pumps302A and302B display respective messages regarding the match of

data

320A and322A and

data

320B and322B in response to receiving the respective authorization signal. The message provides verification for a caregiver (not shown) operating the respective pump. In one embodiment, the respective pump infuses the respective medication only if the respective authorization signal is received in the respective pump. This arrangement automatically prevents operation of the respective pump is there is a problem with

data

320A or320B, preventing possible harm to a patient (not shown) receiving an infusion of

medication

316A or316B.

In one embodiment, whenserver304 determines that

data

320A and322A or

data

320B and322B are different,server304 generates and wirelessly transmits, to pump302A and302B,

difference signal

328A and328B. respectively. In one embodiment, the respective pump displays a respective message regarding the difference between

data

320A and322A or

data

320B and322B in response to receiving the respective difference signal. The message provides a warning to a caregiver operating the respective pump. In one embodiment, the pumping capability of the respective pump is disabled upon receipt of the respective difference signal. That is, the respective pump cannot automatically operate if the respective difference signal is received. This arrangement automatically prevents operation of the respective pump is there is a problem with

data

medication

316A or316B. In one embodiment, a caregiver is able to manually override the disablement of the respective pumping capability.

In one embodiment, whenserver304 determines that

data

320A and322A or

data

320B and322B are different, and that

data

322A or322B is a correct update of

data

320A or320B, respectively,server304 wirelessly transmits

data

322A or322B to the respective pump. The respective pump generates and displays a message, for example,

message

323A and323B for

pumps

302A and302B, respectively, informing a caregiver that correct updated programming data (

data

322A or322B) has been downloaded into the respective pump and provides a prompt to begin infusion based on

data

322A or322B. This arrangement enables a caregiver to quickly start an infusion based on the updated programming data.

In one embodiment,

label data

312A and312B include respective label medication data, for example,

label medication data

324A and324B, identifying respective medications, for example,

medications

316A and316B, and

data

322A and322B includes respective medication identification data, for example,

medication identification data

332A and332B.

Medication identification data

332A and332B identifies a respective medication to be infused using

data

322A and322B, respectively, and that is presumably the same as

medication medications

316A and316B, but subject to confirmation as described infra. The server comparesdata324A withdata332A anddata324B withdata332B. In one embodiment, whendata324A anddata332A ordata324B anddata332B match (the respective medications identified in

label medication data

324A or324B and

medication identification data

332A or332B are the same),server304 generates and wirelessly transmits to the pump, respective authorization signals, for example, signals334A and334B, respectively. In one embodiment, the respective pump displays a respective message regarding the match of the respective medications in response to receiving a respective authorization signal. The respective message provides verification for a caregiver (not shown) operating the respective pump. In one embodiment, the respective pump infuses

medication

316A or316B only if the respective authorization signal is received in the respective pump. This arrangement automatically prevents operation of the respective pump if there is a problem with

medication

316A or316B, preventing possible harm to a patient (not shown) scheduled to receive an infusion of

medication

316A or316B.

In one embodiment, whenserver304 determines that the respective medications identified indata324A anddata332A ordata324B anddata332B are different,server304 generates and wirelessly transmits, to the respective pump, a respective difference signal, for example, signals336A and336B, respectively. In one embodiment, the respective pump displays a respective message regarding the difference between the respective medications in response to receiving the respective difference signal. The respective message provides a warning to a caregiver operating the respective pump. In one embodiment, the pumping capability of the respective pump is disabled upon receipt of the respective difference signal. That is, the respective pump cannot automatically operate if the difference signal is received. This arrangement automatically prevents operation of the respective pump if there is a problem with

medication

316A or316B. In one embodiment, a caregiver is able to manually override the disablement of the pumping capability.

In one embodiment,

label data

312A and312B include respective label patient identity data, for example, label

patient identity data

338A and338B, respectively, identifying a patient for whom

medication

316A or316B, respectively, has been prescribed. The central server stores list340 of patients including listpatient identification data342 and listpump programming data344 for patients in the list. The list pump programming data includeslist medication data346 identifying medications to be infused using the list pump programming data.

The central server is arranged to receive, from at least one bedside scanning device, for example,device348,

pump data

321A and321B and patient data, for example,patient data350, identifying the patient in whom the respective pump is intended to infuse medication, for example,

medications

316A or316B.

Pump data

321A and321B can be made available fordevice348 by any means known in the art, for example, by a respective barcode (not shown) on the respective pump.Device348 can be any device known in the art, anddata350 can be implemented by any means known in the art, for example,barcode352 on a bracelet (not shown) for the patient mentioned above. In one embodiment (not shown), the at least one scanner is part of the pumps.

The central server also is arranged to matchpatient data350 with respective list patient identification data from listpatient identification data342, for example, matchpatient data350 with list

patient identity data

342A and342B. The central server is arranged to match respective label medication identification data with respective list medication data fromlist medication data346, for example, match

label medication data

324A and324B with

list medication data

346A and346B. That is,patient data350 and list

patient identity data

342A and342B are the same and

label medication data

324A and324B and

list medication data

346A and346B, respectively, are the same. Since there is more than one pump for a single patient, using the patient identification alone, as described forFIG. 1, is not sufficient to differentiate between entries inlist340 for the patient. Therefore, an additional parameter, for example, the respective medication identifications, is used to enable the differentiation. It should be understood that other parameters, such as pump programming data, could be used instead of or in addition to the medication identification.

The central server also correlates, or associates, using the matches of the respective list patient identification data and the respective list medication data, respective list pump programming data from listpump programming data344, respective listpatient identification data342, and respectivelist medication identification346, with the respective pump data. For example, using the matches of list

patient identity data

342A and342B andpatient data350 and the matches of list

medication identity data

346A and346B with

label medication data

324A and324B, the central server correlates list

pump programming data

344A and344B with

pump data

321A and321B, respectively. For example, the central server flags list

patient identity data

342A and342B, list

pump programming data

344A and344B, and list

medication identity data

346A and346B with

pump data

321A and321B, respectively. In one embodiment, the central server selects, as the respective second pump programming data and using the respective correlations noted supra, the respective list pump programming data. For example, the central server selects list

pump programming data

344A and344B as

pump programming data

322A and322B, respectively.

In one embodiment, the central server selects the respective patient identification data, for example,

data

342A and342B, using the respective correlations noted supra. For example, in response to receiving

data

321A and321B fromserver304, the central server selects

data

342A and342B that have been flagged with respective pump data as noted supra. The at least one server receives from the central server the respective list patient identification data and compares the respective list patient identification data with the respective label patient label identification data, for example, the at least one server compares list

patient identity data

342A and342B with label

patient identity data

338A and338B, respectively. In other words, the at least one server determines if the patient to be infused by the respective pump is the same patient for whom

medication

316A or316B has been prescribed according to the respective label data. Thus,system100 provides a means for linking, through the respective pump data, the identification of a patient intended to be infused with a medication with the identification of a patient for whom the medication has been prescribed.

In one embodiment, when the respective list patient identification data matches the respective label patient identification data, for example, list

patient identity data

342A or342B and label

patient identity data

338A or338B, respectively, are the same (identify the same patient);server304 generates and wirelessly transmits to the respective pump, a respective authorization signal, for example, signals354A and354B. In one embodiment, when the respective list patient identification data does not match the respective label patient identification data, for example, list

patient identity data

342A or342B and label

patient identity data

338A or338B, respectively, are not the same (do not identify the same patient);server304 generates and wirelessly transmits to the respective pump, a respective difference signal, for example, signals356A and356B.

The discussion in the description ofFIG. 1 with respect to messages regarding the data matches, infusing medication only if an authorization signal is received, displaying a message regarding a difference in data, disabling pumping capability of the pump upon receipt of a difference signal, and manually override the disablement of the pumping capability, is applicable toFIG. 3.

The following is a summary of a process involving one embodiment of a present invention system. A bedside scanner, for example,scanner148, scans identification data for an infusion pump, for example,data121 forpump102, and identification data for a patient, for example,data150, and transmits the data to a central server, for example,server106. The central server correlates a list of patients, for example,list140, and respective data, such as data142 and144 withdata121. The pump wirelessly transmits the pump identification data, for example,data121, and information from a medication barcode, for example,data112 fromlabel114, to a wireless server, for example,server104. The barcode includes patient, medication, and prescription/pump programming data, for example,

data

138,116, and120, respectively. The wireless server transmits the pump identification data to the central server. Using the correlation, the central server selects the respective data associated with the pump data and transmits the respective data to the wireless server. The associated data can include patient identification, drug identification, and pump programming/prescription data. The wireless server compares some or all of the patient identification, drug identification, and pump programming/prescription data from the central server with the label data to ensure that the right patient, right drug, and right prescription are being implemented with the pump.

The present invention also comprises a server, for example,server104, for managing an infusion therapy. The server includesinterface element158,processor160, andmemory element162. By interface element, we mean any combination of hardware, firmware, or software in a processor-based device used to enable communication or data transfer between the device and a device, system, or network external to the computer. The interface element can connect with the device, system, or network external to the computer, for example, pump102 andserver106, using any means known in the art, including, but not limited to a hardwire connection, an optical connection, an Internet connection, or a wireless connection, such as a radio frequency connection.Processor160 andinterface element158 can be any processor or interface element, respectively, or combination thereof, known in the art. In one embodiment, the various data described supra are stored in the memory element.

FIG. 1 is used in the following discussion; however it should be understood that the discussion also is applicable toFIGS. 2 and 3. The interface element wirelessly uploads, from an infusion pump, for example, pump102, label data, for example,data112, from a label, for example,label114, for a first medication, for example,medication116. The label data includes pump programming data, for example,data120, for administering the first medication, medication data, for example,data124, identifying the first medication and patient data, for example,data138, identifying a patient for whom the first medication is intended. The label data uploaded from the label by the pump. The interface element also wirelessly uploads, from the infusion pump, pump data, for example,data121, identifying the pump, transmits the pump data to a central server, for example,server106, and receives, from the central server, pump programming data, for example,data122, for administering a second medication, medication data, for example,data132, identifying the second medication, and patient data, for example, data144, identifying a patient for whom the second medication is intended.

The processor compares the first patient, medication, and pump programming data with the second patient, medication, and pump programming data, respectively. For a match of the first patient, medication, and pump programming data, with the second patient, medication, or pump programming data, respectively, generating an authorization signal, for example, signal126,134, or146. The interface element is for wirelessly transmitting the authorization signal to the infusion pump. For a mismatch of the first patient, medication, or pump programming data, with the second patient, medication, or pump programming data, respectively, the processor generates a difference signal, for example, signal128,136, or148. The interface element wirelessly transmits to the pump the difference signal regarding the mismatch.

The central server transmits relevant information regarding the patient associated with the pump identification to the wireless server. For example, the central server receives the patient identification from the bedside scanner, selects appropriate and updated information such as medication and prescription/programming data for the patient, and transmits the updated information to the wireless server. The wireless server compares the patient, medication, and prescription/programming data received from the central server with the scanned data from the medication barcode to ensure that the right patient is given the right medication according to the right prescription/pump program. The wireless server sends a confirmation signal to the pump if the patient, medication, and prescription/programming data match. If the patient and medication data match, but the prescription/programming data has been updated or revised, the wireless server wirelessly transmits or sends the updated or revised prescription/programming data to the pump.

Medical institutions are striving to reduce medication errors, especially those associated with the use of an infusion pump. The typical goal of a medication error reduction system is to ensure the five rights of medication delivery: Right patient, Right medication, Right dose, Right time, and Right route. Typical errors that can occur in the process of delivering medication to a patient include:

- 1. Associating the wrong medication for the patient, that is, giving the wrong medication to the patient;
- 2. Associating the wrong patient with the medication, that is, giving medication to the wrong patient; and,
- 3. Delivering the medication according to an outdated prescription or pump program.
  A present invention system addresses each of the three problems noted above.

As noted supra, some prior art medication management systems use a bedside point of care device with processing capability, for example, a computer, to acquire and compare patient, medication, and prescription data. Thus, the prior art teaches away fromsystem100, which places the comparison functionality in a wireless server that can interface with a large number of pumps.

FIG. 3 is a flow chart illustrating a present invention method for managing an infusion therapy. Although the method inFIG. 2 is depicted as a sequence of numbered steps for clarity, no order should be inferred from the numbering unless explicitly stated. The method starts atStep400. Step402 uploads, using the infusion pump, respective label data from respective labels for at least one medication, the respective label data including respective first pump programming data for infusion of the at least one medication by the pump; step404 wirelessly transmits pump data identifying the pump from the pump to a server; step406 wirelessly transmits the uploaded label data from the pump to the server; step408 transmits the pump data from the server to the central server;step410 receives, in the server, from the central server, and in response to receipt of the pump data by the central server, second pump programming data regarding a second medication; and step412 compares, in the server, the first pump programming data with the second pump programming data.

In one embodiment:step414 determines, in the server, that the first pump programming data and the second pump programming data are the same;step416 generates, in the server, an authorization signal; and step418 wirelessly transmits the authorization signal from the server to the pump. In one embodiment,step420 infuses, using the pump, the first medication only if the authorization signal is received in the pump.

In another embodiment:step422 determines, in the server, that the first pump programming data and the second pump programming data are different;step424 generates, in the server, a difference signal regarding the difference; and step426 wirelessly transmits the difference signal from the server to the pump. In one embodiment, step428 wirelessly transmits the second pump programming data from the server to the pump.

In one embodiment, the first programming data includes first medication data identifying the first medication and the second programming data includes second medication data identifying the second medication and step430 compares, in the server, the first and second medication data;step432 when the first and second medication data match, generates an authorization signal; step434 wirelessly transmits the authorization signal to the pump;step436 infuses the first medication, using the pump, only if the authorization signal is received by the pump;step438, when the first and second medication data are different, generates, using the server, a difference signal regarding the difference between the first and second medications; and step440 wirelessly transmits the difference signal from the server to the pump.

The present invention also includes a method for managing an infusion therapy using a plurality of pumps. Although the method is described as a sequence of steps for clarity, no order should be inferred from the sequence unless explicitly stated. A first step uploads to a plurality of infusion pumps, respective label data from a respective label for a respective first medication, the respective label data including respective first pump programming data for infusion of the respective first medication by said each pump; a second step wirelessly transmits from the plurality of infusion pumps to at least one server, respective pump data identifying said each pump to the at least one server; a third step wirelessly transmits the uploaded respective label data from the plurality of infusion pumps to at least one server; a fourth step transmits the respective pump data from the at least one server to a central server; a fifth step receives, in the at least one server, from the central server, and in response to receipt of the respective pump data by the central server, respective second pump programming data regarding a respective second medication; and a sixth step compares, in the at least one server and for said each pump, the respective first pump programming data with the respective second pump programming data.

In one embodiment, when the respective first pump programming data matches the respective second pump programming data, a seventh step generates and wirelessly transmits to the at least one pump, using the at least one server, at least one authorization signal. In one embodiment, when the respective first pump programming data does not match the respective second pump programming data, an eighth step generates and wirelessly transmits to the at least one pump, using the at least one server, at least one difference signal.

In one embodiment, the respective first programming data includes respective first medication data identifying the respective first medication and the respective second pump programming data includes respective second medication data identifying the respective second medication and: a ninth step compares, using the at least one server, the respective first and second medication data; and, when the respective first and second medication data match, a tenth step generates and wirelessly transmits to the at least one pump, using the at least one server, at least one authorization signal; or, when the respective first and second medication data do not match, an eleventh step generates and wirelessly transmits to the at least one pump, using the at least one server, at least one difference signal.

In one embodiment, when the respective list patient identification data matches the respective label patient identification data, a twentieth step generates and wirelessly transmits to the at least one pump, using the at least one server, at least one authorization signal. In one embodiment, when the respective list patient identification data does not match the respective label patient identification data, a twenty first step generates and wirelessly transmits to the at least one pump, using the at least one server, at least one difference signal.

Thus, it is seen that the objects of the invention are efficiently obtained, although changes and modifications to the invention should be readily apparent to those having ordinary skill in the art, without departing from the spirit or scope of the invention as claimed. Although the invention is described by reference to a specific preferred embodiment, it is clear that variations can be made without departing from the scope or spirit of the invention as claimed.