CA2008715A1 - Infusion fluid management system - Google Patents
Infusion fluid management systemInfo
- Publication number
- CA2008715A1 CA2008715A1 CA002008715A CA2008715A CA2008715A1 CA 2008715 A1 CA2008715 A1 CA 2008715A1 CA 002008715 A CA002008715 A CA 002008715A CA 2008715 A CA2008715 A CA 2008715A CA 2008715 A1 CA2008715 A1 CA 2008715A1
- Authority
- CA
- Canada
- Prior art keywords
- infusion
- data
- alarm
- infusing
- priority
- 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.)
- Abandoned
Links
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/168—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
- A61M5/16831—Monitoring, detecting, signalling or eliminating infusion flow anomalies
-
- 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/168—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
- A61M5/172—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body electrical or electronic
- A61M5/1723—Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body electrical or electronic using feedback of body parameters, e.g. blood-sugar, pressure
-
- 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
-
- 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
- G16H70/00—ICT specially adapted for the handling or processing of medical references
- G16H70/40—ICT specially adapted for the handling or processing of medical references relating to drugs, e.g. their side effects or intended usage
-
- 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
- A61M2005/14208—Pressure infusion, e.g. using pumps with a programmable infusion control system, characterised by the infusion program
-
- 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/18—General characteristics of the apparatus with alarm
-
- 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/35—Communication
- A61M2205/3576—Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
-
- 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
-
- 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
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S128/00—Surgery
- Y10S128/12—Pressure infusion
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S128/00—Surgery
- Y10S128/13—Infusion monitoring
Abstract
ABSTRACT
An infusion management and pumping system is disclosed.
Infusion prescriptions are generated and monitored by a pharmacy management system. Labels for each infusion to be given to a patient are generated and printed in a bar code format. Each label contains data regarding a prescribed infusion program, including the drug or drugs to be infused, the infusion regimen, the expiration date, and the patient to whom the infusion is to be administered. The management system checks for incompatibilities between drugs that are being prescribed for simultaneous infusion. Each label generated by the management system is attached to the container which holds the infusion solution. The data on the label is transferred to an infusion pumping system by a bar code reader at the infusion pumping system. The pumping system checks that all necessary data has been entered. During operation, the pumping system checks for a variety of alarm conditions and stores any alarms in a ranking according to urgency. The infusion pumping system is responsive to remote or biofeedback instructions to alter the planned infusion program. Central computer records processing receives infusion data and provides infusion, inventory, and use analysis.
An infusion management and pumping system is disclosed.
Infusion prescriptions are generated and monitored by a pharmacy management system. Labels for each infusion to be given to a patient are generated and printed in a bar code format. Each label contains data regarding a prescribed infusion program, including the drug or drugs to be infused, the infusion regimen, the expiration date, and the patient to whom the infusion is to be administered. The management system checks for incompatibilities between drugs that are being prescribed for simultaneous infusion. Each label generated by the management system is attached to the container which holds the infusion solution. The data on the label is transferred to an infusion pumping system by a bar code reader at the infusion pumping system. The pumping system checks that all necessary data has been entered. During operation, the pumping system checks for a variety of alarm conditions and stores any alarms in a ranking according to urgency. The infusion pumping system is responsive to remote or biofeedback instructions to alter the planned infusion program. Central computer records processing receives infusion data and provides infusion, inventory, and use analysis.
Description
7~i F_E _ QE~ LNv~IoN
This invention relates to systems for infusing fluids into a patient and more particularly to systems for managing and analysis of prescribed infusion programs.
BACKGROUND
Intravenous infusion therapy is often necessary to administer medications or other fluids directly into the circulatory system of a patient. Epstein, et al., U.S. Patent No. 4,696,671, assigned to the current assignee and incorporated herein by reference, discloses an infusion pumping system capable of administering multiple infusates at individually programmable rates, volumes, and sequences. This system uses one or more single pump systems each of which pumps all plural fluids through one or more fluid input ports and one outlet port. This pump system increases the ability to administer complex programs of infusion therapies and reduces the time and labor required by nurses or other health practitioners in setting up and monitoring infusions while improving the reliability of proper infusion.
"..~
s One or more infusions to be administered to a patient are prescribed by the patient's physician. A pharmacy, generally located within the patient's hospital or clinic, makes up the infusion according to the physician's prescription. The pharmacist places the infusion solution in a bag, bottle, syringe, or other container and labels the container. The label contains data to identify the patient, physician, medications prescribed, and a control number. The label is generally typed or printed in human readable characters only. The container is transported to the patient's location. A nurse or other health practitioner hangs the container from a rack. The nurse runs a tube from the container to the infusion pumping system, such as that disclosed by Epstein, et al. for pumping or gravity feeding the infusion solution to the patient. The nurse then enters all data regarding the infusion program manually, generally through a keyboard, into the pumping system. The data includes, for example, the rate of infusion, the total volume to be infused, and which of the plural lines the infusion is to use.
Hospitals maintain a large inventory of drugs that are kept up to date in volume and availability and size scaling. In addition, each hospital may develop its own vocabulary of drug identification and relies on pharmacist expertise to prevent incompatible drug administration. Manual treatment of this type -- 3 ~
., .
.
.
.:
This invention relates to systems for infusing fluids into a patient and more particularly to systems for managing and analysis of prescribed infusion programs.
BACKGROUND
Intravenous infusion therapy is often necessary to administer medications or other fluids directly into the circulatory system of a patient. Epstein, et al., U.S. Patent No. 4,696,671, assigned to the current assignee and incorporated herein by reference, discloses an infusion pumping system capable of administering multiple infusates at individually programmable rates, volumes, and sequences. This system uses one or more single pump systems each of which pumps all plural fluids through one or more fluid input ports and one outlet port. This pump system increases the ability to administer complex programs of infusion therapies and reduces the time and labor required by nurses or other health practitioners in setting up and monitoring infusions while improving the reliability of proper infusion.
"..~
s One or more infusions to be administered to a patient are prescribed by the patient's physician. A pharmacy, generally located within the patient's hospital or clinic, makes up the infusion according to the physician's prescription. The pharmacist places the infusion solution in a bag, bottle, syringe, or other container and labels the container. The label contains data to identify the patient, physician, medications prescribed, and a control number. The label is generally typed or printed in human readable characters only. The container is transported to the patient's location. A nurse or other health practitioner hangs the container from a rack. The nurse runs a tube from the container to the infusion pumping system, such as that disclosed by Epstein, et al. for pumping or gravity feeding the infusion solution to the patient. The nurse then enters all data regarding the infusion program manually, generally through a keyboard, into the pumping system. The data includes, for example, the rate of infusion, the total volume to be infused, and which of the plural lines the infusion is to use.
Hospitals maintain a large inventory of drugs that are kept up to date in volume and availability and size scaling. In addition, each hospital may develop its own vocabulary of drug identification and relies on pharmacist expertise to prevent incompatible drug administration. Manual treatment of this type -- 3 ~
., .
.
.
.:
2~3~3~
of infusion system data is disadvantageous because it is labor and time consuming and the possibility for incorrect data treatment is greater.
~MMARY OF THE I NVENT I ON
The infusi~n system of the present invention contemplates a system for managin~ the infusion of one or more drug formulations to a patient from the make up of the infusion in the Dharmacy to the generation of a report Cor hospital records ar.~ analysis after the infusion is complete.
The infusion management system of the present invention provides a computer-based pharmacy management system, located in a hospital or clinic's pharmacy, remote from the infusion pumping system. All prescriptions for intravenous infusions are entered into the system when the pharmacist makes up the prescribed formulation. The system prompts the pharmacist or other user for the necessary patient identification data and prescription data, such as the drug to be infused, the carrier solution if any, the concentration of the drug in the carrier solution, and the infusion regimen (continuous, maintenance, or intermittent and rate, volume and infusion frequency). The data entered can be subsequently edited. After all data has been `. ~ : ' .` : `
correctly entered, the system makes a bar code readable label which is applied to the cutside of the container in ~lhich the infusion solution is placed.
The pharmacy rnanagement system also includes a drug database which stores drugs by name, mnemonic, and I.D. number.
The database also includes a matrix of drug incompatibility. If two incompatible dru~s are to be mixed in a single solution, the system alerts the user.
The management system also produces reports to be included ~n ~he ~atient's ~ecord or chart. Further, the management system tracks the inventory of drugs by monitoring the precise amount ~f drugs used and the nature of this drug source. This data may be transferred to the hospital's existing drug inventory control system for more accurate monitoring and ordering of drugs.
The labeled container containing the infusion formulation is transferred to the patient by usual methods either within the hospital or to the patient's home in the case of remote infusion control. The user, a nurse or other health practitioner, using a bar code reader associated with each pump s~stem, enters the data from the formulation container label into the infusion pumping system where it is displayed and accepted. The pumps serial port may be used for this purpose. Data can also be . ' ' - ' ~ .
- . : ' '. ' ` , , ~ : .
entered manually in addition to or in lieu of entry by bar code reader. The pumping system prompts the user for any necessary data that is rnissing from the read label but required by the pumping system before the infusion program can begin. To accommodate emergency situations, the pumping system allows an overrider. A~ter entering the data on the solution container, the user completes ~he infus~on programming by entering the start time. A delayed start time provides flexibility in administrati~n. Preprogramming of functions is useful when the user is expecting I pat-ent to arrive from, for example, an operating room and wants to get the infusion up in advance.
Alternatively, an advance set-up reduces the risk of error due to setting up an infusion too quickly and allows the patient to be connected to the infusion system more rapidly upon arrival.
The infusion pumping system has several input lines for infusing more than one formulation. A similar procedure is used to program each line on the pumping system and the pump itself can identify inappropriately scheduled drugs.
The infusion pumping system performs several checJss to ensure the data is correct. It verifies that the patient identification is correct and that the patient is not allergic to any of the medications in the solutions and allows the user to confirm that all data is correct. The user can override the data on the bar code label by manually entering different data.
:: , The infusion pumping system of the present invention also contemplates an improved alarm handler system. During operation, the pumping system can yenerate a variety of alarm conditions of varying severity. Some alarm conditions, such as various pump failures, unlocked cassette, and patient line occlusion require stopping all pumping immediately. Other alarms, such as air in a secondary input line merely require temporarily holding the pumping on that line until the alarm condition has been cleared while other lines continue to infuse. Finally, alarms such as an empty bottle on one of the input lines do not effect pumping at all. Also, several alarms can exist simultaneously if, for example, a second ala~m occurs before a first alarm has been cleared.
The present invention pro~ides an alarm handler capable of dealing with many alarms at once. The alarm handler ranks the alarms by degree of urgency. The alarms are stored in a stack with the most urgent presented to the user for clearing first. Alarms of the same degree of urgency are stored in reverse chronological order. An audible tone alerts the user to the existence of one or more alarm conditions. The system, upon prompting by the user, presents the alarms to the user for action.
The infusion pumping system is also responsive to remote or biofeedback instructions to alter a planned infusion program.
, :
"'' ` ' ~. .
2~ 5 DESCRIPTION OF THE DRAWINGS
Fig. 1 shows a schematic block diagram of the fluid management and pumping system of the present invention;
Fig. lA shows a bar coded label of the present fluid management system;
Figs. 2-29 are flow charts illustrating the pharmacy management system of the present invention;
Figs. 30-34 are flow charts illustrating data entry into the fluid pumping system of the present invention;
Fig. 35 is a diagram showing the state of the pumping system after various alarm conditions;
Fig. 36 is an alarm priority table;
Fig. 37 is a schematic block diagram of the biofeedback remote programming system of the present invention;
Fig. 38 is a flow chart illustrating the biofeedback/remote programming system; and Figs. 38-42 are flow charts illustrating the biofeedback~remote programming system.
;`
~ . ,. . . : . -- : , . , ' ,.
.
2~
DETAILED DESCRIPTION OF THE INVENTI~N
The present invention is shown generally in block diagram format in Fig. 1. A pharmacy manag~ment system 20 includes a computer keyboard 20-1 for input, bar code reader 20-2, database 20-3 and a printer 20-4 for generating a bar coded label to be placed on the container for an intravenous solution made up by the pharmacy of a hospital or clinic. Since the pharmacy management s~stem 20 accurately tracks the quantities of drugs used, it ~ay communicate through an interface 22 with the hospital's existing computer based pharmacy inventory control syste~ 29 ~or the exchange of hospital specific inventory and drug labelling data.
A hospital typically has a pre-existing computerized administration system 26. The pharmacy management system 20 communicates through interface 28 with this pre-existing hospital administration system 26. The hospital administration system also eommunicates through an interface 30 with the hospital's pre-existing inventory control system 24.
Labels 32 for infusion formulation generated by the pharmacy management system 20 from keyboard bar code input of prescriptions are transported to the appropriate patient 34 infusion pumping systems 38 and 40 (as shown in the above . ` ` '`` ` ` ` ~ ~
: ` ~
. .
referenced patent) as shown by the dotted lines in Fig. 1.
While only two pati~nts 34, 36 and associated pumping systems 38 and 40 are shown in Fig. 1, each hospital will generall~ have many such patients. ~ach infusion pumping system 38, 40 includes a bar code reader 38-1 and 90-1 coupled into the database of the pump through a parallel data port or an RS-232 serial port shown in Epstein, et al.. The label is read by the bar code reader and all the nformation on the label is transferred to the in~usion pumping system in the same manner as manual data entry occurs.
The infusion management system also includes a remote/biofeedback control system 42 which operates through an interface 94. In biofeedback applications information is sensed by patient sensors 34-1 and 36-2, such as blood pressure or glucose levels, and instructions are sent to the infusion pumping systems 38, 40 to alter the planned program of infusion in response to the sensed information. With the remote capabilities of control system 42, a patient may remain at home. Instructions for programming an infusion pumping system are sent over a phone line communication path 42-1 to a home system 42-2 of pumping systems by the control system 42.
'' . , '' j':
'7~
The pharmacy rnanagement system 20 may be described with more detail by reference to the flow charts of Figs. 2-29.
Specifically, the pharmacy management system provides a program for encoding in~usion delivery instructions ~or intra~enous solutions in a bar code format. The system takes the operator through a series of screens and menus which request the information necessary to program the infusion pumping system. A
final screen summarizes all the data that has been entered, requests confirmation from the operator, and provides the option for making a label. The delivery instructions are printed in bar code rormat as well as in human readable format on the label.
The system can be run on commercially available computers. Preerably, the system includes a monitor 20 5 for displaying the data screens and a keyboard 20-l for entering the data.
The flow chart of Fig. 2 shows the overall operation of entering data for each intravellous solution to be infused into a patient. The encoding program is initialized in step 102 by booting up the computer with the pharmacy management system installed in the computer's memory and typing an appropriate command including calendar entry. The system invokes a system menu processing routine in step 104, which gives the user a choice of several tasks to perform. The system menu processing .
2~
routine is described in greater detail by reference to the flow chart of Fig. 3. lhe system displays the main menu 106. The main menu displayed to the user allows the choice of editing previous labels, all on specific patient scripts, processing new entries, printing all on a range of labels, generating a report, archiving the database, batch delete or restoring the database.
The user makes a selection 108 and the system returns the selection in step 109 and returns yrocessing to the main program. The user's selection is then processed in step 112 in Fig. 2. After the user's selection has been processed, the system gives the user the option of quitting or performinq another task. If the user wants to perform another task, the system returns to the step of invoking the system menu processing in step 104 to allow the user another selection. If the user quits, the system invokes system termination, as shown by block 116.
The task of processinq previous entries is shown in the flow chart of Fig. 4. This task allows the user to call up infusions that have been previously entered and are due to expire on a specified date. The user then determines whether the infusion should be renewed. If the infusion is to be renewed, the system saves the patient's records. As shown by the flow chart of Fig. 4, this routine retrieves the date from ,.; . . .~ . ' :
., : i 971~
the system in step 120. It clears the screen in step 122 and a work space in ~AM, as shown by steps 124 and 126. The system then executes a patient scan 128, in which it searches ~or infusions due to expire that date. It displays each infusion record on the screen and provides the user with the option of renewing the i~fusi~n by printing a bar coded label. A~ter the scan is complete, and all bar coded labels printed, the routine sets return status to "~K," enabling processing t~ return to the routine of Fig. 2.
The processing of new infusion entries is shown by the flow charts of Figs. 5-17. The system's ~irst step is to put all existing records, including records saved in the "processing previous entries" routine, in a workspace in RAM 20-3 in step 132. The system then calls a routine to process a patient record 134, shown in more detail in Figs. 6 and 7. The system will display a screen asking for patient identification data in step 150 and will set the data mode to allow input in step 152.
The patient may be identified by name or identification number.
If the patient has previously been recorded in the system, entering one of the ~atient's name or identification number will cause any other patient data in the patient's record stored in RAM 20-3 to appear on the screen. The patient identification screen also contains data fields requesting or displaying data -- 1~ --' ,~ .
on the patient's room number or other location identifier, total number of intravenous solution labels required by the patient, the patient's physician, and physician identification number.
OncP all the patient identification data corresponding to label fields in a typical label as shown in Fig. lA has been correctly provided, the special function key may be depressed to enter this data and display the next screen 154. The patient data remains displayed in a window at the top of the monitor while the remaining infusion data on the subsequent screens is entered. If the system includes a color monitor, the patient identification screen may change to a different color in step 156; to indicate that it has been entered.
Each patient can receive a number of different drug regimens. Each regimen refers to the delivery instructions for a solution of drugs contained in one intravenous container. As in step 158, the system sets the regimen count to zero. The system then increments the regimen count, in step 160. For the ~irst drug regimen, the regimen count is l. The system clears a work space in RAM, in step 162. The system then makes a control number, in step 164. The control number is for the pharmacy's use in keeping track of all the intravenous solutions it formulates. The next step 166 initializes a default prescription (or script) 166. For example, certain data such as .: ,: , ,: :
i` ~' : , '," .. "
: ~, ~ ;" ' :
'` ' ! : ~: :`
:, the keep vein open (KVO) rate is often the same regardless of the drug. In addition, the expiration date is usually set for one day later but can be adjusted by a higher level of authorization. This data is placed into the system as default data, but it can be changed by the user during the next step of processing the script in step 168.
The procedure involved in processing each prescription is shown with more detail in Figs. 8-16. As shown in Fig. 8, the ~irst step 122 in:tializes the script causing the drug entry screen to appear. ~he system accepts entry of data in each of the data fields in the screen. The data fields include the drug regimen number, the prescription date, the e~piration date, the prescription number, the pharmacy control number, and the drug name, drug nmemonic, and drug identification number, and the drug concentration in a carrier solution. These correspond to fields shown in a sample label in Fig. lA. When the user enters a drug either by name, mnemonic or number, the remaining unentered data previously set up as default data, will automatically be supplied by the system.
- The system then displays a screen asking the user if additives are desired in step 178. If the user selects additives, the additives are processed in step 180 as shown by the flow charts of Figs. 9 and 10. The system initializes the additives by displaying an additive screen in step 182. User - , :
' ~ .
., . ~ . , ' .
, ;,' 2,~ 5 .
input in step 189 allows the user to enter the additi~Jes desired. The system builds an additive list in step 186 simply by adding a new additive to the list in the routine as shown in Fig. 10. The system then updates the script in step la8 to include all the additives. Once all the additives have been processed, the system returns to the routine of Fig. 8, displays the data in a window of a different color to show that all the prescription medication data has been entered in step 190, and continues to the step of processing the infusion in step 199.
The steps of processina the infusion are shown in Fig. 11. The system displays a menu in step 110 for choosing the type of infusion. The infusion types are continuous, maintenance, and intermittent. If continuous infusion is selected, the screen will display data fields for the dose rate and the dose volume and a menu for the selection of the appropriate units. If maintenance infusion is selected, the screen will display data fields for the maintenance rate and total volume and a menu for the selection of the apyropriate units. If intermittent infusion is selected, the screen will display data fields for the volume per dose, the time per dose, the dose rate, the dose frequency, the total number of doses, and whether a dilution or a syringe is desired. Again, the screen will also allow the selection of the desired units. If , , . ~ ", . , .
..
....
: , ; ~
:
, 3~5 dilution is selected, the screen will display data fields for the entry of the dilution rate per dose and ~olume per dose.
After all this data has been entered, the user hits a special ~unction key which allows the system to update the script and store the data in step 116. This data may also be displayed in a red window in step 118.
At this point, all the necessary data for the infusion has been entered into the system. The next step is to generate a label containing the data in both bar code readable and human readable format. The system gets the label instructions in step 196, as shown in Fig. 8 and in flow charts of Figs. 12-17.
The first step of the flow chart of Fig. 12 is to display an option menu in step 202. The options are to make a label, skip making a label, edit a label, or terminate. After a menu option is selected, the processor moves on to the ne~t step of finishing the regimen in step 204.
If the terminate option is selected, the system, as shown in Fig. 13 clears the screen in step 206, sets the data mode to input in step 208, allowing the user to start on a new patient or prescription, and sets the system to terminate the present infusion entry in step 210. Processing is returned to step 198 in Fig. 8. Since termination has been selected, the system quits in step 200. Processin~ then returns to step 168 in -, .
.
: ` , ' `
. .
:, ' , ' , . . .
' . ' , , ' Fig. 6. Since "quit" has been selected, processing ~eturns as shown in Fig. 7 to the ~ain program of Fig. 2 and finally terminates in steps 114, 116.
If, instead, the option to skip making the label is selected, then the system as shown in Fig. 19 clears the screen in step 212 and sets the data mode to input in step 214. This allows the user to continue inputting data on the same patient.
I~ the user elects to edit the data, as shown in Fig. 15, the system clears the screen in step 216, redisplays the patient screen in step 218, and sets the data mode to edit in step 220, allowing the user to edit the data relatin~ to the current patient or prescription. This allows the user to make any changes that may be necessary.
If all the data has been correctly entered, the user can make a label, as shown in Fig. 16. The systern displays a screen in step 222 to allow the user to set the number of copies. The system then generates labels in step 22g, as shown in Fig. 17.
The system formats the data in step 226 in bar code readable and human readable form. The system then prints the label in step 228. A conventional bar code printer may be used. The bar code symbology preferably is three o~ nine (39), an alpha/numeric encoding system with, a high reliability rate (internal check character) as recommended by the Health Industry Business Communications Counsel.
: . , :. ,. ,. ::
., , - : ~ , ; , ; ; ; . . ~, . ~ , ~
.: ,,:. , :
. .
. .
" :: . :
: .
: . . . , - . ~, .. .
The system then makes a log entry and a label in step 230 and prints an additional label in step 240, for example, to attach to the patient's chart. The system then clears the screen in step 242, as shown in Fig. 16, sets the data mode to input in step 244 to allow further input of data, and updates the prescription database in step Z46 by storing the completed prescription in the database. Processing is then returned to step 198 of Fig. 8, where the user is given the option of terminating the input on the present patient or continuing with the present patient by processing a rurther prescription.
If the user selects termination, in step 198, quit is set to yes in step 200. Processing is returned to step 170, as shown in Fig. 6 and the patient screen is redisplayed. If quit, as shown in step 250 of Fig. 7 is selected, the screen is cleared in step 252. Processing returns to the routine shown by the flow chart in Fig. 2. If the user does ~not select termination, in step 2S0 processing returns to step 160 of Fig. 6. The regiment count is incre~ented by one. This allows the user to process a second prescription for the same patient.
The system then goes through the identical steps for any desired number of prescriptions for the particular patient. If the user has finished processing scri~ts for the patient, the system sets a "return" status, which allows processing to return to the main menu.
- . .
- , .
~ further user selection allowed by the system in the routine shown in the ~low chart of Fig. 2 is the rnaking of a patient report. The flow charts of Figs. 1~ and 19 describe this routine. When this option is selected, a report menu is displayed in step 260. The system gets the user selection in step 262 and processes the report in step 264, as shown more fully in Fig. 19. The system displays an input screen in step 266, gets the ~ser~s data in step 268 and loops the database in step in step 270, applying the search criteria input by the user n the ,revious step 268 to the patient script records. The system then prints the report in step 272.
Alternatively, ~he system could interface with the hospital administration system 26, as shown in Fig. 1, and send the report to the hospital administration system.
Typical examples of report generation include a summary over a specified time of all drugs labelled for a patient. Two other options provided in the menu of Fig. 2 are to archive the database or to restore the database. Archiving the database is shown in the flow chart of Fig. 20. The system executes a backup in step 280, generally by storing the database on a floppy disk and returns in step 282 to the main menu. The opposite procedure, shown in Fig. 22, is the restoring of the database to the system. In this routine, the system executes a - .. , . , . ., . ,, , . , . ~
-, .: - , "
,.
, :
, s restore in step 284, generally reading the database from the Eloppy disk into the storage on the system and returns in step 286 to the main menu.
;The system also includes a stored drug table in RAM 20-3. The drug table includes a list of all the drugs used or prescribed for patients in the hospital. The drugs may be stored by drug name, nmemonic, and identification number. The drug table may also include incompatibility data for the drugs.
For example, if a solution containing a mi~ture of two drugs were to cause particles to precipitate, the drugs would be incompatible, since a solution with precipitates would not be suitable for infusion into a patient. The system checks the drug table upon entering new prescriptions for each patient.
The drug table supplies some of the drug data to be included on the label. The drug table may be edited to change data on the drugs included in the database, or to add or delete drugs to and from the database.
Figs. 23-29 show the flow charts for the routines which allow entry, deletion, and editing of the data in the drug database. Fig. 23 shows the flow chart for the main routine.
The first step 302 to initialize the system, gen~rally by typing an appropriate command on the keyboard. The system then invokes the system menu processing in step 304. The user can select ```,f ~
- -' ' `
Z~
from the choices of loadinq the drug file, saving the drug file, printing a drug table, entering drug data, editing drug data, and deleting drug data. After the user rnakes a selection, the system processes the user selection in step 306.
To work on the database, the user must first load the drug file, as shown by the routine cf Fig. 29. The system loads the database in step 312. The system then returns and asks the user whether the user wishes to quit or continue, as shown by step 308. If the user wishes to continue, the system menu processing is once aqain invoked in step 304 allowing the user to make a further selection.
New drug data is entered by the routine shown by the flow chart in Fig. 27. The system displays a drug entry screen in step 3Z2. The user enters data in step 324, and the system puts the entered drug data into the database in step 326. If the user selected the option of editing the drug data, the routine shown in Fig. 28 is followed. The system displays a drug edit screen in step 323. The drug edit screen requests the user to specify a particular dru~ and the system displays the data contained for this dru~ in step 330. The user may then edit the data regarding the specified drug in step 332. After the user has completed editing, the system updates the internal database by storing the edited data. If the user selects the option of !
.. . . " ` :
,, - :` . :~
' ' ` ' ' ' ' '` '' :
: ' ` "~' ` ' ~ '`' ' 7~ ~i deleting a drug from the database, the routine shown in Fig. 29 is followed. The system displays ~ delete drug screen in step 336. The user selects a drug to be deleted. The display shows the drug specified by the user in step 338. The system then asks for verification that the drug is to be deleted in step 340. If the user chooses no, the drug will not be deleted. If the user chooses yes, the drug will be deleted from the database in step 342.
The flow chart of Fig. 25 allows the archiving o a drug database that has ~een recen-ly changed. If this option is selected, the system deletes the old copy of the drug database in step 314. The new copy of the drug database is saved in step 316. The user can also print the drug database, as shown by Fig. 26. If the user selects this option, the system redirects the output to a printer in step 318. The system then loops through the drug database, ~ormatting and printing each entry in step 320.
After each prescription label has been generated by the pharmacy management system, the label is placed on the bag containing the solution to be infused. The bag is carried or transported by the hospital's usual method to the patient's location. The delivery instructions printed on the label on the medication container must be inputted to the infusion pumping : ~ . . ..
~, ~,:
. ~. , , . ~ , , . , , : ~ :
:
, `r system~ The flow charts of Figs . 30-34 describe the process used to enter the data on the labeled medications by bar code reading.
The infusion pumping system generally is a system similar to that described in the above-referenced patent to Epstein, et al. The system contains a housing in which is placed a disposable cassette containing plural input ports and a single patient output port. The medications are hung from a rack and tubing is run from the medication container to one of the input ports. In tha prior art system, A nurse or other heaith practitioner programs the infusion pumping system with the necessary delivery instructions such as dose rate, total volume to be infused, and starting and stopping times. With the system of the present invention, this data has already been encoded on the bar code label attached to the solution container. As shown in Fig. 30, the user initializes the system in step 400, generally by turning on the infusion pumping device, which runs a self test procedure and is then ready to accept input. The user hangs the line medication or medications on the rack in step 402. The user selects the method of inputting the data to the system, either through the bar codes or manually through a keypad as in the prior art systems. If bar code entry is desired, the user depresses an appropriate key : :,: . ;,; . . .
on the keypad in step 404. The user then programs the line processor in step 406 by wanding the bar coded data with a bar code wand 38-2, 40-2~
The button corresponding to the connect line (A-D) is pushed to correlate that regimen to the appropriate line. The infusion pumping system generally contains plural input lines.
If other solutions are to be infused on additional lines, the delivery instructions for those solutions may be entered in the same manner in st~p 408. After all lines have been programmed, the system gives the option of selecting a pre-programmed mode in step 410. The pre-program mode allows the start of the infusion program to be delayed. This is a useful option if the user is expecting the patient to arrive from, for example, an operating room and desires to get the infusions set up in advance. If the pre-program mode is selected, the system will resume the realtime process in step 412 at the appropriate time. When the start time arrives, the system controls the infusion process in step 414 according to the programmed delivery instructions.
Fig. 31 shows the procedure for programming each infusion line, as shown by step 406 of Fig. 30 in more detail. If bar code input has been selected at step in step 404, the user inputs the bar coded data through a conventional bar code - ~5 -., -' ' ~ ;' ' ~ .
2~
reader 38-1, 40-1. Generally, the user passes a bar code ~,and or pen 38-2, 40-2 across the coded data, ~rom right to left or left to right. All the lines must be read. A ~alidity ~heck is made on the data read by the bar code reader, into the infusion pumping system and a "good" beep is provided if the data falls within expected ranges. If the data is not accepted by the bar code wand, the system will respond in a manner which is readily distinguishable ~rom the '-good" beep. Data not accepted by the bar code reader is to be wanded again. If the data continues to be unreadable, Lhe data may be entered through the keypad of the infusion system 38, 40.
The infusion pumping syst~m 38, ~0 includes a database memory 38-4, 40-4, a small screen, generally a liquid crystal display, which prompts the user for the data to be wanded or entered through the keypad. The system will prompt the user for the user's personal identification number. This data may be provided in bar code format on, for e~ample, a nurses badge.
The system will then request entry of the data contained on the solution label. Finally, the patient identification data must be entered. This data may also be in bar code format on the patient's chart or bracelet. The system verifies that the patient identification from the chart or bracelet matches the patient identification on the solution label and provides a mismatch indication.
.: : , , `~ ' , ' ~' '.'. ''... .', '' ' '" ,' ' ; ' ''j . ' ' ' . ' ', , .'' ' ' ', ' `'`` '' `' `''` :,' ' .
.. :, After all the data has been entered, the system checks to see whether all the data has been entered correctly, as shown by step 424. If not, the system prompts ~or any rnissing data in step 9Z6. The manual prompt routine, as shown in Fig. 32, runs through all the necessary data in step 450. For any missing data, it displays a prompt in step 452 requesting entry of the data. The user wands or keys in the data in step 454. At this point, the system may also check the prescribed drugs against the patient's record for allergies to the drugs that have been prerecorded in databases 38-4, 90-4. If any drugs to which the patient is allergic ha~e been prescribed, the pumping system displays a message so informing the user.
The user may edit the data to change the regimen in step 456. Fig. 33 shows a flow chart for the routine the system uses when data is entered by keyboard 38-5, 40-S. The data is entered and the system range checks the data in step 440. Then, the system encodes the event in an I.V. history in step 442 that is maintained for each course of infusion therapy.
After all the data identifying the medications and the infusion data are entered, the system re~uests the user to select an input line in step 428, as shown in Fig. 31. Finally, the system runs through a data confirmation check in step 430.
As shown in Fig. 34, the system checks all the medications in - ' ~ : ' :
: .
"
.. : :
'~ ~
step 442, by displaying the medications to the user who confirms by depression of an appropriate key on the keypad. The system then displays the drug regimen to the user in step 446, ~ho again confirms the drug regimen by depression of the key on the keypad for that purpose (38-5, 40-5). The user can make any changes to the medications or the regimen at this point by manual entry through the keypad. In this manner, a safety check on the data contained on the bar code label is provided. Also, any changes to the infusion therapy can be made. Finally, the systern checks if the infusion is to be a continuous or maintenance infusion in step 432. If not, the system prompts the user for the entry of a start time in step 43~, as shown in Fig. 31. The above procedure is repeated for each solution to be infused on each of the input lines provided on the infusion pumping system.
During the administration of an infusion, various alarm conditions can occur. Alarms can range from a simple audible tone to call the operator back to, for e~ample, start an infusion, to a problem which renders it impossible for fluid to be delivered to the patient. More than one alarm condition can occur at the same time. The present invention provides an improved alarm handler. The alarm handler is best described by reference to Figs. 35 and 36. Each of the various alarms is . . . . .
~ ~ .
. ~: . .
, ~ .
,' ~. ~ ' ' `,, " ' ' '' 2~ s assigned a priority which is used for displaying the alarm conditions to the operator for clearing. When more than one alarm exists at a single time, the alarms are displayed in order of priority, hi~hest priority first. If a subsequent alarm has a higher priority than an existing alarm, the subsequent alarm will be handled before -he earlier alarm. If two alarms have the same priority, the most recent aiarm will be handled first.
The alarms ~ay generally be classified into three distinct types: warnings, pumping alarms, and fluid delivery alarms. Flui( delivery alarms have the highest priority, warninqs the least. Warnings do not change the state of the infusion pumping system and merely alert the operator to a condition. Pumping alarms relate to the ability to pump on one or more of the input lines and may change the state of the device by suspending pumping on one or more of the lines. Fluid delivery alarms occur when fluid cannot be delivered to the patient or when there is the possibility of free flow to the patient.
When an alarm occurs, its time of occurrence is recorded and it is placed on an alarm stack. When the operator arrives to service the alarms~ the alarms are displayed in order of highest priority first and in reverse chronolo~ical order for alarms of the same priority. If one or more lines of the pump .. - `
. . . .: , : :
-`
7~ S
have be~n placed on ~old or pumping has been stopped on alllines, pump operation ~ill not resume until the entire alarm stack has been displayed to the operator and serviced if necessary.
The table of Fig. 6 displays the alarm priorities of the preferred embodiment. The highest priority alarm is the cassette unlocked alarm. When the cassette is unlocked, free flow of a fluid to the ?atient may be possible. Therefore, all infusing lines are placed on hold immediately when the cassette is unlocked.
The second priority alarm is a pump failure. The effect of a pump failure alarm is to stop pumping on all lines immediately. Service may be re~uired to repair a pump failure.
The third priority alarm occurs when an occlusion in the patient output line is detected by the on pump prsssure system.
This alarm is not detectable unless one or rnore lines are infusing. The effect is to cause all infusing lines to be placed on hold until the occlusion is cleared.
The fourth priority alarm is a possible full collection bag. The collection bag is used when the pump has detected air in the one of the infusing lines or an occlusion in one of the infusing lines and is attempting to purge the infusing line by diverting to the collection bag. Detection of a possible full .. . . . . . ... . .
` ': - , :
- ,:. ' . , :', -, .
, ~3~7~5 collection bag causes all infusing lines to be placed on hold until the condition is cleared.
The fifth priority alarm occurs when air or another occlusion occurs in the primary fluid input line. Generally one of plural input lines is designated the prirnary input line.
This alarm is generated after a few pump strokes. When this condition is detected, the system first attempts to purge the line with a few pumping strokes, diverting output to the collection bag if the condition does not clear up.
The sixth priority alarm relates to air or an occlusion detected in one of the remaining input lines. This alarm causes the line with the occlusion to be placed on hold. If all of the secondary input lines are placed on hold, pumping on the primary infusion line continues at a keep-vein-open rate.
The seventh priority alarm occurs when the pump is unable to pump at its programmed rate. The alarm is generated when, after several sequential "catch-up" pump cycles have occurred, the pumping rate remains less than the programmed rate. This alarm causes the primary input to infuse at the pre-selected keep-vein-open rate while all the other infusing lines are placed on hold.
The eighth priority alarm is a possible empty contai~er alarm. This alarm is a warning, so actual pumping operation will continue.
- : ~ ,. . : :.,: .
- : . : . : . :
.: - , : .: ~ ,, . :
: ,: .: ~ , . ::;
- . .. : . . .
. ; , . . . .
-: , : . : . -:: .
-: ' ' , , :. :
~- - . ~ :: . ; . :
. : . ' , :
: ~ ' ' ' , , : ' , ''." :'' :' : ' ' :' .
The ninth priority alarm is a callback request. I'his alarm also is a warninq. It is generated ~lhenever an intermittent infusion is started or stopped.
Several other warnings may occur, but are not generally given a priority and placed on the alarm stack. The system alerts the operator, by producing an audible tone, that the battery voltage is low if the system is powered by a battery.
Battery operation is advantageous when a patient must be moved from one location to another with the infusion continuing during ihe move. Another audible alarm is generated when one of the infusing lines has been manually placed on hold. After two minutes, an audible tone alerts the operator that the line is still on hold. Finally, an audible tone alerts the operator whenever the pumping system is transferred to battery operation.
Fig. 35 is a state diagram showing the states that the infusion pumping system is placed in by programming in the on board computer after the occurrence of one or more alarms. Each state is represented by a of the pumping system. The zero states box 502 labeled RVN refers to normal pumping operation.
Box 504 labeled LINE HOLD refers to the one state in which one or more but not all of the pumping input lines have been placed on hold. The box 506 labeled HOLD KVO refers to the two state in which all the lines have been placed on hold except for the ,.~ ~ ... .. .
. .
' .. . ..
, : ; ', ) ' ' ' primary line, which continues to pump at the keep-vein-open rate. The bo~ 508 labeled HOLD ALL refers to the three state in which all lines have been placed on hold. Finally, the box 510 labeled STOP ALL refers to the four state in which pumping has been stopped completely.
When infusing, the system is normally in the RUN
state 502. Arrows label each one of the nine alarm priorities.
Each arrow shows the state to which the system goes upon occurrence of an ~larm of a given priority. For example, the cassette unlocked alarm has priority 1. The arrow with the 1 beside it (this arrow also has 3, 4, and 5 beside it), leads to the state labeled HOLD ALL in box 508. Thus, upon occurrence of a cassette unlocked alarm, all lines are placed on hold. They remain on hold until the alarm is cleared by the operator (by locking the cassette in place). If the system is in the RUN
state 502 and an empty container alarm occurs, the system remains in the RUN state, as shown by the arrow exiting and returning to the RUN box.
If the system is in the RUN state and a sixth priority alarm occurs, the system will place that line on hold and be in the LINE HOLD state indicated by box 504. If, while the system is in that state, a second alarm of sixth priority occurs, that line will also be placed on hold. The system will remain in the :.... .. . .
:: i :, , .
--: :.:, :.~ . . : . , : : , , :
.
2~
LINE HOLD state, as shown by the arrow exiting and returning to the LINE HOLD bo~ 504. However, if all secondary lines generate sixth priority alarms, the system will go to the state labeled HOLD KVO in box 506. This is not specifically shown in Fig. 35.
Each possible alarm condition is designated by a bit in the processor's storage. If the processor receives a signal that the alarm condition has occurred, the bit d~signated for that alarm condition becomes a "1." All the bits are passed through a filter which identifies all the "1" bits. These bits are ranked according to priority and time of occurrence and the user is alerted to call them up for display and action when a keyboard 38-5, 90-5 requested is made. The keyboard 38-5, 40-5 includes an override key whose function is to remove that bit from the memory and effectively reverse the process of Fig. 35.
In addition to the above alarms, the infusion pumping system performs a self-test upon installation. At this time, it tests for various error conditions and generates a screen display for any of these conditions which occur. These error conditions are tested only at this time. They are not included in the above priority table.
The pumping system includes an event recorder 38-6, 90-6 which generates a record in memory of all the "events" during a course of intravenous infusions, referred to as an IV history.
. . . ' . :
. ` ' ' ` ' : , r~
The events include stopping, holding, or resuming an infusion on a particular line automatically or manually, and keyed to the time of occurrence. The IV history will also record unscheduled events, such as alarms or a t~ansfer to battery power.
A complete IV history containing, in the preferred embodiment, events spanning up to 2~ hours, can be generated and printed on printers 38-3 40-3 chronologically alony with patient ID and drug ID. Alternatively, the operator can specify through the keyboard 38-5, ~0-5 a range of events, such as the last twenty events, or ~ time period, such as the last two hours.
The system will then generate and print an IV history only for the range or time period specified. Events pertaining to a particular patient when printed represent a retrospective medication administration record for that patient. This report can be appended to the patient's chart.
External events may also be recorded. For example, the operator may take the patient's blood pressure. The operator then enters the blood pressure data through appropriate keys on the keypad. The system records the blood pressure data and time it was entered and includes this event in the IV history.
The entry of event data follows a flow chart of Fig. 39.
From a start state 700, which functions as an event occurrence interrupt so that it can be entered with each event a :
:, ~ ,, '' ;,. ;
.. ~ , . . ..
: `
.
~ ,r~
keyboard 38-5, ~0-5 request ~or event entry in step 702 initiates an event entry mode. Step 709 causes the event data to be received as such from keyboard and/or sensors and step 706 records the event and tirne in rnemory 3~-~, 40-~. Step 708 returns to normal, pre-interrupt, processing.
The pumping system also is able to ~enerate a record of the current device status. This record includes patient identification data, present infusion regimen data, the current status of each line, and the total amount infused on each line up to the current time. This report, when generated immediately after completion of regimen programming represents a prospective medication administration record for that patient and can be appended to the patient chart. This record may be updated each time a line is started, stopped, placed on hold, or resumed.
The entry of most of this data occurs from initial bar code reading. Pump volume data is recorded continuously during pumping using a volume accumulation update as shown in Fig. 40.
In a step 710, volume for each line is accumulated for pump cycle commands. In step 712 this is periodically added to a volume record for each line in the database 38-4, 40-4 and step 710 resumed.
The pumping system includes a storage buffer to which the IV history or device status record is written. From there, the - . . .
..
'`
.
. ' , ' : : t 7~5i operator may direct the pumping system to generate a printed output on a local printer 38-3, 40-3 to, for example, be attached to the patient's chart.
Printout of the Iv history and device status uses a print routine of Fig. 41. From state 720, a step 720 is entered upon keypad command for printout. In step 722 the range of time or events and the decision for an IV history or device status is made. In subsequent step 724, this record is assembled by the preset chronological format and sent to the printer.
Also, the operator may transfer the record directly through a serial port and mutltiplxer 29, or by manual transfer to the hospital administration system computer 26, via interface 28 as shown in Fig. 1. By making this data available to the hospital's main administration system 26, more accurate record keeping can be accomplished. For e~ample, the patient can be billed for only the amount of solution actually infused.
Also, the data can be transferred to the pharmacy management system 20 where it is stored in memory 20-3 for analysis of medication usage.
The analysis at either the pharmacy or administration systems 20, 26 follows the processing of Fig. 42. From a start state 730, an operator request for analysis causes step 732 to ~e entered. In step 732, the operator selects the type of g ~ .:
:, analysis which includes: total drug usage by drug, by drug concentration, L)ottle size, total patient drug usage (by the same breakdown). In step 734, this analysis is run on the database 20-3, 26-3. In step 736, the result is printed in a step 736 and in step 738 the system returns to its prior state.
Biofeedback and remote prograrnrning are implemented as different functions of a single auxilliary computer system 42 capability. This capability is shown more fully in Figs. 37 and 38. Two infusion pumping systems 602 and 612, representing a network of infusion pumping systems, are shown in Fig. 37.
Any number of pumping systems may be added. One of the pumpin~
systems 612, as shown by Fig. 37, may be located away from the hospital in, for e~ample, the home of patient 614.
A remote biofeedback network computer 610 functions as the remote controller for a network of pumping systems as shown in Epstein, et al. The computer 610 communicates with each pumping system generally through a serial port on each pumping system. Each infusion pumping system has data, such as that contained in the IV history record or device status record described above, available at the serial port for the remote computer 610. For e~ample, an operator at the remote computer 610 can review all the alarm conditions on the alarm stack. In this manner, the remote system 610 monitors each .
, . , .
7~
pumping system 602, 612. The remote system also sends instructions to each pumping system over the net~ork and in through the RS-232 serial port to alter the purnping state rnuch like the bar code reader.
In biofeedback, or closed loop infusion applications, sensors 608, 616 monitor physiological conditions of the patient 604, 614, such as blood pressure, pulse rate, respiration rate, temperature, blood gases, and blood sugar levels. These sensors are either fully automated (as in Fig. 37) or alternatively, some operator inter~ention is instrumented as, for example, having the nurse measure the patient's blood pressure and enter the data manually via a keypad 602-5, 610-5, 612-5.
The flow chart of Fig. 38 shows the steps taken by the system 610. The system 610 reads the sensor data in step 640 either directly ~rom the sensor 608, as shown in Fig. 37, or from the infusion pumping system. The system evaluates the data in step 642 according to a pre-programmed set of conditions-result determinations in a memory 610-1. The condition-result analysis, which may be simple or a knowledge (based system (AI) determines if the infusion regimen should be changed in a step 644 as the result of the sensed conditions.
If it datermines a change is necessary, it suggests an ' ' ' ' ' ' ,: ' - : , . : - ~ . :
,,' ' , ' ' ' . , .. ~'' `
, .
'~ : '";
appropriate change to an operator in step 646 and requests the operator confirmation in step 648. The operator can confirm the change, or override the system and make no change, or make a different change. Lastly, the system will e~ecute any change to be made in step 650 by sending instructions directly to the infusion pumping system.
The network computer system 610 is locatable in a central area, such a nurse's station, where infusions ~or several patients are monitored. If an emergency condition develops, the nurse/operator can take immediate steps via the system 610 to help the patient. For example, an infusion can be immediately stopped, started, altered, or increased or a different drug added.
An e~ample where biofeedback is useful is where precise alternations in the rate of flow of insulin are made in response to the patient's level of blood sugar. If the level gets too high, the rate of insulin infusion can be increased. Altering the rate of nitroprusside infusion in response to an inappropriate blood pressure is a further e~ample.
. The system is also capable of altering infusions on several lines in response to sensed conditions. For example, insulin may be infused on one line to lower a patient's blood sugar lever. If the level gets too low, the insulin infusion "
' , `,` ~ ';
: `
, 7~
can be stopped and a glucose infusion can be started on another line. As a further example, nitroprusside and dobutamine can be alternately inf~sed, depending cn the patient's blood pressure.
As a further example, if a carrier ~luid is infusing on one line and the operator wants to get medication on another line into the patient quickly, the medication on the other line can be started and the ra~e of infusion on the carrier's line increased.
Infusion pumping system 612 is shown in Fig. 37 configured for use in a patient's home. Some keypad functions on the pumping system 612 may be disabled to prevent accidental interference, but the system 612 is essentially the same in terms of infusion capability as is used in the hospital. An interface 618 is provided between pumping system 612 and a modem 620. Modem 620 allows communication to take place over a telephone line 62Z. At the hospital, a mode 624 and interface 626 to the network system 610 is provided.
In use, either the patient or a visiting medical technician hangs the medication and sets up the system in the home. The infusion can be started directly at the pumping system or by a signal sent by the remote system 610. The pumping system 612 initiates calls through interface 618 to the system 610 and the system 610 initiates calls to the pumping system via interface 626 using conventional automatic answer, .
! ` , . ' ! ~ ' 2~
automatic dial capabilities. A sensor 616, similar to sensor 604, may be included for biofeedback purposes, as described above.
The network configuration is useful for other tasks as well. For example, the network computer system 610 monitors the version of each pump and ensure that the delivery instructions encoded on the solution container by the pharmacy are appropriate for that version. Updating hardware and software is usually an ongoing process, so it is useful to have a back up check as to a safeguard.
The invention is not to be limited by what has been particularly shown and described, except as indicated by the appended claims.
. . :
. , . -, . ~ :
.: , :
.'' ' . , . ' . ',, . .
..
, ..
: ` ;
~ .
of infusion system data is disadvantageous because it is labor and time consuming and the possibility for incorrect data treatment is greater.
~MMARY OF THE I NVENT I ON
The infusi~n system of the present invention contemplates a system for managin~ the infusion of one or more drug formulations to a patient from the make up of the infusion in the Dharmacy to the generation of a report Cor hospital records ar.~ analysis after the infusion is complete.
The infusion management system of the present invention provides a computer-based pharmacy management system, located in a hospital or clinic's pharmacy, remote from the infusion pumping system. All prescriptions for intravenous infusions are entered into the system when the pharmacist makes up the prescribed formulation. The system prompts the pharmacist or other user for the necessary patient identification data and prescription data, such as the drug to be infused, the carrier solution if any, the concentration of the drug in the carrier solution, and the infusion regimen (continuous, maintenance, or intermittent and rate, volume and infusion frequency). The data entered can be subsequently edited. After all data has been `. ~ : ' .` : `
correctly entered, the system makes a bar code readable label which is applied to the cutside of the container in ~lhich the infusion solution is placed.
The pharmacy rnanagement system also includes a drug database which stores drugs by name, mnemonic, and I.D. number.
The database also includes a matrix of drug incompatibility. If two incompatible dru~s are to be mixed in a single solution, the system alerts the user.
The management system also produces reports to be included ~n ~he ~atient's ~ecord or chart. Further, the management system tracks the inventory of drugs by monitoring the precise amount ~f drugs used and the nature of this drug source. This data may be transferred to the hospital's existing drug inventory control system for more accurate monitoring and ordering of drugs.
The labeled container containing the infusion formulation is transferred to the patient by usual methods either within the hospital or to the patient's home in the case of remote infusion control. The user, a nurse or other health practitioner, using a bar code reader associated with each pump s~stem, enters the data from the formulation container label into the infusion pumping system where it is displayed and accepted. The pumps serial port may be used for this purpose. Data can also be . ' ' - ' ~ .
- . : ' '. ' ` , , ~ : .
entered manually in addition to or in lieu of entry by bar code reader. The pumping system prompts the user for any necessary data that is rnissing from the read label but required by the pumping system before the infusion program can begin. To accommodate emergency situations, the pumping system allows an overrider. A~ter entering the data on the solution container, the user completes ~he infus~on programming by entering the start time. A delayed start time provides flexibility in administrati~n. Preprogramming of functions is useful when the user is expecting I pat-ent to arrive from, for example, an operating room and wants to get the infusion up in advance.
Alternatively, an advance set-up reduces the risk of error due to setting up an infusion too quickly and allows the patient to be connected to the infusion system more rapidly upon arrival.
The infusion pumping system has several input lines for infusing more than one formulation. A similar procedure is used to program each line on the pumping system and the pump itself can identify inappropriately scheduled drugs.
The infusion pumping system performs several checJss to ensure the data is correct. It verifies that the patient identification is correct and that the patient is not allergic to any of the medications in the solutions and allows the user to confirm that all data is correct. The user can override the data on the bar code label by manually entering different data.
:: , The infusion pumping system of the present invention also contemplates an improved alarm handler system. During operation, the pumping system can yenerate a variety of alarm conditions of varying severity. Some alarm conditions, such as various pump failures, unlocked cassette, and patient line occlusion require stopping all pumping immediately. Other alarms, such as air in a secondary input line merely require temporarily holding the pumping on that line until the alarm condition has been cleared while other lines continue to infuse. Finally, alarms such as an empty bottle on one of the input lines do not effect pumping at all. Also, several alarms can exist simultaneously if, for example, a second ala~m occurs before a first alarm has been cleared.
The present invention pro~ides an alarm handler capable of dealing with many alarms at once. The alarm handler ranks the alarms by degree of urgency. The alarms are stored in a stack with the most urgent presented to the user for clearing first. Alarms of the same degree of urgency are stored in reverse chronological order. An audible tone alerts the user to the existence of one or more alarm conditions. The system, upon prompting by the user, presents the alarms to the user for action.
The infusion pumping system is also responsive to remote or biofeedback instructions to alter a planned infusion program.
, :
"'' ` ' ~. .
2~ 5 DESCRIPTION OF THE DRAWINGS
Fig. 1 shows a schematic block diagram of the fluid management and pumping system of the present invention;
Fig. lA shows a bar coded label of the present fluid management system;
Figs. 2-29 are flow charts illustrating the pharmacy management system of the present invention;
Figs. 30-34 are flow charts illustrating data entry into the fluid pumping system of the present invention;
Fig. 35 is a diagram showing the state of the pumping system after various alarm conditions;
Fig. 36 is an alarm priority table;
Fig. 37 is a schematic block diagram of the biofeedback remote programming system of the present invention;
Fig. 38 is a flow chart illustrating the biofeedback/remote programming system; and Figs. 38-42 are flow charts illustrating the biofeedback~remote programming system.
;`
~ . ,. . . : . -- : , . , ' ,.
.
2~
DETAILED DESCRIPTION OF THE INVENTI~N
The present invention is shown generally in block diagram format in Fig. 1. A pharmacy manag~ment system 20 includes a computer keyboard 20-1 for input, bar code reader 20-2, database 20-3 and a printer 20-4 for generating a bar coded label to be placed on the container for an intravenous solution made up by the pharmacy of a hospital or clinic. Since the pharmacy management s~stem 20 accurately tracks the quantities of drugs used, it ~ay communicate through an interface 22 with the hospital's existing computer based pharmacy inventory control syste~ 29 ~or the exchange of hospital specific inventory and drug labelling data.
A hospital typically has a pre-existing computerized administration system 26. The pharmacy management system 20 communicates through interface 28 with this pre-existing hospital administration system 26. The hospital administration system also eommunicates through an interface 30 with the hospital's pre-existing inventory control system 24.
Labels 32 for infusion formulation generated by the pharmacy management system 20 from keyboard bar code input of prescriptions are transported to the appropriate patient 34 infusion pumping systems 38 and 40 (as shown in the above . ` ` '`` ` ` ` ~ ~
: ` ~
. .
referenced patent) as shown by the dotted lines in Fig. 1.
While only two pati~nts 34, 36 and associated pumping systems 38 and 40 are shown in Fig. 1, each hospital will generall~ have many such patients. ~ach infusion pumping system 38, 40 includes a bar code reader 38-1 and 90-1 coupled into the database of the pump through a parallel data port or an RS-232 serial port shown in Epstein, et al.. The label is read by the bar code reader and all the nformation on the label is transferred to the in~usion pumping system in the same manner as manual data entry occurs.
The infusion management system also includes a remote/biofeedback control system 42 which operates through an interface 94. In biofeedback applications information is sensed by patient sensors 34-1 and 36-2, such as blood pressure or glucose levels, and instructions are sent to the infusion pumping systems 38, 40 to alter the planned program of infusion in response to the sensed information. With the remote capabilities of control system 42, a patient may remain at home. Instructions for programming an infusion pumping system are sent over a phone line communication path 42-1 to a home system 42-2 of pumping systems by the control system 42.
'' . , '' j':
'7~
The pharmacy rnanagement system 20 may be described with more detail by reference to the flow charts of Figs. 2-29.
Specifically, the pharmacy management system provides a program for encoding in~usion delivery instructions ~or intra~enous solutions in a bar code format. The system takes the operator through a series of screens and menus which request the information necessary to program the infusion pumping system. A
final screen summarizes all the data that has been entered, requests confirmation from the operator, and provides the option for making a label. The delivery instructions are printed in bar code rormat as well as in human readable format on the label.
The system can be run on commercially available computers. Preerably, the system includes a monitor 20 5 for displaying the data screens and a keyboard 20-l for entering the data.
The flow chart of Fig. 2 shows the overall operation of entering data for each intravellous solution to be infused into a patient. The encoding program is initialized in step 102 by booting up the computer with the pharmacy management system installed in the computer's memory and typing an appropriate command including calendar entry. The system invokes a system menu processing routine in step 104, which gives the user a choice of several tasks to perform. The system menu processing .
2~
routine is described in greater detail by reference to the flow chart of Fig. 3. lhe system displays the main menu 106. The main menu displayed to the user allows the choice of editing previous labels, all on specific patient scripts, processing new entries, printing all on a range of labels, generating a report, archiving the database, batch delete or restoring the database.
The user makes a selection 108 and the system returns the selection in step 109 and returns yrocessing to the main program. The user's selection is then processed in step 112 in Fig. 2. After the user's selection has been processed, the system gives the user the option of quitting or performinq another task. If the user wants to perform another task, the system returns to the step of invoking the system menu processing in step 104 to allow the user another selection. If the user quits, the system invokes system termination, as shown by block 116.
The task of processinq previous entries is shown in the flow chart of Fig. 4. This task allows the user to call up infusions that have been previously entered and are due to expire on a specified date. The user then determines whether the infusion should be renewed. If the infusion is to be renewed, the system saves the patient's records. As shown by the flow chart of Fig. 4, this routine retrieves the date from ,.; . . .~ . ' :
., : i 971~
the system in step 120. It clears the screen in step 122 and a work space in ~AM, as shown by steps 124 and 126. The system then executes a patient scan 128, in which it searches ~or infusions due to expire that date. It displays each infusion record on the screen and provides the user with the option of renewing the i~fusi~n by printing a bar coded label. A~ter the scan is complete, and all bar coded labels printed, the routine sets return status to "~K," enabling processing t~ return to the routine of Fig. 2.
The processing of new infusion entries is shown by the flow charts of Figs. 5-17. The system's ~irst step is to put all existing records, including records saved in the "processing previous entries" routine, in a workspace in RAM 20-3 in step 132. The system then calls a routine to process a patient record 134, shown in more detail in Figs. 6 and 7. The system will display a screen asking for patient identification data in step 150 and will set the data mode to allow input in step 152.
The patient may be identified by name or identification number.
If the patient has previously been recorded in the system, entering one of the ~atient's name or identification number will cause any other patient data in the patient's record stored in RAM 20-3 to appear on the screen. The patient identification screen also contains data fields requesting or displaying data -- 1~ --' ,~ .
on the patient's room number or other location identifier, total number of intravenous solution labels required by the patient, the patient's physician, and physician identification number.
OncP all the patient identification data corresponding to label fields in a typical label as shown in Fig. lA has been correctly provided, the special function key may be depressed to enter this data and display the next screen 154. The patient data remains displayed in a window at the top of the monitor while the remaining infusion data on the subsequent screens is entered. If the system includes a color monitor, the patient identification screen may change to a different color in step 156; to indicate that it has been entered.
Each patient can receive a number of different drug regimens. Each regimen refers to the delivery instructions for a solution of drugs contained in one intravenous container. As in step 158, the system sets the regimen count to zero. The system then increments the regimen count, in step 160. For the ~irst drug regimen, the regimen count is l. The system clears a work space in RAM, in step 162. The system then makes a control number, in step 164. The control number is for the pharmacy's use in keeping track of all the intravenous solutions it formulates. The next step 166 initializes a default prescription (or script) 166. For example, certain data such as .: ,: , ,: :
i` ~' : , '," .. "
: ~, ~ ;" ' :
'` ' ! : ~: :`
:, the keep vein open (KVO) rate is often the same regardless of the drug. In addition, the expiration date is usually set for one day later but can be adjusted by a higher level of authorization. This data is placed into the system as default data, but it can be changed by the user during the next step of processing the script in step 168.
The procedure involved in processing each prescription is shown with more detail in Figs. 8-16. As shown in Fig. 8, the ~irst step 122 in:tializes the script causing the drug entry screen to appear. ~he system accepts entry of data in each of the data fields in the screen. The data fields include the drug regimen number, the prescription date, the e~piration date, the prescription number, the pharmacy control number, and the drug name, drug nmemonic, and drug identification number, and the drug concentration in a carrier solution. These correspond to fields shown in a sample label in Fig. lA. When the user enters a drug either by name, mnemonic or number, the remaining unentered data previously set up as default data, will automatically be supplied by the system.
- The system then displays a screen asking the user if additives are desired in step 178. If the user selects additives, the additives are processed in step 180 as shown by the flow charts of Figs. 9 and 10. The system initializes the additives by displaying an additive screen in step 182. User - , :
' ~ .
., . ~ . , ' .
, ;,' 2,~ 5 .
input in step 189 allows the user to enter the additi~Jes desired. The system builds an additive list in step 186 simply by adding a new additive to the list in the routine as shown in Fig. 10. The system then updates the script in step la8 to include all the additives. Once all the additives have been processed, the system returns to the routine of Fig. 8, displays the data in a window of a different color to show that all the prescription medication data has been entered in step 190, and continues to the step of processing the infusion in step 199.
The steps of processina the infusion are shown in Fig. 11. The system displays a menu in step 110 for choosing the type of infusion. The infusion types are continuous, maintenance, and intermittent. If continuous infusion is selected, the screen will display data fields for the dose rate and the dose volume and a menu for the selection of the appropriate units. If maintenance infusion is selected, the screen will display data fields for the maintenance rate and total volume and a menu for the selection of the apyropriate units. If intermittent infusion is selected, the screen will display data fields for the volume per dose, the time per dose, the dose rate, the dose frequency, the total number of doses, and whether a dilution or a syringe is desired. Again, the screen will also allow the selection of the desired units. If , , . ~ ", . , .
..
....
: , ; ~
:
, 3~5 dilution is selected, the screen will display data fields for the entry of the dilution rate per dose and ~olume per dose.
After all this data has been entered, the user hits a special ~unction key which allows the system to update the script and store the data in step 116. This data may also be displayed in a red window in step 118.
At this point, all the necessary data for the infusion has been entered into the system. The next step is to generate a label containing the data in both bar code readable and human readable format. The system gets the label instructions in step 196, as shown in Fig. 8 and in flow charts of Figs. 12-17.
The first step of the flow chart of Fig. 12 is to display an option menu in step 202. The options are to make a label, skip making a label, edit a label, or terminate. After a menu option is selected, the processor moves on to the ne~t step of finishing the regimen in step 204.
If the terminate option is selected, the system, as shown in Fig. 13 clears the screen in step 206, sets the data mode to input in step 208, allowing the user to start on a new patient or prescription, and sets the system to terminate the present infusion entry in step 210. Processing is returned to step 198 in Fig. 8. Since termination has been selected, the system quits in step 200. Processin~ then returns to step 168 in -, .
.
: ` , ' `
. .
:, ' , ' , . . .
' . ' , , ' Fig. 6. Since "quit" has been selected, processing ~eturns as shown in Fig. 7 to the ~ain program of Fig. 2 and finally terminates in steps 114, 116.
If, instead, the option to skip making the label is selected, then the system as shown in Fig. 19 clears the screen in step 212 and sets the data mode to input in step 214. This allows the user to continue inputting data on the same patient.
I~ the user elects to edit the data, as shown in Fig. 15, the system clears the screen in step 216, redisplays the patient screen in step 218, and sets the data mode to edit in step 220, allowing the user to edit the data relatin~ to the current patient or prescription. This allows the user to make any changes that may be necessary.
If all the data has been correctly entered, the user can make a label, as shown in Fig. 16. The systern displays a screen in step 222 to allow the user to set the number of copies. The system then generates labels in step 22g, as shown in Fig. 17.
The system formats the data in step 226 in bar code readable and human readable form. The system then prints the label in step 228. A conventional bar code printer may be used. The bar code symbology preferably is three o~ nine (39), an alpha/numeric encoding system with, a high reliability rate (internal check character) as recommended by the Health Industry Business Communications Counsel.
: . , :. ,. ,. ::
., , - : ~ , ; , ; ; ; . . ~, . ~ , ~
.: ,,:. , :
. .
. .
" :: . :
: .
: . . . , - . ~, .. .
The system then makes a log entry and a label in step 230 and prints an additional label in step 240, for example, to attach to the patient's chart. The system then clears the screen in step 242, as shown in Fig. 16, sets the data mode to input in step 244 to allow further input of data, and updates the prescription database in step Z46 by storing the completed prescription in the database. Processing is then returned to step 198 of Fig. 8, where the user is given the option of terminating the input on the present patient or continuing with the present patient by processing a rurther prescription.
If the user selects termination, in step 198, quit is set to yes in step 200. Processing is returned to step 170, as shown in Fig. 6 and the patient screen is redisplayed. If quit, as shown in step 250 of Fig. 7 is selected, the screen is cleared in step 252. Processing returns to the routine shown by the flow chart in Fig. 2. If the user does ~not select termination, in step 2S0 processing returns to step 160 of Fig. 6. The regiment count is incre~ented by one. This allows the user to process a second prescription for the same patient.
The system then goes through the identical steps for any desired number of prescriptions for the particular patient. If the user has finished processing scri~ts for the patient, the system sets a "return" status, which allows processing to return to the main menu.
- . .
- , .
~ further user selection allowed by the system in the routine shown in the ~low chart of Fig. 2 is the rnaking of a patient report. The flow charts of Figs. 1~ and 19 describe this routine. When this option is selected, a report menu is displayed in step 260. The system gets the user selection in step 262 and processes the report in step 264, as shown more fully in Fig. 19. The system displays an input screen in step 266, gets the ~ser~s data in step 268 and loops the database in step in step 270, applying the search criteria input by the user n the ,revious step 268 to the patient script records. The system then prints the report in step 272.
Alternatively, ~he system could interface with the hospital administration system 26, as shown in Fig. 1, and send the report to the hospital administration system.
Typical examples of report generation include a summary over a specified time of all drugs labelled for a patient. Two other options provided in the menu of Fig. 2 are to archive the database or to restore the database. Archiving the database is shown in the flow chart of Fig. 20. The system executes a backup in step 280, generally by storing the database on a floppy disk and returns in step 282 to the main menu. The opposite procedure, shown in Fig. 22, is the restoring of the database to the system. In this routine, the system executes a - .. , . , . ., . ,, , . , . ~
-, .: - , "
,.
, :
, s restore in step 284, generally reading the database from the Eloppy disk into the storage on the system and returns in step 286 to the main menu.
;The system also includes a stored drug table in RAM 20-3. The drug table includes a list of all the drugs used or prescribed for patients in the hospital. The drugs may be stored by drug name, nmemonic, and identification number. The drug table may also include incompatibility data for the drugs.
For example, if a solution containing a mi~ture of two drugs were to cause particles to precipitate, the drugs would be incompatible, since a solution with precipitates would not be suitable for infusion into a patient. The system checks the drug table upon entering new prescriptions for each patient.
The drug table supplies some of the drug data to be included on the label. The drug table may be edited to change data on the drugs included in the database, or to add or delete drugs to and from the database.
Figs. 23-29 show the flow charts for the routines which allow entry, deletion, and editing of the data in the drug database. Fig. 23 shows the flow chart for the main routine.
The first step 302 to initialize the system, gen~rally by typing an appropriate command on the keyboard. The system then invokes the system menu processing in step 304. The user can select ```,f ~
- -' ' `
Z~
from the choices of loadinq the drug file, saving the drug file, printing a drug table, entering drug data, editing drug data, and deleting drug data. After the user rnakes a selection, the system processes the user selection in step 306.
To work on the database, the user must first load the drug file, as shown by the routine cf Fig. 29. The system loads the database in step 312. The system then returns and asks the user whether the user wishes to quit or continue, as shown by step 308. If the user wishes to continue, the system menu processing is once aqain invoked in step 304 allowing the user to make a further selection.
New drug data is entered by the routine shown by the flow chart in Fig. 27. The system displays a drug entry screen in step 3Z2. The user enters data in step 324, and the system puts the entered drug data into the database in step 326. If the user selected the option of editing the drug data, the routine shown in Fig. 28 is followed. The system displays a drug edit screen in step 323. The drug edit screen requests the user to specify a particular dru~ and the system displays the data contained for this dru~ in step 330. The user may then edit the data regarding the specified drug in step 332. After the user has completed editing, the system updates the internal database by storing the edited data. If the user selects the option of !
.. . . " ` :
,, - :` . :~
' ' ` ' ' ' ' '` '' :
: ' ` "~' ` ' ~ '`' ' 7~ ~i deleting a drug from the database, the routine shown in Fig. 29 is followed. The system displays ~ delete drug screen in step 336. The user selects a drug to be deleted. The display shows the drug specified by the user in step 338. The system then asks for verification that the drug is to be deleted in step 340. If the user chooses no, the drug will not be deleted. If the user chooses yes, the drug will be deleted from the database in step 342.
The flow chart of Fig. 25 allows the archiving o a drug database that has ~een recen-ly changed. If this option is selected, the system deletes the old copy of the drug database in step 314. The new copy of the drug database is saved in step 316. The user can also print the drug database, as shown by Fig. 26. If the user selects this option, the system redirects the output to a printer in step 318. The system then loops through the drug database, ~ormatting and printing each entry in step 320.
After each prescription label has been generated by the pharmacy management system, the label is placed on the bag containing the solution to be infused. The bag is carried or transported by the hospital's usual method to the patient's location. The delivery instructions printed on the label on the medication container must be inputted to the infusion pumping : ~ . . ..
~, ~,:
. ~. , , . ~ , , . , , : ~ :
:
, `r system~ The flow charts of Figs . 30-34 describe the process used to enter the data on the labeled medications by bar code reading.
The infusion pumping system generally is a system similar to that described in the above-referenced patent to Epstein, et al. The system contains a housing in which is placed a disposable cassette containing plural input ports and a single patient output port. The medications are hung from a rack and tubing is run from the medication container to one of the input ports. In tha prior art system, A nurse or other heaith practitioner programs the infusion pumping system with the necessary delivery instructions such as dose rate, total volume to be infused, and starting and stopping times. With the system of the present invention, this data has already been encoded on the bar code label attached to the solution container. As shown in Fig. 30, the user initializes the system in step 400, generally by turning on the infusion pumping device, which runs a self test procedure and is then ready to accept input. The user hangs the line medication or medications on the rack in step 402. The user selects the method of inputting the data to the system, either through the bar codes or manually through a keypad as in the prior art systems. If bar code entry is desired, the user depresses an appropriate key : :,: . ;,; . . .
on the keypad in step 404. The user then programs the line processor in step 406 by wanding the bar coded data with a bar code wand 38-2, 40-2~
The button corresponding to the connect line (A-D) is pushed to correlate that regimen to the appropriate line. The infusion pumping system generally contains plural input lines.
If other solutions are to be infused on additional lines, the delivery instructions for those solutions may be entered in the same manner in st~p 408. After all lines have been programmed, the system gives the option of selecting a pre-programmed mode in step 410. The pre-program mode allows the start of the infusion program to be delayed. This is a useful option if the user is expecting the patient to arrive from, for example, an operating room and desires to get the infusions set up in advance. If the pre-program mode is selected, the system will resume the realtime process in step 412 at the appropriate time. When the start time arrives, the system controls the infusion process in step 414 according to the programmed delivery instructions.
Fig. 31 shows the procedure for programming each infusion line, as shown by step 406 of Fig. 30 in more detail. If bar code input has been selected at step in step 404, the user inputs the bar coded data through a conventional bar code - ~5 -., -' ' ~ ;' ' ~ .
2~
reader 38-1, 40-1. Generally, the user passes a bar code ~,and or pen 38-2, 40-2 across the coded data, ~rom right to left or left to right. All the lines must be read. A ~alidity ~heck is made on the data read by the bar code reader, into the infusion pumping system and a "good" beep is provided if the data falls within expected ranges. If the data is not accepted by the bar code wand, the system will respond in a manner which is readily distinguishable ~rom the '-good" beep. Data not accepted by the bar code reader is to be wanded again. If the data continues to be unreadable, Lhe data may be entered through the keypad of the infusion system 38, 40.
The infusion pumping syst~m 38, ~0 includes a database memory 38-4, 40-4, a small screen, generally a liquid crystal display, which prompts the user for the data to be wanded or entered through the keypad. The system will prompt the user for the user's personal identification number. This data may be provided in bar code format on, for e~ample, a nurses badge.
The system will then request entry of the data contained on the solution label. Finally, the patient identification data must be entered. This data may also be in bar code format on the patient's chart or bracelet. The system verifies that the patient identification from the chart or bracelet matches the patient identification on the solution label and provides a mismatch indication.
.: : , , `~ ' , ' ~' '.'. ''... .', '' ' '" ,' ' ; ' ''j . ' ' ' . ' ', , .'' ' ' ', ' `'`` '' `' `''` :,' ' .
.. :, After all the data has been entered, the system checks to see whether all the data has been entered correctly, as shown by step 424. If not, the system prompts ~or any rnissing data in step 9Z6. The manual prompt routine, as shown in Fig. 32, runs through all the necessary data in step 450. For any missing data, it displays a prompt in step 452 requesting entry of the data. The user wands or keys in the data in step 454. At this point, the system may also check the prescribed drugs against the patient's record for allergies to the drugs that have been prerecorded in databases 38-4, 90-4. If any drugs to which the patient is allergic ha~e been prescribed, the pumping system displays a message so informing the user.
The user may edit the data to change the regimen in step 456. Fig. 33 shows a flow chart for the routine the system uses when data is entered by keyboard 38-5, 40-S. The data is entered and the system range checks the data in step 440. Then, the system encodes the event in an I.V. history in step 442 that is maintained for each course of infusion therapy.
After all the data identifying the medications and the infusion data are entered, the system re~uests the user to select an input line in step 428, as shown in Fig. 31. Finally, the system runs through a data confirmation check in step 430.
As shown in Fig. 34, the system checks all the medications in - ' ~ : ' :
: .
"
.. : :
'~ ~
step 442, by displaying the medications to the user who confirms by depression of an appropriate key on the keypad. The system then displays the drug regimen to the user in step 446, ~ho again confirms the drug regimen by depression of the key on the keypad for that purpose (38-5, 40-5). The user can make any changes to the medications or the regimen at this point by manual entry through the keypad. In this manner, a safety check on the data contained on the bar code label is provided. Also, any changes to the infusion therapy can be made. Finally, the systern checks if the infusion is to be a continuous or maintenance infusion in step 432. If not, the system prompts the user for the entry of a start time in step 43~, as shown in Fig. 31. The above procedure is repeated for each solution to be infused on each of the input lines provided on the infusion pumping system.
During the administration of an infusion, various alarm conditions can occur. Alarms can range from a simple audible tone to call the operator back to, for e~ample, start an infusion, to a problem which renders it impossible for fluid to be delivered to the patient. More than one alarm condition can occur at the same time. The present invention provides an improved alarm handler. The alarm handler is best described by reference to Figs. 35 and 36. Each of the various alarms is . . . . .
~ ~ .
. ~: . .
, ~ .
,' ~. ~ ' ' `,, " ' ' '' 2~ s assigned a priority which is used for displaying the alarm conditions to the operator for clearing. When more than one alarm exists at a single time, the alarms are displayed in order of priority, hi~hest priority first. If a subsequent alarm has a higher priority than an existing alarm, the subsequent alarm will be handled before -he earlier alarm. If two alarms have the same priority, the most recent aiarm will be handled first.
The alarms ~ay generally be classified into three distinct types: warnings, pumping alarms, and fluid delivery alarms. Flui( delivery alarms have the highest priority, warninqs the least. Warnings do not change the state of the infusion pumping system and merely alert the operator to a condition. Pumping alarms relate to the ability to pump on one or more of the input lines and may change the state of the device by suspending pumping on one or more of the lines. Fluid delivery alarms occur when fluid cannot be delivered to the patient or when there is the possibility of free flow to the patient.
When an alarm occurs, its time of occurrence is recorded and it is placed on an alarm stack. When the operator arrives to service the alarms~ the alarms are displayed in order of highest priority first and in reverse chronolo~ical order for alarms of the same priority. If one or more lines of the pump .. - `
. . . .: , : :
-`
7~ S
have be~n placed on ~old or pumping has been stopped on alllines, pump operation ~ill not resume until the entire alarm stack has been displayed to the operator and serviced if necessary.
The table of Fig. 6 displays the alarm priorities of the preferred embodiment. The highest priority alarm is the cassette unlocked alarm. When the cassette is unlocked, free flow of a fluid to the ?atient may be possible. Therefore, all infusing lines are placed on hold immediately when the cassette is unlocked.
The second priority alarm is a pump failure. The effect of a pump failure alarm is to stop pumping on all lines immediately. Service may be re~uired to repair a pump failure.
The third priority alarm occurs when an occlusion in the patient output line is detected by the on pump prsssure system.
This alarm is not detectable unless one or rnore lines are infusing. The effect is to cause all infusing lines to be placed on hold until the occlusion is cleared.
The fourth priority alarm is a possible full collection bag. The collection bag is used when the pump has detected air in the one of the infusing lines or an occlusion in one of the infusing lines and is attempting to purge the infusing line by diverting to the collection bag. Detection of a possible full .. . . . . . ... . .
` ': - , :
- ,:. ' . , :', -, .
, ~3~7~5 collection bag causes all infusing lines to be placed on hold until the condition is cleared.
The fifth priority alarm occurs when air or another occlusion occurs in the primary fluid input line. Generally one of plural input lines is designated the prirnary input line.
This alarm is generated after a few pump strokes. When this condition is detected, the system first attempts to purge the line with a few pumping strokes, diverting output to the collection bag if the condition does not clear up.
The sixth priority alarm relates to air or an occlusion detected in one of the remaining input lines. This alarm causes the line with the occlusion to be placed on hold. If all of the secondary input lines are placed on hold, pumping on the primary infusion line continues at a keep-vein-open rate.
The seventh priority alarm occurs when the pump is unable to pump at its programmed rate. The alarm is generated when, after several sequential "catch-up" pump cycles have occurred, the pumping rate remains less than the programmed rate. This alarm causes the primary input to infuse at the pre-selected keep-vein-open rate while all the other infusing lines are placed on hold.
The eighth priority alarm is a possible empty contai~er alarm. This alarm is a warning, so actual pumping operation will continue.
- : ~ ,. . : :.,: .
- : . : . : . :
.: - , : .: ~ ,, . :
: ,: .: ~ , . ::;
- . .. : . . .
. ; , . . . .
-: , : . : . -:: .
-: ' ' , , :. :
~- - . ~ :: . ; . :
. : . ' , :
: ~ ' ' ' , , : ' , ''." :'' :' : ' ' :' .
The ninth priority alarm is a callback request. I'his alarm also is a warninq. It is generated ~lhenever an intermittent infusion is started or stopped.
Several other warnings may occur, but are not generally given a priority and placed on the alarm stack. The system alerts the operator, by producing an audible tone, that the battery voltage is low if the system is powered by a battery.
Battery operation is advantageous when a patient must be moved from one location to another with the infusion continuing during ihe move. Another audible alarm is generated when one of the infusing lines has been manually placed on hold. After two minutes, an audible tone alerts the operator that the line is still on hold. Finally, an audible tone alerts the operator whenever the pumping system is transferred to battery operation.
Fig. 35 is a state diagram showing the states that the infusion pumping system is placed in by programming in the on board computer after the occurrence of one or more alarms. Each state is represented by a of the pumping system. The zero states box 502 labeled RVN refers to normal pumping operation.
Box 504 labeled LINE HOLD refers to the one state in which one or more but not all of the pumping input lines have been placed on hold. The box 506 labeled HOLD KVO refers to the two state in which all the lines have been placed on hold except for the ,.~ ~ ... .. .
. .
' .. . ..
, : ; ', ) ' ' ' primary line, which continues to pump at the keep-vein-open rate. The bo~ 508 labeled HOLD ALL refers to the three state in which all lines have been placed on hold. Finally, the box 510 labeled STOP ALL refers to the four state in which pumping has been stopped completely.
When infusing, the system is normally in the RUN
state 502. Arrows label each one of the nine alarm priorities.
Each arrow shows the state to which the system goes upon occurrence of an ~larm of a given priority. For example, the cassette unlocked alarm has priority 1. The arrow with the 1 beside it (this arrow also has 3, 4, and 5 beside it), leads to the state labeled HOLD ALL in box 508. Thus, upon occurrence of a cassette unlocked alarm, all lines are placed on hold. They remain on hold until the alarm is cleared by the operator (by locking the cassette in place). If the system is in the RUN
state 502 and an empty container alarm occurs, the system remains in the RUN state, as shown by the arrow exiting and returning to the RUN box.
If the system is in the RUN state and a sixth priority alarm occurs, the system will place that line on hold and be in the LINE HOLD state indicated by box 504. If, while the system is in that state, a second alarm of sixth priority occurs, that line will also be placed on hold. The system will remain in the :.... .. . .
:: i :, , .
--: :.:, :.~ . . : . , : : , , :
.
2~
LINE HOLD state, as shown by the arrow exiting and returning to the LINE HOLD bo~ 504. However, if all secondary lines generate sixth priority alarms, the system will go to the state labeled HOLD KVO in box 506. This is not specifically shown in Fig. 35.
Each possible alarm condition is designated by a bit in the processor's storage. If the processor receives a signal that the alarm condition has occurred, the bit d~signated for that alarm condition becomes a "1." All the bits are passed through a filter which identifies all the "1" bits. These bits are ranked according to priority and time of occurrence and the user is alerted to call them up for display and action when a keyboard 38-5, 90-5 requested is made. The keyboard 38-5, 40-5 includes an override key whose function is to remove that bit from the memory and effectively reverse the process of Fig. 35.
In addition to the above alarms, the infusion pumping system performs a self-test upon installation. At this time, it tests for various error conditions and generates a screen display for any of these conditions which occur. These error conditions are tested only at this time. They are not included in the above priority table.
The pumping system includes an event recorder 38-6, 90-6 which generates a record in memory of all the "events" during a course of intravenous infusions, referred to as an IV history.
. . . ' . :
. ` ' ' ` ' : , r~
The events include stopping, holding, or resuming an infusion on a particular line automatically or manually, and keyed to the time of occurrence. The IV history will also record unscheduled events, such as alarms or a t~ansfer to battery power.
A complete IV history containing, in the preferred embodiment, events spanning up to 2~ hours, can be generated and printed on printers 38-3 40-3 chronologically alony with patient ID and drug ID. Alternatively, the operator can specify through the keyboard 38-5, ~0-5 a range of events, such as the last twenty events, or ~ time period, such as the last two hours.
The system will then generate and print an IV history only for the range or time period specified. Events pertaining to a particular patient when printed represent a retrospective medication administration record for that patient. This report can be appended to the patient's chart.
External events may also be recorded. For example, the operator may take the patient's blood pressure. The operator then enters the blood pressure data through appropriate keys on the keypad. The system records the blood pressure data and time it was entered and includes this event in the IV history.
The entry of event data follows a flow chart of Fig. 39.
From a start state 700, which functions as an event occurrence interrupt so that it can be entered with each event a :
:, ~ ,, '' ;,. ;
.. ~ , . . ..
: `
.
~ ,r~
keyboard 38-5, ~0-5 request ~or event entry in step 702 initiates an event entry mode. Step 709 causes the event data to be received as such from keyboard and/or sensors and step 706 records the event and tirne in rnemory 3~-~, 40-~. Step 708 returns to normal, pre-interrupt, processing.
The pumping system also is able to ~enerate a record of the current device status. This record includes patient identification data, present infusion regimen data, the current status of each line, and the total amount infused on each line up to the current time. This report, when generated immediately after completion of regimen programming represents a prospective medication administration record for that patient and can be appended to the patient chart. This record may be updated each time a line is started, stopped, placed on hold, or resumed.
The entry of most of this data occurs from initial bar code reading. Pump volume data is recorded continuously during pumping using a volume accumulation update as shown in Fig. 40.
In a step 710, volume for each line is accumulated for pump cycle commands. In step 712 this is periodically added to a volume record for each line in the database 38-4, 40-4 and step 710 resumed.
The pumping system includes a storage buffer to which the IV history or device status record is written. From there, the - . . .
..
'`
.
. ' , ' : : t 7~5i operator may direct the pumping system to generate a printed output on a local printer 38-3, 40-3 to, for example, be attached to the patient's chart.
Printout of the Iv history and device status uses a print routine of Fig. 41. From state 720, a step 720 is entered upon keypad command for printout. In step 722 the range of time or events and the decision for an IV history or device status is made. In subsequent step 724, this record is assembled by the preset chronological format and sent to the printer.
Also, the operator may transfer the record directly through a serial port and mutltiplxer 29, or by manual transfer to the hospital administration system computer 26, via interface 28 as shown in Fig. 1. By making this data available to the hospital's main administration system 26, more accurate record keeping can be accomplished. For e~ample, the patient can be billed for only the amount of solution actually infused.
Also, the data can be transferred to the pharmacy management system 20 where it is stored in memory 20-3 for analysis of medication usage.
The analysis at either the pharmacy or administration systems 20, 26 follows the processing of Fig. 42. From a start state 730, an operator request for analysis causes step 732 to ~e entered. In step 732, the operator selects the type of g ~ .:
:, analysis which includes: total drug usage by drug, by drug concentration, L)ottle size, total patient drug usage (by the same breakdown). In step 734, this analysis is run on the database 20-3, 26-3. In step 736, the result is printed in a step 736 and in step 738 the system returns to its prior state.
Biofeedback and remote prograrnrning are implemented as different functions of a single auxilliary computer system 42 capability. This capability is shown more fully in Figs. 37 and 38. Two infusion pumping systems 602 and 612, representing a network of infusion pumping systems, are shown in Fig. 37.
Any number of pumping systems may be added. One of the pumpin~
systems 612, as shown by Fig. 37, may be located away from the hospital in, for e~ample, the home of patient 614.
A remote biofeedback network computer 610 functions as the remote controller for a network of pumping systems as shown in Epstein, et al. The computer 610 communicates with each pumping system generally through a serial port on each pumping system. Each infusion pumping system has data, such as that contained in the IV history record or device status record described above, available at the serial port for the remote computer 610. For e~ample, an operator at the remote computer 610 can review all the alarm conditions on the alarm stack. In this manner, the remote system 610 monitors each .
, . , .
7~
pumping system 602, 612. The remote system also sends instructions to each pumping system over the net~ork and in through the RS-232 serial port to alter the purnping state rnuch like the bar code reader.
In biofeedback, or closed loop infusion applications, sensors 608, 616 monitor physiological conditions of the patient 604, 614, such as blood pressure, pulse rate, respiration rate, temperature, blood gases, and blood sugar levels. These sensors are either fully automated (as in Fig. 37) or alternatively, some operator inter~ention is instrumented as, for example, having the nurse measure the patient's blood pressure and enter the data manually via a keypad 602-5, 610-5, 612-5.
The flow chart of Fig. 38 shows the steps taken by the system 610. The system 610 reads the sensor data in step 640 either directly ~rom the sensor 608, as shown in Fig. 37, or from the infusion pumping system. The system evaluates the data in step 642 according to a pre-programmed set of conditions-result determinations in a memory 610-1. The condition-result analysis, which may be simple or a knowledge (based system (AI) determines if the infusion regimen should be changed in a step 644 as the result of the sensed conditions.
If it datermines a change is necessary, it suggests an ' ' ' ' ' ' ,: ' - : , . : - ~ . :
,,' ' , ' ' ' . , .. ~'' `
, .
'~ : '";
appropriate change to an operator in step 646 and requests the operator confirmation in step 648. The operator can confirm the change, or override the system and make no change, or make a different change. Lastly, the system will e~ecute any change to be made in step 650 by sending instructions directly to the infusion pumping system.
The network computer system 610 is locatable in a central area, such a nurse's station, where infusions ~or several patients are monitored. If an emergency condition develops, the nurse/operator can take immediate steps via the system 610 to help the patient. For example, an infusion can be immediately stopped, started, altered, or increased or a different drug added.
An e~ample where biofeedback is useful is where precise alternations in the rate of flow of insulin are made in response to the patient's level of blood sugar. If the level gets too high, the rate of insulin infusion can be increased. Altering the rate of nitroprusside infusion in response to an inappropriate blood pressure is a further e~ample.
. The system is also capable of altering infusions on several lines in response to sensed conditions. For example, insulin may be infused on one line to lower a patient's blood sugar lever. If the level gets too low, the insulin infusion "
' , `,` ~ ';
: `
, 7~
can be stopped and a glucose infusion can be started on another line. As a further example, nitroprusside and dobutamine can be alternately inf~sed, depending cn the patient's blood pressure.
As a further example, if a carrier ~luid is infusing on one line and the operator wants to get medication on another line into the patient quickly, the medication on the other line can be started and the ra~e of infusion on the carrier's line increased.
Infusion pumping system 612 is shown in Fig. 37 configured for use in a patient's home. Some keypad functions on the pumping system 612 may be disabled to prevent accidental interference, but the system 612 is essentially the same in terms of infusion capability as is used in the hospital. An interface 618 is provided between pumping system 612 and a modem 620. Modem 620 allows communication to take place over a telephone line 62Z. At the hospital, a mode 624 and interface 626 to the network system 610 is provided.
In use, either the patient or a visiting medical technician hangs the medication and sets up the system in the home. The infusion can be started directly at the pumping system or by a signal sent by the remote system 610. The pumping system 612 initiates calls through interface 618 to the system 610 and the system 610 initiates calls to the pumping system via interface 626 using conventional automatic answer, .
! ` , . ' ! ~ ' 2~
automatic dial capabilities. A sensor 616, similar to sensor 604, may be included for biofeedback purposes, as described above.
The network configuration is useful for other tasks as well. For example, the network computer system 610 monitors the version of each pump and ensure that the delivery instructions encoded on the solution container by the pharmacy are appropriate for that version. Updating hardware and software is usually an ongoing process, so it is useful to have a back up check as to a safeguard.
The invention is not to be limited by what has been particularly shown and described, except as indicated by the appended claims.
. . :
. , . -, . ~ :
.: , :
.'' ' . , . ' . ',, . .
..
, ..
: ` ;
~ .
Claims (56)
1. A system for administering fluid infusions to a patient comprising:
means for infusing an infusate into the patient;
means located remotely from the infusing means for processing data, the data including data representative of an infusion, the infusion data comprising data identifying the patient, data identifying the infusate, and data identifying the manner of infusion; and means for transferring the infusion data to the infusing means.
means for infusing an infusate into the patient;
means located remotely from the infusing means for processing data, the data including data representative of an infusion, the infusion data comprising data identifying the patient, data identifying the infusate, and data identifying the manner of infusion; and means for transferring the infusion data to the infusing means.
2. The system of claim 1 wherein the data processing means includes means for outputting the infusion data in a bar code format and the data transferring means includes means for reading the bar code format.
3. The system of claim 1 wherein the data processing means comprises means for entering the data;
means for editing the data; and means for outputting the data;
means for editing the data; and means for outputting the data;
4. The system of claim 3 wherein the data outputting means comprises means for formatting the infusion data as a bar code.
5. The system of claim 4 wherein the data outputting means further comprises means for printing the bar code on a label.
6. The system of claim 3 wherein the data processing means further comprises means for storing data representative of medications and the data entering means includes means for obtaining the medication data from the data storing means.
7. The system of claim 6 wherein the medication data includes data identifying a plurality of medications and data representative of dosages for each medication.
8. The system of claim 7 wherein the medication data further includes data representative of incompatibilities between each of the medications and the data processing means further comprises means for detecting incompatibilities by comparing the incompatibility data of the medications obtained by the data entry means and means for outputting a warning when an incompatibility is detected.
9. The system of claim 1 wherein the data processing means comprises means for storing data representative of medications in a database.
10. The system of claim g wherein the medication data includes data identifying a plurality of medications and data representative of dosages for each medication, whereby the dosages stored in the database are default dosages.
11. The system of claim 9 wherein the data processing means further comprises means for entering the medication data, means for deleting the medication data, and means for editing the medication data.
12. The system of claim 1 wherein the data identifying the infusate includes data identifying a primary medication.
13. The system of claim 12 wherein the data identifying the infusate further includes data identifying a carrier fluid for the primary medication.
14. The system of claim 12 wherein the data identifying the infusate further includes data identifying an additive to the primary medication.
15. The system of claim 12 wherein the data identifying the infusate further includes data representative of an expiration date for the primary medication.
16. The system of claim 1 wherein the data identifying the manner of infusion includes data representative of dosage of the infusate.
17. The system of claim 1 wherein the data identifying the manner of infusion includes data representative of a concentration of a primary medication in a carrier fluid.
18. The system of claim 1 wherein the data identifying the manner of infusion includes data representative of a type of infusion.
19. The system of claim 18 wherein the type of infusion comprises a continuous infusion.
20. The system of claim 18 wherein the type of infusion comprises an intermittent infusion.
21. An apparatus for administering fluid infusions to a patient comprising:
means for infusing an infusate into a patient; and means for automatically transferring data representative of the infusion to the infusing means from a source external of the infusing means.
means for infusing an infusate into a patient; and means for automatically transferring data representative of the infusion to the infusing means from a source external of the infusing means.
22. The apparatus of claim 21 wherein the automatically transferring means comprises a bar code reader.
23. The apparatus of claim 22 further including:
means for manually transferring the infusion data to the infusing means from a source external of the infusing means; and means for prompting for the manual transference of the infusion data.
means for manually transferring the infusion data to the infusing means from a source external of the infusing means; and means for prompting for the manual transference of the infusion data.
24. The apparatus of claim 21 further including:
means for manually transferring the infusion data to the infusing means from a source external of the infusing means; and means for prompting for the manual transference of the infusion data.
means for manually transferring the infusion data to the infusing means from a source external of the infusing means; and means for prompting for the manual transference of the infusion data.
25. The apparatus of claim 21 further including means for confirming the infusion data.
26. The apparatus of claim 21 further including means for entering a program of infusion into the infusing means.
27. The apparatus of claim 26 wherein the infusing means includes means for infusing more than one infusate.
28. The apparatus of claim 27 wherein the program entering means includes means for programming a starting time for the infusion program.
29. The apparatus of claim 21 wherein the infusion data includes data identifying medications in the infusate, data identifying manner of infusion, data identifying dosage of infusate, and data identifying the patient.
30. The apparatus of claim 29 wherein the manner of infusion is continuous.
31. The apparatus of claim 29 wherein the manner of infusion is intermittent.
32. The apparatus of claim 29 further including means for confirming the infusion data.
33. The apparatus of claim 32 wherein the confirming means includes means for checking for missing data.
34. The apparatus of claim 21 further including means for recording occurrences of events during an infusion.
35. The apparatus of claim 34 further including means for printing a record of the event occurrences.
36. An infusion system comprising:
means for pumping at least one fluid to an output line from plural input lines;
means for detecting alarm conditions;
means for recording times at which the alarm conditions occur;
means for assigning each alarm condition a priority;
means for storing each alarm condition; and means for recalling each alarm condition in order of greater priority first and in a chronological order for alarm conditions having general priority.
means for pumping at least one fluid to an output line from plural input lines;
means for detecting alarm conditions;
means for recording times at which the alarm conditions occur;
means for assigning each alarm condition a priority;
means for storing each alarm condition; and means for recalling each alarm condition in order of greater priority first and in a chronological order for alarm conditions having general priority.
37. The infusion system of claim 36 wherein the chronological order is most recent occurrences first.
38. The infusion system of claim 36 further including:
a disposable cassette having means for receiving individual ones of the plural input lines;
means for lockably receiving the cassette in the infusing means; and wherein the alarm conditions include a cassette unlocked alarm and the priority assigning means includes means to assign a first priority to the cassette unlocked alarm.
a disposable cassette having means for receiving individual ones of the plural input lines;
means for lockably receiving the cassette in the infusing means; and wherein the alarm conditions include a cassette unlocked alarm and the priority assigning means includes means to assign a first priority to the cassette unlocked alarm.
39. The infusion system of claim 38 wherein the alarm conditions further include a pump failure alarm and the priority assigning means further includes means for assigning a second priority to the pump failure alarm.
40. The infusion system of claim 39 further including means for stopping pumping on all the input lines when the pump failure alarm occurs.
41. The infusion system of claim 39 wherein the alarm conditions further include an output line occlusion alarm and the priority assigning means further includes means for assigning a third priority to the output line occlusion alarm.
42. The infusion system of claim 41 wherein the alarm conditions further include a full collection container warning and the priority assigning means further includes means for assigning a fourth priority to the full collection container alarm.
43. The infusion system of claim 42 wherein:
one of the input lines is a primary input line;
the alarm conditions further include an alarm that the primary input line contains air and a primary input line occlusion alarm; and the priority assigning means further includes means for assigning a fifth priority to the air in the primary line alarm and to the primary input line occlusion alarm.
one of the input lines is a primary input line;
the alarm conditions further include an alarm that the primary input line contains air and a primary input line occlusion alarm; and the priority assigning means further includes means for assigning a fifth priority to the air in the primary line alarm and to the primary input line occlusion alarm.
44. The infusion system of claim 43 further including means for holding pumping on all the input lines when at least one of the first, third, fourth, and fifth priorities has been assigned.
45. The infusion system of claim 43 wherein:
a remainder of the input lines are secondary input lines;
the alarm conditions further include an alarm that one of the secondary input lines contains air and a secondary input line occlusion alarm; and the priority assigning means further includes means for assigning a sixth priority to the air in the secondary line alarm and to the secondary input line occlusion alarm.
a remainder of the input lines are secondary input lines;
the alarm conditions further include an alarm that one of the secondary input lines contains air and a secondary input line occlusion alarm; and the priority assigning means further includes means for assigning a sixth priority to the air in the secondary line alarm and to the secondary input line occlusion alarm.
46. The infusion system of claim 45 further including means for placing pumping on one of the secondary input lines on hold when the sixth priority has been assigned.
47. The infusion system of claim 45 wherein:
the alarm conditions further include an alarm that the pumping means is unable to pump at a predetermined rate; and the priority assigning means further includes means for assigning a seventh priority to the alarm that the pumping means is unable to pump at a predetermined rate.
the alarm conditions further include an alarm that the pumping means is unable to pump at a predetermined rate; and the priority assigning means further includes means for assigning a seventh priority to the alarm that the pumping means is unable to pump at a predetermined rate.
48. The infusion system of claim 47 further including means to pump at a predetermined keep-vein-open rate when the seventh priority has been assigned and when the sixth priority has been assigned for alarm conditions occurring on all of the secondary input lines.
49. The infusion system of claim 47 wherein:
the alarm conditions further include an empty container on one of the input lines alarm, a callback alarm, a low battery voltage alarm and an alarm that one of the input lines has been manually placed on hold for greater than a predetermined time;
and the priority assigning means includes means for assigning an eighth priority to the empty container alarm, means for assigning a ninth priority to the callback alarm, and means for assigning a tenth priority to the low battery voltage alarm.
the alarm conditions further include an empty container on one of the input lines alarm, a callback alarm, a low battery voltage alarm and an alarm that one of the input lines has been manually placed on hold for greater than a predetermined time;
and the priority assigning means includes means for assigning an eighth priority to the empty container alarm, means for assigning a ninth priority to the callback alarm, and means for assigning a tenth priority to the low battery voltage alarm.
50. A system for infusing fluids into a patient comprising:
means for infusing fluids into a patient in accordance with instructions to carry out a desired course of infusion therapy, including means for generating initial instructions to carry out the desired course of infusion therapy;
means for sensing physiological conditions of the patient; and means for controlling the infusing means in response to the sensed physiological conditions, including means for generating adapted instructions to carry out an adapted course of infusion therapy.
means for infusing fluids into a patient in accordance with instructions to carry out a desired course of infusion therapy, including means for generating initial instructions to carry out the desired course of infusion therapy;
means for sensing physiological conditions of the patient; and means for controlling the infusing means in response to the sensed physiological conditions, including means for generating adapted instructions to carry out an adapted course of infusion therapy.
51. The system of claim 50 wherein:
the controlling means is located remotely from the infusing means.
the controlling means is located remotely from the infusing means.
52. The system of claim 51 wherein:
the controlling means is on line with the infusing means.
the controlling means is on line with the infusing means.
53. The system of claim 51 further including:
means for transferring first signals representative of the sensed physiological conditions to the controlling means and second signals representative of the adapted instructions to the infusing means, the signal transferring means further including a first modem locally associated with the infusing means and a second modem locally associated with the controlling means.
means for transferring first signals representative of the sensed physiological conditions to the controlling means and second signals representative of the adapted instructions to the infusing means, the signal transferring means further including a first modem locally associated with the infusing means and a second modem locally associated with the controlling means.
54. The system of claim 50 wherein:
the initial instructions include infusing a first fluid at a first rate of flow and infusing a second fluid at a second rate of flow; and the adapted instructions include decreasing the first rate of flow of the first fluid and increasing the second rate of flow of the second fluid.
the initial instructions include infusing a first fluid at a first rate of flow and infusing a second fluid at a second rate of flow; and the adapted instructions include decreasing the first rate of flow of the first fluid and increasing the second rate of flow of the second fluid.
55. The system of claim 50 wherein:
the initial instructions include infusing a first fluid;
and the adapted instructions include stopping the infusing of the first fluid and infusing a second fluid.
the initial instructions include infusing a first fluid;
and the adapted instructions include stopping the infusing of the first fluid and infusing a second fluid.
56. The system of claim 50 wherein:
the sensed physiological conditions include at least one of blood pressure, blood sugar level, pulse, respiration rate, and temperature.
the sensed physiological conditions include at least one of blood pressure, blood sugar level, pulse, respiration rate, and temperature.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/304,068 | 1989-01-30 | ||
US07/304,068 US5153827A (en) | 1989-01-30 | 1989-01-30 | An infusion management and pumping system having an alarm handling system |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2008715A1 true CA2008715A1 (en) | 1990-07-30 |
Family
ID=23174923
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002008715A Abandoned CA2008715A1 (en) | 1989-01-30 | 1990-01-26 | Infusion fluid management system |
Country Status (2)
Country | Link |
---|---|
US (3) | US5153827A (en) |
CA (1) | CA2008715A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106139307A (en) * | 2016-08-16 | 2016-11-23 | 肇庆医学高等专科学校 | A kind of vein frame for automatic alarm and APP terminal system |
US11524112B2 (en) * | 2009-12-01 | 2022-12-13 | Sanofi-Aventis Deutschland Gmbh | Drug delivery device and method of operation |
Families Citing this family (674)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6241704B1 (en) | 1901-11-22 | 2001-06-05 | Sims Deltec, Inc. | Drug pump systems and methods |
US5338157B1 (en) * | 1992-09-09 | 1999-11-02 | Sims Deltec Inc | Systems and methods for communicating with ambulat |
US5935099A (en) | 1992-09-09 | 1999-08-10 | Sims Deltec, Inc. | Drug pump systems and methods |
GB8909891D0 (en) * | 1989-04-28 | 1989-06-14 | Riker Laboratories Inc | Device |
US5486286A (en) * | 1991-04-19 | 1996-01-23 | Althin Medical, Inc. | Apparatus for performing a self-test of kidney dialysis membrane |
EP0523308A1 (en) * | 1991-07-19 | 1993-01-20 | GRETAG Aktiengesellschaft | Photometrical method and computer controlled photometer |
US5337044A (en) * | 1991-10-08 | 1994-08-09 | Nomadic Systems, Inc. | System for remote computer control using message broadcasting system |
WO1993012828A1 (en) * | 1991-12-20 | 1993-07-08 | Abbott Laboratories | Drug channel identification and security system for infusion and pumping systems |
FR2690622B1 (en) * | 1992-04-29 | 1995-01-20 | Chronotec | Programmable ambulatory infusion pump system. |
US5511594A (en) * | 1992-06-23 | 1996-04-30 | Brennan; Eric L. | Modular pharmacy system and pharmacy process |
US5383858B1 (en) | 1992-08-17 | 1996-10-29 | Medrad Inc | Front-loading medical injector and syringe for use therewith |
US6402718B1 (en) | 1992-08-17 | 2002-06-11 | Medrad, Inc. | Front-loading medical injector and syringe for use therewith |
US5788669A (en) * | 1995-11-22 | 1998-08-04 | Sims Deltec, Inc. | Pump tracking system |
US5298021A (en) * | 1992-09-24 | 1994-03-29 | Sherer David J | ACLS infusion pump system |
DE69329774T2 (en) * | 1992-10-15 | 2001-06-21 | Gen Hospital Corp | INFUSION PUMP WITH ELECTRONICALLY LOADABLE MEDICINE LIBRARY |
US5719761A (en) † | 1993-01-15 | 1998-02-17 | Alaris Medical Systems, Inc. | Configuration control system for configuring multiple biomedical devices |
AU7323994A (en) * | 1993-07-13 | 1995-02-13 | Sims Deltec, Inc. | Medical pump and method of programming |
EP0650738B1 (en) | 1993-10-28 | 2003-05-02 | Medrad, Inc. | Multi-patient fluid dispensing |
EP1258262A3 (en) | 1993-10-28 | 2002-12-18 | Medrad, Inc. | Total system for contrast delivery |
US5431627A (en) * | 1993-11-12 | 1995-07-11 | Abbott Laboratories | Cassette identification system for use with a multi-program drug infusion pump |
US5531697A (en) * | 1994-04-15 | 1996-07-02 | Sims Deltec, Inc. | Systems and methods for cassette identification for drug pumps |
CH690049A5 (en) * | 1994-03-04 | 2000-03-31 | Microflow Eng Sa | Device for determining an amount of medicament and delivery device of at least one medicament. |
US5658133A (en) * | 1994-03-09 | 1997-08-19 | Baxter International Inc. | Pump chamber back pressure dissipation apparatus and method |
US5630710A (en) * | 1994-03-09 | 1997-05-20 | Baxter International Inc. | Ambulatory infusion pump |
FR2717919B1 (en) * | 1994-03-28 | 1996-06-21 | Ensyma Sa | Medical decision support system and device for administering at least one drug. |
US5486999A (en) * | 1994-04-20 | 1996-01-23 | Mebane; Andrew H. | Apparatus and method for categorizing health care utilization |
DE69526613T2 (en) * | 1994-07-12 | 2002-08-29 | Medrad Inc | Information path control loop for a system that delivers medical fluids |
US5840026A (en) | 1994-09-21 | 1998-11-24 | Medrad, Inc. | Patient specific dosing contrast delivery systems and methods |
US5673588A (en) * | 1995-01-26 | 1997-10-07 | Abbott Laboratories | Infusion pump retraction mechanism |
US5520637A (en) * | 1995-01-31 | 1996-05-28 | Pager; David | Closed-loop system for infusing oxytocin |
US5758095A (en) * | 1995-02-24 | 1998-05-26 | Albaum; David | Interactive medication ordering system |
US7074205B1 (en) * | 1995-03-13 | 2006-07-11 | Cardinal Health 303, Inc. | Method and apparatus for power connection in a modular patient care system |
US7384410B2 (en) * | 1995-03-13 | 2008-06-10 | Cardinal Health 303, Inc. | System and method for managing patient care |
US6126595A (en) * | 1995-05-12 | 2000-10-03 | Seiko Epson Corporation | Device for diagnosing physiological state and device for controlling the same |
US5781442A (en) * | 1995-05-15 | 1998-07-14 | Alaris Medical Systems, Inc. | System and method for collecting data and managing patient care |
US6671563B1 (en) | 1995-05-15 | 2003-12-30 | Alaris Medical Systems, Inc. | System and method for collecting data and managing patient care |
US5772635A (en) * | 1995-05-15 | 1998-06-30 | Alaris Medical Systems, Inc. | Automated infusion system with dose rate calculator |
US5665065A (en) * | 1995-05-26 | 1997-09-09 | Minimed Inc. | Medication infusion device with blood glucose data input |
US5873731A (en) * | 1995-10-20 | 1999-02-23 | Eagle Simulation, Inc. | Patient drug recognition system |
US7925531B1 (en) | 1995-11-13 | 2011-04-12 | TrialCard Incorporated | Method of delivering goods and services via media |
GB9601969D0 (en) * | 1996-01-31 | 1996-04-03 | Meldet Ltd | A system for the delivery of drugs and therapeutic agents |
IL118766A0 (en) | 1996-07-01 | 1996-10-31 | Medun Ltd | Improved infusion apparatus |
US5853386A (en) | 1996-07-25 | 1998-12-29 | Alaris Medical Systems, Inc. | Infusion device with disposable elements |
US6689091B2 (en) | 1996-08-02 | 2004-02-10 | Tuan Bui | Medical apparatus with remote control |
US5885245A (en) * | 1996-08-02 | 1999-03-23 | Sabratek Corporation | Medical apparatus with remote virtual input device |
US5807336A (en) * | 1996-08-02 | 1998-09-15 | Sabratek Corporation | Apparatus for monitoring and/or controlling a medical device |
US5895371A (en) * | 1996-08-27 | 1999-04-20 | Sabratek Corporation | Medical treatment apparatus and method |
US6605057B2 (en) | 1996-10-24 | 2003-08-12 | Medtronic Ave, Inc. | Reinforced monorail balloon catheter |
US5927349A (en) | 1996-12-09 | 1999-07-27 | Baxter International Inc. | Compounding assembly for nutritional fluids |
US6021392A (en) * | 1996-12-09 | 2000-02-01 | Pyxis Corporation | System and method for drug management |
US6611733B1 (en) * | 1996-12-20 | 2003-08-26 | Carlos De La Huerga | Interactive medication dispensing machine |
US6529446B1 (en) * | 1996-12-20 | 2003-03-04 | Telaric L.L.C. | Interactive medication container |
US6824528B1 (en) | 1997-03-03 | 2004-11-30 | Medical Solutions, Inc. | Method and apparatus for pressure infusion and temperature control of infused liquids |
US7090658B2 (en) * | 1997-03-03 | 2006-08-15 | Medical Solutions, Inc. | Temperature sensing device for selectively measuring temperature at desired locations along an intravenous fluid line |
US7061831B2 (en) | 1997-03-28 | 2006-06-13 | Carlos De La Huerga | Product labeling method and apparatus |
US7978564B2 (en) * | 1997-03-28 | 2011-07-12 | Carlos De La Huerga | Interactive medication container |
US6467953B1 (en) | 1999-03-30 | 2002-10-22 | Medical Solutions, Inc. | Method and apparatus for monitoring temperature of intravenously delivered fluids and other medical items |
US7041941B2 (en) * | 1997-04-07 | 2006-05-09 | Patented Medical Solutions, Llc | Medical item thermal treatment systems and method of monitoring medical items for compliance with prescribed requirements |
US6660974B2 (en) | 1997-04-07 | 2003-12-09 | Medical Solutions, Inc. | Warming system and method for heating various items utilized in surgical procedures |
US6012034A (en) * | 1997-08-18 | 2000-01-04 | Becton, Dickinson And Company | System and method for selecting an intravenous device |
US6070761A (en) | 1997-08-22 | 2000-06-06 | Deka Products Limited Partnership | Vial loading method and apparatus for intelligent admixture and delivery of intravenous drugs |
JP4291506B2 (en) * | 1997-08-22 | 2009-07-08 | デカ・プロダクツ・リミテッド・パートナーシップ | Intravenous drug mixing and injection system, method and cassette |
WO1999010830A1 (en) * | 1997-08-22 | 1999-03-04 | Deka Products Limited Partnership | Automated health care system |
US6697783B1 (en) * | 1997-09-30 | 2004-02-24 | Medco Health Solutions, Inc. | Computer implemented medical integrated decision support system |
US6036458A (en) * | 1997-10-03 | 2000-03-14 | Allergan Sales, Inc. | Automated phaco pack bar code reader identification |
US7216802B1 (en) | 1997-10-21 | 2007-05-15 | Carlos De La Huerga | Method and apparatus for verifying information |
US6726650B2 (en) | 1997-12-04 | 2004-04-27 | Bracco Research S.A. | Automatic liquid injection system and method |
AU754594B2 (en) | 1998-04-24 | 2002-11-21 | Indigo Medical, Incorporated | Energy application system with ancillary information exchange capability, energy applicator, and methods associated therewith |
US6949816B2 (en) | 2003-04-21 | 2005-09-27 | Motorola, Inc. | Semiconductor component having first surface area for electrically coupling to a semiconductor chip and second surface area for electrically coupling to a substrate, and method of manufacturing same |
US8974386B2 (en) | 1998-04-30 | 2015-03-10 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods of use |
US8346337B2 (en) | 1998-04-30 | 2013-01-01 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods of use |
US6175752B1 (en) | 1998-04-30 | 2001-01-16 | Therasense, Inc. | Analyte monitoring device and methods of use |
US8480580B2 (en) | 1998-04-30 | 2013-07-09 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods of use |
US8465425B2 (en) | 1998-04-30 | 2013-06-18 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods of use |
US9066695B2 (en) | 1998-04-30 | 2015-06-30 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods of use |
US8688188B2 (en) | 1998-04-30 | 2014-04-01 | Abbott Diabetes Care Inc. | Analyte monitoring device and methods of use |
DE19823240A1 (en) | 1998-05-25 | 1999-12-02 | Braun Melsungen Ag | Device for central control and / or monitoring of infusion pumps |
US6199603B1 (en) | 1998-08-14 | 2001-03-13 | Baxter International Inc. | Compounding assembly for nutritional fluids |
US6554798B1 (en) | 1998-08-18 | 2003-04-29 | Medtronic Minimed, Inc. | External infusion device with remote programming, bolus estimator and/or vibration alarm capabilities |
US6558320B1 (en) * | 2000-01-20 | 2003-05-06 | Medtronic Minimed, Inc. | Handheld personal data assistant (PDA) with a medical device and method of using the same |
US6164921A (en) | 1998-11-09 | 2000-12-26 | Moubayed; Ahmad Maher | Curvilinear peristaltic pump having insertable tubing assembly |
US6398727B1 (en) | 1998-12-23 | 2002-06-04 | Baxter International Inc. | Method and apparatus for providing patient care |
US6231560B1 (en) | 1999-02-10 | 2001-05-15 | Baxter International Inc | Method and apparatus for automatically controlling the level of medication |
JP4122107B2 (en) * | 1999-04-27 | 2008-07-23 | 株式会社湯山製作所 | Injection mixing support device |
US6339718B1 (en) * | 1999-07-30 | 2002-01-15 | Medrad, Inc. | Programmable injector control |
US7933780B2 (en) | 1999-10-22 | 2011-04-26 | Telaric, Llc | Method and apparatus for controlling an infusion pump or the like |
US6958053B1 (en) | 1999-11-24 | 2005-10-25 | Medrad, Inc. | Injector providing drive member advancement and engagement with syringe plunger, and method of connecting a syringe to an injector |
US6519569B1 (en) | 1999-12-01 | 2003-02-11 | B. Braun Medical, Inc. | Security infusion pump with bar code reader |
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 |
US6824052B2 (en) * | 1999-12-28 | 2004-11-30 | Christopher S. Walsh | Healthcare verification methods, apparatus and systems |
US6652489B2 (en) * | 2000-02-07 | 2003-11-25 | Medrad, Inc. | Front-loading medical injector and syringes, syringe interfaces, syringe adapters and syringe plungers for use therewith |
US20030060765A1 (en) * | 2000-02-16 | 2003-03-27 | Arthur Campbell | Infusion device menu structure and method of using the same |
US6461329B1 (en) * | 2000-03-13 | 2002-10-08 | Medtronic Minimed, Inc. | Infusion site leak detection system and method of using the same |
WO2001070304A1 (en) * | 2000-03-22 | 2001-09-27 | Docusys, Inc. | A drug delivery and monitoring system |
US6542902B2 (en) | 2000-03-24 | 2003-04-01 | Bridge Medical, Inc. | Method and apparatus for displaying medication information |
US6533183B2 (en) | 2000-05-03 | 2003-03-18 | Novo Nordisk A/S | Coding of cartridges for an injection device |
WO2001093152A1 (en) * | 2000-05-03 | 2001-12-06 | Silva Joe D | Method and system for using a communications network in the selection and delivery of pharmaceutical formulation information, training and products |
US20040172283A1 (en) * | 2003-02-09 | 2004-09-02 | Vanderveen Timothy W. | Medication management and event logger and analysis system |
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 |
US7860583B2 (en) | 2004-08-25 | 2010-12-28 | Carefusion 303, Inc. | System and method for dynamically adjusting patient therapy |
US20050171815A1 (en) * | 2003-12-31 | 2005-08-04 | Vanderveen Timothy W. | Centralized medication management system |
US9069887B2 (en) | 2000-05-18 | 2015-06-30 | Carefusion 303, Inc. | Patient-specific medication management system |
WO2001088828A2 (en) | 2000-05-18 | 2001-11-22 | Alaris Medical Systems, Inc. | Distributed remote asset and medication management drug delivery system |
US10353856B2 (en) | 2011-03-17 | 2019-07-16 | Carefusion 303, Inc. | Scalable communication system |
US9427520B2 (en) | 2005-02-11 | 2016-08-30 | Carefusion 303, Inc. | Management of pending medication orders |
TW499314B (en) * | 2000-05-30 | 2002-08-21 | Novo Nordisk As | A medication delivery device with replaceable cooperating modules and a method of making same |
US6565535B2 (en) * | 2000-06-16 | 2003-05-20 | Nardo Zaias | Medical infusion and aspiration system |
AU2001278187A1 (en) * | 2000-07-07 | 2002-01-21 | Fluidsense Corporation | Method and apparatus for determining air content and pressure of a liquid in an infusion line |
AUPQ867900A0 (en) | 2000-07-10 | 2000-08-03 | Medrad, Inc. | Medical injector system |
US9135393B1 (en) * | 2000-08-02 | 2015-09-15 | Smiths Medical Asd, Inc. | Processing program data for medical pumps |
EP1309366B1 (en) | 2000-08-10 | 2007-02-21 | Novo Nordisk A/S | Medication delivery device comprising a support for a cartridge |
US6994261B2 (en) * | 2000-08-10 | 2006-02-07 | Novo Nirdisk A/S | Support for a cartridge for transferring an electronically readable item of information from the cartridge to an electronic circuit |
US8565860B2 (en) | 2000-08-21 | 2013-10-22 | Biosensors International Group, Ltd. | Radioactive emission detector equipped with a position tracking system |
WO2005119025A2 (en) | 2004-06-01 | 2005-12-15 | Spectrum Dynamics Llc | Radioactive-emission-measurement optimization to specific body structures |
US8489176B1 (en) | 2000-08-21 | 2013-07-16 | Spectrum Dynamics Llc | Radioactive emission detector equipped with a position tracking system and utilization thereof with medical systems and in medical procedures |
US8909325B2 (en) | 2000-08-21 | 2014-12-09 | Biosensors International Group, Ltd. | Radioactive emission detector equipped with a position tracking system and utilization thereof with medical systems and in medical procedures |
US6932517B2 (en) | 2000-10-27 | 2005-08-23 | Ethicon Endo-Surgery, Inc. | Connector incorporating a contact pad surface on a plane parallel to a longitudinal axis |
ATE439643T1 (en) * | 2000-11-29 | 2009-08-15 | Docusys Inc | DEVICE FOR DISPENSING A MEDICINAL PRODUCT WITH A TRACKING CODE |
US20020087360A1 (en) * | 2001-01-02 | 2002-07-04 | Pettit Stephen W. | Immunization tracking method |
US6560471B1 (en) | 2001-01-02 | 2003-05-06 | Therasense, Inc. | Analyte monitoring device and methods of use |
US7238171B2 (en) | 2001-03-12 | 2007-07-03 | Medical Solutions, Inc. | Method and apparatus for controlling pressurized infusion and temperature of infused liquids |
US7031602B2 (en) | 2001-03-12 | 2006-04-18 | Patented Medical Solutions, Llc | Method and apparatus for controlling temperature of infused liquids |
EP1397068A2 (en) | 2001-04-02 | 2004-03-17 | Therasense, Inc. | Blood glucose tracking apparatus and methods |
US6574861B1 (en) | 2001-04-11 | 2003-06-10 | Applied Micro Circuits Corporation | System and method for solder ball rework |
US20030040835A1 (en) * | 2001-04-28 | 2003-02-27 | Baxter International Inc. | A system and method for managing inventory of blood component collection soft goods in a blood component collection facility |
EP2140891B1 (en) | 2001-05-18 | 2013-03-27 | DEKA Products Limited Partnership | Conduit for coupling to a fluid delivery device |
US8034026B2 (en) | 2001-05-18 | 2011-10-11 | Deka Products Limited Partnership | Infusion pump assembly |
US20020184369A1 (en) * | 2001-05-31 | 2002-12-05 | Parkinson Steven William | Appointment scheme for redistributing service access |
KR100407467B1 (en) * | 2001-07-12 | 2003-11-28 | 최수봉 | Insulin pump operated by remote-controller |
US20030055685A1 (en) * | 2001-09-19 | 2003-03-20 | Safety Syringes, Inc. | Systems and methods for monitoring administration of medical products |
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 |
US8226605B2 (en) | 2001-12-17 | 2012-07-24 | Medical Solutions, Inc. | Method and apparatus for heating solutions within intravenous lines to desired temperatures during infusion |
JP4101511B2 (en) * | 2001-12-27 | 2008-06-18 | 株式会社半導体エネルギー研究所 | Light emitting device and manufacturing method thereof |
US20030125662A1 (en) | 2002-01-03 | 2003-07-03 | Tuan Bui | Method and apparatus for providing medical treatment therapy based on calculated demand |
US6985870B2 (en) | 2002-01-11 | 2006-01-10 | Baxter International Inc. | Medication delivery system |
US20070167853A1 (en) * | 2002-01-22 | 2007-07-19 | Melker Richard J | System and method for monitoring health using exhaled breath |
AU2003217253A1 (en) * | 2002-01-25 | 2003-09-02 | Intellipatch, Inc. | Evaluation of a patient and prediction of chronic symptoms |
US7698156B2 (en) * | 2002-01-29 | 2010-04-13 | Baxter International Inc. | System and method for identifying data streams associated with medical equipment |
US20030140929A1 (en) * | 2002-01-29 | 2003-07-31 | Wilkes Gordon J. | Infusion therapy bar coding system and method |
US20030141368A1 (en) * | 2002-01-29 | 2003-07-31 | Florante Pascual | System and method for obtaining information from a bar code for use with a healthcare system |
US20040010425A1 (en) * | 2002-01-29 | 2004-01-15 | Wilkes Gordon J. | System and method for integrating clinical documentation with the point of care treatment of a patient |
US20030141981A1 (en) * | 2002-01-29 | 2003-07-31 | Tuan Bui | System and method for operating medical devices |
US8775196B2 (en) | 2002-01-29 | 2014-07-08 | Baxter International Inc. | System and method for notification and escalation of medical data |
US10173008B2 (en) | 2002-01-29 | 2019-01-08 | Baxter International Inc. | System and method for communicating with a dialysis machine through a network |
US20030144878A1 (en) * | 2002-01-29 | 2003-07-31 | Wilkes Gordon J. | System and method for providing multiple units of measure |
AU2003217727A1 (en) * | 2002-02-26 | 2003-09-09 | Safety Syringes, Inc. | Systems and methods for tracking pharmaceuticals |
US20030160698A1 (en) * | 2002-02-26 | 2003-08-28 | Safety Syringes, Inc. | Systems and methods for tracking pharmaceuticals within a facility |
US6935560B2 (en) * | 2002-02-26 | 2005-08-30 | Safety Syringes, Inc. | Systems and methods for tracking pharmaceuticals within a facility |
US8504179B2 (en) * | 2002-02-28 | 2013-08-06 | Smiths Medical Asd, Inc. | Programmable medical infusion pump |
US8250483B2 (en) | 2002-02-28 | 2012-08-21 | Smiths Medical Asd, Inc. | Programmable medical infusion pump displaying a banner |
US7109974B2 (en) * | 2002-03-05 | 2006-09-19 | Matsushita Electric Industrial Co., Ltd. | Remote control system including an on-screen display (OSD) |
US6959865B2 (en) * | 2002-03-28 | 2005-11-01 | Hand Held Products, Inc. | Customizable optical reader |
US20030193395A1 (en) * | 2002-04-10 | 2003-10-16 | Yavuz Ahiska | Allocation of network bandwidth and prioritization in networks |
CA2484977C (en) * | 2002-04-30 | 2013-03-12 | Baxter International Inc. | System and method for identifying data streams associated with medical equipment |
US20030204416A1 (en) * | 2002-04-30 | 2003-10-30 | Sayeh Radpay | System and method for facilitating time-based infusion orders |
US8234128B2 (en) | 2002-04-30 | 2012-07-31 | Baxter International, Inc. | System and method for verifying medical device operational parameters |
CN1668358A (en) * | 2002-05-16 | 2005-09-14 | 斯科特实验室公司 | Kits of medical supplies for sedation and analgesia |
US7553294B2 (en) | 2002-05-30 | 2009-06-30 | Medrad, Inc. | Syringe plunger sensing mechanism for a medical injector |
US20030225728A1 (en) * | 2002-05-31 | 2003-12-04 | Moura Anthony A. | Pharmacy system and method |
US20040078231A1 (en) * | 2002-05-31 | 2004-04-22 | Wilkes Gordon J. | System and method for facilitating and administering treatment to a patient, including clinical decision making, order workflow and integration of clinical documentation |
US6997905B2 (en) | 2002-06-14 | 2006-02-14 | Baxter International Inc. | Dual orientation display for a medical device |
US7018361B2 (en) | 2002-06-14 | 2006-03-28 | Baxter International Inc. | Infusion pump |
US20040068230A1 (en) * | 2002-07-24 | 2004-04-08 | Medtronic Minimed, Inc. | System for providing blood glucose measurements to an infusion device |
US7278983B2 (en) * | 2002-07-24 | 2007-10-09 | Medtronic Minimed, Inc. | Physiological monitoring device for controlling a medication infusion device |
US20040051368A1 (en) * | 2002-09-17 | 2004-03-18 | Jimmy Caputo | Systems and methods for programming pumps |
US20040077996A1 (en) * | 2002-10-22 | 2004-04-22 | Jasperson Keith E. | Drug infusion system with multiple medications |
US7860724B2 (en) * | 2002-10-30 | 2010-12-28 | Automed Technologies, Inc. | System and method for management of pharmacy workflow |
US8095378B2 (en) * | 2002-11-14 | 2012-01-10 | Cerner Innovation, Inc. | Automated system for managing the selection of clinical items and documentation for a clinical event |
US20040122353A1 (en) | 2002-12-19 | 2004-06-24 | Medtronic Minimed, Inc. | Relay device for transferring information between a sensor system and a fluid delivery system |
US7835927B2 (en) * | 2002-12-27 | 2010-11-16 | Carefusion 303, Inc. | Medication management system |
AU2003303597A1 (en) | 2002-12-31 | 2004-07-29 | Therasense, Inc. | Continuous glucose monitoring system and methods of use |
DE602004015432D1 (en) * | 2003-03-24 | 2008-09-11 | Novo Nordisk As | TRANSPARENT ELECTRONIC MARKING OF A MEDICATION CONTAINER |
US20040193325A1 (en) * | 2003-03-25 | 2004-09-30 | David Bonderud | Method and apparatus to prevent medication error in a networked infusion system |
US7587287B2 (en) | 2003-04-04 | 2009-09-08 | Abbott Diabetes Care Inc. | Method and system for transferring analyte test data |
EP1631237B1 (en) * | 2003-05-16 | 2016-11-30 | Acorda Therapeutics, Inc. | Proteoglycan degrading mutants for treatment of cns |
US8066639B2 (en) | 2003-06-10 | 2011-11-29 | Abbott Diabetes Care Inc. | Glucose measuring device for use in personal area network |
US7419478B1 (en) | 2003-06-25 | 2008-09-02 | Medrad, Inc. | Front-loading syringe for medical injector having a flexible syringe retaining ring |
US7591801B2 (en) * | 2004-02-26 | 2009-09-22 | Dexcom, Inc. | Integrated delivery device for continuous glucose sensor |
DE10341313A1 (en) * | 2003-09-08 | 2005-04-07 | B. Braun Melsungen Ag | Barcode arrangement for storing medical information comprises barcode elements having identification elements for testing the bond of the barcode elements using a barcode laser |
US7272445B2 (en) * | 2003-10-02 | 2007-09-18 | Medtronic, Inc. | Medical device programmer with faceplate |
US20060243804A1 (en) * | 2003-10-03 | 2006-11-02 | Novo Nordisk A/S | Container comprising code information elements |
US7490021B2 (en) * | 2003-10-07 | 2009-02-10 | Hospira, Inc. | Method for adjusting pump screen brightness |
US20050278194A1 (en) * | 2003-10-07 | 2005-12-15 | Holland Geoffrey N | Medication management system |
US7895053B2 (en) * | 2003-10-07 | 2011-02-22 | Hospira, Inc. | Medication management system |
US20060100907A1 (en) * | 2003-10-07 | 2006-05-11 | Holland Geoffrey N | Medication management system |
US9123077B2 (en) * | 2003-10-07 | 2015-09-01 | Hospira, Inc. | Medication management system |
US8065161B2 (en) | 2003-11-13 | 2011-11-22 | Hospira, Inc. | System for maintaining drug information and communicating with medication delivery devices |
US20070214003A1 (en) * | 2003-10-07 | 2007-09-13 | Holland Geoffrey N | Medication management system |
US20060089855A1 (en) * | 2003-10-07 | 2006-04-27 | Holland Geoffrey N | Medication management system |
US20060089854A1 (en) * | 2003-10-07 | 2006-04-27 | Holland Geoffrey N | Medication management system |
US20050086071A1 (en) * | 2003-10-15 | 2005-04-21 | Fox Charles S.Jr. | System and method for managing patient care |
US20050251418A1 (en) * | 2003-10-15 | 2005-11-10 | Cerner Innovation, Inc. | System and method for processing ad hoc orders in an automated patient care environment |
US7690558B2 (en) * | 2003-10-15 | 2010-04-06 | Cemer Innovation, Inc. | Utilizing scanned supply information and a patient task list to document care |
US20050086072A1 (en) * | 2003-10-15 | 2005-04-21 | Fox Charles S.Jr. | Task-based system and method for managing patient care through automated recognition |
EP1527792A1 (en) * | 2003-10-27 | 2005-05-04 | Novo Nordisk A/S | Medical injection device mountable to the skin |
US7896572B2 (en) * | 2003-10-30 | 2011-03-01 | Hospira, Inc. | Medical device system |
US7417729B2 (en) * | 2003-11-07 | 2008-08-26 | Cardinal Health 303, Inc. | Fluid verification system and method for infusions |
US7666169B2 (en) | 2003-11-25 | 2010-02-23 | Medrad, Inc. | Syringe and syringe plungers for use with medical injectors |
US8020564B2 (en) * | 2003-12-01 | 2011-09-20 | Carefusion 303, Inc. | System and method for analyzing medical treatment data |
EP1692635A2 (en) | 2003-12-05 | 2006-08-23 | Cardinal Health 303, Inc. | System and method for network monitoring of multiple medical devices |
WO2005057879A1 (en) * | 2003-12-05 | 2005-06-23 | Cardinal Health 303, Inc. | Discovery and connection management with mobile systems manager |
US20050149355A1 (en) * | 2004-01-02 | 2005-07-07 | Cyr Keneth K. | System and method for management of clinical supply operations |
US20050149379A1 (en) * | 2004-01-02 | 2005-07-07 | Cyr Keneth K. | System and method for management of clinical supply operations |
US20050149356A1 (en) * | 2004-01-02 | 2005-07-07 | Cyr Keneth K. | System and method for management of clinical supply operations |
US20050149354A1 (en) * | 2004-01-02 | 2005-07-07 | Cyr Keneth K. | System and method for management of clinical supply operations |
US7968851B2 (en) | 2004-01-13 | 2011-06-28 | Spectrum Dynamics Llc | Dynamic spect camera |
US9470801B2 (en) | 2004-01-13 | 2016-10-18 | Spectrum Dynamics Llc | Gating with anatomically varying durations |
US8586932B2 (en) | 2004-11-09 | 2013-11-19 | Spectrum Dynamics Llc | System and method for radioactive emission measurement |
WO2008010227A2 (en) | 2006-07-19 | 2008-01-24 | Spectrum Dynamics Llc | Imaging protocols |
US8571881B2 (en) | 2004-11-09 | 2013-10-29 | Spectrum Dynamics, Llc | Radiopharmaceutical dispensing, administration, and imaging |
WO2007010534A2 (en) | 2005-07-19 | 2007-01-25 | Spectrum Dynamics Llc | Imaging protocols |
CN1981210A (en) | 2004-01-13 | 2007-06-13 | 光谱动力学有限责任公司 | Multi-dimensional image reconstruction |
US7571851B2 (en) * | 2004-01-29 | 2009-08-11 | Cerner Innovations, Inc. | Computerized system and method for processing a number of attachments associated with a patient |
US7823767B2 (en) * | 2004-01-29 | 2010-11-02 | Cerner Innovation, Inc. | Computerized system and method for determining whether a location on a patient's body is available for an attachment |
US7506807B2 (en) * | 2004-01-29 | 2009-03-24 | Cerner Innovation, Inc. | Computerized system and method for determining whether a consumable may be safely administered to a body site of a patient |
EP1718198A4 (en) | 2004-02-17 | 2008-06-04 | Therasense Inc | Method and system for providing data communication in continuous glucose monitoring and management system |
US8954336B2 (en) | 2004-02-23 | 2015-02-10 | Smiths Medical Asd, Inc. | Server for medical device |
US7145553B2 (en) * | 2004-02-24 | 2006-12-05 | Research In Motion Limited | Handheld electronic device having facilitated input and associated method |
US7598946B2 (en) * | 2004-02-24 | 2009-10-06 | Research In Motion Limited | Handheld electronic device having facilitated input and associated method |
US8092549B2 (en) | 2004-09-24 | 2012-01-10 | The Invention Science Fund I, Llc | Ciliated stent-like-system |
US8512219B2 (en) | 2004-04-19 | 2013-08-20 | The Invention Science Fund I, Llc | Bioelectromagnetic interface system |
US8024036B2 (en) | 2007-03-19 | 2011-09-20 | The Invention Science Fund I, Llc | Lumen-traveling biological interface device and method of use |
US7998060B2 (en) | 2004-04-19 | 2011-08-16 | The Invention Science Fund I, Llc | Lumen-traveling delivery device |
US9011329B2 (en) | 2004-04-19 | 2015-04-21 | Searete Llc | Lumenally-active device |
US7850676B2 (en) | 2004-04-19 | 2010-12-14 | The Invention Science Fund I, Llc | System with a reservoir for perfusion management |
US8353896B2 (en) | 2004-04-19 | 2013-01-15 | The Invention Science Fund I, Llc | Controllable release nasal system |
US8337482B2 (en) | 2004-04-19 | 2012-12-25 | The Invention Science Fund I, Llc | System for perfusion management |
US8361013B2 (en) | 2004-04-19 | 2013-01-29 | The Invention Science Fund I, Llc | Telescoping perfusion management system |
US7857767B2 (en) | 2004-04-19 | 2010-12-28 | Invention Science Fund I, Llc | Lumen-traveling device |
US20050251054A1 (en) * | 2004-05-10 | 2005-11-10 | Medpond, Llc | Method and apparatus for measurement of autonomic nervous system function |
WO2005110214A2 (en) * | 2004-05-10 | 2005-11-24 | Meddorna, Llc | Method and apparatus for facilitating the provision of health care services |
US20050251051A1 (en) * | 2004-05-10 | 2005-11-10 | Medpond, Llc | Method and apparatus for assessing autonomic function |
WO2005111926A1 (en) * | 2004-05-18 | 2005-11-24 | Silverbrook Research Pty Ltd | Method and apparatus for security document tracking |
US8961461B2 (en) | 2004-05-27 | 2015-02-24 | Baxter International Inc. | Multi-state alarm system for a medical pump |
US20050277873A1 (en) * | 2004-05-27 | 2005-12-15 | Janice Stewart | Identification information recognition system for a medical device |
US7927313B2 (en) * | 2004-05-27 | 2011-04-19 | Baxter International Inc. | Medical device configuration based on recognition of identification information |
US20060020490A1 (en) * | 2004-07-20 | 2006-01-26 | Staton Paul E Jr | Database and model for monitoring and predicting outcomes with vascular access devices |
US8398592B2 (en) * | 2004-09-07 | 2013-03-19 | Thomas Leibner-Druska | Medication data transfer system and method for patient infusions |
EP1827505A4 (en) | 2004-11-09 | 2017-07-12 | Biosensors International Group, Ltd. | Radioimaging |
US8615405B2 (en) * | 2004-11-09 | 2013-12-24 | Biosensors International Group, Ltd. | Imaging system customization using data from radiopharmaceutical-associated data carrier |
US8423125B2 (en) | 2004-11-09 | 2013-04-16 | Spectrum Dynamics Llc | Radioimaging |
US9316743B2 (en) | 2004-11-09 | 2016-04-19 | Biosensors International Group, Ltd. | System and method for radioactive emission measurement |
US9943274B2 (en) | 2004-11-09 | 2018-04-17 | Spectrum Dynamics Medical Limited | Radioimaging using low dose isotope |
JP2008520287A (en) * | 2004-11-16 | 2008-06-19 | メドラッド インコーポレーテッド | System and method for determining patient transfer function for drug infusion and modeling patient response |
WO2008059489A2 (en) | 2006-11-13 | 2008-05-22 | Spectrum Dynamics Llc | Radioimaging applications of and novel formulations of teboroxime |
EP2902053B1 (en) | 2004-11-24 | 2017-09-06 | Bayer Healthcare LLC | Devices, systems and methods for fluid delivery |
US20060116639A1 (en) * | 2004-11-29 | 2006-06-01 | Russell Claudia J | Total patient input monitoring |
US20060149599A1 (en) * | 2005-01-03 | 2006-07-06 | Cerner Innovation, Inc. | System and method for automatically generating physician orders for urgent care |
US7575567B2 (en) * | 2005-01-31 | 2009-08-18 | Simpkins Dale H | Multiple medication IV pump |
US8374887B1 (en) | 2005-02-11 | 2013-02-12 | Emily H. Alexander | System and method for remotely supervising and verifying pharmacy functions |
DE602006014838D1 (en) * | 2005-04-06 | 2010-07-22 | Mallinckrodt Inc | A system for managing information regarding a syringe and a medical fluid |
US8112240B2 (en) | 2005-04-29 | 2012-02-07 | Abbott Diabetes Care Inc. | Method and apparatus for providing leak detection in data monitoring and management systems |
WO2006120182A1 (en) | 2005-05-10 | 2006-11-16 | Novo Nordisk A/S | Injection device comprising an optical sensor |
WO2006124775A2 (en) * | 2005-05-16 | 2006-11-23 | Mallinckrodt Inc. | Radiopharmaceutical pigs and portable powered injectors |
US20060287884A1 (en) * | 2005-06-21 | 2006-12-21 | Sandy Neal J | Pre-delivery drug identification system |
US7991627B2 (en) * | 2005-06-21 | 2011-08-02 | General Electric Company | Injected drug identification and fail-safe system |
US8837793B2 (en) | 2005-07-19 | 2014-09-16 | Biosensors International Group, Ltd. | Reconstruction stabilizer and active vision |
US8638108B2 (en) | 2005-09-22 | 2014-01-28 | Novo Nordisk A/S | Device and method for contact free absolute position determination |
US7766829B2 (en) | 2005-11-04 | 2010-08-03 | Abbott Diabetes Care Inc. | Method and system for providing basal profile modification in analyte monitoring and management systems |
US7654456B2 (en) * | 2005-11-30 | 2010-02-02 | Basf Corporation | Method and system for managing supplies and performance in a collision center |
CN101394875B (en) * | 2006-01-06 | 2011-04-20 | 雷纳尔解决方法公司 | Dual purpose acute and home treatment dialysis machine |
CN101395611A (en) * | 2006-01-06 | 2009-03-25 | 雷纳尔解决方法公司 | Dialysis machine with transport mode |
US7641612B1 (en) | 2006-01-17 | 2010-01-05 | Mccall Kenneth Shawn | Blood loss detection for hemodialysis system |
CN104162200B (en) | 2006-02-09 | 2018-03-27 | 德卡产品有限公司 | peripheral system |
US11364335B2 (en) | 2006-02-09 | 2022-06-21 | Deka Products Limited Partnership | Apparatus, system and method for fluid delivery |
US11497846B2 (en) | 2006-02-09 | 2022-11-15 | Deka Products Limited Partnership | Patch-sized fluid delivery systems and methods |
US11478623B2 (en) | 2006-02-09 | 2022-10-25 | Deka Products Limited Partnership | Infusion pump assembly |
US7967202B2 (en) * | 2006-02-10 | 2011-06-28 | Cerner Innovation, Inc. | Computerized system and method for managing consumables and attachments |
US8076244B2 (en) * | 2006-02-10 | 2011-12-13 | Micron Technology, Inc. | Methods for causing fluid to flow through or into via holes, vents and other openings or recesses that communicate with surfaces of substrates of semiconductor device components |
US8926569B2 (en) | 2006-03-15 | 2015-01-06 | Bayer Medical Care Inc. | Plunger covers and plungers for use in syringes and methods of fabricating plunger covers and plungers for use in syringes |
WO2007107562A2 (en) | 2006-03-20 | 2007-09-27 | Novo Nordisk A/S | Contact free reading of cartridge identification codes |
US8487738B2 (en) | 2006-03-20 | 2013-07-16 | Medical Solutions, Inc. | Method and apparatus for securely storing medical items within a thermal treatment system |
WO2007126948A2 (en) * | 2006-03-28 | 2007-11-08 | Hospira, Inc. | Medication administration and management system and method |
US8226891B2 (en) | 2006-03-31 | 2012-07-24 | Abbott Diabetes Care Inc. | Analyte monitoring devices and methods therefor |
US7620438B2 (en) | 2006-03-31 | 2009-11-17 | Abbott Diabetes Care Inc. | Method and system for powering an electronic device |
US20080033368A1 (en) * | 2006-04-04 | 2008-02-07 | Mallinckrodt Inc. | Systems and methods for managing information relating to medical fluids and containers therefor |
EP2011223B1 (en) | 2006-04-12 | 2018-06-13 | Novo Nordisk A/S | Absolute position determination of movably mounted member in medication delivery device |
US20120035437A1 (en) | 2006-04-12 | 2012-02-09 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Navigation of a lumen traveling device toward a target |
RU2431805C2 (en) * | 2006-04-26 | 2011-10-20 | Ново Нордиск А/С | Method of contactless determination of medicine delivery device movable element position |
US20070253380A1 (en) * | 2006-04-28 | 2007-11-01 | James Jollota | Data translation device with nonvolatile memory for a networked medical device system |
US20070254593A1 (en) * | 2006-04-28 | 2007-11-01 | Medtronic Minimed, Inc. | Wireless data communication for a medical device network that supports a plurality of data communication modes |
US20070255125A1 (en) * | 2006-04-28 | 2007-11-01 | Moberg Sheldon B | Monitor devices for networked fluid infusion systems |
US8073008B2 (en) | 2006-04-28 | 2011-12-06 | Medtronic Minimed, Inc. | Subnetwork synchronization and variable transmit synchronization techniques for a wireless medical device network |
US20070255126A1 (en) * | 2006-04-28 | 2007-11-01 | Moberg Sheldon B | Data communication in networked fluid infusion systems |
US8894974B2 (en) | 2006-05-11 | 2014-11-25 | Spectrum Dynamics Llc | Radiopharmaceuticals for diagnosis and therapy |
US7920907B2 (en) | 2006-06-07 | 2011-04-05 | Abbott Diabetes Care Inc. | Analyte monitoring system and method |
US20070290029A1 (en) * | 2006-06-15 | 2007-12-20 | Cerner Innovation, Inc. | Updating financial records to reflect the use of supply items for a patient |
US20070290030A1 (en) * | 2006-06-15 | 2007-12-20 | Cerner Innovation, Inc. | Updating supply inventory data to reflect the use of a medical supply item for a patient |
US7601966B2 (en) * | 2006-06-28 | 2009-10-13 | Spectrum Dynamics Llc | Imaging techniques for reducing blind spots |
WO2008008281A2 (en) | 2006-07-07 | 2008-01-17 | Proteus Biomedical, Inc. | Smart parenteral administration system |
US8858526B2 (en) | 2006-08-03 | 2014-10-14 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US8435206B2 (en) | 2006-08-03 | 2013-05-07 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US8149131B2 (en) | 2006-08-03 | 2012-04-03 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US8965707B2 (en) | 2006-08-03 | 2015-02-24 | Smiths Medical Asd, Inc. | Interface for medical infusion pump |
US20080058772A1 (en) * | 2006-08-31 | 2008-03-06 | Robertson Timothy L | Personal paramedic |
US8025634B1 (en) * | 2006-09-18 | 2011-09-27 | Baxter International Inc. | Method and system for controlled infusion of therapeutic substances |
AU2007317669A1 (en) | 2006-10-16 | 2008-05-15 | Hospira, Inc. | System and method for comparing and utilizing activity information and configuration information from mulitple device management systems |
US9275451B2 (en) | 2006-12-20 | 2016-03-01 | Biosensors International Group, Ltd. | Method, a system, and an apparatus for using and processing multidimensional data |
US20080214919A1 (en) * | 2006-12-26 | 2008-09-04 | Lifescan, Inc. | System and method for implementation of glycemic control protocols |
WO2008082937A2 (en) * | 2006-12-29 | 2008-07-10 | Medrad, Inc. | Modeling of pharmaceutical propagation |
EP3376504A1 (en) | 2006-12-29 | 2018-09-19 | Bayer Healthcare, LLC | Patient-based parameter generation systems for medical injection procedures |
US8088097B2 (en) * | 2007-11-21 | 2012-01-03 | Glumetrics, Inc. | Use of an equilibrium intravascular sensor to achieve tight glycemic control |
US8738107B2 (en) | 2007-05-10 | 2014-05-27 | Medtronic Minimed, Inc. | Equilibrium non-consuming fluorescence sensor for real time intravascular glucose measurement |
EP2989975B1 (en) | 2007-02-06 | 2018-06-13 | Medtronic MiniMed, Inc. | Optical systems and methods for rationmetric measurement of blood glucose concentration |
US8930203B2 (en) | 2007-02-18 | 2015-01-06 | Abbott Diabetes Care Inc. | Multi-function analyte test device and methods therefor |
US8732188B2 (en) | 2007-02-18 | 2014-05-20 | Abbott Diabetes Care Inc. | Method and system for providing contextual based medication dosage determination |
US8226293B2 (en) | 2007-02-22 | 2012-07-24 | Medical Solutions, Inc. | Method and apparatus for measurement and control of temperature for infused liquids |
US8123686B2 (en) | 2007-03-01 | 2012-02-28 | Abbott Diabetes Care Inc. | Method and apparatus for providing rolling data in communication systems |
US20080228056A1 (en) | 2007-03-13 | 2008-09-18 | Michael Blomquist | Basal rate testing using frequent blood glucose input |
USD942005S1 (en) | 2007-03-14 | 2022-01-25 | Bayer Healthcare Llc | Orange syringe plunger cover |
USD1002840S1 (en) | 2007-03-14 | 2023-10-24 | Bayer Healthcare Llc | Syringe plunger |
USD847985S1 (en) | 2007-03-14 | 2019-05-07 | Bayer Healthcare Llc | Syringe plunger cover |
WO2008113772A1 (en) | 2007-03-21 | 2008-09-25 | Novo Nordisk A/S | A medical delivery system having container recognition and container for use with the medical delivery system |
FR2915105A1 (en) † | 2007-04-19 | 2008-10-24 | Gambro Lundia Ab | MEDICAL FLUID TREATMENT APPARATUS AND METHOD FOR PREPARING MEDICAL FLUID TREATMENT APPARATUS. |
US8954354B2 (en) * | 2007-05-02 | 2015-02-10 | Carefusion 303, Inc. | Automated intravenous fluid container delivery device and system |
US11224551B2 (en) | 2007-05-02 | 2022-01-18 | Carefusion 303, Inc. | Automated intravenous fluid container delivery device and system |
US8257337B2 (en) * | 2007-05-02 | 2012-09-04 | Carefusion 303, Inc. | Intravenous fluid container |
US8461985B2 (en) | 2007-05-08 | 2013-06-11 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US8665091B2 (en) | 2007-05-08 | 2014-03-04 | Abbott Diabetes Care Inc. | Method and device for determining elapsed sensor life |
US7928850B2 (en) | 2007-05-08 | 2011-04-19 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US8456301B2 (en) | 2007-05-08 | 2013-06-04 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods |
US7751907B2 (en) | 2007-05-24 | 2010-07-06 | Smiths Medical Asd, Inc. | Expert system for insulin pump therapy |
US8221345B2 (en) | 2007-05-30 | 2012-07-17 | Smiths Medical Asd, Inc. | Insulin pump based expert system |
US20080300572A1 (en) * | 2007-06-01 | 2008-12-04 | Medtronic Minimed, Inc. | Wireless monitor for a personal medical device system |
DE602008002762D1 (en) * | 2007-06-09 | 2010-11-04 | Novo Nordisk As | CONTACT-FREE READING OF MEMORY IDENTIFICATION CODES |
EP2170165B1 (en) | 2007-07-17 | 2018-12-05 | Bayer Healthcare LLC | Systems for determination of parameters for a procedure, for estimation of cardiopulmonary function and for fluid delivery |
US20090150484A1 (en) * | 2007-08-10 | 2009-06-11 | Smiths Medical Md | Medical device metadata |
US8062008B2 (en) | 2007-09-27 | 2011-11-22 | Curlin Medical Inc. | Peristaltic pump and removable cassette therefor |
US8083503B2 (en) | 2007-09-27 | 2011-12-27 | Curlin Medical Inc. | Peristaltic pump assembly and regulator therefor |
US7934912B2 (en) | 2007-09-27 | 2011-05-03 | Curlin Medical Inc | Peristaltic pump assembly with cassette and mounting pin arrangement |
WO2009055733A1 (en) | 2007-10-25 | 2009-04-30 | Proteus Biomedical, Inc. | Fluid transfer port information system |
US8521253B2 (en) | 2007-10-29 | 2013-08-27 | Spectrum Dynamics Llc | Prostate imaging |
US20090112626A1 (en) * | 2007-10-30 | 2009-04-30 | Cary Talbot | Remote wireless monitoring, processing, and communication of patient data |
WO2009067463A1 (en) | 2007-11-19 | 2009-05-28 | Proteus Biomedical, Inc. | Body-associated fluid transport structure evaluation devices |
US9026370B2 (en) * | 2007-12-18 | 2015-05-05 | Hospira, Inc. | User interface improvements for medical devices |
US8636670B2 (en) | 2008-05-13 | 2014-01-28 | The Invention Science Fund I, Llc | Circulatory monitoring systems and methods |
US20090287120A1 (en) | 2007-12-18 | 2009-11-19 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Circulatory monitoring systems and methods |
US8280484B2 (en) | 2007-12-18 | 2012-10-02 | The Invention Science Fund I, Llc | System, devices, and methods for detecting occlusions in a biological subject |
US9672471B2 (en) | 2007-12-18 | 2017-06-06 | Gearbox Llc | Systems, devices, and methods for detecting occlusions in a biological subject including spectral learning |
US9717896B2 (en) | 2007-12-18 | 2017-08-01 | Gearbox, Llc | Treatment indications informed by a priori implant information |
US20090287094A1 (en) * | 2008-05-15 | 2009-11-19 | Seacrete Llc, A Limited Liability Corporation Of The State Of Delaware | Circulatory monitoring systems and methods |
US8313467B2 (en) | 2007-12-27 | 2012-11-20 | Medtronic Minimed, Inc. | Reservoir pressure equalization systems and methods |
US10188787B2 (en) | 2007-12-31 | 2019-01-29 | Deka Products Limited Partnership | Apparatus, system and method for fluid delivery |
US8881774B2 (en) | 2007-12-31 | 2014-11-11 | Deka Research & Development Corp. | Apparatus, system and method for fluid delivery |
US9456955B2 (en) | 2007-12-31 | 2016-10-04 | Deka Products Limited Partnership | Apparatus, system and method for fluid delivery |
US10080704B2 (en) | 2007-12-31 | 2018-09-25 | Deka Products Limited Partnership | Apparatus, system and method for fluid delivery |
US8491570B2 (en) | 2007-12-31 | 2013-07-23 | Deka Products Limited Partnership | Infusion pump assembly |
US8900188B2 (en) | 2007-12-31 | 2014-12-02 | Deka Products Limited Partnership | Split ring resonator antenna adapted for use in wirelessly controlled medical device |
MX361885B (en) | 2007-12-31 | 2018-12-18 | Deka Products Lp | Infusion pump assembly. |
US20090177147A1 (en) | 2008-01-07 | 2009-07-09 | Michael Blomquist | Insulin pump with insulin therapy coaching |
US8608484B2 (en) * | 2008-03-04 | 2013-12-17 | Medrad, Inc. | Dynamic anthropomorphic cardiovascular phantom |
KR101586106B1 (en) * | 2008-04-01 | 2016-01-15 | 스미스 메디칼 에이에스디, 인크. | Software features for medical infusion pump |
WO2009129186A2 (en) | 2008-04-17 | 2009-10-22 | Glumetrics, Inc. | Sensor for percutaneous intravascular deployment without an indwelling cannula |
US20120101476A1 (en) * | 2008-05-01 | 2012-04-26 | Curtis Guy P | Transvenous Soaker Catheter Using Microfibers |
US8133197B2 (en) | 2008-05-02 | 2012-03-13 | Smiths Medical Asd, Inc. | Display for pump |
US8315449B2 (en) | 2008-06-24 | 2012-11-20 | Medrad, Inc. | Identification of regions of interest and extraction of time value curves in imaging procedures |
US9514283B2 (en) * | 2008-07-09 | 2016-12-06 | Baxter International Inc. | Dialysis system having inventory management including online dextrose mixing |
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 |
US7920935B2 (en) * | 2008-08-19 | 2011-04-05 | International Business Machines Corporation | Activity based real-time production instruction adaptation |
US7959598B2 (en) | 2008-08-20 | 2011-06-14 | Asante Solutions, Inc. | Infusion pump systems and methods |
CA2725252C (en) * | 2008-08-26 | 2016-12-13 | Mallinckrodt Inc. | Power injector with keep vein open functionality |
CA3132517A1 (en) * | 2008-09-15 | 2010-03-18 | Deka Products Limited Partnership | Systems and methods for fluid delivery |
US9180245B2 (en) | 2008-10-10 | 2015-11-10 | Deka Products Limited Partnership | System and method for administering an infusible fluid |
US8262616B2 (en) | 2008-10-10 | 2012-09-11 | Deka Products Limited Partnership | Infusion pump assembly |
US8708376B2 (en) | 2008-10-10 | 2014-04-29 | Deka Products Limited Partnership | Medium connector |
US8223028B2 (en) | 2008-10-10 | 2012-07-17 | Deka Products Limited Partnership | Occlusion detection system and method |
US8267892B2 (en) | 2008-10-10 | 2012-09-18 | Deka Products Limited Partnership | Multi-language / multi-processor infusion pump assembly |
US8016789B2 (en) | 2008-10-10 | 2011-09-13 | Deka Products Limited Partnership | Pump assembly with a removable cover assembly |
US8066672B2 (en) | 2008-10-10 | 2011-11-29 | Deka Products Limited Partnership | Infusion pump assembly with a backup power supply |
US8554579B2 (en) | 2008-10-13 | 2013-10-08 | Fht, Inc. | Management, reporting and benchmarking of medication preparation |
US8105269B2 (en) | 2008-10-24 | 2012-01-31 | Baxter International Inc. | In situ tubing measurements for infusion pumps |
US9421330B2 (en) | 2008-11-03 | 2016-08-23 | Bayer Healthcare Llc | Mitigation of contrast-induced nephropathy |
US8613719B2 (en) * | 2008-11-03 | 2013-12-24 | Calibra Medical, Inc. | Dosage sensing unit with tactile feedback |
US8208973B2 (en) | 2008-11-05 | 2012-06-26 | Medtronic Minimed, Inc. | System and method for variable beacon timing with wireless devices |
EP2352536B1 (en) | 2008-11-06 | 2018-03-14 | Novo Nordisk A/S | Electronically assisted drug delivery device |
US20100161346A1 (en) * | 2008-12-24 | 2010-06-24 | Kristen Getschmann | Systems and Methods for Providing Bolus Dosage Recommendations |
CN101785885A (en) * | 2009-01-23 | 2010-07-28 | 深圳市深科医疗器械技术开发有限公司 | Method and system for monitoring and managing infusion |
US8103456B2 (en) | 2009-01-29 | 2012-01-24 | Abbott Diabetes Care Inc. | Method and device for early signal attenuation detection using blood glucose measurements |
CN102316917B (en) | 2009-02-13 | 2014-09-10 | 诺沃—诺迪斯克有限公司 | Medical device and cartridge |
US8137083B2 (en) | 2009-03-11 | 2012-03-20 | Baxter International Inc. | Infusion pump actuators, system and method for controlling medical fluid flowrate |
US8271106B2 (en) | 2009-04-17 | 2012-09-18 | Hospira, Inc. | System and method for configuring a rule set for medical event management and responses |
US20100271218A1 (en) * | 2009-04-23 | 2010-10-28 | Carefusion 303, Inc. | Infusion tracking system |
US9226701B2 (en) | 2009-04-28 | 2016-01-05 | Abbott Diabetes Care Inc. | Error detection in critical repeating data in a wireless sensor system |
US8172798B2 (en) * | 2009-05-12 | 2012-05-08 | Sigma International General Medical Apparatus LLC | System and method for managing infusion therapies |
US9283339B2 (en) * | 2009-05-18 | 2016-03-15 | Zoll Medical Corporation | Life support and monitoring apparatus with malfunction correction guidance |
WO2010138856A1 (en) | 2009-05-29 | 2010-12-02 | Abbott Diabetes Care Inc. | Medical device antenna systems having external antenna configurations |
CN104721898B (en) | 2009-07-01 | 2018-05-18 | 弗雷塞尼斯医疗保健控股公司 | Drug delivery device and related system and method |
US20110006880A1 (en) * | 2009-07-09 | 2011-01-13 | Medtronic Minimed, Inc. | Fingerprint-linked control of a portable medical device |
US8344847B2 (en) | 2009-07-09 | 2013-01-01 | Medtronic Minimed, Inc. | Coordination of control commands in a medical device system having at least one therapy delivery device and at least one wireless controller device |
US20110009813A1 (en) * | 2009-07-09 | 2011-01-13 | Medtronic Minimed, Inc. | Panning a display of a portable medical device |
EP2453948B1 (en) | 2009-07-15 | 2015-02-18 | DEKA Products Limited Partnership | Apparatus, systems and methods for an infusion pump assembly |
US8338788B2 (en) | 2009-07-29 | 2012-12-25 | Spectrum Dynamics Llc | Method and system of optimized volumetric imaging |
WO2011024159A2 (en) | 2009-08-24 | 2011-03-03 | Refael Hof | Phase-change and shape-change materials |
WO2011026147A1 (en) | 2009-08-31 | 2011-03-03 | Abbott Diabetes Care Inc. | Analyte signal processing device and methods |
WO2011026148A1 (en) | 2009-08-31 | 2011-03-03 | Abbott Diabetes Care Inc. | Analyte monitoring system and methods for managing power and noise |
US8487758B2 (en) | 2009-09-02 | 2013-07-16 | Medtronic Minimed, Inc. | Medical device having an intelligent alerting scheme, and related operating methods |
US9320461B2 (en) | 2009-09-29 | 2016-04-26 | Abbott Diabetes Care Inc. | Method and apparatus for providing notification function in analyte monitoring systems |
WO2011041546A1 (en) | 2009-09-30 | 2011-04-07 | Glumetrics, Inc. | Sensors with thromboresistant coating |
US8639525B2 (en) * | 2009-10-16 | 2014-01-28 | Codonics, Inc. | Drug labeling |
US8386042B2 (en) | 2009-11-03 | 2013-02-26 | Medtronic Minimed, Inc. | Omnidirectional accelerometer device and medical device incorporating same |
US8467843B2 (en) | 2009-11-04 | 2013-06-18 | Glumetrics, Inc. | Optical sensor configuration for ratiometric correction of blood glucose measurement |
US8945066B2 (en) | 2009-11-06 | 2015-02-03 | Crisi Medical Systems, Inc. | Medication injection site and data collection system |
US8882701B2 (en) | 2009-12-04 | 2014-11-11 | Smiths Medical Asd, Inc. | Advanced step therapy delivery for an ambulatory infusion pump and system |
US8552880B2 (en) * | 2009-12-04 | 2013-10-08 | Smiths Medical Asd, Inc. | Guided user help system for an ambulatory infusion system |
US8771251B2 (en) * | 2009-12-17 | 2014-07-08 | Hospira, Inc. | Systems and methods for managing and delivering patient therapy through electronic drug delivery systems |
US8574201B2 (en) | 2009-12-22 | 2013-11-05 | Medtronic Minimed, Inc. | Syringe piston with check valve seal |
US8755269B2 (en) | 2009-12-23 | 2014-06-17 | Medtronic Minimed, Inc. | Ranking and switching of wireless channels in a body area network of medical devices |
US20110152970A1 (en) * | 2009-12-23 | 2011-06-23 | Medtronic Minimed, Inc. | Location-based ranking and switching of wireless channels in a body area network of medical devices |
US8382447B2 (en) | 2009-12-31 | 2013-02-26 | Baxter International, Inc. | Shuttle pump with controlled geometry |
US11164672B2 (en) | 2010-01-22 | 2021-11-02 | Deka Products Limited Partnership | System and apparatus for electronic patient care |
US10911515B2 (en) | 2012-05-24 | 2021-02-02 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US20110313789A1 (en) | 2010-01-22 | 2011-12-22 | Deka Products Limited Partnership | Electronic patient monitoring system |
US11244745B2 (en) | 2010-01-22 | 2022-02-08 | Deka Products Limited Partnership | Computer-implemented method, system, and apparatus for electronic patient care |
US10453157B2 (en) | 2010-01-22 | 2019-10-22 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US11881307B2 (en) | 2012-05-24 | 2024-01-23 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US11210611B2 (en) * | 2011-12-21 | 2021-12-28 | Deka Products Limited Partnership | System, method, and apparatus for electronic patient care |
US10242159B2 (en) | 2010-01-22 | 2019-03-26 | Deka Products Limited Partnership | System and apparatus for electronic patient care |
CA3033439C (en) | 2010-01-22 | 2021-04-06 | Deka Products Limited Partnership | Method and system for shape-memory alloy wire control |
EP2531099B1 (en) | 2010-02-01 | 2018-12-12 | Proteus Digital Health, Inc. | Data gathering system |
CN102905612A (en) | 2010-02-01 | 2013-01-30 | 普罗秋斯数字健康公司 | Two-wrist data gathering system |
US8894631B2 (en) | 2010-03-24 | 2014-11-25 | Baxter International Inc. | Multiple drug infusion system and method |
US9101534B2 (en) | 2010-04-27 | 2015-08-11 | Crisi Medical Systems, Inc. | Medication and identification information transfer apparatus |
US9930297B2 (en) | 2010-04-30 | 2018-03-27 | Becton, Dickinson And Company | System and method for acquiring images of medication preparations |
US8988237B2 (en) | 2010-05-27 | 2015-03-24 | University Of Southern California | System and method for failure prediction for artificial lift systems |
US8988236B2 (en) | 2010-05-27 | 2015-03-24 | University Of Southern California | System and method for failure prediction for rod pump artificial lift systems |
US9514131B1 (en) | 2010-05-30 | 2016-12-06 | Crisi Medical Systems, Inc. | Medication container encoding, verification, and identification |
US10492991B2 (en) | 2010-05-30 | 2019-12-03 | Crisi Medical Systems, Inc. | Medication container encoding, verification, and identification |
AU2011261296C1 (en) | 2010-06-04 | 2016-08-18 | Bayer Healthcare, Llc. | System and method for planning and monitoring multi-dose radiopharmaceutical usage on radiopharmaceutical injectors |
JP6025718B2 (en) | 2010-06-24 | 2016-11-16 | ベイヤー メディカル ケア インク. | A model for drug propagation and parameter generation for infusion protocols |
US8567235B2 (en) | 2010-06-29 | 2013-10-29 | Baxter International Inc. | Tube measurement technique using linear actuator and pressure sensor |
US8551038B2 (en) * | 2010-07-19 | 2013-10-08 | Micrel Medical Devices S.A. | Pump infusion system |
US8676600B2 (en) | 2010-08-12 | 2014-03-18 | Fenwal, Inc | Mobile applications for blood centers |
US11901069B2 (en) | 2010-08-12 | 2024-02-13 | Fenwal, Inc. | Processing blood donation data for presentation on operator interface |
US8784668B2 (en) | 2010-10-12 | 2014-07-22 | Fresenius Medical Care Holdings, Inc. | Systems and methods for compensation of compliant behavior in regenerative dialysis systems |
US8562565B2 (en) | 2010-10-15 | 2013-10-22 | Medtronic Minimed, Inc. | Battery shock absorber for a portable medical device |
US8603032B2 (en) | 2010-10-15 | 2013-12-10 | Medtronic Minimed, Inc. | Medical device with membrane keypad sealing element, and related manufacturing method |
US8603033B2 (en) | 2010-10-15 | 2013-12-10 | Medtronic Minimed, Inc. | Medical device and related assembly having an offset element for a piezoelectric speaker |
US8479595B2 (en) | 2010-10-20 | 2013-07-09 | Medtronic Minimed, Inc. | Sensor assembly and medical device incorporating same |
US8495918B2 (en) | 2010-10-20 | 2013-07-30 | Medtronic Minimed, Inc. | Sensor assembly and medical device incorporating same |
US8474332B2 (en) | 2010-10-20 | 2013-07-02 | Medtronic Minimed, Inc. | Sensor assembly and medical device incorporating same |
US8469942B2 (en) | 2010-12-22 | 2013-06-25 | Medtronic Minimed, Inc. | Occlusion detection for a fluid infusion device |
US8628510B2 (en) | 2010-12-22 | 2014-01-14 | Medtronic Minimed, Inc. | Monitoring the operating health of a force sensor in a fluid infusion device |
US8197444B1 (en) | 2010-12-22 | 2012-06-12 | Medtronic Minimed, Inc. | Monitoring the seating status of a fluid reservoir in a fluid infusion device |
US8690855B2 (en) | 2010-12-22 | 2014-04-08 | Medtronic Minimed, Inc. | Fluid reservoir seating procedure for a fluid infusion device |
EP2469432A1 (en) | 2010-12-24 | 2012-06-27 | F. Hoffmann-La Roche AG | Ambulatory infusion system with alert prioritizing features |
DE102011008856A1 (en) | 2011-01-18 | 2012-07-19 | Fresenius Medical Care Deutschland Gmbh | Method for carrying out a query of a specification feature of a medical-technical functional device, medical-technical functional device, medical-technical treatment device and control device |
MX356030B (en) | 2011-01-31 | 2018-05-09 | Fresenius Medical Care Holdings Inc | Preventing over-delivery of drug. |
WO2012108984A1 (en) | 2011-02-08 | 2012-08-16 | Fresenius Medical Care Holdings, Inc. | Magnetic sensors and related systems and methods |
CN103370099B (en) | 2011-02-18 | 2016-01-13 | 美敦力公司 | There is the medical treatment device programmable device of adjustable support |
WO2012112178A1 (en) | 2011-02-18 | 2012-08-23 | Medtronic,Inc | Modular medical device programmer |
US8945068B2 (en) | 2011-02-22 | 2015-02-03 | Medtronic Minimed, Inc. | Fluid reservoir having a fluid delivery needle for a fluid infusion device |
US9393399B2 (en) | 2011-02-22 | 2016-07-19 | Medtronic Minimed, Inc. | Sealing assembly for a fluid reservoir of a fluid infusion device |
US9463309B2 (en) | 2011-02-22 | 2016-10-11 | Medtronic Minimed, Inc. | Sealing assembly and structure for a fluid infusion device having a needled fluid reservoir |
US9283318B2 (en) | 2011-02-22 | 2016-03-15 | Medtronic Minimed, Inc. | Flanged sealing element and needle guide pin assembly for a fluid infusion device having a needled fluid reservoir |
US8614596B2 (en) | 2011-02-28 | 2013-12-24 | Medtronic Minimed, Inc. | Systems and methods for initializing a voltage bus and medical devices incorporating same |
US9101305B2 (en) | 2011-03-09 | 2015-08-11 | Medtronic Minimed, Inc. | Glucose sensor product and related manufacturing and packaging methods |
US8564447B2 (en) | 2011-03-18 | 2013-10-22 | Medtronic Minimed, Inc. | Battery life indication techniques for an electronic device |
US9018893B2 (en) | 2011-03-18 | 2015-04-28 | Medtronic Minimed, Inc. | Power control techniques for an electronic device |
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 |
US9280517B2 (en) * | 2011-06-23 | 2016-03-08 | University Of Southern California | System and method for failure detection for artificial lift systems |
JP2014520593A (en) | 2011-07-01 | 2014-08-25 | バクスター・コーポレーション・イングルウッド | System and method for intelligent patient interface device |
EP2745204A4 (en) | 2011-08-19 | 2015-01-07 | Hospira Inc | Systems and methods for a graphical interface including a graphical representation of medical data |
JP2014527881A (en) | 2011-09-21 | 2014-10-23 | ベイヤー メディカル ケア インク. | Continuous multi-fluid pump device, drive and actuation system and method |
US9594875B2 (en) | 2011-10-21 | 2017-03-14 | Hospira, Inc. | Medical device update system |
JP6443802B2 (en) | 2011-11-07 | 2018-12-26 | アボット ダイアベティス ケア インコーポレイテッドAbbott Diabetes Care Inc. | Analyte monitoring apparatus and method |
US8992777B2 (en) | 2011-11-18 | 2015-03-31 | Fresenius Medical Care Holdings, Inc. | Systems and methods for providing notifications in dialysis systems |
US8945043B2 (en) | 2011-12-01 | 2015-02-03 | Zyno Medical, LLC. | Medical device with contextual awareness |
WO2013090709A1 (en) | 2011-12-16 | 2013-06-20 | Hospira, Inc. | System for monitoring and delivering medication to a patient and method of using the same to minimize the risks associated with automated therapy |
US9273544B2 (en) * | 2011-12-29 | 2016-03-01 | Chevron U.S.A. Inc. | System, method, and program for monitoring and hierarchial displaying of data related to artificial lift systems |
US9610401B2 (en) | 2012-01-13 | 2017-04-04 | Medtronic Minimed, Inc. | Infusion set component with modular fluid channel element |
US9211381B2 (en) | 2012-01-20 | 2015-12-15 | Medical Solutions, Inc. | Method and apparatus for controlling temperature of medical liquids |
US9165112B2 (en) | 2012-02-03 | 2015-10-20 | Fresenius Medical Care Holdings, Inc. | Systems and methods for displaying objects at a medical treatment apparatus display screen |
US11524151B2 (en) | 2012-03-07 | 2022-12-13 | Deka Products Limited Partnership | Apparatus, system and method for fluid delivery |
US8603026B2 (en) | 2012-03-20 | 2013-12-10 | Medtronic Minimed, Inc. | Dynamic pulse-width modulation motor control and medical device incorporating same |
US8523803B1 (en) | 2012-03-20 | 2013-09-03 | Medtronic Minimed, Inc. | Motor health monitoring and medical device incorporating same |
US8603027B2 (en) | 2012-03-20 | 2013-12-10 | Medtronic Minimed, Inc. | Occlusion detection using pulse-width modulation and medical device incorporating same |
EP2830687B1 (en) | 2012-03-30 | 2019-07-24 | ICU Medical, Inc. | Air detection system and method for detecting air in a pump of an infusion system |
US9144646B2 (en) | 2012-04-25 | 2015-09-29 | Fresenius Medical Care Holdings, Inc. | Vial spiking devices and related assemblies and methods |
WO2013172811A1 (en) | 2012-05-14 | 2013-11-21 | Medrad, Inc. | Systems and methods for determination of pharmaceutical fluid injection protocols based on x-ray tube voltage |
US9238100B2 (en) | 2012-06-07 | 2016-01-19 | Tandem Diabetes Care, Inc. | Device and method for training users of ambulatory medical devices |
US10391242B2 (en) | 2012-06-07 | 2019-08-27 | Medtronic Minimed, Inc. | Diabetes therapy management system for recommending bolus calculator adjustments |
US9333292B2 (en) | 2012-06-26 | 2016-05-10 | Medtronic Minimed, Inc. | Mechanically actuated fluid infusion device |
EP3586891A1 (en) | 2012-07-31 | 2020-01-01 | ICU Medical, Inc. | Patient care system for critical medications |
US8808269B2 (en) | 2012-08-21 | 2014-08-19 | Medtronic Minimed, Inc. | Reservoir plunger position monitoring and medical device incorporating same |
US9849239B2 (en) | 2012-08-30 | 2017-12-26 | Medtronic Minimed, Inc. | Generation and application of an insulin limit for a closed-loop operating mode of an insulin infusion system |
US9623179B2 (en) | 2012-08-30 | 2017-04-18 | Medtronic Minimed, Inc. | Safeguarding techniques for a closed-loop insulin infusion system |
US10496797B2 (en) | 2012-08-30 | 2019-12-03 | Medtronic Minimed, Inc. | Blood glucose validation for a closed-loop operating mode of an insulin infusion system |
US10130767B2 (en) | 2012-08-30 | 2018-11-20 | Medtronic Minimed, Inc. | Sensor model supervisor for a closed-loop insulin infusion system |
US9662445B2 (en) | 2012-08-30 | 2017-05-30 | Medtronic Minimed, Inc. | Regulating entry into a closed-loop operating mode of an insulin infusion system |
US20140066884A1 (en) | 2012-08-30 | 2014-03-06 | Medtronic Minimed, Inc. | Sensor model supervisor for a closed-loop insulin infusion system |
US9878096B2 (en) | 2012-08-30 | 2018-01-30 | Medtronic Minimed, Inc. | Generation of target glucose values for a closed-loop operating mode of an insulin infusion system |
CA2883273C (en) | 2012-08-31 | 2023-10-24 | Baxter Corporation Englewood | Medication requisition fulfillment system and method |
US9968306B2 (en) | 2012-09-17 | 2018-05-15 | Abbott Diabetes Care Inc. | Methods and apparatuses for providing adverse condition notification with enhanced wireless communication range in analyte monitoring systems |
US9174003B2 (en) | 2012-09-28 | 2015-11-03 | Bayer Medical Care Inc. | Quick release plunger |
KR101695119B1 (en) | 2012-10-26 | 2017-01-23 | 백스터 코포레이션 잉글우드 | Improved image acquisition for medical dose preparation system |
NZ716476A (en) | 2012-10-26 | 2018-10-26 | Baxter Corp Englewood | Improved work station for medical dose preparation system |
US8870818B2 (en) | 2012-11-15 | 2014-10-28 | Medtronic Minimed, Inc. | Systems and methods for alignment and detection of a consumable component |
US9033924B2 (en) | 2013-01-18 | 2015-05-19 | Medtronic Minimed, Inc. | Systems for fluid reservoir retention |
US9522223B2 (en) | 2013-01-18 | 2016-12-20 | Medtronic Minimed, Inc. | Systems for fluid reservoir retention |
US9107994B2 (en) | 2013-01-18 | 2015-08-18 | Medtronic Minimed, Inc. | Systems for fluid reservoir retention |
KR102328988B1 (en) * | 2013-01-23 | 2021-11-22 | 백스터 코포레이션 잉글우드 | Patient care device-specific configuration output |
CA2896100C (en) | 2013-01-28 | 2021-04-27 | Smiths Medical Asd, Inc. | Medication safety devices and methods |
US11182728B2 (en) | 2013-01-30 | 2021-11-23 | Carefusion 303, Inc. | Medication workflow management |
US10430554B2 (en) | 2013-05-23 | 2019-10-01 | Carefusion 303, Inc. | Medication preparation queue |
US9656029B2 (en) | 2013-02-15 | 2017-05-23 | Medical Solutions, Inc. | Plural medical item warming system and method for warming a plurality of medical items to desired temperatures |
US9308321B2 (en) | 2013-02-18 | 2016-04-12 | Medtronic Minimed, Inc. | Infusion device having gear assembly initialization |
US9641432B2 (en) | 2013-03-06 | 2017-05-02 | Icu Medical, Inc. | Medical device communication method |
EP2973366B1 (en) | 2013-03-13 | 2020-08-19 | Carefusion 303 Inc. | Patient-specific medication management system |
US20140276560A1 (en) * | 2013-03-13 | 2014-09-18 | Carefusion 303, Inc. | Infusion Management Platform For Medication Container Volume Tracking |
US10143830B2 (en) | 2013-03-13 | 2018-12-04 | Crisi Medical Systems, Inc. | Injection site information cap |
CN105074766A (en) | 2013-03-13 | 2015-11-18 | 康尔福盛303公司 | Predictive medication safety |
US9390235B2 (en) | 2013-03-13 | 2016-07-12 | Carefusion 303, Inc. | Infusion management platform with infusion data grouping logic |
US10357606B2 (en) | 2013-03-13 | 2019-07-23 | Tandem Diabetes Care, Inc. | System and method for integration of insulin pumps and continuous glucose monitoring |
US9555379B2 (en) | 2013-03-13 | 2017-01-31 | Bayer Healthcare Llc | Fluid path set with turbulent mixing chamber, backflow compensator |
US10016561B2 (en) | 2013-03-15 | 2018-07-10 | Tandem Diabetes Care, Inc. | Clinical variable determination |
US9603995B2 (en) * | 2013-03-15 | 2017-03-28 | Tandem Diabetes Care. Inc. | Device and method for setting therapeutic parameters for an infusion device |
US8920381B2 (en) | 2013-04-12 | 2014-12-30 | Medtronic Minimed, Inc. | Infusion set with improved bore configuration |
EP2799098A1 (en) * | 2013-04-29 | 2014-11-05 | F.Hoffmann-La Roche Ag | Ambulatory infusion system including wireless earphone device |
CA2913421C (en) | 2013-05-24 | 2022-02-15 | Hospira, Inc. | Multi-sensor infusion system for detecting air or an occlusion in the infusion system |
EP3003442B1 (en) | 2013-05-29 | 2020-12-30 | ICU Medical, Inc. | Infusion system and method of use which prevents over-saturation of an analog-to-digital converter |
CA2913915C (en) | 2013-05-29 | 2022-03-29 | Hospira, Inc. | Infusion system which utilizes one or more sensors and additional information to make an air determination regarding the infusion system |
EP3016629B1 (en) | 2013-07-03 | 2023-12-20 | DEKA Products Limited Partnership | Apparatus and system for fluid delivery |
US9433731B2 (en) | 2013-07-19 | 2016-09-06 | Medtronic Minimed, Inc. | Detecting unintentional motor motion and infusion device incorporating same |
US9402949B2 (en) | 2013-08-13 | 2016-08-02 | Medtronic Minimed, Inc. | Detecting conditions associated with medical device operations using matched filters |
US9889257B2 (en) | 2013-08-21 | 2018-02-13 | Medtronic Minimed, Inc. | Systems and methods for updating medical devices |
US9880528B2 (en) | 2013-08-21 | 2018-01-30 | Medtronic Minimed, Inc. | Medical devices and related updating methods and systems |
US9259528B2 (en) | 2013-08-22 | 2016-02-16 | Medtronic Minimed, Inc. | Fluid infusion device with safety coupling |
AU2014312122A1 (en) | 2013-08-30 | 2016-04-07 | Icu Medical, Inc. | System and method of monitoring and managing a remote infusion regimen |
US9662436B2 (en) | 2013-09-20 | 2017-05-30 | Icu Medical, Inc. | Fail-safe drug infusion therapy system |
US10311972B2 (en) | 2013-11-11 | 2019-06-04 | Icu Medical, Inc. | Medical device system performance index |
US20150133861A1 (en) | 2013-11-11 | 2015-05-14 | Kevin P. McLennan | Thermal management system and method for medical devices |
US10042986B2 (en) | 2013-11-19 | 2018-08-07 | Icu Medical, Inc. | Infusion pump automation system and method |
US9750878B2 (en) | 2013-12-11 | 2017-09-05 | Medtronic Minimed, Inc. | Closed-loop control of glucose according to a predicted blood glucose trajectory |
US9750877B2 (en) | 2013-12-11 | 2017-09-05 | Medtronic Minimed, Inc. | Predicted time to assess and/or control a glycemic state |
US10105488B2 (en) | 2013-12-12 | 2018-10-23 | Medtronic Minimed, Inc. | Predictive infusion device operations and related methods and systems |
US9849240B2 (en) | 2013-12-12 | 2017-12-26 | Medtronic Minimed, Inc. | Data modification for predictive operations and devices incorporating same |
US9694132B2 (en) | 2013-12-19 | 2017-07-04 | Medtronic Minimed, Inc. | Insertion device for insertion set |
EP4250313A3 (en) | 2013-12-26 | 2023-11-22 | Tandem Diabetes Care, Inc. | Integration of infusion pump with remote electronic device |
GB2523989B (en) | 2014-01-30 | 2020-07-29 | Insulet Netherlands B V | Therapeutic product delivery system and method of pairing |
US9399096B2 (en) | 2014-02-06 | 2016-07-26 | Medtronic Minimed, Inc. | Automatic closed-loop control adjustments and infusion systems incorporating same |
US9861748B2 (en) | 2014-02-06 | 2018-01-09 | Medtronic Minimed, Inc. | User-configurable closed-loop notifications and infusion systems incorporating same |
CN105960642B (en) * | 2014-02-21 | 2020-06-26 | 阿克西姆医疗技术有限公司 | Infusion pump with graphic user interface |
WO2015130674A1 (en) * | 2014-02-27 | 2015-09-03 | Draeger Medical Systems, Inc. | Medical device alarm management |
ES2776363T3 (en) | 2014-02-28 | 2020-07-30 | Icu Medical Inc | Infusion set and method using dual wavelength in-line optical air detection |
AU2015231396B2 (en) | 2014-03-19 | 2018-12-06 | Bayer Healthcare Llc | System for syringe engagement to an injector |
US10034976B2 (en) | 2014-03-24 | 2018-07-31 | Medtronic Minimed, Inc. | Fluid infusion patch pump device with automatic fluid system priming feature |
US10001450B2 (en) | 2014-04-18 | 2018-06-19 | Medtronic Minimed, Inc. | Nonlinear mapping technique for a physiological characteristic sensor |
US10232113B2 (en) | 2014-04-24 | 2019-03-19 | Medtronic Minimed, Inc. | Infusion devices and related methods and systems for regulating insulin on board |
WO2015168427A1 (en) | 2014-04-30 | 2015-11-05 | Hospira, Inc. | Patient care system with conditional alarm forwarding |
US9681828B2 (en) | 2014-05-01 | 2017-06-20 | Medtronic Minimed, Inc. | Physiological characteristic sensors and methods for forming such sensors |
US10275572B2 (en) | 2014-05-01 | 2019-04-30 | Medtronic Minimed, Inc. | Detecting blockage of a reservoir cavity during a seating operation of a fluid infusion device |
JP5822317B1 (en) | 2014-05-12 | 2015-11-24 | 日機装株式会社 | Blood purification equipment |
US10274349B2 (en) | 2014-05-19 | 2019-04-30 | Medtronic Minimed, Inc. | Calibration factor adjustments for infusion devices and related methods and systems |
US10152049B2 (en) | 2014-05-19 | 2018-12-11 | Medtronic Minimed, Inc. | Glucose sensor health monitoring and related methods and systems |
US10007765B2 (en) | 2014-05-19 | 2018-06-26 | Medtronic Minimed, Inc. | Adaptive signal processing for infusion devices and related methods and systems |
CN106659845A (en) | 2014-05-20 | 2017-05-10 | 瑟丘尔股份有限公司 | Medicine delivery device with restricted access filling port |
WO2015184366A1 (en) | 2014-05-29 | 2015-12-03 | Hospira, Inc. | Infusion system and pump with configurable closed loop delivery rate catch-up |
US9724470B2 (en) | 2014-06-16 | 2017-08-08 | Icu Medical, Inc. | System for monitoring and delivering medication to a patient and method of using the same to minimize the risks associated with automated therapy |
JP2017525032A (en) | 2014-06-30 | 2017-08-31 | バクスター・コーポレーション・イングルウッドBaxter Corporation Englewood | Managed medical information exchange |
US9669160B2 (en) | 2014-07-30 | 2017-06-06 | Tandem Diabetes Care, Inc. | Temporary suspension for closed-loop medicament therapy |
US10143795B2 (en) | 2014-08-18 | 2018-12-04 | Icu Medical, Inc. | Intravenous pole integrated power, control, and communication system and method for an infusion pump |
US20160058940A1 (en) | 2014-08-28 | 2016-03-03 | Zyno Medical, LLC. | Low-cost ambulatory medical pump |
US10679342B2 (en) | 2014-09-08 | 2020-06-09 | Becton, Dickinson And Company | Aerodynamically streamlined enclosure for input devices of a medication preparation system |
US9539383B2 (en) | 2014-09-15 | 2017-01-10 | Hospira, Inc. | System and method that matches delayed infusion auto-programs with manually entered infusion programs and analyzes differences therein |
US9833563B2 (en) | 2014-09-26 | 2017-12-05 | Medtronic Minimed, Inc. | Systems for managing reservoir chamber pressure |
US9839753B2 (en) | 2014-09-26 | 2017-12-12 | Medtronic Minimed, Inc. | Systems for managing reservoir chamber pressure |
US11107574B2 (en) | 2014-09-30 | 2021-08-31 | Baxter Corporation Englewood | Management of medication preparation with formulary management |
US11575673B2 (en) | 2014-09-30 | 2023-02-07 | Baxter Corporation Englewood | Central user management in a distributed healthcare information management system |
US10279126B2 (en) | 2014-10-07 | 2019-05-07 | Medtronic Minimed, Inc. | Fluid conduit assembly with gas trapping filter in the fluid flow path |
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 |
US9833564B2 (en) | 2014-11-25 | 2017-12-05 | Medtronic Minimed, Inc. | Fluid conduit assembly with air venting features |
CN107206082B (en) | 2014-11-25 | 2022-01-11 | 纽菲斯有限公司 | Phase-change nanoparticles |
US10195341B2 (en) | 2014-11-26 | 2019-02-05 | Medtronic Minimed, Inc. | Systems and methods for fluid infusion device with automatic reservoir fill |
US9987420B2 (en) | 2014-11-26 | 2018-06-05 | Medtronic Minimed, Inc. | Systems and methods for fluid infusion device with automatic reservoir fill |
US9636453B2 (en) | 2014-12-04 | 2017-05-02 | Medtronic Minimed, Inc. | Advance diagnosis of infusion device operating mode viability |
US9943645B2 (en) | 2014-12-04 | 2018-04-17 | Medtronic Minimed, Inc. | Methods for operating mode transitions and related infusion devices and systems |
EP3937116A1 (en) | 2014-12-05 | 2022-01-12 | Baxter Corporation Englewood | Dose preparation data analytics |
US9937292B2 (en) | 2014-12-09 | 2018-04-10 | Medtronic Minimed, Inc. | Systems for filling a fluid infusion device reservoir |
US11344668B2 (en) | 2014-12-19 | 2022-05-31 | Icu Medical, Inc. | Infusion system with concurrent TPN/insulin infusion |
US10307535B2 (en) | 2014-12-19 | 2019-06-04 | Medtronic Minimed, Inc. | Infusion devices and related methods and systems for preemptive alerting |
US10265031B2 (en) | 2014-12-19 | 2019-04-23 | Medtronic Minimed, Inc. | Infusion devices and related methods and systems for automatic alert clearing |
CA2973257C (en) | 2015-01-09 | 2023-09-19 | Bayer Healthcare Llc | Multiple fluid delivery system with multi-use disposable set and features thereof |
CN111905188B (en) | 2015-02-18 | 2022-07-22 | 英赛罗公司 | Fluid delivery and infusion device and method of use |
US10850024B2 (en) | 2015-03-02 | 2020-12-01 | Icu Medical, Inc. | Infusion system, device, and method having advanced infusion features |
JP2018507487A (en) | 2015-03-03 | 2018-03-15 | バクスター・コーポレーション・イングルウッドBaxter Corporation Englewood | Pharmacy workflow management with alert integration |
US10307528B2 (en) | 2015-03-09 | 2019-06-04 | Medtronic Minimed, Inc. | Extensible infusion devices and related methods |
US10449298B2 (en) | 2015-03-26 | 2019-10-22 | Medtronic Minimed, Inc. | Fluid injection devices and related methods |
WO2016189419A1 (en) | 2015-05-26 | 2016-12-01 | Hospira, Nc. | Disposable infusion fluid delivery device for programmable large volume drug delivery |
US10137243B2 (en) | 2015-05-26 | 2018-11-27 | Medtronic Minimed, Inc. | Infusion devices with distributed motor control and related operating methods |
US9999721B2 (en) | 2015-05-26 | 2018-06-19 | Medtronic Minimed, Inc. | Error handling in infusion devices with distributed motor control and related operating methods |
EP3304370B1 (en) | 2015-05-26 | 2020-12-30 | ICU Medical, Inc. | Infusion pump system and method with multiple drug library editor source capability |
US10575767B2 (en) | 2015-05-29 | 2020-03-03 | Medtronic Minimed, Inc. | Method for monitoring an analyte, analyte sensor and analyte monitoring apparatus |
US9993594B2 (en) | 2015-06-22 | 2018-06-12 | Medtronic Minimed, Inc. | Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and rotor position sensors |
US9878095B2 (en) | 2015-06-22 | 2018-01-30 | Medtronic Minimed, Inc. | Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and multiple sensor contact elements |
US9987425B2 (en) | 2015-06-22 | 2018-06-05 | Medtronic Minimed, Inc. | Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and sensor contact elements |
US10010668B2 (en) | 2015-06-22 | 2018-07-03 | Medtronic Minimed, Inc. | Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and a force sensor |
US9879668B2 (en) | 2015-06-22 | 2018-01-30 | Medtronic Minimed, Inc. | Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and an optical sensor |
CN116206744A (en) | 2015-06-25 | 2023-06-02 | 甘布罗伦迪亚股份公司 | Medical device systems and methods with distributed databases |
EP3313475A1 (en) | 2015-06-26 | 2018-05-02 | Seiratherm GmbH | Medical device and method for tempering infusion fluids in a rack-like structure |
US10478557B2 (en) | 2015-08-21 | 2019-11-19 | Medtronic Minimed, Inc. | Personalized parameter modeling methods and related devices and systems |
US20170053084A1 (en) | 2015-08-21 | 2017-02-23 | Medtronic Minimed, Inc. | Data analytics and reporting of glucose-related information |
US10201657B2 (en) | 2015-08-21 | 2019-02-12 | Medtronic Minimed, Inc. | Methods for providing sensor site rotation feedback and related infusion devices and systems |
US10293108B2 (en) | 2015-08-21 | 2019-05-21 | Medtronic Minimed, Inc. | Infusion devices and related patient ratio adjustment methods |
US10463297B2 (en) | 2015-08-21 | 2019-11-05 | Medtronic Minimed, Inc. | Personalized event detection methods and related devices and systems |
US10117992B2 (en) | 2015-09-29 | 2018-11-06 | Medtronic Minimed, Inc. | Infusion devices and related rescue detection methods |
US11501867B2 (en) | 2015-10-19 | 2022-11-15 | Medtronic Minimed, Inc. | Medical devices and related event pattern presentation methods |
US11666702B2 (en) | 2015-10-19 | 2023-06-06 | Medtronic Minimed, Inc. | Medical devices and related event pattern treatment recommendation methods |
US10146911B2 (en) | 2015-10-23 | 2018-12-04 | Medtronic Minimed, Inc. | Medical devices and related methods and systems for data transfer |
US9480797B1 (en) | 2015-10-28 | 2016-11-01 | Bayer Healthcare Llc | System and method for syringe plunger engagement with an injector |
US10037722B2 (en) | 2015-11-03 | 2018-07-31 | Medtronic Minimed, Inc. | Detecting breakage in a display element |
US10449306B2 (en) | 2015-11-25 | 2019-10-22 | Medtronics Minimed, Inc. | Systems for fluid delivery with wicking membrane |
US10569016B2 (en) | 2015-12-29 | 2020-02-25 | Tandem Diabetes Care, Inc. | System and method for switching between closed loop and open loop control of an ambulatory infusion pump |
EP3374905A1 (en) | 2016-01-13 | 2018-09-19 | Bigfoot Biomedical, Inc. | User interface for diabetes management system |
CN112933333B (en) | 2016-01-14 | 2023-03-28 | 比格福特生物医药公司 | Adjusting insulin delivery rate |
US10898638B2 (en) | 2016-03-03 | 2021-01-26 | Bayer Healthcare Llc | System and method for improved fluid delivery in multi-fluid injector systems |
CA3019549A1 (en) * | 2016-04-08 | 2017-10-12 | Icu Medical, Inc. | Control of a drug infusion device |
US10589038B2 (en) | 2016-04-27 | 2020-03-17 | Medtronic Minimed, Inc. | Set connector systems for venting a fluid reservoir |
AU2017264784B2 (en) | 2016-05-13 | 2022-04-21 | Icu Medical, Inc. | Infusion pump system and method with common line auto flush |
WO2017214441A1 (en) | 2016-06-10 | 2017-12-14 | Icu Medical, Inc. | Acoustic flow sensor for continuous medication flow measurements and feedback control of infusion |
WO2018013842A1 (en) | 2016-07-14 | 2018-01-18 | Icu Medical, Inc. | Multi-communication path selection and security system for a medical device |
WO2018058041A1 (en) * | 2016-09-23 | 2018-03-29 | Insulet Corporation | Fluid delivery device with sensor |
US11097051B2 (en) | 2016-11-04 | 2021-08-24 | Medtronic Minimed, Inc. | Methods and apparatus for detecting and reacting to insufficient hypoglycemia response |
US10238030B2 (en) | 2016-12-06 | 2019-03-26 | Medtronic Minimed, Inc. | Wireless medical device with a complementary split ring resonator arrangement for suppression of electromagnetic interference |
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 |
US10272201B2 (en) | 2016-12-22 | 2019-04-30 | Medtronic Minimed, Inc. | Insertion site monitoring methods and related infusion devices and systems |
US10500135B2 (en) | 2017-01-30 | 2019-12-10 | Medtronic Minimed, Inc. | Fluid reservoir and systems for filling a fluid reservoir of a fluid infusion device |
US10532165B2 (en) | 2017-01-30 | 2020-01-14 | Medtronic Minimed, Inc. | Fluid reservoir and systems for filling a fluid reservoir of a fluid infusion device |
US10363365B2 (en) | 2017-02-07 | 2019-07-30 | Medtronic Minimed, Inc. | Infusion devices and related consumable calibration methods |
US10552580B2 (en) | 2017-02-07 | 2020-02-04 | Medtronic Minimed, Inc. | Infusion system consumables and related calibration methods |
US11207463B2 (en) | 2017-02-21 | 2021-12-28 | Medtronic Minimed, Inc. | Apparatuses, systems, and methods for identifying an infusate in a reservoir of an infusion device |
US10646649B2 (en) | 2017-02-21 | 2020-05-12 | Medtronic Minimed, Inc. | Infusion devices and fluid identification apparatuses and methods |
CA3067625A1 (en) | 2017-08-31 | 2019-03-07 | Bayer Healthcare Llc | Injector pressure calibration system and method |
US11141535B2 (en) | 2017-08-31 | 2021-10-12 | Bayer Healthcare Llc | Fluid path impedance assessment for improving fluid delivery performance |
CA3068544A1 (en) | 2017-08-31 | 2019-03-07 | Bayer Healthcare Llc | Method for dynamic pressure control in a fluid injector system |
AU2018326380B2 (en) | 2017-08-31 | 2024-02-29 | Bayer Healthcare Llc | System and method for drive member position and fluid injector system mechanical calibration |
CN110809482B (en) | 2017-08-31 | 2023-03-07 | 拜耳医药保健有限公司 | Fluid injector system volume compensation system and method |
US10089055B1 (en) | 2017-12-27 | 2018-10-02 | Icu Medical, Inc. | Synchronized display of screen content on networked devices |
HUE061426T2 (en) | 2018-02-27 | 2023-06-28 | Bayer Healthcare Llc | Syringe plunger engagement mechanism |
USD928199S1 (en) | 2018-04-02 | 2021-08-17 | Bigfoot Biomedical, Inc. | Medication delivery device with icons |
WO2019209963A1 (en) | 2018-04-24 | 2019-10-31 | Deka Products Limited Partnership | Apparatus and system for fluid delivery |
CA3099113A1 (en) | 2018-05-04 | 2019-11-07 | Insulet Corporation | Safety constraints for a control algorithm-based drug delivery system |
US20210308375A1 (en) * | 2018-05-25 | 2021-10-07 | Smiths Medical Asd, Inc. | Systems and methods for improving operation of infusion pumps |
EP3824383B1 (en) | 2018-07-17 | 2023-10-11 | ICU Medical, Inc. | Systems and methods for facilitating clinical messaging in a network environment |
AU2019306490A1 (en) | 2018-07-17 | 2021-02-04 | Icu Medical, Inc. | Updating infusion pump drug libraries and operational software in a networked environment |
US11139058B2 (en) | 2018-07-17 | 2021-10-05 | Icu Medical, Inc. | Reducing file transfer between cloud environment and infusion pumps |
US10741280B2 (en) | 2018-07-17 | 2020-08-11 | Icu Medical, Inc. | Tagging pump messages with identifiers that facilitate restructuring |
US10692595B2 (en) | 2018-07-26 | 2020-06-23 | Icu Medical, Inc. | Drug library dynamic version management |
AU2019309766A1 (en) | 2018-07-26 | 2021-03-18 | Icu Medical, Inc. | Drug library management system |
CN112789070A (en) | 2018-09-28 | 2021-05-11 | 英赛罗公司 | Mode of activity of the artificial pancreas System |
US11565039B2 (en) | 2018-10-11 | 2023-01-31 | Insulet Corporation | Event detection for drug delivery system |
EP3653239A1 (en) * | 2018-11-13 | 2020-05-20 | Epic Medical Pte Ltd | Infusion pump control method, infusion pump and tube cassette for fluid delivery |
USD939079S1 (en) | 2019-08-22 | 2021-12-21 | Icu Medical, Inc. | Infusion pump |
US11801344B2 (en) | 2019-09-13 | 2023-10-31 | Insulet Corporation | Blood glucose rate of change modulation of meal and correction insulin bolus quantity |
US11935637B2 (en) | 2019-09-27 | 2024-03-19 | Insulet Corporation | Onboarding and total daily insulin adaptivity |
US11278671B2 (en) | 2019-12-04 | 2022-03-22 | Icu Medical, Inc. | Infusion pump with safety sequence keypad |
US11833329B2 (en) | 2019-12-20 | 2023-12-05 | Insulet Corporation | Techniques for improved automatic drug delivery performance using delivery tendencies from past delivery history and use patterns |
US11551802B2 (en) | 2020-02-11 | 2023-01-10 | Insulet Corporation | Early meal detection and calorie intake detection |
US11547800B2 (en) | 2020-02-12 | 2023-01-10 | Insulet Corporation | User parameter dependent cost function for personalized reduction of hypoglycemia and/or hyperglycemia in a closed loop artificial pancreas system |
US11324889B2 (en) | 2020-02-14 | 2022-05-10 | Insulet Corporation | Compensation for missing readings from a glucose monitor in an automated insulin delivery system |
US11607493B2 (en) | 2020-04-06 | 2023-03-21 | Insulet Corporation | Initial total daily insulin setting for user onboarding |
WO2022020184A1 (en) | 2020-07-21 | 2022-01-27 | Icu Medical, Inc. | Fluid transfer devices and methods of use |
US11684716B2 (en) | 2020-07-31 | 2023-06-27 | Insulet Corporation | Techniques to reduce risk of occlusions in drug delivery systems |
CN111905192B (en) * | 2020-09-18 | 2023-01-31 | 上海市金山区亭林医院(中国福利会国际和平妇幼保健院金山分院) | Sickbed, nurse station and alarm method of sickbed nurses |
US11135360B1 (en) | 2020-12-07 | 2021-10-05 | Icu Medical, Inc. | Concurrent infusion with common line auto flush |
US11904140B2 (en) | 2021-03-10 | 2024-02-20 | Insulet Corporation | Adaptable asymmetric medicament cost component in a control system for medicament delivery |
US11738144B2 (en) | 2021-09-27 | 2023-08-29 | Insulet Corporation | Techniques enabling adaptation of parameters in aid systems by user input |
US11439754B1 (en) | 2021-12-01 | 2022-09-13 | Insulet Corporation | Optimizing embedded formulations for drug delivery |
Family Cites Families (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4370983A (en) * | 1971-01-20 | 1983-02-01 | Lichtenstein Eric Stefan | Computer-control medical care system |
US4032908A (en) * | 1975-07-02 | 1977-06-28 | Automated Systems, Inc. | Security alarm system |
US4126132A (en) * | 1975-07-28 | 1978-11-21 | Andros Incorporated | Intravenous and intra arterial delivery system |
US4619653A (en) * | 1979-04-27 | 1986-10-28 | The Johns Hopkins University | Apparatus for detecting at least one predetermined condition and providing an informational signal in response thereto in a medication infusion system |
US4373527B1 (en) * | 1979-04-27 | 1995-06-27 | Univ Johns Hopkins | Implantable programmable medication infusion system |
US4731051A (en) * | 1979-04-27 | 1988-03-15 | The Johns Hopkins University | Programmable control means for providing safe and controlled medication infusion |
US4573994A (en) * | 1979-04-27 | 1986-03-04 | The Johns Hopkins University | Refillable medication infusion apparatus |
US4784645A (en) * | 1982-11-04 | 1988-11-15 | The Johns Hopkins University | Apparatus for detecting a condition of a medication infusion system and providing an informational signal in response thereto |
US4538138A (en) * | 1982-12-17 | 1985-08-27 | American District Telegraph Company | Integrated security system having a multiprogrammed controller |
US4553958A (en) * | 1983-02-04 | 1985-11-19 | Quest Medical, Inc. | IV Delivery controller |
US4526404A (en) * | 1983-04-29 | 1985-07-02 | Vazquez Richard M | Container for clinical product |
US4811844A (en) * | 1983-09-14 | 1989-03-14 | Moulding Jr Thomas S | Dual layered card for permitting selective access to an object |
US5108367A (en) * | 1984-02-08 | 1992-04-28 | Abbott Laboratories | Pressure responsive multiple input infusion system |
US4865584A (en) * | 1984-02-08 | 1989-09-12 | Omni-Flow, Inc. | Cassette for programable multiple input infusion system |
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 |
US5100380A (en) * | 1984-02-08 | 1992-03-31 | Abbott Laboratories | Remotely programmable infusion system |
WO1985004039A1 (en) * | 1984-03-05 | 1985-09-12 | Progrator Innovation Ab | Monitor for an alarm system |
CA1254091A (en) * | 1984-09-28 | 1989-05-16 | Vladimir Feingold | Implantable medication infusion system |
US4705506A (en) * | 1984-11-29 | 1987-11-10 | Minnesota Mining And Manufacturing Company | Multiple solution IV system with setup error protection |
US5088981A (en) * | 1985-01-18 | 1992-02-18 | Howson David C | Safety enhanced device and method for effecting application of a therapeutic agent |
US4810243A (en) * | 1985-01-18 | 1989-03-07 | Intelligent Medicine, Inc. | Device and method for effecting application of a therapeutic agent |
US4756706A (en) * | 1985-01-23 | 1988-07-12 | American Hospital Supply Corporation | Centrally managed modular infusion pump system |
US4835372A (en) * | 1985-07-19 | 1989-05-30 | Clincom Incorporated | Patient care system |
FR2593951B1 (en) * | 1986-02-03 | 1989-01-06 | Bertin & Cie | METHOD AND SYSTEM FOR REMOTE CONTROL OF AT LEAST ONE INFUSION STATION |
US4857713A (en) * | 1986-02-14 | 1989-08-15 | Brown Jack D | Hospital error avoidance system |
US4816208A (en) * | 1986-02-14 | 1989-03-28 | Westinghouse Electric Corp. | Alarm management system |
US4857716A (en) * | 1986-05-12 | 1989-08-15 | Clinicom Incorporated | Patient identification and verification system and method |
JPH0655479B2 (en) * | 1986-07-28 | 1994-07-27 | 住友化学工業株式会社 | Photoselectively transparent film or sheet |
US4839806A (en) * | 1986-09-30 | 1989-06-13 | Goldfischer Jerome D | Computerized dispensing of medication |
US4730849A (en) * | 1987-02-05 | 1988-03-15 | Seigel Family Revocable Trust | Medication dispensing identifier method |
US4732411A (en) * | 1987-02-05 | 1988-03-22 | Siegel Family Revocable Trust | Medication dispensing identifier system |
EP0290683A3 (en) * | 1987-05-01 | 1988-12-14 | Diva Medical Systems B.V. | Diabetes management system and apparatus |
US4847764C1 (en) * | 1987-05-21 | 2001-09-11 | Meditrol Inc | System for dispensing drugs in health care instituions |
US4817044A (en) * | 1987-06-01 | 1989-03-28 | Ogren David A | Collection and reporting system for medical appliances |
US4925444A (en) * | 1987-08-07 | 1990-05-15 | Baxter Travenol Laboratories, Inc. | Closed multi-fluid delivery system and method |
US5041086A (en) * | 1987-12-04 | 1991-08-20 | Pacesetter Infusion, Ltd. | Clinical configuration of multimode medication infusion system |
US4919596A (en) * | 1987-12-04 | 1990-04-24 | Pacesetter Infusion, Ltd. | Fluid delivery control and monitoring apparatus for a medication infusion system |
US4853521A (en) * | 1987-12-28 | 1989-08-01 | Claeys Ronald W | System for verifying and recording drug administration to a patient |
US4898578A (en) * | 1988-01-26 | 1990-02-06 | Baxter International Inc. | Drug infusion system with calculator |
US4951029A (en) * | 1988-02-16 | 1990-08-21 | Interactive Technologies, Inc. | Micro-programmable security system |
US5072383A (en) * | 1988-11-19 | 1991-12-10 | Emtek Health Care Systems, Inc. | Medical information system with automatic updating of task list in response to entering orders and charting interventions on associated forms |
-
1989
- 1989-01-30 US US07/304,068 patent/US5153827A/en not_active Expired - Lifetime
-
1990
- 1990-01-26 CA CA002008715A patent/CA2008715A1/en not_active Abandoned
-
1992
- 1992-05-12 US US07/882,692 patent/US5317506A/en not_active Expired - Lifetime
-
1994
- 1994-03-07 US US08/207,574 patent/US5643212A/en not_active Expired - Lifetime
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11524112B2 (en) * | 2009-12-01 | 2022-12-13 | Sanofi-Aventis Deutschland Gmbh | Drug delivery device and method of operation |
CN106139307A (en) * | 2016-08-16 | 2016-11-23 | 肇庆医学高等专科学校 | A kind of vein frame for automatic alarm and APP terminal system |
Also Published As
Publication number | Publication date |
---|---|
US5643212A (en) | 1997-07-01 |
US5317506A (en) | 1994-05-31 |
US5153827A (en) | 1992-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5153827A (en) | An infusion management and pumping system having an alarm handling system | |
US11590281B2 (en) | Management of pending medication orders | |
EP2284742B1 (en) | Patient input monitoring | |
US7471994B2 (en) | Infusion pump with an electronically loadable drug library and label reader | |
EP0302752B1 (en) | Closed multi-fluid delivery system and method | |
US8407068B2 (en) | Medicine management apparatus and medicine management system | |
AU2005282453B2 (en) | Medication data transfer system and method for patient infusions | |
US10387619B2 (en) | Medication order processing and reconciliation | |
CA2224228C (en) | System and method for collecting data and managing patient care | |
WO1999010829A1 (en) | Health care system and method for physician order entry | |
KR20030088032A (en) | System and method for managing patient care | |
CA1327499C (en) | Closed multi-fluid delivery system and method | |
AU2012200125A1 (en) | Management of Pending Medication Orders |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Discontinued |