US 8,990,099 B2Grant
Management of pharmacy kits
Issue Date:2015-03-24
•20 Claims
•23 Drawing Sheets
Abstract
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.
Metadata
Assignee
- Kit Check, Inc.
Inventors
- Kevin William MacDonald
- Timothy James Leo Kress-Spatz
Application Information
Application Number:US 13/554,342
Filing Date:2012-07-20
Priority Date:2011-08-02
Art Unit:3626
Classifications
IPC:
G06Q50/22G06Q50/24G06Q10/08G06F19/00
Field of Search:
G06Q 50/22G06Q 50/24
Patent Drawings (23 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims priority under 35 U.S.C. §119 to U.S. Provisional Application No. 61/514,231 filed on Aug. 2, 2011, the subject matter of which is hereby incorporated by reference.
Background
[0002] Hospital 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.
[0003] 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.
[0004] 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.
[0005] 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.
[0006] 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.
[0007] Due to the above and other shortcomings, there is a general need for improved techniques and technologies for managing pharmacy kits.
Summary
[0008] According 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.
[0009] 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.
[0010] 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.
Brief Description of the Drawings
[0011] The drawings illustrate selected embodiments of the inventive concept. In the drawings, like reference numbers indicate like features.
[0012] FIG. 1 is a block diagram of a system for managing pharmacy kits according to an embodiment of the inventive concept.
[0013] FIGS. 2A through 2C are diagrams illustrating a pharmacy kit according to an embodiment of the inventive concept.
[0014] FIGS. 3A and 3B are diagrams of a read station in the system of FIG. 1 according to an embodiment of the inventive concept.
[0015] FIG. 4 is a diagram of an information processing system in the system of FIG. 1 according to an embodiment of the inventive concept.
[0016] FIG. 5 is a flowchart illustrating a method of managing pharmacy kits according to an embodiment of the inventive concept.
[0017] FIG. 6 is a flowchart illustrating a method of receiving and processing items for a pharmacy kit according to an embodiment of the inventive concept.
[0018] FIG. 7 is a flowchart illustrating a method of building a pharmacy kit according to an embodiment of the inventive concept.
[0019] FIGS. 8A and 8B are flowcharts illustrating methods of operating the system of FIG. 1 according to an embodiment of the inventive concept.
[0020] FIG. 9 shows an interface that can be used to control the system of FIG. 1 according to an embodiment of the inventive concept.
[0021] FIG. 10 shows a report generated for a pharmacy kit using the system of FIG. 1 according to an embodiment of the inventive concept.
[0022] FIG. 11 shows another report generated for a pharmacy kit using the system of FIG. 1 according to an embodiment of the inventive concept.
[0023] FIG. 12 shows an interface for checking out a kit to a user or location according to an embodiment of the inventive concept.
[0024] FIGS. 13A and 13B show interfaces used to generate and view reports regarding pharmacy kits according to an embodiment of the inventive concept.
[0025] FIGS. 14A through 14D are diagrams of a label that can be used to attach an RFID tag to various items of a pharmacy kit according to an embodiment of the inventive concept.
Detailed Description
[0026] 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.
[0027] 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.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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.
[0034] 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.
[0035] 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.
[0036] 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.
[0037] 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.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] FIG. 1 is a block diagram of a system 100 for managing pharmacy kits according to an embodiment of the inventive concept.
[0042] Referring to FIG. 1 , system 100 comprises an information processing system 115 and an RFID reading station 110. System 100 is configured to automatically read and process information from a pharmacy kit 105. This allows relatively efficient monitoring and updating of the kit's contents.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] Although FIG. 1 shows RFID reading station 110 and information processing system 115 as separate features, they are not required to be physically or functionally separate. For instance, information processing features could be integrated with parts of RFID reading station 110, such as an RFID reader. In general, the physical and functional implementation of system 100 can be partitioned arbitrarily between various forms of hardware, software, firmware, etc., as will be recognized by those skilled in the art.
[0051] 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.
[0052] FIGS. 2A through 2C are diagrams illustrating a pharmacy kit according to an embodiment of the inventive concept. In particular, FIG. 2A shows an example of a kit tray comprising multiple items having RFID tags, FIG. 2B shows an example of a partial template associated with the kit, and FIG. 2C shows an example of a partial kit record for the kit. The kit of FIGS. 2A through 2C represents one example of pharmacy kit 105 shown in FIG. 1 .
[0053] Referring to FIG. 2A , kit 105 comprises a container 205 and items 210. Container 205 is shown as a tray in FIG. 2A , but this is merely one example of a container that can be used to carry items 210. Alternative examples include boxes, canisters, bags, coolers, and various others. Although not shown in FIG. 2A , kit 105 could further comprise a cover, such as a lid, that can be used to enclose items 210 prior to deployment. Additionally, the cover can be sealed onto container 205 to prevent tampering between deployment and use of kit 105. In general, where kit 105 is susceptible to opening or closing (e.g., where it has a lid or other covering), it can be read in an open configuration or a closed configuration.
[0054] Items 210 typically include medicines or other medical supplies that may be stocked by a pharmacy. As shown in FIG. 2A , items 210 can have various different forms of packaging. For example, they can be packaged in vials, bags, boxes, bottles, and other forms. These different forms of packaging may also comprise different materials, such as glass, plastic, paper, cardboard, foam, or metal.
[0055] 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.
[0056] 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.
[0057] Referring to FIG. 2B , an example template defines items to be placed in kit 105. More specifically, the template defines a plurality of item segments (or “segments”) to be included in kit 105, where each item segment corresponds to a class or type of items and/or additional segments to be included in specific quantities. For instance, an item segment may define a specific class of medications, such as ibuprofen, acetaminophen, adenosine, or albuterol. Where a segment includes one or more additional segments, the template is considered to have multiple segment “levels”. In general, a template can have an arbitrary number of segment levels. An example of a template having multiple segment levels would be one containing a segment “analgesic”, with the item “morphine” and a sub-segment “ibuprofen” containing items “Advil” and “Generic”.
[0058] For simplicity, FIG. 2B shows example segments in generic form, i.e., “medicine bottle 1”, “medicine vial 2”, etc. The segment “medicine bottle 1”, for example, indicates that kit 105 is to include one or more bottles of a first type of medicine (e.g., a bottle of ibuprofen). Similarly, the segment “medicine vial 2” indicates that kit 105 is to include one or more vials of a second type of medicine (e.g., a vial of adenosine), and so on. Although each segment in FIG. 2B is associated with a particular type of packaging, such as a bottle, vial, or bag, segments are not necessarily limited by package type. For instance, a segment could be defined more broadly based on medicine type alone.
[0059] 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, FIG. 2B shows the items associated with each segment in generic form, i.e., “product A”, “product B”, etc. Accordingly, the segment “medicine bottle 1” may be satisfied by two different products “A” and “B”, the segment “medicine vial 2” may be satisfied by three different products “C”, “D”, and “E”, and so on.
[0060] 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 FIG. 2B , kit 105 is to include one item corresponding to “medicine bottle 1” (e.g., one bottle of ibuprofen), three items corresponding to “medicine vial 2”, two items corresponding to “medicine bag 3”, and so on. As a more concrete example, a segment “Pain Medication” could have permissible items “Tylenol” or “Advil”, with a quantity of two, which could be satisfied by two bottles of Tylenol, two bottles of Advil, or one of each, for instance.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] Referring to FIG. 2C , a kit record comprises information regarding the contents of a kit that has been built in a pharmacy and verified through the use of RFID reading station 110. In the example of FIG. 2C , the information comprises the name of each segment in the kit, and specific details of each item in each segment. The specific item details include a brand name, an item name, an NDC identifier, a lot number, medicine strength or concentration, and an expiration date. The item details may further include information indicating whether an item has a fixed expiration date or one that varies based on time away from a refrigerator. Where the item has a variable expiration date, the item details may indicate whether the item has been removed from the refrigerator, and if so, at what time or date.
[0065] 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.
[0066] FIGS. 3A and 3B are diagrams of RFID reading station 110 of FIG. 1 according to an embodiment of the inventive concept. In particular, FIG. 3A is a block diagram illustrating electronic equipment associated with RFID reading station 110 according to an example embodiment, and FIG. 3B is a schematic diagram of a container configured to receive kit 105 during a read operation of RFID reading station 110.
[0067] Referring to FIG. 3A , RFID reading station 110 comprises an RFID reader 305 and an antenna 310. Antenna 310 is located within a container 315 designed to receive kit 105 during a read operation. RFID reader 305 controls antenna 310 to communicate with RFID tags associated with items of kit 105, as well as any RFID tag associated with the kit itself. In addition, RFID reader 305 receives and processes communications received by antenna 310 from kit 105. Although RFID reader 305 is shown outside of container 315, it could alternatively be included within container 315. Moreover, although RFID reader 305 and antenna 310 are shown as two separate components, they could alternatively be integrated into a single component or divided into additional components.
[0068] 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.
[0069] Referring to FIG. 3B , container 315 comprises an enclosed space for receiving kit 105. The left side of FIG. 3B shows container 315 with doors opened to receive kit 105, and the right side of FIG. 3B shows container 315 with doors closed to perform a read operation. The use of an enclosed space to allows RFID tags to be read without interference from objects in the surrounding environment, such as false positives from RFID tags on items not belonging to kit 105. Accordingly, container 315 may be formed of a material designed to provide electromagnetic shielding, such as a metal box.
[0070] 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.
[0071] FIG. 4 is a diagram of information processing system 115 according to an embodiment of the inventive concept. In the embodiment of FIG. 4 , various features of information processing system 115 are connected in a networked configuration. However, in alternative embodiments these components could be in alternative configurations, e.g., with components directly connected, physically integrated, or functionally partitioned in other ways.
[0072] Referring to FIG. 4 , information processing system 115 comprises a computer 405 and a server 420. Computer 405 and server 420 are connected to each other via the internet 415, and computer 405 is connected to an RFID reader, a bar code reader, and an RFID printer through a local area network (LAN) 435.
[0073] 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.
[0074] Although server 420 is shown as a single unit in FIG. 4 , it may comprise more than one device, such as multiple local and/or central computers. In addition, although server 420 is shown to be connected with a single computer, it may be connected to additional or alternative devices, such as other local computers, mobile devices, and so on. Moreover, although server 420 is shown to receive information from a single RFID reader, it could also receive information from other RFID readers. For example, information processing system could be connected to multiple RFID reading stations through the internet 415.
[0075] 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.
[0076] FIG. 5 is a flowchart illustrating a method of managing pharmacy kits according to an embodiment of the inventive concept. The method of FIG. 5 is typically performed by a pharmacist or other medical professional associated with a hospital pharmacy. For explanation purposes, it will be assumed that the method of FIG. 5 is performed using system 100 of FIG. 1 . However, the method is not limited to a particular system. In the description that follows, example method steps will be indicated by parentheses (XXX) to distinguish them from device or system components.
[0077] Referring to FIG. 5 , the method begins with a pharmacy receiving and processing kit items (505). The items typically arrive in bulk at the pharmacy and are processed by tagging them with RFID tags and recording them in an inventory system. Next, a kit is built from tagged items in the pharmacy inventory (510), and the kit is scanned using RFID reading station 110 (515). The scan detects RFID tags of kit items and the kit itself and transmits corresponding information to information processing system 115.
[0078] 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.
[0079] 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.
[0080] 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).
[0081] The updating of records and status check are typically performed any time the kit is scanned, as indicated by the flow of FIG. 5 . This can take place under a variety of circumstances, such as when a kit is first built and verified, when the kit is checked-in to the pharmacy for storage, or when the kit is checked-out of the pharmacy for use.
[0082] 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.
[0083] FIG. 6 is a flowchart illustrating a method of receiving and processing items for a pharmacy kit according to an embodiment of the inventive concept. The method of FIG. 6 is an example of step 505 of FIG. 5 .
[0084] Referring to FIG. 6 , items arrive at a facility (e.g., a hospital) from a third party manufacturer, distributor, or supplier (605). In some circumstances, the items may have RFID tags when they arrive at the facility. Accordingly, system 100 may scan the items and look up item information from the third party or an additional third party. Such information may include, for example, item master data, item lot data, and item expiration dates. If the items are not already tagged, item information may be entered into system 100 using a bar code scanner as described above, or by manual user input (610).
[0085] 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 FIG. 6 shows an example using two different tag types, the described method is not limited to two tag types, and could be performed with additional tag types. Following the determination of the tag type, system 100 creates the first type of tag (620) or the second type of tag (625).
[0086] 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.
[0087] 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).
[0088] FIG. 7 is a flowchart illustrating a method of building a pharmacy kit according to an embodiment of the inventive concept. The method of FIG. 7 is an example of step 510 of FIG. 5 .
[0089] Referring to FIG. 7 , the method comprises inserting tagged items into a container (705), generating an RFID tag for the kit (710), and applying the RFID tag to the kit (715). The method may further comprise sealing the kit; however, the sealing is typically performed after the kit has been scanned. Where system 100 is connected to an RFID printer, the kit's RFID tag can be generated using the printer, similar to the method of FIG. 6 . Otherwise, a preprinted RFID tag can be used, and the tag's number can be manually entered into system 100 as in the method of FIG. 6 . The sealing can be performed, for example, using a shrink wrap material, an adhesive, a sticker, or various other known techniques. In general, the term seal or sealing, as used herein, should not be construed in an overly formal sense—for example, it does not require an airtight seal—but rather it merely refers to a mechanism for ensuring that the contents of the kit are not tampered with as long as a seal remains in place or unbroken. Moreover, some seals used in conjunction with RFID technology may allow RFID based detection of whether a seal is broken.
[0090] FIGS. 8A and 8B are flowcharts illustrating methods of operating kit management system 100 according to an embodiment of the inventive concept. In particular, FIG. 8A shows a method that can be used to implement step 515 of FIG. 5 , and FIG. 8B shows a method that can be used to implement parts of the method of FIG. 8A .
[0091] Referring to FIG. 8A , a user or sensor initiates an RFID read operation (805). This can be accomplished, for instance, by merely placing kit 105 in RFID reading station 115, or by actuating specific controls on a user interface. In the read operation, RFID reader 305 powers antennas of RFID tags in kit 105, and it reads item tags and a kit tag, if present (810). The read operation may be used to perform an initial inventory of kit 105 following its assembly, or it can used for a re-inventory following use. Next, tag data is sent to a server in information processing system 115 or elsewhere (815). Finally, the server reports information to a user via an interface such as a computer display or a computer-generated printout (820).
[0092] Referring to FIG. 8B , steps 805 and 815 can be performed through the use of a web interface such as a web browser. For example, in some embodiments, a user directs a computer to request a web page from a server (825). This is typically accomplished through a web browser and it can be done in an encrypted or non-encrypted manner. For instance, the computer can communicate with the server using an encrypted protocol such as the secure sockets layer (SSL) protocol.
[0093] 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).
[0094] 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 FIG. 4 . This information can be compared with the tag information relayed to the server in step 840, and then based on the comparison the server may generate a report on the status of the kit, such as whether any items are absent or whether any items have been erroneously included in the kit. The report may also include information relating to the expiration status of the items in kit 105, such as whether the items are expired or near expiration, or a summary of the expiration status of a set of items or the kit as a whole. The report may also include a charge sheet including the status of each item, such as its expiration date, which items have expired, which items are about to expire, and which item is going to expire next. In general, the information included in the report may be data that was read from a kit, item, or other source, or it may be data that was calculated based on rules, inputs, or other criteria.
[0095] FIG. 9 shows an interface 900 that can be used to control system 100 according to an embodiment of the inventive concept. For example, interface 900 can be used to control various aspects of the methods illustrated in FIGS. 5 through 8 . Interface 900 is typically accessed through a display connected to a computer or server such as those illustrated in FIG. 4 .
[0096] Referring to FIG. 9 , interface 900 comprises interactive graphical user interface (GUI) components including a menu bar 905 and buttons 910 through 925. These features allow a user to initiate various kit-related procedures, such as scanning a kit that has been placed in an RFID reading station, generating reports based on kit information, printing RFID tags for a kit, and performing administrative tasks. For example, a user may press button 910 (or alternatively, a scan button in menu bar 905) to initiate a read operation of RFID reading station 110 after kit 105 has been placed in a designated reading location such as a metal box. The user may press button 915 to generate a report comprising information similar to that illustrated in FIG. 2C . The user may press button 920 to initiate a procedure for capturing item information and printing RFID tags. Finally, the user may press button 925 to access various administrative controls for system 100 or interface 900.
[0097] FIG. 10 shows a report 1000 generated for a pharmacy kit using system 100 according to an embodiment of the inventive concept. Report 1000 corresponds to a pediatric emergency drug tray, which is a type of kit comprising items used for common pediatric emergencies. Such a kit can be deployed to a hospital emergency room, for example.
[0098] Referring to FIG. 10 , report 1000 comprises a portion 1005 indicating the type of kit for which the report was generated, as well as the total number of items in the kit. In this example, the kit comprises 51 total items. Report 1000 further comprises a portion 1010 indicating the number of extra and missing items in the kit, as well as the number of expired or soon to expire items. In this example, one item is missing and two items are near expiration. The soon-to-expire items are listed as two containers of Procainamide Hydrochloride, which expire on Oct. 1, 2012. The date range of soon-to-expire items can be set arbitrarily, for example, using administrative tools accessible through button 925 in interface 900. Nevertheless, the date range is typically established in consideration of factors such as the anticipated delay between deployment of the kit and its use, as well as any regulatory considerations, such as rules from the board-of-pharmacy requirements or the joint commission (TJC).
[0099] 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.
[0100] FIG. 11 shows another report 1100 generated for a pharmacy kit using system 100 according to an embodiment of the inventive concept. Report 1100 corresponds to a demonstration kit, which is a type of kit comprising items used for common pediatric emergencies. Such a kit can be deployed to a hospital emergency room, for example.
[0101] 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.
[0102] 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”.
[0103] FIG. 12 shows an interface 1200 for checking out a kit to a user or location according to an embodiment of the inventive concept. Interface 1200 can be invoked, for instance, using the check out button in area 1135 of FIG. 11 . In response to a user pressing the check out button, a dialog box 1205 appears within interface 1200. Dialog box 1205 allows a user to select a person or place to whom the kit may be assigned. This selection can be made, for example, as the kit is placed in possession of the selected person or an authorized delivery agent. Information regarding the selected person and location can then be stored in system 100 to facilitate subsequent recovery or further monitoring of the kit.
[0104] FIGS. 13A and 13B show interfaces 1300A and 1300B used to generate and view reports for pharmacy kits according to an embodiment of the inventive concept. In particular, FIG. 13A shows an example of an interface where a user has selected to view a report of kits that need re-working, and FIG. 13B shows an example of an interface where a user has selected to view a report of kits containing a specific lot number.
[0105] Referring to FIG. 13A , interface 1300A comprises a first area 1305A where a user selects a type of report to be generated. In this example, the user has selected from a drop down menu to generate a report of kits that need re-working. Once the selection is made the drop down menu, first area 1305A is further populated with options of details to include in the report. In this example, the options allow the user to select whether the report should include surplus items, shortages, expired items, expiring items, or all segments of the kit.
[0106] 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.
[0107] Referring to FIG. 13B , interface 1300B comprises a first area 1305B where a user selects the type of report to be generated. In this example, the user has selected from the drop down menu to generate a report of kits containing a specific item or lot number. Based on this selection, first area 1305B is populated with a form allowing the user to enter all or part of a lot number or other information for identifying the item. In the example of FIG. 13B , the user has entered a lot number.
[0108] 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 FIG. 13B , only a partial lot number is entered first area 1310B, so second area 1310B displays information related to items that begin with the partial lot number. However, system 100 could be modified to use the exact lot number only. It could also be modified to use multiple lot numbers.
[0109] In addition to generating reports such as those illustrated in FIGS. 10 through 13 , system 100 may also generate reports on kit locations. Such locations can be determined, for example, through automatic kit tracking or some other mechanism. Moreover, system 100 may also provide mechanisms for automatically tracking inventory in the kits and the usage of items based on usage data. For example, by analyzing usage data of different items, system 100 could determine the level inventory to meet minimum requirements of all kits in a facility or a target level of inventory to be maintained. For example, if a type of kit requires a bottle of ibuprofen and the facility has 20 kits of that type, the facility has a minimum requirement of 20 bottles of ibuprofen. If the facility uses 10 bottles of ibuprofen during a specified time (e.g., a month), system 100 could then estimate or predict when the facility will run out of the current stock of ibuprofen. Accordingly, system 100 can be used to predict where inventory shortages may occur and then alert relevant personnel of potential existing or upcoming inventory shortages.
[0110] 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.
[0111] FIGS. 14A through 14D are diagrams of a label 1400 that can be used to attach an RFID tag to various items of a pharmacy kit according to an embodiment of the inventive concept. In particular, FIG. 14A shows label 1400 in a configuration prior to use, and FIG. 14B shows label 1400 in a configuration for attachment to a pharmaceutical item. FIG. 14C shows an example of label 1400 with example dimensions and an embedded RFID device 1435, and FIG. 14D shows label 1400 in the context of a printable roll.
[0112] 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.
[0113] Referring to FIG. 14A , label 1400 comprises a first portion 1405 having a printed portion 1410 and a flap portion 1415 separated by a perforation indicated by a dotted line. Label 1400 further comprises a second portion 1420 having a tail 1425 attached to first portion 1405, and a backing 1430 designed to be removed when tail 1425 is adhered to an item.
[0114] 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.
[0115] 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 FIG. 14C . The substrate material can be printed with identifying information for an item. Among the printed information, there may be a bar code for backward compatibility, or human-readable information related to the item or label 1400. The RFID device can be encoded with identifying information through RFID printing.
[0116] 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.
[0117] As alternatives to the example of FIG. 14A , the size of the tail may vary, and the perforated portion may be omitted. The tail size, for example, may be at least as large as the printable labeling portion.
[0118] Referring to FIG. 14B , label 1400 is shown in a configuration used to attach it to an item, which is illustrated conceptually by a dotted rectangle. When label 1400 is attached to the item, flap portion 1415 is adhered over printed portion 1410, and tail 1425 is adhered to the item while first portion 1405 hangs off of it.
[0119] Referring to FIG. 14C , label 1400 may have example dimensions as shown. However, these dimensions may vary in alternative embodiments. In addition, label 1400 may comprise RFID 1435 as shown, although other devices or device configurations can be used in alternative embodiments.
[0120] Referring to FIG. 14D , label 1400 is shown in the context of a roll comprising successive printable labels that can be fed into an RFID printer. In particular, label 1400 is shown as a second label among three successive labels “label 1”, “label 2”, and “label 3”. These labels are separated from each other by a small gap having a vertical sense mark used for alignment with an RFID printer.
[0121] 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
Post-issuance certificates present
The text shown below may not reflect later post-issuance changes.
What is claimed is:
1. A system for managing pharmacy kits, comprising:
a reading station, comprising:
a pharmacy kit container formed of a material designed to provide electromagnetic shielding, and
an antenna coupled to the pharmacy kit container;
computer-executable instructions that when executed by a processor cause the processor to:
cause the antenna to emit a radio signal at least within the pharmacy kit container, and
receive tag information from a plurality of radio frequency identification (RFID) tags coupled to a plurality of medicinal containers configured to store a plurality of drugs, the plurality of RFID tags being associated with a pharmacy kit located within the pharmacy kit container,
wherein for the plurality of RFID tags, a particular RFID tag is coupled to a particular medicinal container of the plurality of medicinal containers and the particular medicinal container is configured to store a particular drug of the plurality of drugs, and
wherein the particular RFID tag is associated with drug data of the particular drug, the drug data comprising at least an identifier of the particular drug and an expiration of the particular drug; and
an information processing system communicatively coupled to the reading station and configured to:
verify a first drug of the plurality of drugs using the tag information, wherein to verify the first drug, the information processing system is configured to:
determine whether a first medicinal container associated with the first drug is present based at least in part on the tag information received from the plurality of RFID tags,
based at least upon a determination that the first medicinal container is not present, determine whether a second medicinal container configured to store a substitute first drug is present based at least in part on the tag information,
based at least upon a determination that the second medicinal container is present, determine whether an expiration of the substitute first drug satisfies an expiration threshold based at least in part on the drug data associated with a first RFID tag of the plurality of RFID tags, wherein the first RFID tag is coupled to the second medicinal container, and
based at least upon a determination that the expiration of the substitute first drug satisfies the expiration threshold, verify the first drug,
identify any drugs that are missing from the pharmacy kit based at least in part on the tag information received from the plurality of RFID tags and a template for the pharmacy kit,
identify any drugs of the plurality of drugs that do not satisfy the expiration threshold based at least in part on the tag information received from the plurality of RFID tags, and
cause a display to display information regarding the plurality of drugs in the pharmacy kit including the substitute first drug, the any drugs that are missing from the pharmacy kit, and the any drugs of the plurality of drugs that do not satisfy the expiration threshold.
2. The system of claim 1, wherein to identify the any drugs that are missing from the pharmacy kit the information processing system is configured to compare the tag information with the template, wherein the template specifies a plurality of segments for the pharmacy kit and a quantity of pharmaceutical items including the plurality of medications from each segment to be included in the pharmacy kit.
3. The system of claim 1, wherein the information processing system is configured to monitor locations of a plurality of pharmacy kits based at least in part on information received from a real-time tracking system regarding the locations of the plurality of pharmacy kits.
4. The system of claim 2, wherein the template identifies the substitute first drug as an acceptable substitute for the first drug.
5. The system of claim 1, wherein the information processing system stores the template and kit records of the pharmacy kit.
6. The system of claim 1, wherein the pharmacy kit container is configured to receive only one pharmacy kit at a time.
7. The system of claim 1, wherein the information processing system stores a virtual history for each of the plurality of the pharmacy kit and updates the virtual history in response to a transaction involving the pharmacy kit.
8. A method of managing pharmacy kits, comprising:
receiving tag information of a plurality of radio frequency identification (RFID) tags coupled to a plurality of medicinal containers based at least in part on an antenna coupled to a pharmacy kit container emitting a radio signal at least within the pharmacy kit container,
wherein the pharmacy kit container provides electromagnetic shielding,
wherein the plurality of medicinal containers are configured to store a plurality of medications and the plurality of RFID tags are associated with a pharmacy kit located within the pharmacy kit container,
wherein for the plurality of RFID tags, a particular RFID tag is coupled to a particular medicinal container of the plurality of medicinal containers and the particular medicinal container is configured to store a particular medication of the plurality of medications, and
wherein the particular RFID tag is associated with medication data of the particular medication, the medication data comprising at least an identifier of the particular medication and an expiration of the particular medication;
verifying the plurality of medications including at least a first medication of the plurality of medications using the tag information, wherein verifying the at least a first medication comprises:
determining that a first medicinal container associated with the first medication is not present based at least in part on the tag information received from the plurality of RFID tags,
determining that a second medicinal container configured to store a substitute first medication is present based at least in part on the tag information, and
determining that an expiration of the substitute first medication satisfies an expiration threshold based at least in part on the medication data associated with a first RFID tag of the plurality of RFID tags, wherein the first RFID tag is coupled to the second medicinal container; and
causing a display to display results of the verifying the plurality of medications including information regarding the substitute first medication.
9. The method of claim 8, further comprising identifying any missing medications in the pharmacy kit based at least in part on a comparison between the tag information and a template of the pharmacy kit.
10. The method of claim 9, further comprising generating a report indicating the any missing medications.
11. The method of claim 9, further comprising generating billing information for a medical patient based on the any missing medications.
12. The method of claim 9, further comprising determining at least one medication of the plurality of medications is expired based at least in part on an amount of time since the at least one medication was removed from refrigeration.
13. The method of claim 9, further comprising
determining any near expired medications of the plurality of medications based at least in part on a predetermined expiration margin; and
generating a report indicating the near expired items.
14. A system for managing pharmacy kits, comprising:
a reading station, comprising:
a pharmacy kit container formed of a material designed to provide electromagnetic shielding, and
an antenna coupled to the pharmacy kit container; and
computer-executable instructions that when executed by one or more processors cause the one or more processors to:
receive tag information of a plurality of radio frequency identification (RFID) tags coupled to a plurality of medicinal containers based at least in part on the antenna emitting a radio signal at least within the pharmacy kit container,
wherein the plurality of medicinal containers are configured to store a plurality of medications and the plurality of RFID tags are associated with a pharmacy kit located within the pharmacy kit container,
wherein for the plurality of RFID tags, a particular RFID tag is coupled to a particular medicinal container of the plurality of medicinal containers and the particular medicinal container is configured to store a particular medication of the plurality of medications, and
wherein the particular RFID tag is associated with medication data of the particular medication, the medication data comprising at least an identifier of the particular medication and an expiration of the particular medication,
verify the plurality of medications using the tag information, wherein to verify at least a first medication of the plurality of medications the computer-executable instructions cause the one or more processors to:
determine that a first medicinal container associated with the first medication is not present based at least in part on the tag information received from the plurality of RFID tags,
determine that a second medicinal container configured to store a substitute first medication is present based at least in part on the tag information, and
determine that an expiration of the substitute first medication satisfies an expiration threshold based at least in part on the medication data associated with a first RFID tag of the plurality of RFID tags, wherein the first RFID tag is coupled to the second medicinal container, and
cause a display to display results of the verification of the plurality of medications including information regarding the substitute first medication.
15. The system of claim 14, wherein the first medicinal container associated with the first medication is determined to be not present based at least in part on a comparison of the tag information with a template of the pharmacy kit.
16. The system of claim 15, wherein the template specifies medications to be included in the plurality of medications associated with the pharmacy kit.
17. The system of claim 15, wherein to verify the plurality of medications, the computer-executable instructions when executed further cause the one or more processors to compare the tag information with a template of the pharmacy kit to identify one or more missing medications.
18. The system of claim 15, wherein to verify the plurality of medications, the computer-executable instructions when executed further cause the one or more processors to determine whether an expiration of each of the plurality of medications satisfies the expiration threshold.
19. The system of claim 15, wherein to verify the plurality of medications, the computer-executable instructions when executed further cause the one or more processors to determine whether a quantity of each medication of the plurality of medications satisfies a threshold quantity.
20. The system of claim 15, wherein to verify the plurality of medications, the computer-executable instructions when executed further cause the one or more processors to determine whether any the plurality of medications are subject to a recall based.
Patent Citations (258)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5986662(A) | 1999-11-01 | Argiro et al. | Applicant |
| US6249299(B1) | 2001-06-01 | Tainer | Applicant |
| US6294999(B1) | 2001-09-01 | Yarin et al. | Applicant |
| US6574166(B2) | 2003-06-01 | Niemiec | Applicant |
| US6632619(B1) | 2003-10-01 | Harrison et al. | Applicant |
| US6825864(B2) | 2004-11-01 | Botten et al. | Applicant |
| US6851615(B2) | 2005-02-01 | Jones | Applicant |
| US6877658(B2) | 2005-04-01 | Raistrick et al. | Applicant |
| US6900021(B1) | 2005-05-01 | Harrison et al. | Applicant |
| US6933849(B2) | 2005-08-01 | Sawyer | Applicant |
| US6935560(B2) | 2005-08-01 | Andreasson et al. | Applicant |
| US6985870(B2) | 2006-01-01 | Martucci et al. | Applicant |
| US7061831(B2) | 2006-06-01 | De La Huerga | Applicant |
| US7116343(B2) | 2006-10-01 | Botten et al. | Applicant |
| US7118029(B2) | 2006-10-01 | Nycz et al. | Applicant |
| US7140542(B2) | 2006-11-01 | Andreasson et al. | Applicant |
| US7146247(B2) | 2006-12-01 | Kirsch et al. | Applicant |
| US7151456(B2) | 2006-12-01 | Godfrey | Applicant |
| US7158030(B2) | 2007-01-01 | Chung | Applicant |
| US7175081(B2) | 2007-02-01 | Andreasson et al. | Applicant |
| US7177721(B2) | 2007-02-01 | Kirsch et al. | Applicant |
| US7182256(B2) | 2007-02-01 | Andreasson et al. | Applicant |
| US7227469(B2) | 2007-06-01 | Varner et al. | Applicant |
| US7232066(B2) | 2007-06-01 | Andreasson et al. | Applicant |
| US7253736(B2) | 2007-08-01 | Tethrake et al. | Applicant |
| US7256699(B2) | 2007-08-01 | Tethrake et al. | Applicant |
| US7264323(B2) | 2007-09-01 | Tainer et al. | Applicant |
| US7268684(B2) | 2007-09-01 | Tethrake et al. | Applicant |
| US7299981(B2) | 2007-11-01 | Hickle et al. | Applicant |
| US7341147(B2) | 2008-03-01 | Mallett et al. | Applicant |
| US7354884(B2) | 2008-04-01 | Hada et al. | Applicant |
| US7362228(B2) | 2008-04-01 | Nycz et al. | Applicant |
| US7375737(B2) | 2008-05-01 | Botten et al. | Applicant |
| US7394383(B2) | 2008-07-01 | Hager et al. | Applicant |
| US7440818(B2) | 2008-10-01 | Handfield et al. | Applicant |
| US7446747(B2) | 2008-11-01 | Youngblood et al. | Applicant |
| US7454880(B1) | 2008-11-01 | Austin et al. | Applicant |
| US7486188(B2) | 2009-02-01 | Van Alstyne | Applicant |
| US7492257(B2) | 2009-02-01 | Tethrake et al. | Applicant |
| US7492261(B2) | 2009-02-01 | Cambre et al. | Applicant |
| US7504954(B2) | 2009-03-01 | Spaeder | Applicant |
| US7518502(B2) | 2009-04-01 | Austin et al. | Applicant |
| US7551089(B2) | 2009-06-01 | Sawyer | Applicant |
| US7559483(B2) | 2009-07-01 | Hickle et al. | Applicant |
| US7564364(B2) | 2009-07-01 | Zweig | Applicant |
| US7639136(B1) | 2009-12-01 | Wass et al. | Applicant |
| US7644016(B2) | 2010-01-01 | Nycz et al. | Applicant |
| US7672872(B2) | 2010-03-01 | Shanton | Applicant |
| US7706915(B2) | 2010-04-01 | Mohapatra et al. | Applicant |
| US7706916(B2) | 2010-04-01 | Hilton | Applicant |
| US7712670(B2) | 2010-05-01 | Sauerwein, Jr. et al. | Applicant |
| US7715277(B2) | 2010-05-01 | De La Huerga | Applicant |
| US7729597(B2) | 2010-06-01 | Wright et al. | Applicant |
| US7734157(B2) | 2010-06-01 | Wright et al. | Applicant |
| US7747477(B1) | 2010-06-01 | Louie et al. | Applicant |
| US7752085(B2) | 2010-07-01 | Monroe | Applicant |
| US7772964(B2) | 2010-08-01 | Tethrake et al. | Applicant |
| US7775056(B2) | 2010-08-01 | Lowenstein | Applicant |
| US7783163(B2) | 2010-08-01 | Wright et al. | Applicant |
| US7783174(B2) | 2010-08-01 | Wright et al. | Applicant |
| US7801422(B2) | 2010-09-01 | Wright et al. | Applicant |
| US7834765(B2) | 2010-11-01 | Sawyer | Applicant |
| US7834766(B2) | 2010-11-01 | Sawyer | Applicant |
| US7837093(B1) | 2010-11-01 | Leu et al. | Applicant |
| US7837107(B1) | 2010-11-01 | Leu et al. | Applicant |
| US7858841(B2) | 2010-12-01 | Krautkramer et al. | Applicant |
| US7868754(B2) | 2011-01-01 | Salvat, Jr. | Applicant |
| US7893876(B2) | 2011-02-01 | Brown et al. | Applicant |
| US7908030(B2) | 2011-03-01 | Handfield et al. | Applicant |
| US7918830(B2) | 2011-04-01 | Langan et al. | Applicant |
| US7933033(B2) | 2011-04-01 | Ohishi et al. | Applicant |
| US7976508(B2) | 2011-07-01 | Hoag | Applicant |
| US7985711(B2) | 2011-07-01 | Tohmatsu et al. | Applicant |
| US7990272(B2) | 2011-08-01 | Wass et al. | Applicant |
| US7996286(B2) | 2011-08-01 | Kreiner et al. | Applicant |
| US8002174(B2) | 2011-08-01 | Coyne, III et al. | Applicant |
| US8031347(B2) | 2011-10-01 | Edwards et al. | Applicant |
| US8042738(B2) | 2011-10-01 | Cloix | Applicant |
| US8049627(B1) | 2011-11-01 | Addante | Applicant |
| US8063925(B2) | 2011-11-01 | Tainer et al. | Applicant |
| US8065858(B2) | 2011-11-01 | Leu et al. | Applicant |
| US8082192(B2) | 2011-12-01 | Nycz et al. | Applicant |
| US8108068(B1) | 2012-01-01 | Boucher et al. | Applicant |
| US8111159(B2) | 2012-02-01 | Andreasson et al. | Applicant |
| US8112175(B2) | 2012-02-01 | Handfield et al. | Applicant |
| US8131397(B2) | 2012-03-01 | Vahlberg et al. | Applicant |
| US8154390(B2) | 2012-04-01 | Heath et al. | Applicant |
| US8174392(B1) | 2012-05-01 | Sagbhini et al. | Applicant |
| US8186587(B2) | 2012-05-01 | Zmood et al. | Applicant |
| US8212677(B2) | 2012-07-01 | Ferguson | Applicant |
| US8219413(B2) | 2012-07-01 | Martinez et al. | Applicant |
| US8224483(B1) | 2012-07-01 | Ansari et al. | Applicant |
| US8231749(B2) | 2012-07-01 | Dent et al. | Applicant |
| US8258961(B2) | 2012-09-01 | Phillips et al. | Applicant |
| US8261939(B2) | 2012-09-01 | Knoth | Applicant |
| US8279069(B2) | 2012-10-01 | Sawyer | Applicant |
| US8283287(B2) | 2012-10-01 | Aihara et al. | Applicant |
| US8284059(B2) | 2012-10-01 | Ross | Applicant |
| US8285083(B2) | 2012-10-01 | Canessa et al. | Applicant |
| US8285607(B2) | 2012-10-01 | Danilewitz | Applicant |
| US8292173(B2) | 2012-10-01 | Yturralde et al. | Applicant |
| US8296950(B2) | 2012-10-01 | Colbrunn et al. | Applicant |
| US8339649(B2) | 2012-12-01 | Ohishi et al. | Applicant |
| US8341041(B2) | 2012-12-01 | Hull | Applicant |
| US8346632(B2) | 2013-01-01 | Saghbini | Applicant |
| US8355962(B2) | 2013-01-01 | Delaney et al. | Applicant |
| US8359338(B2) | 2013-01-01 | Butterfield et al. | Applicant |
| US8376228(B2) | 2013-02-01 | DeVet et al. | Applicant |
| US8384545(B2) | 2013-02-01 | Hussain et al. | Applicant |
| US8403212(B2) | 2013-03-01 | van Esch | Applicant |
| US8403224(B2) | 2013-03-01 | Fedorko et al. | Applicant |
| US8405508(B2) | 2013-03-01 | Burke | Applicant |
| US8461076(B2) | 2013-06-01 | Okada et al. | Applicant |
| US8483550(B2) | 2013-07-01 | Wright et al. | Applicant |
| US8509604(B2) | 2013-08-01 | Wright et al. | Applicant |
| US8515251(B2) | 2013-08-01 | Wright et al. | Applicant |
| US8530379(B2) | 2013-09-01 | Shimizu et al. | Applicant |
| US8564416(B2) | 2013-10-01 | Steven et al. | Applicant |
| US8565552(B2) | 2013-10-01 | Sommer et al. | Applicant |
| US8582171(B2) | 2013-11-01 | Srnka et al. | Applicant |
| US8593678(B2) | 2013-11-01 | Ohishi et al. | Applicant |
| USD694817(S) | 2013-12-01 | Adam et al. | Applicant |
| US8636202(B2) | 2014-01-01 | Keefe et al. | Applicant |
| US8639525(B2) | 2014-01-01 | Levine et al. | Applicant |
| US8686859(B2) | 2014-04-01 | Hussain et al. | Applicant |
| US8699054(B2) | 2014-04-01 | Edwards et al. | Applicant |
| US8749356(B2) | 2014-06-01 | Hussain et al. | Applicant |
| US8755056(B2) | 2014-06-01 | Edwards et al. | Applicant |
| US8825680(B2) | 2014-09-01 | Burke et al. | Applicant |
| US2002/0026330(A1) | 2002-02-01 | Klein | Applicant |
| US2003/0074223(A1) | 2003-04-01 | Hickle et al. | Applicant |
| US2003/0160698(A1) | 2003-08-01 | Andreasson et al. | Applicant |
| US2004/0008123(A1) | 2004-01-01 | Carrender et al. | Applicant |
| US2004/0032330(A1) | 2004-02-01 | Hoffman | Applicant |
| US2004/0057609(A1) | 2004-03-01 | Weinberg | Applicant |
| US2004/0081669(A1) | 2004-04-01 | Greeven et al. | Applicant |
| US2004/0178071(A1) | 2004-09-01 | Harrison et al. | Applicant |
| US2005/0014849(A1) | 2005-01-01 | Pettit et al. | Applicant |
| US2005/0060171(A1) | 2005-03-01 | Molnar | Applicant |
| US2005/0062603(A1) | 2005-03-01 | Fuerst et al. | Applicant |
| US2005/0108044(A1) | 2005-05-01 | Koster | Applicant |
| US2005/0149378(A1) | 2005-07-01 | Cyr et al. | Applicant |
| US2005/0283259(A1) | 2005-12-01 | Wolpow | Applicant |
| US2005/0285732(A1) | 2005-12-01 | Sengupta et al. | Applicant |
| US2005/0285746(A1) | 2005-12-01 | Sengupta et al. | Applicant |
| US2006/0006999(A1) | 2006-01-01 | Walczyk et al. | Applicant |
| US2006/0043177(A1) | 2006-03-01 | Nycz et al. | Applicant |
| US2006/0043179(A1) | 2006-03-01 | Nycz et al. | Applicant |
| US2006/0065726(A1) | 2006-03-01 | Andreasson et al. | Applicant |
| US2006/0132311(A1) | 2006-06-01 | Kruest et al. | Applicant |
| US2006/0145871(A1) | 2006-07-01 | Donati et al. | Applicant |
| US2006/0152338(A1) | 2006-07-01 | Hsu | Applicant |
| US2006/0152364(A1) | 2006-07-01 | Walton | Applicant |
| US2006/0267731(A1) | 2006-11-01 | Chen | Applicant |
| US2007/0008399(A1) | 2007-01-01 | Botten et al. | Applicant |
| US2007/0023512(A1) | 2007-02-01 | Miller et al. | Examiner |
| US2007/0023513(A1) | 2007-02-01 | Andreasson et al. | Applicant |
| US2007/0074722(A1) | 2007-04-01 | Giroux et al. | Applicant |
| US2007/0150382(A1) | 2007-06-01 | Danilewitz | Applicant |
| US2007/0188306(A1) | 2007-08-01 | Tethrake et al. | Applicant |
| US2007/0200702(A1) | 2007-08-01 | Chung | Applicant |
| US2007/0213659(A1) | 2007-09-01 | Trovato et al. | Applicant |
| US2007/0213684(A1) | 2007-09-01 | Hickle et al. | Applicant |
| US2007/0229268(A1) | 2007-10-01 | Swan et al. | Examiner |
| US2008/0004908(A1) | 2008-01-01 | Oh et al. | Applicant |
| US2008/0012687(A1) | 2008-01-01 | Rubinstein | Applicant |
| US2008/0045930(A1) | 2008-02-01 | Makin et al. | Applicant |
| US2008/0122878(A1) | 2008-05-01 | Keefe et al. | Applicant |
| US2008/0128482(A1) | 2008-06-01 | Chen et al. | Applicant |
| US2008/0172253(A1) | 2008-07-01 | Chung et al. | Applicant |
| US2008/0191013(A1) | 2008-08-01 | Liberatore | Applicant |
| US2008/0218307(A1) | 2008-09-01 | Schoettle | Applicant |
| US2008/0243088(A1) | 2008-10-01 | Evans | Applicant |
| US2008/0270178(A1) | 2008-10-01 | McRae et al. | Applicant |
| US2008/0296373(A1) | 2008-12-01 | Zmood et al. | Applicant |
| US2008/0306772(A1) | 2008-12-01 | Shahrokh | Applicant |
| US2008/0316045(A1) | 2008-12-01 | Sriharto et al. | Applicant |
| US2009/0002173(A1) | 2009-01-01 | Bergsten et al. | Applicant |
| US2009/0020442(A1) | 2009-01-01 | Dietrich et al. | Applicant |
| US2009/0058653(A1) | 2009-03-01 | Geissler et al. | Applicant |
| US2009/0153290(A1) | 2009-06-01 | Bierach | Applicant |
| US2009/0164042(A1) | 2009-06-01 | Handfield et al. | Applicant |
| US2009/0231138(A1) | 2009-09-01 | Cheung et al. | Applicant |
| US2009/0267740(A1) | 2009-10-01 | Pizzuto et al. | Applicant |
| US2009/0267772(A1) | 2009-10-01 | Dehnadi | Applicant |
| US2009/0277815(A1) | 2009-11-01 | Kohl | Applicant |
| US2010/0036310(A1) | 2010-02-01 | Hillman | Applicant |
| US2010/0036678(A1) | 2010-02-01 | Bray | Applicant |
| US2010/0036755(A1) | 2010-02-01 | Saghbini | Applicant |
| US2010/0042439(A1) | 2010-02-01 | Martinez et al. | Applicant |
| US2010/0079337(A1) | 2010-04-01 | Hsu et al. | Applicant |
| US2010/0098425(A1) | 2010-04-01 | Kewitsch | Applicant |
| US2010/0108761(A1) | 2010-05-01 | Nycz et al. | Applicant |
| US2010/0114951(A1) | 2010-05-01 | Bauman et al. | Applicant |
| US2010/0185458(A1) | 2010-07-01 | Calderwood et al. | Applicant |
| US2010/0219097(A1) | 2010-09-01 | Ramasubramanian et al. | Applicant |
| US2010/0238039(A1) | 2010-09-01 | Tethrake et al. | Applicant |
| US2010/0268548(A1) | 2010-10-01 | Garrett et al. | Applicant |
| US2010/0275625(A1) | 2010-11-01 | Lowenstein | Applicant |
| US2010/0328474(A1) | 2010-12-01 | Hsieh | Applicant |
| US2011/0006879(A1) | 2011-01-01 | Bartos | Applicant |
| US2011/0063091(A1) | 2011-03-01 | Kang | Applicant |
| US2011/0068922(A1) | 2011-03-01 | Ross | Applicant |
| US2011/0093279(A1) | 2011-04-01 | Davison et al. | Applicant |
| US2011/0115612(A1) | 2011-05-01 | Kulinets et al. | Applicant |
| US2011/0125315(A1) | 2011-05-01 | Handfield et al. | Applicant |
| US2011/0139871(A1) | 2011-06-01 | Yturralde et al. | Applicant |
| US2011/0161112(A1) | 2011-06-01 | Keefe et al. | Applicant |
| US2011/0163871(A1) | 2011-07-01 | Einav et al. | Applicant |
| US2011/0166878(A1) | 2011-07-01 | Louie et al. | Applicant |
| US2011/0240729(A1) | 2011-10-01 | Schuck | Applicant |
| US2011/0270441(A1) | 2011-11-01 | Handfield et al. | Applicant |
| US2011/0291809(A1) | 2011-12-01 | Niemiec et al. | Applicant |
| US2011/0301446(A1) | 2011-12-01 | Kamen | Applicant |
| US2011/0313395(A1) | 2011-12-01 | Krulevitch et al. | Applicant |
| US2012/0041778(A1) | 2012-02-01 | Kraft | Applicant |
| US2012/0044054(A1) | 2012-02-01 | Hussain et al. | Applicant |
| US2012/0061463(A1) | 2012-03-01 | Burke | Applicant |
| US2012/0089411(A1) | 2012-04-01 | Srnka et al. | Applicant |
| US2012/0089418(A1) | 2012-04-01 | Kamath et al. | Applicant |
| US2012/0116798(A1) | 2012-05-01 | Heath et al. | Applicant |
| US2012/0125994(A1) | 2012-05-01 | Heath et al. | Applicant |
| US2012/0173440(A1) | 2012-07-01 | Becker et al. | Applicant |
| US2012/0177256(A1) | 2012-07-01 | Keefe et al. | Applicant |
| US2012/0179132(A1) | 2012-07-01 | Valk et al. | Applicant |
| US2012/0185951(A1) | 2012-07-01 | Bauman et al. | Applicant |
| US2012/0209619(A1) | 2012-08-01 | Knotts et al. | Applicant |
| US2012/0240067(A1) | 2012-09-01 | Bauman et al. | Applicant |
| US2012/0273087(A1) | 2012-11-01 | Einy et al. | Applicant |
| US2012/0278228(A1) | 2012-11-01 | Rubinstein | Applicant |
| US2012/0323208(A1) | 2012-12-01 | Bochenko et al. | Applicant |
| US2013/0038452(A1) | 2013-02-01 | Sawyer | Applicant |
| US2013/0041784(A1) | 2013-02-01 | Danilewitz | Applicant |
| US2013/0092727(A1) | 2013-04-01 | Edwards et al. | Applicant |
| US2013/0105568(A1) | 2013-05-01 | Jablonski et al. | Applicant |
| US2013/0221082(A1) | 2013-08-01 | Botten | Applicant |
| US2013/0221087(A1) | 2013-08-01 | Keefe et al. | Applicant |
| US2013/0327822(A1) | 2013-12-01 | Keefe et al. | Applicant |
| US2014/0060729(A1) | 2014-03-01 | Srnka et al. | Applicant |
| US2014/0117081(A1) | 2014-05-01 | Jablonski et al. | Applicant |
| US2014/0142975(A1) | 2014-05-01 | Keefe et al. | Applicant |
| US2014/0184390(A1) | 2014-07-01 | Elizondo, II | Applicant |
| US2014/0184391(A1) | 2014-07-01 | Elizondo, II | Applicant |
| US2014/0197954(A1) | 2014-07-01 | Caputo et al. | Applicant |
| US2014/0210596(A1) | 2014-07-01 | Hussain et al. | Applicant |
| US2014/0262919(A1) | 2014-09-01 | Hussain et al. | Applicant |
| US2014/0263614(A1) | 2014-09-01 | Keefe et al. | Applicant |
| US2014/0282197(A1) | 2014-09-01 | Keefe et al. | Applicant |
| US2014/0291397(A1) | 2014-10-01 | Caputo et al. | Applicant |
| US2014/0367080(A1) | 2014-12-01 | Hussain et al. | Applicant |
| CA2722328(A1) | 2009-10-01 | Applicant | |
| WO2095675(A1) | 2002-11-01 | Applicant | |
| WO3071943(A2) | 2003-09-01 | Applicant | |
| WO2006026246 | 2006-03-01 | Applicant | |
| WO2006135830(A2) | 2006-12-01 | Applicant | |
| WO2010074781(A2) | 2010-07-01 | Applicant | |
| WO2011115676(A2) | 2011-09-01 | Applicant | |
| WO2011150013(A2) | 2011-12-01 | Applicant |
Non-Patent Literature (16)
- C. O'Driscoll et al, “RFID: An Ideal Technology for Ubiquitous Computing?,” Dublin Institute of Technology School of Electronic and Communications Conference Papers, Jan. 1, 2008, pp. 1-17.Applicant
- Matthias Lampe et al., “The smart box application model,” Advances in pervasive computing, 2004, pp. 1-6.Applicant
- Shiou-Fen Tzeng et al., “Evaluating the business value of RFID: Evidence from five case studies,” International Journal of Production Economics 112 (2008) pp. 601-613.Applicant
- John Curtin et al., “Making the ‘MOST’ out of RFID technology: a research agenda for the study of the adoption, usage and impact of RFID,” Information Technology Management (Apr. 2007) 8 pp. 87-110.Applicant
- Chun-Liang Lai et al., “Enhancing Medication Safety and Reduce Adverse Drug Events on Inpatient Medication Administration using RFID,” WSEAS Transactions on Communications, Issue 10, vol. 7, Oct. 2008, pp. 1045-1054.Applicant
- Stephen Barlas, “Pharmacy Product Tracing Likely to Go National—Costs to Pharmacies Worrisome,” Pharmacy &Therapeutics, Jan. 2009, vol. 34 No. 1, p. 14.Applicant
- D. Belson, “Storage, Distribution, and Dispensing of Medical Supplies,” CREATE Interim Report Under FEMA Grant EMW-2004-GR-0112, Apr. 21, 2005, pp. 1-36.Applicant
- O.E. Cakiciet al., “Using RFID for the management of pharmaceutical inventory-system optimization and shrinkage control,” Decision Support Systems, 2011, pp. 842-852.Applicant
- Wang et al, “Applying RFID Technology to Develop a Distant Medical Care Service Platform,” International Journal of Electronic Business Management, (2010) vol. 8, No. 2, pp. 161-170.Applicant
- Peter Harrop et al., “RFID for Healthcare and Pharmaceuticals, 2008-2018,” Securing Pharma, May 2008, pp. 1-12.Applicant
- Stephanie Gonzalez, “Health Maintenance System (HMS) Hardware Research, Design, and Collaboration,” NASA USRP—Internship Final Report (2010), pp. 1-20.Applicant
- Crash Cart Inventory Checklist, Outpatient Surgery Magazine, Oct. 2004, “Outpatient Surgery” in 1 page, available at: http://www.outpatientsurgery.net/resources/forms/2004/pdf/OutpatientSurgeryMagazine—0410—crashCart.pdf.Applicant
- Medical Packaging Inc. Announces Clear Stem Flag Label System for Ampoules, Vials, and Syringes in 1 page (Feb. 1, 2006) available at: http://www.medpak.com/v1/news/20060201—CSFLAG.pdf.Applicant
- CPG Sec. 400.210, Radiofrequency Identification Feasibility Studies and Pilot Programs for Drugs Nov. 2004 Compliance Policy Guide available at: http://www.fda.gov/ICECI/ComplianceManuals/CompliancePolicyGuidanceManual/ucm074357.htm.Applicant
- U.S. Appl. No. 14/126,419, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, filed Dec. 14, 2013, Kress-Spatz, et al.Applicant
- U.S. Appl. No. 14/472,410, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents, filed Aug. 29, 2014, MacDonald, et al.Applicant