CA2600867C - Line verification for multi-pump arrays - Google Patents
Line verification for multi-pump arrays Download PDFInfo
- Publication number
- CA2600867C CA2600867C CA2600867A CA2600867A CA2600867C CA 2600867 C CA2600867 C CA 2600867C CA 2600867 A CA2600867 A CA 2600867A CA 2600867 A CA2600867 A CA 2600867A CA 2600867 C CA2600867 C CA 2600867C
- Authority
- CA
- Canada
- Prior art keywords
- medication
- delivery device
- medication delivery
- identifier
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012795 verification Methods 0.000 title abstract description 3
- 238000003491 array Methods 0.000 title description 3
- 239000003814 drug Substances 0.000 claims abstract description 267
- 229940079593 drug Drugs 0.000 claims abstract description 267
- 238000001802 infusion Methods 0.000 claims abstract description 67
- 238000000034 method Methods 0.000 claims abstract description 21
- 238000004891 communication Methods 0.000 claims description 16
- 238000005086 pumping Methods 0.000 claims description 15
- 239000003978 infusion fluid Substances 0.000 claims description 7
- 239000012530 fluid Substances 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000002572 peristaltic effect Effects 0.000 claims description 2
- 230000004044 response Effects 0.000 claims description 2
- 238000002483 medication Methods 0.000 abstract description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000036772 blood pressure Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 208000003443 Unconsciousness Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000000747 cardiac effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 238000012377 drug delivery Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 208000014674 injury Diseases 0.000 description 1
- 238000007917 intracranial administration Methods 0.000 description 1
- 238000001990 intravenous administration Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 238000002560 therapeutic procedure Methods 0.000 description 1
- 230000008733 trauma Effects 0.000 description 1
Classifications
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/1407—Infusion of two or more substances
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
- G16H10/65—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records stored on portable record carriers, e.g. on smartcards, RFID tags or CD
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H20/17—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/50—General characteristics of the apparatus with microprocessors or computers
- A61M2205/52—General characteristics of the apparatus with microprocessors or computers with memories providing a history of measured variating parameters of apparatus or patient
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M2205/00—General characteristics of the apparatus
- A61M2205/60—General characteristics of the apparatus with identification means
- A61M2205/6063—Optical identification systems
- A61M2205/6072—Bar codes
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61M—DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
- A61M5/00—Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
- A61M5/14—Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
- A61M5/142—Pressure infusion, e.g. using pumps
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H20/13—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered from dispensers
Abstract
A system and method for verifying that a medication delivery device is properly programmed to deliver a medication from a medication source. The system and method insure that the right medication is delivered in the right manner to a patient, and is particularly advantageous where multiple medications are being delivered simultaneously to a patient. The system and method also provides for ensuring that the device is properly programmed each time a medication to be delivered is changed by requiring verification each time an infusion pump is opened. The identification devices contemplated by the system includes barcodes affixed to the delivery device and medication.
Other devices besides barcodes, such as RFID devices may also be used.
Other devices besides barcodes, such as RFID devices may also be used.
Description
LINE VERIFICATION FOR MULTI-PUMP ARRAYS
FIELD OF THE INVENTION
The invention is directed to infusion pumps, and more specifically, arrays of infusion pumps, including multi-channel infusion pumps, that are configured to deliver more than one infusion fluid into a patient through multiple infusion lines.
BACKGROUND OF THE INVENTION
In the environment of intensive care units, cardiac care units, operating rooms or trauma centers, it is often necessary to infuse into the patient more than one different drugs simultaneously. In addition, some of the drugs used in these environments are not directly compatible with each other and therefore need to be infused into the patient at different points of the body. Accordingly, arrays of infusion pumps are used to infuse each of the medications through different infusion lines. More recently, multi-channel infusion pumps capable of infusing several medications simultaneously at similar or different rates into a patient have been developed. While some types of these pumps are designed to deliver the medications through a common cannula, others are designed with multiple pumps, or channels, that pump fluid into a patient through a plurality of infusion lines.
As the name implies, multi-channel infusion pumps have more than one pumping channel, and an infusion line or set is installed into each channel. This arrangement allows each pump to be programmed to deliver the particular medication that flows through the infusion line or set installed in the channel such that each line may deliver mediation at different rates or in different volumes.
One problem that exists when infusing a patient with multiple infusion medications being delivered through different infusion lines is that it is necessary to ensure that each pump, or channel of a multi-channel pump, is properly programmed to deliver each medication. Since many infusion fluids and their sources look similar, one potential error is to load a drug into the wrong pump or pump channel. For example, drug A and infusion set A intended to be installed in pump A are mistakenly placed into pump B.
Moreover, even where the proper drug and infusion set are initially installed in pump A, if the infusion fluid container must be changed during infusion, there is potential for the drug and infusion set to be placed in the wrong pump or channel at the time of replacement.
Another potential error that can occur is that a pump or pump channel may be correctly programmed to deliver a particular medication, but the infusion line installed in the pump or pump channel is connected to the wrong medication source.
What has been needed, and not previously available, is a system and method of identifying infusion lines that ensures that the right line is installed in the right pumping channel. Such a system and method would include an automatic determination by the pumping channel that the right infusion line was installed. Alternatively, such a system could require some action on the part of the care giver before the pump would allow the infusion to begin.
SUMMARY OF THE INVENTION
In one aspect, the present invention provides a method for verifying that a medication delivery device selected from among a plurality of medication delivery devices is programmed to deliver a selected medication, comprising: opening a door on the medication delivery device; installing an infusion line into the medication delivery device in a manner that engages the infusion line to cause an infusion fluid within the infusion line, wherein installing the infusion line requires opening the door; reading a medication delivery device identifier affixed to a surface of the medication delivery device that is accessible when the door of the medication delivery device is opened and not accessible when the door of the medication delivery device is not opened, the medication delivery device identifier including information representing an identity of the medication delivery device; reading a medication source identifier affixed to a medication source in communication with the infusion line installed in the medication delivery device, the medication source identifier including information representing an identity of the medication; associating the medication delivery device with the medication source; and after associating the medical delivery device with the medication source, prompting with the controller a care giver to provide values of operating parameters associated with the medication to be delivered to the medication delivery device to operate the medication delivery device.
In a further aspect, the method of the present invention includes determining if more than one door of any of the plurality of medication delivery devices are open, and when more than one door is determined to be open in response to the determining step, providing an alert that more than one door is open. In yet another aspect, the method of the present invention also includes detecting a door opening after initiating delivery of the medication, providing an alert that a door has been opened, and requiring that the medication delivery device identifier affixed to the medication delivery device and the medication source identifier affixed to the medication source be read again before medication delivery may be restarted.
In yet another aspect, there is provided a system for associating a medical delivery device with a medication source, comprising: a medication source; a medication delivery device, wherein the medication source is operatively connected to the medication delivery device at a connection point for delivery of medication to a patient and the medication delivery device comprises a door which is opened to access the connection point;
a medication delivery device identifier disposed on the medication delivery device, the medication delivery device identifier including information providing an identification of the medication delivery device, wherein the medication delivery device identifier is readable when the door is opened, and not readable when the door is closed; a medication source identifier disposed on the medication source, the medication source identifier including information providing an identification of medication contained in the medication source;
an identifier reader configured to read the medication delivery device identifier and the medication source identifier and to retrieve the identification information included in each of the medication delivery device identifier and the medication source identifier; input means for inputting values of device operating parameters in operable communication with the medication delivery device; and a processor in operable communication with the identifier reader and the medication delivery device, the processor programmed to receive the retrieved identification information, associate the medication source with the medication delivery device, receive the values of device operating parameters from the input means after associating the medication source with the medication delivery device, communicate the values of device operating parameters to the medication delivery device and operate the medication delivery device in accordance with the values of device operating parameters.
FIELD OF THE INVENTION
The invention is directed to infusion pumps, and more specifically, arrays of infusion pumps, including multi-channel infusion pumps, that are configured to deliver more than one infusion fluid into a patient through multiple infusion lines.
BACKGROUND OF THE INVENTION
In the environment of intensive care units, cardiac care units, operating rooms or trauma centers, it is often necessary to infuse into the patient more than one different drugs simultaneously. In addition, some of the drugs used in these environments are not directly compatible with each other and therefore need to be infused into the patient at different points of the body. Accordingly, arrays of infusion pumps are used to infuse each of the medications through different infusion lines. More recently, multi-channel infusion pumps capable of infusing several medications simultaneously at similar or different rates into a patient have been developed. While some types of these pumps are designed to deliver the medications through a common cannula, others are designed with multiple pumps, or channels, that pump fluid into a patient through a plurality of infusion lines.
As the name implies, multi-channel infusion pumps have more than one pumping channel, and an infusion line or set is installed into each channel. This arrangement allows each pump to be programmed to deliver the particular medication that flows through the infusion line or set installed in the channel such that each line may deliver mediation at different rates or in different volumes.
One problem that exists when infusing a patient with multiple infusion medications being delivered through different infusion lines is that it is necessary to ensure that each pump, or channel of a multi-channel pump, is properly programmed to deliver each medication. Since many infusion fluids and their sources look similar, one potential error is to load a drug into the wrong pump or pump channel. For example, drug A and infusion set A intended to be installed in pump A are mistakenly placed into pump B.
Moreover, even where the proper drug and infusion set are initially installed in pump A, if the infusion fluid container must be changed during infusion, there is potential for the drug and infusion set to be placed in the wrong pump or channel at the time of replacement.
Another potential error that can occur is that a pump or pump channel may be correctly programmed to deliver a particular medication, but the infusion line installed in the pump or pump channel is connected to the wrong medication source.
What has been needed, and not previously available, is a system and method of identifying infusion lines that ensures that the right line is installed in the right pumping channel. Such a system and method would include an automatic determination by the pumping channel that the right infusion line was installed. Alternatively, such a system could require some action on the part of the care giver before the pump would allow the infusion to begin.
SUMMARY OF THE INVENTION
In one aspect, the present invention provides a method for verifying that a medication delivery device selected from among a plurality of medication delivery devices is programmed to deliver a selected medication, comprising: opening a door on the medication delivery device; installing an infusion line into the medication delivery device in a manner that engages the infusion line to cause an infusion fluid within the infusion line, wherein installing the infusion line requires opening the door; reading a medication delivery device identifier affixed to a surface of the medication delivery device that is accessible when the door of the medication delivery device is opened and not accessible when the door of the medication delivery device is not opened, the medication delivery device identifier including information representing an identity of the medication delivery device; reading a medication source identifier affixed to a medication source in communication with the infusion line installed in the medication delivery device, the medication source identifier including information representing an identity of the medication; associating the medication delivery device with the medication source; and after associating the medical delivery device with the medication source, prompting with the controller a care giver to provide values of operating parameters associated with the medication to be delivered to the medication delivery device to operate the medication delivery device.
In a further aspect, the method of the present invention includes determining if more than one door of any of the plurality of medication delivery devices are open, and when more than one door is determined to be open in response to the determining step, providing an alert that more than one door is open. In yet another aspect, the method of the present invention also includes detecting a door opening after initiating delivery of the medication, providing an alert that a door has been opened, and requiring that the medication delivery device identifier affixed to the medication delivery device and the medication source identifier affixed to the medication source be read again before medication delivery may be restarted.
In yet another aspect, there is provided a system for associating a medical delivery device with a medication source, comprising: a medication source; a medication delivery device, wherein the medication source is operatively connected to the medication delivery device at a connection point for delivery of medication to a patient and the medication delivery device comprises a door which is opened to access the connection point;
a medication delivery device identifier disposed on the medication delivery device, the medication delivery device identifier including information providing an identification of the medication delivery device, wherein the medication delivery device identifier is readable when the door is opened, and not readable when the door is closed; a medication source identifier disposed on the medication source, the medication source identifier including information providing an identification of medication contained in the medication source;
an identifier reader configured to read the medication delivery device identifier and the medication source identifier and to retrieve the identification information included in each of the medication delivery device identifier and the medication source identifier; input means for inputting values of device operating parameters in operable communication with the medication delivery device; and a processor in operable communication with the identifier reader and the medication delivery device, the processor programmed to receive the retrieved identification information, associate the medication source with the medication delivery device, receive the values of device operating parameters from the input means after associating the medication source with the medication delivery device, communicate the values of device operating parameters to the medication delivery device and operate the medication delivery device in accordance with the values of device operating parameters.
In another aspect, the medication source identifier is a barcode, and in still another aspect, the medication source identifier is an RFID device. In yet another aspect, the medication delivery device identifier is a barcode, and in another aspect, the medication delivery device identifier is an RFID device.
Other features and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the features of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram of a patient care management system according to the present invention.
FIG. 2 is a graphic representation of a patient identification bracelet including a barcode that can be read by a barcode reader.
FIG. 3 is a drawing of a barcode label affixed to a medication container that can be read by a barcode reader.
FIG. 3A is a drawing of a barcode label affixed to a caregiver identity badge.
FIG. 4 is a drawing showing a sheet of barcode labels that can be affixed to various containers or devices.
FIG. 5 is a schematic diagram of a multi-channel pumping arrangement showing the pumping channels and multiple infusion sources and infusion lines.
FIG. 6 is a schematic diagram of a pump or pump channel showing a barcode label affixed to the pump housing adjacent a peristaltic infusion pump and infusion line.
Other features and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the features of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram of a patient care management system according to the present invention.
FIG. 2 is a graphic representation of a patient identification bracelet including a barcode that can be read by a barcode reader.
FIG. 3 is a drawing of a barcode label affixed to a medication container that can be read by a barcode reader.
FIG. 3A is a drawing of a barcode label affixed to a caregiver identity badge.
FIG. 4 is a drawing showing a sheet of barcode labels that can be affixed to various containers or devices.
FIG. 5 is a schematic diagram of a multi-channel pumping arrangement showing the pumping channels and multiple infusion sources and infusion lines.
FIG. 6 is a schematic diagram of a pump or pump channel showing a barcode label affixed to the pump housing adjacent a peristaltic infusion pump and infusion line.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
Referring now to the drawings in detail, in which like reference numerals indicate like or corresponding elements among the several figures, there is shown in FIG. 1 a general illustration of a patient care system in accordance with one embodiment of the present invention. In FIG. 1, a patient care device 12 is connected to a hospital network 10 including a pharmacy management system 34 and a hospital information system server 30.
Each element 12, 30 and 34 is connected to network 10 by a transmission channel 32.
Transmission channel 32 is any wired or wireless transmission channel, for example a 802.11 wireless local area network (LAN). In a preferred embodiment of the present invention, network 10 also includes computer systems located in various departments throughout a hospital. For example, network 10 of FIG. 1 optionally includes computer systems associated with an admissions department 36, a billing department 38, a biomedical engineering department 40, a clinical laboratory 42, a central supply department 44, one or more unit station computers and/or a medical decision support system 48.
Patient care device 12 preferably comprises a system similar to that described in U.S.
Pat. No. 5,713,856 to Eggers et al. Alternatively, other patient care devices, such as pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapy devices, and other drug delivery devices may be utilized according to the teachings set forth herein. Patient care device 12 preferably comprises an advanced programming module 14, also referred to as interface unit 14, connected to one or more functional modules 16, 18, 20, 22. Interface unit 14 includes a central processing unit (CPU) 50 connected to a memory, e.g. random access memory (RAM) 58, and one or more interface devices such as user interface device 54, a coded data input device 60, a network connection 52, and an auxiliary interface 62 for communicating with additional modules or devices.
Interface unit 14 also preferably, although not necessarily, includes a main nonvolatile storage unit 56, preferably a hard disk drive, for storing software and data and one or more internal buses 64 for interconnecting the aforementioned elements.
In a typical embodiment, user interface device 54 is a touch screen for displaying information to a user and allowing a user to input information by touching defined areas of the screen. Alternatively, user interface device 54 could include any means for displaying and inputting information, such as a monitor, a printer, a keyboard, softkeys, a mouse, a track ball and/or a light pen. Coded data input device 60 is preferably a bar code reader capable of scanning and interpreting data printed in bar coded format.
Alternatively, data input device 60 could be any device for entering coded data into a computer, such as devices for reading a magnetic strips, PCMCIA smart cards, radio frequency cards, memory sticks, CDs, DVDs, or any other analog or digital storage media. Other examples of data input device 60 include a voice activation or recognition device or a portable personal data assistant (PDA). Depending upon the types of interface devices used, user interface device 54 and coded data input device 60 may be the same device.
Alternatively, although data input device 60 is shown in FIG. 1 to be disposed within interface unit 14, one skilled in the art will recognize that data input device 60 may be integral within pharmacy system 34 or located externally and communicating with pharmacy system 34 through an RS-232 serial interface or any other appropriate communication means.
Auxiliary interface 62 is preferably an RS-232 communications interface, however any other means for communicating with a peripheral device such as a printer, patient monitor, infusion pump or other medical device may be used without departing from the scope of the invention.
Network connection 52 is preferably a direct network connection such as a Ti connection, an integrated services digital network (ISDN) connection, a digital subscriber line (DSL) modem or a cable modem. Alternatively, any direct or indirect network connection may be used, including, but not limited to a telephone modem, an MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link or a WLANS connection.
Functional modules 16, 18, 20, 22 are any devices for providing care to a patient or for monitoring patient condition. In preferred embodiment of the present invention, at least one of functional modules 16, 18, 20, 22 is an infusion pump module such as an intravenous infusion pump for delivering medication or other fluid to a patient. For the purposes of this discussion, functional module 16 is an infusion pump module.
Each of functional modules 18, 20, 22 may be any patient treatment or monitoring device including, but not limited to, an infusion pump, a syringe pump, a PCA pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an EKG
monitor, an EEG monitor, a heart rate monitor or an intracranial pressure monitor.
Alternatively, 6 =
functional module 18, 20 and/or 22 may be a printer, scanner or any other peripheral input/output device.
Each functional module 16, 18, 20, 22 communicates directly or indirectly with interface unit 14, with interface unit 14 providing overall monitoring and control of device 12. In a preferred embodiment, functional modules 16, 18, 20, 22 are connected physically and electronically in serial fashion to one or both ends of interface unit 14 as shown in FIG. 1 and as detailed in Eggers et al. However, one skilled in the art will recognize that there are other means for connecting functional modules with the interface unit may be utilized without departing from the scope of the invention. It will also be appreciated that devices such as pumps or monitors that provide sufficient programmability and connectivity may communicate directly with the network without a separate interface unit.
As described above, additional medical devices or peripheral devices may be connected to patient care device 12 through one or more auxiliary interfaces 62.
Each functional module 16, 18, 20, 22 typically includes module-specific components 76, a microprocessor 70, a volatile memory 72 and a nonvolatile memory 74 for storing information. It should be noted that while four functional modules are shown in FIG. 1, any number of devices may be connected directly or indirectly to central computer 14. The number and type of functional modules described herein are intended to be illustrative, and in no way limit the scope of the present invention. Module-specific components 76 include any components necessary for operation of a particular module, such as a pumping mechanism for infusion pump module 16.
While each functional module is typically capable of a least some level of independent operation, interface unit 14 monitors and controls overall operation of device 12. For example, as will be described in more detail below, interface unit 14 provides programming instructions to the functional modules 16, 18, 20, 22 and monitors the status of each module.
In a preferred embodiment of the present invention, patient care device 12 is capable of operating in several different modes, or personalities, with each personality defined by a configuration database. A particular configuration database is selected based, at least in part, by patient-specific information such as patient location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) or a patient care device's 10 location in the hospital or hospital computer network. Patient care information may be entered through interface device 52, 54, 60 or 62, and may originate from anywhere in network 10, e.g.
from pharmacy 34, admissions 36, laboratory 42, etc.
Data to and from the various data sources can be converted into network-compatible data with existing technology, and movement of the information between the medical device and network can be accomplished by a variety of means. For example, patient care device 12 and network 10 may communicate via automated interaction and/or manual interaction. Automated interaction may be continuous or intermittent and may occur through direct network connection 54 (as shown in FIG. 1), or alternatively through RS232 links, MIB systems, RF links such as BLLTETOOTH (Amtel Corp., San Jose, Calif.), IR links, WLANS, digital cable systems, telephone modems or other communication means. Manual interaction between patient care device 12 and network 10 involves physically transferring, intermittently or periodically, data between systems using, for example, user interface device 54, coded data input device 60, bar codes, computer disks, portable data assistants, memory cards, or any other media for storing data. Preferably, the communication means is bidirectional with access to data from as many points of the distributed data sources as possible. Decision-making can occur at a variety of places within network 10. For example, and not by way of limitation, decisions can be made in HIS server 30, decision support 48, hospital department or unit stations 46, or within patient care device 12 itself.
Referring now to FIGS. 2-4, a variety of implementations of the barcode identification system of the present invention are shown. FIG. 2, for example, shows a patient identification bracelet 100 of the kind typically used in hospitals and other institutional settings to ensure that each patient is able to be identified even if the patient is unconscious or otherwise unable to respond to questioning. A barcode 105 is printed on a label that is attached to the patient identification bracelet 100 and has encoded within its sequence of bars the information necessary to identify the patient. This barcode may be read using a computerized barcode reader, such as those identified by reference number 60 (FIG. 1). In one embodiment, the barcode reader 60 comprises a light emitting and receiving wand that is scanned across the barcode. The light emitted by the wand is reflected by the sequence of dark and light lines comprising the barcode into the receiving lens of the wand. A sensor in the wand converts the received light into a signal that is then transmitted to the CPU. A software application program running on the CPU then decodes the signal into the data represented by the barcode in a manner well known to one skilled in the art. Using appropriate software programs, this data may then be automatically entered into a database stored in the CPU's memory or disk storage.
Alternatively, the sensor and suitable optics may be mounted within a module such that a badge or medication container is passed over a window that allows the emitted light to fall upon the bar code and be reflected back to the sensor.
Barcode systems are extremely flexible and the amount of information that can be represented by the barcode, while limited, can be used in a variety of ways.
For example, as depicted in FIG. 3, a drug container 110 is identified by a label 115 having a barcode 120 printed thereon. This barcode 120 can represent the patient identification and the medical order number, and any other information the institution finds helpful in dispensing the drug and tracking the treatment, such as operating parameters from programming and controlling the medical device that is intended to deliver the medication. The barcode 120 may also be read using a barcode reader, and, using suitable application software can be used to link the drug container and its contents with the patient identification bracelet 100 affixed to a patient to ensure the right drug is delivered to the right patient at the right time in the right manner. The use of barcodes is not limited to the implementations discussed above. A sheet 190 of barcode labels 130 having barcodes 135 is shown in FIG.
4. Such labels can be printed by a printer connected to a pharmacy CPU or the care management system or, alternatively, by any other printer connected to any other hospital infatination system that can be programmed to produce barcodes bearing the information in a form that can be read by the barcode readers connected to the various CPUs of the care management system. These barcode labels 135 may then be affixed to clinical devices, patient belongings, or other items where positive identification is needed. As will be discussed in more detail below, barcodes may also be affixed to various clinical devices to assist in identifying the device. For example, a barcode may be placed on a pump and linked through appropriate software to the identification barcode of a medication container to ensure that the pump that will dispense a specific medication is programmed with operating parameters that are correct for the linked medication.
FIG. 5 depicts one embodiment of the present invention showing a setup 200 arranged to deliver multiple infusions to a patient. While FIG. 5 shows a multi-channel pumping arrangement, those skilled in the art will understand that such an arrangement could be replaced with an array of single, double or other configuration pumps and still accomplish the solution to the problem of ensuring that the right drugs are delivered by the right pumps at the right rates that is provided by the present invention.
The setup 200 depicted in FIG. 5 includes an interface unit/controller 205, four LVP infusion pumps 215, 220, 225 and 230, and a barcode module 235. Barcode module 235 includes a barcode reader 240 mounted within the barcode module 235, as well as a barcode reader wand 245 operable connected to the barcode module 235. The barcode reader wand 245 allows reading barcodes affixed to objects that cannot be placed directly in front of barcode reader 240.
As shown in FIG. 5, medication sources 250, 255, 260 and 265 containing medication to be delivered to a patient are connected to infusion lines 270, 275, 280 and 285 respectively. Each of these infusion lines is routed through one of infusion pumps 215, 220, 225 or 230. Downstream of each of the pumps is a continuation of the infusion line, here identified as 290, 295, 300 and 305, that communicates the medication to be delivered to the patient 310.
In the depicted embodiment, each of the pumps 215, 220, 225 and 230 have a barcode 320, 325, 330 and 335 affixed to the pump that may be read by the barcode wand 245 to identify the pump. Additionally, each medication source 250, 255, 260 and 265 has a barcode 340, 345, 350 and 355 fixed to it to identify the medication contained within the medication source. Moreover, each of barcodes 340, 345, 350 and 355 may contain additional information, such as operating information including values for various medication delivery parameters, such as volume to be infused, rate and the like that can be read by barcode wand 245 and used to program the processor of controller 205 to deliver the mediation contained within a specification medication source to the patient.
As is easily imagined, it is important that a medication delivery device such as infusion pumps 215, 220, 225 or 230 be properly programmed to ensure that the medication that each pump is delivering to the patient is delivered properly.
One problem that exists in a busy institution where multiple infusions are being given to a single patient is the possibility that a care giver will make a mistake and program a pump for a medication other than the medication that is actually be delivered by the pump. Such errors arise because of the multitude of medication sources and lines can result in a confusing array of infusion lines that must be traced to a specific medication source. The care giver must then program the particular pump with the proper operating parameters.
The present invention solves this problem by providing a system and method for matching an infusion pump to a medication source. In one embodiment, the software operating on the controller 205 and pump use information provided by the barcode reader 235 to ensure that the proper pump or pumping channel is being programmed with operating parameters that are appropriate to the medication contained in the medication source connected to the pump. For example, in one embodiment, the caregiver scans an identification bracelet containing a barcode on a patient, and then scans the barcode 340 on medication source 250. The controller processes the information provided by the barcodes to see if the medication contained in medication source 250 is intended to be administered to that specific patient. If the controller determines that the right medication is being given to the right patient, the controller then allows, or in some embodiments, prompts, the care giver to read barcode 320 on pump 215.
When barcode 320 has been read, the controller assigns pump 215 to the medication contained in medication source 250, and then prompts the care giver to manually enter all information necessary to start the infusion, such as operating parameters such as infusion rate, volume and the like. By using the barcode reader 245 to identify the pump channel connected to medication source 250, the controller ensures that the delivery parameters associated with the medication contained in source 250 are programmed into the proper pump or pumping channel.
It will be understood that while the invention is described in terms of use of barcodes, other means for positively identifying patients, care givers, medications, and devices may be used, such as wireless devices. For example, each of the barcodes in to the above described example may be replaced with radio frequency identification devices (RFID). Such devices incorporate circuitry that is responsive to signals generated by a transmitter or transmitter/receiver to provide a transmission of information to the receiver.
In such a system, the transmitter sends a query signal that is received by the RFID device.
The RFID device responds to the signal by transmitting a signal containing identification information, or any other information it is programmed to transmit, that is then received by the receiver. Thus, the RFD) device can provide the same sort of positive identification as the barcodes described above. Moreover, the system and method of the present invention contemplates the use of any combination of barcodes, RFID devices or other means for identification to ensure that the right drug is delivered to the right patient using the right delivery parameters.
FIG. 6 depicts a further embodiment of the present invention. In this embodiment, a barcode is mounted on an interior surface of pump 220, and can only be accessed by opening the door 390 of pump 220, such as when infusion line 275 is mounted in pumping portion 400 so that the line is in operable communication with pumping fingers 405, 410 and 415. In this embodiment, barcode label 420 having barcode 425 is read by the barcode reader 245. This provides further insurance that the right medication delivery parameters are being programmed into the right pump. In another embodiment, the software operating controller 205 may include routines that only allow the door of a single pump to be opened at any given time.
In a further scenario, controller 205 may require that barcode 425 be read and matched to a medication source barcode every time that the door 390 is opened.
In this manner, controller 205 may insure that the pump is correctly programmed in the event that the door is opened to change an infusion line or for some other purpose, thus preventing inadvertent switching of lines from a source that would result in improper delivery of the medication contained in the source.
The comparisons required to carry out the present invention may be carried out in the processor of the controller 205 or the infusion pump 215. Additionally, since the controller 205 may be in communication with one or more internal or external servers associated with the institution, the comparisons may be carried out in any of the servers, with the appropriate commands and information being communicated between the server and the controller.
Additionally, the software instructions that are used to program the controller may also include capabilities such as providing for comparing values of operation parameters used to program and operate medication delivery devices to rules contained in a database of rules that have been established by the institution to ensure proper medication delivery. If any value of an operational value is not included within a range of predetermined acceptable values, such as set forth in a rule or rule as described above, the controller or server, depending on where the comparison takes place, may provide an alert to call attention to the discrepancy. Similarly, the rule may cause the system to pause until the discrepancy is corrected.
While several particular forms of the invention have been illustrated and described, it will be apparent that various modifications can be made. The scope of the claims should not be limited by the preferred embodiments set forth in the examples, but should be given the broadest interpretation consistent with the description as a whole.
This writing has disclosed at least the following concepts.
Concept 1. A method for matching an infusion channel with a medication source, comprising:
reading a barcode including information associated with an identification of a patient;
reading a barcode including information associated with an identification of a medication to be delivered to the patient;
comparing the information associated with the identification of the patient to the information associated with the identification of the medication;
providing an alert signal if the comparison does not satisfy a predetermined condition;
reading a barcode associated with a medication delivery device, the barcode including information associated with an identification of the medication delivery device;
controlling a processor to accept operating parameters associated with the medication when the controller receives the information associated with the identification of the medication delivery device; and programming the medication delivery device to deliver the medication in accordance with the accepted operating parameters.
Concept 2. The method of Concept 1, wherein programming the medication delivery device includes programming a selected one of a plurality of medication delivery devices, the selected one selected in accordance with the information associated with the identification of the medication delivery device.
Concept 3. A method for verifying that a medication delivery device selected from among a plurality of medication delivery devices is programmed to deliver a selected medication, comprising:
13a opening a door on the medication delivery device;
installing an infusion line into the medication delivery device in a manner that engages the infusion line to cause an infusion fluid within the infusion line to be delivered to a patient;
reading a barcode affixed to a surface of the medication delivery device that is accessible when the door of the medication delivery device is opened, the barcode including information representing an identity of the medication delivery device;
reading a barcode affixed to a medication source in communication with the infusion line installed in the medication delivery device, the barcode including information representing an identity of the medication to be delivered to the patient;
associating the medication delivery device with the medication source; and providing values of operating parameters associated with the medication to be delivered to the medication delivery device to operate the medication delivery device to deliver the medication to the patient.
Concept 4. The method of Concept 3, further comprising:
determining if more than one door of any of the plurality of medication delivery devices are open; and providing an alert that more than one door is open.
Concept 5. The method of Concept 3, further comprising:
detecting a door opening after initiating delivery of the medication;
providing an alert that a door has been opened;
requiring that the barcode affixed to the medication delivery device and the barcode affixed to the medication source be read again before medication delivery may be restarted.
Concept 6. A system for associating a medical delivery device with a medication source, comprising:
a medication delivery device;
13b a medication delivery device identifier disposed on the medication delivery device, the medication delivery device identifier including information providing an identification of the medication delivery device;
a medication source;
a medication source identifier disposed on the medication source, the medication source identifier including information providing an identification of medication contained in the medication source;
an identifier reader capable of reading the medication delivery device identifier and the medication source identifier and retrieving the identification information included in each of the medication delivery device identifier and the medication source identifier;
input means for inputting values of device operating parameters in operable communication with the medication delivery device; and a processor in operable communication with the identifier reader and the medication delivery device, the processor programmed to receive the retrieved identification information, associate the medication source with the medication delivery device, receive the values of device operating parameters from the input means, communicate the values of device operating parameters to the medication delivery device and operate the medication delivery device in accordance with the values of device operating parameters.
Concept 7. The system of Concept 6, wherein the medication source identifier is a barcode.
Concept 8. The system of Concept 6, wherein the medication source identifier is an RFID device.
Concept 9. The system of Concept 6, wherein the medication delivery device identifier is a barcode.
Concept 10. The system of Concept 6, wherein the medication delivery device identifier is an RFID device.
13c
Referring now to the drawings in detail, in which like reference numerals indicate like or corresponding elements among the several figures, there is shown in FIG. 1 a general illustration of a patient care system in accordance with one embodiment of the present invention. In FIG. 1, a patient care device 12 is connected to a hospital network 10 including a pharmacy management system 34 and a hospital information system server 30.
Each element 12, 30 and 34 is connected to network 10 by a transmission channel 32.
Transmission channel 32 is any wired or wireless transmission channel, for example a 802.11 wireless local area network (LAN). In a preferred embodiment of the present invention, network 10 also includes computer systems located in various departments throughout a hospital. For example, network 10 of FIG. 1 optionally includes computer systems associated with an admissions department 36, a billing department 38, a biomedical engineering department 40, a clinical laboratory 42, a central supply department 44, one or more unit station computers and/or a medical decision support system 48.
Patient care device 12 preferably comprises a system similar to that described in U.S.
Pat. No. 5,713,856 to Eggers et al. Alternatively, other patient care devices, such as pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapy devices, and other drug delivery devices may be utilized according to the teachings set forth herein. Patient care device 12 preferably comprises an advanced programming module 14, also referred to as interface unit 14, connected to one or more functional modules 16, 18, 20, 22. Interface unit 14 includes a central processing unit (CPU) 50 connected to a memory, e.g. random access memory (RAM) 58, and one or more interface devices such as user interface device 54, a coded data input device 60, a network connection 52, and an auxiliary interface 62 for communicating with additional modules or devices.
Interface unit 14 also preferably, although not necessarily, includes a main nonvolatile storage unit 56, preferably a hard disk drive, for storing software and data and one or more internal buses 64 for interconnecting the aforementioned elements.
In a typical embodiment, user interface device 54 is a touch screen for displaying information to a user and allowing a user to input information by touching defined areas of the screen. Alternatively, user interface device 54 could include any means for displaying and inputting information, such as a monitor, a printer, a keyboard, softkeys, a mouse, a track ball and/or a light pen. Coded data input device 60 is preferably a bar code reader capable of scanning and interpreting data printed in bar coded format.
Alternatively, data input device 60 could be any device for entering coded data into a computer, such as devices for reading a magnetic strips, PCMCIA smart cards, radio frequency cards, memory sticks, CDs, DVDs, or any other analog or digital storage media. Other examples of data input device 60 include a voice activation or recognition device or a portable personal data assistant (PDA). Depending upon the types of interface devices used, user interface device 54 and coded data input device 60 may be the same device.
Alternatively, although data input device 60 is shown in FIG. 1 to be disposed within interface unit 14, one skilled in the art will recognize that data input device 60 may be integral within pharmacy system 34 or located externally and communicating with pharmacy system 34 through an RS-232 serial interface or any other appropriate communication means.
Auxiliary interface 62 is preferably an RS-232 communications interface, however any other means for communicating with a peripheral device such as a printer, patient monitor, infusion pump or other medical device may be used without departing from the scope of the invention.
Network connection 52 is preferably a direct network connection such as a Ti connection, an integrated services digital network (ISDN) connection, a digital subscriber line (DSL) modem or a cable modem. Alternatively, any direct or indirect network connection may be used, including, but not limited to a telephone modem, an MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link or a WLANS connection.
Functional modules 16, 18, 20, 22 are any devices for providing care to a patient or for monitoring patient condition. In preferred embodiment of the present invention, at least one of functional modules 16, 18, 20, 22 is an infusion pump module such as an intravenous infusion pump for delivering medication or other fluid to a patient. For the purposes of this discussion, functional module 16 is an infusion pump module.
Each of functional modules 18, 20, 22 may be any patient treatment or monitoring device including, but not limited to, an infusion pump, a syringe pump, a PCA pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an EKG
monitor, an EEG monitor, a heart rate monitor or an intracranial pressure monitor.
Alternatively, 6 =
functional module 18, 20 and/or 22 may be a printer, scanner or any other peripheral input/output device.
Each functional module 16, 18, 20, 22 communicates directly or indirectly with interface unit 14, with interface unit 14 providing overall monitoring and control of device 12. In a preferred embodiment, functional modules 16, 18, 20, 22 are connected physically and electronically in serial fashion to one or both ends of interface unit 14 as shown in FIG. 1 and as detailed in Eggers et al. However, one skilled in the art will recognize that there are other means for connecting functional modules with the interface unit may be utilized without departing from the scope of the invention. It will also be appreciated that devices such as pumps or monitors that provide sufficient programmability and connectivity may communicate directly with the network without a separate interface unit.
As described above, additional medical devices or peripheral devices may be connected to patient care device 12 through one or more auxiliary interfaces 62.
Each functional module 16, 18, 20, 22 typically includes module-specific components 76, a microprocessor 70, a volatile memory 72 and a nonvolatile memory 74 for storing information. It should be noted that while four functional modules are shown in FIG. 1, any number of devices may be connected directly or indirectly to central computer 14. The number and type of functional modules described herein are intended to be illustrative, and in no way limit the scope of the present invention. Module-specific components 76 include any components necessary for operation of a particular module, such as a pumping mechanism for infusion pump module 16.
While each functional module is typically capable of a least some level of independent operation, interface unit 14 monitors and controls overall operation of device 12. For example, as will be described in more detail below, interface unit 14 provides programming instructions to the functional modules 16, 18, 20, 22 and monitors the status of each module.
In a preferred embodiment of the present invention, patient care device 12 is capable of operating in several different modes, or personalities, with each personality defined by a configuration database. A particular configuration database is selected based, at least in part, by patient-specific information such as patient location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) or a patient care device's 10 location in the hospital or hospital computer network. Patient care information may be entered through interface device 52, 54, 60 or 62, and may originate from anywhere in network 10, e.g.
from pharmacy 34, admissions 36, laboratory 42, etc.
Data to and from the various data sources can be converted into network-compatible data with existing technology, and movement of the information between the medical device and network can be accomplished by a variety of means. For example, patient care device 12 and network 10 may communicate via automated interaction and/or manual interaction. Automated interaction may be continuous or intermittent and may occur through direct network connection 54 (as shown in FIG. 1), or alternatively through RS232 links, MIB systems, RF links such as BLLTETOOTH (Amtel Corp., San Jose, Calif.), IR links, WLANS, digital cable systems, telephone modems or other communication means. Manual interaction between patient care device 12 and network 10 involves physically transferring, intermittently or periodically, data between systems using, for example, user interface device 54, coded data input device 60, bar codes, computer disks, portable data assistants, memory cards, or any other media for storing data. Preferably, the communication means is bidirectional with access to data from as many points of the distributed data sources as possible. Decision-making can occur at a variety of places within network 10. For example, and not by way of limitation, decisions can be made in HIS server 30, decision support 48, hospital department or unit stations 46, or within patient care device 12 itself.
Referring now to FIGS. 2-4, a variety of implementations of the barcode identification system of the present invention are shown. FIG. 2, for example, shows a patient identification bracelet 100 of the kind typically used in hospitals and other institutional settings to ensure that each patient is able to be identified even if the patient is unconscious or otherwise unable to respond to questioning. A barcode 105 is printed on a label that is attached to the patient identification bracelet 100 and has encoded within its sequence of bars the information necessary to identify the patient. This barcode may be read using a computerized barcode reader, such as those identified by reference number 60 (FIG. 1). In one embodiment, the barcode reader 60 comprises a light emitting and receiving wand that is scanned across the barcode. The light emitted by the wand is reflected by the sequence of dark and light lines comprising the barcode into the receiving lens of the wand. A sensor in the wand converts the received light into a signal that is then transmitted to the CPU. A software application program running on the CPU then decodes the signal into the data represented by the barcode in a manner well known to one skilled in the art. Using appropriate software programs, this data may then be automatically entered into a database stored in the CPU's memory or disk storage.
Alternatively, the sensor and suitable optics may be mounted within a module such that a badge or medication container is passed over a window that allows the emitted light to fall upon the bar code and be reflected back to the sensor.
Barcode systems are extremely flexible and the amount of information that can be represented by the barcode, while limited, can be used in a variety of ways.
For example, as depicted in FIG. 3, a drug container 110 is identified by a label 115 having a barcode 120 printed thereon. This barcode 120 can represent the patient identification and the medical order number, and any other information the institution finds helpful in dispensing the drug and tracking the treatment, such as operating parameters from programming and controlling the medical device that is intended to deliver the medication. The barcode 120 may also be read using a barcode reader, and, using suitable application software can be used to link the drug container and its contents with the patient identification bracelet 100 affixed to a patient to ensure the right drug is delivered to the right patient at the right time in the right manner. The use of barcodes is not limited to the implementations discussed above. A sheet 190 of barcode labels 130 having barcodes 135 is shown in FIG.
4. Such labels can be printed by a printer connected to a pharmacy CPU or the care management system or, alternatively, by any other printer connected to any other hospital infatination system that can be programmed to produce barcodes bearing the information in a form that can be read by the barcode readers connected to the various CPUs of the care management system. These barcode labels 135 may then be affixed to clinical devices, patient belongings, or other items where positive identification is needed. As will be discussed in more detail below, barcodes may also be affixed to various clinical devices to assist in identifying the device. For example, a barcode may be placed on a pump and linked through appropriate software to the identification barcode of a medication container to ensure that the pump that will dispense a specific medication is programmed with operating parameters that are correct for the linked medication.
FIG. 5 depicts one embodiment of the present invention showing a setup 200 arranged to deliver multiple infusions to a patient. While FIG. 5 shows a multi-channel pumping arrangement, those skilled in the art will understand that such an arrangement could be replaced with an array of single, double or other configuration pumps and still accomplish the solution to the problem of ensuring that the right drugs are delivered by the right pumps at the right rates that is provided by the present invention.
The setup 200 depicted in FIG. 5 includes an interface unit/controller 205, four LVP infusion pumps 215, 220, 225 and 230, and a barcode module 235. Barcode module 235 includes a barcode reader 240 mounted within the barcode module 235, as well as a barcode reader wand 245 operable connected to the barcode module 235. The barcode reader wand 245 allows reading barcodes affixed to objects that cannot be placed directly in front of barcode reader 240.
As shown in FIG. 5, medication sources 250, 255, 260 and 265 containing medication to be delivered to a patient are connected to infusion lines 270, 275, 280 and 285 respectively. Each of these infusion lines is routed through one of infusion pumps 215, 220, 225 or 230. Downstream of each of the pumps is a continuation of the infusion line, here identified as 290, 295, 300 and 305, that communicates the medication to be delivered to the patient 310.
In the depicted embodiment, each of the pumps 215, 220, 225 and 230 have a barcode 320, 325, 330 and 335 affixed to the pump that may be read by the barcode wand 245 to identify the pump. Additionally, each medication source 250, 255, 260 and 265 has a barcode 340, 345, 350 and 355 fixed to it to identify the medication contained within the medication source. Moreover, each of barcodes 340, 345, 350 and 355 may contain additional information, such as operating information including values for various medication delivery parameters, such as volume to be infused, rate and the like that can be read by barcode wand 245 and used to program the processor of controller 205 to deliver the mediation contained within a specification medication source to the patient.
As is easily imagined, it is important that a medication delivery device such as infusion pumps 215, 220, 225 or 230 be properly programmed to ensure that the medication that each pump is delivering to the patient is delivered properly.
One problem that exists in a busy institution where multiple infusions are being given to a single patient is the possibility that a care giver will make a mistake and program a pump for a medication other than the medication that is actually be delivered by the pump. Such errors arise because of the multitude of medication sources and lines can result in a confusing array of infusion lines that must be traced to a specific medication source. The care giver must then program the particular pump with the proper operating parameters.
The present invention solves this problem by providing a system and method for matching an infusion pump to a medication source. In one embodiment, the software operating on the controller 205 and pump use information provided by the barcode reader 235 to ensure that the proper pump or pumping channel is being programmed with operating parameters that are appropriate to the medication contained in the medication source connected to the pump. For example, in one embodiment, the caregiver scans an identification bracelet containing a barcode on a patient, and then scans the barcode 340 on medication source 250. The controller processes the information provided by the barcodes to see if the medication contained in medication source 250 is intended to be administered to that specific patient. If the controller determines that the right medication is being given to the right patient, the controller then allows, or in some embodiments, prompts, the care giver to read barcode 320 on pump 215.
When barcode 320 has been read, the controller assigns pump 215 to the medication contained in medication source 250, and then prompts the care giver to manually enter all information necessary to start the infusion, such as operating parameters such as infusion rate, volume and the like. By using the barcode reader 245 to identify the pump channel connected to medication source 250, the controller ensures that the delivery parameters associated with the medication contained in source 250 are programmed into the proper pump or pumping channel.
It will be understood that while the invention is described in terms of use of barcodes, other means for positively identifying patients, care givers, medications, and devices may be used, such as wireless devices. For example, each of the barcodes in to the above described example may be replaced with radio frequency identification devices (RFID). Such devices incorporate circuitry that is responsive to signals generated by a transmitter or transmitter/receiver to provide a transmission of information to the receiver.
In such a system, the transmitter sends a query signal that is received by the RFID device.
The RFID device responds to the signal by transmitting a signal containing identification information, or any other information it is programmed to transmit, that is then received by the receiver. Thus, the RFD) device can provide the same sort of positive identification as the barcodes described above. Moreover, the system and method of the present invention contemplates the use of any combination of barcodes, RFID devices or other means for identification to ensure that the right drug is delivered to the right patient using the right delivery parameters.
FIG. 6 depicts a further embodiment of the present invention. In this embodiment, a barcode is mounted on an interior surface of pump 220, and can only be accessed by opening the door 390 of pump 220, such as when infusion line 275 is mounted in pumping portion 400 so that the line is in operable communication with pumping fingers 405, 410 and 415. In this embodiment, barcode label 420 having barcode 425 is read by the barcode reader 245. This provides further insurance that the right medication delivery parameters are being programmed into the right pump. In another embodiment, the software operating controller 205 may include routines that only allow the door of a single pump to be opened at any given time.
In a further scenario, controller 205 may require that barcode 425 be read and matched to a medication source barcode every time that the door 390 is opened.
In this manner, controller 205 may insure that the pump is correctly programmed in the event that the door is opened to change an infusion line or for some other purpose, thus preventing inadvertent switching of lines from a source that would result in improper delivery of the medication contained in the source.
The comparisons required to carry out the present invention may be carried out in the processor of the controller 205 or the infusion pump 215. Additionally, since the controller 205 may be in communication with one or more internal or external servers associated with the institution, the comparisons may be carried out in any of the servers, with the appropriate commands and information being communicated between the server and the controller.
Additionally, the software instructions that are used to program the controller may also include capabilities such as providing for comparing values of operation parameters used to program and operate medication delivery devices to rules contained in a database of rules that have been established by the institution to ensure proper medication delivery. If any value of an operational value is not included within a range of predetermined acceptable values, such as set forth in a rule or rule as described above, the controller or server, depending on where the comparison takes place, may provide an alert to call attention to the discrepancy. Similarly, the rule may cause the system to pause until the discrepancy is corrected.
While several particular forms of the invention have been illustrated and described, it will be apparent that various modifications can be made. The scope of the claims should not be limited by the preferred embodiments set forth in the examples, but should be given the broadest interpretation consistent with the description as a whole.
This writing has disclosed at least the following concepts.
Concept 1. A method for matching an infusion channel with a medication source, comprising:
reading a barcode including information associated with an identification of a patient;
reading a barcode including information associated with an identification of a medication to be delivered to the patient;
comparing the information associated with the identification of the patient to the information associated with the identification of the medication;
providing an alert signal if the comparison does not satisfy a predetermined condition;
reading a barcode associated with a medication delivery device, the barcode including information associated with an identification of the medication delivery device;
controlling a processor to accept operating parameters associated with the medication when the controller receives the information associated with the identification of the medication delivery device; and programming the medication delivery device to deliver the medication in accordance with the accepted operating parameters.
Concept 2. The method of Concept 1, wherein programming the medication delivery device includes programming a selected one of a plurality of medication delivery devices, the selected one selected in accordance with the information associated with the identification of the medication delivery device.
Concept 3. A method for verifying that a medication delivery device selected from among a plurality of medication delivery devices is programmed to deliver a selected medication, comprising:
13a opening a door on the medication delivery device;
installing an infusion line into the medication delivery device in a manner that engages the infusion line to cause an infusion fluid within the infusion line to be delivered to a patient;
reading a barcode affixed to a surface of the medication delivery device that is accessible when the door of the medication delivery device is opened, the barcode including information representing an identity of the medication delivery device;
reading a barcode affixed to a medication source in communication with the infusion line installed in the medication delivery device, the barcode including information representing an identity of the medication to be delivered to the patient;
associating the medication delivery device with the medication source; and providing values of operating parameters associated with the medication to be delivered to the medication delivery device to operate the medication delivery device to deliver the medication to the patient.
Concept 4. The method of Concept 3, further comprising:
determining if more than one door of any of the plurality of medication delivery devices are open; and providing an alert that more than one door is open.
Concept 5. The method of Concept 3, further comprising:
detecting a door opening after initiating delivery of the medication;
providing an alert that a door has been opened;
requiring that the barcode affixed to the medication delivery device and the barcode affixed to the medication source be read again before medication delivery may be restarted.
Concept 6. A system for associating a medical delivery device with a medication source, comprising:
a medication delivery device;
13b a medication delivery device identifier disposed on the medication delivery device, the medication delivery device identifier including information providing an identification of the medication delivery device;
a medication source;
a medication source identifier disposed on the medication source, the medication source identifier including information providing an identification of medication contained in the medication source;
an identifier reader capable of reading the medication delivery device identifier and the medication source identifier and retrieving the identification information included in each of the medication delivery device identifier and the medication source identifier;
input means for inputting values of device operating parameters in operable communication with the medication delivery device; and a processor in operable communication with the identifier reader and the medication delivery device, the processor programmed to receive the retrieved identification information, associate the medication source with the medication delivery device, receive the values of device operating parameters from the input means, communicate the values of device operating parameters to the medication delivery device and operate the medication delivery device in accordance with the values of device operating parameters.
Concept 7. The system of Concept 6, wherein the medication source identifier is a barcode.
Concept 8. The system of Concept 6, wherein the medication source identifier is an RFID device.
Concept 9. The system of Concept 6, wherein the medication delivery device identifier is a barcode.
Concept 10. The system of Concept 6, wherein the medication delivery device identifier is an RFID device.
13c
Claims (16)
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A method for verifying that a medication delivery device selected from among a plurality of medication delivery devices is programmed to deliver a selected medication, comprising:
opening a door on the medication delivery device;
installing an infusion line into the medication delivery device in a manner that engages the infusion line to cause an infusion fluid within the infusion line, wherein installing the infusion line requires opening the door;
reading a medication delivery device identifier affixed to a surface of the medication delivery device that is accessible when the door of the medication delivery device is opened and not accessible when the door of the medication delivery device is not opened, the medication delivery device identifier including information representing an identity of the medication delivery device;
reading a medication source identifier affixed to a medication source in communication with the infusion line installed in the medication delivery device, the medication source identifier including information representing an identity of the medication;
associating the medication delivery device with the medication source; and after associating the medical delivery device with the medication source, prompting with the controller a care giver to provide values of operating parameters associated with the medication to be delivered to the medication delivery device to operate the medication delivery device.
opening a door on the medication delivery device;
installing an infusion line into the medication delivery device in a manner that engages the infusion line to cause an infusion fluid within the infusion line, wherein installing the infusion line requires opening the door;
reading a medication delivery device identifier affixed to a surface of the medication delivery device that is accessible when the door of the medication delivery device is opened and not accessible when the door of the medication delivery device is not opened, the medication delivery device identifier including information representing an identity of the medication delivery device;
reading a medication source identifier affixed to a medication source in communication with the infusion line installed in the medication delivery device, the medication source identifier including information representing an identity of the medication;
associating the medication delivery device with the medication source; and after associating the medical delivery device with the medication source, prompting with the controller a care giver to provide values of operating parameters associated with the medication to be delivered to the medication delivery device to operate the medication delivery device.
2. The method of claim 1, further comprising:
determining if more than one door of any of the plurality of medication delivery devices are open; and when more than one door is determined to be open in response to the determining step, providing an alert that more than one door is open.
determining if more than one door of any of the plurality of medication delivery devices are open; and when more than one door is determined to be open in response to the determining step, providing an alert that more than one door is open.
3. The method of claim 1 or 2, further comprising:
detecting a door opening after initiating delivery of the medication;
providing an alert that a door has been opened;
requiring that the medication delivery device identifier affixed to the medication delivery device and the medication source identifier affixed to the medication source be read again before medication delivery may be restarted.
detecting a door opening after initiating delivery of the medication;
providing an alert that a door has been opened;
requiring that the medication delivery device identifier affixed to the medication delivery device and the medication source identifier affixed to the medication source be read again before medication delivery may be restarted.
4. The method of any one of claims 1 to 3, wherein at least one of the medication delivery device identifier and the medication source identifier comprises a barcode.
5. The method of any one of claims 1 to 3, wherein at least one of the medication delivery device identifier and the medication source identifier comprises an RFID device.
6. A system for associating a medical delivery device with a medication source, comprising:
a medication source;
a medication delivery device, wherein the medication source is operatively connected to the medication delivery device at a connection point for delivery of medication to a patient and the medication delivery device comprises a door which is opened to access the connection point;
a medication delivery device identifier disposed on the medication delivery device, the medication delivery device identifier including information providing an identification of the medication delivery device, wherein the medication delivery device identifier is readable when the door is opened, and not readable when the door is closed;
a medication source identifier disposed on the medication source, the medication source identifier including information providing an identification of medication contained in the medication source;
an identifier reader configured to read the medication delivery device identifier and the medication source identifier and to retrieve the identification information included in each of the medication delivery device identifier and the medication source identifier;
input means for inputting values of device operating parameters in operable communication with the medication delivery device; and a processor in operable communication with the identifier reader and the medication delivery device, the processor programmed to receive the retrieved identification information, associate the medication source with the medication delivery device, receive the values of device operating parameters from the input means after associating the medication source with the medication delivery device, communicate the values of device operating parameters to the medication delivery device and operate the medication delivery device in accordance with the values of device operating parameters.
a medication source;
a medication delivery device, wherein the medication source is operatively connected to the medication delivery device at a connection point for delivery of medication to a patient and the medication delivery device comprises a door which is opened to access the connection point;
a medication delivery device identifier disposed on the medication delivery device, the medication delivery device identifier including information providing an identification of the medication delivery device, wherein the medication delivery device identifier is readable when the door is opened, and not readable when the door is closed;
a medication source identifier disposed on the medication source, the medication source identifier including information providing an identification of medication contained in the medication source;
an identifier reader configured to read the medication delivery device identifier and the medication source identifier and to retrieve the identification information included in each of the medication delivery device identifier and the medication source identifier;
input means for inputting values of device operating parameters in operable communication with the medication delivery device; and a processor in operable communication with the identifier reader and the medication delivery device, the processor programmed to receive the retrieved identification information, associate the medication source with the medication delivery device, receive the values of device operating parameters from the input means after associating the medication source with the medication delivery device, communicate the values of device operating parameters to the medication delivery device and operate the medication delivery device in accordance with the values of device operating parameters.
7. The system of claim 6, wherein the medication source identifier is a barcode.
8. The system of claim 6 or 7, wherein the medication source identifier is an RFID device.
9. The system of any one of claims 6 to 8, wherein the medication delivery device identifier is a barcode.
10. The system of claim any one of claims 6 to 9, wherein the medication delivery device identifier is an RFID device.
11. The system of any one of claims 6 to 10, further comprising a patient identifier to including information providing an identification of a patient and a controller, wherein the controller is configured to:
compare the information associated with an identification of the patient to the information associated with the identification of the medication; and provide an alert signal if the comparison does not satisfy a predetermined condition;
the identifier reader is configured to read the patient identifier and retrieving the identification of the patient;
read the medication delivery device identifier associated with the identification of the medication delivery device; and the controller is configured to:
assign the medication delivery device to the medication to be delivered to the patient; and prompt, after assigning the medication delivery devices, a caregiver to enter into the medication delivery device operating parameters associated with the medication to program the medication delivery device to deliver the medication in accordance with the operating parameters.
compare the information associated with an identification of the patient to the information associated with the identification of the medication; and provide an alert signal if the comparison does not satisfy a predetermined condition;
the identifier reader is configured to read the patient identifier and retrieving the identification of the patient;
read the medication delivery device identifier associated with the identification of the medication delivery device; and the controller is configured to:
assign the medication delivery device to the medication to be delivered to the patient; and prompt, after assigning the medication delivery devices, a caregiver to enter into the medication delivery device operating parameters associated with the medication to program the medication delivery device to deliver the medication in accordance with the operating parameters.
12. The system of any one of claims 6 to 11, further comprising:
an infusion line, the infusion line in fluid communication with the medication source and configured to be installed into the medication delivery device at the connection point in a manner where the medication delivery device engages the infusion line to cause an infusion fluid within the infusion line to be delivered to the patient.
an infusion line, the infusion line in fluid communication with the medication source and configured to be installed into the medication delivery device at the connection point in a manner where the medication delivery device engages the infusion line to cause an infusion fluid within the infusion line to be delivered to the patient.
13. The system of claim 12, further comprising a controller to allow the door of one medication delivery device to be opened at any given time.
14. The system of any one of claims 6 to 12, wherein the connection point comprises a pumping portion for engaging an infusion line.
15. The system of claim 14, wherein the pumping portion comprises a peristaltic pump head.
16. The system of claim 14, wherein the pumping portion comprises pumping fingers.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/077,369 US20060206356A1 (en) | 2005-03-09 | 2005-03-09 | Line verification for multi-pump arrays |
| US11/077,369 | 2005-03-09 | ||
| PCT/US2006/008136 WO2006098960A1 (en) | 2005-03-09 | 2006-03-07 | Line verification for multi-pump arrays |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2600867A1 CA2600867A1 (en) | 2006-09-21 |
| CA2600867C true CA2600867C (en) | 2014-11-18 |
Family
ID=36390219
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2600867A Active CA2600867C (en) | 2005-03-09 | 2006-03-07 | Line verification for multi-pump arrays |
Country Status (9)
| Country | Link |
|---|---|
| US (1) | US20060206356A1 (en) |
| EP (1) | EP1871443A1 (en) |
| JP (2) | JP2008532635A (en) |
| AU (1) | AU2006223460B2 (en) |
| CA (1) | CA2600867C (en) |
| NO (1) | NO20074400L (en) |
| NZ (1) | NZ560952A (en) |
| WO (1) | WO2006098960A1 (en) |
| ZA (1) | ZA200707199B (en) |
Families Citing this family (46)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7860583B2 (en) | 2004-08-25 | 2010-12-28 | Carefusion 303, Inc. | System and method for dynamically adjusting patient therapy |
| US9741001B2 (en) | 2000-05-18 | 2017-08-22 | Carefusion 303, Inc. | Predictive medication safety |
| US11087873B2 (en) | 2000-05-18 | 2021-08-10 | Carefusion 303, Inc. | Context-aware healthcare notification system |
| US10062457B2 (en) | 2012-07-26 | 2018-08-28 | Carefusion 303, Inc. | Predictive notifications for adverse patient events |
| US9427520B2 (en) | 2005-02-11 | 2016-08-30 | Carefusion 303, Inc. | Management of pending medication orders |
| WO2001088828A2 (en) | 2000-05-18 | 2001-11-22 | Alaris Medical Systems, Inc. | Distributed remote asset and medication management drug delivery system |
| US9069887B2 (en) | 2000-05-18 | 2015-06-30 | Carefusion 303, Inc. | Patient-specific medication management system |
| US10353856B2 (en) | 2011-03-17 | 2019-07-16 | Carefusion 303, Inc. | Scalable communication system |
| WO2003026558A2 (en) * | 2001-09-24 | 2003-04-03 | Scott Laboratories, Inc. | Methods and apparatuses for assuring quality and safety of drug administration and medical products and kits |
| DE602006014838D1 (en) * | 2005-04-06 | 2010-07-22 | Mallinckrodt Inc | A system for managing information regarding a syringe and a medical fluid |
| AU2006244085B2 (en) * | 2005-05-10 | 2012-12-13 | Carefusion 303, Inc. | Medication safety system featuring a multiplexed RFID interrogator panel |
| US8057679B2 (en) | 2008-07-09 | 2011-11-15 | Baxter International Inc. | Dialysis system having trending and alert generation |
| US10089443B2 (en) | 2012-05-15 | 2018-10-02 | Baxter International Inc. | Home medical device systems and methods for therapy prescription and tracking, servicing and inventory |
| US9480789B2 (en) | 2009-06-01 | 2016-11-01 | Ethicon Endo-Surgery, Inc. | Method and sedation delivery system including a pump assembly and a co-formulation of first and second drugs |
| US9242042B2 (en) * | 2009-07-21 | 2016-01-26 | Ethicon Endo-Surgery, Inc. | Drug delivery system including a drug-container holder and a pump assembly |
| US8945066B2 (en) | 2009-11-06 | 2015-02-03 | Crisi Medical Systems, Inc. | Medication injection site and data collection system |
| EP2504784A2 (en) | 2009-11-27 | 2012-10-03 | Bayer Intellectual Property GmbH | Injector system |
| JP2011212045A (en) * | 2010-03-31 | 2011-10-27 | Terumo Corp | Integrated circuit and medical equipment using the same |
| US9101534B2 (en) | 2010-04-27 | 2015-08-11 | Crisi Medical Systems, Inc. | Medication and identification information transfer apparatus |
| US10492991B2 (en) | 2010-05-30 | 2019-12-03 | Crisi Medical Systems, Inc. | Medication container encoding, verification, and identification |
| US9514131B1 (en) | 2010-05-30 | 2016-12-06 | Crisi Medical Systems, Inc. | Medication container encoding, verification, and identification |
| CN103153361B (en) * | 2010-09-29 | 2016-01-20 | 泰尔茂株式会社 | Medical pump host rack and control method thereof |
| JP5784918B2 (en) * | 2011-02-08 | 2015-09-24 | テルモ株式会社 | Medical pump system and medical pump mounting rack |
| US8567681B2 (en) | 2011-03-22 | 2013-10-29 | Carefusion 303, Inc. | Displaying a barcode on a display of an infusion pump |
| US9078809B2 (en) | 2011-06-16 | 2015-07-14 | Crisi Medical Systems, Inc. | Medication dose preparation and transfer system |
| US9744298B2 (en) | 2011-06-22 | 2017-08-29 | Crisi Medical Systems, Inc. | Selectively controlling fluid flow through a fluid pathway |
| US10293107B2 (en) | 2011-06-22 | 2019-05-21 | Crisi Medical Systems, Inc. | Selectively Controlling fluid flow through a fluid pathway |
| JP5985848B2 (en) * | 2012-03-22 | 2016-09-06 | テルモ株式会社 | Medical pump and control method thereof |
| NZ709436A (en) | 2012-11-13 | 2017-11-24 | Baxter Healthcare Sa | Infusion line management system |
| US10430554B2 (en) | 2013-05-23 | 2019-10-01 | Carefusion 303, Inc. | Medication preparation queue |
| US11182728B2 (en) | 2013-01-30 | 2021-11-23 | Carefusion 303, Inc. | Medication workflow management |
| DE102013002231A1 (en) * | 2013-02-11 | 2014-08-14 | Fresenius Medical Care Deutschland Gmbh | Apparatus and method for generating and displaying graphics encodings specific to medical devices and medical treatments |
| US10143830B2 (en) | 2013-03-13 | 2018-12-04 | Crisi Medical Systems, Inc. | Injection site information cap |
| EP2973366B1 (en) | 2013-03-13 | 2020-08-19 | Carefusion 303 Inc. | Patient-specific medication management system |
| CN105074766A (en) | 2013-03-13 | 2015-11-18 | 康尔福盛303公司 | Predictive medication safety |
| US8998100B2 (en) * | 2013-06-26 | 2015-04-07 | Carefusion 303, Inc. | Infusion system configured for transfer of data |
| CN106687960B (en) * | 2014-07-22 | 2021-04-30 | 美国安进公司 | System and method for detecting activation of a medical delivery device |
| EP2987517B1 (en) * | 2014-08-21 | 2020-01-08 | Micrel Medical Devices S.A. | Medication infusion safety device with reservoir recognition and connection verification |
| US9505233B2 (en) | 2014-10-10 | 2016-11-29 | Becton, Dickinson And Company | Tensioning control device |
| EP3804787B1 (en) | 2014-10-10 | 2023-06-07 | Becton, Dickinson and Company | Syringe labeling device |
| CN116206744A (en) | 2015-06-25 | 2023-06-02 | 甘布罗伦迪亚股份公司 | Medical device systems and methods with distributed databases |
| JP6622544B2 (en) * | 2015-10-07 | 2019-12-18 | 日本光電工業株式会社 | Biological signal measuring apparatus and biological signal measuring system |
| AU2017381172A1 (en) | 2016-12-21 | 2019-06-13 | Gambro Lundia Ab | Medical device system including information technology infrastructure having secure cluster domain supporting external domain |
| EP3388095B1 (en) * | 2017-04-12 | 2024-01-24 | Micrel Medical Devices S.A. | Infusion pump system |
| CN114728121A (en) * | 2019-11-08 | 2022-07-08 | 百时美施贵宝公司 | System for verifying accuracy of serially connected drug modules in a combination drug delivery device |
| WO2021211735A1 (en) * | 2020-04-15 | 2021-10-21 | Carefusion 303, Inc. | Infusion pump administration system |
Family Cites Families (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6241704B1 (en) * | 1901-11-22 | 2001-06-05 | Sims Deltec, Inc. | Drug pump systems and methods |
| IL74236A (en) * | 1984-02-08 | 1990-07-12 | Omni Flow Inc | Infusion system having plural fluid input ports and at least one patient output port |
| US4853871A (en) * | 1987-04-06 | 1989-08-01 | Genex Corporation | Computer-based method for designing stablized proteins |
| US4853521A (en) * | 1987-12-28 | 1989-08-01 | Claeys Ronald W | System for verifying and recording drug administration to a patient |
| US4978335A (en) * | 1989-09-29 | 1990-12-18 | Medex, Inc. | Infusion pump with bar code input to computer |
| FR2690622B1 (en) * | 1992-04-29 | 1995-01-20 | Chronotec | Programmable ambulatory infusion pump system. |
| EP0655107B1 (en) * | 1992-06-09 | 2002-10-16 | Baxter International Inc. | Programmable infusion pump with interchangeable tubing |
| US5376070A (en) * | 1992-09-29 | 1994-12-27 | Minimed Inc. | Data transfer system for an infusion pump |
| DE69329774T2 (en) * | 1992-10-15 | 2001-06-21 | Gen Hospital Corp | INFUSION PUMP WITH ELECTRONICALLY LOADABLE MEDICINE LIBRARY |
| US5378231A (en) * | 1992-11-25 | 1995-01-03 | Abbott Laboratories | Automated drug infusion system |
| US5368562A (en) * | 1993-07-30 | 1994-11-29 | Pharmacia Deltec, Inc. | Systems and methods for operating ambulatory medical devices such as drug delivery devices |
| US5573506A (en) * | 1994-11-25 | 1996-11-12 | Block Medical, Inc. | Remotely programmable infusion system |
| US6671563B1 (en) * | 1995-05-15 | 2003-12-30 | Alaris Medical Systems, Inc. | System and method for collecting data and managing patient care |
| US5885245A (en) * | 1996-08-02 | 1999-03-23 | Sabratek Corporation | Medical apparatus with remote virtual input device |
| US5984893A (en) * | 1997-03-27 | 1999-11-16 | Ward; Roger T. | Blood infusion control system |
| JP3821411B2 (en) * | 1997-10-14 | 2006-09-13 | 株式会社大井製作所 | Automotive lock detection switch |
| US6110152A (en) * | 1998-01-13 | 2000-08-29 | Minimed Inc. | Medication cartridge for an electronic pen-type injector, infusion pump, electronic delivery device, or the like, and method of making the same |
| US7645258B2 (en) * | 1999-12-01 | 2010-01-12 | B. Braun Medical, Inc. | Patient medication IV delivery pump with wireless communication to a hospital information management system |
| US6790198B1 (en) * | 1999-12-01 | 2004-09-14 | B-Braun Medical, Inc. | Patient medication IV delivery pump with wireless communication to a hospital information management system |
| US6519569B1 (en) * | 1999-12-01 | 2003-02-11 | B. Braun Medical, Inc. | Security infusion pump with bar code reader |
| WO2001045774A1 (en) | 1999-12-22 | 2001-06-28 | Catharsis Medical Technology, Inc. | Adverse drug event monitoring |
| JP4055926B2 (en) * | 2000-08-14 | 2008-03-05 | テルモ株式会社 | Infusion pump |
| US7317967B2 (en) * | 2001-12-31 | 2008-01-08 | B. Braun Medical Inc. | Apparatus and method for transferring data to a pharmaceutical compounding system |
| US6985870B2 (en) * | 2002-01-11 | 2006-01-10 | Baxter International Inc. | Medication delivery system |
| US20030141981A1 (en) * | 2002-01-29 | 2003-07-31 | Tuan Bui | System and method for operating medical devices |
| US7935081B2 (en) * | 2004-08-31 | 2011-05-03 | Ethicon Endo-Surgery, Inc. | Drug delivery cassette and a medical effector system |
-
2005
- 2005-03-09 US US11/077,369 patent/US20060206356A1/en not_active Abandoned
-
2006
- 2006-03-07 JP JP2008500849A patent/JP2008532635A/en active Pending
- 2006-03-07 WO PCT/US2006/008136 patent/WO2006098960A1/en active Application Filing
- 2006-03-07 AU AU2006223460A patent/AU2006223460B2/en active Active
- 2006-03-07 EP EP06737320A patent/EP1871443A1/en not_active Withdrawn
- 2006-03-07 NZ NZ560952A patent/NZ560952A/en not_active IP Right Cessation
- 2006-03-07 CA CA2600867A patent/CA2600867C/en active Active
-
2007
- 2007-08-24 ZA ZA200707199A patent/ZA200707199B/en unknown
- 2007-08-29 NO NO20074400A patent/NO20074400L/en not_active Application Discontinuation
-
2011
- 2011-06-27 JP JP2011141836A patent/JP2011183211A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| NZ560952A (en) | 2011-06-30 |
| JP2008532635A (en) | 2008-08-21 |
| WO2006098960A1 (en) | 2006-09-21 |
| AU2006223460A1 (en) | 2006-09-21 |
| ZA200707199B (en) | 2008-07-30 |
| US20060206356A1 (en) | 2006-09-14 |
| NO20074400L (en) | 2007-10-08 |
| EP1871443A1 (en) | 2008-01-02 |
| JP2011183211A (en) | 2011-09-22 |
| AU2006223460B2 (en) | 2012-01-19 |
| CA2600867A1 (en) | 2006-09-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2600867C (en) | Line verification for multi-pump arrays | |
| US10064579B2 (en) | System and method for dynamically adjusting patient therapy | |
| US8359338B2 (en) | System and method for managing medical databases for patient care devices | |
| AU2006213664B2 (en) | Identification system and method for medication management | |
| US7384410B2 (en) | System and method for managing patient care | |
| US8235938B2 (en) | Method of providing care to a patient | |
| EP1944709A1 (en) | Identification system and method for medication management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |