Source: http://www.google.es/patents/US9741001
Timestamp: 2018-01-19 12:10:47
Document Index: 613105820

Matched Legal Cases: ['Application No. 2512991', 'Application No. 2551903', 'Application No. 201480015147', 'Application No. 12756903', 'Application No. 14772937', 'Application No. 14779139', 'Application No. 14775918', 'Application No. 14779655', 'Application No. 14780320', 'Application No. 14801713', 'Application No. 14801726']

Patente US9741001 - Predictive medication safety - Google Patentes
Methods for facilitating safe use of a medical item are provided. In one aspect, a method includes receiving a first identifier for a medical entity located in an institution. The medical entity includes at least one of a patient, medical device, medical location, or medical item. The method also includes...http://www.google.es/patents/US9741001?utm_source=gb-gplus-sharePatente US9741001 - Predictive medication safety
Número de publicación US9741001 B2
Número de solicitud US 13/802,683
También publicado como US20130197931
Número de publicación 13802683, 802683, US 9741001 B2, US 9741001B2, US-B2-9741001, US9741001 B2, US9741001B2
Inventores Vikas Gupta, Scott Loebig, Federico Garibaldi, Timothy W. Vanderveen
Citas de patentes (552), Otras citas (45), Clasificaciones (9), Eventos legales (1)
US 9741001 B2
Methods for facilitating safe use of a medical item are provided. In one aspect, a method includes receiving a first identifier for a medical entity located in an institution. The medical entity includes at least one of a patient, medical device, medical location, or medical item. The method also includes receiving a second identifier for a first course of action associated with the medical entity. The method further includes generating, based on a history of the medical entity and the first course of action associated with the medical entity, a second course of action for the medical entity, and providing a notification to a device indicating the second course of action. Systems and machine-readable media are also provided.
receiving, by a monitoring system, a first identifier for a medication, a second identifier for a first course of action for administering the medication with an infusion pump, and a third identifier for a caregiver;
obtaining, by a processor of the monitoring system, medication orders from a medical entity database;
reviewing, by the processor, the medication orders based on the received identifiers;
determining, by the processor, the caregiver's level of waste for the medication based on a history of the medication being dispensed but never used by the caregiver;
generating, by the processor, a second course of action based on the caregiver's level of waste for the medication order to be dispensed;
providing, by the processor via a communications module of the monitoring system, instructions to the infusion pump prior to implementation of the first course of action, wherein the instructions comprise instructions for the infusion pump to take the second course of action in place of the first course of action; and
performing, by the infusion pump responsive to the instructions, the second course of action by (a) restricting operation of the infusion pump to perform the first course of action until appropriate authorization for performing the first course of action is received by the infusion pump from the caregiver, and (b) providing, with the infusion pump to the caregiver, a notification including a purpose for taking the second course of action based on the caregiver's history of wasting the medication.
2. The method of claim 1, wherein the at least one of the first identifier, the second identifier, or the history of the medical entity is received over a network from a healthcare facility information system in a native message format of the healthcare facility information system and converted into an internal messaging format configured for use with the monitoring system.
3. The method of claim 1, wherein the first course of action comprises a plurality of parameters for administration of the medication by the infusion pump.
4. The method of claim 1, wherein the purpose comprises a level of waste of the medication by the caregiver.
5. A non-transitory machine-readable storage medium comprising machine-readable instructions for causing a processor of a monitoring system in communication with an infusion pump to execute a method, the method comprising:
receiving, at a monitoring system, a first identifier for a medication, a second identifier for a first course of action for administering the medication with an infusion pump, and a third identifier for a caregiver;
providing, by the processor via a communications module of the monitoring system, instructions to the infusion pump prior to implementation of the first course of action, wherein the instructions comprise instructions for the infusion pump to take the second course of action in place of the first course of action,
wherein the second course of action comprises (a) restricting operation of the infusion pump for performance of the first course of action until appropriate authorization for performing the first course of action is received at the infusion pump by the caregiver, and (b) providing, with the infusion pump to the caregiver, a notification including a purpose for taking the second course of action based on the caregiver's history of wasting the medication.
6. The non-transitory machine-readable storage medium of claim 5, wherein the at least one of the first identifier, the second identifier, or the history of the medical entity is received over a network from a healthcare facility information system in a native message format of the healthcare facility information system and converted into an internal messaging format configured for use with the monitoring system.
7. The non-transitory machine-readable storage medium of claim 5, wherein the first course of action comprises a plurality of parameters for administration of the medication by the infusion pump.
8. The non-transitory machine-readable storage medium of claim 5, wherein the purpose comprises a level of waste of the medication by the caregiver.
The present disclosure generally relates to medical devices, and particularly to configuring medical devices to reduce error.
Medication errors, that is, errors that occur in the ordering, dispensing, and administration of medications, regardless of whether those errors cause injury or not, are a significant consideration in the delivery of healthcare in the institutional setting. Additionally, adverse drug events (ADE), which are defined as injuries involving a drug that require medical intervention and are a subset of medication errors, represent some of the most serious medication errors are responsible for a number of patient injuries and death.
Healthcare facilities continually search for ways to reduce the occurrence and severity of medication errors. Various systems and methods are commonly used to reduce the frequency of occurrence and severity of preventable adverse drug events (PADE) and other medication errors. In the administration of medication, focus is typically directed to the following five “rights” or factors: the right patient, the right drug, the right route, the right amount, and the right time. Systems and methods seeking to reduce ADEs and PADEs should take these five rights into consideration.
Delivery, verification, and control of medication in an institutional setting have traditionally been areas where errors can occur. In a typical healthcare facility, a physician enters an order for a medication for a particular patient. This order may be handled either as a simple prescription slip, or it may be entered into an automated system, such as a physician order entry (POE) system. The prescription slip or the electronic prescription from the POE system is routed to the pharmacy, where the order is filled. Typically, pharmacies check the physician order against possible allergies of the patient and for possible drug interactions in the case where two or more drugs are prescribed, and also check for contraindications. Depending on the healthcare facility, the medication may be identified and gathered within the pharmacy and placed into a transport carrier for transport to a nurse station. Once at the nurse station, the prescriptions are again checked against the medications that have been identified for delivery to ensure that no errors have occurred. Each of these steps or workflows is typically captured as event data in a hospital information system. The event data is not, however, used to adjust future workflows involving medical items. For example, a medical item from a dispensing cabinet may have an associated warning related to how commonly the medical item is wasted. This information is not, however, used to adjust future workflows from reducing waste of the medical item.
According to one embodiment of the present disclosure, a method for facilitating safe use of a medical item is provided. The method includes receiving a first identifier for a medical entity located in an institution. The medical entity includes at least one of a patient, medical device, medical location, or medical item. The method also includes receiving a second identifier for a first course of action associated with the medical entity. The method further includes generating, based on a history of the medical entity and the first course of action associated with the medical entity, a second course of action for the medical entity, and providing a notification to a device indicating the second course of action.
According to another embodiment of the present disclosure, a monitoring system for facilitating safe use of a medical item is provided. The system includes a memory that includes a history of a medical entity located in an institution. The medical entity includes at least one of a patient, medical device, medical location, or medical item. The system also includes a processor. The processor is configured to receive a first identifier for the medical entity and a second identifier for a first course of action associated with the medical entity, and generate, based on a history of the medical entity and the first course of action associated with the medical entity, a second course of action for the medical entity. The processor is also configured to provide a notification to a device indicating the second course of action.
According to a further embodiment of the present disclosure, a machine-readable storage medium that includes machine-readable instructions for causing a processor to execute a method for facilitating safe use of a medical item is provided. The method includes receiving a first identifier for a medical entity located in an institution. The medical entity includes at least one of a patient, medical device, medical location, or medical item. The method also includes receiving a second identifier for a first course of action associated with the medical entity. The method further includes generating, based on a history of the medical entity and the first course of action associated with the medical entity, a second course of action for the medical entity, and providing a notification to a device indicating the second course of action.
According to yet a further embodiment of the present disclosure, a method for instructing a caregiver is provided. The method includes receiving a first identity of a caregiver at an institution and a proposed course of action for a medical entity, and generating, based on a history of the caregiver within the institution, a modified course of action. The method also includes providing a notification of the modified course of action to the caregiver.
FIG. 1 illustrates a block diagram of a system for facilitating safe use of a medical item.
FIG. 2 is a block diagram illustrating the monitoring system and server from the architecture of FIG. 1 according to certain aspects of the disclosure.
FIG. 3 illustrates an example process for facilitating safe use of a medical item using the example monitoring system of FIG. 2.
FIG. 4 is an example illustration of a medical item, namely a medical device, associated with the example process of FIG. 3.
FIG. 5 is a block diagram illustrating an example computer system with which the clients and server of FIG. 2 can be implemented.
Each of the steps of a workflow related to a medical entity, such as a patient, medical device, medical location, or medical item, can be captured as event data in a hospital information system. The event data can be, for example, historical data related to the medical entity. The disclosed system leverages the event data for the medical entity to determine, for example, whether to suggest an alternative workflow for the medical entity. For instance, event information for a medication from a dispensing cabinet may be evaluated by the disclosed system to determine a percentage of times the medication is wasted. The disclosed system may then send a notification to a caregiver attempting to dispense the medication regarding the potential wastage, and may further restrict the caregiver from dispensing the medication until additional verification steps are taken. Similar notifications and workflow suggestions can be suggested for improving a health level of a patient, expediting dispensing of a medical item, indicating an incidence rate of illness in a medical location, or a recommending an increase of an order being placed for medical items based on a recent change in demand for the medical item. The notifications and other workflow suggestions can be specific to the caregiver specific when, for example, an abnormal utilization pattern for a medical item is specific to the caregiver.
Several examples will now be presented regarding how the disclosed system can assist a caregiver in facilitating a safe interaction with a medical entity. As one example, a notification can be sent if a certain medication is continuously used to address a certain pathology when it is shown that the patient length of stay is not improved over time using that medication. As another example, a specific nurse can be alerted to check on order information if the nurse is historically hitting safe or therapeutic limits on doses too often. As yet another example, a specific caregiver can be informed that the caregiver's level of drug waste is high on average. As a further example, a pharmacist can be informed that a certain medication may be required statim (e.g., “stat” or urgently) because the medication has historically taken a long time to be delivered to a patient.
Referring now to the drawings, FIG. 1 provides an example illustration of an integrated healthcare facility-wide information and care management system 28 in accordance with certain aspects of the present disclosure. Various subsystems of a healthcare facility's information management system are connected together by way of a facility communication system 30. The communication system 30 may 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 communication system 30 can 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. As shown in FIG. 1, the communication system 30 connects through various interfaces 32 to a healthcare facility information system 34, a pharmacy information system 36, a physician order entry system 38, a medical entity database 60, and a monitoring system 40.
The facility communication system 30 is not meant to be taken in a limited sense. Such a facility communication system 30 may encompass an entire healthcare facility or may be located only in a small area of the healthcare facility. It may also include a communication system in a healthcare facility other than a hospital and may have application to an alternate care facility, such as a patient's home. Additionally, the word caregiver is intended to be used in its broadest sense and is meant to include nurses, physicians, health care specialists, and others who provide care to patients.
The monitoring system 40 in accordance with an aspect of the present disclosure may be, for example, a server or other computer having sufficient memory 42 and processing capability to connect with the communication system 30 and determine a change in workflow for a healthcare process. The monitoring system 40 includes operational software or other instructions for carrying out various aspects of the present disclosure, as will be discussed more fully below, enabling communications with other hardware or networks, and data input and output and report generation and printing, among other functions. While the monitoring system 40 is shown as a separate piece of equipment, it will be understood that the monitoring system 40 and the associated memory 42 may also be incorporated into another element, such as the medical device 80.
The communication system 30 may comprise, for example, a wired or wireless Ethernet (IEEE 522.3) utilizing transmitters and receivers positioned throughout the healthcare facility and/or attached to various computers, clinical devices and other equipment used in the facility. In such a wireless system, the signals transmitted and received by the system could be radio frequency (RF), infrared (IR), or other means capable of carrying information in a wireless manner between devices having appropriate transmitters or receivers may be used. It will be immediately understood by those skilled in the art that such a system may be identical to the system set forth in FIG. 1, with the exception that no wires are required to interconnect the various aspects of the system.
In a typical healthcare facility, patient rooms, wards, or areas are typically situated in groups located near a nurse station 44, where the caregivers assigned to care for the patients in the particular area carry out the administrative functions of their duties. Typically, these functions include updating and monitoring the patients' charts, preparation of and administering medication orders, and monitoring and recording any other information deemed necessary by the facility for tracking. There is also usually a room located adjacent the nurse station that is dedicated to storage and/or the preparation of medications to be delivered to patients. This room may contain inventories of commonly used oral, IM, or IV medications. The room may also be used to formulate the contents of infusion bags in accordance with prescribed treatment regimens.
The nurse station 44 will typically include a terminal or computer system 46 connected either directly or through an interface 48 to the communication system 30, allowing users at the nurse station to enter and retrieve patient data or information from other systems, such as the healthcare facility information system 34, the pharmacy information system 36, the physician order entry system 38, or other systems used in the facility. It should be understood that not all users will be provided with access rights to each system. For example, physicians may be able to access the physician order entry system 38 from the nurse station system 44 to enter, edit, or track medication orders, but a caregiver may only be able to view such orders. Moreover, while the present disclosure is described with reference to the computer system 46 being located at a nurse station 44, the computer system 46 may also be a satellite system that is located anywhere in the care-giving facility where it is convenient or efficient to do so. Such a satellite computer system may be operably connected to the communication system 30 using either a wired or wireless network connection. A printer 50 may also be connected to the nurse station computer system 46 for printing reports, bar codes, labels, or other materials, and a bar code reader 52 may be provided for reading bar codes on medication labels, reports, or other items having bar coded labels provided for identification.
In a different embodiment where radio frequency identification (RFID) tags are used with medications, patients, equipment, or in other ways, the nurse station 44 may also include an interrogator or RFID reader (not shown) for use with the RFID tags.
In accordance with aspects of the present disclosure, a medical entity database 60 stores information related to medical entities, such as patients, medical devices, medical locations, and medical items. Various types of information may be stored in the memory of the medical entity database 60, including medical item history and course of action information (e.g., orders, history of use, caregivers associated with the item, etc.). Databases can also be stored in the database 60 that contain information about drug interactions and possible contraindications and/or side-effects of medications, and established guidelines for the administration of various medications. For example, the guidelines may include institutionally-established guidelines or limits on drug administration parameters, such as dosage, frequency of administration, and other delivery related information such as, for example, appropriate flow rates and infusion durations for programming infusion pumps. Additionally, the guidelines may encompass guidelines for providing drug administration appropriate to a particular patient or to treatment areas having different sets of delivery parameters for similar medications, such as medication administration directed to geriatric, pediatric, and oncology patients. Guidelines may also be included that are directed to particular therapy regimens, such as chemotherapy regimens or regimens for treating chronic infection or pain. The term database as used herein will be understood by those skilled in the art to be used as is commonly understood. That is, the term database refers to a collection of values or information organized, formatted, and stored in such a manner as to be capable of being retrieved and analyzed using an appropriate program contained in software or other form.
The medications guidelines database 60 may be stored on a device, such as a server. The healthcare facility may also or alternatively have the medical entity database 60 centrally located in the memory 42 of the monitoring system 40. The medical entity database 60 includes medication information, medical item history, and course of action information, and/or databases or libraries, including institutionally generated guidelines for the delivery of medication to a patient, as well as drug interaction information or information concerning possible drug side-effects. The medications guidelines database 60 may also have a storage capability and technology for interfacing with a computer system or network so that information may be communicated between the medications guidelines database 60 and other devices, such as computers, medication administration devices, clinical devices such as vital signs monitoring devices and the like. A general concept embodied in the medications guidelines database 60 is to provide safe medication guidelines for dispensing, administering, or otherwise providing medication a patient using, for example, a medical device 80 such as an infusion pump.
In accordance with aspects of the present disclosure, the monitoring system 40 is configured to obtain medical entity information from the medical entity database 60. The medical entity database 60 is configured to obtain device information from the medical device 80, previous medical item history and course of action information (e.g., orders, history of use, caregivers associated with the item, etc.) from physician order entry system 38, the pharmacy information system 36, and the healthcare facility information system 34. Information may be retrieved information from the medical device 80 prior to actual medication administration. Monitoring system 40 can determine, based on a history of a medical entity and a current course of action for the medical entity, whether an alternative course of action should be taken for the medical entity. If the determination indicates an alternative course of action should be taken, then the monitoring system 40 is configured to transmit a notification to a relevant caregiver or device indicating the alternative course of action. The monitoring system 40 may also restrict or otherwise inhibit the current course of action from being taken (e.g., by locking a device).
For example, physician order system 38 may indicate that a certain medication is to be provided to a patient, and the pharmacy information system 36 may indicate how often the medication has been dispensed to the patient in the past. Based on this information, the monitoring system 40 may determine that dispensing the medication to the patient is harmful according to certain medical guidelines (e.g., from medical entity database 60). The monitoring system may then prevent a medical device 80 from dispensing the medication by locking the medical device 80 and possibly requiring a manual override of the lock in order to dispense the medication to the patient.
As another example, the pharmacy information system 36 may indicate that an order for 30 doses of a medication is to be placed, and the healthcare facility information system 34 may indicate that an incidence of an illness (e.g., with reference to patient laboratory data) that is treated by the medication has increased sharply in the past 24 hours. Based on the order and incidence information, the monitoring can send a notification to the pharmacy information system 36 to increase the number of doses being ordered, and may provide a suggested amount based on the incidence information.
As yet a further example, the healthcare facility information system 34 may include a caregiver's history regarding medication and medical device usage, and the medical entity database 60 may indicate an appropriate amount of a medication the caregiver has given in the past. The monitoring system 40 may determine that the amount of the medication the caregiver has given in the past has been inadequate, and send a notification to the medical device 80 or another device of the caregiver indicating that the medication amount provided by the caregiver should be increased.
While specific examples of a monitoring system 40 are set forth herein, it will be understood that the monitoring system 40 is meant to include any device that carries out the basic concept of the disclosure. That is, a device that receives an identification of a medical entity, such as a patient, medical device, medical location, or medical item, and an identification of a course of action associated with the medical entity, and has a processor that generates, based on a history of the medical entity and the course of action associated with the medical entity, a second (e.g., alternative) course of action for the medical entity, and provides a notification to a device (e.g., device of a caregiver, medical device 80, physician order entry system 38, pharmacy information system 36, healthcare facility information system 34) indicating the second course of action.
One particular mode of operation of the present disclosure will now be described. A patient entering a healthcare facility is provided with a wrist band, necklace, ankle band, or other band, chain, or device designed to remain affixed to or embedded in the patient during the patient's entire stay in the healthcare facility (the “patient ID”). The patient ID is designed to remain affixed in a manner so that the patient can be identified even if unconscious or otherwise unresponsive. The patient ID is used to identify specific patient data, such as the patient's name and other information that the facility has determined is important, such as age, allergies, or other vital information. The patient identifying device may comprise a bar code, written information, or an electronic information storage device, such as an RF transponder (e.g., RFID tag), that contains the information, or other device affixed to the patient. In the case where the patient-specification information may also include the patient's medication administration record (MAR). This would allow for consistent documentation and also checks against drug interaction in the medical entity database 60.
Such RFID tags, barcodes, and other technologies useful in identification, may be applied to others and to other things in providing healthcare to patients. For example, physicians, nurses, and other caregivers, as well as others who have access to patients and facilities, may also have an RFID tag that can be read anywhere in the healthcare facility. The medical fluid containers may contain RFID tags having information about the contents of the container as well as the patient for whom they have been prepared, the pharmacist who prepared them, and the physician who prescribed them. The infusion pumps and other healthcare instruments and devices may have RFID tags useful for inventory control. Even though the instruments may be connected to the healthcare facility communication system 30, RFID tags can be useful for manual inventory purposes as well as for other purposes. Their low cost makes them attractive as a backup support system.
After the patient is admitted and situated in a bed within the facility, the patient is typically evaluated by a physician and a course of treatment is prescribed. The physician prescribes a course of treatment by preparing an order that may request a series of laboratory tests or the administration of a particular medication to the patient. In some cases, the physician prepares the order by filling in a form or writing the order on a slip of paper to be entered into the healthcare facility system for providing care. In other cases, the physician may enter the medication order directly into a physician order entry system 38 or may instruct a nurse or other care-giving professional to do so. In yet another case, the physician may use the Internet to forward and enter a prescription for the patient into the pharmacy system. Depending on the arrangement at the healthcare facility, the physician's order or prescription may directly reach a website for the pharmacy information system 36 or may go to a website for the healthcare facility where it may then be routed to the pharmacy information system 36. In certain aspects, the monitoring system 40 may review the prescribed course of treatment for the patient and the history of prescriptions by the physician or other physicians, and propose an alternative treatment for the patient to the physician for review.
Pharmacy information systems 36 may enable a safer physician medication order process. The pharmacy information system 36 may provide the physician with a list of available drugs from which the physician may select. The pharmacy information system 36 may contain a drug library having the list of available drugs but may also contain and present to the physician the drug names associated with recommended dosages and dose limits that have been established or adopted by the healthcare facility. In such a case where the physician need only select items from the computer screen rather than having to manually type in drug names and drug administration numbers (such as infusion rates, times, etc.) associated with administration of the medication, a more accurate medication process should result.
If the order is for administration of a particular medication regimen, the order will be transmitted to the facility's pharmacy information system 36. The pharmacy reviews the order. In certain aspects, the monitoring system 40 may, for example, review the particular medication regimen for the patient and the history of medication regimens for the patient or similar patients, and then propose an medication regiment for the patient to the pharmacist (or physician) for review.
The pharmacy prepares the medication according to the requirements of the physician. Typically, the pharmacy packages the medication in a container, and a copy of the order, or at a minimum the patient's name, the drug name, and the appropriate treatment parameters are represented on a label or other device that is affixed to the drug container. This information may be represented by a bar code, or it may be stored in a smart label, such as a label having an embedded computer, or in a passive device such as an RFID tag discussed above.
Once the order has been prepared, the order is sent to the nurse station 44 for matching with the appropriate patient. Alternatively, if the medication is for a commonly or routinely prescribed medication, the medication may be included in an inventory of medications that is stored in a secure cabinet adjacent the nurse station 44. In such a case, the nurse station 44 will receive a list of orders from the pharmacy information system 36 that may be drawn from the inventory adjacent the nurse station 44. The caregiver will enter a unique identifier at the cabinet to gain access in accordance with standard practice. The caregiver or other professional assigned the task of gathering medications will then match the orders received from the pharmacy information system 60 to the medications stored in the inventory and pull those medications that are to be delivered to specific patients. These procedures are carried out whether the medication to be delivered is an oral medication or a medication that is to be delivered intramuscularly or through an infusion. In certain aspects, the monitoring system 40 may review the medication orders to determine, for example, whether the caregiver has a particularly high level of waste for the medication order being dispensed. If such a determination is made, the monitoring system 40 may send a notification to the nurse station 44 for the caregiver to view. The notification can state, for example, the caregiver's recorded history of waste and either remind the caregiver to be careful in dispensing the medication order, or propose an alternative workflow to dispensing the medication order.
In certain circumstances, a pharmacy dispenses a vial of a medication (a “multidose vial”) that includes more than the specific dose of the medication required for a patient. one advisory that we should give the nurse is exactly how to prepare the medication. A nurse or other caregiver may then be tasked calculating an appropriate dose of the medication for the patient based on the total amount of medication included in the vial. For example, a physician may order that a 65 kg patient receive a 40 unit/kg bolus dose, and the administration of the medication should be at a rate not to exceed 400 units/minute. The vial of the medication contains 1000 units/mL. The nurse must manually calculate the total dose of the vial, namely, that the vial contains 2600 units of the medication. The nurse must then determine that this is 2.6 mL of the 1000 units/mL, and then calculate the dose injection for a minimum time of 6.5 minutes. The disclosed monitoring system 40 may advantageously provide this information to the nurse so that the nurse, such as a notification to remove 2.6 mL of the 1000 units/mL medication and administer at 0.4 Ml/min, and further provide the syringe label complete with patient, drug, dose and bar code to the nurse.
When the prescribed time for delivery of the medication or medications arrives, the medications are carried to the patient's area and administered to the patient by the caregiver. In the case of drugs to be delivered via infusion, the caregiver hangs the infusion bag and prepares the infusion line, attaches the bag to an infusion pump 80, and sets up the infusion pump to deliver the medication by programming the pump with values for various parameters that are used by the pump to control delivery of the medication to the patient. When the medication delivery parameters are entered into the pump, the pump communicates the entered parameters to the medical entity database 60. In certain aspects, the monitoring system 40 may, for example, review the medication delivery parameters and a history of previous medication delivery parameters entered into the infusion pump 80 to deliver the medication or similar medications, and determine that alternative medication delivery parameters should be used. If such a determination is made, the monitoring system 40 may send a notification to the infusion pump 80 for the caregiver to view. The notification can propose, for example, alternative medication delivery parameters and a reason for proposing the alternative medication delivery parameters. If the alternative medication delivery parameters for the infusion pump 80 are accepted, or alternatively manually overridden, the monitoring system 40 can send a signal to the infusion pump 80 to begin infusion of the medication.
FIG. 2 is a block diagram 200 illustrating an example monitoring system 40 and server 130 from the architecture of FIG. 1 according to certain aspects of the disclosure. The control system 40, a device 160 (e.g., such as medical device 80), and the server 130 are connected over the network 30 via respective communications modules 210, 156, and 138. The communications modules 210, 156, and 138 are configured to interface with the network 30 to send and receive information, such as data, requests, responses, and commands to other devices on the network. The communications modules 210, 156, and 138 can be, for example, modems or Ethernet cards and communicate over a wired or wireless connection.
The monitoring system 40 includes a processor 212, the communications module 210, and a memory 42 that includes a monitoring application 208. The monitoring application 208 includes instructions for the processor 212 to obtain, from the processor 136 of the server 130, information from the medical entity database 62 over the network 30 using respective communications modules 210 and 138 of the monitoring system 40 and the server 130. The information received from the medical entity database 62 includes identification information for a medical entity, courses of action associated with the medical entity, and a history of the medical entity. The medical entity can be, for example, a patient, medical device 80, medical location (e.g., hospital or area within a hospital, such as an Intensive Care Unit), or medical item such as a medication or medical. For example, identification information for a medical entity can be a name or unique identifier for a patient. A course of action associated with a medical entity can be providing a prescribed amount of medication to a patient. A history of a medical entity can be a listing of medications administered using a medical device 80.
The processor 212 of the monitoring system 40 is configured to execute instructions, such as instructions physically coded into the processor 212, instructions received from software in memory 42, or a combination of both. For example, the processor 212 of the monitoring system 40 executes instructions from the monitoring application 208 to receive a first identifier for a medical entity located in an institution and a second identifier for a first course of action associated with the medical entity. The first and second identifiers can be received from the medical entity database 62 over the network 30. The processor 212 of the monitoring system is also configured to generate, based on a history of the medical entity and the first course of action associated with the medical entity, a second course of action for the medical entity, and provide a notification to the device 160 indicating the second course of action. The second course of action can be, for example, an alternative to the first course of action selected in order to promote a safe or efficient interaction with the medical entity. The device 160 can be, for example, a caregiver's mobile device, a medical device 80 at or near a patient's bedside, a display at a nurse station 44, or a display of the healthcare facility information system 34, pharmacy information system 36, physician order entry system 38, or monitoring system 40. The notification can include a message indicating a purpose for indicating the second course of action. For example, a notification can be displayed using display device 214 on a caregiver's mobile device 160 indicating a prescribed amount of medication for the patient is too high based on the patient's physiological history relative to administration of the medication, and further indicate an alternative amount of medication that is appropriate to the patient based on the patient's physiological history relative to administration of the medication. The caregiver may then be asked to confirm or override the alternative amount using an input device 216 of the mobile device 160.
The first identifier, the second identifier, or the history of the medical entity can be received from an external data system (e.g., server 130) in a native message format of the external data system, and the processor 212 of the monitoring system 40 can be configured to convert the first identifier, the second identifier, or the history of the medical entity into an internal messaging format configured for use with the monitoring system 40. The processor 212 can be configured to perform the conversion according to the system and method of converting messages being sent between data systems using different communication protocols and message structures described in U.S. patent application Ser. No. 13/421,776, entitled “Scalable Communication System,” and filed on Mar. 15, 2012, the disclosure of which is hereby incorporated by reference in its entirety for all purposes. The memory 42 of the monitoring system 40 can include, for example, an interface module for communicating with the server 130. The interface module can include information on the communication protocol and data structure used by the server 130 and is configured to both receive messages from and transmit messages to the server 130.
In certain aspects where the medical entity is or otherwise includes a medical item, the history of the medical entity can include a number of times the medical item has been dispensed. For example, the history of the medical entity can indicate that the psychoactive drug alprazolam has been dispensed by a specific caregiver over ten times in the past twenty four hours. The first course of action associated with the medical item alprazolam may indicate an instruction to dispense alprazolam for a specific patient, and the second course of action can indicate an instruction to restrict dispensing of alprazolam (e.g., by locking the device 160 for dispensing alprazolam), for example, due to the specific caregiver's abnormally high rate of dispensing of alprazolam. A notification can be sent to the device 160 for dispensing alprazolam or the caregiver's mobile device 160 indicating that dispensing of alprazolam has been restricted based on the caregiver's abnormally high rate of dispensing of alprazolam. Alternatively, the alprazolam may be removed from the listing of available medications to the caregiver (e.g., “unprofiling” the medication) until a pharmacist or other authorized caregiver takes appropriate action, such as contacting the physician or repeating a lab test.
In certain other aspects where the medical entity is or otherwise includes a medical item, the processor 212 of the monitoring system 40 may be configured to receive a third identifier for a caregiver (e.g., from the medical entity database 62 over the network 30) in the institution. The history of the medical item can include a level of waste of the medical item by the caregiver. For example, the history of the medical item can indicate that it is an antihypertensive that is wasted (e.g., dispensed but never used) by the caregiver on average 22% of the times it is dispensed by the caregiver. The waste may occur due to, for example, resolution of the condition for which the medication was prescribed, patient-perceived ineffectiveness, prescription changes by the physician, and patient-perceived adverse effects. The abnormally high rate of wastage by the caregiver may be due to the caregiver being prone to not checking a patient's record before dispensing a medication. The first course of action associated with the antihypertensive medication may indicate an instruction to the caregiver to dispense a ten count of the antihypertensive medication, and the second course of action can indicate an instruction to decrease the dispensing count of the antihypertensive medication to two, or restrict dispensing altogether, for example, based on the caregivers history of wasting the antihypertensive medication. A notification can be sent to the device 160 for dispensing the antihypertensive medication or the caregiver's mobile device 160 indicating that dispensing of the antihypertensive medication has been reduced or restricted due to the caregiver's history of wasting the antihypertensive medication.
In certain further aspects where the medical entity is or otherwise includes a medical item, the history of the medical entity can include an average amount of time between dispensing of the medical item and the medical item being administered to a patient. For example, the average amount of time for dispensing a solution of adrenaline in an institution is 45 minutes, and a first course of action associated with the solution of adrenaline is to dispense the solution of adrenaline according to normal procedures. The second course of action associated with the dispensing solution can be to dispense the solution of adrenaline statim (e.g., according to expedited procedures) because adrenaline is commonly needed urgently to administer to a patient and an average wait time of 45 minutes for the solution is not acceptable. A notification can be sent to the pharmacy information system 36, nurse station 44, or other device 160 indicating the expedited need for the adrenaline solution.
In certain aspects where the medical entity is or otherwise includes a medical location, such as a ward in a hospital, the hospital itself, or a campus of multiple hospitals, the history of the medical location can include, for example, a rate of improvement of patients associated with the medical location. For example, the history of the medical location such as a pediatric intensive care unit (PICU) may indicate a sharp decline in immunity levels of patients in the PICU. The first course of action associated with the medical location may indicate an instruction to order a small amount of a macrolide antibiotic, azithromycin, to treat immunity deficiency in the PICU, and the second course of action can indicate an instruction to recommend an increase in the amount of azithromycin being ordered for the PICU, for example, due to the sharp decline in patient immunity levels. A notification can be sent to the pharmacy information system 36, nurse station 44, or other device 160 indicating the recommendation for the increased need for azithromycin.
In certain other aspects where the medical entity is or otherwise includes a medical location, the history of the medical entity can include an incidence rate of illness associated with the medical location. For example, the history of a specific hospital may indicate that the incidence of the influenza virus has dramatically increased over the past seven days from an average of three new influenza cases per day to over twenty influenza cases per day. The first course of action associated with the specific hospital may indicate an instruction to order a small amount of an antiviral drug, oseltamivir, to treat influenza, and the second course of action can indicate an instruction to increase the amount of oseltamivir being ordered for the specific hospital, for example, due to the sharp increase in daily incidence of influenza. A notification can be sent to the pharmacy information system 36, nurse station 44, or other device 160 indicating an increased need for oseltamivir.
In certain aspects, the processor 212 of the monitoring system 40 is configured to receive a first identity of a caregiver at an institution and a proposed course of action for a medical entity, generate, based on a history of the caregiver within the institution, a modified course of action, and provide a notification of the modified course of action to the caregiver. For example, the history of the caregiver can indicate a level of waste of a medical item by the caregiver, and the modified course of action can include an indication of an action to decrease a level of waste of the medical item by the caregiver. The indicated action can be, for example, an instruction to reduce the number of the medical items being dispensed. As another example, the history of the caregiver can include an identification of one or many error made by the caregiver with a medical item or patient, and the modified course of action can include an indication of an action to decrease a likelihood of the error with the medical item, the patient, another medical item, or another patient. The indicated action can be, for instance, an instruction to not perform a certain action with a patient or medical item, or a suggestion for additional training.
FIG. 3 illustrates an example process 300 for facilitating safe use of a medical item using the example monitoring system 40 of FIG. 2. While FIG. 3 is described with reference to FIG. 2, it should be noted that the process steps of FIG. 3 may be performed by other systems. The process 300 begins by proceeding from beginning step 301 when a request is initiated to perform an action associated with a medical entity, to step 302 when a first identifier for a medical entity located in an institution and a second identifier for a first course of action associated with the medical entity are received. The medical entity can include at least one of a patient, medical device, medical location, or medical item. Next, in step 303, a second course of action for the medical entity is generated based on a history of the medical entity and the first course of action associated with the medical entity. Finally, in step 304, a notification is provided to a device 160 indicating the second course of action. The process 300 then ends in step 305.
FIG. 3 set forth an example process 300 for facilitating safe use of a medical item using the example monitoring system 40 of FIG. 2. An example will now be described using the example process 300 of FIG. 3, a medical entity that is a medication, a device 160 that is an infusion pump (e.g., infusion pump 80), and an error-prone caregiver.
The process 300 begins by proceeding from beginning step 301 when the caregiver enters parameters into the infusion pump 160 to administer a medication, to step 302 when a monitoring system 40 receives a first identifier identifying the medication and a second identifier identifying a first course of action, namely, certain parameters entered by the caregiver into the infusion pump 160 in order to administer the medication. Next, in step 303, a second course of action, namely, a requirement to confirm the medication parameters before administration, is generated based on a history of the medication and the entered parameters for administering the medication. Specifically, the history of the medication indicates that the caregiver has previously administered the medication incorrectly 20% of the time. Finally, as provided in the example illustration of FIG. 4, in step 304, a notification 482 requiring confirmation from the caregiver is provided for display on the infusion pump 160. The process 300 then ends in step 305.
FIG. 5 is a block diagram illustrating an example computer system 500 with which the monitoring system 40, the device 160, and the server 130 of FIG. 2 can be implemented. In certain aspects, the computer system 500 may 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 system 500 (e.g., monitoring system 40, the device 160, and the server 130) includes a bus 508 or other communication mechanism for communicating information, and a processor 502 (e.g., processor 212, 154, and 136) coupled with bus 508 for processing information. By way of example, the computer system 500 may be implemented with one or more processors 502. Processor 502 may 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 system 500 can 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 memory 504 (e.g., memory 42, 152, or 132), 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 bus 508 for storing information and instructions to be executed by processor 502. The processor 502 and the memory 504 can be supplemented by, or incorporated in, special purpose logic circuitry.
Computer system 500 further includes a data storage device 506 such as a magnetic disk or optical disk, coupled to bus 508 for storing information and instructions. Computer system 500 may be coupled via input/output module 510 to various devices. The input/output module 510 can be any input/output module. Example input/output modules 510 include data ports such as USB ports. The input/output module 510 is configured to connect to a communications module 512. Example communications modules 512 (e.g., communications module 210, 156, and 138) include networking interface cards, such as Ethernet cards and modems. In certain aspects, the input/output module 510 is configured to connect to a plurality of devices, such as an input device 514 (e.g., input device 216) and/or an output device 516 (e.g., display device 214). Example input devices 514 include a keyboard and a pointing device, e.g., a mouse or a trackball, by which a user can provide input to the computer system 500. Other kinds of input devices 514 can 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 devices 516 include 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 monitoring system 40, the device 160, and the server 130 can be implemented using a computer system 500 in response to processor 502 executing one or more sequences of one or more instructions contained in memory 504. Such instructions may be read into memory 504 from another machine-readable medium, such as data storage device 506. Execution of the sequences of instructions contained in main memory 504 causes processor 502 to 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 memory 504. 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.
Various aspects of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. The communication network (e.g., network 30) can 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 communication network can include, but is not limited to, for example, 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, or the like. The communications modules can be, for example, modems or Ethernet cards.
US2141006 24 Dic 1936 20 Dic 1938 Whitehall Patents Corp End tape coupling for separable fasteners
US3724455 2 Jun 1970 3 Abr 1973 P Unger Cardiac warning device
US3831006 19 Ene 1973 20 Ago 1974 Honeywell Inc Patient-specimen identification system using stored associated numbers
US3872448 11 Dic 1972 18 Mar 1975 Community Health Computing Inc Hospital data processing system
US3970996 7 Ene 1974 20 Jul 1976 Perfect Liberty Apparatus for collecting medical data
US4135241 4 Nov 1974 16 Ene 1979 Medelco, Incorporated Inventory control, bed allocation and accounting data handling system
US4164320 28 Jul 1976 14 Ago 1979 Medical Laboratory Automation, Inc. Patient and specimen identification means and system employing same
US4321461 18 Abr 1980 23 Mar 1982 K/W/D Associates Flow rate monitor and totalizer with count display
US4733364 20 Jun 1984 22 Mar 1988 Coco Research Inc. Period detecting circuit
US4756706 21 Ene 1986 12 Jul 1988 American Hospital Supply Corporation Centrally managed modular infusion pump system
US4778449 2 Feb 1987 18 Oct 1988 Bertin & Cie Monitoring system for the remote supervision of a plurality of gravity perfusion sets
US4855909 20 Nov 1987 8 Ago 1989 Hewlett-Packard Company Forensic sample tracking system and print station therefor
US4918604 3 Oct 1988 17 Abr 1990 Medco Containment Services, Inc. Prescription drug depiction and labeling system
US4970669 14 Abr 1989 13 Nov 1990 Kenneth B. McIntosh Medication clock
US5001630 20 Dic 1988 19 Mar 1991 Wiltfong M J Computerized case history business method
US5126957 30 Ago 1991 30 Jun 1992 Health Tech Services Corp. Interactive medication delivery system
US5164575 23 Abr 1991 17 Nov 1992 Neeley William E Blood sampling procedure and apparatus
US5166498 4 Mar 1992 24 Nov 1992 Neeley William E Procedure and assembly for drawing blood
US5235507 16 Ene 1990 10 Ago 1993 P. B. Toau And Company, Ltd. Health insurance management system
US5315505 29 Ene 1992 24 May 1994 Micro Chemical, Inc. Method and system for providing animal health histories and tracking inventory of drugs
US5368554 20 Nov 1992 29 Nov 1994 Minnesota Mining And Manufacturing Company Blood pumping system with selective backflow warning
US5371692 12 Mar 1991 6 Dic 1994 Hewlett-Packard Company Activating circuit for modifying or adding a new program to an electronic device
US5382232 13 Mar 1992 17 Ene 1995 Ivac Corporation Infusion system with air-in-line clear function
US5404384 25 Ene 1993 4 Abr 1995 Medselect Systems, Inc. Inventory monitoring apparatus employing counter for adding and subtracting objects being monitored
US5460605 7 Dic 1993 24 Oct 1995 Gensia, Inc. Diagnosis, evaluation and treatment of coronary artery disease by exercise simulation using closed loop drug delivery of an exercise simulating agent beta agonist
US5533079 25 Ene 1994 2 Jul 1996 Medselect Systems, Inc. Inventory monitoring apparatus
US5538006 24 Mar 1994 23 Jul 1996 Hewlett-Packard Company Configuration method for an anesthesia protocol system
US5601445 13 Mar 1995 11 Feb 1997 Imed Corporation Electrical and structural interconnector
US5622429 21 Ene 1994 22 Abr 1997 Jostra Medizintechnik Gmbh & Co. Kg. Medical apparatus for transferring data between a data monitoring unit and a remote data analysis unit via a contactless memory card
US5657236 14 Ago 1995 12 Ago 1997 Profile Systems, Llc Medication dispensing and timing system utilizing patient communicator with internal clock
US5672154 27 Ago 1993 30 Sep 1997 Minidoc I Uppsala Ab Method and apparatus for controlled individualized medication
US5703786 14 Ago 1995 30 Dic 1997 Profile Systems, Llc Medication dispensing and timing system utilizing time reference message
US5704352 22 Nov 1995 6 Ene 1998 Tremblay; Gerald F. Implantable passive bio-sensor
US5710551 26 Jul 1995 20 Ene 1998 Ridgeway; Donald G. Self-medication monitoring system
US5712913 8 Feb 1994 27 Ene 1998 Digicash Incorporated Limited-traceability systems
US5758096 9 Ago 1995 26 May 1998 Barsky; Howard System and method for personalized medication treatment management
US5803906 11 Abr 1994 8 Sep 1998 Micro Chemical, Inc. Method and system for providing animal health histories and tracking inventory of related drug usage
US5819229 7 Nov 1995 6 Oct 1998 Northrop Grumman Corporation Surgical assistance and monitoring system
US5850344 14 Ago 1995 15 Dic 1998 Profile Systems, Llc Medication dispensing and timing system
US5852408 16 Oct 1995 22 Dic 1998 Christiansen; Steven Aagard Medication dispensing and compliance monitoring system
US5894273 26 Ago 1996 13 Abr 1999 Fairway Medical Technologies, Inc. Centrifugal blood pump driver apparatus
US5941710 17 Dic 1996 24 Ago 1999 University Of Florida Research Foundation Apparatus and method of simulating the determination of continuous blood gases in a patient simulator
US5953099 22 Oct 1997 14 Sep 1999 Walach; Michael Nonprogressive multi-focal ophthalmic lens
US5995077 31 Ene 1996 30 Nov 1999 The United States Of America As Represented By The Secretary Of The Navy Portable, wearable read/write data device
US6000828 22 Ago 1997 14 Dic 1999 Power Med Incorporated Method of improving drug treatment
US6009333 14 Ago 1997 28 Dic 1999 Executone Information Systems, Inc. Telephone communication system having a locator and a scheduling facility
US6048087 12 Mar 1998 11 Abr 2000 Biostat S.A. Multi-compartment, electronic pocket pillbox
US6053887 4 Dic 1998 25 Abr 2000 Baxter Healthcare Inc. Medical treatment apparatus and method
US6290681 26 Jul 1995 18 Sep 2001 Remote Medical Corporation Flow monitoring device for medical application
US6314556 * 24 Ago 1999 6 Nov 2001 Deroyal Business Systems, Llc Modular health care information management system utilizing reusable software objects
US6409684 19 Abr 2000 25 Jun 2002 Peter J. Wilk Medical diagnostic device with multiple sensors on a flexible substrate and associated methodology
US6529892 4 Ago 1999 4 Mar 2003 Illinois, University Of Apparatus, method and product for multi-attribute drug comparison
US6558352 30 May 2000 6 May 2003 Verilogik, Inc. System and method for variable dosage medicine delivery
US6581606 26 Mar 2001 24 Jun 2003 The Rx Files Corporation Method, apparatus and system for use in treating patient with a drug having an antineoplastic effect to optimize therapy and prevent an adverse drug response
US6757898 18 Ene 2000 29 Jun 2004 Mckesson Information Solutions, Inc. Electronic provider—patient interface system
US6856247 25 Abr 2003 15 Feb 2005 A La Cart, Inc. Food information monitoring system
US7034691 25 Ene 2002 25 Abr 2006 Solvetech Corporation Adaptive communication methods and systems for facilitating the gathering, distribution and delivery of information related to medical care
US7054844 5 Ene 2001 30 May 2006 Bce Emergis Inc. Secure electronic procurement system and method
US7230529 5 Feb 2004 12 Jun 2007 Theradoc, Inc. System, method, and computer program for interfacing an expert system to a clinical information system
US7263492 15 Feb 2002 28 Ago 2007 Fair Isaac Corporation Sequencing models of healthcare related states
US7421709 4 Ene 2005 2 Sep 2008 Information Builders, Inc. Framework for adapter used in enterprise application integration
US7526769 5 Nov 2004 28 Abr 2009 Sun Microsystems, Inc. Message translation and parsing of data structures in a distributed component architecture
US7847970 15 Abr 2005 7 Dic 2010 Automed Technologies, Inc. System and method for reception, analysis, and annotation of prescription data
US7962544 20 Abr 2006 14 Jun 2011 Siemens Medical Solutions Usa, Inc. Patient and device location dependent healthcare information processing system
US7970550 16 Sep 2003 28 Jun 2011 Optimata, Ltd Interactive technique for optimizing drug development from the pre-clinical phases through phase-IV
US8005688 7 Nov 2005 23 Ago 2011 Carefusion 303, Inc. Distributed remote asset and medication management drug delivery system
US8024200 11 May 2006 20 Sep 2011 Cerner Innovation, Inc. Graphical user interface for clinical order administration scheduling
US8160895 16 Ene 2007 17 Abr 2012 Cerner Innovation, Inc. User interface for clinical decision support
US8291337 19 Nov 2009 16 Oct 2012 Cerner Innovation, Inc. Infusion management
US8689008 5 Ago 2009 1 Abr 2014 Net.Orange, Inc. Operating system
US20020016923 2 Abr 2001 7 Feb 2002 Knaus William A. Broadband computer-based networked systems for control and management of medical records
US20020022973 21 Mar 2001 21 Feb 2002 Jianguo Sun Medical information management system and patient interface appliance
US20020033548 5 Oct 2001 21 Mar 2002 Dmitri Brodkin Dental restorations formed by solid free-form fabrication methods
US20020042636 13 Nov 2001 11 Abr 2002 Cardiac Pacemakers, Inc. Change log for implantable medical device
US20020046346 3 Oct 2001 18 Abr 2002 Evans Jae A. Electronic medical records system
US20020077849 18 Dic 2000 20 Jun 2002 Baruch Howard M. System and method for improving efficiency of health care
US20020087114 31 Oct 2001 4 Jul 2002 Medtronic, Inc. Therapy management techniques for an implantable medical device
US20020120350 3 Oct 2001 29 Ago 2002 Klass David B. Method and system for identifying and anticipating adverse drug events
US20020198624 22 Jun 2001 26 Dic 2002 Shlomo Greenwald Hospital drug distribution system
US20030009244 6 Sep 2002 9 Ene 2003 Engleson Joseph J. System and method for collecting data and managing patient care
US20030045858 27 Sep 2002 6 Mar 2003 Aspect Medical Systems, Inc. System and method for adaptive drug delivery
US20030051737 31 Jul 2002 20 Mar 2003 Scott Laboratories, Inc. Apparatuses and methods for titrating drug delivery
US20030063524 3 Sep 2002 3 Abr 2003 Niemiec Mark A. Drug delivery management system
US20030069481 30 Sep 2002 10 Abr 2003 Robert Hervy System for the remote monitoring of patients
US20030105389 2 Abr 2002 5 Jun 2003 Siemens Medical Solutions Health Services Corporation System for processing data acquired from multiple medical devices
US20030105555 30 Nov 2001 5 Jun 2003 Lunak Richard R. Method of issuing medical supplies and dispensing and administering medications through a hand-held device and a device and system for doing the same
US20030121517 17 Dic 2002 3 Jul 2003 Mcfarland Joseph L. Portable, handheld, pneumatic driven medicinal nebulizer
US20030129578 4 Jun 2002 10 Jul 2003 Mault James R. Method and system for early detection of infectious diseases or symptoms of bioterrorism attacks
US20030156143 11 Oct 2002 21 Ago 2003 University Of Utah Anesthesia drug monitor
US20030158746 5 Abr 2001 21 Ago 2003 Steven Forrester Method and system for collecting and circulating data derived from medical appliances, useful in particular in intensive care units
US20030205897 8 Jun 2001 6 Nov 2003 Kaufman Stacy R. Verification of prescription information and warning label
US20030236683 19 Jun 2003 25 Dic 2003 Dwight Henderson Closed loop medication use system and method
US20040068229 19 Feb 2002 8 Abr 2004 Willem Jansen Method and a system for administerinng muscle relaxant to a patient
US20040073329 18 Jul 2003 15 Abr 2004 Engleson Joseph J. System and method for collecting data and managing patient care
US20040107118 26 Nov 2003 3 Jun 2004 Hugh Harnsberger Electronic clinical reference and education system and method of use
US20040122702 18 Dic 2002 24 Jun 2004 Sabol John M. Medical data processing system and method
US20040122705 18 Dic 2002 24 Jun 2004 Sabol John M. Multilevel integrated medical knowledge base system and method
US20040122719 18 Dic 2002 24 Jun 2004 Sabol John M. Medical resource processing system and method utilizing multiple resource type data
US20040176297 24 Mar 2004 9 Sep 2004 Wing Cheung Pharmacokinetic and pharmacodynamic modeling of erythropoietin administration
US20040260478 1 Abr 2002 23 Dic 2004 Schwamm Lee H. System, process and diagnostic arrangement establishing and monitoring medication doses for patients
US20050020996 18 Ago 2004 27 Ene 2005 Medtronic, Inc. Method and apparatus to control drug therapy dosages in an implantable pump
US20050021297 4 Ago 2004 27 Ene 2005 Medtronic, Inc. Therapy management techniques for an implantable medical device
US20050088296 28 Oct 2003 28 Abr 2005 Lee Jung K. Baby health monitoring system
US20050096941 9 Oct 2003 5 May 2005 Greg Tong Method for saving medication costs by redistributing unused medications
US20050097566 5 Nov 2004 5 May 2005 Seebeyond Technology Corporation, A California Corporation Message translation and parsing of data structures in a distributed component architecture
US20050113945 29 Dic 2004 26 May 2005 Alaris Medical Systems, Inc. System and method for programming a clinical device
US20050145010 31 Dic 2003 7 Jul 2005 Vanderveen Timothy W. Medication safety enhancement for secondary infusion
US20050148890 31 Dic 2003 7 Jul 2005 Ge Medical Systems Information Technologies, Inc. Alarm notification system and receiver incorporating multiple functions
US20050171815 31 Dic 2003 4 Ago 2005 Vanderveen Timothy W. Centralized medication management system
US20050224083 19 Dic 2003 13 Oct 2005 Crass Richard E Intravenous medication harm index system
US20060026205 30 Jul 2004 2 Feb 2006 Butterfield Robert D System and method for managing medical databases for patient care devices
US20060047538 25 Ago 2004 2 Mar 2006 Joseph Condurso System and method for dynamically adjusting patient therapy
US20060101072 21 Oct 2004 11 May 2006 International Business Machines Corproation System and method for interpreting scan data
US20060122481 22 Nov 2004 8 Jun 2006 Crispian Lee Sievenpiper System and method for location based remote services
US20060200369 30 Dic 2005 7 Sep 2006 Batch Richard M Management of pending medication orders
US20060218015 13 Jun 2006 28 Sep 2006 Walker Jay S Methods and apparatus for increasing and/or for monitoring a party's compliance with a schedule for taking medicines
US20060249423 27 Jun 2006 9 Nov 2006 Mika Reijonen Method and apparatus to identify and separate medicinal preparations and dosages thereof
US20070015972 21 Jun 2004 18 Ene 2007 Le Yi Wang System for identifying patient response to anesthesia infusion
US20070043767 22 Ago 2006 22 Feb 2007 Forhealth Technologies, Inc. Data transmission capture in support of medication preparation
US20070061393 1 Feb 2006 15 Mar 2007 Moore James F Management of health care data
US20070083389 * 30 Mar 2006 12 Abr 2007 Cerner Innovation,Inc. User Interface for Prioritizing Opportunities for Clinical Process Improvement
US20070106457 26 Sep 2006 10 May 2007 Outland Research Portable computing with geospatial haptic compass
US20070156860 30 Dic 2005 5 Jul 2007 Microsoft Corporation Implementing computer application topologies on virtual machines
US20070168301 1 Dic 2006 19 Jul 2007 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070208454 25 Oct 2006 6 Sep 2007 Mckesson Automation Systems Inc. Adaptive interface for product dispensing systems
US20070210157 11 Abr 2006 13 Sep 2007 Jadak Technologies, Inc. Infusion Pump Having Radiofrequency Identification and Optical Imaging Capabilities
US20070286466 25 May 2006 13 Dic 2007 Heffernan Patrick B DICOM adapter service for CAD system
US20070293843 31 Ago 2007 20 Dic 2007 Medtronic Minimed, Inc. Physiological monitoring device for controlling a medication infusion device
US20080015549 16 Jul 2007 17 Ene 2008 Siemens Medical Solutions Usa, Inc. System For Processing Medication Restriction Information
US20080025230 27 Jul 2006 31 Ene 2008 Alpesh Patel Applying quality of service to application messages in network elements based on roles and status
US20080034323 3 Ago 2006 7 Feb 2008 Blomquist Michael L Interface for medical infusion pump
US20080046292 17 Ene 2007 21 Feb 2008 Accenture Global Services Gmbh Platform for interoperable healthcare data exchange
US20080141272 6 Dic 2006 12 Jun 2008 Borgendale Kenneth W Application Message Conversion Using A Feed Adapter
US20080162254 19 Mar 2008 3 Jul 2008 International Business Machines Corporation Method and System for Patient Care Triage
US20080164998 * 20 Dic 2007 10 Jul 2008 Siemens Medical Solutions Usa, Inc. Location Sensitive Healthcare Task Management System
US20080169045 31 Oct 2006 17 Jul 2008 Forhealth Technologies, Inc. Automated drug preparation apparatus including serial dilution functionality
US20080195246 23 May 2007 14 Ago 2008 Forhealth Technologies, Inc. Centralized sterile drug products distribution and automated management of sterile compounding stations
US20080272138 12 Oct 2007 6 Nov 2008 Cardinal Health 303, Inc. Automated medication handling system
US20080317672 20 Jun 2007 25 Dic 2008 The General Electric Company Detection of anomalies in measurement of level of hypnosis
US20090012812 6 Mar 2008 8 Ene 2009 Tracy Rausch System and method for patient care
US20090012813 3 Jul 2008 8 Ene 2009 Mckesson Financial Holdings Limited Systems and methods for managing medical information
US20090099867 11 Ago 2008 16 Abr 2009 Smiths Medical Md, Inc. Communicating preventative maintenance data to a medical device
US20090150484 11 Ago 2008 11 Jun 2009 Smiths Medical Md Medical device metadata
US20090210252 30 Oct 2008 20 Ago 2009 Marc Silver Method and apparatus for real time analysis of medical orders
US20090240651 20 Mar 2008 24 Sep 2009 General Electric Company Systems and Methods for a Predictive Notification Engine
US20090306585 8 May 2009 10 Dic 2009 Changlin Pang Implantable pumps and cannulas therefor
US20090306944 16 Jun 2007 10 Dic 2009 Bayer Technology Services Gmbh Device and method for calculating and supplying a drug dose
US20090319623 24 Jun 2008 24 Dic 2009 Oracle International Corporation Recipient-dependent presentation of electronic messages
US20100037067 5 Ago 2009 11 Feb 2010 Vasu Rangadass Operating System
US20100094653 23 Ene 2009 15 Abr 2010 Forhealth Technologies, Inc. Management, reporting and benchmarking of medication preparation
US20100121654 22 Jul 2009 13 May 2010 Siemens Medical Solutions Usa, Inc. Integrated Medication and Infusion Monitoring System
US20100161113 4 Mar 2010 24 Jun 2010 Forhealth Technologies, Inc. Automated drug preparation apparatus including drug reconstitution
US20100169120 31 Dic 2008 1 Jul 2010 Cerner Innovation, Inc. Patient to device association
US20100169771 31 Dic 2008 1 Jul 2010 Cerner Innovation, Inc. User Interface for Managing Patient Care Plans
US20100174552 12 Nov 2009 8 Jul 2010 Paxit Automation Products LLC System and methodology for filling prescriptions
US20100174553 21 Dic 2009 8 Jul 2010 Medtronic Minimed, Inc. Diabetes Therapy Management System
US20100179825 8 Ene 2010 15 Jul 2010 Cerner Innovation, Inc. Copying patient-customized healthcare plans/orders/phases
US20100241453 20 Mar 2009 23 Sep 2010 Mckesson Financial Holdings Limited Method, Apparatus And Computer Program Product For Displaying And Permitting Revision Of A Potential Interaction
US20100241456 10 Mar 2010 23 Sep 2010 Siemens Medical Solutions Usa, Inc. Integrated Point of Care Medication Administration Information System
US20100271218 21 Abr 2010 28 Oct 2010 Carefusion 303, Inc. Infusion tracking system
US20100280840 29 Abr 2010 4 Nov 2010 Sony Corporation Drug information processing device and drug information processing method
US20100323397 10 May 2007 23 Dic 2010 Scottish Crop Research Institute Modified vird2 protein and its use in improved gene transfer
US20110015941 27 Ago 2010 20 Ene 2011 Virtual Radiologic Corporation Teleradiology image processing system
US20110046975 20 Ago 2010 24 Feb 2011 Cerner Innovation, Inc. Dynamically adjusted rules-based decision support using site-specific mapped values
US20110060758 16 Nov 2010 10 Mar 2011 Carefusion 303, Inc. Medication management system
US20110119612 24 Sep 2010 19 May 2011 Cerner Innovation, Inc. Integrating action boxes for infusion management
US20110202495 18 Feb 2010 18 Ago 2011 Ute Gawlick Adjustable alert rules for medical personnel
US20110282691 18 Jul 2011 17 Nov 2011 Carefusion 303, Inc. Distributed remote asset and medication management drug delivery system
US20110288882 * 1 Ago 2011 24 Nov 2011 Halow George M System to Prevent Medical Billing Fraud
US20110313787 16 Jun 2010 22 Dic 2011 Vasu Rangadass Operating System
US20120011253 19 Sep 2011 12 Ene 2012 Carefusion 303, Inc. System and method for network monitoring of multiple medical devices
US20120016215 27 Sep 2011 19 Ene 2012 Carefusion 303, Inc. System and method for dynamically adjusting patient therapy
US20120041775 20 May 2011 16 Feb 2012 Cardiocom, Llc Systems, methods, and computer program products for patient monitoring
US20120053533 7 Nov 2011 1 Mar 2012 Carefusion 303, Inc. Infusion data communication system
US20120075061 24 Sep 2010 29 Mar 2012 Carefusion 303, Inc. Automatic association of medical elements
US20120136673 30 Nov 2010 31 May 2012 Mckesson Financial Holdings Limited Methods, apparatuses and computer program products for determining changes in levels of care for patients
US20120173264 30 Dic 2011 5 Jul 2012 Cerner Innovation, Inc. Facilitating identification of potential health complications
US20120182939 13 Ene 2012 19 Jul 2012 Qualcomm Incorporated Telehealth wireless communication hub and service platform system
US20120185267 21 Dic 2011 19 Jul 2012 Deka Products Limited Partnership System, Method, and Apparatus for Electronic Patient Care
US20120191052 20 Feb 2007 26 Jul 2012 Ip Holdings, Inc. Intelligent activated skin patch system
US20120239824 15 Mar 2012 20 Sep 2012 Carefusion 303, Inc. Scalable communication system
US20120247480 29 Mar 2011 4 Oct 2012 Varga Christopher M Flow splitting ncpap device
US20120253835 31 Mar 2011 4 Oct 2012 Mckesson Financial Holdings Methods, apparatuses and computer program products for facilitating quality reporting and alerts management
US20120265549 12 Abr 2011 18 Oct 2012 General Electric Company System and Computer Readable Medium for Predicting Patient Outcomes
US20130085771 27 Sep 2012 4 Abr 2013 Patientsafe Solutions Method of displaying patient data in a medical workflow environment
US20130096444 4 Dic 2012 18 Abr 2013 Carefusion 303, Inc. System and method for dynamically adjusting patient therapy
US20130197927 13 Mar 2013 1 Ago 2013 Carefusion 303, Inc. Healthcare validation system
US20130197928 13 Mar 2013 1 Ago 2013 Carefusion 303, Inc. Context-aware healthcare notification system
US20130197929 13 Mar 2013 1 Ago 2013 Carefusion 303, Inc. Healthcare communication system
US20130197930 13 Mar 2013 1 Ago 2013 Carefusion 303, Inc. Infusion order and delivery consistency
US20130197931 13 Mar 2013 1 Ago 2013 Carefusion 303, Inc. Predictive medication safety
US20130204433 13 Mar 2013 8 Ago 2013 Carefusion 303, Inc. Patient-specific medication management system
US20130204637 13 Mar 2013 8 Ago 2013 Carefusion 303, Inc. Pharmacy workflow management system
US20130262138 23 May 2013 3 Oct 2013 Carefusion 303, Inc. Medication preparation queue
US20140028464 26 Jul 2012 30 Ene 2014 Carefusion 303, Inc. Predictive notifications for adverse patient events
US20140100868 11 Dic 2013 10 Abr 2014 Carefusion 303, Inc. System and method for dynamically adjusting patient therapy
US20140278466 15 Mar 2013 18 Sep 2014 Cvs Pharmacy, Inc. Pharmacy workflow
US20140297313 16 Jun 2014 2 Oct 2014 Carefusion 303, Inc. System and method for dynamically adjusting patient therapy
US20140350950 23 May 2013 27 Nov 2014 Carefusion 303, Inc. Medication preparation queue
US20150250948 26 May 2015 10 Sep 2015 Carefusion 303, Inc. Patient-specific medication management system
US20160000997 8 Sep 2015 7 Ene 2016 Carefusion 303, Inc. Management of pending medication orders
CA2472098A1 30 Dic 2002 17 Jul 2003 Scott Laboratories, Inc. Apparatuses and methods for automatically assessing and monitoring a patient's responsiveness
CA2554903A1 7 Oct 2004 21 Abr 2005 Hospira, Inc. Medication management system
CN1759398A 21 Nov 2003 12 Abr 2006 阿拉里医疗设备有限公司 Medication management system
CN101116077A 11 Feb 2006 30 Ene 2008 卡迪纳尔健康303公司 Identification system and method for medication management
CN101146055A 14 Sep 2006 19 Mar 2008 中国电信股份有限公司 SMS realization method and related system of SIP terminal
CN101890193A 13 Jul 2010 24 Nov 2010 深圳职业技术学院 Intelligent venous transfusion monitoring system
CN102068725A 25 Nov 2009 25 May 2011 善德仕医疗科技（北京）有限公司 Medicinal execution equipment and method capable of identifying medicaments
CN102688532A 14 Jun 2012 26 Sep 2012 钱峰 Transfusion prompt system
CN201110955Y 7 Dic 2007 3 Sep 2008 华中科技大学 Medical infusion velocity monitoring and controlling device based on machine vision
DE4023785A1 26 Jul 1990 30 Ene 1992 Mueller & Sebastiani Elek Gmbh Central computer system storing, preparing and updating patient's dat - has associated mobile computer units with data exchange facilities and multiple memory input media
EP0384155A2 26 Ene 1990 29 Ago 1990 B. Braun Melsungen AG Combination of a medical device with a redundant controller for infusion therapy or blood treatmentand a programming device
EP0649316A1 14 Oct 1993 26 Abr 1995 Baxter International Inc. An infusion pump with an electronically loadable drug library
EP0652528A2 26 Oct 1994 10 May 1995 AT&amp;T Corp. Integrated computer system and method for processing medical informations and patient data
EP0784283A1 27 Nov 1996 16 Jul 1997 Kameda Medical Information Laboratory Medical care schedule and record aiding system and method
EP1003121A2 29 Oct 1999 24 May 2000 Becton, Dickinson and Company Medication and specimen management system
EP1018347A2 26 Ago 1993 12 Jul 2000 Sims Deltec, Inc. Systems and methods for communicating with ambulatory medical devices such as drug delivery devices
EP1237113A2 22 Feb 2002 4 Sep 2002 VigiLanz Corporation System and method for integrating pharmacy and laboratory data
GB2141006B Título no disponible
JP5168708B2 Título no disponible
JP2002520718A Título no disponible
JP2003085283A Título no disponible
JP2004287616A Título no disponible
JP2006155070A Título no disponible
JPH05168708A Título no disponible
JPH11505352A Título no disponible
JPS62114562A Título no disponible
KR100847397B1 Título no disponible
KR20070045611A Título no disponible
KR20080013129A Título no disponible
KR20100125972A Título no disponible
KR20110070824A Título no disponible
KR20120076615A Título no disponible
KR20120076635A Título no disponible
NZ522631A Título no disponible
WO1993022735A1 3 May 1993 11 Nov 1993 Pacing Management & Consultancy B.V. Method and system for patient-oriented optimization of order of care treatments and patient identification card for use in such a method or such a system
WO1994005344A1 1 Sep 1993 17 Mar 1994 Pall Corporation Process and apparatus for removal of unwanted fluids from processed blood products
WO1994013250A1 3 Dic 1993 23 Jun 1994 Automated Healthcare, Inc. Portable nursing center
WO1995023378A2 27 Feb 1995 31 Ago 1995 Executone Information Systems, Inc. Patient care and communication system
WO1997004712A1 19 Jul 1996 13 Feb 1997 Mc Medical Card Systems Gmbh System for the transmission and storage of personal medical data, and an ic card for use in such a system
WO1998028676A2 9 Dic 1997 2 Jul 1998 Pyxis Corporation System for drug and health care supply distribution and replenishment
WO1999009505A1 23 Jul 1998 25 Feb 1999 Becton Dickinson And Company System and method for selecting an intravenous device
WO1999010829A1 17 Ago 1998 4 Mar 1999 Deka Products Limited Partnership Health care system and method for physician order entry
WO1999010830A1 18 Ago 1998 4 Mar 1999 Deka Products Limited Partnership Automated health care system
WO1999044167A1 12 Feb 1999 2 Sep 1999 Rx Communications, Inc. Pharmacy drug management system providing patient specific drug dosing, drug interaction analysis, order generation, and patient data matching
WO1999045490A2 3 Mar 1999 10 Sep 1999 Goetech Llc Medication monitoring system and apparatus
WO1999067732A1 23 Jun 1999 29 Dic 1999 Joseph Ifergan System for collecting data for each patient in hospital environment
WO2000003344A1 9 Jul 1999 20 Ene 2000 Alaris Medical Systems, Inc. System and method for collecting data and managing patient care
WO2000004521A1 9 Jul 1999 27 Ene 2000 Brien Charles T O Interactive prescription compliance and life safety system
WO2001086506A1 7 May 2001 15 Nov 2001 Merck-Medco Managed Care, Llc System for monitoring regulation of pharmaceuticals from data structure of medical and laboratory records
WO2002069099A2 25 Feb 2002 6 Sep 2002 Alaris Medical Systems, Inc. System and method for managing patient care
WO2003038566A2 1 Nov 2002 8 May 2003 Scott Laboratories, Inc. User interface for sedation and analgesia delivery systems and methods
WO2003092769A2 28 Abr 2003 13 Nov 2003 Baxter International Inc. Medical treatment verification system and method
WO2003094091A1 28 Abr 2003 13 Nov 2003 Baxter International Inc. Infusion therapy flow rate adjustment system and method
WO2004060443A2 23 Dic 2003 22 Jul 2004 Scott Laboratories, Inc. Apparatuses and methods for automatically assessing and monitoring a patient’s responsiveness
WO2004061745A2 21 Nov 2003 22 Jul 2004 Alaris Medical Systems, Inc. Medication management system
WO2010124016A1 21 Abr 2010 28 Oct 2010 Lead Horse Technologies, Inc. Artificial intelligence-assisted medical reference system and method
WO2010124328A1 28 Abr 2010 4 Nov 2010 Austin Health A system, method and computer program for determining the probability of a medical event occurring
WO2012095829A2 16 Ene 2012 19 Jul 2012 Q-Core Medical Ltd. Methods, apparatus and systems for medical device communication, control and localization
1 "General-Purpose Infusion Pumps," Evaluation-Health Devices, Oct. 2002, pp. 353-387, vol. 31(10), ECRI Institute.
2 "Infusion Pump Technology," Health Devices, Apr.-May 1998, pp. 150-170, vol. 27(4-5), ECRI Institute.
3 "Infusion Pumps, General-Purpose," Healthcare Product Comparison System, 2007, pp. 1-54, ECRI Institute.
4 "Infusion Pumps, Large-Volume," Healthcare Product Comparison System, 2010, pp. 1-51, ECRI Institute.
5 "'Smart' Infusion Pumps Join CPOE and Bar Coding as Important Ways to Prevent Medication Errors," ISMP-Medication Safety Alert, Feb. 7, 2002, 2 pgs., Institute for Safe Medication Practices.
6 "THE PROBLEM WITH MULTIFUNCTION OPTICAL IS TOO MANY STANDARDS.", SYSTEMS INTEGRATION., CAHNERS PUBLISHING, NEWTON., US, vol. 24., no. 06., 1 June 1991 (1991-06-01), US, pages 43 - 44 + 46, XP000234431
7 "‘Smart’ Infusion Pumps Join CPOE and Bar Coding as Important Ways to Prevent Medication Errors," ISMP—Medication Safety Alert, Feb. 7, 2002, 2 pgs., Institute for Safe Medication Practices.
8 "General-Purpose Infusion Pumps," Evaluation—Health Devices, Oct. 2002, pp. 353-387, vol. 31(10), ECRI Institute.
9 Anonymous, Guardrails® Safety Software-Medley TM Medication Safety System, Alaris Medical Systems XP-00234431; 2002 Alaris Medical Systems Inc. Nov. 2002, SSM @2159C.
10 Baldauf-Sobez et al., "How Siemens' Computerized Physician Order Entry Helps Prevent the Human Error," Electromedica, vol. 71, No. 1, 2003, pp. 2-10.
11 Calabrese, et al., "Medication administration errors in adult patients in the ICU," Intensive Care Med, 2001, pp. 1592-1598, vol. 27, Springer-Verlag.
12 Canadian Office Action for Application No. 2512991, dated Mar. 2, 2017, 4 pages.
13 Canadian Office Action for Application No. 2551903, dated Mar. 28, 2017, 7 pages.
14 Chinese Office Action for Application No. 201480015147.6, dated Mar. 10, 2017, 10 pages excluding translation.
15 Eskew, James et al., Using Innovative Technologies to Set New Safety Standards for the Infusion of Intravenous Medications, Hospital Pharmacy, vol. 37, No. 11, pp. 1179-1189, 2002, Facts and Comparisons.
16 European Office Action for Application No. 12756903.6, dated Apr. 19, 2017, 5 pages.
17 Evans, R. S. et al., "Enhanced notification of infusion pump programming errors", Studies in health technology and informatics, Jan. 1, 2010, pp. 734-738, XP055305644, Netherlands DOI: 10.3233/978-1-60750-588-4-734 Retrieved from the Internet: URL:http://booksonline.iospress.nl/Extern/EnterMedLine.aspx?ISSN=0926-9630&Volume=160&SPage=734 [retrieved on Sep. 26, 2016].
18 Extended European Search Report and Written Opinion for Application No. 14772937.0, dated Oct. 10, 2016, 9 pages.
19 Extended European Search Report and Written Opinion for Application No. 14779139.6, dated Nov. 7, 2016, 7 pages.
20 Extended European Search Report for Application No. 14775918.7, dated Sep. 13, 2016, 10 pages.
21 Extended European Search Report for Application No. 14779655.1, dated Jul. 14, 2016, 8 pages.
22 Extended European Search Report for Application No. 14780320.9, dated Jul. 1, 2016, 7 pages.
23 Extended European Search Report for Application No. 14801713.0, dated Jan. 16, 2017, 8 pages.
24 Extended European Search Report for Application No. 14801726.2, dated Jan. 5, 2017, 8 pages.
25 International Search Report and Written Opinion of the International Searching Authority dated Sep. 5, 2014, for PCT application PCT/US2014/037577.
26 International Search Report and Written Opinion, Application No. PCT/US2014/022832, Jun. 24, 2014, 12 pgs.
27 International Search Report and Written Opinion, Application No. PCT/US2014/022840, Jun. 19, 2014, 13 pgs.
28 International Search Reports and Written Opinion of the International Searching Authority dated Jun. 18, 2014 and Jun. 19, 2014 for PCT applications PCT/US2014/022830, PCT/US2014/022835 and PCT/US2014/022837. Office Action issued in U.S. Appl. No. 13/802,433 dated Aug. 25, 2014.
29 International Search Reports and Written Opinions of the International Searching Authority dated Jun. 19, 2014 and Jun. 24, 2014 for PCT Application Nos. PCT/US2014/022840 and PCT/US2014/022532.
30 Kohn, et al., "To Err is Human-Building a Safer Health System," National Academy Press, 2002, pp. i-287, National Academy of Sciences.
31 Kohn, et al., "To Err is Human—Building a Safer Health System," National Academy Press, 2002, pp. i-287, National Academy of Sciences.
32 Lesar, "Recommendations for Reducing Medication Errors," Medscape Pharmacists, posted Jul. 24, 2000, 10 pgs, vol. 1(2), Medscape Pharmacists, <http://www.medscape.com>.
33 Meier, "Hospital Products Get Seal of Approval at a Price," The New York Times, Apr. 23, 2002, 5 pgs.
34 Non-Final Office Action dated Oct. 14, 2014, issued in U.S. Appl. No. 11/326,145, and Non-Final Office Action dated Oct. 24, 2014, issued in U.S. Appl. No. 13/559,537.
35 Office Action for United Arab Emirates Application No. UAE/P/0962/2013, dated Apr. 17, 2017, 18 pages.
36 Queensland Health. Use of returned or unused dispensed medicines, Jan. 5, 2005, Queensland Government. pp. 1-2.
37 R SCOTT EVANS, CARLSON RICK, JOHNSON KYLE V, PALMER BRENT K, LLOYD JAMES F: "Enhanced notification of infusion pump programming errors", STUDIES IN HEALTH TECHNOLOGY AND INFORMATICS, NETHERLANDS, 1 January 2010 (2010-01-01), Netherlands, pages 734 - 738, XP055305644, [retrieved on 20160926], DOI: 10.3233/978-1-60750-588-4-734
38 Shabot, et al., "Wireless clinical alerts for critical medication, laboratory and physiologic data," System Sciences 2000. Proceedings of the 33rd Annual Conference on Jan. 4-7, 2000, Piscataway, NJ, IEEE, Jan. 4, 2000.
39 U.S. Appl. No. 13/901,501, filed May 23, 2013.
40 U.S. Appl. No. 90/009,912, filed Aug. 12, 2013, Schlotterbeck et al.
41 U.S. Appl. No. 90/011,697, filed Aug. 12, 2013, Schlotterbeck et al.
42 Williams, et al., "Reducing the Risk of User Error with Infusion Pumps," Professional Nurse-Safe Practice-Infusion Devices, Mar. 2000, pp. 382-384, vol. 15(6).
43 Williams, et al., "Reducing the Risk of User Error with Infusion Pumps," Professional Nurse—Safe Practice—Infusion Devices, Mar. 2000, pp. 382-384, vol. 15(6).
44 Yokoi, "Prevention of Errors in Injection/Drip Infusion-No excuse for ignorance!-Essential Points of Accident Prevention, IV Infusion Pump, Syringe-pump Accident Prevention," JIN Special, Igaku Shoin K.K., Dec. 1, 2001, pp. 109-120, No. 70.
45 Yokoi, "Prevention of Errors in Injection/Drip Infusion—No excuse for ignorance!—Essential Points of Accident Prevention, IV Infusion Pump, Syringe-pump Accident Prevention," JIN Special, Igaku Shoin K.K., Dec. 1, 2001, pp. 109-120, No. 70.
Clasificación internacional G06F19/00, G06Q50/22, G06Q50/00, G06Q10/06
Clasificación cooperativa G06F19/3468, G06F19/326, G06F19/3462, G06Q50/22, G06Q10/06313
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GUPTA, VIKAS;LOEBIG, SCOTT;GARIBALDI, FEDERICO;AND OTHERS;SIGNING DATES FROM 20130326 TO 20130418;REEL/FRAME:030422/0092