The subject matter described herein relates to a medication identification, encoding and verification for use in scanning, verifying and/or marking medication containers so the medications in those containers can be properly identified and documented during the process of patient medication preparation, administration, and disposal. Medication containers can include syringes, bags, vials, medication transfer apparatus as well as medical packaging with marking applied during various manufacturing and pharmacy processes.
Many health care procedures involving the preparation, administration and wasting of medication involve a clinician manually reading labeling applied to various medication containers. Such an arrangement is fraught for user error resulting in over-medication, under-medication, administration of non-compatible medications and/or administration of medications to which a patient is allergic. In addition, problems also arise in properly labeling medication containers during manufacture and preparation (whether in the pharmacy or otherwise). Proper labeling is of particular import when there are multiple components bundled together.
In one aspect, data characterizing medication within a medication container is received. Thereafter, an identifier encapsulating data characterizing the medication is generated and applied to the medication container. The identifier can be positioned such that it is automatically readable by a medication administration device when the medication is administered to a patient and/or by a medication disposal device when the medication is wasted.
The medication container can take a variety of forms. The medication container can be a syringe comprising a barrel portion and a tip portion comprising a fluid outlet such that the identifier is applied to the tip portion. The tip portion can comprise a cylindrical or conical outer surface terminating at the fluid outlet such that the identifier is applied to the outer surface. The tip portion can comprise a Luer lock fitting such that identifier is positioned on the Luer lock fitting.
The medication container can be a vial having a stopper or a corresponding stopper closure to which the identifier is applied. The medication container can be a medication bag containing a medication solution having a Luer fitting and/or a spikeable port to which the identifier is applied. The medication container can be an envelope having a Luer fitting or a tubing set extending therefrom to which the identifier is applied. The medication container can comprise a fluid transfer device for transferring the medication from a first receptacle to a second receptacle. The medication container can comprise packaging including a medication receptacle containing the medication. The medication container can be a fluid tubing set having a fluid outlet such as a Luer fitting to which the identifier is applied.
The medication administration device can take a variety of forms. For example, the medication administration device can comprise: a housing, a medication port accessible via an outer surface of the housing, an identification sensor disposed within the housing to generate information indicative of contents of the medication container when the fluid outlet of the medication container is fluidically coupled to the medication port, and a transmitter disposed within the housing and in communication with the identification sensor to transmit the information generated by the identification sensor to a remote data collection system.
The encapsulated data can comprise a reference to data accessible via a communications network. In such cases, the encapsulated data can include a a Uniform Resource Locator, a database path, a pointer to a look-up table, or a file path such that the medication administration device accesses such remote information (which can be used, for example, for more informed patient treatment, etc.). In addition or in the alternative, the medication administration device can comprises a memory storing data corresponding to the encapsulated data which is accessed when the medication administration device reads the identifier.
The encapsulated data can be formatted using an industry standard representation of the medication being characterized or a proprietary representation of the medication being characterized. The referenced data accessible via a communications network 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 identifier can take a variety of forms. For example, the identifier can be any of: optical identifiers, magnetic identifiers, RFID identifiers, and mechanically encoded identifiers. The identifier can be etched on an outer surface of the medication container. The identifier can be a mechanical element secured to or extending from the medication container. The identifier can include a coded disc or coded ring secured to the medication container.
The medication container can be bundled with at least one other item (e.g., second medication container, fluid adapter, tubing set, packaging, etc.) bearing a second identifier corresponding to the identifier. In such cases, it can be verified, after the bundling, that the identifier on the medication container corresponds to the second identifier on the at least one other item.
In a further aspect, data is read from a medication source characterizing medication contained by the medication source. Thereafter, an identifier encapsulating data characterizing the medication is generated and is applied to a medication container filled or to be filled with the medication from the medication source. The identifier can be positioned such that it is readable by a medication administration device when administering the medication to a patient or when disposing the medication without deliberate effort on behalf of a clinician to facilitate information transfer between the medication container and the medication administration device or the medication wasting device.
In a further aspect, a medication identification encoding and verification apparatus is provided that includes a medication information source, an identification information reader (ID reader), an identification information writer (ID writer), a verification method to check the read information and a medication identification target (ID target). The ID reader includes a detector, scanner or imaging element to receive the medication identification information. The ID writer includes a marking element to deposit or encode identification information onto the ID target. The ID target receives the encoded identification information mark, image, code or other information rich media content. If the medication container is a syringe, the encoded information on the target is positioned such that it can be read by a medication administration device when administering the medication to a patient without deliberate effort on behalf of a clinician to facilitate information transfer between the medication container and the medication administration device.
In another aspect, a medication identification encoding and verification apparatus is provided with a second ID reader, a verification comparator, an identification information verification writer (IDV writer) and a second identification information target on packaging materials. The second ID reader includes a scanner element to receive medication information from a medication container or associated medical packaging. The verification comparator includes means for comparing desired identification information to medication container identification information. The IDV writer includes a marking element to deposit or encode identification information on a second ID target. The second ID target receives the second identification information mark. The second ID target can be packaging material. A read-write instrument can be provided for reading a medication identification code source and writing information to a target for encoding the target with the medication identification information used, for example, in a pharmaceutical manufacturing facility. In a further variation that can be used in a pharmaceutical repacking operation or in-hospital pharmacy, the reader can identify medication information from a multi-dose container and the writer can then encode single or partial dose information on the target. In this variation, the written information can be different from the original read information in that it can indicate smaller volumes, lower concentrations or be a patient specific dose. Multiple writes can be made on multiple targets to encode information about aliquots of medication written onto multiple single dose containers.
The information reader aspect of the read-write instrument can be any one of a linear bar-code reader, a 2D barcode reader, a magnetic strip reader, an image capture device, a camera, a manual data input information string, a stored alpha numeric character string, a unique symbolic identifier.
The information writer aspect of the read-write instrument can be any one of a laser, a printer, a hot stamp, a magnetic coding element, an electronic coding element, an RFID writer, a printed label, a coded disc, or coded ring element to be affixed to a medication container or packaging.
The information target can be any one of a syringe including but not limited to an empty and/or a prefilled syringe, a bag, a vial, a medication transfer apparatus including but not limited to an fluid administration set, a vial transfer apparatus, packaging, a medication container ID label marking element or coded disc, or coded ring to be affixed to the medication container. The information element can be applied to the tip portion (i.e., the portion of the medication container having the fluid outlet and a diameter smaller than or equal to the chamber of the medication container, etc.) or fluid outlet of the medication container.
The medication container and or the vial transfer apparatus can be enveloped in a sterile pouch (i.e., enclosure, etc.). The sterile pouch can contain information indicative of the encoded information on the information transfer element. The medication information transfer element can be part of a kit that also contains the vial and medication instructions for use. The kit can be manufactured complete by a pharmaceutical company including the medication in the vial and the information transfer apparatus. The kit can be packaged by a local pharmacy, a pharmaceutical repackaging operation or an in-hospital pharmacy and can include a pharmaceutical company packaged vial and the information applied to a fluid transfer apparatus.
In the pharmacy and/or pharmaceutical repackaging kit configuration the pharmacy can match and verify the medication information on the vial and vial packaging with the medication information on the transfer apparatus packaging and the information transfer element. The encoded information on the transfer apparatus can be positioned such that it can be read by a medication administration device when administering the medication to a patient without deliberate effort on behalf of a clinician to facilitate information transfer between the medication container and the medication administration device. Once matched and verified the pharmacy can join the vial and information transfer apparatus into a secondary package and label the kit. The secondary package can provide a tamper evident element providing assurance of maintaining the matched elements. The secondary package can contain pharmacy specific information including lot number, packaging date, medication expiration date, dosage, patient information and/or container serial number.
In a pharmacy and/or pharmaceutical repackaging operation, the read-write instrument can be provided for reading a medication identification code source and writing information to multiple targets with the medication identification information encoded on multiple medication containers. In this variation, a multi-dose medication container (vial, Act-O-Vial™, bag, bottle, ampoule, syringe, etc.) is provided to the pharmaceutical filler. Using the method, the pharmaceutical filler can encode multiple containers, or transfer elements, sub-dividing the contents of a multi-dose container into more than one dose administration sub-container. The multi-dose container information can be read and verified with an identification code. Then multiple sub-containers can be written (encoded) with sub-container information. The written sub-container information can contain the same or different information than the multi-dose medication container. The sub-container information can include any information useful for characterizing the contents of the sub-container (such as the data described above). If the sub-container is a syringe, the encoded information on the target can be positioned such that it can be read by a medication administration device when administering the medication to a patient without deliberate effort on behalf of a clinician to facilitate information transfer between the medication container and the medication administration device.
The encoded information can be selected from a group comprising: optically encoded information, optical image information, magnetically encoded information, radio frequency detectable information, and mechanically detectable information. The encoded information can include a unique identifier, NDC information, dose, concentration, package serial number, lot number, expiration date. The encoded information can be based on an industry standard representation of information content or a proprietary representation of the content.
The current subject matter provides many advantages. For example, by allowing for the automatic identification of the contents of medication containers (whether during administration of such medication or as part of a verification process during manufacture/preparation), medication administration errors can be greatly reduced. In addition, adverse effects from drug allergies and incompatible medications can be significantly minimized by providing a medication container that can be automatically identified. Providing a medication container labeled in a way that is automatically readable by a medication administration device without deliberate effort on the part of the clinician, greatly reduces the possibility of human error or that the label identification step will be skipped or adversely abbreviated in an effort to focus on immediate patient care needs. Lastly, proper record keeping can be maintained with regard to wasted medication (which is especially important with regard to controlled substances).
The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.
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:
Like reference symbols in the various drawings indicate like or similar elements.
The medication identification information 20 can be displayed on a variety of locations on an information target 8 (i.e., a medication container, etc.). For example, when the information target 8, the medication identification information 20 can be positioned on a tip of the syringe. More specifically, in some implementations, the medication identification information 20 can be placed on a tapered portion of the tip, a Luer lock fitting on the tip, and a portion of the tip interposed between the tapered portion and the cylindrical chamber of the syringe.
The current subject matter is applicable to a wide variety of medication containers. Examples of medication containers include: a pre-filled or empty needle-less syringe having a fluid outlet at a tip of the syringe, a vial having a fluid outlet corresponding to the stopper at the vial closure, a bag containing a premixed solution having a Luer fitting connector or an IV set spikeable port, an envelope (e.g., disposable, rigid, semi-rigid or flexible envelope, etc.) having an integral Luer fitting or tubing extended therefrom, a fluid transfer device used with medication vials having a luer fitting connector, and/or a fluid delivery tubing set having an integral luer fitting at one end of the tubing.
The medication code source 6 can be/include any one or more of a barcode (one or two dimensional), an optical image (e.g. picture, symbol, image, hologram, etc.), 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, human readable code, a machine readable code, a manually entered code or other codes that can be created to uniquely identify one or more of a medication's name, manufacturer, re-packager, distributer, strength (concentration), dosage form, dose instructions (whether generic for all patients or specifically prescribed for a particular patient), formulation, package form, package size, contained volume, package serial number, lot number, expiration date.
Additional complementary information can also be included within the medication code source 6 such as a reference to a database or document (via, for example, a URL, etc.) which can include additional information regarding the medication such as how it interacts with other medications and/or information regarding medications that are often administered along with the specified medication. As an example, before and/or coincident to the medication being administered, such complementary information may be accessed by a reader (whether at the point of administration or otherwise) so that additional information can be presented regarding the medication (including which medications should not be administered concurrently). In addition, in some implementations, it can be determined whether there is a possibility of an adverse reaction if the medication is delivered (whether via overmedication or interaction with previously delivered medications or due to some potential patient adverse condition). Such complementary information can also identify other medications that are often administered with the identified medication (especially in the case of complex protocols).
During use, the operator of read-write instrument 4 first determines which medication code source 6 is to be used and positions it in range of reader 10. Alternately, the operator can manually enter medication code source 6 information by using user interface 26. Secondly, the operator positions target 8 in range of writer 16. This positioning of target 8 may be a manual process or facilitated by automated equipment. The scanner element 12 of the reader 10 reads medication code source 6 and produces read information 14. Instrument control 24 receives read information 14 and prepares for a writing operation. Writer 16 receives read information 14 from instrument control 24 and writing element 18 of the writer 16 produces written information 20 to be written or deposited on target 8's fluid outlet 22. Writing element 18 can be one of a laser writer, a hot stamp, a printer, a magnetic encoder, an electronic data packet message, or a surface treatment facilitating optical, magnetic, electronic or proximity recognition. Once written, target 8 is encoded with information from medication code source 6.
As a first alternative, the writer 16 can deposit the encoded information on an adhesive backed element which can then be applied to target 8 (e.g., an RFID tag or other machine readable label applied to target). As a second alternative, writer 16 may apply a coded article such as a coded ring to target 8. As a third alternative the coded information or article can be radially written on the syringe surface 50 or take the form of coded disc 52 applied to surface 50.
Similar to
As a first alternative, the writer 16 can deposit the encoded information on an adhesive backed element which can then be applied to target 30 (e.g., an RFID tag or other machine readable label applied to target). As a second alternative, writer 16 may apply a coded article such as a coded disk 52 to target 30. As a third alternative the coded information or article can be radially written on the vial surface 54 in a pattern similar to disc 52.
Other variations of medication containers and information targets can be incorporated that use various forms of medication code source 6a to provide information about the contents of the container and different target 8a with alternate fluid outlet 22a configurations. Targets can be encoded as separate parts and then grouped with other parts as assemblies.
The apparatus and process depicted in
In a further implementation, vial 30 can be customized to provide a particular dosage of medication for a patient. Container 34 may be configured to hold a fraction of the entire volume of medication held in medication vial 30 as will be discussed later regarding
Step 1—Initialize instrument 4, locate medication code source 6a, initialize first reader 10; locate, scan and read medication code source 6a, and send medication code 6a to instrument control 24.
Step 2—Locate encoded element 6b or 22a, initialize second reader 40, scan and read encoded element, and send information to instrument control 24.
Step 3—Compare first read information (e.g., medication code 6a) to second read information (encoded element 6b or 22a) and verify information identity. Reject container or transfer element if there is not a match.
Step 4—Locate packaging element 46b, initialize writer 16, write verified information 44b, and repeat from step 1 thru step 4 if needed/desired.
The method and apparatus of
Step 1—Initialize instrument 4, locate medication code source 6, initialize first reader 10, locate, scan and read medication code source 6, and send medication code 6 to instrument control 24.
Step 2—Locate multi-dose vial 60, initialize second reader 40, scan and read multi-dose code 6a, and send information to instrument control 24.
Step 3—Compare first read information (e.g., medication code 6a) to second read information (code 6a) and verify information identity. Reject multi-dose container if there is not a match.
Step 4—Locate medication container, customize information 20 as required, initialize writer 16, write information 22A, and repeat from steps for additional containers B-E and information 22B-E as needed/desired. When all containers are encoded, END the process.
Step 1—Prepare empty containers by application of encoded information element and prepare medication for container filling. Empty medication containers are received and inspected for use. Identification ID Code element is received and prepared for application. The ID Code element is written (applied) to the empty container (syringe, vial, bag, etc.). Medication is received and the medication ID Code determined. The ID Code is associated with the medication.
Step 2—Empty encoded containers and coded medication are delivered to an assembly operation. Prior to filling the empty containers with medication, the identity of the medication ID Code can be verified to determine if the ID Code on the empty container is the same as that associated with the medication. If they are the same, proceed to the filling operation. Each and every medication container can be verified or a lot sample can be verified.
Step 3—Empty encoded containers and coded medication are prepared for the filling process. Medication is filled into the empty containers.
Step 4—After filling the empty containers with medication, the identity of the medication ID Code can be verified to determine if the ID Code on the filled container is the same as that associated with the medication. If the identity is the same, proceed to the packaging operation. If there is not identity, the filled containers are rejected.
Features and functions of a sample medication container encoded fluid outlet and the use of same by a medication injection site/medication administration device are 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 read-write encoding system.
In addition, while the foregoing examples are mainly directed to the preparation and administration of medication within medication containers, it will be appreciated that the same concepts can be applied to a medication wasting device. For example, a medication wasting device can be configured to receive a syringe containing a controlled substance and bearing an identifier such that the identifier 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. Pat. App. Ser. No. 61/358,937 entitled: “Medication Waste Collection Apparatus”, the contents of which are hereby fully incorporated by reference.
The subject matter described herein may be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. In particular, aspects of the subject matter described herein may 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 may 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 may 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 may 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 tangible/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 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 following claims.
This application claims priority to U.S. Pat. App. Ser. No. 61/349,878 filed on May 30, 2010 and entitled: “Medication Identification Encoding and Verification”, the contents of which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4650475 | Smith et al. | Mar 1987 | A |
4853521 | Claeys et al. | Aug 1989 | A |
4978335 | Arthur, III | Dec 1990 | A |
5011032 | Rollman | Apr 1991 | A |
5078683 | Sancoff et al. | Jan 1992 | A |
5279576 | Loo et al. | Jan 1994 | A |
5383858 | Reilly et al. | Jan 1995 | A |
5628309 | Brown | May 1997 | A |
5651775 | Walker et al. | Jul 1997 | A |
5692640 | Caulfield et al. | Dec 1997 | A |
5782814 | Brown et al. | Jul 1998 | A |
5792117 | Brown | Aug 1998 | A |
5873731 | Prendergast | Feb 1999 | A |
5984901 | Sudo et al. | Nov 1999 | A |
6019745 | Gray | Feb 2000 | A |
6123686 | Olsen et al. | Sep 2000 | A |
6192945 | Ford et al. | Feb 2001 | B1 |
6338200 | Baxa et al. | Jan 2002 | B1 |
6468424 | Donig et al. | Oct 2002 | B1 |
RE38189 | Walker et al. | Jul 2003 | E |
6626862 | Duchon et al. | Sep 2003 | B1 |
D481121 | Evans | Oct 2003 | S |
D485356 | Evans | Jan 2004 | S |
6685678 | Evans et al. | Feb 2004 | B2 |
6790198 | White et al. | Sep 2004 | B1 |
6960192 | Flaherty et al. | Nov 2005 | B1 |
7017623 | Tribble et al. | Mar 2006 | B2 |
7074209 | Evans et al. | Jul 2006 | B2 |
7115113 | Evans et al. | Oct 2006 | B2 |
7117041 | Engleson et al. | Oct 2006 | B2 |
7161488 | Frasch | Jan 2007 | B2 |
7236936 | White et al. | Jun 2007 | B2 |
7470266 | Massengale et al. | Dec 2008 | B2 |
7722083 | McCarthy et al. | May 2010 | B2 |
7727196 | Neer | Jun 2010 | B2 |
7834816 | Marino et al. | Nov 2010 | B2 |
7976508 | Hoag | Jul 2011 | B2 |
7991627 | Hutchinson et al. | Aug 2011 | B2 |
8035517 | Gibson | Oct 2011 | B2 |
8151835 | Khan et al. | Apr 2012 | B2 |
20020040208 | Flaherty et al. | Apr 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 |
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 |
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 |
20040104271 | Martucci et al. | Jun 2004 | A1 |
20040186437 | Frenette et al. | Sep 2004 | A1 |
20040204673 | Flaherty | Oct 2004 | A1 |
20050101905 | Merry | May 2005 | A1 |
20050106225 | Massengale et al. | May 2005 | A1 |
20050107923 | Vanderveen | May 2005 | A1 |
20050182358 | Veit et al. | Aug 2005 | A1 |
20050277890 | Stewart et al. | Dec 2005 | A1 |
20060079767 | Gibbs et al. | Apr 2006 | A1 |
20060079843 | Brooks et al. | Apr 2006 | A1 |
20060116639 | Russell | Jun 2006 | A1 |
20060122577 | Poulsen et al. | Jun 2006 | A1 |
20060144942 | Evans et al. | Jul 2006 | A1 |
20060226089 | Robinson et al. | Oct 2006 | A1 |
20060229551 | Martinez et al. | Oct 2006 | A1 |
20060258985 | Russell | Nov 2006 | A1 |
20060265186 | Holland et al. | Nov 2006 | A1 |
20070043335 | Olsen et al. | Feb 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 |
20070191787 | Lim et al. | Aug 2007 | A1 |
20070279625 | Rzasa et al. | Dec 2007 | A1 |
20070299421 | Gibson | Dec 2007 | A1 |
20080045930 | Makin et al. | Feb 2008 | A1 |
20080051937 | Khan et al. | Feb 2008 | A1 |
20080061153 | Hickle et al. | Mar 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 |
20080294108 | Briones et al. | Nov 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 |
20090149744 | Nemoto et al. | Jun 2009 | A1 |
20090157008 | Vitral | Jun 2009 | A1 |
20090159654 | Grimard | Jun 2009 | A1 |
20090294521 | de La Huerga | Dec 2009 | A1 |
20100065643 | Leyvraz et al. | Mar 2010 | A1 |
20100152562 | Goodnow et al. | Jun 2010 | A1 |
20100153136 | Whittacre et al. | Jun 2010 | A1 |
20100174266 | Estes | Jul 2010 | A1 |
20100262002 | Martz | Oct 2010 | A1 |
20100280486 | Khair et al. | Nov 2010 | A1 |
20100305499 | Matsiev et al. | Dec 2010 | A1 |
20110060198 | Bennett et al. | Mar 2011 | A1 |
20110111794 | Bochenko et al. | May 2011 | A1 |
20110112473 | Bochenko et al. | May 2011 | A1 |
20110112474 | Bochenko et al. | May 2011 | A1 |
20110220713 | Cloninger | Sep 2011 | A1 |
20110224649 | Duane et al. | Sep 2011 | A1 |
20110264069 | Bochenko | Oct 2011 | A1 |
20120037266 | Bochenko | Feb 2012 | A1 |
20120041355 | Edman et al. | Feb 2012 | A1 |
Number | Date | Country |
---|---|---|
29617777 | Dec 1996 | DE |
Number | Date | Country | |
---|---|---|---|
61349878 | May 2010 | US |