Medication dose preparation and transfer system

Information

  • Patent Grant
  • 11464708
  • Patent Number
    11,464,708
  • Date Filed
    Monday, July 15, 2019
    4 years ago
  • Date Issued
    Tuesday, October 11, 2022
    a year ago
Abstract
Apparatus, systems, methods and articles are described to prepare and track medications and medication containers as they are prepared, administered to patients and, in some cases, disposed of. Information such as medication type, concentration, and volume are associated with medication containers during preparation and this information can later be consumed/utilized when administering the medication from a container to a patient. Disposing of any remaining medication can also be tracked.
Description
FIELD OF THE INVENTION

The subject matter described herein relates to a medication dose preparation and transfer apparatus used for identifying medication within a medication container, measuring an amount of medication withdrawn from the medication container and transferred to a secondary container (e.g. syringe), tracking the amount of medication actually administered to a patient and tracking the amount of any residual medication disposed of as waste.


BACKGROUND OF THE INVENTION

There are a number of patient clinical settings including in-hospital, outpatient and emergency medical services (EMS) that require transfer of medications from original pharmaceutical manufacturer's primary containers to secondary containers to facilitate caregiver administration to patients. When medications are transferred to secondary containers it is standard clinical best practice to label them to reduce the potential for medication errors. However, due to dose measurement mistakes, incorrect transfer of labeling information and other factors, errors continue to occur when caregivers transfer medications from primary containers (vials to syringes) or prepare partial doses (empty syringe withdraws of a partial amount from a primary vial).


SUMMARY OF THE INVENTION

In one aspect, an apparatus for transferring medication from a primary medication container to a manually injectable secondary medication container is provided. The apparatus includes a fluid channel, a primary medication container coupling, a secondary medication coupling, at least one identification sensor and a communications module. The fluid channel terminates at a primary medication container port on a first end and a secondary medication container port on a second end. The primary medication container coupling is configured to fluidically couple the primary medication container to the primary medication container port. The secondary medication container coupling is configured to fluidically couple the secondary medication container to the secondary medication container port. The at least one identification sensor senses (i) an information transfer element on the primary medication container and (ii) an information transfer element on the secondary medication container with the information transfer element on the primary container being used to characterize the medication. The communications module transmits data obtained by and/or derived from the at least one identification sensor to a remote computing system to associate the medication in the primary medication container as having been transferred to the secondary medication container.


The primary medication container coupling can include a spike to penetrate a barrier of the primary medication container. The secondary medication container coupling can include a female luer fitting to mate with a male luer fitting of the secondary medication container. The primary medication container can be vial with a vial adapter having the information transfer element disposed thereon.


The secondary medication container can be a syringe with the information transfer element disposed upon an encoded hub attached to a fluid outlet of the syringe (which in turn is configured to fluidically couple with the secondary medication container port). The communications module can wirelessly transmit data to and/or receive data from the remote computing system.


A first identification sensor can sense the information transfer element of a primary medication container and a second identification sensor can sense the information transfer element of the secondary medication container. The information transfer element on at least one of the primary medication container and the secondary medication container can include or be a unique identifier such as a serial number.


The at least one flow sensor can characterize an amount of medication passing through the fluid channel such that the communications module transmits data indicating same. In some implementations, the at least one flow sensor can be a bi-directional flow sensor measuring fluid flow in two opposing directions and the data transmitted can separately characterize fluid flow in both opposing directions.


Memory can be included that stores data such as data obtained from the at least one identification sensor and/or the at least one flow sensor. At least one data processor (e.g., a CPU/microprocessor, etc.) can process data stored in the memory.


A user indicator (e.g., an interface, display, etc.) can be provided that provides visual and/or audio feedback to a user. The indicator can be interactive allowing the user to change one or more operating parameters (e.g., alarm override, enter patient information and the like). The user indicator can display a wide range of information, including but not limited to: medication name, medication category, recommended dosage, secondary medication container fill volume, medication waste volume, secondary medication container identifier, and partial dosage volume.


In some implementations, the entire apparatus can be disposable. In other implementations, only a portion of the apparatus is disposable (with the remaining portion being reusable). With this latter arrangement, the fluid channel can be selectively removable to avoid medication cross-contamination and/or sterility issues. With a removable fluid channel, there can be memory within or otherwise coupled to the removable fluid channel. Such memory can have and/or store a unique identifier (e.g., serial number, etc.).


The remote computing system can be, for example, one or more of medication management devices and systems, electronic medical records systems, pharmacy management and fulfillment systems, medication storage systems, medication dispensing stations, and medication waste disposal systems.


The fluid channel can undertake a variety of geometries. It can be linear, at least partially curved, and angled. With the latter, the fluid channel can have at least one 90 degree angle, and in one implementation, it can have at least two 90 degree angles.


The fluid channel can terminate at a patient outlet which can, for example, lead to an IV line for a patient. The fluid channel can include a first sub-channel connecting the primary medication container port with the patient outlet and a second sub-channel extending at an angle from the first sub-channel terminating on one end at the first sub-channel and on a second end at the secondary medication container port. A bi-directional flow sensor can measure the flow of medication in both directions within the second sub-channel as it is transferred to the secondary medication container and as it is expelled from the secondary medication container. With such an arrangement, the communications module can transmit data characterizing the medication flow detected by the bi-direction sensor.


At least one check valve can be incorporated to prevent the medication expelled from the secondary medication container from flowing towards the primary medication container port and/or to prevent medication extracted from the primary medication container from flowing back towards the primary medication container port. Removable channel caps can be employed that are secured to the primary medication container port and the secondary medication container port.


A housing can be provided through which the fluid channel traverses. Such housing can have a size and shape to allow a user to hold the housing and a primary medication container in a first hand and to operate the manually injectable secondary medication container using a second hand.


The fluid channel can include a primary fluid channel terminating at two sub-channels. The two sub-channels can be at an angle in relation to the primary fluid channel and being parallel in relation to each other, the sub-channels respectively terminating in the primary medication container port and the secondary medication container port.


A display can be displayed on a housing (i.e., an outer surface of a housing) that envelopes the fluid channel. The communications module can receive data from at least one computing system characterizing the medication, at least a portion of the received data being displayed on the display. It will be appreciated that the communications module can transmit data to a first computing system while receiving data from a second computing system. At least a portion of the information being displayed can include one or more of: information about the fluid transfer process, user guidance, information about the dose to be administered, information about the dose administered to a patient, and patient specific medication administration guidelines or restrictions. The received data can include one or more of: medication delivery order data, patient-specific identifiers, general or medication-specific dosing limits, data for contraindication checking, Broselow color/classification, patient drug allergies, patient weight, medication data, patient specific data, procedural cautionary data, error prevention data, dose time data, physician instructions, drug manufacturer instructions, precautions associated with the medication, and contraindications associated with the medication.


The at least one identification sensor can detect the information transfer element using one or more technologies such as optical, magnetic, mechanical, conductive, capacitive, inductive, proximity sensors, infrared, and switchable RFID.


In an interrelated aspect, an apparatus for transferring medication from a primary medication container to a manually injectable secondary medication container includes a fluid channel, a primary medication container, a secondary medication container, at least one fluid flow sensor, and a communications module. The fluid channel terminates at a primary medication container port on a first end and a secondary medication container port on a second end. The primary medication container coupling is configured to fluidically couple the primary medication container to the primary medication container port. The secondary medication container coupling is configured to fluidically couple the secondary medication container to the secondary medication container port. The at least one flow sensor to sense medications flowing through the fluid channel. The communications module transmits data obtained by and/or derived from the at least one flow sensor to a remote computing system and, in some implementations, receives data from one or more remote computing systems associated with the medication and/or the patient.


Systems can be provided that additionally include a dose preparation and transfer apparatus and one or more of a primary medication container and manually injectable secondary medication container. Kits can be provided that include dose preparation and transfer apparatus as well as one or more of a primary medication container and a manually injectable container.


In a further interrelated aspect, a dose preparation and transfer apparatus detects a medication identification code (information transfer element) on a primary medication container, detects an identifier (information transfer element) of a secondary medication container, and transmits data to a remote computing system that characterizes the detected medication identification code and the detected identifier. In some implementations, the dose preparation and transfer apparatus further detects an amount of medication transferred from the primary container to the secondary container and data characterizing same is transmitted to the remote computing system.


Apparatus, systems, methods and articles are described to prepare and track medication containers as they are prepared, administered to patients and, in some cases, disposed of. Information such as medication type, concentration, and volume are associated with medication containers during preparation and this information can later be consumed/utilized when administering the medication from a container to a patient. Disposing of any remaining medication can also be tracked (which can be advantageous in connection with controlled substances). In some examples, medication is transferred from a container such as a vial into a syringe and data characterizing the medication is associated with the syringe (e.g., a bar code, a record in a look-up table, etc.). The medication in this syringe can then be injected into a patient via, for example, a medication injection site which can automatically identify the medication container and/or its contents. Any remaining contents of this syringe can be injected into a waste disposal system which can also automatically identify the medication container and/or its contents (and log the container and amount of disposed medication disposed).





BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, show certain aspects of the subject matter disclosed herein and, together with the description, help explain some of the principles associated with the disclosed embodiments. In the drawings:



FIG. 1 is a diagram illustrating a medication dose preparation and transfer system;



FIG. 2 is a diagram describing a detailed view of a medication dose preparation and transfer system as in FIG. 1;



FIG. 3 is a diagram describing a detailed view of a second medication dose preparation and transfer system as in FIG. 1;



FIG. 4 is a diagram describing a detailed view of a third medication dose preparation and transfer system as in FIG. 1;



FIG. 5 is a diagram describing a detailed view of a fourth medication dose preparation and transfer system as in FIG. 1;



FIG. 6 is a diagram describing the assembly of a medication dose preparation and transfer apparatus with medication containers as in FIG. 3;



FIG. 7 is a diagram describing a detailed view of a fifth medication dose preparation and transfer system as in FIG. 1;



FIG. 8 is a diagram describing the assembly of a medication dose preparation and transfer apparatus with medication containers as in FIG. 7;



FIG. 9 depicts the basic steps taken in the use of a medication dose preparation and transfer system as in FIG. 3;



FIG. 10 is a diagram illustrating a medication dose preparation and transfer apparatus as in FIG. 3 with a display;



FIG. 11 is a diagram illustrating a second medication dose preparation and transfer apparatus as in FIG. 3 with a display;



FIG. 12 is a diagram showing the sequence of operation for the device in FIG. 11;



FIG. 13 is a diagram describing a detailed view of a sixth medication dose preparation and transfer system as in FIG. 1;



FIG. 14 is a diagram describing a detailed view of a seventh medication dose preparation and transfer system as in FIG. 1;





Like reference symbols in the various drawings indicate like or similar elements.


DETAILED DESCRIPTION


FIG. 1 is a diagram illustrating a medication dose preparation and transfer system 2. System 2 comprises primary medication container 4, secondary medication container 6, dose preparation and transfer apparatus 8 and interconnecting dose transfer fluid channel 10. Fluid channel 10 can include spike 14 for connection to primary medication container 4 and female luer fitting 15 for connection to secondary container 6. Following attachment of container 4 and container 6, fluid from container 4 can be transferred to container 6 through dose transfer channel 10. Information 18 about containers 4 and 6 and the medication transferred through fluid channel 10 can be transmitted (via, for example, a communications module) to recordkeeping system 30 (which may be coupled wirelessly, via a hard-wired communications network, or a combination of both). Recordkeeping system 30 (including healthcare information computing systems) can include one or more of: medication management devices and systems, electronic patient medical records, medication administration records, pharmacy records, medication storage station inventory records, records accounting for the disposal of medication wastes, and the like.


A healthcare provider can select vial 4 from an array of available vials and transfer the medication and medication information to a patient's medication injection site for administration. Examples of medication injection sites and related data collection systems are described in U.S. patent applications Ser. Nos. 12/614,276, 12/765,707 and 12/938,300 all entitled “Medication Injection Site and Data Collection System,” the contents of which are hereby fully incorporated by reference.


Medication container 4 and secondary container 6 can be joined by a dose preparation and transfer apparatus 8 to form medication dose preparation and transfer system 2. Housing 12 can contain hardware, software and mechanical elements for characterizing the transferred medication (e.g., identify and measure amount of transferred medication, determine transfer time, etc.). A dose transfer fluid channel 10 can connect each container (4 and 6) forming a transfer pathway. Fluid channel 10 can be integrated within housing 12 or be separate. When separate, housing 12 is reusable and can be used with many fluid channels 10 that can be made sterile and disposable for single patient use. Disposable flow channel 10 can be sterilized and be part of a kit including a sterile pouch enveloping the disposable sub-housing. Housing 12 and/or fluid channel 10 can be assigned serial numbers for identification which can be read by or received from recordkeeping system 30. One end of fluid channel 10 can have spike 14 to puncture medication container 4 to access the medication for transfer to secondary container (e.g. syringe) 6. The other end of fluid channel 10 can be a female luer type fitting 15 to accept a male luer fitting on secondary container 6.


The dose preparation and transfer apparatus 8 allows a desired amount of medication in vial 4 to be transferred to a syringe 12 through fluid channel 10. Syringe 6 can initially be provided empty, or in the case of a medication mixture or dilution, can contain an existing volume of fluid. Syringe 6 can be attached to the medication dose preparation and transfer device to withdraw the medication from vial 4. Primary medication container 4's contents can be identified using an information transfer element ID Code 102 (medication name, manufacturer name, drug concentration, NDC code, volume contained, serial number, and other drug or patient specific information) on or associated with primary medication container 4. Secondary medication container 6 can be identified using an information transfer element (ID Code 106). These ID Codes will be described below.



FIG. 2 is a diagram describing a detailed view of a medication dose preparation and transfer system 2 as in FIG. 1. At the top of the figure, primary medication container (vial) 4 contains medication 20. At the bottom of vial 4 the open end can be closed by rubber closure and protected by flip off cap. Vial 4 can carry an information source (e.g., medication ID code 102) that provides detectable information indicative of the medication in primary container 4 and/or of the volume of the contents. Primary medication container (Vial) 4 as used herein refers to both vials and other medication containers such as pre-filled syringes and/or bags (except when explicitly disclaimed). It can be appreciated that many configurations of vial 4 can be manufactured and can function in system 2.


At the bottom of the figure, secondary container 6 can be a syringe with a syringe body, male luer fitting tip, plunger and plunger rod. It can be appreciated that many configurations of secondary container 12 can be manufactured and can function in system 2.



FIG. 2 further illustrates a medication dose preparation and transfer system 2 that comprises medication container adapter (vial adapter) 16 joined with information transfer element (ID Code 102). Vial adapter 16 can be a sterilizable plastic material and can comprise vial spike, spike cover, vial clips, a flow channel and a female luer fitting. It can be appreciated that many configurations of vial adapter 16 can be manufactured and can function in system 2 (provided that the vial adapter can create a sterile fluid pathway between the vial contents and the dose transfer fluid channel 10). Examples of vial adapter devices are described in U.S. patent application Ser. No. 13/282,255 entitled “Medication and Identification Information Transfer Apparatus”, the contents of which is hereby fully incorporated by reference.


The vial adapter 16 can be a sterilizable injection molded plastic material consisting of element body, fluid inlet, fluid outlet, flow channel and ID Code 102.


ID Code 102 can be one or more of an optical source, a magnetic source, a mechanical source, a switchable RFID source, a conductive source, and/or a proximity source. One implementation can provide information encoded within the information element in the form of an optically detectable surface, reflective or absorbing light surface, and can be embedded into or on top of element body.


Alternatively, information provided by ID Code 102 can be a magnetically detectable strip similar to a credit card magnetic strip, facilitating a magnetic scan similar to credit card swiping, that is embedded into or on top of the information element body.


Further and alternatively, information provided by the information element can be a mechanically detectable feature consisting of Braille like features of bumps or ridges or valleys on the surface of or at the end of element body, facilitating mechanical detection by a micro switch or similar physical detection method.


Further and alternatively, information provided by information element can be an RFID tag located on the surface of element body, facilitating detection by an RFID reader. The antenna of the RFID tag can be switchable and can be OPEN prior to connection to the medication dose preparation and transfer apparatus 8. Upon connection to the dose preparation and transfer apparatus 8, the antenna can become CLOSED (or connected) facilitating RFID reader detection. When the container is disconnected from the dose preparation and transfer apparatus, the RFID tag antenna can again become OPEN.


Further and alternatively, information provided by information transfer element ID Code 102 can be in the form of a capacitive or inductive proximity feature on the surface of or embedded into element body, facilitating capacitive or inductive proximity detection.


The information element can be an integrated feature of the information transfer element such as etched or molded features. The information element can alternatively be adhered or deposited to the element body (i.e., information element can be a label, etc.) or embedded therein. In addition, the information element can be a separate element that extends around fluid outlet 54.


The encapsulated data within ID Code 102 can be formatted using an industry standard representation of the medication being characterized or a proprietary representation of the medication being characterized. The data can include one or more of: an NDC code (National Drug Code), a segment of the NDC code identifying the drug product, a segment of the NDC code identifying the drug package, a unique identifier code, a human readable alphanumeric, a machine readable code, a name of the medication, a manufacturer of the medication, a re-packager of the medication, a distributor of the medication, a strength of the medication, a dosage form of the medication, dose instructions for the medication, administration instructions for a specific patient, medication formulation, medication package form, medication package size, medication contained volume, medication package serial number, medication lot number, and medication expiration date. The encapsulated data can additionally or alternatively also include such information.


The ID Code 102 can be applied by any number of operations or steps in the medication supply chain prior to medication administration to a patient including, but not limited to: the original medication manufacturer, a pharmaceutical re-packager, a hospital pharmacy, a compounding pharmacy service, a healthcare professional or caregiver, a patient.


Secondary container 6 can be encoded with ID Code 106 to identify the container. ID Code 106 can be a unique number, code, symbol, serial number, random number, or other information describing a specific unique secondary container 6. A medication dose can be transferred from primary container 4 through fluid channel 10 into secondary container 6 by pulling on the plunger rod of syringe 6 and drawing medication dose 22 into it.


The ID Code 106 can be applied by any number of operations or steps in the supply chain of secondary container 6 prior to medication transfer including, but not limited to: the original secondary container manufacturer, a pharmaceutical re-packager, a compounding pharmacy service, a hospital pharmacy, a healthcare professional or caregiver, a patient. ID Code 106 can be one or more of an optical source, a magnetic source, a mechanical source, a switchable RFID source, a conductive source, and/or a proximity source. One implementation can provide information encoded within the information element in the form of an optically detectable surface, reflective or absorbing light surface, and can be embedded into or on top of the element body.


Alternatively, information provided by ID Code 106 can be a magnetically detectable strip similar to a credit card magnetic strip, facilitating a magnetic scan similar to credit card swiping, that is embedded into or on top of the information element body.


Further and alternatively, information provided by the information element can be a mechanically detectable feature consisting of Braille like features of bumps or ridges or valleys on the surface of or at the end of element body, facilitating mechanical detection by a micro switch or similar physical detection method.


Further and alternatively, information provided by ID Code 106's information element can be an RFID tag located on the surface of element body, facilitating detection by an RFID reader. The antenna of the RFID tag can be switchable and would be OPEN prior to connection to the medication dose preparation and transfer apparatus 8. Upon connection to the medication dose preparation and transfer apparatus 8, the antenna can become CLOSED (or connected) facilitating RFID reader detection. When the container is disconnected from the dose preparation and transfer apparatus, the RFID tag antenna can again become OPEN.


Further and alternatively, information provided by ID Code 106's information element can be in the form of a capacitive or inductive proximity feature on the surface of or embedded into element body, facilitating capacitive or inductive proximity detection.


ID Code 106's information element can be an integrated feature of the information transfer element such as etched or molded features. The information element can alternatively be adhered or deposited to the element body (i.e., information element can be a label, etc.) or embedded therein. In addition, the information element can be a separate element that extends around fluid outlet. Further, ID Code 106 can be part of an extension or a similar vial adapter adapter 16 that can attach to the fluid outlet of secondary container 6 in a way that once connected becomes permanently or semi-permanently affixed.


Dose preparation and transfer apparatus 8 can have housing 12 that encloses a power source 115, hardware and software elements 110 and 114. Within apparatus 8 are dose transfer fluid channel 10 (either built-in or separately clipped-in), medication container emitter/detector 104 to detect and transfer ID Code 102 to microprocessor/memory 114, secondary container emitter/detector 108 to detect and transfer ID Code 106 to microprocessor/memory 114 (e.g., a data processor, etc.), volume/flow transducer 118 to monitor and measure fluid transfer, a user indicator 116 can be provided to indicate various steps in the process and provide feedback to the user. Other user indicators can include a display which will be discussed later.


When dose transfer fluid channel 10 is separate from dose preparation transfer apparatus 8, fluid channel 10 can be clipped-in in any number of ways to facilitate mating with apparatus 8 for the connection of volume/flow transducer 118 to monitor and measure fluid transfer including, but not limited to: snap fit of fluid channel 10 into a cavity within housing 12, snap fit of fluid channel 10 onto the outside of housing 12, an electrical connector, an inductive connector, an optical connection, etc.


Alternately, the separate fluid channel 10 can include volume/flow transducer 118 and/or a memory element 119. The memory element 119 can include any one of calibration data, serial number or other unique information.


Dose preparation transfer apparatus 8 can also contain a communications module (sometimes referred to as a wireless radio) 110 for transmission of information 18 to a remote recordkeeping system 30. Recordkeeping system 30 will be discussed later and can be a remote computing system. Information 18 can be bi-directional and can include transfer of data from recordkeeping system 30 (including a medication management system or a healthcare information system) to dose preparation and transfer apparatus 8. Information that can be transferred from record keeping system 30 to dose transfer apparatus 8 includes but is not limited to medication delivery order data, patient-specific identifiers, general or medication-specific dosing limits, data for contraindication checking, Broselow color/classification, patient drug allergies, patient weight, or other information relevant for ensuring the medication being transferred is the right medication and that the resultant dose transferred to secondary container 6 is correct for the intended patient use.



FIG. 3 is a diagram describing a detailed view of a second medication dose preparation and transfer system as in FIG. 1. In this variation, medication ID Code 102 can be placed on the closure rim of the primary medication container 4. No vial adapter 16 is needed. Here, medication container emitter/detector 104 can directly identify medication ID Code 102 from primary medication container (vial) 4. The other features and functions of dose preparation and transfer apparatus 8 described in FIG. 2 can be the same.



FIG. 4 is a diagram describing a detailed view of a third medication dose preparation and transfer system as in FIG. 1. In this variation, medication ID Code 102 is placed on the outlet of a prefilled syringe 4. Here, medication container emitter/detector 104 can directly identify medication ID Code 102 from primary medication container 4 (syringe). The other features and functions of dose preparation and transfer apparatus 8 described in FIG. 2 can be the same.



FIG. 5 is a diagram describing a detailed view of a fourth medication dose preparation and transfer system as in FIG. 1. In this implementation, medication ID Code 102 can be placed on the closure rim of primary medication container 4 and secondary container (syringe) 6 and located at right angle (or any angle convenient to facilitate use) to the fluid transfer channel 10. Here, medication container emitter/detector 104 can directly identify medication ID Code 102 from primary medication container 4 (vial). Secondary container emitter/detector 108 can identify ID Code 106. Additionally dose transfer fluid channel 10 can form a “T” (or other angled junction).


A single direction set of check valves 120 can be located at the junction to control flow through channel 10. When a plunger rod of the secondary container (syringe) 6 is pulled (withdrawn), fluid is removed from primary medication container 4 and passes into syringe 6. The upstream check valve allows flow to the secondary container 6 and the downstream check valve prevents backflow (or air) from the patient outlet 122. Here, a volume/flow bi-directional sensor 118 can measure fluid transfer into the secondary container 6 from vial 4. The secondary container 6 can be removed for administration to a patient as in FIG. 3. Alternately, the entire dose preparation and transfer apparatus 8 can be attached to a patient's administration injection port (not shown). In this variation, fluid outlet 122 is attached to the injection port and medication dose 22 is injected by pushing on the syringe plunger rod. Check valves 120 direct flow to the patient. The upstream check valve prevents flow back into primary container 4 and the downstream check valve allows fluid flow to the patient. The other features and functions of dose preparation and transfer apparatus 8 described in FIG. 2 are the same.



FIG. 6 is a diagram describing the assembly of a medication dose preparation and transfer apparatus with medication containers as in FIG. 1. Primary medication container 4 and secondary medication container 6 can be prepared for use by removing their respective protective caps 22 and 24. Dose fluid transfer channel 10 can be prepared by removing channel cap 26 and spike cap 28. These caps protect the containers and fluid transfer channel 10 when they are provided sterile (fluid path is sterile). Dose preparation apparatus 8 may be held in a first hand and medication container 4 (vial) is held in a second hand. Fluid channel 10's fluid inlet spike 14 can be inserted through a sterile closure stopper in the vial. Secondly, secondary container 6 can be attached to the fluid channel outlet female lure fitting 15 (this can be a slip luer or luer lock type fitting).



FIG. 7 is a diagram describing a detailed view of a fifth medication dose preparation and transfer system 2 as in FIG. 1. In this implementation dose transfer fluid channel 10 can be “U” shaped. This can provide for an alternate user configuration where both primary container 4 and secondary container 6 are on the same side of dose preparation apparatus 8. Medication ID Code 102 is placed on the closure rim of the primary medication container 4. Medication container emitter/detector 104 directly identifies medication ID Code 102 from primary medication container (vial) 4. Alternately, fluid transfer channel 10 can be “L” shaped, “J” shaped or otherwise shaped to facilitate use. The other features and functions of dose preparation and transfer apparatus 8 described in FIG. 2 can be the same.



FIG. 8 is a diagram illustrating the assembly of a medication dose preparation and transfer apparatus with medication containers as in FIG. 7. Primary medication container 4 and secondary medication container 6 can be prepared for use by removing their respective protective caps 22 and 24. Dose fluid transfer channel 10 can be prepared by removing channel cap 26 and spike cap 28. These caps protect the containers and fluid transfer channel 10 when they are provided sterile (fluid path is sterile). Dose preparation apparatus 8 may be held in a first hand and medication container 4 (vial) is held in a second hand. Fluid channel 10's fluid inlet spike 14 can be inserted through a sterile closure stopper in the vial. Secondly, secondary container 6 can be attached to the fluid channel outlet female lure fitting 15. The other steps of dose preparation and transfer apparatus 8 described in FIG. 6 can be the same.



FIG. 9 depicts steps that can be taken in the use of a medication dose preparation and transfer system as in FIG. 3.


Step 1: Containers 4 and 6 are prepared for use by removing their protective caps 22 and 24. The dose fluid transfer channel is prepared by removing its caps 26 and 28. Primary container 4 is spiked with the inlet of fluid channel 10 and secondary container 6 is attached to the outlet of fluid channel 10.


Step 2: Connection of containers 4 and 6 allow emitter/detectors 104 and 108 to identify and decode ID Codes 102 and 106 respectively. Information 18 is transmitted to recordkeeping system 30. The two ID Codes can be associated with one another in the recordkeeping system 30, along with an amount of medication transferred between the containers and the volume in each medication container following the transfer. Alternatively, ID Codes 102 and 106 can be associated with one another in dose preparation apparatus 8. The assembled dose preparation and transfer apparatus is inverted allowing withdrawal of medication from vial 4.


Step 3: Medication is withdrawn from container 4 into container 6 by pulling on the plunger rod of the syringe container (6). Volume/flow sensor 118 measures the transferred medication and the dose preparation and transfer apparatus 8 transmits information 19 (volume/flow information) to recordkeeping system 30. The transferred medication dose volume information 19 is associated with ID Code 106 on secondary container 6. The remaining medication in primary container 4 is associated with ID Code 102.


Step 4: Secondary container 6 is detached from fluid channel 10 and protective caps 24 and 26 can be replaced to maintain sterility protection. Syringe 6 is then taken to a patient for dose administration. Alternately, vial 4 and vial spike 14 can be detached from fluid channel 10 and syringe 6 with fluid channel 10 still attached can be used to administer medication to a patient (not shown).


Step 5: A caregiver can then administer the dose from syringe 6 to a patient by attaching it to medication injection port 200 on a fluid administration tubing set. When attached, ID Code 106 is identified by injection port 200 and that information 21 transmitted to recordkeeping system 30. Recordkeeping system 30 associates the injection with the medication withdrawn in Step 3 and medication type and concentration information (ID Code 102) identified in Step 2. The volume of the dose can be measured by injection port 200 and that information 21 can also be transmitted to recordkeeping system 30 for recording in a patient's medication administration record. Information 21 transmitted to recordkeeping system 30 can be integrated or associated with additional information stored within or accessible by recordkeeping systems 30 and utilized to create paper reports and/or electronic records associated with the medication delivery.


The features and functions of medication injection port 200 are described in a medication injection site/medication administration device detailed in the U.S. patent application Ser. Nos. 12/614,276, 12/765,707, and 12/938,300 all entitled “MEDICATION INJECTION SITE AND DATA COLLECTION SYSTEM”. Features and functions of a sample vial adapter and encoded fluid transfer element are detailed in U.S. patent application Ser. No. 12/768,509 entitled “MEDICATION AND IDENTIFICATION INFORMATION TRANSFER APPARATUS”. The contents of each of the aforementioned applications are hereby fully incorporated by reference. Other medication containers and/or vial adapters and fluid transfer elements may be implemented with this medication dose preparation and transfer system 2. Record keeping system 30 can account for and track medication transfers and administrations to patients in a medication dose history for each patient. Additionally, remaining medication in vial 4 or syringe 6 can be tracked, accounted for and associated with waste disposal. The withdrawn transfer medication volume can be subtracted from the original medication volume in syringe 6 to determine the remaining medication volume. Similarly, the residual medication volume in syringe 6 after dosing and be determined by subtracting the volume of medication delivered to the patient from the total volume of medication that was transferred from vial 4 to syringe 6. The disposed of medication can be tracked by a waste disposal system. For example, a medication wasting device can be configured to receive a syringe 6 containing a controlled substance and bearing an information transfer element ID Code 106 such that the information transfer element is automatically read by the medication wasting device when the syringe is coupled thereto. One example of a medication wasting device is described in U.S. patent application Ser. No. 13/170,073 entitled: “Medication Waste Collection Apparatus”, the contents of which are hereby fully incorporated by reference.



FIG. 10 is a diagram illustrating a medication dose preparation and transfer apparatus as in FIG. 3 with a display. A display 120 can be included on housing 12 of medication dose preparation and transfer apparatus 8. Display 120 can include a user interface 130 providing information about the fluid transfer process or user guidance to ensure the medication and volume transferred is correct and appropriate for its intended use. For example a pediatric dose preparation system can include the selection of a pediatric color (Broselow color) or patient weight (kilograms or pounds), an indication of the medication type and/or concentration connected identified by ID Code 102 and subsequently recommend a dose or volume for withdrawal from the primary container 4. Pediatric color, patient weight, recommended dose, and other relevant dose preparation parameters can also be downloaded to the medication dose preparation and transfer apparatus 8 from recordkeeping system 30 via information transmission 18. When the secondary container 6 is attached and the syringe plunger rod is pulled a medication dose can be removed from the primary container 4 into secondary container 6. That dose transfer is measured by volume/flow sensor 118 and can be displayed as the syringe fill volume. Subsequently, when the dose is administered to the patient the display can indicate the dose volume. Alternately, the measured volume can be used to calculate a dose in grams, milligrams, micrograms or other medication units instead of milliliters (mL) as shown in FIG. 10.


Information 18 can be bi-directionally exchanged and can include transfer of data from recordkeeping system 30 (including medication management devices and systems, or any healthcare information computer system) to dose preparation and transfer apparatus 8 for display to a user. Information 18 can provide additional data to the display including, but not limited to medication delivery order data, patient-specific identifiers, general or medication-specific dosing limits, data for contraindication checking, Broselow color/classification, patient drug allergies, patient weight, medication data, patient specific data, procedural cautionary data, error prevention data, dose time data, physician instructions, drug manufacturer's instructions, precautions, contraindications, etc.



FIG. 11 is a diagram illustrating a second medication dose preparation and transfer apparatus as in FIG. 3 with a display. A display 120 can be included on housing 12 of medication dose preparation and transfer apparatus 8. Display 120 can include a user interface 130 providing information about the fluid transfer process or user guidance to ensure the medication and volume transferred is correct and appropriate for its intended use. For example a controlled substance dose preparation system can include an indication of the medication type and or concentration connected identified by ID Code 102. A caregiver can determine an appropriate dose volume and withdraw that dose volume from the primary container 4. When the secondary container 6 is attached and the syringe plunger rod is pulled a medication dose is removed from the primary container 4 into secondary container 6. That dose transfer is measured by volume/flow sensor 118 and can be displayed as the syringe fill volume. Subsequently, when the dose is administered to the patient the display can indicate the patient dose volume.


Alternately, the entire volume of medication can be withdrawn from vial 4. In this case any extra medication can be disposed of in a waste container prior to dose administration to a patient. In this case the remaining volume is retained in syringe 6 for administration to the patient. Information 18 about the medication (ID Code 102, the withdrawn volume, the disposed of waste volume measured, the unique syringe ID Code 106) can all be transferred to recordkeeping system 30 for tracking and accounting of controlled substances. Dose volumes can be used to calculate a dose in grams, milligrams, micrograms or other medication units instead of milliliters (mL) as shown in FIG. 11.



FIG. 12 is a diagram showing an example sequence of operation for the device in FIG. 11.


Step 1: A caregiver receives medication orders and prepares the dose preparation and transfer apparatus 8 (300, 302, 304, 306).


Step 2: A caregiver assembles the medication containers (4 and 6) to medication dose preparation and transfer apparatus 8 (308, 310, 312, 314, 316, 318).


Step 3: The recordkeeping system 30 maintains a tracking record of ID codes and transfer volumes (320) and the caregiver detaches the secondary container 6 from apparatus 8 (322).


Step 4: The caregiver administers the medication to the patient and disposes of unused medication waste (324, 326, 328). The recordkeeping system 30 accounts for the history of medication transferred with from primary medication container 4 to secondary medication container 6, the dose administered to the patient, and any residual waste disposal (330).



FIG. 13 is a diagram describing a detailed view of a sixth medication dose preparation and transfer system 2 as in FIG. 1. In this implementation, medication ID Code 102 can be placed on the primary medication container vial 4 (102a) or on vial closure rim (102b) of the primary medication container 4. In FIG. 13, medication container emitter/detector 104 can identify medication ID Code 102 (102a or 102b) on primary medication container (vial) 4 when it is not attached to dose transfer fluid channel 10. Then, after ID Code 102 has been identified by dose preparation and transfer apparatus 8 it can be spiked or attached onto fluid channel 10, inverted and prepared for dose transfer into secondary container 6. Secondary container 6 can still have ID Code 106 located at the fluid outlet and can be identified by emitter/detector 108. In this implementation dose transfer fluid channel 10 couples primary medication container 4 to secondary container 6. Housing 12 can contain a volume/flow transducer 118 coupled to dose transfer fluid channel 10 to measure an amount of medication transferred from vial 4 to syringe 6. The other features and functions of dose preparation and transfer apparatus 8 described in FIG. 3 can be the same.



FIG. 14 is a diagram describing a detailed view of a seventh medication dose preparation and transfer system 2 as in FIG. 1. In this implementation, dose preparation and transfer apparatus 8 does not utilize dose transfer fluid channel 10 and instead uses a separate vial adapter 16. Housing 12 can contain identification emitter/detectors 104 and 108 to read ID Codes 102 and 106 respectively. Housing 12 can contain hardware and software elements 110 and 114 to process and transmit or receive information 18 to/from recordkeeping system 30.


ID Code 102 can be placed on the primary medication container vial 4 (102a) or on vial closure rim (102b) of the primary medication container 4 as in FIG. 13. Additionally, ID Code 106 can be placed on secondary medication container 6 (106a) or on the syringe fluid outlet (106b) of secondary medication container 6. Emitter/detector 104 can identify ID Code 102 (102a or 102b) on primary medication container (vial) 4 when it is not attached to dose transfer fluid channel 10. Emitter/detector 108 can identify ID Code 106 (106a or 106b) on secondary medication container (syringe) 6 when it is not attached to dose transfer fluid channel 10.


Then, after ID Codes 102 and 104 have been identified by dose preparation and transfer apparatus 8 they can be associated with each other via information transmission 18 using recordkeeping system 30.


When used, primary medication container (vial) 4 is coupled to secondary container (syringe) 6 for fluid transfer. Vial 4 can be coupled (spiked) using medication container adapter 16 attached to the fluid outlet of secondary container (syringe) 6. Adapter 16 can contain dose transfer fluid channel 10. Adapter 16 can be a vial adapter, a needle, a blunt tip cannula, a needle-less luer adapter with spike as shown in FIG. 2 or any fluid transfer apparatus designed to transfer medication 20 from vial 4 into syringe 6.


Following the coupling of vial 4 to syringe 6 through dose transfer fluid channel 10, the assembly is inverted and prepared for dose transfer. In this implementation dose transfer fluid channel 10 couples primary medication container 4 to secondary container 6. Measurement of fluid transfer is done by the caregiver and manually entered into recordkeeping system 30. The other features and functions of dose preparation and transfer apparatus 8 described in FIG. 2 can be the same.


The subject matter described herein can be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. In particular, aspects of the subject matter described herein can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.


These computer programs (also known as programs, software, software applications, applications, components, or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any non-transitory computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.


The user interface can include, for example a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor for displaying information to the user. The user may input any information to the display device using a keyboard and a pointing device, such as for example a mouse or a trackball. Other possible input devices include, but are not limited to, touch screens or other touch-sensitive devices such as single or multi-point resistive or capacitive trackpads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like. Other kinds of devices can be used to provide for interaction with a user as well. Further, the input from the user may be received in any form, including, but not limited to, acoustic, speech, or tactile input.


Besides a digital feedback shown to the health care provider, the feedback may be an audio signal, a video signal, or any form of sensory feedback such as a visual feedback, an auditory feedback, or tactile feedback.


The implementations set forth in the foregoing description do not represent all implementations consistent with the subject matter described herein. Instead, they are merely some examples consistent with aspects related to the described subject matter. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.


Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations can be provided in addition to those set forth herein. For example, the implementations described above can be directed to various combinations and sub-combinations of the disclosed features and/or combinations and sub-combinations of several further features disclosed above. In addition, the logic flows and steps for use described herein do not require the particular order shown, or sequential order, to achieve desirable results. Other embodiments can be within the scope of the claim.

Claims
  • 1. An apparatus for transferring medication, comprising: a housing having a fluid channel including a first sub-channel connecting a primary medication container port with a patient outlet and a second sub-channel extending an angle from the first sub-channel, wherein the first sub-channel terminates at a first end at the first sub-channel and at a second end at a secondary medication container port;at least one identification sensor disposed within the housing configured to sense an information transfer element on a medication container, the information transfer element on the medication container associated with a medication within the medication container; anda bi-directional flow sensor configured to measure a flow of medication in each direction within the second sub-channel.
  • 2. The apparatus of claim 1, further comprising: a communication module to transmit information obtained by and/or derived from the at least one identification sensor to a remote computing system.
  • 3. The apparatus of claim 1, further comprising: a medication container coupling configured to fluidically couple the medication container to the primary medication container port.
  • 4. The apparatus of claim 1, wherein the information transfer element includes at least one of an optical source, a magnetic source, a mechanical source, a switchable RFID source, a conductive source, and a proximity source.
  • 5. The apparatus of claim 4, wherein the information transfer element comprises a magnetically detectable strip.
  • 6. The apparatus of claim 4, wherein the information transfer element comprises a plurality of ridges and valleys facilitating detection by a micro-switch.
  • 7. The apparatus of claim 4, wherein the information transfer element comprises an RFID tag, wherein the RFID tag is open prior to connection to the apparatus and wherein the RFID tag is closed after connection to the apparatus.
  • 8. The apparatus of claim 4, wherein the information transfer element comprises at least one of etched and molded features.
  • 9. The apparatus of claim 4, wherein the information transfer element comprises a label adhered to the medication container.
  • 10. The apparatus of claim 1, wherein the information identified by the information transfer element includes at least one of: a unique number, a code, a symbol, a serial number, and a random number describing a specific unique secondary container.
  • 11. The apparatus of claim 3, wherein the medication container coupling comprises a luer fitting to accept a complementary luer fitting of the medication container.
  • 12. The apparatus of claim 1, wherein the housing includes a display that includes a user interface configured to provide information associated with a fluid transfer process.
  • 13. The apparatus of claim 2, wherein the communication module transmits the information obtained by and/or derived from the at least one identification sensor to the remote computing system to associate the information with the secondary medication container.
  • 14. The apparatus of claim 2, wherein the communication module wirelessly transmits information obtained by and/or derived from the at least one identification sensor to the remote computing system.
  • 15. The apparatus of claim 1, wherein the first sub-channel includes an upstream check valve between the primary medication container port and a junction formed by the first end of the second sub-channel and the first sub-channel, and wherein the first sub-channel includes a downstream check valve between the patient outlet and the junction formed by the first end of the second sub-channel and the first sub-channel.
  • 16. A system, comprising: a medication container; andan apparatus for transferring medication, comprising: a housing having a fluid channel including a first sub-channel connecting a primary medication container port with a patient outlet and a second sub-channel extending an angle from the first sub-channel, wherein the first sub-channel terminates at a first end at the first sub-channel and at a second end at a secondary medication container port;at least one identification sensor disposed within the housing configured to sense an information transfer element on the medication container, the information transfer element on the medication container associated with a medication within the medication container; anda bi-directional flow sensor configured to measure a flow of medication in each direction within the second sub-channel.
  • 17. The system of claim 16, wherein the apparatus further comprises a communication module to transmit information obtained by and/or derived from the at least one identification sensor to a remote computing system.
  • 18. The system of claim 16, wherein the apparatus further comprises: a medication container coupling configured to fluidically couple the medication container to the primary medication container port.
  • 19. The system of claim 16, wherein the information transfer element comprises an RFID tag.
  • 20. The system of claim 16, wherein the housing includes a display that includes a user interface configured to provide information associated with a fluid transfer process.
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S. application Ser. No. 15/443,006, entitled “Medication Dose Preparation and Transfer System” filed Feb. 27, 2017, which is a continuation application of U.S. application Ser. No. 14/728,408, entitled “Medication Dose Preparation and Transfer System” filed Jun. 2, 2015 (now U.S. Pat. No. 9,615,999), which is a continuation application of U.S. application Ser. No. 13/524,736, entitled “Medication Dose Preparation and Transfer System” filed Jun. 15, 2012 (now U.S. Pat. No. 9,078,809), which claims priority to U.S. Provisional Application Ser. No. 61/497,855, filed Jun. 16, 2011, the entire contents of each of which are hereby fully incorporated by reference.

US Referenced Citations (404)
Number Name Date Kind
3430625 McLeod, Jr. Mar 1969 A
4003252 Dewath Jan 1977 A
4415802 Long Nov 1983 A
4650475 Smith et al. Mar 1987 A
4853521 Claeys et al. Aug 1989 A
4857713 Brown Aug 1989 A
4921277 McDonough May 1990 A
4978335 Arthur, III Dec 1990 A
5011032 Rollman Apr 1991 A
5040422 Frankenberger et al. Aug 1991 A
5078683 Sancoff et al. Jan 1992 A
5179862 Lynnworth Jan 1993 A
5247826 Frola et al. Sep 1993 A
5279576 Loo et al. Jan 1994 A
5317506 Coutre et al. May 1994 A
5338157 Blomquist Aug 1994 A
5383858 Reilly et al. Jan 1995 A
5429602 Hauser Jul 1995 A
5463906 Spani et al. Nov 1995 A
5531697 Olsen et al. Jul 1996 A
5531698 Olsen Jul 1996 A
5569212 Brown Oct 1996 A
5611784 Barresi et al. Mar 1997 A
5612524 Sant' Anselmo et al. Mar 1997 A
5628309 Brown May 1997 A
5651775 Walker et al. Jul 1997 A
5692640 Caulfield et al. Dec 1997 A
5713856 Eggers et al. Feb 1998 A
5720733 Brown Feb 1998 A
5740428 Mortimore et al. Apr 1998 A
5781442 Engleson et al. Jul 1998 A
5782814 Brown et al. Jul 1998 A
5792117 Brown Aug 1998 A
5845264 Nellhaus Dec 1998 A
5873731 Prendergast Feb 1999 A
5882338 Gray Mar 1999 A
5920263 Huttenhoff et al. Jul 1999 A
5925014 Teeple Jr. Jul 1999 A
5941846 Duffy et al. Aug 1999 A
5984901 Sudo et al. Nov 1999 A
6019745 Gray Feb 2000 A
6039251 Holowko et al. Mar 2000 A
6106498 Friedli et al. Aug 2000 A
6123686 Olsen et al. Sep 2000 A
6192945 Ford et al. Feb 2001 B1
D438634 Merry Mar 2001 S
6249299 Tainer Jun 2001 B1
6256037 Callahan Jul 2001 B1
6270455 Brown Aug 2001 B1
6277099 Strowe et al. Aug 2001 B1
6338200 Baxa et al. Jan 2002 B1
6341174 Callahan et al. Jan 2002 B1
6342889 Callahan Jan 2002 B1
6381029 Tipirneni Apr 2002 B1
6422094 Ganshorn Jul 2002 B1
6464667 Kamen et al. Oct 2002 B1
6468424 Donig et al. Oct 2002 B1
6471089 Liff et al. Oct 2002 B2
6482185 Hartmann Nov 2002 B1
6519569 White et al. Feb 2003 B1
6579231 Phipps Jun 2003 B1
RE38189 Walker et al. Jul 2003 E
6626355 Sasse et al. Sep 2003 B2
6626862 Duchon et al. Sep 2003 B1
D481121 Evans Oct 2003 S
6641562 Peterson Nov 2003 B1
6644130 Imai et al. Nov 2003 B2
6671563 Engelson et al. Dec 2003 B1
D485356 Evans Jan 2004 S
6675660 Mosier et al. Jan 2004 B1
6685227 Merry et al. Feb 2004 B2
6685678 Evans et al. Feb 2004 B2
6697067 Callahan et al. Feb 2004 B1
6731989 Engleson et al. May 2004 B2
6733495 Bek et al. May 2004 B1
6742992 Davis Jun 2004 B2
6790198 White et al. Sep 2004 B1
6798533 Tipirneni Sep 2004 B2
6825864 Botten et al. Nov 2004 B2
6851615 Jones Feb 2005 B2
6854338 Khur-Yakub et al. Feb 2005 B2
6915170 Engleson et al. Jul 2005 B2
6960192 Flaherty et al. Nov 2005 B1
6985870 Martucci et al. Jan 2006 B2
6993402 Klass et al. Jan 2006 B2
7000485 Ao et al. Feb 2006 B2
7017623 Tribble et al. Mar 2006 B2
7061831 De La Huerga Jun 2006 B2
7074205 Duffy et al. Jul 2006 B1
7074209 Evans et al. Jul 2006 B2
7096072 Engleson et al. Aug 2006 B2
7103419 Engleson et al. Sep 2006 B2
7106479 Roy et al. Sep 2006 B2
7107106 Engleson et al. Sep 2006 B2
7115113 Evans et al. Oct 2006 B2
7116343 Botten et al. Oct 2006 B2
7117041 Engleson et al. Oct 2006 B2
7161488 Frasch Jan 2007 B2
7171277 Engleson et al. Jan 2007 B2
7175081 Andreasson et al. Feb 2007 B2
7180624 Tipirneni Feb 2007 B2
7182256 Andreasson et al. Feb 2007 B2
7225683 Harnett et al. Jun 2007 B2
7236936 White et al. Jun 2007 B2
7237199 Menhardt et al. Jun 2007 B1
7264323 Tainer et al. Sep 2007 B2
7299981 Hickle et al. Nov 2007 B2
7319540 Tipirneni Jan 2008 B2
7347841 Elhadad et al. Mar 2008 B2
7358505 Woodworth et al. Apr 2008 B2
7360448 Maginnis et al. Apr 2008 B2
7364067 Steusloff et al. Apr 2008 B2
7370797 Sullivan et al. May 2008 B1
7375737 Botten et al. May 2008 B2
7384410 Eggers et al. Jun 2008 B2
7442181 Schubert et al. Oct 2008 B2
7469598 Shkarlet et al. Dec 2008 B2
7469599 Froehlich et al. Dec 2008 B2
7470266 Massengale et al. Dec 2008 B2
7483756 Engleson et al. Jan 2009 B2
D588200 Langan et al. Mar 2009 S
7534239 Schneider et al. May 2009 B1
D593613 Langan et al. Jun 2009 S
D595361 Langan et al. Jun 2009 S
7559483 Hickle et al. Jul 2009 B2
7564579 Tipirneni Jul 2009 B2
D597608 Langan et al. Aug 2009 S
D602534 Langan et al. Oct 2009 S
7614545 Christoffersen et al. Nov 2009 B2
7617739 Dam Nov 2009 B1
D605228 Langan et al. Dec 2009 S
D605229 Langan et al. Dec 2009 S
D605230 Langan et al. Dec 2009 S
7645258 White et al. Jan 2010 B2
7673527 Ehring et al. Mar 2010 B2
7694565 Koerdt et al. Apr 2010 B2
7703336 Genosar Apr 2010 B2
7704231 Pongpairochana et al. Apr 2010 B2
7722083 McCarthy et al. May 2010 B2
7727196 Neer Jun 2010 B2
7753880 Malackowski Jul 2010 B2
7753891 Fennican et al. Jul 2010 B2
7756724 Gropper et al. Jul 2010 B2
7763006 Tennican Jul 2010 B2
D621879 Langan et al. Aug 2010 S
D621880 Langan et al. Aug 2010 S
7771385 Eggers et al. Aug 2010 B2
D624595 Langan et al. Sep 2010 S
D624596 Langan et al. Sep 2010 S
7799010 Tennican Sep 2010 B2
7813939 Clements et al. Oct 2010 B2
7815123 Conner et al. Oct 2010 B2
7815605 Souter Oct 2010 B2
7819838 Ziegler et al. Oct 2010 B2
7822096 Kuksenkov Oct 2010 B2
7834816 Marino et al. Nov 2010 B2
7859473 Gibson Dec 2010 B2
D633151 Langan et al. Feb 2011 S
7887513 Nemoto et al. Feb 2011 B2
D634367 Langan et al. Mar 2011 S
D634368 Langan et al. Mar 2011 S
D634369 Langan et al. Mar 2011 S
7905861 Rhinehart et al. Mar 2011 B2
7918830 Langan et al. Apr 2011 B2
7922073 de la Huerga Apr 2011 B2
7927313 Stewart et al. Apr 2011 B2
7933780 De La Huerga Apr 2011 B2
7941949 Cloninger May 2011 B2
D639861 Langan et al. Jun 2011 S
D639862 Langan et al. Jun 2011 S
D639863 Langan et al. Jun 2011 S
7967778 Nemoto et al. Jun 2011 B2
D641421 Langan et al. Jul 2011 S
D641422 Langan et al. Jul 2011 S
7976508 Hoag Jul 2011 B2
D643468 Langan et al. Aug 2011 S
D643469 Langan et al. Aug 2011 S
D643470 Langan et al. Aug 2011 S
D643471 Langan et al. Aug 2011 S
D643472 Langan et al. Aug 2011 S
7991627 Hutchinson et al. Aug 2011 B2
D645094 Langan et al. Sep 2011 S
8031347 Edwards et al. Oct 2011 B2
8035517 Gibson Oct 2011 B2
D649196 Langan et al. Nov 2011 S
8059297 Tipirneni Nov 2011 B2
8063925 Tainer et al. Nov 2011 B2
8065924 Ziegler et al. Nov 2011 B2
8069060 Tipirneni Nov 2011 B2
8111159 Andreasson et al. Feb 2012 B2
8133178 Brauker et al. Mar 2012 B2
8140349 Hanson et al. Mar 2012 B2
8151835 Khan et al. Apr 2012 B2
8235938 Eggers et al. Aug 2012 B2
8240550 Steusloff et al. Aug 2012 B2
8303547 Brown Nov 2012 B2
8328082 Bochenko et al. Dec 2012 B1
8355753 Bochenko et al. Jan 2013 B2
8385972 Bochenko et al. Feb 2013 B2
8394053 Bochenko et al. Mar 2013 B2
8480834 Rice et al. Jul 2013 B2
8505809 Steusloff et al. Aug 2013 B2
8606596 Bochenko et al. Dec 2013 B1
8636202 Keefe et al. Jan 2014 B2
8639521 Eggers et al. Jan 2014 B2
8639525 Levine et al. Jan 2014 B2
8645154 Eggers et al. Feb 2014 B2
8702674 Bochenko Apr 2014 B2
8752088 Harvey et al. Jun 2014 B1
20010020148 Sasse et al. Sep 2001 A1
20010049608 Hochman Dec 2001 A1
20010056258 Evans Dec 2001 A1
20020040208 Flaherty et al. Apr 2002 A1
20020077852 Ford et al. Jun 2002 A1
20020088131 Baxa et al. Jul 2002 A1
20020098598 Coffen et al. Jul 2002 A1
20020099334 Hanson et al. Jul 2002 A1
20020177811 Reilly et al. Nov 2002 A1
20020188259 Hickle et al. Dec 2002 A1
20030012701 Sangha et al. Jan 2003 A1
20030052787 Zerhusen et al. Mar 2003 A1
20030055685 Cobb et al. Mar 2003 A1
20030065537 Evans Apr 2003 A1
20030088238 Poulsen et al. May 2003 A1
20030130698 King Jul 2003 A1
20030135388 Martucci et al. Jul 2003 A1
20030139701 White et al. Jul 2003 A1
20030139706 Gray Jul 2003 A1
20030140929 Wilkes et al. Jul 2003 A1
20030164401 Andreasson et al. Sep 2003 A1
20030174326 Rzasa et al. Sep 2003 A1
20040051368 Caputo et al. Mar 2004 A1
20040082918 Evans et al. Apr 2004 A1
20040092885 Duchon et al. May 2004 A1
20040103951 Osborne et al. Jun 2004 A1
20040104271 Martucci et al. Jun 2004 A1
20040105115 Edwards et al. Jun 2004 A1
20040179051 Tainer et al. Sep 2004 A1
20040179132 Fujino et al. Sep 2004 A1
20040186437 Frenette et al. Sep 2004 A1
20040193453 Butterfield et al. Sep 2004 A1
20040204673 Flaherty Oct 2004 A1
20040212834 Edwards et al. Oct 2004 A1
20040238631 Andreasson et al. Dec 2004 A1
20050055242 Bello et al. Mar 2005 A1
20050070978 Bek et al. Mar 2005 A1
20050088306 Andreasson et al. Apr 2005 A1
20050101905 Merry May 2005 A1
20050106225 Massengale et al. May 2005 A1
20050107923 Vanderveen May 2005 A1
20050118048 Traxinger Jun 2005 A1
20050151652 Frasch Jul 2005 A1
20050151823 Botten et al. Jul 2005 A1
20050154368 Lim et al. Jul 2005 A1
20050165559 Nelson Jul 2005 A1
20050182358 Veit et al. Aug 2005 A1
20050277873 Stewart et al. Dec 2005 A1
20050277890 Stewart et al. Dec 2005 A1
20060032918 Andreasson et al. Feb 2006 A1
20060065713 Kingery Mar 2006 A1
20060079767 Gibbs et al. Apr 2006 A1
20060079843 Brooks et al. Apr 2006 A1
20060102503 Elhadad et al. May 2006 A1
20060116639 Russell Jun 2006 A1
20060122577 Poulsen et al. Jun 2006 A1
20060143051 Eggers et al. Jun 2006 A1
20060144942 Evans et al. Jul 2006 A1
20060178617 Adams et al. Aug 2006 A1
20060190302 Eggers et al. Aug 2006 A1
20060206356 Vanderveen Sep 2006 A1
20060224125 Simpson et al. Oct 2006 A1
20060226089 Robinson et al. Oct 2006 A1
20060229551 Martinez et al. Oct 2006 A1
20060253346 Gomez Nov 2006 A1
20060258985 Russell Nov 2006 A1
20060265186 Holland et al. Nov 2006 A1
20060270997 Lim et al. Nov 2006 A1
20060287887 Hutchinson et al. Dec 2006 A1
20070008399 Botten et al. Jan 2007 A1
20070043335 Olsen et al. Feb 2007 A1
20070100316 Traxinger May 2007 A1
20070134044 Colbrunn et al. Jun 2007 A1
20070135765 Miller et al. Jun 2007 A1
20070136218 Bauer et al. Jun 2007 A1
20070166198 Sangha et al. Jul 2007 A1
20070167919 Nemoto et al. Jul 2007 A1
20070179448 Lim et al. Aug 2007 A1
20070186923 Poutiatine et al. Aug 2007 A1
20070187475 MacLeod Aug 2007 A1
20070191787 Lim et al. Aug 2007 A1
20070255199 Dewey Nov 2007 A1
20070279625 Rzasa et al. Dec 2007 A1
20070280710 Tainer et al. Dec 2007 A1
20070293830 Martin Dec 2007 A1
20070299421 Gibson Dec 2007 A1
20080043088 Botten et al. Feb 2008 A1
20080045930 Makin et al. Feb 2008 A1
20080051937 Khan et al. Feb 2008 A1
20080061153 Hickle et al. Mar 2008 A1
20080071219 Rhinehart et al. Mar 2008 A1
20080118141 Sommer et al. May 2008 A1
20080125724 Monroe May 2008 A1
20080191013 Liberatore Aug 2008 A1
20080208042 Ortenzi et al. Aug 2008 A1
20080234630 Iddan et al. Sep 2008 A1
20080243088 Evans Oct 2008 A1
20080255523 Grinberg Oct 2008 A1
20080294108 Briones et al. Nov 2008 A1
20080306439 Nelson et al. Dec 2008 A1
20090018494 Nemoto et al. Jan 2009 A1
20090030730 Dullemen et al. Jan 2009 A1
20090036846 Dacquay et al. Feb 2009 A1
20090043253 Podaima Feb 2009 A1
20090069714 Eichmann et al. Mar 2009 A1
20090085768 Patel et al. Apr 2009 A1
20090112178 Behzadi Apr 2009 A1
20090112333 Sahai Apr 2009 A1
20090126483 Blendinger et al. May 2009 A1
20090126866 Stenner et al. May 2009 A1
20090137956 Souter May 2009 A1
20090143673 Drost et al. Jun 2009 A1
20090145509 Baker Jun 2009 A1
20090149744 Nemoto et al. Jun 2009 A1
20090156931 Nemoto et al. Jun 2009 A1
20090157008 Vitral Jun 2009 A1
20090159654 Grimard Jun 2009 A1
20090200185 Follman et al. Aug 2009 A1
20090259176 Yair Oct 2009 A1
20090288497 Ziegler et al. Nov 2009 A1
20090294521 de la Huerga Dec 2009 A1
20090296540 Gilbert et al. Dec 2009 A1
20090306620 Thilly et al. Dec 2009 A1
20100022953 Bochenko et al. Jan 2010 A1
20100022987 Bochenko et al. Jan 2010 A1
20100036310 Hillman Feb 2010 A1
20100036313 Shener et al. Feb 2010 A1
20100065633 Nelson et al. Mar 2010 A1
20100065643 Leyvraz et al. Mar 2010 A1
20100076310 Wenderow et al. Mar 2010 A1
20100095782 Ferencz et al. Apr 2010 A1
20100114951 Bauman et al. May 2010 A1
20100145465 Smirthwaite et al. Jun 2010 A1
20100152562 Goodnow et al. Jun 2010 A1
20100153136 Whittacre et al. Jun 2010 A1
20100168711 Bazargan Jul 2010 A1
20100174266 Estes Jul 2010 A1
20100179417 Russo Jul 2010 A1
20100204659 Bochenko et al. Aug 2010 A1
20100262002 Martz Oct 2010 A1
20100280486 Khair et al. Nov 2010 A1
20100286599 Ziegler et al. Nov 2010 A1
20100305499 Matsiev et al. Dec 2010 A1
20110009800 Dam et al. Jan 2011 A1
20110009817 Bennett et al. Jan 2011 A1
20110028937 Powers et al. Feb 2011 A1
20110060198 Bennett et al. Mar 2011 A1
20110093279 Levine et al. Apr 2011 A1
20110111794 Bochenko et al. May 2011 A1
20110112473 Bochenko et al. May 2011 A1
20110112474 Bochenko et al. May 2011 A1
20110137288 Tallarida et al. Jun 2011 A1
20110152824 DiPerna et al. Jun 2011 A1
20110152825 Marggi Jun 2011 A1
20110152834 Langan et al. Jun 2011 A1
20110160655 Hanson et al. Jun 2011 A1
20110161112 Keefe et al. Jun 2011 A1
20110166511 Sharvit et al. Jul 2011 A1
20110176490 Mehta et al. Jul 2011 A1
20110185821 Genosar Aug 2011 A1
20110220713 Cloninger Sep 2011 A1
20110224649 Duane et al. Sep 2011 A1
20110259954 Bartz et al. Oct 2011 A1
20110264069 Bochenko Oct 2011 A1
20110313349 Krulevitch et al. Dec 2011 A1
20110315611 Fulkerson et al. Dec 2011 A1
20120004542 Nemoto et al. Jan 2012 A1
20120004602 Hanson et al. Jan 2012 A1
20120004637 Krulevitch et al. Jan 2012 A1
20120006127 Nielsen Jan 2012 A1
20120022458 Oh et al. Jan 2012 A1
20120035535 Johnson et al. Feb 2012 A1
20120037266 Bochenko Feb 2012 A1
20120041355 Edman et al. Feb 2012 A1
20120046295 Charrier et al. Feb 2012 A1
20120065617 Matsiev et al. Mar 2012 A1
20120222468 Nelson et al. Sep 2012 A1
20120226446 Nelson et al. Sep 2012 A1
20120226447 Nelson et al. Sep 2012 A1
20120287431 Matsiev et al. Nov 2012 A1
20120323208 Bochenko et al. Dec 2012 A1
20120325330 Prince et al. Dec 2012 A1
20130018356 Prince et al. Jan 2013 A1
20130105568 Jablonski et al. May 2013 A1
20130135388 Samoto et al. May 2013 A1
20130181046 Fedorko et al. Jul 2013 A1
20130204227 Bochenko et al. Aug 2013 A1
20130225945 Prince et al. Aug 2013 A1
20130226137 Brown Aug 2013 A1
20130327822 Keefe et al. Dec 2013 A1
20140039383 Dobbies et al. Feb 2014 A1
20140060729 Smka et al. Mar 2014 A1
20140142975 Keefe et al. May 2014 A1
20150204705 Forster et al. Jul 2015 A1
20150211904 Forster Jul 2015 A1
Foreign Referenced Citations (10)
Number Date Country
2504288 May 1987 GB
2183046 Nov 1989 GB
2504295 Jan 2014 GB
2504297 Jan 2014 GB
2009114115 Sep 2009 WO
2010144482 Dec 2010 WO
2012034084 Mar 2012 WO
2014016311 Jan 2014 WO
2014016315 Jan 2014 WO
2014016316 Jan 2014 WO
Related Publications (1)
Number Date Country
20190336395 A1 Nov 2019 US
Provisional Applications (1)
Number Date Country
61497855 Jun 2011 US
Continuations (3)
Number Date Country
Parent 15443006 Feb 2017 US
Child 16511144 US
Parent 14728408 Jun 2015 US
Child 15443006 US
Parent 13524736 Jun 2012 US
Child 14728408 US