Management of pharmacy kits
A system for managing pharmacy kits comprises a reading station configured to read tag information from a plurality of radio frequency identification (RFID) tags associated with a pharmacy kit, and an information processing system operatively connected to the reading station and configured to receive the tag information from the reading station and determine a status of the pharmacy kit based on the tag information, a plurality of stored templates defining contents to be included in each of a plurality of pharmacy kits, and a plurality of kit records indicating the current contents of a plurality of pharmacy kits.
Latest Kit Check, Inc. Patents:
This application is a continuation of U.S. patent application Ser. No. 14/603,730 filed on Jan. 23, 2015, which is a continuation of U.S. patent application Ser. No. 13/554,342 filed on Jul. 20, 2012, which claims priority to U.S. Provisional Application No. 61/514,231 filed on Aug. 2, 2011, each of which is incorporated herein by reference in its entirety.
BACKGROUNDHospital pharmacies often manage groups of medical items in the form of pharmacy kits. A pharmacy kit can be used, for instance, to provide a group of items for a specific medical procedure, a particular physician, or a designated location of a hospital. As an example, a pharmacy kit can be used to aggregate and transport a collection of medicines for treating a patient with a specific type of stroke, heart condition, or other ailment.
A pharmacy kit (or “kit”) typically comprises a group of items specified by a template. For example, the template may specify that the kit requires three vials of adenosine, two containers of albuterol solution, two vials of amiodarone, and so on. The template may also specify ways in which individual items may be satisfied. For example, it may specify that the vials of adenosine may be satisfied by certain product brands. Pharmacy kits are usually stocked by a hospital pharmacy, but they may be stocked by another entity, such as an outsourced kit stocking company.
Local board-of-pharmacy regulations (e.g., state regulations) typically allow a hospital or other facility to define the contents of its kits. In other words, they allow the hospital to create its own templates. These regulations, however, also require that the hospital adhere to a template once defined. This typically requires specific procedures to ensure accuracy of kit contents. Such procedures can include, for instance, regulated kit creation and inventory procedures, and prescribed monitoring and/or update procedures. The following are examples of such procedures as used in certain conventional contexts.
A kit is typically created by receiving specified items in a pharmacy, manually recording (e.g., on paper and/or electronic records) their product identifiers (e.g., National Drug Code (NDC) or Universal Product Code (UPC)), lot numbers, and expiration dates, and then loading the items into a container, such as a box, tray, or canister. During the kit's lifetime, it may be updated periodically to replace expired or consumed items. These updates are typically performed by manually inspecting the kit, comparing it to a corresponding template, modifying kit contents as required, and then manually recording any changes.
Unfortunately, the above procedures tend to suffer from significant shortcomings. For instance, the manual recording of item information is generally time consuming and error prone, which drives up the cost of creating and updating the kits. Moreover, these procedures are usually performed by highly trained pharmacy staff, which may be an inefficient use of their time. Manual inspections for missing, expired, or soon-to-be expired items can also be time consuming and error prone, particularly because item expiration dates tend to vary between different products within the same kit.
Due to the above and other shortcomings, there is a general need for improved techniques and technologies for managing pharmacy kits.
SUMMARYAccording to one embodiment of the inventive concept, a system for managing pharmacy kits comprises a reading station configured to read tag information from a plurality of radio frequency identification (RFID) tags associated with a pharmacy kit, and an information processing system operatively connected to the reading station and configured to receive the tag information from the reading station and determine a status of the pharmacy kit based on the tag information, a plurality of stored templates defining contents to be included in each of a plurality of pharmacy kits, and a plurality of kit records indicating the current contents of a plurality of pharmacy kits.
According to another embodiment of the inventive concept, a method of managing pharmacy kits comprises operating an RFID reader to read tag information from a plurality of RFID tags associated with a pharmacy kit, identifying a plurality of items present in the pharmacy kit based on the tag information, and comparing the plurality of items with an electronic template to determine a status of the pharmacy kit.
According to another embodiment of the inventive concept, a method comprises building a pharmacy kit comprising a plurality of pharmaceutical items labeled with RFID tags, verifying contents of the pharmacy kit by operating an RFID reader to read tag information from the RFID tags and comparing the tag information with an electronic template, deploying the pharmacy kit within a facility following the verification, and re-verifying the contents of the pharmacy kit following the deployment by operating an RFID reader to read tag information from the RFID tags and comparing the tag information with the electronic template.
The drawings illustrate selected embodiments of the inventive concept. In the drawings, like reference numbers indicate like features.
Embodiments of the inventive concept are described below with reference to the accompanying drawings. These embodiments are presented as teaching examples and should not be construed to limit the scope of the inventive concept.
The described embodiments relate generally to management of pharmacy kits (hereafter, “kits”) such as those commonly used in hospital environments or other medical facilities. Such kits can be distinguished generally from other types of kits used by hospitals, such as surgical instrumentation kits, electronic equipment kits, and so on, due to the unique nature of pharmaceutical products. For example, pharmaceutical products may be regulated very different from the items in surgical kits due to the need to constantly monitor expiration dates, and also due to the substitutability of some pharmaceutical products for others.
In certain embodiments, a kit management system uses RFID technology to label and track the contents of a kit. The use of RFID technology can allow a pharmacy to accurately and efficiently determine whether items in the kit are consumed, missing, expired, or near expiration. These determinations can be used thereafter to verify and update the kit contents, track item usage patterns, generate patient billing information based on item consumption, and so on.
In certain embodiments, a hospital pharmacy begins by tagging items upon bulk receipt in the hospital, or when a kit is stocked. Alternatively, items may arrive at a hospital pre-tagged. One way to tag the items is by scanning bar codes present on most items used in a kit, printing RFID tags based on the scanned bar codes, and then applying the RFID tags to the items. The scanned bar codes typically provide item information such as product identifiers (e.g., NDC or UPC), lot numbers, and expiration dates. This information can be associated with the RFID tags in a computer database to allow subsequent identification and processing by RFID technology. In some embodiments, the RFID tags can be generated automatically when scanning the bar codes, e.g., through the use of an RFID tag printer operatively connected to a bar code scanning machine. Alternatively, the RFID tags may be non-printed tags.
A kit is typically built by placing tagged items in a container such as a box, tray, or canister, and optionally labeling the kit with an RFID tag having information such as a kit identifier, kit type, intended user, or location, for example. These steps are generally performed by a pharmacist or other competent medical professional.
Once a kit is built, its contents are verified by placing it in an RFID reading station, which reads all RFID tags within its sensing range to identify the kit type and any items present. In some embodiments, the RFID reading station includes an enclosure such as a metal box to allow scanning of the kit exclusive of other RFID devices that may be in the surrounding environment. Alternatively, the RFID reading station may omit such an enclosure, for instance, by performing reading in an open area such as table, or using a handheld RFID reader. If the kit has an RFID tag, the kit type can be determined from the tag. Otherwise, it may be inferred from the items present. Items are typically identified by recognizing their RFID tags and then accessing stored information that maps the RFID tags to specific item information.
The stored information may reside on electronic equipment located at the RFID reader station or a remote location such as a remote server, a personal computer (PC), a mobile device, etc. In addition to basic kit and item information, the electronic equipment may also store metadata related to kit processes, such as who built or rebuilt a kit, what items were replaced if the kit was restocked, when the items were inserted in the kit, when verification and update procedures were last performed or will next be performed, and so on.
After the kit and item information are determined by the kit management system, they are analyzed automatically with reference to one or more templates. For instance, a kit template may be located based on the kit type, and then the identified items may be compared with the kit template to determine whether any items are missing or require replacement based on use or expiration. Additionally, the information processing system may analyze item information to determine whether any items are expired or will soon expire. The kit can then be updated based on these analyses.
Kit templates are typically stored in a database within or associated with the information processing system. However, they can alternatively be stored within a memory associated within the RFID reading station or RFID reader, or they can be stored in a separate system accessible by the information processing system.
In general, expiration of an item may occur based on a fixed or variable timeframe. For example, some items may expire at a fixed date indicated by the manufacturer, while other items may expire after a certain amount of time out of the refrigerator, e.g., time of removal+X days. Whether the timeframe is fixed or variable can be indicated in the template at a master level for a particular item, or at a segment level for a segment including the item.
The automatic processing provided by RFID technology and associated electronic equipment allows kit management to be performed with greater efficiency and accuracy compared with conventional approaches. For instance, in some embodiments, kit contents and expiration dates can be validated in 15 seconds or less. Moreover, kit deficiencies can be reported to a pharmacist automatically, allowing them to be addressed in an efficient manner. This reporting can be accomplished, for instance, by an automatically generated charge sheet showing kit contents and expirations.
Once a kit is built and verified, it is ready to be sealed and deployed for use in the hospital. When a kit is used, the seal is broken and items may be removed or consumed. Accordingly, the kit may be subsequently returned to the RFID reading station for additional verification, monitoring, and updates. These additional procedures can be used, for example, to determine whether any items in the kit are missing (e.g., due to use), and whether any items are erroneously present in the kit. This information can then be used to generate a report indicating the status and any necessary updates for the kit, or for other purposes such as patient billing or supply ordering. Once the relevant information is collected, the kit can be rebuilt using the automatically generated report, and then redeployed for another use.
Stored item and kit information can also be used to perform various forms of monitoring and/or reporting related to inventory management. For instance, stored kit information can be analyzed to identify patterns of item consumption. Moreover, the stored information can be inspected to determine the location of kits containing expired items. These and other forms of monitoring and/or reporting can be performed either automatically or in response to user input. For instance, they can be performed according to a predetermined schedule or in response to certain event triggers. Alternatively, a user may simply request monitoring or a report as needed. For example, a pharmacy manager may log in to view consumption logs, usage logs, and current inventory to make more informed decisions on which inventory to keep and which kits may require special attention.
The kit management system typically further comprises a user interface and one or more software applications allowing a user to access information regarding the status of kits. As an example, a software application may be used to generate and print a kit charge sheet or charge sheet with the contents and expiration dates of the items and a kit. As other examples, a software application may be used to generate inventory reports showing where kits are dispatched within a hospital, an expiration report indicating dispatched items that are expired or near expiration, consumption, and usage reports with traceability to departments, code types, or patients. The kit management system can also comprise or be integrated with a real-time tracking system to maintain current information regarding kit locations. The real-time tracking system typically comprises electronic components associated with the kits and configured to transmit information from the kits to the information processing system to identify the kits' respective locations. Such tracking systems can also be combined with kit management software in order to update the information used to generate inventory reports.
As indicated by the foregoing, a kit management system according to certain embodiments can provide many potential benefits compared with conventional technologies. For example, the kit management system can provide more efficient verification and recording of kit contents, and more accurate monitoring of kits, items, and expiration dates. In certain embodiments, the kit management system may also provide data analysis capabilities for purposes such as patient billing, inventory tracking, and so on.
Referring to
RFID reading station 110 comprises an RFID reader configured to read RFID tags located on kit 105. During a typical read operation, the RFID reader interrogates RFID tags associated with respective items in kit 105, and it also interrogates any RFID tag associated with kit 105. As a consequence of the interrogation, the RFID reader receives information identifying each tag, and it conveys the information to information processing system 115. Based on the tag information, information processing system 115 identifies kit 105 and the items present. This can be accomplished, for instance, by relating the tag information to item or kit information stored in a computer database.
Once the kit and items are identified, information processing system 115 may process corresponding information in various ways, for example, by displaying it to a user, generating reports indicating missing or expired items, performing patient billing procedures based on any consumed items, or merely storing it for subsequent analysis. In certain embodiments, the kit and item information is managed as a list. For example, it can be stored and accessed in the form of a list in a computer database or other storage medium.
System 100 may occasionally aggregate last known status information for each kit that has been read, and it may then determine whether any action is required to resolve expiration issues, missing item issues, or extra item issues in all of the kits in a hospital or other facility. These actions can be performed, for example, on a periodic basis, in response to particular events, or in response to a user request.
In addition to storing the current or most recent information regarding the kits, system 100 may also store a virtual history for each kit. Such a virtual history may include, for example, a record of each transaction involving the kit since the time it was tagged. Such transactions may include, for example, scans, database queries, updates such as restocking or removal of items, and so on. The virtual history may be maintained by information processing system 115, for example, and it may be output in the form of a report in response to a user request. In addition, the virtual history may be used to gather data or statistics that may be useful for planning future tasks such as kit updates, item restocking, and so on.
Kit 105 can be associated to a location or responsible person, such as a physician. This association can then be stored in system 100, and it can be used to quickly determine the location of kit 105 after deployment. The location of kit 105 can also be determined and/or updated by associating its RFID tag with a real time location system. In addition, kit 105 may be associated with a patient identifier or billing identifier and any missing items may be marked as being consumed by that billing or patient identifier. Such billing information may be stored either in system 100, in a separate system or in both system 100 and a separate system. System 100 may retrieve or update some or all of the billing information when a kit is read and items may or may not be consumed.
Where kit 105 contains prescription pharmaceuticals, the facility may be required to comply with requirements set by a state board of pharmacy. The precise regulations may vary from state to state, but can include requirements such as a mandatory visual inspection of kit 105 prior to deployment, or an item-by-item determination of each item type, lot number and expiration date. Other board of pharmacy requirements may include documentation to be included in kit 105 to verify completeness and accuracy of expiration data or a label on the outside of kit 105 to indicate the last check of the kit and the next expiring item in the kit.
In some embodiments, system 100 is configured to store relevant board of pharmacy requirements and verify that each step has been completed. System 100 can also be configured to compute steps automatically where allowed by regulations. Such steps may include, for example, printing documentation or labels, reading tags and verifying items, or requesting confirmation that a manual step has been completed. As these steps are completed, system 100 may record the name of the person who performed the steps. It may also confirm whether the person is authorized to perform the steps. In general, information regarding these and other steps can be recorded in system 100 using a log, database, or other storage format.
Although
In addition, the physical and functional implementation of system 100 can be distributed arbitrarily across multiple devices, systems, or network components. For example, in some embodiments, information processing system 115 may include or be integrated with wireless mobile devices in order to convey information remotely. One potential use of such a configuration would be to transmit kit notifications to remote users via push email or SMS text messaging, or subscription based data feeds. Such notifications could be used, for instance, to alert users that an updated kit is available, that a kit should be returned to the pharmacy, that a checked-out kit requires updates due to item expiration, and so on. Another potential reason to integrate information processing system 115 with remote components is to receive updates of kit templates and item master data. For example, some or all of a kit template or item master data may be received from an external system. The received item master data could indicate, for example, that an item has been recalled or changed in some material respect.
Referring to
Items 210 typically include medicines or other medical supplies that may be stocked by a pharmacy. As shown in
Due to the different types of packaging and materials, items 210 may be tagged with RFID tags having different shapes or types. As one example, RFID tags placed on metal bags may be subject to electromagnetic interference (EMI) from the metal. Accordingly, to prevent EMI, RFID tags connected to metal bags may have a foam backing or other form of insulation to create separation from the bags. Such tags may be referred to as metal-mount tags. As another example, RFID tags attached to small vials or bottles may potentially occlude label information on the vials. Accordingly, to prevent occlusion, RFID tags having a transparent adhesive portion may be attached to vials, bottles, or other types of packages. Such tags may be referred to as transparent tags.
Kit 105 is typically built by manually placing items 205 in container 210. This is typically accomplished by a pharmacist or other competent medical professional after items 205 have been labeled with RFID tags and stocked in the pharmacy. For example, a pharmacist may visit pharmacy shelves to collect items 205 and place them in container 210.
Referring to
For simplicity,
The template further defines a set of permissible items that can be used to satisfy each segment. The permissible items may correspond to different brands or other forms of each item corresponding to the segment. These items are generally identifiable by distinct NDC or UPC identifiers. As an example, a segment defined as a “bottle of ibuprofen” may be satisfied by a either a bottle of Advil or a bottle of generic ibuprofen. For simplicity,
The template still further defines a quantity of items to be included in kit 105 for each segment. For example, based on the template of
In general, the quantity can be zero or more. Where the quantity is greater than one, each item of a particular segment can be satisfied by any combination of the permissible items for that segment. For example, if there are three permissible items and the required quantity is three, the requirement may be satisfied by three of the same permissible item, one of each, etc. For instance, some kits may allow the stock of adenosine vials to be satisfied by different product brands. Alternatively, the template may require that multiple instances of the same item be selected, or that only certain combinations of items are permitted. Moreover, the template may include restrictions on the items that can be included in combination from among different segments.
Although the template determines the contents to be included in the kit under most circumstances, there are occasions where deviation from the template will be permitted. One of these occasions is a national shortage of one or more items to be included in the kit. When there is a national shortage of a particular item, certain substitutions or omissions of the item may be allowed. For example, if sodium bicarbonate is on national shortage, a kit may be permitted to include a suitable substitute for sodium bicarbonate, or it may be permitted to be deployed without sodium bicarbonate or any substitute.
The procedure for managing items under shortage may be defined in a variety of ways. For example, allowable substitutes for national shortage conditions may be embedded in the template itself and then triggered by information processing system 115 when a shortage arises. As an alternative example, information processing system 115 may simply ignore certain restrictions in a template when a shortage arises.
Referring to
The kit record is typically generated by RFID reading station 110 or information processing system 115 upon verifying or re-verifying the kit. It can then be compared to a corresponding template to determine whether the kit has missing or expired items, or it can be stored in information processing system 115 for subsequent comparisons, updates, or analyses.
Referring to
In a typical read operation, RFID reader 305 controls antenna 310 to interrogate any RFID tags within container 315. In response to the interrogation, the RFID tags communicate information to RFID reader 305 via antenna 310. The communicated information is typically associated with corresponding information stored in a database, such as NDC identifiers, lot numbers, and expiration dates for individual items, and a kit identifier for the kit as a whole. RFID reader 305 communicates the received information to information processing system 115 for storage and/or comparison with a template.
Referring to
In some embodiments, RFID reading station 110 is restricted to receiving only one kit at a time. This restriction may be imposed in a variety of ways, for instance, by configuring an enclosure to accommodate only one kit container or interrogating kit tags prior to scanning to ensure that no more than one kit tag is present. In certain alternative embodiments, RFID reading station 110 may be specifically configured to allow concurrent scanning of multiple kits. For example, two kits could be placed in RFID reading station 110, scanned concurrently, and then assigned to a common location or person, such as a particular cart, room, physician, etc. Moreover, such a common assignment may be recorded in information processing system 115 to allow joint analysis or tracking of more than one kit.
Referring to
Computer 405 comprises a browser 410 that receives kit information from the RFID reader via LAN 435 and communicates with server 420 through the internet 415. Server 420 stores templates 425, which typically include kit master templates and item master templates. Server 420 also stores records 430, which include information regarding individual kits and items.
Although server 420 is shown as a single unit in
The RFID printer can be used to print RFID tags automatically when a kit is being built or updated. For example, an RFID tag can be printed for a new item by scanning the item's bar code using a bar code scanner connected to computer 405, accessing server 420 to associate a particular RFID tag with the item, and then printing the RFID tag.
Referring to
Information processing system 115 updates stored records to reflect the scanning (520). In the update, a database in information processing system 115 is updated to reflect the scanned kit contents. For example, the database may be updated to reflect the presence of any new or replaced items, along with their expiration dates. The database may also be updated with other information, such as the name of the person who last modified the kit contents, a location to which the kit is to be deployed, a patient to be billed for consumption of kit items, and so on.
Based on the updated records, information processing system 115 performs a status check to verify the contents of the kit (525). The status check typically involves forming a list of items based on the transmitted information or updated records and comparing the list against a kit template. It may also involve comparing the updated kit information against information obtained in prior scans, or evaluating the kit information in light of certain business rules, such as billing protocols.
If the status check indicates a deficiency in the kit (525=“Deficiency”), such as missing or expired items, the kit contents are updated (530), and the method returns to step 515 where the kit is re-scanned. The update can be performed, for example, by replacing any expired items or inserting missing items. Otherwise, if the status check indicates no deficiency in the kit (525=“No Deficiency”), the kit is deployed for use in the hospital or other facility served by the pharmacy (535).
The updating of records and status check are typically performed any time the kit is scanned, as indicated by the flow of
Deployment of the kit may involve, for example, transporting it to a specific location of the hospital, checking it out to a particular individual, or merely storing it within the pharmacy. Following deployment, steps 515 through 535 may be repeated any number of times as needed. For example, the kit may be re-scanned and updated following each use or it may be periodically updated at specified times, such as daily, weekly, or whenever an expired item is noted in information processing system 115.
Referring to
Based on the item information, system 100 determines whether each item requires a first type of tag (illustrated as type “A”) or a second type of tag (illustrated as item type “B”) (615). This determination is typically performed based on the type of the item or its packaging. For example, items having metal packaging such as metal bag, etc., may require an RFID tag having a thicker insulation layer (e.g., foam) to prevent it from experiencing EMI from the metal. Other types of items, such as glass or plastic packages, may not require such an RFID tag. Although the method of
In creating the tags, system 100 may optionally perform automatic detection of whether it is attached to an RFID printer. If such an attachment is detected, it may control the RFID printer to print an RFID tag having a unique identifier for each item in the kit. Otherwise, a user may manually enter a unique tag identifier for each item into system 100. The manually entered identifiers can be determined, for example, based on the labeling of already printed RFID tags.
Next, system 100 associates the unique identifiers with the stored item information (630), allowing the item information to be retrieved subsequently when the RFID tags are scanned. Finally, the RFID tags are attached to corresponding items (635).
Referring to
Referring to
Referring to
Next, the server returns instructions on how to scan which could take the form of a link allowing control of the RFID reader (830). In the example using a link, the user clicks on the link to start a read operation, and the RFID reader then captures tag information from kit 105 and transmits it to the computer (835). Finally, the computer relays the tag information to the server for validation, storage, and/or other forms of processing (840).
The server typically stores kit-related information such as master templates, item master templates, and information regarding individual kits and items, as in the example of
Referring to
Referring to
Report 1000 also includes a portion 1015 indicating the date of a most recent scan, a portion 1020 showing additional details for the soon-to-expire items, and a portion 1025 showing additional details for missing items.
Report 1100 comprises a portion 1105 indicating the type of the kit and the total number of items in the kit. In this example, the kit comprises 26 total items. Report 1100 further comprises a portion 1010 indicating the number of extra and missing items in the kit, an entity to be billed for used items, and the number of expired or soon to expire items. In this example, there are two extra items, one expired item, and one soon-to-expire item. The entity to be billed is listed as KRE1981. The expired item is a box of Protopic, which is listed as having expired on Sep. 28, 2012.
Report 1100 further comprises a portion 1115 indicating the date of a most recent scan, a portion 1120 showing additional details for the expired items, a portion 1125 showing additional details for the soon-to-expire items, and a portion 1130 showing additional details for the extra items. Report 1100 still further comprises a portion 1135 indicating a current location of the kit and providing a “check out” button for assigning the kit to a specific location or person. In this example, the kit is currently assigned to the location “Central Pharmacy”.
Referring to
Interface 1300A further comprises a second area 1310A for displaying the report. According to the report in area 1310A, system 100 has information on two kits satisfying the specified options. In particular, a demo kit has a shortage of nasal spray, and it has a soon-to-expire container of Gentamicin Sulfate. A bandage kit has shortages of small, medium, and large bandages.
Referring to
Interface 1300B further comprises a second area 1310B for displaying the report. According to the report in area 1310B, a demo kit includes an item with the lot number specified in second area 1310A. Notably, in the example of
In addition to generating reports such as those illustrated in
System 100 may also automatically inventory items in pharmacy kits to determine where anything is missing, extra, expired, or near expired. This can reduce the chance of manual kit stocking errors or related medical errors in a hospital or other facility. System 100 may also automatically find items for recall in the hospital or emergency medical field kits.
Label 1400 is designed such that it can be securely attached to different types of items in a pharmacy kit without occluding labeling information. For example, label 1400 can be used in such a way that it hangs off the side of a vial, ampule, or other product where it may be inappropriate to place the main portion of the label directly on the product or product packaging. Alternatively, label 1400 can be attached to an item such that it does not hang off the side. A configuration where a portion of label 1400 hangs off the side of an item will be referred to as a “flagged” configuration.
Referring to
First and second portions 1405 and 1420 both have an adhesive backing. Accordingly, where label 1400 is used in the flagged configuration, adhesive backing portions of printed portion 1410 and flap portion 1415 may be folded together along the perforation to prevent them from sticking to other objects. Where label 1400 is not used in the flagged configuration (e.g., when it is attached to a boxed item), first and second portions 1405 and 1420 may both be adhered to an item. Moreover, where label 1400 is not used in the flagged configuration, flap portion 1415 may be removed by detaching it from printed portion 1410 along the perforation.
Printed portion 1410 and flap portion 1415 are typically formed with a substrate material comprising a common labeling material such as paper or plastic. Printed portion 1410 further comprises an embedded RFID device attached to the substrate. An example of such an RFID device is shown by RFID device 1435 in
The adhesive side of tail 1425 can be used to attach label 1400 to a kit item. Prior to use, the adhesive side is attached to backing 1430. Tail 1425 is typically formed of a transparent material to avoid obscuring information on the items in a kit. In general, when labeling medical items such as pharmaceuticals, it is important not to obscure labels, warnings, and other information on the packaging. The use of a transparent tail 1425 avoids this problem by allowing the user to see through any portion of the tail that may be attached to an item. Moreover, the shape of tail 1425 and allows an RFID tag to be attached to and/or hang off items having various different types of packaging. As examples, tail 1425 can be wrapped around a vial or ampule while allowing first portion 1405 to hang off. Similarly, it can be attached to a face of a box or a panel of a bag.
As alternatives to the example of
Referring to
Referring to
Referring to
The foregoing is illustrative of embodiments and is not to be construed as limiting thereof. Although a few embodiments have been described, those skilled in the art will readily appreciate that many modifications are possible in the embodiments without materially departing from the novel teachings and advantages of the inventive concept. Accordingly, all such modifications are intended to be included within the scope of the inventive concept as defined in the claims.
Claims
1. A system, comprising:
- one or more processors; and
- a computer storage medium storing a pharmacy kit template, the one or more processors configured to: receive tag information of a plurality of RFID tags coupled to a plurality of pharmacy item containers located within a pharmacy kit container that includes electromagnetic shielding material based at least in part on an interrogation of the plurality of RFID tags using an antenna, wherein the plurality of pharmacy item containers are configured to store a plurality of pharmacy items, and wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item of the plurality of pharmacy items; verify a pharmacy kit based at least in part on the tag information and the pharmacy kit template, wherein the pharmacy kit template comprises a plurality of segments, each segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating for each segment: one or more different pharmacy items that correspond to the each segment and an expected quantity of the one or more different pharmacy items to satisfy the each segment, wherein to verify the pharmacy kit, the one or more processors are configured to at least one of: determine that an expected quantity for a first segment is satisfied based at least in part on a determination that a first pharmacy item that corresponds to the first segment is not located within the pharmacy kit container and a second pharmacy item that corresponds to the first segment is located within the pharmacy kit container, determine that the expected quantity for a second segment is not satisfied based at least in part on a determination that a first pharmacy item that corresponds to the second segment is not located within the pharmacy kit container and a second pharmacy item that corresponds to the second segment is not located within the pharmacy kit container, determine that an excess pharmacy item is present based at least in part on a determination that an actual quantity of at least one pharmacy item located within the pharmacy kit container exceeds an expected quantity of the at least one pharmacy item, determine that a third pharmacy item located within the pharmacy kit container is subject to a recall, or determine that a fourth pharmacy item located within the pharmacy kit container is a near-expiration pharmacy item based at least in part on an expiration date associated with the fourth pharmacy item; and cause a display to display results of the verification of the pharmacy kit.
2. The system of claim 1, wherein the pharmacy kit container comprises at least one door and the interrogation of the plurality of RFID tags using the antenna occurs when the at least one door is closed.
3. The system of claim 1, wherein the particular RFID tag is associated with particular pharmacy item data comprising at least an identifier of the particular pharmacy item.
4. The system of claim 1, wherein each RFID tag of the plurality of RFID tags is associated with pharmacy item data corresponding to a pharmacy item stored in a pharmacy item container to which the each RFID tag is coupled.
5. The system of claim 1, wherein to verify a pharmacy kit based at least in part on the tag information and the pharmacy kit template, the one or more processors are further configured to compare at least a portion of the tag information with the pharmacy kit template.
6. The system of claim 1, wherein to verify a pharmacy kit based at least in part on the tag information and the pharmacy kit template, the one or more processors are configured to compare at least a portion of pharmacy item data with the pharmacy kit template, wherein the pharmacy item data is associated with the tag information.
7. The system of claim 6, wherein the pharmacy item data is stored in the computer storage medium apart from the plurality of RFID tags and the tag information is used to access the pharmacy item data.
8. The system of claim 1, wherein to verify the pharmacy kit, the one or more processors are configured to determine that the expected quantity for the first segment is satisfied based at least in part on a determination that the first pharmacy item that corresponds to the first segment is not located within the pharmacy kit container and the second pharmacy item that corresponds to the first segment is located within the pharmacy kit container.
9. The system of claim 1, wherein to verify the pharmacy kit, the one or more processors are configured to determine that the expected quantity for the second segment is not satisfied based at least in part on a determination that the first pharmacy item that corresponds to the second segment is not located within the pharmacy kit container and the second pharmacy item that corresponds to the second segment is not located within the pharmacy kit container.
10. The system of claim 1, wherein to verify the pharmacy kit, the one or more processors are further configured to determine that the third pharmacy item located within the pharmacy kit container is subject to a recall.
11. The system of claim 1, wherein to verify the pharmacy kit, the one or more processors are configured to determine that the fourth pharmacy item located within the pharmacy kit container is the near-expiration pharmacy item.
12. The system of claim 11, wherein to determine that the fourth pharmacy item located within the pharmacy kit container is the near-expiration pharmacy item, the one or more processors are configured to determine that the expiration date precedes a particular date.
13. A system, comprising:
- one or more processors; and
- a computer storage medium, the one or more processors configured to: receive tag information of a plurality of RFID tags coupled to a plurality of pharmacy item containers within a pharmacy kit container that includes electromagnetic shielding material based at least in part on an interrogation of the plurality of RFID tags using an antenna, wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item, and verify a pharmacy kit based at least in part on the tag information, wherein to verify the pharmacy kit, the one or more processors are configured to at least one of: determine that a first pharmacy item container configured to store a first pharmacy item is not present and determine that a second pharmacy item container configured to store a potential substitute pharmacy item is present, determine that a second pharmacy item is subject to a recall, or identify the second pharmacy item as a near-expiration pharmacy item based at least in part on an expiration date associated with the second pharmacy item; and cause a display to display results of the verification of the pharmacy kit.
14. The system of claim 13, wherein the pharmacy kit container comprises at least one door, and the plurality of RFID tags are interrogated using the antenna when the at least one door is closed.
15. The system of claim 13, wherein to verify a pharmacy kit based at least in part on the tag information, the one or more processors are configured to compare at least a portion of the tag information with a pharmacy kit template.
16. The system of claim 13, wherein to verify a pharmacy kit based at least in part on the tag information, the one or more processors are configured to compare at least a portion of pharmacy item data with a pharmacy kit template, wherein the pharmacy item data is associated with the tag information.
17. The system of claim 16, wherein the pharmacy item data is stored in the computer storage medium apart from the plurality of RFID tags and the tag information is used to access the pharmacy item data.
18. The system of claim 13, wherein to verify the pharmacy kit, the one or more processors are further configured to determine that the first pharmacy item container configured to store the first pharmacy item is not located within the pharmacy kit container, and determine that the second pharmacy item container configured to store the potential substitute pharmacy item is located within the pharmacy kit container.
19. The system of claim 13, wherein to verify the pharmacy kit, the one or more processors are further configured to determine that the second pharmacy item is subject to a recall.
20. The system of claim 13, wherein to verify the pharmacy kit, the one or more processors are configured to identify the second pharmacy item as the near-expiration pharmacy item based at least in part on a comparison of the expiration date with a particular date.
21. The system of claim 20, wherein to identify the second pharmacy item as the near-expiration pharmacy item, the one or more processors are configured to determine that the second pharmacy item is expired or will expire by the particular date.
22. A non-transitory, computer storage medium storing computer-executable instructions that when executed by one or more processors, cause the one or more processors to at least:
- receive tag information of a plurality of RFID tags coupled to a plurality of pharmacy item containers within a pharmacy kit container that includes electromagnetic shielding material based at least in part on an interrogation of the plurality of RFID tags using an antenna, wherein the plurality of pharmacy item containers are configured to store a plurality of pharmacy items, wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item of the plurality of pharmacy items, and
- verify a pharmacy kit based at least in part on the tag information, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to at least one of: determine that a potential substitute pharmacy item for a first pharmacy item is located within the pharmacy kit container, determine that a second pharmacy item is subject to a recall, or identify a third pharmacy item as a near-expiration pharmacy item based at least in part on an expiration date associated with the third pharmacy item; and
- cause a display to display results of the verification of the pharmacy kit.
23. The non-transitory, computer-readable medium of claim 22, wherein the pharmacy kit container comprises at least one door, and the plurality of RFID tags are interrogated using the antenna when the at least one door is closed.
24. The non-transitory, computer-readable medium of claim 22, wherein to verify a pharmacy kit based at least in part on the tag information, the computer-executable instructions when executed cause the one or more processors to compare at least a portion of the tag information with a pharmacy kit template.
25. The non-transitory, computer-readable medium of claim 22, wherein to verify a pharmacy kit based at least in part on the tag information, the computer-executable instructions when executed cause the one or more processors to compare at least a portion of pharmacy item data with a pharmacy kit template, wherein the pharmacy item data is associated with the tag information.
26. The non-transitory, computer-readable medium of claim 25, wherein the pharmacy item data is stored in a non-transitory computer-readable medium apart from the plurality of RFID tags and the tag information is used to access the pharmacy item data.
27. The non-transitory, computer-readable medium of claim 22, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to determine that the potential substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container.
28. The non-transitory, computer-readable medium of claim 22, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to determine that the second pharmacy item is subject to a recall.
29. The non-transitory, computer-readable medium of claim 22, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to identify the third pharmacy item as the near-expiration pharmacy item based at least in part on a determination that the third pharmacy item is expired or will expire by a particular date.
30. The non-transitory, computer-readable medium of claim 29, wherein to determine that the third pharmacy item is expired or will expire by a particular date, the computer-executable instructions when executed cause the one or more processors to compare the expiration date associated with the third pharmacy item with the particular date.
31. A method for managing a pharmacy kit, comprising:
- receiving tag information of a plurality of radio frequency identification (RFID) tags coupled to a plurality of pharmacy item containers within a pharmacy kit container that includes electromagnetic shielding material based at least in part on an interrogation of the plurality of RFID tags using an antenna, wherein the plurality of pharmacy item containers are configured to store a plurality of pharmacy items, wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item of the plurality of pharmacy items, and wherein the particular RFID tag is associated with particular pharmacy item data comprising at least an identifier of the particular pharmacy item;
- verifying a pharmacy kit based at least in part on the tag information, wherein verifying the pharmacy kit comprises at least one of: determining that a pharmacy item container configured to store a potential substitute pharmacy item for a first pharmacy item is present, determining that a second pharmacy item is subject to a recall, or identifying a third pharmacy item as a near-expiration pharmacy item based at least in part on an expiration date associated with the third pharmacy item; and causing a display to display results of the verifying the pharmacy kit.
32. The method of claim 31, wherein the pharmacy kit container comprises at least one door and the plurality of RFID tags are interrogated using the antenna when the at least one door is closed.
33. The method of claim 31, wherein said verifying a pharmacy kit based at least in part on the tag information, comprises comparing at least a portion of the tag information with a pharmacy kit template.
34. The method of claim 31, wherein said verifying a pharmacy kit based at least in part on the tag information, comprises comparing at least a portion of pharmacy item data with a pharmacy kit template, wherein the pharmacy item data is associated with the tag information.
35. The method of claim 34, wherein the pharmacy item data is stored in a non-transitory computer-readable medium apart from the plurality of RFID tags and the tag information is used to access the pharmacy item data.
36. The method of claim 31, wherein said verifying the pharmacy kit, comprises determining that the pharmacy item container configured to store the potential substitute pharmacy item is located within the pharmacy kit container.
37. The method of claim 31, wherein said verifying the pharmacy kit, comprises determining that the second pharmacy item is subject to a recall.
38. The method of claim 31, wherein said verifying the pharmacy kit, comprises identifying the third pharmacy item as the near-expiration pharmacy item based at least in part on a comparison of the expiration date with a particular date.
39. The method of claim 38, wherein said identifying the third pharmacy item as the near-expiration pharmacy item comprises determining that the third pharmacy item is expired or will expire by the particular date based at least in part on the comparison of the expiration date with the particular date.
40. A system for managing a pharmacy kit, comprising:
- a pharmacy kit container that includes electromagnetic shielding material; and
- a non-transitory, computer-readable medium storing computer-executable instructions that when executed by one or more processors, cause the one or more processors to at least: receive tag information of a plurality of radio frequency identification (RFID) tags coupled to a plurality of pharmacy item containers within the pharmacy kit container based at least in part on an interrogation of the plurality of RFID tags using an antenna, wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item, and verify a pharmacy kit based at least in part on the tag information, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to at least one of: determine that a potential substitute pharmacy item for a first pharmacy item is located within the pharmacy kit container, determine that a second pharmacy item is subject to a recall, or identify a third pharmacy item as a near-expiration pharmacy item based at least in part on an expiration date associated with the third pharmacy item; and cause a display to display results of the verification of the pharmacy kit.
41. The system of claim 40, wherein the pharmacy kit container comprises at least one door and the plurality of RFID tags are interrogated using the antenna when the at least one door is closed.
42. The system of claim 40, wherein to verify a pharmacy kit based at least in part on the tag information, the computer-executable instructions when executed cause the one or more processors to compare at least a portion of the tag information with a pharmacy kit template.
43. The system of claim 40, wherein to verify a pharmacy kit based at least in part on the tag information, the computer-executable instructions when executed cause the one or more processors to compare at least a portion of pharmacy item data with a pharmacy kit template, wherein the pharmacy item data is associated with the tag information.
44. The system of claim 43, wherein the pharmacy item data is stored in a non-transitory computer-readable medium apart from the plurality of RFID tags and the tag information is used to access the pharmacy item data.
45. The system of claim 40, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to determine that the potential substitute pharmacy item is located within the pharmacy kit container.
46. The system of claim 40, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to determine that the second pharmacy item is subject to a recall.
47. The system of claim 40, wherein to verify the pharmacy kit, the computer-executable instructions when executed cause the one or more processors to identify the third pharmacy item as the near-expiration pharmacy item based at least in part on a comparison of the expiration date with a particular date.
48. The system of claim 47, wherein to identify the third pharmacy item as the near-expiration pharmacy item, the computer-executable instructions when executed cause the one or more processors to determine that the third pharmacy item is expired or will expire by the particular date based at least in part on the comparison of the expiration date with the particular date.
49. A system for managing a pharmacy kit, the system comprising:
- a pharmacy kit container that includes electromagnetic shielding material;
- a radio frequency identification (RFID) reading station comprising an RFID reader and an antenna, the RFID reading station configured to: control the antenna to interrogate a plurality of RFID tags located within the pharmacy kit container, the plurality of RFID tags coupled to a plurality of pharmacy item containers located within the pharmacy kit container, wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item, and receive tag information associated with the plurality of RFID tags based at least in part on the interrogation of the plurality of RFID tags; and an information processing system, configured to: verify a pharmacy kit based at least in part on the tag information, wherein to verify the pharmacy kit, the information processing system is configured to at least one of: determine that a substitute pharmacy item for a first pharmacy item is located within the pharmacy kit container, determine that an excess pharmacy item is located within the pharmacy kit container, determine that an expected pharmacy item is not present in the pharmacy kit container, determine that a second pharmacy item is subject to a recall, or identify the second pharmacy item as a near-expiration pharmacy item based at least in part on an expiration date associated with the second pharmacy item; and cause a display to display results of the verification of the pharmacy kit.
50. The system of claim 49, wherein the RFID reading station comprises the information processing system.
51. The system of claim 49, wherein the information processing system is remotely located from the RFID reading station.
52. The system of claim 49, wherein the pharmacy kit container further comprises a door and the RFID reading station is configured to control the antenna to interrogate a plurality of RFID tags when the door is closed.
53. The system of claim 49, wherein the particular RFID tag comprises:
- an identification portion including an RFID device for storing at least a portion of the tag information, and
- a tail portion formed of a transparent material and including an adhesive backing for affixing the particular RFID tag to the particular pharmacy item container, wherein the transparent material enables visualization of label information of the particular pharmacy item container when the tail portion is located on top of the label information.
54. The system of claim 49, wherein:
- the tag information is first tag information,
- the RFID reading station is further configured to receive second tag information associated with an RFID tag associated with the pharmacy kit based at least in part on an interrogation of the RFID tag using the antenna, and
- the information processing system is further configured to: determine a kit type based at least in part on the second tag information, and identify a pharmacy kit template from a plurality of pharmacy kit templates based at least in part on the determined kit type, and verify the pharmacy kit based at least in part on the first tag information and the identified pharmacy kit template.
55. The system of claim 49, wherein to verify the pharmacy kit, the information processing system is configured to determine that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, and wherein the determination that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container is based at least in part on the tag information and a pharmacy kit template.
56. The system of claim 55, wherein the determination that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container is further based at least in part on a comparison of pharmacy item data and the pharmacy kit template, wherein the pharmacy item data is associated with the tag information.
57. The system of claim 55,
- wherein the pharmacy kit template identifies one or more different pharmacy items including the first pharmacy item to be included in the pharmacy kit and one or more potential substitute pharmacy items for the first pharmacy item, and
- wherein to determine that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, the information processing system is configured to determine that at least one of the plurality of pharmacy items located within the pharmacy kit container corresponds to at least one of the one or more potential substitute pharmacy items identified by the pharmacy kit template.
58. The system of claim 55,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating one or more different pharmacy items that correspond to the at least one segment, and
- wherein to determine that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, the information processing system is configured to determine that the first pharmacy item corresponds to the at least one segment and is not located within the pharmacy kit container and a second pharmacy item that is different from the first pharmacy item and that corresponds to the at least one segment is located within the pharmacy kit container.
59. The system of claim 55,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy the at least one segment, and
- wherein to determine that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, the information processing system is configured to determine that the first pharmacy item corresponds to one of the plurality of permissible pharmacy items and that a second pharmacy item located within the pharmacy kit container corresponds to a different one of the plurality of permissible pharmacy items.
60. The system of claim 55,
- wherein the pharmacy kit template comprises a plurality of segments, each of the plurality of segments corresponding to a different class and/or type of pharmacy item, the pharmacy kit template indicating for each segment: a plurality of permissible pharmacy items for that can be used to satisfy the each segment and an expected quantity of the plurality of permissible pharmacy items to satisfy the each segment, and
- wherein to determine that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, the information processing system is configured to determine that the first pharmacy item corresponds to one of the plurality of permissible pharmacy items of a first segment and that a second pharmacy item located within the pharmacy kit container corresponds to a different one of the plurality of permissible pharmacy items of the first segment.
61. The system of claim 49, wherein to verify the pharmacy kit, the information processing system is configured to determine that the excess pharmacy item is located within the pharmacy kit container, wherein the determination that the excess pharmacy item is located within the pharmacy kit container is based at least in part on the tag information and a pharmacy kit template.
62. The system of claim 61,
- wherein the pharmacy kit template identifies one or more different pharmacy items to be included in the pharmacy kit and a quantity of the one or more different pharmacy items to be included in the pharmacy kit, and
- wherein to determine that the excess pharmacy item is located within the pharmacy kit container, the information processing system is configured to compare an expected quantity of at least one pharmacy item identified using the pharmacy kit template with an actual quantity of the at least one pharmacy item identified using pharmacy item data associated with the tag information.
63. The system of claim 61,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy the at least one segment, and an expected quantity of the plurality of permissible pharmacy items to satisfy the segment, and
- wherein to determine that the excess pharmacy item is located within the pharmacy kit container, the information processing system is configured to compare the expected quantity of the plurality of permissible pharmacy items with an actual quantity of the plurality of permissible pharmacy items, the actual quantity being identified using pharmacy item data associated with the tag information.
64. The system of claim 49, wherein to verify the pharmacy kit, the information processing system is configured to determine that the expected pharmacy item is not located within the pharmacy kit container, wherein the determination that the expected pharmacy item is not located within the pharmacy kit container is based at least in part on the tag information and a pharmacy kit template.
65. The system of claim 64,
- wherein the pharmacy kit template identifies one or more different pharmacy items to be included in the pharmacy kit and a quantity of the one or more different pharmacy items to be included in the pharmacy kit, and
- wherein to determine that the expected pharmacy item is not located within the pharmacy kit container, the information processing system is configured to compare an expected quantity of the expected pharmacy item using the pharmacy kit template with an actual quantity of the expected pharmacy item identified using pharmacy item data associated with the tag information.
66. The system of claim 64,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy the at least one segment, and an expected quantity of the plurality of permissible pharmacy items to satisfy the segment, and
- wherein to determine that the expected pharmacy item is not located within the pharmacy kit container, the information processing system is configured to compare the expected quantity of the plurality of permissible pharmacy items with an actual quantity of the plurality of permissible pharmacy items, the actual quantity being identified using pharmacy item data associated with the tag information.
67. The system of claim 49, wherein to verify the pharmacy kit, the information processing system is configured to determine that a second pharmacy item is subject to a recall.
68. The system of claim 49, wherein to verify the pharmacy kit, the information processing system is configured to identify the second pharmacy item as the near-expiration pharmacy item based at least in part on an expiration date associated with the second pharmacy item.
69. A method for managing a pharmacy kit, comprising:
- controlling an antenna to interrogate a plurality of radio frequency identification (RFID) tags located within a pharmacy kit container, the pharmacy kit container including electromagnetic shielding material, the plurality of RFID tags coupled to a plurality of pharmacy item containers located within the pharmacy kit container, wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item;
- receiving tag information associated with the plurality of RFID tags based at least in part on the interrogation of the plurality of RFID tags;
- verifying a pharmacy kit based at least in part on the tag information, wherein said verifying the pharmacy kit comprises at least one of: determining that a substitute pharmacy item for a first pharmacy item is located within the pharmacy kit container, determining that an excess pharmacy item is located within the pharmacy kit container, determining that an expected pharmacy item is not present in the pharmacy kit container, determining that a second pharmacy item is subject to a recall, or identifying the second pharmacy item as a near-expiration pharmacy item based at least in part on an expiration date associated with the second pharmacy item; and causing a display to display results of the verifying the pharmacy kit.
70. The method of claim 69, wherein the particular RFID tag comprises:
- an identification portion including an RFID device for storing at least a portion of the tag information, and
- a tail portion formed of a transparent material and including an adhesive backing for affixing the particular RFID tag to the particular pharmacy item container, wherein the transparent material enables visualization of label information of the particular pharmacy item container when the tail portion is located on top of the label information.
71. The method of claim 69, wherein the tag information is first tag information, the method further comprising:
- receiving second tag information associated with an RFID tag associated with the pharmacy kit based at least in part on an interrogation of the RFID tag using the antenna;
- determining a kit type based at least in part on the second tag information;
- identifying a pharmacy kit template from a plurality of pharmacy kit templates based at least in part on the determined kit type; and
- verifying the pharmacy kit based at least in part on the first tag information and the identified pharmacy kit template.
72. The method of claim 69, said verifying comprises determining that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, and wherein said determining that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container is based at least in part on the tag information and a pharmacy kit template.
73. The method of claim 72,
- wherein the pharmacy kit template identifies one or more different pharmacy items including the first pharmacy item to be included in the pharmacy kit and one or more potential substitute pharmacy items for the first pharmacy item, and
- wherein said determining that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container, comprises determining that at least one of the plurality of pharmacy items located within the pharmacy kit container corresponds to at least one of the one or more potential substitute pharmacy items identified by the pharmacy kit template.
74. The method of claim 72,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating one or more different pharmacy items that correspond to the at least one segment, and
- wherein said determining that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container further comprises determining that the first pharmacy item corresponds to the at least one segment and is not located within the pharmacy kit container and a second pharmacy item that is different from the first pharmacy item and that corresponds to the at least one segment is located within the pharmacy kit container.
75. The method of claim 72,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy the at least one segment, and
- wherein said determining that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container comprises determining that the first pharmacy item corresponds to one of the plurality of permissible pharmacy items and that a second pharmacy item located within the pharmacy kit container corresponds to a different one of the plurality of permissible pharmacy items.
76. The method of claim 72,
- wherein the pharmacy kit template comprises a plurality of segments, each of the plurality of segments corresponding to a different class and/or type of pharmacy item, the pharmacy kit template indicating for each segment: a plurality of permissible pharmacy items for that can be used to satisfy the each segment and an expected quantity of the plurality of permissible pharmacy items to satisfy the each segment, and
- wherein said determining that the substitute pharmacy item for the first pharmacy item is located within the pharmacy kit container comprises determining that the first pharmacy item corresponds to one of the plurality of permissible pharmacy items of a first segment and that a second pharmacy item located within the pharmacy kit container corresponds to a different one of the plurality of permissible pharmacy items of the first segment.
77. The method of claim 69,
- wherein said verifying the pharmacy kit comprises determining that the excess pharmacy item is located within the pharmacy kit container, and wherein said determining that the excess pharmacy item is located within the pharmacy kit container is based at least in part on the tag information and a pharmacy kit template,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy the at least one segment, and an expected quantity of the plurality of permissible pharmacy items to satisfy the segment, and
- wherein said determining that the excess pharmacy item is located within the pharmacy kit container comprises comparing the expected quantity of the plurality of permissible pharmacy items with an actual quantity of the plurality of permissible pharmacy items, the actual quantity being identified using pharmacy item data associated with the tag information.
78. The method of claim 69,
- wherein said verifying the pharmacy kit comprises determining that the expected pharmacy item is not located within the pharmacy kit container, wherein said determining that the expected pharmacy item is not located within the pharmacy kit container is based at least in part on the tag information and a pharmacy kit template,
- wherein the pharmacy kit template comprises at least one segment, the at least one segment corresponding to a particular class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy the at least one segment, and an expected quantity of the plurality of permissible pharmacy items to satisfy the segment, and
- wherein said determining that the expected pharmacy item is not located within the pharmacy kit container comprises comparing the expected quantity of the plurality of permissible pharmacy items with an actual quantity of the plurality of permissible pharmacy items, the actual quantity being identified using pharmacy item data associated with the tag information.
79. A system comprising:
- a pharmacy kit container that includes electromagnetic shielding material;
- a radio frequency identification (RFID) reading station comprising an RFID reader and an antenna, the RFID reading station configured to receive tag information associated with a plurality of RFID tags coupled to a plurality of pharmacy item containers located within the pharmacy kit container based at least in part on an interrogation of the plurality of RFID tags using an antenna,
- wherein the plurality of pharmacy item containers are configured to store a plurality of pharmacy items, and wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item of the plurality of pharmacy items; and
- an information processing system configured to verify a pharmacy kit based at least in part on the tag information and a pharmacy kit template, the pharmacy kit template comprising a plurality of segments, each of the plurality of segments corresponding to a different class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy each of the plurality of segments and an expected quantity of the plurality of permissible pharmacy items to satisfy each of the plurality of segments,
- wherein to verify the pharmacy kit, the information processing system is configured to determine that the expected quantity of the permissible items of a first segment is satisfied based at least in part on a determination that a first permissible pharmacy item of the permissible pharmacy items of the first segment is present and that a second permissible pharmacy item of the permissible pharmacy items of the first segment that is different from the first permissible pharmacy item is present; and
- cause a display to display results of the verification of the pharmacy kit.
80. The system of claim 79, wherein:
- the tag information is first tag information,
- the RFID reading station is further configured to receive second tag information associated with an RFID tag associated with the pharmacy kit based at least in part on an interrogation of the RFID tag using the antenna, and
- the information processing system is further configured to: determine a kit type based at least in part on the second tag information, and identify a pharmacy kit template from a plurality of pharmacy kit templates based at least in part on the determined kit type, wherein the pharmacy kit is verified based at least in part on the first tag information and the identified pharmacy kit template.
81. The system of claim 79, wherein the RFID reading station comprises the information processing system.
82. The system of claim 79, wherein the information processing system is remotely located from the RFID reading station.
83. The system of claim 79, wherein the pharmacy kit container further includes a door and the interrogation of the plurality of RFID tags occurs when the door is closed.
84. The system of claim 79, wherein to verify the pharmacy kit, the information processing system is further configured to:
- compare the expected quantity of the plurality of permissible pharmacy items of a first segment with an actual quantity of the plurality of permissible pharmacy items of the first segment, the actual quantity being identified using pharmacy item data associated with the tag information, and
- determine that an excess pharmacy item is located within the pharmacy kit container based at least in part on the comparison.
85. The system of claim 79, wherein to verify the pharmacy kit, the information processing system is further configured to:
- compare the expected quantity of the plurality of permissible pharmacy items of a first segment with an actual quantity of the plurality of permissible pharmacy items of the first segment, the actual quantity being identified using pharmacy item data associated with the tag information, and
- determine that an expected pharmacy item is not located within the pharmacy kit container based at least in part on the comparison.
86. A system, comprising:
- one or more processors; and
- a computer storage medium storing a pharmacy kit template, the system configured to: receive tag information associated with a plurality of RFID tags coupled to a plurality of pharmacy item containers located within a pharmacy kit container that includes electromagnetic shielding material based at least in part on an interrogation of the plurality of RFID tags using an antenna, wherein the plurality of pharmacy item containers are configured to store a plurality of pharmacy items, and wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item of the plurality of pharmacy items; verify a pharmacy kit based at least in part on the tag information and the pharmacy kit template, wherein the pharmacy kit template comprises a plurality of segments, each of the plurality of segments corresponding to a different class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy each of the plurality of segments and an expected quantity of the plurality of permissible pharmacy items to satisfy each of the plurality of segments, wherein to verify the pharmacy kit, the one or more processors are configured to determine that the expected quantity of the permissible items of a first segment is satisfied based at least in part on a determination that a first permissible pharmacy item of the permissible pharmacy items of the first segment is present and that a second permissible pharmacy item of the permissible pharmacy items of the first segment that is different from the first permissible pharmacy item is present; and cause a display to display results of the verification of the pharmacy kit.
87. The system of claim 86, wherein to verify the pharmacy kit, the system is further configured to determine that an excess pharmacy item is located within the pharmacy kit container based at least in part on a comparison of the expected quantity of the plurality of permissible pharmacy items of a first segment with an actual quantity of the plurality of permissible pharmacy items of the first segment, the actual quantity being identified using pharmacy item data associated with the tag information.
88. The system of claim 86, wherein to verify the pharmacy kit, the system is further configured to determine that an expected pharmacy item is not located within the pharmacy kit container based at least in part on a comparison of the expected quantity of the plurality of permissible pharmacy items of a first segment with an actual quantity of the plurality of permissible pharmacy items of the first segment, the actual quantity being identified using pharmacy item data associated with the tag information.
89. A method, comprising:
- receiving tag information associated with a plurality of RFID tags coupled to a plurality of pharmacy item containers located within a pharmacy kit container that includes electromagnetic shielding material based at least in part on an interrogation of the plurality of RFID tags using an antenna,
- wherein the plurality of pharmacy item containers are configured to store a plurality of pharmacy items, and wherein a particular RFID tag of the plurality of RFID tags is coupled to a particular pharmacy item container of the plurality of pharmacy item containers and the particular pharmacy item container is configured to store a particular pharmacy item of the plurality of pharmacy items;
- verifying a pharmacy kit based at least in part on the tag information and a pharmacy kit template, wherein the pharmacy kit template comprises a plurality of segments, each of the plurality of segments corresponding to a different class and/or type of pharmacy item, the pharmacy kit template indicating a plurality of permissible pharmacy items that can be used to satisfy each of the plurality of segments and an expected quantity of the plurality of permissible pharmacy items to satisfy each of the plurality of segments,
- wherein said verifying comprises determining that the expected quantity of the permissible items of a first segment is satisfied based at least in part on a determination that a first permissible pharmacy item of the permissible pharmacy items of the first segment is present and that a second permissible pharmacy item of the permissible pharmacy items of the first segment that is different from the first permissible pharmacy item is present; and
- causing a display to display results of said verifying.
90. The method of claim 89, wherein the tag information is first tag information, the method further comprising:
- receiving second tag information associated with an RFID tag associated with the pharmacy kit based at least in part on an interrogation of the RFID tag using the antenna;
- determining a kit type based at least in part on the second tag information; and
- identifying the pharmacy kit template from a plurality of pharmacy kit templates based at least in part on the determined kit type, wherein the pharmacy kit is verified based at least in part on the first tag information and the identified pharmacy kit template.
4884827 | December 5, 1989 | Kelley |
5713485 | February 3, 1998 | Liff et al. |
5930145 | July 27, 1999 | Yuyama et al. |
5963134 | October 5, 1999 | Bowers et al. |
5986662 | November 16, 1999 | Argiro et al. |
6112502 | September 5, 2000 | Frederick et al. |
6249299 | June 19, 2001 | Tainer |
6275157 | August 14, 2001 | Mays et al. |
6294999 | September 25, 2001 | Yarin et al. |
6330351 | December 11, 2001 | Yasunaga |
6574166 | June 3, 2003 | Niemiec |
6632619 | October 14, 2003 | Harrison et al. |
6771369 | August 3, 2004 | Rzasa et al. |
6825864 | November 30, 2004 | Botten et al. |
6847861 | January 25, 2005 | Lunak et al. |
6851615 | February 8, 2005 | Jones |
6861954 | March 1, 2005 | Levin |
6877658 | April 12, 2005 | Raistrick et al. |
6879876 | April 12, 2005 | O'Dougherty et al. |
6900021 | May 31, 2005 | Harrison et al. |
6933849 | August 23, 2005 | Sawyer |
6935560 | August 30, 2005 | Andreasson et al. |
6952681 | October 4, 2005 | McQuade et al. |
6985870 | January 10, 2006 | Martucci et al. |
6994249 | February 7, 2006 | Peterka et al. |
7061831 | June 13, 2006 | De La Huerga |
7111780 | September 26, 2006 | Broussard et al. |
7116343 | October 3, 2006 | Botten et al. |
7118029 | October 10, 2006 | Nycz et al. |
7140542 | November 28, 2006 | Andreasson et al. |
7146247 | December 5, 2006 | Kirsch et al. |
7151456 | December 19, 2006 | Godfrey |
7158030 | January 2, 2007 | Chung |
7165077 | January 16, 2007 | Kalies |
7175081 | February 13, 2007 | Andreasson et al. |
7177721 | February 13, 2007 | Kirsch et al. |
7178729 | February 20, 2007 | Shaffer et al. |
7182256 | February 27, 2007 | Andreasson et al. |
7212100 | May 1, 2007 | Terenna |
7227469 | June 5, 2007 | Varner et al. |
7232066 | June 19, 2007 | Andreasson et al. |
7253736 | August 7, 2007 | Tethrake et al. |
7256699 | August 14, 2007 | Tethrake et al. |
7263501 | August 28, 2007 | Tirinato et al. |
7264323 | September 4, 2007 | Tainer et al. |
7268684 | September 11, 2007 | Tethrake et al. |
7275645 | October 2, 2007 | Mallett et al. |
7299981 | November 27, 2007 | Hickle et al. |
7316231 | January 8, 2008 | Hickle |
7317393 | January 8, 2008 | Maloney |
7318529 | January 15, 2008 | Mallett et al. |
7341147 | March 11, 2008 | Mallett et al. |
7348884 | March 25, 2008 | Higham |
7354884 | April 8, 2008 | Hada et al. |
7362228 | April 22, 2008 | Nycz et al. |
7375737 | May 20, 2008 | Botten et al. |
7394383 | July 1, 2008 | Hager et al. |
7440818 | October 21, 2008 | Handfield et al. |
7446747 | November 4, 2008 | Youngblood et al. |
7454880 | November 25, 2008 | Austin et al. |
7486188 | February 3, 2009 | Van Alstyne |
7492257 | February 17, 2009 | Tethrake et al. |
7492261 | February 17, 2009 | Cambre et al. |
7504954 | March 17, 2009 | Spaeder |
7518502 | April 14, 2009 | Austin et al. |
7551089 | June 23, 2009 | Sawyer |
7559483 | July 14, 2009 | Hickle et al. |
7564364 | July 21, 2009 | Zweig |
7630791 | December 8, 2009 | Nguyen et al. |
7639136 | December 29, 2009 | Wass et al. |
7644016 | January 5, 2010 | Nycz et al. |
7672872 | March 2, 2010 | Shanton |
7706915 | April 27, 2010 | Mohapatra et al. |
7706916 | April 27, 2010 | Hilton |
7712670 | May 11, 2010 | Sauerwein, Jr. et al. |
7715277 | May 11, 2010 | De La Huerga |
7729597 | June 1, 2010 | Wright et al. |
7734157 | June 8, 2010 | Wright et al. |
7747477 | June 29, 2010 | Louie et al. |
7752085 | July 6, 2010 | Monroe |
7772964 | August 10, 2010 | Tethrake et al. |
7775056 | August 17, 2010 | Lowenstein |
7783163 | August 24, 2010 | Wright et al. |
7783174 | August 24, 2010 | Wright et al. |
7801422 | September 21, 2010 | Wright et al. |
7815117 | October 19, 2010 | Tuschel et al. |
7834765 | November 16, 2010 | Sawyer |
7834766 | November 16, 2010 | Sawyer |
7837093 | November 23, 2010 | Leu et al. |
7837107 | November 23, 2010 | Leu et al. |
7858841 | December 28, 2010 | Krautkramer et al. |
7860730 | December 28, 2010 | Goodall et al. |
7868754 | January 11, 2011 | Salvat, Jr. |
7893876 | February 22, 2011 | Brown et al. |
7908030 | March 15, 2011 | Handfield et al. |
7918830 | April 5, 2011 | Langan et al. |
7933033 | April 26, 2011 | Ohishi et al. |
7976508 | July 12, 2011 | Hoag |
7985711 | July 26, 2011 | Tohmatsu et al. |
7990272 | August 2, 2011 | Wass et al. |
7996286 | August 9, 2011 | Kreiner et al. |
8002174 | August 23, 2011 | Coyne, III et al. |
8006903 | August 30, 2011 | Braun et al. |
8009913 | August 30, 2011 | Greyshock |
8031347 | October 4, 2011 | Edwards et al. |
8042738 | October 25, 2011 | Cloix |
8049627 | November 1, 2011 | Addante |
8063925 | November 22, 2011 | Tainer et al. |
8065858 | November 29, 2011 | Leu et al. |
8072635 | December 6, 2011 | Roberts et al. |
8077041 | December 13, 2011 | Stern et al. |
8082192 | December 20, 2011 | Nycz et al. |
8099339 | January 17, 2012 | Pinsonneault et al. |
8108068 | January 31, 2012 | Boucher et al. |
8111159 | February 7, 2012 | Andreasson et al. |
8112175 | February 7, 2012 | Handfield et al. |
8131397 | March 6, 2012 | Vahlberg et al. |
8154390 | April 10, 2012 | Heath et al. |
8174392 | May 8, 2012 | Saghbini et al. |
8186587 | May 29, 2012 | Zmood et al. |
8212677 | July 3, 2012 | Ferguson |
8219413 | July 10, 2012 | Martinez et al. |
8224483 | July 17, 2012 | Ansari et al. |
8231749 | July 31, 2012 | Dent et al. |
8258961 | September 4, 2012 | Phillips et al. |
8261939 | September 11, 2012 | Knoth |
8271128 | September 18, 2012 | Schultz |
8279069 | October 2, 2012 | Sawyer |
8283287 | October 9, 2012 | Aihara et al. |
8284059 | October 9, 2012 | Ross |
8285083 | October 9, 2012 | Canessa et al. |
8285607 | October 9, 2012 | Danilewitz |
8286222 | October 9, 2012 | Silverbrook et al. |
8292173 | October 23, 2012 | Yturralde et al. |
8292186 | October 23, 2012 | Deloche et al. |
8296950 | October 30, 2012 | Colbrunn et al. |
8313024 | November 20, 2012 | Marino |
8319607 | November 27, 2012 | Grimlund et al. |
8328082 | December 11, 2012 | Bochenko et al. |
8339649 | December 25, 2012 | Ohishi et al. |
8341041 | December 25, 2012 | Hull |
8346632 | January 1, 2013 | Saghbini |
8355753 | January 15, 2013 | Bochenko et al. |
8355962 | January 15, 2013 | Delaney et al. |
8359338 | January 22, 2013 | Butterfield et al. |
8371448 | February 12, 2013 | Reaux |
8376228 | February 19, 2013 | DeVet et al. |
8384545 | February 26, 2013 | Hussain et al. |
8385972 | February 26, 2013 | Bochenko et al. |
8386070 | February 26, 2013 | Eliuk et al. |
8394053 | March 12, 2013 | Bochenko et al. |
8403212 | March 26, 2013 | van Esch |
8403224 | March 26, 2013 | Fedorko et al. |
8405508 | March 26, 2013 | Burke |
8438067 | May 7, 2013 | Omura et al. |
8461076 | June 11, 2013 | Okada et al. |
8483550 | July 9, 2013 | Wright et al. |
8509604 | August 13, 2013 | Wright et al. |
8515251 | August 20, 2013 | Wright et al. |
8519849 | August 27, 2013 | Ross-Messemer |
8530379 | September 10, 2013 | Shimizu et al. |
8564416 | October 22, 2013 | Steven et al. |
8565552 | October 22, 2013 | Sommer et al. |
8582171 | November 12, 2013 | Srnka et al. |
8593278 | November 26, 2013 | Churbock et al. |
8593678 | November 26, 2013 | Ohishi et al. |
D694817 | December 3, 2013 | Adam et al. |
8606596 | December 10, 2013 | Bochenko et al. |
8636202 | January 28, 2014 | Keefe et al. |
8639525 | January 28, 2014 | Levine et al. |
8686859 | April 1, 2014 | Hussain et al. |
8699054 | April 15, 2014 | Edwards et al. |
8702674 | April 22, 2014 | Bochenko |
8723674 | May 13, 2014 | Conley et al. |
8749356 | June 10, 2014 | Hussain et al. |
8755056 | June 17, 2014 | Edwards et al. |
8825680 | September 2, 2014 | Burke et al. |
8922435 | December 30, 2014 | Fontecchio et al. |
8945066 | February 3, 2015 | Bochenko et al. |
8985388 | March 24, 2015 | Ratnakar |
8990099 | March 24, 2015 | MacDonald et al. |
9037479 | May 19, 2015 | MacDonald et al. |
9058412 | June 16, 2015 | MacDonald et al. |
9058413 | June 16, 2015 | MacDonald et al. |
9171280 | October 27, 2015 | Gitchell et al. |
9367665 | June 14, 2016 | MacDonald et al. |
9449296 | September 20, 2016 | MacDonald et al. |
9539374 | January 10, 2017 | Halpern |
9582644 | February 28, 2017 | Gitchell et al. |
9734294 | August 15, 2017 | MacDonald et al. |
20020026330 | February 28, 2002 | Klein |
20020049650 | April 25, 2002 | Reff |
20020087360 | July 4, 2002 | Pettit |
20020087362 | July 4, 2002 | Cobb et al. |
20020087554 | July 4, 2002 | Seelinger |
20030055685 | March 20, 2003 | Cobb et al. |
20030074223 | April 17, 2003 | Hickle et al. |
20030102970 | June 5, 2003 | Creel et al. |
20030160698 | August 28, 2003 | Andreasson et al. |
20030216974 | November 20, 2003 | Browne |
20040008123 | January 15, 2004 | Carrender et al. |
20040032330 | February 19, 2004 | Hoffman |
20040051368 | March 18, 2004 | Caputo et al. |
20040057609 | March 25, 2004 | Weinberg |
20040081669 | April 29, 2004 | Greeven et al. |
20040158507 | August 12, 2004 | Meek et al. |
20040178071 | September 16, 2004 | Harrison et al. |
20040215486 | October 28, 2004 | Braverman |
20040225528 | November 11, 2004 | Brock |
20050014849 | January 20, 2005 | Pettit et al. |
20050060171 | March 17, 2005 | Molnar |
20050062603 | March 24, 2005 | Fuerst et al. |
20050108044 | May 19, 2005 | Koster |
20050125097 | June 9, 2005 | Chudy et al. |
20050127176 | June 16, 2005 | Dickinson |
20050149378 | July 7, 2005 | Cyr et al. |
20050149414 | July 7, 2005 | Schrodt et al. |
20050184151 | August 25, 2005 | DiMaggio et al. |
20050283259 | December 22, 2005 | Wolpow |
20050285732 | December 29, 2005 | Sengupta et al. |
20050285746 | December 29, 2005 | Sengupta et al. |
20060006999 | January 12, 2006 | Walczyk et al. |
20060043177 | March 2, 2006 | Nycz et al. |
20060043179 | March 2, 2006 | Nycz et al. |
20060065726 | March 30, 2006 | Andreasson et al. |
20060109105 | May 25, 2006 | Varner et al. |
20060132311 | June 22, 2006 | Kruest et al. |
20060145871 | July 6, 2006 | Donati et al. |
20060152338 | July 13, 2006 | Hsu |
20060152364 | July 13, 2006 | Walton |
20060152367 | July 13, 2006 | Narayanaswamy |
20060208886 | September 21, 2006 | Beamer |
20060267731 | November 30, 2006 | Chen |
20070001809 | January 4, 2007 | Kodukula et al. |
20070008399 | January 11, 2007 | Botten et al. |
20070023512 | February 1, 2007 | Miller et al. |
20070023513 | February 1, 2007 | Andreasson et al. |
20070074722 | April 5, 2007 | Giroux et al. |
20070114279 | May 24, 2007 | Lessing et al. |
20070150382 | June 28, 2007 | Danilewitz |
20070187475 | August 16, 2007 | MacLeod |
20070188306 | August 16, 2007 | Tethrake et al. |
20070200702 | August 30, 2007 | Chung |
20070213659 | September 13, 2007 | Trovato et al. |
20070213684 | September 13, 2007 | Hickle et al. |
20070229268 | October 4, 2007 | Swan et al. |
20070272746 | November 29, 2007 | Ortiz et al. |
20080004908 | January 3, 2008 | Oh et al. |
20080012687 | January 17, 2008 | Rubinstein |
20080045930 | February 21, 2008 | Makin et al. |
20080046295 | February 21, 2008 | Albrecht |
20080094214 | April 24, 2008 | Azevedo et al. |
20080122878 | May 29, 2008 | Keefe et al. |
20080128482 | June 5, 2008 | Chen et al. |
20080129496 | June 5, 2008 | Koblasz |
20080150722 | June 26, 2008 | Jackson |
20080157967 | July 3, 2008 | Jones et al. |
20080172253 | July 17, 2008 | Chung et al. |
20080191013 | August 14, 2008 | Liberatore |
20080218307 | September 11, 2008 | Schoettle |
20080228160 | September 18, 2008 | Harrison |
20080243088 | October 2, 2008 | Evans |
20080270178 | October 30, 2008 | McRae et al. |
20080296373 | December 4, 2008 | Smood et al. |
20080297356 | December 4, 2008 | Oberle |
20080306772 | December 11, 2008 | Shahrokh |
20080316045 | December 25, 2008 | Sriharto et al. |
20090002173 | January 1, 2009 | Bergsten et al. |
20090020442 | January 22, 2009 | Dietrich et al. |
20090058653 | March 5, 2009 | Geissler et al. |
20090144087 | June 4, 2009 | Kelsch et al. |
20090153290 | June 18, 2009 | Bierach |
20090164042 | June 25, 2009 | Handfield et al. |
20090194987 | August 6, 2009 | Christie et al. |
20090231138 | September 17, 2009 | Cheung et al. |
20090267740 | October 29, 2009 | Pizzuto |
20090267772 | October 29, 2009 | Dehnadi |
20090277815 | November 12, 2009 | Kohl |
20090294521 | December 3, 2009 | De La Huerga |
20100022953 | January 28, 2010 | Bochenko et al. |
20100022987 | January 28, 2010 | Bochenko |
20100036310 | February 11, 2010 | Hillman |
20100036678 | February 11, 2010 | Bray |
20100036755 | February 11, 2010 | Saghbini |
20100042439 | February 18, 2010 | Martinez et al. |
20100079337 | April 1, 2010 | Shiau et al. |
20100098425 | April 22, 2010 | Kewitsch |
20100108761 | May 6, 2010 | Nycz et al. |
20100114951 | May 6, 2010 | Bauman et al. |
20100185458 | July 22, 2010 | Calderwood et al. |
20100204659 | August 12, 2010 | Bochenko |
20100217621 | August 26, 2010 | Schoenberg et al. |
20100219097 | September 2, 2010 | Ramasubramanian et al. |
20100238039 | September 23, 2010 | Tethrake et al. |
20100268548 | October 21, 2010 | Garrett et al. |
20100275625 | November 4, 2010 | Lowenstein |
20100299158 | November 25, 2010 | Siegel |
20100328474 | December 30, 2010 | Hsieh |
20100332246 | December 30, 2010 | Fedorko et al. |
20110006879 | January 13, 2011 | Bartos |
20110063091 | March 17, 2011 | Kang |
20110068922 | March 24, 2011 | Ross |
20110112682 | May 12, 2011 | Matsukawa et al. |
20110115612 | May 19, 2011 | Kulinets et al. |
20110125315 | May 26, 2011 | Handfield et al. |
20110131056 | June 2, 2011 | Chudy et al. |
20110139871 | June 16, 2011 | Yturralde et al. |
20110161112 | June 30, 2011 | Keefe et al. |
20110163871 | July 7, 2011 | Einav et al. |
20110166878 | July 7, 2011 | Louie et al. |
20110184751 | July 28, 2011 | Holmes |
20110187549 | August 4, 2011 | Balasing |
20110225100 | September 15, 2011 | Sangal et al. |
20110227722 | September 22, 2011 | Salvat, Jr. |
20110240729 | October 6, 2011 | Schuck |
20110257991 | October 20, 2011 | Shukla |
20110270441 | November 3, 2011 | Handfield et al. |
20110291809 | December 1, 2011 | Niemiec et al. |
20110301446 | December 8, 2011 | Kamen |
20110313395 | December 22, 2011 | Krulevitch et al. |
20120037266 | February 16, 2012 | Bochenko |
20120041778 | February 16, 2012 | Kraft |
20120044054 | February 23, 2012 | Hussain et al. |
20120061463 | March 15, 2012 | Burke |
20120089411 | April 12, 2012 | Srnka et al. |
20120089418 | April 12, 2012 | Kamath et al. |
20120116798 | May 10, 2012 | Heath et al. |
20120125994 | May 24, 2012 | Heath et al. |
20120130534 | May 24, 2012 | Wurm |
20120173440 | July 5, 2012 | Becker et al. |
20120177256 | July 12, 2012 | Keefe et al. |
20120179132 | July 12, 2012 | Valk et al. |
20120185951 | July 19, 2012 | Bauman et al. |
20120209619 | August 16, 2012 | Knotts et al. |
20120240067 | September 20, 2012 | Bauman et al. |
20120273087 | November 1, 2012 | Einy et al. |
20120278096 | November 1, 2012 | Holness |
20120278228 | November 1, 2012 | Rubinstein |
20120323208 | December 20, 2012 | Bochenko et al. |
20120325330 | December 27, 2012 | Prince et al. |
20130018356 | January 17, 2013 | Prince et al. |
20130038452 | February 14, 2013 | Sawyer |
20130041784 | February 14, 2013 | Danilewitz |
20130092727 | April 18, 2013 | Edwards et al. |
20130105568 | May 2, 2013 | Jablonski et al. |
20130151005 | June 13, 2013 | Gerold et al. |
20130191149 | July 25, 2013 | Kolberg et al. |
20130221082 | August 29, 2013 | Botten |
20130221087 | August 29, 2013 | Keefe et al. |
20130225945 | August 29, 2013 | Prince et al. |
20130327822 | December 12, 2013 | Keefe et al. |
20140060729 | March 6, 2014 | Srnka et al. |
20140066880 | March 6, 2014 | Prince et al. |
20140117081 | May 1, 2014 | Jablonski et al. |
20140136229 | May 15, 2014 | Levine et al. |
20140142975 | May 22, 2014 | Keefe et al. |
20140184390 | July 3, 2014 | Elizondo, II |
20140184391 | July 3, 2014 | Elizondo, II |
20140197954 | July 17, 2014 | Caputo et al. |
20140210596 | July 31, 2014 | Hussain et al. |
20140262919 | September 18, 2014 | Hussain et al. |
20140263614 | September 18, 2014 | Keefe et al. |
20140276213 | September 18, 2014 | Bochenko |
20140282197 | September 18, 2014 | Keefe et al. |
20140291397 | October 2, 2014 | Caputo et al. |
20140367080 | December 18, 2014 | Hussain et al. |
20140372145 | December 18, 2014 | MacDonald et al. |
20150058182 | February 26, 2015 | Kress-Spatz et al. |
20170132734 | May 11, 2017 | MacDonald et al. |
20170212993 | July 27, 2017 | Gitchell et al. |
2 722 328 | October 2009 | CA |
2 790 220 | June 2013 | CA |
102791310 | December 2014 | CN |
2012/04914 | October 2013 | IN |
WO 02/095675 | November 2002 | WO |
WO 2006/026246 | March 2006 | WO |
WO 2006/135830 | December 2006 | WO |
WO 2010/074781 | July 2010 | WO |
WO 2011/115676 | September 2011 | WO |
WO 2011/150013 | December 2011 | WO |
WO 2013/082423 | June 2013 | WO |
WO 2013/116873 | August 2013 | WO |
WO 2013/134256 | September 2013 | WO |
WO 2014/159928 | October 2014 | WO |
WO 2014/189834 | November 2014 | WO |
- U.S. Appl. No. 14/603,730, filed Jan. 23, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- U.S. Appl. No. 14/603,828, filed Jan. 23, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- U.S. Appl. No. 14/603,962, filed Jan. 23, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- U.S. Appl. No. 14/563,732, filed Dec. 8, 2014, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, Gitchell et al.
- U.S. Appl. No. 14/126,419, filed Dec. 14, 2013, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, Kress-Spatz et al.
- U.S. Appl. No. 14/469,524, filed Aug. 26, 2014, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- U.S. Appl. No. 14/472,410, filed Aug. 29, 2014, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- Barlas, Stephen, “Pharmacy Product Tracing Likely to Go National—Costs to Pharmacies Worrisome,” Pharmacy & Therapeutics, Jan. 2009, vol. 34 No. 1, p. 14.
- 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.
- akici et al., “Using RFID for the management of pharmaceutical inventory-system optimization and shrinkage control,” Decision Support Systems, 2011, pp. 842-852.
- CPG Sec. 400.210, Radiofrequency Identification Feasibility Studies and Pilot Programs for Drugs Nov. 2004 Compliance Policy Guide available at: http://www.fda.gov/ICECI/ComplianceManuals/CompliancePolicyGuidanceManual/ucm074357.htm.
- Crash Cart Inventory Checklist, Outpatient Surgery Magazine, Oct. 2004, “Outpatient Surgery”, available at: http://www.outpatientsurgery.net/resources/forms/2004/pdf/OutpatientSurgeryMagazine—0410—crashCart.pdf, in 1 page.
- 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.
- Gonzalez, Stephanie, “Health Maintenance System (HMS) Hardware Research, Design, and Collaboration,” NASA USRP—Internship Final Report, 2010, pp. 1-20.
- Harrop et al., “RFID for Healthcare and Pharmaceuticals, 2008-2018,” Securing Pharma, May 2008, pp. 1-12.
- 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 httpp://citrenz.ac.nz/bacit/0301/2005Houliston—RFID.htm.
- Jorgensen et al., “Executable Use Cases: Requirements for a Pervasive Health Care System,” IEEE Software, Mar./Apr. 2004, pp. 34-41.
- Lai et al., “Enhancing Medication Safety and Reduce Adverse Drug Events on Inpatient Medication Administration using RFID,” WSEAS Transactions on Communications, Oct. 2008, vol. 7, No. 10, pp. 1045-1054.
- Lampe et al., “The Smart Box Application Model,” Advances in Pervasive Computing, 2004, pp. 1-6.
- “McKesson's Announces New Touch-Screen Driven Medication Dispensing Solution”, Business Wire, Jun. 15, 2009, pp. 2, Available at: http://www.businesswire.com/news/home/20090615005349/en/McKesson-Announces-Touch-Screen-Driven-Medication-Dispensing-Solution#.VR7quPnF—10.
- “Medical Packaging Inc. Announces Clear Stem Flag Label System for Ampoules, Vials, and Syringes” Feb. 1, 2006 available at: http://www.medpak.com/v1/news/20060201—CSFLAG.pdf, in 1 page.
- 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.
- 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.
- 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.
- 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.
- U.S. Appl. No. 14/818,101, filed Aug. 4, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- U.S. Appl. No. 14/818,113, filed Aug. 4, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, MacDonald et al.
- U.S. Appl. No. 14/876,533, filed Oct. 6, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, Gitchell et al.
- Liu et al., “Point-of-Care Support for Error-Free Medication Process” (Jun. 25, 2007), retrieved Aug. 21, 2017, 12 pages, available at http://ieeexplore.ieee.org/document/4438162/.
- McCall et al., “RMAIS: RFID-based Medication Adherence Intelligence System” (Aug. 31, 2010), retrieved Aug. 21, 2017, 4 pages, available at http://ieeexplore.ieee.org/document/5627529/.
- Tsai et al., “iMAT: Intelligent Medication Administration Tools” (Jul. 1, 2010), retrieved Aug. 21, 2017, 8 pages available at http://ieeexplore.ieee.org/document/5556551/.
- Tsai et al., “Smart Medication Dispenser: Design, Architecture and Implementation” (Sep. 27, 2010), retrieved Aug. 21, 2017, 12 pages, available at http://ieeexplore.ieee.org/document/5585838/.
- O'Connor, “Johnson & Johnson Finds Value in Multiple RFID Apps” (Apr. 23, 2008), retrieved Aug. 21, 2017, 2 pages, available at http://www.rfidjournal.com/articles/pdf?4046.
- Collins, “RFID Cabinet Manages Medicine” (Aug. 12, 2004), retrieved Aug. 21, 2017, 1 page, available at http://www.rfidjournal.com/articles/pdf?1081.
- 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.
Type: Grant
Filed: May 1, 2015
Date of Patent: Oct 31, 2017
Patent Publication Number: 20150235005
Assignee: Kit Check, Inc. (Washington, DC)
Inventors: Kevin William MacDonald (Washington, DC), Timothy James Leo Kress-Spatz (Washington, DC)
Primary Examiner: Eliza Lam
Application Number: 14/701,958
International Classification: G06Q 50/22 (20120101); G06Q 50/24 (20120101); G06F 19/00 (20110101);