Medication delivery management

Methods for managing a delivery of prepared medications are provided. In one aspect, a method includes receiving first information includes a delivery deadline for a first medication, and receiving second information includes a preparation status of a second medication. The method also includes comparing the first information includes the delivery deadline for the first medication with the second information includes the preparation status of the second medication to determine whether the first medication should be indicated for delivery prior to completing preparation of the second medication, and providing a notification indicating when to deliver the first medication based on the determination. Systems and machine-readable media are also provided.

BACKGROUND

Field

The present disclosure generally relates to medication distribution, and, in particular, relates to systems and methods for managing delivery of a prepared medication in a healthcare facility.

Description of the Related Art

Certain pharmaceutical drugs are compounded to fit the needs of a patient. Compounding pharmacists combine or process appropriate ingredients using various tools to create a compounded pharmaceutical drug. For instance, compounding of sterile intravenous (IV) compounds can be done in anticipation of medication orders based on standard doses, or compounding can be done specific to a patient's need based on a physician order. Compounding may be done for medically necessary reasons, such as to change the form of the medication from a solid pill to a liquid, to avoid a non-essential ingredient that the patient is allergic to, or to obtain the exact dose(s) needed of particular active pharmaceutical ingredient(s). It may also be done for more optional reasons, such as adding flavors to a medication or otherwise altering taste or texture. Compounding is most routine in the case of intravenous (IV)/parenteral medication.

IV fluid delivery systems are used to deliver or “administer” such compounded IV medications (or “infusion solutions”) in fluid form to patients at controlled rates. Many individuals suffer from acute and chronic health problems, the treatment of which could require regular, and sometimes extended, IV infusions. Certain treatment regimens for diseases such as infections, cancer and even basic fluid and electrolyte replacement, require the regular and sequenced infusion of precise amounts of intravenous medication for the patient's survival. Specifics of intravenous infusion of medications may depend on the patient, treatment regimen, and choices of the clinician and institution. Treating chronic medical disorders often requires the administration of medication over a long period of time according to a treatment regimen specified by a medical professional, such as a physician.

In cases of patients admitted to a healthcare facility, one or more infusions to be administered to a patient are prescribed by the patient's physician. A pharmacy, generally located within the patient's hospital or healthcare facility, prepares the infusion medication or solution according to the physician's prescription, for example, in a cleanroom (e.g., an environment having a controlled level of contamination that is specified by a number of particles per cubic meter at a specified particle size). An appropriately trained and credentialed pharmacist places the infusion solution in a bag, bottle, syringe, or other container and labels the container. The infusion solution is then commonly staged in a pickup location, such as a bin-sorting area. A sorting person is then responsible for placing each prepared infusion solution into bins or delivery carts that correspond to the locations where the infusion solutions will be delivered, such as an Intensive Care Unit (ICU). A delivery person retrieves the infusion solutions from the bins that correspond to areas of the healthcare facility to which that delivery person delivers. The delivery person then delivers the infusion solutions to the appropriate locations of the healthcare facility.

A delivery person may not have any knowledge whether an infusion solution that urgently needs to be delivered to an area of the hospital that the delivery person delivers to is sitting in the bin-sorting area, or is in the process of being prepared. Thus, even though there may be a prepared infusion solution sitting it the bin-sorting area that urgently needs to be delivered to an area of the healthcare facility that the delivery person delivers to, the delivery person may be unaware of the infusion solution and may leave without the infusion solution. Therefore another delivery person will need to be dispatched to urgently deliver the infusion solution.

The infusion solution is then delivered to the patient's location and a clinician such as a nurse or other clinician hangs the infusion solution from a rack. The nurse connects a tube between the infusion solution and an infusion pumping system and inserts a cannula at the end of the tube into the vessel of the patient for delivery of the infusion solution to the patient.

SUMMARY

According to certain embodiments of the present disclosure, a system for managing a delivery of prepared medications is provided. The system includes a memory that includes instructions, and one or more processors. The one or more processors are configured to execute the instructions to receive first information including a delivery deadline for a first medication, and receive second information including a preparation status of a second medication. The one or more processors are also configured to execute the instructions to compare the first information that includes the delivery deadline for the first medication with the second information that includes the preparation status of the second medication to determine whether the first medication should be indicated for delivery prior to completing preparation of the second medication, and provide a notification indicating when to deliver the first medication based on the determination.

According to certain embodiments of the present disclosure, a method for managing a delivery of prepared medications is provided. The method includes receiving first information including a delivery deadline for a first medication, and receiving second information including a preparation status of a second medication. The method also includes comparing the first information that includes the delivery deadline for the first medication with the second information that includes the preparation status of the second medication to determine whether the first medication should be indicated for delivery prior to completing preparation of the second medication, and providing a notification indicating when to deliver the first medication based on the determination.

According to certain embodiments of the present disclosure, a machine-readable storage medium that includes machine-readable instructions for causing a processor to execute a method for managing a delivery of prepared medications is provided. The method includes receiving first information including a delivery deadline for a first medication, and receiving second information including a preparation status of a second medication. The method also includes comparing the first information that includes the delivery deadline for the first medication with the second information that includes the preparation status of the second medication to determine whether the first medication should be indicated for delivery prior to completing preparation of the second medication, and providing a notification indicating when to deliver the first medication based on the determination.

DETAILED DESCRIPTION

The disclosed system determines, upon a delivery person identifying (e.g., by scanning) a medication, such as an infusion solution, to be delivered, whether there are any other prepared or almost prepared medications that need to be delivered to the area of the hospital to which the delivery person is delivering the identified medication. If another medication is available or almost prepared for delivery, and it would be preferable to deliver the other medication during the same delivery as the identified medication, such as based on an urgency of the other medication or an expiration or delivery time of either medication, then a notification is provided to the delivery person to wait for the other medication to arrive for the appropriate bin prior to leaving to deliver the identified medication. The notification can be provided as an alert on a display of a device at or near the bin-sorting area, and/or may be sent to a device of the delivery person, such as the delivery person's mobile device. If another medication is available or almost prepared for delivery, but it is not preferable to deliver the other medication during the same delivery as the identified medication, then either no notification is provided to the delivery person, or a notification is provided to the delivery person to proceed with delivering the identified medication.

In this manner, the disclosed system provides the delivery person with insight into the medication preparation process by determining whether the delivery person should request (for delivery to the appropriate bin) a prepared medication that is sitting in the bin-sorting area from a sorting person, or whether the delivery person should wait for an medication to finish being prepared. The disclosed system may determine how urgently the medications identified (e.g., scanned) for delivery need to be delivered by the delivery person, and how long the delivery person will need to wait to obtain any other medication for which the preparation is almost complete. The disclosed system may notify (e.g., by a visible or audible alert, such as a text message or notification window) the delivery person of an medication that is almost prepared if the system determines that the delivery person has sufficient time to wait for the preparation of the medication to complete, e.g., based on an estimated amount of time required to complete the preparation of the medication, the times that the identified medications need to be delivered by, and an estimated amount of time required to deliver the identified medications.

FIG. 1illustrates an example architecture100for managing a delivery of prepared medications according to certain aspects of the present disclosure. For ease and clarity of illustration only, without any intent to limit the scope of the present disclosure any way, it is assumed that the prepared medication provided as an example forFIG. 1is an anesthetics IV solution.

The architecture100includes a pharmacy1having a medication storage area10, a fill and/or preparation (fill/prep) area20, and a delivery pickup area30(e.g., bin-sorting area). The medication storage area10includes a plurality of medications and supplies including an anesthetic drug (e.g., bupivicanine or chloroprocaine) and an appropriate fluid for the anesthetic drug. The anesthetic drug and the fluid are taken from the medication storage area10to the prep/fill area20where they are mixed together to produce the anesthetics IV solution. A patient/medication ID device72, such as a barcode label or an radio frequency identification (RFID) tag, is provided on (e.g., affixed to) a package70(e.g., IV bag) containing the IV solution at the prep/fill area20. The patient/medication ID device72includes patient/medication ID information indicative of the medication and the patient to whom the medication is prescribed. The package70is then taken by a technician at the pharmacy1to the delivery pickup area30. The technician determines an appropriate bin or delivery cart90into which to place the package70, and then loads the package70onto the appropriate delivery cart90for delivery to a scheduled delivery/drop location60(e.g. a patient room) by a delivery person2.

In the illustrated embodiment, the prep/fill area20has a barcode reader24provided therein that the technician at the pharmacy1can use to read the patient/medication ID device72(a barcode label in the illustrated example) before the package70is taken to the delivery pickup area30. The delivery pickup area30has a barcode reader34connected to a client110provided therein that the technician at the pharmacy1can use to read the patient/medication ID device72once the package70is taken to the delivery pickup area30. The delivery cart90may also be provided with a location barcode label reader. The delivery person2can use the barcode reader34to scan the package70to indicate the delivery person2will begin delivery of the package70.

The pharmacy1includes a server130(e.g., pharmacy server) that includes a processor40. The server130can be any device having an appropriate processor, memory, and communications capability for receiving, processing, and sending information associated with a medication database45. The processor40is coupled to the medication database45that is configured to store a variety of information including order status information and delivery progress information to be discussed below. The processor40is configured to receive an order for the medication from a doctor3, and to determine whether to notify the delivery person2to begin delivery of the package70or wait for preparation of another package to be completed (e.g., based on the order) prior to delivery of the package70. For example, a notification can be sent to a client110for display on an output device114at or near the delivery pickup area30instructing the delivery person2to hold delivery of the package70until the other package is prepared, and optionally confirm receipt of the notification using an input device116of the client110. The client110can be, for example, a computer system associated with the delivery pickup area30such as a desktop computer or mobile computer. The client110can also be, for example, a tablet computer, mobile device (e.g., a smartphone or PDA), or any other device having appropriate processor, memory, and communications capabilities. The mobile device may, for example, be associated with the delivery person2.

Also depicted inFIG. 1is an intermediate stop location50(e.g., a first patient room), located between the pharmacy1and the delivery location50. The delivery cart90may make a temporary stop at the intermediate stop location50, e.g., for delivering another package containing a medication for the patient in the first patient room.

The delivery location60and/or the intermediate stop location50can include, for example, patient rooms having an infusion device for providing an IV infusion from a package to a patient. In the illustrated example, the intermediate stop location50and the delivery location60are provided with location barcode label52and location barcode label62, respectively. Each of the location barcode labels52,62includes a unique location ID information indicative of the respective location50,60where the corresponding barcode label is provided. As described above, the package70(e.g., IV bag) containing the medication (e.g., IV solution) is provided with a patient/medication identification (ID) device72. In the illustrated example, the patient/medication ID device72is a barcode label that includes patient/medication information indicative of the patient (e.g., “Jane Smith”) and the medication (e.g., “bupivicanine IV solution”). The patient/medication information may also contain other drug or patient related information such as the patient's medical conditions (e.g., allergies), name of the drug (e.g., bupivicanine), the drug dosage, the drug concentration, the drug administration schedules, and the drug administration rate.

Also depicted in the architecture100ofFIG. 1is a reader device84that is hand carried by the delivery person2and/or attached to the delivery cart90and is configured to read the patient/medication information from the patient/medication ID device72provided on the package70. In the illustrated example, the reader device84is a barcode scanner. In those embodiments in which the barcode scanner84is hand carried by the delivery person2, the scanner84is also configured to read the location ID information from the location barcode labels52,62,92.

In the embodiments described above, the location ID devices52,62,92and/or the patient/medication ID device72are passive ID devices, meaning that certain action (e.g., scanning) has to be taken by the participant (e.g., a pharmacy technician or the delivery person2) to retrieve information therefrom. In other embodiments, the ID devices can be active ID devices, meaning that the information retrieval from the ID devices occur automatically without an action taken by the participant. In some embodiments, the active ID devices can actively transmit signals containing the relevant information to the reader device72through a wireless link. The wireless link can use a variety of technologies including Bluetooth, ZigBee, wireless USB, and proprietary systems. In other embodiments, the active ID devices do not themselves transmit signals, but respond to query signals generated by a reader device (e.g., by altering impedance of an RF circuit therein) as the reader device passes by the ID devices in close proximity.

In the illustrated example, each time the barcode scanner84scans an ID device (e.g., patient/medication ID device or location ID device), the information read thereby is wirelessly transmitted to a wireless bridge50that receives the information. The bridge50is in data communication with the processor40via a hospital network150. The network150can include, for example, any one or more of a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), the Internet, and the like. Further, the network150can include, but is not limited to, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star-bus network, tree or hierarchical network, and the like.

The processor40is configured to receive medication/patient ID information and/or location ID information read by the barcode scanner84, generate delivery progress information therefrom, and store the delivery progress information in the medication database45. The medication database45can include information such as, but not limited to: the patient's name or ID; the medication name or ID, the scheduled delivery location60, the scheduled delivery time, an expiration date or time for a prepared medication, an urgency of delivery of the prepared medication, one or more read locations where the medication/patient ID information and/or the location ID information was read by the barcode scanner84, time when the information was read, and the name or ID of the delivery person2.

The architecture100further comprises tracking devices120,152that allow a care provider4(e.g., a nurse assigned the task of administering the patient-specific medication to the patient) to monitor the progress of the delivery of the medication. Each of the tracking devices120,152is configured to receive a tracking request by the care provider4, access the medication database45, either directly or via the processor40, retrieve the delivery progress information stored in the database45, and indicate a delivery progress of the medication to the care provider4based on the delivery progress information. In the illustrated example, the tracking device120is an automated dispensing machine having a processor (not shown), a display121, and a keyboard123; and the tracking device152is a mobile communication device (e.g. a cell phone, personal digital assistant (PDA), or pager) having a processor (not shown), a display151, and a keyboard153. The delivery progress information can inform the care provider4of a last-known read location and time of the last reading. Based on such information, the care provider4can decide, e.g., whether to wait for the delivery at the delivery location60, go to the delivery location later at an expected delivery time, or go to the last-known location to retrieve the medication from the cart90.

FIG. 2is a block diagram200illustrating an example server130and client110in the architecture100ofFIG. 1according to certain aspects of the disclosure. The client110and the server130are connected over the network150via respective communications modules218and238. The communications modules218and238are configured to interface with the network150to send and receive information, such as data, requests, responses, and commands to other devices on the network150. The communications modules218and238can be, for example, modems or Ethernet cards.

The server130includes a processor40, a communications module238, and a memory232that includes the medication database45. The processor40of the server130is configured to execute instructions, such as instructions physically coded into the processor40, instructions received from software in memory240, or a combination of both. For example, the processor40of the server130executes instructions to receive first information including a delivery deadline for a first medication (e.g., package70) and receive second information including a preparation status of a second medication. For instance, when the delivery person2uses the barcode reader34of the client110to scan the package70at the delivery pickup area30, the processor212of the client110sends information identifying the package70via a communications module218over the network150to the server130. The processor40of the server130may then query the medication database45to determine a delivery deadline for the first medication and a delivery location for the first medication.

The processor40may also query the medication database45to receive information indicating the preparation status of a second medication. The preparation status of the second medication can include, for example, a status indicating that the second medication is ready but not yet sorted into a bin in the delivery pickup area30, a current location of the second medication, an indication that preparation of the second medication is almost complete, or an estimated amount of time to finish preparation of the second medication. The received information can also include a delivery location for the second medication.

The processor40of the server130compares the first information including the delivery deadline for the first medication with the second information including the preparation status of the second medication to determine whether the first medication should be indicated for delivery prior to completing preparation of the second medication. The completed preparation of the second medication includes, in certain aspects, delivery of the second medication to the delivery pickup area30. The determination can be based on various factors including, for instance, a degree of urgency for delivery of the first medication or the second medication, the delivery deadline for the first medication, the preparation status of the second medication, an estimated amount of time remaining for the completing preparation of the second medication, the intended delivery location of the first medication or the second medication, or an estimated amount of time required to deliver either the first medication or the second medication.

The processor40provides a notification (e.g., to the client110) indicating when to deliver the first medication based on the determination. The notification can be provided, for example, as a computer generated alert for display on a screen, or as a text message. The notification can, for example, indicate that the delivery person2should wait for the preparation of the second medication to be completed prior to delivering the first medication to the delivery/drop location60. This may be the case where, for example, the second medication is indicated as being needed urgently and requiring delivery within a short time period and the first medication is not indicated as being needed urgently. As another example, the notification can indicate that the delivery person2should wait for the preparation of the second medication to be completed prior to delivering the first medication to the delivery/drop location60because the delivery location for the first medication, delivery/drop location60, is at or near the delivery location for the second medication, intermediate stop location50.

Alternatively, the notification provided by the processor40of the server130can indicate that the delivery person2should not wait for the preparation of the second medication to be completed prior to delivering the first medication to the delivery/drop location60, but instead proceed with delivering the first medication to the delivery/drop location60. This may be the case where, for example, the estimated time to prepare the second medication would exceed the delivery deadline of the first medication.

The notification is provided by the processor40to the client110. A notification application222in the memory220of the client110may receive the notification and, for example, provide an audible or visible alert using the output device114. For example, the client110can be a mobile device of the delivery person2, and the notification can be a text message sent to the mobile device for display. As another example, the client110can be a computer located at the delivery pickup area30and the notification can be a visual alert displayed on the output device114of the computer. When the preparation status of the second medication indicates the second medication has been prepared but is not yet sorted for the appropriate delivery bin at the delivery pickup area30, the visual alert can include an interface for the delivery person2to request that the prepared second medication be delivered (e.g., by a pharmacy technician) to the appropriate delivery bin at the delivery pickup area30. The delivery person2may use the input device116of the client110to confirm the request to deliver the prepared second medication to the delivery pickup area30. The visual alert can also identify a degree of urgency for delivery of either the first medication or the second medication.

FIG. 3illustrates an example process300for managing a delivery of prepared medications using the server130ofFIG. 2. WhileFIG. 3is described with reference toFIG. 2, it should be noted that the process steps ofFIG. 3may be performed by other systems.

The process300begins by proceeding from beginning step301when a first medication, such as the package70, is identified (e.g., scanned by a barcode reader34of the client110) at a delivery pickup area30, such as by a delivery person2, to step302when the server130(e.g., at the pharmacy1) receives first information including a delivery deadline for the first medication located at the delivery pickup area30. Next, in step303, the server130receives second information (e.g., from the medication database45in memory232) including a preparation status of a second medication to be delivered to the delivery pickup area30, such as a current location of the second medication or an estimated amount of time to finish preparation of the second medication. In step304, the first information including the delivery deadline for the first medication is compared with the second information including the preparation status of the second medication to determine whether the first medication should be indicated for delivery prior to completing preparation of the second medication. The determination may be based on any of, for example, a degree of urgency for delivery of either or both of the first medication and the second medication, the delivery deadline of the first medication, an estimated amount of time remaining for the completing preparation of the second medication, and an estimated amount of time required to deliver at least one of the first medication or the second medication.

If the comparison of step304does not indicate proceeding with delivery of the first medication, then the process300proceeds to step306in which a notification based on the determination is provided (e.g., to the client110) indicating to wait for the preparation of the second medication to be completed prior to delivering the first medication. If, however, the comparison of step304indicates proceeding with delivery of the first medication, then the process300proceeds to step307in which a notification based on the determination is provided (e.g., to the client110) indicating to proceed with delivery of the first medication. The process300then ends in step308.

FIG. 3sets forth an example process300for managing a delivery of prepared medications using the server130ofFIG. 2. Examples will now be described using the example process300ofFIG. 3and various medications for delivery at different stages in the preparation process.

In one example where a delivery person2is instructed to wait for preparation of a second medication to be completed, the process300begins by proceeding from beginning step301when the delivery person2scans a first medication, Vancomycin, using a barcode reader34of the client110, which is a computer terminal, at the delivery pickup area30. Next, in step302, the server130at the pharmacy1receives first information identifying the scanned Vancomycin and a delivery deadline for the scanned Vancomycin. Next, in step303, the server130receives second information from the medication database45in memory232that includes a preparation status of two other medications, Cefazolin (1 gm/NS 50 ml) and Cefazolin (2 gm/NS 50 ml), that are intended to be delivered to the delivery pickup area30. The preparation status indicates that the two other medications are identified as high priority (e.g., photostat or “stat”), are currently being prepared in the fill/prep area20, and based on how much of the preparation has been completed, an estimated amount of time to finish preparation of the other medications.

In step304, the delivery deadline for the scanned Vancomycin is compared with the priority of the other medications, their location, their delivery deadlines, their delivery location, an estimated amount of time required to deliver at least one of the first medication or the second medication, and an amount of time estimated for preparation of the other medications to be completed, to determine whether the delivery person2should wait for preparation of Cefazolin (1 gm/NS 50 ml) and Cefazolin (2 gm/NS 50 ml) to be completed prior to leaving to deliver the Vancomycin at the delivery/drop location60. The comparison of step304indicates in step305to wait for the preparation of Cefazolin (1 gm/NS 50 ml) and Cefazolin (2 gm/NS 50 ml) to be completed and delivered to the delivery pickup area30because of their high priority, their nearness to completion, their close delivery deadlines, and the proximity of their delivery location at intermediate stop location50to the delivery/drop location60for the scanned Vancomycin.

In step306, the server130sends a notification to the computer terminal110for display to the delivery person2as provided in the example illustration400ofFIG. 4A. The example illustration is of the output device114, a display screen, of the computer terminal110. The display includes a user interface identifying a current time402, and a list of 50 unchecked orders406that may be sorted by, for example, priority, due time, location, or alphabetically and may be searched using a search interface404. Five orders408,410,412,414, and416are listed and additional orders may be viewed by scrolling the interface below the five listed orders408,410,412,414, and416. For each order, a due time, patient location, medication information, preparation status, and level of priority may be indicated. For example, the first order408listed identifies the medication as Cefazolin (1 gm/NS 5 ml), a high priority “stat” medication whose preparation status is 100% (i.e., completely prepared) and due by 8:00 AM to patient location 5E-12.

The user interface also includes a messages area418that both identifies420the medication scanned by the delivery person2, namely the third listed order412of Vancomycin (1 gm/NS 50 ml), and provides the notification422(of step306) for the delivery person2to read. The notification422indicates to the delivery person2to request, using a “request” button424, that the first listed order408, Cefazolin (1 gm/NS 50 ml), be sorted into the appropriate bin in the delivery pickup area30, prior to proceeding with delivery of the scanned Vancomycin. The notification422also indicates to the delivery person2to wait for completion of the second listed order410, Cefazolin (2 gm/NS 50 ml). The process300then ends in step308.

In another example where a delivery person2is instructed to proceed with delivery of a first medication prior to completion of preparation of a second medication, the process300begins by proceeding from beginning step301when the delivery person2scans two medications, Vancomycin and Norepinephrine, using a barcode reader34of the client110, which is a handheld display and scanner (e.g., such as reader device84), at the delivery pickup area30. Next, in step302, the server130at the pharmacy1receives first information identifying the scanned Vancomycin and Norepinephrine and a delivery deadline for the scanned Vancomycin and Norepinephrine. Next, in step303, the server130receives second information from the medication database45in memory232that includes a preparation status of two other medications, Cefazolin (1 gm/NS 50 ml) and Cefazolin (2 gm/NS 50 ml), that are intended to be delivered to the delivery pickup area30. The preparation status indicates that the two other medications are identified as high priority, are currently being prepared in the fill/prep area20, and based on how much of the preparation has been completed, an estimated amount of time to finish preparation of the other medications.

In step304, the delivery deadlines for the scanned Vancomycin and Norepinephrine are compared with the priority of the other medications, their location, their delivery deadlines, their delivery location, an estimated amount of time required to deliver at least one of the first medication or the second medication, and an amount of time estimated for preparation of the other medications to be completed, to determine whether the delivery person2should wait for preparation of Cefazolin (1 gm/NS 50 ml) and Cefazolin (2 gm/NS 50 ml) to be completed prior to leaving to deliver the Vancomycin and Norepinephrine at the delivery/drop location60. The comparison of step304indicates in step305to proceed with delivery of the Vancomycin and Norepinephrine because, for example, preparation of the Cefazolin (1 gm/NS 50 ml) and Cefazolin (2 gm/NS 50 ml) is only 10% completed and their deadline for delivery is not near.

In step306, the server130sends a notification to the handheld device110for display to the delivery person2as provided in the example illustration450ofFIG. 48. The example illustration is of the output device114, a display screen, of the handheld device110. The display includes a user interface identifying a current time452, and a list of 50 unchecked orders456. Five orders458,460,462,464, and466are listed and additional orders may be viewed by scrolling the interface below the five listed orders458,460,462,464, and466. For each order, a due time, patient location, medication information, preparation status, and level of priority may be indicated. For example, the first order458listed identifies the medication as Cefazolin (1 gm/NS 5 ml), a high priority “stat” medication whose preparation status is 10% complete and due by 8:00 AM to patient location 5E-12.

The user interface also includes a messages area468that both identifies470the medications scanned by the delivery person2, and provides the notification472(of step306) for the delivery person2to read. The notification472indicates to the delivery person2to proceed with delivery of the scanned Vancomycin and Norepinephrine. The process300then ends in step308.

FIG. 5is a block diagram illustrating an example computer system500with which the client110and server130ofFIG. 2can be implemented. In certain aspects, the computer system500may be implemented using hardware or a combination of software and hardware, either in a dedicated server, or integrated into another entity, or distributed across multiple entities.

Computer system500(e.g., client110and server130) includes a bus508or other communication mechanism for communicating information, and a processor502(e.g., processor212and40) coupled with bus508for processing information. By way of example, the computer system500may be implemented with one or more processors502. Processor502may be a general-purpose microprocessor, a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other manipulations of information.

Computer system500can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them stored in an included memory504(e.g., memory220and232), such as a Random Access Memory (RAM), a flash memory, a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable PROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device, coupled to bus508for storing information and instructions to be executed by processor502. The processor502and the memory504can be supplemented by, or incorporated in, special purpose logic circuitry.

Computer system500further includes a data storage device506such as a magnetic disk or optical disk, coupled to bus508for storing information and instructions. Computer system500may be coupled via input/output module510to various devices (e.g., barcode reader34). The input/output module510can be any input/output module. Example input/output modules510include data ports such as USB ports. The input/output module510is configured to connect to a communications module512. Example communications modules512(e.g., communications module218and238) include networking interface cards, such as Ethernet cards and modems. In certain aspects, the input/output module510is configured to connect to a plurality of devices, such as an input device514(e.g., input device116) and/or an output device516(e.g., output device114). Example input devices514include a keyboard and a pointing device, e.g., a mouse or a trackball, by which a user can provide input to the computer system500. Other kinds of input devices514can be used to provide for interaction with a user as well, such as a tactile input device, visual input device, audio input device, or brain-computer interface device. For example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, tactile, or brain wave input. Example output devices516include display devices, such as a LED (light emitting diode), CRT (cathode ray tube), or LCD (liquid crystal display) screen, for displaying information to the user.

According to one aspect of the present disclosure, the client110and server130can be implemented using a computer system500in response to processor502executing one or more sequences of one or more instructions contained in memory504. Such instructions may be read into memory504from another machine-readable medium, such as data storage device506. Execution of the sequences of instructions contained in main memory504causes processor502to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in memory504. In alternative aspects, hard-wired circuitry may be used in place of or in combination with software instructions to implement various aspects of the present disclosure. Thus, aspects of the present disclosure are not limited to any specific combination of hardware circuitry and software.

These and other implementations are within the scope of the following claims.