Patient care system with conditional alarm forwarding

Information

  • Patent Grant
  • 11628246
  • Patent Number
    11,628,246
  • Date Filed
    Monday, January 25, 2021
    3 years ago
  • Date Issued
    Tuesday, April 18, 2023
    a year ago
Abstract
A patient care system is disclosed that includes a medical device such as an infusion pump. The medical device generates a data message containing information such as the status of the therapy being delivered, operating data or both. An alarm generating system assesses the data message from the pump and generates an alarm message if certain conditions established by a first set of rules are met. The alarm message is assessed according to a second set of rules as to whether to suppress the alarm message. The data message contains a required input for both the first and second algorithms. A dispatching system is adapted to forward the alarm message to an alarm destination according to a third set of rules. The alarm destination expresses an alarm upon receipt of the alarm message.
Description
BACKGROUND

Modern medical care often involves the use of medication management systems that include medication delivery and monitoring devices such as medication delivery pumps or patient parameter monitors or both, Medication management systems for configuring, controlling and monitoring medication delivery devices have been disclosed. For example, commonly owned U.S. Pat. No. 7,895,053 titled “MEDICATION MANAGEMENT SYSTEM” that issued on Feb. 22, 2011 and U.S. patent application Ser. No. 10/783,573 titled “MEDICATION MANAGEMENT SYSTEM” that published as US20050278194A1 on Dec. 15, 2005 disclose a medication management system wherein user customizable drug library or medical device configuration information is prepared using a drug library editor (DLE) program and module of a medication management unit (MMU). Hospira MedNet™ Meds™ software available from Hospira, Inc. of Lake Forest, Ill., U.S.A. includes such a DLE program. The MMU, which is equipped with Hospira MedNet™ Server software, downloads the customizable drug library to the medication delivery pump and receives status or activity information from the pump. Commonly owned U.S. Pat. No. 8,065,161 titled “SYSTEM FOR MAINTAINING DRUG INFORMATION AND COMMUNICATING WITH MEDICATION DELIVERY DEVICES” that issued on Nov. 22, 2011 discloses how the drug library or medical device configuration information is created, edited, stored and communicated to a medication delivery device in the context of a medication management system to deliver substances, such as fluids or fluid medication or both to patients.


According to the above-mentioned commonly owned published patent applications, a typical medication management system includes a point of care computer, such as a barcode point of care computer and/or pharmacy computer, and/or an MMU, in communication with one or more medication delivery devices. The point of care computer(s) and/or the MMU, with associated memory, store and share or communicate various information, such as patient information, prescription information, customized drug library or other information, for managing medication delivery to a patients, such as performing five-rights checking, configuring the medication delivery devices, and receiving and storing event, status or activity information received from the medication delivery devices.


Caregivers and clinicians use outputs from patient monitoring and equipment monitoring devices to make various patient care decisions. Patient monitoring devices and patient care equipment monitoring devices may be connected to a receiver, which receives the output signals from the patient monitoring devices and patient care equipment monitoring devices. In some cases, the receivers may display and/or record the information from the patient and patient care equipment monitoring devices. In other cases, the devices may include a monitor and/or recording medium. The receivers or devices may also have preset or adjustable alarms that are triggered when one of the outputs from the patient or patient care equipment monitoring devices deviates from a pre-set limit.


In hospitals that use infusion pumps and other medical devices, alarms are used to indicate device malfunction, therapy interruptions, end of therapy and other events that need to be handled by the clinical staff. Typically, alarms get displayed on device screens and produce audible sound. In some cases, there are too many devices that alarm in close proximity to each other. As a result, it is very hard to tell which device is actually alarming. The sound of alarms can also disturb or wake up sleeping patients. Hospital nurses usually manage multiple infusions running on multiple patients in one or more given clinical care areas. It is difficult for a nurse to be in the same vicinity of the infusion device at all times during an infusion, thus making it difficult to respond immediately to infusion-related or infusion device alarms. Further, clinical staff is not always in the close proximity to the alarming device to hear the alarm. In such situations it would be desirable for the staff to be notified of device alarms as soon as possible regardless of their proximity to the device so that they can better attend to their patients' needs.


Further, in some patient cases, it is critical to isolate the patient and reduce the exposure of the patient to unnecessary hospital conditions (e.g. burn patient being exposed to drafts or airborne contaminants when opening the door to the patient room). Further, multiple nurses may utilize the same pump on a patient between device cleaning. This results in an increase possibility of contamination due to an increased number of clinicians contacting the device. The pump may be contaminated by a clinician. This contamination may be transferred to the patient either by the clinician that first contaminated the pump or by a subsequent clinician who acquires the contamination by contacting the pump and then who transfers the contamination to the patient in the course of providing care to the patient. Further, contamination applied to a pump may be transferred to other devices and patients by clinicians who come in contact with the contamination on the pump and carry it with them to other pumps and patients where the contamination can be deposited and spread. Where alarms require a clinician to actually come to and contact a pump in order to assess the alarm, shut the alarm off or otherwise respond to the alarm, the likelihood of such contamination and cross-contamination increases.


SUMMARY OF THE INVENTION

A patient care system is disclosed that, in a preferred embodiment, includes at least one medical device such as an infusion pump. Each pump is capable of generating a data message containing information regarding the pump including the status of the therapy being delivered, operating data or both. The patient care system includes an alarm generating system that received the data message from the pump. The alarm generating system assesses the data message from the pump and fires a trigger if certain conditions established by a first set of rules, algorithms or instructions are met. The firing of a trigger produces an alarm message. This alarm message is assessed according to a second set of rules, algorithms or instructions as to whether to suppress the alarm message. For both the first and second algorithms, information generated by each pump is a required input.


The patient care system also includes a dispatching system that is connected to the alarm generating system. The dispatching system is adapted to forward the alarm message to an alarm destination according to a third set of rules, algorithms or instructions. Further, the patient care system includes an alarm destination connected to the dispatching system, the alarm destination expressing an alarm upon receipt by the alarm destination of the alarm.


In an alternate embodiment of the patient care system, the medical device is not part of the patient care system. Instead, the patient care system as disclosed interacts with the medical device. In another alternate embodiment of the patient care system, then alarm destination is not part of the patient care system but instead interacts with the patient care system. In yet another alternate embodiment of the patient care system, both the medical device and alarm destination are not part of the patient care system but instead interact with the patient care system. In yet another embodiment of the patient care system, both including and excluding the medical device and alarm destination or both, the alarm generating system and the dispatching system are combined into a single system.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic drawing of the architecture of one embodiment of a patient care system.



FIG. 2 is a data flow chart of one embodiment of a patient care system.



FIG. 3 is a chart showing the flow of information between various personnel and components of the patient care system of FIG. 1.



FIG. 4 is a flow chart of one embodiment of the patient care system of FIG. 1.



FIG. 5 is a chart of one embodiment of patient care system showing the process of configuring a pump from a monitor/controlling system.



FIG. 6 is a flow chart of one embodiment of patient care system showing the alarm forwarding and acknowledgment functions.



FIG. 7 is a chart of one embodiment of the patient care system showing the process of changing the pump infusion program with a monitor/controlling system.



FIG. 8 is a chart of one embodiment of the patient care system showing the process of transferring oversight of one or more pumps from one monitor/controller system to another monitor/controlling system.



FIG. 9 is a chart of one embodiment of the patient care system showing the process of monitoring the infusion by a pump with a monitor/controlling system.



FIG. 10 is a top view of one embodiment of a monitor/controlling system user interface design in various states during operation.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring to the Figures, a patient care system is shown in the Figures generally referred to by the reference number 10. The patient care system 10 interacts with a medical device 12 to manage alarms produced by the medical device 12. The patient care system 10 includes a dispatching system 14, an alarm forwarding system 16 and, in certain embodiments, a monitor/controlling system 18.


The patient care system 10 is intended to be deployed in any hospital or other facility that utilizes medical devices 12, including but not limited to infusion pumps, that are connected to networks either via hardwiring or through wireless connections. Such networks may be specific to the connection of one or more pumps 12 to each other or to control or monitoring devices. The networks may connect many medical devices and allow control or monitoring of a variety of such devices including control or monitoring from and to remote locations.


Medical device 12 is preferably an infusion pump 12 capable of receiving programming data from a nurse or other practitioner. Further, pump 12 is preferably capable of having its operational infusion program reviewed or confirmed or both by the nurse or other practitioner. Examples of pump 12 are the PLUM A+™ infusion system, LIFECARE PCA™ infusion system and SAPPHIRE™ infusion system sold by Hospira, Inc. of Lake Forest, Ill. Although medical device 12 is preferably an infusion pump 12, pump 12 as applied to the present patient care system 10 is intended to be understood to be any medical pump and more broadly, any medical device that has the capability of producing data and being connectable to a dispatching system 14 as described herein. Each pump 12 or other medical device is capable of generating a data message containing information regarding the pump including the status of the therapy being delivered, operating data or both. Examples of the data message generated by the pump 12 include, but are not limited to, pump 12 status data, the status of the therapy being delivered by the pump 12, event data associated with the pump 12 (e.g., expiration of certain time periods) and alarms associated with pump 12 or the delivery of therapy by the pump 12. Further, in some embodiments, pump 12 includes a local delay timer 50. The local delay timer may be a mechanical timer or a timer implemented in software. The local delay timer 50 is activated and begins counting when an alarm condition message is sent by the pump 12 to the dispatching system 14. In other embodiments of pump 12, pump 12 includes logic 52 that can be either discrete or implemented through software. Logic 52 allows pump 12 to make evaluations or take actions according to programming including rules, algorithms or instructions implemented on or associated with the logic 52 and may, in certain embodiments, also provide the local delay timer 50.


Dispatching system 14 is preferably a network application that manages alarms and preferably includes a dispatching server 20 capable of running software. A key function of the dispatching system 14 is to facilitate alarm management from the pump 12 to one of more alarm destinations (e.g., monitor/controlling systems 18) and back. For example, in a preferred embodiment, the dispatching system 14 is adapted to forward the alarm messages from the pump 12 to one or more monitor/controlling systems 18 according to a set of rules, algorithms or instructions. In a preferred embodiment of the patient care system 10, these rules, algorithms or instructions are executed on the alarm forwarding system 16 which, in effect, orchestrates the alarm flow from the pump 12 to one or more monitor/controlling systems 18 and back in order to implement safe, secure and reliable alarm handling. In a variant of this embodiment, rules, algorithms or instructions may be implemented on the pump 12 itself. The rules, algorithms or instructions can be configured by a rule editor.


In one embodiment, the dispatching server 14 incorporates an alarm forwarding system 16 that separates the alarm communication from the actual means of communication and forwards alarm information to monitor/controlling systems 18 according to rules, algorithms or instructions. The alarm forwarding system 16 assesses data messages produced by the pump 12 that are passed from the pump 12 to the alarm forwarding system 16 by the dispatching system 14 and fires a trigger if certain conditions established by a first set of rules, algorithms or instructions are met. The firing of a trigger produces an alarm message that is assessed according to a second set of rules, algorithms or instructions as to whether to suppress the alarm message. An example of a dispatching server 14 is a server equipped with the Hospira MedNet™ medication management software manufactured and sold by Hospira, Inc. of Lake Forest, Ill. The dispatching server can be used in combination with a hospital's existing alarm forwarding system or can be used in combination with a hospital's alarm forwarding system that has been modified to interface with the alarm messages received from dispatching server 14. In a preferred embodiment of the patient care system 10, the dispatching system 14 and alarm forwarding system 16 are separate systems that are connected together, for example, by a local area network (LAN) or wide area network (WAN), whether wireless, hardwired or connected by optical fibers, or any other communication protocol or system. However, the dispatching system 14 and alarm forwarding system 16 can be combined into a single system that performs the functions of the dispatching system 14 and alarm forwarding system 16 as described herein.


The patient care system 10, in a preferred embodiment, includes one or more monitor/controlling systems 18 connected to the dispatching system 14. The function of the monitor/controlling system 18 is to connect to the dispatching system 14, receive alarms and data from the dispatching system 14, communicate such alarms and data to a clinician and, in some embodiments, allow a clinician to produce a response to such alarms and data and otherwise produce acknowledgment or control responses and communicate such responses and acknowledgments to the dispatching system 14. The monitor/controlling system 18 preferably expresses an alarm upon receipt by the monitor/controlling system 18 of an alarm notification. The alarm can take various forms, including but not limited to an audible, visual, or vibratory alarm. The list of possible monitor/controlling systems 18 includes, but is not limited to, mobile wireless devices, network connected workstations, laptop computers, tablets, electronic mail, text messages, pagers and even fax machines


In an embodiment of the patient care system 10, medical device 12 forwards a data message to dispatching system 14, and dispatching system 14 accesses the data message to determine if an alarm condition is met and if an escalated alarm should be suppressed. For example, a local alarm at the medical device 12 could be temporarily suppressed while an alarm is sent to a remote monitor/controlling system 18. The content of the data message could be a required input for the evaluation of both whether or not an alarm condition is met, and if the escalated alarm should be suppressed. As mentioned above, the data message could contain information regarding pump therapy status data, pump operating point data, or both pump therapy status data and pump operating point data. If an alarm condition is met, dispatching system 14 could cause alarm forwarding system 16 to forward an alarm message to one or more monitor/control systems 18. As a result, the monitor/controlling system 18 does not sound the alarm at the monitor/controlling system 18 except under certain predetermined conditions. Further, the medical device 12 itself may not sound an alarm except according to certain predetermined conditions.



FIG. 2 shows an alarm condition being sent to the nurse and pharmacist to aid in their workflow (e.g., the nurse will pick up the next package of medication from the pharmacist and the pharmacist is informed that the infusion is nearing completion, which is the cue to prepare for the nurse to come and get the next package of medication for infusion). As can be seen in the embodiment shown in FIG. 2, pump 12 is in communication with the dispatching system 14 so that pump 12 sends status data about pump 12 to the dispatching system 14. Such status data includes, but is not limited to, patient biometric, physiological or medical parameter information, the location of pump 12 and the type and amount of medication administered by the pump 12. In addition, pump 12 sends event data to the dispatching system 14. Such event data includes, but is not limited to, information indicating that the infusion is nearing completion. Further, pump 12 sends alarm data to the dispatching system 14. Alarm data, as used in this specification, means all notifications that can benefit physicians, clinical staff or patients in handling the operation and safety of the pump 12.


Although the patient care system 10 described herein interacts with one or more pumps 12, the pumps 12 are not required to be part of the patient care system 10. However, as described hereafter, various aspects of the functionality of the patient care system 10 may be shared with the pump 12 so that in some embodiments the pump 12 may be part of the patient care system 10.


Besides receiving data from a pump 12, the dispatching system 14 may also send programming data to the pump 12. Such programming data may reconfigure the parameters and operation of the pump 12 with respect to both infusing of medication by the pump 12 and the type, amount and frequency of data gathered by the pump 12 and sent to the dispatching system 14. Further, dispatching system 14 may also send drug library data to the pump 12 which may then be used by pump 12 to configure limits and infuser settings to be used in the infusion of medication to the patient. In addition, the dispatching system 14 may send software updates to the pump 12 so that pump 12 has the most current software for its operations.


Dispatching system 14 interacts with alarm forwarding system 16 to forward alarms generated by the dispatching system 14 according to the appropriate recipient according to rules, algorithms or instructions. These rules, algorithms or instructions can, in part, be based on or take into consideration the clinical care area (CCA), patient identification, alarm priority, location of the pump 12 and the type of drug being infused by the pump 12. The rules, algorithms or instructions can be fixed and predetermined or can be customizable by the hospital or healthcare facility according to their own preferred practice or other practices recommended by others. An example of an appropriate recipient is the nurse who is caring for a patient that is receiving therapy from a pump 12. Further, where the alarms are sent to appropriate recipients, who that recipient is or the location where the alarm was forwarded may also be indicated or displayed on the pump 12 itself.


Dispatching system 14 may also communicate data, raw or processed by the dispatching system 14, to a clinical system 24 through an interface 22. Interface 22 provides a connection between the dispatching system 14 and a clinical system 24. The clinical system 24 may be another network (separate or interconnected with the network of dispatching system 14) where such network communicates information to the appropriate recipients such as the nurse having supervisory responsibility for the nurse caring for a patient that is receiving therapy from a pump 12, a physician overseeing the care of the patient, a pharmacist preparing medication for the patient or any combination of these or others having a need to know the status of the infusion therapy being applied to a patient through a pump 12. Examples of the data that can be communicated from the dispatching system 14 to and from the clinical system 24 via the interface 22 and from the clinical system 24 to an appropriate recipient includes, but is not limited to, the raw data produced by the pump 12 such as pump status data, pump event data and alarms associated with pump 12 or rules, results and data that has been processed by the dispatching system 14 or alarm forwarding system 16.


Further, the clinical system 24 allows appropriate personnel, such as the physician overseeing the care of the patient, to interface with and ultimately control or change the operation of the pump 12. For example, a physician through the clinical system 24 could modify the infusion parameters of the pump 12 by sending an infusion order to the clinical system 24 that passes through the interface 22, dispatching system 14 and ultimately to the pump 12. Further, new or modified programming data for the pump 12 may be entered into the clinical system 24, passed through the interface 22 to the dispatching system 14 and ultimately to the pump 12 where the current programming of pump 12 is either modified or replaced, preferably in an automated and/or remote manner.


Interface 22 likewise allows appropriate personnel to administer the rules used to control alarm forwarding in the system via a rule editor available on monitor/control device 18 or clinical system 24. The administration interface would allow the hospital personnel to determine rules for what contents from a data message from pump 12 would cause an alarm message to be generated. For example, an administrator could determine that an alarm would be generated whenever a certain kind of medication was interrupted, even if only temporarily, while the interruption of a different kind of medication did not generate an alarm unless the interruption was of a sufficient duration. The administration interface could also allow the hospital personnel to determine rules for what contents from a data message from pump 12 would control how and if certain alarm messages would be suppressed. For example, an administrator could determine that an alarm message generated based on a data message regarding a life critical or otherwise high risk drug, such as analgesics, sedatives or anticoagulants like Heparin for example, would not be suppressed at all, an alarm message generated based on a data message regarding a less critical drug could be locally suppressed at the device but could not be cleared remotely, and an alarm message generated based on a data message regarding a noncritical drug could be both locally suppressed at the device and cleared remotely.


An example of how information flows in patient care system 10 can be described with references to FIG. 3. The main communication nodes in FIG. 3 include pump 12, dispatching system 14, alarm forwarding system 16, alarm destinations or monitor/controlling systems 18, the patient, nurse, telemedicine personnel, and pharmacist. As can be seen, an exemplary alarm condition 23, “Nearing the End of Infusion,” is communicated from the pump 12 to the dispatching system 14. The dispatching system 14, operating according to an algorithm 25 for this alarm condition, sends the “Nearing the End of Infusion” alarm 23 to the alarm forwarding system 16, which broadcasts, according to its rules or algorithms 25 to the monitor/controlling system 18 and clinical system 24 through the interface 22 (FIG. 2). Alternatively or in addition, the dispatching system 14 can send the alarm 23 to the interface 22 where it is subsequently passed to the clinical system 24 where it passes to the appropriate personnel such as the nurse, pharmacist or physician. In this way, multiple alarm messages are sent in parallel to the appropriate personnel according to the operation of the algorithm 25 operating on the dispatching system 14. Further, in a variant of this embodiment, an initial alarm message may be forwarded from a recipient of such alarm message to another person not initially sent the alarm message in a so-called “serial forwarding” fashion. Further, to avoid the same alarm being received by multiple devices at different times, which could give the mistaken impression that there are more alarms than there actual are, alarm messages can be synchronized when dispatched to multiple recipients (e.g., various monitor/controlling systems 18 such as a mobile tablet and a nurse station) so that the alarm messages arrive at the same time.


The administration interface could also be used to control how certain alarm messages flowed in patient care system 10. For example, the rules applied to alarm messages by alarm forwarding system 16 could be configurable so that alarm messages pertaining to life critical drugs were forwarded to various monitor/controlling systems 18 in parallel while alarm messages pertaining to less critical drugs were forwarded to a single monitoring system 18 and serially forwarded to another monitoring system 18 only in the event that the alarm was not acknowledged.


As can also be seen, the dispatching system 14 may receive an acknowledgment message 27 from the appropriate personnel, in this case, the nurse. Upon receipt of an alarm message, the nurse may send an acknowledgment message acknowledging receipt of the alarm message. Once again, the rules, algorithms or instructions 25 operating on dispatching system 14 for this alarm condition processes the acknowledgment and determines if additional action needs to be taken. For example, if an acknowledgment message is not received within a predetermined time, the algorithm could instruct the pump 12 to issue a local alarm to alert those caring for the patient in the vicinity of the patient of this alarm condition. Of course, if the alarm condition is acknowledged before the predetermined time has expired 29, no such local alarm may be required as defined by the algorithm 25 and thus no local alarm will sound by pump 12.


In embodiments of patient care system 10 where an alarm condition has been forwarded to the dispatching system 14, it is desirable, but not required, to indicate on the pump 12 that an alarm occurred and that it has been forwarded. Further, in situations where the local alarm is suppressed, it is desirable, but not required, that the time remaining before the alarm sounds or is otherwise indicated locally on the pump 12 be displayed so that the clinician located in the vicinity of pump 12 may see and act upon this information appropriately.


Further, a desirable function of the patient care system 10 is the capability to have confirmation that an alarm has been successfully delivered. As shown in FIGS. 3 and 4, the algorithm 25 running on dispatching system 14 could, if so defined, send a “successfully forwarded” message 31 back to the pump 12 after alarm messages have been sent to the appropriate personnel by the dispatching system 14 as described above. This “successfully forwarded” message 31 could be processed by the rules, algorithms or instructions 25 on dispatching system 14, alarm forwarding system 16 or pump 12 software and rules, algorithms or instructions to take action as defined by such software and rules, algorithms or instructions. For example, beyond just delivering such a “successfully forwarded” message 31 to the pump 12, the “successfully forwarded” message 31 may be displayed, including by activation of an audible, visual or tactile messaging systems as described herein to alert an appropriate caregiver of such receipt.


Each combination of alarm forwarding, acknowledgment, and particular kinds of suppression can be referred to as a suppression protocol. For example, the combination of suppressing a local auditory alarm until either a set time has elapsed or an alarm forwarding confirmation or acknowledgment was received is a first suppression protocol, while the combination of suppressing a remote alarm to a supervisor until either a set time has elapsed or a primary care giver cleared an alarm locally at the medical device is a second suppression protocol. Various suppression protocols can be created by hospital personnel via use of the rules editor mentioned previously, which can in one embodiment be incorporated into the Hospira MedNet™ software. The various suppression protocols can further be selectively applied by the care system based on the content of medical device data messages, alarm messages, and other information available to the system. As such, particularly stringent suppression protocols can be applied to low priority alarms automatically while more lax suppression protocols are applied to higher priority alarms.


In all of the above situations in which the content of a data message from pump 12 or the content of an alarm message were used to control the manner in which an alarm was generated, suppressed, or forwarded, the clinical care area (CCA) of the pump or medical device 12 can be used additionally or in the alternative as an input to a rule or can be used to select which rule should to be applied. This functionality provides significant benefits in that an alarm forwarding protocol or alarm suppression protocol might be appropriate for a given medical situation in one CCA and not appropriate in another. For example, the temporary interruption of a basic saline drip may be a low priority alarm towards which a stringent suppression protocol is applied in one CCA while the same medical event is a high priority in a level 4 NICU where the slightest divergence from a planned treatment can be more problematic for the patient. The CCA can be received as an input for any of these determinations by first being programmed into the medical device when it is deployed or provided in a drug library downloaded to the medical device, and subsequently selected by the clinician on the device so that the selected CCA information is delivered as part of the data message generated by the medical device 12. In the alternative, the CCA can be determined indirectly from the data message and/or alarm message by conducting a lookup operation on a database associated with a server that is in communication with a plurality of the medical devices in the healthcare facility. For example, an ID number associated with a pump could be received in a data message and then applied to a database to lookup the CCA area in which the pump had last been deployed, programmed in, or heard from via the network.



FIG. 4 shows the operation of one possible function of the patient care system 10. In this function, the dispatching system 14 and alarm forwarding system 16 are shown as separate systems. But, as described above, it is intended to be within the scope of the invention that the dispatching system 14 and alarm forwarding system 16 be combined into a single system or software module that performs the functions of the dispatching system 14 and alarm forwarding system 16 as described herein. Further, as can be seen in FIG. 4, the medical pump 12 itself may operate according to certain algorithms and may itself perform some of the functionality of the dispatching system 14 and alarm forwarding system 16.


In this example, if an alarm condition occurs at 26, the pump 12 generates an alarm condition message at 28. This alarm condition message is sent from pump 12 to the dispatching system 14 where the alarm condition message is evaluated at 30. The alarm condition message preferably includes information relevant to the alarm such as pump 12 ID, the patient ID/name, location of pump 12 and type/concentration/name of drug used. Pump 12 gets acknowledgement from the server of the dispatching system 14 that it received the alarm and acknowledgement from the forwarding system 16 and/or the alarm destination or recipient entity.


The evaluation at 30 occurs according to rules, algorithms or instructions established in the dispatching system 14. If, at step 30, it is determined that the alarm condition received from pump 12 should be passed to the alarm forwarding system 16 to be managed, the alarm condition is passed to the alarm forwarding system 16 where it is received at step 32. Alarm forwarding system 16 then forwards the alarm condition to the appropriate personnel via monitor/controlling systems 18 according to the rules, algorithms or instructions established in alarm forwarding system 16 for that particular alarm condition. Alarms have different priorities and repeat rates and require different responses. As a result, the rules, algorithms or instructions established in alarm forwarding system 16 determine which alarms get priority when one or more alarms are present at the same time as well as the appropriate routing, timing and display of alarm information in alarm conflicts. Further, the rules, algorithms or instructions established in alarm forwarding system 16 determine how, when and by whom alarms may be cancelled or suppressed, particularly in alarm conflict situations.


The monitor/controlling system 18 to which the alarm forwarding system 16 forwards the alarm condition may be any of a number of devices such as a pager, mobile phone, wireless device, tablet, workstation, email or any other form of communication that is able to communicate with the alarm forwarding system 16 and communicate information to the appropriate personnel. In the embodiment shown, the dispatching system 14 itself evaluates, according to rules, algorithms or instructions established in the dispatching system 14, whether the alarm condition received from pump 12 should be passed to the alarm forwarding system 16 to be managed. In an alternate embodiment, the dispatching system 14 contains no such evaluation system but instead passes the alarm message directly to the alarm forwarding system 16.


Upon receipt of an alarm condition message by the alarm forwarding system 16 at 32, in the embodiment shown, the program passes to step 34 where it is determined whether the alarm forwarding system 16 is configured to send a “successfully received” acknowledgment of the alarm condition message. If the alarm forwarding system 16 is so configured, the program passes from step 34 to step 36 where a “successfully received” acknowledgment message is generated and sent from the alarm forwarding system 16 to the dispatching system 14.


The “successfully received” message sent from alarm forwarding system 16 is received at the dispatching system 14 at step 38. Step 38 determines whether the alarm condition message originally generated by pump 12 and passed to dispatching system 14 was successfully forwarded to the alarm forwarding system 16. If, according to the logical operations of this step 38, the alarm condition message was not received by the alarm forwarding system 16, the program passes to step 40 where an escalation scheme is entered. The escalation scheme includes a determination, by rules, algorithms or instructions, of the appropriate response when an alarm condition message has not been acknowledged. Examples of such an appropriate response could be resending the alarm condition message, sending the alarm condition message to another monitor/controlling system 18, triggering a local display of the alarm condition on the pump 12, causing the display of an alarm alert condition at some other device, or any other appropriate response as determined by those having care of the patient and which have been programmed into the rules, algorithms or instructions operating on the dispatching system 14.


If the alarm condition message generated by pump 12 was ultimately received by the alarm forwarding system 16, then at step 38 a confirmation message is automatically sent to both steps 42 and 44 which are processed on the pump 12 by the operation of the logic 52 as explained above. At step 42, whether the alarm condition message was successfully forwarded to alarm forwarding system 16 is evaluated. If the alarm condition message was not successfully forwarded to the alarm forwarding system 16, the program passes to step 46 where a local alarm is visually displayed. If however, it is ascertained at step 42 that the alarm condition was successfully received by the alarm forwarding system 16, the program passes to step 48 where no local alarm is displayed by pump 12.


In this embodiment, pump 12 includes a local delay timer 50 as described above. Such a local delay timer 50 is activated when an alarm condition message is sent at step 28 by the pump 12 to the dispatching system 14. As mentioned, at step 38 the dispatching system 14 determines whether the alarm condition message generated by pump 12 was received by the alarm forwarding system 16. If the alarm condition message was ultimately received by the alarm forwarding system 16, the program also passes to step 44. Step 44 determines whether to cause the local delay timer 50 to cease. This determination at step 44 occurs according to rules, algorithms or instructions. In particular, this determination preferably takes into consideration whether an acknowledgment of receipt of an alarm message 54 has been sent by medical personnel at 58 and ultimately passed through steps 60 and 62 to step 54 where an acknowledgment message is sent from step 54 to step 44. Logic 52 (FIG. 1 or general arrow in FIG. 4) within pump 12 is set up to send a local alarm message if the local delay timer 50 (FIG. 1) exceeds its allotted time and preferably under the rules, algorithms and rules governing step 44, where no acknowledgment of an alarm condition message is received from the dispatching system 14 via step 54. However, upon receipt of an acknowledgement of an alarm condition message from the dispatching system 14 at 54, the local delay timer 50 ceases counting and no local alarm message is generated. The length of the delay set in the local delay timer 50 can be set, for example, according to the priority of the type of alarm 28 generated or the type/concentration/name of drug being infused by the pump 12. Further, if receipt of an acknowledgement of an alarm condition message arrives from step 54 after the timeout of the local delay timer 50, and as a result a local alarm has already started, according to rules, algorithms or instructions, the patient care system 10 can stop the local alarm, restart the local delay timer 50 or both.


Receipt at the monitor/controlling system 18 of an alarm condition causes the monitor/controlling system 18 to display the alarm condition at 56. This display may take the form of visual, audible or tactile displays. For example, the display may cause an audible alarm to sound indicating to the clinician the receipt of an alarm condition message. Further, the display may, on a viewing screen, display information related to the alarm condition message. In addition, the display may include activation of a visual indicator of the receipt of an alarm condition message such as a flashing light. Finally, the display may take the form of a tactile display such as a vibrating device indicating to the clinician the receipt of an alarm condition message. This list of possible displays is intended to illustrate possible displays or indications that a monitor/controlling system 18 may use. However, it is to be understood that this list is illustrative and not intended to be limiting. As a result, it is intended that any type of display that attracts the attention of the clinician to the receipt of an alarm condition message or displays or otherwise communicates the contents of an alarm condition message is intended to be within the scope of the present patient care system 10.


Upon receipt of an alarm condition message by a monitor/controlling system 18, the clinician may send an “acknowledgment of receipt” message back to the dispatching system 14 if their destination device permits two-way communication. Generating and sending such an acknowledgment message occurs at the monitor/controlling system 18 at 58. The acknowledgment receipt message is sent from the monitor/controlling system 18 to the alarm forwarding system 16 at 60 where the acknowledgment of the receipt of the alarm condition message is passed to the dispatching system 14 at 62. Step 62 determines whether the alarm message 28 previously sent from the dispatching system 14 has been acknowledged. If it has not, the program passes to 40 where an escalation scheme is determined according to rules, algorithms or instructions.


If, at step 62, it has been determined that an alarm condition acknowledgment message has been received, the program passes to step 54 where acknowledgment message is sent from the dispatching system 14 to the pump 12 at 44. This alarm condition 28 is evaluated at 64 to determine, according to rules, algorithms or instructions, if this alarm condition requires the display of a local alarm on pump 12. Whether such an alarm condition 28 requires the display of a local alarm on pump 12 is determined according to certain rules, algorithms or instructions that have been programmed into the pump 12. If the alarm condition 28 requires that a local alarm be displayed on pump 12, such an alarm is displayed at 46. If the alarm condition 28 does not require that a local alarm be displayed, the program advances to 42 where it is evaluated whether the alarm condition was successfully forwarded to appropriate personnel through the dispatching system 14 and alarm forwarding system 16.


The creation of an alarm condition at 26, in addition to the sending of an alarm condition message at step 28, also causes the program operating according to the logic 52 on pump 12 to move to step 66 where it is determined, according to rules, algorithms or instructions, whether pump 12 is configured to suppress the local alarm audio alarm. Determining whether pump 12 is configured to express the local alarm audio alarm is done according to rules, algorithms or instructions programmed on the pump 12.


If, at step 66, it is determined, according to rules, algorithms or instructions, that the pump 12 is configured to suppress the local audio alarm, the program advances to step 68 where it is evaluated whether to delay or suppress the local audio alarm based on its rules, algorithms or instructions including, but not limited to, reference to the current stage of the local delay timer 50. If, at step 68, it is determined that the local audio alarm should be suppressed, the program passes to step 70. Step 70 determines whether the local delay timer 50 has exhausted its predetermined delay time and the alarm condition still persists. If the local delay timer 50 has exhausted its local delay time and the alarm condition still persists, the program passes to step 72 where pump 12 provides a local audio alarm even though the alarm had previously been determined to be suppressed. The reason the alarm suppression is overridden in this embodiment is that the failure to receive an acknowledgment of receipt of an alarm notice, as evidenced by the local delay time 50 timing out, has been determined, according to rules, algorithms or instructions, to require an alarm to be generated. Also, according to rules, algorithms or instructions, the alarm can be generated immediately or can be generated after taking further action (e.g., resending the alarm message to see if an acknowledgment or receipt of the alarm message returns). If at step 66 it is determined that pump 12 is not configured to suppress a local audio alarm indication, the program passes to step 72 where pump 12 provides a local audio alarm. Either or both a local audio or visual alarm can be produced at 46 and 72.


Although embodiments of the patient care system 10 discussed above had the alarm forwarding system 16 sending a “successfully received” acknowledgment of the alarm condition message, this is not required for the patient care system 10. Further, although those embodiments of the patient care system 10 had an escalation scheme 40, that also is not required for the patient care system 10. Similarly, various explicit acts, evaluations, messages sent or suppressed, alarms activated or suppressed and similar aspect of the embodiment described above and with respect to other embodiments shown may be eliminated or added in a wide variety of permutations and combinations and still fall within the scope of the invention. Patient care system 10 allows for the management of alarms in all varieties of the term “management.” The various aspects of “managing” alarms given in this description are intended to be illustrative and not limiting.



FIG. 5 indicates the interrelationship between an administrator, such as an information technology (IT) specialist, a biomedical engineer, or a nurse or other clinician with responsibility for care of a patient, with the pump 12 through dispatching system 14, alarm forwarding system 16, and monitor/controlling system 18. Where the administrator desires to configure the pump 12 at 74, the administrator sends a command through the monitor/controller system 18 at 76.


Where an administrator desires to reconfigure a pump 12, the monitor/controller system 18 “pings” the alarm forwarding system 16 at 78 to determine which pumps 12 are available for configuration. The alarm forwarding system 16 then “pings” the dispatching system 14 at 80 to determine which pumps 12 are available for configuration. The pumps 12 in communication with dispatching system 14 send their identification information and data to dispatching system 14 at 82. This can be a near real time push of data from the pumps 12 to the dispatching system 14 or the data can be pulled in response to a request or “ping” of the pumps by the dispatching system 14. Dispatching system 14 then sends information about the available pumps 12 to the alarm forwarding system 1610 at 84 where such information is sent to the monitor/controller system 18 at 86 where the monitor/controller 18 displays the relevant information about this particular pump 12 including the current status of the pump and the range of available options for reconfiguration. By monitor/controlling system 18 displaying this information, the information is made available to the administrator.


Once the administrator has determined which pumps 12 are available for configuration, the administrator selects the pump 12 to be configured at 88. The administrator makes the desired selection on the monitor/controller system 18 which then displays the newly configured settings about this particular pump 12 at 90. Once the administrator has entered the particular parameters for configuration of the desired pump 12 on the monitor/controlling system 18, the monitor/controller system 18 passes this information to the alarm forwarding system 16 at 92 which sends the information to the dispatching system 14 at 93 where the parameters configuration are sent to the selected pump 12 by the dispatching system 14 where they are received by the pump 12 at 94 and implemented on the pump 12 at 95.


A similar process is employed for the administrator to configure the dispatching system 14, alarm forwarding system 16 or the monitor/controller system 18 itself. If the monitor/controller system 18 itself is to be configured, the configuration can take place directly by entering the new configurations on the monitor/controlling system 18. However, it may be desirable to alert others through the dispatching system 14 or clinical system 24 of such configuration changes. In that case, the monitor/controller system 18 sends the configuration information to the alarm forwarding system 16 which sends this information to the dispatching system 14 which then sends the information, according to rules, algorithms or instructions on the dispatching system 14, to the appropriate locations.


Where the alarm forwarding system 16 is to receive new configurations, configurable aspects of the alarm forwarding system 16 are displayed on the monitor/controller system 18. The desired configurations for the alarm forwarding system 16 are entered into the monitor/controlling system 18 which then sends the new configurations to the alarm forwarding system 16 to be implemented. Again, it may be desirable to alert others through the dispatching system 14 or clinical system 24 of such configuration changes. In that case, the alarm forwarding system 16 sends the configuration information to the dispatching system 14 which then sends the information, according to rules, algorithms or instructions on the dispatching system 14, to the appropriate locations.


Where the dispatching system 14 is to receive new configurations, configurable aspects of the dispatching system 14 and alarm forwarding system 16 are received from the dispatching system 14, passed through the alarm forwarding system and displayed on the monitor/controller system 18. The desired configurations for the dispatching system 14 are entered into the monitor/controlling system 18 which then sends the new configurations to be implemented by the dispatching system 14. Again, it may be desirable to alert others through the dispatching system 14 or clinical system 24 of such configuration changes. In that case, the dispatching system 14 sends the information, according to rules, algorithms or instructions on the dispatching system 14, to the appropriate locations.


In this embodiment, the interface 22 and clinical system 24 are not explicitly shown. However, the interface 22 and clinical system 24 may be incorporated into a monitor/controller system 18. However, it is to be understood that interface 22 and clinical system 24 may be separate and independent systems or that the functions of interface 22 and clinical system 24, in whole or in part, may be performed by the dispatching system 14, alarm forwarding system 16 or monitor/controlling system 18. Further, it is within the scope of the patient care system 10 that the function or elements or both of the dispatching system 14, alarm forwarding system 16, interface 22, clinical system 14 and monitor/controlling system 18 be combined in any permutation or combination of such functions or elements including into a single system.


The operation of the patient care system 10 with respect to the alarm forwarding function is shown in FIG. 6. When an alarm condition occurs at 26, pump 12 determines at 96 whether pump 12 is connected to the dispatching system 14. If pump 12 is not connected to the dispatching system 14, the program passes to step 98 where the pump displays a visual or audible alarm or both on pump 12 indicating that pump 12 is not connected to the dispatching system 14. If, at step 96, it is determined that the pump 12 is connected to the dispatching system 14, the program passes to step 100. At step 100, pump 12 sends an alarm condition notice to the dispatching system 14 where the dispatching system 14 receives the alarm condition notice at 102. In addition to sending an alarm condition notice to the dispatching system 14, the program passes from step 100 to step 104 where it is determined whether the pump 12 is configured to display a local alarm condition indicating that pump 12 is not connected to the dispatching system 14. If pump 12 is configured to display such a local alarm notice, the program passes to step 106 where such an alarm condition is displayed or otherwise indicated. If pump 12 is not configured to display such an alarm notice, the program passes to step 108 where action occurs, as will be discussed hereafter.


As mentioned above, when an alarm condition is generated at 26 and the pump 12 is connected to the dispatching system 14, an alarm condition message is sent at step 100 to the dispatching system 14 where it is received at step 102. At step 102, the alarm condition message is evaluated according to the rules, algorithms or instructions that determine whether the alarm condition message should be forwarded to the alarm forwarding system 16 or the monitor/controller system 18 or both. If, at step 102, it is determined that the alarm condition message should not be forwarded to either the alarm forwarding system 16 or monitor/controller system 18, the program passes to step 98 where the pump 12 will display or generate an alarm on the pump 12.


If, at step 102, it is determined that the alarm condition message should be forwarded to either the alarm forwarding system 16 or monitor/controller system 18, the program passes to step 110 in the alarm forwarding system 16. At step 110, the program determines, according to rules, algorithms or instructions, whether the alarm condition should be routed to a recipient and if so, which recipient. If it is determined that the alarm condition notice should be forwarded to a recipient, the program passes from step 110 in the alarm forwarding system 16 to step 112 in the monitor/controller system 18. In order for the program to reach step 110, an alarm condition message must have been received by the alarm forwarding system 16. Consequently, at step 110, the program passes to step 114 where it is determined whether the alarm forwarding system 16 is configured to send acknowledgment of a successful receipt of an alarm notice message. If the alarm forwarding system 16 is not configured to send such an acknowledgment, the program passes to 116 were no further action is taken. However, if the alarm forwarding system 16 is configured to send such an acknowledgement, the program passes to step 118 where such acknowledgment is generated by the alarm forwarding system 16 and sent to the dispatching system 14 to be received at step 120. If, at step 120, it is determined that the alarm condition message was successfully received by the alarm forwarding system 16, the program passes to step 108 in the pump 12.


If, at step 108, it is determined that the alarm condition message generated at step 100 was not received by the alarm forwarding system 16, the program passes to step 106 where an alarm condition indicating that the alarm condition message was not received by the alarm forwarding system 16 is displayed on the pump 12. If however, at step 108, it is determined that the alarm condition message generated step 100 was successfully received by the alarm forwarding system 16, the program passes to step 122 where no alarm is displayed locally on pump 12.


If, at step 120, it is determined that the alarm condition message received from pump 12 by the dispatching system 14 at step 102 has not been successfully forwarded to the alarm forwarding system 16, the program passes to an escalation scheme 40 where the appropriate level of escalation is determined according to rules, algorithms or instructions as discussed above. Also at step 120, if it is been determined that the alarm condition message generated by pump 12 and received by dispatching system 14 has also been successfully received by the alarm forwarding system 16, the program also passes to step 44 where the local delay timer 50 is canceled and no alarm message is generated.


If, in the monitor/controller system 18 at step 112, an alarm condition indication is indicated on a monitor/controlling system 18, the program passes to step 124 where the recipient of the alarm condition message is given the opportunity to acknowledge receipt of the alarm condition message. If the recipient chooses to generate an acknowledgment of the receipt of such a message, the program passes to step 126 in the alarm forwarding system 16 where the acknowledgement is passed to step 128 in the dispatching system 14. Step 128 ascertains whether the recipient has acknowledged receipt of the alarm condition message sent by pump 12. If the answer is yes, the program passes to step 130 where acknowledgment to send from the dispatching system 14 to step 44 where the local delay timer 50 is canceled and no alarm message is thus generated.


If an alarm condition indication is sent to a monitor/controlling system 18 at step 112, the program passes to step 132 where, according to rules, algorithms or instructions, it is ascertained whether the alarm condition is capable of remote clearing. If the alarm condition is not capable of remote clearing, the program passes to step 134 where no further action is taken. However, if the alarm condition is capable of remote clearing, the program passes to step 136 where the alarm may be cleared on the monitor/controlling system 18 by a qualified clinician.


The program then passes to step 138 in the alarm forwarding system 16. Step 138 passes the alarm clearing message to step 140 of the dispatching system 14 which passes the alarm clearing message to pump 12 at step 142. At step 142, the pump alarm is cleared on pump 12. If the pump alarm is cleared at step 142 on pump 12, the program passes to step 144 of the dispatching system 14. At step 144 the dispatching system 14 is notified that the alarm condition message previously generated by pump 12 at step 100 has been cleared remotely. The program then passes to step 146 on the alarm forwarding system 16 where a local alarm notification is sent to the appropriate recipients as determined by the rules, algorithms or instructions running on alarm forming system 16. Further, the program passes to step 148 in the monitor/controller system 18 where a local alarm condition is indicated on the appropriate monitor/controlling systems 18 indicating that an alarm condition notice has been cleared.


The program then passes to step 150 where it is determined whether the alarm condition has been resolved. If the alarm condition has been resolved, the program passes to step 152 on pump 12 where the alarm on pump 12 is cleared. If the program determined at step 150 that the alarm condition is not been resolved, the program passes to step 40 where an escalation scheme is entered into so that the appropriate action, according to the rules, algorithms or instructions previously determined, can be taken to resolve the alarm condition issue. At step 144, the program also passes to step 72 where, as described above, if the pump 12 is not configured to suppress a local edible alarm, pump 12 will provide a local audible alarm.


When an alarm gets cleared, either manually by a clinician or automatically according to the rules, algorithms or instructions running on the patient care system 10, a “clearing alarm message” may be sent to all the entities that received the original alarm. Such clearing alarm message may indicate how the alarm was cleared, when, and by whom and may include an indication of what the original alarm was, its timestamp and how the alarm was resolved. Further, although the alarm has been shown as being cleared in certain locations, the alarm may be cleared from wherever a clinician has access to the patient care system 10, whether at the pump 12, dispatching system 14, alarm forwarding system 16, clinical system server 24 or monitor/controlling system 18. It may be desirable to explicitly indicate or highlight on the pump 12 itself that the clearing took place remotely in order to alert the nearby attending personnel of the source of the clearing. In addition, if the alarm is locally cleared before it was cleared remotely, the dispatching system server 14 will receive notice of this occurrence and forward such notice to the remote recipients.


Further, it is desirable if the alarm is cleared remotely but not locally, that the local delay timer described above be employed to re-start the alarm sequence described herein after the expiration of a predetermined time in case a clinician clears the alarm remotely but forgets to check on the pump 12 and clear the alarm locally on the pump.



FIG. 7 illustrates an embodiment of the patient care system 10 where the infusion program operating on pump 12 is modified or replaced by an operator. In this embodiment of the patient care system 10, the pump 12 must be connected to the dispatching system 14 in order to be controlled by the monitor/controller system 18 as will be described hereafter. Further, the pump 12 must have an appropriate drug library with settings selected or configured by the manufacturer or more preferably the healthcare facility that allow the infusion program to be modified or replaced remotely from a monitor/controlling system for alarm management purposes. The drug library must be stored on the pump or otherwise be accessible to the pump 12. In this embodiment, an appropriate or authorized person, for example a nurse providing care to a patient, on their respective monitor/controller system 18 selects some aspect of the operation of the pump 12 with respect to the patient. For example, as shown in FIG. 7, at step 154, the clinician could select the infusion titrate. Consequently, at 156 the clinician accesses a programming screen on the monitor/controller 18. The clinician, at step 158, then enters the desired programming information on the programming screen of the monitor/controlling system 18. Thereafter, the process passes to step 160 where the clinician confirms the program information. The process then passes to step 162 where the monitor/controller system 18 sends the new program information to the alarm forwarding system 16 where it is received at step 164. At step 164, the alarm forwarding system sends the programming instructions to the dispatching system 14 where it is received at step 166. At step 166, the dispatching system 14 sends the program instructions to the infusion pump 12 where it is received and incorporated into the pump 12 at step 168. The pump 12 may act on the new or modified program instructions immediately as shown in FIG. 7 or may proceed in a delayed manner after local or remote confirmation.


As can be seen in the description of the patient care system 10, there are certain steps that are performed as part of the logic, whether software or by discrete logic on the various components of the patient care system 10 and pump 12. But, there are also certain steps that are performed by the clinician that are not part of or performed by such logic. Where a process involving the patient care system 10 involves steps performed by the clinician but that are not performed by the patient care system 10, whether in embodiments including the pump 12 or monitor/controller 18, the process steps performed by the clinician are not part of the patient care system 10.


Also as shown in FIG. 7, at 169 pump 12 sends confirmation to the dispatching system 14 that infusion by the pump 12 to the patient has started. The dispatching system 14 at 170 receives confirmation that the infusion by pump 12 was started and passes this information to the alarm forwarding system 16 at 172. At step 172, the alarm forwarding system 16 sends confirmation that the pump 12 has started infusion to the monitor/controller 18 at 174. At step 174, the monitor/controller system 18 displays a confirmation that the infusion by the pump 12 has started. At step 174, the monitor/controller system 18 displays that the infusion has started by the pump 12. This confirmation is also sent from the monitor/controller 18 to the dispatching system 14 at step 176 (via the alarm forwarding system 16). At step 176 the dispatching system 14 ascertains whether the infusion started by pump 12 is the desired infusion as programmed by the monitor/controller 18. If the infusion is not correct, the dispatching system 14 passes to step 40 where an escalation scheme is entered into and action taken according to the rules, algorithms or instructions set up in the escalation scheme.


Another management function of the patient care system 10 is shown in FIG. 8. In this function, a clinician transfers responsibility for one or more pumps 12 to another clinician. To access this functionality, both the clinician doing the transferring and the clinician receiving the transfer of responsibility for the pumps 12 must have appropriate access to the dispatching system 14 and alarm forwarding system 16, for example, through each clinician's respective monitor/controlling systems 18 with their appropriate interfaces. By accessing the monitor/controller system 18, at 178 the clinician selects a list of pumps 12 to be transferred. The process passes to step 180 where the clinician selects the monitor/controlling system 18 to which the responsibility for the pumps 12 will be transferred.


The process passes to step 182 where the monitor/controller 18 for the person passing responsibility for the pumps 12 then transfers the list of selected pumps 12 to the monitor/controlling system 18 of the person receiving responsibility for the pumps 12 via the alarm forwarding system 16 where this information is received at 184. At step 184, the alarm forwarding system 16 pushes the list of selected pumps to the selected monitor/controller 18 receiving responsibility for the pumps 12 at 186. At 186, the respective monitor/controlling system 18 displays the transferred list of pumps 12 and ask for confirmation of the transfer. The clinician associated with the new responsibility for the pumps 12 then, on their monitor/controlling system 18, accepts the pump list transfer at 188. Also, as a result of the clinician accepting the pump 12 transfer list, the monitor/controller 18 of that clinician then displays the list of newly acquired pumps 12 at 190.


A monitor infusion function of the patient care system 10 is displayed in FIG. 9. Pump 12 is configured to interact with the dispatching system 14. At 192, pump 12 sends non-alarm status information to the dispatching system 14 where it is received at 194. Examples of such non-alarm status information include, but are not limited to, the medication being delivered, the dose, rate, volume to be infused (VTBI) and duration of infusion. Step 194 forwards the non-alarm status information from pump 12 to the alarm forwarding system 16 where it is received at 196. Step 196 then routes the pump 12 non-alarm status information to the appropriate recipient or recipients as configured by rules, algorithms or instructions operating on the alarm forwarding system 16. Each recipient of the pump 12 non-alarm status information receives this status information at step 198 on their respective monitor/controller system 18. As a result, the monitor/controller system 18 displays the non-alarm status information from pump 12 so that the clinician can be apprised of such status. If a particular clinician's monitor/controlling system 18 is monitoring more than one pump 12, it can be set to select and display individual information about each pump 12. At step 200, the clinician selects a pump 12 to view that pump 12's non-alarm status details. As a result of selecting a particular pump 12 to monitor, the monitor/controller system 18 at 202 displays the non-alarm infusion status information for that pump 12.


The patient care system 10 may also include functionality that affects the duration that certain information is displayed on the monitor/controller system 18. An example of such functionality is shown in FIG. 9. From 202, the program may pass to step 204 which is a timer that times the amount of inactivity associated with the clinician's interaction with the monitor/controller system 18. If a sufficiently long amount of time elapses according to rules, algorithms or instructions without the clinician interacting with the monitor/controller system 18 (e.g., 10 seconds), the program passes to step 206 where the monitor/controlling system 18 closes the detailed view of the non-alarm status information provided by a particular pump 12. Of course, the amount of time that must pass before activating this closing of the detailed view can vary and may be selectable by the clinician to suit the clinician's preference or may be preset according to certain safety protocols. Further, this functionality includes, in addition to the length of time certain information is displayed, also determining what information is displayed and for both, may take into consideration who the clinician is, what the pump status is and the location of the clinician.


As a result of having transferred responsibility for one or more pumps 12 to another monitor/controlling system 18, the clinician may clear their monitor/controlling system 18 of the transferred pumps 12. Of course, the clinician must first have transferred responsibility for the pumps 12 as is done at step 208 where the process described above is summarized into a single step 208. Thereafter, the program passes to 210 where the clinician clears the pumps 12 that have been transferred. The program then passes to step 212 where the monitor/controlling system 18 clears the previously monitored pumps 12 which have now been transferred to another clinician.



FIG. 10 shows examples of the monitor/controlling system 18. Monitor/controlling system 18 may be a mobile phone, laptop computer, tablet or any other mobile device capable of interacting with the alarm forwarding system 16 and dispatching system 14, displaying information and allowing information to be entered and sent to the alarm forwarding system 16 and dispatching system 14. As can be seen in part A of FIG. 10, the status of devices being monitored located in several different locations (e.g., Bed 2, Bed 5 and Bed 7) can be displayed on a main status screen 214. The information displayed on the screen is the name of the pump 12 and the infusion status. Further as shown in part B of FIG. 10, the details of the infusion taking place by any particular pump 12 can be displayed once a pump 12 from the main status screen 214 is selected. For example, as can be seen in the example of part B of FIG. 10, where pump 12 is indicated as “Infuser 1” that is located at “Bed 2,” the status “Infusing” is indicated as well as the drug being infused, in this case “Dopamine.” Furthermore, the concentration of dopamine is indicated (5 mg/100 ml) as well as the dose (5 ml/hr), rate 10 (250 ml/hr) and VTBI (500 ml). A “patient” designation can of course be substituted for a “bed” designation without departing from the scope of the invention.


As shown in part C of FIG. 10, an alarm state can also be shown on the monitor/controller system 18. In this case, the pump 12 indicated as “Infuser 3” located at “Bed 2” is reaching the end of its infusion program. As a result, an “End of Infusion” 15 alarm message has been generated. One possible result of generating such an alarm message is that the monitor/controlling system 18 itself may indicate the alarm. In addition to indicating the status of particular pumps 12 (here, “End of Infusion”), the monitor/controlling system 18 may also activate a visual, audible or tactile alarm to alert the clinician of receipt of this alarm message.


Further, the order of display of the pumps 12 being monitored can be changed to represent the priority of their respective statuses. For example, as shown in part C of FIG. 10, the pump 12 designated “Infuser 3” at “Bed 2” is in a higher priority status than the other pumps 12 due to the presence of an alarm message associated with this particular pump 12. As a result, this pump 12 is listed higher on the display of the monitor/controlling system 18 than the other pumps 12 with lesser priority status in order to draw attention to this pump 12's heightened status.


Throughout this description, repeated mention has been made to “rules, algorithms or instructions.” These rules, algorithms or instructions can be directed to virtually anything that is determined to be useful including, but not limited to, promoting safety or improving efficacy, longevity or ease of use. In addition, where the clinician is configuring or reconfiguring a pump 12, these rules, algorithms or instructions can include safeguards to warn clinicians if certain configurations are outside of accepted bounds or are dangerous so that the clinician may be required to confirm such configurations before they are accepted by the patient care system 10. Further, where, when and to whom alarm messages may be forwarded or communicated to may take into consideration the staff available, clinical care area (CCA), therapy being delivered, type of drug, condition of the patient, time of day, day of the week, whether there has been or is an alarm escalation scheme 40 in effect to name but a few possible considerations.


The patient care system 10 described herein, in one or more of the embodiments disclosed, has advantages over current systems in increased patient safety and increased ease of use for the clinicians. With respect to increased patient safety, the patient care system 10 in one or more embodiments increases patient safety by sounding an alarm when the alarm forwarding does not reach clinical personnel or they are unable to respond to or acknowledge the alarm in a timely manner. In this way, the possibility of a clinician missing or failing to respond to an alarm is decreased. The possibility of a clinician missing or failing to respond to an alarm is also decreased, and thus patient safety is increased, by creating alarm escalation procedures that help medical personnel back up each other in case an initial alarm is missed or failed to be responded to. Further, patient safety increases with one or more embodiments of the patient care system 10 because reaction time by medical personnel to adverse infusion events or pending adverse infusion events is reduced. This reaction time is reduced by alerting medical personnel to such adverse event or pending adverse event even though the medical personnel is physically distant from the pump 12.


Additionally, patient safety is increased in one or more embodiments of the patient care system 10 by creating a system of alarm evaluation and dispatch that operates according to rules, algorithms or instructions so that alarm management logic is removed from the individual and various monitor/controller systems 18 and corresponding communication technology and is instead governed and controlled by a reduced set (in some cases, a single set) of rules, algorithms and instructions operating on a smaller number of devices (in some cases, on a single dispatching system 14).


Further, patient safety is increased in one or more embodiments of the patient care system 10 by allowing medical personnel to program or modify an infusion without exposing the patient to unnecessary contact or the requirement that the pump 12 be programmed at the pump 12 itself. Because the clinician does not need to be physically present or come in contact directly with the pump 12, the likelihood of contamination of the patient by the clinician is reduced. In addition, because the clinician does not need to be physically present or contact the pump 12 directly, the likelihood of cross contamination by multiple clinicians is reduced when multiple clinicians utilize the same infusion pump 12. In this way, the pump 12 is not contaminated by a clinician in the first place and even if the pump 12 were initially contaminated, cross-contamination is eliminated because subsequent clinicians do not need to come in contact with or be in close proximity to the pump 12 to change or modify programming on pump 12 or check the status of the pump 12 or an infusion program running on pump 12. If necessary confirmations or double checks of program values previously done at the pump 12 can be done by the clinician on the monitor/controlling system 18.


In yet other embodiments of the patient care system 10, patient safety increases by reducing the chance of incorrect therapy delivery. The chance of delivering an incorrect therapy is reduced because the clinician need only become familiar with a single interface (monitor/controlling system 18) instead of needing to gain familiarity with the interfaces on a large number of devices which might be involved in therapy delivery. Further, the chance of delivering an incorrect therapy is reduced in one or more embodiments because there are checks built into the rules, algorithms or instructions implemented on the patient care system 10.


The patient care system 10 also increases ease of use for the clinicians. With respect to increasing ease of use, in one or more embodiments of the patient care system 10, patient care system 10 allows medical personnel to clear alarms remotely instead of requiring the personnel to move to the pump 12 to clear the alarm. Further, in one or more embodiments of the patient case system 10, ease of use for medical personnel is increased by reducing the time necessary and the difficulty involved in modifying or updating programming and infusion program updates. Besides producing a simplified process for modifying or updating such programming, ease of use is increased by requiring the clinician to become familiar with only a single interface (e.g., monitor/controlling system 18) instead of the interfaces for each device that might be involved in therapy delivery.


In addition, the patient care system 10, in one or more embodiments, increases ease of use for medical personnel by sending alarm messages to medical personnel even 5 when they are not in proximity of the device (i.e., they are outside of visual and acoustic range of the pump 12). Further, in one or more embodiments, information that is useful or needed by the medical personnel about an alarm message such as the pump 12 ID, pump 12 location, patient information, drug information, program information, etc. are provided with the alarm message to aid such personnel in evaluating the alarm. As a result, medical personnel can have greater range from their patients and still deliver safe and effective therapy.


Another aspect of the patient care system 10 that increases ease of use for medical personnel in one or more embodiments of the patient care system 10 is that alarm noise in the hospital is reduced, which is beneficial—especially at night time. The reduction in alarm noise is due to the processing of alarms according to rules, algorithms or instructions to eliminate false or unnecessary alarms thereby producing fewer audible or visual alarms. Reducing the number of annoying distracting, false or unnecessary alarms benefits not only the medical personnel but the patient and other nearby patients as well.


Not all of these advantages will be present in every embodiment of the patient care system 10; some embodiments may have only one of these advantages while other embodiments will have more than one advantage and some embodiments may have all of the advantages. The disclosure has been directed to certain embodiments, combinations, configurations and relative dimensions. It is to be understood, however, that the description given herein has been given for the purpose of explaining and illustrating the invention and are not intended to limit the scope of the invention. It is to be further understood that changes and modifications to the descriptions given herein will occur to those skilled in the art. Therefore, the scope of the invention should be limited only by the scope of the claims.

Claims
  • 1. A system for managing alerts generated at an infusion pump with a mobile device, the system comprising one or more hardware processors configured to: receive a selection of a plurality of infusion pumps from a first clinician mobile device associated with a first clinician to be transferred to a second clinician mobile device associated with a second clinician;send the selection of the plurality of infusion pumps to an alarm forwarding system associated the plurality of infusion pumps;send the selection of the plurality of infusion pumps from the alarm forwarding system to the second clinician mobile device;generate a display showing the plurality of infusion pumps at the second clinician mobile device;receive a confirmation from the second clinician mobile device corresponding to acceptance of the transfer;receive a first alert from a first infusion pump from the plurality of infusion pumps;send the first alert from the alarm forwarding system to the second clinician mobile device; andgenerate a first user interface configured to be displayed on the second clinician mobile device, said first user interface including a detailed view of the first alert.
  • 2. The system of claim 1, wherein the first user interface including a detailed view of a non-alarm status information is closed after a time period.
  • 3. The system of claim 2, wherein the one or more hardware processors are further configured to generate a second user interface including a listing of the plurality of infusion pumps and their corresponding infusion status.
  • 4. The system of claim 1, wherein the one or more hardware processors are further configured to delay an audible alarm corresponding to an alarm condition at the first infusion pump for a time period responsive to the alarm condition being forwarded to the second clinician mobile device.
  • 5. The system of claim 4, wherein the one or more hardware processors are further configured to generate, at the first infusion pump, the audible alarm based on a determination that the alarm condition was not cleared by the second clinician mobile device.
  • 6. A method for managing alerts generated at an infusion pump with a mobile device, the method comprising: receiving a selection of a plurality of infusion pumps from a first clinician mobile device associated with a first clinician to be transferred to a second clinician mobile device associated with a second clinician;sending the selection of the plurality of infusion pumps to an alarm forwarding system associated the plurality of infusion pumps;sending the selection of the plurality of infusion pumps from the alarm forwarding system to the second clinician mobile device;generating a display showing the plurality of infusion pumps at the second clinician mobile device;receiving a confirmation from the second clinician mobile device corresponding to acceptance of the transfer;receiving a first alert from a first infusion pump from the plurality of infusion pumps;sending the first alert from the alarm forwarding system to the second clinician mobile device; andgenerating a first user interface configured to be displayed on the second clinician mobile device, said first user interface including a detailed view of the first alert.
  • 7. The method of claim 6, wherein the first user interface including a detailed view of a non-alarm status information is closed after a time period.
  • 8. The method of claim 7, further comprising generating a second user interface including a listing of the plurality of infusion pumps and their corresponding infusion status.
  • 9. The method of claim 6, further comprising delaying an audible alarm corresponding to an alarm condition at the first infusion pump for a time period responsive to the alarm condition being forwarded to the second clinician mobile device.
  • 10. The method of claim 9, further comprising, generating, at the first infusion pump, the audible alarm based on a determination that the alarm condition was not cleared by the second clinician mobile device.
  • 11. A method for managing alerts generated at an infusion pump with a mobile device, the method comprising: receiving a selection of a plurality of infusion pumps from a first clinician mobile device associated with a first clinician to be transferred to a second clinician mobile device associated with a second clinician;sending the selection of the plurality of infusion pumps to an alarm forwarding system associated the plurality of infusion pumps;sending the selection of the plurality of infusion pumps from the alarm forwarding system to the second clinician mobile device, wherein the plurality of infusion pumps are displayed at the second clinician mobile device;receiving a confirmation from the second clinician mobile device corresponding to acceptance of the transfer;receiving a first alert from a first infusion pump from the plurality of infusion pumps; andsending the first alert from the alarm forwarding system to the second clinician mobile device, wherein a detailed view of the first alert is displayed on as a first user interface on the second clinician mobile device.
  • 12. The method of claim 11, wherein the first user interface including a detailed view of a non-alarm status information is closed after a time period.
  • 13. The method of claim 12, further comprising generating a second user interface including a listing of the plurality of infusion pumps and their corresponding infusion status.
  • 14. The method of claim 11, further comprising delaying an audible alarm corresponding to an alarm condition at the first infusion pump for a time period responsive to the alarm condition being forwarded to the second clinician mobile device.
  • 15. The method of claim 14, further comprising generating, at the first infusion pump, the audible alarm based on a determination that the alarm condition was not cleared by the second clinician mobile device.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/846,882, entitled “Patient Care System with Conditional Alarm Forwarding,” filed Apr. 13, 2020, which is a continuation of U.S. patent application Ser. No. 16/408,272, entitled “Patient Care System with Conditional Alarm Forwarding,” filed May 9, 2019, which is a continuation of U.S. patent application Ser. No. 15/674,889, entitled “Patient Care System with Conditional Alarm Forwarding,” filed Aug. 11, 2017, which is a continuation of U.S. patent application Ser. No. 14/700,357, entitled “Patient Care System with Conditional Alarm Forwarding,” filed Apr. 30, 2015, which claims the benefit of priority to U.S. Provisional Patent Application No. 61/986,562, entitled “Patient Care System with Conditional Alarm Forwarding,” filed Apr. 30, 2014, the disclosures of which are hereby incorporated by reference in their entirety.

US Referenced Citations (1229)
Number Name Date Kind
4024864 Davies et al. May 1977 A
4055175 Clemens et al. Oct 1977 A
4151845 Clemens May 1979 A
4213454 Shim Jul 1980 A
4240438 Updike et al. Dec 1980 A
4280494 Cosgrove et al. Jul 1981 A
4308866 Jeliffe Jan 1982 A
4370983 Lichtenstein et al. Feb 1983 A
4373527 Fischell Feb 1983 A
4392849 Petre et al. Jul 1983 A
4395259 Prestele et al. Jul 1983 A
4457751 Rodler Jul 1984 A
4464170 Clemens Aug 1984 A
4469481 Kobayashi Sep 1984 A
4475901 Kraegen et al. Oct 1984 A
4494950 Fischell Jan 1985 A
4498843 Schneider et al. Feb 1985 A
4515584 Abe et al. May 1985 A
4526568 Clemens et al. Jul 1985 A
4529401 Leslie et al. Jul 1985 A
4543955 Schroeppel Oct 1985 A
4551133 Zegers de Beyl et al. Nov 1985 A
4553958 LeCocq Nov 1985 A
4559037 Franetzki et al. Dec 1985 A
4613937 Batty Sep 1986 A
4624661 Arimond Nov 1986 A
4633878 Bombardieri Jan 1987 A
4634426 kamen Jan 1987 A
4634427 Hannula et al. Jan 1987 A
4674652 Aten et al. Jun 1987 A
4676776 Howson et al. Jun 1987 A
4679562 Luksha Jul 1987 A
4685903 Cable et al. Aug 1987 A
4695954 Rose Sep 1987 A
4696671 Epstein et al. Sep 1987 A
4714462 DiDomenico Dec 1987 A
4722734 Kolin Feb 1988 A
4730849 Siegel Mar 1988 A
4731051 Fischell Mar 1988 A
4741732 Crankshaw et al. May 1988 A
4756706 Kerns et al. Jul 1988 A
4776842 Franetzki et al. Oct 1988 A
4785969 McLaughlin Nov 1988 A
4803625 Fu et al. Feb 1989 A
4835372 Gombrich et al. May 1989 A
4838275 Lee Jun 1989 A
4838856 Mulreany et al. Jun 1989 A
4838857 Strowe et al. Jun 1989 A
4854324 Hirschman et al. Aug 1989 A
4857716 Gombrich et al. Aug 1989 A
4858154 Anderson et al. Aug 1989 A
4898578 Rubalcaba, Jr. Feb 1990 A
4908017 Howson et al. Mar 1990 A
4933873 Kaufman et al. Jun 1990 A
4943279 Samiotes et al. Jul 1990 A
4946439 Eggers Aug 1990 A
4953745 Rowlett Sep 1990 A
4978335 Arthur, III Dec 1990 A
5000739 Kulisz et al. Mar 1991 A
5010473 Jacobs Apr 1991 A
5014698 Cohen May 1991 A
5016172 Dessertine May 1991 A
5026084 Paisfield Jun 1991 A
5034004 Crankshaw Jul 1991 A
5041086 Koenig et al. Aug 1991 A
5058161 Weiss Oct 1991 A
5078683 Sancoff et al. Jan 1992 A
5084828 Kaufman et al. Jan 1992 A
5088981 Howson et al. Feb 1992 A
5097505 Weiss Mar 1992 A
5100380 Epstein et al. Mar 1992 A
5102392 Sakai et al. Apr 1992 A
5104374 Bishko et al. Apr 1992 A
5109850 Blanco et al. May 1992 A
5131816 Brown Jul 1992 A
5142484 Kaufman et al. Aug 1992 A
5153827 Coutre et al. Oct 1992 A
5157640 Backner Oct 1992 A
5161222 Montejo et al. Nov 1992 A
5177993 Beckman et al. Jan 1993 A
5181910 Scanlon Jan 1993 A
5190522 Wocicki et al. Mar 1993 A
5199439 Zimmerman et al. Apr 1993 A
5200891 Kehr et al. Apr 1993 A
5216597 Beckers Jun 1993 A
5221268 Barton et al. Jun 1993 A
5230061 Welch Jul 1993 A
5243982 Möstl et al. Sep 1993 A
5244463 Cordner, Jr. et al. Sep 1993 A
5249260 Nigawara et al. Sep 1993 A
5256156 Kern et al. Oct 1993 A
5256157 Samiotes et al. Oct 1993 A
5261702 Mayfield Nov 1993 A
5317506 Coutre et al. May 1994 A
5319355 Russek Jun 1994 A
5319363 Welch Jun 1994 A
5330634 Wong et al. Jul 1994 A
5338157 Blomquist Aug 1994 A
5341476 Lowell Aug 1994 A
5364346 Schrezenmeir Nov 1994 A
5366346 Danby Nov 1994 A
5368562 Blomquist et al. Nov 1994 A
5373454 Kanda et al. Dec 1994 A
5376070 Purvis et al. Dec 1994 A
5378231 Johnson et al. Jan 1995 A
5389071 Kawahara et al. Feb 1995 A
5389078 Zalesky et al. Feb 1995 A
5417222 Dempsey et al. May 1995 A
5423748 Uhala Jun 1995 A
5429602 Hauser Jul 1995 A
5431627 Pastrone et al. Jul 1995 A
5432777 Le Boudec et al. Jul 1995 A
5445621 Poli et al. Aug 1995 A
5447164 Shaya et al. Sep 1995 A
5455851 Chaco et al. Oct 1995 A
5461365 Schlager et al. Oct 1995 A
5464392 Epstein et al. Nov 1995 A
5465082 Chaco Nov 1995 A
5485408 Blomquist Jan 1996 A
5486286 Peterson et al. Jan 1996 A
5493430 Lu et al. Feb 1996 A
5496273 Pastrone et al. Mar 1996 A
5505828 Wong et al. Apr 1996 A
5507288 Bocker et al. Apr 1996 A
5507786 Morgan et al. Apr 1996 A
5508499 Ferrario Apr 1996 A
5515713 Saugues et al. May 1996 A
5520637 Pager et al. May 1996 A
5522798 Johnson et al. Jun 1996 A
5547470 Johnson et al. Aug 1996 A
5554013 Owens et al. Sep 1996 A
5562615 Nassif Oct 1996 A
5577169 Prezioso Nov 1996 A
5582323 Kurtenbach Dec 1996 A
5582593 Hultman Dec 1996 A
5594786 Chaco et al. Jan 1997 A
5598519 Narayanan Jan 1997 A
5620608 Rosa et al. Apr 1997 A
5630710 Tune et al. May 1997 A
5636044 Yuan et al. Jun 1997 A
5643212 Coutre et al. Jul 1997 A
5651775 Walker et al. Jul 1997 A
5658131 Aoki et al. Aug 1997 A
5658250 Blomquist et al. Aug 1997 A
5665065 Colman et al. Sep 1997 A
5669877 Blomquist Sep 1997 A
5672154 Sillén et al. Sep 1997 A
5681285 Ford et al. Oct 1997 A
5685844 Marttila Nov 1997 A
5687717 Halpern et al. Nov 1997 A
5689229 Chaco et al. Nov 1997 A
5697899 Hillman et al. Dec 1997 A
5699509 Gary et al. Dec 1997 A
5713350 Yokota et al. Feb 1998 A
5713856 Eggers et al. Feb 1998 A
5718562 Lawless et al. Feb 1998 A
5719761 Gatti et al. Feb 1998 A
5733259 Valcke et al. Mar 1998 A
5738102 Lemelson Apr 1998 A
5744027 Connell et al. Apr 1998 A
5752621 Passamante May 1998 A
5754111 Garcia May 1998 A
5764034 Bowman et al. Jun 1998 A
5764159 Neftel et al. Jun 1998 A
5772635 Dastur et al. Jun 1998 A
5774865 Glynn Jun 1998 A
5778256 Darbee Jul 1998 A
5778345 McCartney Jul 1998 A
5781442 Engleson et al. Jul 1998 A
5782805 Meinzer et al. Jul 1998 A
5788669 Peterson Aug 1998 A
5797515 Liff et al. Aug 1998 A
5800387 Duffy et al. Sep 1998 A
5814015 Gargano et al. Sep 1998 A
5822544 Chaco et al. Oct 1998 A
5822715 Worthington et al. Oct 1998 A
5827179 Lichter et al. Oct 1998 A
5832448 Brown Nov 1998 A
5836910 Duffy et al. Nov 1998 A
5850344 Conkright Dec 1998 A
5867821 Ballantyne et al. Feb 1999 A
5870733 Bass et al. Feb 1999 A
5871465 Vasko Feb 1999 A
5873731 Predergast Feb 1999 A
5885245 Lynch et al. Mar 1999 A
5897493 Brown Apr 1999 A
5897498 Canfield, II et al. Apr 1999 A
5910252 Truitt et al. Jun 1999 A
5912818 McGrady et al. Jun 1999 A
5915240 Karpf Jun 1999 A
5920054 Uber, III Jul 1999 A
5920263 Huttenhoff et al. Jul 1999 A
5924074 Evans Jul 1999 A
5931764 Freeman et al. Aug 1999 A
5935099 Peterson et al. Aug 1999 A
5935106 Olsen Aug 1999 A
5941846 Duffy et al. Aug 1999 A
5956501 Brown Sep 1999 A
5957885 Bollish et al. Sep 1999 A
5960085 de la Huerga Sep 1999 A
5961448 Swenson et al. Oct 1999 A
5967559 Abramowitz Oct 1999 A
5971594 Sahai et al. Oct 1999 A
5975081 Hood et al. Nov 1999 A
5990838 Burns et al. Nov 1999 A
5997476 Brown Dec 1999 A
6000828 Leet Dec 1999 A
6003006 Colella et al. Dec 1999 A
6012034 Hamparian et al. Jan 2000 A
6017318 Gauthier et al. Jan 2000 A
6021392 Lester et al. Feb 2000 A
6024539 Blomquist Feb 2000 A
6024699 Surwit et al. Feb 2000 A
6032155 de la Huerga Feb 2000 A
6032676 Moore Mar 2000 A
6039251 Holowko et al. Mar 2000 A
6070761 Bloom et al. Jun 2000 A
6073106 Rozen et al. Jun 2000 A
6104295 Gaisser et al. Aug 2000 A
6112182 Akers et al. Aug 2000 A
6112323 Meizlik et al. Aug 2000 A
RE36871 Epstein et al. Sep 2000 E
6115390 Chuah Sep 2000 A
6122536 Sun et al. Sep 2000 A
6126637 Kriesel et al. Oct 2000 A
6135949 Russo et al. Oct 2000 A
6150942 O'Brien Nov 2000 A
6151643 Cheng et al. Nov 2000 A
6157914 Seto et al. Dec 2000 A
6159147 Lichter et al. Dec 2000 A
6167567 Chiles et al. Dec 2000 A
6182667 Hanks et al. Feb 2001 B1
6189105 Lopes Feb 2001 B1
6195589 Ketcham Feb 2001 B1
6208974 Campbell et al. Mar 2001 B1
6222323 Yamashita et al. Apr 2001 B1
6223440 Rashman May 2001 B1
6226277 Chuah May 2001 B1
6227371 Song May 2001 B1
6234176 Domae et al. May 2001 B1
6241704 Peterson et al. Jun 2001 B1
6248067 Causey, III et al. Jun 2001 B1
6249705 Snell Jun 2001 B1
6257265 Brunner et al. Jul 2001 B1
6259355 Chaco et al. Jul 2001 B1
6269340 Ford et al. Jul 2001 B1
6270455 Brown Aug 2001 B1
6271813 Palalau Aug 2001 B1
6277072 Bardy Aug 2001 B1
6280380 Bardy Aug 2001 B1
6283761 Joao Sep 2001 B1
6285665 Chuah Sep 2001 B1
6292860 Cochcroft, Jr. Sep 2001 B1
6312378 Bardy Nov 2001 B1
6327254 Chuah Dec 2001 B1
6330008 Razdow et al. Dec 2001 B1
6339718 Zatezalo et al. Jan 2002 B1
6346886 de la Huerga Feb 2002 B1
6363282 Nichols et al. Mar 2002 B1
6371719 Hildebrandt Apr 2002 B1
6377548 Chuah Apr 2002 B1
6388951 Matsumoto et al. May 2002 B1
6406426 Reuss et al. Jun 2002 B1
6408330 de la Huerga Jun 2002 B1
6418334 Unger et al. Jul 2002 B1
6427088 Bowman et al. Jul 2002 B1
6428483 Carlebach Aug 2002 B1
6442432 Lee Aug 2002 B2
6469991 Chuah Oct 2002 B1
6475180 Peterson et al. Nov 2002 B2
6482158 Mault Nov 2002 B2
6485418 Yasushi et al. Nov 2002 B2
6494694 Lawless et al. Dec 2002 B2
6494831 Koritzinsky Dec 2002 B1
6497680 Holst et al. Dec 2002 B1
6514460 Fendrock Feb 2003 B1
6517482 Eiden et al. Feb 2003 B1
6519569 White et al. Feb 2003 B1
6520930 Critchlow et al. Feb 2003 B2
6540672 Simonsen et al. Apr 2003 B1
6542902 Dulong et al. Apr 2003 B2
6544212 Galley et al. Apr 2003 B2
6544228 Heitmeier Apr 2003 B1
6546350 Hartmann et al. Apr 2003 B1
6551276 Mann et al. Apr 2003 B1
6554798 Mann et al. Apr 2003 B1
6558320 Causey et al. May 2003 B1
6558351 Steil et al. May 2003 B1
6565509 Say et al. May 2003 B1
6567416 Chuah May 2003 B1
6571294 Simmon et al. May 2003 B2
6572542 Houben et al. Jun 2003 B1
6572545 Knobbe et al. Jun 2003 B2
6578002 Derzay et al. Jun 2003 B1
6581117 Klein et al. Jun 2003 B1
6587034 Heiman et al. Jul 2003 B1
6589229 Connelly et al. Jul 2003 B1
6599281 Struys et al. Jul 2003 B1
6602191 Quy Aug 2003 B2
6605072 Struys et al. Aug 2003 B2
6628809 Rowe et al. Sep 2003 B1
6631353 Davis et al. Oct 2003 B1
6640246 Gardy, Jr. et al. Oct 2003 B1
6641533 Causey, III et al. Nov 2003 B2
6647299 Bourget Nov 2003 B2
6652455 Kocher Nov 2003 B1
6653937 Nelson et al. Nov 2003 B2
6659947 Carter et al. Dec 2003 B1
6669630 Joliat et al. Dec 2003 B1
6671563 Engleson et al. Dec 2003 B1
6673033 Sciulli et al. Jan 2004 B1
6674403 Gray et al. Jan 2004 B2
6681003 Linder et al. Jan 2004 B2
6689091 Bui et al. Feb 2004 B2
6692241 Watanabe et al. Feb 2004 B2
6694191 Starkweather et al. Feb 2004 B2
6694334 DuLong et al. Feb 2004 B2
6721286 Williams et al. Apr 2004 B1
6721582 Trepagnier et al. Apr 2004 B2
6725200 Rost Apr 2004 B1
6731989 Engleson et al. May 2004 B2
6740072 Starkweather et al. May 2004 B2
6751651 Crockett Jun 2004 B2
6752787 Causey, III et al. Jun 2004 B1
6753830 Gelbman Jun 2004 B2
6758810 Lebel et al. Jul 2004 B2
6773396 Flach et al. Aug 2004 B2
6774786 Havekost et al. Aug 2004 B1
6775577 Cmkovich et al. Aug 2004 B2
6780156 Haueter et al. Aug 2004 B2
6790198 White et al. Sep 2004 B1
6796956 Hartlaub et al. Sep 2004 B2
6799149 Hartlaub Sep 2004 B2
6809653 Mann et al. Oct 2004 B1
6811534 Bowman, IV et al. Nov 2004 B2
6816605 Rowe et al. Nov 2004 B2
6839753 Biondi et al. Jan 2005 B2
6852104 Blomquist Feb 2005 B2
6859134 Heiman et al. Feb 2005 B1
6871211 Labounty et al. Mar 2005 B2
6873268 Lebel et al. Mar 2005 B2
6876303 Reeder et al. Apr 2005 B2
6885881 Leonhardt Apr 2005 B2
6891525 Ogoro May 2005 B2
6892278 Ebergen May 2005 B2
6899695 Herrera May 2005 B2
6915170 Engleson et al. Jul 2005 B2
6923763 Kovatchev et al. Aug 2005 B1
6924781 Gelbman Aug 2005 B1
6928338 Buchser et al. Aug 2005 B1
6928490 Bucholz et al. Aug 2005 B1
6936029 Mann et al. Aug 2005 B2
6945954 Hochman et al. Sep 2005 B2
6948492 Wemeling et al. Sep 2005 B2
6958677 Carter Oct 2005 B1
6958691 Anderson et al. Oct 2005 B1
6958705 Lebel et al. Oct 2005 B2
6961448 Nichols et al. Nov 2005 B2
6969352 Chiang et al. Nov 2005 B2
6969865 Duchon et al. Nov 2005 B2
6974437 Lebel et al. Dec 2005 B2
6979326 Mann et al. Dec 2005 B2
6980958 Surwit et al. Dec 2005 B1
6985870 Martucci et al. Jan 2006 B2
6986347 Hickle Jan 2006 B2
6997880 Carlebach et al. Feb 2006 B2
6997920 Mann et al. Feb 2006 B2
6998984 Zittrain Feb 2006 B1
7017293 Riley Mar 2006 B2
7025743 Mann et al. Apr 2006 B2
7029455 Flaherty Apr 2006 B2
7038584 Carter May 2006 B2
7060031 Webb et al. Jun 2006 B2
7060059 Keith et al. Jun 2006 B2
7069552 Lindberg et al. Jun 2006 B2
7072725 Bristol et al. Jul 2006 B2
7079035 Bock et al. Jul 2006 B2
7092943 Roese et al. Aug 2006 B2
7096072 Engleson et al. Aug 2006 B2
7099809 Dori Aug 2006 B2
7103419 Engleson et al. Sep 2006 B2
7103578 Beck et al. Sep 2006 B2
7107106 Engleson et al. Sep 2006 B2
7108680 Rohr et al. Sep 2006 B2
7109878 Mann et al. Sep 2006 B2
7114002 Okumura et al. Sep 2006 B1
7117041 Engleson et al. Oct 2006 B2
7136645 Hanson et al. Nov 2006 B2
7137964 Flaherty Nov 2006 B2
7142190 Martinez Nov 2006 B2
7150741 Erickson et al. Dec 2006 B2
7153289 Vasko Dec 2006 B2
7154397 Zerhusen et al. Dec 2006 B2
7156807 Carter et al. Jan 2007 B2
7158030 Chung Jan 2007 B2
7161484 Tsoukalis et al. Jan 2007 B2
7167755 Seeberger et al. Jan 2007 B2
7167920 Traversat Jan 2007 B2
7171277 Engleson et al. Jan 2007 B2
7171492 Borella et al. Jan 2007 B1
7181493 English et al. Feb 2007 B2
7185288 McKeever Feb 2007 B2
7193514 Ritson Mar 2007 B2
7197025 Chuah Mar 2007 B2
7201734 Hickle Apr 2007 B2
7204823 Estes et al. Apr 2007 B2
7213009 Pestotnik May 2007 B2
7216802 de la Huerga May 2007 B1
7220240 Struys et al. May 2007 B2
7224979 Singhal et al. May 2007 B2
7229430 Hickle et al. Jun 2007 B2
7230529 Ketcherside Jun 2007 B2
7236936 White et al. Jun 2007 B2
7238164 Childers et al. Jul 2007 B2
7247154 Hickle Jul 2007 B2
7248239 Dowling Jul 2007 B2
7250856 Havekost et al. Jul 2007 B2
7255683 Vanderveen et al. Aug 2007 B2
7256888 Staehr et al. Aug 2007 B2
7258534 Fathallah et al. Aug 2007 B2
7263213 Rowe Aug 2007 B2
7267664 Rizzo Sep 2007 B2
7267665 Steil et al. Sep 2007 B2
7275156 Balfanz et al. Sep 2007 B2
7278983 Ireland et al. Oct 2007 B2
7289815 Gfeller et al. Oct 2007 B2
7289948 Mohri Oct 2007 B1
7293107 Hanson et al. Nov 2007 B1
7295119 Rappaport et al. Nov 2007 B2
7295556 Roese et al. Nov 2007 B2
7301451 Hastings Nov 2007 B2
7308300 Toews et al. Dec 2007 B2
7315825 Rosenfeld et al. Jan 2008 B2
7319386 Collins, Jr. et al. Jan 2008 B2
7324000 Zittrain et al. Jan 2008 B2
7327705 Fletcher et al. Feb 2008 B2
7343224 DiGianfilippo et al. Mar 2008 B2
7346025 Bryson Mar 2008 B2
7347836 Peterson et al. Mar 2008 B2
7354420 Steil et al. Apr 2008 B2
7369897 Boveja et al. May 2008 B2
7369948 Ferenczi et al. May 2008 B1
7383088 Spinelli et al. Jun 2008 B2
7384410 Eggers et al. Jun 2008 B2
7398183 Holland et al. Jul 2008 B2
7398279 Muno, Jr. et al. Jul 2008 B2
7399277 Saidara et al. Jul 2008 B2
7402153 Steil et al. Jul 2008 B2
7420472 Tran Sep 2008 B2
7432807 Schmitt Oct 2008 B2
7447643 Olson Nov 2008 B1
7454314 Holland et al. Nov 2008 B2
7457804 Uber, III et al. Nov 2008 B2
7464040 Joao Dec 2008 B2
7471994 Ford et al. Dec 2008 B2
7483756 Engleson et al. Jan 2009 B2
7489808 Gerder Feb 2009 B2
7490021 Holland et al. Feb 2009 B2
7490048 Joao Feb 2009 B2
7491187 Van Den Berghe et al. Feb 2009 B2
7519905 Kougiouris et al. Apr 2009 B2
7523401 Aldridge Apr 2009 B1
7524304 Genosar Apr 2009 B2
7551078 Carlson Jun 2009 B2
7559321 Wermeling et al. Jul 2009 B2
7565197 Haulbrich et al. Jul 2009 B2
7572230 Neumann et al. Aug 2009 B2
7578802 Hickle Aug 2009 B2
7621009 Elhabashy Nov 2009 B2
D606533 De Jong et al. Dec 2009 S
7636718 Steen et al. Dec 2009 B1
7640172 Kuth Dec 2009 B2
7645258 White et al. Jan 2010 B2
7647237 Malave et al. Jan 2010 B2
7662124 Duchon et al. Feb 2010 B2
7668731 Martucci et al. Feb 2010 B2
7671733 McNeal et al. Mar 2010 B2
7678071 Lebel et al. Mar 2010 B2
7687678 Jacobs Mar 2010 B2
7697994 VanDanacker et al. Apr 2010 B2
7698239 Lieuallen Apr 2010 B2
7705727 Pestotnik Apr 2010 B2
7724147 Brown et al. May 2010 B2
7739126 Cave Jun 2010 B1
7746218 Collins, Jr. Jun 2010 B2
7766873 Moberg et al. Aug 2010 B2
7776029 Whitehurst et al. Aug 2010 B2
7776031 Hartlaub et al. Aug 2010 B2
7785313 Mastrototaro Aug 2010 B2
7788369 McAllen et al. Aug 2010 B2
7806852 Jurson Oct 2010 B1
7806886 Kanderian, Jr. et al. Oct 2010 B2
7826981 Goode, Jr. et al. Nov 2010 B2
7835927 Schlotterbeck et al. Nov 2010 B2
7836314 Chieu Nov 2010 B2
7856276 Ripart et al. Dec 2010 B2
7860583 Condurso et al. Dec 2010 B2
7864771 Tavares et al. Jan 2011 B2
7868754 Salvat, Jr. Jan 2011 B2
7871394 Halbert et al. Jan 2011 B2
7886231 Hopermann et al. Feb 2011 B2
7895053 Holland et al. Feb 2011 B2
7896842 Palmroos et al. Mar 2011 B2
7899546 Sieracki et al. Mar 2011 B2
7905710 Wang et al. Mar 2011 B2
7920061 Klein et al. Apr 2011 B2
7933780 de la Huerga Apr 2011 B2
7938796 Moubayed May 2011 B2
7945452 Fathallah et al. May 2011 B2
7974714 Hoffberg Jul 2011 B2
7976508 Hoag Jul 2011 B2
7996241 Zak Aug 2011 B2
8034026 Grant Oct 2011 B2
8038593 Friedman et al. Oct 2011 B2
8048040 Kiani Nov 2011 B2
8060576 Chan et al. Nov 2011 B2
8065161 Howard et al. Nov 2011 B2
8066672 Mandro Nov 2011 B2
8075514 Butterfield et al. Dec 2011 B2
8078983 Davis et al. Dec 2011 B2
8082018 Duchon et al. Dec 2011 B2
8082312 Chan et al. Dec 2011 B2
8095692 Mehta et al. Jan 2012 B2
8126730 Dicks et al. Feb 2012 B2
8147448 Sundar et al. Apr 2012 B2
8149131 Blomquist Apr 2012 B2
8169914 Bajpai May 2012 B2
8171094 Chan et al. May 2012 B2
8172798 Hungerford et al. May 2012 B2
8185322 Schroeder et al. May 2012 B2
8195478 Petersen et al. Jun 2012 B2
8206350 Mann et al. Jun 2012 B2
8219413 Martinez et al. Jul 2012 B2
8231578 Fathallah et al. Jul 2012 B2
8234128 Martucci et al. Jul 2012 B2
8267892 Spencer et al. Sep 2012 B2
8271106 Wehba et al. Sep 2012 B2
8287495 Michaud et al. Oct 2012 B2
8291337 Gannin et al. Oct 2012 B2
8298184 DiPerna et al. Oct 2012 B2
8312272 Serenyl et al. Nov 2012 B1
8352290 Bartz et al. Jan 2013 B2
8359338 Butterfield et al. Jan 2013 B2
8380536 Howard et al. Feb 2013 B2
8387112 Ranjan et al. Feb 2013 B1
8394077 Jacobson et al. Mar 2013 B2
8398592 Leibner-Druska Mar 2013 B2
8403908 Jacobson et al. Mar 2013 B2
8435206 Evans et al. May 2013 B2
8449523 Brukalo et al. May 2013 B2
8452953 Buck et al. May 2013 B2
8453645 Figueiredo et al. Jun 2013 B2
8472630 Konrad et al. Jun 2013 B2
8480648 Burnett et al. Jul 2013 B2
8489427 Simpson et al. Jul 2013 B2
8494879 Davis et al. Jul 2013 B2
8504179 Blomquist Aug 2013 B2
8517990 Teel et al. Aug 2013 B2
8518021 Stewart et al. Aug 2013 B2
8543416 Palmroos et al. Sep 2013 B2
8551038 Tsoukalis et al. Oct 2013 B2
8560345 Wehba et al. Oct 2013 B2
8567681 Borges et al. Oct 2013 B2
8577692 Silkaitis et al. Nov 2013 B2
8579884 Lanier et al. Nov 2013 B2
8626530 Tran et al. Jan 2014 B1
8655676 Wehba et al. Feb 2014 B2
8660860 Wehba et al. Feb 2014 B2
8662388 Belkin Mar 2014 B2
8666769 Butler et al. Mar 2014 B2
8667293 Birtwhistle et al. Mar 2014 B2
8687811 Nierzwick et al. Apr 2014 B2
8700421 Feng et al. Apr 2014 B2
8731960 Butler et al. May 2014 B2
8768719 Wehba et al. Jul 2014 B2
8771251 Ruchti et al. Jul 2014 B2
8777894 Butterfield et al. Jul 2014 B2
8777895 Hsu et al. Jul 2014 B2
8799012 Butler et al. Aug 2014 B2
8876793 Ledford et al. Nov 2014 B2
8922330 Moberg et al. Dec 2014 B2
8936565 Chawla Jan 2015 B2
8945043 Lee et al. Feb 2015 B2
8952794 Blomquist et al. Feb 2015 B2
8959617 Newlin et al. Feb 2015 B2
8998100 Halbert et al. Apr 2015 B2
9026370 Rubalcaba et al. May 2015 B2
9069887 Gupta et al. Jun 2015 B2
9077544 Baker et al. Jul 2015 B2
9089642 Murphy et al. Jul 2015 B2
9114217 Sur et al. Aug 2015 B2
9123077 Silkaitis et al. Sep 2015 B2
9192712 DeBelser et al. Nov 2015 B2
9240002 Hume et al. Jan 2016 B2
9302035 Marseille et al. Apr 2016 B2
9381296 Arrizza et al. Jul 2016 B2
9393362 Cozmi et al. Jul 2016 B2
9483615 Roberts Nov 2016 B2
9498583 Sur et al. Nov 2016 B2
9539383 Kohlbrecher Jan 2017 B2
9572923 Howard et al. Feb 2017 B2
9594875 Arrizza et al. Mar 2017 B2
9604000 Wehba et al. Mar 2017 B2
9641432 Jha et al. May 2017 B2
9649431 Gray et al. May 2017 B2
9662436 Belkin et al. May 2017 B2
9690909 Stewart et al. Jun 2017 B2
9707341 Dumas, III et al. Jul 2017 B2
9717845 Istoc Aug 2017 B2
9724470 Day et al. Aug 2017 B2
9764082 Day et al. Sep 2017 B2
9886550 Lee et al. Feb 2018 B2
9943269 Muhsin et al. Apr 2018 B2
9967739 Proennecke et al. May 2018 B2
9971871 Arrizza et al. May 2018 B2
9995611 Ruchti et al. Jun 2018 B2
10022498 Ruchti et al. Jul 2018 B2
10042986 Ruchti et al. Aug 2018 B2
10046112 Oruklu et al. Aug 2018 B2
10166328 Oruklu et al. Jan 2019 B2
10173008 Simpson et al. Jan 2019 B2
10238799 Kohlbrecher Mar 2019 B2
10238801 Wehba et al. Mar 2019 B2
10242060 Butler et al. Mar 2019 B2
10300194 Day et al. May 2019 B2
10311972 Kohlbrecher et al. Jun 2019 B2
10314974 Day et al. Jun 2019 B2
10333843 Jha et al. Jun 2019 B2
10341866 Spencer et al. Jul 2019 B1
10430761 Hume et al. Oct 2019 B2
10434246 Silkaitis et al. Oct 2019 B2
10453157 Kamen et al. Oct 2019 B2
10463788 Day Nov 2019 B2
10516536 Rommel Dec 2019 B2
10617815 Day et al. Apr 2020 B2
10646651 Day et al. May 2020 B2
10692595 Xavier et al. Jun 2020 B2
10740436 Moskal et al. Aug 2020 B2
10741280 Xavier et al. Aug 2020 B2
10757219 Moskal Aug 2020 B2
10765799 Belkin et al. Sep 2020 B2
10799632 Kohlbrecher Oct 2020 B2
10812380 Jha et al. Oct 2020 B2
10861592 Xavier et al. Dec 2020 B2
10898641 Day et al. Jan 2021 B2
10950339 Xavier et al. Mar 2021 B2
10964428 Xavier et al. Mar 2021 B2
11013861 Wehba et al. May 2021 B2
11037668 Ruchti et al. Jun 2021 B2
11052193 Day et al. Jul 2021 B2
11139058 Xavier et al. Oct 2021 B2
11152108 Xavier et al. Oct 2021 B2
11152109 Xavier et al. Oct 2021 B2
11152110 Xavier et al. Oct 2021 B2
11194810 Butler et al. Dec 2021 B2
11235100 Howard et al. Feb 2022 B2
11289183 Kohlbrecher Mar 2022 B2
11309070 Xavier et al. Apr 2022 B2
20010016056 Westphal et al. Aug 2001 A1
20010031944 Peterson et al. Oct 2001 A1
20010032099 Joao Oct 2001 A1
20010037060 Thompson et al. Nov 2001 A1
20010044731 Coffman et al. Nov 2001 A1
20010048027 Walsh Dec 2001 A1
20010051787 Haller et al. Dec 2001 A1
20010056358 Dulong et al. Dec 2001 A1
20020010595 Kapp Jan 2002 A1
20020013551 Zaitsu et al. Jan 2002 A1
20020013723 Mise Jan 2002 A1
20020015018 Shimazu et al. Feb 2002 A1
20020019584 Schulze et al. Feb 2002 A1
20020021700 Hata et al. Feb 2002 A1
20020026103 Norris et al. Feb 2002 A1
20020029776 Blomquist Mar 2002 A1
20020032583 Joao Mar 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020040282 Bailey et al. Apr 2002 A1
20020044043 Chaco et al. Apr 2002 A1
20020082728 Mueller et al. Jun 2002 A1
20020087115 Hartlaub Jul 2002 A1
20020087116 Hartlaub Jul 2002 A1
20020095486 Bahl Jul 2002 A1
20020103675 Vanelli Aug 2002 A1
20020123905 Goodroe et al. Sep 2002 A1
20020143580 Bristol et al. Oct 2002 A1
20020152239 Bautista-Lloyd et al. Oct 2002 A1
20020154600 Ido et al. Oct 2002 A1
20020173702 Lebel et al. Nov 2002 A1
20020173875 Wallace et al. Nov 2002 A1
20020194329 Alling Dec 2002 A1
20030009244 Engleson Jan 2003 A1
20030013959 Grunwald et al. Jan 2003 A1
20030014222 Klass et al. Jan 2003 A1
20030014817 Gallant et al. Jan 2003 A1
20030025602 Medema et al. Feb 2003 A1
20030028082 Thompson Feb 2003 A1
20030036683 Kehr et al. Feb 2003 A1
20030036744 Struys et al. Feb 2003 A1
20030047126 Tomaschko Mar 2003 A1
20030050621 Lebel et al. Mar 2003 A1
20030059750 Bindler et al. Mar 2003 A1
20030060688 Ciarniello et al. Mar 2003 A1
20030069963 Jayant et al. Apr 2003 A1
20030079746 Hickle May 2003 A1
20030097529 Arimilli et al. May 2003 A1
20030104982 Wittmann et al. Jun 2003 A1
20030105389 Noonan et al. Jun 2003 A1
20030106553 Vanderveen Jun 2003 A1
20030115358 Yun Jun 2003 A1
20030120384 Haitin et al. Jun 2003 A1
20030125662 Bui Jul 2003 A1
20030130616 Steil Jul 2003 A1
20030135087 Hickle et al. Jul 2003 A1
20030139701 White et al. Jul 2003 A1
20030140928 Bui et al. Jul 2003 A1
20030140929 Wilkes et al. Jul 2003 A1
20030141981 Bui et al. Jul 2003 A1
20030143746 Sage, Jr. Jul 2003 A1
20030144878 Wilkes et al. Jul 2003 A1
20030158749 Olchanski et al. Aug 2003 A1
20030187338 Say et al. Oct 2003 A1
20030200116 Forrester Oct 2003 A1
20030204416 Acharya Oct 2003 A1
20030204781 Peebles et al. Oct 2003 A1
20030212364 Mann et al. Nov 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030212821 Gillies et al. Nov 2003 A1
20030217962 Childers et al. Nov 2003 A1
20040008123 Carrender et al. Jan 2004 A1
20040015132 Brown Jan 2004 A1
20040019607 Moubayed et al. Jan 2004 A1
20040030323 Ullestad et al. Feb 2004 A1
20040039257 Hickle Feb 2004 A1
20040057226 Berthou et al. Mar 2004 A1
20040064341 Langan et al. Apr 2004 A1
20040064342 Browne et al. Apr 2004 A1
20040064435 Moubayed et al. Apr 2004 A1
20040073811 Sanin Apr 2004 A1
20040077934 Massad Apr 2004 A1
20040078231 Wilkes et al. Apr 2004 A1
20040078236 Stoodley et al. Apr 2004 A1
20040085186 Eveland et al. May 2004 A1
20040104271 Martucci et al. Jun 2004 A1
20040122530 Hansen Jun 2004 A1
20040128162 Schlotterbeck et al. Jul 2004 A1
20040128163 Goodman et al. Jul 2004 A1
20040133441 Brady et al. Jul 2004 A1
20040139004 Cohen et al. Jul 2004 A1
20040145480 Despotis Jul 2004 A1
20040147034 Gore et al. Jul 2004 A1
20040167464 Ireland et al. Aug 2004 A1
20040167465 Kohler Aug 2004 A1
20040167804 Simpson Aug 2004 A1
20040172222 Simpson et al. Sep 2004 A1
20040172283 Vanderveen Sep 2004 A1
20040172301 Mihai et al. Sep 2004 A1
20040172302 Martucci et al. Sep 2004 A1
20040176667 Mihai et al. Sep 2004 A1
20040176980 Bulitta et al. Sep 2004 A1
20040176984 White et al. Sep 2004 A1
20040181314 Zaleski Sep 2004 A1
20040189708 Larcheveque et al. Sep 2004 A1
20040193325 Bonderud Sep 2004 A1
20040193328 Butterfield et al. Sep 2004 A1
20040204673 Flaherty et al. Oct 2004 A1
20040215278 Stegink et al. Oct 2004 A1
20040220517 Starkweather et al. Nov 2004 A1
20040225252 Gillespie et al. Nov 2004 A1
20040236240 Kraus et al. Nov 2004 A1
20040243438 Mintz Dec 2004 A1
20040254434 Goodnow et al. Dec 2004 A1
20050010269 Lebel et al. Jan 2005 A1
20050020886 Hutchinson et al. Jan 2005 A1
20050021006 Tonnies Jan 2005 A1
20050027560 Cook Feb 2005 A1
20050027567 Taha Feb 2005 A1
20050038311 Kuth Feb 2005 A1
20050038669 Sachdeva et al. Feb 2005 A1
20050038680 McMahon Feb 2005 A1
20050040226 Al-Sheikh Feb 2005 A1
20050043620 Fallows et al. Feb 2005 A1
20050049910 Lancaster et al. Mar 2005 A1
20050055242 Bello et al. Mar 2005 A1
20050055244 Mullan et al. Mar 2005 A1
20050065465 Lebel et al. Mar 2005 A1
20050065817 Mihai et al. Mar 2005 A1
20050075544 Shapiro et al. Apr 2005 A1
20050080801 Kothandaraman et al. Apr 2005 A1
20050086071 Fox, Jr. et al. Apr 2005 A1
20050086072 Fox Apr 2005 A1
20050090808 Malave et al. Apr 2005 A1
20050099624 Staehr May 2005 A1
20050102162 Blumenfeld May 2005 A1
20050102165 Oshita et al. May 2005 A1
20050102167 Kapoor May 2005 A1
20050102669 Marney et al. May 2005 A1
20050107923 Vanderveen May 2005 A1
20050108057 Cohen et al. May 2005 A1
20050117529 Ramos-Escano Jun 2005 A1
20050119788 Engleson et al. Jun 2005 A1
20050119914 Batch Jun 2005 A1
20050131739 Rabinowitz et al. Jun 2005 A1
20050135306 McAllen et al. Jun 2005 A1
20050137522 Aoki Jun 2005 A1
20050137573 McLaughlin Jun 2005 A1
20050138428 McAllen et al. Jun 2005 A1
20050154769 Eckart et al. Jul 2005 A1
20050160057 Wefers et al. Jul 2005 A1
20050171503 Van Den Berghe et al. Aug 2005 A1
20050171815 Vanderveen Aug 2005 A1
20050177096 Bollish et al. Aug 2005 A1
20050177395 Blomquist Aug 2005 A1
20050182306 Sloan Aug 2005 A1
20050182355 Bui Aug 2005 A1
20050187950 Parker Aug 2005 A1
20050192557 Brauker et al. Sep 2005 A1
20050197554 Polcha Sep 2005 A1
20050197621 Poulsen et al. Sep 2005 A1
20050210037 Wefers et al. Sep 2005 A1
20050216479 Wefers et al. Sep 2005 A1
20050216480 Wefers et al. Sep 2005 A1
20050223045 Funahashi et al. Oct 2005 A1
20050224083 Crass Oct 2005 A1
20050234746 Funahashi Oct 2005 A1
20050240305 Bogash et al. Oct 2005 A1
20050246416 Blomquist Nov 2005 A1
20050251418 Fox, Jr. et al. Nov 2005 A1
20050261660 Choi Nov 2005 A1
20050273059 Mernoe et al. Dec 2005 A1
20050273367 Nourie et al. Dec 2005 A1
20050277873 Stewart et al. Dec 2005 A1
20050277890 Stewart et al. Dec 2005 A1
20050278194 Holland et al. Dec 2005 A1
20060004772 Hagan et al. Jan 2006 A1
20060009727 O'Mahony et al. Jan 2006 A1
20060009734 Martin Jan 2006 A1
20060010098 Goodnow et al. Jan 2006 A1
20060042139 Mendes Mar 2006 A1
20060047270 Shelton Mar 2006 A1
20060053036 Coffman et al. Mar 2006 A1
20060064020 Burnes et al. Mar 2006 A1
20060074633 Mahesh et al. Apr 2006 A1
20060074920 Wefers et al. Apr 2006 A1
20060079831 Gilbert Apr 2006 A1
20060089854 Holland et al. Apr 2006 A1
20060089855 Holland et al. Apr 2006 A1
20060100746 Leibner-Druska May 2006 A1
20060100907 Holland et al. May 2006 A1
20060106649 Eggers et al. May 2006 A1
20060111943 Wu May 2006 A1
20060116904 Brem Jun 2006 A1
20060116907 Rhodes et al. Jun 2006 A1
20060122481 Sievenpiper et al. Jun 2006 A1
20060122867 Eggers et al. Jun 2006 A1
20060129140 Todd et al. Jun 2006 A1
20060129429 Moubayed et al. Jun 2006 A1
20060129434 Smitherman et al. Jun 2006 A1
20060129435 Smitherman et al. Jun 2006 A1
20060136266 Tarassenko et al. Jun 2006 A1
20060136271 Eggers et al. Jun 2006 A1
20060143051 Eggers et al. Jun 2006 A1
20060173260 Gaoni et al. Aug 2006 A1
20060173406 Hayes et al. Aug 2006 A1
20060173715 Wang et al. Aug 2006 A1
20060173927 Beyer et al. Aug 2006 A1
20060190302 Eggers et al. Aug 2006 A1
20060195022 Trepagnier et al. Aug 2006 A1
20060200007 Brockway et al. Sep 2006 A1
20060200369 Batch et al. Sep 2006 A1
20060211404 Cromp et al. Sep 2006 A1
20060224141 Rush et al. Oct 2006 A1
20060229918 Fotsch et al. Oct 2006 A1
20060258985 Russell Nov 2006 A1
20060259327 Hoag Nov 2006 A1
20060264895 Flanders Nov 2006 A1
20060267753 Hussey et al. Nov 2006 A1
20060268710 Appanna et al. Nov 2006 A1
20060270971 Gelfand et al. Nov 2006 A1
20060277206 Bailey et al. Dec 2006 A1
20060287885 Frick Dec 2006 A1
20070015972 Wang et al. Jan 2007 A1
20070016443 Wachman et al. Jan 2007 A1
20070027506 Stender et al. Feb 2007 A1
20070060796 Kim Mar 2007 A1
20070060870 Tolle et al. Mar 2007 A1
20070060871 Istoc Mar 2007 A1
20070061393 Moore Mar 2007 A1
20070065363 Dalal et al. Mar 2007 A1
20070073419 Sesay Mar 2007 A1
20070078314 Grounsell Apr 2007 A1
20070083870 Kanakogi Apr 2007 A1
20070088333 Levin et al. Apr 2007 A1
20070093786 Goldsmith et al. Apr 2007 A1
20070100665 Brown May 2007 A1
20070100667 Bardy May 2007 A1
20070106126 Mannheimer et al. May 2007 A1
20070112298 Mueller et al. May 2007 A1
20070116037 Moore May 2007 A1
20070118405 Campbell et al. May 2007 A1
20070135866 Baker et al. Jun 2007 A1
20070136098 Smythe et al. Jun 2007 A1
20070142822 Remde Jun 2007 A1
20070156282 Dunn Jul 2007 A1
20070156452 Batch Jul 2007 A1
20070169008 Varanasi et al. Jul 2007 A1
20070179448 Lim et al. Aug 2007 A1
20070186923 Poutiatine et al. Aug 2007 A1
20070191817 Martin Aug 2007 A1
20070191973 Holzbauer et al. Aug 2007 A1
20070213657 Jennewine et al. Sep 2007 A1
20070213684 Hickle et al. Sep 2007 A1
20070214003 Holland et al. Sep 2007 A1
20070215545 Bissler et al. Sep 2007 A1
20070229249 McNeal Oct 2007 A1
20070232867 Hansmann Oct 2007 A1
20070233035 Wehba et al. Oct 2007 A1
20070233049 Wehba et al. Oct 2007 A1
20070233206 Frikart Oct 2007 A1
20070233520 Wehba et al. Oct 2007 A1
20070251835 Mehta et al. Nov 2007 A1
20070253021 Mehta et al. Nov 2007 A1
20070254593 Jollota et al. Nov 2007 A1
20070255125 Moberg et al. Nov 2007 A1
20070257788 Carlson Nov 2007 A1
20070258395 Jollota et al. Nov 2007 A1
20070299687 Palmer et al. Dec 2007 A1
20070299695 Jung et al. Dec 2007 A1
20080004904 Tran Jan 2008 A1
20080009684 Corsetti et al. Jan 2008 A1
20080033361 Evans et al. Feb 2008 A1
20080033966 Wahl Feb 2008 A1
20080034323 Blomquist Feb 2008 A1
20080041942 Aissa Feb 2008 A1
20080052704 Wysocki Feb 2008 A1
20080065007 Peterson et al. Mar 2008 A1
20080065417 Jung et al. Mar 2008 A1
20080071217 Moubayed et al. Mar 2008 A1
20080071251 Moubayed et al. Mar 2008 A1
20080091466 Butler et al. Apr 2008 A1
20080095339 Elliott Apr 2008 A1
20080097289 Steil et al. Apr 2008 A1
20080126969 Blomquist May 2008 A1
20080139907 Rao et al. Jun 2008 A1
20080148047 Appenzeller et al. Jun 2008 A1
20080149117 Raghuram Jun 2008 A1
20080154177 Moubayed Jun 2008 A1
20080172337 Banfield et al. Jul 2008 A1
20080184219 Matsumoto Jul 2008 A1
20080188796 Steil et al. Aug 2008 A1
20080214919 Harmon et al. Sep 2008 A1
20080246748 Cassidy et al. Oct 2008 A1
20080256305 Kwon Oct 2008 A1
20080259926 Tavares et al. Oct 2008 A1
20080262469 Bristol et al. Oct 2008 A1
20080269714 Mastrototaro et al. Oct 2008 A1
20080269723 Mastrototaro et al. Oct 2008 A1
20080275384 Mastrototaro et al. Nov 2008 A1
20080300572 Rankers Dec 2008 A1
20080301298 Bernardi et al. Dec 2008 A1
20080320387 Sasaki et al. Dec 2008 A1
20080320466 Dias Dec 2008 A1
20090003554 Katis et al. Jan 2009 A1
20090005703 Fasciano Jan 2009 A1
20090005728 Weinert et al. Jan 2009 A1
20090006061 Thukral et al. Jan 2009 A1
20090006129 Thukral Jan 2009 A1
20090006133 Weinert Jan 2009 A1
20090018495 Panduro Jan 2009 A1
20090051560 Manning et al. Feb 2009 A1
20090054743 Stewart Feb 2009 A1
20090054754 McMahon et al. Feb 2009 A1
20090057399 Sajkowsky Mar 2009 A1
20090063187 Johnson et al. Mar 2009 A1
20090069785 Miller et al. Mar 2009 A1
20090099867 Newman Apr 2009 A1
20090135196 Holland et al. May 2009 A1
20090143662 Estes et al. Jun 2009 A1
20090149743 Barron et al. Jun 2009 A1
20090150174 Buck et al. Jun 2009 A1
20090150439 Gejdos et al. Jun 2009 A1
20090150878 Pathak et al. Jun 2009 A1
20090156991 Roberts Jun 2009 A1
20090157695 Roberts Jun 2009 A1
20090158274 Roberts Jun 2009 A1
20090177146 Nesbitt et al. Jul 2009 A1
20090177769 Roberts Jul 2009 A1
20090177992 Rubalcaba et al. Jul 2009 A1
20090183147 Davis et al. Jul 2009 A1
20090209938 Aalto-Setala Aug 2009 A1
20090210250 Prax et al. Aug 2009 A1
20090221890 Saffer et al. Sep 2009 A1
20090231249 Wang et al. Sep 2009 A1
20090270833 DeBelser Oct 2009 A1
20090275886 Blomquist et al. Nov 2009 A1
20090275896 Kamen et al. Nov 2009 A1
20090284691 Marhefka et al. Nov 2009 A1
20090292340 Mass et al. Nov 2009 A1
20090306573 Gagner et al. Dec 2009 A1
20090326340 Wang Dec 2009 A1
20090326516 Bangera et al. Dec 2009 A1
20100022988 Wochner Jan 2010 A1
20100036310 Hillman Feb 2010 A1
20100056992 Hayter Mar 2010 A1
20100083060 Rahman Apr 2010 A1
20100095229 Dixon et al. Apr 2010 A1
20100121170 Rule May 2010 A1
20100121246 Peters et al. May 2010 A1
20100121415 Skelton et al. May 2010 A1
20100121654 Portnoy et al. May 2010 A1
20100121752 Banigan et al. May 2010 A1
20100130933 Holland et al. May 2010 A1
20100131434 Magent et al. May 2010 A1
20100138523 Umess et al. Jun 2010 A1
20100146137 Wu et al. Jun 2010 A1
20100156633 Buck et al. Jun 2010 A1
20100160854 Gauthier Jun 2010 A1
20100160860 Celentano et al. Jun 2010 A1
20100174266 Estes Jul 2010 A1
20100191525 Rabenko et al. Jul 2010 A1
20100198034 Thomas et al. Aug 2010 A1
20100198196 Wei Aug 2010 A1
20100200506 Ware et al. Aug 2010 A1
20100209268 Davis Aug 2010 A1
20100212675 Walling et al. Aug 2010 A1
20100217621 Schoenberg Aug 2010 A1
20100234708 Buck et al. Sep 2010 A1
20100250732 Bucknell Sep 2010 A1
20100271479 Heydlauf Oct 2010 A1
20100273738 Valcke et al. Oct 2010 A1
20100274218 Yodfat et al. Oct 2010 A1
20100280486 Khair et al. Nov 2010 A1
20100292634 Kircher Nov 2010 A1
20100298765 Budiman et al. Nov 2010 A1
20100318025 John Dec 2010 A1
20110001605 Kiani et al. Jan 2011 A1
20110021898 Wei et al. Jan 2011 A1
20110040158 Katz et al. Feb 2011 A1
20110060758 Schlotterbeck et al. Mar 2011 A1
20110071844 Cannon et al. Mar 2011 A1
20110072379 Gannon Mar 2011 A1
20110078253 Chan et al. Mar 2011 A1
20110078608 Gannon et al. Mar 2011 A1
20110093284 Dicks et al. Apr 2011 A1
20110099313 Bolanowski Apr 2011 A1
20110125095 Lebel et al. May 2011 A1
20110138185 Ju et al. Jun 2011 A1
20110175728 Baker, Jr. Jul 2011 A1
20110178462 Moberg et al. Jul 2011 A1
20110196748 Caron et al. Aug 2011 A1
20110231216 Fyke et al. Sep 2011 A1
20110257496 Terashima et al. Oct 2011 A1
20110257798 Ali et al. Oct 2011 A1
20110259954 Bartz et al. Oct 2011 A1
20110264043 Kotnick et al. Oct 2011 A1
20110264044 Bartz et al. Oct 2011 A1
20110266221 Ware et al. Nov 2011 A1
20110270045 Lebel et al. Nov 2011 A1
20110275904 Lebel et al. Nov 2011 A1
20110286457 Ee Nov 2011 A1
20110289497 Kiaie et al. Nov 2011 A1
20110295196 Chazot et al. Dec 2011 A1
20110295341 Estes et al. Dec 2011 A1
20110296051 Vange Dec 2011 A1
20110296411 Tang et al. Dec 2011 A1
20110313789 Karmen et al. Dec 2011 A1
20110319813 Kamen et al. Dec 2011 A1
20110320049 Chossat et al. Dec 2011 A1
20120005680 Dolby et al. Jan 2012 A1
20120011253 Friedman et al. Jan 2012 A1
20120016305 Jollota Jan 2012 A1
20120029941 Malave et al. Feb 2012 A1
20120036102 Fletcher et al. Feb 2012 A1
20120066501 Xiong Mar 2012 A1
20120070045 Vesper et al. Mar 2012 A1
20120095437 Hemmerling Apr 2012 A1
20120112903 Kaib et al. May 2012 A1
20120130198 Beaule May 2012 A1
20120143116 Ware et al. Jun 2012 A1
20120150556 Galasso et al. Jun 2012 A1
20120157920 Flachbart et al. Jun 2012 A1
20120179135 Rinehart et al. Jul 2012 A1
20120179136 Rinehart et al. Jul 2012 A1
20120185267 Kamen et al. Jul 2012 A1
20120203177 Lanier Aug 2012 A1
20120245554 Kawamura Sep 2012 A1
20120259978 Petersen et al. Oct 2012 A1
20120260012 Gao-Saari et al. Oct 2012 A1
20120277716 Ali et al. Nov 2012 A1
20120283630 Lee et al. Nov 2012 A1
20120284734 McQuaid et al. Nov 2012 A1
20120323212 Murphy Dec 2012 A1
20130006666 Schneider Jan 2013 A1
20130006702 Wu Jan 2013 A1
20130012877 Debelser et al. Jan 2013 A1
20130012879 Debelser et al. Jan 2013 A1
20130012880 Blomquist Jan 2013 A1
20130015980 Evans et al. Jan 2013 A1
20130036403 Geist Feb 2013 A1
20130036412 Birtwhistle et al. Feb 2013 A1
20130066265 Grant Mar 2013 A1
20130072872 Yodfat et al. Mar 2013 A1
20130096444 Condurso et al. Apr 2013 A1
20130096648 Benson Apr 2013 A1
20130102963 Marsh et al. Apr 2013 A1
20130138452 Cork et al. May 2013 A1
20130144206 Lee et al. Jun 2013 A1
20130150824 Estes et al. Jun 2013 A1
20130167245 Birtwhistle et al. Jun 2013 A1
20130173473 Birtwhistle et al. Jul 2013 A1
20130191770 Bartz et al. Jul 2013 A1
20130204188 Kamen et al. Aug 2013 A1
20130218080 Peterfreund et al. Aug 2013 A1
20130274669 Stempfle et al. Oct 2013 A1
20130275539 Gross Oct 2013 A1
20130291116 Homer Oct 2013 A1
20130296823 Melker et al. Nov 2013 A1
20130296984 Burnett et al. Nov 2013 A1
20130317753 Kamen et al. Nov 2013 A1
20130346108 Kamen et al. Dec 2013 A1
20140025392 Chandrasenan Jan 2014 A1
20140142963 Hill et al. May 2014 A1
20140163517 Finan et al. Jun 2014 A1
20140180711 Kamen et al. Jun 2014 A1
20140194817 Lee et al. Jul 2014 A1
20140197950 Shupp et al. Jul 2014 A1
20140257251 Bush et al. Sep 2014 A1
20140266790 Al-Ali et al. Sep 2014 A1
20140266794 Brown et al. Sep 2014 A1
20140269643 Sun Sep 2014 A1
20140276571 Ludolph Sep 2014 A1
20140280522 Watte Sep 2014 A1
20140288947 Simpson et al. Sep 2014 A1
20140294177 Shastry et al. Oct 2014 A1
20140297329 Rock Oct 2014 A1
20140316819 Dunsirn et al. Oct 2014 A1
20140366878 Baron Dec 2014 A1
20150005935 Bae et al. Jan 2015 A1
20150006907 Brouwer et al. Jan 2015 A1
20150066531 Jacobson et al. Mar 2015 A1
20150100038 McCann et al. Apr 2015 A1
20150100787 Westin et al. Apr 2015 A1
20150117234 Raman et al. Apr 2015 A1
20150151051 Tsoukalis Jun 2015 A1
20150161354 Blomquist Jun 2015 A1
20150199192 Borges et al. Jul 2015 A1
20150230760 Schneider Aug 2015 A1
20150328396 Adams et al. Nov 2015 A1
20150371004 Jones Dec 2015 A1
20150379237 Mills et al. Dec 2015 A1
20160006695 Prodoehl et al. Jan 2016 A1
20160015885 Pananen et al. Jan 2016 A1
20160034655 Gray et al. Feb 2016 A1
20160045661 Gray et al. Feb 2016 A1
20160051749 Istoc Feb 2016 A1
20160228633 Welsch et al. Aug 2016 A1
20160241391 Fenster Aug 2016 A1
20160285876 Perez et al. Sep 2016 A1
20160317742 Gannon et al. Nov 2016 A1
20160350513 Jacobson et al. Dec 2016 A1
20170104645 Wooton et al. Apr 2017 A1
20170147761 Moskal et al. May 2017 A1
20170149567 Moskal May 2017 A1
20170262590 Karakosta et al. Sep 2017 A1
20170274140 Howard et al. Sep 2017 A1
20170286637 Arrizza et al. Oct 2017 A1
20170319780 Belkin et al. Nov 2017 A1
20170325091 Freeman et al. Nov 2017 A1
20170351841 Moskal Dec 2017 A1
20180121613 Connely, IV et al. May 2018 A1
20180126067 Ledford et al. May 2018 A1
20180181712 Ensey et al. Jun 2018 A1
20180247712 Muhsin et al. Aug 2018 A1
20180322948 Drost et al. Nov 2018 A1
20180359085 Dervyn Dec 2018 A1
20190006044 Brask Jan 2019 A1
20190096518 Pace Mar 2019 A1
20190132196 Trivedi et al. May 2019 A1
20190147998 Ruchti et al. May 2019 A1
20190228863 Dharwad et al. Jul 2019 A1
20190229982 Ikuta et al. Jul 2019 A1
20190240405 Wehba et al. Aug 2019 A1
20190243829 Butler et al. Aug 2019 A1
20190244689 Atkin Aug 2019 A1
20190245942 Moskal Aug 2019 A1
20190269852 Kohlbrecher Sep 2019 A1
20190311803 Kohlbrecher et al. Oct 2019 A1
20190348160 Heavelyn et al. Nov 2019 A1
20190392929 Gassman Dec 2019 A1
20200023127 Simpson et al. Jan 2020 A1
20200027541 Xavier et al. Jan 2020 A1
20200027542 Xavier et al. Jan 2020 A1
20200027543 Xavier et al. Jan 2020 A1
20200027548 Xavier et al. Jan 2020 A1
20200027549 Xavier et al. Jan 2020 A1
20200027550 Xavier et al. Jan 2020 A1
20200027551 Xavier et al. Jan 2020 A1
20200028837 Xavier et al. Jan 2020 A1
20200028914 Xavier et al. Jan 2020 A1
20200028929 Xavier et al. Jan 2020 A1
20200035355 Xavier et al. Jan 2020 A1
20200054825 Kamen et al. Feb 2020 A1
20200061291 Day et al. Feb 2020 A1
20200145332 Jha et al. May 2020 A1
20200206413 Silkaitis et al. Jul 2020 A1
20200282139 Susi Sep 2020 A1
20200330685 Day Oct 2020 A1
20200335194 Jacobson et al. Oct 2020 A1
20200351376 Moskal Nov 2020 A1
20200353167 Vivek et al. Nov 2020 A1
20200353168 Keenan et al. Nov 2020 A1
20210043296 Xavier et al. Feb 2021 A1
20210045640 Poltorak Feb 2021 A1
20210050097 Xavier et al. Feb 2021 A1
20210085855 Belkin et al. Mar 2021 A1
20210098106 Kohlbrecher et al. Apr 2021 A1
20210098107 Xavier et al. Apr 2021 A1
20210105206 Jha et al. Apr 2021 A1
20210358603 Xavier et al. Nov 2021 A1
20210375421 Ruchti et al. Dec 2021 A1
20210375438 Xavier et al. Dec 2021 A1
20220023535 Day Jan 2022 A1
20220037011 Fryman Feb 2022 A1
20220037012 Fryman Feb 2022 A1
20220051777 Xavier et al. Feb 2022 A1
20220062541 Kamen et al. Mar 2022 A1
20220139536 Xavier et al. May 2022 A1
20220139537 Xavier et al. May 2022 A1
20220139538 Xavier et al. May 2022 A1
20220165404 Vivek et al. May 2022 A1
Foreign Referenced Citations (138)
Number Date Country
2 060 151 Aug 1997 CA
2 125 300 Oct 1999 CA
2 898 825 Jul 2014 CA
31 12 762 Jan 1983 DE
34 35 647 Jul 1985 DE
198 44 252 Mar 2000 DE
199 32 147 Jan 2001 DE
103 52 456 Jul 2005 DE
0 319 267 Jun 1989 EP
0 380 061 Aug 1990 EP
0 384 155 Aug 1990 EP
0 460 533 Dec 1991 EP
0 564 127 Jun 1993 EP
0 633 035 Jan 1995 EP
0 652 528 May 1995 EP
0 672 427 Sep 1995 EP
0 683 465 Nov 1995 EP
0 880 936 Dec 1998 EP
1 157 711 Nov 2001 EP
1 174 817 Jan 2002 EP
0 664 102 Apr 2002 EP
1 197 178 Apr 2002 EP
0 830 775 Aug 2002 EP
1 500 025 Apr 2003 EP
2 113 842 Nov 2009 EP
2 228 004 Sep 2010 EP
2 243 506 Oct 2010 EP
2 410 448 Jan 2012 EP
2 742 961 Jun 2014 EP
2 717 919 Sep 1995 FR
2 285 135 Jun 1995 GB
04-161139 Jun 1992 JP
07-502678 Mar 1995 JP
11-500643 Jan 1999 JP
2000-316820 Nov 2000 JP
2002-531154 Sep 2002 JP
2003-016183 Jan 2003 JP
2003-296173 Oct 2003 JP
2005-021463 Jan 2005 JP
2005-527284 Sep 2005 JP
2005-284846 Oct 2005 JP
2006-047319 Feb 2006 JP
2006-520949 Sep 2006 JP
2007-518479 Jul 2007 JP
2007-525256 Sep 2007 JP
2008-080036 Apr 2008 JP
2008-516303 May 2008 JP
2008-158622 Jul 2008 JP
2008-529675 Aug 2008 JP
2009-163534 Jul 2009 JP
2010-502361 Jan 2010 JP
2011-506048 Mar 2011 JP
2012-011204 Jan 2012 JP
2012-070991 Apr 2012 JP
2012-523895 Oct 2012 JP
2014-068283 Apr 2014 JP
WO 84001719 May 1984 WO
WO 91016416 Oct 1991 WO
WO 92010985 Jul 1992 WO
WO 92013322 Aug 1992 WO
WO 94005355 Mar 1994 WO
WO 96008755 Mar 1996 WO
WO 96025186 Aug 1996 WO
WO 96025963 Aug 1996 WO
WO 98012670 Mar 1998 WO
WO 98019263 May 1998 WO
WO 99051003 Oct 1999 WO
WO 00013580 Mar 2000 WO
WO 00053243 Sep 2000 WO
WO 01014974 Mar 2001 WO
WO 01033484 May 2001 WO
WO 01045014 Jun 2001 WO
WO 02005702 Jan 2002 WO
WO 02036044 May 2002 WO
WO 02049153 Jun 2002 WO
WO 02049279 Jun 2002 WO
WO 02069099 Sep 2002 WO
WO 02081015 Oct 2002 WO
WO 02088875 Nov 2002 WO
WO 03006091 Jan 2003 WO
WO 03050917 Jun 2003 WO
WO 03091836 Nov 2003 WO
WO 03094092 Nov 2003 WO
WO 2004060455 Jul 2004 WO
WO 2004070557 Aug 2004 WO
WO 2004070562 Aug 2004 WO
WO 2004072828 Aug 2004 WO
WO 2005036447 Apr 2005 WO
WO 2005050526 Jun 2005 WO
WO 2005057175 Jun 2005 WO
WO 2005066872 Jul 2005 WO
WO 2007087443 Aug 2007 WO
WO 2007117705 Oct 2007 WO
WO 2007127879 Nov 2007 WO
WO 2007127880 Nov 2007 WO
WO 2008067245 Jun 2008 WO
WO 2008082854 Jul 2008 WO
WO 2008088490 Jul 2008 WO
WO 2008097316 Aug 2008 WO
WO 2008103915 Aug 2008 WO
WO 2008124478 Oct 2008 WO
WO 2008134146 Nov 2008 WO
WO 2009016504 Feb 2009 WO
WO 2009023406 Feb 2009 WO
WO 2009023407 Feb 2009 WO
WO 2009023634 Feb 2009 WO
WO 2009036327 Mar 2009 WO
WO 2009049252 Apr 2009 WO
WO 2010017279 Feb 2010 WO
WO 2010033919 Mar 2010 WO
WO 2010053703 May 2010 WO
WO 2010075371 Jul 2010 WO
WO 2010099313 Sep 2010 WO
WO 2010114929 Oct 2010 WO
WO 2010119409 Oct 2010 WO
WO 2010124127 Oct 2010 WO
WO 2010130992 Nov 2010 WO
WO 2010135646 Nov 2010 WO
WO 2010135654 Nov 2010 WO
WO 2010135686 Nov 2010 WO
WO 2011005633 Jan 2011 WO
WO 2011022549 Feb 2011 WO
WO 2012048833 Apr 2012 WO
WO 2012049214 Apr 2012 WO
WO 2012049218 Apr 2012 WO
WO 2012120078 Sep 2012 WO
WO 2012140547 Oct 2012 WO
WO 2012164556 Dec 2012 WO
WO 2012170942 Dec 2012 WO
WO 2013045506 Apr 2013 WO
WO 2014100736 Jun 2014 WO
WO 2014131729 Sep 2014 WO
WO 2014131730 Sep 2014 WO
WO 2015124569 Aug 2015 WO
WO 2016179389 Nov 2016 WO
WO 2019219290 Nov 2019 WO
WO 2020227403 Nov 2020 WO
WO 2022006014 Jan 2022 WO
Non-Patent Literature Citations (121)
Entry
“Download”, Free On-Line Dictionary of Computing, as archived Jun. 16, 2010 in 1 page, http://web.archive.org/web/20100616010314/https://foldoc.org/download.
Edworthy, Judy, “Medical Audible Alarms: A Review”, Journal of the American Medical Informatics Association, vol. 20, No. 3, 2013, pp. 584-589.
“File Verification”, Wikipedia.org, as last modified Oct. 11, 2011 in 2 pages, https://en.wikipedia.org/w/index.php?title=File_verification&oldid=455048290.
Gabel et al., “Camp: A Common API for Measuring Performance”, 21st Large Installations System Administration Conference (LISA '07), 2007, pp. 49-61.
“McKesson Automation and Alaris Medical Systems Developing Point-of-Care Bar Coding Solution to Improve IV Medication Safety”, PR Newswire, NY, Dec. 9, 2002, pp. 4.
“Software Versioning”, Wikipedia.org, dated Oct. 16, 2011 in 11 pages, https://en.wikipedia.org/w/index.php?title=Software_versioning&oldid=455859110.
Sutton et al., “The Syntax and Semantics of the PROforma Guideline Modeling Language”, Journal of the American Medical Informatics Association, Sep./Oct. 2003, vol. 10, No. 5, pp. 433-443.
Akridge, Jeannie, “New Pumps Outsmart User Error”, Healthcare Purchasing News, Apr. 2011, pp. 10, http://web.archive.org/web/20110426122450/http://www.hpnonline.com/inside/2011-04/1104-OR-Pumps.html.
Alur et al., “Formal Specifications and Analysis of the Computer-Assisted Resuscitation Algorithm (CARA) Infusion Pump Control System”, International Journal on Software Tools for Technology Transfer, Feb. 2004, vol. 5, No. 4, pp. 308-319.
Aragon, Daleen RN, Ph.D., CCRN, “Evaluation of Nursing Work Effort and Perceptions About Blood Glucose Testing in Tight Glycemic Control”, American Journal of Critical Care, Jul. 2006, vol. 15, No. 4, pp. 370-377.
ASHP Advantage, “Improving Medication Safety in Health Systems Through Innovations in Automation Technology”, Proceedings of Educational Symposium and Educational Sessions during the 39th ASHP Midyear Clinical Meeting, Dec. 5-9, 2004, Orlando, FL, pp. 28.
Beard et al., “Total Quality Pain Management: History, Background, Resources”, Abbott Laboratories, TQPM Survey History, available Feb. 2015 or earlier, pp. 1-3.
Bektas et al., “Bluetooth Communication Employing Antenna Diversity”, Proceedings of Eight IEEE International Symposium on Computers and Communication, Jul. 2003, pp. 6.
Bequette, Ph.D., “A Critical Assessment of Algorithms and Challenges in the Development of a Closed-Loop Artificial Pancreas”, Diabetes Technology & Therapeutics, Feb. 28, 2005, vol. 7, No. 1, pp. 28-47.
Bequette, B. Wayne, Ph.D., “Analysis of Algorithms for Intensive Care Unit Blood Glucose Control”, Journal of Diabetes Science and Technology, Nov. 2007, vol. 1, No. 6, pp. 813-824.
Braun, “Infusomat® Space and Accessories”, Instructions for Use, Nov. 2010, pp. 68. http://corp.bbraun.ee/Extranet/Infusionipumbad/Kasutusjuhendid/Vanad/Kasutusjuhend-Infusomat_Space(vers688J,inglise_k).pdf.
Brownlee, Seth, “Product Spotlight: The Plum A+ with Hospira MedNet Infusion System”, PP&P Magazine, Dec. 2005, vol. 2, No. 7, pp. 2.
Cannon, MD et al., “Automated Heparin-Delivery System to Control Activated Partial Thromboplastin Time”, Circulation, Feb. 16, 1999, vol. 99, pp. 751-756.
Cardinal Health, “Alaris® Syringe Pumps” Technical Service Manual, Copyright 2002-2006, Issue 9, pp. 1-88, http://www.frankshospitalworkshop.com/equipment/documents/infusion_pumps/service_manuals/Cardinal_Alaris_-_Service_Manual.pdf.
“CareAware® Infusion Management”, Cerner Store, as printed May 12, 2011, pp. 3, https://store.cerner.com/items/7.
Chen et al., “Enabling Location-Based Services on Wireless LANs”, The 11th IEEE International Conference on Networks, ICON 2003, Sep. 28-Oct. 1, 2003, pp. 567-572.
“Computer Dictionary”, Microsoft Press, Third Edition, Microsoft Press, 1997, pp. 430 & 506.
“Context-Free Grammar”, Wikipedia.org, as last modified Mar. 5, 2010 in 11 pages, https://en.wikipedia.org/w/index.php/?title=Context-free_grammar&oldid=347915989.
Crawford, Anne J., MSN, RNC, “Building a Successful Quality Pain Service: Using Patient Satisfaction Data and the Clinical Practice Guideline”, USA, 1995, pp. 1-6.
Crocker et al., “Augmented BNF for Syntax Specifications: ABNF”, Network Working Group, Standards Track, Jan. 2008, pp. 16.
Davidson et al., “A Computer-Directed Intravenous Insulin System Shown to be Safe, Simple, and Effective in 120,618 h of Operation”, Diabetes Care, Oct. 2005, vol. 28, No. 10, pp. 2418-2423.
Davies, T., “Cordless Data Acquisition in a Hospital Environment”, IEE Colloquium on Cordless Computing—Systems and User Experience, 1993, pp. 4.
Dayhoff et al., “Medical Data Capture and Display: The Importance of Clinicians' Workstation Design”, AMIA, Inc., 1994, pp. 541-545.
Diabetes Close Up, Close Concerns AACE Inpatient Management Conference Report, Consensus Development Conference on Inpatient Diabetes and Metabolic Control, Washington, D.C., Dec. 14-16, 2003, pp. 1-32.
East PhD et al., “Digital Electronic Communication Between ICU Ventilators and Computers and Printers”, Respiratory Care, Sep. 1992, vol. 37, No. 9, pp. 1113-1122.
Einhorn, George W., “Total Quality Pain Management: A Computerized Quality Assessment Tool for Postoperative Pain Management”, Abbott Laboratories, Chicago, IL, Mar. 2, 2000, pp. 1-4.
Eskew et al., “Using Innovative Technologies to Set New Safety Standards for the Infusion of Intravenous Medications”, Hospital Pharmacy, 2002, vol. 37, No. 11, pp. 1179-1189.
Felleiter et al., “Data Processing in Prehospital Emergency Medicine”, International journal of Clinical Monitoring and Computing, Feb. 1995, vol. 12, No. 1, pp. 37-41.
Fogt et al., Development and Evaluation of a Glucose Analyzer for a Glucose-Controlled Insulin Infusion System (Biostator®), Clinical Chemistry, 1978, vol. 24, No. 8, pp. 1366-1372.
Gage et al., “Automated Anesthesia Surgery Medical Record System”, International Journal of Clinical Monitoring and Computing, Dec. 1990, vol. 7, No. 4, pp. 259-263.
Galt et al., “Personal Digital Assistant-Based Drug Information Sources: Potential to Improve Medication Safety”, Journal of Medical Library Association, Apr. 2005, vol. 93, No. 2, pp. 229-236.
Gardner, Ph.D. et al., “Real Time Data Acquisition: Recommendations for the Medical Information Bus (MIB)”, 1992, pp. 813-817.
“General-Purpose Infusion Pumps”, Health Devices, EXRI Institute, Oct. 1, 2002, vol. 31, No. 10, pp. 353-387.
Givens et al., “Exploring the Internal State of User Interfaces by Combining Computer Vision Techniques with Grammatical Inference”, Proceedings of the 2013 International Conference on Software Engineering, San Francisco, CA, May 18-26, 2013, pp. 1165-1168.
Glaeser, “A Hierarchical Minicomputer System for Continuous Post-Surgical Monitoring”, Computers and Biomedical Research, Aug. 31, 1975, pp. 336-361.
Goldberg et al., “Clinical Results of an Updated Insulin Infusion Protocol in Critically Ill Patients”, Diabetes Spectrum, 2005, vol. 18, No. 3, pp. 188-191.
Gomez et al., “CLAM: Connection-Less, Lightweight, and Multiway Communication Support for Distributed Computing”, Computer Science, 1997, vol. 1199, pp. 227-240.
“GPS Tracker for Medical Equipment”, http://www.trackingsystem.com/forbusinesses/corporate-trackingsystem/1098-gps-tracker-formedicalequipment.html, Mar. 15, 2015, pp. 2.
Graseby, “Model 3000/500 and Micro 3100/505: Volumetric Infusion Pump”, Technical Service Manual, Graseby Medical Ltd., Apr. 2002, Issue A, pp. 160.
Graseby, “Model 3000/500 and Micro 3100/505: Volumetric Infusion Pump: Illustrated Parts List for Pump Serial Numbers from 3000 to 59,999”, Technical Service Manual, Graseby Medical Ltd., Apr. 2002, Issue A, pp. 71.
Halpern et al., “Changes in Critical Care Beds and Occupancy in the United States 1985-2000: Differences Attributable to Hospital Size”, Critical Care Medical, Aug. 2006, vol. 34, No. 8, pp. 2105-2112.
Hamann et al., “PUMPSIM: A Software Package for Simulating Computer-Controlled Drug Infusion Pumps”, Annual International Conference of the IEEE Engineering in Medicine and Biology Society, 1990, vol. 12, No. 5, pp. 2019-2020.
Hasegawa et al., “On a Portable Memory Device for Physical Activities and Informations of Maternal Perception”, Journal of Perinatal Medicine, 1988, vol. 16, No. 4, pp. 349-356.
Hawley et al., “Clinical Implementation of an Automated Medical Information Bus in an Intensive Care Unit”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 9, 1988, pp. 621-624.
Hayes-Roth et al., “Guardian: A Prototype Intelligent Agent for Intensive-Care Monitoring”, Artificial Intelligence in Medicine, vol. 4, Dec. 31, 1992, pp. 165-185.
Hospira, GemStar® Pain Management Infusion System 9-084-PR1-2-2, www.hospira.com/products/gemstar_painmanagement.aspx, Jan. 28, 2010, pp. 1-2.
Introducing Abbott TQPM (Total Quality Pain Management), Abbott Laboratories, Abbott Park, IL, May 2000, pp. 1-4.
“Infusion Pump”, Wikipedia.org, as last modified Mar. 27, 2014, in 3 pages, https://web.archive.org/web/20140703024932/https://en.wikipedia.org/wiki/Infusion_pump.
International Preliminary Report on Patentability and Written Opinion received in PCT Application No. PCT/US2015/028551, dated Nov. 10, 2016 in 9 pages.
International Search Report and Written Opinion received in PCT Application No. PCT/US2015/028551, dated Jul. 29, 2015 in 10 pages.
Isaka et al., “Control Strategies for Arterial Blood Pressure Regulation”, IEEE Transactions on Biomedical Engineering, Apr. 1993, vol. 40, No. 4, pp. 353-363.
Johnson et al., “Using BCMA Software to Improve Patient Safety in Veterans Administration Medical Centers”, Journal of Healthcare Information Management, Dec. 6, 2004, vol. 16, No. 1, pp. 46-51.
Kent Displays, “Reflex™ Electronic Skins”, Product Brief 25127B, 2009, pp. 2.
Kent Displays, “Reflex Electronic Skins Engineering Evaluation Kit”, 25136A, Mar. 10, 2009.
Lefkowitz et al., “A Trial of the Use of Bar Code Technology to Restructure a Drug Distribution and Administration System”, Hospital Pharmacy, Mar. 31, 1991, vol. 26, No. 3, pp. 239-242.
Lenssen et al., “Bright Color Electronic Paper Technology and Applications”, IDS '09 Publication EP1-2 (Phillips Research), 2009, pp. 529-532.
Leveson, Nancy, “Medical Devices: The Therac-25”, Appendix A, University of Washington, 1995, pp. 49.
Linkens, D.A. “Computer Control for Patient Care”, Computer Control of Real-Time Processes, IEE Control Engineering Series 41, 1990, Ch. 13, pp. 216-238.
Mako Hill et al., “The Official Ubuntu Book”, Shoeisha Co., Ltd., 1st Edition, Jun. 11, 2007, pp. 115 to 125.
Marshall, et al., “New Microprocessor-Based Insulin Controller”, IEEE Transactions on Biomedical Engineering, Nov. 1983, vol. BME-30, No. 11, pp. 689-695.
Martino et al., “Automation of a Medical Intensive Care Environment with a Flexible Configuration of Computer Systems”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 5, 1980, vol. 3, pp. 1562-1568.
Matsunaga et al., “On the Use of Machine Learning to Predict the Time and Resources Consumed by Applications”, 2010 10th IEEE/ACM International Conference on Cluster, Cloud and Grid Computing (CCGrid), May 17-20, 2010, pp. 495-504.
Mauseth et al., “Proposed Clinical Application for Tuning Fuzzy Logic Controller of Artificial Pancreas Utilizing a Personalization Factor”, Journal of Diabetes Science and Technology, Jul. 2010, vol. 4, No. 4, pp. 913-922.
Medfusion™, “Medfusion Syringe Infusion Pump Model 4000”, Operator's Manual, Software Version V1.1, Sep. 2011, pp. 154. http://www.medfusionpump.com/assets/literature/manuals/Operators_Manual_4000_40-5760-51A.pdf.
Metnitz et al., “Computer Assisted Data Analysis in Intensive Care: the ICDEV Project-Development of a Scientific Database System for Intensive Care”, International Journal of Clinical Monitoring and Computing, Aug. 1995, vol. 12, No. 3, pp. 147-159.
Micrel Medical Devices, “MP Daily +” http://web.archive.org/web/20130803235715/http://www.micrelmed.com/index.aspx?productid=9 as archived Aug. 3, 2013 in 1 page.
Moghissi, Etie, MD, FACP, FACE, “Hyperglycemia in Hospitalized Patients”, A Supplement to ACP Hospitalist, Jun. 15, 2008, pp. 32.
Murray, Jr. et al., “Automated Drug Identification System (during surgery)”, IEEE Proceedings of Southeastcon '91, Apr. 7-10, 1991, pp. 265.
Nicholson et al., “‘Smart’ Infusion Apparatus for Computation and Automated Delivery of Loading, Tapering, and Maintenance Infusion Regimens of Lidocaine, Procainamide, and Theophylline”, Proceedings of the Seventh Annual Symposium on Computer Applications in Medical Care, Oct. 1983, pp. 212-213.
Nolan et al., “The P1073 Medical Information Bus Standard: Overview and Benefits for Clinical Users”, 1990, pp. 216-219.
Omnilink Systems, Inc., “Portable Medical Equipment Tracking”, http://www.omnilink.com/portablemedicalequipmenttracking/, Mar. 15, 2015, pp. 2.
O'Shea, Kristen L., “Infusion Management: Working Smarter, Not Harder”, Hospital Pharmacy, Apr. 2013, vol. 48, No. 3, pp. S1-S14.
Package Management in Debian GNU/Linux, Debian GNU/Linux Expert Desktop Use Special, Giutsu-Hyohron Co., Ltd., First Edition, Sep. 25, 2004, pp. 183-185.
Passos et al., “Distributed Software Platform for Automation and Control of General Anaesthesia”, Eighth International Symposium on Parallel and Distributed Computing, ISPDC '09, Jun. 30-Jul. 4, 2009, pp. 8.
Philips, “IntelliSpace Event Management and IntelliVue Patient Monitoring”, Release 10, 2011, http://incenter.medical.philips.com/doclib/enc/fetch/2000/4504/577242/577243/577247/582646/583147/8359175/Philips_Patient_Monitoring_and_IntelliSpace_Event_Management_Interoperability.pdf%3fnodeid%3d8508574%26vernum%3d-2, pp. 2.
Pretty et al., “Hypoglycemia Detection in Critical Care Using Continuous Glucose Monitors: An in Silico Proof of Concept Analysis”, Journal of Diabetes Science and Technology, Jan. 2010, vol. 4, No. 1, pp. 15-24.
Rappoport, Arthur E., “A Hospital Patient and Laboratory machine-Readable Identification System (MRIS) Revisited”, Journal of Medical Systems, Apr. 1984, vol. 8, Nos. 1/2, pp. 133-156.
Ritchie et al., “A Microcomputer Based Controller for Neuromuscular Block During Surgery”, Annals of Biomedical Engineering, Jan. 1985, vol. 13, No. 1, pp. 3-15.
Saager et al., “Computer-Guided Versus Standard Protocol for Insulin Administration in Diabetic Patients Undergoing Cardiac Surgery”, Annual Meeting of the American Society of Critical Care Anesthesiologists, Oct. 13, 2006.
Sanders et al., “The Computer in a Programmable Implantable Medication System (PIMS)”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 2, 1982, pp. 682-685.
Schilling et al., “Optimizing Outcomes! Error Prevention and Evidence-Based Practice with IV Medications”, A Pro-Ce Publication, Hospira, Inc., Feb. 6, 2012, pp. 56.
Schulze et al., “Advanced Sensors Technology Survey”, Final Report, Feb. 10, 1992, pp. 161.
Scott, et al., “Using Bar-Code Technology to Capture Clinical Intervention Data in a Hospital with a Stand-Alone Pharmacy Computer System”, Mar. 15, 1996, American Journal of Health-System Pharmacy, vol. 53, No. 6, pp. 651-654.
Sebald et al., “Numerical Analysis of a Comprehensive in Silico Subcutaneous Insulin Absorption Compartmental Model”, 31st Annual International Conference of the IEEE Engineering in Medicine and Biology Society, Sep. 2-6, 2009, pp. 3901-3904.
Shabot, M. Michael, “Standardized Acquisition of Bedside Data: The IEEE P1073 Medical Information Bus”, International Journal of Clinical Monitoring and Computing, vol. 6, Sep. 27, 1989, pp. 197-204.
Sheppard, Louis, Ph.D., “Automation of the Infusion of Drugs Using Feedback Control”, Journal of Cardiothoracic and Vascular Anesthesia, Feb. 28, 1989, vol. 3, No. 1, pp. 1-3.
Sheppard, Louis, Ph.D., “Computer Control of the Infusion of Vasoactive Drugs”, Annals of Biomedical Engineering, Jul. 1980, vol. 8, No. 4-6, pp. 431-444.
Sheppard, Louis, Ph.D., “The Application of Computers to the Measurement, Analysis, and Treatment of Patients Following Cardiac Surgical Procedures”, The University of Alabama in Birmingham, Oct. 31, 1977, pp. 297-300.
Sheppard, Louis, Ph.D., “The Computer in the Care of Critically Ill Patients”, Proceedings of the IEEE, Sep. 1979, vol. 67, No. 9, pp. 1300-1306.
“Sigma Spectrum: Operator's Manual”, Oct. 2009, pp. 72. http://static.medonecapital.com/manuals/userManuals/Sigma-Spectrum-Operator-Manual-October-2009.pdf.
Simonsen, Michael Ph.D., POC Testing, New Monitoring Strategies on Fast Growth Paths in European Healthcare Arenas, Biomedical Business & Technology, Jan. 2007, vol. 30, No. 1, pp. 1-36.
Siv-Lee et al., “Implementation of Wireless ‘Intelligent’ Pump IV Infusion Technology in a Not-for-Profit Academic Hospital Setting”, Hospital Pharmacy, Sep. 2007, vol. 42, No. 9, pp. 832-840. http://www.thomasland.com/hpj4209-832.pdf.
Slack, W.V., “Information Technologies for Transforming Health Care”, https://www.andrew.cmu.edu/course/90-853/medis.dir/otadocs.dir/03ch2.pdf, Ch. 2, 1995, pp. 29-78.
Smith, Joe, “Infusion Pump Informatics”, CatalyzeCare: Transforming Healthcare, as printed May 12, 2011, pp. 2.
Sodders, Lisa, “VA Center Keeps Medicine in Right Hands”, The Capital-Journal, Dec. 4, 1999, pp. 1-2.
Stitt, F.W., “The Problem-Oriented Medical Synopsis: a Patient-Centered Clinical Information System”, Proceedings of the Annual Symposium on Computer Application in Medical Care, 1994, pp. 88-92.
Stokowski, Laura A. RN, MS, “Using Technology to Improve Medication Safety in the Newborn Intensive Care Unit”, Advances in Neonatal Care, Dec. 2001, vol. 1, No. 2, pp. 70-83.
Szeinbach et al., “Automated Dispensing Technologies: Effect on Managed Care”, Journal of Managed Care Pharmacy (JMCP), Sep./Oct. 1995, vol. 1, No. 2, pp. 121-127.
Szolovits et al., “Guardian Angel: Patient-Centered Health Information Systems”, Technical Report MIT/LCS/TR-604, Massachusetts Institute of Technology Laboratory for Computer Science, May 1994, pp. 39.
Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in Critically Ill Patients”, The New England Journal of Medicine, Nov. 8, 2001, vol. 345, No. 19, pp. 1359-1367.
Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in the Medical ICU”, The New England Journal of Medicine, Feb. 2, 2006, vol. 354, No. 5, pp. 449-461.
Van Der Maas et al., “Requirements for Medical Modeling Languages”, Journal of the American Medical Informatics Association, Mar./Apr. 2001, vol. 8, No. 2, pp. 146-162.
Villalobos et al., “Computerized System in Intensive Care medicine”, Medical Informatics, vol. 11, No. 3, 1986, pp. 269-275.
Wilkins et al., “A Regular Language: The Annotated Case Report Form”, PPD Inc., PharmaSUG2011—PaperCD18, 2011, pp. 1-9.
Ying et al., “Regulating Mean Arterial Pressure in Postsurgical Cardiac Patients. A Fuzzy Logic System to Control Administration of Sodium Nitroprusside”, IEEE Engineering in Medicine and Biology Magazine, vol. 13, No. 5, Nov.-Dec. 1994, pp. 671-677.
Yue, Ying Kwan, “A Healthcare Failure Mode and Effect Analysis on the Safety of Secondary Infusions”, Thesis, Institute of Biomaterials and Biomedical Engineering, University of Toronto, 2012, pp. 168.
Yurkonis et al., “Computer Simulation of Adaptive Drug Infusion”, IEEE Transactions on Biomedical Engineering, vol. BME-34, No. 8, Aug. 1987, pp. 633-635.
Zakariah et al., “Combination of Biphasic Transmittance Waveform with Blood Procalcitonin Levels for Diagnosis of Sepsis in Acutely Ill Patients”, Critical Care Medicine, 2008, vol. 36, No. 5, pp. 1507-1512.
Ahn et al., “Towards Scalable Authentication in Health Services”, Eleventh IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, Jun. 2002, pp. 83-88.
Bellare et al., “Security Proofs for Identity-Based Identification and Signature Schemes”, Lecture Notes in Computer Science, Jan. 2009, vol. 22, No. 1, pp. 18.
Doesburg et al., “Improved Usability of a Multi-Infusion Setup Using a Centralized Control Interface: A Task-Based Usability Test”, Aug. 11, 2017, PLoS One, vol. 12, No. 8, pp. 10.
Huang et al., “Secure Identity-Based Data Sharing and Profile Matching for Mobile Healthcare Social Networks in Cloud Computing”, vol. 6, Jul. 2018, pp. 36584-36594.
Li et al., “Hijacking an Insulin Pump: Security Attacks and Defenses for a Diabetes Therapy System”, 2011 IEEE 13th International Conference on e-Health Networking, Applications and Services, 2011, pp. 150-156.
Michienzi, Kelly, “Managing Drug Library Updates”, Pharmacy Purchasing Products, https://www.pppmag.com/article/1061, Feb. 2012, vol. 9, pp. 22-23.
“Sigma Spectrum: Operator's Manual”, May 15, 2008, pp. 63. <https://usme.com/content/manuals/sigma-spectrum-operator-manual.pdf>.
“TCG TPM v2.0 Provisioning Guidance”, Reference, Version 1, Revision 1, Mar. 15, 2017, pp. 1-43.
Related Publications (1)
Number Date Country
20210252210 A1 Aug 2021 US
Provisional Applications (1)
Number Date Country
61986562 Apr 2014 US
Continuations (4)
Number Date Country
Parent 16846882 Apr 2020 US
Child 17157597 US
Parent 16408272 May 2019 US
Child 16846882 US
Parent 15674889 Aug 2017 US
Child 16408272 US
Parent 14700357 Apr 2015 US
Child 15674889 US