Disposable infusion fluid delivery device for programmable large volume drug delivery

Information

  • Patent Grant
  • 12156986
  • Patent Number
    12,156,986
  • Date Filed
    Tuesday, April 11, 2023
    a year ago
  • Date Issued
    Tuesday, December 3, 2024
    a day ago
Abstract
A disposable electronically controlled infusion pump system includes at least one disposable infusion container and at least one disposable electronically controlled medication pumping system. The at least one disposable infusion container is configured to contain infusion fluid. The at least one disposable electronically controlled medication pumping system is fluidly connected to the at least one disposable infusion container. The at least one disposable electronically controlled medication pumping system includes an infusion channel, a disposable electronically controlled micropump, and valves, but may further include a microprocessor, a memory, a battery or a power receiver configured to wirelessly receive power, a wireless communication device, and other components. The memory is in electronic communication with the microprocessor. The wireless communication device is configured to receive a wireless signal which wirelessly controls the at least one disposable electronically controlled medication pumping system. The disposable electronically controlled micropump is configured to pump the infusion fluid through the infusion channel. The valves are connected to the infusion channel.
Description
FIELD OF THE DISCLOSURE

This disclosure relates to a disposable electronically controlled infusion pump system which includes a micropump and is configured for large volume drug delivery. This system is designed to be used only once for a particular patient, and then disposed of. The disposable electronically controlled infusion pump system is configured to be wirelessly controlled by a non-disposable microcontroller which has a micropump in electronic communication with an interface. The non-disposable microcontroller and the interface are configured to be reused to control additional disposable electronically controlled pump infusion systems after they are disconnected or decoupled from the first disposable electronically controlled infusion pump system. The disclosure further relates to a method for delivering infusion fluid to a patient utilizing the disposable electronically controlled infusion pump system, the non-disposable microcontroller, and the interface.


BACKGROUND

Existing infusion systems typically utilize bulky and complex electromechanical pump devices, which range from five pounds in weight up to 18 lbs., for large volume drug delivery. These electromechanical pump devices are large in size, heavy, require special mounting and handling hardware, are noisy, and are difficult to sterilize. Utilization of these electromechanical pump devices requires a substantial capital investment in procurement and periodic maintenance. Moreover, these electromechanical pump devices require the availability of adequate electric power and batteries. Other existing infusion systems may experience additional issues.


An infusion system and method is needed to reduce or eliminate one or more issues of one or more of the existing infusion systems.


SUMMARY

In one embodiment, a disposable electronically controlled infusion pump system includes at least one disposable infusion container and a disposable electronically controlled medication pumping system. The at least one disposable infusion container is configured to contain infusion fluid. The disposable electronically controlled medication pumping system is fluidly connected to the at least one disposable infusion container. The disposable electronically controlled medication pumping system includes an infusion channel, a disposable electronically controlled micropump, air in line sensors, and active valves for pumping, and may further include a microprocessor, a memory, a battery or power receiver configured to wirelessly receive power, a wireless communication device, and other components. The memory is in electronic communication with the microprocessor. The wireless communication device is configured to receive a wireless signal which wirelessly controls the disposable electronically controlled medication pumping system. The disposable electronically controlled micropump is configured to pump the infusion fluid through the infusion channel. The valves are operably connected to the infusion channel to sequence and control the flow.


In another embodiment, an infusion pump system includes a non-disposable microcontroller, at least one disposable infusion container, and at least one disposable electronically controlled medication pumping system. The non-disposable microcontroller includes a first microprocessor, a first memory in electronic communication with the first microprocessor, a battery or power source, a power transmitter connected to the battery or power source and configured to transmit power, and a first wireless communication device. The at least one disposable infusion container is configured to contain infusion fluid. The at least one disposable electronically controlled medication pumping system, controlled by the non-disposable microcontroller, is fluidly connected to the at least one disposable infusion container. The at least one disposable electronically controlled medication pumping system includes a second microprocessor, a second memory in electronic communication with the second microprocessor, a power receiver configured to wirelessly receive power from the power transmitter, a second wireless communication device configured to wirelessly communicate with the first wireless communication device, an infusion channel, a disposable electronically controlled micropump configured to pump the infusion fluid through the infusion channel, air in line sensor and valves operably connected to the infusion channel to control or sequence the flow.


In another embodiment, an infusion pump system includes a non-disposable microcontroller, at least one disposable infusion container, and at least one disposable electronically controlled medication pumping system. The non-disposable microcontroller includes a first microprocessor, a first memory in electronic communication with the first microprocessor, a battery or other power source, a power transmitter connected to the power source and configured to transmit power, and a first wireless communication device. The at least one disposable infusion container is configured to contain infusion fluid. The at least one disposable electronically controlled medication pumping system, controlled by the non-disposable microcontroller, is a ganged system fluidly connected to the at least one disposable infusion container. The at least one disposable electronically controlled medication pumping system includes an infusion channel, at least two disposable electronically controlled micropumps configured to pump the infusion fluid through the infusion channel, and valves operably connected to the infusion channel. The at least one medication pumping system may also include a second microprocessor, a second memory in electronic communication with the second microprocessor, a power receiver configured to receive power from the power transmitter, a second wireless communication device configured to wirelessly communicate with the first wireless communication device, and other components. Other of at least one disposable electronically controlled medication pumping systems may further include a third microprocessor, a third memory in electronic communication with the third microprocessor, a power receiver configured to receive power from the power transmitter, a third wireless communication device configured to wirelessly communicate with the first wireless communication device or the second wireless communication device.


In still another embodiment, a method is disclosed for delivering infusion fluid from an electronically controlled infusion system. In one step, a disposable infusion fluid delivery device is provided including at least one disposable infusion container and a disposable electronically controlled medication pumping system. In another step, a pre-determined amount of infusion fluid is disposed into the at least one disposable infusion container. In an additional step, the disposable infusion fluid delivery device containing the infusion fluid in the at least one disposable infusion container is delivered to a location at which the patient is located. In yet another step, the disposable electronically controlled medication pumping system of the disposable infusion fluid delivery device is wirelessly controlled and wirelessly powered with a non-disposable microcontroller to infuse the infusion fluid from the disposable infusion container of the disposable infusion fluid delivery device. In another step, the disposable infusion fluid delivery device is disposed of after the infusion fluid is infused so that the disposable infusion fluid delivery device is only used one time, for a single patient,


The scope of the present disclosure is defined solely by the appended claims and is not affected by the statements within this summary.





BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure can be better understood with reference to the following drawings and description. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure.



FIG. 1 illustrates a block diagram of one embodiment of an electronically controlled infusion pump system configured to infuse infusion fluid;



FIG. 2 illustrates a block diagram of another embodiment of an infusion pump system configured to infuse infusion fluid;



FIG. 3 illustrates a block diagram of another embodiment of an infusion pump system configured to infuse infusion fluid;



FIG. 4 illustrates a block diagram of another embodiment of an infusion pump system configured to infuse infusion fluid;



FIG. 5 illustrates a block diagram of another embodiment of an infusion pump system configured to infuse infusion fluid; and



FIG. 6 illustrates a flowchart of one embodiment of a method for delivering infusion fluid.





DETAILED DESCRIPTION


FIG. 1 illustrates a block diagram of one embodiment of an infusion pump system 10 configured to infuse infusion fluid. The infusion pump system 10 comprises an interface 12, a dedicated non-disposable microcontroller other devices such as existing pump systems, PC, tablets, and smartphones can be used to control disposable pumps providing they have necessary power charging attachments and wireless communication capabilities 14, and a disposable infusion fluid delivery device 16. In other embodiments, the components of the infusion pump system 10 may vary in configuration, type, or function.


For purposes of this disclosure, the term “disposable” means used once for a particular patient and then disposed of (i.e. thrown away or destroyed). For purposes of this disclosure, the term “disposable” means that the component is made of a disposable material such as plastic or another inexpensive material, which is only needed for single patient, one-time use and will not have to be sterilized after first use due to its disposal instead of re-use for the same or different (multiple) patients. For purposes of this disclosure, the term “non-disposable” means that the component will be repeatedly used for the infusion of infusion fluid to the same or varying patients. Disposable items are sometimes used in the medical field because those items come in contact with hazardous medical fluids or bodily fluids. Disposable items can be disposed of rather than being used beyond the recommended time on a given patient or on a different patient with the risk of cross-contamination, infections, or other reactions. Non-disposable items are advantageously reusable with proper isolation, cleaning, disinfection, or sterilization between uses on the same or different patients. In the case of uses on different patients, isolation, cleaning, disinfecting, or sterilizing an item between uses can help reduce the likelihood of transmission of germs, staff, bacteria or other contamination, but can be difficult to accomplish completely or effectively.


The interface 12 comprises a device which is configured to interface with the non-disposable microcontroller 14 in order to power and electronically control the non-disposable microcontroller 14 which in turn powers and electronically controls the disposable infusion fluid delivery device 16. In other embodiments, the interface 12 may be used to only power or to only electronically control the non-disposable microcontroller 14 which in turns powers and/or electronically controls the disposable infusion fluid delivery device 16. The interface 12 may comprise a smartphone, a laptop, a stand-alone computer, a nurse station, an infusion pump, or another type of device. The interface 12 may be in wired or wireless communication with the non-disposable microcontroller 14.


In one embodiment, the non-disposable microcontroller 14 and the disposable infusion fluid delivery device 16 are not configured to work at all until the non-disposable microcontroller 14 is connected to the interface 12. In another embodiment, the system 10 may be configured to operate without the interface 12 with the non-disposable microcontroller 14 exclusively powering and/or electronically controlling the disposable infusion fluid delivery device 16. The interface 12 and the non-disposable microcontroller 14 are configured to be used as many times as needed (i.e. non-disposable for repeated use) to electronically power and control differing disposable infusion fluid delivery devices 16 to deliver infusion fluid to varying patients without the interface 12 or the non-disposable microcontroller 14 ever coming into contact with either the disposable infusion fluid delivery device 16 or the infusion fluid delivered by the disposable infusion fluid delivery device 16.


The disposable infusion fluid delivery device 16, which contains a programmed pre-determined amount and type of infusion fluid for a particular patient, is configured to be a stand-alone device which is only used for the particular patient and then disposed of immediately after use. Due to the disposable infusion fluid delivery device 16 never coming into contact with either the interface 12 or the non-disposable microcontroller 14, neither the interface 12 nor the non-disposable microcontroller 14 need to be sterilized. Additionally, since the disposable infusion fluid delivery device 16 is disposed of immediately after use on the particular patient it was intended for, it also does not need to be sterilized after use. As a result, significant time and cost involved in sterilization is saved, in addition to decreasing the health risk which is typically associated with sterilization deficiencies.


The non-disposable microcontroller 14 comprises a first microprocessor 18, a first memory 20, a first wireless communication device 22, a power transmitter 24, a power source 26 such as A/C and/or a battery, and a multiplexer 28. The first processor 18 is in communication with each of the first memory 20, the first wireless communication device 22, the power transmitter 24, the battery 26, and the multiplexer 28. In other embodiments, the components of the non-disposable microcontroller 14 may vary in configuration, type, or function.


The disposable infusion fluid delivery device 16 comprises at least one disposable infusion container 30, a seal 32, a temperature sensor 33, air in line sensor, flow sensor, active valves and a disposable medication pumping system 34. In other embodiments, the components of the disposable infusion fluid delivery device 16 may vary in configuration, type, or function. The disposable medication pumping system 34 comprises a second microprocessor 36, a second memory 38, a second wireless communication device 40, a power receiver 42, an infusion channel 44, a micropump 45, valves 46, one or more piezo actuators 48, a pressure detection sensor 50, a flow detection sensor 52, an air detection sensor 54, an optional one-dimensional, two-dimensional, holographic or other type of barcode 56, and a Radio Frequency Identification Tag 58. The second processor 36 is in communication with each of the temperature sensor 33, the second memory 38, the second wireless communication device 40, the power receiver 42, the micropump 45, the active valves 46, the piezo actuators 48, the pressure detection sensor 50, the flow detection sensor 52, the air detection sensor 54, the barcode 56, and the Radio Frequency Identification Tag 58. In other embodiments, the components of the disposable medication pumping system 34 may vary in configuration, type, or function. The disposable infusion fluid delivery device 16 may comprise an integral sealed cartridge containing all components of the disposable infusion fluid delivery device 16. In other embodiments, the disposable infusion fluid delivery device 16 and its components may vary in configuration, type, or function.


In one embodiment, the non-disposable microcontroller 14 has a size in a range of 9×6 cm and a weight in a range of 100-200 grams. In another embodiment, the non-disposable microcontroller 14 has a size in a range of 6×4 cm and a weight in a range of 50-100 grams. In still another embodiment, the non-disposable microcontroller 14 has a size in a range of 5×3 cm and a weight in a range of 25-50 grams. In other embodiments, the size and weight of the non-disposable microcontroller 14 may vary.


The first microprocessor 18 operates based on programming instructions and data saved in the first memory 20. The programming instructions and data saved in the first memory 20 may be pre-stored, or obtained from any source in the hospital information system, for example through interface 12. The programming instructions and data can be obtained from the second memory 38 of the disposable infusion fluid delivery device 16, from the temperature sensor 33, from the pressure detection sensor 50, from the flow detection sensor 52, from the air detection sensor 54, from the barcode 56, from the Radio Frequency Identification Tag 58, or obtained from another source. The programming instructions and data may have been set-up in in the first memory 20 or in the second memory 38 by the drug preparer (i.e., the pharmacy) based on the patient's drug prescription from a doctor. In other embodiments, a doctor or other medical provider may set-up this information into the first memory 20 or into the second memory 38 of the disposable infusion fluid delivery device 16. In still other embodiments, the programming instructions and data may have been set-up in in the first memory 20 or in the second memory 38 in varying ways.


This data may comprise any combination of the following information: a name or identification of the drug preparer that prepared the infusion fluid contained in the disposable infusion fluid delivery device 16 (this could be a drug manufacturer, pharmacy or a compounder of the infusion fluid); a date the infusion fluid was placed into or added to the disposable infusion fluid delivery device 16; a date the infusion fluid contained in the disposable infusion fluid delivery device 16 is to expire; a manufacturing date, serial number, storage information (temperature/time) a time related to the infusion of the infusion fluid contained in the disposable infusion fluid delivery device 16; an identification of the infusion fluid contained in the disposable infusion fluid delivery device 16; a drug identification of the infusion fluid contained in the disposable infusion fluid delivery device 16, which may include a drug name and concentration, a drug identification number, and diluent information; a volume of the infusion fluid contained in the infusion delivery device 16 to be infused into the patient, or a volume of the infusion fluid infused into the patient; a flow rate (programmed and/or actual) of the infusion fluid; a duration or delivery time of the infusion fluid; a power status and/or used or remaining battery capacity of the interface 12, of the non-disposable microcontroller 14, or of the disposable infusion fluid delivery device 16; a charging status of the interface 12, of the non-disposable microcontroller 14, or of the disposable infusion fluid delivery device 16; an identification or name of the patient; a RX order number or order ID; a therapy start time; a therapy end time; a delivery time; one or more alarm conditions; a flow sensor output (flow rate); a pressure sensor output (pressure); an air-in-line sensor output (single bubble or cumulative air volume); temperature data; data regarding parameters for infusion of the infusion fluid for the particular patient; or other types of information.


The first wireless communication device 22 is configured to wirelessly communicate with the second wireless communication device 40 to allow the non-disposable microcontroller 14 and the disposable infusion fluid delivery device 16 to communicate with one another. In one embodiment, the first wireless communication device 22 and the second wireless communication device 40 may comprise a Near-Field communication device. In other embodiments, the first wireless communication device 22 and the second wireless communication device 40 may vary in type or configuration. The power transmitter 24 is configured to wirelessly transmit power or energy to the power receiver 42 (which may comprise a battery) of the disposable infusion fluid delivery device 16 in order to power the operation of disposable infusion fluid delivery device 16. In one embodiment, the power or energy transmitter 24 may utilize Near-Field Charging (capacitive, inductive energy charging) to wirelessly charge the power receiver 42. In other embodiments, the power transmitter 24 may charge the power receiver 42 utilizing varying charging methods.


The power source 26 (in non-disposable controller) is configured in one embodiment as one or more disposable or rechargeable batteries that store electrical energy and provide energy to the power transmitter 24. The multiplexer 28 is configured to electronically and wirelessly control a plurality of the disposable electronically controlled medication pumping systems 34 (only one disposable electronically controlled medication pumping system 34 is shown in FIG. 1, however FIG. 3 discussed later shows an embodiment having a plurality of the disposable electronically controlled medication pumping systems 34 being concurrently electronically and wirelessly controlled by the multiplexer 28 to deliver different infusion fluids or to provide a redundant and highly reliable infusion system). Each disposable electronically controlled medication system 34 have capability to communicate with non-disposable controller and other disposable electronically controlled medication systems. This communication capability will further increase the redundancy and reliability of the entire system and would create a topology of a complex medication delivery system that in parallel can deliver a higher combined rate of fluid delivery or in series can deliver greater accumulated volumes.


The at least one disposable infusion container 30 is configured to contain infusion fluid. At least one hermetic seal 32 permanently seals the at least one disposable infusion container 30 to the disposable medication pumping system 34 so that after the drug preparer (manufacturer or pharmacy) disposes the infusion fluid within the at least one disposable infusion container 30 no one else comes in contact with the infusion fluid other than the patient since the disposable infusion fluid delivery device 16 is disposed of after the one-time use for the intended patient. The temperature sensor 33 keeps track of a temperature the disposable infusion fluid delivery device 16 is exposed to throughout its lifetime so that it is ensured that a temperature range requirement for the infusion fluid was not violated during storage, shipping or handling prior to infusion. If the temperature range was violated during the storage or transportation of the disposable infusion container, the infusion would not be permitted. Any of the interface 12, the non-disposable microcontroller 14, and the disposable infusion fluid delivery device 16 may be configured to analyze data emulating from the temperature sensor and to compare it to pre-set temperature parameters regarding the infusion fluid in order to ensure the temperature range requirement for the infusion fluid was not violated, and if it was, to prevent infusion of the infusion fluid.


In one embodiment, the micropump disclosed in US 2011/0005606 to Bartels et al., which is hereby incorporated by reference, may be used for the disposable electronically controlled micropump 45. The disposable electronically controlled micropump 45 may contain a plurality of electrically activated piezo-actuators 48 to control the pumping of infusion fluid through the infusion channel 44. In one embodiment, the disposable electronically controlled micropump 45 is configured to pump in a range of between 0.1 to 350 milliliters of the infusion fluid per hour with accuracy of +/−10% or better. In one embodiment, the disposable electronically controlled micropump 45 has a size in a range of 8×4 cm and a weight in a range of 50-100 grams. In another embodiment, the disposable electronically controlled micropump 45 has a size in a range of 5×3 cm and a weight in a range of 30-50 grams. In still another embodiment, the disposable electronically controlled micropump 45 has a size in a range of 4×2 cm and a weight in a range of 20-40 grams. In other embodiments, the size and weight of the disposable electronically controlled micropump 45 may vary. The disposable pump can be packaged in a packaging that is capable of providing hermiticity and is compliant with FDA approved materials and capable of withstanding necessary sterilization methods including gamma irradiation, EtO, E-beam, and steam sterilization.


The second microprocessor 36 operates based on programming instructions and data saved in the second memory 38. The programming instructions and data saved in the second memory 38 may be pre-stored, or obtained from any source in the hospital information system, for example through interface 12. The programming instructions and data can be obtained from the first memory 20 of the disposable infusion fluid delivery device 16, from the temperature sensor 33, from the pressure detection sensor 50, from the flow detection sensor 52, from the air detection sensor 54, from the barcode 56, from the Radio Frequency Identification Tag 58, or obtained from another source.


This data may comprise any combination of the following information: a name or identification of the drug preparer that prepared the infusion fluid contained in the disposable infusion fluid delivery device 16; a date the infusion fluid was disposed in the disposable infusion fluid delivery device 16; a date the infusion fluid contained in the disposable infusion fluid delivery device 16 is to expire; a time related to the infusion of the infusion fluid contained in the disposable infusion fluid delivery device 16; an identification of the infusion fluid contained in the disposable infusion fluid delivery device 16; a drug identification of the infusion fluid contained in the disposable infusion fluid delivery device 16; a volume of the infusion fluid contained in the infusion delivery device 16 to be infused into the patient, or a volume of the infusion fluid infused into the patient; a flow rate of the infusion fluid; a delivery time of the infusion fluid; a power status of the interface 12, of the non-disposable microcontroller 14, or of the disposable infusion fluid delivery device 16; a charging status of the interface 12, of the non-disposable microcontroller 14, or of the disposable infusion fluid delivery device 16; an identification or name of the patient; a RX order number; a therapy start time; a therapy end time; a delivery time; one or more alarm conditions; a flow sensor output (flow rate); a pressure sensor output (pressure); an air-in-line sensor output (single bubble or cumulative air volume); temperature data; data regarding parameters for infusion of the infusion fluid for the particular patient; or other types of information. The data can be in the form of near real-time logs of the infusion delivery device's operation.


The infusion channel 44 is configured so that the infusion fluid from the at least one disposable infusion container 30 is flowed or pumped through the infusion channel 44 to the patient. The valves 46 are operatively connected to the infusion channel 44 and, along with the micropump 45, control the flow of the infusion fluid through the infusion channel 44. The valves 46 may comprise passive or active input and output valves controlled by the first microprocessor 18 or the second microprocessor 36. Use of active valves provides inherent free-flow protection and reduces the impact of backpressure and head height variability thus assuring flow rate accuracy. In other embodiments, varying types and configurations of valves 46 may be utilized.


The pressure detection sensor 50 is configured to determine a pressure of the infusion fluid flowing through the infusion channel 44 to provide real-time feedback regarding the infusion fluid pressure. In one embodiment the pressure sensor is downstream or distal with respect to the micropump 45. The flow detection sensor 52 is configured to determine a flow rate of the infusion fluid flowing through the infusion channel 44 to provide real-time feedback regarding delivery accuracy. The air detection sensor 54 is configured to determine a quantity of air in the infusion fluid flowing through the infusion channel 44 to provide real time feedback regarding the air in the infusion fluid.


The barcode 56 provides information regarding the infusion fluid, the particular patient the infusion fluid is intended for, or other information regarding the patient, the infusion fluid, and/or its delivery. The Radio Frequency Identification Tag 58 provides information such as: drug lot; program details; patient information; pump lot; pharmacy information; day and time; or other information regarding the patient, the infusion fluid, and/or its delivery.


Any of the interface 12, the non-disposable microcontroller 14, and the disposable infusion fluid delivery device 16 may be configured to analyze the information provided by the barcode 56 and/or the Radio Frequency Identification Tag 58, to analyze information stored in the first memory 20 or the second memory 38 regarding the infusion fluid, its delivery, or the particular patient, to analyze information sensed by the temperature sensor 33, the pressure detection sensor 50, the flow detection sensor 52, or the air detection sensor 54, or to analyze other information provided from other sources regarding the infusion fluid, its delivery, or the particular patient in order to ensure that patient and infusion delivery parameters are met. This may include making sure that the right infusion fluid is being infused into the right patient, making sure that the infusion fluid is infused using the correct parameters (i.e. time, flow-rate, pressure, air-prevention, temperature, amount delivered, etc.), preventing the disposable infusion fluid device 16 from being reused after it has been used on the intended patient, or ensuring that other patient and/or infusion delivery parameters are followed. If the interface 12, the non-disposable microcontroller 14, or the disposable infusion fluid delivery device 16 determine that the appropriate patient and/or infusion delivery parameters are not being followed they may be configured to adjust the infusion delivery to ensure compliance with these restraints and/or to provide an alert, alarm or stop the infusion.



FIG. 2 illustrates a block diagram of another embodiment of an infusion pump system 10A configured to infuse medication. Components of the system 10A which are identical to the components of system 10 of FIG. 1 have been labeled with identical reference numbers as to those used in FIG. 1. The only difference structurally and functionally between the system 10A of FIG. 2 relative to the system 10 of FIG. 1 is that the power transmitter 24 and power receiver 42 have been removed in the embodiment of FIG. 2, and a battery 60 has been added to the disposable medication pumping system 34 of FIG. 2. In the embodiment of FIG. 2, rather than transmitting power wirelessly from a power transmitter 24 of the non-disposable microcontroller 14 to the power receiver 42 of the disposable electronically controlled medication pumping system 34 to power the disposable electronically controlled medication pumping system 34 as done in FIG. 1, the battery 60 of the disposable electronically controlled medication pumping system 34 is utilized to provide power to the disposable medication pumping system 34. In other embodiments, varying components may be utilized to power the disposable electronically controlled medication pumping system 34.



FIG. 3 illustrates a block diagram of another embodiment of an infusion pump system 10B configured to infuse infusion fluid. Components of the system 10B which are identical to the components of system 10 of FIG. 1 have been labeled with identical reference numbers as to those used in FIG. 1. The only difference structurally and functionally between the system 10B of FIG. 3 relative to the system 10 of FIG. 1 is that the system 10B of FIG. 3 comprises a plurality of the disposable infusion fluid delivery devices 16, each having at least one disposable infusion container 30 and a disposable electronically controlled medication pumping system 34, rather than having only one disposable infusion fluid delivery device 16 as in FIG. 1. The multiplexer 28 of the non-disposable microcontroller 14 is configured to concurrently electronically wirelessly control the plurality of electronically controlled medication pumping systems 34 of the plurality of disposable infusion fluid delivery devices 16 to deliver different infusion fluids or to have a redundant system. In other embodiments, varying components may be utilized to concurrently control the plurality of electronically controlled medication pumping systems 34 of one or more disposable infusion fluid delivery devices 16.


For example, in the embodiment shown in FIG. 4 where the detailed components previously shown in FIGS. 1-3 can still be present but have been omitted from the figure merely for the sake of simplicity, the infusion pump system 10C includes a plurality of electronically controlled medication pumping systems 34 that are fluidly connected to a single container 30 by respective seals 32 to form a disposable infusion fluid delivery device 16. Thus, the plurality of electronically controlled medication pumping systems 34 are each configured with an infusion channel 44, one or more valves 46 operatively associated with the infusion channel 44, and a micropump 45 to draw fluid sequentially or concurrently from a common source such as the disposable infusion container 30. The electronically controlled medication pumping systems 34 can be operated in series or in parallel to provide a desired cumulative flow rate in the range of about 0.1-2000 mL/hr. In the example shown in FIG. 4, a cumulative flow rate in the range of about 0.1-1000 mL/hr can be provided with three medication pumping systems 34 fluidly connected in parallel to a single container 30. A single second microprocessor 36 and second memory 38 can control and serve all of the plurality of medication pumping systems 34 from a location in one of the systems 34, or individual second microprocessors 36 and second memories 38 can control and serve individual electronically controlled medication pumping systems 34 respectively, or second microprocessors 36 and memories 38 can be distributed throughout the medication pumping systems in various other ways. The infusion channels 44 can be joined together with a connector 400 downstream of the micropumps 45 and upstream of the patient 402 to whom the fluid is delivered through a common output line 404. The connector 400 can be inside the disposable infusion fluid delivery device 16, as shown, or outside and downstream of it. Advantageously, the integrated disposable infusion delivery device 16 is a hermitically sealed system capable of withstanding necessary sterilization methods used on the medical fluid container 30, including gamma irradiation, EtO, E-beam, and steam sterilization.



FIG. 5 illustrates another embodiment similar to those described above with respect to FIGS. 1-4 except that the infusion pump system 10D has a single seal 32 or gasket, which is used to integrally attach and fluidly connect the plurality of electronically controlled medication pumping systems 34 to the container 30 or flexible intravenous solution bag to form an integrated disposable infusion fluid delivery device 16.



FIG. 6 illustrates a flowchart of one embodiment of a method 70 for delivering infusion fluid to a patient. The method 70 may utilize any of the systems of FIGS. 1-5. In other embodiments, the method may utilize 70 varying systems having differing components and arrangements or configurations. In step 72 a disposable infusion fluid delivery device, comprising at least one disposable infusion container and at least one disposable electronically controlled medication pumping system, is provided. In step 74 a pre-determined amount of infusion fluid for a particular patient is disposed by a drug preparer, such as a pharmacy, into the at least one disposable infusion container according to a prescription the drug preparer received for the particular patient. In step 76 information regarding the infusion fluid, its delivery, or the particular patient to which the medication is to be infused is stored by the drug preparer, who could be a drug manufacturer, compounder or pharmacist, to a barcode or a Radio Frequency Identification Tag attached to the disposable infusion fluid delivery device, to a first memory of a non-disposable microcontroller, to a second memory of the disposable infusion fluid delivery device, or to another memory.


This information may comprise drug lot, program details, patient information, pump lot, pharmacy information, day and time, or other information regarding the patient, the infusion fluid, and/or its delivery. This information may further comprise any combination of the following information: a name or identification of the drug preparer that prepared the infusion fluid contained in the disposable infusion fluid delivery device; a date the infusion fluid was disposed in the disposable infusion fluid delivery device; a date the infusion fluid contained in the disposable infusion fluid delivery device is to expire; a time related to the infusion of the infusion fluid contained in the disposable infusion fluid delivery device; an identification of the infusion fluid contained in the disposable infusion fluid delivery device; a drug identification of the infusion fluid contained in the disposable infusion fluid delivery device; a volume of the infusion fluid contained in the infusion delivery device to be infused into the patient, or a volume of the infusion fluid infused into the patient; a flow rate of the infusion fluid; a delivery time of the infusion fluid; a power status of the interface, of the non-disposable microcontroller, or of the disposable infusion fluid delivery device; a charging status of the interface, of the non-disposable microcontroller, or of the disposable infusion fluid delivery device; an identification or name of the patient; a RX order number; a therapy start time; a therapy end time; a delivery time; one or more alarm conditions; a flow sensor output (flow rate); a pressure sensor output (pressure); an air-in-line sensor output (cumulative air volume); data regarding parameters for infusion of the infusion fluid for the particular patient; or other types of information.


In step 78 the disposable infusion fluid delivery device containing the infusion fluid disposed in the at least one disposable infusion container is delivered from the drug preparer to a location at which the patient is located. In step 80, at the location at which the patient is located, the non-disposable microcontroller, with or without connection to an interface communicates with the disposable infusion fluid delivery device. In step 82 the information of the barcode or the Radio Frequency Identification Tag attached to the disposable infusion fluid delivery device, information contained in the second memory of the disposable infusion fluid delivery device, information contained in the first memory of the non-disposable microcontroller, or other information contained in another memory is wirelessly communicated to and/or read by the non-disposable microcontroller or the disposable infusion fluid delivery device microcontroller as the desired direction of the communication or information flow dictates. In step 84 the disposable electronically controlled medication pumping system of the disposable infusion fluid delivery device is wirelessly controlled and wirelessly powered with the non-disposable microcontroller to infuse the infusion fluid from the disposable infusion container of the disposable infusion fluid delivery device into the patient.


In one embodiment, in step 84 the non-disposable microcontroller wirelessly controls the disposable infusion fluid delivery device to infuse the infusion fluid into the patient utilizing the information of the barcode or the Radio Frequency Tag, utilizing the information saved in the first memory of the non-disposable microcontroller or the second memory of the disposable infusion fluid delivery device, utilizing information saved in another memory, or utilizing other information regarding the infusion fluid, its delivery, or the particular patient to which the infusion fluid is being infused.


In one embodiment, in step 84 any of the interface, the non-disposable microcontroller, and the disposable infusion fluid delivery device may analyze the information provided by the barcode and/or the Radio Frequency Identification Tag, to analyze information stored in the first memory or the second memory regarding the infusion fluid, its delivery, or the particular patient, to analyze information sensed by the temperature sensor, the pressure detection sensor, the flow detection sensor, or the air detection sensor, or to analyze other information provided from other sources regarding the infusion fluid, its delivery, or the particular patient in order to ensure that patient, infusion fluid conditions such as age, storage/transit/delivery temperature, and the like, and infusion delivery parameters are met.


For instance this may include ensuring that the temperature range requirements for the infusion fluid have been followed during storage, shipment and delivery, ensuring that the infusion fluid is being infused into the right patient, ensuring that the infusion fluid is infused using the correct parameters (i.e. time, flow-rate, pressure, air-prevention, temperature, amount delivered, etc.), ensuring that the disposable infusion fluid device is not reused after it has been used on the intended patient, or ensuring that other patient and/or infusion delivery parameters are followed. If the interface, the non-disposable microcontroller, or the disposable infusion fluid delivery device determine that the appropriate patient and/or infusion delivery parameters are not being followed they may be configured to adjust the infusion delivery to ensure compliance with these restraints, provide an alert or alarm signal, and/or to stop the infusion.


In step 86 a log of the disposable infusion fluid delivery device, regarding the infusion of the infusion fluid to the patient, is wirelessly communicated from the disposable infusion fluid delivery device to the non-disposable microcontroller. In step 88 the disposable infusion fluid delivery device is disposed of after the medication is infused into the patient so that the disposable infusion fluid delivery device is only used for a single patient and single delivery before its disposal.


In step 90 the method is repeated using new disposable infusion fluid delivery devices with the interface and the non-disposable microcontroller being used to wirelessly control and wirelessly power the new disposable infusion fluid delivery devices to infuse infusion fluid contained in the new disposable infusion fluid delivery devices to the same or different patients on a one-time basis, after which the new disposable infusion fluid delivery devices are disposed of. Since the interface and the non-disposable microcontroller never came into contact with the disposable infusion fluid delivery device, the infusion fluid itself, or the bodily fluids of patients, no sterilization of the interface or the non-disposable microcontroller is necessary.


In one embodiment, an additional step of the method 70 may comprise a multiplexer of the non-disposable microcontroller concurrently electronically and wirelessly controlling a plurality of disposable infusion fluid delivery devices, each comprising at least one disposable infusion container and a disposable electronically controlled medication pumping system, to deliver different infusion fluids to the patient or to provide a redundant system.


In another embodiment suggested in view of FIGS. 4-6, an additional step of the method 70 may comprise a multiplexer of the non-disposable microcontroller electronically and wirelessly controlling an integrated disposable infusion fluid delivery device having a plurality of electronically controlled medication pumping systems, each being fluidly connected to the same disposable infusion container, to deliver an infusion fluid to the patient in a series or parallel arrangement over time to provide an increased volume or increased volumetric flow rate than would be possible with a single micropump.


In one embodiment, the interface utilized in the method 70 comprises a smartphone, a laptop, a stand-alone computer, a nurse station, an infusion pump, or another type of device. In one embodiment, the non-disposable microcontroller utilized in the method 70 comprises a first microprocessor, a first memory in electronic communication with the first microprocessor, a battery, a power transmitter configured to wirelessly transmit power, and a first wireless communication device. In one embodiment, the disposable electronically controlled medication pumping system of the disposable infusion fluid delivery device utilized in the method 70 comprises a second microprocessor, a second memory in electronic communication with the second microprocessor, a power receiver configured to wirelessly receive power from the power transmitter, a second wireless communication device configured to wirelessly communicate with the first wireless communication device, an infusion channel, a disposable electronically controlled micropump, and valves connected to the infusion channel.


In other embodiments, the interface, the non-disposable microcontroller, and the disposable infusion fluid delivery device may vary. In still other embodiments, any of the steps of the method 70 may be eliminated or changed in substance or in order, or one or more additional steps may be added in varying orders.


The systems and methods of the disclosure provide many benefits over existing infusion systems. For instance, substantial cost is saved in the manufacture of the infusion systems of the disclosure due to the use of the inexpensive disposable electronically controlled micropump which requires a fraction of the power required to run current infusion systems. Moreover, since the disposable infusion fluid delivery devices of the disclosure are sealed, delivered in a sterilized state, and only used once for a single patient and then disposed of, cleaning cost are effectively eliminated and the risk to medical personnel from being exposed to the infusion fluid is similarly substantially eliminated. Additionally, the infusion systems of the disclosure are substantially smaller in weight and size than current infusion systems. These factors reduce shipping and storage cost, and make the infusion system easier to handle and interface with. Further, the infusion systems of the disclosure have significant noise reduction over current infusion systems due to the small disposable micropumps.


Moreover, the small size of the disposable infusion fluid delivery devices of the disclosure reduces the risk of over-exposure to the infusion fluid. Smaller and more concentrated amounts of the costly infusion fluids can be delivered. Additionally, the infusion systems of the disclosure utilize a multiplexed controller which allows multiple drug infusions simultaneously. Further, the disposable infusion fluid delivery devices of the disclosure can be shipped for medical control, i.e. insulin and glucose, in a single pumping mechanism. The infusion systems of the disclosure cover all therapies given via current technology and many others including: blood clotting (heparin and coagulant); blood pressure and heart rate control; oxygenation, SPO2 (saturation of peripheral oxygen); renal failure prevention (protect kidney); fluid volume balance; PCA (patient controlled analgesia)/cardiac arrest; and others. Additionally, the infusion systems of the disclosure provide for automatic data capture, recording, and near real-time feedback regarding the infusion delivery and the patient to ensure that the required parameters for the infusion are met in order to improve reliability and accuracy. Additionally, the infusion system allows configuration of highly redundant medication delivery system, which is impractical or very difficult to achieve using current pump technology.


The Abstract is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.


While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true scope of the subject matter described herein. Furthermore, it is to be understood that the disclosure is defined by the appended claims. Accordingly, the disclosure is not to be restricted except in light of the appended claims and their equivalents.

Claims
  • 1. A method for delivering infusion fluid to a patient, the method comprising: providing a disposable infusion fluid delivery device comprising a single disposable infusion container and a plurality of disposable electronically controlled medication pumping systems, wherein the single disposable infusion container is configured to contain the infusion fluid; andwirelessly controlling and wirelessly powering each of the plurality of disposable electronically controlled medication pumping systems of the disposable infusion fluid delivery device with a non-disposable microcontroller to infuse the infusion fluid from the single disposable infusion container of the disposable infusion fluid delivery device, through infusion channels arranged in parallel of the plurality of disposable electronically controlled medication pumping systems, through a connector joined downstream of the infusion channels arranged in parallel of the plurality of disposable electronically controlled medication pumping systems, into the patient,wherein the disposable infusion fluid delivery device is configured to be disposed of after the infusion fluid is infused into the patient so that the disposable infusion fluid delivery device is configured to be only used for a single patient before the infusion fluid delivery device is disposed.
  • 2. The method of claim 1, further comprising storing information regarding the infusion fluid, a delivery of the infusion fluid, or a particular patient to which the infusion fluid is to be infused to a barcode or a Radio Frequency Identification Tag attached to the disposable infusion fluid delivery device, and wirelessly communicating the information of the barcode or the Radio Frequency Identification Tag attached to the disposable infusion fluid delivery device to the non-disposable microcontroller.
  • 3. The method of claim 2, further comprising sensing conditions of the infusion fluid comprising a temperature of the infusion fluid, a pressure of the infusion fluid, a flow rate of the infusion fluid, or a quantity of air in the infusion fluid.
  • 4. The method of claim 3, further comprising: analyzing the information provided by the barcode or the Radio Frequency Identification Tag; andcomparing the information provided by the barcode or the Radio Frequency Identification Tag to the conditions of the infusion fluid.
  • 5. The method of claim 4, further comprising: determining the conditions of the infusion fluid do not comply with the information provided by the barcode or the Radio Frequency Identification Tag.
  • 6. The method of claim 5, further comprising providing an alert or an alarm signal subsequent to the determining the conditions of the infusion fluid do not comply with the information provided by the barcode or the Radio Frequency Identification Tag.
  • 7. The method of claim 6, further comprising stopping delivery of the infusion fluid subsequent to the determining that conditions of the infusion fluid do not comply with the information provided by the barcode or the Radio Frequency Identification Tag.
  • 8. The method of claim 1, further comprising wirelessly communicating a log of the disposable infusion fluid delivery device, regarding the infusion of the infusion fluid to the patient, from the disposable infusion fluid delivery device to the non-disposable microcontroller prior to the disposable infusion fluid delivery device being disposed.
  • 9. The method of claim 1, wherein the non-disposable microcontroller comprises: a first microprocessor, a first memory in electronic communication with the first microprocessor, a battery or an A/C power source, a power transmitter configured to wirelessly transmit power, and a first wireless communication device; and the plurality of disposable electronically controlled medication pumping systems of the disposable infusion fluid delivery device each comprises: a second microprocessor, a second memory in electronic communication with the second microprocessor, a power receiver configured to wirelessly receive the power from the power transmitter, a second wireless communication device configured to wirelessly communicate with the first wireless communication device, a disposable electronically controlled micropump, and valves connected to the infusion channel of each of the plurality of disposable electronically controlled medication pumping systems.
  • 10. The method of claim 9, further comprising pumping the infusion fluid through the infusion channels with the micropump of each of the plurality of disposable electronically controlled medication pumping systems.
  • 11. The method of claim 9, further comprising controlling a flow of the infusion fluid with the valves of each of the plurality of disposable electronically controlled medication pumping systems.
  • 12. The method of claim 1, wherein each of the plurality of disposable electronically controlled medication pumping systems is permanently hermetically sealed to the single disposable infusion container by at least one seal or gasket.
  • 13. The method of claim 1, further comprising operating the plurality of disposable electronically controlled medication pumping systems in parallel to pump the infusion fluid concurrently from the single disposable infusion container at a combined flow rate.
  • 14. The method of claim 13, wherein the combined flow rate is between 0.1 to 2,000 milliliters of the infusion fluid per hour.
  • 15. The method of claim 1, further comprising receiving an input on an interface to communicate with the non-disposable microcontroller.
  • 16. The method of claim 15, wherein the interface comprises a smartphone, a tablet, a laptop, a stand-alone computer, a nurse station, or an infusion pump.
  • 17. The method of claim 1, further comprising sensing a temperature of the infusion fluid, a pressure of the infusion fluid, a flow rate of the infusion fluid, or a quantity of air in the infusion fluid.
  • 18. The method of claim 1, further comprising repeating using the non-disposable microcontroller with a second disposable infusion fluid delivery device.
  • 19. The method of claim 1, further comprising concurrently electronically and wirelessly controlling a plurality of disposable infusion fluid delivery devices including the disposable infusion fluid delivery device with a multiplexer of the non-disposable microcontroller.
  • 20. The method of claim 1, further comprising delivering different infusion fluids including the infusion fluid to the patient with the plurality of disposable infusion fluid delivery devices.
INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/142,823, filed Jan. 6, 2021, which is a divisional of U.S. patent application Ser. No. 15/164,277, filed on May 25, 2016, which claims the benefit of U.S. Provisional Application Ser. No. 62/166,422, filed on May 26, 2015, each of which are hereby incorporated by reference in their entirety.

US Referenced Citations (672)
Number Name Date Kind
790353 Estlingen May 1905 A
1248058 Bailey Nov 1917 A
1576445 Mitchell Mar 1926 A
1647039 Fischer Apr 1927 A
1749491 Kokay Apr 1930 A
2820886 Posey May 1955 A
2869690 Winters et al. Jan 1959 A
2903165 Hanson et al. Sep 1959 A
3185153 Leucci May 1965 A
3316935 Kaiser et al. May 1967 A
3367270 Schlosser Feb 1968 A
3427986 Corneil Feb 1969 A
3606596 Edwards Sep 1971 A
3647176 Usry Mar 1972 A
3650296 Johnson et al. Mar 1972 A
3771862 Land et al. Nov 1973 A
3777581 Sartori Dec 1973 A
3812482 Clark May 1974 A
3898637 Wolstenholme Aug 1975 A
3901231 Olson Aug 1975 A
3913384 Furuya Oct 1975 A
3921622 Cole Nov 1975 A
3935876 Massie et al. Feb 1976 A
3985133 Jenkins et al. Oct 1976 A
4068521 Cosentino et al. Jan 1978 A
4155362 Jess May 1979 A
4187057 Xanthopoulos Feb 1980 A
4193635 Thiruvengadam et al. Mar 1980 A
4195515 Smoll Apr 1980 A
4211380 Lillegard et al. Jul 1980 A
4213454 Shim Jul 1980 A
4223813 Garrett et al. Sep 1980 A
4236880 Archibald Dec 1980 A
4240294 Grande Dec 1980 A
4244365 McGill Jan 1981 A
4261356 Turner et al. Apr 1981 A
4291701 Bowman et al. Sep 1981 A
4303376 Siekmann Dec 1981 A
4332378 Pryor Jun 1982 A
4343316 Jespersen Aug 1982 A
4381591 Barger et al. May 1983 A
4397642 Lamadrid Aug 1983 A
4397648 Knute et al. Aug 1983 A
4406042 McPhee et al. Sep 1983 A
4418565 St. John Dec 1983 A
4439179 Lueders et al. Mar 1984 A
4468222 Lundquist Aug 1984 A
4469765 McCartney et al. Sep 1984 A
4482347 Borsanyi Nov 1984 A
4496351 Hillel et al. Jan 1985 A
4513885 Hogan Apr 1985 A
4528847 Halmi Jul 1985 A
4530647 Uno Jul 1985 A
4551134 Slavik et al. Nov 1985 A
4565500 Jeensalute et al. Jan 1986 A
4573968 Parker Mar 1986 A
4585441 Archibald et al. Apr 1986 A
4586691 Kozlow May 1986 A
4589171 McGill et al. May 1986 A
4607520 Dam Aug 1986 A
4613325 Abrams Sep 1986 A
4626243 Singh et al. Dec 1986 A
4626244 Reinicke Dec 1986 A
4644960 Johans Feb 1987 A
4680977 Conero et al. Jul 1987 A
4681563 Deckert et al. Jul 1987 A
4683916 Raines Aug 1987 A
4689043 Bisha Aug 1987 A
4694273 Franchino Sep 1987 A
4696671 Epstein et al. Sep 1987 A
4722725 Sawyer Feb 1988 A
4728265 Cannon Mar 1988 A
4735558 Kienholz et al. Apr 1988 A
4756706 Kerns et al. Jul 1988 A
4758228 Williams Jul 1988 A
4759749 Verkaart Jul 1988 A
4802650 Stricker Feb 1989 A
4811928 Iwatschenko et al. Mar 1989 A
4813280 Miller et al. Mar 1989 A
4820281 Lawler Apr 1989 A
4828545 Epstein et al. May 1989 A
4832299 Gorton et al. May 1989 A
4840345 Neil et al. Jun 1989 A
4842584 Pastrone et al. Jun 1989 A
4844397 Skakoon et al. Jul 1989 A
4845487 Frantz et al. Jul 1989 A
4846636 Danby et al. Jul 1989 A
4856339 Williams Aug 1989 A
4857048 Simons et al. Aug 1989 A
4857050 Lentz et al. Aug 1989 A
4858548 Echeverria Aug 1989 A
4865584 Epstein et al. Sep 1989 A
4881413 Georgi et al. Nov 1989 A
D305060 Bisha′ et al. Dec 1989 S
4892656 Pietzsch Jan 1990 A
4898578 Rubalcaba, Jr. Feb 1990 A
4925444 Orkin et al. May 1990 A
4927411 Pastrone et al. May 1990 A
4935014 Haber Jun 1990 A
4938079 Goldberg Jul 1990 A
4947856 Beard Aug 1990 A
5014798 Glynn May 1991 A
5017192 Dodge et al. May 1991 A
5031465 Redus Jul 1991 A
5034004 Crankshaw Jul 1991 A
5062775 Orth Nov 1991 A
5085644 Watson et al. Feb 1992 A
5098262 Wecker et al. Mar 1992 A
5102083 Baskas Apr 1992 A
5102392 Sakai et al. Apr 1992 A
5113904 Aslanian May 1992 A
5138743 Hoffman Aug 1992 A
5125891 Hossain et al. Sep 1992 A
5152753 Laguette et al. Oct 1992 A
5154513 Beer et al. Oct 1992 A
5163900 Wortrich Nov 1992 A
5165406 Wong et al. Nov 1992 A
5165873 Meijer Nov 1992 A
5169106 Rasmussen Dec 1992 A
5177993 Beckman et al. Jan 1993 A
5187746 Narisawa Feb 1993 A
5192269 Poli et al. Mar 1993 A
5205153 Hlavinka et al. Apr 1993 A
5207642 Orkin et al. May 1993 A
5211626 Frank et al. May 1993 A
5217355 Hyman et al. Jun 1993 A
5219099 Spence et al. Jun 1993 A
5219327 Okada Jun 1993 A
5219428 Stern Jun 1993 A
5220920 Gharib Jun 1993 A
5225063 Gumbrecht et al. Jul 1993 A
5242406 Gross et al. Sep 1993 A
5256157 Samiotes et al. Oct 1993 A
5257978 Haber et al. Nov 1993 A
5270702 Krolak Dec 1993 A
5271815 Wong Dec 1993 A
5282787 Wortrich Feb 1994 A
5287851 Beran et al. Feb 1994 A
5292306 Wynkoop et al. Mar 1994 A
5302093 Owens et al. Apr 1994 A
5306122 Gebauer et al. Apr 1994 A
5309604 Poulsen et al. May 1994 A
5317506 Coutre et al. May 1994 A
D348101 Poli et al. Jun 1994 S
5322253 Stevens Jun 1994 A
5324266 Ambrisco et al. Jun 1994 A
5325728 Zimmerman et al. Jul 1994 A
5326059 Pryor et al. Jul 1994 A
5330634 Wong et al. Jul 1994 A
5332184 Davis Jul 1994 A
5345932 Yafuso et al. Sep 1994 A
5346466 Yerlikaya et al. Sep 1994 A
5358205 Starkey et al. Oct 1994 A
5364364 Kasvikis et al. Nov 1994 A
D353667 Tsubota et al. Dec 1994 S
5378126 Abrahamson et al. Jan 1995 A
5378231 Johnson et al. Jan 1995 A
5380665 Cusack et al. Jan 1995 A
5382232 Hague et al. Jan 1995 A
D355716 Nash et al. Feb 1995 S
5395320 Padda et al. Mar 1995 A
5401256 Stone et al. Mar 1995 A
5403277 Dodge et al. Apr 1995 A
5417119 Smoll May 1995 A
5417395 Fowler et al. May 1995 A
5421209 Redus Jun 1995 A
5421328 Bedingham Jun 1995 A
5431174 Knute Jul 1995 A
5431509 Anderson et al. Jul 1995 A
5431627 Pastrone et al. Jul 1995 A
5437635 Fields et al. Aug 1995 A
5445506 Afflerbaugh et al. Aug 1995 A
5445621 Poli et al. Aug 1995 A
5445622 Brown Aug 1995 A
5450758 Smoll Sep 1995 A
5453098 Botts et al. Sep 1995 A
5462052 Gehrich Oct 1995 A
5462256 Minick et al. Oct 1995 A
5463906 Spani et al. Nov 1995 A
5465938 Werge et al. Nov 1995 A
5482446 Williamson et al. Jan 1996 A
D367528 Martson et al. Feb 1996 S
5489265 Montalvo et al. Feb 1996 A
5489486 Glover Feb 1996 A
5505828 Wong et al. Apr 1996 A
5515713 Saugues et al. May 1996 A
5524475 Kolpak Jun 1996 A
5527289 Foster et al. Jun 1996 A
5538807 Hagiuda Jul 1996 A
5540561 Johnson et al. Jul 1996 A
5551300 Vurek et al. Sep 1996 A
5554013 Owens et al. Sep 1996 A
5554112 Walbrink et al. Sep 1996 A
D376199 Rozek et al. Dec 1996 S
5584671 Schweitzer, Jr. et al. Dec 1996 A
5586868 Lawless et al. Dec 1996 A
5601420 Warner et al. Feb 1997 A
5601445 Schipper et al. Feb 1997 A
5603613 Butterfield et al. Feb 1997 A
5609572 Lang Mar 1997 A
5611784 Barresi et al. Mar 1997 A
5616124 Hague et al. Apr 1997 A
5626151 Linden May 1997 A
5628309 Brown May 1997 A
5628731 Dodge et al. May 1997 A
5630710 Tune et al. May 1997 A
5647491 Foster et al. Jul 1997 A
5647852 Atkinson Jul 1997 A
5651775 Walker et al. Jul 1997 A
5657000 Ellingboe Aug 1997 A
5658133 Anderson et al. Aug 1997 A
5672832 Cucci et al. Sep 1997 A
5673588 Raymond Oct 1997 A
5681019 Boyce Oct 1997 A
5693891 Brown et al. Dec 1997 A
5697899 Hillman et al. Dec 1997 A
5697916 Schraga Dec 1997 A
5709663 Younkes Jan 1998 A
D390574 Ashcraft Feb 1998 S
D390654 Alsberg et al. Feb 1998 S
5713509 Correll Feb 1998 A
5713856 Eggers et al. Feb 1998 A
5718569 Holst Feb 1998 A
5723773 Bryan Mar 1998 A
5728069 Montevecchi et al. Mar 1998 A
5728074 Castellano et al. Mar 1998 A
5733061 Child Mar 1998 A
5736650 Hiron et al. Apr 1998 A
5738662 Shannon et al. Apr 1998 A
5740810 Johnson et al. Apr 1998 A
5745378 Barker et al. Apr 1998 A
D394440 Chen May 1998 S
5752918 Fowler et al. May 1998 A
5755563 Clegg et al. May 1998 A
5755683 Houle et al. May 1998 A
5758643 Wong et al. Jun 1998 A
5763760 Gumbrecht et al. Jun 1998 A
5772166 Adams Jun 1998 A
5772637 Heinzmann et al. Jun 1998 A
5782611 Neftel et al. Jul 1998 A
5782805 Meinzer et al. Jul 1998 A
5793216 Constant Aug 1998 A
5804048 Wong et al. Sep 1998 A
5805455 Lipps Sep 1998 A
5807345 Grabenkort Sep 1998 A
5812419 Chupp et al. Sep 1998 A
5814015 Gargano et al. Sep 1998 A
5816779 Lawless et al. Oct 1998 A
5848971 Fowler et al. Dec 1998 A
5853386 Davis et al. Dec 1998 A
5868696 Giesler et al. Feb 1999 A
5868710 Battiato et al. Feb 1999 A
5868712 Briggs et al. Feb 1999 A
5891051 Han et al. Apr 1999 A
5895371 Levitas et al. Apr 1999 A
5902253 Pfeiffer et al. May 1999 A
5904666 DeDecker et al. May 1999 A
5910808 Fukasawa et al. Jun 1999 A
5925022 Battiato et al. Jul 1999 A
5932175 Knute et al. Aug 1999 A
5935099 Peterson et al. Aug 1999 A
5938638 Passariello et al. Aug 1999 A
5939326 Chupp et al. Aug 1999 A
5941846 Duffy et al. Aug 1999 A
5944660 Kimball et al. Aug 1999 A
5947911 Wong et al. Sep 1999 A
5954485 Johnson et al. Sep 1999 A
5989222 Cole et al. Nov 1999 A
6004292 Battiato et al. Dec 1999 A
6007941 Hermann et al. Dec 1999 A
6017318 Gauthier et al. Jan 2000 A
6027445 Von Bahr Feb 2000 A
6027479 Alei et al. Feb 2000 A
6032536 Peeters et al. Mar 2000 A
D424692 Monaghan et al. May 2000 S
6056522 Johnson May 2000 A
6068615 Brown et al. May 2000 A
6080583 Von Bahr Jun 2000 A
6085574 Neftel et al. Jul 2000 A
6090071 Kriesel et al. Jul 2000 A
6099470 Bahr Aug 2000 A
6105442 Kriesel et al. Aug 2000 A
6106498 Friedli et al. Aug 2000 A
6109460 Herlevi et al. Aug 2000 A
6110153 Davis Aug 2000 A
6110410 Owens et al. Aug 2000 A
RE36871 Epstein et al. Sep 2000 E
6117290 Say et al. Sep 2000 A
6123827 Wong et al. Sep 2000 A
6165154 Gray et al. Dec 2000 A
6186752 Deniega et al. Feb 2001 B1
6186977 Andrews et al. Feb 2001 B1
6186983 Von Bahr Feb 2001 B1
6203528 Deckert Mar 2001 B1
6210361 Kamen et al. Apr 2001 B1
6221065 Davis Apr 2001 B1
6231320 Lawless et al. May 2001 B1
6237398 Porat et al. May 2001 B1
6250132 Drzewiecki Jun 2001 B1
6254572 Knipfer et al. Jul 2001 B1
6261262 Briggs Jul 2001 B1
6269704 Ziv et al. Aug 2001 B1
6270455 Brown Aug 2001 B1
6272934 Rajan et al. Aug 2001 B1
6277099 Strowe et al. Aug 2001 B1
6285155 Maske et al. Sep 2001 B1
6290681 Brown Sep 2001 B1
6325264 Omosako Dec 2001 B1
6349740 Cho et al. Feb 2002 B1
D454884 Christiansen et al. Mar 2002 S
6364857 Gray et al. Apr 2002 B1
6385505 Lipps May 2002 B1
6386050 Yin et al. May 2002 B1
6390120 Guala May 2002 B1
6396583 Clare May 2002 B1
6409707 Guala Jun 2002 B1
6422256 Balazy et al. Jul 2002 B1
6445053 Cho Sep 2002 B1
6463394 Von Bahr Oct 2002 B1
6464667 Kamen et al. Oct 2002 B1
6478065 Haberstroh et al. Nov 2002 B1
6482185 Hartmann Nov 2002 B1
6488652 Weijand et al. Dec 2002 B1
6489896 Platt Dec 2002 B1
6494694 Lawless et al. Dec 2002 B2
6503221 Briggs Jan 2003 B1
6515487 Dawson Feb 2003 B1
6519569 White et al. Feb 2003 B1
6537258 Guala Mar 2003 B1
6558125 Futterknecht May 2003 B1
6565054 Weesner et al. May 2003 B2
6568416 Tucker et al. May 2003 B2
D475454 Gillespie, Jr. et al. Jun 2003 S
D475721 Harper et al. Jun 2003 S
6578435 Gould et al. Jun 2003 B2
RE38189 Walker et al. Jul 2003 E
6595943 Burbank Jul 2003 B1
6599746 Gumbrecht Jul 2003 B1
6609047 Lipps Aug 2003 B1
D479248 Gist et al. Sep 2003 S
6623470 Munis et al. Sep 2003 B2
D481121 Evans Oct 2003 S
6635033 Hill et al. Oct 2003 B1
6645142 Braig et al. Nov 2003 B2
6656148 Das et al. Dec 2003 B2
D485356 Evans Jan 2004 S
6672561 Kerg et al. Jan 2004 B2
6685668 Cho et al. Feb 2004 B1
6685670 Miles et al. Feb 2004 B2
6685678 Evans et al. Feb 2004 B2
6695803 Robinson et al. Feb 2004 B1
6700174 Mui et al. Mar 2004 B1
6700784 Huang et al. Mar 2004 B2
6709417 Houle et al. Mar 2004 B1
6722211 Ciobanu et al. Apr 2004 B1
6726656 Kamen et al. Apr 2004 B2
6726657 Dedig et al. Apr 2004 B1
6736801 Gallagher May 2004 B1
6749403 Bryant et al. Jun 2004 B2
6755086 Salamitou Jun 2004 B2
6755391 Newton et al. Jun 2004 B2
6760643 Lipps Jul 2004 B2
6813964 Clark et al. Nov 2004 B1
D500326 Fathallah et al. Dec 2004 S
6827709 Fujii Dec 2004 B2
6872297 Mansouri et al. Mar 2005 B2
D504507 Ziegler et al. Apr 2005 S
6890315 Levin et al. May 2005 B1
6905314 Danby Jun 2005 B2
6915679 Chien et al. Jul 2005 B2
6920795 Bischoff et al. Jul 2005 B2
6929619 Fago et al. Aug 2005 B2
6932796 Sage et al. Aug 2005 B2
6935189 Richards Aug 2005 B2
6935192 Sobek et al. Aug 2005 B2
6939111 Huitt et al. Sep 2005 B2
6942473 Abrahamson et al. Sep 2005 B2
6942636 Holst et al. Sep 2005 B2
6964204 Clark et al. Nov 2005 B2
6969419 Macemon Nov 2005 B1
6975922 Duncan et al. Dec 2005 B2
6981960 Cho et al. Jan 2006 B2
D515205 Fathalla et al. Feb 2006 S
7004727 Kline et al. Feb 2006 B2
7008393 Robinson et al. Mar 2006 B2
RE39075 Verkaart Apr 2006 E
7029105 Matsuba et al. Apr 2006 B2
7037428 Robinson et al. May 2006 B1
7041076 Westberg et al. May 2006 B1
7044002 Ericson et al. May 2006 B2
7059184 Kanouda et al. Jun 2006 B2
7061766 Wainwright et al. Jun 2006 B2
7070578 Leukanech et al. Jul 2006 B2
7074209 Evans et al. Jul 2006 B2
7077650 Johnstone Jul 2006 B2
7082843 Clark et al. Aug 2006 B2
7087036 Busby et al. Aug 2006 B2
7096729 Repko et al. Aug 2006 B2
7115113 Evans et al. Oct 2006 B2
7140070 Yuta et al. Nov 2006 B2
7152469 Milleker et al. Dec 2006 B2
7160087 Fathallah et al. Jan 2007 B2
7161488 Frasch Jan 2007 B2
7162290 Levin Jan 2007 B1
7162927 Selvan et al. Jan 2007 B1
7169128 Kriesel et al. Jan 2007 B2
7190275 Goldberg et al. Mar 2007 B2
7258534 Fathallah et al. Aug 2007 B2
7327273 Hung et al. Feb 2008 B2
7364562 Braig et al. Apr 2008 B2
7367942 Grage et al. May 2008 B2
7377148 Cassidy et al. May 2008 B2
7415895 Kurisaki et al. Aug 2008 B2
7462161 O'Mahony et al. Dec 2008 B2
7503903 Carlisle et al. Mar 2009 B2
7556616 Fathallah et al. Jul 2009 B2
7571024 Duncan et al. Aug 2009 B2
7608042 Golberger et al. Oct 2009 B2
7615007 Shults et al. Nov 2009 B2
7621892 Fago et al. Nov 2009 B2
7693697 Westenskow et al. Apr 2010 B2
7707897 Ong May 2010 B2
7722537 Sterling et al. May 2010 B2
7766630 Fathallah et al. Aug 2010 B2
7771389 Grispo et al. Aug 2010 B2
7775126 Eckhardt Aug 2010 B2
7775127 Wade Aug 2010 B2
7784330 Angelescu et al. Aug 2010 B2
7810401 Brown et al. Oct 2010 B2
7819838 Ziegler et al. Oct 2010 B2
7846131 Hudson et al. Dec 2010 B2
7850659 Trombley, III et al. Dec 2010 B1
7866201 Tutu et al. Jan 2011 B1
7884735 Newkirk Feb 2011 B2
7895053 Holland et al. Feb 2011 B2
7896572 Fathallah et al. Mar 2011 B2
7905710 Wang et al. Mar 2011 B2
7933780 de la Huerga Apr 2011 B2
7935077 Thor et al. May 2011 B2
7972296 Braig et al. Jul 2011 B2
7975491 Smisson, III et al. Jul 2011 B2
7976508 Hoag Jul 2011 B2
D644250 Barber et al. Aug 2011 S
7998115 Bedingfield et al. Aug 2011 B2
8033157 Yardimci et al. Oct 2011 B2
8048022 Moy et al. Nov 2011 B2
8052644 Radgowski et al. Nov 2011 B2
8057437 Ziegler et al. Nov 2011 B2
8061219 Rezgui et al. Nov 2011 B2
8065161 Howard et al. Nov 2011 B2
8065924 Ziegler et al. Nov 2011 B2
8105269 Zhou et al. Jan 2012 B2
8147448 Sundar et al. Apr 2012 B2
8149131 Blomquist Apr 2012 B2
8152486 Fathallah et al. Apr 2012 B2
8219413 Martinez et al. Jul 2012 B2
8256984 Fathallah et al. Sep 2012 B2
8258973 Newkirk Sep 2012 B2
D669096 Katsura Oct 2012 S
8286977 Butler et al. Oct 2012 B2
8313308 Lawless et al. Nov 2012 B2
8315885 Krogh et al. Nov 2012 B2
8317698 Lowery Nov 2012 B2
8380536 Howard et al. Feb 2013 B2
D677784 Marguerie Mar 2013 S
8403908 Jacobson et al. Mar 2013 B2
D679800 Gusky et al. Apr 2013 S
8417311 Rule Apr 2013 B2
D682318 Goh May 2013 S
8449500 DelCastillo et al. May 2013 B2
8449524 Braig et al. May 2013 B2
8491523 Thor et al. Jul 2013 B2
8506552 Rebours Aug 2013 B2
8518021 Stewart et al. Aug 2013 B2
8523797 Lowery et al. Sep 2013 B2
8523813 Grispo et al. Sep 2013 B2
8581454 Corrington et al. Nov 2013 B2
8591491 Moy et al. Nov 2013 B2
8657778 Ziegler et al. Feb 2014 B2
D700626 Zhangyan et al. Mar 2014 S
8666769 Butler et al. Mar 2014 B2
D703311 Daly Apr 2014 S
8731960 Butler et al. May 2014 B2
8768719 Wehba et al. Jul 2014 B2
8777590 Moy et al. Jul 2014 B2
8801656 Lowery et al. Aug 2014 B2
8926562 Fathallah et al. Jan 2015 B2
D728779 Sabin et al. May 2015 S
D734475 Ross Jul 2015 S
9072831 Kelly et al. Jul 2015 B2
D736370 Sabin et al. Aug 2015 S
9174145 Weissenbach et al. Nov 2015 B2
D752736 Chandrasenan et al. Mar 2016 S
D759230 Gordon et al. Jun 2016 S
D759804 Singh et al. Jun 2016 S
D765832 Hochman et al. Sep 2016 S
D767756 Sabin Sep 2016 S
9468713 Hoenninger, III Oct 2016 B2
D776802 Loew et al. Jan 2017 S
9545475 Borges et al. Jan 2017 B2
9545476 Qi et al. Jan 2017 B2
D797275 Evans et al. Sep 2017 S
9799274 Alberti et al. Oct 2017 B2
D804017 Sabin Nov 2017 S
D805183 Sabin et al. Dec 2017 S
9849233 Edwards et al. Dec 2017 B1
D814021 Sabin Mar 2018 S
D815726 Bjelovuk et al. Apr 2018 S
D817479 Sabin et al. May 2018 S
D817480 Sabin et al. May 2018 S
D823456 Lacy et al. Jul 2018 S
10034975 McLennan et al. Jul 2018 B2
10039878 Gamelin Aug 2018 B2
D830546 Lacy et al. Oct 2018 S
D831820 Petersen Oct 2018 S
D831821 Petersen Oct 2018 S
10143795 Chen Dec 2018 B2
D840021 Lacy et al. Feb 2019 S
10260161 Rauenbusch et al. Apr 2019 B2
D859634 Hochman et al. Sep 2019 S
D859638 Swanbury et al. Sep 2019 S
D871568 Pratt et al. Dec 2019 S
D871572 Lacy et al. Dec 2019 S
D883472 Hogerwerf et al. May 2020 S
D890914 Ghodsi et al. Jul 2020 S
D891607 Bjelovuk et al. Jul 2020 S
D893704 Pratt et al. Aug 2020 S
D899584 Carrubba et al. Oct 2020 S
D899598 Lucio Oct 2020 S
D903093 Seddon et al. Nov 2020 S
D903094 Ghodsi et al. Nov 2020 S
D909567 Archat et al. Feb 2021 S
10918787 Shubinsky et al. Feb 2021 B2
D916275 Kolenda et al. Apr 2021 S
D921190 Shor et al. Jun 2021 S
D939079 Harris et al. Dec 2021 S
11213619 McLennan et al. Jan 2022 B2
D963158 Gibson et al. Sep 2022 S
D965139 Gibson et al. Sep 2022 S
D972125 Collins Dec 2022 S
D982739 Tamir Apr 2023 S
D982740 Mulcahy Apr 2023 S
11660386 Shubinsky et al. May 2023 B2
20010007932 Kamen et al. Jul 2001 A1
20010009610 Augustine et al. Jul 2001 A1
20010044602 Angersbach et al. Nov 2001 A1
20020004015 Carlisle et al. Jan 2002 A1
20020013551 Zaitsu et al. Jan 2002 A1
20020096608 Cedarberg Jul 2002 A1
20020099334 Hanson et al. Jul 2002 A1
20020120229 Miles et al. Aug 2002 A1
20020123741 Rake et al. Sep 2002 A1
20030065537 Evans Apr 2003 A1
20030127850 Bischoff et al. Jul 2003 A1
20030138349 Robinson et al. Jul 2003 A1
20030139701 White et al. Jul 2003 A1
20030144574 Heilman et al. Jul 2003 A1
20030175820 Smith et al. Sep 2003 A1
20040025597 Ericson Feb 2004 A1
20040074795 Fischer Apr 2004 A1
20040082918 Evans et al. Apr 2004 A1
20040176724 Kamen et al. Sep 2004 A1
20040225409 Duncan et al. Nov 2004 A1
20040232219 Fowler Nov 2004 A1
20040249308 Forssell Dec 2004 A1
20040251406 Figueria Dec 2004 A1
20050006538 Turi et al. Jan 2005 A1
20050055242 Bello et al. Mar 2005 A1
20050059926 Sage et al. Mar 2005 A1
20050074340 Xu et al. Apr 2005 A1
20050095152 Dale May 2005 A1
20050165384 Gravesen et al. Jul 2005 A1
20050168941 Sokol et al. Aug 2005 A1
20050171512 Flaherty Aug 2005 A1
20050177110 Azzolini Aug 2005 A1
20050209547 Burbank et al. Sep 2005 A1
20050209563 Hopping et al. Sep 2005 A1
20050260090 Stark et al. Nov 2005 A1
20050268712 Repko et al. Dec 2005 A1
20050274194 Skinner et al. Dec 2005 A1
20050277911 Stewart et al. Dec 2005 A1
20060030821 Lee et al. Feb 2006 A1
20060042633 Bishop et al. Mar 2006 A1
20060070669 Mabry et al. Apr 2006 A1
20060079831 Gilbert Apr 2006 A1
20060136095 Rob et al. Jun 2006 A1
20060142692 Jacobson et al. Jun 2006 A1
20060173253 Ganapathy et al. Aug 2006 A1
20060181695 Sage, Jr. Aug 2006 A1
20060187069 Duan Aug 2006 A1
20060189858 Sterling et al. Aug 2006 A1
20060189925 Gable et al. Aug 2006 A1
20060189926 Hall et al. Aug 2006 A1
20060194325 Gable et al. Aug 2006 A1
20060195045 Gable et al. Aug 2006 A1
20060195058 Gable et al. Aug 2006 A1
20060200070 Callicoat et al. Sep 2006 A1
20060200071 Sterling et al. Sep 2006 A1
20060200094 Holz Sep 2006 A1
20060229531 Goldberger et al. Oct 2006 A1
20060235348 Callicoat et al. Oct 2006 A1
20060241550 Kamen et al. Oct 2006 A1
20060260416 Sage et al. Nov 2006 A1
20060266128 Clark et al. Nov 2006 A1
20070038188 Bialecki et al. Feb 2007 A1
20070060869 Tolle et al. Mar 2007 A1
20070060872 Hall et al. Mar 2007 A1
20070112297 Plahey et al. May 2007 A1
20070129618 Goldberger et al. Jun 2007 A1
20070151366 McDonald et al. Jul 2007 A1
20070179436 Braig et al. Aug 2007 A1
20070225675 Robinson et al. Sep 2007 A1
20070239096 Keenan et al. Oct 2007 A1
20070250339 Mallett et al. Oct 2007 A1
20080039824 Fathallah et al. Feb 2008 A1
20080051732 Chen Feb 2008 A1
20080065420 Tirinato et al. Mar 2008 A1
20080086042 Brister et al. Apr 2008 A1
20080086044 Brister et al. Apr 2008 A1
20080097288 Levin et al. Apr 2008 A1
20080108942 Brister et al. May 2008 A1
20080116157 Fulbrook et al. May 2008 A1
20080145249 Smisson Jun 2008 A1
20080208103 Demers et al. Aug 2008 A1
20090004767 Parks et al. Jan 2009 A1
20090018483 Walker et al. Jan 2009 A1
20090046402 Malkus et al. Feb 2009 A1
20090069743 Krishnamoorthy et al. Mar 2009 A1
20090105646 Hendrixson et al. Apr 2009 A1
20090143711 Braig et al. Jun 2009 A1
20090240123 Siebrecht et al. Sep 2009 A1
20100137778 Kunjan et al. Jun 2010 A1
20100152681 Mathias Jun 2010 A1
20100271218 Hoag et al. Oct 2010 A1
20100280486 Khair et al. Nov 2010 A1
20110005606 Bartels et al. Jan 2011 A1
20110015610 Plahey et al. Jan 2011 A1
20110060199 Robinson et al. Mar 2011 A1
20110060758 Schlotterbeck et al. Mar 2011 A1
20110106462 Kilburn et al. May 2011 A1
20110213395 Corrington et al. Sep 2011 A1
20110264043 Kotnick et al. Oct 2011 A1
20110264044 Bartz et al. Oct 2011 A1
20110313318 Rule et al. Dec 2011 A1
20110313358 Hariharesan et al. Dec 2011 A1
20120035418 Talbert et al. Feb 2012 A1
20120065482 Robinson et al. Mar 2012 A1
20120078218 Barnes Mar 2012 A1
20120130341 Whitley May 2012 A1
20120145616 Weissenbach et al. Jun 2012 A1
20120245554 Kawamura Sep 2012 A1
20120271226 Farrell et al. Oct 2012 A1
20130079710 Krogh et al. Mar 2013 A1
20130165900 Braig et al. Jun 2013 A1
20130177455 Kamen et al. Jul 2013 A1
20130253946 Broselow Sep 2013 A1
20130274669 Stempfle et al. Oct 2013 A1
20130281965 Kamen et al. Oct 2013 A1
20130297330 Kamen et al. Nov 2013 A1
20150005935 Bae et al. Jan 2015 A1
20150133861 McLennan et al. May 2015 A1
20150167651 Balteanu et al. Jun 2015 A1
20160051750 Tsoukalis Feb 2016 A1
20170132867 Berg et al. May 2017 A1
20180300994 Nelson et al. Oct 2018 A1
20190059859 Pinch Feb 2019 A1
20190060539 Siess et al. Feb 2019 A1
20190298579 Moore et al. Oct 2019 A1
20190351131 Butterfield et al. Nov 2019 A1
20210304864 Kamen et al. Sep 2021 A1
20220362457 McLennan et al. Nov 2022 A1
20230310735 Cousineau Oct 2023 A1
Foreign Referenced Citations (74)
Number Date Country
2 808 379 Feb 2012 CA
304975990 Jan 2019 CN
306797374 Aug 2021 CN
37 42 268 Jun 1989 DE
0 197 705 Oct 1986 EP
0 306 130 Mar 1989 EP
0 396 003 Nov 1990 EP
0 423 978 Apr 1991 EP
0 429 866 Jun 1991 EP
0 447 985 Sep 1991 EP
0 450 736 Oct 1991 EP
0 483 794 May 1992 EP
0 510 881 Oct 1992 EP
0 569 030 Nov 1993 EP
0 477 551 Jan 1995 EP
0 481 656 Aug 1995 EP
0 697 898 Feb 1996 EP
0 839 062 May 1998 EP
0 891 784 Jan 1999 EP
0 960 627 Dec 1999 EP
1 177 802 Feb 2002 EP
2 742 961 Jun 2014 EP
01-265973 Oct 1989 JP
02-093917 Jul 1990 JP
09-327512 Dec 1997 JP
10-239193 Sep 1998 JP
2002-119587 Apr 2002 JP
3102285 Mar 2004 JP
2007-071695 Mar 2007 JP
2008-539964 Nov 2008 JP
4322661 Jun 2009 JP
2009-148592 Jul 2009 JP
2012-010718 Jan 2012 JP
D1467576 Apr 2013 JP
2014-104011 Jun 2014 JP
5716879 Mar 2015 JP
D1711790 Apr 2022 JP
D192262 Aug 2018 TW
D209965 Feb 2021 TW
WO 91016087 Oct 1991 WO
WO 92017226 Oct 1992 WO
WO 93005829 Apr 1993 WO
WO 93012828 Jul 1993 WO
WO 94009847 May 1994 WO
WO 95024229 Sep 1995 WO
WO 95031233 Nov 1995 WO
WO 96035472 Nov 1996 WO
WO 98013080 Apr 1998 WO
WO 99010028 Mar 1999 WO
WO 99010830 Mar 1999 WO
WO 00057941 Oct 2000 WO
WO 00066203 Nov 2000 WO
WO 01039816 Jun 2001 WO
WO 02027276 Apr 2002 WO
WO 02036044 May 2002 WO
WO 02087664 Nov 2002 WO
WO 02103209 Dec 2002 WO
WO 2004069095 Aug 2004 WO
WO 2004070994 Aug 2004 WO
WO 2005000378 Jan 2005 WO
WO 2005082450 Sep 2005 WO
WO 2005118015 Dec 2005 WO
WO 2007008692 Jan 2007 WO
WO 2007124070 Nov 2007 WO
WO 2008144575 Nov 2008 WO
WO 2009021705 Feb 2009 WO
WO 2009039203 Mar 2009 WO
WO 2009039214 Mar 2009 WO
WO 2010048644 Apr 2010 WO
WO 2011159956 Dec 2011 WO
WO 2014131729 Sep 2014 WO
WO 2017144366 Aug 2017 WO
WO 2020214717 Oct 2020 WO
WO 2023192791 Oct 2023 WO
Non-Patent Literature Citations (11)
Entry
“CritiCore® Monitor: Critical Fluid Output and Core Bladder Temperature Monitor”, BARD Urological Catheter Systems, Advertisement, 2005, pp. 2.
“Differential Pressure Transmitter, Series PD-39 X”, SensorsOne Ltd., Advertisement, Dec. 2005, pp. 2.
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.
International Search Report and Written Opinion received in PCT Application No. PCT/IB2016/052830, dated Aug. 9, 2016 in 9 pages.
International Preliminary Report on Patentability and Written Opinion received in PCT Application No. PCT/IB2016/052830, dated Dec. 7, 2017 in 8 pages.
Kutschka et al., “A New Minimized Perfusion Circuit Provides Highly Effective Ultrasound Controlled Deairing”, Artificial Organs, 2007, vol. 31, No. 3, pp. 215-220.
Merry et al., “A New, Safety-Oriented, Integrated Drug Administration and Automated Anesthesia Record System”, Anesthesia & Analgesia, Aug. 2001, vol. 93, No. 2 pp. 385-390.
Palanchon et al., “Acoustical Bubble Trapper Applied to Hemodialysis”, Ultrasound in Medicine & Biology, Apr. 2008, vol. 34, No. 4, pp. 681-684.
Parlex, “Medical Device Product Examples”, Johnson Medtech, Published at least as early as May 2008, pp. 2.
Stegmayr et al., “Development of Air Micro Bubbles in the Venous Outlet Line: An In Vitro Analysis of Various Air Traps Used for Hemodialysis”, Artificial Organs, 2007, vol. 31, No. 6, pp. 483-488.
“ICU Medical Receives FDA Clearance for Plum Duo™ Infusion Pump and LifeShield™ Infusion Safety Software”, PR Newswire, https://www.prnewswire.com/news-releases/icu-medical-receives-fda-clearance-for-plum-duo-infusion-pump-and-lifeshield-infusion-safety-software-301911857.html, Aug. 29, 2023, pp. 2.
Related Publications (1)
Number Date Country
20230321340 A1 Oct 2023 US
Provisional Applications (1)
Number Date Country
62166422 May 2015 US
Divisions (1)
Number Date Country
Parent 15164277 May 2016 US
Child 17142823 US
Continuations (1)
Number Date Country
Parent 17142823 Jan 2021 US
Child 18298624 US