Patent Description:
Infusion pumps are commonplace among medical devices in modern hospitals. The pumps serve as a useful tool for delivering medication to patients, and are particularly beneficial for their great accuracy in delivering medication at a specific rate and dose. Moreover, medical facilities have enabled hospital caregivers, such as nurses, to deliver medication to patients using auto-programming features available for the infusion pump. Although auto-programming features may reduce errors made manually by hospital caregivers, medical facilities still struggle with identifying and responding to errors made when using an infusion pump. In a conventional auto-programmable pump, error codes and messages may be sent surreptitiously from the pump to other areas of the medical network, but are not immediately accessible to a hospital caregiver submitting an auto-program request at the infusion pump. Furthermore, these error codes often do not specifically describe the error to the caregiver at the pump so that the caregiver may immediately respond to the error.

In addition, known systems do not analyze potential acceptable events if the manual program entered by the caregiver while waiting for an auto-program to arrive at the infusion pump is acceptable. Known systems do not store or analyze the differences between the manual program and the auto-program to determine response times, quality of data entry by the caregiver, and do not learn from caregivers that are at the point of care and thus may purposefully enter a different infusion rate or volume. Thus, there is a need for system and method that matches delayed infusion auto-programs with manually entered infusion programs and analyzes differences therein.

Prior art document <CIT> determines whether there has been an error and stops the use of the infusion program in response to a detected error. Prior art document <CIT> teaches a system that expires an unutilized program and removes the stale program from the queue.

The following presents a simplified summary of the present disclosure in order to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. The following summary merely presents some concepts of the disclosure in a simplified form as a prelude to the more detailed description provided below. The invention is defined in appended claims <NUM> to <NUM>.

Certain examples disclose a method, comprising: receiving, at an infusion pump, an auto-programming request, wherein the auto-programming request comprises IV drug container information, infusion pump information, and optionally patient wristband information; receiving, at the infusion pump, infusion program settings; comparing, at the infusion pump, the infusion program settings with drug library program settings, wherein the drug library program settings are provided in a drug library stored at the infusion pump; determining, at the infusion pump, that the infusion program settings are inconsistent with the drug library program settings based on the comparing; generating, at the infusion pump, an error message based on the determining; and displaying, at the infusion pump, a screen, wherein the screen comprises the error message and a recommended action.

Certain other aspects disclose a non-transitory computer-readable storage medium having computer-executable program instructions stored thereon that, when executed by a processor, cause the processor to: receive an auto-programming request, wherein the auto-programming request comprises patient wristband information, IV drug container information, infusion pump information, and optionally patient wristband information; receive infusion program settings; compare the infusion program settings with drug library program settings, wherein the drug library program settings are provided in a drug library stored at the infusion pump; determine that the infusion program settings are inconsistent with the drug library program settings based on the comparing; generate an error message based on the determining; and display a screen on the infusion pump, wherein the screen comprises the error message and a recommended action; and receive a command in response to the error message and the suggested action.

Certain other aspects disclose an apparatus comprising: a memory; a processor, wherein the processor executes computer-executable program instructions which cause the processor to: receive an auto-programming request, wherein the auto-programming request comprises patient wristband information, IV bag information, infusion pump information, and optionally patient wristband information; receive infusion program settings; compare the infusion program settings with drug library program settings, wherein the drug library program settings are provided in a drug library stored at the infusion pump; determine that the infusion program settings are inconsistent with the drug library program settings based on the comparing; generate an error message based on the determining; and display a screen at the infusion pump, wherein the screen comprises the error message and a recommended action.

One or more embodiments of the invention include a system that identify delayed infusion programs at an infusion pump. At least one embodiment of the invention includes a first computer including a computer network interface and at least one infusion pump. In one or more embodiments, the first computer communicates with the at least one infusion pump via the computer network interface.

By way of one or more embodiments, the first computer receives at least one infusion auto-program from a remote source. In at least one embodiment, the remote source may include hospital information system, pharmacy information system or medication administration system and the first computer may include a medication management unit (MMU), such as a server equipped with Hospira MedNet™ software. In one or more embodiments, the at least one infusion auto-program may include one or more of IV drug container information, infusion pump information, and infusion program settings.

In at least one embodiment, the first computer transmits the at least one infusion auto-program to the at least one infusion pump. In one or more embodiments, the first computer may queue the at least one infusion auto-program when the first computer is unable to transmit the at least one infusion auto-program to the at least one infusion pump. In at least one embodiment, the first computer sends the at least one stale auto-program to the at least one infusion pump when the at least one infusion pump communicates with the first computer.

According to one or more embodiments of the invention, at least one infusion pump may receive at least one manual infusion program from a caregiver. In one or more embodiments, the at least one manual infusion program may include one or more of a completed manual infusion program or a running manual infusion program. In one or more embodiments, the at least one infusion pump saves and executes the at least one manual infusion program received from the caregiver, and compares the at least one stale auto-program to the at least one manual infusion program. In at least one embodiment of the invention, the at least one manual infusion program may be manually selected by a caregiver at the pump from a plurality of protocols that are predefined and provided in a drug library stored in the memory of the at least one infusion pump. In one or more embodiments, the comparison may be based on an approximate time of infusion administration and parameter matching logic including infusion administration parameters and infusion pump operating parameters.

By way of at least one embodiment, the at least one infusion pump compares the infusion pump operating parameters and the infusion administration parameters to identify potential matches between the at least one stale auto-program and the at least one manual infusion program. In one or more embodiments, the at least one infusion pump may evaluate the potential matches using one or more configurable rules and determines if the potential matches are within a predefined tolerance. In at least one embodiment, the at least one infusion pump may continue to execute the at least one manual infusion program on the at least one infusion pump if the potential matches are within the predefined tolerance.

In one or more embodiments, the at least one infusion pump saves differences in the at least one manual infusion program and the at least one stale auto-program locally in a processor of the pump and/or remotely in the remote server. In at least one embodiment, the at least one infusion pump locally and/or remotely saves a first event alert indicating the at least one manual infusion program as an acceptable potential match of the potential matches, and locally and/or remotely saves a second event alert indicating the at least one auto-program as an un-executed program because the at least one manual infusion program is an acceptable potential match.

According to at least one embodiment of the invention, the at least one infusion pump may include an input screen, such that the caregiver may input the at least one manual infusion program via the input screen.

In one or more embodiments, the at least one infusion pump may save identification data of the caregiver locally and/or remotely in the remote server. In at least one embodiment of the invention, the at least one infusion pump compares the at least one manual infusion program from the caregiver to the at least one stale auto-program to determine a scoring of accuracy. In at least one embodiment, the scoring of accuracy may include an acceptability level of the at least one manual infusion program from the caregiver.

By way of one or more embodiments of the invention, the at least one infusion pump may generate at least one report from the comparison of the at least one manual infusion program to the at least one stale auto-program. In at least one embodiment, the report generated by the at least one infusion pump may include one or more of a time differential between completion time of the at least one manual infusion program and completion time of the at least one stale auto-program, a scoring of accuracy including an acceptability level between infusion administration parameters of the at least one manual infusion program and the at least one stale auto-program, and a rating of the caregiver.

In one or more embodiments, the at least one infusion pump may transmit the at least one manual infusion program from the caregiver to the first computer. In at least one embodiment, the first computer may save the at least one manual infusion program from the caregiver and may save identification data of the caregiver. In one or more embodiments, the first computer may compare the at least one manual infusion program from the caregiver to the at least one stale auto-program to determine a scoring of accuracy. In at least one embodiment, the scoring of accuracy may include an acceptability level of the at least one manual infusion program from the caregiver, or analyze and save the program for review if the outcome for the patient results in improved care for example,.

By way of one or more embodiments of the invention, the first computer may generate at least one report from the comparison of the at least one manual infusion program to the at least one stale auto-program. In at least one embodiment, the report generated by the first computer may include one or more of a time differential between completion time of the at least one manual infusion program and completion time of the at least one stale auto-program, a scoring of accuracy including an acceptability level between infusion administration parameters of the at least one manual infusion program and the at least one stale auto-program, and a rating of the caregiver. Data mining may be utilized to determine the manual programs that result in improved outcomes, less drug use, shorter patient stay or any other parameter.

The details of these and other embodiments of the disclosure are set forth in the accompanying drawings and description below. Other features and advantages of aspects of the disclosure will be apparent from the description, drawings, and claims.

The above and other aspects, features and advantages of at least one embodiment of the invention will be more apparent from the following more particular description thereof, presented in conjunction with the following drawings wherein:.

The following description is of the best mode presently contemplated for carrying out at least one embodiment of the invention. This description is not to be taken in a limiting sense, but is made merely for the purpose of describing the general principles of the invention. The scope of the invention should be determined with reference to the claims.

<FIG> illustrates an exemplary schematic diagram of a system for administering medication via an infusion pump. The medication management system (MMS) shown in <FIG> comprises a medication management unit (MMU) <NUM> and a medical device, such as infusion pump <NUM>, typically operating in conjunction with one or more information systems or components of a hospital environment.

Intravenous (IV) fluid(s) and/or medication(s) <NUM> in containers <NUM> may be administered to a patient <NUM> using the system shown in <FIG>. Although the system shown in exemplary <FIG> utilizes barcodes and a barcode reader as apparatus to input and read machine readable information, those skilled in the art will appreciate that other apparatus for reading or inputting information may be utilized. Machine readable indicia or identifying information may be provided by a transmitter, radio frequency identification (RFID) tag, or transponder and read by a radio frequency receiver or transceiver. The system may also utilize digital photography or imaging and scanning technology. Human biometric data, including retina patterns, voice, skin, fingerprints, and the like may also be recognized by an appropriate scanner or receiver. Moreover, POC client <NUM> may comprise an identification receiver <NUM> adapted to recognize such indicia may be provided in the MMS.

In certain aspects, the IV fluids and/or medications <NUM> in container <NUM> may be provided with new or supplemental labels with a unique infusion order identifying barcode by a pharmacist according to certain hospital practices. Specifically, drug container specific identification information, such as barcoded information on the container <NUM> may include patient identification information, including a patient name, patient number, medical record number for which the medication has been prescribed, medication identification information such as a medication name or solution within the IV container <NUM>, universal identification information which may be created or assigned at the hospital, medical device delivery information, such as the operating parameters to use in programming an infusion pump to deliver fluids and/or medication <NUM> to the patient <NUM>, and/or medication order information, such as one or more of above information items and/or other medication order information specific to a particular patient <NUM>, and which may be a part of a medication order for a particular patient. The IV fluids and/or medications <NUM> in barcode-identified containers <NUM> may be supplied to hospitals by various vendors, with preexisting unique barcode identifiers which include medication information and other information, such as a National Disease Center (NDC) code, expiration information, drug interaction information, and the like.

In some aspects of the disclosure, the universal identification information on the container <NUM> may be a unique medication order identifier that, by itself, identifies the order associated with the container. In other aspects, the identification information on the container <NUM> may be a composite patient/order code that contains both a patient ID (such as a medical record number) and an order ID unique only within the context of the patient. In certain aspects, the identification information on the container <NUM> may comprise a medication ID. Within a particular hospital, all medication prepared or packaged for patients by the pharmacy may contain either a composite patient/order ID or a universally unique order ID, but generally not within the same hospital. The medication ID alone option may be used only for medication that are pulled by a nurse directly from floor stock at the point of care.

The system identified in <FIG> may comprise a drug library editor (DLE) or DLE computer <NUM>, such as a notebook, desktop or server computer. The DLE computer <NUM> may comprise DLE software that runs on the DLE terminal, computer or workstation <NUM>, shown as DLE Client in <FIG>. As described above, a medication management unit (MMU) or computer <NUM>, such as a server, may have MMU software that is installed and runs on the MMU server <NUM>. The drug library and other databases may be stored on the MMU server <NUM>, a separate server, and/or in remote locations.

Hospital information systems (HIS) <NUM> may include one or more computers connected by cabling, interfaces and/or Ethernet connections. Alternatively wireless connections and communications may be used in whole or in part. Servers provide processing capability and memory for storage of data and various application programs or modules, including but not limited to a module for admissions-discharge-and-transfer (ADT) <NUM>, a computerized physician order entry (CPOE) module <NUM>, and a pharmacy information system (PIS) module <NUM>. Hospital personnel, such as admission clerks <NUM>, physicians <NUM>, and pharmacists <NUM>, respectively, may be authorized to access these modules through client workstations connected to the servers in order to enter data, access information, run reports, and complete other tasks.

In the embodiment shown in <FIG>, the HIS <NUM> may also include a point of care (POC) system <NUM> including a server or POC computer <NUM> (sometimes referred to as a barcode point of care server or computer), or the POC computer <NUM> may be separate from the HIS <NUM>. The POC computer <NUM> may act as a part of a point of care (POC) system <NUM> (sometimes referred to as the barcode point of care system or BPOC) and may be able to wirelessly communicate through a plurality of wireless communication nodes located throughout the hospital, utilizing a wireless communications protocol, such as IEEE <NUM>, IEEE <NUM>, or Bluetooth. The POC computer <NUM> may communicate wirelessly with a portable thick client POC or input device <NUM> carried by a caregiver. The POC client device <NUM> may be a personal digital assistant (PDA) that comprises significant memory, display and processing capabilities. The POC client device may execute a variety of programs stored in its memory in some degree independently of the POC computer <NUM>.

In one embodiment of <FIG>, the MMU server <NUM> may be hard-wired to the DLE client desktop computer/workstation <NUM> and to a MMU client computer/workstation <NUM>. Alternatively, the MMU and DLE client functions may be combined onto a single client computer/workstation or may reside together with the MMU server <NUM> on a single combined MMU/DLE server. The MMU server <NUM> may reside in a location remote from the patient's room or treatment area. For instance, the MMU server <NUM> may reside in a secure, climate controlled information technology room with other hospital servers and computer equipment and its client terminals may be located in the pharmacy, biomedical engineering area, nurse station, or ward monitoring area. One MMU server <NUM> may monitor, coordinate and communicate with many infusion pumps <NUM>. For example, in one embodiment, the MMU software running on the MMU server <NUM> may support up to one thousand infusion pumps concurrently.

In embodiment of <FIG>, the client PDA <NUM> in the POC computer system <NUM> may communicate through the POC server 3124with the MMU server <NUM>. The MMU server <NUM> may interface or communicate wirelessly with the infusion pump <NUM> through the same wireless nodes <NUM> utilized by the POC system <NUM> and a connectivity engine and antenna on or in the infusion pump <NUM>. Communication between the infusion pump <NUM> and the POC client <NUM> may take place through the MMU server <NUM> and POC server <NUM>. The MMU computer <NUM> may store in an associated memory both the logical ID and the network ID or Internet Protocol (IP) address of the infusion pump(s) <NUM>, such that only the MMU computer <NUM> may communicate in a direct wireless manner with the infusion pump <NUM>. Alternatively the MMU <NUM> may provide the IP address and other information about the pump <NUM> to the POC system <NUM> to facilitate direct communication between the POC system <NUM> and the pump <NUM>.

Upon admission to the hospital, the admission clerk <NUM> or similar personnel may enter demographic information about each patient <NUM> into an associated memory of the ADT computer or module <NUM> of an HIS database stored in an associated memory of the HIS system <NUM>. Each patient <NUM> may be issued a patient identification wristband, bracelet or tag <NUM> (or other patient identification device) that may include an identifier <NUM>, such as a barcode or RFID tag for example, representing a unique set of characters, typically a patient ID or medical record number, identifying the patient, sometimes referred to as patient specific identification information. The wristband, bracelet or tag <NUM> may also include other information, in machine readable or human-readable form, such as the name of the patient's doctor, blood type, allergies, and the like as part of the patient specific identification information.

The patient's doctor <NUM> may prescribe medical treatment by entering an order into the CPOE computer terminal or module <NUM> within the HIS system <NUM>. The order, as prescribed, may specify a start time, stop time, a range of allowable doses, physiological targets, route, and site of administration. In the case of an order for infusion of fluids or medication, the order may be written in various formats, but typically includes the patient's name, patient ID number, a unique medication order or prescription number, a medication name, medication concentration, a dose or dosage, frequency, and a time of desired delivery. This information may be entered into the memory of the CPOE computer <NUM>, and may be stored in a memory associated with at least the POC server or computer <NUM>.

The medication order may also be delivered electronically to the PIS computer <NUM> in the pharmacy and may be stored in an associated memory. The pharmacist <NUM> may screen the prescribed order, translate it into an order for dispensing medication, and prepare the medication or fluids with the proper additives and/or necessary diluents. The pharmacist <NUM> may prepare and affix a label <NUM> with drug container specific identifying information <NUM> to the medication or drug container <NUM>. In one embodiment, the label only includes in machine-readable (barcode, RFID, etc.) form a unique sequentially assigned "dispense ID number" that may be tied to or associated with the particular patient ID number and medication order number in the HIS <NUM>, PIS <NUM> and/or POC computer <NUM>. In another embodiment, the label may include in machine readable form a composite identifier that includes an order ID and a patient ID, which may be a medical record number. In another embodiment, the label does not include a patient ID at all in barcode or machine readable format but includes in machine readable form only a medication ID. Another embodiment may be useful for "floor stock" items that are commonly stocked in operating rooms, emergency rooms, or on a ward for administration on short notice with ad hoc or post hoc orders. In another embodiment, the label may include in machine readable and/or human-readable form medical device specific delivery information including but not limited to the dispense ID number, patient ID, drug name, drug concentration, container volume, volume-to-be-infused ("VTBI"), rate or duration, and the like. Only two of the three variables VTBI, rate and duration may be required to be defined as the third may be calculated when the other two are known. The labeled medication may be delivered to a secure, designated staging location or mobile drug cart on the ward or floor near the patient's room or treatment area. The medication order pending dispensing or administration may be posted to a task list in the HIS system <NUM> and POC system <NUM> and stored in an associated memory.

The caregiver <NUM> (e.g., a nurse) may use the identification receiver <NUM> associated with the POC client <NUM> to scan the caregiver specific identification information <NUM> or barcode on his/her caregiver identification badge <NUM> (or other caregiver identification device) and enter a password, which logs the caregiver into the system and authorizes the caregiver to access a nurse's task list from the POC system <NUM> through the POC client <NUM>. The information within the nurse's badge <NUM> is sometimes referred to as the caregiver specific identification information herein. The caregiver <NUM> may view from the task list that IV drugs are to be administered to certain patients <NUM> in certain rooms. The caregiver <NUM> obtains the necessary supplies, including medications, from the pharmacy and/or a staging area in the vicinity of the patient's room.

The caregiver <NUM> may take the supplies to a patient's bedside, turn on the infusion pump <NUM>, verify that the network connection icon on the pump <NUM> indicates a network connection (for example, a wireless connection such as Wi-Fi or the like) is present, select the appropriate clinical care area (CCA) on the pump, and mount the IV bag, container, or vial <NUM> and any associated tube set as required in position relative to the patient <NUM> and infusion pump <NUM> for infusion. Another connection icon on the pump <NUM> or pump user interface screen can indicate that a wired or wireless connection to the MMU server <NUM> is present. Using the identification receiver/reader integral to the POC client PDA <NUM>, the caregiver <NUM> may scan the barcode on the patient's identification wristband, bracelet or tag <NUM> or other patient identification device. A task list associated with that particular patient may appear on the PDA <NUM> screen. The task list, which may also include orders to give other forms of treatment or medication by other routes (oral, topical, etc.), may be obtained from the HIS via the POC server <NUM> and communicated wirelessly to the POC client PDA <NUM>. In one embodiment, the list is generated by matching the scanned patient ID with the patient ID for orders in memory within the POC server <NUM>. In another embodiment, as will be described below, the order information may be obtained by scanning the drug container specific identification information for associated orders in memory within the POC server <NUM>, through the following step(s).

The caregiver <NUM> may scan the medication barcode label <NUM> containing medication container specific identification information <NUM> on the medication container <NUM> with the PDA <NUM>. The PDA <NUM> may highlight the IV administration task on the task list and send the scanned medication container specific identification information, such as dispense ID information, from the medication container <NUM>, to the POC server <NUM>, which uses the medication container specific identification information, such as the dispense ID, to pull together the rest of the order details and send them back to the PDA <NUM>. The PDA <NUM> may then display an IV Documentation Form on its screen. One side of the IV Documentation Form screen may show the order details as "ordered" and the other side may be reserved for a status report from the infusion pump <NUM>. The status report from the infusion pump <NUM> may be transmitted to the PDA <NUM> through the POC server <NUM> and MMU server <NUM>, as will be described below. The lower portion of the IV Documentation Form screen may provide the caregiver <NUM> with instructions (like to scan the infusion pump <NUM> barcode) or identify whether the pump is running or stopped.

The caregiver <NUM> may then scan the barcode label <NUM> associated with the infusion pump <NUM> (or pump channel if the pump is a multi-channel pump). The barcode label <NUM> may contain medical device specific identification information <NUM>, such as the logical name and/or logical address of the device or channel. The POC system <NUM> then automatically bundles the information into a program pump request containing the "order details" and in one embodiment, without further interaction with the caregiver <NUM>, transmits this information to the MMU server <NUM>.

The program pump request may include at least some of the following information (in HIS/POC system format): a Transaction ID, which may include a Logical Pump ID, a Pump Compartment, a Pump Channel ID, a Reference Device Address, a Caregiver ID, a Caregiver Name, a Patient/Person ID (HIS identifier), a Patient Name, a Patient Birth Date & Time, a Patient Gender, a Patient Weight, a Patient Height, and an Encounter ID which may include a Room, a Bed, and a Building (including Clinical Care Area or CCA). The program pump request may also include Order Information or "order details", including an Order ID, a Start Date/Time, a Stop Date/Time, a Route of Administration, a Rate, a Duration of Infusion (Infuse Over), a Total Volume to be Infused (VTBI), an Ad Hoc Order Indicator, and Ingredients including HIS Drug Name or HIS Generic Drug Name, HIS Drug Identifier or HIS Generic Drug ID, Rx Type (Additive or Base), Strength w/units, and Volume w/units. The program pump request may further include Patient Controlled Analgesia (PCA) Orders Only information, such a PCA Mode-PCA only, Continuous only, or PCA and Continuous, a Lockout Interval (in minutes), a PCA Continuous Rate, a PCA Dose, a Loading Dose, a Dose Limit, a Dose Limit Time w/units, a Total Volume in vial or syringe, and Order Comments.

The MMU <NUM> may map or convert the wide range of expressions of units allowed by the HIS system <NUM> or POC system <NUM> for PDA <NUM> requests into the much more limited set of units allowed in the MMU <NUM> and infusion pump <NUM>. For example, the PDA <NUM> request may express "g, gm, gram, or grams" whereas the MMU <NUM> and/or infusion pump <NUM> may accept "grams" only. Infusion pump <NUM> delivery parameters or infusion pump <NUM> settings are mapped or converted from corresponding order information or "order details" of the program pump request.

The MMU <NUM> may store in an associated memory a mapping or translation table that keep track of the logical ID, serial number or other identifier of an infusion pump <NUM> and the corresponding current network (static or dynamic) address (Internet Protocol (IP) address) or ID of the infusion pump <NUM> on the network, which in this example is a wireless network. The MMU <NUM> may be able to translate or associate a given identifier of the infusion pump <NUM> with its network address in the translation table and provide the network IP address to the requesting POC system <NUM> or device. The MMU <NUM> may also store in an associated memory and/or may look up the drug library applicable to the scanned infusion pump <NUM> and may also convert the Drug ID and Strength from the pump program request into an index number of the medication at the desired strength or concentration from the drug library. The duration of the infusion may come from the POC system <NUM> in hours and minutes and may be converted to just minutes for the infuser to recognize it. Volume or VTBI may be rounded to provide a value-specific and infuser-specific number of digits to the right of the decimal point. Units (of drug) may be converted to million units where appropriate. Patient weight may be converted and either rounded according to infuser-specific rules or not sent to the infuser.

Once the MMU <NUM> transforms the information from the program pump request into infusion pump settings or delivery parameters and other information in a format acceptable to the infusion pump <NUM>, the MMU <NUM> may wirelessly download a command message to the infusion pump <NUM>. If the infusion pump <NUM> is not already equipped with the latest appropriate version of the hospital-established drug library, the MMU <NUM> may also automatically download a drug library to the infusion pump <NUM>. The hospital-established drug library may be maintained in a separate process undertaken by the biomedical engineer or pharmacist <NUM> to place limits on the programming of the infusion pump <NUM>, as well as other infusion pump operating parameters such as default alarm settings for air in the line, occlusion pressure, and the like. The drug library may set up acceptable ranges or hard and/or soft limits for various drug delivery parameters in the infusion pump <NUM>.

The MMU <NUM> may also download to the infusion pump new versions, patches, or software updates of the infusion pump's internal operating system software. The infusion settings or delivery parameters and other information from the MMU <NUM> may be entered into the memory of the infusion pump <NUM> and the infusion pump <NUM> settings may automatically populate the programming screen(s) of the infuser, just as if the caregiver <NUM> had entered the information and settings manually. The infusion pump <NUM> screen may populate with the name of the drug and drug concentration based on the drug library index number, patient weight (if applicable), rate, VTBI, and duration (only two of the last three variable are sent by the MMU <NUM> because the pump <NUM> may calculate the third from the other two). A return message of confirmation signal may be sent to the MMU <NUM> by the infusion pump <NUM> to indicate that the command message has been received. At this point, if necessary, the caregiver <NUM> may manually enter any additional infusion settings or optional information that was not included in the command message.

The infusion pump <NUM> may then prompt the caregiver <NUM> to start the infusion pump <NUM> by pressing the start button. When the caregiver <NUM> presses the start button, a confirmation screen with the infusion settings programmed may be presented for confirmation and an auto-program acknowledgment message can be sent to the MMU server <NUM> to forward without request (i.e., pushed in a near real-time manner) or provide to the POC system <NUM> when requested or polled. When the caregiver <NUM> presses the button to confirm, the infusion pump <NUM> may begin delivering fluid according to the programmed settings. The infusion pump <NUM> may send a status message to the MMU <NUM> indicating that the infusion pump <NUM> was successfully auto-programmed, confirmed and started by the caregiver <NUM>, and is now delivering fluid. This information may also be displayed at the infusion pump. The MMU <NUM> may continue to receive logs and status messages wirelessly from the infusion pump <NUM> periodically as the infusion progresses or when alarms occur.

The MMU <NUM> may report a portion of the initial status message to the PDA <NUM> through the POC server <NUM> (in MMU format) to indicate that the infusion pump <NUM> has been auto-programmed and the caregiver <NUM> has confirmed the settings. The MMU <NUM> may communicate to the POC system <NUM> and/or at the infusion pump <NUM> the actual Rate, VTBI and Duration. A notation at the bottom of the PDA screen and/or the infusion pump may indicate that the infusion pump <NUM> is running. The infusion pump <NUM> may compare and give a visual, audio or other type of affirmative signal if the pump information matches or acceptably corresponds with the ordered information. An initial determination of whether the pump information matches the order may be done in the MMU <NUM> and communicated to the PDA <NUM> through the POC server <NUM>. Alternatively, the POC server <NUM> or the infusion pump <NUM> may make the necessary comparisons. If the pump information does not match the order, the infusion pump <NUM> at the display <NUM> may output a visual, audio or other type of negative signal, which may include an error message.

At least one embodiment of the invention includes a first computer, such as a medication management unit (MMU) <NUM>, including a computer network interface and the at least one infusion pump <NUM>. In one or more embodiments, the first computer communicates with the at least one infusion pump <NUM> via the computer network interface.

By way of one or more embodiments, the first computer receives at least one infusion auto-program from a remote source. In at least one embodiment, the remote source may include a hospital information system, pharmacy information system or medication administration system and the first computer may include the medication management unit (MMU) <NUM>, such as a server equipped with Hospira MedNet™ software. In one or more embodiments, the at least one infusion auto-program may include one or more of IV drug container information, infusion pump information, and infusion program settings.

In at least one embodiment, the first computer transmits the at least one infusion auto-program to the at least one infusion pump <NUM>. In one or more embodiments, the first computer may queue the at least one infusion auto-program when the first computer is unable to transmit the at least one infusion auto-program to the at least one infusion pump <NUM>. In at least one embodiment, the first computer sends the at least one stale auto-program to the at least one infusion pump <NUM> when the at least one infusion pump <NUM> communicates with the first computer.

According to one or more embodiments of the invention, the at least one infusion pump <NUM> may receive at least one manual infusion program from the at least one caregiver <NUM>. In one or more embodiments, the at least one manual infusion program may include one or more of a completed manual infusion program or a running manual infusion program.

The caregiver <NUM> may be prompted to review and press a save button on the infusion pump <NUM> if the order has been begun as desired or any variations are acceptable. The MMU <NUM> may receive status, event, differences and variation information from the infusion pump <NUM> and pass such information to the POC system <NUM>. In a separate subsequent step, the nurse may electronically sign the record and presses a send button on the POC client PDA <NUM> to send the information to the patient's electronic medication record (EMR) or medication administration record (MAR).

Referring now to <FIG> and <FIG>, flowcharts further illustrate a system and method for notifying a caregiver (e.g., caregiver <NUM>, such as a nurse) at an infusion pump <NUM> of the status of administration of fluid and/or medication <NUM> to a patient <NUM> according to aspects of the disclosure. In one embodiment, the POC system <NUM> sends a program pump message containing infusion pump settings to the MMU computer <NUM>, which looks up the targeted infusion pump <NUM> according to its identifier and relays the infusion pump settings to the pump <NUM>. In another embodiment, when the POC system <NUM> is auto-programming the infusion pump <NUM>, the POC system <NUM>, including the POC computer <NUM> and/or the POC client <NUM> may request the MMU <NUM> for permission to program the infusion pump <NUM>. The MMU computer <NUM> may grant this permission and then the POC system <NUM> may communicate directly with the infusion pump <NUM>, without intervention by the MMU computer <NUM>. The MMU computer <NUM> may continually receive asynchronous or synchronous near real-time status messages and event logs from the infusion pump <NUM> and store this information in an associated memory for purposes of at least displaying infusion pump <NUM> status and generating reports.

In certain aspects of the disclosure, prior to beginning the workflow illustrated in <FIG> and <FIG>, a caregiver <NUM> may first be required to use POC system <NUM> to scan an identifier of the caregiver's ID badge <NUM>. The POC system <NUM> may then determine if the caregiver <NUM> is a valid POC system <NUM> user. The POC system <NUM> may also require the caregiver <NUM> to enter a password, user name, and/or other information.

As shown in <FIG> and <FIG>, the caregiver <NUM> may initiate the workflow for automatically programming the infusion pump <NUM> by scanning the patient's wristband (step <NUM>), scanning the IV bag (step <NUM>), and scanning the infusion pump (step <NUM>). At step <NUM>, the caregiver <NUM> may use a scanner, such as identification receiver <NUM> at POC client <NUM>, to scan the identifier on the patient's wristband, bracelet, or tag <NUM>. The patient ID, which may be a medical record number, an account number or some other identifier that the care facility uses to positively identify the patient, may be retained in a memory in the POC client <NUM>.

At step <NUM>, the caregiver <NUM> may use the POC client <NUM> to scan the identifier <NUM> on the identification label <NUM> on the IV bag <NUM>. The container ID <NUM> may comprise machine-readable indicia such as a bar code, RFID tag, or the like. The container ID <NUM> may be a universally unique order ID so that the HIS <NUM> or POC system <NUM> may retrieve information about the association medication order without having to scan the patient ID on the patient wristband, bracelet, or tag <NUM> (or other patient identification device) or rely on such patient ID information for comparison purposes. Alternatively, the container ID may be a composite ID that includes patient ID or some portion thereof and an order ID related to that particular patient. Alternatively, the container ID may be an absolute or unique pharmacy order identifier that may be generated by the order entry or pharmacy information systems. Alternatively, for commonly used containers that are stocked on the ward or patient care floor, like dextrose, saline or other solutions, the container ID may be a medication ID that includes only medication-specific information, including but not limited to medication name, concentration (if applicable) and volume.

At step <NUM>, the caregiver <NUM> may use the POC client <NUM> to scan the barcode label <NUM> or RFID tag on the infusion pump <NUM> or a channel of the pump to obtain medical device specific identification information <NUM> on the identifier. Thus, the POC client <NUM> may receive or capture the pump ID or identifier information. Steps <NUM>, <NUM>, and <NUM> may be performed in any order. For instance, the caregiver <NUM> may perform step <NUM> first, followed by steps <NUM> and <NUM>, or may perform step <NUM> first, followed by steps <NUM> and <NUM>, and the like.

As shown in <FIG> and <FIG>, the information scanned by the caregiver <NUM> at steps <NUM>, <NUM>, and <NUM> may be transmitted to the patient's electronic medical records (EMR) and/or the barcode medication administration (BCMA). In certain aspects, the caregiver <NUM>, after performing the scans with the POC client <NUM>, may select a button (such as a "start" or "done" button) on the POC client <NUM>. Selection of the button may cause the POC client <NUM> to transmit the scanned information to the EMR/BCMA. The BCMA may comprise, for example, POC system <NUM>.

Based on the received scanned information, the EMR/BCMA within the HIS <NUM> may look up patient demographic information it received from the Admission, Discharge and Transfer (ADT) system <NUM> and an infusion order for the patient or medication it received from the Pharmacy Information System (PIS) <NUM>. Software in POC system <NUM> may then perform a variety of safety checks, comparisons or matching functions to ensure that the right drug is administered to the right patient, at the right rate, in the right dose, at the right time, via the right route, and by an authorized or right caregiver, etc. as is conventional in the BCMA art. The BCMA/POC system <NUM> then transmits an auto-programming message containing infusion pump settings to the MMU <NUM>.

At step <NUM>, based upon the pump identification information contained in the auto-programming message, the MMU <NUM> may then look up the infusion pump network location to determine the pump that is targeted to receive the infusion pump settings contained in the auto-programming message.

At step <NUM>, the MMU <NUM> may send the infusion pump settings to the infusion pump <NUM> using the pump's IP address. At step <NUM>, the infusion pump <NUM> may receive the infusion pump setting and then verify the infusion program settings against the installed drug library. In other words, the infusion pump <NUM> may ensure that the received program settings for the patient <NUM> are consistent with the information provided in the drug library. Steps <NUM>, <NUM>, and <NUM> shown in <FIG> illustrate exemplary steps that may be performed after the infusion pump has determined that the program settings are consistent with the permissible settings specified in the drug library of the pump <NUM>. As discussed further below, steps <NUM>, <NUM>, and <NUM> shown in <FIG> illustrate exemplary steps that may be performed after the infusion pump has determined that the program settings are inconsistent with the permissible settings specified in the drug library of the pump <NUM>.

As shown in <FIG>, at step <NUM>, after the infusion pump <NUM> has verified that the program settings are consistent with the drug library, the infusion pump may populate the program settings, for example at display screen <NUM>. The infusion pump <NUM> may display one or more program settings at display screen <NUM>, such as drug name, drug concentration, container volume, VTBI, rate or duration, and the like. The infusion pump <NUM> may also display a request for a nurse to confirm the displayed program settings.

At step <NUM>, the caregiver <NUM> may review and verify that the displayed infusion program settings were correctly populated. The caregiver <NUM>, in some aspects, may be required to select a button at the infusion pump <NUM> in order to indicate confirmation that the infusion program settings were correctly populated. In response, the infusion pump <NUM> may display a start button on screen <NUM> that enables the caregiver <NUM> to start the infusion in accordance with the final confirmed programmed pump settings. The caregiver <NUM> may select the start button to start the infusion program at step <NUM>.

Referring now to <FIG>, workflow steps illustrate an exemplary process in which the infusion pump settings are inconsistent with the settings stored in the drug library. The process illustrated in <FIG> comprises the same steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> as <FIG>. However, the auto-programming workflow illustrated in <FIG> comprises exemplary steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> not performed at <FIG>, and which may be performed after infusion pump <NUM> determines that the infusion program settings are inconsistent with the drug library at step <NUM> or in the case of steps <NUM>, <NUM> and <NUM>, if the manual program is acceptable, yet perhaps not an exact match for a stale auto-program that arrives after or during a manual infusion for example. Embodiments generally analyze and save these events wherein the caregiver may also be notified that an auto-program has arrived, but that the caregiver has successfully manually programmed the infusion pump, whether exactly or acceptably when compared to the auto-program.

At step <NUM>, infusion pump <NUM> may display an error message. The error message may be reported to the MMU <NUM> at step 315a. The error message may be relayed and reported to the EMR/POC system <NUM> via the MMU server <NUM> at step 315b. Alternative, the error message can be reported directly from the pump <NUM> to the EMR/POC system <NUM> through any wired or wireless networks available in the hospital. Most importantly, the error message may be displayed at or on the display screen <NUM> of infusion pump <NUM>. Thus, even if the caregiver has limited or no access to the POC client or other computer systems within the hospital at the time, they will be advised of auto-programming errors at the pump <NUM>. As will be discussed in greater detail below, the error message may notify the caregiver <NUM> of the rejection of the auto-programming request. The error message may comprise an error code and a brief description of the error cause. The error message may further comprise suggested actions for the caregiver <NUM> to perform in response to the error message. For example, if the keypad is locked, the infusion pump <NUM> may output an error message KL000017 stating "The auto-program is not valid because the keypad is locked. " The infusion pump <NUM> may also display, on the same screen, a suggested or recommended action, e.g., "Unlock the keypad". A table of errors, including exemplary code numbers, descriptions and recommended actions are included below in Table <NUM>.

At step <NUM>, the caregiver <NUM> may review and respond to the error message displayed at the infusion pump <NUM>. The caregiver <NUM> may provide a response that comprises at least one of a modification to the auto-programming request, performing the actions suggested at the pump <NUM>, and/or rejecting or clearing the error message and suggested action. Based on the response to the error message received at step <NUM>, pump <NUM> may perform an operation at step <NUM>. For example, after displaying the error message provided above and suggested action "Unlock the keypad", infusion pump <NUM> may receive a response from the caregiver <NUM> that the keypad has been unlocked. The caregiver's action of unlocking the keypad may itself serve as the response to the error message at step <NUM>. Thereafter, the operation performed at step <NUM> may comprise the infusion pump starting the infusion program similar to or the same as step <NUM> illustrated in <FIG>. Thus, if the caregiver <NUM> responds to the error message at step <NUM> by performing the suggested action, the infusion pump <NUM> may, at step <NUM>, automatically start the requested infusion auto-program. The caregiver <NUM> may respond to the error message by adjusting program settings such as dose, rate, VTBI, duration, and the like on the infusion pump <NUM>.

In some aspects, the caregiver <NUM> may reject or override the error message displayed at step <NUM>. The caregiver <NUM> may override the error message at step <NUM> in cases of soft limit violations. Some limit violations may require entry of a special override code or input of a code from a second caregiver or supervisory personnel. In another aspect of the invention, the infusion pump <NUM> may display an error message that a pump channel is "Already in Use". The caregiver <NUM> may investigate and determine that the pump is not in use. The caregiver <NUM> may send a response rejecting the error message and indicating that the pump channel is not currently in use. The pump <NUM> may then return to step <NUM> to verify infusion program settings against the installed drug library or may automatically start the infusion program at step <NUM>.

In certain aspects, the caregiver <NUM> may not input a response into infusion pump <NUM> within a predetermined time. The lack of a response within this predetermined time may itself server as a response to error message <NUM>. Specifically, the infusion pump <NUM> may be configured (for example, by the manufacturer or the hospital via the user customized drug library configuration settings downloaded to the pump by the MMU) to timeout after a predetermined time. The predetermined time may be about <NUM> seconds, <NUM> seconds, <NUM> seconds or any other amount of time. If the infusion pump <NUM> does not receive a response within the timeout period (or predetermined time), the infusion pump <NUM> may reject the auto-program and display a previous or home screen at display screen <NUM>. In this case, the operation performed at step <NUM> may comprise clearing the error message and displaying a previous or home screen at the pump <NUM>.

In one or more embodiments, the at least one infusion pump <NUM> saves and executes the at least one manual infusion program received from the at least one caregiver <NUM>. At step <NUM>, in at least one embodiment, the at least one infusion pump <NUM> compares the at least one stale auto-program to the at least one manual infusion program that has been completed or is running.

In at least one embodiment of the invention, the at least one manual infusion program may be entered at the infusion pump and/or accessed as provided in a library stored at the at least one infusion pump <NUM>. In one or more embodiments, the comparison may be based on an approximate time of infusion administration and parameter matching logic including infusion administration parameters and infusion pump operating parameters, for example volume to be infused, rate, or any other characteristic available in the system.

By way of at least one embodiment, the at least one infusion pump compares the infusion pump operating parameters and the infusion administration parameters to identify potential matches between the at least one stale auto-program and the at least one manual infusion program. In one or more embodiments, the at least one infusion pump <NUM> may evaluate the potential matches using one or more configurable rules and determines if the potential matches are within a predefined tolerance. In at least one embodiment, the at least one infusion pump <NUM> may continue to execute the at least one manual infusion program on the at least one infusion pump <NUM> if the potential matches are within the predefined tolerance. Any type of logic including neural networks, rule based, threshold or range based may be utilized to determine whether an acceptable manual program has executed or is executing when compared with the stale auto-program.

At step <NUM>, in one or more embodiments, the at least one infusion pump <NUM> saves differences in the at least one manual infusion program and the at least one stale auto-program in the remote server or MMU <NUM> for later analysis and/or data mining. This may allow the management system to determine which caregivers are accurate or even may be utilized to determine whether better outcomes of care result from a slightly different, yet acceptable manual program when compared to the auto-program as well as determine whether cost saving may be made while maintaining a given level of service, for example with shorter patient stays or less drug volume used overall. Any other large data analysis is in keeping with the invention when comparing manual programs and stale auto-programs and any parameters associated with the patient, drug, volume to be infused, rate, or any patient characteristics such as age or time of stay or any other parameter.

In at least one embodiment, the at least one infusion pump <NUM> remotely saves a first event alert indicating the at least one manual infusion program as an acceptable potential match of the potential matches, and remotely saves a second event alert indicating the at least one auto-program as an un-executed program because the at least one manual infusion program is an acceptable potential match.

At step <NUM>, in one or more embodiments, the at least one infusion pump <NUM> may optionally notify the at least one caregiver <NUM> of the acceptable at least one manual infusion program using the first event alert, and optionally notify the at least one caregiver <NUM> of the at least one auto-program as an un-executed program using the second event alert.

According to at least one embodiment of the invention, the at least one infusion pump <NUM> may include a graphical user interface comprising keys and a display screen <NUM> or an input/output touch screen <NUM> on the at least one infusion pump, such that the at least one caregiver <NUM> may input the at least one manual infusion program via the graphical user interface.

In one or more embodiments, the at least one infusion pump <NUM> may save identification data of the at least caregiver <NUM>. In at least one embodiment of the invention, the at least one infusion pump <NUM> compares the at least one manual infusion program from the at least one caregiver <NUM> to the at least one stale auto-program to determine a scoring of accuracy. In at least one embodiment, the scoring of accuracy may include an acceptability level of the at least one manual infusion program from the at least one caregiver.

By way of one or more embodiments of the invention, the at least one infusion pump <NUM> may generate at least one report from the comparison of the at least one manual infusion program to the at least one stale auto-program. In at least one embodiment, the report generated by the at least one infusion pump <NUM> may include one or more of a time differential between completion time of the at least one manual infusion program and completion time of the at least one stale auto-program, a scoring of accuracy including an acceptability level between infusion administration parameters of the at least one manual infusion program and the at least one stale auto-program, and a rating of the at least one caregiver <NUM>.

In at least one embodiment of the invention, the accuracy/effectiveness history or rating of the at least one caregiver <NUM> may determine if the at least one manual infusion program received from said at least one caregiver <NUM> is acceptable and/or more accurate or effective than the at least one auto-program. The at least one stale auto-program is aggregated and compared using matching logic (either statically residing on the pump or dynamically provided with the auto-program) to the at least one manual infusion program received from the at least one caregiver <NUM> at the at least one infusion pump <NUM>. This comparison generates an auto-program compliance information / rating or contributes to an overall auto-program compliance information / rating for the at least one caregiver <NUM>. The at least one infusion pump <NUM> would subsequently display the at least one caregiver <NUM> compliance information (rating) for the at least one caregiver <NUM> at the next attempt to auto-program the infusion pump. Auto-program compliance information is saved in a memory of the pump and, whether or not displayed on the pump, can be subsequently transmitted or relayed to the first computer, another medical device or infusion pump or a remote computer for storage, analysis, display or use.

In one or more embodiments, the at least one infusion pump <NUM> may transmit the at least one manual infusion program from the at least one caregiver <NUM> to the first computer. In at least one embodiment, the first computer may save the at least one manual infusion program from the at least one caregiver <NUM> and may save identification data of the at least one caregiver <NUM>. In one or more embodiments, the first computer may compare the at least one manual infusion program from the at least one caregiver <NUM> to the at least one stale auto-program to determine a scoring of accuracy or effectiveness. In at least one embodiment, the scoring of accuracy may include an acceptability level of the at least one manual infusion program from the at least one caregiver <NUM>.

By way of one or more embodiments of the invention, the first computer may generate at least one report from the comparison of the at least one manual infusion program to the at least one stale auto-program. In at least one embodiment, the report generated by the first computer may include one or more of a time differential between completion time of the at least one manual infusion program and completion time of the at least one stale auto-program, a scoring of accuracy including an acceptability level between infusion administration parameters of the at least one manual infusion program and the at least one stale auto-program, and a rating of the at least one caregiver <NUM>.

<FIG> illustrates an enhanced view of the exemplary infusion pump <NUM> comprising display screen <NUM>. The exemplary screens provided in <FIG> and <FIG> may be displayed at display screen <NUM>. The infusion pump <NUM> may display error messages, error codes, and suggested actions at display screen <NUM>. The display screen <NUM> includes a plurality of areas or regions such as a status region 88A, a working region 88B, and a message region 88C. The pump may comprise a memory, a processor, a clock (real time or otherwise) and other components. The memory may store computer-executable program instruction. Moreover, the processor may execute the computer-executable program instructions, which may cause the processor to perform one or more steps recited in the present disclosure.

<FIG> and <FIG> illustrate exemplary flow diagrams for displaying error messages at display screen <NUM>. Prior to turning on the multi-channel infusion pump <NUM>, a cassette may or may not first be required to be installed in the infuser. A caregiver <NUM> may install the cassette into the door of pump <NUM> and then close the door. Next, the nurse may turn on the infusion pump <NUM> by pressing an ON/OFF button, such as the ON/OFF button <NUM> shown in <FIG>. After the ON/OFF button <NUM> is pressed, infusion pump <NUM> may begin its startup process. After the startup process, which may take up to a few minutes, the infusion pump <NUM> may be prepared to accept an auto-programming request.

At this point, infusion pump <NUM> may display screen <NUM>. Display screen <NUM> may be referred herein as the A/B screen or home screen. As shown in <FIG>, screen <NUM> may display (in the working region 88B or elsewhere) delivery information for channel A and channel B, such as the rate and volume infused or volume to be infused (VTBI). Because an auto-programming request has not yet been received, the initial values for the delivery information may be set at <NUM> as shown in screen <NUM>. The home screen <NUM> may also display a selected CCA (here shown directly below the Volume Infused or Volume To Be Infused (VTBI) as "ICU," which represents an intensive care unit). Home screen <NUM> may also display instructions or suggested actions that could be taken by a caregiver <NUM>. For example, screen <NUM> may initially display suggested action "Select Line A/B to program" as shown in <FIG>. The suggested action may alert the caregiver <NUM> of the next steps to be taken in order to submit a manual or an auto-program request. In certain aspects, infusion pump <NUM> may display the suggested actions at screen <NUM> in a different color and/or with different shading than other information displayed on the screen. Exemplary screens shown in <FIG> and <FIG>, for example, display the suggested actions in white text with black shading in contrast to other information displayed in black text and white shading. Moreover, the suggested actions may be displayed in a particular section, region or area of each screen, such as in the message region near the bottom of each screen shown in <FIG> and <FIG>.

The screens displayed at the infusion pump <NUM> may include other indicators, such as a battery life indicator <NUM> (which may indicate the amount of battery life remaining for the pump <NUM>), a wireless signal indicator <NUM> (which may indicate the strength of the wireless signal connection at pump <NUM>), and a two-way arrow <NUM> (which may indicate connection between the MMU and the pump and thus the capability of pump <NUM> to upload and download information to and from the MMU server <NUM>).

Screens, as shown in <FIG> and <FIG>, may further comprise various input options. The input options may be presented in a row at the bottom of the screen (such as directly below the suggested actions as shown in <FIG> and <FIG>). Each input option may be an option that may be selected by a caregiver <NUM>. In some aspects, the caregiver <NUM> may touch the screen itself to select an input option, and in other aspects, the caregiver <NUM> may select a corresponding soft key or button directly below the input option. See the triangles below the screen <NUM> and the input options in <FIG>. Other options and text, such as "OK", "Continue", "Reject", "Yes", "No", "Standby", "Standby Confirmation", "Delay Start", "Return to A/B", etc. may be displayed in the message region 88C and selected by caregiver using a touchable screen or the corresponding soft key below the displayed option or text. In response to the display at screen <NUM> and the suggested action "Select Line A/B to program", caregiver <NUM> may select either input option "A", input option "B", or input option "Settings/Vols/CCA". Selecting option "Settings/Vols/CCA" may cause infusion pump <NUM> to display a screen in which caregiver <NUM> may edit settings, the way volume is displayed (volume infused versus volume to be infused or VTBI), or a CCA for the infusion pump <NUM>. Selecting either option "A" or "B" may initiate the auto-program sequence for that selected channel.

At step <NUM>, infusion pump <NUM> may determine whether an auto-programming request has been received. In other words, infusion pump <NUM> may determine whether the steps described with respect to <FIG> have been performed, particularly steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>.

At step <NUM>, the infusion pump <NUM> may determine whether it needs to change the auto-program drug order to "No Drug Selected". The analysis performed at step <NUM> is an example of the various analyses that may be performed when the infusion pump <NUM> verifies the infusion program settings against the installed drug library at step <NUM>. Thus, as the pump <NUM> performs its verification step <NUM>, one of the plurality of verification actions it may perform may include determining whether the medication selected by caregiver <NUM> is stored in the drug library for the selected CCA. For example, caregiver <NUM> may select the CCA "ICU" prior to auto-programming. Then the caregiver <NUM> may select or scan medication using POC client <NUM> at step <NUM>. After pump <NUM> receives the auto-programming request for the ICU CCA, pump <NUM> may verify the program settings against installed settings stored in its drug library at step <NUM>. One of the verification steps may include determining whether the selected or scanned medication is included among the medications stored in the drug library for the ICU CCA. In other words, a processor of the pump <NUM> makes a comparison between the drug name, concentration and dosing units provided in the auto-programming request to the same parameters in the drug library for the particular clinical care area selected or active on the pump. If, in the drug library, the selected medication is not among the listed medications available for the ICU CCA, pump <NUM> may be programmed to output "No Drug Selected" as a substitution alert error message. At step <NUM>, if the pump <NUM> determines that it must change the order to "No Drug Selected", it may display an error message such as screen <NUM>.

The error message may comprise a brief description of the error so that the caregiver <NUM> may be able to quickly determine the cause of the error at the pump <NUM> and perform subsequent actions in response to the error. In the example provided at screen <NUM>, processor of the pump <NUM> may perform a drug name, concentration, dosing units, or drug ID comparison against the drug list in the drug library on the pump for the selected clinical care area or CCA and display at display screen <NUM> the error message "The Auto-Program contains a medication which is not available in the CCA (ICU)" and "For this order the medication 'No Drug Selected' has been substituted". The pump <NUM> may display a "Substitution Alert" in the status region or elsewhere on screen <NUM> to notify caregiver <NUM> that an error has occurred. The error message may then notify the caregiver <NUM> of the precise cause of the error (here, the selected CCA and the fact that the auto-program contained a medication that, pursuant to the hospital's best practices as set forth in the customizable drug library, is not planned to be available in the CCA). The error message may also, in some aspects display the actions taken by the pump <NUM> in response to the error (here, "No Drug Selected" has been substituted for the medication by the processor of the pump because it found no match for the medication in the drug library entries for the selected CCA).

Also shown in the message region or elsewhere on the screen <NUM> is the suggested action "Continue with no drug selected or Reject program". The suggested action may notify caregiver <NUM> that s/he should either select the input option "Continue" in order to continue the auto-program request with no drug selected substituted for the medication, or select the input option "Reject" to cancel the auto-program request. The input options may be displayed immediately below the suggested action, as shown in screen <NUM>. If the caregiver <NUM> selects the "Reject" option, pump <NUM> may deny the auto-program request and display a previous screen such as home screen <NUM>. A message concerning the rejection of the auto-program request may be sent to the MMU server <NUM>, which then relays the message to the POC system <NUM>. In certain aspects, screen <NUM> may be displayed for a predetermined amount of time, such as about <NUM> seconds. If no response or input option is selected within that predetermined amount of time, pump <NUM> may automatically reject the auto-programming request and display screen <NUM>. If, instead, the caregiver <NUM> selects the "Continue" input option, pump <NUM> may display screen <NUM> where the rest of the auto-programmed delivery information is pre-populated on the pump screen <NUM> in the working region 88B or elsewhere as shown on screen <NUM>. At screen <NUM>, caregiver <NUM> may edit the delivery information, such as rate, VTBI, and duration. Screen <NUM> may continue to display "No Drug Selected" in or near the status region 88A at the top of the screen and a suggested action "Enter value using keypad" in the message region 88C at the lower portion of the screen <NUM>. Pump <NUM> may also highlight the field that may have its value edited (here, e.g., "<NUM>" for VTBI in mL) or do so when activated by touch or other keys. The caregiver <NUM> may enter these values on the keypad <NUM> provided at the pump <NUM>, as shown in <FIG>.

At step <NUM>, pump <NUM> may determine if the start button <NUM> (<FIG>) has been selected or pressed by the user. If so, pump <NUM> may display a screen such as screen <NUM>. The screen <NUM> may correlate with step <NUM> in which the caregiver <NUM> verifies the infusion program settings were correctly populated. Caregiver <NUM> may select input option "No" to return to screen <NUM> and edit one or more of the displayed delivery information values. Alternatively, caregiver <NUM> may select the "Standby" input option to standby for a predetermined or configurable period of time to await confirmation of the medication delivery. If the "Yes" input option is selected, pump <NUM> may start the infusion program at step <NUM> and may display screen <NUM>. Screen <NUM> may notify the caregiver <NUM> that medication is pumping on the selected channel (here, channel A) at the selected rate (here, <NUM>/hr) and display a current Volume Infused (here, <NUM>). Screen <NUM> may also display the suggested action "Select Line A/B to program", which may enable the caregiver <NUM> to edit or submit another auto-program request for channel A or B. In certain aspects, channel A may be a primary channel for administering medication and channel B may be a secondary line for administering medication.

<FIG> illustrates another example of a flow diagram of screens displayed at pump <NUM>. The series of screens shown in <FIG> begins at screen <NUM>, which may be similar to screen <NUM> shown in <FIG>. In the example provided in <FIG>, a caregiver <NUM> may request an auto-program at pump <NUM> even as channel A is pumping. Here the pump <NUM> is pumping Dopamine, a commonly prescribed vasoactive medication for controlling blood pressure. Dopamine is prescribed based on the patient's weight, which in this example is <NUM>. The Dopamine is supplied at a concentration of <NUM> in a <NUM> container. The prescribe dose is <NUM> mcg/kg/min, which the pump converts to a rate of <NUM>/hr. The pump <NUM> has pumped <NUM> so far. Similar to step <NUM> of <FIG>, the pump <NUM> may determine in step <NUM> whether an auto-programming (AP) request has been received for channel A. The request may be received after steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> have been performed. At step <NUM>, pump <NUM> may verify infusion program settings against program settings stored in the drug library. In some aspects, pump <NUM> may further verify the infusion program settings against settings hard-coded into the pump. The verification step <NUM> of <FIG> or <FIG> may comprise step <NUM> of <FIG>, in which pump <NUM> may determine whether the auto-program request for channel A is for the same medication or an acceptable alternative to the medication currently being delivered at channel A. In one aspect, the concept of the "same medication" can comprise the same medication by name (generic or brand), and one or more of concentration and dosing units. If the medication in the auto-program request for channel A is Dopamine, it might be okay and not trigger a mismatched medication/concentration error (code MCD00006 in Table <NUM> above). However, if the pump determines in step <NUM> that a different or non-equivalent medication is specified in the auto-program request received in step <NUM>, such as Morphine for example, the pump <NUM> displays the error message shown on screen <NUM>.

Screen <NUM> may display "Rejection Alert" in the status region or another region of the screen to notify caregiver <NUM> of an error. Screen <NUM> may also display the error message, such as "The Auto-Program received contained a medication which is different from what is delivering on the programmed line" in the working region or another region. Thus, the caregiver <NUM> may be notified at the pump <NUM> that there has been an error and the cause of the error. In some aspects, this error message may also display the medication that is being delivered on the channel, and/or other information such as the concentration and or dosing units of the medication order. For example, the error message at screen <NUM> may display "The Auto-Program received contained a medication [Morphine] which is different from [Dopamine] that is delivering on the programmed line" or "The Auto-Program received contained a medication which is different from the [Dopamine <NUM>/<NUM>] that is delivering on the programmed line". Screen <NUM> may also display the suggested action for this error message in the message region or another region, in this case "Reject this order now, or wait for automatic rejection?" Pump <NUM> may provide one or more one input options at screen <NUM>, e.g., an option to reject the auto-program order. Caregiver <NUM> may select the "Reject" option to return to screen <NUM>. Alternatively, caregiver <NUM> may not select an input option at all, in which case pump <NUM> may automatically reject the auto-program order after the timeout period, such as about <NUM> seconds.

If, at step <NUM>, pump <NUM> determines that the medication in the auto-programming request is the same or equivalent as the medication currently pumping on channel A, or that the at least one manual infusion program is acceptable, pump <NUM> may display screen <NUM>. Similar to screen <NUM>, discussed above, screen <NUM> may enable a caregiver <NUM> to modify the settings of the delivery information values, such as concentration, rate, VTBI, and duration. Also shown at screen <NUM> is an input option "Delay Start". A caregiver <NUM> may select the "Delay Start" input option in order to select a later time in which to begin pumping of the auto-program medication. Alternatively, caregiver <NUM> may select the "Return to A/B" input option to return to screen <NUM>.

At step <NUM>, pump <NUM> determines if the start button <NUM> (as shown in <FIG>) has been selected. If so, pump <NUM> may display screen <NUM>. Caregiver <NUM> may be able to review the information displayed at screen <NUM>, similar to screen <NUM> as discussed above. Caregiver <NUM> may then select the "Yes" input option to verify that the infusion program settings were correctly populated at step <NUM>. In response, pump <NUM> may start the infusion program at step <NUM> and the infusion pump <NUM> may display screen <NUM>.

Some other examples of error messages that may be displayed by the pump <NUM>, for example at screens such as screens <NUM> and <NUM>, will now be discussed in further detail. In certain aspects, pump <NUM> may determine an error at step <NUM> without any outside intervention from, for example, MMU, HIS, BCMA, EMR, and the POC system. In some cases, pump <NUM> may allow an auto-programming order to continue after displaying an error message. Pump <NUM> may also notify parties, such as MMU, HIS, BCMA, EMR, and the POC system of an error and the error message that was displayed. Those of ordinary skill in the art will appreciate that the error messages disclosed herein are exemplary, and may be modified without veering from the scope of this disclosure.

Pump <NUM> may display an error message such as associated with error code NTA00003 in Table <NUM> above, "The auto-program received contains duration information, and you cannot titrate the duration of a delivery with this dosing unit". This error message will be displayed when the infuser receives an auto-program message with a titrated duration value and is for a medication that normally has time-based alternative dosing units. For example, if the drug involved in the program has time-based alternative dosing units the caregiver is not allowed to change the duration because such an action would change the associated dose. Examples include but are not limited to vasoactive drugs like nitroglycerin or Dopamine dosed in mcg/kg/min, anti-coagulants like Heparin dosed in units/kg/hour, diabetes control drugs like Insulin dosed in Units/kg/day, and oncolytic drugs like Taxol dosed in mg/m2/day. The particular drugs or categories of drugs for which this type error is generated can be established by the hospital according to their preferences in their user customizable drug library. On the same screen, pump <NUM> may display the suggested action, e.g., "Press OK now, or wait for this screen to automatically dismiss". After selection of the "OK" input option or waiting for the screen to automatically dismiss after the timeout period, pump <NUM> may display the home A/B screen.

In some aspects of the disclosure, pump <NUM> may display an error message such as "The auto-program received did not contain all required information". Generally, the auto-programming message should include at a minimum the following information: pump channel, drug name and concentration. If one or more of these elements, parameters or settings is missing, the above-mentioned error message is displayed. On the same screen, pump <NUM> may display the suggested action, e.g., "Press OK now, or wait for this screen to automatically dismiss". As discussed above, after selection of the "OK" input option or waiting for the screen to automatically dismiss after the timeout period, pump <NUM> may display the home A/B screen.

Pump <NUM> may be programmed to generate and display an error message such as "The auto-program received contains a value that exceeds a system limit. Or the values cause a calculated parameter to exceed a system limit. " One or more system limits may be hard-coded into pump <NUM> and/or included in the drug library. The system limits may pertain to a rate. For example, the pump <NUM> may be able to pump at a maximum rate of <NUM>/hr. If an auto-program request is received at a rate greater than <NUM>/hr. , for example say <NUM>/hr. , pump <NUM> may display the error message. Similar system limits may exist for other information such as duration, VTBI, and the like. Along with the error message, pump <NUM> may display the suggested action, e.g., "Press OK now, or wait for this screen to automatically dismiss".

In some instances, pump <NUM> may display an error message such as "The auto-program is for a line that contains unconfirmed programming data". This might happen if the caregiver got called away on an emergency to help another patient or co-worker before confirming the programming data. Pump <NUM> may also display the corresponding suggested action "Resubmit the auto-program. All unconfirmed data will be cleared. " Thus, in response to the error message, caregiver <NUM> may either resubmit the auto-program or reject the auto-program. If the user elects to resubmit the auto-program, all of the unconfirmed data previously entered will be cleared and thereafter replaced with the data from the resubmitted auto-program. If the caregiver rejects the auto-program, the unconfirmed data will be maintained and the user is taken to the last input screen used or the home A/B screen.

Pump <NUM> may generate an error message at screen <NUM> stating "The auto-program is rejected because of a partially programmed line. " A line is partially programmed when a drug is selected for the line and the line program has not been cleared or confirmed. A pump with an installed cassette was started. The CCA was selected. A new IV bag containing the same or different drug was hung. The user manually selects one of the lines and a medication on the pump. The user then switches part way through the programming sequence to the auto-program process, wherein the barcode on the drug container is scanned and the order sent. The standard auto-program for line A is sent to the infuser, which rejects the auto-program because a manual program was already partially input. On the same screen, the suggested course of action is displayed: "Press [Clear] and resubmit the auto-program. All unconfirmed data will be cleared.

Caregiver <NUM> may select a "Standby" input option at pump <NUM> for a particular channel. The standby input option is selected to suspend for an indefinite time, up to <NUM> hours, an infusion that has already been programmed on a particular channel or infusion line. The standby option can be used prior to an infusion being started if the caregiver is unsure of the time the infusion should be started. For example, the caregiver can set up the pump and it can be programmed, but the patient may not yet be present at their bed. However, unlike the delayed start option which inserts a predetermined delay prior to the start of a programmed infusion, the standby option also can be selected during the execution of a programmed infusion. It would be undesirable in most cases for a previously programmed and started infusion program to be automatically supplanted by a new set of infusion pump settings through an auto-programming message or request. Thus, the pump <NUM> may not accept an auto-program request for a channel or line that is already in standby mode. When a request is received for a line in standby, pump <NUM> may display an error message such as "The auto-program is for a line which is in Standby". Similarly, pump <NUM> may not accept an auto-program request for a channel or line that is "Delay Start" mode. As discussed above, "Delay Start" may enable a caregiver <NUM> to input auto-program settings to be started automatically at a later time (X number of minutes or hours later), wherein the later time may be predetermined, known and selected by the caregiver <NUM>. If pump <NUM> receives a request for auto-program on a line which is in "Delay Start" mode, pump <NUM> may display an error message such as "The auto program is for a line which is in Delay Start". For both the Standby and Delay Start error messages, pump <NUM> may display a suggested action, e.g., "Clear this line and resubmit the auto-program". This suggested action may advise the caregiver <NUM> to clear the line that is in either "Standby" or "Delay Start" mode and then resubmit the auto-program request.

Pump <NUM> may display the error message "The auto-program is for a line that has an active alarm that stops or prevents delivery, thus the auto-program is not valid in this alarm condition. " Pump <NUM> may be capable of outputting alarms for various situations or conditions. For example, the pump <NUM> battery may be almost dead and not plugged in to a power source. In another example, a high priority alarm may be in progress. During these situations, pump <NUM> may not accept an auto-program request and, along with the error message, may display the suggested action "Clear the alarm condition and resubmit the auto-program". Clearing the alarm may comprise eliminating the condition causing the alarm (such as replacing or charging the pump battery).

Because of the unique concurrent delivery capabilities of the PLUM™ infusion pump, two different medications can be delivered from two different source containers upstream of the pump, effectively at the same time through a single line to the patient downstream of the pump. The pump can also switch back and forth from delivering medication from lines A and B respectively, and vice versa, making separate but coordinated "piggyback" delivery possible and convenient. However, this can lead to some rather complex scenarios from an auto-programming perspective. Many things can go wrong and lead to errors, including failures, unintended consequences or problems. Previously many of these errors would not have been communicated to the caregiver at the pump or on its display screen. Recall from above that the pump may have a rate limit of <NUM>/hr. The pump may have certain low flow limitations too. Thus, in certain aspects, pump <NUM> may display an error message such as "The auto-program is not valid due to concurrency violation. Delivery A+B greater than <NUM>/hr or less than <NUM>/hr for each line. " Although the pump is physically capable of <NUM>/hr. through a single line, when concurrent delivery is taking place through two lines (A and B) only <NUM>/hr. is permitted for each of the lines A and B. Otherwise, if each line were to be programmed to deliver <NUM>/hr. or more, the pump system rate limit of <NUM>/hr. would be exceeded. Also, each line must also be programmed to deliver at least <NUM>/hr. or more for proper pump operation. As discussed above, on the same screen, pump <NUM> may display the suggested action, e.g., "Press OK now, or wait for this screen to automatically dismiss". For greater clarity to the pump user, the specific cause for the concurrency violation could be specified. For example, the error message could read "Delivery of A+B greater than <NUM>/hr" or "Delivery A+B less than <NUM>/hr" depending upon the specific cause. Concurrency errors can result from various situations as well. For example, an auto-program can be rejected for a concurrency violation when a new IV bag or container or rate change is requested for Line A or Line B when B is running in concurrent, which would result in a concurrency violation, i.e., delivery greater than <NUM>/hr. for the sum of the two lines or less than <NUM>/hr. on each line. Alternatively a concurrency violation can happen on the first attempt to program an initial concurrent delivery on Line B. The error messages can be tailored to more clearly indicate the specific situation that caused the rejection of the auto-program.

In some aspects, infusion pump <NUM> may be configured to pump primary medications through line A and secondary medication through line B in a separate but coordinated piggyback delivery in series. In some cases, an auto-program request for line B may cause an interruption to the pumping medication in line A. This may be undesirable, particularly when the medication pumping in line A is vital such as critical medications including but not limited to Dopamine, Heparin or Insulin. Thus, when the infusion pump <NUM> receives an auto-program for line B in step <NUM>, the infusion pump <NUM> may at step <NUM> make a determination whether a medication on that or another line is interruptible. If the answer is affirmative, then the process can continue to screen <NUM>, step <NUM>, etc. If the answer is negative, the pump <NUM> can display an error message at screen <NUM> such as "The auto-program is not valid for line B. The medication delivering for line A cannot be interrupted. " Similarly, infusion pump <NUM> may display an error message such as "The auto-program is not valid for line A. The medication in the Auto-Program is not interruptible and Line B is delivering a Piggyback infusion. " Correspondingly, pump <NUM> may display the suggested action "Press OK now, or wait for this screen to automatically dismiss".

Pump <NUM> may display the same suggested action on a screen with an error message such as "The auto-program is not valid because the weight of the patient in the Auto-Program does not match the weight of the patient on the program delivering on the other line. " The infusion pump <NUM> may generate this or similar error message when the weight or expected weight range entered for a patient is inconsistent among the multiple lines. For instance, a nurse may enter a weight of <NUM> for a patient on line A and then a weight of <NUM> for the same patient on line B. These inconsistent weights may cause infusion pump <NUM> to display the error message. Similarly, pump <NUM> may display an error message such as "The auto-program is not valid because the height of the patient in the auto-program does not match the height of the patient on the program delivering on the other line. " In this case, pump <NUM> may ensure that the height or expected height range of the patient receiving medication is consistent on line A and line B. Similarly, pump <NUM> may display an error message such as "The auto-program is not valid because the BSA in the auto-program does not match the BSA on the program delivering on the other line. " BSA means body surface area and is usually estimated or calculated based on a patient's body mass and height. BSA is also sometimes expressed as BMI or body mass index and some drugs are dosed on this basis.

As discussed previously, a caregiver <NUM> may be required to enter a CCA prior to programming the pump <NUM> manually or submitting an auto-program request. If no CCA is received or a CCA not stored in the drug library is received, infusion pump <NUM> may display an error message such as "The Auto-Program is not valid because a CCA has not been selected on the infuser. " Pump <NUM> may also suggest the action, e.g., "Select a CCA and resubmit the Auto-Program".

Pump <NUM> may comprise a lock to the keypad shown in <FIG>. When the keypad is locked, pump <NUM> may not receive commands submitted by selecting buttons on the keypad. Pump <NUM> also may not receive auto-programming requests when the keypad is locked. In those cases, pump <NUM> may display an error message such as "The auto-program is not valid because the keypad is locked. " The infusion pump <NUM> may also display the suggested action, e.g., "Unlock the keypad. " After caregiver <NUM> unlocks the keypad, pump <NUM> may automatically accept the auto-programming request.

The remaining error messages discussed below may be displayed in conjunction with the suggested action, e.g., "Press OK now, or wait for this screen to automatically dismiss". As discussed above, after selection of the "OK" input option or waiting for the screen to automatically dismiss after the timeout period, pump <NUM> may display the home A/B screen.

Pump <NUM> may, in some cases, generate and display an error message such as "The Auto-Program is not valid because the received parameters will not result in a valid dose. " When two out of the three parameters or variables volume, (flow) rate and duration are provided to the pump <NUM>, its processor can calculate a dose. Normally when a certain dosage is being targeted or ordered by the doctor, it is based upon the weight of the patient. The drug may be available as an amount or mass in a given volume of diluent such as <NUM> / <NUM> IV container. When there is no combination of values of flow rate and duration that will result in a valid dose, this error message is generated.

Infusion pump <NUM> may display an error message such as "The auto-program is not valid because the Rate cannot be titrated when VTBI is <NUM>. " This error message may be displayed when a caregiver <NUM> enters a rate for a medication to be pumped while also entering a total volume of the medication to be infused of <NUM>. Pump <NUM> may therefore require a VTBI greater than <NUM>. The auto-program might be a change to a currently running program - a "titration. " However, if there is no VTBI left to infuse in the program, the rate or other parameters cannot effectively be changed because there is no volume left to be infused. Similarly, infusion pump <NUM> may display an error message such as "The auto-program is not valid because it is a titration for a line that has no confirmed program. " A titration is by definition a change in rate, duration or VTBI in a currently running or already programmed infusion. Thus, you cannot auto-program a titration or change for a line or pump channel until after it has a prior program that has been confirmed.

In certain aspects, pump <NUM> may display an error message such as "The auto-program is not valid for a line with a Multistep or Loading dose program. " If the line is busy with a multistep infusion or loading dose program, that program must be completed or cleared before any new auto-program request can be received and executed.

Infusion pump <NUM> may display an error message such as "The Auto-Program was rejected by Hospira MedNet due to incomplete or corrupt data. " This might be highlighted by a checksum failure or handshake failure. Part of the auto-program message may have been lost or corrupted for one reason or another.

Pump <NUM> may display an error message such as "The Auto-Program for this infuser was rejected by Hospira MedNet™ due to drug library incompatibility. " The drug library identified in the device manifest for the auto-program message is not recognized. In other words, the active drug library mentioned in the auto-program manifest does not match what the MMU server <NUM> and/or the pump itself thinks is the appropriate drug library that is in the pump. For example, the drug library has an identifier (perhaps an alphanumerical string) that may include the pump type and version of the drug library. For some reason, the drug library version may get out of synch between the infusion pump and the MMU such that drug library identifier in the auto-program request does match the drug library that is currently in the infusion pump.

<FIG> illustrates a flow chart of a process <NUM> in accordance with aspects of the disclosure. Process <NUM> may be carried out using infusion pump <NUM> shown in <FIG>. Step <NUM> may comprise receiving an auto-programming request, wherein the auto-programming request may comprise IV bag or drug container information such as drug name, concentration or other drug identifying information, and infusion pump information, and optionally patient identification information. Step <NUM> may comprise receiving infusion program settings, parameters or variables including but not limited to dose, flow rate, duration and volume. Step <NUM> may comprise comparing the infusion program settings with drug library program settings, wherein the drug library program settings are included in rule sets that place soft (breachable) limits and hard (non-breachable) limits provided in a drug library stored at the infusion pump. Step <NUM> may comprise determining whether the infusion program settings are consistent or inconsistent with the drug library program settings based on the comparing.

Step <NUM> may comprise generating an error message based on the determining that the infusion program settings are inconsistent with the drug library settings. Step <NUM> may comprise displaying a screen, wherein the screen comprises the error message and a suggested action. In some aspects, other steps may be performed as discussed above in connection with <FIG>.

In at least one embodiment of the invention, if the infusion program settings are consistent with the drug library program settings based on the comparing, at step <NUM> the at least one infusion pump <NUM> compares the at least one stale auto-program received to the at least one completed or running manual infusion program based on an approximate time of infusion administration and parameter matching logic including infusion administration parameters and infusion pump operating parameters, to determine if the at least one previously completed or running manual infusion program is acceptable based on the potential matches as discussed previously.

Claim 1:
A system configured to identify an acceptable manual program, the system comprising:
a first computer (<NUM>) comprising a computer network interface; and
an infusion pump (<NUM>) configured to communicate with said first computer (<NUM>) using said computer network interface;
wherein said first computer (<NUM>) is configured to:
receive an infusion auto-program from a remote source, wherein said infusion auto-program comprises IV drug container information, infusion pump information, and infusion program settings,
when determining that said first computer (<NUM>) is unable to transmit said infusion auto-program to said infusion pump (<NUM>),
queue said infusion auto-program, and
send a stale auto-program to said infusion pump (<NUM>) when said infusion pump (<NUM>) communicates with said first computer (<NUM>); and wherein said infusion pump (<NUM>) is configured to:
receive a manual infusion program from a caregiver, wherein said manual infusion program comprises one or more of a completed manual infusion program or a running manual infusion program,
save and execute said manual infusion program,
compare said stale auto-program to said manual infusion program, wherein said comparison is based on one or more factors comprising an approximate time of infusion administration or parameter matching logic comprising infusion parameters,
identify potential matches between said stale auto-program and said manual infusion program using the infusion parameters,
determine that said potential matches are within a predefined tolerance using one or more configurable rules,
continue to execute said manual infusion program on said infusion pump if said potential matches are within said predefined tolerance,
save differences between said manual infusion program and said stale auto-program,
save a first event alert indicating the manual infusion program as an acceptable potential match of said potential matches, and
save a second event alert indicating the stale auto-program as an un-executed program because the manual infusion program is an acceptable potential match.