System and method for pharmaceutical management and tracking

A product inventory management system including a cabinet configured to contain an inventory of product units having RFID tags and further configured to monitor the inventory by wirelessly detecting the RFID tags, and a server system configured to communicate over a network with the cabinet, the server system capable of managing the inventory of the cabinet. There is also a method for product inventory management, including receiving, in a server system and via a network, inventory data from a cabinet, the inventory data corresponding to an inventory of product units stored in the cabinet, and generating an order to have additional product units added to the cabinet according to the cabinet inventory.

TECHNICAL FIELD

The present disclosure is directed, in general, to inventory management and tracking systems, and in particular to pharmaceutical management and tracking.

BACKGROUND

Product tracking is of importance to any manufacturing, distribution, or sales enterprise. It can be particularly important in the pharmaceutical area, where many products must be carefully identified and tracked from manufacture until administered to a patient. Typical known means of tracking pharmaceuticals involve manual record keeping and identifying products according to written labels. Inventory management and distribution also typically rely on a manual process of taking a physical inventory of product and manually ordering refills or restocking, while also eliminating product that is nearing or passed its expiry.

Another significant issue with pharmaceuticals is the very high cost of maintaining an inventory of expensive drugs. Some drugs can cost several thousand dollars per dose, and be relatively rarely needed, but these same drugs, when needed, are needed immediately. Pre-purchasing and stocking such drugs is a great expense for pharmacies and hospitals. Further, because of the high cost of these drugs, managing and tracking each product becomes essential.

There is, therefore, a need in the art for improved systems, methods, and apparatuses for inventory management and tracking systems, and in particular for pharmaceutical management and tracking.

SUMMARY

One disclosed embodiment includes a product inventory management system including a cabinet configured to contain an inventory of product units having RFID tags, a reader configured to monitor the inventory by wirelessly detecting the RFID tags, and a server configured to communicate over a network with the cabinet, the server capable of managing the inventory of the cabinet and of maintaining a product inventory list and a consumed product list according to the detected RFID tags.

Another disclosed embodiment includes a method for product inventory management, including receiving, in a server and via a network, data comprising each RFID tag associated with a product unit from a cabinet, the data corresponding to product units stored in the cabinet, creating a current inventory list comprising identifiers corresponding to the plurality of RFID tags, and generating an order to have additional product units added to the cabinet according to the cabinet inventory.

DETAILED DESCRIPTION

FIGS. 1 through 5, discussed below, and the various embodiments used to describe the principles disclosed in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles may be implemented in any suitably arranged device. The numerous innovative teachings of the present application will be described with particular reference to the presently preferred embodiment.

Various embodiments include a system and method for managing pharmaceutical inventories, and in particular to managing consigned pharmaceuticals in third-party facilities, such as hospital pharmacies. Various embodiments can use a product-management cabinet capable of tracking product inventory, and corresponding products. Before describing overall processes, it will be helpful to discuss various aspects of cabinets and products that can be used in implementing the processes.

One aspect of the disclosed embodiments concerns an innovative pharmaceutical cabinet used to store pharmaceutical inventory.FIG. 1depicts a simplified block diagram of a cabinet that can be used to implement the processes described herein.

The cabinet100, in a preferred embodiment, includes a refrigerated chassis110, but can be held at any required temperature, including cooled, frozen, ambient temperature, or even heated, using conventional means. For refrigerated or ambient-temperature use, a conventional refrigerator unit can be modified as described herein to function as the cabinet. For ambient-temperature use, a non-refrigerated cabinet can be used, or the refrigeration unit can be turned off or disconnected. In some embodiments, the cabinet includes a door that is substantially (or at least partially) transparent, or including a window, so that the product unit inventory can be easily viewed without opening the cabinet. The chassis110is configured to contain an inventory of product units having RFID tags.

The cabinet100also includes a reader120to wirelessly and automatically detect and identify the contents of the cabinet. Preferably, this is a radio-frequency identification (RFID) reader, known to those of skill in the art. The cabinet100includes one or more RFID antennas130connected to RFID reader120to scan the contents of the cabinet.

Preferably, the cabinet100also includes one or more optional sensor devices140, such as a thermometer, a door-open sensor; a power-failure sensor and optional backup power supply; a GPS locating device; and other devices, and one or more sensor devices140may communicate sensor data to the data processing system described below. In some embodiments, cabinet100also has an attached RFID tag.

The cabinet also includes a data processing system150capable of communicating with and controlling the RFID reader120. The cabinet data processing system150also includes communications software for communicating as described more fully below. The cabinet data processing system150is also preferably connected to communicate with and control the optional sensor devices140described above.

Cabinet data processing system150can be implemented using any appropriate technology and components, capable of operating as described herein, as known to those of skill in the art. The cabinet data processing system150generally includes at least a processor or controller and an accessible memory for storing data as described herein. The data processing system150is connected to communicate with the reader120and to maintain a product inventory list and a consumed product list according to the detected RFID tags as described herein.

Cabinet data processing system150is also connected to communicate with other devices using network interface160, which can be implemented using wired communications such as Ethernet or a telephone modem, or wireless communications such as GSM or IEEE 802.11, or a cable modem system, or otherwise, or a combination of these. Preferably, network interface160communicates using Internet Protocol. Network interface160allows the cabinet data processing system150to communicate with a server system such as the inventory management system, described below, and optionally with other cabinets100using mesh networking, direct cabling, or other technologies known to those of skill in the art. Communications between cabinet data processing system150and the inventory management system can be implemented using any suitable data communications technology, or a combination of them. In embodiments where multiple cabinets100communicate with each other, these can be configured to communicate with the inventory management system as a single unit with a combined inventory.

In use, the cabinet data processing system150will make periodic inventory scans, using the RFID reader120, to uniquely identify each product unit200(as shown inFIG. 2) stored in the cabinet. If a new identifier is found during any scan, the cabinet data processing system150notes the identifier and stores it to a current inventory list for that cabinet. Similarly, if a specific identifier is no longer detected during a periodic scan, because the product has been removed or the RFID tag has been destroyed, the cabinet data processing system150notes the missing identifier and removes it from the current inventory list for the cabinet. The identifiers of such removed products are also stored in a “consumed product” list in the cabinet data processing system.

The product inventory list comprises identifiers corresponding to detected RFID tags. The consumed product list comprises identifiers corresponding to RFID tags previously on the product inventory list that are not detected by the reader either immediately or after a predetermined amount of time.

In this way, the cabinet is configured to monitor the inventory by wirelessly detecting the RFID tags. The cabinet performs a periodic wireless scan to determine the current product units in the inventory, and can determine that a product unit has been removed from the inventory when the RFID tag corresponding to the product unit is not detected for a predetermined amount of time.

Of course, the references herein to the inventory list and consumed product list are not intended to specify a data structure for this information, as this information can be stored in any number of forms within the scope of the disclosed embodiments. “Lists” is simply used for convenient reference.

In alternate embodiments, cabinet100can also include a locking mechanism, or one or more individual locking compartments, to control access to the product. These locks can be any known technology, including keylocks, digital keypad locks, biometric locks, etc. Preferably, any locking device can also be opened remotely if the cabinet data processing system150receives such a command from the inventory management system.

Cabinet100can also include marketing or informational displays, either as a fixed display, or as a customizable electronic display. Similarly, cabinet100can include a display connected to cabinet data processing system150that is capable of displaying status or informational messages related to the status of the cabinet or the product inventory.

Preferably, cabinet100includes a power-failure detection device and a backup power supply. When a power failure is detected, cabinet100can sound an audible alarm, and can communicate with the inventory management system to notify it of a problem.

Product: In a preferred embodiment, the product consists of packaged pharmaceuticals, but of course the systems and methods described herein can be applied to other products.FIG. 2shows a simple illustration of a product unit200as can be used in various embodiments of the present disclosure. An important feature of the products, in a preferred embodiment, is that each product unit200includes an RFID tag230affixed to the product or its packaging, where the RFID tag230includes identifying information capable of being read by the RFID reader.

In a typical implementation, an individual product unit200includes the product210itself in an appropriate packaging220, such as a box. The packaging includes the RFID tag230, which seals the package. The RFID tag has at least a unique identifier, such as a serial number, that can be read by the RFID reader. Preferably, to open the package220to use the product210, the RFID tag230is destroyed, at which point it can no longer be read by the RFID reader.

For ease of reference, the term “serial number” will be used herein to refer to the unique identifier, although those of skill in the art will recognize that any other style of unique identifier can be used.

As will be understood by those of skill in the art, the product unit200represents a generic product. There can be one or more actual products210identified as a product unit200, and preferably packaged together. For example, in the pharmaceutical context, a single dose, pill, or pre-filled syringe can be a single product210, but multiple ones of these can be packaged together as a single product unit200, depending on the requirements for using, dispensing, or billing for the product210.

Inventory management system: An inventory management system300is used to control the inventory in multiple cabinets100.FIG. 3depicts a simplified diagram of an inventory management system300, in accordance with an embodiment of the present disclosure, including server system310, warehouse system320, management system330, and multiple cabinets100, all communicating via network340. Network340can be implemented using any known networking technology, as a public or private network or as direct communications, and is preferably implemented using the Internet to communicate between each system. Network340can be implemented using multiple technologies, and can be implemented using multiple separate networks.

Server system310, warehouse system320, management system330, while depicted as single, individual systems in this simplified figure, can each be implemented using one or more data processing systems, which can be commonly located but are not necessarily so. For example, as known to those of skill in the art, different functions of server system310may be more efficiently performed using separate data processing systems, each performing specific tasks but connected to communicate with each other in such a way as to together perform the functions described herein for the server system310as a whole. Similarly, one or more of server system310, warehouse system320, and management system330could be implemented as an integrated system as opposed to distinct and separate systems.

Server system310performs overall inventory management functions for multiple cabinets100, as described in more detail below with regard to the overall process. In general, server system310communicates with cabinets100to monitor the inventory of each cabinet100on a regular basis. Server system310can also monitor other status information of each cabinet100according to sensor devices140. Server system310includes a database of the current inventory of each cabinet100, the product inventory assigned to each cabinet100, and other information regarding the cabinets100.

Server system310also tracks all product units200from time of purchase and receiving into a warehouse, to shipment placement in a cabinet100, to storage in cabinet100, to removal from cabinet100. Server system310will periodically receive communications from each cabinet100including the current inventory list, the consumed product list, and other information. These communications can be initiated by server system310, by polling each of the cabinets100, or can be initiated by the cabinets100.

Server system310preferably includes a web server interface to allow management using a standard web browser interface. Preferably, at least some data sent and received by server system310is in XML format. Server system310maintains at least one database for product inventory data; in a preferred embodiment, this database is an SQL database.

Server system310can also generate billing and invoice data according to the reports from cabinets100of product units200that are delivered (added to the current inventory list) or consumed (added to the consumed inventory list).

In various embodiments, the server system310is capable of creating an order to have additional product units added to the cabinet according to the cabinet inventory. In some cases, the product units in the cabinet inventory are consignment product units, and the server system310creates an invoice when the product units are removed from the inventory. The server system310is further capable, in some embodiments, of receiving cabinet status data from the cabinet, and sending cabinet control instructions to the cabinet. The server system310is further capable, in some embodiments, of analyzing product consumption data according to inventory data received from the cabinet, as described below.

Warehouse system320is connected to communicate with server system310. Warehouse system320is configured to receive inventory management orders from server system310, to have inventory shipped or delivered for placement in a cabinet100. Warehouse system320is also preferably capable of reading the RFID tags of the product units200to identify exactly which product units are being shipped to a given destination. In alternate embodiments, warehouse system320is also configured to produce RFID tags for labeling product units200.

Management system330is preferably a data processing system configured to connect with server system310to allow a user to manage the functions of server system310and the processes it controls. Management system330can preferably be implemented using a common data processing system including a standard internet browser, connected to allow the user to connect to a web server interface on server system310.

FIG. 4depicts a flowchart of a first process in accordance with a disclosed embodiment. Various embodiments include an inventory management process that provides monitoring, tracking, and billing functions for product units200in cabinets100. In this way, each cabinet100can function as a “virtual warehouse” of product units200located at each product location, such as hospital pharmacies. This process is particularly useful when the product is not sold when shipped for placement in a cabinet, but rather is held on consignment in the cabinet, and considered sold when removed from the cabinet or the product packaging.

In particular, the embodiments described herein can be used for high-dollar injectable pharmaceuticals, which a pharmacy may desire to have readily available but may not be willing or able to pre-purchase. In this case, the consignment product in the “virtual warehouse” cabinet functions to answer a significant and immediate need in the industry.

According to one process, product units200are first designated to be transferred from a warehouse to a cabinet100(step405). Of course, this process is performed for any number of cabinets100, but for simplicity of description, the process will be described with reference to only one cabinet100.

The warehouse system320will record the serial numbers of each product unit shipped to the cabinet100, along with an identifier of cabinet100(step410), which may be the RFID tag serial number of the cabinet100, if it were so tagged. Warehouse system320can preferably record each of these serial numbers by performing an RFID scan of all product units being shipped to the cabinet100.

When the product units are shipped (step415), warehouse system320will notify server system310that the product units200have shipped, the destination cabinet100of the product units200, and the serial numbers of the RFID tags of each of the shipped product units200(step420), and any other inventory management data.

Server system310, in turn, periodically communicates with cabinet100. At some point after shipment, the shipped product units200will be delivered to and placed within cabinet100at a customer site. Cabinet100will detect the serial numbers of the RFID tags of each of the product units, and add those to the current inventory list (step425). Cabinet100will communicate the current inventory list to server system310, which will update a status record for each corresponding serial number (step430).

In implementations where there is a direct sale of the product, server system310can generate a billing invoice for the customer either when the product units200are shipped or when they are detected within cabinet100, depending on the terms of the customer contract, or at another appropriate time (step440, see also below).

When the cabinet100no longer detects a given RFID serial number of a product unit200, that serial number is added to the consumed product list and eventually reported to server system310, as described above (step435). Typically, this will be when the product unit100is opened and the product is consumed, but it can also happen when the RFID tag is destroyed when the packaging is opened, or if the product is otherwise removed, stolen, destroyed, etc.

In a preferred embodiment, a particular product unit is not moved to the consumed product list immediately when it is not detected, but only when it has not been detected for a significant period, such as 24, 48, or 72 hours. This is to accommodate the event that the product unit200is removed from cabinet100in anticipation of use, but is not actually consumed, and so is returned to the cabinet100and is thereafter detected by cabinet100.

In an implementation where the product is in the cabinet on consignment, server system310can generate a billing invoice for the customer when the product units200are placed on the consumed product list (step440).

Server system310continues to monitor the inventory of cabinet100on a periodic basis. As products are consumed, server system310updates its inventory and performs any necessary billing procedures (step445).

When server system310determines that the number of product units200in cabinet100for a given product has fallen below a predetermined threshold, server system310will preferably send a purchase order (for direct sales) or transfer purchase order (for consignment sales) to warehouse system320(step450). Warehouse system320will process a new delivery of the required product to the cabinet (e.g., returning to step405). That is, when the server system determines that a cabinet is running low on a specific product, it will preferably automatically generate an order for the warehouse system to replenish the supply.

Also, in preferred embodiments and particularly in pharmaceutical implementations, the server system310will maintain pedigree and expiry information for each product unit200, associated with the product unit serial number. In the event of a product recall or product that is nearing its expiration in a cabinet, the server system310can produce an order for the product to be removed or replaced in the cabinet (step455), and adjust its inventory and billing records when the replacement is reported by the cabinet.

In alternate embodiments, the temperature and other parameters of the cabinet100can be directly modified by cabinet data processing system150. Further, server system310can send appropriate commands to cabinet data processing system150to change the cabinet parameters. In this way, for example, server system310can determine the optimal cabinet parameters according to the current cabinet inventory, and thereafter modify the parameters accordingly (step460).

Server system310can also track product units200indicated as shipped by warehouse system320but that are not timely detected by the destination cabinet100. When this occurs, server system310can send an appropriate notice to an operator, the customer, or other appropriate person or system. By reference to the status information of the carrier contracted to deliver the product units, server system310can also determine whether the product was delivered to the customer location but never placed by the customer in the cabinet100. According to the provisions of a customer contract, server system310can optionally automatically bill the customer for such product units that are never placed in the destination cabinet.

According to other embodiments, server system310can also communicate with physicians and other individuals using electronic mail, text messaging to mobile telephones or PDAs, paging, or in other ways known to those of skill in the art (step465). These communications can be real-time, such as text messaging or paging, or can be delayed. In particular embodiments, these messages can be used to provide updates of product inventory to individuals regarding the particular cabinets in their facility, to advise of new stock or to warn of low product inventory. These messages can be combined with advertisement or promotional material, for example to promote the use and benefits of particular products stocked or available to be stocked in the cabinet.

In other embodiments, product inventory data can be analyzed and/or aggregated by server system310(step470) in order to determine and predict product usage trends. For example, in the pharmaceutical context, server system310can determine the general rate at which any particular product is used in a particular cabinet, and thereby determine an optimum inventory level for that product to meet ongoing and emergent needs. Further, server system310can use aggregate data to determine how much product should be ordered and stocked in warehouses, and to determine what drugs are most often used and in what contexts, among other information.

FIG. 5depicts a flowchart of a second process in accordance with a disclosed embodiment. In this process, each cabinet100can again function as a “virtual warehouse” of product units200located at each product location, such as hospital pharmacies. This process is particularly useful when the product is not sold when shipped for placement in a cabinet, but rather is held on consignment in the cabinet.

In particular, the embodiments described can be used for high-dollar injectable pharmaceuticals, which a pharmacy may desire to have readily available but may not be willing or able to pre-purchase. In this case, the consignment product in the “virtual warehouse” cabinet functions to answer a significant and immediate need in the industry.

In a disclosed process, at some point product units200are delivered to and placed within cabinet100at a customer site (step505). Cabinet100wirelessly scans its contents to detect the serial numbers of the RFID tags of each of the product units (step510), and add those to the current inventory list (step515). Cabinet100will communicate the current inventory list to server system310(step520). Cabinet100will also communicate the consumed inventory list to server system310(step525). Server system310will update a status record for each corresponding serial number (step530).

Cabinet100continues to periodically wirelessly scan its contents as in step505above. When the cabinet100no longer detects a given RFID serial number of a product unit200, that serial number is added to the consumed product list (step535), and can be removed from the current inventory list. The consumed list and updated current inventory list are eventually reported to server system310, as described above (step540). Typically, this will be when the product unit100is opened and the product is consumed, but it can also happen when the RFID tag is destroyed when the packaging is opened, or if the product is otherwise removed, stolen, destroyed, etc.

In some embodiments, a particular product unit is not moved to the consumed product list immediately when it is not detected, but only when it has not been detected for a significant period, such as 24, 48, or 72 hours. This is to accommodate the event that the product unit200is removed from cabinet100in anticipation of use, but is not actually consumed, and so is returned to the cabinet100and is thereafter detected by cabinet100.

In some embodiments, the temperature and other parameters of the cabinet100can be directly modified by cabinet data processing system150. Further, server system310can send appropriate commands to cabinet data processing system150to change the cabinet parameters. In this way, for example, server system310can determine the optimal cabinet parameters according to the current cabinet inventory, and thereafter modify the parameters accordingly. Cabinet100sends cabinet status data to server system310(step545) indicating the current status of the cabinet and inventory, such as that determined by any sensor devices140. Cabinet100receives cabinet control instructions from server310(step550), and adjusts the cabinet parameters accordingly (step555).

In various embodiments, a cabinet's current inventory list is reconstructed each time the cabinet scans its contents. The consumed inventory list is not routinely cleared by the cabinet until its contents have been sent to the server system. In some embodiments, the cabinet will receive an instruction from the server to clear the consumed inventory list, and will do so (step560).

The systems and techniques described herein, while particularly described in a pharmaceutical context, are of course not limited to pharmaceuticals. Those of skill in the art will recognize that these techniques can be applied to any number of other products, with particular utility in managing inventory of consumable products such as drugs, foods, drinks, liquors, etc.

It is important to note that while the present disclosure has been described in the context of a fully functional system, those skilled in the art will appreciate that at least portions of the mechanism of the present disclosure are capable of being distributed in the form of a instructions contained within a machine usable medium in any of a variety of forms, and that the present disclosure applies equally regardless of the particular type of instruction or signal bearing medium utilized to actually carry out the distribution. Examples of machine usable mediums include: nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), user-recordable type mediums such as floppy disks, hard disk drives and compact disk read only memories (CD-ROMs) or digital versatile disks (DVDs), and transmission type mediums such as digital and analog communication links.