Injection site information cap

Abstract
A injection site information cap includes a housing, a cover portion, an engagement portion configured to couple to and cover an injection port of an injection site, and at least one information element on the cover portion that is positioned to be automatically sensed by at least one sensor of the injection site when the engagement portion is coupled to or is being coupled to the medication injection port. Related apparatus, systems, and techniques are also described.
Description
FIELD

The subject matter described herein relates to an injection site information cap and method for use in providing information to recordkeeping systems to automatically document caregiver identification, patient care activity, and/or procedural steps in the use of and/or care of a medication injection site.


BACKGROUND

Many health care procedures involve IV medication administrations. The type of medication and timing of administration are important to record in order to provide healthcare providers real-time information on the conduct of the procedure and the completion of a medical record. Some protocols require quick medication administrations with limited time for documentation and record keeping. Others require completion and verification of medication administration manually to ensure proper patient care and accounting for use of medications.


Injectable medications and fluids are frequently utilized by healthcare providers (caregivers) in the care of patients in the hospital, in pre-hospital emergency medical services (EMS) and at alternate care sites (including skilled nursing facilities, home health and hospice settings). Caregivers can include medical doctors, registered nurses, EMS paramedics, dentists and other licensed healthcare practitioners. Accurate documentation of what, when and how much medication and/or IV fluid is given to a patient is required by healthcare institutions, governmental agencies and regulatory oversight agencies. This is especially true when the IV fluid being administered to the patient is a medication or blood product. The type of IV fluid and the timing of administration are important to record in order to provide healthcare providers real-time information on the conduct of the procedure and the completion of a medical record. Some protocols require quick IV fluid administrations with limited time for documentation and record keeping. Others require completion and verification of manually administered IV fluids to ensure proper patient care and accounting for use of IV fluids.


Additionally, to ensure proper patient safety and limit exposure to catheter-related bloodstream infections (CRBSI), vascular access ports (injection sites) require careful disinfection and careful management of the patient's IV site for patency. Absent these activities, needleless injection sites can become contaminated and patient vascular access can become infiltrated or blocked. When these situations occur, patient safety is compromised resulting in infection, pain, longer hospital stays and even death. Hospital costs for continued patient care increase and are not reimbursed by third party payers.


New automated documentation systems for medication administrations will likely help in the tracking of medication injections, but none have addressed the documentation of proper IV site care and the management of needleless injection sites for infection control or IV site for patency. Manual use of alcohol swabs or sterile caps containing a disinfectant solution are gaining popularity for disinfecting IV injection sites and controlling CRBSI. When caps are left attached to IV luer access needless valves they can disinfect and protect the IV site. To date, these activities are often not documented, rarely time tracked and even less likely to be identified by caregiver.


Other patient care activity and procedural steps such as obtaining lab samples, assisting in respiratory therapy, dietary management also require timely documentation. Manual documentation often results in accuracy errors, missed notations and undocumented activity due to fast paced patient care with limited resources. A better system could result in less error, increased billing accuracy, reduced paperwork and more time for caregivers to focus on patient care. Tracking of who did what and when at the point of care can be improved.


SUMMARY

In one aspect, an injection site information cap includes a housing, a cover portion, an engagement portion configured to couple to and cover an injection port of an injection site and at least one information element on the cover portion that is positioned to be automatically sensed by at least one sensor of the injection site when the engagement portion is coupled to or is being coupled to the medication injection port.


The engagement portion can include a female luer lock thread configured to be coupled to a male luer lock thread on the injection port.


The at least one information element can be encoded with one or more of: mechanically encoded information, magnetically encoded information, a near field communication (NFC) tag, and a radio frequency identification (RFID) tag.


The at least one information element can include optically encoded information. The optically encoded information can include at least one bar code. The at least one bar code can be sensed by the at least one sensor as the cover portion is circumferentially rotated or translated linearly on the axial centerline of the luer lock.


The injection site information cap can include a disinfectant to disinfect the injection port upon the coupling of the engagement portion with the injection port. The engagement portion can be further configured to seal the injection port of the injection site.


The injection port can be fluidically coupled to a patient and/or to a fluid wasting reservoir.


The information element can encapsulate data characterizing one or more of: a disinfection state of the injection port, a caregiver identification, an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient.


Some or all of the housing can be color coded with one of a plurality of color categories. Each color category can characterize one or more of: caregiver identification, a patient care procedural activity, a laboratory sample, a state of the injection port, a fluid injected into the injection port, and a state of a patient. The at least one sensor or a different sensor can, in some variations, detect the color. In addition, in some variations, at least the information element is color coded with one of a plurality of color categories, each color category characterizing one or more of: care giver identification, a patient care procedural activity, a laboratory sample, a state of the injection port, a fluid injected into the injection port, and a state of a patient.


The information element can be affixed to an outer surface of the cover portion or it can be integral to an outer surface of the cover portion.


In a further aspect, an injection site information cap can include multiple engagement portions. For example, a medication injection site can comprise a housing including a first engagement portion on the housing configured to couple to and cover a first injection port of a first injection site. At least one first information element on an outer surface of the first engagement portion of the housing can be positioned to be automatically sensed by at least one first sensor of the first injection site when the first engagement portion is coupled to or is being coupled to the first injection port, a second engagement portion on the housing can be configured to couple to and cover a second injection port of a second injection site, and at least one second information element on an outer surface of the second engagement portion of the housing can be positioned to be automatically sensed by at least one second sensor of the second injection site when the second engagement portion is coupled to or is being coupled to the second injection port.


The at least one of the first engagement portion and the second engagement portion can comprises a female luer lock thread configured to couple to a male luer lock thread on the injection port. The at least one first information element and the at least one second information element can be encoded with one or more of: mechanically encoded information, magnetically encoded information, a near field communication (NFC) tag, and a radio frequency identification (RFID) tag. The at least one second information element can be optically encoded information. The optically encoded information can be at least one bar code. The at least one bar code can be sensed by the at least one sensor as the housing is circumferentially rotated.


The information cap can further comprise: a disinfectant to disinfect at least one of the first injection port upon the coupling of the first engagement portion to the first injection port. The at least one of the first injection port and the second injection port can be fluidically coupled to a patient. The at least one of the first injection port and the second injection port can be fluidically coupled to a fluid wasting reservoir.


The injection site information cap can include one or more of the at least one first information element and the at least one second information element to encapsulate data characterizing one or more of: a disinfection state of the injection port, a caregiver identification, an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient. The information cap can include at least a portion of the housing, and/or the information element, to be color coded with one of a plurality of color categories, each color category characterizing one or more of: caregiver identification, a patient care procedural activity, a laboratory sample, a state of the injection port, a fluid injected into the injection port, and a state of a patient.


The one or more of the at least one first information element and the at least one second information element can be affixed to an outer surface of the housing. The at least one first information element and the at least one second information element can be integral to an outer surface of the housing. The at least one of the first engagement portion and the second engagement portion can be further configured to seal and/or cover the injection port of the injection site. The first injection site and the second injection site can be physically connected to each other.


In some variations, the at least one first information element is different from the at least one second information element while in other variations the elements are the same (identical). Each engagement portion can have identical features such as disinfectant or they can differ (one side has disinfectant while the other does not). The housing can be color coded in different manners similar to a single engagement portion injection cap.


The first engagement portion can be positioned opposite the second engagement portion. In other variations, the first engagement portion is positioned at an angle or otherwise askew as compared to a center line of the second engagement portion. In other variations, the housing can be flexible.


In a further interrelated aspect, an apparatus includes a first engagement portion on the housing configured to cover a injection port, at least one first information element on an outer surface of the first engagement portion of the housing positioned to be automatically sensed by at least one first sensor of the injection site when the first engagement portion is coupled to or is being coupled to the injection port; a second engagement portion on the housing configured to cover the injection port, and at least one second information element on an outer surface of the second engagement portion of the housing positioned to be automatically sensed by at least one sensor of the injection site when the second engagement portion is coupled to or is being coupled to the injection port.


The injection site information caps as described herein can be used in connection with various methods. For example, one method can include receiving information from a medication delivery apparatus characterizing at least one information element on a cap covering an injection port of the medication delivery apparatus, associating the received information with data comprising one or more of: a disinfection state of the injection port, a caregiver identification, an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient, and promoting the associated data.


The medication delivery apparatus (injection site) can include a housing, a fluid conduit at least partially extending within the housing and configured to deliver medication within a medication container to the patient, an injection port extending from an external surface of the housing and configured to be coupled to a fluid outlet of the medication container (the medication port being fluidically and directly coupled to the fluid conduit), and at least one sensor disposed within the housing to sense the at least one information element on the information cap. In some variations, the medication delivery apparatus can also include a transmitter within the housing to wirelessly transmit information generated by the at least one sensor to a remote data collection system, and a self-contained power source within the housing powering the at least one sensor and the transmitter.


Promoting the associated data can include one or more of: displaying the associated data, storing the associated data into a physical storage device, loading the associated data into memory, and transmitting the associated data to a remote computing system.


Computer program products are also described that comprise nontransitory computer readable media storing instructions, which when executed one or more data processor of one or more computing systems, causes at least one data processor to perform operations herein. Similarly, computer systems are also described that may include one or more data processors and a memory coupled to the one or more data processors. The memory may temporarily or permanently store instructions that cause at least one processor to perform one or more of the operations described herein. In addition, methods can be implemented by one or more data processors either within a single computing system or distributed among two or more computing systems. Such computing systems can be connected and can exchange data and/or commands or other instructions or the like via one or more connections, including but not limited to a connection over a network (e.g. the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, or the like), via a direct connection between one or more of the multiple computing systems, etc.


The subject matter described herein provides many advantages. For example, the current subject matter allows for compact injection port systems that automatically identify activity at the injection site. The fluid injection port is sufficiently small to be placed on a standard IV line (and to be self-supporting) allowing it to be used in multiple situations including on-site paramedic treatments, during ambulance delivery of patients, as well as medical facilities such as emergency rooms/intensive care units/operating rooms/general care. Moreover, as medical staff (e.g., doctors, nurses, paramedics, etc.) are accustomed to handling Y-sites on IV lines and the current subject matter requires little, if any, behavior modifications while allowing for intelligent logging of patient care activities within normal workflow. In addition, the compact nature of the fluid injection port obviates the need for a larger tabletop or cradle bar code unit which can be cumbersome during code blue or other emergency events and which can require much needed space (displacing other required equipment). In addition, the current subject matter utilizes a wireless interface and does not require wires for communication of information to a data collection system which could interfere with or complicate patient care activity. Data received by the data collection system can be actively displayed in real-time providing clearly visible information to the medical staff keeping all informed and up-to-date. Furthermore, the current subject matter reduces manual record keeping and other activities that can tend to detract from the needed attention to a patient. Automated record keeping provides accurate records and frees up the health care provider's time enabling improved patient care.


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.





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 depicts an intelligent injection site housing directly coupled to a “Y” site of an IV fluid delivery tubing set;



FIG. 2 depicts a medication container with an information element attached;



FIG. 3 illustrates a medication container attached to an intelligent injection site housing;



FIG. 4 depicts an injection site information cap with an information element attached;



FIG. 5 depicts an information cap about to be attached to intelligent injection site;



FIG. 6 illustrates an information cap fully coupled to an intelligent injection site;



FIGS. 7 & 8 illustrate two alternative information caps with extended surfaces;



FIG. 9 illustrates two alternatives of applying an information element to an injection site information cap;



FIG. 10 illustrates a double ended information cap; and



FIG. 11 illustrates several possible packaging configurations.





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


DETAILED DESCRIPTION

This application relates to each of the following applications, which are all entitled “Medication Injection Site and Data Collection System”: U.S. patent application Ser. No. 13/777,964 filed Feb. 26, 2013, which is a continuation-in-part of U.S. patent application Ser. No. 13/777,831 filed on Feb. 26, 2013, which in turn is a continuation-in-part of U.S. patent application Ser. No. 12/938,300 filed on Nov. 2, 2010, which in turn is a continuation-in-part of U.S. patent application Ser. No. 12/765,707 filed on Apr. 22, 2010, which in turn is a continuation-in-part of U.S. patent application Ser. No. 12/614,276 filed on Nov. 6, 2009; and additionally, priority is also claimed to U.S. Pat. App. Ser. No. 61/370,974 filed on Aug. 5, 2010. Each of the aforementioned patent applications are hereby fully incorporated by reference.


Additionally, this application relates to each of the following applications, which are entitled “Medication Container Encoding, Verification, and Identification”: U.S. patent application Ser. No. 13/671,752 filed Nov. 8, 2012, which is a continuation-in-part of U.S. patent application Ser. No. 13/149,782 filed on May 31, 2011. Each of the aforementioned patent applications are hereby fully incorporated by reference.



FIG. 1 depicts an intelligent injection site 4 directly coupled to a “Y” site of an IV fluid delivery tubing set 11. Connection of an intelligent injection site can be to other injection sites such as stopcocks, manifolds, “T” sites, venous access devices, catheters, etc. Details of intelligent injection site 4 are discussed in the referenced patent applications entitled “Medication Injection Site and Data Collection System”. Tubing set 11 is attached at one end to a fluid source for delivery of fluids to a patient. Distal end of tubing set 11 is attached to vascular access device 16 (needle, catheter, etc.). Located in between each end of tubing set 11 is a “Y” site providing and injection site for additional fluids and medications to be administered to a patient. Fluid containers can be coupled to intelligent injection site 4 by inlet 13 and luer lock threads 56. Outlet 14 of intelligent injection site 4 can be coupled to the “Y” site providing for fluid delivery to a patient into inlet 13, through conduit 10 and out of output 14. Intelligent injection site 4 can include emitter 31 and identification sensor 18 positioned such that when an information element 24 is in the field of view or within a predefined distance, circuit 30 can image and transmit 36 information contained on information element 24 to data collection system 6. Data collection system 6 can transmit 50 data collected to medical information system 52. Additionally, intelligent injection site 4 can include fluid delivery sensor 60, power source 19 and indicator 35.



FIG. 2 depicts a medication container 20 (syringe example) with an added information element 24 forming an encoded medication container 33. Information element 24 can be a label for example and can contain encoded information 12. Encoded medication container 33 can contain medication 22 for injection into a medication injection site. Medication container 33 can include outlet 16 to deliver medication 22 to a medication injection site. Details of information element 24 and its coupling to medication container 33 are discussed in the referenced patent applications entitled “Medication Container Encoding, Verification, and Identification”.



FIG. 3 illustrates system 3 with an encoded medication container 33 attached to housing 5 of an intelligent injection site 4. Fluid outlet 16 of medication container 33 can be coupled to fluid inlet 13 of intelligent injection site 4. Coupling can automatically activate emitter 31 and identification sensor 18 to read information element 24. Data from information element 24 can be transmitted 36 by transmitter 34 to data collection system 6. Data collection system 6 can identify, display, time stamp and record the information content of information element 24. Medication container 33 can expel medication 22 through conduit 10, through outlet 14 and into an injection site coupled to a patient. Fluid delivery sensor 60 (not shown) can measure the expelled fluid 22 and transmit 36 data to data collection system 6. Data collection system 6 can display, time stamp and record the data from fluid delivery sensor 60.



FIG. 4 depicts an injection site cap 100 that can include information element 24 forming information cap 200. The injection site information cap 200 can have a shape and size configured to couple to and cover (and in some cases seal) an injection port. Injection site information cap 200 can include luer lock threads 154 on the inner diameter. Additionally, injection site information cap 200 can include a disinfectant 102 to disinfect an injection site (“Y” site) on IV tubing set 11 as shown in FIG. 1. Disinfectant 102 can be 70% alcohol or any other type of IV site disinfectant. Injection site information cap 200 can limit contact with injection site 4 fluid inlet 13 to only the surface of housing 5 (fluid inlet surface 13 and/or external threads 56) and not enter the fluid pathway.


In addition to system 3 for encoded medication containers as shown in FIG. 3, FIG. 5 depicts a non-medication container information system 2. System 2 can include information element 24, information cap 200, intelligent injection site 4 and data collection system 6. Information cap 200 can be made from plastic (polycarbonate, polystyrene, polyvinylchloride, etc.), can be provided sterile and can be enclosed in a sealed foil package for single use. Information cap 200 can attach to inlet 13 by engaging internal luer lock threads 154 with external threads 56 on intelligent injection site 4. Information cap 200 can be rotated clockwise to engage luer lock threads 154 and 56. Information cap 200 can be rotated counter clockwise to disengage luer lock threads 154 and 56 and remove information cap 200. Information cap 200 can be a push-on type without luer lock threads 154. Information cap 200 can cover, protect and/or disinfect inlet 13.


Information cap 200 can be colored to designate a category. The color can be part of housing 5, part of information element 24 (background color) or part of data element 12. Categories can include any assigned color or type. For example color assignments could be: red=lab sample taken, orange=caregiver ID, yellow=medication given, green=billing charge, blue=physical therapy activity, violet=lab sample taken, white=sedation activity. Other colors and/or categories can be included. The color can be detected by identification sensor 18 and transmitted to the data collection system in addition to the information contained in the information element. The information can be detected by identification sensor 18 when a specific wavelength light (ultraviolet, infrared, etc), a specific RF or magnetic frequency, or a combination of frequency and wavelength is emitted from emitter 31.


Information cap 200 can be used with intelligent injection site 4 for caregiver identification during medication waste disposal. In this use case, intelligent injection site 4 can be connected to a medication waste disposal receptacle. Information cap 200 can contain caregiver ID information and document who and when medication waste is disposed. This can be followed by an encoded medication container and injection of waste medication into the receptacle. Fluid delivery sensor 60 can measure the volume of waste disposed. A second caregiver can verify waste disposal by immediately following waste disposal with the attachment of a second information cap 200 having a different caregiver ID. Information detected on caregivers information caps 200 and encoded medication container waste disposed volume can be transmitted 36 to data collection system 6, time stamped and transmitted 50 to medical information system 52.



FIG. 6 illustrates system 2 with information cap 200 fully coupled to intelligent injection site 4. Coupling information cap 200 to intelligent injection site 4 can automatically activate emitter 31 and identification sensor 18 to read information element 24. Data from information element 24 can be transmitted 36 by transmitter 34 to data collection system 6. Data collection system 6 can identify, display, time stamp and record the information content of information element 24. Data collection system 6 can display, time stamp and record the data from identification sensor 18. Data collection system 6 can transmit 50 this data to medical information system 52.


Information element 24 on information cap 200 can be any one or more of: mechanically encoded information, magnetically encoded information, a near field communication (NFC) tag, a radio frequency readable information (RFID tag). The information element 24 can also or alternatively comprise optically encoded information and the identification sensor 18 can comprise an optical emitter and an optical detector to read the optically encoded information. The identification sensor 18 can include an optical emitter LED to illuminate the information element 24 and an optical detector such as a camera (charge coupled device—CCD). The identification sensor 18 can read information from the information element 24 as a result of relative motion of the information cap relative to injection site 4. The identification sensor 18 can read information from the information element 24 in response to mechanically coupling the information cap 200 to the injection site 4.


Information cap 200 can carry an information element 24 that provides detectable information indicative of an activity performed by a caregiver or a patient. The activity can be any one or more of: disinfection of the injection site, caregiver identification (name, ID number, employee number), a procedural step performed (IV site visual assessment, a surgical procedure step, an intensive care unit activity, an emergency medical services {EMS} activity), confirmation of waste disposal (unused controlled substances, contaminated waste, etc.), other patient care activity such as obtaining a lab sample from a patient, assisting in respiratory therapy of a patient, dietary management of a patient, and many other patient care activities at home, in the field, or in a hospital environment where recordation is appropriate. The data encapsulated by element 24 can be detected by an intelligent injection site and processed either locally or by transmitting to a remote computing system.


The identification sensor 18 can include an optical emitter/detector pair 31 that detects encoded information contained on information element 24 (a sleeve or label wrapped around injection site information cap 100). The identification sensor 18 can comprise a plurality of sensors to detect information element 24. In some variations, the identification sensors can be sensors such as optical, magnetic, mechanical, conductive, switchable RFID and/or proximity sensors. In other variations, identification sensor 18 can be optical and can include an illumination source (emitter) such as an LED and a detection source (detector) such as a camera (CCD). Sensor circuit 30 can provide signal processing and connects identification sensor 18 to transmitter 34. The identification sensor 18 can be directly coupled to power source 19.



FIGS. 7 & 8 illustrate two alternative information caps 200 with extended surfaces to assist users in attaching and detaching information cap 200 from/to injection site 4. FIG. 7 illustrates an extended cap housing with a stripped grip section 104. FIG. 8 illustrates a narrower extended surface 106 forming a finger grip handle. Additionally, information element 24 can include human readable information 26 (“Disinfected”) to enable a user to verify the information content prior to information cap 200 use.



FIG. 9 illustrates two alternatives of applying information element 24 to injection site cap 100. As shown at the top, information element 24 can slide over (110) and attach to injection site cap 100 forming assembled information cap 200. On the bottom, information element 24 can wrap around (120) and attach to injection site cap 100 forming assembled information cap 200. Information element 24 can be a label or any one of: an optical image (1 dimensional barcode, 2 dimensional barcode, symbol, image or picture), a magnetic image (magnetic strip on an identification card/badge/ID tag), a Near Field Communication (NFC) tag, an RFID tag, and/or mechanically encoded information. Details are included in aforementioned patent applications.



FIG. 10 depicts an information cap 400 with two active ends (A and B). Injection site cap 300 can have two ends A and B. Each end can have disinfectant 102 and luer lock threads 154. Injection site cap 300 can have two information elements (24A and 24B), one at each end to form injection site information cap 400. Information element 24A can be the same as information element 24B to allow multiple uses (e.g. two injection site disinfections). Information element 24A can be different from information element 24B allowing two different activities to be recorded. One could be “Disinfected” (24A) and the other could be a procedural step “Procedure X” (24B). The sequence and timing of use can be determined by the user. For example: End A can be used prior to a medication injection to provide information 24A (disinfection of the injection site). A medication can then be administered using an encoded syringe (see FIG. 3). End B can be used to provide information 24B (document the procedural step “X”). End B can remain coupled to the intelligent injection site 4 to protect it from contamination. The data collection system 6 can record and timestamp each information element (24A and 24B) as well as the medication administration. Maintaining End B coupled to the injection site can be recorded by the data collection system (“site protected”, End B=not removed). At a later time, when End B is removed from the injection site, the injection site can be recorded as unprotected. This same recordation can be completed using single ended information cap 200. It will be appreciated that information cap 400 can have more than two active ends. In some variations, the housing of information cap 400 can be flexible and optionally elongated.



FIG. 11 illustrates two methods of packaging and sealing the open end of information cap 200 (or 400). To the left is a simple peel open tab foil/poly seal 108. To the right is a foil/poly sealed pouch 109 with a tare open strip. Any number of other methods of packaging and sealing information cap 200 can be envisioned. Each method can protect information cap 200 internally prior to use, maintain sterility and contain the disinfectant solution.


Aspects of the subject matter described herein can be embodied in systems, apparatus, kits (e.g., kits with the medication injection site being enclosed therein), 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, which can also be referred to programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logical programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device, such as for example magnetic discs, optical disks, memory, and Programmable Logic Devices (PLDs), used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. The machine-readable medium can store such machine instructions non-transitorily, such as for example as would a non-transient solid state memory or a magnetic hard drive or any equivalent storage medium. The machine-readable medium can alternatively or additionally store such machine instructions in a transient manner, such as for example as would a processor cache or other random access memory associated with one or more physical processor cores.


To provide for interaction with a user, the subject matter described herein can be implemented on a computer having a display device, such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, such as for example visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including, but not limited to, acoustic, speech, or tactile input. 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.


The subject matter described herein may be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user may interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.


The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.


The subject matter described herein can be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. 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. 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 subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. In addition, the logic flow(s) depicted in the accompanying figures and/or described herein do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Other implementations may be within the scope of the following claims.

Claims
  • 1. A system comprising: an injection site including an injection port, wherein the injection site includes a fluid pathway, a first sensor, and a transmitter within a housing; anda first cap including a disinfectant and at least one first information element,wherein the at least one first information element encapsulates data characterizing a disinfection state of the injection port of the injection site,wherein the first cap is configured to removably couple to and cover the injection port of the injection site,wherein the first sensor is configured to automatically sense the data encapsulated by the at least one first information element in response to coupling of the first cap to the injection port,wherein the transmitter is configured to transmit the sensed data to a remote computing system, andwherein the system further comprises:a medication container containing a medication for injection into the injection site, wherein the medication container is not connected to the first cap, wherein the medication container is configured to removably couple to the injection port of the injection site separate from the first cap, wherein the medication container includes at least one second information element different than the at least one first information element, wherein the at least one second information element encapsulates data including information associated with the medication in the medication container, wherein the first sensor is configured to automatically sense the data encapsulated by the at least one second information element in response to coupling of the medication container to the injection port, and wherein the transmitter is configured to transmit the information associated with the medication in the medication container to the remote computing system.
  • 2. The system of claim 1, wherein the transmitter includes a wireless transmitter.
  • 3. The system of claim 1, wherein the injection site further includes a self-contained power source within the housing that powers the first sensor and the transmitter.
  • 4. The system of claim 1, wherein the at least one first information element further encapsulates data including information associated with a first caregiver identification.
  • 5. The system of claim 4, wherein the at least one first information element further encapsulates data including information associated with at least one of: an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient.
  • 6. The system of claim 4, further comprising: a second cap configured to removably couple to and cover the injection port of the injection site, wherein the second cap includes at least one further information element, wherein the at least one further information element encapsulates data including information associated with a second caregiver identification different than the first caregiver identification, wherein the first sensor is configured to automatically sense the data encapsulated by the at least one further information element in response to coupling of the second cap to the information port, and wherein the transmitter is configured to transmit the information associated with the second caregiver identification to the remote computing system.
  • 7. The system of claim 6, wherein the second cap includes the disinfectant, and wherein the at least one further information element further encapsulates data characterizing the disinfection state of the injection port.
  • 8. The system of claim 6, wherein the at least one further information element further encapsulates data including information associated with at least one of: an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient.
  • 9. The system of claim 1, wherein the injection site further includes a second sensor within the housing, wherein the second sensor is configured to sense a volume of the medication expelled through the fluid pathway, and wherein the transmitter is configured to transmit information associated with the volume of the medication expelled through the fluid pathway to the remote computing system.
  • 10. The system of claim 1, further comprising: the remote computing system, wherein the remote computing system is configured to identify, display, time stamp, and record the data encapsulated by the at least one first information element that characterizes the disinfection state of the injection port, and wherein the remote computing system is configured to transmit the data to a medical information system.
  • 11. The system of claim 1, wherein the at least one first information element is colored to designate a category, wherein the first sensor is configured to detect the color of the at least one first information element, and wherein the transmitter is configured to transmit information associated with the detected color to the remote computing system.
  • 12. A system comprising: an injection site including an injection port, wherein the injection site includes a fluid pathway, a first sensor, and a transmitter within a housing; anda first cap including a disinfectant and at least one first information element,wherein the at least one first information element encapsulates data characterizing a disinfection state of the injection port of the injection site,wherein the first cap is configured to removably couple to and cover the injection port of the injection site,wherein the first sensor is configured to automatically sense the data encapsulated by the at least one first information element in response to coupling of the first cap to the injection port,wherein the transmitter is configured to transmit the sensed data to a remote computing system,wherein the at least one first information element further encapsulates data including information associated with a first caregiver identification,wherein the at least one first information element further encapsulates data including information associated with at least one of: an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient, andwherein the system further comprises:a second cap configured to removably couple to and cover the injection port of the injection site, wherein the second cap includes at least one second information element, wherein the at least one second information element encapsulates data including information associated with a second caregiver identification different than the first caregiver identification, wherein the first sensor is configured to automatically sense the data encapsulated by the at least one second information element in response to coupling of the second cap to the information port, and wherein the transmitter is configured to transmit the information associated with the second caregiver identification to the remote computing system.
  • 13. The system of claim 12, wherein the second cap includes the disinfectant, and wherein the at least one second information element further encapsulates data characterizing the disinfection state of the injection port.
  • 14. The system of claim 12, wherein the at least one second information element further encapsulates data including information associated with at least one of: an identification of a patient, a procedural step performed in connection with care of the patient, a state of waste disposal, a lab sample, respiratory management for the patient, and dietary management for the patient.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. Utility patent application Ser. No. 15/352,897 filed Nov. 16, 2016, which is a continuation application of U.S. Utility patent application Ser. No. 13/802,231 filed Mar. 13, 2013 (now U.S. Pat. No. 10,143,830), the entire disclosures of each of which are herein incorporated by reference.

US Referenced Citations (448)
Number Name Date Kind
1614703 Delory Nov 1898 A
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
5190534 Kendell Mar 1993 A
5247826 Frola Sep 1993 A
5279576 Loo et al. Jan 1994 A
5317506 Coutre et al. May 1994 A
5338157 Blomquist Aug 1994 A
5383858 Reilly 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 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 Jul 1998 A
5782814 Brown et al. Jul 1998 A
5792117 Brown Aug 1998 A
5792120 Menyhay 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
6028433 Cheiky-Zelina 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 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
6585691 Vitello Jul 2003 B1
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 Khuri-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 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
7119689 Mallett 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 May 2008 B1
7375737 Botten et al. May 2008 B2
7384410 Eggers et al. Jun 2008 B2
7442181 Schubert et al. Oct 2008 B2
7452349 Miyahara Nov 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
D607941 Langan et al. Jan 2010 S
7645258 White et al. Jan 2010 B2
7668731 Martucci Feb 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 Tennican 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
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
8137303 Stout Mar 2012 B2
8140349 Hanson et al. Mar 2012 B2
8151835 Khan et al. Apr 2012 B2
8172082 Edwards May 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 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
8808637 Ferlic Aug 2014 B2
9216440 Ma Dec 2015 B2
9283369 Ma Mar 2016 B2
9931498 Bochenko Apr 2018 B2
20010020148 Sasse et al. Sep 2001 A1
20010049608 Hochman Dec 2001 A1
20010056258 Evans Dec 2001 A1
20020040208 Flaherty 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
20020161460 Noguchi Oct 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
20030160698 Andreasson et al. Aug 2003 A1
20030164401 Andreasson et al. Sep 2003 A1
20030174326 Rzasa et al. Sep 2003 A1
20030199897 Boecker Oct 2003 A1
20030220599 Lundtveit Nov 2003 A1
20040051368 Caputo 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
20040111078 Miyahara Jun 2004 A1
20040179051 Tainer et al. Sep 2004 A1
20040179132 Fujino et al. Sep 2004 A1
20040186437 Frenette 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
20050147524 Bousquet Jul 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
20050197646 Connell Sep 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
20060212306 Mallett 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
20070094303 Zwingenberger Apr 2007 A1
20070100316 Traxinger May 2007 A1
20070112333 Hoang May 2007 A1
20070129708 Edwards et al. Jun 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
20070286764 Noguchi Dec 2007 A1
20070293818 Stout et al. Dec 2007 A1
20070293830 Martin Dec 2007 A1
20070299421 Gibson Dec 2007 A1
20080009783 Branderburger et al. Jan 2008 A1
20080015492 Biesel Jan 2008 A1
20080027399 Harding et al. Jan 2008 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
20080116908 Potyrailo et al. May 2008 A1
20080118141 Sommer et al. May 2008 A1
20080125724 Monroe May 2008 A1
20080147047 Davis et al. Jun 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
20080319795 Poteet Dec 2008 A1
20090008393 Howlett et al. Jan 2009 A1
20090012448 Childers Jan 2009 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
20090099552 Levy 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
20090149744 Nemoto et al. Jun 2009 A1
20090156931 Nemoto et al. Jun 2009 A1
20090157008 Vitral Jun 2009 A1
20090159654 Grimard Jun 2009 A1
20090171297 Smith et al. Jul 2009 A1
20090200185 Follman et al. Aug 2009 A1
20090259176 Yairi 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
20100010443 Morgan Jan 2010 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
20100056975 Dale et al. Mar 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
20100140342 Deshays Jun 2010 A1
20100145165 Merry Jun 2010 A1
20100145721 Deshays Jun 2010 A1
20100152562 Goodnow et al. Jun 2010 A1
20100153136 Whittacre et al. Jun 2010 A1
20100174266 Estes Jul 2010 A1
20100179417 Russo Jul 2010 A1
20100204659 Bochenko et al. Aug 2010 A1
20100245056 Braun Sep 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
20110054440 Lewis Mar 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
20110284024 Trebella et al. Nov 2011 A1
20110313349 Krulevitch et al. Dec 2011 A1
20110315611 Fulkerson et al. Dec 2011 A1
20110317004 Tao 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
20120325330 Prince et al. Nov 2012 A1
20120323208 Bochenko et al. Dec 2012 A1
20130018356 Prince et al. Jan 2013 A1
20130030348 Lauer Jan 2013 A1
20130105568 Jablonski 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
20130245604 Kouyoumjian Sep 2013 A1
20130327822 Keefe et al. Dec 2013 A1
20140039383 Dobbles et al. Feb 2014 A1
20140060729 Srnka et al. Mar 2014 A1
20140142975 Keefe et al. May 2014 A1
20150204705 Forster et al. Jul 2015 A1
20150211904 Forster Jul 2015 A1
20160015885 Pananen Jan 2016 A1
Foreign Referenced Citations (16)
Number Date Country
29617777 Jan 1997 DE
1980974 Oct 2008 EP
2183046 Nov 1989 GB
2504288 Jan 2014 GB
2504295 Jan 2014 GB
2504297 Jan 2014 GB
S63260523 Oct 1988 JP
H1176380 Mar 1999 JP
2009219700 Oct 2009 JP
2009537250 Oct 2009 JP
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
20190366071 A1 Dec 2019 US
Continuations (2)
Number Date Country
Parent 15352897 Nov 2016 US
Child 16541122 US
Parent 13802231 Mar 2013 US
Child 15352897 US