WO2014100324A1

WO2014100324A1 - Product inventory information sharing system and method

Info

Publication number: WO2014100324A1
Application number: PCT/US2013/076369
Authority: WO
Inventors: Chris Flori
Original assignee: Amerisourcebergen Specialty Group
Priority date: 2012-12-19
Filing date: 2013-12-19
Publication date: 2014-06-26
Also published as: BR112015014865A2; EP2936463A1; US20140172651A1; CA2896024A1; EP2936463A4; BR112015014865A8; AU2013361402B2; US9767429B2; CA2896024C; AU2013361402A1; JP2016503206A

Abstract

A product inventory sharing system (100) includes a product management device (102, 200) in communication with a server (104). The product management device is configured to store one or more product units (300) each configured with a corresponding one or more RFID tags (302), and monitor an inventory of the product units by wirelessly detecting the RFID tags. The server is configured to periodically receive product information from the product management device, the product information comprising inventory data, store the product information, and transmit the product information to a network node (106) associated with at least one vested entity (108) associated with the product units.

Description

PRODUCT INVENTORY INFORMATION SHARING SYSTEM AND METHOD

TECHNICAL FIELD

[0001] The present disclosure is generally related to inventory management and tracking systems, and more particularly, to a product inventory sharing system and method.

BACKGROUND

[0002] 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.

[0003] Another significant issue with pharmaceuticals is the 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.

SUMMARY

[0004] According to one embodiment, a product inventory sharing system includes a product management device in communication with a server. The product management device is configured to store one or more product units each configured with a corresponding one or more RFID tags, and monitor an inventory of the product units by wirelessly detecting the RFID tags. The server is configured to periodically receive product information from the product management device, the product information comprising inventory data, store the product information, and transmit the product information to a network node associated with at least one vested entity associated with the product units.

[0005] According to another embodiment, a product inventory sharing method includes storing one or more product units each configured with a corresponding one or more RFID tags, and monitoring an inventory of the product units by wirelessly detecting the RFID tags. The method also includes periodically receiving product information from the product management device, the product information comprising inventory data, storing the product information, and transmitting the product information to a network node associated with at least one vested entity associated with the product units. [0006] According to yet another embodiment, a product inventory sharing system includes a server configured to periodically receive product information, store the product information, and transmit the product information to a network node associated with at least one vested entity associated with the product units. The product information includes inventory data from a cabinet. The cabinet is configured to store one or more pharmaceutical units each configured with a corresponding one or more RFID tags, and monitor an inventory of the product units by wirelessly detecting the RFID tags. The pharmaceutical units comprising one or more pharmaceutical units are configured to treat an ailment of a patient.

[0007] Before undertaking the DETAILED DESCRIPTION OF THE INVENTION below, it may be advantageous to set forth definitions of certain words or phrases used throughout this patent document: the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or" is inclusive, meaning and/or; the phrases "associated with" and "associated therewith," as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term "controller" means any device, system or part thereof that controls at least one operation, whether such a device is implemented in hardware, firmware, software or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, and those of ordinary skill in the art will understand that such definitions apply in many, if not most, instances to prior as well as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, wherein like numbers designate like objects, and in which:

[0009] FIGURE 1 illustrates an example network topology of a product inventory sharing system according to embodiments of the present disclosure;

[0010] FIGURE 2 illustrates an example cabinet according to embodiments of the present disclosure;

[0011] FIGURE 3 illustrates an example product unit according to embodiments of the present disclosure;

[0012] FIGURE 4 illustrates an example user input device that may be used with the cabinet of FIGURE 2 according to embodiments of the present disclosure; and

[0013] FIGURE 5 illustrates an example process for sharing product information according to embodiments of the present disclosure .

DETAILED DESCRIPTION

[0014] FIGURES 1 through 5, discussed below, and the various embodiments used to describe the principles of the present disclosure 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 of the present disclosure may be implemented in any suitably arranged device. The numerous innovative teachings of the present application will be described with particular reference to the presented embodiments .

[0015] Embodiments of the present disclosure include a system and method for sharing product inventories with one or more entities vested in the use of the product for which the inventory is maintained. Various embodiments may use a product management cabinet that tracks or otherwise maintains an ongoing status of the product inventory, and a server that stores the product inventory for use by the one or more vested entities .

[0016] FIGURE 1 illustrates an example network topology of a product inventory sharing system 100 according to one embodiment of the present disclosure. Product information sharing system 100 includes a product management device 102, a server 104, and one or more network nodes 106 of one or more corresponding vested entities 108 that communicate through a network 110, such as the Internet. The product management device 102 stores and maintains an inventory of one or more product units. As will be described in detail below, the server 104 periodically receives product information from the product management device 102 through the network 110. The server 104 stores the product information, and transmits the product information to network nodes 106 associated with one or more vested entities 108 associated with the product units.

[0017] Products stored in product management device 102 may be any suitable type for which an ongoing, relatively up-to- date inventory may be maintained and shared with any entities vested in the product. In certain embodiments, the product may be a pharmaceutical product that treats an ailment of a patient. In a particular embodiment, the product may be pharmaceutical product that is adapted to treat chronic ailments of a patient, such as, for example, a patient diagnosed with hemophilia. In other embodiments, the product may include pharmaceutical products adapted for treatment of other types of ailments.

[0018] The vested entities 108 may include those entities having a vested interest in the use and administration of the product. For products such as pharmaceutical products, these vested entities may include a user of the pharmaceutical product (i.e., the patient), a payer of the pharmaceutical product (i.e., an insurance provider), a manufacturer of the pharmaceutical product, a caregiver who administers the pharmaceutical (i.e., a doctor), and a pharmacy that provides the pharmaceutical product to the patient.

[0019] Each vested entity 108 may receive up-to-date inventory information via its associated network node 106. The network nodes 106 may be any computing system having one or more processors that execute instructions stored in a memory. Examples of such a computing system include personal computers, mainframe computers, laptop computers, personal digital assistants, cellular telephones, and the like.

[0020] In one embodiment, the network node 106 used by a vested entity 108 may periodically receive product inventory information from the product management device 102 via the server 104. In another embodiment, the network node transmits the product information to at least one vested entity associated with the product units in response to a request for the inventory information from the vested entity.

[0021] Access to the product information may be protected from illicit access via an authentication process. For example, the server 104 may use a password protected login session to restrict access to only registered vested entities 108. As another example, the server 104 may use a public- private key authentication architecture for automated, periodic access to information by network nodes used by each vested entity 108. [0022] In certain embodiments, the server 104 may maintain an account for each vested entity such that the type and level of product information may be allocated independently for each vested entity 108. For an example in which the product is a pharmaceutical product, a payer of the product, such as a medical insurance provider, may wish to maintain an accurate status of the amount of product used for cost purposes, while a caregiver, such as a doctor, may wish to know symptoms associated with the use of the product. Thus, the account associated with the payer may be allocated to receive only product use information, while the caregiver may be allocated to receive product use information as well as any symptom related information associated with the use of the pharmaceutical product.

[0023] In certain embodiments, information transmitted through the network 110 may be encrypted to maintain its integrity and/or to thwart its illicit use. For example, the encryption of information may reduce the possibility of its modification by sniffing packets transmitted by the product management device 102 and spoofing these packets with illicit data. As another example, the information may be encrypted for compliance with certain governmental privacy requirements, such as the Health Insurance Portability and Accountability Act (HIPAA) , which requires that only certain authorized entities have access to medical records of the patient that uses the product management device 102.

[0024] Network 110 can be implemented using any known networking technology, such as a public or private network or as direct communications, and is may be implemented using the Internet to communicate between each system. Network 110 can be implemented using multiple technologies, and can be implemented using multiple separate networks.

[0025] Although the product information sharing system 100 as shown and described includes a single product management device 102, other embodiments of the product information sharing system may include multiple product management devices 102. The server 104 may perform an overall inventory management functions for these multiple cabinets 100. In general, server 104 communicates with the product management device 102 to monitor its inventory on a regular basis. Server 104 can also monitor other status information of each product management device 102 according to one or more sensor devices configured in the product management device 102. Server 104 includes a database that maintains a current inventory of the product, the product inventory assigned to the product management device 102, and other information regarding the product management device 102.

[0026] Server 104 may also track all products from time of purchase and receiving into a warehouse, to shipment placement in the product management device 102, to storage in product management device 102, to removal from product management device 102. Server 104 will periodically receive communications from each product management device 102 including the current inventory list, the consumed product list, and other information. These communications can be initiated by server 104, by polling of the product management device 102, or can be initiated by the product management device 102.

[0027] Server 104 may include a web server interface to allow management using a standard web browser interface. At least some data sent and received by server 104 may be in extensible markup language (XML) format. Server 104 maintains at least one database for product inventory data, which in a particular embodiment, is a structured query language (SQL) database .

[0028] Server 104 can also generate billing and invoice data according to the reports from product management device 102 of a product that is delivered (added to the current inventory list) or consumed (added to the consumed inventory list) .

[0029] In various embodiments, the server 104 may create an order to have additional product added to the product management device 102 according to its inventory. In some cases, the product in the inventory includes consignment product units, and the server 104 creates an invoice when the product is removed from the inventory. The server 104 may be further configured to, in some embodiments, receive status data from the product management device 102, and send control instructions to the product management device 102. The server 104 may be further configured to, in some embodiments, analyze product consumption data according to inventory data received from the product management device 102, as described below.

[0030] Although FIGURE 1 illustrates one example product information sharing system 100 for sharing product information with one or more vested entities 108, various changes may be made to FIGURE 1. For example, in some embodiments, product information may be stored in a memory configured in the product management device 102 and periodically downloaded to a portable memory device, such as a flash memory card, which is then physically transported to, and accessed by a network node of a vested entity such that the communication network may not be necessary. In other embodiments, for security reasons, the product information may not be stored in the product management device 102. In yet other embodiments, the product management device 102, server 104, and network nodes 106 administered by the vested entities 108 may exist as a single computing system in which communication of product information may be provided by internal system calls between each of its users. [0031] FIGURE 2 illustrates an example cabinet 200 according to the teachings of the present disclosure. In an embodiment, the cabinet 200 functions as the product management device 102 as described above with reference to FIGURE 1. The cabinet .200 has an internal storage space 202 for storage of one or more product units 300 (FIGURE 3) . The cabinet 200 may include a refrigeration and/or heating system for maintaining a temperature of the storage space at any desired temperature. For refrigerated use, a conventional refrigerator unit can be modified as described herein. For ambient-temperature use, a non-refrigerated cabinet can be used, or the refrigeration unit can be turned off or disconnected .

[0032] The cabinet 200 also includes a reader 204 to wirelessly and automatically detect and identify the contents of the cabinet 200. In one embodiment, the reader 204 is a radio-frequency identification (RFID) reader. The cabinet 200 includes one or more RFID antennas 206 coupled to the RFID reader 204 that scans the contents of the cabinet.

[0033] The cabinet 200 also includes one or more optional sensor devices 208, such as a thermometer, a door-open sensor, a power-failure sensor and optional backup power supply, a GPS locating device, and other devices. In some embodiments, the cabinet 200 also has an attached RFID tag. [0034] The cabinet 200 also includes a data processing system 210 that communicates with and controls the RFID reader 204. The cabinet data processing system 210 also includes communications software for communicating as described in detail below. The cabinet data processing system 210 also communicates with and controls the optional sensor devices 208 described above.

[0035] The data processing system 210 may be implemented using any appropriate technology and components, configured to operate as described herein. The cabinet data processing system 210 generally includes one or more processors and one or more memory units for storing data as described herein.

[0036] Cabinet also includes a network interface 212 for communication with other devices, such as the server 104 and/or network nodes 106 of vested entities 108 (See FIGURE 1) . The network interface 212 may be implemented using a wired communication medium such as an Ethernet or a telephone modem, or wireless communication medium such as a Global System for Mobile (GSM) communications architecture, Wi-Fi network (e.g., IEEE 802.11), a cable modem system, or any combination of these. In a particular embodiment, network interface 212 communicates using an Internet Protocol. Network interface 212 allows the cabinet data processing system 210 to communicate with the server 104, and optionally with other cabinets 200 using a mesh networking topology, direct cabling, or other technologies. Communications between cabinet data processing system 210 and the server 104 may be implemented using any suitable data communications technology, or any combination thereof. In embodiments where multiple cabinets 200 communicate with each other, they can be configured to communicate with the server 104 as a single unit with a combined inventory.

[0037] In use, the cabinet data processing system 210 performs periodic inventory scans, using the RFID reader 204, to uniquely identify each product unit 300 (See FIGURE 3) stored in the cabinet. If a new identifier is found during any scan, the cabinet data processing system 210 notes 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 damaged, the cabinet data processing system 210 notes 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.

[0038] In this manner, the cabinet 200 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 determines 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.

[0039] 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. The term "Lists" is simply used for convenient reference.

[0040] In certain embodiments, cabinet 200 may 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 key locks, digital keypad locks, biometric locks, etc. The locking device can also be opened remotely if the cabinet data processing system 210 receives such a command from a particular node of the product inventory sharing system 100.

[0041] The cabinet 200 may also include marketing or informational displays, either as a fixed display, or as a customizable electronic display. Similarly, the cabinet 200 can include a display connected to cabinet data processing system 210 that displays status or informational messages related to the status of the cabinet or the product inventory.

[0042] The cabinet 200 may include a power-failure detection device and a backup power supply. When a power failure is detected, the cabinet 200 may generate an audible alarm, and can communicate with the server 104 to notify the existence of a problem.

[0043] FIGURE 3 illustrates an example product unit 300 according to the teachings of the present disclosure. The product unit 200 described herein is configured for storage of pharmaceutical products; however, the systems and methods described herein can be applied to other products. Each product unit 300 includes an RFID tag 302 affixed to the product or its packaging, where the RFID tag 302 includes identifying information capable of being read by the RFID reader .

[0044] In a typical implementation, an individual product unit 300 includes the product 304 itself in an appropriate packaging 306, such as a box. The packaging includes the RFID tag 302 that 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 package 306 for use of the product 304, the RFID tag 302 is damaged, at which point it can no longer be read by the RFID reader.

[0045] 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 suitable style of unique identifier can be used.

[0046] Although the product unit 300 generally represents a generic product, there can be one or more actual products 304 identified as a product unit 300, which are packaged together. For example, in the pharmaceutical context, a single dose, pill, or pre-filled syringe can comprise a single product 304, but multiple ones of these can be packaged together as a single product unit 300, depending on the requirements for using, dispensing, or billing for the product 304.

[0047] FIGURES 2 and 3 illustrate one example cabinet 200 and product unit 300, however, various changes may be made to FIGURES 2 and 3. For example, RFID tag 302 may wirelessly communicate with reader 204 of the cabinet 200 using any suitable protocol. Additionally, the packaging 320 may be any suitable type, such as a bottle, jar, or a disposable capsule for containing the product 304.

[0048] FIGURE 4 illustrates an example user input device 400 that may be used with the cabinet 200 of FIGURE 2 according to one embodiment of the present disclosure. The user input device 400 may be disposed on an outer surface of the cabinet 200 and configured to receive patient data associated with one or more ailments of the patient. Entry of patient data may be provided by one or more fields 402, 404, 406, 408, 410, and 412 displayed on the user input device 400. The patient data may be stored by the server 104 and transmitted to network nodes 106 of the vested entities 108.

[0049] The user input device 400 may include a refreshable display device, such as a touch screen that receives input as well as provides a display under the control of a controller, such as the data processing system (See FIGURE 2) . The user input device 400 may be configured on a door of the cabinet for entry of patient data each time the door of the cabinet 200 is opened for access of one or more product units 300.

[0050] In an embodiment, the user input device 400 includes a Linux-based personal computing tablet that is installed on a refrigerator unit. Use of the personal computing tablet may provide a refreshable display of the user input device 400 for alternatively displaying different fields for corresponding different product units.

[0051] The cabinet 200 may include a door lock that maintains the door of the cabinet in a locked condition until all patient data is entered through the user input device 400. In this manner, a relatively quality level of patient data may be maintained for accurate analysis of the patient's condition .

[0052] As a failsafe feature, in the event of an emergency, such as a catastrophic fault of the data processing system 210, or a condition in which the patient is generally incoherent, the lock may be disabled such that access may be provided even when all patient data is not inputted into user input device 400. For example, the door lock may be biased in the unlocked position and locked only when electrical power is actively provided to the door lock. Thus, access to the inner space of the cabinet 200 may be provided by merely unplugging the power cord to the cabinet such that energizing power for locking the door of the cabinet is removed. When power is again applied at a later time, the RFID reader 204 may again rectify the inventory of product units 300 and send notification to one or more vested entities that the failsafe condition was used to access one or more product units .

[0053] The user input device 400 includes one or more fields that may be selected by the patient each time the patient desires to access a product unit from the cabinet 200. The example user input device 400 shown in FIGURE 4 includes fields that provide entry of patient data that may be particularly beneficial for hemophiliac patients. Nevertheless, the user input device 400 may include fields that provide for entry of any suitable type of patient data.

[0054] With regard to the particular example user input device 400 shown, fields include a bleed location entry field 402, a bleed location display field 404, a time to treat field 406, a pain rating field 408, and several control buttons 410 and 412 that allow clearing of entered data in the fields and entry for a "no bleed" condition, respectively. Each of these entry fields is generally associated with a hemophiliac medical condition. Nevertheless, it should be understood that any suitable type and number of fields may be displayed on the user input device 400 for entry of patient data associated with any type of medical condition each time a product unit 300 (e.g., a pharmaceutical product) is accessed or removed from the cabinet 200.

[0055] Although FIGURE 4 illustrates one example user input device 400 that may be used with the cabinet 200 of FIGURE 2, various changes may be made to FIGURE 4. For example, the user input device 400 may also be configured remotely from the cabinet 200 such that patient data, which is entered on the user input device 400, may be wirelessly transmitted to the data processing system. Alternatively, the user input device 400 may be electrically coupled to the cabinet via a cord, such as an Ethernet cable, in which patient data is transferred from the user input device 400 to the data processing, system 210.

[0056] FIGURE 5 illustrates an example process for sharing product information according to certain embodiments of the present disclosure. In step 502, the process is initiated.

[0057] In step 504, one or more products units are stored in a product management device. The product management device may include a cabinet that is configured with a user input device for entry of patient information each time a product unit is removed from or added to the cabinet.

[0058] In step 506, the product management device monitors an ongoing inventory of the product units using RFID tags configured on each product unit stored in the cabinet. In one embodiment, the product units include a pharmaceutical product that is adapted to treat an ailment of a patient.

[0059] In step 508, a server in communication with the product management device periodically receives product information from the product management device. The product information may include inventory data associated with a quantity of product units currently in the cabinet as well as historical information associated with the previous removal of product units. The product information may also include patient data associated with one or more symptoms or medical conditions of the patient that is entered through the user input device each time a product unit is accessed by the patient .

[0060] In step 510, the server stores the obtained product information. The obtained product information may include inventory data, clinical data, or both. In one embodiment, patient data may be correlated with inventory data to generate additional information about a health or ongoing medical condition of the patient. For example, a rate of usage may be generated according to a quantity of pharmaceutical product used over a given period of time. As another example, patterns associated with certain periods of increased and/or decreased usage, such as increased usage during weekends, or decreased usage at nighttime may be determined according to the correlated patient data and inventory data. Using this additional information, vested entities, such as caregivers may provide enhanced medical treatment of the patient.

[0061] In one embodiment, the server may include a database for storage of the product information and patient information. The database may aggregate and organize the product information and patient information according to one or more criteria that may be useful to one or more of the vested entities. For example, the database may correlate an amount of medical product used by a particular patient with the patient's medical insurance information, and may further include triggers that send appropriate messages to a vested entity through the network, such as a payer of the product, when certain usage levels are exceeded.

[0062] As another example, the database may aggregate clinical data, including product information and patient information, in a manner useful to a caregiver (e.g., doctor) by correlating patient-specific data from a number of patients, such as how frequently each patient uses the medical product in relation to symptoms. In a specific example of a hemophiliac patient, the user input device may include fields for entry of patient information associated with bleed occurrences, location (s) of these bleed occurrences, and/or levels of pain during these bleed occurrences. The database may correlate such information with specific usage of the medical product such that the caregiver may identify ongoing patterns associated with specific locations of the patient's body, such as how quickly does the patient treat themselves in response to the occurrence, what level of pain is most common, and the like. Such ongoing patterns may be associated with one patient or across multiple patients. The information may be correlated in such a manner that would be useful to a caregiver for further diagnosis and/or treatment of each patient .

[0063] As yet another example, the database may aggregate the product information (including inventory data, clinical data, or both) in a manner useful to a manufacturer of the product. In a specific example in which the product is a medical product, the product information may be organized in a manner suitable for comparison with earlier clinical studies conducted during the development phase of the medical product, such as those studies conducted during development with mice or other non-human life-forms.

[0064] In step 512, the server transmits the product information to one or entities vested in the product units . Examples of vested entities may include a payer of the pharmaceutical product, a manufacturer of the pharmaceutical product, a caregiver who administers the pharmaceutical product, a pharmacy that provided the pharmaceutical product, and a user of the pharmaceutical product. [0065] In one embodiment, a network node may include a portable wireless device, such as a cellular telephone or personal digital assistant (PDA) , for remote entry of patient data. The network node may include executable software that displays fields for entry of patient data in a similar manner as shown in FIGURE 4. Additionally, the executable software may include a mobile application ("app") that may be executed under an operating system, such as the Android™ operating system executed on the wireless device, such as a smartphone.

[0066] Certain embodiments of the wireless device configured with such a mobile app may provide accurate reporting and storage of patient data even when the patient does not have ready access to the cabinet for an extended period of time. For example, a patient wishing to go on vacation for an extended period of time may remove a sufficient quantity of product units that are anticipated to be used during the extended period of time. The portable wireless device may be configured with a user input screen similar to that shown above with respect to FIGURE 4 such that, each time a dose of the pharmaceutical product is taken, the patient data may be entered into the portable wireless device and transmitted to the server.

[0067] In one embodiment, the server transmits the inventory information in response to a request for the inventory information from a network node associated with the vested entity. That is, the inventory information is transmitted to the vested entity upon a request for such information. In another embodiment, the server periodically transmits the inventory information to the network node of the vested entity. That is, the server may implement a push-type protocol in which product information is automatically transmitted to certain vested entities at recurring time periods. In either case, access to the product information may be restricted to an authentication process such that only qualified entities may receive such information.

[0068] Use of the product information sharing method as described above may be continued throughout medical treatment of the patient. When use of the product information sharing system is no longer needed or desired, the process ends in step 514.

[0069] 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 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.

[0070] While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of the disclosure, as defined by the following claims.

Claims

WHAT IS CLAIMED IS:

1. A product inventory sharing system comprising:

a product management device configured to:

store one or more product units each configured with a corresponding one or more RFID tags; and

monitor an inventory of the product units by wirelessly detecting the RFID tags; and

a server configured to:

periodically receive product information from the product management device, the product information comprising inventory data;

store the product information; and

transmit the product information to a network node associated with at least one vested entity associated with the product units .

2. The product inventory sharing system of Claim 1, wherein the one or more product units comprise one or more pharmaceutical units configured to treat an ailment of a patient .

3. The product inventory sharing system of Claim 2, wherein the product management device comprises:

a cabinet configured to store the one or more pharmaceutical units; and

a user input device on the outer surface of the cabinet and configured to receive patient data associated with the ailment of the patient, the product information comprising the patient data.

4. The product inventory sharing system of Claim 3, further comprising a computing system disposed in the cabinet, wherein the user input device comprises one or more entry fields configured to receive the patient data, and

wherein the computing system is configured to maintain a door of the cabinet in a locked condition until the one or more entry fields have been entered by the patient.

5. The product inventory sharing system of Claim 1, wherein the at least one vested entity comprises one or more of a payer of the pharmaceutical unit, a manufacturer of the pharmaceutical unit, a caregiver who administers the pharmaceutical unit, a pharmacy that provides the pharmaceutical unit, and a user of the pharmaceutical unit.

6. The product inventory sharing system of Claim 5, wherein the product information further comprises clinical data .

7. The product inventory sharing system of Claim 1, wherein the server is configured to transmit the product information in response to a request for the product information from the network node of the vested entity.

8. The product inventory sharing system of Claim 1, wherein the server is configured to periodically transmit the product information to the network node of the vested entity.

9. The product inventory sharing system of Claim 1 wherein the server is configured to correlate the patient dat with the inventory data to generate additional info about health of the patient.

10. A product inventory sharing method comprising:

storing one or more product units each configured with a corresponding one or more RFID tags;

monitoring an inventory of the product units by wirelessly detecting the RFID tags;

periodically receiving product information from the product management device, the product information comprising inventory data;

storing the product information; and

transmitting the product information to a network node associated with at least one vested entity associated with the product units.

11. The product inventory sharing method of Claim 10, wherein the one or more product units comprise one or more pharmaceutical units configured to treat an ailment of a patient .

12. The product inventory sharing method of Claim 11, further comprising:

storing the one or more pharmaceutical units in a cabinet; and

receiving, via a user input device configured on the cabinet, patient data associated with the ailment of the patient, the product information comprising the patient data.

13. The product inventory sharing method of Claim 12, further comprising:

receiving the patient data via one or more entry fields configured on the user input device; and

maintaining a door of the cabinet in a locked condition until the one or more entry fields have been entered by the patient.

14. The product inventory sharing method of Claim 10, wherein the at least one vested entity comprises one or more of a payer of the pharmaceutical unit, a manufacturer of the pharmaceutical unit, a caregiver who administers the pharmaceutical unit, a pharmacy that provided the pharmaceutical unit, and a user of the pharmaceutical unit.

15. The product inventory sharing method of Claim 14, wherein the product information further comprises clinical data .

16. The product inventory sharing method of Claim 10, wherein the server transmits the product information in response to a request for the product information from the network node of the vested entity.

17. The product inventory sharing method of Claim 10, wherein the server periodically transmits the product information to the network node of the vested entity.

18. The product inventory sharing method of Claim 10, wherein the server correlates the patient data with the inventory data to generate additional info about a health of the patient.

19. A product inventory sharing system comprising:

a server configured to:

periodically receive product information comprising inventory data from a cabinet, the cabinet configured to store one or more pharmaceutical units each configured with a corresponding one or more RFID tags, and monitor an inventory of the product units by wirelessly detecting the RFID tags, the pharmaceutical units comprising one or more pharmaceutical units configured to treat an ailment of a patient;

store the product information; and

20. The product inventory sharing system of Claim 19, wherein the product management device comprises: