Patent Grant
12165763
Pharmaceutical items (for example, drugs, diluents, medical and surgical supplies, gauze, scissors, needles, labels, baggies, bandages, packaging, vial, syringes, and/or other items that the pharmacy is responsible for), such as medications (for example, drugs, diluents, etc., in solid or liquid form), that have left a pharmacy of a medical care facility are to be managed closely to conform to regulatory guidelines regarding use and waste, to avoid misadministration and diversion, and to ensure appropriate inventory management and patient billing. In this context, medical care providers administer medications received from the pharmacy or removed from a crash cart or other pharmaceutical item storage unit. In some cases, prior to, or as part of, administration, the medical care providers transfer one or more medications from one medicinal container (for example, a vial, syringe, etc.) to another medicinal container and/or combine multiple medications into one medicinal container. As part of the transfer, the medical care provider prepares a handwritten label for the new medicinal container or new combination of medications in order to identify and track it throughout its lifecycle within the medical care facility. In addition, the medical care provider is responsible for returning unused medications (including any medications in the new medicinal container) from the original set of assigned pharmaceutical items, or reporting the administration, use, or waste of the medications, to the pharmacy for inventory management, billing, and regulatory control.
System and methods are described herein for querying or reading machine-readable data from labels associated with medicinal containers, generating new labels with machine-readable data, and tracking the administration, waste, and return of medications in a medical care facility. Although various aspects of the disclosure will be described with regard to examples and embodiments, one skilled in the art will appreciate that the disclosed embodiments and examples should not be construed as limiting.
Parent/Child Medicinal Containers and Medications
In the present disclosure, reference is made to medicinal containers (which may also be referred to as medicinal packages), including parent and child medicinal containers, and medications, including parent and child medications. Examples of medicinal containers include, but are not limited to, vials, ampoules, IV bags, syringes, or other containers configured to store a medication, and the like.
A child medication can refer to a medication that results from an action, such as a transfer of a medication or combination of two or more medications. A parent medication can refer to the medication used in the action, such as a medication prior to combination with another (parent) medication or transfer. In addition, a child medicinal container can refer to a medicinal container that stores the child medication and/or a medicinal container into which medications are added and a parent medicinal container can refer to a medicinal container that stores parent medications and/or a medicinal container from which the medications in the child medicinal container were sourced.
Although referred to as parent and child medications and medicinal containers, it will be understood that a parent medicinal container (or parent medication) in one context may be a child medicinal container (or child medication) in another context. Similarly, a child medicinal container (or child medication) in one context may be a parent medicinal container (or parent medication) in another context. For example, if Fentanyl in a vial is transferred to a syringe, and then combined with sodium chloride in an IV bag, the Fentanyl in the syringe can be referred to as a child medication as part of the transfer to the syringe and as a parent medication as part of the combination with the sodium chloride in the IV bag. Similarly, the syringe can be referred to as a child medicinal container as part of the Fentanyl transfer to the syringe and as a parent medicinal container as part of the combination of the Fentanyl with the sodium chloride in the IV bag.
In some cases, a child medicinal container may be a previously unused medicinal container and/or have a single parent medicinal container. Similarly, a child medication may have a single parent medication. For example, if Propofol is removed from a vial and added to a syringe, the vial can be considered the parent medicinal container and the syringe can be considered the child medicinal container and/or the Propofol in the vial can be considered the parent medication and the Propofol in the syringe can be considered the child medication. In such cases, the syringe may have been previously unused, used with the same patient, or sterilized prior to the addition of the Propofol.
In certain cases, the child medicinal container may have multiple parent medicinal containers and may even be the same as one of the parent medicinal containers. Similarly, a child medication may have multiple parent medications. For example, if Fentanyl from one vial and sodium chloride from another vial are combined into a syringe, the vials can be referred to as the parent medicinal containers and the syringe can be referred to as the child medicinal container and/or the Fentanyl and sodium chloride in the vials can be referred to as the parent medications and the combined Fentanyl and sodium chloride in the syringe can be referred to as the child medication.
In some scenarios, the child medicinal container can be the same as one of the parent medicinal containers. For example, if Fentanyl is in a syringe and sodium chloride is added to the syringe from a vial, the vial can be referred to as a parent medicinal container and the syringe can be referred to as a parent medicinal container and the child medicinal container. Similarly, the Fentanyl in the syringe prior to the combination and the sodium chloride in the vial prior to the combination can be referred to as the parent medications and the combined Fentanyl and sodium chloride in the syringe can be referred to as the child medication.
It will be understood that the system can track child/parent medicinal containers and/or child/parent medications, as desired. Accordingly, the examples used above and throughout the description should not be construed as limiting. Furthermore, it will be understood that the system can track any pharmaceutical item and is not limited to tracking medicinal containers and/or medications.
System Overview
The system described herein can be used for the identification and lifecycle tracking of medicinal containers within the medical care facility environment, and can enhance the identification and lifecycle tracking of medications that have left the medical care facility pharmacy. Child medications or medicinal containers created outside the pharmacy (for example, at a crash cart, in a patient room, or in the operating room) can be tagged using RFID technology or a serialized number, or barcode, so that the child medication or child medicinal container as well as any parent medications or parent medicinal containers assigned to the medical provider can be available in the pharmacy's inventory for reconciliation, regulatory reporting, and as overall inventory management. In some instances, users may be barred from creating labels for child medications or medicinal containers that do not follow rules defined by the hospital and regulatory agencies, or for medications to which the user does not have permissions.
In addition, the system can allow users to indicate administration and non-administration of medications and other pharmaceutical items provided by the pharmacy or elsewhere, or items created by the provider. By enforcing rules regarding the combination of medications, such as drugs and/or diluents, and creation of child medications or medicinal containers, and enhancing the existing reconciliation workflow of providers in the medical care facility, the system can be used to create reports for use by the pharmacy and hospital for patient billing, detection and elimination of medication diversion, detection and elimination of medication misadministration and misuse, and other procedural errors or inefficiencies.
In some embodiments, the system can rely on data specific to each pharmaceutical inventory item (for example, medicinal containers, such as vials, ampoules, IV bags, and syringes, gauze, medical supplies, etc.) originating in the pharmacy or created by the user within the medical care facility environment. This data can be captured by reading data encoded on RFID tags present on each item or alternatively by scanning a serialized barcode or QR code, or other technology, etc. The system can create RFID or serialized barcode tags for placement on child medicinal containers, and can provide the user with the ability to indicate the administration of medication and/or the disposal of medication.
Although described above with reference to identification and lifecycle tracking of pharmaceutical items in the medical care facility environment, it will be understood that the system can also be used to enforce adherence to regulations regarding creation of child medications or medicinal containers as well as proper administration of medications, such as disallowing the use of expired medications and medications from manufacturer lots and/or medical care facility lots that have been recalled, and providing warnings, such when a syringe has already been used by another patient.
Pharmaceutical items, such as medicinal containers, are processed in several different stages before being distributed to locations inside the hospital such as smaller satellite pharmacies, dispensing stations, and pre-prepared groups of medications in kits and trays. The system described herein can track the location and custody of pharmaceutical items throughout these locations, and into the patient administration environment. Once inside the patient administration environment, the system can enforce rules regarding the creation, administration, and reconciliation of both new and preexisting pharmaceutical items.
In the patient administration environment, the system can use a handheld, tablet, or desktop device used to interact with the user, an RFID reader (or barcode or QR code reader) to identify the pharmaceutical items, and a printer used to create RFID or serialized tags for pharmaceutical items created within the patient administration environment.
The system can further include a graphical user interface, an application programming interface, a database containing pharmaceutical items, user information, data related to hospital-specific workflows and rules, log entries for pharmaceutical item history, custody, location, administration, and other data, and an application that sends data to the printer for the creation of standards-compliant pharmaceutical labels for items created in the operating room environment.
The system can further record the physical location of items within a hospital or medical center campus, and the possession of items by specific users. The system can use both physical checkpoints such as RFID readers, and workflow checkpoints to record the location of a pharmaceutical item. For example, an RFID tag with a specific unique identifier can be coupled to a 10 mL vial of Fentanyl, which is a DEA Schedule II controlled substance. The unique identifier can be used to store data regarding the Fentanyl and/or the vial in the database used by the system. As the vial (and Fentanyl) physically moves throughout the medical care facility, RFID readers throughout the medical care facility can record the physical movement and note the location and time that the RFID tag of that pharmaceutical item was read.
Medicinal Container Tracking
Before the vial (and medication) leaves a pharmacy, the system can facilitate the custody assignment of that vial (and medication) to a specific user and can record the user in possession of the item, in a specific place, and at a specific time. Tracking the chain of custody can continue in the patient administration environment, as the medication can be administered directly to the patient (either partially or in its entirety), can be discarded into a waste receptacle (either partially or in its entirety), can be returned to the pharmacy (either partially or in its entirety), or can be used to create a child medication or child medicinal container in the operating room, or elsewhere (either partially or in its entirety).
The system can track these additional movements and transformations, including any other assignments of custody that might occur within the patient administration context, such as assigning custody to another provider to complete a work shift or patient case or procedure. To assign custody to another provider the custodian provider can scan a badge or otherwise self-identify to the system. The provider can then scan the medications (separately or collectively) that are to change custody. The receiving provider can similarly self-identify to the system and indicate to the system that they are taking custody. The system can verify the status of the medications (for example, expiration, amounts, etc., as described in greater detail below). In addition, the system can verify that the receiving provider has the appropriate privileges to receive the medications.
Additionally, the system can enforce the rules of the medical care facility by requiring one or more approval actions for changes in custody as well as one or more approval actions for user indications of administration or waste actions. For example, the system can allow a provider to indicate they have discarded a pharmaceutical item into a waste receptacle, and if the medical care facility rules dictate that action must be verified by another user, the system can provide the interface and logging mechanism for the witness to verify the action, either through manual interaction with a graphical user interface or by the system reading user information which may come from an RFID-enabled badge or some other authentication method.
The tracking mechanisms of the system can pertain to pharmaceutical items compounded elsewhere on-site or within the patient administration environment. The system can provide a detailed history of pharmaceutical items used in a patient administration environment regardless of their origin, by capturing a snapshot of the package and its contents as it exists over time. The data capture can enable the system to provide a clear picture into the movement of medications through medicinal containers. In turn, the system can allow staff members to locate any pharmaceutical item that has been identified as problematic, such as expired or recalled medication, regardless of whether it has been assigned to a user or a physical location, administered to a patient, discarded into a waste receptacle, or used in the creation of a child medication or child medicinal container.
For example, in the patient administration environment an anesthesiology provider may have custody of a vial of Vecuronium bromide powder and a vial of normal saline. The provider can create a child medication or child medicinal container that combines an amount of Vecuronium bromide powder in milligrams with an amount of normal saline in milliliters. The system can handle the combination of pharmaceutical items of different types, and can produce a child medication or child medicinal container of the appropriate type. In the example above, the system can determine that the combination of a powder and a liquid creates an item that is a mixture, combining two liquids results in another liquid, and combining two mixtures results in another mixture.
Similarly, the system can determine the appropriate unit of measure from the combination of pharmaceutical items measured in different units. In the example above, a powder measured in milligrams combined with a liquid measured in milliliters results in a mixture measured in milligrams over milliliters. Similarly, a liquid measured in milliliters combined with another liquid measured in milliliters, results in a new liquid measured in milliliters, and so on.
New Label Creation
As part of the process of physically combining items, the provider can use the system to create an RFID label (or barcode or QR code label) to place on the child medicinal container, which the system can use to track location, custody, and administration of the contents of the child medicinal container (“Vecuronium bromide in Normal Saline”), or child medication, alongside the two parent medications or parent medicinal containers (“Vecuronium bromide” and “Normal Saline”). The system can automatically create a new expiration date for the child medication and/or child medicinal container based on rules set by the medical care facility, or otherwise, and automatically calculate the volume of the contents within the child medicinal container, or child medication. The system can also update the quantity of the parent medicinal containers, or parent medications, as wells the expiration of the parent medications or parent medicinal containers to reflect that a sterile barrier has been pierced. The system can block a provider from creating child medications or child medicinal containers from expired or recalled sources, and it may not allow the provider to create child medications or child medicinal containers outside of rules established by the medical care facility, which includes the number of different items within one child medicinal container as well as specific medicinal combinations. Once the label has been created and placed on the child medicinal container, the system can associate the label with the child medication or child medicinal container and assign custody to the provider.
The provider can use the system in the same way to produce another distinct child medication or child medicinal container of “Vecuronium bromide in Normal Saline” from the same parent medications or parent medicinal containers used to create the first child medication or child medicinal container. In this case, the system can record both children of the parent medications or parent medicinal containers, and track the location, custody, and administration of all of the medications or medicinal containers separately. The system allows for the creation and tracking of multiple generations of pharmaceutical items. For instance, if a provider takes the second generation “Vecuronium bromide in Normal Saline” item and combines it with a large bag of normal saline for use in an IV drip, the system can create another RFID label for the third-generation medication or medicinal container and track its custody, location, and administration accordingly. Should the medical care facility or pharmacy need to account for every milligram of Vecuronium bromide from a specific manufacturer's lot, the system can enable them to find not only unused vials on pharmacy shelves, but syringes drawn up in the patient administration context, as well as bags of solution containing the contents of syringes drawn up in the patient administration context.
The system can also be configured to track amounts of medications moving between items. For example, a provider may want to fill three syringes with a DEA Class 2 drug, such as Fentanyl, but may not indicate the actual amounts transferred from each vial, and may simply “administer” a syringe rather than record partial use. At some point, the provider reconciles how much Fentanyl was used, administered, and wasted. The system can record all of the parent medications or medicinal containers where Fentanyl came from and can also record all of the child medications or medicinal containers, such as destination syringes or bags, as well as the cases, rooms and waste bins where any of the medicinal containers may have been placed. Accordingly, the actual reconciliation of how much Fentanyl was used, wasted, and returned can be reconciled at some later point in time without knowing the exact volumes of drugs in each item along the way.
Reconciling Medications
The system can also provide an efficient mechanism for reconciling the administration and waste of pharmaceutical items in a patient administration context. Through the use of RFID or serialized labels on the pharmaceutical items, the provider can scan these items in bulk and perform one action on all of the items scanned, or can scan items individual and perform more granular actions. For example, at the end of a medical case in the operating room, the provider may have ten empty syringes to reconcile. If all of the syringes are empty and the provider intends to place them all in a waste receptacle, the system can scan the group of items. The system can identify all items scanned and allows the user to indicate the amount used (e.g. “all”) and intention (e.g. “discard”), which is then applied to all of the scanned items. The system can also record partial amounts used or wasted of single medicinal containers (e.g. “10 mL used and 15 mL wasted from a 25 mL package”). The system allows for medical care facilities to specify the intentions they would like to track as well as rules regarding item administration and reconciliation, which includes the units of measure used to record administration and waste and whether to record mass versus volume of an item. In addition to the manual reconciliation of administration and waste of items, the system can interact with patient electronic medical record stored in systems accessible within the patient administration context. The system can send data regarding syringe contents, as well as receive data regarding actual use from the patient's electronic medical records.
Restocking
The system can use the data captured within the patient administration environment not only for reports within this environment but also for reports used in the pharmacy and medical care facility overall. Using the data captured in the location and custody tracking features, the system can provide reports indicating drawers and cabinets in specific locations to be restocked due to expired, empty, recalled, or otherwise incorrect inventory. In addition, the system can cause a display to display the inventory of a particular drawer or cabinet. Furthermore, as part of the restocking, the system can query the RFID or serialized labels on the new items, update the database accordingly, and report the correct state of the pharmaceutical and supply items in a particular location and as verified by the user. The system can additionally provide detailed reports on pharmaceutical and supply items assigned to a user, to a room, or to a patient case, and the end result of each of those items, thus clearly showing where pharmaceutical items such as controlled medications have been misused or lost. Beyond the day-to-day workflow of tracking drugs, the data captured within the system can be used for pattern detection of different events or situations such as diversion patterns, over and under administration of drugs by a provider, over or under billing of patients, pharmaceutical and supply order optimization, warning and calculation of waste and the impact on the water supply and other predictive measures.
Tracking Environment
The label reading station 102 can be located in any location of a medical care facility, such as on a particular floor, in a particular wing, in an operating room, patient room, or other patient administration environment. In some embodiments, multiple label reading stations 102 can be located throughout a medical care facility, such as in different patient rooms, operating rooms, etc.
In the illustrated embodiment, the label reading station 102 includes a label printer 104 and a label reader 106. In some embodiments, the label printer 104 and the label reader 106 can be implemented as an RFID label printer and an RFID label reader, respectively. In certain embodiments, the label printer 104 and the label reader 106 can be implemented using a variety of technologies, such as a bar code reader and printer, QR code reader and printer, etc.
When implemented using barcode or QR code technology, the label reader 106 can be configured to capture an image of a barcode or QR code and/or emit a laser that can capture the barcode or QR code data. When implemented using RFID technology, the label reader 106 can be configured to emit an electromagnetic wave, such as a radio wave, that activates one or more RFID tags in proximity to the label reader 106. The emission of the electromagnetic wave can also be referred to as a query. In some embodiments, the RFID tags used in conjunction with the label reading station 102 can be passive or active RFID tags.
The electromagnetic wave emitted by the label reader 106 can cause the RFID tags to generate a response that includes data stored on the RFID tag. Upon receiving the data from the RFID tag, the label reading station 102 can communicate with the information processing system 108 and/or the electronic medical records database 110 to process the data.
In some scenarios, as part of the processing, the label reading station 102 can generate a label to be affixed to a medicinal container. The label printer 104 can be used to print the new label. In some embodiments, the new label can include an RFID tag that has stored thereon a unique identifier. In certain embodiments additional information can be stored on the RFID tag, such as medication name data, expiration data, provider data, patient data, etc. In some embodiments, the label printer 104 prints information regarding the medication onto the RFID tag. Some non-limiting embodiments of labels that can be printed by the label printer 104 are described in greater detail below with respect to
Although the illustrated embodiment shows the label reading station 102 as including a label printer 104 and a label reader 106, it will be understood that in some embodiments the label reading station 102 may include fewer or more components. For example, in some scenarios, the label reading station 102 can omit the label printer 104. In such embodiments, the label reading station 102 can be placed at or near a location where a medication is being administered to a patient. In such situations, a medical care provider can place a label near the label reading station 102, which can be read by the label reader 106. The label reading station 102 can then transmit the information to the information processing system 108 for processing. Accordingly, the information processing system 108 can update the medical records of the particular patient with data regarding the administration of the medication, determine whether a particular medication has been provided to a patient located at or near the label reading station 102, determine whether the medicinal container has been used previously, etc. In some embodiments the label reading station 102 can be implemented as a portable or handheld device that can be used to quickly and easily read RFID tags.
Furthermore, although reference is made throughout the specification to the label reading station 102 performing various analytical or processing functions, it will be understood that, in some embodiments, the information processing system 108 performs these functions, and the label reading station 102 is used to acquire data from one or more labels, display data based on data and/or instructions received from the information processing system 108, and print a label based on data and/or instructions received from the information processing system 108. In such embodiments, the label reading station 102 can receive notifications of processing functions performed by the information processing system 108, such as indications of the verification of a medication and/or indications regarding associations between any combination of medications, medicinal containers, unique identifiers, medical providers and/or patients, etc. Accordingly, in some embodiments, the amount of processing performed by the label reading station 102 can be reduced and/or minimized, and the label reading station 102 can act as a conduit to the information processing system 108. In this way, the hardware requirements and costs of the label reading station 102 can be reduced in favor of a larger or more robust information processing system 108. In certain embodiments, the label reading station 102 can include the information processing system 108 and perform all of the functions described herein.
The information processing system 108 can include one or more microprocessors, a data storage device 114, a personal health data storage device 116, and a network interface for communication over the network 112. In some embodiments, the information processing system 108 can be implemented as a server or workstation located at a remote facility or at the same medical care facility. The data storage device 114 can include information regarding medications and pharmaceutical items used in the environment 100, user that are allowed to use the label reading station 102, account information for individual medical care facilities, audit information, reports, logs, and various rules with regards to the medications, etc.
The rules can include information regarding which medications can be used with each other, preferences for different users, how to calculate expiration dates for medications, substitute medications that can be used in place of other medications, drug policies, etc. Using the information received from the label reading station 102 and data in the data storage device 114, the information processing system 108 can verify the status of the medications, calculate expiration dates for the medications, determine whether a medication has been recalled or is expired, provide mixing or dilutions suggestions, associate medications, RFID tags, and/or unique identifiers with medical care providers and/or patients, generate restocking notifications, create new database entries for new medications and/or new RFID tags, track drug administration and/or reconciliation, generate reports regarding drug administration by various providers, reports regarding drug administration to different patients, etc.
The personal health data storage device 116 can include personal health information of the patients at a medical care facility, similar to that stored in the electronic medical records database 110. In some embodiments, the personal health data storage device 116 stores a subset of the data from the electronic medical records database 110, such as gender, allergic reactions, and medications received, etc. In certain embodiments, the personal health data storage device 116 is a copy of the electronic medical records database 110. In some cases, the personal health data storage device 116 can include data from multiple electronic medical records databases 110 from various medical care facilities.
Furthermore, as data in the personal health data storage device 116 is changed by the information processing system 108, a similar change can be made in the electronic medical records database 110. Similarly, changes to the electronic medical records database 110 can be updated in the personal health data storage device 116. In this way, the personal health data storage device 116 and electronic medical records database 110 can be synched.
In some cases, additional requirements are placed on databases that store patient identifying data. Accordingly, in some embodiments, the data storage device 114 can be implemented separately from the personal health data storage device 116, as either a separate database and/or on a distinct data storage device. However, it will be understood that in certain embodiments, the data storage device 114 and personal health data storage device 116 can be implemented as part of the same database and/or on the same storage device.
When implemented separately, the data storage device 114 can include a unique identifier for each patient that does not include personal health data. For example the unique identifier can be a unique number or other identifier. When the data storage device 114 desires to access personal health data, it can use the unique identifier to communicate with the personal health data storage device 116. In this way, the personal health information can be separated from non-personal health information.
Furthermore, in some embodiments, the information processing system 108 can omit the personal health data storage device 116. For example, in some cases a particular medical care facility may prefer not to have a copy of personal health information stored outside the electronic medical records database 110. In such embodiments, the information processing system 108 can omit the personal health data storage device 116.
The electronic medical records database 110 can include patient specific information, such as gender, age, medical history, medications taken, allergies, weight, medical procedures, vital signs, audit info, and whatever other information a medical care provider desires. The electronic medical records from the electronic medical records database 110 can be used in conjunction with the rules in the data storage device 114 of the information processing system 108 to determine which medications can be provided to a patient and generate labels at the label reading station 102.
In certain embodiments, the label reading station 102, the information processing system 108, and/or the electronic medical records database 110 can implemented in a single device. In some embodiments, the information processing system 108 and/or the electronic medical records database 110 can be remotely located from the label reading station 102. For example, the electronic medical records database 110 and the information processing system 108 can be located at a different site from the medical care facility. In some embodiments, electronic medical records database 110 and the information processing system 108 can be proximally located at the same medical care facility, such as in the same room or floor of the medical care facility.
In the illustrated embodiment, the label reading station 102 includes a display 160, a label printer 104. In addition, the label reading station 102 can include a label reader (not shown), microprocessor, a data storage device, and a network interface. The microprocessor can be configured to execute instructions stored in the data storage device and to read and write data to and from the data storage device. The network interface can be used by the microprocessor to communicate with the electronic medical records database 110 and/or the information processing system 108, as described previously with respect to
The display 160 can be used to prompt a user for information and to display information regarding the medications, labels, patients, medicinal containers, etc. For example, the display 160 can be used to display a prompt for the user to tap a label to the display 160 or to move a label in close proximity to the display 160 such that the label reader 106 can read the label. In addition, the display 160 can be used to display information as the label reading station 102 prepares and prints a label. For example, the display 160 can display information regarding a medication that will be printed onto a new label.
The label reader 106 (not shown in
As described previously with respect to
The label reading station 102 in conjunction with the information processing system 108 can further be used to manage inventory of the pharmaceutical item storage unit 152. For example, when a medication is removed from the pharmaceutical item storage unit 152 by a user and scanned by the label reading station 102, the information can be used to determine whether the pharmaceutical item storage unit 152 includes a threshold number of the medication that was removed. For example, if Propofol is removed from the pharmaceutical item storage unit 152 and there is only one vial of Propofol left in the pharmaceutical item storage unit 152, the label reading station 102 can generate a notification indicating that the pharmaceutical item storage unit 152 should be restocked with more Propofol.
In some embodiments, the label reading station 102 and/or information processing system 108 can track the total number of each medication found within the pharmaceutical item storage unit 152 and from use that information to determine whether a threshold has been satisfied. In some embodiments, the label reading station 102 and/or information processing system 108 can use a one out one in policy such that for each medication removed, the label reading station 102 and/or information processing system 108 can request a replacement medication.
In determining whether a threshold has been reached, the label reading station 102 and/or information processing system 108 can use templates, as described in greater detail in U.S. patent application Ser. Nos. 14/472,410, and 13/554,342, each of which is incorporated herein by reference in its entirety. The templates can be used to identify substitute medications that can be used when a particular medication is not present. For example, the templates can indicate a generic version of a branded drug and/or other drugs that can be used as a substitute. In some embodiments, the substitute drug can be the same drug but at a different concentration or a different amount. In certain embodiments, the substitute drug may not be chemically equivalent and/or have a different active ingredient, but is deemed medically suitable for a particular use or as a substitute to the missing drug.
The label reading station 102 and/or information processing system 108 can further be used to manage and track which medications are in a user's possession. For example, when a doctor scans a label for medication A, medication A can be associated with the doctor, indicating that the doctor is in possession of a particular medicinal container storing medication A. Accordingly, throughout the day, as the doctor removes medications from pharmaceutical item storage units 152, administers medications to a patient, or wastes medications, the label reading station 102 and/or information processing system 108 can be used to track all of the medications in the doctor's possession. This information can be used by the pharmacy to reconcile all medications used by the doctor and ensure medications are not misplaced, lost, or abused.
The label reading station 102 and/or information processing system 108 can further be used to handle and reconcile waste. For example, after a doctor has administered a medication to a patient, any remaining portions of the medication in a vial or syringe may need to be discarded. Accordingly, the label reading station 102 and/or information processing system 108 can provide prompts for the doctor to discard the medications, and in some embodiments, prompt a second doctor to act as a witness for the reconciliation or waste of the medication.
In the illustrated embodiments of
As a non-limiting example, when a doctor enters a patient's room and/or an operating room in which medications will be administered to a patient, the label reading station 102 can scan or read the contents of an RFID tag associated with a particular medication. In this situation, the medication can be associated with the patient that is in the patient room or operating room. Using this information, the label reading station 102 and/or information processing system 108 can determine whether the patient may have any allergic reactions to the medication, update the patient's electronic medical record with information regarding the administration of the medication, and/or calculate the waste based on the amount of the medication used on the patient. In addition, the label reading station 102 and/or information processing system 108 can determine whether the medication or medicinal container has been used previously. In this manner, the label reading station 102 and/or information processing system 108 can prevent multiple uses of a medicinal container, such as a syringe, on different patients.
In some embodiments, the label reading station 102, can omit the display 160 and/or the label printer 104. Furthermore, the label reading station 102 can be any form factor, including a smaller or more portable electronic device, such as a phone, tablet, personal electronic device, etc. For example, a smaller or more portable form factor of the label reading station 102 can be used in an operating room and/or a patient's room to conserve space.
Furthermore, in some embodiments, a smaller form factor of the label reading station 102 can be used as a type of wand to inventory the contents of the pharmaceutical item storage unit 152. Once the contents of the pharmaceutical item storage unit 152 are inventoried, the information processing system 108 can generate a template for the pharmaceutical item storage unit 152 for restocking purposes and/or compare the inventoried items with a template to determine whether any items are to be restocked.
Labels
Similarly, the abbreviated data portions 208, 210 can extend height-wise along a latitudinal portion of the RFID portion 206, as is shown in
In the illustrated embodiment of
Although
The applicator portion 204 can include an adhesive formed on one side and can be transparent or translucent. In this way, the applicator portion 204 can be applied to a medicinal container, such as a syringe, without obscuring the view of any information printed on the medicinal container, such as units of measure. However, it will be understood that the applicator portion 204 can be opaque.
In embodiments where the applicator portion 204 extends lengthwise across a longitudinal portion of the RFID portion 206, the label 202 can be applied to the medicinal container in such a way as to reduce the amount of the label that extends away from the medicinal container. This can reduce the likelihood of the label 202 catching onto some other object.
In certain embodiments in which the applicator portion 204 (for example, applicator portion 204B) in which the applicator portion 204 extends along a latitudinal portion of the RFID portion 206, the label 202 can be configured so as to minimize or reduce the amount of adhesive used in coupling the label 202 to the medicinal container.
In the illustrated embodiment, the RFID portion 206 includes an RFID tag, a printable surface, and is opaque. However, it will be understood that the RFID portion 206 can use other machine-readable data, such as a bar code or QR code, etc. In addition, it will be understood that in some embodiments, the RFID portion can be transparent or translucent and/or not include a printable surface. Furthermore, in some embodiments, the RFID portion 206 does not include an adhesive, and in certain embodiments, the RFID portion includes an adhesive.
The RFID portion 206 can include machine-readable data, as well as human-readable text. The machine-readable data can include a serialized identifier or unique ID stored on an RFID tag, which distinguishes the RFID tag from other RFID tags that are registered with the information processing system 108. In this way, the information processing system 108 can store data that is unique to the label 202, and enables the information processing system 108 to distinguish the label and the medicinal container to which the label is attached from all other medicinal containers, including medicinal containers that form part of the same lot as the medicinal container.
Using the unique identifier, the information processing system 108 can store and look up data unique to the label 202. For example, the data can include one or more lot numbers to which the medication or medicinal container belongs, chain of custody data, expiration data, recall data, drug class data, concentration data, total medication amount data, preparation data, transfer data, etc. This data can be used by the information processing system 108 to verify the status of the medication contained within the medicinal container, produce warnings, provide instructions and/or information, and print labels. In some embodiments, the RFID portion 206 can store some or all of the data on the RFID tag included within the RFID portion 206. In some embodiments, the RFID tag included within the RFID portion 206 includes only the unique identifier, and the other data associated with unique identifier is stored at the label reading station 102 and/or the data storage device 114 of the information processing system 108.
In addition to the RFID tag, the RFID portion 206 can include text, and other information regarding the medication and/or the medicinal container to which the label 202 is affixed. For example, the RFID portion 206 can include a color identifier identifying the drug class of the medication, a drug name, concentration of the drug, total amount of the drug, expiration data, user identifier, preparation data, and/or any other information desired. In this way, a user can read the text on the RFID portion 206 to determine the contents of the medicinal container. As mentioned previously, although reference is made to an RFID tag forming part of the RFID portion 206, it will be understood that other machine-readable identifiers can be used, such as, a bar code, QR code, etc. Such identifiers can include either a unique identifier or serialized identifier, or additional data as described previously.
The abbreviated data portions 208, 210 in the illustrated embodiment of
Furthermore although illustrated as having two abbreviated data portions 208, 210, it will be understood that the label 202 can have fewer or more abbreviated data portions as desired. For example in some embodiments, the label 202 does not include any abbreviated data portions or only one abbreviated data portion. In certain embodiments, the label 202 can include three or more abbreviated data portions arranged in any number of orientations, such as the orientation shown in
With respect to
Mixing and Dilution
In the illustrated embodiments of
The various links 304, 306, 308 can be used to navigate to various portions of the user interface 300. For example, the inventory data link 304 can be used to navigate to a portion of the user interface 300 displaying medications that are in the possession of a user, as well as additional information regarding the use of those medications, such as the embodiments of the user interface 300 illustrated in
The medication names 312, 332 can include a proper name for the medication, a generic name for the medication and/or other identifying name for the medication. The class identifier 313 can indicate the class of the medication, such as a drug classification. In some embodiments, the class identifier can be a color coded drug class identifier, or other identifier to indicate the classification of the medication or drug.
The mass field 316 can indicate the total mass of the medicinal container associated with the label 202 that is scanned by the label reading station 102. The final concentration field 318 can indicate the final concentration of the child medication or content of a child medicinal container. The total volume field 320 can indicate the total volume of the child medication or content of the child medicinal container.
The first medication volume field 317 can indicate the volume of the parent medication being removed or the volume being removed from the parent medicinal container. Similarly, the second medication volume field 338 can indicate the volume of the parent medication being removed and/or the volume being removed from the second parent medicinal container and being added to the child medicinal container to form the child medication.
By interacting with the mixture object 322, the system can provide the user with one or more suggestions of diluents that can be combined with the medication 312, as illustrated on
The additional interface objects 324, 326, 328 can be used to control portions of the user interface 300 and/or navigate to different portions of the user interface 300. For example, interacting with the preview object 324 can provide the user with a preview of a label to be printed based on the contents of the user interface 300, and interacting with the print object 326 can cause the label reading station 102 to print a label 202 based on the information displayed on the user interface 300.
With continued reference to
Once the new label 202 is printed, the unique identifier from the RFID tag of the label 202 can be associated with the new database entry. In some embodiments this association can take place during the printing of the label 202 and/or following the printing of the label 202. For example, a user can tap or place the newly generated label 202 on or near the label reading station 102. The label reading station 102 can read the unique identifier from the label 202 and use that information to associate the unique identifier with the data regarding the contents of the new medicinal container.
In addition, as part of this process, the information processing system 108 can update the medication data associated with the parent medications or parent medicinal containers. For example, the information processing system 108 can update an expiration date for the parent medications or parent medicinal containers from a sealed expiration date to a broken seal expiration date, a vial expiration date to a syringe expiration date, and/or a refrigerated expiration date to a non-refrigerated expiration date, etc., as described in greater detail below.
In some embodiments, the information processing system 108 can reduce quantity data associated with the parent medications or parent medicinal containers and increase quantity data associated with the child medication or child medicinal container. For example, if the parent medicinal container is a vial and included four mL of Fentanyl, two of which were removed and placed into the child medicinal container to form the child medication, the information processing system 108 can decrement the quantity data associated with the parent medication and/or parent medicinal container by two mL and increase the child medication or contents of the child medicinal container by two mL.
The first medication information 310 can include, but is not limited to, a medication name 312, a class identifier 313, concentration data 314, a mass field 316, a final concentration field 318, origin data 315 indicating the origin of the medication (shown in
The second medication information 330 can include similar information. In the illustrated embodiment of
The various fields illustrated in the user interface 300 can be fillable fields or auto populated. In some embodiments some of the fields auto populate based on data collected in a fillable field. For example, the total volume field 320 can auto populate based on the contents of the first medication volume field 317 and the second medication volume field 338. Similarly, the final concentration field 318 can also be auto populated based on the information from the mass field 316, the first medication volume field 317, and/or the second medication volume field 338.
The origin data 315, 336 can indicate the origin of the medications, respectively. For example, the origin data 315 can indicate that the first medication originated from a medicinal container such as a vial that also includes a label 202 uniquely identifying the vial. The origin data 336 can indicate that the second medication originates from a medicinal container that does not include a label 202. For example, the second medication can originate from an IV bag or drip line that is not tracked and/or does not include a label 202.
Medical Care Provider Inventory
In the illustrated embodiment of
Medication Administration
In some embodiments, the information processing system 108 can automatically determine that medications are to be provided to a particular patient based at least in part on the location of the label reading station 102 and the electronic medical records of the particular patient. For example, if the label reading station 102 is located in operating room 1 and the medical records of Abigail Jones indicate that she is in operating room 1, when the medical care provider logs into or accesses the label reading station 102, the information processing system 108 can automatically determine that a procedure is in progress for Abigail Jones and that the medical care provider will be administering medications to Abigail Jones.
As the label reading station 102 in the operating room 1 reads RFID tags associated with various medicinal containers, the information processing system 108 can associate the various medicinal containers with the Abigail Jones and with the medical care provider (if it has not already done so as part of a label creation). As the RFID tags are scanned, information regarding them can be displayed on the user interface 300. Furthermore, the information processing system 108 can verify the status of the medications, log the date and time of administration, determine whether Abigail Jones may have any allergic reactions to the medications, etc. The label reading station 102 can display applicable warnings based on the processing of the information processing system 108. For example, the label reading station 102 can display or sound a warning indicating a possible allergic reaction to a medication, an adverse reaction between two medications, an expired medication, etc.
As the medications are administered, the information processing system 108 can update the data storage device 114, personal health data storage device 116 and/or the electronic medical records database 110. For example, the information processing system 108 can indicate in the personal health data storage device 116 and/or the electronic medical records database 110 that a particular medication has been administered to the patient.
In addition, the information processing system 108 can update the medication data for the particular medication to indicate the quantity that was administered. From that information, the information processing system 108 can determine the amount of the medication that is to be returned or wasted. Furthermore, the information processing system 108 can update any expiration dates associated with the medication. For example, the expiration date may be changed from a sealed expiration date to a broken seal expiration date, as described in greater detail below.
In the illustrated embodiments of
The patient data 502 and completed procedure patient data 504 can include information uniquely identifying a patient, such as a patient name, date of birth, gender, and/or a patient identification number, etc. The patient data 502 and completed procedure patient data 504 can correspond to patients with whom the user or medical care provider is working or has worked. As mentioned previously, the label reading station 102 and/or information processing system 108 can communicate with an electronic medical records database 110 to retrieve data regarding the patients of a particular medical care facility. Using the data from the electronic medical records database 110, the information processing system 108 can associate the patients with a particular medical care provider.
The medication delivery time icon 506 and medication detailed information icon 508 can be used to alter the information displayed on the user interface 300. In the illustrated embodiment of
The add/edit medication icons 510,512 can be used to add information regarding additional medications that are used during the current procedure with the identified patient. In some embodiments, the information can be added by scanning an RFID tag associated with a medicinal container.
The medication name/concentration data 516 can be similar to the drug name/concentration data 402 described previously with respect to
The user interface can include additional information and objects as desired. For example, in the illustrated embodiment of
As mentioned previously,
In the illustrated embodiment, it is shown that a vial containing five milligrams of Midazolam was associated with the patient. Of the five milligrams, three milligrams were administered to the patient. Accordingly, the to waste amount data 528 of the user interface 300 indicates that two milligrams of Midazolam are to be wasted. Once wasted, the user interface 300 can be updated to reflect the wasted amount 524 as 2 mg and the to be wasted amount 528 as zero.
Furthermore, in the illustrated embodiment of
Medication Reconciliation
The to waste medication quantity 604 can include the number of medicinal containers that include medications that are to be wasted. In the illustrated embodiment of
The to return medication quantity 606 can indicate the number of medicinal containers that are to be returned to the pharmacy. This quantity may indicate medicinal containers that were never used by the medical care provider or medicinal containers that include medications that can be reused by the pharmacy.
In addition, the user interface 300 can include additional information regarding the medications that are to be wasted. For example, the user interface 300 can include medication data 608, initial quantity data 610, to waste quantity data 612, and drug classification data 614. As described in greater detail above, the item data 608 can include medication name and concentration, the initial quantity data 610 can include an initial quantity of a medication and a particular medicinal container, the to waste quantity data 612 can indicate the total amount of the particular medication that is to be wasted, and a drug classification data 614 can indicate a drug classification of the particular medication.
For medications that are to be returned, the user interface 300 can include some or different information as the information that is used for the medication that is to be wasted. For example, the user interface 300 can indicate item data 608, medicinal container volume data 616, quantity of medicinal containers to return data 618, and drug classification data 614.
The medicinal container volume data 616 can include information regarding the volume of the medication within a particular medicinal container and the quantity of medicinal containers to return data 618 can indicate the number of medicinal containers containing a particular medication that are to be returned to the pharmacy.
In addition, the user interface 300 can include a to waste witness icon 620. By interacting with the waste witness icon 620, the user interface 300 can enable the user to waste the medications. The user interface can control what the user is able to do in order to enforce one or more policies set by the medical care facility. For example, the user interface can require another medical care provider to witness the wasting of the medications. In addition, the user interface can require the witness to sign and/or scan in in order to ensure that the witness is present for the wasting.
Following the wasting and reconciliation of the medications, the information processing system 108 can generate a receipt indicating the inventory of the medications that were in the possession of the user, as well as a detailed report regarding which medications were administered to which patients, which medications were wasted (and their quantity), the identification of the witness, and which medications were returned to the pharmacy, etc. In this regard, the information processing system 108 can provide a complete audit trail and chain of custody of a medication throughout its use at a medical care facility.
Flow Diagrams
One skilled in the relevant art will appreciate that the elements outlined for routine 700 can be implemented by one or many computing devices/components that are associated with the environment 100, including, but not limited to, the label reading station 102, the information processing system 108, and/or the electronic medical records database 110, or any combination thereof. For simplicity, routine 700 has been associated as being generally performed by the label reading station 102, and thus the following illustrative embodiments should not be construed as limiting.
At block 702, the label reading station 102 queries a first RFID tag of a first label. To query the first RFID tag, the label reading station 102 can emit an electromagnetic wave that activates the first RFID tag or causes the RFID tag to emit a response. In some embodiments, such as when an RFID tag is not used, the label reading station 102 can include a QR code reader or bar code reader that is able to query the first label containing machine-readable data.
At block 704, the label reading station 102 receives a first unique identifier from the first label. As mentioned previously, each RFID tag can include a unique identifier that uniquely identifies that RFID tag from all other RFID tags in a particular pharmaceutical item storage unit, at the medical care facility and/or that are tracked by the information processing system 108. In this way each medicinal container associated with an RFID tag can be uniquely identified.
Furthermore the information processing system 108 can include a database entry for each unique identifier. The database entry for the unique identifier can include information regarding the medicinal container, medication name, drug classification, concentration of the medication within the medicinal container, total volume, lot numbers associated with the medication and/or the medicinal container, expiration data of the medication, recall information regarding the medication, national drug code (NDC), user and facility audit information, multi-dose information, refrigerated information, and/or event history etc. In some embodiments, the RFID tag can store some or all of the data associated with the unique identifier.
At block 706, the label reading station 102 can verify the status of the medication using the data associated with the first unique identifier. Although reference is made to the label reading station 102 verifying the status, it will be understood that in some embodiments, the label reading station 102 receives a status from the information processing system 108 based on an analysis conducted by the information processing system 108, and in certain embodiments, the label reading station 102 analyzes the data to determine the status. In some embodiments, to verify the medication status, the label reading station 102 can determine whether the medication is part of a recall and/or has expired.
To determine whether the medication is part of a recall, the label reading station 102 can cross-reference the lot numbers associated with the first unique identifier (including lot numbers associated with the unique identifiers of all parent medications or parent medicinal containers) with lot numbers that have been recalled. In some embodiments, to verify whether a medication has been recalled, the information processing system 108 can consider only those lot numbers that were created at the same time as or prior to the creation of the database entry corresponding to the first unique identifier. For example, in some instances, a child medication is created or a medication is added to a child medicinal container and then something happens to the medication remaining in the parent medicinal container, or parent medication, such that the parent medication is to subject to a recall or is to be discarded. However, in some embodiments, the recall is only applied to the medication remaining in the parent medicinal container and does not apply to the child medication that was already in the child medicinal container.
To verify the expiration of the medication, the label reading station 102 can determine whether the current date and time is past an expiration date and time of the medication. As part of the expiration verification, the label reading station 102 can identify multiple expirations and use the earliest expiration to determine whether the medication is expired. For example, some medicinal containers may include multiple medications. Each medication may have one or more expirations, the combination of the medications may create a different expiration, and one or more rules may apply to the medications or combination thereof.
For example, some medications have an expiration based on refrigeration and a different expiration when not refrigerated. Similarly, once a seal of a medicinal container is broken, the expiration for a medication, such as a multi-dose medication, may change. For example, while sealed, a medication may have a one year shelf life, but once the seal is broken or punctured, the expiration may change to 60 days from the time the seal was broken or punctured. The broken seal expiration may vary depending on the medication.
In some cases, when a medication is moved to a syringe, the expiration of the medication in the syringe is different than the expiration of the medication in a vial. For example, a medical care facility may have a rule that all syringes expire within 12 hours of being drawn. In certain embodiments, the location of where the syringe is drawn can affect the expiration. For example, a medical care facility may have a rule that syringes drawn in a patient administration environment expire in 24 hours or less, while syringes drawn in a clean room expire in 7 days. Furthermore, in some embodiments, combining two medications can result in a different expiration. As such, in embodiments where multiple expirations are provided, the label reading station 102 can compare the current date and time with the earliest expiration to determine whether the medication is expired. In certain embodiments, only the earliest expiration is provided in conjunction with the unique identifier, and is used to determine whether the medication is expired.
In some embodiments, as part of verifying the status of the medication, the label reading station 102 can determine whether the medical provider has appropriate rights or permissions to handle the medication. For example, some medications can only be handled by certain personnel at a medical care facility. Accordingly, the label reading station 102 can query whether the medical provider that is attempting to handle the medication has the appropriate permissions.
In some embodiments, if the medication cannot be verified, the label reading station 102 can display a warning or disallow the use of the medication. For example, the label reading station 102 can display a warning that the medication is expired or recalled. In addition, when two medications are being combined and the information processing system 108 can, as part of the verification, determine whether the combination would have any adverse reactions. If the information processing system 108 determines that the combination of the two medications would cause an adverse reaction, the label reading station 102 can display a warning or disallow the printing of a label for the combination, etc.
At block 708, the label reading station 102 generates a second expiration date for the medication. The label reading station 102 can generate the second expiration date in a variety of ways. For example in some embodiments the label reading station 102 can use the same expiration date as the parent medication or parent medicinal container. In certain embodiments, the label reading station 102 can generate the second expiration date based on one or more rules associated with the parent medication. For example, once Propofol has been removed from a vial and placed into a syringe, its shelf life decreases to six hours. In such instances, the label reading station 102 can calculate the second expiration date based on the rules of the Propofol, or other applicable rules of the parent medication(s) or medical care facility, as described above.
In embodiments in which multiple parent medications are combined to form the child medication, the label reading station 102 can generate the second expiration date by reviewing the expiration dates of all parent medications that will be used to form the child medication, as well as any rules associated with the parent medications or medical care facility. As mentioned previously, medications and combinations of medications can have various expirations. The label reading station 102 can determine the second expiration date as the earliest expiration date of all of the expiration dates of the parent medications, as well as the expiration date based on any rules associated with the parent medications.
At block 710, the label reading station 102 associates the first RFID tag with a medical care provider. To associate the first RFID tag with the medical care provider, the label reading station 102 can identify the medical care provider that has logged into or scanned their badge prior to scanning the first RFID tag. The label reading station 102 can then associate the first unique identifier of the first RFID tag with a unique identifier of the medical care provider in the data storage device 114 of the information processing system 108. As part of the association, an entry can be added to the information associated with the unique identifier of the RFID tag indicating that the medical care provider has accessed, taken control of, is in possession of, and/or has used the medicinal container associated with the first unique identifier.
At block 712, the label reading station 102 can print medication data on a second label having a second RFID tag. The medication data can include the name of the medication, the expiration of the medication, the concentration of the medication, and/or the total volume of the medication in the second medicinal container. In addition to the medication data, the label reading station 102 can print information regarding the transfer of the medication, including the date and time of the transfer, and the identification of the user that caused the printing to occur.
In some embodiments, the label reading station 102 can print the medication and other data onto the labels described previously with respect to
At block 714 the label reading station 102 queries the second RFID tag. As described previously with respect to block 702, the label reading station 102 can query the second RFID tag using electromagnetic waves. However, it will be understood that a variety of technologies can be used to query the machine-readable data contained on the second label. In some embodiments, the label reading station 102 can query the second RFID tag during printing of the medication data on to the second label. In certain embodiments the label reading station 102 can query a second RFID tag after printing the medication data onto the second label. In such embodiments, following the printing of the medication data on the second label, a user can tap or move the label onto or in close proximity to, the label reading station 102.
At block 716, the label reading station 102 receives the second unique identifier from the second RFID tag. As mentioned previously, this second unique identifier can be associated with, or used to generate, a new database entry for the data for the child medication or child medicinal container. The database entry can include information similar to the database entry described previously.
At block 718, the label reading station 102 associates the second medicinal container with the medical care provider. For example, the label reading station 102 can associate the second unique identifier with the medical care provider indicating that the medical care provider created, is in possession of, or in some other way used the child medication or child medicinal container associated with the second label. In this way, the information processing system 108 can track the chain of custody of the child medication and/or child medicinal container and provide audit information regarding its location and use.
At block 720, the label reading station 102 can associate the child medication or child medicinal container (using the second unique identifier) with a medical patient. For example, similar to the manner in which the label reading station 102 associates the child medication or child medicinal container with the medical care provider, the label reading station 102 can associate the child medication or child medicinal container with the medical patient. For example, the second unique identifier can be associated with the medical patient indicating that the child medication is to be used for the medical patient.
At block 722, the label reading station 102 determines that the pharmaceutical item storage unit does not store a threshold quantity of the medication. In some embodiments, the label reading station 102 can store a complete inventory of the pharmaceutical item storage unit, such that each time a medicinal container is removed from the pharmaceutical item storage unit, the label reading station 102 can decrement the total number of medicinal containers containing the particular medication. The label reading station 102 can then compare the updated quantity of medicinal containers including a particular medication with a threshold quantity of medicinal containers containing the medication. Upon determining that the quantity of medicinal containers containing the medication does not satisfy the threshold quantity, the label reading station 102 can generate a restocking notification, as illustrated at block 724.
In some embodiments, the label reading station 102 may not store or know the inventory of the medication stored in the pharmaceutical item storage unit. As such, the label reading station 102 can implement a one out one in inventory policy such that each time a particular medication is removed from the pharmaceutical item storage unit, the label reading station 102 can generate a restocking notification to replace the medication that has been removed.
In some embodiments, the label reading station 102 can use one or more templates to determine whether or not the pharmaceutical item storage unit stores a threshold quantity of a medication. The templates can indicate one or more substitute medications and/or substitute quantities that may be used in case a particular medication does not satisfy the threshold quantity. For example, one or more rules may indicate that Advil may be used in place of Tylenol. Accordingly, if a medicinal container including Advil is removed from the pharmaceutical item storage unit, and the total number of Advil in the pharmaceutical item storage unit does not satisfy the threshold quantity of Advil, the label reading station 102 can determine whether or not the number of Tylenol in the pharmaceutical item storage unit satisfies the threshold quantity of Advil. Based upon a determination that the quantity of Tylenol in the pharmaceutical item storage unit satisfies the threshold quantity of Advil, the label reading station 102 can determine that the pharmaceutical item storage unit stores a threshold quantity of Advil. However, in embodiments in which the label reading station 102 determines that the pharmaceutical item storage unit does not store a threshold quantity of Advil (or Tylenol), the label reading station 102 can generate the restocking notification, as illustrated at block 724. The restocking notification can include an email notification, text message, voicemail, page, or other visual and/or audible indication, etc. to enable a user to identify the location of the pharmaceutical item storage unit and medication that is to be replaced.
It will be understood that fewer, more, or different blocks can be used as part of routine 700. For example, the routine 700 can omit block 720 such that the second medicinal container is not associated with a particular medical patient. Such an association can be reserved for a different time, such as when the second label is read by a label reading station 102 that is in close proximity to the patient (for example, when the label reading station 102 is located in an operating room or in the patient's room).
Similarly, in some embodiments the routine 700 can omit blocks 714 and 716. In certain embodiments, the label reading station 102 can determine the second unique identifier of the second RFID tag as it is printing the medication data onto the second label. For example, in some embodiments the label reading station 102 can include a printer that can print RFID tags. In such embodiments, as the label reading station 102 is printing the medication data onto the second label, it can also print the RFID tag. Accordingly, it can determine and/or know the second unique identifier as it is being printed and does not query the RFID tag to receive the second unique identifier.
In some embodiments, the routine 700 can be used when multiple medications are being combined into a child medicinal container or multiple parent medications are used to create a child medication. In such embodiments, the routine 700 can include additional blocks for querying multiple RFID tags associated with the parent medications that are to be combined and receiving the unique identifiers for each parent medication. In such embodiments, the routine 700 can furthermore verify the status of each parent medication, and generate a second expiration date based on the expiration dates of all of the parent medications. In such embodiments, the routine 700 can print child medication data that includes information regarding all of the parent medications that have been used to form the child medication.
Furthermore, routine 700 can include one or more blocks for tracking the inventory of a medical care provider, tracking administration of a medication to a patient, displaying information regarding patients associated with a particular medical care provider, and/or tracking waste, as described in greater detail above with reference to
One skilled in the relevant art will appreciate that the elements outlined for routine 800 can be implemented by one or many computing devices/components that are associated with the environment 100, including, but not limited to, the label reading station 102, the information processing system 108, and/or the electronic medical records database 110, or any combination thereof. For simplicity, routine 800 has been associated as being generally performed by the label reading station 102, and thus the following illustrative embodiments should not be construed as limiting.
At block 802, the label reading station 102 queries a first label. The first label can include a first RFID tag, or other machine-readable tag, such as a barcode or QR code. To query the first label, the label reading station 102 can emit an electromagnetic wave that activates an RFID tag of the first label or causes the RFID tag to emit a response, capture an image of a barcode or QR code, and/or use a laser scanner that can read a barcode or QR code.
At block 804, the label reading station 102 receives a first unique identifier from the first label. As mentioned previously, each label can include a unique identifier that uniquely identifies that label from all other labels that are tracked by the information processing system 108. In this way each medicinal container associated with the first label can be uniquely identified. As mentioned previously, the information processing system 108 can include a database entry for each unique identifier.
At block 806, the label reading station 102 can verify the status of the medication using the data associated with the first unique identifier, as described in greater detail above with reference to block 706 of
At block 808, the label reading station 102 associates the first label with a medical care provider. To associate the first label with the medical care provider, the label reading station 102 can identify the medical care provider that has logged into or scanned their badge prior to querying the first label. The label reading station 102 can then associate the first unique identifier of the first label with a unique identifier of the medical care provider in the data storage device 114 of the information processing system 108. As part of the association, an entry can be added to the information associated with the first unique identifier of the first label indicating that the medical care provider has accessed, taken control of, is in possession of, and/or has used the medicinal container associated with the first unique identifier.
At block 810, the label reading station 102 can print medication data on a second label having a second unique identifier. In some embodiments, the second label can include an RFID tag that includes the second unique identifier. In certain embodiments, the second label can include a barcode or QR code that includes the second unique identifier. The RFID tag, barcode, and/or QR code can be form part of the label prior to printing the medication data or can be printed onto the label with the medication data. In some embodiments, the label reading station 102 can embed some or all of the medication data into the RFID tag, barcode, and/or QR code.
The medication data can include the name of the medication, the expiration of the medication, the concentration of the medication, and/or the total volume of the medication in the medicinal container. In addition to the medication data, the label reading station 102 can print information regarding the transfer of the medication, including the date and time of the transfer, and the identification of the user that caused the printing to occur. In some embodiments, the label reading station 102 can print the medication data and other data onto the labels described previously with respect to
At block 812, the label reading station 102 queries the second label. As described previously with respect to block 802, the label reading station 102 can query the second label using electromagnetic waves, an image capture, and/or a laser scanner. In some embodiments, the label reading station 102 can query the second label during the printing of the medication data on to the second label. In certain embodiments the label reading station 102 can query the second label after printing the medication data onto the second label. In such embodiments, following the printing of the medication data on the second label, a user can tap or move the label onto or in close proximity to the label reading station 102, scan the label, or capture an image of the label using the label reading station 102.
At block 814, the label reading station 102 receives the second unique identifier from the second label. As mentioned previously, this second unique identifier can be associated with, or used to generate, a new database entry for the data for the child medication or child medicinal container. The database entry can include information similar to the database entry described previously.
At block 816, the label reading station 102 can associate the child medication and/or child medicinal container (using the second unique identifier) with a medical patient. For example, similar to the manner in which the label reading station 102 associates the child medication and/or child medicinal container with the medical care provider, the label reading station 102 can associate the child medication and/or child medicinal container with the medical patient. For example, the second unique identifier can be associated with the medical patient indicating that the contents of the child medicinal container are, or the child medication is, to be used for the medical patient.
It will be understood that fewer, more, or different blocks can be used as part of routine 800. For example, in some embodiments, the routine 800 can include any one or any combination of the blocks described above with respect to routines 700 or 900. In certain embodiments, the routine 800 can omit blocks 812 and 814. In some embodiments, the label reading station 102 can determine the second unique identifier of the second label as it is printing the medication data onto the second label. For example, in some embodiments the label reading station 102 can include a printer that can print RFID tags, barcodes, and/or QR codes. In such embodiments, as the label reading station 102 is printing the medication data onto the second label, it can also print the RFID tag, barcode, and/or QR code. Accordingly, it can determine and/or know the second unique identifier as it is being printed and does not query the RFID tag to receive the second unique identifier.
As described above with respect to routine 700, it will be understood that routine 800 can be used when multiple parent medications are being combined to create a child medication and/or can include one or more blocks for tracking the inventory of a medical care provider, tracking administration of a medication to a patient, displaying information regarding patients associated with a particular medical care provider, and/or tracking waste, as described in greater detail above with reference to
One skilled in the relevant art will appreciate that the elements outlined for routine 900 can be implemented by one or many computing devices/components that are associated with the environment 100, including, but not limited to, the label reading station 102, the information processing system 108, and/or the electronic medical records database 110, or any combination thereof. For simplicity, routine 900 has been associated as being generally performed by the label reading station 102, and thus the following illustrative embodiments should not be construed as limiting.
At block 902, the label reading station 102 queries a label. The label can include a RFID tag, or other machine-readable tag, such as a barcode or QR code. To query the label, the label reading station 102 can emit an electromagnetic wave that activates an RFID tag of the label or causes the RFID tag to emit a response, capture an image of a barcode or QR code, and/or use a laser scanner that can read a barcode or QR code.
At block 904, the label reading station 102 receives a unique identifier from the label. As mentioned previously, each label can include a unique identifier that uniquely identifies that label from all other labels that are tracked by the information processing system 108. In this way each medicinal container associated with the label can be uniquely identified. As mentioned previously, the information processing system 108 can include a database entry for each unique identifier.
At block 906, the label reading station 102 can verify the status of the medication using the data associated with the unique identifier, as described in greater detail above with reference to block 706 of
At block 908, the label reading station 102 associates the label with a medical care provider. To associate the label with the medical care provider, the label reading station 102 can identify the medical care provider that has logged into or scanned their badge prior to querying the label. The label reading station 102 can then associate the unique identifier of the label with a unique identifier of the medical care provider in the data storage device 114 of the information processing system 108. As part of the association, an entry can be added to the information associated with the unique identifier of the label indicating that the medical care provider has accessed, taken control of, is in possession of, and/or has used the medicinal container associated with the unique identifier.
At block 910, the label reading station 102 determines that the pharmaceutical item storage unit does not store a threshold quantity of the medication, and at block 912 the label reading station 102 generates a restocking notification, as described in greater detail above with reference to blocks 722 and 724 of
It will be understood that few or more or different blocks can be used as part of routine 900. For example, in some embodiments, the routine 900 can include any one or any combination of the blocks described above with respect to routines 700 and/or 800. Furthermore, as described above with respect to routines 700 and 800, it will be understood that routine 900 can include one or more blocks for tracking the inventory of a medical care provider, tracking administration of a medication to a patient, displaying information regarding patients associated with a particular medical care provider, and/or tracking waste, as described in greater detail above with reference to
It will be understood that the methods and systems described herein can be used in other applications. For example, the process of determining the second expiration date can be used in conjunction with the systems and methods described in U.S. patent application Ser. Nos. 14/472,410, and 13/554,342, incorporated herein by reference. For example, when a medication having a multiple expiration dates or a variable expiration date (for example, a refrigerated/non-refrigerated expiration date, a sealed/broken seal expiration date, and/or a vial/syringe expiration date, etc.), such as a multi-dose medication, is included in a pharmacy kit, the information processing system 108 can verify the medication based on the earliest expiration date or active expiration date. In addition, when an event (for example, breaking the seal, etc.) occurs that alters the expiration date of the medication, the information processing system 108 can update the medication data in the data storage device 114 or in the RFID tag with the new expiration date.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list. Likewise the term “and/or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list.
Depending on the embodiment, certain operations, acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all are necessary for the practice of the algorithms). Moreover, in certain embodiments, operations, acts, functions, or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein. Software and other modules may reside and execute on servers, workstations, personal computers, computerized tablets, PDAs, and other computing devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, interactive voice response, command line interfaces, and other suitable interfaces.
Further, the processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. In addition, two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems and/or computing devices. Likewise, the data storage devices shown can represent physical and/or logical data storage, including, for example, storage area networks or other distributed storage systems. Moreover, in some embodiments the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.
Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams, may be implemented by computer program instructions. Such instructions may be provided to a processor of a general purpose computer, special purpose computer, specially-equipped computer (e.g., comprising a high-performance database server, a graphics subsystem, etc.) or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor(s) of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks.
These computer program instructions may also be stored in a non-transitory computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computing device or other programmable data processing apparatus to cause a series of operations to be performed on the computing device or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
To reduce the number of claims, certain aspects of the invention are presented below in certain claim forms, but the applicant contemplates the various aspects of the invention in any number of claim forms. Any claims intended to be treated under 35 U.S.C. § 112(f) will begin with the words “means for”, but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application, in either this application or in a continuing application.
The present application is a continuation of U.S. patent application Ser. No. 17/177,914, filed on Feb. 17, 2021, entitled MEDICATION TRACKING, which is a continuation of U.S. patent application Ser. No. 16/822,459, filed on Mar. 18, 2020, entitled MEDICATION TRACKING, which is a continuation of U.S. patent application Ser. No. 16/103,001, filed Aug. 14, 2018, entitled MEDICATION TRACKING, which is a continuation of U.S. patent application Ser. No. 15/426,302, filed Feb. 7, 2017, entitled MEDICATION TRACKING, which is a continuation of U.S. patent application Ser. No. 14/876,533, filed Oct. 6, 2015, entitled MEDICATION TRACKING, which is a continuation of U.S. patent application Ser. No. 14/563,732, filed Dec. 8, 2014, entitled MEDICATION TRACKING, which claims priority to U.S. Provisional Patent App. No. 61/913,337, filed Dec. 8, 2013, entitled ENHANCED MEDICATION MANAGEMENT IN THE OPERATING ROOM ENVIRONMENT, U.S. Patent Provisional App. No. 62/000,570, filed May 20, 2014, entitled ANESTHESIA LABEL CREATION AND MIXTURE PREFERENCES SOLUTION, U.S. Patent App. No. 62/020,576, filed Jul. 3, 2014, entitled MULTI-DOSE INVENTORY SOLUTION, and U.S. Patent App. No. 62/062,845, filed Oct. 11, 2014, entitled ANESTHESIA CHECK; AUTOMATING AND IMPROVING THE WORKFLOW OF ANESTHESIA LABELING, ADMINISTRATION, AND INVENTORY RECONCILIATION, each of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4884827 | Kelley | Dec 1989 | A |
| 4961533 | Teller et al. | Oct 1990 | A |
| 5713485 | Liff et al. | Feb 1998 | A |
| 5930145 | Yuyama et al. | Jul 1999 | A |
| 5963134 | Bowers et al. | Oct 1999 | A |
| 5986662 | Argiro et al. | Nov 1999 | A |
| 6112502 | Frederick et al. | Sep 2000 | A |
| 6249299 | Tainer | Jun 2001 | B1 |
| 6275157 | Mays et al. | Aug 2001 | B1 |
| 6294999 | Yarin et al. | Sep 2001 | B1 |
| 6330351 | Yasunaga | Dec 2001 | B1 |
| 6574166 | Niemiec | Jun 2003 | B2 |
| 6632619 | Harrison et al. | Oct 2003 | B1 |
| 6771369 | Rzasa et al. | Aug 2004 | B2 |
| 6825864 | Botten et al. | Nov 2004 | B2 |
| 6847861 | Lunak et al. | Jan 2005 | B2 |
| 6851615 | Jones | Feb 2005 | B2 |
| 6861954 | Levin | Mar 2005 | B2 |
| 6877658 | Raistrick et al. | Apr 2005 | B2 |
| 6879876 | O'Dougherty et al. | Apr 2005 | B2 |
| 6900021 | Harrison et al. | May 2005 | B1 |
| 6933849 | Sawyer | Aug 2005 | B2 |
| 6935560 | Andreasson et al. | Aug 2005 | B2 |
| 6952681 | McQuade et al. | Oct 2005 | B2 |
| 6985870 | Martucci et al. | Jan 2006 | B2 |
| 6992574 | Aupperle et al. | Jan 2006 | B2 |
| 6994249 | Peterka et al. | Feb 2006 | B2 |
| 7036729 | Chung | May 2006 | B2 |
| 7061831 | De La Huerga | Jun 2006 | B2 |
| 7111780 | Broussard et al. | Sep 2006 | B2 |
| 7116343 | Botten et al. | Oct 2006 | B2 |
| 7118029 | Nycz et al. | Oct 2006 | B2 |
| 7140542 | Andreasson et al. | Nov 2006 | B2 |
| 7146247 | Kirsch et al. | Dec 2006 | B2 |
| 7151456 | Godfrey | Dec 2006 | B2 |
| 7158030 | Chung | Jan 2007 | B2 |
| 7165077 | Kalies | Jan 2007 | B2 |
| 7175081 | Andreasson et al. | Feb 2007 | B2 |
| 7177721 | Kirsch et al. | Feb 2007 | B2 |
| 7178729 | Shaffer et al. | Feb 2007 | B2 |
| 7182256 | Andreasson et al. | Feb 2007 | B2 |
| 7212100 | Terenna | May 2007 | B2 |
| 7212127 | Jacober et al. | May 2007 | B2 |
| 7227469 | Varner et al. | Jun 2007 | B2 |
| 7232066 | Andreasson et al. | Jun 2007 | B2 |
| 7253736 | Tethrake et al. | Aug 2007 | B2 |
| 7256699 | Tethrake et al. | Aug 2007 | B2 |
| 7263501 | Tirinato et al. | Aug 2007 | B2 |
| 7264323 | Tainer et al. | Sep 2007 | B2 |
| 7268684 | Tethrake et al. | Sep 2007 | B2 |
| 7275645 | Mallett et al. | Oct 2007 | B2 |
| 7299981 | Hickle et al. | Nov 2007 | B2 |
| 7316231 | Hickle | Jan 2008 | B2 |
| 7317393 | Maloney | Jan 2008 | B2 |
| 7318529 | Mallett et al. | Jan 2008 | B2 |
| 7339550 | Hayama et al. | Mar 2008 | B2 |
| 7341147 | Mallett et al. | Mar 2008 | B2 |
| 7348884 | Higham | Mar 2008 | B2 |
| 7354884 | Hada et al. | Apr 2008 | B2 |
| 7362228 | Nycz et al. | Apr 2008 | B2 |
| 7375737 | Botten et al. | May 2008 | B2 |
| 7394383 | Hager et al. | Jul 2008 | B2 |
| 7440818 | Handfield et al. | Oct 2008 | B2 |
| 7446747 | Youngblood et al. | Nov 2008 | B2 |
| 7454880 | Austin et al. | Nov 2008 | B1 |
| 7486188 | Van Alstyne | Feb 2009 | B2 |
| 7492257 | Tethrake et al. | Feb 2009 | B2 |
| 7492261 | Cambre et al. | Feb 2009 | B2 |
| 7504954 | Spaeder | Mar 2009 | B2 |
| 7518502 | Austin et al. | Apr 2009 | B2 |
| 7518516 | Azevedo et al. | Apr 2009 | B2 |
| 7551089 | Sawyer | Jun 2009 | B2 |
| 7559483 | Hickle et al. | Jul 2009 | B2 |
| 7564364 | Zweig | Jul 2009 | B2 |
| 7630791 | Nguyen et al. | Dec 2009 | B2 |
| 7639136 | Wass et al. | Dec 2009 | B1 |
| 7644016 | Nycz et al. | Jan 2010 | B2 |
| 7672872 | Shanton | Mar 2010 | B2 |
| 7706915 | Mohapatra et al. | Apr 2010 | B2 |
| 7706916 | Hilton | Apr 2010 | B2 |
| 7712670 | Sauerwein, Jr. et al. | May 2010 | B2 |
| 7715277 | De La Huerga | May 2010 | B2 |
| 7729597 | Wright et al. | Jun 2010 | B2 |
| 7734157 | Wright et al. | Jun 2010 | B2 |
| 7737858 | Matityaho | Jun 2010 | B2 |
| 7747477 | Louie et al. | Jun 2010 | B1 |
| 7752085 | Monroe | Jul 2010 | B2 |
| 7772964 | Tethrake et al. | Aug 2010 | B2 |
| 7775056 | Lowenstein | Aug 2010 | B2 |
| 7783163 | Wright et al. | Aug 2010 | B2 |
| 7783174 | Wright et al. | Aug 2010 | B2 |
| 7801422 | Wright et al. | Sep 2010 | B2 |
| 7815117 | Tuschel et al. | Oct 2010 | B2 |
| 7834765 | Sawyer | Nov 2010 | B2 |
| 7834766 | Sawyer | Nov 2010 | B2 |
| 7837093 | Leu et al. | Nov 2010 | B1 |
| 7837107 | Leu et al. | Nov 2010 | B1 |
| 7858841 | Krautkramer et al. | Dec 2010 | B2 |
| 7860730 | Goodall et al. | Dec 2010 | B1 |
| 7868754 | Salvat, Jr. | Jan 2011 | B2 |
| 7893876 | Brown et al. | Feb 2011 | B2 |
| 7908030 | Handfield et al. | Mar 2011 | B2 |
| 7918830 | Langan et al. | Apr 2011 | B2 |
| 7928844 | Mackenzie et al. | Apr 2011 | B2 |
| 7933033 | Ohishi et al. | Apr 2011 | B2 |
| 7976508 | Hoag | Jul 2011 | B2 |
| 7985711 | Tohmatsu et al. | Jul 2011 | B2 |
| 7990272 | Wass et al. | Aug 2011 | B2 |
| 7996286 | Kreiner et al. | Aug 2011 | B2 |
| 8002174 | Coyne, III et al. | Aug 2011 | B2 |
| 8006903 | Braun et al. | Aug 2011 | B2 |
| 8009913 | Greyshock | Aug 2011 | B2 |
| 8019471 | Bogash et al. | Sep 2011 | B2 |
| 8031347 | Edwards et al. | Oct 2011 | B2 |
| 8042738 | Cloix | Oct 2011 | B2 |
| 8049627 | Addante | Nov 2011 | B1 |
| 8063925 | Tainer et al. | Nov 2011 | B2 |
| 8065858 | Leu et al. | Nov 2011 | B2 |
| 8072635 | Roberts et al. | Dec 2011 | B2 |
| 8077041 | Stern et al. | Dec 2011 | B2 |
| 8082192 | Nycz et al. | Dec 2011 | B2 |
| 8099339 | Pinsonneault et al. | Jan 2012 | B1 |
| 8108068 | Boucher et al. | Jan 2012 | B1 |
| 8111159 | Andreasson et al. | Feb 2012 | B2 |
| 8112175 | Handfield et al. | Feb 2012 | B2 |
| 8131397 | Vahlberg et al. | Mar 2012 | B2 |
| 8154390 | Heath et al. | Apr 2012 | B2 |
| 8174392 | Sagbhini et al. | May 2012 | B1 |
| 8186587 | Zmood et al. | May 2012 | B2 |
| 8212677 | Ferguson | Jul 2012 | B2 |
| 8219413 | Martinez et al. | Jul 2012 | B2 |
| 8224483 | Ansari et al. | Jul 2012 | B1 |
| 8231749 | Dent et al. | Jul 2012 | B2 |
| 8258961 | Phillips et al. | Sep 2012 | B2 |
| 8261939 | Knoth | Sep 2012 | B2 |
| 8271128 | Schultz | Sep 2012 | B1 |
| 8279069 | Sawyer | Oct 2012 | B2 |
| 8283287 | Aihara et al. | Oct 2012 | B2 |
| 8284059 | Ross | Oct 2012 | B2 |
| 8285083 | Canessa et al. | Oct 2012 | B2 |
| 8285607 | Danilewitz | Oct 2012 | B2 |
| 8286222 | Silverbrook et al. | Oct 2012 | B2 |
| 8292173 | Yturralde et al. | Oct 2012 | B2 |
| 8292186 | Deloche et al. | Oct 2012 | B2 |
| 8296950 | Colbrunn et al. | Oct 2012 | B2 |
| 8313024 | Marino | Nov 2012 | B2 |
| 8319607 | Grimlund et al. | Nov 2012 | B2 |
| 8328082 | Bochenko et al. | Dec 2012 | B1 |
| 8339649 | Ohishi et al. | Dec 2012 | B2 |
| 8341041 | Hull | Dec 2012 | B2 |
| 8346632 | Saghbini | Jan 2013 | B2 |
| 8355753 | Bochenko et al. | Jan 2013 | B2 |
| 8355962 | Delaney et al. | Jan 2013 | B2 |
| 8359338 | Butterfield et al. | Jan 2013 | B2 |
| 8371448 | Reaux | Feb 2013 | B1 |
| 8376228 | DeVet et al. | Feb 2013 | B2 |
| 8384545 | Hussain et al. | Feb 2013 | B2 |
| 8385972 | Bochenko et al. | Feb 2013 | B2 |
| 8386070 | Eliuk et al. | Feb 2013 | B2 |
| 8394053 | Bochenko et al. | Mar 2013 | B2 |
| 8403212 | van Esch | Mar 2013 | B2 |
| 8403224 | Fedorko et al. | Mar 2013 | B2 |
| 8405508 | Burke | Mar 2013 | B2 |
| 8438067 | Omura et al. | May 2013 | B2 |
| 8461076 | Okada et al. | Jun 2013 | B2 |
| 8483550 | Wright et al. | Jul 2013 | B2 |
| 8509604 | Wright et al. | Aug 2013 | B2 |
| 8515251 | Wright et al. | Aug 2013 | B2 |
| 8519849 | Ross-Messemer | Aug 2013 | B2 |
| 8530379 | Shimizu et al. | Sep 2013 | B2 |
| 8564416 | Steven et al. | Oct 2013 | B2 |
| 8565552 | Sommer et al. | Oct 2013 | B2 |
| 8582171 | Srnka et al. | Nov 2013 | B2 |
| 8589271 | Evans | Nov 2013 | B2 |
| 8593278 | Churbock et al. | Nov 2013 | B2 |
| 8593678 | Ohishi et al. | Nov 2013 | B2 |
| D694817 | Adam et al. | Dec 2013 | S |
| 8600548 | Bossi et al. | Dec 2013 | B2 |
| 8606596 | Bochenko et al. | Dec 2013 | B1 |
| 8636202 | Keefe et al. | Jan 2014 | B2 |
| 8639525 | Levine et al. | Jan 2014 | B2 |
| 8686859 | Hussain et al. | Apr 2014 | B2 |
| 8699054 | Edwards et al. | Apr 2014 | B2 |
| 8702674 | Bochenko | Apr 2014 | B2 |
| 8723674 | Conley et al. | May 2014 | B2 |
| 8749356 | Hussain et al. | Jun 2014 | B2 |
| 8755056 | Edwards et al. | Jun 2014 | B2 |
| 8825680 | Burke et al. | Sep 2014 | B2 |
| 8838215 | John et al. | Sep 2014 | B2 |
| 8868616 | Otto et al. | Oct 2014 | B1 |
| 8893970 | Keefe et al. | Nov 2014 | B2 |
| 8922435 | Fontecchio et al. | Dec 2014 | B2 |
| 8935280 | Bauman et al. | Jan 2015 | B2 |
| 8945066 | Bochenko et al. | Feb 2015 | B2 |
| 8948478 | Keefe et al. | Feb 2015 | B2 |
| 8985388 | Ratnakar | Mar 2015 | B2 |
| 8990099 | MacDonald et al. | Mar 2015 | B2 |
| 9037479 | MacDonald et al. | May 2015 | B1 |
| 9058412 | MacDonald et al. | Jun 2015 | B2 |
| 9058413 | MacDonald et al. | Jun 2015 | B2 |
| 9058435 | Keefe et al. | Jun 2015 | B2 |
| 9171280 | Gitchell | Oct 2015 | B2 |
| 9189769 | Caputo et al. | Nov 2015 | B2 |
| 9367665 | MacDonald et al. | Jun 2016 | B2 |
| 9449296 | MacDonald et al. | Sep 2016 | B2 |
| 9539374 | Halpern | Jan 2017 | B2 |
| 9582644 | Gitchell et al. | Feb 2017 | B2 |
| 9734294 | MacDonald et al. | Aug 2017 | B2 |
| 9805169 | MacDonald et al. | Oct 2017 | B2 |
| 10083766 | Gitchell et al. | Sep 2018 | B2 |
| 10210954 | Caputo et al. | Feb 2019 | B2 |
| 10600513 | Gitchell et al. | Mar 2020 | B2 |
| 10609845 | Elizondo, II | Mar 2020 | B2 |
| 10621394 | Hussain et al. | Apr 2020 | B2 |
| 10643743 | Caputo et al. | May 2020 | B2 |
| 10658077 | Hussain et al. | May 2020 | B2 |
| 10658078 | Caputo et al. | May 2020 | B2 |
| 10664740 | Elizondo, II | May 2020 | B2 |
| 10853380 | Agnew et al. | Dec 2020 | B1 |
| 10930393 | Gitchell et al. | Feb 2021 | B2 |
| 11017352 | MacDonald et al. | May 2021 | B2 |
| 11037342 | Agnew et al. | Jun 2021 | B1 |
| 11139075 | MacDonald et al. | Oct 2021 | B2 |
| 11551797 | Kress-Spatz et al. | Jan 2023 | B2 |
| 11557393 | Gitchell et al. | Jan 2023 | B2 |
| 11664105 | Yanowitz et al. | May 2023 | B2 |
| 20020026330 | Klein | Feb 2002 | A1 |
| 20020049650 | Reff | Apr 2002 | A1 |
| 20020087360 | Pettit | Jul 2002 | A1 |
| 20020087362 | Cobb et al. | Jul 2002 | A1 |
| 20020087554 | Seelinger | Jul 2002 | A1 |
| 20030055685 | Cobb et al. | Mar 2003 | A1 |
| 20030074223 | Hickle et al. | Apr 2003 | A1 |
| 20030102970 | Creel et al. | Jun 2003 | A1 |
| 20030160698 | Andreasson et al. | Aug 2003 | A1 |
| 20030216974 | Browne | Nov 2003 | A1 |
| 20040008123 | Carrender et al. | Jan 2004 | A1 |
| 20040032330 | Hoffman | Feb 2004 | A1 |
| 20040051368 | Caputo et al. | Mar 2004 | A1 |
| 20040057609 | Weinberg | Mar 2004 | A1 |
| 20040081669 | Greeven et al. | Apr 2004 | A1 |
| 20040158507 | Meek et al. | Aug 2004 | A1 |
| 20040178071 | Harrison et al. | Sep 2004 | A1 |
| 20040215486 | Braverman | Oct 2004 | A1 |
| 20040225528 | Brock | Nov 2004 | A1 |
| 20050014849 | Pettit et al. | Jan 2005 | A1 |
| 20050060171 | Molnar | Mar 2005 | A1 |
| 20050062603 | Fuerst et al. | Mar 2005 | A1 |
| 20050108044 | Koster | May 2005 | A1 |
| 20050125097 | Chudy et al. | Jun 2005 | A1 |
| 20050127176 | Dickinson | Jun 2005 | A1 |
| 20050149378 | Cyr et al. | Jul 2005 | A1 |
| 20050149414 | Schrodt et al. | Jul 2005 | A1 |
| 20050184151 | DiMaggio et al. | Aug 2005 | A1 |
| 20050283259 | Wolpow | Dec 2005 | A1 |
| 20050285732 | Sengupta et al. | Dec 2005 | A1 |
| 20050285746 | Sengupta et al. | Dec 2005 | A1 |
| 20060006999 | Walczyk et al. | Jan 2006 | A1 |
| 20060043177 | Nycz et al. | Mar 2006 | A1 |
| 20060043179 | Nycz et al. | Mar 2006 | A1 |
| 20060065726 | Andreasson et al. | Mar 2006 | A1 |
| 20060109105 | Varner et al. | May 2006 | A1 |
| 20060132311 | Kruest et al. | Jun 2006 | A1 |
| 20060145871 | Donati et al. | Jul 2006 | A1 |
| 20060152338 | Hsu | Jul 2006 | A1 |
| 20060152364 | Walton | Jul 2006 | A1 |
| 20060152367 | Narayanaswamy | Jul 2006 | A1 |
| 20060208886 | Beamer | Sep 2006 | A1 |
| 20060244593 | Nycz et al. | Nov 2006 | A1 |
| 20060267731 | Chen | Nov 2006 | A1 |
| 20070001809 | Kodukula et al. | Jan 2007 | A1 |
| 20070008399 | Botten et al. | Jan 2007 | A1 |
| 20070023512 | Miller et al. | Feb 2007 | A1 |
| 20070023513 | Andreasson et al. | Feb 2007 | A1 |
| 20070074722 | Giroux et al. | Apr 2007 | A1 |
| 20070114279 | Lessing et al. | May 2007 | A1 |
| 20070150382 | Danilewitz | Jun 2007 | A1 |
| 20070187475 | MacLeod | Aug 2007 | A1 |
| 20070188306 | Tethrake et al. | Aug 2007 | A1 |
| 20070200702 | Chung | Aug 2007 | A1 |
| 20070213659 | Trovato et al. | Sep 2007 | A1 |
| 20070213684 | Hickle et al. | Sep 2007 | A1 |
| 20070229268 | Swan et al. | Oct 2007 | A1 |
| 20070272746 | Ortiz et al. | Nov 2007 | A1 |
| 20080004908 | Oh et al. | Jan 2008 | A1 |
| 20080012687 | Rubinstein | Jan 2008 | A1 |
| 20080045930 | Makin et al. | Feb 2008 | A1 |
| 20080046295 | Albrecht | Feb 2008 | A1 |
| 20080061153 | Hickle et al. | Mar 2008 | A1 |
| 20080094214 | Azevedo et al. | Apr 2008 | A1 |
| 20080122878 | Keefe et al. | May 2008 | A1 |
| 20080128482 | Chen et al. | Jun 2008 | A1 |
| 20080129496 | Koblasz | Jun 2008 | A1 |
| 20080150722 | Jackson | Jun 2008 | A1 |
| 20080157967 | Jones et al. | Jul 2008 | A1 |
| 20080172253 | Chung et al. | Jul 2008 | A1 |
| 20080186180 | Butler et al. | Aug 2008 | A1 |
| 20080191013 | Liberatore | Aug 2008 | A1 |
| 20080218307 | Schoettle | Sep 2008 | A1 |
| 20080228160 | Harrison | Sep 2008 | A1 |
| 20080231456 | Matityaho | Sep 2008 | A1 |
| 20080243088 | Evans | Oct 2008 | A1 |
| 20080270178 | McRae et al. | Oct 2008 | A1 |
| 20080296373 | Smood et al. | Dec 2008 | A1 |
| 20080297356 | Oberle | Dec 2008 | A1 |
| 20080306772 | Shahrokh | Dec 2008 | A1 |
| 20080316045 | Sriharto et al. | Dec 2008 | A1 |
| 20090002173 | Bergsten et al. | Jan 2009 | A1 |
| 20090020442 | Dietrich et al. | Jan 2009 | A1 |
| 20090058653 | Geissler et al. | Mar 2009 | A1 |
| 20090144087 | Kelsch et al. | Jun 2009 | A1 |
| 20090153290 | Bierach | Jun 2009 | A1 |
| 20090164042 | Handfield et al. | Jun 2009 | A1 |
| 20090194987 | Christie et al. | Aug 2009 | A1 |
| 20090224891 | Vishik et al. | Sep 2009 | A1 |
| 20090231138 | Cheung et al. | Sep 2009 | A1 |
| 20090267740 | Pizzuto et al. | Oct 2009 | A1 |
| 20090267772 | Dehnadi | Oct 2009 | A1 |
| 20090277815 | Kohl | Nov 2009 | A1 |
| 20090294521 | De La Huerga | Dec 2009 | A1 |
| 20100022953 | Bochenko et al. | Jan 2010 | A1 |
| 20100022987 | Bochenko | Jan 2010 | A1 |
| 20100036310 | Hillman | Feb 2010 | A1 |
| 20100036678 | Bray | Feb 2010 | A1 |
| 20100036755 | Saghbini | Feb 2010 | A1 |
| 20100042439 | Martinez et al. | Feb 2010 | A1 |
| 20100079337 | Hsu et al. | Apr 2010 | A1 |
| 20100098425 | Kewitsch | Apr 2010 | A1 |
| 20100108761 | Nycz et al. | May 2010 | A1 |
| 20100114951 | Bauman et al. | May 2010 | A1 |
| 20100185458 | Calderwood et al. | Jul 2010 | A1 |
| 20100204659 | Bochenko | Aug 2010 | A1 |
| 20100217621 | Schoenberg et al. | Aug 2010 | A1 |
| 20100219097 | Ramasubramanian et al. | Sep 2010 | A1 |
| 20100238039 | Tethrake et al. | Sep 2010 | A1 |
| 20100268548 | Garrett et al. | Oct 2010 | A1 |
| 20100275625 | Lowenstein | Nov 2010 | A1 |
| 20100299158 | Siegel | Nov 2010 | A1 |
| 20100328474 | Hsieh | Dec 2010 | A1 |
| 20100332246 | Fedorko et al. | Dec 2010 | A1 |
| 20110006879 | Bartos | Jan 2011 | A1 |
| 20110060455 | Bogash et al. | Mar 2011 | A1 |
| 20110063091 | Kang | Mar 2011 | A1 |
| 20110068922 | Ross | Mar 2011 | A1 |
| 20110093279 | Levine et al. | Apr 2011 | A1 |
| 20110112682 | Matsukawa et al. | May 2011 | A1 |
| 20110115612 | Kulinets et al. | May 2011 | A1 |
| 20110125315 | Handfield et al. | May 2011 | A1 |
| 20110131056 | Chudy et al. | Jun 2011 | A1 |
| 20110139871 | Yturralde et al. | Jun 2011 | A1 |
| 20110161112 | Keefe et al. | Jun 2011 | A1 |
| 20110163871 | Einav et al. | Jul 2011 | A1 |
| 20110166878 | Louie et al. | Jul 2011 | A1 |
| 20110184751 | Holmes | Jul 2011 | A1 |
| 20110187549 | Balasing | Aug 2011 | A1 |
| 20110202174 | Bogash et al. | Aug 2011 | A1 |
| 20110225100 | Sangal et al. | Sep 2011 | A1 |
| 20110227722 | Salvat, Jr. | Sep 2011 | A1 |
| 20110240729 | Schuck | Oct 2011 | A1 |
| 20110257991 | Shukla | Oct 2011 | A1 |
| 20110270441 | Handfield et al. | Nov 2011 | A1 |
| 20110291809 | Niemiec et al. | Dec 2011 | A1 |
| 20110301446 | Kamen | Dec 2011 | A1 |
| 20110313395 | Krulevitch et al. | Dec 2011 | A1 |
| 20120037266 | Bochenko | Feb 2012 | A1 |
| 20120041778 | Kraft | Feb 2012 | A1 |
| 20120044054 | Hussain et al. | Feb 2012 | A1 |
| 20120061463 | Burke | Mar 2012 | A1 |
| 20120089411 | Srnka et al. | Apr 2012 | A1 |
| 20120089418 | Kamath et al. | Apr 2012 | A1 |
| 20120116798 | Heath et al. | May 2012 | A1 |
| 20120125994 | Heath et al. | May 2012 | A1 |
| 20120130534 | Wurm | May 2012 | A1 |
| 20120173440 | Becker et al. | Jul 2012 | A1 |
| 20120177256 | Keefe et al. | Jul 2012 | A1 |
| 20120179132 | Valk et al. | Jul 2012 | A1 |
| 20120185951 | Bauman et al. | Jul 2012 | A1 |
| 20120209619 | Knotts et al. | Aug 2012 | A1 |
| 20120240067 | Bauman et al. | Sep 2012 | A1 |
| 20120273087 | Einy et al. | Nov 2012 | A1 |
| 20120278096 | Holness | Nov 2012 | A1 |
| 20120278228 | Rubinstein | Nov 2012 | A1 |
| 20120323208 | Bochenko et al. | Dec 2012 | A1 |
| 20120325330 | Prince et al. | Dec 2012 | A1 |
| 20130018356 | Prince et al. | Jan 2013 | A1 |
| 20130035950 | MacDonald et al. | Feb 2013 | A1 |
| 20130038452 | Sawyer | Feb 2013 | A1 |
| 20130041784 | Danilewitz | Feb 2013 | A1 |
| 20130092727 | Edwards et al. | Apr 2013 | A1 |
| 20130105568 | Jablonski et al. | May 2013 | A1 |
| 20130151005 | Gerold et al. | Jun 2013 | A1 |
| 20130191149 | Kolberg et al. | Jul 2013 | A1 |
| 20130221082 | Botten | Aug 2013 | A1 |
| 20130221087 | Keefe et al. | Aug 2013 | A1 |
| 20130225945 | Prince et al. | Aug 2013 | A1 |
| 20130327822 | Keefe et al. | Dec 2013 | A1 |
| 20140060729 | Srnka et al. | Mar 2014 | A1 |
| 20140066880 | Prince et al. | Mar 2014 | A1 |
| 20140114472 | Bossi et al. | Apr 2014 | A1 |
| 20140117081 | Jablonski et al. | May 2014 | A1 |
| 20140136229 | Levine et al. | May 2014 | A1 |
| 20140142975 | Keefe et al. | May 2014 | A1 |
| 20140184390 | Elizondo, II | Jul 2014 | A1 |
| 20140184391 | Elizondo, II | Jul 2014 | A1 |
| 20140197954 | Caputo et al. | Jul 2014 | A1 |
| 20140210596 | Hussain et al. | Jul 2014 | A1 |
| 20140262919 | Hussain et al. | Sep 2014 | A1 |
| 20140263614 | Keefe et al. | Sep 2014 | A1 |
| 20140276213 | Bochenko | Sep 2014 | A1 |
| 20140282197 | Keefe et al. | Sep 2014 | A1 |
| 20140291397 | Caputo et al. | Oct 2014 | A1 |
| 20140367080 | Hussain et al. | Dec 2014 | A1 |
| 20140372145 | MacDonald et al. | Dec 2014 | A1 |
| 20150058182 | Kress-Spatz et al. | Feb 2015 | A1 |
| 20150235005 | MacDonald et al. | Aug 2015 | A1 |
| 20150339622 | MacDonald et al. | Nov 2015 | A1 |
| 20170132734 | MacDonald et al. | May 2017 | A1 |
| 20180039758 | MacDonald et al. | Feb 2018 | A1 |
| 20190088354 | Yanowitz et al. | Mar 2019 | A1 |
| 20190272396 | Clouser et al. | Sep 2019 | A1 |
| 20200013494 | Caputo et al. | Jan 2020 | A1 |
| 20200167534 | Elizondo, II | May 2020 | A1 |
| 20200357509 | Gitchell et al. | Nov 2020 | A1 |
| 20210043291 | James et al. | Feb 2021 | A1 |
| 20210383323 | MacDonald et al. | Dec 2021 | A1 |
| 20220238219 | MacDonald et al. | Jul 2022 | A1 |
| 20220282199 | Vann | Sep 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 722 328 | Oct 2009 | CA |
| 2 790 220 | Jun 2013 | CA |
| 102791310 | Dec 2014 | CN |
| 2 496 283 | Sep 2012 | EP |
| 201204914 | Oct 2013 | IN |
| WO 02095675 | Nov 2002 | WO |
| WO 03071943 | Sep 2003 | WO |
| WO 2006026246 | Mar 2006 | WO |
| WO 2006135830 | Dec 2006 | WO |
| WO 2010074781 | Jul 2010 | WO |
| WO 2011056888 | Sep 2011 | WO |
| WO 2011115676 | Sep 2011 | WO |
| WO 2011150013 | Dec 2011 | WO |
| WO 2013082423 | Jun 2013 | WO |
| WO 2013116873 | Aug 2013 | WO |
| WO 2013134256 | Sep 2013 | WO |
| WO 2014159928 | Oct 2014 | WO |
| WO 2014189834 | Nov 2014 | WO |
| WO 2015026387 | Feb 2015 | WO |
| Entry |
|---|
| “AmerisourceBergen Specialty Group Reconfigures Cubixx Medical Cabinet”, Jan. 9, 2011, pp. 2, <https://web.archive.org/web/20180620192642/http://pharmaceuticalcommerce.com/supply-chain- logistics/amerisourcebergen-specialty-group-reconfigures-cubixx-medical-cabinet/>. |
| Bacheldor, Beth, “ASD Healthcare Deploys RFID Refrigerated Drug Cabinets”, RFID Journal, Sep. 24, 2007, p. 1. <http://www.rfidjournal.com/articles/view?3632>. |
| Bacheldor, Beth, “Cardinal Health Readies Item-Level Pilot”, RFID Journal, May 31, 2006, p. 1. <http://www.rfidjournal.com/articles/view?2380>. |
| Bacheldor, Beth, “UCSD Medical Center Expands Its RFID Deployment”, RFID Journal, Oct. 29, 2008, pp. 2. <http://www.rfidjournal.com/articles/view?4423>. |
| Bacheldor, Beth, “UMass Med Center Finds Big Savings Through Tagging”, RFID Journal, Nov. 21, 2007, pp. 2. <http://www.rfidjournal.com/articles/view?3763/2>. |
| Barlas, Stephen, “Pharmacy Product Tracing Likely to Go National—Costs to Pharmacies Worrisome,” Pharmacy & Therapeutics, Jan. 2009, vol. 34 No. 1, p. 14. |
| Baum, “How did RFID help University of MD Medical Center cut medication error rate?” Med City News, https://medcitynews.com/2013/12/rfid-help-university-md-medical-center-cut-medication-error-rate/?rf=1, Dec. 4, 2013, 2 Pages. |
| Becker et al., “SmartDrawer: RFID-Based Smart Medicine Drawer for Assistive Environments”, Conference: Proceedings of the 2nd International Conference on Pervasive Technologies Related to Assistive Environments, PETRA 2009, Corfu, Greece, Jun. 9-13, 2009, pp. 8. |
| Belson, D., “Storage, Distribution, and Dispensing of Medical Supplies,” CREATE Interim Report Under FEMA Grant EMW-2004-GR-0112, Apr. 21, 2005, pp. 1-36. |
| Bendavid et al., “Using RFID to Improve Hospital Supply Chain Management for High Value and Consignment Items”, Procedia Computer Science, vol. 5, 2011, pp. 849-856. |
| Bendavid et al., “Redesigning the Replenishment Process of Medical Supplies in Hospitals with RFID”, Business Process Management Journal, 2010, vol. 16, No. 6, pp. 991-1013. |
| Brown, Dennis E., “Rfid Implementation”, McGraw-Hill Communications, 2007, Ch. 3 & 7 (portions), pp. 62-65, 81, 92-96, 106-113, 188-193 & 429. |
| Bryant, Blake, “Hacking SIEMs to Catch Hackers: Decreasing the Mean Time to Respond to Network Security Events with a Novel Threat Ontology in SIEM Software”, Master's Thesis, University of Kansas, 2016, pp. 257. |
| Çakici et al., “Using RFID for the Management of Pharmaceutical Inventory-System Optimization and Shrinkage Control,” Decision Support Systems, 2011, pp. 842-852. |
| Cangialosi et al., “Leveraging RFID in Hospitals: Patient Life Cycle and Mobility Perspectives”, IEEE Applications & Practice, Sep. 2007, pp. 18-23. |
| Chao et al., “Determining Technology Trends and Forecasts of RFID by a Historical Review and Bibliometric Analysis from 1991 to 2005”, Technovation, vol. 27, 2007, pp. 268-279. |
| Collins, “RFID Cabinet Manages Medicine”, RFID Journal, Aug. 12, 2004, p. 1. <http://www.rfidjournal.com/articles/pdf?1081>. |
| CPG Sec. 400.210, Radiofrequency Identification Feasibility Studies and Pilot Programs for Drugs Nov. 2004 Compliance Policy Guide available at: <http://www.fda.gov/ICECI/ComplianceManuals/CompliancePolicyGuidanceManual/ucm074357.htm>. |
| “Crash Cart Inventory Checklist”, Outpatient Surgery Magazine, Oct. 2004, p. 1. <http://www.outpatientsurgery.net/resources/forms/2004/pdf/OutpatientSurgeryMagazine_0410_crashCart.pdf>. |
| Curtin et al., “Making the ‘MOST’ out of RFID: a research agenda for the study of the adoption, usage and impact of RFID,” Information Technology Management, Apr. 2007, pp. 87-110. |
| “Data Gathering Developments”, Manufacturing Chemist, Feb. 1, 2005, p. 24. <https://www.manufacturingchemist.com/news/article_page/Data_gathering_developments/35805>. |
| Dutta et al., “RFID and Operations Management: Technology, Value, and Incentives”, Production and Operations Management (POMS), vol. 16, No. 5, Sep.-Oct. 2007, pp. 646-655. |
| Edwards, John, “RFID Smart Shelves and Cabinets”, RFID Journal, Aug. 24, 2009, pp. 4. <http://www.rfidjournal.com/articles/view?5140/4>. |
| Electric Power Group v. Alstom, S.A., 830 F.3d 1350, 1353-54, 119 USPQ2d 1739, 1741-42 (Fed. Cir. 2016), pp. 12. |
| Epstein et al., “Development of a Scheduled Drug Diversion Surveillance System Based on an Analysis of Atypical Drug Transactions”, Anesthesia and Analgesia, Oct. 2007, vol. 105, No. 4, pp. 1053-1060. |
| Erdem et al., “Investigation of RFID Tag Readability for Pharmaceutical Products at Item Level”, Drug Development and Industrial Pharmacy, 2009, vol. 35, No. 11, pp. 1312-1324. |
| Fahrni, Jerry, “More RFID Refrigerator Stuff—Cubixx and myCubixx”, Sep. 3, 2012, pp. 4. <http://jerryfahrni.com/2012/09/more-rfid-refrigerator-stuff-cubixx-and-mycubixx/>. |
| “Faraday Cage”, Wikipedia, last edited Apr. 12, 2018, pp. 5. <https://en.wikipedia.org/wiki/Faraday_cage>. |
| Floerkemeier et al., “The Smart Box Concept for Ubiquitous Computing Environments”, The Smart Box Concept for Ubiquitous Computing Environments, 2004, pp. 4. |
| Garza, Anyssa, “The Future of Pharmacy Medication Kit Storage”, Pharmacy Times, https://www.pharmacytimes.com/contributor/anyssa-garza/2014/12/the-future-of-pharmacy-medication-kit-storage, Dec. 12, 2014, 2 Pages. |
| Glover et al., “RFID Essentials”, O'Reilly Media, 2006, pp. 2, 14, 24, 31, 33, 107-110, 113-114, 117, 137-143, 162-169, 178-179. |
| Gonzalez, Stephanie, “Health Maintenance System (HMS) Hardware Research, Design, and Collaboration,” NASA USRP—Internship Final Report, 2010, pp. 1-20. |
| Green, Kathryn, “Doing the Wave: Inventory Management with RFID”, Diagnostic & Interventional Services, UMass Memorial Medical Center, Worcester, MA, vol. 15, No. 9, Sep. 2007, pp. 7. <https://www.cathlabdigest.com/articles/Doing-Wave-Inventory-Management-RFID>. |
| Harrop et al., “RFID for Healthcare and Pharmaceuticals, 2008-2018,” Securing Pharma, May 2008, pp. 1-12. |
| Hawkins-Simons, “RFID Streamlines Refilling of Drug Trays”, Pharmacy Technology Report, https://www.pharmacypracticenews.com/Pharmacy-Technology-Report/Article/03-14/RFID-Streamlines-Refilling-of-Drug-Trays/26159, Mar. 21, 2014, 9 Pages. |
| Ho et al., “A Prototype on RFID and Sensor Networks for Elder Healthcare: Progress Report”, SIGCOMM '05 Workshops, Aug. 22-26, 2005, Philadelphia, PA, pp. 70-75. |
| Houliston, Bryan, “Integrating RFID Technology into a Drug Administration System,” Bulletin of Applied Computing and Information Technology, vol. 3, No. 1, May 2005, pp. 8. Retrieved Sep. 26, 2013 from <http://citrenz.ac.nz/bacit/0301/2005Houliston_RFID.htm>. |
| Howard, JD, “Implementation of RFID in the Pharmaceutical Industry”, Advisor: Dr. Jay Singh, California Polytechnic State University, San Luis Obispo, CA, Feb. 2009, pp. 11. |
| Humble, RN, Carol, “How RFID Freed Nurses From the Pain of Inventory Duties”, Cath Lab Digest, Dec. 2009, vol. 17, No. 12. <https://www.cathlabdigest.com/articles/How-RFID-Freed-Nurses-From-Pain-Inventory-Duties>. |
| “Intel & Siemens Launch RFID Blood Bank in Malaysia”, RFID Journal, Aug. 16, 2007, p. 1. <https://www.rfidjournal.com/articles/view?6801>. |
| Jones et al., “The Benefits, Challenges and Impacts of Radio Frequency Identification Technology (RFID) for Retailers in the UK”, Marketing Intelligence & Planning, Mar. 2005, vol. 23, No. 4, pp. 395-402. |
| Jorgensen et al., “Executable Use Cases: Requirements for a Pervasive Health Care System,” IEEE Software, Mar./Apr. 2004, pp. 34-41. |
| Juels, Ari, “RFID Security and Privacy: A Research Survey”, IEEE Journal on Selected Areas in Communications, vol. 24, No. 2, Feb. 2006, pp. 381-394. |
| Kinsella, Bret, “Premier, Inc. Identifies Kit Check as ‘Technology Breakthrough Product’—Awards exclusive agreement for pharmacy kit medication tracking solution”, Press Release, https://kitcheck.com/2014/04/premier-inc-identifies-kit-check-technology-breakthrough-product-awards-exclusive-agreement-pharmacy-kit-medication-tracking-solution/, Apr. 2, 2014, 5 Pages. |
| KitCheck, Bluesight for Controlled Substances Overview, as retrieved Aug. 30, 2018 from https://web.archive.org/web/20180830001131/https://kitcheck.com/learn-more/video/bluesight-for-controlled-substances-overview/ in 1 page. |
| KitCheck, Diversion Events, as retrieved Aug. 30, 2018 from https://web.archive.org/web/20180830001851/https://kitcheck.com/solutions/controlled-substances/diversion-events/ in 3 pages. |
| KitCheck, “PharMEDium Prefilled Syringes with Kit Check: ASHP Symposium Summary”, Jun. 2016, <https://kitcheck.com/wp-content/uploads/2016/06/pharmedium-prefilled-syringes-with-kit-check-download.pdf> in 9 pages. |
| KitCheck, Security, as retrieved Aug. 30, 2018 from https://web.archive.org/web/20180830000040/https://kitcheck.com/security/ in 1 page. |
| KitCheck, “St. Rita's Medical Center: 75% First-year ROI, Less Frustration”, Case Study, 2016, <https://kitcheck.com/learn-more/case-study/st-ritas-medical-center/> in 2 pages. |
| Lahtela et al., “RFID and NFC in Healthcare: Safety of Hospitals Medication Care”, 2008 Second International Conference on Pervasive Computing Technologies for Healthcare, Tampere, Finland, Jan. 30-Feb. 1, 2008, pp. 4. |
| Lai et al., “Enhancing Medication Safety and Reduce Adverse Drug Events on Inpatient Medication Administration using RFID,” WSEAS Transactions on Communications, Oct. 2008, vol. 7, No. 10, pp. 1045-1054. |
| Lampe et al., “The Smart Box Application Model,” Advances in Pervasive Computing, 2004, pp. 1-6. |
| Lewis, Mark O., “RFID-Enabled Capabilities and their Impact on Healthcare Process Performance”, 31st International Conference on Information Systems, St. Louis, 2010, pp. 1-20. |
| Liu et al., “Point-of-Care Support for Error-Free Medication Process” (Jun. 25, 2007), retrieved Aug. 21, 2017, 12 pages, available at http://ieeexplore.ieee.org/document/4438162/. |
| McCall et al., “RMAIS: RFID-based Medication Adherence Intelligence System” (Aug. 31, 2010), retrieved Aug. 21, 2017, 4 pages, available at http://ieeexplore.ieee.org/document/5627529/. |
| “McKesson's Announces New Touch-Screen Driven Medication Dispensing Solution”, Business Wire, Jun. 15, 2009, pp. 2, Available at: <http://www.businesswire.com/news/home/20090615005349/en/Mckesson-Announces-Touch-Screen-Driven-Medication-Dispensing-Solution#. VR7quPnF_10>. |
| “Medical Packaging Inc. Announces Clear Stem Flag Label System for Ampoules, Vials, and Syringes” Feb. 1, 2006 available at: <http://www.medpak.com/v1/news/20060201_CSFLAG.pdf>, in 1 page. |
| “Medication Tray Management” Pharmacy Purchasing & Products, Feb. 2018, pp. 18 & 20. |
| “Medication Tray Management” Pharmacy Purchasing & Products, Presentation, Nov. 2018, pp. 76 & 78. |
| “Medication Tray Management” Pharmacy Purchasing & Products, State of Pharmacy Automation, Aug. 2016, pp. 42 & 45. |
| “Medication Tray Management” Pharmacy Purchasing & Products, State of Pharmacy Automation, Aug. 2019, pp. 34-35. |
| Mehrjerdi, Yahia Zare, “RFID-Enabled Healthcare Systems: Risk-Benefit Analysis”, International Journal of Pharmaceutical and Healthcare Marketing, 2010, vol. 4, No. 3, pp. 282-300. |
| Meiller et al., “Adaptive Knowledge-Based System for Health Care Applications with RFID-Generated Information”, Decision Support Systems, vol. 51, 2011, pp. 198-207. |
| Mowry, Mike, “A Survey of RFID in the Medical Industry: With Emphasis on Applications to Surgery and Surgical Devices”, MAE188, Introduction to RFID, Dr. Rajit Gadh, UCLA, Jun. 9, 2008, pp. 22. |
| “New RFID Medical Cabinets Deployed at 50 Hospitals”, RFID Journal, Sep. 17, 2007, pp. 2. <https://www.rfidjournal.com/articles/view?6823>. |
| New et al., “Utilize ADC Transaction Data to Detect Diversion”, Oct. 2017, vol. 14, No. 10, pp. 3, as retrieved from https://www.pppmag.com/article/2119/. |
| O'Connor, Mary Catherine, “Drug Distributor Uses RFID to Vend Meds”, RFID Journal, May 23, 2006, pp. 2. <https://www.rfidjournal.com/articles/view?2363/2>. |
| O'Connor, Mary Catherine, “GlaxoSmithKline Tests RFID on HIV Drug”, RFID Journal, Mar. 24, 2006, pp. 2. <https://www.rfidjournal.com/articles/view?2219/>. |
| O'Connor, Mary Catherine, “Interrogators Start to Evolve”, RFID Journal, Jun. 1, 2006, pp. 3. <http://www.rfidjournal.com/purchase-access?type=Article&id=2398&r=%2Farticles%2Fview%3F2398>. |
| O'Connor, Mary Catherine, “Johnson & Johnson Finds Value in Multiple RFID Apps”, RFID Journal, Apr. 23, 2008, pp. 2. <http://www.rfidjournal.com/articles/pdf?4046>. |
| O'Connor, Mary Catherine, “Mckesson Starts RFID Pilot for Viagra”, RFID Journal, Feb. 17, 2005, pp. 2. <http://www.rfidjournal.com/articles/view?2157>. |
| O'Connor, Mary Catherine, “Pfizer Using RFID to Fight Fake Viagra”, RFID Journal, Jun. 6, 2006, pp. 2. <http://www.rfidjournal.com/articles/pdf?2075>. |
| O'Connor, Mary Catherine, “To Keep Drugs from Expiring, Hospital Tests Intelliguard System”, RFID Journal, Jan. 12, 2011, pp. 3. <http://www.rfidjournal.com/articles/view?8123>. |
| “ODIN Innovation Lab: EasyTunnel RFID”, as posted Jul. 13, 2009, archived via archive.org <https://web.archive.org/web/20200316173502/https://www.youtube.com/watch?v=0rQhT4slQnw>, 1 page. |
| “ODIN RFID HQ Tour 2009”, as posted Mar. 19, 2009, archived via archive.org <https://web.archive.org/web/20200316180429/https://www.youtube.com/watch?v=4Y4XIID0B_Y>, 1 page. |
| O'Driscoll et al., “RFID: An Ideal Technology for Ubiquitous Computing?” Dublin Institute of Technology School of Electronic and Communications Conference Papers, Jan. 1, 2008, pp. 1-17. |
| Pace et al., “Distributed Ambulatory Research in Therapeutics Network (DARTNet): Summary Report”,Effective Health Care Research Reports, No. 14, Agency for Healthcare Research and Quality, Jul. 2009, pp. 41. |
| Pappu, Ph.D et al., “RFID in Hospitals: Issues and Solutions” Consortium for the Accelerated Deployment of RFID in Distribution, Sep. 2004, pp. 1-12. |
| Parida et al., “Application of RFID Technology for In-House Drug Management System”, 15th International Conference on Network-Based Information Systems, 2012, pp. 577-581. |
| “RFID Medical Cabinets Evaluated in New Benchmark”, RFID Journal, Sep. 12, 2007, pp. 2. <http://www.rfidjournal.com/articles/view?6819>. |
| Roberti, Mark, “RFID Basics for Health Care”, RFID in Health Care, Produced by RFID Journal, Sep. 17, 2009, The Westin Waltham-Boston, Waltham, MA, pp. 33. |
| Saygin, C., “Adaptive Inventory Management Using RFID Data”, The International Journal of Advanced Manufacturing Technology, 2007, vol. 32, pp. 1045-1051. |
| Singh et al., “Versatility of Radio Frequency Identification (RFID) Tags in the Pharmaceutical Industry”, Instrumentation Science and Technology, vol. 36, pp. 656-663, 2008. |
| Summerfield, et al. “Evaluation of Medication Kit Processing Time Using Radio Frequency Identification (RFID) Technology”, Innovations in Pharmacy, 2015, vol. 6, No. 2, Article 199, 7 Pages. |
| Swedberg, Claire, “North Carolina Hospital Identifies Recalled Drugs Via RFID”, RFID Journal, http://www.rfidjournal.com/articles/view?10913, Aug. 14, 2013, 4 Pages. |
| Swedberg, Claire, “Tennessee Hospital Tracks High-Value Items”, RFID Journal, Aug. 5, 2009, pp. 2. <http://www.rfidjournal.com/articles/view?5106>. |
| Swedberg, Claire, “Zimmer Ohio to Use RFID to Manage Orthopedic Products”, RFID Journal, May 12, 2010, pp. 3. <https://www.rfidjournal.com/articles/pdf?7588>. |
| Tsai et al., “iMAT: Intelligent Medication Administration Tools” (Jul. 1, 2010), retrieved Aug. 21, 2017, 8 pages, available at http://ieeexplore.ieee.org/document/5556551/. |
| Tsai et al., “Smart Medication Dispenser: Design, Architecture and Implementation” (Sep. 27, 2010), retrieved Aug. 21, 2017, 12 pages, available at http://ieeexplore.ieee.org/document/5585838/. |
| Tzeng et al., “Evaluating the Business Value of RFID: Evidence from Five Case Studies,” International Journal of Production Economics, 2008, vol. 112, pp. 601-613. |
| “UPM Raflatac UHF EPC Gen2 RFID in ODIN Solution at Johnson-Johnson DePuyIn-Q-Tel”, as posted Jun. 10, 2009, archived via archive.org <https://web.archive.org/web/20200316174347/https://www.youtube.com/watch?v=JWGyR8Bgfl8>, 1 page. |
| “Vizient, Inc. Awards Kit Check Contract for Pharmacy Kit Medication Inventory Tracking and Replenishment”, Press Release, http://www.prweb.com/releases/2016/09/prweb13691526.htm, Sep. 19, 2016, 3 Pages. |
| Wang et al., “Applying RFID Technology to Develop a Distant Medical Care Service Platform,” International Journal of Electronic Business Management, 2010, vol. 8, No. 2, pp. 161-170. |
| Wang et al., “RFID Applications in Hospitals: A Case Study on a Demonstration RFID Project in a Taiwan Hospital”, Proceedings of the 39th Hawaii International Conference on System Sciences, 2006, pp. 1-10. |
| Wasserman, Elizabeth, “Purdue Pharma to Run Pedigree Pilot”, RFID Journal, May 31, 2005, pp. 2. <http://www.rfidjournal.com/articles/view?1626>. |
| Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Dec. 1, 2017, 45 pages. |
| Exhibit L; Fagron Academy, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos.|8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Dec. 1, 2017, 2 pages. |
| Defendant's Answer, Affirmative Defenses and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 2, 2018, 43 pages. |
| Plaintiff's Answer to Defendant's Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 19, 2018, 14 pages. |
| Plaintiff Kit Check, Inc.'s Motion to Strike Insufficient Defenses, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 19, 2018, 8 pages. |
| Defendant's First Amended Answer, Affirmative Defenses and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 9, 2018, 43 pages. |
| Defendant's Memorandum in Opposition to Plaintiff Kit Check, Inc.'s Motion to Strike Insufficient Defenses, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 9, 2018, 6 pages. |
| Plaintiff's Answer to Defendant's First Amended Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 21, 2018, 14 pages. |
| Plaintiff Kit Check, Inc.'s Reply in Support of its Motion to Strike Insufficient Defenses, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 21, 2018, 6 pages. |
| Defendant Health Care Logistics, Inc.'s Motion for Judgment on the Pleadings Pursuant to Fed. R. Civ. P. 12(C), Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), May 25, 2018, 31 pages. |
| Exhibit A; U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), May 25, 2018, 12 pages. |
| Opinion & Order, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099,|9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 13, 2018, 9 pages. |
| Defendant Health Care Logistics, Inc's Invalidity Contentions Pursuant to Local Patent Rule 103.4, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 25 pages. |
| Exhibit 1; Initial Invalidity Claim Chart for U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 51 pages. |
| Exhibit 2; Initial Invalidity Claim Chart for U.S. Pat. No. 9,058,413, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 94 pages. |
| Exhibit 3; Initial Invalidity Claim Chart for U.S. Pat. No. 9,058,412, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 83 pages. |
| Exhibit 4; Initial Invalidity Claim Chart for U.S. Pat. No. 9,734,294, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 58 pages. |
| Exhibit 5; Initial Invalidity Claim Chart for U.S. Pat. No. 9,805,169, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 251 pages. |
| Exhibit 6; Initial Invalidity Claim Chart for U.S. Pat. No. 9,037,479, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 43 pages. |
| Exhibit 7; Initial Invalidity Claim Chart for U.S. Pat. No. 9,367,665, Kit Check, Inc. v. Health Care Logistics, Inc., Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 109 pages. |
| Plaintiff Kit Check, Inc.'s Memorandum in Opposition to Defendant Health Care Logistics, Inc.'s Motion for Judgment on the Pleadings, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 35 pages. |
| Exhibit 1; Non-Final Office Action for U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 11 pages. |
| Exhibit 2; Notice of Allowance for U.S. Pat. No. 8,990,099, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 15 pages. |
| Exhibit 3; Non-Final Office Action for U.S. Pat. No. 9,367,665, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 12 pages. |
| Exhibit 4; Response to Non-Final Office Action for U.S. Pat. No. 9,367,665, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 29, 2018, 18 pages. |
| Defendant Health Care Logistics, Inc.'s Reply in Support of Motion for Judgment on the Pleadings Pursuant to Fed. R. Civ. P. 12(C), Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 20, 2018, 22 pages. |
| Exhibit A, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, |9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 20, 2018, 43 pages. |
| Exhibit B; Plaintiff Kit Check, Inc.'s Disclosure of Asserted Claims and Infringement Contentions under Local Patent Rule 103.2, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 20, 2018, 11 pages. |
| Plaintiff Kit Check, Inc.'s Motion to Strike Portions of Defendants' Reply or, in the Alternative, Motion for Leave to File a Sur-Reply, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 10, 2018, 6 pages. |
| Exhibit A; Plaintiff Kit Check, Inc.'s Sur-Reply in Opposition to Defendant's Motion for Judgment on the Pleadings, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 10, 2018, 5 pages. |
| Defendant Health Care Logistics, Inc.'s Memorandum in Opposition to Plaintiff Kit Check, Inc.'s Motion to Strike Portions of Defendant's Reply or, in the Alternative, Motion for Leave to File a|Sur-Reply, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 31, 2018, 6 pages. |
| Plaintiff Kit Check, Inc.'s Reply in Support of its Motion to Strike Portions of Defendant's Reply or, in the Alternative, Motion for Leave to File a Sur-Reply, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Sep. 14, 2018, 7 pages. |
| Joint Claim Construction and Prehearing Statement, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Sep. 20, 2018, 21 pages. |
| Plaintiff Kit Check, Inc.'s Opening Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 50 pages. |
| Exhibit 1; Disputed Claim Terms Chart, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 4 pages. |
| Declaration of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 24 pages. |
| Defendant Health Care Logistics, Inc.'s Opening Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Nov. 16, 2018, 32 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,367,665, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 256 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 9 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 32pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. PGR2019-00022, Nov. 30, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 8,990,099, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 42 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 8,990,099, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 557 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 9 pages. |
| Exhibit 1010; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 32 pages. |
| Exhibit 1011; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, Nov. 30, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,058,412, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 75 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,058,412, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 75 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 9 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 32 pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, Nov. 30, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,058,413, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 73 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,058,413, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 549 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 9 pages. |
| Exhibit 1009; Children's Hospital Boston Joins Others Using RFID to Track Implantables, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 3 pages. |
| Exhibit 1012; The “Orange Book”, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 1103 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 32 pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, Dec. 1, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,805,169, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 76 pages. |
| Exhibit 1002; File History of U.S. Patent No. 9,805, 169, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 286 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 9 pages. |
| Exhibit 1009; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 32 pages. |
| Exhibit 1010; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, Dec. 1, 2018, 50 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,367,665, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 69 pages. |
| Exhibit 1002; File History of U.S. Pat. No. 9,367,665, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 256 pages. |
| Exhibit 1003; Expert Declaration, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 9 pages. |
| Exhibit 1013; Claim Construction Brief (Defendant), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 32 pages. |
| Exhibit 1014; Claim Construction Brief (Plaintiff), Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, Dec. 3, 2018, 50 pages. |
| Plaintiff Kit Check, Inc.'s Notice of Filing Deposition Transcript of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 3 pages. |
| Exhibit A; Deposition of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 86 pages. |
| Plaintiff Kit Check, Inc.'s Responsive Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 23 pages. |
| Exhibit A, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479,|9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 43 pages. |
| Exhibit B; Deposition of Jeffrey Fischer, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 22 pages. |
| Defendant Health Care Logistics, Inc.'s Response to Plaintiff Kit Check, Inc.'s Opening Claim Construction Brief, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 3, 2019, 22 pages. |
| Plaintiff Kit Check, Inc.'s Memorandum in Opposition to Defendant Health Care Logistics, Inc.'s Motion for Stay, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 11, 2019, 21 pages. |
| Exhibit 1; Defendant Health Care Logistics, Inc.'s Invalidity Contentions Pursuant to Local Patent Rule 103.4, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 11, 2019, 26 pages. |
| Defendant Health Care Logistics, Inc.'s Reply in Support of Motion for Stay, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 25, 2019, 10 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, U.S. Pat. No. 8,990,099, Mar. 8, 2019, 26 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, U.S. Pat. No. 9,058,412 B2, Mar. 8, 2019, 28 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, U.S. Pat. No. 9,058,413 B2, Mar. 13, 2019, 28 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00388, U.S. Pat. No. 9,805,169 B2, Mar. 13, 2019, 25 pages. |
| Patent Owner's Preliminary Response, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, U.S. Pat. No. 9,367,668 B2, Mar. 13, 2019, 28 pages. |
| Opinion & Order, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Mar. 14, 2019, 17 pages. |
| Joint Stipulation of Partial Dismissal Without Prejudice, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Apr. 16, 2019, 2 pages. |
| Transcript of Markman Hearing Proceedings, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), May 6, 2019, 74 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. § 314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, U.S. Pat. No. 9,058,412 B2, Jun. 3, 2019, 28 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. § 314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00385, U.S. Pat. No. 9,805,169 B2, Jun. 3, 2019, 20 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. § 314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00376, U.S. Pat. No. 8,990,099 B2, Jun. 4, 2019, 18 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. § 314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00387, U.S. Pat. No. 9,058,413 B2, Jun. 7, 2019, 26 pages. |
| Decision Denying Institution of Inter Partes Review 35 U.S.C. § 314, Health Care Logistics, Inc. v. Kit Check, Inc., Case No. IPR2019-00394, U.S. Pat. No. 9,367,665 B2, Jun. 11, 2019, 25 pages. |
| Stipulation and [Proposed] Order Granting Leave to Amend Plaintiff's Infringement Contentions and Defendant's Invalidity Contentions, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 3, 2019, 3 pages. |
| Defendant Health Care Logistics, Inc.'s Motion for Leave to File Second Amended Answer, Affirmative Defenses, and Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 17, 2019, 5 pages. |
| Exhibit A; Defendant's Second Amended Answer, Affirmative Defenses, and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jul. 17, 2019, 49 pages. |
| Request for Ex Parte Reexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 8,990,099 B2, U.S. Appl. No. 13/554,342, filed Jul. 25, 2019 in 80 pages. |
| Request for Ex Parte Reexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,058,412 B2, U.S. Appl. No. 14/603,730, filed Jul. 26, 2019 in 118 pages. |
| Request for Ex Parte Reexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,058,413 B2, U.S. Appl. No. 14/603,828, filed Jul. 25, 2019 in 151 pages. |
| Request for Ex Parte Reexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,805,169 B2, U.S. Appl. No. 14/701,958, filed Jul. 26, 2019 in 220 pages. |
| Request for Ex Parte Reexamination Under 35 U.S.C. 302-307 and 37 C.F.R. 1.510, U.S. Pat. No. 9,367,665 B2, U.S. Appl. No. 14/818,113, filed Jul. 26, 2019 in 164 pages. |
| Opinion & Order, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. Nos. 8,990,099, 9,037,479, 9,058,412, 9,058,413, 9,367,665, 9,734,294, and 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Aug. 30, 2019, 26 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230377728 A1 | Nov 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62062845 | Oct 2014 | US | |
| 62020576 | Jul 2014 | US | |
| 62000570 | May 2014 | US | |
| 61913337 | Dec 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17177914 | Feb 2021 | US |
| Child | 18154646 | US | |
| Parent | 16822459 | Mar 2020 | US |
| Child | 17177914 | US | |
| Parent | 16103001 | Aug 2018 | US |
| Child | 16822459 | US | |
| Parent | 15426302 | Feb 2017 | US |
| Child | 16103001 | US | |
| Parent | 14876533 | Oct 2015 | US |
| Child | 15426302 | US | |
| Parent | 14563732 | Dec 2014 | US |
| Child | 14876533 | US |
