Fluid transfer port information system

Information

  • Patent Grant
  • 9125979
  • Patent Number
    9,125,979
  • Date Filed
    Friday, October 24, 2008
    16 years ago
  • Date Issued
    Tuesday, September 8, 2015
    9 years ago
Abstract
Methods are provided for associating a specific one of two or more distinct fluid transfer ports of a patient with a given fluid transfer event of fluid from a parenteral fluid delivery device. Aspects of the methods include establishing a fluid transfer connection between the parenteral fluid delivery device and the patient via one of the two or more distinct fluid transfer ports and transmitting a fluid transfer signal between the parenteral fluid delivery device and a patient associated identifier using the patient's body as a signal conduction medium. Association may result in identification of the fluid transfer port that will be, is being or has been employed for the given fluid transfer event. Also provided are systems for practicing methods of the invention.
Description
INTRODUCTION

The parenteral administration (i.e., administration in a manner other than through the digestive tract, such as by intravenous or intramuscular injection or inhalation) of beneficial agents and fluids is an established clinical practice. Parenteral administration of beneficial agents are effective remedies for many patients when administered properly, e.g., according to instructions. However, studies have shown that, on average, about 10% of patients receive an incorrect injectable medication. For example, a significant percentage of serious errors are associated with the administration of intravenous (IV) medication.


In the clinical setting, misconnections of tubing used to link patients to medical devices have the potential to result in serious injury or death. Medical devices used in hospitals must have the ability to connect to related tubing and accessories. Connection is generally achieved through the standard “luer” connector. However, because the luer connector is a standard size and is used on such a broad range of medical devices and products with totally different functions, the risk for tubing misconnections is great.


A patient, for example, may be connected to several devices used to administer fluids through a vein; deliver feedings via a tube to the stomach; monitor blood pressure; and administer oxygen via mask or cannula. This collection of devices, all of which may include luer connectors, poses a risk of tubing misconnection especially in a busy clinical environment where stress, fatigue and distractions are common.


Misconnections, which have been made between numerous types of medical devices in diverse clinical settings, include but are not limited to the following: enteral feeding tubes mistakenly connected to IV lines; IV tubing connected to the tracheal-cuff pilot balloon port; noninvasive blood pressure (BP) cuffs connected to IV lines; and drugs intended for IV administration given intrathecally.


SUMMARY

Aspects of the invention include systems and methods for associating a specific one of multiple distinct fluid transfer ports in a patient with a given fluid transfer even of a fluid from a parenteral fluid delivery device to that patient. Aspects of the methods include establishing a fluid connection between the parenteral fluid delivery device and the patient via one of the two or more distinct fluid transfer ports. Next, a fluid transfer signal is transmitted between the parenteral fluid delivery device and a patient associated identifier using the patient's body as a signal conduction medium, e.g., from the fluid delivery device to the patient associated identifier or from the patient associated identifier to the fluid delivery device. A parameter of the fluid transfer signal, such as the strength of the fluid transfer signal, is then employed to a specific one of the two or more distinct fluid transfer ports of the patient with the given fluid transfer even. The association may include identification of the specific fluid transfer port that has been, is being or will be employed for the fluid delivery of fluid from the parenteral fluid delivery device to the patient. Where desired, the methods may include production of an error signal upon identification of an error concerning a specific fluid transfer port and a given fluid transfer event.





BRIEF DESCRIPTION OF THE FIGURES


FIG. 1 illustrates an IV bag delivery system according to a first embodiment of the invention.



FIG. 2 illustrates an IV bag delivery system according to a second embodiment of the invention.





DETAILED DESCRIPTION

Methods are provided for associating a specific one of two or more distinct fluid transfer ports of a patient with a given fluid transfer event of fluid from a parenteral fluid delivery device. Aspects of the methods include establishing a fluid transfer connection between the parenteral fluid delivery device and the patient via one of the two or more distinct fluid transfer ports and transmitting a fluid transfer signal between the parenteral fluid delivery device and a patient associated identifier using the patient's body as a signal conduction medium. Association may result in identification of the fluid transfer port that will be, is being or has been employed for the given fluid transfer event. Also provided are systems for practicing methods of the invention.


Systems of the invention may include a parenteral fluid delivery device and one or more patient associated identifiers. The parenteral fluid delivery device and the one or more patient associated identifiers are configured so that a fluid transfer signal can be transmitted between the two components using the body of the patient as a communication medium. To employ the body as a conduction medium for the fluid transfer signal, a fluid communication between the fluid delivery device and the patient is first established. As the body of the patient is used as a communication medium, the signal that is transferred between the parenteral fluid delivery device and the patient travels through the body, (e.g., in a direction from the patient associated identifier to the delivery device and/or from the delivery device to the patient associated identifier), and requires the body as the conduction medium. The fluid transfer signal may be conductively transmitted between the fluid delivery device and the patient associated identifier(s) using the patient as a conductive medium.


As the body is required as a conduction medium and requires the establishment of fluid transfer connection between the fluid delivery device and the patient, receipt of the signal (either at the patient associated identifier, the parenteral fluid delivery device or another component of the system, e.g., as reviewed in greater detail below) provides accurate knowledge about a fluid transfer event and a particular fluid transfer port associated with the fluid transfer event, e.g., that will be, is being or has been employed for the fluid transfer event. This accurate knowledge can then be further employed in a variety of different ways, depending on the application, where such applications include prospective, real-time and historic applications. Examples of prospective applications are those applications in which the fluid transfer signal is employed to determine beforehand which of two or more fluid transfer ports associated with a patient is going to be employed for a contemplated (i.e., future) fluid delivery event between the fluid delivery device and the patient. Such applications may further include a determination of whether the particular fluid transfer port is the correct fluid transfer port for the contemplated fluid delivery event. Examples of historic or retrospective applications of the methods and systems of the invention include applications where the fluid transfer signal is employed to obtain an accurate history of a fluid(s) that have been delivered to a patient via a parenteral fluid deliver device, and specifically which of two or more fluid transfer ports have been employed for delivery of the fluid.


As reviewed above, the components of the systems of the invention include a fluid delivery device, one or more patient associated identifiers and two or more fluid transfer ports. The various components are configured such that, during use, a fluid transfer signal is transmitted between them and a parameter of the signal, such as a measure of signal strength, is then employed to identify a particular fluid transfer port via which a fluid delivery event is contemplated or will occur.


In further describing embodiments of the invention, aspects of the systems are further reviewed in greater detail, followed by more detailed discussion of how the systems are employed in methods of fluid transfer port identification.


Systems


Systems of the invention may include a fluid delivery device, one or more patient associated identifiers, and two or more fluid transfer ports, where the systems may further include additional components, e.g., additional communication components, etc.


Parenteral Fluid Delivery Device


The parenteral fluid delivery device of systems of the invention is a device that delivers a quantity of a fluid (e.g., liquid) to a patient by a route other than the digestive tract, e.g., via intravenous delivery, etc. Of particular interest are fluid delivery devices that are configured to interact with a patient associated fluid transfer port via connection element, e.g., by a luer lock fitting. In certain embodiments, the delivery device includes a fluid transfer signal generator, e.g., in the form of an integrated circuit device or other suitable structure, that generates and transmits a signal to a receiver, e.g., which may be part of a patient associated identifier, upon transfer of fluid to the patient. In certain situations, the parenteral fluid delivery device is one that provides for one way transfer of fluid from the device to the patient. For parenteral delivery of a liquid, the delivery device may vary. One type of device of interest is an intravenous administration device, which may include a liquid storage element, e.g., a fluid containment or IV bag, a fluid metering unit or pump, a drip bag, etc. The liquid delivered to the patient may vary greatly in composition, and may include one or more distinct beneficial agents in a liquid pharmaceutically acceptable vehicle, e.g., one or more pharmaceutical agents, or may be a beneficial agent in its own right, e.g., such as where the liquid is a plasma volume expander. Also of interest are delivery devices that provide for transfer of fluid both to and from the patient. Such devices include those where the fluid, e.g., blood, dialysate, etc., is transferred from a patient to an external device and then transferred back from the device to the patient, typically after some type of processing in the device. An example of a parenteral fluid delivery device that finds use in these situations is a dialysis machine, where such devices may be parenteral dialysis devices or hemodialysis devices, etc.


A given fluid delivery device may include a single component or two or more disparate components, e.g., syringes and vials, fluid containment bags and IV pumps, etc.) which are operatively connected to one another during use and collectively have the ability to transfer a fluid transfer signal between the device and a patient associated identifier, as reviewed above. As such, the various components of the systems may further include communication elements, e.g., broadcasters and/or receivers, as may be required or desired for a given embodiment of the system. Such components may further include power sources, as may be desired, where any convenient power source may be present, including those mentioned in connection with the patient associated identifier, below.


Embodiments of the fluid delivery devices may include what are viewed as pharma-informatics enabled components, such as pharma-informatics enabled fluid containers. By pharma-informatics enabled fluid container is meant a fluid container which includes an identifier that provides identifying information about the fluid in the container. The container may vary, where the container may be a, bag, vial, etc., which includes a volume of fluid that is to be transferred to a patient. The nature of the identifying information may vary greatly from the simple, e.g., the name of the fluid, the name of the pharmaceutical agent present therein, to the more complex, e.g., the dosage present in the container, the history of the fluid in the container, the quality of the fluid in the container (e.g., whether it is compromised or spoiled), etc. The nature of the identifier may also vary, e.g., from being a passive interrogatable element, such as a barcode or other machine readable identifier, to a more active component, such as a component that can broadcast information and may include a power source. Sensors, as described below, may also be associated with the medical containers.


Where a given system includes two or more different fluid containers, the system may be configured as a multiplex system. Multiplex systems of interest are configured to sufficiently reduce or eliminate cross-talk and confusion between various broadcast signals of multiple components of the multiplex system such that a given fluid transfer signal about a given fluid and a patient may be properly matched up or associated with each other. For example, a signal generated about a first IV bag may be distinguishable from a signal generated about a second bag, where distinguishable signals may be provided in a number of different ways, e.g., by using an appropriate time based communication protocol, by having signals of different frequencies, etc. Of interest are the signal protocols described in PCT/US2006/016370 filed on Apr. 28, 2006, the disclosure of which is herein incorporated by reference. In certain embodiments where multiple different fluid containers are present in a given fluid delivery system, the different fluids may be color coded to provide an additional distinguishing feature, where this color coding may be detected and transmitted to the patient associated identifier (e.g., as part of a fluid transfer signal) for further confirmation that the right medicine, e.g., composition, dosage, quality, etc., is being delivered to the right patient.


Parenteral fluid delivery devices of interest, including examples of circuitry that may be used therein for the broadcaster and/or receiver elements thereof, are further described in PCT application serial no. PCT/US2007/015547 titled “Smart Parenteral Administration System” and filed on Jul. 6, 2007; the disclosure of which is herein incorporated by reference.


Patient Associated Identifier


As summarized above, a component of the systems of the invention is one or more patient associated identifiers. The patient associate identifier is a device that is configured to be associated with the patient, e.g., either topically or by implantation, and includes a communications element that performs at least one of broadcasting and receiving functions. The patient associated identifier is one that at least provides for broadcast and/or receipt of a fluid transfer signal, where the signal may comprise a variety of different types of information, such as identifying information about the patient. The identifier can be configured in a variety of different ways, including formats that are configured to simply broadcast a signal to more complex formats where the identifier receives information about a fluid transfer event (e.g., where the patient associated identifier includes a receiver element) and internally processes that information to evaluate the fluid transfer event in some manner. For example, the identifier may have a memory containing pre-existing knowledge of which medications are to be delivered to the patient. The identifier may compare the identifying information in the signal to the information in the memory to confirm that the medication associated with the fluid transfer event is correct. If it is not correct, the patient associate identifier may generate an error signal, e.g., as described in greater detail below. The identifiers may be configured to simply broadcast a signal, which may include identifying information about the patient, to the fluid delivery device. Alternatively, the identifiers may be configured to receive a signal from the fluid delivery device. In these cases, the identifiers are signal receivers that are configured to receive a signal from a parenteral fluid delivery device enabled to transmit a fluid transfer signal.


Where desired, the patient associated identifier may be one that is sized to be stably associated with a living subject in a manner that does not substantially impact movement of said living subject. In these instances, the patient associated identifier has dimensions that, when employed with a subject, such as a human subject, will not cause the subject to experience any difference in its ability to move. As such, the patient associated identifier is dimensioned such that its size does not hinder the ability of the subject to physically move. In certain embodiments, the patient associated identifier has a small size, where in certain embodiments the signal receiver has occupies a volume of space of about 5 cm3 or less, such as about 3 cm3 or less, including about 1 cm3 or less.


The patient associated identifiers of interest include both external and implantable devices. In external embodiments, the patient associated identifier is ex vivo, by which is meant that the receiver is present outside of the body during use. Where the identifiers are external, they may be configured in any convenient manner, where in certain embodiments they are configured to be associated with a desirable skin location. As such, in certain embodiments the external signal receivers are configured to be contacted with a topical skin location of a subject. Configurations of interest include, but are not limited to: patches, wrist bands, belts, etc. For instance, a watch or belt worn externally and equipped with suitable receiving electrodes can be used as signal receivers in accordance with one embodiment of the present invention. By further example, it could be positioned by a harness that is worn outside the body and has one or more electrodes that attach to the skin at different locations. In these external embodiments, a portion of the patient associate identifier, e.g., electrode, contacts the skin in a manner such that a communication line that includes the patient's body, e.g., a conductive communication line, may be established between the identifier and a fluid delivery device during use of the system.


Patient associated identifiers of interest also include implantable components. By implantable is meant that the identifier is designed, i.e., configured, for implantation into a patient, e.g., on a semi-permanent or permanent basis. In these instances, the signal receiver is in vivo during use. By implantable is meant that the patient associated identifiers are configured to maintain functionality when present in a physiological environment, including a high salt, high humidity environment found inside of a body, for 2 or more days, such as about 1 week or longer, about 4 weeks or longer, about 6 months or longer, about 1 year or longer, e.g., about 5 years or longer. In certain embodiments, the implantable circuits are configured to maintain functionality when implanted at a physiological site for a period ranging from about 1 to about 80 years or longer, such as from about 5 to about 70 years or longer, and including for a period ranging from about 10 to about 50 years or longer.


Where the patient associated identifiers are implantable, the identifiers may have any convenient shape, including but not limited to: capsule-shaped, disc-shaped, etc. The patient associated identifiers may have any convenient power source, which could either be a primary cell or rechargeable battery, or one that is powered by broadcast inductively to a coil, or even a photoelectric or other power source, as may be appropriate for the identifier given its site of association with the patient (e.g., topical or internal) and expected operating conditions. Implantable patient associated identifiers of interest include a rechargeable battery, e.g., one that recharges automatically from a power transmitter, e.g., coils, present in the patient's environment, e.g., associated with the patient's bed. The patient associated identifier may be configured to be placed in a number of different locations, e.g., the abdomen, small of the back, shoulder (e.g., where implantable pulse generators are placed), etc.


In addition to being configured to participate in transmission of a signal between the identifier and a fluid delivery device using the patient's body as a conduction medium, the patient associated identifier may further include one or more distinct physiological parameter sensing abilities. By physiological parameter sensing ability is meant a capability of sensing a physiological parameter or biomarker, such as, but not limited to: heart rate, respiration rate, temperature, pressure, chemical composition of fluid, e.g., analyte detection in blood, fluid state, blood flow rate, accelerometer motion data, IEGM (intra cardiac electrogram) data, etc.


Patient associated identifiers of the invention may be configured to provide a further communication path via which collected data can be extracted by a patient or health care practitioner. For instance, an implanted collector may include conventional RF circuitry (operating, e.g., in the 405-MHz medical device band) with which a practitioner can communicate, e.g., using a data retrieval device, such as a wand or analogous device. Where the patient associated identifier includes an external component, that component may have output devices for providing, e.g., audio and/or visual feedback; examples include audible alarms, light emitting diodes, display screens, or the like. The external component may also include an interface port via which the component can be connected to a computer for reading out data stored therein. In these instances, the circuitry of the patient associated identifier may be configured to receive signals from devices inside of the subject, e.g., from an identifier of a pharma-informatics enabled pharmaceutical composition, and then relay this information to an external processing device, e.g., a PDA, smartphone, etc.


Of interest in certain situations are parenteral fluid delivery devices that are configured to transmit the fluid transfer signal only when fluid is delivered from the device to the patient and in a manner such that transmission of the signal can only occur when the device actually contacts patient and fluid is transferred to the patient. As such, the system is distinguished from other systems which provide for generation of a signal when a package is opened, or other proxy-type signals for actual administration of the fluid. Instead, the system of the invention provides a signal which provides information that delivery of the fluid to the patient actually occurred, e.g., by only transmitting the signal when the device touches the patient and fluid enters the patient from the device. While the fluid transfer signal may be transmitted between the parenteral fluid delivery device and the patient associated identifier using any convenient protocol, in certain embodiments protocols that ensure transmission only occurs upon contact of the device with the patient are employed. One such protocol of interest is conductive transmission, e.g., where the body is employed as a conductive medium between the fluid delivery device and the patient associated identifier to provide for transmission of the signal.


Patient associated identifiers of interest, including examples of circuitry for the broadcaster and/or receiver elements thereof, include, but are not limited to, those described in: PCT/US2006/16370 titled “Pharma-Informatics System” and filed on Apr. 28, 2006; PCT/US2007/015547 titled “Smart Parenteral Administration System” and filed on Jul. 6, 2007; and PCT/US2008/52845 titled “Ingestible Event Marker Systems” and filed on Feb. 1, 2008; the disclosures of which are herein incorporated by reference.


Fluid Transfer Ports


Fluid transfer ports that are part of systems of the invention may vary widely. In certain embodiments, the ports are partially implanted, while in other embodiments the ports are fully implanted, as is known in the art. The ports may vary from simple to complex, and where desired may include a connector element, e.g., luer lock, for mating with a fluid conveyer, e.g., IV catheter, IV line, etc., of the fluid delivery device. A patient may include two or more fluid transfer ports, such as three or more, four or more, five or more, etc., where the distinct fluid transfer ports are positioned as different locations of the body, e.g., in the neck/collarbone region, on the arms, on the legs, etc.


Additional System Components


As detailed below, certain embodiments are characterized in that the patient associated identifier and/or the fluid delivery device further transmits a signal to and/or receives a signal from an additional external component. The external component is, in certain embodiments, an external processing component, such that it is designed to accept data, perform prescribed mathematical and/or logical operations, and output the results of these operations. Examples of external components of interest include, but are not limited to: a healthcare provider network (e.g., a hospital information system (HIS); a home healthcare information system, etc). Accordingly, systems of the invention may further include an external processor component, such as a hospital information system (HIS) or analogous system that includes various aspects of a patient specific data, such as a prescriptions, treatment regimens, health history, dosage guidelines, etc. This data may include information obtained from an electronic medication storage unit, e.g., a Pyxis system, etc.


The systems may further include various sensors. Physiological sensors may be associated with the patient, and may or may not be part of the patient associated identifier. Physiological sensors of interest include, but are not limited to: heart rate sensors, breathing sensors, temperature sensors, etc., as described more fully above in connection with the patient associated identifier.


Sensors may also be associated with various components of the fluid delivery system. Sensors may be associated with fluid containers, e.g., to detect a color-coded liquid therein, to detect clarity of a fluid, to detect the presence of one or more analytes in the fluid, etc. Sensors may also be present in tubing components of the system, e.g., to detect proxies of bacterial infection, such as turbidity, etc.


Fluid Transfer Signal


As reviewed above, systems of the invention are configured to transfer a fluid transfer signal between the patient associated identifier and the fluid delivery device, where the signal is transferred between these two components using the patient's body as a signal conduction medium. The physical nature of the signal may vary, e.g., where physical types of signals of interest include electric, magnetic, optical, thermal, acoustic, etc. Because the fluid transfer signal is transferred between the two components using the patient's body as a conduction medium, fluid communication is established between the parenteral fluid delivery device and the patient prior to transmission of the fluid transfer signal.


The content of the fluid transfer signal may vary depending on the particular application in which the methods and systems are employed, where the content may range from simple to complex, depending on the particular type of application, e.g., prospective, real-time or historical, the direction, e.g., to and/or from the patient associated identifier, etc. A given fluid transfer signal provides prospective information about a fluid transfer event if the fluid transfer event is a future fluid transfer event, i.e., the fluid transfer event has not yet occurred. A given fluid transfer signal provides real-time information about a fluid transfer event if the fluid transfer event is a currently occurring fluid transfer event, i.e., the fluid transfer currently happening. A given fluid transfer signal provides retrospective information about a fluid transfer event if the fluid transfer event is a past fluid transfer event, i.e., the fluid transfer event has already occurred.


In certain embodiments, the content of the fluid transfer signal is that a fluid connection has been established between the fluid delivery device (including disparate components thereof) and the patient. In certain embodiments, the content of the fluid transfer signal is that of a previously established fluid connection between the fluid delivery device (including disparate components thereof) and the patient has been interrupted. In addition to an indication that a fluid connection has been established, the fluid transfer signal may include additional content, e.g., where additional content of interest includes, but is not limited to: patient specific content, fluid specific content, delivery device specific content, etc.


Patient specific content of interest includes, but is not limited to: identity of patient (e.g., name, unique identifier), general information about the patient, e.g., gender, age, race, etc., health history of patient; health status of patient, including one or more sensed physiological parameters, which may or may not be combined into a health indicative marker, e.g., a wellness marker or index, and the like.


Fluid specific content of interest includes, but is not limited to: identity of the fluid, the contents of the fluid, the identity of one or more pharmacological agents in the fluid, the concentrations of such agents in the fluid, the history of the fluid, e.g., where manufactured, how stored, the quality of the fluid, e.g., whether compromised or not, etc. Also of interest is fluid container specific content, which content includes, but is not limited to: the source/history of the container, the identity of the container, e.g., general (e.g., type such as bag) or specific (e.g., serial no.), etc.


The fluid transfer signal may include information that an actual fluid transfer event has occurred, e.g., a transfer between a parenteral fluid delivery device and a patient. In such embodiments, the fluid transfer signal provides information about whether fluid has been transferred between the parenteral delivery device and the patient. The fluid transfer signal is one that provides for actual knowledge that fluid has been parenterally transferred from the device to the patient.


Accordingly, a given fluid transfer signal may include qualitative or quantitative information. Qualitative information is information that is not tied to specific numerical values or units, and includes but is not limited to: identifying information, quality control information about a fluid (e.g., age, storage conditions, etc.), information about a patient, e.g., how patient is responding, etc., whether something is or is not present, etc. Quantitative information is information that includes numerical values or units, and includes but is not limited to dosage information, etc.


Communication Between System Components


As reviewed above, communication of the fluid transfer signal between the patient associated identifier and the fluid delivery device employs the patient's body as a conductive medium. One or more additional and separate communication lines may be established between various components of the system, such as between the patient associated identifier and an external component, such as a hospital information system, between components of a fluid delivery device, such as an infusion pump and a fluid container, between the fluid delivery device and the hospital information system, etc. These additional communication lines may be wired or wireless communication lines, as desired, employing traditional physical connections, such as wires, optical fibers, etc., or wireless communication protocols, e.g., RFID, etc. These additional communication lines may be employed to transfer information and/or power between the different device components. For example, disparate components of a fluid deliver system may include communications components that are powered via wireless transmission of power from one element to another. These additional communication lines are, in certain embodiments, non-conductive communication lines.


Fluid Transfer Port Identification


As summarized above, the systems as described above are employed in a manner that allows for association of a given fluid transfer event with a specific fluid transfer port. The association may include identification of the specific fluid transfer port that has been, is being or will be employed for a fluid transfer event from a possibility of two or more distinct fluid transfer ports that are associated with a given patient. Accordingly, for those patients that include two or more distinct fluid transfer ports, such as three or more, four or more, etc., the methods and systems of the invention provide for identification of the particular fluid transfer port that has been, is being or will be employed for a given fluid transfer event.


In practicing methods of invention, a parameter of the fluid transfer signal is employed to identify the fluid transfer port that has been, is being or will be used for a given fluid transfer event. The parameter of the fluid transfer signal that is employed is, in certain instances, a non-informational parameter, such as a parameter that does not provide specific information about the patient, nature of the fluid delivery device, nature of the delivered fluid, etc. Instead, the parameter that is employed is a parameter that is independent of any specific content of the signal.


Signal parameters of interest include those parameters that change as a function of distance traveled by the signal between the origin of the signal, e.g., the fluid delivery device or the patient associated identifier, and the destination and/or receiver of the signal, e.g., the patient associated identifier or the fluid delivery device. The parameter may change as a function of distance in either a linear or non-linear manner, depending on the particular nature of the parameter.


One type of parameter that may be employed is a measure of strength of the fluid transfer signal. The fluid transfer signal may consist of a binary signal pattern encoding the information of interest communicated using amplitude modulation, phase key shifting, frequency modulation, or wide-band communication techniques. The parameter that may be employed is the amplitude of the signal, such that the amplitude of the signal at the receiver is employed in determining which of two or more distinct fluid transfer ports will be or has been employed for a given fluid transfer event. In certain embodiments, of interest is an evaluation, e.g., measurement, quantification or other appropriate analysis that provides for comparison to a suitable control, of amplitude of a decoded signal, the envelope strength of a demodulated signal, or statistics related to the time-series or frequency domain characterization of the transmitted signal (i.e., power at specified transmission frequency, standard deviation of time-series transmission packet). Characteristics of the decoded transmission packet, such as signal-to-noise, relative phase, or time-of-detection may also be employed.


In practicing the methods, the parameter of the fluid transfer signal as detected at the receiver component of the system being employed, e.g., the patient associated identifier or the fluid delivery device, is evaluated to determine the identity of the particular fluid transfer port with which the fluid delivery device has established a fluid connection. Evaluation of the signal parameter may include a comparison of the signal parameter to a suitable reference or control value, e.g., an predetermined expected signal parameter value associated with a given fluid transfer port, a comparison to the parameter of the original signal at the fluid transfer port, etc. For example, a patient may have two separate IV ports for use with an IV bag delivery system, where one is located on the left arm and one is located on the right arm. The patient may also have a patient associated identifier located on the right wrist, which acts as a receiver for the fluid transfer signal generated by the IV bag delivery system upon establishment of fluid contact with the patient via one of the two IV ports. The receiver is configured to measure the amplitude of the decoded fluid transfer signal. The signal-to-noise ratio of the signal broadcast by the intelligent IV bag when used to deliver fluid via the IV port on the on the same arm as the patient associated identifier will have a larger amplitude at the patient associated identifier than the signal-to-noise ratio of the signal broadcast by the bag when used to delivery fluid via the IV port on the opposite arm of the receiver. By comparing this measure signal strength at the patient associated identifier on the right wrist to either the signal strength originally broadcast from the fluid delivery device or a predetermined value associated with each of the IV ports, the particular IV port via which fluid communication was established between the fluid delivery device and the patient is identified.


Where the patient has two or more patient associated identifiers associated with different physical locations, e.g., present on each wrist and/or at a torso location, such as the chest, abdomen, etc., one can evaluate the parameter of the signal received at each of the distinct patient associated identifiers and employ derivative and/or triangulation methods to identify the port with which fluid communication was established.


The receiver/evaluation functions performed in practicing the methods may be located at the patient associated identifier or the fluid deliver device, as desired. For example, the signal whose parameter is evaluated in practicing the methods may be one broadcast by the fluid delivery device and received at the patient identifier. Alternatively, the signal whose parameter is evaluated may be one that is broadcast by the patient associated identifier and received at the fluid delivery device. In the latter embodiment, the signal may be one that is continually broadcast, such that it will be broadcast and detected when fluid communication is established by the fluid delivery device via a fluid transfer port. In the former case, the signal may be one that is only broadcast by the fluid delivery device upon establishment of fluid communication.


Where desired, the methods include generating an error signal when the identified fluid transfer port is an incorrect fluid transfer port. For example, the system may be configured to have knowledge regarding which IV ports are to be employed for a given fluid delivery device. When the wrong IV port is employed by a fluid delivery device, the system is configured in these embodiments to produce an error signal. The nature of the error signal may vary, may cause an alarm, e.g., visual and/or sound, to be produced; a message to be sent to a health care manager, e.g., via a hospital information system, etc. Such embodiments are desirable where intervention because of the error is desired, e.g., to counteract any problems caused by the error. In such applications, a processor is conveniently employed to match a port and fluid transfer event specific information, e.g., to determine whether or not to allow the fluid transfer event to occur, to produce an error signal, etc. The location of this processor may vary within the components of the system, as desired. As such, in certain embodiments, the processor may be located in the patient associated identifier. In certain other embodiments, the processor may be located in the fluid delivery device. In yet other embodiments, the processor may be located in the hospital information system.


Where desired, the system may be configured to produce a fluid administration log comprising information about fluid delivery via the two or more distinct fluid transfer ports. The log (i.e., history) that is produced may vary in format, including a recorded file on a suitable computer readable medium which can be output to a user via a user interface of a monitor, a paper printout, etc.


Systems of the invention may be configured to associate a signal fluid transfer port at a time with a given fluid transfer event, or the systems may be configured to associate two or more fluid transfer ports with two or more simultaneous fluid transfer events. For example, the systems may be configured to evaluate fluid transfer events that are simultaneously occurring at each of two or more distinct fluid transfer ports, e.g., where each distinct fluid transfer event has a unique fluid transfer signal that can be distinguished by the receiver component, e.g., present in the patient associate identifier(s).


Applications


The methods of the invention find use in a variety of different applications, including those where one wishes to identify which port of a plurality of two or more distinct fluid transfer ports will be, is being or has been employed for a given fluid transfer event. Certain applications of the systems are prospective applications, in that the system is employed prospectively to evaluate a fluid transfer event (e.g., delivery of a fluid dosage to a patient), where the fluid transfer event has yet to actually occur. Specifically, the prospective applications enable identification of which fluid transfer port will be employed for a fluid transfer event before the event occurs. Such applications include situations where the system is employed as a check to ensure that a given dosage of a fluid is going to be administered to the patient via the correct fluid transfer port. If a proper match is detected between the fluid transfer port and the fluid transfer event of interest, the system can be configured to automatically enable the fluid transfer event to occur, e.g., by activating the fluid delivery device, such as the pump. Alternatively, where a proper match between a fluid transfer port and a given fluid transfer event is not detected, the system can be configured to disable the fluid transfer event, e.g., by inactivating the fluid delivery device, etc.


Where desired, the systems of the invention are configured to provide an error signal upon detection of an error in a parenteral administration event. As such, the systems may be configured to generate an error signal when the wrong port is identified for a given fluid transfer event. The signal may also vary greatly, including an audible alarm, an alarm signal sent to a physician, etc. Such embodiments include methods where the system is monitored for the occurrence of the error signal.


Applications of interest also include real-time applications, where the system is employed to evaluate a fluid transfer event (e.g., which port is employed for delivery of a fluid dosage to a patient), while the fluid transfer event is actually occurring, i.e., is in progress. For example, the system can be used to monitor the patient for an adverse reaction during delivery of the fluid, e.g., by monitoring physiological parameters of the patient. If monitored physiological parameters vary from acceptable predetermined ranges, the system can be configured to produce an error signal, e.g., as described above, and or take action, e.g., investigate the specific port to ensure that the specific port is operating correctly. One example of such an application is where, during a given fluid transfer event, the transfer of fluid is compromised in some manner, e.g., interrupted. The system may be configured to generate a signal indicative of such an interruption, which could be manifested as an alarm, etc., causing the particular functionality of the identified port to be investigated. In response to the error signal, the particular fluid transfer port that may be evaluated, fixed as necessary and/or replaced, e.g., in order to avoid further complications.


Also of interest are uses of the systems and methods for historical applications, such that the systems are employed to obtain a true and correct record of fluid transfer events that have actually occurred between a patient and a fluid delivery device, and specifically which ports have been employed for which specific fluid transfer events. Historical applications are any applications that use information which includes knowledge that a fluid transfer event has actually occurred and which fluid transfer port was employed. True and accurate records of fluid transfer events find use in providing health care practitioners or other individuals of accurate treatment records for a given patient. As such, historical applications include employing the fluid transfer event data in further treatment of an individual, e.g., developing future treatment regimens and/or modifying existent treatment regimens. Additional historical applications of interest include employing the fluid transfer event data for invoicing purposes, e.g., so that patients are accurately billed for medications and/or services that they actually receive, etc. (for example, where compensation is tied to which port is employed, accurate records of port employment are obtained for such invoicing purposes).


Specific Illustrative Embodiments of the Methods and Systems


Aspects of the invention having been described in general terms above, additional details in the context of specific embodiments are now provided. One embodiment of an IV fluid delivery system according to the invention is shown in FIG. 1.


As shown in FIG. 1, a transmitter 52 is attached to the IV bag 56 or the IV set, which is anything connected to the IV bag, and a receiver 53, which is also referred to as a patient associated identifier, is implanted in the patient. When the IV bag is not connected to the patient, the receiver 53 cannot detect the transmitter 52 transmitting from the IV bag 54. But when the IV bag is infusing fluid, or there is a fluid connection between the IV bag 54 and the receiver 53 via the patient 50 acting as a conducting bridge, or at least attached to the arm in anticipation of delivery of fluid from the IV bag to the patient, then a signal is transmitted by the IV bag 54 and received by the receiver 53.


During operation, the transmitter capacitively couples a signal to the fluid. That signal transmits through the fluid and to the patient, through the patient's body, and to the receiver, e.g., one electrode of the receiver (thereby making up one side of the conductive loop). The other side of the conductive loop is that on the other side of the transmitter, which capacitively couples a signal to ground, which is everything surrounding a patient which is not attached to the patient. The ground could be chairs, tables, the floor, etc. The signal goes through the ground and then is capacitively coupled to the other side of the patch receiver, thereby completing the loop. This capacitive coupling on either side to ground is illustrated in the FIG. 1 by capacitors and dashed arrows 55 and 57, respectively.


Referring to 1, starting at transmitter 52, the fluid signal goes through the bag 54, which is the container or IV bag, and is capacitively coupled through the IV bag. Then the signal progresses to the fluid in the IV bag 56 through the IV tube 58, through the patient's arm, or a vein somewhere in the body, e.g., arm, leg or elsewhere in the body. The signal continues to go through the body to the receiver 53. On the other side of the receiver, a capacitive coupling 57 between the receiver housing and the ground is provided to give a differential signal. The loop is completed through the ground and back up through the capacitive coupling 55 from the ground to the broadcaster, which is attached to the IV bag.


The fluid transfer signal may be a high frequency signal, e.g., between 1 and 10 MHz, and may be higher, e.g., 100 MHz or more, e.g., 1 GHz or more. The frequency is in a range such that the receiver only picks up the signal when the IV bag is connected to the body, and not just by the electromagnetic waves that are emitted by the broadcaster. In certain embodiments, the frequency is chosen based on the considerations that the higher the frequency, the easier it is to couple it directly to the IV bag, but the more likely it is that the signal will be picked up by the receiver regardless of whether the IV bag is connected to the body.


In certain embodiments, the fluid transfer signal also encodes a number, either through phase shift keying, or through frequency shift keying, or one of any other telecommunication convenient technique.


Also shown in FIG. 1 are fluid transfer ports 59A and 59B. By evaluating a parameter of the fluid transfer signal at receiver 53, identification that port 59A is being employed for the fluid transfer event with bag 56 is made.


A variation of this system is where there are two separate links. One of the links goes from an IV bag via a fluid processing unit, e.g., a pump. A second of the links is established between the processing unit and the patient. Such an embodiment is illustrated in FIG. 2. A transconduction link 61 goes from the IV bag 54 into the IV pump 66. A second transconduction link 63 goes from the IV pump 66 to the patient 50, e.g., via one of multiple fluid transfer ports (not shown). If, for example, there are any processing or filtering, or additional chemicals at the IV pump, a different signal may be transmitted to the body which is distinct from the signal transmitted from the IV bags. For example, if there are two different IV bags that are being mixed by the pump, and delivered immediately after being mixed, each of them would be broadcasting identifying information about one of the solutions to the IV pump, and a different signal reflecting that combination being administered to the patient would be broadcast from the pump 66 to the patient associated identifier 53.


Still referring to FIG. 2, the entire system is depicted, where the patient associated identifier 53 broadcasts via an RF link to one or more external devices, e.g., a network of relay stations 65, handheld devices, personal digital assistants, e.g., smart phones, etc. The transmitted data may be data that have been gathered over time, or obtained immediately following reception of delivery data, or even instantaneous data. The data may be further communicated, e.g., via an RF link to a relay station, which then may be further communicated, e.g., through either an RF link or a conductive path link such as a cable or any other type of telecommunication link to an external processing component 68, such as a Health Information System or Service or Server (Hospital Information System (HIS)) within the hospital or care facility. Then this information is processed an output, e.g., recorded to a physical recordable medium, displayed to a user, etc., such as displayed to a nurse or other medical practitioner.


Where desired, the external processor 68 can provide various alerts. For example, an IV bag could have bar codes on it for shipping and receiving purposes, and also before for providing information to be transferred before the contents of the bag are administered to the patient. For example, a given medical fluid container with fluid may be bar coded and entered into the health information system (hospital information system). The prescription for a given patient with respect to that medical fluid container may also be entered into the health information system, and that prescription may be downloaded into the patient's patient associated identifier, e.g., through an RF link. In addition, the same information may be downloaded, for example to the IV pump that is being used to deliver the fluid inside the container to the patient. The IV pump, for example, may only permit delivery after two confirmations occur. In addition, the system may be configured to confirm that the correct IV port will be employed for delivery of the fluid.


In certain embodiments, the port identification information obtained with methods and systems of the invention can also be linked to an internet system. For example, by using a wireless communication protocol, the port identification information can be broadcasted to a hospital bedside monitor. The bedside monitor may then be configured to relay the information to the internet and subsequently to the data base management system. As such, the patient's medical record and IV port usage information is immediately updated and could be verified against the patient's health record so that if the administered medicine was incorrectly administered via the wrong port, an alert to an appropriate individual, e.g., a nursing staff member may be made.


Kits


Also provided are kits for practicing the subject methods. Kits may include one or more receivers of the invention, as described above. In addition, the kits may include one or more parenteral fluid deliver devices, e.g., IV bags, etc.


The subject kits may also include instructions for how to practice the subject methods using the components of the kit. The instructions may be recorded on a suitable recording medium or substrate. For example, the instructions may be printed on a substrate, such as paper or plastic, etc. As such, the instructions may be present in the kits as a package insert, in the labeling of the container of the kit or components thereof (i.e., associated with the packaging or sub-packaging) etc. In other embodiments, the instructions are present as an electronic storage data file present on a suitable computer readable storage medium, e.g. CD-ROM, diskette, etc. In yet other embodiments, the actual instructions are not present in the kit, but means for obtaining the instructions from a remote source, e.g. via the internet, are provided. An example of this embodiment is a kit that includes a web address where the instructions can be viewed and/or from which the instructions can be downloaded. As with the instructions, this means for obtaining the instructions is recorded on a suitable substrate.


Some or all components of the subject kits may be packaged in suitable packaging to maintain sterility. In many embodiments of the subject kits, the components of the kit are packaged in a kit containment element to make a single, easily handled unit, where the kit containment element, e.g., box or analogous structure, may or may not be an airtight container, e.g., to further preserve the sterility of some or all of the components of the kit.


It is to be understood that this invention is not limited to particular embodiments described, as such may vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present invention will be limited only by the appended claims.


Where a range of values is provided, it is understood that each intervening value, to the tenth of the unit of the lower limit unless the context clearly dictates otherwise, between the upper and lower limit of that range and any other stated or intervening value in that stated range, is encompassed within the invention. The upper and lower limits of these smaller ranges may independently be included in the smaller ranges and are also encompassed within the invention, subject to any specifically excluded limit in the stated range. Where the stated range includes one or both of the limits, ranges excluding either or both of those included limits are also included in the invention.


Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the present invention, representative illustrative methods and materials are now described.


All publications and patents cited in this specification are herein incorporated by reference as if each individual publication or patent were specifically and individually indicated to be incorporated by reference and are incorporated herein by reference to disclose and describe the methods and/or materials in connection with which the publications are cited. The citation of any publication is for its disclosure prior to the filing date and should not be construed as an admission that the present invention is not entitled to antedate such publication by virtue of prior invention. Further, the dates of publication provided may be different from the actual publication dates which may need to be independently confirmed.


It is noted that, as used herein and in the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. It is further noted that the claims may be drafted to exclude any optional element. As such, this statement is intended to serve as antecedent basis for use of such exclusive terminology as “solely,” “only” and the like in connection with the recitation of claim elements, or use of a “negative” limitation.


As will be apparent to those of skill in the art upon reading this disclosure, each of the individual embodiments described and illustrated herein has discrete components and features which may be readily separated from or combined with the features of any of the other several embodiments without departing from the scope or spirit of the present invention. Any recited method can be carried out in the order of events recited or in any other order which is logically possible.

Claims
  • 1. A method of associating a specific fluid transfer port with a given fluid transfer event of fluid to a patient from a parenteral fluid delivery device, the method comprising: transmitting a conductive fluid transfer signal from the parenteral fluid delivery device to a patient associated identifier by capacitively coupling the conductive fluid transfer signal to the fluid infused to the patient from the parenteral fluid delivery device, wherein the patient associated identifier is configured to use a patient's body as a signal conduction medium upon establishment of a fluid transfer connection between the parenteral fluid delivery device and the patient, and wherein the parenteral delivery device is coupled to the patient using a plurality of fluid transfer ports; anddetermining which of the plurality of fluid transfer ports is employed for the given fluid transfer event based on a parameter of the conductive fluid transfer signal; andwherein the parameter varies with respect to distance traveled by the fluid transfer signal.
  • 2. The method according to claim 1, wherein the parameter is a measure of signal strength of the fluid transfer signal.
  • 3. A method of associating a specific fluid transfer port with a given fluid transfer event of fluid to a patient from a parenteral fluid delivery device, the method comprising: transmitting a conductive fluid transfer signal from the parenteral fluid delivery device to a patient associated identifier by capacitively coupling the conductive fluid transfer signal to the fluid infused to the patient from the parenteral fluid delivery device, wherein the patient associated identifier is configured to use a patient's body as a signal conduction medium upon establishment of a fluid transfer connection between the parenteral fluid delivery device and the patient, and wherein the parenteral delivery device is coupled to the patient using a plurality of fluid transfer ports; anddetermining which of the plurality of fluid transfer ports is employed for the given fluid transfer event based on a parameter of the conductive fluid transfer signal; andtransmitting an acknowledgement of the conductive fluid transfer signal from the patient associated identifier to the parenteral fluid delivery device.
  • 4. The method according to claim 3, wherein the patient associated identifier and the parenteral fluid delivery device are further configured to communicate non-conductively.
  • 5. The method according to claim 3, further comprising transmitting a signal from at least one of the patient associated identifier or the parenteral fluid delivery device to an external processing system.
  • 6. The method according to claim 5, wherein the external processing system is a hospital information system.
  • 7. The method according to claim 3, further comprising generating an error signal when the associated fluid transfer port is an incorrect fluid transfer port.
  • 8. The method according to claim 3, further comprising producing a fluid administration log comprising information about fluid delivery via the plurality of fluid transfer ports.
  • 9. A system comprising: a parenteral fluid delivery device configured to transmit a conductive fluid transfer signal;a patient associated identifier configured to be associated with a patient, and wherein the patient associated identifier is configured to use a patient's body as a signal conduction medium upon establishment of a fluid transfer connection between the parenteral fluid delivery device and the patient; anda plurality of fluid transfer ports, wherein each one of the plurality of fluid transfer ports is configured to couple the parenteral fluid delivery device or another fluid delivery device with the patient; andwherein the parenteral fluid delivery device is configured to transmit the conductive fluid transfer signal to the patient associated identifier by capacitively coupling the conductive fluid transfer signal to fluid of the parenteral fluid delivery device infused to the patient; andwherein at least one of the parenteral fluid delivery device and the patient associated identifier is configured to determine which of the plurality of fluid transfer ports is employed for a fluid transfer event associated with the parenteral fluid delivery device based on a parameter of the fluid transfer signal.
  • 10. The system according to claim 9, wherein the patient associated identifier further comprises a transmitter for transmitting a signal acknowledging the conductive fluid transfer signal to the parenteral fluid delivery device, and wherein the parenteral fluid delivery device further comprises a receiver for receiving the signal acknowledging the conductive fluid transfer signal from the patient associated identifier.
  • 11. The system according to claim 9, wherein said system further comprises an external processing system.
  • 12. The system according to claim 11, wherein said external processing system is a hospital information system.
  • 13. The system according to claim 9, wherein the system is configured to produce an error signal when the determined specific fluid transfer port is an incorrect fluid transfer port for the fluid transfer event.
  • 14. The system according to claim 9, wherein the system is configured to produce a fluid administration log comprising information about fluid delivery via the plurality of fluid transfer ports.
  • 15. The system according to claim 9, wherein the patient associated identifier is configured to be associated with the patient by coupling the patient associated identifier to the patient topically or by implantation.
  • 16. The system according to claim 9, wherein the patient associated identifier and the parenteral fluid delivery device are further configured to communicate non-conductively.
  • 17. A system comprising: a parenteral fluid delivery device configured to transmit a conductive fluid transfer signal;a patient associated identifier configured to be associated with a patient, and wherein the patient associated identifier is configured to use a patient's body as a signal conduction medium upon establishment of a fluid transfer connection between the parenteral fluid delivery device and the patient; anda plurality of fluid transfer ports, wherein each one of the plurality of fluid transfer ports is configured to couple the parenteral fluid delivery device or another fluid delivery device with the patient; andwherein the parenteral fluid delivery device is configured to transmit the conductive fluid transfer signal to the patient associated identifier by capacitively coupling the conductive fluid transfer signal to fluid of the parenteral fluid delivery device infused to the patient; andan external processing system configured to receive information regarding a parameter of the fluid transfer signal and to determine which of the plurality of fluid transfer ports is employed for a fluid transfer event associated with the parenteral fluid delivery device based on the parameter of the fluid transfer signal.
  • 18. A method of associating a specific fluid transfer port with a given fluid transfer event of fluid to a patient from a parenteral fluid delivery device, the method comprising: transmitting a conductive fluid transfer signal from the parenteral fluid delivery device to a patient associated identifier by capacitively coupling the conductive fluid transfer signal to the fluid infused to the patient from the parenteral fluid delivery device, wherein the patient associated identifier is configured to use a patient's body as a signal conduction medium upon establishment of a fluid transfer connection between the parenteral fluid delivery device and the patient, and wherein the parenteral delivery device is coupled to the patient using a plurality of fluid transfer ports;determining which of the plurality of fluid transfer ports is employed for the given fluid transfer event based on a parameter of the conductive fluid transfer signal;generating an error signal when the associated fluid transfer port is an incorrect fluid transfer port; anddisabling the parenteral fluid delivery device upon receiving the error signal.
CROSS-REFERENCE TO RELATED APPLICATIONS

Pursuant to 35 U.S.C. §119 (e), this application claims priority to the filing date of: U.S. Provisional Patent Application Ser. No. 60/982,661 filed Oct. 25, 2007; the disclosure of which applications is herein incorporated by reference.

US Referenced Citations (495)
Number Name Date Kind
3812854 Michaels et al. May 1974 A
3880146 Everett et al. Apr 1975 A
4403989 Christensen et al. Sep 1983 A
4475905 Himmelstrup Oct 1984 A
4487602 Christensen et al. Dec 1984 A
4529401 Leslie et al. Jul 1985 A
4551133 Zegers de Beyl et al. Nov 1985 A
4621644 Ellers Nov 1986 A
4669479 Dunseath, Jr. Jun 1987 A
4705503 Dorman et al. Nov 1987 A
4795429 Feldstein Jan 1989 A
4850967 Cosmai Jul 1989 A
4911916 Cleary Mar 1990 A
4922901 Brooks et al. May 1990 A
5006342 Cleary et al. Apr 1991 A
5125888 Howard et al. Jun 1992 A
5135479 Sibalis et al. Aug 1992 A
5156911 Stewart Oct 1992 A
5167649 Zook Dec 1992 A
5190522 Wojcicki et al. Mar 1993 A
5205292 Czar et al. Apr 1993 A
5213568 Lattin et al. May 1993 A
5246418 Haynes et al. Sep 1993 A
5284133 Burns et al. Feb 1994 A
5300299 Sweet et al. Apr 1994 A
5317506 Coutre et al. May 1994 A
5331953 Andersson et al. Jul 1994 A
5351695 Mills et al. Oct 1994 A
5363842 Mishelevich et al. Nov 1994 A
5364838 Rubsamen Nov 1994 A
5394866 Ritson et al. Mar 1995 A
5404871 Goodman et al. Apr 1995 A
5415866 Zook May 1995 A
5423750 Spiller Jun 1995 A
5479920 Piper et al. Jan 1996 A
5487378 Robertson et al. Jan 1996 A
5505195 Wolf Apr 1996 A
5505958 Bello et al. Apr 1996 A
5507277 Rubsamen et al. Apr 1996 A
5509404 Lloyd et al. Apr 1996 A
5522378 Ritson et al. Jun 1996 A
5527288 Gross et al. Jun 1996 A
5536503 Kitchell et al. Jul 1996 A
5540669 Sage et al. Jul 1996 A
5542410 Goodman et al. Aug 1996 A
5556421 Prutchi et al. Sep 1996 A
5570682 Johnson Nov 1996 A
5586550 Ivri et al. Dec 1996 A
5587237 Korpman Dec 1996 A
5593390 Castellano et al. Jan 1997 A
RE35474 Woodard et al. Mar 1997 E
5608647 Rubsamen et al. Mar 1997 A
5616124 Hague et al. Apr 1997 A
5622162 Johannson et al. Apr 1997 A
5622180 Tammi et al. Apr 1997 A
5634899 Shapland et al. Jun 1997 A
5645855 Lorenz Jul 1997 A
5655516 Goodman et al. Aug 1997 A
5655523 Hodson et al. Aug 1997 A
5656286 Miranda et al. Aug 1997 A
5666945 Davenport Sep 1997 A
5676129 Rocci, Jr. et al. Oct 1997 A
5686099 Sablotsky et al. Nov 1997 A
5688232 Flower Nov 1997 A
5694919 Rubsamen et al. Dec 1997 A
5694920 Abrams et al. Dec 1997 A
5697899 Hillman et al. Dec 1997 A
5709202 Lloyd et al. Jan 1998 A
5713349 Keaney Feb 1998 A
5724986 Jones, Jr. et al. Mar 1998 A
5740793 Hodson et al. Apr 1998 A
5746711 Sibalis et al. May 1998 A
5781442 Engleson et al. Jul 1998 A
5794612 Wachter et al. Aug 1998 A
5807375 Gross et al. Sep 1998 A
5809997 Wolf Sep 1998 A
5810888 Fenn Sep 1998 A
5813397 Goodman et al. Sep 1998 A
5823179 Grychowski et al. Oct 1998 A
5826570 Goodman et al. Oct 1998 A
5830175 Flower Nov 1998 A
5839430 Cama Nov 1998 A
5843014 Lattin et al. Dec 1998 A
5848991 Gross et al. Dec 1998 A
5851197 Marano et al. Dec 1998 A
5857994 Flower Jan 1999 A
5860957 Jacobsen et al. Jan 1999 A
5865786 Sibalis et al. Feb 1999 A
5865787 Shapland et al. Feb 1999 A
5873835 Hastings et al. Feb 1999 A
5894841 Voges Apr 1999 A
5906579 Vander et al. May 1999 A
5906597 McPhee et al. May 1999 A
5921237 Eisele et al. Jul 1999 A
5924997 Campbell Jul 1999 A
5925021 Castellano et al. Jul 1999 A
5928201 Poulsen et al. Jul 1999 A
5960792 Lloyd et al. Oct 1999 A
5967986 Cimochowski et al. Oct 1999 A
5967989 Cimochowski et al. Oct 1999 A
5991655 Gross et al. Nov 1999 A
5997501 Gross et al. Dec 1999 A
6006747 Eisele et al. Dec 1999 A
6012454 Hodson et al. Jan 2000 A
6018680 Flower Jan 2000 A
6024976 Miranda et al. Feb 2000 A
6029083 Flower et al. Feb 2000 A
6053873 Govari et al. Apr 2000 A
6053888 Kong Apr 2000 A
6055980 Mecikalski et al. May 2000 A
RE36754 Noel Jun 2000 E
6076519 Johnson Jun 2000 A
6085740 Ivri et al. Jul 2000 A
6085742 Wachter Jul 2000 A
6095141 Armer et al. Aug 2000 A
6105571 Coffee Aug 2000 A
6109260 Bathe Aug 2000 A
6116233 Denyer et al. Sep 2000 A
6119684 Nohl et al. Sep 2000 A
6125844 Samiotes Oct 2000 A
6142146 Abrams et al. Nov 2000 A
6148815 Wolf Nov 2000 A
6152130 Abrams et al. Nov 2000 A
6196218 Voges Mar 2001 B1
6196219 Hess et al. Mar 2001 B1
6198966 Heruth Mar 2001 B1
6202642 Mckinnon et al. Mar 2001 B1
6221383 Miranda et al. Apr 2001 B1
6231560 Bui et al. May 2001 B1
6237398 Porat et al. May 2001 B1
6237589 Denyer et al. May 2001 B1
6237594 Davenport May 2001 B1
6245026 Campbell et al. Jun 2001 B1
6251079 Gambale et al. Jun 2001 B1
6254573 Haim et al. Jul 2001 B1
6256533 Yuzhakov et al. Jul 2001 B1
6260549 Sosiak Jul 2001 B1
6269340 Ford et al. Jul 2001 B1
6272370 Gillies et al. Aug 2001 B1
6283951 Flaherty et al. Sep 2001 B1
6283953 Ayer et al. Sep 2001 B1
6309370 Haim et al. Oct 2001 B1
6315719 Rose et al. Nov 2001 B1
6316022 Mantelle Nov 2001 B1
6318361 Sosiak Nov 2001 B1
6327486 Nissila et al. Dec 2001 B1
6340357 Poulsen et al. Jan 2002 B1
6349724 Burton et al. Feb 2002 B1
6352715 Hwang et al. Mar 2002 B1
6377848 Garde et al. Apr 2002 B1
6378520 Davenport Apr 2002 B1
6385488 Flower et al. May 2002 B1
6390088 Nohl et al. May 2002 B1
6394997 Lemelson May 2002 B1
6397838 Zimlich et al. Jun 2002 B1
6406426 Reuss et al. Jun 2002 B1
6413238 Maget Jul 2002 B1
6422236 Nilsson et al. Jul 2002 B1
6425392 Sosiak Jul 2002 B1
6427684 Ritsche et al. Aug 2002 B2
6431171 Burton Aug 2002 B1
6435175 Stenzler Aug 2002 B1
6443146 Voges Sep 2002 B1
6448303 Paul Sep 2002 B1
6453195 Thompson Sep 2002 B1
6468242 Wilson et al. Oct 2002 B1
6484721 Bliss Nov 2002 B1
6485461 Mason et al. Nov 2002 B1
6516796 Cox et al. Feb 2003 B1
6517481 Hoek et al. Feb 2003 B2
6517527 Gambale et al. Feb 2003 B2
6520928 Junior et al. Feb 2003 B1
6527759 Tachibana et al. Mar 2003 B1
6533733 Ericson et al. Mar 2003 B1
6536423 Conway Mar 2003 B2
6540154 Ivri et al. Apr 2003 B1
6564093 Ostrow et al. May 2003 B1
6568390 Nichols et al. May 2003 B2
6575932 O'Brien et al. Jun 2003 B1
6578741 Ritsche et al. Jun 2003 B2
6582393 Sage Jun 2003 B2
6584971 Denyer et al. Jul 2003 B1
6585698 Packman et al. Jul 2003 B1
6589229 Connelly et al. Jul 2003 B1
6599281 Struys et al. Jul 2003 B1
6605072 Struys et al. Aug 2003 B2
6606989 Brand et al. Aug 2003 B1
6607508 Knauer Aug 2003 B2
6615827 Greenwood et al. Sep 2003 B2
6629524 Goodall et al. Oct 2003 B1
6640804 Ivri et al. Nov 2003 B2
6651651 Bonney et al. Nov 2003 B1
6655381 Keane et al. Dec 2003 B2
6656148 Das et al. Dec 2003 B2
6678555 Flower et al. Jan 2004 B2
6685648 Flaherty et al. Feb 2004 B2
6705316 Blythe et al. Mar 2004 B2
6715487 Nichols et al. Apr 2004 B2
6723077 Pickup et al. Apr 2004 B2
6726661 Munk et al. Apr 2004 B2
6728574 Ujhelyi et al. Apr 2004 B2
6745761 Christup et al. Jun 2004 B2
6745764 Hickle Jun 2004 B2
6746429 Sadowski et al. Jun 2004 B2
6748945 Grychowski et al. Jun 2004 B2
6796305 Banner et al. Sep 2004 B1
6796956 Hartlaub et al. Sep 2004 B2
6807965 Hickle Oct 2004 B1
6810290 Lebel et al. Oct 2004 B2
6854461 Nichols et al. Feb 2005 B2
6858011 Sehgal Feb 2005 B2
6866037 Aslin et al. Mar 2005 B1
6886557 Childers et al. May 2005 B2
6893415 Madsen et al. May 2005 B2
6902740 Schaberg et al. Jun 2005 B2
6923784 Stein et al. Aug 2005 B2
6941168 Girouard Sep 2005 B2
6949081 Chance Sep 2005 B1
6958691 Anderson et al. Oct 2005 B1
6961601 Matthews et al. Nov 2005 B2
6971383 Hickey et al. Dec 2005 B2
6981499 Anderson et al. Jan 2006 B2
6983652 Blakely et al. Jan 2006 B2
6985771 Fischell et al. Jan 2006 B2
6985870 Martucci et al. Jan 2006 B2
6990975 Jones et al. Jan 2006 B1
6999854 Roth Feb 2006 B2
7010337 Furnary et al. Mar 2006 B2
7034692 Hickle Apr 2006 B2
7040314 Nguyen et al. May 2006 B2
7044911 Drinan et al. May 2006 B2
7047964 Bacon May 2006 B2
7054782 Hartlaub May 2006 B2
7072802 Hartlaub Jul 2006 B2
7089935 Rand Aug 2006 B1
7097853 Garbe et al. Aug 2006 B1
7104972 Moller et al. Sep 2006 B2
7107988 Pinon et al. Sep 2006 B2
7108680 Rohr et al. Sep 2006 B2
7117867 Cox et al. Oct 2006 B2
7138088 Wariar et al. Nov 2006 B2
7147170 Nguyen et al. Dec 2006 B2
7168597 Jones et al. Jan 2007 B1
7181261 Silver et al. Feb 2007 B2
7191777 Brand et al. Mar 2007 B2
7198172 Harvey et al. Apr 2007 B2
7201734 Hickle Apr 2007 B2
7204823 Estes et al. Apr 2007 B2
7220240 Struys et al. May 2007 B2
7225805 Bacon Jun 2007 B2
7232435 Hildebrand et al. Jun 2007 B2
7242981 Ginggen Jul 2007 B2
7247154 Hickle Jul 2007 B2
7261733 Brown et al. Aug 2007 B1
7267121 Ivri et al. Sep 2007 B2
7278983 Ireland et al. Oct 2007 B2
7291126 Shekalim Nov 2007 B2
7320675 Pastore et al. Jan 2008 B2
7322352 Minshull et al. Jan 2008 B2
7322355 Jones et al. Jan 2008 B2
7331340 Barney Feb 2008 B2
7342660 Altobelli et al. Mar 2008 B2
7347200 Jones et al. Mar 2008 B2
7347202 Aslin et al. Mar 2008 B2
7347851 Kriksunov Mar 2008 B1
7367968 Rosenberg et al. May 2008 B2
7380550 Sexton et al. Jun 2008 B2
7382263 Danowski et al. Jun 2008 B2
7383837 Robertson et al. Jun 2008 B2
7387121 Harvey Jun 2008 B2
7390311 Hildebrand et al. Jun 2008 B2
7397730 Skyggebjerg et al. Jul 2008 B2
7415384 Hartlaub Aug 2008 B2
7424888 Harvey et al. Sep 2008 B2
7455667 Uhland et al. Nov 2008 B2
7458373 Nichols et al. Dec 2008 B2
7467629 Rand Dec 2008 B2
7483743 Mann et al. Jan 2009 B2
7488305 Mickley et al. Feb 2009 B2
7495546 Lintell et al. Feb 2009 B2
7510551 Uhland et al. Mar 2009 B2
7517332 Tonelli et al. Apr 2009 B2
7520278 Crowder et al. Apr 2009 B2
7530352 Childers et al. May 2009 B2
7530975 Hunter May 2009 B2
7537590 Santini et al. May 2009 B2
7542798 Girouard Jun 2009 B2
7544190 Pickup et al. Jun 2009 B2
7548314 Altobelli et al. Jun 2009 B2
7549421 Levi et al. Jun 2009 B2
7552728 Bonney et al. Jun 2009 B2
7554090 Coleman et al. Jun 2009 B2
7575003 Rasmussen et al. Aug 2009 B2
7581540 Hale et al. Sep 2009 B2
7597099 Jones et al. Oct 2009 B2
7631643 Morrison et al. Dec 2009 B2
7670329 Flaherty et al. Mar 2010 B2
7672726 Ginggen Mar 2010 B2
7677467 Fink et al. Mar 2010 B2
7686788 Freyman et al. Mar 2010 B2
7699060 Bahm Apr 2010 B2
7699829 Harris et al. Apr 2010 B2
7708011 Hochrainer et al. May 2010 B2
7713229 Veit et al. May 2010 B2
7715919 Osorio et al. May 2010 B2
7717877 Lavi et al. May 2010 B2
7725161 Karmarker et al. May 2010 B2
7783344 Lackey et al. Aug 2010 B2
7904133 Gehman et al. Mar 2011 B2
8016798 Sparks et al. Sep 2011 B2
8162899 Tennican Apr 2012 B2
8777894 Butterfield et al. Jul 2014 B2
20010000802 Soykan et al. May 2001 A1
20010022279 Denyer et al. Sep 2001 A1
20020000225 Schuler et al. Jan 2002 A1
20020002349 Flaherty et al. Jan 2002 A1
20020010432 Klitmose et al. Jan 2002 A1
20020013615 Haim et al. Jan 2002 A1
20020026940 Brooker et al. Mar 2002 A1
20020077852 Ford et al. Jun 2002 A1
20020099328 Scheiner et al. Jul 2002 A1
20020120236 Diaz et al. Aug 2002 A1
20020153006 Zimlich et al. Oct 2002 A1
20020189612 Rand et al. Dec 2002 A1
20020189615 Henry et al. Dec 2002 A1
20020198493 Diaz et al. Dec 2002 A1
20030004236 Meade et al. Jan 2003 A1
20030078561 Gambale et al. Apr 2003 A1
20030079744 Bonney et al. May 2003 A1
20030094508 Peng et al. May 2003 A1
20030136418 Behm et al. Jul 2003 A1
20030140921 Smith et al. Jul 2003 A1
20030150446 Patel et al. Aug 2003 A1
20030159693 Melker et al. Aug 2003 A1
20030168057 Snyder et al. Sep 2003 A1
20030171738 Konieczynski et al. Sep 2003 A1
20030176804 Melker Sep 2003 A1
20030183226 Brand et al. Oct 2003 A1
20030205229 Crockford et al. Nov 2003 A1
20040004133 Ivri et al. Jan 2004 A1
20040019321 Sage et al. Jan 2004 A1
20040025871 Davies et al. Feb 2004 A1
20040031331 Blakley et al. Feb 2004 A1
20040050385 Bonney et al. Mar 2004 A1
20040089299 Bonney et al. May 2004 A1
20040098117 Hossainy et al. May 2004 A1
20040106902 Diaz et al. Jun 2004 A1
20040122530 Hansen et al. Jun 2004 A1
20040133154 Flaherty et al. Jul 2004 A1
20040139963 Ivri et al. Jul 2004 A1
20040158167 Smith et al. Aug 2004 A1
20040181196 Pickup et al. Sep 2004 A1
20040187864 Adams et al. Sep 2004 A1
20040193453 Butterfield et al. Sep 2004 A1
20040210199 Atterbury et al. Oct 2004 A1
20040254435 Mathews et al. Dec 2004 A1
20050010166 Hickle Jan 2005 A1
20050045734 Peng et al. Mar 2005 A1
20050059924 Katz et al. Mar 2005 A1
20050072421 Suman et al. Apr 2005 A1
20050081845 Barney et al. Apr 2005 A1
20050087189 Crockford et al. Apr 2005 A1
20050137626 Pastore et al. Jun 2005 A1
20050139651 Lim et al. Jun 2005 A1
20050155602 Lipp Jul 2005 A1
20050165342 Odland Jul 2005 A1
20050172956 Childers et al. Aug 2005 A1
20050172958 Singer et al. Aug 2005 A1
20050183725 Gumaste et al. Aug 2005 A1
20050203637 Edman et al. Sep 2005 A1
20050235732 Rush Oct 2005 A1
20050236501 Zimlich et al. Oct 2005 A1
20050245906 Makower et al. Nov 2005 A1
20050247312 Davies et al. Nov 2005 A1
20050251289 Bonney et al. Nov 2005 A1
20050274378 Bonney et al. Dec 2005 A1
20060005842 Rashad et al. Jan 2006 A1
20060030813 Chance Feb 2006 A1
20060031099 Vitello et al. Feb 2006 A1
20060037612 Herder et al. Feb 2006 A1
20060042632 Bishop et al. Mar 2006 A1
20060058593 Drinan et al. Mar 2006 A1
20060090752 Imondi et al. May 2006 A1
20060130832 Schechter et al. Jun 2006 A1
20060131350 Schechter et al. Jun 2006 A1
20060167530 Flaherty et al. Jul 2006 A1
20060178586 Dobak Aug 2006 A1
20060184087 Wariar et al. Aug 2006 A1
20060191534 Hickey et al. Aug 2006 A1
20060201499 Muellinger et al. Sep 2006 A1
20060204532 John et al. Sep 2006 A1
20060231093 Burge et al. Oct 2006 A1
20060243277 Denyer et al. Nov 2006 A1
20060253005 Drinan Nov 2006 A1
20060283465 Nickel Dec 2006 A1
20070023034 Jongejan et al. Feb 2007 A1
20070023036 Grychowski et al. Feb 2007 A1
20070043591 Meretei et al. Feb 2007 A1
20070044793 Kleinstreuer et al. Mar 2007 A1
20070060800 Drinan et al. Mar 2007 A1
20070074722 Giroux et al. Apr 2007 A1
20070088334 Hillis et al. Apr 2007 A1
20070091273 Sullivan et al. Apr 2007 A1
20070107517 Arnold et al. May 2007 A1
20070123829 Atterbury et al. May 2007 A1
20070125370 Denyer et al. Jun 2007 A1
20070157931 Parker et al. Jul 2007 A1
20070161879 Say et al. Jul 2007 A1
20070169778 Smith et al. Jul 2007 A1
20070197954 Keenan Aug 2007 A1
20070203411 Say et al. Aug 2007 A1
20070208322 Rantala et al. Sep 2007 A1
20070209659 Ivri et al. Sep 2007 A1
20070213658 Hickle Sep 2007 A1
20070221218 Warden et al. Sep 2007 A1
20070224128 Dennis et al. Sep 2007 A1
20070240712 Fleming et al. Oct 2007 A1
20070256688 Schuster et al. Nov 2007 A1
20070258894 Melker et al. Nov 2007 A1
20070295329 Lieberman et al. Dec 2007 A1
20070299550 Nishijima et al. Dec 2007 A1
20080009800 Nickel Jan 2008 A1
20080021379 Hickle Jan 2008 A1
20080039700 Drinan et al. Feb 2008 A1
20080051667 Goldreich Feb 2008 A1
20080058703 Subramony et al. Mar 2008 A1
20080077080 Hengstenberg et al. Mar 2008 A1
20080078382 LeMahieu et al. Apr 2008 A1
20080078385 Xiao et al. Apr 2008 A1
20080082001 Hatlestad et al. Apr 2008 A1
20080086112 Lo et al. Apr 2008 A1
20080091138 Pastore et al. Apr 2008 A1
20080114299 Damgaard-Sorensen et al. May 2008 A1
20080125759 Konieczynski et al. May 2008 A1
20080142002 Fink et al. Jun 2008 A1
20080147004 Mann et al. Jun 2008 A1
20080147050 Mann et al. Jun 2008 A1
20080173301 Deaton et al. Jul 2008 A1
20080177246 Sullican et al. Jul 2008 A1
20080178872 Genova et al. Jul 2008 A1
20080200804 Hartlep et al. Aug 2008 A1
20080216834 Easley et al. Sep 2008 A1
20080221408 Hoarau et al. Sep 2008 A1
20080262469 Brister et al. Oct 2008 A1
20080269689 Edwards et al. Oct 2008 A1
20080281276 Shekalim Nov 2008 A1
20080306436 Edwards et al. Dec 2008 A1
20080306444 Brister et al. Dec 2008 A1
20080306449 Kristensen et al. Dec 2008 A1
20090005763 Makower et al. Jan 2009 A1
20090024112 Edwards et al. Jan 2009 A1
20090025714 Denyer et al. Jan 2009 A1
20090025718 Denyer et al. Jan 2009 A1
20090048526 Aarts et al. Feb 2009 A1
20090048556 Durand Feb 2009 A1
20090056708 Stenzler Mar 2009 A1
20090064997 Li Mar 2009 A1
20090082829 Panken et al. Mar 2009 A1
20090107503 Baran Apr 2009 A1
20090151718 Hunter et al. Jun 2009 A1
20090156952 Hunter et al. Jun 2009 A1
20090163781 Say et al. Jun 2009 A1
20090187167 Sexton et al. Jul 2009 A1
20090194104 Van Sickle Aug 2009 A1
20090211576 Lehtonen et al. Aug 2009 A1
20090213373 Altobelli et al. Aug 2009 A1
20090216194 Elgard et al. Aug 2009 A1
20090221087 Martin et al. Sep 2009 A1
20090227941 Say et al. Sep 2009 A1
20090229607 Brunnberg et al. Sep 2009 A1
20090241951 Jafari et al. Oct 2009 A1
20090241955 Jafari et al. Oct 2009 A1
20090270752 Coifman Oct 2009 A1
20090301472 Kim et al. Dec 2009 A1
20090314372 Ruskewicz et al. Dec 2009 A1
20090326509 Muse et al. Dec 2009 A1
20090326510 Haefner et al. Dec 2009 A1
20100012120 Herder et al. Jan 2010 A1
20100031957 McIntosh Feb 2010 A1
20100049004 Edman et al. Feb 2010 A1
20100049172 Chance Feb 2010 A1
20100078015 Imran Apr 2010 A1
20100094099 Levy et al. Apr 2010 A1
20100099967 Say et al. Apr 2010 A1
20100100078 Say et al. Apr 2010 A1
20100100160 Edman et al. Apr 2010 A1
20100106098 Atterbury et al. Apr 2010 A1
20100114026 Karratt et al. May 2010 A1
20100114060 Ginngen et al. May 2010 A1
20100116070 Farina et al. May 2010 A1
20100121314 Iobbi May 2010 A1
20100122697 Przekwas et al. May 2010 A1
20100268111 Drinan et al. Oct 2010 A1
20110224912 Bhavaraju et al. Sep 2011 A1
20110230732 Edman et al. Sep 2011 A1
Foreign Referenced Citations (246)
Number Date Country
6296633 Oct 1994 JP
2001-061799 Mar 2001 JP
2008-525063 Jul 2008 JP
WO8102982 Oct 1981 WO
WO8607269 Dec 1986 WO
WO9207599 May 1992 WO
WO9209324 Jun 1992 WO
WO9211808 Jul 1992 WO
WO9215353 Sep 1992 WO
WO9217231 Oct 1992 WO
WO9306803 Apr 1993 WO
WO9312823 Jul 1993 WO
WO9405359 Mar 1994 WO
WO9408655 Apr 1994 WO
WO9416755 Aug 1994 WO
WO9416756 Aug 1994 WO
WO9416759 Aug 1994 WO
WO9427653 Dec 1994 WO
WO9507723 Mar 1995 WO
WO9507724 Mar 1995 WO
WO9513838 May 1995 WO
WO9526769 Oct 1995 WO
WO9610440 Apr 1996 WO
WO9616686 Jun 1996 WO
WO9625186 Aug 1996 WO
WO9625978 Aug 1996 WO
WO9627341 Sep 1996 WO
WO9630078 Oct 1996 WO
WO9707896 Mar 1997 WO
WO9711655 Apr 1997 WO
WO9711742 Apr 1997 WO
WO9711743 Apr 1997 WO
WO9726934 Jul 1997 WO
WO9733640 Sep 1997 WO
WO9733645 Sep 1997 WO
WO9748431 Dec 1997 WO
WO9800188 Jan 1998 WO
WO9801168 Jan 1998 WO
WO9806450 Feb 1998 WO
WO9814235 Apr 1998 WO
WO9832479 Jul 1998 WO
WO9839057 Sep 1998 WO
WO9844984 Oct 1998 WO
WO9850095 Nov 1998 WO
WO9900144 Jan 1999 WO
WO9930760 Jun 1999 WO
WO9965551 Dec 1999 WO
WO0001434 Jan 2000 WO
WO0007652 Feb 2000 WO
WO0018339 Apr 2000 WO
WO0021598 Apr 2000 WO
WO0027278 May 2000 WO
WO0032267 Jun 2000 WO
WO0038770 Jul 2000 WO
WO0043059 Jul 2000 WO
WO0047253 Aug 2000 WO
WO0050111 Aug 2000 WO
WO0053247 Sep 2000 WO
WO0059483 Oct 2000 WO
0105463 Jan 2001 WO
0105463 Jan 2001 WO
WO0113973 Mar 2001 WO
WO0124851 Apr 2001 WO
WO0130419 May 2001 WO
WO0158236 Aug 2001 WO
WO0168169 Sep 2001 WO
WO0183007 Nov 2001 WO
WO0185027 Nov 2001 WO
WO0187378 Nov 2001 WO
WO0189607 Nov 2001 WO
WO0200280 Jan 2002 WO
WO0202052 Jan 2002 WO
WO0204043 Jan 2002 WO
WO0217988 Mar 2002 WO
WO0217998 Mar 2002 WO
WO0224257 Mar 2002 WO
WO0224268 Mar 2002 WO
WO0234318 May 2002 WO
WO0236181 May 2002 WO
WO02053223 Jul 2002 WO
WO02072178 Sep 2002 WO
WO02076533 Oct 2002 WO
WO02078535 Oct 2002 WO
WO02081016 Oct 2002 WO
WO02089879 Nov 2002 WO
WO02089884 Nov 2002 WO
WO02096489 Dec 2002 WO
WO03006091 Jan 2003 WO
WO03008014 Jan 2003 WO
WO03020349 Mar 2003 WO
WO03022327 Mar 2003 WO
WO03028797 Apr 2003 WO
WO03035172 May 2003 WO
WO03038566 May 2003 WO
WO03045302 Jun 2003 WO
WO03059413 Jul 2003 WO
WO03071930 Sep 2003 WO
WO03073977 Sep 2003 WO
WO03086505 Oct 2003 WO
WO03090821 Nov 2003 WO
WO03097120 Nov 2003 WO
WO2004009161 Jan 2004 WO
WO2004011067 Feb 2004 WO
WO2004012801 Feb 2004 WO
WO2004020024 Mar 2004 WO
WO2004021882 Mar 2004 WO
WO2004022128 Mar 2004 WO
WO2004022153 Mar 2004 WO
WO2004022242 Mar 2004 WO
WO2004026380 Apr 2004 WO
WO2004032989 Apr 2004 WO
WO2004034998 Apr 2004 WO
WO 2004041334 May 2004 WO
WO 2004041339 May 2004 WO
WO 2004045690 Jun 2004 WO
WO 2004060436 Jul 2004 WO
WO 2004060443 Jul 2004 WO
WO 2004060447 Jul 2004 WO
WO 2004080522 Sep 2004 WO
WO 2004088567 Oct 2004 WO
WO 2005009514 Feb 2005 WO
WO 2005011779 Feb 2005 WO
WO 2005028008 Mar 2005 WO
WO 2005031317 Apr 2005 WO
WO 2005039750 May 2005 WO
WO 2005046559 May 2005 WO
WO 2005051177 Jun 2005 WO
WO 2005072798 Aug 2005 WO
WO 2005084275 Sep 2005 WO
WO 2005084738 Sep 2005 WO
WO 2005087299 Sep 2005 WO
WO 2005102412 Nov 2005 WO
WO 2005102417 Nov 2005 WO
WO 2005102418 Nov 2005 WO
WO 2005102428 Nov 2005 WO
WO 2005120615 Dec 2005 WO
WO 2005123002 Dec 2005 WO
WO 2006003665 Jan 2006 WO
WO 2006009596 Jan 2006 WO
WO 2006015299 Feb 2006 WO
2006029090 Mar 2006 WO
2006029090 Mar 2006 WO
WO 2006022714 Mar 2006 WO
WO 2006023644 Mar 2006 WO
WO 2006035443 Apr 2006 WO
WO 2006044206 Apr 2006 WO
WO 2006045524 May 2006 WO
2006069323 Jun 2006 WO
2006069323 Jun 2006 WO
WO 2006058426 Jun 2006 WO
WO 2006060106 Jun 2006 WO
WO 2006079898 Aug 2006 WO
WO 2006096286 Sep 2006 WO
WO 2006098933 Sep 2006 WO
WO2006098936 Sep 2006 WO
WO2006113408 Oct 2006 WO
2006116718 Nov 2006 WO
2006116718 Nov 2006 WO
WO2006120253 Nov 2006 WO
WO2006124759 Nov 2006 WO
WO2006125577 Nov 2006 WO
WO2006127257 Nov 2006 WO
WO2006127905 Nov 2006 WO
WO2006127953 Nov 2006 WO
WO2006128794 Dec 2006 WO
WO2006130098 Dec 2006 WO
WO2006133101 Dec 2006 WO
WO2007012854 Feb 2007 WO
2007028035 Mar 2007 WO
2007028035 Mar 2007 WO
WO2007031740 Mar 2007 WO
WO2007034237 Mar 2007 WO
WO2007041158 Apr 2007 WO
WO2007041471 Apr 2007 WO
WO2007051563 May 2007 WO
WO2007070093 Jun 2007 WO
WO2007070695 Jun 2007 WO
2007120884 Oct 2007 WO
2007120884 Oct 2007 WO
WO2007125699 Nov 2007 WO
WO2007127981 Nov 2007 WO
WO2007131025 Nov 2007 WO
2008008281 Jan 2008 WO
WO2008008281 Jan 2008 WO
WO2008016698 Feb 2008 WO
WO2008021252 Feb 2008 WO
WO2008022010 Feb 2008 WO
WO2008029403 Mar 2008 WO
WO2008030837 Mar 2008 WO
WO2008037801 Apr 2008 WO
WO2008038241 Apr 2008 WO
WO2008039091 Apr 2008 WO
WO2008043724 Apr 2008 WO
WO2008052039 May 2008 WO
WO2008073806 Jun 2008 WO
WO2008077706 Jul 2008 WO
WO2008078287 Jul 2008 WO
2008095183 Aug 2008 WO
2008095183 Aug 2008 WO
WO2008103620 Aug 2008 WO
WO2008115906 Sep 2008 WO
WO2008117226 Oct 2008 WO
WO2008127743 Oct 2008 WO
WO2008130801 Oct 2008 WO
WO2008134107 Nov 2008 WO
WO2008134545 Nov 2008 WO
WO2008152588 Dec 2008 WO
WO2008154312 Dec 2008 WO
WO2008154504 Dec 2008 WO
WO2009003989 Jan 2009 WO
WO2009008001 Jan 2009 WO
WO2009013501 Jan 2009 WO
WO2009013670 Jan 2009 WO
WO2009023247 Feb 2009 WO
WO2009035759 Mar 2009 WO
WO2009042379 Apr 2009 WO
WO2009049252 Apr 2009 WO
WO2009063421 May 2009 WO
WO2009072079 Jun 2009 WO
WO2009076363 Jun 2009 WO
WO2009079589 Jun 2009 WO
WO2009081262 Jul 2009 WO
WO2009091851 Jul 2009 WO
WO2009098648 Aug 2009 WO
WO2009105337 Aug 2009 WO
WO2009126653 Oct 2009 WO
WO2009137661 Nov 2009 WO
WO2009140251 Nov 2009 WO
WO2009145801 Dec 2009 WO
WO2009155335 Dec 2009 WO
WO2010007573 Jan 2010 WO
WO2010007574 Jan 2010 WO
WO2010008424 Jan 2010 WO
WO2010010473 Jan 2010 WO
WO2010021589 Feb 2010 WO
WO2010023591 Mar 2010 WO
WO2010025428 Mar 2010 WO
WO2010025431 Mar 2010 WO
WO2010029054 Mar 2010 WO
WO2010037828 Apr 2010 WO
WO2010042034 Apr 2010 WO
WO2010043054 Apr 2010 WO
WO2010045460 Apr 2010 WO
WO2010051551 May 2010 WO
WO2010052275 May 2010 WO
WO2010062675 Jun 2010 WO
Non-Patent Literature Citations (11)
Entry
Nikander et al., “The Adaptive Delivery System in a Telehealth Setting: Patient Acceptance, Performance and Feasibility” Journal of Aerosol Medicine and Pulmonary Drug Delivery; vol. 23, Supp. 1, (2010) pp. S21-S27.
AADE, “AADE 37th Annual Meeting San Antonio Aug. 4-7, 2010” American Association of Diabetes Educators (2010); http://www.diabeteseducator.org/annualmeeting/2010/index.html; 2 pp.
Juvenile Diabetes Research Foundation International (JDRF), “Artificial Pancreas Project” (2010); http://www.artificialpancreasproject.com/; 3 pp.
Lifescan, “OneTouch UltraLink™”http://www.lifescan.com/products/meters/ultralink (N.D.) 2 pp.
Medtronic, “CareLink Therapy Management Software for Diabetes” (2010); https://carelink.minimed.com/patient/entry.jsp?bhcp=1; 1 pp.
Medtronic, “Carelink™ USB” (n.d.) http://www.medtronicdiabetes.com/pdf/carelink—usb—factsheet.pdf 2pp.
Medtronic “The New MiniMed Paradigm® REAL-Time Revel™ System” http://www.medtronicdiabetes.com/products/index.html; 2 pp.
Medtronic, “Mini Med Paradigm® Revel™ Insulin Pump” (n.d.) http://www.medtronicdiabetes.com/products/insulinpumps/index.html; 2 pp.
Medtronic, Mini Med Paradigm™ Veo™ System: Factsheet (2010). http://www.medtronic-diabetes.com.au/downloads/Paradigm%20Veo%20Factsheet.pdf ; 4 pp.
Park, “Medtronic to Buy MiniMed for $3.7 Billion” (2001) HomeCare; http://homecaremag.com/mag/ medical—medtronic—buy—minimed/; 2 pp.
Prutchi et al., “Design and Development of Medical Electronic Instrumentation: A Practical Perspective of the Design, Construction, and Test of Medical Devices” Wiley-Interscience (2005) pp. 12-14.
Related Publications (1)
Number Date Country
20090112178 A1 Apr 2009 US
Provisional Applications (1)
Number Date Country
60982661 Oct 2007 US