U.S. patent application number 14/738684 was filed with the patent office on 2015-10-01 for system and method for pharmaceutical management and tracking.
The applicant listed for this patent is AmerisourceBergen Specialty Group, Inc.. Invention is credited to Dale Danilewitz.
Application Number | 20150278755 14/738684 |
Document ID | / |
Family ID | 38092793 |
Filed Date | 2015-10-01 |
United States Patent
Application |
20150278755 |
Kind Code |
A1 |
Danilewitz; Dale |
October 1, 2015 |
SYSTEM AND METHOD FOR PHARMACEUTICAL MANAGEMENT AND TRACKING
Abstract
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.
Inventors: |
Danilewitz; Dale;
(Haverford, PA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
AmerisourceBergen Specialty Group, Inc. |
Frisco |
TX |
US |
|
|
Family ID: |
38092793 |
Appl. No.: |
14/738684 |
Filed: |
June 12, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13647737 |
Oct 9, 2012 |
|
|
|
14738684 |
|
|
|
|
11607832 |
Dec 1, 2006 |
8285607 |
|
|
13647737 |
|
|
|
|
60741631 |
Dec 2, 2005 |
|
|
|
Current U.S.
Class: |
705/28 |
Current CPC
Class: |
G08B 13/2434 20130101;
G06K 7/10366 20130101; G07F 9/026 20130101; G06K 7/1413 20130101;
G07G 1/009 20130101; G16H 40/20 20180101; G06Q 30/04 20130101; G16H
40/63 20180101; G16H 20/10 20180101; G07G 1/0036 20130101; G08B
13/2462 20130101; G06F 16/9554 20190101; G06K 19/0723 20130101;
G06K 7/1417 20130101; G06K 19/06037 20130101; G06Q 10/087 20130101;
G06Q 10/08 20130101 |
International
Class: |
G06Q 10/08 20060101
G06Q010/08; G06K 7/10 20060101 G06K007/10; G06Q 30/04 20060101
G06Q030/04 |
Claims
1. A system comprising: a cabinet configured to contain a plurality
of pharmaceutical product units, each of the pharmaceutical product
units having a radio frequency identification (RFID) tag
identifying the respective pharmaceutical product unit, the cabinet
comprising a reader configured to detect each of the pharmaceutical
product units within the cabinet by detecting the associated RFID
tag; and at least one server configured to: communicate over a
network with the cabinet to receive information regarding the RFID
tags detected by the cabinet, based on the received RFID tag
information, determine whether a first of the pharmaceutical
product units in the cabinet has been removed from the cabinet and
whether the first pharmaceutical product unit has been returned to
the cabinet, and in response to determining that the first
pharmaceutical product unit has been removed from the cabinet and
then has not been returned to the cabinet prior to an expiration of
a predetermined period of time, generate data for billing a
customer for the first pharmaceutical product unit.
2. The system of claim 1, wherein the predetermined period of time
is 24 hours.
3. The system of claim 1, wherein the cabinet is configured to
periodically read the RFID tags within the cabinet and transmit the
RFID tag information to the at least one server, and wherein the
RFID tag information comprises first RFID tag information
corresponding to RFID tags detected by the cabinet at a first time
and second RFID tag information corresponding to RFID tags detected
by the cabinet at a second time.
4. The system of claim 1, wherein the at least one server is
configured to monitor status information associated with the
cabinet based upon a door-open sensor, and wherein the status
information includes the RFID tag information.
5. The system of claim 1, wherein the at least one server is
configured to not generate the data for billing the customer if the
first pharmaceutical product unit is returned to the cabinet prior
to the expiration of the predetermined period of time.
6. The system of claim 1, wherein the at least one server is
configured to determine when the first pharmaceutical product unit
has been removed from the cabinet based on a failure of the cabinet
to detect a first of the RFID tags corresponding to the first
pharmaceutical product unit.
7. The system of claim 1, wherein the pharmaceutical product units
comprise pharmaceutical product units delivered to the customer on
consignment.
8. The system of claim 1, wherein each of at least one of the
pharmaceutical product units comprises a pharmaceutical product
unit that when opened renders a corresponding RFID tag unreadable
by the cabinet.
9. A system comprising: a cabinet located within a customer
facility for a customer, the cabinet configured to contain one or
more pharmaceutical product units available for use by the
customer, each of the one or more pharmaceutical product units
having a radio frequency identification (RFID) tag with an RFID tag
identifier identifying a respective one of the one or more
pharmaceutical product units, the cabinet comprising: a reader
configured to detect each pharmaceutical product unit within the
cabinet by wirelessly reading the RFID tag identifier from the
associated RFID tag, and an interface configured to communicate
over a network; and at least one server configured to: communicate
over the network with the cabinet to receive RFID tag identifiers
for RFID tags detected by the cabinet, based on the RFID tag
identifiers, determine that a first of the one or more
pharmaceutical product units has been placed within the cabinet,
subsequently removed from the cabinet, and, following removal from
the cabinet, not returned to the cabinet prior to an expiration of
a predetermined period of time, and in response to the first
pharmaceutical product unit not having been returned to the cabinet
prior to the expiration of the predetermined period of time
following removal of the first pharmaceutical product unit from the
cabinet, list at least a product identifier for the first
pharmaceutical product unit for use in billing the customer for the
first pharmaceutical product unit.
10. The system of claim 9, wherein the at least one server is
further configured to: maintain an inventory of the one or more
pharmaceutical product units based upon the RFID tag identifiers
received from the cabinet, based upon the inventory, create an
order to have one or more additional pharmaceutical product units
shipped for placement in the cabinet, and determine when any of the
one or more additional pharmaceutical product units are placed in
the cabinet.
11. The system of claim 9, wherein, in response to the first
pharmaceutical product unit having not been returned to the cabinet
prior to the expiration of the predetermined period of time
following removal of the first pharmaceutical product unit from the
cabinet, the at least one server is configured to list the product
identifier for the first pharmaceutical product unit on a consumed
products list.
12. The system of claim 9, wherein the at least one server is
further configured to transmit invoice data for invoicing the
customer for the first pharmaceutical product unit subsequent to
the expiration of the predetermined period of time.
13. The system of claim 9, wherein the at least one server is
further configured to: determine that the first pharmaceutical
product unit has been returned to the cabinet.
14. The system of claim 9, wherein the at least one server is
configured to periodically receive, from the cabinet, RFID tag
information for the one or more pharmaceutical product units within
the cabinet and status information associated with the cabinet.
15. The system of claim 14, wherein the status information includes
a temperature within the cabinet.
16. The system of claim 9, wherein the first pharmaceutical product
unit is associated with a first of the RFID tags having a first of
the RFID tag identifiers on an inventory for the cabinet, and
wherein the at least one server is configured to determine that the
first pharmaceutical product unit has been removed from the cabinet
based upon an absence of the first RFID tag identifier from first
RFID tag information received at the at least one server from the
cabinet.
17. The system of claim 16, wherein the at least one server is
configured to determine that the first pharmaceutical product unit
has been returned to the cabinet based upon a presence of the first
RFID tag identifier within second RFID tag information received at
the at least one server from the cabinet subsequent to receipt of
the first RFID tag information at the at least one server.
18. The system of claim 9, wherein the interface is configured to
communicate over the network using at least one of an Ethernet
connection, a wireless local area network connection, and a mobile
telecommunications connection.
19. The system of claim 9, wherein the at least one server is
configured to maintain expiration information in association with
the RFID tag identifier for each of the one or more pharmaceutical
product units within the cabinet, and to produce an order for
removal of an expired one of the one or more pharmaceutical product
units from the cabinet.
20. The system of claim 9, wherein the at least one server is
further configured to determine if one or more additional
pharmaceutical product units shipped from a warehouse to the
customer facility are not placed in the cabinet following the
shipment from the warehouse.
21. A system comprising: a cabinet within a customer facility
configured to contain a plurality of pharmaceutical product units
delivered on consignment to a customer, each of the pharmaceutical
product units having a radio frequency identification (RFID) tag
identifying the respective pharmaceutical product unit, the cabinet
comprising a reader configured to detect each of the pharmaceutical
product units within the cabinet by detecting the associated RFID
tag; and at least one server configured to: communicate over a
network with the cabinet to receive information regarding the RFID
tags detected by the cabinet, maintain an inventory of the
pharmaceutical product units associated with the cabinet based upon
contents of the cabinet as determined from the RFID tag information
received from the cabinet, determine that a first of the
pharmaceutical product units on the inventory has been removed from
the cabinet, maintain an association of the first pharmaceutical
product unit with the cabinet for at least a predetermined period
after the first pharmaceutical product unit was removed from the
cabinet, and transfer identification data for the first
pharmaceutical product unit to a list for billing the customer for
the first pharmaceutical product unit subsequent to an expiration
of the predetermined period after the first pharmaceutical product
unit was removed from the cabinet.
22. The system of claim 21, wherein the predetermined period is 24
hours.
23. The system of claim 21, wherein, if the first pharmaceutical
product unit on the inventory is returned to the cabinet prior to
the expiration of the predetermined period after the first
pharmaceutical product unit was removed from the cabinet, the
identification data for the first pharmaceutical product unit is
not transferred to the list for billing the customer.
24. The system of claim 23, wherein the at least one server is
configured to: receive, from the cabinet, first RFID tag
information for the one or more pharmaceutical product units within
the cabinet and first status information associated with the
cabinet for a first time, second RFID tag information for the one
or more pharmaceutical product units within the cabinet and second
status information associated with the cabinet for a second time
subsequent to the first time, and third RFID tag information for
the one or more pharmaceutical product units within the cabinet and
third status information associated with the cabinet for a third
time subsequent to the second time, determine, from the first and
second RFID tag information, that the first pharmaceutical product
unit was removed from the cabinet, and determine, from the second
and third RFID tag information, that the first pharmaceutical
product unit was not returned to the cabinet.
25. The system of claim 24, wherein the first, second and third
status information include temperatures within the cabinet, and
wherein the at least one server is configured to produce an order
for removal of the first pharmaceutical product unit from the
cabinet in response to the first pharmaceutical product unit
becoming unusable.
26. A system comprising: a cabinet within a customer facility
configured to contain one or more pharmaceutical product units
delivered on consignment to a customer, each of the one or more
pharmaceutical product units distinguishable by a radio frequency
identification (RFID) tag on a respective one of the one or more
pharmaceutical product units, the cabinet configured to read the
one or more RFID tags on the one or more pharmaceutical product
units within the cabinet and communicate one or more identifiers
read from the one or more RFID tags over a network; and at least
one server configured to: receive from the cabinet the one or more
identifiers read from the one or more RFID tags on the one or more
pharmaceutical product units within the cabinet, monitor
temperature information for the cabinet from status information
received over the network from the cabinet, maintain a database of
the one or more identifiers received from the cabinet for the one
or more pharmaceutical product units within the cabinet, expiration
information for each of the one or more pharmaceutical product
units within the cabinet, and the temperature information for the
cabinet, determine that a first of the one or more pharmaceutical
product units was placed in the cabinet, determine that the first
pharmaceutical product unit was removed from the cabinet, determine
that the first pharmaceutical product unit was returned to the
cabinet, determine whether a time between removal of the first
pharmaceutical product unit from the cabinet and return of the
first pharmaceutical product unit to the cabinet exceeds a
predetermined duration of time, and generate an order for removal
of the first pharmaceutical product unit from the cabinet for
disposal in response to the first pharmaceutical product unit
becoming unusable.
27. The system of claim 26, wherein the at least one server is
configured to determine that the first pharmaceutical product unit
is unusable based upon a product recall or expiration of the first
pharmaceutical product unit.
28. The system of claim 26, wherein the at least one server is
configured to produce an order for additional pharmaceutical
product units.
29. The system of claim 26, wherein the at least one server is
configured, if a time between removal of the first pharmaceutical
product unit from the cabinet and return of the first
pharmaceutical product unit to the cabinet exceeds the
predetermined duration of time, to generate data for billing the
customer for the first pharmaceutical product unit.
30. The system of claim 26, wherein the at least one server is
further configured to determine if one or more additional
pharmaceutical product units shipped from a warehouse to the
customer facility are not placed in the cabinet following the
shipment from the warehouse.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. Non-Provisional
patent application Ser. No. 13/647,737 filed Oct. 9, 2012 and
entitled "SYSTEM AND METHOD FOR PHARMACEUTICAL MANAGEMENT AND
TRACKING," which is a continuation of U.S. Non-Provisional patent
application Ser. No. 11/607,832 filed Dec. 1, 2006 and entitled
"SYSTEM AND METHOD FOR PHARMACEUTICAL MANAGEMENT AND TRACKING," now
U.S. Pat. No. 8,285,607. This application also claims the benefit
of the filing date of U.S. Provisional Patent Application No.
60/741,631 filed Dec. 2, 2005 and entitled "SYSTEM AND METHOD FOR
PHARMACEUTICAL MANAGEMENT AND TRACKING." The contents of each of
these are hereby incorporated by reference into this application as
if fully set forth herein.
TECHNICAL FIELD
[0002] The present disclosure is directed, in general, to inventory
management and tracking systems, and in particular to
pharmaceutical management and tracking.
BACKGROUND
[0003] 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.
[0004] 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.
[0005] 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
[0006] 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.
[0007] 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.
[0008] The foregoing has outlined rather broadly the features and
technical advantages of the present disclosure so that those
skilled in the art may better understand the detailed description
that follows. Additional features and advantages of the subject
matter of the disclosure will be described hereinafter that form
the subject of the claims. Those skilled in the art will appreciate
that they may readily use the conception and the specific
embodiment disclosed as a basis for modifying or designing other
structures for carrying out the same purposes of the present
disclosure. Those skilled in the art will also realize that such
equivalent constructions do not depart from the spirit and scope of
the disclosure in its broadest form.
[0009] Before undertaking the DETAILED DESCRIPTION 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
[0010] 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:
[0011] FIG. 1 depicts a simplified block diagram of a cabinet in
accordance with an embodiment of the present disclosure;
[0012] FIG. 2 illustrates a product unit as can be used in various
embodiments of the present disclosure;
[0013] FIG. 3 depicts a simplified diagram of an inventory
management system in accordance with an embodiment of the present
disclosure;
[0014] FIG. 4 depicts a flowchart of a first process in accordance
with a disclosed embodiment; and
[0015] FIG. 5 depicts a flowchart of a second process in accordance
with a disclosed embodiment.
DETAILED DESCRIPTION
[0016] 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.
[0017] 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.
[0018] One aspect of the disclosed embodiments concerns an
innovative pharmaceutical cabinet used to store pharmaceutical
inventory. FIG. 1 depicts a simplified block diagram of a cabinet
that can be used to implement the processes described herein.
[0019] The cabinet 100, in a preferred embodiment, includes a
refrigerated chassis 110, 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 chassis 110 is configured to contain an inventory of
product units having RFID tags.
[0020] The cabinet 100 also includes a reader 120 to 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 cabinet 100 includes one or
more RFID antennas 130 connected to RFID reader 120 to scan the
contents of the cabinet.
[0021] Preferably, the cabinet 100 also includes one or more
optional sensor devices 140, 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
devices 140 may communicate sensor data to the data processing
system described below. In some embodiments, cabinet 100 also has
an attached RFID tag.
[0022] The cabinet also includes a data processing system 150
capable of communicating with and controlling the RFID reader 120.
The cabinet data processing system 150 also includes communications
software for communicating as described more fully below. The
cabinet data processing system 150 is also preferably connected to
communicate with and control the optional sensor devices 140
described above.
[0023] Cabinet data processing system 150 can 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 system 150 generally includes at least a
processor or controller and an accessible memory for storing data
as described herein. The data processing system 150 is connected to
communicate with the reader 120 and to maintain a product inventory
list and a consumed product list according to the detected RFID
tags as described herein.
[0024] Cabinet data processing system 150 is also connected to
communicate with other devices using network interface 160, 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 interface 160 communicates using
Internet Protocol. Network interface 160 allows the cabinet data
processing system 150 to communicate with a server system such as
the inventory management system, described below, and optionally
with other cabinets 100 using mesh networking, direct cabling, or
other technologies known to those of skill in the art.
Communications between cabinet data processing system 150 and the
inventory management system can be implemented using any suitable
data communications technology, or a combination of them. In
embodiments where multiple cabinets 100 communicate with each
other, these can be configured to communicate with the inventory
management system as a single unit with a combined inventory.
[0025] In use, the cabinet data processing system 150 will make
periodic inventory scans, using the RFID reader 120, to uniquely
identify each product unit 200 (as shown in FIG. 2) stored in the
cabinet. If a new identifier is found during any scan, the cabinet
data processing system 150 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 destroyed,
the cabinet data processing system 150 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.
[0026] 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.
[0027] 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.
[0028] 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.
[0029] In alternate embodiments, cabinet 100 can 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 system 150 receives such a
command from the inventory management system.
[0030] Cabinet 100 can also include marketing or informational
displays, either as a fixed display, or as a customizable
electronic display. Similarly, cabinet 100 can include a display
connected to cabinet data processing system 150 that is capable of
displaying status or informational messages related to the status
of the cabinet or the product inventory.
[0031] Preferably, cabinet 100 includes a power-failure detection
device and a backup power supply. When a power failure is detected,
cabinet 100 can sound an audible alarm, and can communicate with
the inventory management system to notify it of a problem.
[0032] 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. 2 shows a
simple illustration of a product unit 200 as can be used in various
embodiments of the present disclosure. An important feature of the
products, in a preferred embodiment, is that each product unit 200
includes an RFID tag 230 affixed to the product or its packaging,
where the RFID tag 230 includes identifying information capable of
being read by the RFID reader.
[0033] In a typical implementation, an individual product unit 200
includes the product 210 itself in an appropriate packaging 220,
such as a box. The packaging includes the RFID tag 230, 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 package 220 to use the product 210, the RFID tag 230 is
destroyed, at which point it can no longer be read by the RFID
reader.
[0034] 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.
[0035] As will be understood by those of skill in the art, the
product unit 200 represents a generic product. There can be one or
more actual products 210 identified as a product unit 200, and
preferably packaged together. For example, in the pharmaceutical
context, a single dose, pill, or pre-filled syringe can be a single
product 210, but multiple ones of these can be packaged together as
a single product unit 200, depending on the requirements for using,
dispensing, or billing for the product 210.
[0036] Inventory management system: An inventory management system
300 is used to control the inventory in multiple cabinets 100. FIG.
3 depicts a simplified diagram of an inventory management system
300, in accordance with an embodiment of the present disclosure,
including server system 310, warehouse system 320, management
system 330, and multiple cabinets 100, all communicating via
network 340. Network 340 can 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. Network 340 can be implemented
using multiple technologies, and can be implemented using multiple
separate networks.
[0037] Server system 310, warehouse system 320, management system
330, 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 system 310 may 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 system 310 as a whole. Similarly, one or more of server
system 310, warehouse system 320, and management system 330 could
be implemented as an integrated system as opposed to distinct and
separate systems.
[0038] Server system 310 performs overall inventory management
functions for multiple cabinets 100, as described in more detail
below with regard to the overall process. In general, server system
310 communicates with cabinets 100 to monitor the inventory of each
cabinet 100 on a regular basis. Server system 310 can also monitor
other status information of each cabinet 100 according to sensor
devices 140. Server system 310 includes a database of the current
inventory of each cabinet 100, the product inventory assigned to
each cabinet 100, and other information regarding the cabinets
100.
[0039] Server system 310 also tracks all product units 200 from
time of purchase and receiving into a warehouse, to shipment
placement in a cabinet 100, to storage in cabinet 100, to removal
from cabinet 100. Server system 310 will periodically receive
communications from each cabinet 100 including the current
inventory list, the consumed product list, and other information.
These communications can be initiated by server system 310, by
polling each of the cabinets 100, or can be initiated by the
cabinets 100.
[0040] Server system 310 preferably includes a web server interface
to allow management using a standard web browser interface.
Preferably, at least some data sent and received by server system
310 is in XML format. Server system 310 maintains at least one
database for product inventory data; in a preferred embodiment,
this database is an SQL database.
[0041] Server system 310 can also generate billing and invoice data
according to the reports from cabinets 100 of product units 200
that are delivered (added to the current inventory list) or
consumed (added to the consumed inventory list).
[0042] In various embodiments, the server system 310 is 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 system 310 creates an invoice when the
product units are removed from the inventory. The server system 310
is further capable, in some embodiments, of receiving cabinet
status data from the cabinet, and sending cabinet control
instructions to the cabinet. The server system 310 is further
capable, in some embodiments, of analyzing product consumption data
according to inventory data received from the cabinet, as described
below.
[0043] Warehouse system 320 is connected to communicate with server
system 310. Warehouse system 320 is configured to receive inventory
management orders from server system 310, to have inventory shipped
or delivered for placement in a cabinet 100. Warehouse system 320
is also preferably capable of reading the RFID tags of the product
units 200 to identify exactly which product units are being shipped
to a given destination. In alternate embodiments, warehouse system
320 is also configured to produce RFID tags for labeling product
units 200.
[0044] Management system 330 is preferably a data processing system
configured to connect with server system 310 to allow a user to
manage the functions of server system 310 and the processes it
controls. Management system 330 can 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 system 310.
[0045] FIG. 4 depicts 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 units 200 in cabinets 100. In
this way, each cabinet 100 can function as a "virtual warehouse" of
product units 200 located 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.
[0046] 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.
[0047] According to one process, product units 200 are first
designated to be transferred from a warehouse to a cabinet 100
(step 405). Of course, this process is performed for any number of
cabinets 100, but for simplicity of description, the process will
be described with reference to only one cabinet 100.
[0048] The warehouse system 320 will record the serial numbers of
each product unit shipped to the cabinet 100, along with an
identifier of cabinet 100 (step 410), which may be the RFID tag
serial number of the cabinet 100, if it were so tagged. Warehouse
system 320 can preferably record each of these serial numbers by
performing an RFID scan of all product units being shipped to the
cabinet 100.
[0049] When the product units are shipped (step 415), warehouse
system 320 will notify server system 310 that the product units 200
have shipped, the destination cabinet 100 of the product units 200,
and the serial numbers of the RFID tags of each of the shipped
product units 200 (step 420), and any other inventory management
data.
[0050] Server system 310, in turn, periodically communicates with
cabinet 100. At some point after shipment, the shipped product
units 200 will be delivered to and placed within cabinet 100 at a
customer site. Cabinet 100 will detect the serial numbers of the
RFID tags of each of the product units, and add those to the
current inventory list (step 425). Cabinet 100 will communicate the
current inventory list to server system 310, which will update a
status record for each corresponding serial number (step 430).
[0051] In implementations where there is a direct sale of the
product, server system 310 can generate a billing invoice for the
customer either when the product units 200 are shipped or when they
are detected within cabinet 100, depending on the terms of the
customer contract, or at another appropriate time (step 440, see
also below).
[0052] When the cabinet 100 no longer detects a given RFID serial
number of a product unit 200, that serial number is added to the
consumed product list and eventually reported to server system 310,
as described above (step 435). Typically, this will be when the
product unit 100 is 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.
[0053] 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 unit 200 is removed from cabinet 100 in
anticipation of use, but is not actually consumed, and so is
returned to the cabinet 100 and is thereafter detected by cabinet
100.
[0054] In an implementation where the product is in the cabinet on
consignment, server system 310 can generate a billing invoice for
the customer when the product units 200 are placed on the consumed
product list (step 440).
[0055] Server system 310 continues to monitor the inventory of
cabinet 100 on a periodic basis. As products are consumed, server
system 310 updates its inventory and performs any necessary billing
procedures (step 445).
[0056] When server system 310 determines that the number of product
units 200 in cabinet 100 for a given product has fallen below a
predetermined threshold, server system 310 will preferably send a
purchase order (for direct sales) or transfer purchase order (for
consignment sales) to warehouse system 320 (step 450). Warehouse
system 320 will process a new delivery of the required product to
the cabinet (e.g., returning to step 405). That is, when the server
system determines that a cabinet is running low on a specific
product, will preferably automatically generate an order for the
warehouse system to replenish the supply.
[0057] Also, in preferred embodiments and particularly in
pharmaceutical implementations, the server system 310 will maintain
pedigree and expiry information for each product unit 200,
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 system 310 can produce an order for the product
to be removed or replaced in the cabinet (step 455), and adjust its
inventory and billing records when the replacement is reported by
the cabinet.
[0058] In alternate embodiments, the temperature and other
parameters of the cabinet 100 can be directly modified by cabinet
data processing system 150. Further, server system 310 can send
appropriate commands to cabinet data processing system 150 to
change the cabinet parameters. In this way, for example, server
system 310 can determine the optimal cabinet parameters according
to the current cabinet inventory, and thereafter modify the
parameters accordingly (step 460).
[0059] Server system 310 can also track product units 200 indicated
as shipped by warehouse system 320 but that are not timely detected
by the destination cabinet 100. When this occurs, server system 310
can 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 system 310 can also determine whether the product was
delivered to the customer location but never placed by the customer
in the cabinet 100. According to the provisions of a customer
contract, server system 310 can optionally automatically bill the
customer for such product units that are never placed in the
destination cabinet.
[0060] According to other embodiments, server system 310 can 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 (step 465). 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.
[0061] In other embodiments, product inventory data can be analyzed
and/or aggregated by server system 310 (step 470) in order to
determine and predict product usage trends. For example, in the
pharmaceutical context, server system 310 can 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 system
310 can 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.
[0062] FIG. 5 depicts a flowchart of a second process in accordance
with a disclosed embodiment. In this process, each cabinet 100 can
again function as a "virtual warehouse" of product units 200
located 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.
[0063] 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.
[0064] In a disclosed process, at some point product units 200 are
delivered to and placed within cabinet 100 at a customer site (step
505). Cabinet 100 wirelessly scans its contents to detect the
serial numbers of the RFID tags of each of the product units (step
510), and add those to the current inventory list (step 515).
Cabinet 100 will communicate the current inventory list to server
system 310 (step 520). Cabinet 100 will also communicate the
consumed inventory list to server system 310 (step 525). Server
system 310 will update a status record for each corresponding
serial number (step 530).
[0065] Cabinet 100 continues to periodically wirelessly scan its
contents as in step 505 above. When the cabinet 100 no longer
detects a given RFID serial number of a product unit 200, that
serial number is added to the consumed product list (step 535), and
can be removed from the current inventory list. The consumed list
and updated current inventory list are eventually reported to
server system 310, as described above (step 540). Typically, this
will be when the product unit 100 is 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.
[0066] 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 unit 200 is removed from cabinet 100 in anticipation of
use, but is not actually consumed, and so is returned to the
cabinet 100 and is thereafter detected by cabinet 100.
[0067] In some embodiments, the temperature and other parameters of
the cabinet 100 can be directly modified by cabinet data processing
system 150. Further, server system 310 can send appropriate
commands to cabinet data processing system 150 to change the
cabinet parameters. In this way, for example, server system 310 can
determine the optimal cabinet parameters according to the current
cabinet inventory, and thereafter modify the parameters
accordingly. Cabinet 100 sends cabinet status data to server system
310 (step 545) indicating the current status of the cabinet and
inventory, such as that determined by any sensor devices 140.
Cabinet 100 receives cabinet control instructions from server 310
(step 550), and adjusts the cabinet parameters accordingly (step
555).
[0068] 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 (step
560).
[0069] 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.
[0070] Those skilled in the art will recognize that, for simplicity
and clarity, the full structure and operation of all systems
suitable for use with the present disclosure is not being depicted
or described herein. Instead, only so much of a data processing
system as is unique to the present disclosure or necessary for an
understanding of the present disclosure is depicted and described.
The remainder of the construction and operation of these systems
may conform to any of the various current implementations and
practices known in the art.
[0071] 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.
[0072] Although an exemplary embodiment of the present disclosure
has been described in detail, those skilled in the art will
understand that various changes, substitutions, variations, and
improvements of the subject matter disclosed herein may be made
without departing from the spirit and scope of the disclosure in
its broadest form.
[0073] None of the description in the present application should be
read as implying that any particular element, step, or function is
an essential element which must be included in the claim scope: THE
SCOPE OF PATENTED SUBJECT MATTER IS DEFINED ONLY BY THE ALLOWED
CLAIMS. Moreover, none of these claims are intended to invoke
paragraph six of 35 USC .sctn.112 unless the exact words "means
for" are followed by a participle.
* * * * *