US 10,600,513 B2Grant
Medication tracking
Issue Date:2020-03-24
•20 Claims
•15 Drawing Sheets
Abstract
A system and method is described for printing a label with an RFID tag. The system includes an RFID reader that queries a first RFID tag coupled to a first medicinal container that includes a medication. In response, the system receives a first unique identifier and uses the first unique identifier to determine a status of the medication, associate the first medicinal container with a medical provider and print a second label that includes a second RFID tag for a second medicinal container.
Metadata
Assignee
- Kit Check, Inc.
Inventors
- Jennifer Ashley Gitchell
- Timothy James Leo Kress-Spatz
- Kevin William MacDonald
- Nicholas Bastien Petersen
- Julie Christina Meloni
- Christian Lee Doyle
- Michael David Waud
- David Mario Pedra
- Nicholas Ward Stocchero
- Michael Christopher Wimpee
- Steven Shyu
- Mahesh Murali
Application Information
Application Number:US 16/103,001
Filing Date:2018-08-14
Priority Date:2013-12-08
Art Unit:2876
Classifications
IPC:
G06F17/00G16H40/20G06Q10/08A61J1/18G06Q50/22A61J1/00G06K7/10G06F19/00A61G12/00
Field of Search:
G06Q 30/02G07F 1/1008G06K 17/00
Patent Drawings (15 sheets)
Description
[0001] The present application 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. Patent Application No. 61/913,337, filed Dec. 8, 2013, entitled ENHANCED MEDICATION MANAGEMENT IN THE OPERATING ROOM ENVIRONMENT, U.S. Patent Application No. 62/000,570, filed May 20, 2014, entitled ANESTHESIA LABEL CREATION AND MIXTURE PREFERENCES SOLUTION, U.S. Patent Application No. 62/020,576, filed Jul. 3, 2014, entitled MULTI-DOSE INVENTORY SOLUTION, and U.S. Patent Application 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.
Background
[0002] 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.
Brief Description of the Drawings
[0003] FIG. 1A is a block diagram illustrating an environment for tracking medications at a medical care facility.
[0004] FIGS. 1B and 1C are diagrams illustrating an embodiment of a label reading station coupled to a pharmaceutical item storage unit.
[0005] FIGS. 2A and 2B are diagrams illustrating embodiments of a drug label.
[0006] FIGS. 3A and 3B depict embodiments of a user interface for mixing and/or diluting one or more medications.
[0007] FIG. 4 depicts an embodiment of a user interface for monitoring medications that are in the care of a particular medical care provider.
[0008] FIGS. 5A, 5B, and 5C depict embodiments of the user interface for monitoring the administration of medications to a particular patient.
[0009] FIG. 6 depicts an embodiment of a user interface for reconciling/wasting medications.
[0010] FIG. 7 is a flow diagram illustrating an embodiment for generating a label during a transfer of a drug and generating a restocking notification.
[0011] FIG. 8 is a flow diagram illustrating an embodiment for generating a label as part of a transfer of a drug.
[0012] FIG. 9 is a flow diagram illustrating an embodiment for generating a restocking notification.
Detailed Description
[0013] 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
[0014] 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.
[0015] 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.
[0016] 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.
[0017] 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.
[0018] 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.
[0019] 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.
[0020] 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
[0021] 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.
[0022] 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.
[0023] 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.
[0024] 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.
[0025] 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.
[0026] 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.
[0027] 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.
[0028] 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
[0029] 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).
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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.
[0034] 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
[0035] 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.
[0036] 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.
[0037] 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
[0038] 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
[0039] 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
[0040] FIG. 1A is a block diagram illustrating an environment 100 for tracking medications at a medical care facility. In the illustrated embodiment, the environment 100 includes a label reading station 102 communicatively coupled with an information processing system 108 and an electronic medical records database 110. The label reading station 102 can be communicatively coupled directly with the information processing system 108 and/or the electronic medical records database 110, such as via a wired or wireless connection, or can be communicatively coupled via a network 112. The network 112 can be a local area network or a wide area network, such as the internet, etc.
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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 FIGS. 2A and 2B . In certain embodiments, the label printer 104 can be configured to print the RFID tag or print onto a label that already includes an RFID tag. Similarly, in some embodiments, the label printer 104 can be configured to print a bar code or QR code and/or print onto a label that already includes a bar code or QR code.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] FIGS. 1B and 1C are diagrams illustrating an embodiment of a label reading station 102 coupled to a pharmaceutical item storage unit 152, such as a crash cart. In the illustrated embodiment, the pharmaceutical item storage unit 152 includes drawers 154, shelves 156, and a tabletop 158. The drawers 154 can be locked drawers that require a key code to open. Within the drawers can be stored various medications, including, but not limited to drugs, diluents (for example, sterile water, sodium chloride, etc.), other supplies, etc. The shelves 156 can include unused medicinal containers and other medical supplies, such as tubes, baggies, gauze, etc., as desired. The tabletop 158 can be used for preparing the child medications and/or child medicinal containers. For example, the medications found in the drawers 154 can be combined or mixed together as part of the preparation for a new medication.
[0058] 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 FIG. 1A .
[0059] 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.
[0060] The label reader 106 (not shown in FIGS. 1B and 1C ) can be located behind the display 160 or in some other location within the label reading station 102, such that when a label touches or is placed in close proximity (for example, twelve inches or less, or some other desired distance) to the label reading station 102, the label reader 106 can read the contents of the label. Furthermore, in some embodiments, the label reader 106 can be configured to emit an electromagnetic field large enough to capture data from all RFID tags stored in the pharmaceutical item storage unit 152. In this way, the label reader 106 can determine when a medicinal container associated with an RFID tag is removed from the pharmaceutical item storage unit without having to touch the RFID tag, or place the RFID tag in close proximity, to the label reading station 102. Although described with respect to RFID technology, it will be understood that the labels can be implemented using any number or combination of technologies including, but not limited to bar codes, QR codes, etc.
[0061] As described previously with respect to FIG. 1A , the label reading station 102 can be used in conjunction with the information processing system 108 to verify the status of medications in the pharmaceutical item storage unit 152. For example, labels associated with or coupled to the medicinal containers in the pharmaceutical item storage unit 152 can be queried and read by the label reading station 102. Once read, the label reading station 102 can look up information regarding the medications, such as the expiration date, recall information, warnings, etc. The label reading station 102 can also be used to print labels for medicinal containers. The new labels may replace old labels on a medicinal container and/or can be placed on an unused or child medicinal container. The labels printed by the label reading station 102 will be described in greater detail below with reference to FIGS. 2A and 2B .
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] In the illustrated embodiments of FIGS. 1B and 1C , the label reading station 102 is coupled to the pharmaceutical item storage unit 152. However, it will be understood that the label reading station 102 can be located in any one or more locations within a medical care facility. For example, the label reading station 102 can be located in an operating room, in a patient room, or in a pharmacy. Furthermore, the label reading station 102 can be used in conjunction with the information processing system 108 to track the administration of medications to a patient, determine allergic reactions of the medication with a particular patient, update an electronic medical record of a patient, calculate waste based on an amount of medication given to a patient, and/or determine whether a particular medication has been used previously, such as on a different patient, or is expired or recalled.
[0068] 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.
[0069] 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.
[0070] 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
[0071] FIGS. 2A and 2B are diagrams illustrating embodiments of a label 202 that can be printed by the label printer 104. In the illustrated embodiments of FIGS. 2A and 2B , the label 202 includes an applicator portion 204 (204A and/or 204B), an RFID portion 206, and abbreviated data portions 208, 210. The applicator portion can stand lengthwise across a longitudinal portion of the RFID portion 206 (for example as is shown with portion 204A in FIG. 2A or applicator portion 204 in FIG. 2B ), or can extend height-wise along a latitudinal portion of the RFID portion 206, as shown with applicator portion 204B.
[0072] Similarly, the abbreviated data portions 208, 210 can extend height-wise along a latitudinal portion of the RFID portion 206, as is shown in FIG. 2A , or lengthwise along a longitudinal portion of the RFID portion 206, as is shown in FIG. 2B . In addition, the abbreviated data portions 208, 210 can share or be coupled with each other along a longitudinal portion, as is shown in FIG. 2A , or along a latitudinal portion, as is shown in FIG. 2B .
[0073] In the illustrated embodiment of FIG. 2A , text printed on the RFID portion 206 is oriented at a 90° angled difference from the text printed onto the abbreviated data portions 208, 210. In the illustrated embodiment of FIG. 2B , the text printed on the RFID portion 206 can have the same orientation as text printed onto the abbreviated data portions 208, 210.
[0074] Although FIGS. 2A and 2B illustrate specific embodiments of the label 202, it will be understood that the various portions can be coupled together in a variety of orientations as desired. Furthermore, text printed on any one or more of the portions can be printed in the same orientation or in different orientations, as desired. In addition, although in the illustrated embodiments, the applicator portion 204 extends across an entire length or height of the label, it will be understood that it can extend along a more or less of the RFID portion 206 as desired. For example, the applicator portion 204A can extend along less than the entire length of the RFID portion or more than the length of the RFID portion 206. Similarly the applicator portion 204B can extend along the less than the entire height of the RFID portion 206 or more than the entire height of the RFID portion 206. In some embodiments, the abbreviated data portions 208, 210 can be detachably coupled to the RFID portion 206 and/or to each other. In this way, the abbreviated data portions 208,210 can be removed from the rest of the label 202 and applied to different portions of a medicinal container in order to provide a user the ability to read information regarding the contents of the medicinal container from a variety of positions, angles, or orientations.
[0075] 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.
[0076] 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.
[0077] 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.
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] The abbreviated data portions 208, 210 in the illustrated embodiment of FIG. 2A are opaque and include some of the data printed on the RFID portion 206. For example, the abbreviated data portions 208, 210 of FIG. 2A include the drug name and the concentration, as well as a color code identifier indicating the class of the drug. However, it will be understood that the abbreviated data portions 208, 210 can be transparent and/or translucent and need not have an adhesive portion. Furthermore, as mentioned previously the abbreviated data portions 208, 210 can be detachably coupled to the RFID portion 206, such as using a perforated line, a separate sheet, etc. such that the abbreviated data portions 208, 210 can be removed separately from the RFID portion 206 and affixed to different portions of the medicinal container, as desired.
[0083] 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 FIG. 2A or 2B , or any other orientation as desired.
[0084] With respect to FIG. 2B , specific lengths and heights of the label 202, the applicator portion 204, the RFID portion 206, and the abbreviated data portions 208, 210 are provided. However, it will be understood that the label 202, the applicator portion 204, the RFID portion 206, and the abbreviated data portions 208, 210 can be configured using any dimension as desired. Accordingly, the dimensions illustrated in FIG. 2B should not be construed as limiting.
Mixing and Dilution
[0085] FIGS. 3A and 3B depict embodiments of a user interface 300 for mixing and/or diluting a medication. In some embodiments, the user interface 300 can be presented on the display 160 of the label reading station 102 after a label 202 has been read by the label reading station 102.
[0086] FIG. 3A depicts an embodiment in which one label 202 has been read and FIG. 3B depicts an embodiment of the user interface 300 in which two labels 202 have been read by a label reading station 102. It will be understood that additional labels 202 can be read as desired and/or medication information can be entered manually.
[0087] In the illustrated embodiments of FIGS. 3A and 3B , the user interface includes user data 302, an inventory link 304, a medicinal container preparation link 306, and a patient data link 308, first medication information 310, second medication information 330 (FIG. 3B ), a total volume field 320, a mixture object 322 and other interface objects, including a preview object 324, a print object 326, and a clear all object 328.
[0088] 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 FIGS. 4 and 6 . The medicinal container preparation link 306 can be used to navigate to portions of the user interface 300 for preparing labels 202 for medicinal containers, such as the embodiments illustrated in FIGS. 3A and 3B . The labels 202 can be prepared for medicinal containers that already include a label 202 and/or can be prepared for medicinal containers that do not include a label 202. The patient data link 308 can be used to navigate to portions of the user interface in which data regarding individual patients associated with the user are displayed, such as the embodiments of the user interface 300 illustrated in FIGS. 5A, 5B, and 5C .
[0089] 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.
[0090] 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.
[0091] 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.
[0092] 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 FIG. 3A . The suggested medications can be based on medical facility rules (for example, medications that the medical care facility has indicated as being permissibly combined with a particular medication), best practices, user preferences (for example, medications that the user has indicated that they prefer to use with a particular medication), and/or user history (for example, previous medications that the user has used in the past).
[0093] 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.
[0094] With continued reference to FIGS. 3A and 3B , once the relevant information has been captured regarding the generation of a new label, the label reading station 102 can communicate the information to the information processing system 108. In response, the information processing system 108 can generate a new database entry in the data storage device 114 for the child medication or child medicinal container. The new database entry can include information regarding the drug name, class identification, concentration, origin information (including information regarding the parent medications or parent medicinal containers), expiration, volume information, lot number information regarding the parent medications or parent medicinal containers, and other information to track the child medication or child medicinal container.
[0095] 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.
[0096] 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.
[0097] 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.
[0098] 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 FIG. 3B ), and a first medication volume field 317 (shown in FIG. 3B ).
[0099] The second medication information 330 can include similar information. In the illustrated embodiment of FIG. 3B , the second medication information 330 includes a medication name 332, concentration data 334, origin data 336 indicating the origin of the second medication, and a second medication volume field 338. It will be understood that the medication information for each medication can include less or more information as desired.
[0100] 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.
[0101] 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
[0102] FIG. 4 depicts an embodiment of the user interface 300 for monitoring medications that are in the custody or care of a particular medical care provider. In the illustrated embodiment of FIG. 4 , the particular medical care provider is “Michael Jamison,” as indicated by the user data 302. In the illustrated embodiment of FIG. 4 , the user interface provides data regarding the medications that are in the care of the medical care provider, the amount of each medication, and indications regarding a quantity of each medication that needs to be returned to the pharmacy or accounted for.
[0103] In the illustrated embodiment of FIG. 4 , the user interface provides the medication name and concentration 402, a medication volume 404, and a quantity of medicinal containers of the particular medication 406. As the medical care provider uses, wastes, or returns the medicinal containers, the information processing system 108 can update the inventory data of the user. In this way, the information processing system 108 can maintain an accurate record of the medications in the custody of the medical care providers in a particular medical care facility.
Medication Administration
[0104] FIGS. 5A, 5B, and 5C depict embodiments of the user interface 300 for monitoring the administration of medications for a particular patient. In some embodiments, the user interface 300 of FIGS. 5A, 5B, and 5C can be presented on the display 160 of the label reading station 102 once a user logs into a label reading station 102 located in a patient administration environment, such as an operating room or patient room, and indicates that medications are to be provided to a particular patient.
[0105] 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.
[0106] 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.
[0107] 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.
[0108] 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.
[0109] In the illustrated embodiments of FIGS. 5A, 5B, and 5C , the user interface 300 includes a current patient data 502, completed procedure patient data 504, a medication delivery time icon 506, a medication detailed information icon 508, add/edit medication icons 510, 512, and information regarding medications used during the procedure, including drug classification 514, medication name/concentration data 516, time of administration 518.
[0110] 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.
[0111] 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 FIG. 5A , the medication delivery time icon 506 is selected and in the illustrated embodiment of FIG. 5B , the medication detailed information icon 508 is selected.
[0112] 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.
[0113] The medication name/concentration data 516 can be similar to the drug name/concentration data 402 described previously with respect to FIG. 4 . The time of administration 518 can indicate the time at which a particular medication is administered to the patient. The drug classification 514 can indicate the classification of the medication or drug that is administered to the patient, as described previously.
[0114] The user interface can include additional information and objects as desired. For example, in the illustrated embodiment of FIGS. 5A, 5B, and 5C , the user interface 300 includes information regarding the type of procedure being performed on the patient, the start time of the procedure, and a finish procedure object to indicate when the procedure for the patient is completed and/or when the medical care provider leaves the procedure.
[0115] As mentioned previously, FIG. 5B includes an illustrated embodiment of the user interface 300 when the medication detailed information icon 508 is selected. Accordingly, in the illustrated embodiment of FIG. 5B , the user interface 300 further includes initial amount data 520, administered amount data 522, wasted amount data 524, remainder amount data 526, and to waste amount data 528 for each medication.
[0116] 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, to the 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.
[0117] Furthermore, in the illustrated embodiment of FIG. 5B , a vial containing 200 micrograms of Fentanyl has been associated with the patient, Abigail Jones. However, the illustrated embodiment indicates that 250 micrograms of Fentanyl were administered. In such an instance when the amount administered exceeds the initial amount of the medicinal container, a warning icon 530 can be provided. In addition, a warning message or popup window can be displayed requesting additional information regarding the discrepancy between the initial amount of the medication and the amount administered. Using the popup window or additional data field, a user can provide information indicating an additional initial amount 520. For example, it may be that the medical care provider used a second medicinal container and administered 50 micrograms of Fentanyl from the second medicinal container without the label reading station 102 scanning an RFID tag associated with the second medicinal container. Accordingly, the medical care provider can update the initial amount of Fentanyl from 200 micrograms to 400 micrograms by scanning the RFID tag associated with the second medicinal container (or manually entering the information). Upon updating the information, the information processing system 108 can calculate that the amount of Fentanyl to be wasted is 150 micrograms and the user interface 300 can be updated accordingly, as illustrated in FIG. 5C .
Medication Reconciliation
[0118] FIG. 6 depicts an embodiment of a user interface 300 for reconciling/wasting medications. In the illustrated embodiment of FIG. 6 , the user interface 300 includes medication summary data 602, to waste medication quantity 604, and to return medication quantity 606. The medication summary data 602 can include a list of medications that are in the possession of the medical care provider or user.
[0119] To the waste medication quantity 604 can include the number of medicinal containers that include medications that are to be wasted. In the illustrated embodiment of FIG. 6 , there are four medicinal containers that include medications that are to be wasted.
[0120] 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.
[0121] 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.
[0122] 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.
[0123] 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.
[0124] 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.
[0125] 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
[0126] FIG. 7 is a flow diagram illustrating an embodiment of a routine 700 for generating a label during a transfer of a medication, and generating a restocking notification. In some embodiments, routine 700 can be used when a medical care provider desires to transfer one or more medications from one or more parent medicinal containers to a child medicinal container, or create a child medication from one or more parent medications.
[0127] 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.
[0128] 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.
[0129] 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.
[0130] 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.
[0131] 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.
[0132] 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.
[0133] 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.
[0134] 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.
[0135] 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.
[0136] 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.
[0137] 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.
[0138] 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.
[0139] 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.
[0140] 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.
[0141] 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.
[0142] In some embodiments, the label reading station 102 can print the medication and other data onto the labels described previously with respect to FIGS. 2A and 2B . Furthermore, in some embodiments the second RFID tag can include a second unique identifier that uniquely identifies the RFID tag from all other RFID tags included in the information processing system 108.
[0143] 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.
[0144] 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.
[0145] 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.
[0146] 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.
[0147] 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.
[0148] 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.
[0149] 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.
[0150] 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).
[0151] 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.
[0152] 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.
[0153] 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 FIGS. 4, 5A, 5B, and 5C, and 6 . For example, as part of the administration process, the label reading station 102 can receive a unique identifier associated with a medication, verify the status of the medication, associate the medication with a particular patient, determine whether the particular patient is allergic to the medication or will have any adverse effects when combined with other medications that the particular patient has received, identify discrepancies between an initial amount of the medication in a medicinal container and the amount of the medication administered to the patient, calculate an amount of the medication to waste, and/or track the waste of the medication that was not administered to the patient.
[0154] FIG. 8 is a flow diagram illustrating an embodiment for generating a label as part of a transfer of a drug. In some embodiments, routine 800 can be used when a medical care provider desires to transfer one or more medications from one or more parent medicinal containers to a child medicinal container or desires to create a child medication from one or more parent medications.
[0155] 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.
[0156] 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.
[0157] 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.
[0158] 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 FIG. 7 .
[0159] 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.
[0160] 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.
[0161] 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 FIGS. 2A and 2B .
[0162] 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.
[0163] 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.
[0164] 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.
[0165] 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.
[0166] 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 FIGS. 4, 5A, 5B , and 5C, and 6.
[0167] FIG. 9 is a flow diagram illustrating an embodiment of a routine 900 for generating a restocking notification for a pharmaceutical item storage unit. In some embodiments, routine 900 can be used when a medical care provider removes a medication from the pharmaceutical item storage unit.
[0168] 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.
[0169] 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.
[0170] 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.
[0171] 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 FIG. 7 .
[0172] 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.
[0173] 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 FIG. 7 .
[0174] 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 FIGS. 4, 5A, 5B, and 5C, and 6 .
Additional Embodiments
[0175] 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.
Terminology
[0176] 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.
[0177] 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.
[0178] 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.
[0179] 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.
[0180] 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.
[0181] 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.
[0182] 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.
[0183] 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.
[0184] 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.
[0185] 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.
Claims
What is claimed is:
1. A system comprising:
an RFID reader configured to query an RFID tag of a label coupled to a medicinal container associated with a drug and receive a unique identifier from the RFID tag, wherein the unique identifier uniquely identifies the medicinal container from other medicinal containers, wherein the label comprises a transparent portion including an adhesive, an RFID portion that includes the RFID tag, a first opaque portion comprising an adhesive and a second opaque portion comprising an adhesive, wherein a length of the transparent portion extends along a length of the RFID portion wherein the first opaque portion and the second opaque portion are detachably coupled to the RFID portion; and
a computing device coupled to the RFID reader and configured to:
receive the unique identifier,
query a remotely located database for drug data of the drug using the unique identifier,
receive drug usage information based at least in part on user input,
determine a drug expiration date of the drug, wherein to determine the drug expiration date, the computing device is configured to:
determine a first expiration date based at least in part on the drug data, wherein the first expiration date corresponds to at least one of an expiration based at least in part on a sealed seal, an expiration based at least in part on refrigeration, or an expiration based at least in part on a vial expiration,
determine a second expiration date based at least in part on the drug usage information, wherein the second expiration date corresponds to at least one of an expiration based at least in part on a broken seal, an expiration based at least in part on non-refrigeration, or an expiration based at least in part on a syringe expiration, and
identify the drug expiration date as the earlier of the first expiration date and the second expiration date, and
update the drug data of the remotely located database to associate the drug expiration date with the unique identifier and mark the drug as at least one of an opened drug, an un-refrigerated drug, or a syringe drug.
2. A system comprising:
an RFID reader configured to query an RFID tag of a label coupled to a medicinal container and receive a unique identifier from the RFID tag; and
a computing device coupled to the RFID reader and configured to:
receive the unique identifier,
query, based at least in part on receipt of the unique identifier, a remotely located database for drug data of a drug associated with the medicinal container,
receive drug usage information,
determine a drug expiration date of the drug, wherein to determine the drug expiration date, the computing device is configured to:
determine a first expiration date based at least in part on the drug data,
determine a second expiration date based at least in part on the drug usage information, and
identify the drug expiration date as the earlier of the first expiration date and the second expiration date, and
update the drug data of the remotely located database to associate the drug expiration date with the unique identifier.
3. The system of claim 2, wherein the drug data indicates that the drug is at least one of a multi-dose drug, a drug for refrigeration, or a liquid drug, wherein the medicinal container for a multi-dose drug comprises a seal, wherein the medicinal container for a liquid drug comprises at least one of a vial or a syringe.
4. The system of claim 2, wherein the drug is a multi-dose drug, the medicinal container comprises a seal, the first expiration date corresponds to an expiration based at least in part on a sealed seal, and the second expiration date corresponds to an expiration based at least in part on a broken seal.
5. The system of claim 4, wherein the drug usage information comprises at least one of an indication that the seal is broken, an indication that the seal is punctured, an indication of a date that the seal was broken, or an indication of a date that the seal was punctured.
6. The system of claim 2, wherein the drug is a drug for refrigeration, the first expiration date corresponds to an expiration based at least in part on refrigeration, and the second expiration date corresponds to an expiration that is different from the first expiration date and is based at least in part on non-refrigeration.
7. The system of claim 6, wherein the drug usage information comprises at least one of an indication that the drug for refrigeration is un-refrigerated, an indication of a duration of time that the drug for refrigeration was un-refrigerated, or an indication of a date that the drug for refrigeration was un-refrigerated.
8. The system of claim 2, wherein the drug is a fluid, the medicinal container comprises at least one of a vial or a syringe, the first expiration date corresponds to an expiration based at least in part on a vial expiration, and the second expiration date corresponds to an expiration based at least in part on a syringe expiration.
9. The system of claim 8, wherein the drug usage information comprises at least one of an indication that the drug is contained in the syringe or an indication of a date that the drug was transferred to the syringe.
10. The system of claim 2, wherein the drug data comprises a drug name, concentration, and total amount of the drug in the medicinal container.
11. The system of claim 2, wherein the label comprises a transparent portion including an adhesive, an RFID portion that includes the RFID tag and does not include an adhesive, a first opaque portion comprising an adhesive and a second opaque portion comprising an adhesive, wherein a length of the transparent portion extends along a length of the RFID portion and at least a portion of the drug data is printed onto the RFID portion, and a name of the drug is printed on the first opaque portion and the second opaque portion, and wherein the first opaque portion and the second opaque portion are detachably coupled to the RFID portion.
12. The system of claim 2, wherein the computing device is further configured to generate a notification that the drug is expired based at least in part on the drug expiration date.
13. A method comprising:
querying an RFID tag of a label coupled to a medicinal container;
receiving a unique identifier from the RFID tag, wherein the unique identifier uniquely identifies the medicinal container from other medicinal containers in a pharmaceutical item storage unit;
querying, based at least in part on receiving the unique identifier, a remotely located database for medication data of a medication associated with the medicinal container;
receiving medication usage information;
determining a medication expiration date of the medication, wherein said determining the medication expiration date comprises:
determining a first expiration date based at least in part on the medication data,
determining a second expiration date based at least in part on the medication usage information, and
identifying the medication expiration date, wherein the medication expiration date is the earlier of the first expiration date and the second expiration date; and
updating the medication data of the remotely located database to associate the medication expiration date with the unique identifier.
14. The method of claim 13, wherein the medication data indicates that the medication is at least one of a multi-dose drug, a medication for refrigeration, or a liquid medication, wherein the medicinal container for a multi-dose drug comprises a seal, wherein the medicinal container for a liquid medication comprises at least one of a vial or a syringe.
15. The method of claim 13, wherein the medication is a multi-dose drug, the medicinal container comprises a seal, the first expiration date corresponds to an expiration based at least in part on a sealed seal, and the second expiration date corresponds to an expiration based at least in part on a broken seal.
16. The method of claim 15, wherein the medication usage information comprises at least one of an indication that the seal is broken, an indication that the seal is punctured, an indication of a date that the seal was broken, or an indication of a date that the seal was punctured.
17. The method of claim 13, wherein the medication is a medication for refrigeration, and the first expiration date corresponds to an expiration based on refrigeration, and the second expiration date corresponds to an expiration date that is different from the first expiration date and is based at least in part on non-refrigeration.
18. The method of claim 17, wherein the medication usage information comprises at least one of an indication that the medication for refrigeration is un-refrigerated, an indication of a duration of time that the medication for refrigeration was un-refrigerated, or an indication of a date that the medication for refrigeration was un-refrigerated.
19. The method of claim 13, wherein the medication is a fluid, the medicinal container for comprises at least one of a vial or a syringe, the first expiration date corresponds to an expiration based at least in part on a vial expiration, and the second expiration date corresponds to an expiration based at least in part on a syringe expiration.
20. The method of claim 19, wherein the medication usage information comprises at least one of an indication that the medication is contained in the syringe or an indication of a date that the medication was transferred to the syringe.
Patent Citations (406)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4884827(A) | 1989-12-01 | Kelley | Applicant |
| US5713485(A) | 1998-02-01 | Liff et al. | Applicant |
| US5930145(A) | 1999-07-01 | Yuyama et al. | Applicant |
| US5963134(A) | 1999-10-01 | Bowers et al. | Applicant |
| US5986662(A) | 1999-11-01 | Argiro et al. | Applicant |
| US6112502(A) | 2000-09-01 | Frederick et al. | Applicant |
| US6249299(B1) | 2001-06-01 | Tainer | Applicant |
| US6275157(B1) | 2001-08-01 | Mays et al. | Applicant |
| US6294999(B1) | 2001-09-01 | Yarin et al. | Applicant |
| US6330351(B1) | 2001-12-01 | Yasunaga | Applicant |
| US6574166(B2) | 2003-06-01 | Niemiec | Applicant |
| US6632619(B1) | 2003-10-01 | Harrison et al. | Applicant |
| US6771369(B2) | 2004-08-01 | Rzasa et al. | Applicant |
| US6825864(B2) | 2004-11-01 | Botten et al. | Applicant |
| US6847861(B2) | 2005-01-01 | Lunak et al. | Applicant |
| US6851615(B2) | 2005-02-01 | Jones | Applicant |
| US6861954(B2) | 2005-03-01 | Levin | Applicant |
| US6877658(B2) | 2005-04-01 | Raistrick et al. | Applicant |
| US6879876(B2) | 2005-04-01 | O'Dougherty et al. | Applicant |
| US6900021(B1) | 2005-05-01 | Harrison et al. | Applicant |
| US6933849(B2) | 2005-08-01 | Sawyer | Applicant |
| US6935560(B2) | 2005-08-01 | Andreasson et al. | Applicant |
| US6952681(B2) | 2005-10-01 | McQuade et al. | Applicant |
| US6985870(B2) | 2006-01-01 | Martucci et al. | Applicant |
| US6992574(B2) | 2006-01-01 | Aupperle et al. | Applicant |
| US6994249(B2) | 2006-02-01 | Peterka et al. | Applicant |
| US7036729(B2) | 2006-05-01 | Chung | Applicant |
| US7061831(B2) | 2006-06-01 | De La Huerga | Applicant |
| US7111780(B2) | 2006-09-01 | Broussard et al. | Applicant |
| US7116343(B2) | 2006-10-01 | Botten et al. | Applicant |
| US7118029(B2) | 2006-10-01 | Nycz et al. | Applicant |
| US7140542(B2) | 2006-11-01 | Andreasson et al. | Applicant |
| US7146247(B2) | 2006-12-01 | Kirsch et al. | Applicant |
| US7151456(B2) | 2006-12-01 | Godfrey | Applicant |
| US7158030(B2) | 2007-01-01 | Chung | Applicant |
| US7165077(B2) | 2007-01-01 | Kalies | Applicant |
| US7175081(B2) | 2007-02-01 | Andreasson et al. | Applicant |
| US7177721(B2) | 2007-02-01 | Kirsch et al. | Applicant |
| US7178729(B2) | 2007-02-01 | Shaffer et al. | Applicant |
| US7182256(B2) | 2007-02-01 | Andreasson et al. | Applicant |
| US7212100(B2) | 2007-05-01 | Terenna | Applicant |
| US7212127(B2) | 2007-05-01 | Jacober et al. | Applicant |
| US7227469(B2) | 2007-06-01 | Varner et al. | Applicant |
| US7232066(B2) | 2007-06-01 | Andreasson et al. | Applicant |
| US7253736(B2) | 2007-08-01 | Tethrake et al. | Applicant |
| US7256699(B2) | 2007-08-01 | Tethrake et al. | Applicant |
| US7263501(B2) | 2007-08-01 | Tirinato et al. | Applicant |
| US7264323(B2) | 2007-09-01 | Tainer et al. | Applicant |
| US7268684(B2) | 2007-09-01 | Tethrake et al. | Applicant |
| US7275645(B2) | 2007-10-01 | Mallett et al. | Applicant |
| US7299981(B2) | 2007-11-01 | Hickle et al. | Applicant |
| US7316231(B2) | 2008-01-01 | Hickle | Applicant |
| US7317393(B2) | 2008-01-01 | Maloney | Applicant |
| US7318529(B2) | 2008-01-01 | Mallett et al. | Applicant |
| US7339550(B2) | 2008-03-01 | Hayama et al. | Applicant |
| US7341147(B2) | 2008-03-01 | Mallett et al. | Applicant |
| US7348884(B2) | 2008-03-01 | Higham | Applicant |
| US7354884(B2) | 2008-04-01 | Hada et al. | Applicant |
| US7362228(B2) | 2008-04-01 | Nycz et al. | Applicant |
| US7375737(B2) | 2008-05-01 | Botten et al. | Applicant |
| US7394383(B2) | 2008-07-01 | Hager et al. | Applicant |
| US7440818(B2) | 2008-10-01 | Handfield et al. | Applicant |
| US7446747(B2) | 2008-11-01 | Youngblood et al. | Applicant |
| US7454880(B1) | 2008-11-01 | Austin et al. | Applicant |
| US7486188(B2) | 2009-02-01 | Van Alstyne | Applicant |
| US7492257(B2) | 2009-02-01 | Tethrake et al. | Applicant |
| US7492261(B2) | 2009-02-01 | Cambre et al. | Applicant |
| US7504954(B2) | 2009-03-01 | Spaeder | Applicant |
| US7518502(B2) | 2009-04-01 | Austin et al. | Applicant |
| US7518516(B2) | 2009-04-01 | Azevedo et al. | Applicant |
| US7551089(B2) | 2009-06-01 | Sawyer | Applicant |
| US7559483(B2) | 2009-07-01 | Hickle et al. | Applicant |
| US7564364(B2) | 2009-07-01 | Zweig | Applicant |
| US7630791(B2) | 2009-12-01 | Nguyen et al. | Applicant |
| US7639136(B1) | 2009-12-01 | Wass et al. | Applicant |
| US7644016(B2) | 2010-01-01 | Nycz et al. | Applicant |
| US7672872(B2) | 2010-03-01 | Shanton | Applicant |
| US7706915(B2) | 2010-04-01 | Mohapatra et al. | Applicant |
| US7706916(B2) | 2010-04-01 | Hilton | Applicant |
| US7712670(B2) | 2010-05-01 | Sauerwein, Jr. et al. | Applicant |
| US7715277(B2) | 2010-05-01 | De La Huerga | Applicant |
| US7729597(B2) | 2010-06-01 | Wright et al. | Applicant |
| US7734157(B2) | 2010-06-01 | Wright et al. | Applicant |
| US7747477(B1) | 2010-06-01 | Louie et al. | Applicant |
| US7752085(B2) | 2010-07-01 | Monroe | Applicant |
| US7772964(B2) | 2010-08-01 | Tethrake et al. | Applicant |
| US7775056(B2) | 2010-08-01 | Lowenstein | Applicant |
| US7783163(B2) | 2010-08-01 | Wright et al. | Applicant |
| US7783174(B2) | 2010-08-01 | Wright et al. | Applicant |
| US7801422(B2) | 2010-09-01 | Wright et al. | Applicant |
| US7815117(B2) | 2010-10-01 | Tuschel et al. | Applicant |
| US7834765(B2) | 2010-11-01 | Sawyer | Applicant |
| US7834766(B2) | 2010-11-01 | Sawyer | Applicant |
| US7837093(B1) | 2010-11-01 | Leu et al. | Applicant |
| US7837107(B1) | 2010-11-01 | Leu et al. | Applicant |
| US7858841(B2) | 2010-12-01 | Krautkramer et al. | Applicant |
| US7860730(B1) | 2010-12-01 | Goodall et al. | Applicant |
| US7868754(B2) | 2011-01-01 | Salvat, Jr. | Applicant |
| US7893876(B2) | 2011-02-01 | Brown et al. | Applicant |
| US7908030(B2) | 2011-03-01 | Handfield et al. | Applicant |
| US7918830(B2) | 2011-04-01 | Langan et al. | Applicant |
| US7933033(B2) | 2011-04-01 | Ohishi et al. | Applicant |
| US7976508(B2) | 2011-07-01 | Hoag | Applicant |
| US7985711(B2) | 2011-07-01 | Tohmatsu et al. | Applicant |
| US7990272(B2) | 2011-08-01 | Wass et al. | Applicant |
| US7996286(B2) | 2011-08-01 | Kreiner et al. | Applicant |
| US8002174(B2) | 2011-08-01 | Coyne, III et al. | Applicant |
| US8006903(B2) | 2011-08-01 | Braun et al. | Applicant |
| US8009913(B2) | 2011-08-01 | Greyshock | Applicant |
| US8031347(B2) | 2011-10-01 | Edwards et al. | Applicant |
| US8042738(B2) | 2011-10-01 | Cloix | Applicant |
| US8049627(B1) | 2011-11-01 | Addante | Applicant |
| US8063925(B2) | 2011-11-01 | Tainer et al. | Applicant |
| US8065858(B2) | 2011-11-01 | Leu et al. | Applicant |
| US8072635(B2) | 2011-12-01 | Roberts et al. | Applicant |
| US8077041(B2) | 2011-12-01 | Stern et al. | Applicant |
| US8082192(B2) | 2011-12-01 | Nycz et al. | Applicant |
| US8099339(B1) | 2012-01-01 | Pinsonneault et al. | Applicant |
| US8108068(B1) | 2012-01-01 | Boucher et al. | Applicant |
| US8111159(B2) | 2012-02-01 | Andreasson et al. | Applicant |
| US8112175(B2) | 2012-02-01 | Handfield et al. | Applicant |
| US8131397(B2) | 2012-03-01 | Vahlberg et al. | Applicant |
| US8154390(B2) | 2012-04-01 | Heath et al. | Applicant |
| US8174392(B1) | 2012-05-01 | Sagbhini et al. | Applicant |
| US8186587(B2) | 2012-05-01 | Zmood et al. | Applicant |
| US8212677(B2) | 2012-07-01 | Ferguson | Applicant |
| US8219413(B2) | 2012-07-01 | Martinez et al. | Applicant |
| US8224483(B1) | 2012-07-01 | Ansari et al. | Applicant |
| US8231749(B2) | 2012-07-01 | Dent et al. | Applicant |
| US8258961(B2) | 2012-09-01 | Phillips et al. | Applicant |
| US8261939(B2) | 2012-09-01 | Knoth | Applicant |
| US8271128(B1) | 2012-09-01 | Schultz | Applicant |
| US8279069(B2) | 2012-10-01 | Sawyer | Applicant |
| US8283287(B2) | 2012-10-01 | Aihara et al. | Applicant |
| US8284059(B2) | 2012-10-01 | Ross | Applicant |
| US8285083(B2) | 2012-10-01 | Canessa et al. | Applicant |
| US8285607(B2) | 2012-10-01 | Danilewitz | Applicant |
| US8286222(B2) | 2012-10-01 | Silverbrook et al. | Applicant |
| US8292173(B2) | 2012-10-01 | Yturralde et al. | Applicant |
| US8292186(B2) | 2012-10-01 | Deloche et al. | Applicant |
| US8296950(B2) | 2012-10-01 | Colbrunn et al. | Applicant |
| US8313024(B2) | 2012-11-01 | Marino | Applicant |
| US8319607(B2) | 2012-11-01 | Grimlund et al. | Applicant |
| US8328082(B1) | 2012-12-01 | Bochenko et al. | Applicant |
| US8339649(B2) | 2012-12-01 | Ohishi et al. | Applicant |
| US8341041(B2) | 2012-12-01 | Hull | Applicant |
| US8346632(B2) | 2013-01-01 | Saghbini | Applicant |
| US8355753(B2) | 2013-01-01 | Bochenko et al. | Applicant |
| US8355962(B2) | 2013-01-01 | Delaney et al. | Applicant |
| US8359338(B2) | 2013-01-01 | Butterfield et al. | Applicant |
| US8371448(B1) | 2013-02-01 | Reaux | Applicant |
| US8376228(B2) | 2013-02-01 | Devet et al. | Applicant |
| US8384545(B2) | 2013-02-01 | Hussain et al. | Applicant |
| US8385972(B2) | 2013-02-01 | Bochenko et al. | Applicant |
| US8386070(B2) | 2013-02-01 | Eliuk et al. | Applicant |
| US8394053(B2) | 2013-03-01 | Bochenko et al. | Applicant |
| US8403212(B2) | 2013-03-01 | van Esch | Applicant |
| US8403224(B2) | 2013-03-01 | Fedorko et al. | Applicant |
| US8405508(B2) | 2013-03-01 | Burke | Applicant |
| US8438067(B2) | 2013-05-01 | Omura et al. | Applicant |
| US8461076(B2) | 2013-06-01 | Okada et al. | Applicant |
| US8483550(B2) | 2013-07-01 | Wright et al. | Applicant |
| US8509604(B2) | 2013-08-01 | Wright et al. | Applicant |
| US8515251(B2) | 2013-08-01 | Wright et al. | Applicant |
| US8519849(B2) | 2013-08-01 | Ross-Messemer | Applicant |
| US8530379(B2) | 2013-09-01 | Shimizu et al. | Applicant |
| US8564416(B2) | 2013-10-01 | Steven et al. | Applicant |
| US8565552(B2) | 2013-10-01 | Sommer et al. | Applicant |
| US8582171(B2) | 2013-11-01 | Srnka et al. | Applicant |
| US8593278(B2) | 2013-11-01 | Churbock et al. | Applicant |
| US8593678(B2) | 2013-11-01 | Ohishi et al. | Applicant |
| USD694817(S) | 2013-12-01 | Adam et al. | Applicant |
| US8606596(B1) | 2013-12-01 | Bochenko et al. | Applicant |
| US8636202(B2) | 2014-01-01 | Keefe et al. | Applicant |
| US8639525(B2) | 2014-01-01 | Levine et al. | Applicant |
| US8686859(B2) | 2014-04-01 | Hussain et al. | Applicant |
| US8699054(B2) | 2014-04-01 | Edwards et al. | Applicant |
| US8702674(B2) | 2014-04-01 | Bochenko | Applicant |
| US8723674(B2) | 2014-05-01 | Conley et al. | Applicant |
| US8749356(B2) | 2014-06-01 | Hussain et al. | Applicant |
| US8755056(B2) | 2014-06-01 | Edwards et al. | Applicant |
| US8825680(B2) | 2014-09-01 | Burke et al. | Applicant |
| US8893970(B2) | 2014-11-01 | Keefe et al. | Applicant |
| US8922435(B2) | 2014-12-01 | Fontecchio et al. | Applicant |
| US8935280(B2) | 2015-01-01 | Bauman et al. | Applicant |
| US8945066(B2) | 2015-02-01 | Bochenko et al. | Applicant |
| US8948478(B2) | 2015-02-01 | Keefe et al. | Applicant |
| US8985388(B2) | 2015-03-01 | Ratnakar | Applicant |
| US8990099(B2) | 2015-03-01 | MacDonald et al. | Applicant |
| US9037479(B1) | 2015-05-01 | MacDonald | Examiner |
| US9058412(B2) | 2015-06-01 | MacDonald et al. | Applicant |
| US9058413(B2) | 2015-06-01 | MacDonald et al. | Applicant |
| US9058435(B2) | 2015-06-01 | Keefe et al. | Applicant |
| US9171280(B2) | 2015-10-01 | Gitchell et al. | Applicant |
| US9367665(B2) | 2016-06-01 | MacDonald et al. | Applicant |
| US9449296(B2) | 2016-09-01 | MacDonald et al. | Applicant |
| US9539374(B2) | 2017-01-01 | Halpern et al. | Applicant |
| US9582644(B2) | 2017-02-01 | Gitchell et al. | Applicant |
| US9734294(B2) | 2017-08-01 | MacDonald et al. | Applicant |
| US9805169(B2) | 2017-10-01 | MacDonald et al. | Applicant |
| US10083766(B2) | 2018-09-01 | Gitchell | Examiner |
| US2002/0026330(A1) | 2002-02-01 | Klein | Applicant |
| US2002/0049650(A1) | 2002-04-01 | Reff | Applicant |
| US2002/0087360(A1) | 2002-07-01 | Pettit | Applicant |
| US2002/0087362(A1) | 2002-07-01 | Cobb et al. | Applicant |
| US2002/0087554(A1) | 2002-07-01 | Seelinger | Applicant |
| US2003/0055685(A1) | 2003-03-01 | Cobb et al. | Applicant |
| US2003/0074223(A1) | 2003-04-01 | Hickle et al. | Applicant |
| US2003/0102970(A1) | 2003-06-01 | Creel et al. | Applicant |
| US2003/0160698(A1) | 2003-08-01 | Andreasson et al. | Applicant |
| US2003/0216974(A1) | 2003-11-01 | Browne | Applicant |
| US2004/0008123(A1) | 2004-01-01 | Carrender et al. | Applicant |
| US2004/0032330(A1) | 2004-02-01 | Hoffman | Applicant |
| US2004/0051368(A1) | 2004-03-01 | Caputo et al. | Applicant |
| US2004/0057609(A1) | 2004-03-01 | Weinberg | Applicant |
| US2004/0081669(A1) | 2004-04-01 | Greeven et al. | Applicant |
| US2004/0158507(A1) | 2004-08-01 | Meek et al. | Applicant |
| US2004/0178071(A1) | 2004-09-01 | Harrison et al. | Applicant |
| US2004/0215486(A1) | 2004-10-01 | Braverman | Applicant |
| US2004/0225528(A1) | 2004-11-01 | Brock | Applicant |
| US2005/0014849(A1) | 2005-01-01 | Pettit et al. | Applicant |
| US2005/0060171(A1) | 2005-03-01 | Molnar | Applicant |
| US2005/0062603(A1) | 2005-03-01 | Fuerst et al. | Applicant |
| US2005/0108044(A1) | 2005-05-01 | Koster | Applicant |
| US2005/0125097(A1) | 2005-06-01 | Chudy et al. | Applicant |
| US2005/0127176(A1) | 2005-06-01 | Dickinson | Examiner |
| US2005/0149378(A1) | 2005-07-01 | Cyr et al. | Applicant |
| US2005/0149414(A1) | 2005-07-01 | Schrodt et al. | Applicant |
| US2005/0184151(A1) | 2005-08-01 | DiMaggio et al. | Applicant |
| US2005/0283259(A1) | 2005-12-01 | Wolpow | Applicant |
| US2005/0285732(A1) | 2005-12-01 | Sengupta et al. | Applicant |
| US2005/0285746(A1) | 2005-12-01 | Sengupta et al. | Applicant |
| US2006/0006999(A1) | 2006-01-01 | Walczyk et al. | Applicant |
| US2006/0043177(A1) | 2006-03-01 | Nycz et al. | Applicant |
| US2006/0043179(A1) | 2006-03-01 | Nycz et al. | Applicant |
| US2006/0065726(A1) | 2006-03-01 | Andreasson et al. | Applicant |
| US2006/0109105(A1) | 2006-05-01 | Varner et al. | Applicant |
| US2006/0132311(A1) | 2006-06-01 | Kruest et al. | Applicant |
| US2006/0145871(A1) | 2006-07-01 | Donati et al. | Applicant |
| US2006/0152338(A1) | 2006-07-01 | Hsu | Applicant |
| US2006/0152364(A1) | 2006-07-01 | Walton | Applicant |
| US2006/0152367(A1) | 2006-07-01 | Narayanaswamy | Applicant |
| US2006/0208886(A1) | 2006-09-01 | Beamer | Applicant |
| US2006/0267731(A1) | 2006-11-01 | Chen | Applicant |
| US2007/0001809(A1) | 2007-01-01 | Kodukula et al. | Applicant |
| US2007/0008399(A1) | 2007-01-01 | Botten et al. | Applicant |
| US2007/0023512(A1) | 2007-02-01 | Miller et al. | Applicant |
| US2007/0023513(A1) | 2007-02-01 | Andreasson et al. | Applicant |
| US2007/0074722(A1) | 2007-04-01 | Giroux et al. | Applicant |
| US2007/0114279(A1) | 2007-05-01 | Lessing et al. | Applicant |
| US2007/0150382(A1) | 2007-06-01 | Danilewitz | Applicant |
| US2007/0187475(A1) | 2007-08-01 | MacLeod | Applicant |
| US2007/0188306(A1) | 2007-08-01 | Tethrake et al. | Applicant |
| US2007/0200702(A1) | 2007-08-01 | Chung | Applicant |
| US2007/0213659(A1) | 2007-09-01 | Trovato et al. | Applicant |
| US2007/0213684(A1) | 2007-09-01 | Hickle et al. | Applicant |
| US2007/0229268(A1) | 2007-10-01 | Swan et al. | Applicant |
| US2007/0272746(A1) | 2007-11-01 | Ortiz et al. | Applicant |
| US2008/0004908(A1) | 2008-01-01 | Oh et al. | Applicant |
| US2008/0012687(A1) | 2008-01-01 | Rubinstein | Applicant |
| US2008/0045930(A1) | 2008-02-01 | Makin et al. | Applicant |
| US2008/0046295(A1) | 2008-02-01 | Albrecht | Applicant |
| US2008/0094214(A1) | 2008-04-01 | Azevedo et al. | Applicant |
| US2008/0122878(A1) | 2008-05-01 | Keefe et al. | Applicant |
| US2008/0128482(A1) | 2008-06-01 | Chen et al. | Applicant |
| US2008/0129496(A1) | 2008-06-01 | Koblasz | Applicant |
| US2008/0150722(A1) | 2008-06-01 | Jackson | Applicant |
| US2008/0157967(A1) | 2008-07-01 | Jones et al. | Applicant |
| US2008/0172253(A1) | 2008-07-01 | Chung et al. | Applicant |
| US2008/0191013(A1) | 2008-08-01 | Liberatore | Applicant |
| US2008/0218307(A1) | 2008-09-01 | Schoettle | Applicant |
| US2008/0228160(A1) | 2008-09-01 | Harrison | Applicant |
| US2008/0243088(A1) | 2008-10-01 | Evans | Applicant |
| US2008/0270178(A1) | 2008-10-01 | McRae et al. | Applicant |
| US2008/0296373(A1) | 2008-12-01 | Smood et al. | Applicant |
| US2008/0297356(A1) | 2008-12-01 | Oberle | Applicant |
| US2008/0306772(A1) | 2008-12-01 | Shahrokh | Applicant |
| US2008/0316045(A1) | 2008-12-01 | Sriharto et al. | Applicant |
| US2009/0002173(A1) | 2009-01-01 | Bergsten et al. | Applicant |
| US2009/0020442(A1) | 2009-01-01 | Dietrich et al. | Applicant |
| US2009/0058653(A1) | 2009-03-01 | Geissler et al. | Applicant |
| US2009/0144087(A1) | 2009-06-01 | Kelsch et al. | Applicant |
| US2009/0153290(A1) | 2009-06-01 | Bierach | Applicant |
| US2009/0164042(A1) | 2009-06-01 | Handfield et al. | Applicant |
| US2009/0194987(A1) | 2009-08-01 | Christie et al. | Applicant |
| US2009/0224891(A1) | 2009-09-01 | Vishik et al. | Applicant |
| US2009/0231138(A1) | 2009-09-01 | Cheung et al. | Applicant |
| US2009/0267740(A1) | 2009-10-01 | Pizzuto et al. | Applicant |
| US2009/0267772(A1) | 2009-10-01 | Dehnadi | Applicant |
| US2009/0277815(A1) | 2009-11-01 | Kohl | Applicant |
| US2009/0294521(A1) | 2009-12-01 | De La Huerga | Applicant |
| US2010/0022953(A1) | 2010-01-01 | Bochenko et al. | Applicant |
| US2010/0022987(A1) | 2010-01-01 | Bochenko | Applicant |
| US2010/0036310(A1) | 2010-02-01 | Hillman | Applicant |
| US2010/0036678(A1) | 2010-02-01 | Bray | Applicant |
| US2010/0036755(A1) | 2010-02-01 | Saghbini | Applicant |
| US2010/0042439(A1) | 2010-02-01 | Martinez et al. | Applicant |
| US2010/0079337(A1) | 2010-04-01 | Hsu et al. | Applicant |
| US2010/0098425(A1) | 2010-04-01 | Kewitsch | Applicant |
| US2010/0108761(A1) | 2010-05-01 | Nycz et al. | Applicant |
| US2010/0114951(A1) | 2010-05-01 | Bauman et al. | Applicant |
| US2010/0185458(A1) | 2010-07-01 | Calderwood et al. | Applicant |
| US2010/0204659(A1) | 2010-08-01 | Bochenko | Applicant |
| US2010/0217621(A1) | 2010-08-01 | Schoenberg et al. | Applicant |
| US2010/0219097(A1) | 2010-09-01 | Ramasubramanian et al. | Applicant |
| US2010/0238039(A1) | 2010-09-01 | Tethrake et al. | Applicant |
| US2010/0268548(A1) | 2010-10-01 | Garrett et al. | Applicant |
| US2010/0275625(A1) | 2010-11-01 | Lowenstein | Applicant |
| US2010/0299158(A1) | 2010-11-01 | Siegel | Applicant |
| US2010/0328474(A1) | 2010-12-01 | Hsieh | Applicant |
| US2010/0332246(A1) | 2010-12-01 | Fedorko et al. | Applicant |
| US2011/0006879(A1) | 2011-01-01 | Bartos | Applicant |
| US2011/0063091(A1) | 2011-03-01 | Kang | Applicant |
| US2011/0068922(A1) | 2011-03-01 | Ross | Applicant |
| US2011/0093279(A1) | 2011-04-01 | Levine et al. | Applicant |
| US2011/0112682(A1) | 2011-05-01 | Matsukawa et al. | Applicant |
| US2011/0115612(A1) | 2011-05-01 | Kulinets et al. | Applicant |
| US2011/0125315(A1) | 2011-05-01 | Handfield et al. | Applicant |
| US2011/0131056(A1) | 2011-06-01 | Chudy et al. | Applicant |
| US2011/0139871(A1) | 2011-06-01 | Yturralde et al. | Applicant |
| US2011/0161112(A1) | 2011-06-01 | Keefe et al. | Applicant |
| US2011/0163871(A1) | 2011-07-01 | Einav et al. | Applicant |
| US2011/0166878(A1) | 2011-07-01 | Louie et al. | Applicant |
| US2011/0184751(A1) | 2011-07-01 | Holmes | Applicant |
| US2011/0187549(A1) | 2011-08-01 | Balasing | Applicant |
| US2011/0225100(A1) | 2011-09-01 | Sangal et al. | Applicant |
| US2011/0227722(A1) | 2011-09-01 | Salvat, Jr. | Applicant |
| US2011/0240729(A1) | 2011-10-01 | Schuck | Applicant |
| US2011/0257991(A1) | 2011-10-01 | Shukla | Applicant |
| US2011/0270441(A1) | 2011-11-01 | Handfield et al. | Applicant |
| US2011/0291809(A1) | 2011-12-01 | Niemiec et al. | Applicant |
| US2011/0301446(A1) | 2011-12-01 | Kamen | Applicant |
| US2011/0313395(A1) | 2011-12-01 | Krulevitch et al. | Applicant |
| US2012/0037266(A1) | 2012-02-01 | Bochenko | Applicant |
| US2012/0041778(A1) | 2012-02-01 | Kraft | Applicant |
| US2012/0044054(A1) | 2012-02-01 | Hussain et al. | Applicant |
| US2012/0061463(A1) | 2012-03-01 | Burke | Applicant |
| US2012/0089411(A1) | 2012-04-01 | Srnka et al. | Applicant |
| US2012/0089418(A1) | 2012-04-01 | Kamath et al. | Applicant |
| US2012/0116798(A1) | 2012-05-01 | Heath et al. | Applicant |
| US2012/0125994(A1) | 2012-05-01 | Heath et al. | Applicant |
| US2012/0130534(A1) | 2012-05-01 | Wurm | Applicant |
| US2012/0173440(A1) | 2012-07-01 | Becker et al. | Applicant |
| US2012/0177256(A1) | 2012-07-01 | Keefe et al. | Applicant |
| US2012/0179132(A1) | 2012-07-01 | Valk et al. | Applicant |
| US2012/0185951(A1) | 2012-07-01 | Bauman et al. | Applicant |
| US2012/0209619(A1) | 2012-08-01 | Knots et al. | Applicant |
| US2012/0240067(A1) | 2012-09-01 | Bauman et al. | Applicant |
| US2012/0273087(A1) | 2012-11-01 | Einy et al. | Applicant |
| US2012/0278096(A1) | 2012-11-01 | Holness | Applicant |
| US2012/0278228(A1) | 2012-11-01 | Rubinstein | Applicant |
| US2012/0323208(A1) | 2012-12-01 | Bochenko et al. | Applicant |
| US2012/0325330(A1) | 2012-12-01 | Prince et al. | Applicant |
| US2013/0018356(A1) | 2013-01-01 | Prince et al. | Applicant |
| US2013/0035950(A1) | 2013-02-01 | MacDonald et al. | Applicant |
| US2013/0038452(A1) | 2013-02-01 | Sawyer | Applicant |
| US2013/0041784(A1) | 2013-02-01 | Danilewitz | Applicant |
| US2013/0092727(A1) | 2013-04-01 | Edwards et al. | Applicant |
| US2013/0105568(A1) | 2013-05-01 | Jablonski | Examiner |
| US2013/0151005(A1) | 2013-06-01 | Gerold et al. | Applicant |
| US2013/0191149(A1) | 2013-07-01 | Kolberg et al. | Applicant |
| US2013/0221082(A1) | 2013-08-01 | Botten | Applicant |
| US2013/0221087(A1) | 2013-08-01 | Keefe et al. | Applicant |
| US2013/0225945(A1) | 2013-08-01 | Prince et al. | Applicant |
| US2013/0327822(A1) | 2013-12-01 | Keefe et al. | Applicant |
| US2014/0060729(A1) | 2014-03-01 | Srnka et al. | Applicant |
| US2014/0066880(A1) | 2014-03-01 | Prince et al. | Applicant |
| US2014/0117081(A1) | 2014-05-01 | Jablonski et al. | Applicant |
| US2014/0136229(A1) | 2014-05-01 | Levine et al. | Applicant |
| US2014/0142975(A1) | 2014-05-01 | Keefe et al. | Applicant |
| US2014/0184390(A1) | 2014-07-01 | Elizondo, II | Applicant |
| US2014/0184391(A1) | 2014-07-01 | Elizondo, II | Applicant |
| US2014/0197954(A1) | 2014-07-01 | Caputo et al. | Applicant |
| US2014/0210596(A1) | 2014-07-01 | Hussain et al. | Applicant |
| US2014/0262919(A1) | 2014-09-01 | Hussain et al. | Applicant |
| US2014/0263614(A1) | 2014-09-01 | Keefe et al. | Applicant |
| US2014/0276213(A1) | 2014-09-01 | Bochenko | Applicant |
| US2014/0282197(A1) | 2014-09-01 | Keefe et al. | Applicant |
| US2014/0291397(A1) | 2014-10-01 | Caputo et al. | Applicant |
| US2014/0367080(A1) | 2014-12-01 | Hussain et al. | Applicant |
| US2014/0372145(A1) | 2014-12-01 | MacDonald et al. | Applicant |
| US2015/0058182(A1) | 2015-02-01 | Kress-Spatz et al. | Applicant |
| US2015/0235005(A1) | 2015-08-01 | MacDonald et al. | Applicant |
| US2015/0339622(A1) | 2015-11-01 | MacDonald et al. | Applicant |
| US2017/0132734(A1) | 2017-05-01 | MacDonald et al. | Applicant |
| US2018/0039758(A1) | 2018-02-01 | MacDonald et al. | Applicant |
| US2019/0088354(A1) | 2019-03-01 | Yanowitz et al. | Applicant |
| CA2722328 | 2009-10-01 | Applicant | |
| CA2790220 | 2013-06-01 | Applicant | |
| CN102791310(B) | 2014-12-01 | Applicant | |
| EP2496283 | 2012-09-01 | Applicant | |
| IN2012/04914(P4) | 2013-10-01 | Applicant | |
| WO2/095675 | 2002-11-01 | Applicant | |
| WO3/071943 | 2003-09-01 | Applicant | |
| WO2006/026246 | 2006-03-01 | Applicant | |
| WO2006/135830 | 2006-12-01 | Applicant | |
| WO2010/074781 | 2010-07-01 | Applicant | |
| WO2011/056888 | 2011-09-01 | Applicant | |
| WO2011/115676 | 2011-09-01 | Applicant | |
| WO2011/150013 | 2011-12-01 | Applicant | |
| WO2013/082423 | 2013-06-01 | Applicant | |
| WO2013/116873 | 2013-08-01 | Applicant | |
| WO2013/134256 | 2013-09-01 | Applicant | |
| WO2014/159928 | 2014-10-01 | Applicant | |
| WO2014/189834 | 2014-11-01 | Applicant | |
| WO2015/026387 | 2015-02-01 | Applicant |
Non-Patent Literature (81)
- “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/.Applicant
- Bacheldor, Beth, “ASD Healthcare Deploys RFID Refrigerated Drug Cabinets”, RFID Journal, Sep. 24, 2007, p. 1. http://www.rfidjournal.com/articles/view?3632.Applicant
- Bacheldor, Beth, “Cardinal Health Readies Item-Level Pilot”, RFID Journal, May 31, 2006, p. 1. http://www.rfidjournal.com/articles/view?2380.Applicant
- Bacheldor, Beth, “UCSD Medical Center Expands Its RFID Deployment”, RFID Journal, Oct. 29, 2008, pp. 2. http://www.rfidjournal.com/articles/view?4423.Applicant
- 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.Applicant
- Barlas, Stephen, “Pharmacy Product Tracing Likely to Go National—Costs to Pharmacies Worrisome,” Pharmacy & Therapeutics, Jan. 2009, vol. 34 No. 1, p. 14.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- çakici et al., “Using RFID for the Management of Pharmaceutical Inventory-System Optimization and Shrinkage Control,” Decision Support Systems, 2011, pp. 842-852.Applicant
- Cangialosi et al., “Leveraging RFID in Hospitals: Patient Life Cycle and Mobility Perspectives”, IEEE Applications & Practice, Sep. 2007, pp. 18-23.Applicant
- 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.Applicant
- Collins, “RFID Cabinet Manages Medicine”, RFID Journal, Aug. 12, 2004, p. 1. http://www.rfidjournal.com/articles/pdf?1081.Applicant
- 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.Applicant
- “Crash Cart Inventory Checklist”, Outpatient Surgery Magazine, Oct. 2004, p. 1. http://www.outpatientsurgery.net/resources/forms/2004/pdf/OutpatientSurgeryMagazine_0410_crashCart.pdf.Applicant
- 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.Applicant
- “Data Gathering Developments”, Manufacturing Chemist, Feb. 1, 2005, p. 24. http://www.manufacturingchemist.com/news/article_page/Data_gathering_developments/35805.Applicant
- 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.Applicant
- Edwards, John, “RFID Smart Shelves and Cabinets”, RFID Journal, Aug. 24, 2009, pp. 4. http://www.rfidjournal.com/articles/view?5140/4.Applicant
- 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.Applicant
- 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/.Applicant
- “Faraday Cage”, Wikipedia, last edited Apr. 12, 2018, pp. 5. https://en.wikipedia.org/wiki/Faraday_cage.Applicant
- Floerkemeier et al., “The Smart Box Concept for Ubiquitous Computing Environments”, The Smart Box Concept for Ubiquitous Computing Environments, 2004, pp. 4.Applicant
- Gonzalez, Stephanie, “Health Maintenance System (HMS) Hardware Research, Design, and Collaboration,” NASA USRP—Internship Final Report, 2010, pp. 1-20.Applicant
- 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. http://www.cathlabdigest.com/articles/Doing-Wave-Inventory-Management-RFID.Applicant
- Harrop et al., “RFID for Healthcare and Pharmaceuticals, 2008-2018,” Securing Pharma, May 2008, pp. 1-12.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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-Nurse-From-Pain-Inventory-Duties.Applicant
- “Intel & Siemens Launch RFID Blood Bank in Malaysia”, RFID Journal, Aug. 16, 2007, p. 1. http://www.rfidjournal.com/articles/view?6801.Applicant
- 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.Applicant
- Jorgensen et al., “Executable Use Cases: Requirements for a Pervasive Health Care System,” IEEE Software, Mar./Apr. 2004, pp. 34-41.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- Lampe et al., “The Smart Box Application Model,” Advances in Pervasive Computing, 2004, pp. 1-6.Applicant
- 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.Applicant
- 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/.Applicant
- 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/.Applicant
- “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#.VR7guPnF_10.Applicant
- “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.Applicant
- 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.Applicant
- Meiller et al., “Adaptive Knowledge-Based System for Health Care Applications with RFID-Generated Information”, Decision Support Systems, vol. 51, 2011, pp. 198-207.Applicant
- 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.Applicant
- “New RFID Medical Cabinets Deployed at 50 Hospitals”, RFID Journal, Sep. 17, 2007, pp. 2. http://www.rfidjournal.com/articles/view?6823.Applicant
- O'Connor, Mary Catherine, “Drug Distributor Uses RFID to Vend Meds”, RFID Journal, May 23, 2006, pp. 2. http://www.rfidjournal.com/articles/view?2363/2.Applicant
- O'Connor, Mary Catherine, “GlaxoSmithKline Tests RFID on HIV Drug”, RFID Journal, Mar. 24, 2006, pp. 2. http://www.rfidjournal.com/articles/view?2219.Applicant
- O'Connor, Mary Catherine, “Interrogators Start to Evolve”, RFID Journal, Jun. 1, 2006, pp. 3. http://www.rfidjournal.com/purchase-access?type=Articel&id=2398&r=%2Farticles%2Fview%3F2398.Applicant
- 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.Applicant
- O'Connor, Mary Catherine, “McKesson Starts RFID Pilot for Viagra”, RFID Journal, Feb. 17, 2005, pp. 2. http://www.rfidjournal.com/articles/view?2157.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- “RFID Medical Cabinets Evaluated in New Benchmark”, RFID Journal, Sep. 12, 2007, pp. 2. http://www.rfidjournal.com/articles/view?6819.Applicant
- 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.Applicant
- Saygin, C., “Adaptive Inventory Management Using RFID Data”, The International Journal of Advanced Manufacturing Technology, 2007, vol. 32, pp. 1045-1051.Applicant
- Singh et al., “Versatility of Radio Frequency Identification (RFID) Tags in the Pharmaceutical Industry”, Instrumentation Science and Technology, vol. 36, pp. 656-663, 2008.Applicant
- Swedberg, Claire, “Tennessee Hospital Tracks High-Value Items”, RFID Journal, Aug. 5, 2009, pp. 2. http://www.rfidjournal.com/articles/view?5106.Applicant
- 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/.Applicant
- 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/.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- Wasserman, Elizabeth, “Purdue Pharma to Run Pedigree Pilot”, RFID Journal, May 31, 2005, pp. 2. http://www.rfidjournal.com/articles/view?1626.Applicant
- Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Dec. 1, 2017, 45 pages.Applicant
- Defendant's Answer, Affirmative Defenses and Counterclaims to Plaintiff's Complaint, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 2, 2018, 43 pages.Applicant
- 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. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Feb. 9, 2018, 43 pages.Applicant
- 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. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jun. 18, 2018, 25 pages.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- 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.Applicant
- Exhibit L; Fagron Academy, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Dec. 1, 2017, 2 pages.Applicant
- Plaintiff's Answer to Defendant's Counterclaims, Kit Check, Inc. v. Health Care Logistics, Inc. (involving U.S. Pat. No. 8,990,099, U.S. Pat. No. 9,037,479, U.S. Pat. No. 9,058,412, U.S. Pat. No. 9,058,413, U.S. Pat. No. 9,367,665, U.S. Pat. No. 9,734,294, and U.S. Pat. No. 9,805,169), Case No. 2:17-cv-01041-ALM-CMV (S.D. Ohio), Jan. 19, 2018, 14 pages.Applicant