JP2020129200A - Inventory management device, inventory management method and program - Google Patents

Abstract

To make inventory management of medicines available in a dispensing pharmacy.SOLUTION: Based on a first usage quantity of medicines to which a first code is given and which is included in dispensing data stored in a dispensing data storage unit 101 and a second code included in handling item data stored in a handling item data storage unit 104, a first calculation unit 106 calculates a second usage quantity of medicines for each packaging unit for sale. A second calculation unit 108 calculates expected inventory figures of the medicines for each packaging unit for sale based on the second usage amount calculated by the first calculating unit 106. An inventory data storage unit 105 stores inventory data indicating the inventory figures calculated by the second calculation unit 108.SELECTED DRAWING: Figure 3

Description

The present invention relates to an inventory management device, an inventory management method and a program.

In general, a dispensing pharmacy dispenses a drug (medicine) based on a prescription issued by a hospital to a patient.

However, if the drug required for dispensing is insufficient in the dispensing pharmacy, it may not be possible to dispense even if the patient comes to the dispensing pharmacy with a prescription.

In order to avoid such a situation, it is necessary for the dispensing pharmacy to keep track of the inventory of pharmaceuticals, but the number of pharmaceuticals handled by the dispensing pharmacy is enormous, and the inventory of pharmaceuticals should be managed accurately It's not easy.

JP, 2004-062607, A

Therefore, an object of the present invention is to provide an inventory management device, an inventory management method, and a program capable of managing the inventory of medicines in a dispensing pharmacy.

According to one aspect of the present invention, the inventory management device includes a first storage unit, a second storage unit, a first calculation unit, a second calculation unit, and a fourth storage unit. The first storage means stores dispensing data including a first code given to a drug dispensed at a dispensing pharmacy and a first usage amount of the drug in the dispensing. The second storage means stores handling item data including a second code given to the medicine in the packaging unit for sale handled in the dispensing pharmacy. The first calculation means is the first usage amount of the medicine to which the first code included in the dispensing data stored in the first storage means is added, and the handling item data stored in the second storage means. The second usage amount of the medicine is calculated for each of the sales packaging units based on the second code included in. The second calculating means calculates the expected stock quantity of the medicine for each of the packaging units for sale based on the calculated second usage amount. The fourth storage means stores inventory data indicating the calculated inventory quantity.

The invention makes it possible to manage the inventory of medicines in dispensing pharmacies.

The figure which shows an example of a structure of the inventory management system in 1st Embodiment of this invention. The figure which shows an example of the hardware constitutions of an inventory management apparatus. FIG. 3 is a block diagram showing an example of a functional configuration of an inventory management device. The figure which shows an example of the data structure of the dispensing data stored in the dispensing data storage part. The figure which shows an example of the data structure of the order data stored in the order data storage part. The figure which shows an example of the data structure of the corresponding data stored in the corresponding data storage part. The flowchart which shows an example of the processing procedure of an inventory management apparatus. The figure which shows an example of a structure of the inventory management system in 2nd Embodiment of this invention. FIG. 3 is a block diagram showing an example of a functional configuration of an inventory management device. The flowchart which shows an example of the processing procedure of exhibition processing. The figure which shows an example of the data structure of the exhibition data stored in the exhibition data storage part. The flowchart which shows an example of the processing procedure of purchase reservation processing. The figure which shows an example of the data structure of the purchase reservation data stored in the purchase reservation data storage part. The flowchart which shows an example of the process procedure of a matching process.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(First embodiment)
First, a first embodiment of the present invention will be described. FIG. 1 shows an example of the configuration of an inventory management system (network system) according to this embodiment.

The inventory management system in the present embodiment is, for example, a drug necessary for the dispensing in a store such as a dispensing pharmacy (hereinafter, simply referred to as a dispensing pharmacy) that dispenses a drug based on a prescription issued from a hospital to a patient. Is a system used to manage the inventory of.

As shown in FIG. 1, the inventory management system includes an inventory management device 10 and a store terminal 20. The inventory management device 10 and the store terminal 20 are communicably connected via a network 30 such as the Internet.

The inventory management device 10 according to the present embodiment is a server device having a function of managing the inventory of medicines in the above dispensing pharmacy.

The store terminal 20 is a terminal (electronic device) installed in a dispensing pharmacy where the inventory of medicines is managed, and is used by staff (for example, a pharmacist) of the dispensing pharmacy. For example, a personal computer (PC) can be used as the store terminal 20, but other electronic devices such as a smartphone and a tablet terminal may be used as the store terminal 20.

FIG. 2 shows an example of the hardware configuration of the inventory management device 10 shown in FIG. As shown in FIG. 2, in the inventory management device 10, a non-volatile memory 12, a CPU 13, a main memory 14, a communication device 15 and the like are connected to a bus 11. The non-volatile memory 12 and the main memory 14 configure a storage device of the inventory management device 10.

The nonvolatile memory 12 stores various programs including, for example, an operating system (OS) and the above-described program for managing drug inventory (hereinafter referred to as an inventory management program).

The CPU 13 is a processor that executes various programs stored in the non-volatile memory 12, for example. The CPU 13 executes control of the inventory management device 10 as a whole.

The main memory 14 is used as, for example, a work area required when the CPU 13 executes various programs.

Although only the non-volatile memory 12 and the main memory 14 are shown in FIG. 2, the inventory management device 10 includes other storage devices such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive). Good.

The communication device 15 controls communication performed with an external device such as the store terminal 20 via the network 30 described above, for example. Note that the communication device 15 can realize a wireless communication function such as a wireless LAN and Wifi (registered trademark).

FIG. 3 is a block diagram showing an example of the functional configuration of the inventory management device 10 according to this embodiment. As shown in FIG. 3, the inventory management device 10 includes a dispensing data storage unit 101, an order data storage unit 102, a corresponding data storage unit 103, a handled item data storage unit 104, an inventory data storage unit 105, a first calculation unit 106, The correction unit 107, the second calculation unit 108, and the order processing unit 109 are included.

In this embodiment, each of the storage units 101 to 105 is realized by, for example, the nonvolatile memory 12 shown in FIG. 2 or another storage device.

Further, in the present embodiment, each of the units 106 to 109 is, for example, that the CPU 13 (that is, the computer of the inventory management device 10) illustrated in FIG. 2 executes the inventory management program stored in the nonvolatile memory 12, that is, software. Shall be realized by. The inventory management program can be stored in a computer-readable storage medium in advance and distributed. Further, the inventory management program may be downloaded to the inventory management device 10 via the network 30 or the like, for example.

Although the respective units 106 to 109 have been described as being realized by software here, the respective units 106 to 109 may be realized by hardware or may be realized by a combination of software and hardware.

The dispensing data storage unit 101 stores dispensing data regarding dispensing that has already been performed at the dispensing pharmacy in which the store terminal 20 is installed. The dispensation data stores the dispensation data including the first code given to the drug dispensed at the dispensing pharmacy and the usage amount of the drug in the dispense. It should be noted that the first code is a code given to a drug in units of type (eg, drug name).

Note that the dispensing data is data stored in, for example, a receipt computer used to create a medical fee statement called a receipt, and can be acquired from the receipt computer.

The order data storage unit 102 stores order data regarding past orders of medicines at the dispensing pharmacy in which the store terminal 20 is installed (ordering data indicating that a medicine has been ordered at the dispensing pharmacy). The order data includes the second code assigned to the drug in the packaging unit for sale ordered by the dispensing pharmacy and the order amount of the drug to which the second code is assigned. It should be noted that the second code is a code given to a pharmaceutical product as a product in a packaging unit for sale, that is, for example, distribution to a dispensing pharmacy.

Here, while the first code included in the above-mentioned dispensing data is given in units of type of drug (that is, the dispensing data is managed by the first code), the second code included in, for example, order data. The code is assigned in units of packaging for sale (that is, the order data is managed by the second code).

In other words, even though the medicines have the same first code in the dispensing data, the medicines in different packaging units for sale are managed with the different second codes in the ordering data. That is, in this embodiment, it can be said that the first code and the second code have a one-to-many relationship.

By the way, in the present embodiment, the inventory of the drug is managed based on the usage amount of the drug to which the first code included in the dispensing data is given. In this case, the first code included in the dispensing data is It is necessary to estimate the usage amount of the drug to which each of the second codes corresponding to the first code is applied from the usage amount of the granted drug.

Therefore, the correspondence data storage unit 103 stores in advance correspondence data indicating the correspondence relationship between the above-described first code and second code (the above-mentioned one-to-many relationship).

In the following description, the first code will be referred to as YJ code (individual drug code) and the second code will be referred to as JAN code (unified product code).

The handling item data storage unit 104 stores in advance handling item data indicating medicines (handling items) handled in the dispensing pharmacy. The handling item data includes the JAN code assigned to the medicine in the packaging unit for sale handled by the dispensing pharmacy. In other words, the handling item data is managed by the JAN code, like the order data.

Drugs handled by a dispensing pharmacy include not only drugs that have already been ordered by the dispensing pharmacy but also drugs that are scheduled to be ordered in the future. Therefore, the handling item data is managed separately from the above-mentioned order data. In the present embodiment, as described above, the handling item data is managed separately from the ordering data, but the ordering data may also serve as the handling item data.

The first calculation unit 106 uses the amount of the drug to which the YJ code included in the dispensing data stored in the dispensing data storage unit 101 is attached, the correspondence data and the handling item data stored in the correspondence data storage unit 103. Based on the handling item data stored in the storage unit 104, the usage amount of the drug is calculated (estimated) for each packaging unit for sale (that is, JAN code). The amount of drug used calculated by the first calculator 106 is an estimated value.

The correction unit 107 corrects the usage amount of the drug calculated for each packaging unit for sale by the first calculation unit 106 based on the order data (past order status of the drug) stored in the order data storage unit 102. To do.

The second calculation unit 108 calculates the stock quantity of the drug for each packaging unit for sale based on the usage amount of the drug corrected by the correction unit 107. The stock quantity of the medicine calculated by the second calculator 108 is an expected value (that is, the expected stock quantity).

Inventory data indicating the number of stocks calculated by the second calculation unit 108 for each packaging unit for sale is stored in the inventory data storage unit 105.

The order processing unit 109 orders a drug in units of packaging for sale based on the number of stocks indicated by the inventory data stored in the inventory data storage unit 105 (that is, orders a drug to which a JAN code is attached). ) Perform the process.

FIG. 4 shows an example of the data structure of the dispensing data stored in the dispensing data storage unit 101 shown in FIG. As shown in FIG. 4, the dispensing data includes a prescription ID, a patient name, a dispensing date, a prescription drug, a quantity, and a remark.

The prescription ID is identification information for identifying the prescription used when the drug is dispensed at the dispensing pharmacy. The patient name is the name of the patient who issued the prescription identified by the associated prescription ID. Although a patient name will be described in the present embodiment, the patient name may be a patient ID, for example. The same applies to the following description. The dispensing date is the date when dispensing was performed in the dispensing pharmacy based on the prescription identified by the associated prescription ID.

The prescription drug indicates a drug dispensed based on the prescription identified by the associated prescription ID. The prescription describes the drug name of the drug to be dispensed based on the prescription, but the prescription drug included in the dispensing data includes the YJ code assigned to the drug having the drug name.

The quantity is the quantity of a medicine (medicine to which a YJ code is attached) dispensed based on the prescription identified by the associated prescription ID. In other words, the quantity corresponds to the usage amount of the drug (medicine to which the YJ code is attached) in the dispensing based on the prescription identified by the associated prescription ID.

The remark indicates, for example, the contents described in the remarks column of the prescription identified by the associated prescription ID. The remarks column of the prescription describes, for example, whether or not the medicines to be dispensed based on the prescription are packaged. Therefore, the remarks included in the dispensing data include information indicating whether or not the medicine is packaged (hereinafter, referred to as packaged information). It should be noted that the term “single package” means, for example, that different medicines (tablets, etc.) of the same type having the same administration time zone (time of administration) are collectively delivered in one bag. It should be noted that the necessity of packaging (that is, whether packaging is included) is instructed by the doctor of the hospital that issues the prescription.

In the example shown in FIG. 4, the dispensing data storage unit 101 stores dispensing data 101a to 101c.

The dispensing data 101a includes a prescription ID "1", a patient name "A", a dispensing date "November 22, 2018", a prescription content "YJ code 1", a quantity "quantity 1", and a remark "-". Including. According to this dispensing data 101a, based on the prescription identified by the prescription ID “1” issued to the patient whose patient name is “A”, on November 22, 2018, the “quantity 1” of “ It is shown that a medicine to which “YJ code 1” is given has been dispensed. Further, according to the dispensing data 101a, it is shown that the medicine to which the “YJ code 1” is dispensed based on the prescription identified by the prescription ID “1” is not packaged. ..

Further, the dispensing data 101b includes a prescription ID "1", a patient name "A", a dispensing date "November 22, 2018", a prescription content "YJ code 2", a quantity "quantity 2", and a remark "-". "including. According to this dispensing data 101b, based on the prescription identified by the prescription ID “1” issued to the patient whose patient name is “A”, the “quantity 2” It is shown that a drug to which “YJ code 2” is given has been dispensed. Further, according to the dispensing data 101b, it is shown that the medicine to which the “YJ code 2” dispensed based on the prescription identified by the prescription ID “1” is not packaged. ..

As shown in the above-mentioned dispensing data 101a and 101b, a plurality of pharmaceuticals of different types may be dispensed based on one prescription (prescription identified by the prescription ID “1”).

The dispensing data 101c includes a prescription ID "2", a patient name "B", a dispensing date "November 23, 2018", a prescription content "YJ code 3", a quantity "quantity 3", and a remark "packaging". including. According to this dispensing data 101c, based on the prescription identified by the prescription ID "2" issued to the patient whose patient name is "B", " It is shown that a drug to which “YJ code 3” is given has been dispensed. Further, according to the dispensing data 101c, it is shown that the medicine to which the “YJ code 3” that is dispensed based on the prescription identified by the prescription ID “2” is attached is packaged.

Although only the dispensing data 101a to 101c has been described here, the dispensing data storage unit 101 stores dispensing data for each drug dispensed at the dispensing pharmacy.

Further, in the example shown in FIG. 4, the dispensing data has been described as including the prescription ID, the patient name, the dispensing date, the prescription content, the quantity (usage amount) and the remark (packaging information). May have some of them omitted, or may further include other information.

Note that the dispensing data in the present embodiment is acquired from the receipt computer, but if the dispensing data corresponds to the data described in FIG. 4 above, for example, the data managed independently of the receipt computer. (That is, the data does not have to be obtained from the receiving computer).

FIG. 5 shows an example of the data structure of order data stored in the order data storage unit 102 shown in FIG. As shown in FIG. 5, the order data includes the ordered drug, the ordered date, and the ordered quantity.

The ordered drug indicates a drug ordered by a dispensing pharmacy. The contents of the order include the JAN code given to the medicine as a product ordered by the dispensing pharmacy (that is, the medicine in the packaging unit for sale).

The order date is the date when the medicine indicated by the associated ordered medicine (that is, the medicine in the packaging unit for sale with the JAN code) is ordered.

The order quantity is the quantity in which the medicine indicated by the associated ordered medicine (that is, the medicine in the packaging unit for sale to which the JAN code is attached) is ordered.

In the example shown in FIG. 5, the order data storage unit 102 stores order data 102a and 102b.

The order data 102a includes the ordered drug “JAN code 11”, the order date “October 1, 2018”, and the order amount “500 tablets×1 bottle”. The order data 102a indicates that the medicine in the packaging unit for sale to which the "JAN code 11" is attached is ordered on October 1, 2018 in a quantity of 500 tablets x 1 bottle. ..

In addition, the order data 102b includes the ordered drug “JAN code 12”, the order date “October 1, 2018”, and the order quantity “10 tablets/sheet×50”. The order data 102b indicates that the medicine in the packaging unit for sale to which the "JAN code 12" is attached has been ordered on October 1, 2018 in a quantity of 10 tablets sheet x 50. ..

Although only the order data 102a and 102b have been described here, the order data storage unit 102 stores order data for each drug ordered at the dispensing pharmacy.

In the example shown in FIG. 5, the order data has been described as including the ordered drug, the ordered date, and the ordered quantity, but the ordered data may be a part of these omitted. , Other information may be further included.

FIG. 6 shows an example of the data structure of the corresponding data stored in the corresponding data storage unit 103 shown in FIG. As shown in FIG. 6, the correspondence data includes a YJ code and a JAN code in association with each other.

The YJ code is a code given to a drug for each type as described above, and is included in, for example, dispensing data.

On the other hand, the JAN code is a code given to a medicine for each packaging unit for sale, and is included in, for example, order data, handled item data, and inventory data.

In the example shown in FIG. 6, the corresponding data storage unit 103 stores corresponding data 103a and 103b.

The correspondence data 103a includes a YJ code “YJ code 1” and a JAN code “JAN code 11” in association with each other. According to this correspondence data 103a, the medicine to which the “YJ code 1” is attached is sold (distributed) as the medicine (that is, the product) in the packaging unit for sale to which the “JAN code 11” is attached. Is shown).

On the other hand, the correspondence data 103b includes the YJ code “YJ code 1” and the JAN code “JAN code 12” in association with each other. According to this correspondence data 103b, the medicine to which the “YJ code 1” is attached is sold (distributed) as the medicine (that is, the product) in the packaging unit for sale to which the “JAN code 12” is attached. Is shown).

In addition, in the present embodiment, the packaging unit for sale refers to a packaging state and the like when a pharmaceutical product (for example, a tablet or the like) is sold, and includes, for example, a bottled form or a sheet form. According to this, even if a medicine is provided with "YJ code 1", for example, a product sold in a bottle (that is, in bulk) is provided with "JAN code 11" and is in a sheet form (for example, "JAN code 12" is given to products sold as 10 tablets sheet or the like).

That is, in the present embodiment, as described above, a plurality of JAN codes (here, “JAN code 11” and “JAN code 12”) are provided for the same YJ code (here, “YJ code 1”). They are associated with each other, and the YJ code and the JAN code have a one-to-many relationship.

Here, only the correspondence data 103a and 103b have been described, but the correspondence data storage unit 103 stores the correspondence data for each YJ code.

Although the detailed data structure is not shown, the handling item data stored in the handling item data storage unit 104 shown in FIG. Anything including the JAN code assigned to

The inventory data stored in the inventory data storage unit 105 shown in FIG. 3 may include the JAN code assigned to the drug in the packaging unit for sale and the inventory number of the drug.

Hereinafter, an example of the processing procedure of the inventory management device 10 according to the present embodiment will be described with reference to the flowchart in FIG. 7.

It is assumed that the dispensing data storage unit 101 has already stored the dispensing data acquired from, for example, the receipt computer as described above. Further, it is assumed that the corresponding data storage unit 103 stores the above-mentioned corresponding data in advance.

Furthermore, it is assumed that the order data storage unit 102 stores order data for each drug (medicine to which a JAN code is added) ordered by a dispensing pharmacy. Further, it is assumed that the handling item data storage unit 104 stores in advance handling item data including a JAN code designated by staff of a dispensing pharmacy, for example.

Further, it is assumed that the inventory data storage unit 105 has already stored inventory data, for example, by repeatedly executing the processing shown in FIG. 7 described later. When the process shown in FIG. 7 is first executed, for example, the initially set inventory data may be stored. The inventory quantity indicated by the initialized inventory data may be an arbitrary numeric value (for example, 0 or another numeric value), or may be the inventory quantity actually examined by the staff of the dispensing pharmacy. ..

It should be noted that the processing shown in FIG. 7 is executed every predetermined period. Specifically, the processing shown in FIG. 7 is executed once a day, for example, outside the business hours of the dispensing pharmacy.

In the inventory management device 10, the process shown in FIG. 7 is executed for each of the YJ codes included in the dispensing data stored in the dispensing data storage unit 101. Here, a case will be described in which the process is executed for one of the YJ codes included in the dispensing data (hereinafter referred to as the target YJ code).

First, the first calculation unit 106 acquires the dispensing data including the target YJ code from the dispensing data storage unit 101 (step S1).

Note that, as described above, the process shown in FIG. 7 is executed every predetermined period (for example, one day), but in step S1, since the process was executed last time (that is, the process is Dispensing data regarding the dispensing performed up to the point (at the time of execution) is acquired.

Specifically, for example, when the process shown in FIG. 7 is executed before business hours on November 23, 2018, the dispensing date is “November 22, 2018” in step S1. Dispensing data is acquired. Similarly, when the process shown in FIG. 7 is executed before business hours on November 24, 2018, in step S1, the dispensing date is “November 23, 2018”. The data is acquired. In step S1, a plurality of dispensing data may be acquired.

Next, the first calculating unit 106 calculates the usage amount of the drug to which the target YJ code is attached (hereinafter, referred to as the usage amount of the target YJ code) based on the dispensing data acquired in step S1 ( Step S2). In step S2, the total value of the quantities (usage amounts) included in the dispensing data acquired in step S1 is calculated.

When the process of step S2 is executed, the first calculating unit 106 assigns each of the plurality of JAN codes corresponding to the target YJ code based on the usage amount of the target YJ code calculated in step S2. The usage amount of the existing medicine (hereinafter referred to as the usage amount of JAN code) is calculated (step S3).

Here, the process of step S3 will be described in detail. First, the first calculation unit 106 acquires the corresponding data stored in the corresponding data storage unit 103.

Next, the first calculating unit 106 includes the JAN included in the handled item data stored in the handled item data storage unit 104 among the plurality of JAN codes associated with the target YJ code in the acquired correspondence data. Identify the code. The JAN code specified here is the JAN code given to the drug (the drug in the packaging unit for sale) that may have been used when the drug to which the target YJ code was given was dispensed. ..

Here, for example, a JAN code (hereinafter, referred to as a first JAN code) assigned to a drug having a target YJ code and a packaging state of bottling (that is, a packaging unit for sale is a bottle) is used. And the JAN code (hereinafter, referred to as the second JAN code) assigned to the drug whose packaging state is a sheet (that is, the packaging unit for sale is 10 tablets sheet or 14 tablets sheet). It is assumed that

Here, as described above, the dispensing data includes the packaging information (information indicating whether or not to package the medicine to which the target YJ code is attached). For this reason, the first calculating unit 106 performs packaging in the usage amount of the target YJ code calculated in step S2 described above, based on the packaging information included in the dispensing data acquired in step S1. Calculate the ratio of the amount of drug used to the amount of drug not packaged (hereinafter referred to as packaged ratio).

In addition, in the present embodiment, when the medicine to which the YJ code included in the dispensing data is attached is packaged, it is estimated that, for example, a bottled medicine (that is, a rose) is used. On the other hand, when the medicine to which the YJ code included in the dispensing data is attached is not packaged, it is presumed that the medicine in the sheet form was used.

In the present embodiment, from the above viewpoint, the usage amount for each JAN code is calculated by applying the encapsulation ratio to the usage amount of the target YJ code calculated in step S2.

Specifically, when the above-mentioned packaging ratio is, for example, 1:9 (the specification amount of the packaged drug is 10%, the amount of the drug not packaged is 90%), It is estimated that 10% of the usage amount of the target YJ code was used from the bottled medicine (medicine to which the 1st JAN code is given). Similarly, it is estimated that 90% of the usage amount of the target YJ code is used from the sheet-shaped drug (medicine to which the second JAN code is given).

In step S3, the usage amount of the first JAN code and the usage amount of the second JAN code can be calculated (estimated) by executing the above-described processing.

Next, the correction unit 107 corrects the usage amounts of the first and second JAN codes calculated in step S3 based on the order data stored in the order data storage unit 102 (step S4).

Specifically, the correction unit 107 includes, among the order data stored in the order data storage unit 102, order data including the above-mentioned first JAN code (hereinafter referred to as first order data) and a second JAN code. Ordering data (hereinafter referred to as second ordering data) is acquired. In this case, the correction unit 107 acquires the first order data and the second order data in which the order date falls within a predetermined period (that is, regarding orders placed within the predetermined period).

The correction unit 107, based on the order quantity (total value) included in the first order data and the order quantity (total value) included in the second order data, the drug to which the first JAN code is assigned (for example, The past ordering ratio between the bottled medicine) and the medicine to which the second JAN code is added (for example, a sheet medicine) is calculated.

The correction unit 107 corrects (changes) the above-mentioned packaging rate based on the calculated ordering ratio. Specifically, the correction unit 107 corrects the packaging rate described above to an average value of the packaging rate and the ordering rate.

The correction unit 107 applies the corrected encapsulation ratio to the usage amount of the target YJ code to determine the usage amount of the first JAN code and the usage amount of the second JAN code (that is, the corrected usage amount). Calculate again.

As described above, in step S4, the usage amount of the first JAN code and the usage amount of the second JAN code can be corrected based on the order data stored in the order data storage unit 102.

If, for example, the order data storage unit 102 does not store sufficient order data, the process of step S4 may be omitted.

Hereinafter, the processes of steps S5 to S12 are executed for each of the above-mentioned first JAN code and second JAN code. The JAN code that is the target of the processing in steps S5 to S12 is referred to as the target JAN code.

The second calculation unit 108 is based on the usage amount of the target JAN code (the usage amount of the first JAN code or the usage amount of the second JAN code) corrected in step S4 and the inventory data stored in the inventory data storage unit 105. Then, the stock number of medicines to which the target JAN code is given (hereinafter referred to as the stock number of the target JAN code) is calculated (step S5). In this case, the second calculating unit 108 calculates the current inventory quantity of the target JAN code by subtracting the usage amount of the target JAN code from the inventory quantity included in the inventory data including the target JAN code. The number of stocks included in the inventory data including the target JAN code is the number of stocks of the medicine to which the target JAN code is given which is currently grasped (managed) by the inventory management device 10, and specifically, in FIG. It is the inventory quantity calculated when the process was executed last time (expected inventory quantity up to the previous calculation time), but may be the inventory quantity specified by the staff of the dispensing pharmacy, for example.

In the present embodiment, the order quantity of a drug to which the target JAN code is added, which is included in the order data stored in the order data storage unit 102, is added to the stock quantity of the target JAN code. This addition of the order quantity may be executed when the order data is stored in the order data storage unit 102, or may be executed in step S5. When executed in step S5, the ordering data (that is, the target JAN code is related to the ordering of the drug to which the target JAN code has been given between the time when the process of FIG. The order quantity included in the included order data) may be added to the stock quantity.

The above-described current inventory quantity of the target JAN code is overwritten by the inventory quantity included in the inventory data including the relevant JAN code. As a result, the inventory data (that is, the inventory quantity) stored in the inventory data storage unit 105 can be updated.

In the present embodiment, the stock quantity of the target JAN code can be managed by updating the stock data stored in the stock data storage unit 105 as described above. The stock quantity of the target JAN code indicated by the stock data stored in the stock data storage unit 105 can be confirmed by the staff of the dispensing pharmacy by being displayed on the store terminal 20, for example. The same applies to other JAN codes.

Here, in the present embodiment, when the processing shown in FIG. 7 is executed, for example, every day, the usage amount of the target JAN code corrected in step S4 described above is given by the target JAN code during one day. It corresponds to the amount of medicines used.

Therefore, the order processing unit 109 divides the stock quantity of the target JAN code calculated in step S5 (the stock quantity included in the stock data including the target JAN code) by the usage amount of the target JAN code to obtain the target JAN code. The remaining number of days of dispensing of the drug to which the code is given (that is, the number of remaining days of dispensing possible with the current stock quantity) is calculated (step S6).

When the process of step S6 is executed, the order processing unit 109 determines whether the number of dispensing days calculated in step S6 is equal to or more than a predetermined value (hereinafter, referred to as a threshold) (step S7). ).

When it is determined that the number of dispensing days is not equal to or more than the threshold value (NO in step S7), the order processing unit 109 generates order data regarding the order of the medicine to which the target JAN code is attached (step S8). In step S8, for example, the target JAN code is set as the ordered drug, the shortest date when the drug can be ordered at this time is set as the ordered date, and the current target is determined from the upper limit number (upper limit value) of the stock quantity determined in advance. Order data is generated with the order quantity being a value obtained by subtracting the JAN inventory quantity. The ordering date included in the ordering data generated in step S8 is, for example, a date in consideration of the remaining number of dispensing days described above (for example, a date around which the remaining number of dispensing days elapses from the present time). May be Further, the order quantity included in the order data generated in step S8 may be a predetermined value or the like.

The order data generated in step S8 is transmitted from the inventory management device 10 to the store terminal 20. The order data transmitted from the inventory management device 10 to the store terminal 20 is displayed on the store terminal 20 (that is, the staff of the dispensing pharmacy is notified of the order of the drug with the target JAN code).

Here, the staff of the dispensing pharmacy can confirm the content of the order data displayed on the store terminal 20 (that is, the order content) and operate the store terminal 20 to change the order content. Specifically, the staff of the dispensing pharmacy can change, for example, the order date or the order amount included in the order data displayed on the store terminal 20. Note that the staff of the dispensing pharmacy can cancel the order itself. When the order contents are changed by the staff of the dispensing pharmacy, the changed order contents are transmitted (notified) from the store terminal 20 to the inventory management device 10.

The order processing unit 109 determines whether or not the order details have been changed by the staff of the dispensing pharmacy based on the presence or absence of the notification from the store terminal 20 described above (step S9).

When it is determined that the order content has been changed (YES in step S9), the order processing unit 109 reflects the change in the order content in the order data generated in step S8 (step S10).

Further, when the order contents are changed by the staff of the dispensing pharmacy as described above, the change of the order contents is fed back to the inventory data stored in the inventory data storage unit 105.

In this case, the order processing unit 109 changes the stock quantity included in the stock data including the target JAN code based on the change of the order contents (step S11).
For example, when a change is made to delay the ordering time (ordering date), the actual stock quantity is larger than the stock quantity of the target JAN code managed by the stock management device 10, and therefore the dispensing It is speculated that pharmacy staff have made such changes. Therefore, if the ordering time is delayed, the usage amount of the target JAN code corrected in step S4 described above (that is, the drug to which the target JAN code is assigned during the day is used. The quantity obtained by multiplying the number of days) by the number of delayed days is added to the quantity of inventory included in the inventory data including the target JAN code to change (increase) the quantity of inventory. Note that the stock quantity included in the stock data including the target JAN code is also increased when the order quantity is changed or the order itself is canceled.

On the other hand, when a change is made to accelerate the ordering time (ordering date), the actual inventory quantity is smaller than the inventory quantity of the target JAN code managed by the inventory management device 10, The staff of the dispensing pharmacy is presumed to have made such changes. Therefore, when the order is placed earlier, the amount of usage of the target JAN code corrected in step S4 multiplied by the advanced number of days is included in the inventory data including the target JAN code. The stock quantity is changed (decreased) by subtracting from the stock quantity. Similarly, when the order quantity is changed, the stock quantity included in the stock data including the target JAN code is decreased.

When the process of step S11 is executed, the order processing unit 109 executes the order process based on the order data in which the change of the order content is reflected in step S10 (step S12). The ordering process is completed, for example, by transmitting the ordering data to an external system that manages the ordering of the medicine from the dispensing pharmacy. The ordering data may be directly transmitted to a drug wholesaler or the like. When the order processing is completed, the order data used in the order processing is stored (stored) in the order data storage unit 102.

The process of step S12 may be executed when a predetermined time has elapsed after the process of step S8 or step S10 is executed, or may be executed by the staff of the dispensing pharmacy via the store terminal 20. May be performed accordingly.

When the process of step S12 is executed, it is determined whether or not the processes of steps S5 to S12 have been executed for all JAN codes (here, the first JAN code and the second JAN code) (step S13).

When it is determined that the process has not been executed for all JAN codes (NO in step S13), the process returns to step S5 and the process is repeated. In this case, the JAN code for which the processing of steps S5 to S12 has not been executed is executed as the target JAN code.

On the other hand, when it is determined that the processing has been executed for all JAN codes (YES in step S13), the processing shown in FIG. 7 is ended.

If it is determined in step S7 that the number of dispensing days is equal to or greater than the threshold value (YES in step S7), it is determined that it is not necessary to order the drug with the target JAN code, and the process of step S13 is executed.

When it is determined in step S9 that the order contents have not been changed (NO in step S9), the process of step S12 is executed based on the order data generated in step S8.

In the processing shown in FIG. 7, the description has been made on the assumption that the staff of the dispensing pharmacy is notified of the order of the drug to which the target JAN code is added, but the order is automatically placed without notification. It can also be configured. In this case, the processes of steps S9 to S11 shown in FIG. 7 may be omitted.

Although the processing executed for one of the YJ codes included in the dispensing data has been described with reference to FIG. 7, the processing illustrated in FIG. 7 is performed for each YJ code included in the dispensing data. Shall be executed. As a result, the inventory management device 10 according to the present embodiment manages the inventory for each JAN code corresponding to each YJ code included in the dispensing data.

Note that, for example, the upper limit of the number of ordering processes executed on one day may be set in advance. Specifically, the order processing may be possible up to three times a day. In this case, for example, the first order is an automatic order at the time of inventory renewal, and the second and third orders are optional.

Further, the processing of steps S5 to S11 shown in FIG. 7 may be repeated for each JAN code, and the ordering processing (that is, the processing of step S12) may be collectively executed for the medicines that need to be ordered.

As described above, in the present embodiment, the usage amount of the medicine to which the YJ code (first code) included in the dispensing data stored in the dispensing data storage unit 101 and the handling item data storage unit 104 are stored. Based on the JAN code (2nd code) included in the handled item data, the usage amount of the drug is calculated for each packaging unit for sale, and the inventory quantity of the drug is sold based on the calculated usage amount. The inventory data is calculated for each packaging unit, and the inventory data indicating the calculated inventory quantity is stored in the inventory data storage unit 105.

In the present embodiment, with such a configuration, the inventory of the drug (JAN code) at the dispensing pharmacy is appropriately determined in consideration of the correspondence relationship between the YJ code included in the dispensing data and the JAN code included in the order data. Can be managed. In addition, in the present embodiment, by realizing such inventory management of medicines, it is possible to avoid a situation in which, for example, when a patient comes to a dispensing pharmacy, it is not possible to dispense due to lack of medicines. Becomes

Further, in the present embodiment, the usage amount of the JAN code (that is, the usage amount of each packaging unit for sale) is based on the ratio of the usage amount of the packaged drug to the usage amount of the YJ code included in the dispensing data. To calculate. In the present embodiment, with such a configuration, it is possible to estimate the usage amount of each JAN code corresponding to the YJ code by using the packaging information included in the dispensing data.

Further, in the present embodiment, the usage amount of the JAN code is corrected based on the ordering ratio of the medicine to which the JAN code included in the ordering data stored in the ordering data storage unit 102 is added. As a result, the estimated usage amount of each JAN code can be corrected so as to conform to the past order record.

Further, in the present embodiment, the stock quantity of each JAN code is managed as described above, and then the ordering process for ordering the medicine to which the JAN code is attached is executed based on the stock quantity.

Specifically, the ordering process is executed when the remaining number of dispensing days is calculated based on the current inventory number of the JAN code and the daily usage amount of the JAN code, and when the number of dispensing days is equal to or less than the threshold value. .. Further, the order quantity when the order processing is executed is the number obtained by subtracting the stock quantity from the predetermined upper limit quantity.

In the present embodiment, with such a configuration, it is possible to automatically place an order for a medicine whose inventory quantity has decreased at an appropriate timing and in an appropriate quantity, and reduce the time and effort required for staff of the dispensing pharmacy to place an order. .. When a drug is automatically ordered for each JAN code, the order data relating to the order is added to the order data storage unit 102, and the order quantity included in the order data is added to the inventory quantity of the JAN code. (In other words, the numerical value is reflected in the inventory data).

Further, in the present embodiment, when the order contents are changed based on the operation on the shop terminal 20, the inventory quantity indicated by the inventory data stored in the inventory data storage unit 105 is changed. Even when the inventory quantity managed in the device 10 is different from the actual inventory quantity, the inventory management device 10 manages the inventory by feeding back the change of the order contents by the staff of the dispensing pharmacy. It is possible to correct the number of stocks in stock.

In the present embodiment, the case of managing the inventory of the drug (JAN code) in one dispensing pharmacy has been mainly described, but the inventory management device 10 according to the present embodiment performs the processing described in FIG. 7 described above in the dispensing pharmacy. It is also possible to manage the stocks of the medicines in a plurality of dispensing pharmacies by executing them every time. In this case, the above-mentioned dispensing data, order data, handling item data and inventory data may be managed (stored) for each dispensing pharmacy.

Although the inventory management device 10 has been described as including the storage units 101 to 105 in the present embodiment, at least a part of the storage units 101 to 105 is provided in an external device of the inventory management device 10 or the like. May be. In this case, the inventory management device 10 may be configured to acquire (receive) necessary data from an external device.

Further, although the inventory management device 10 has been described as one device in the present embodiment, the inventory management device 10 may be realized by, for example, a cooperative operation of a plurality of devices.

(Second embodiment)
Next, a second embodiment of the present invention will be described. In the present embodiment, the same parts as those in the drawings used in the description of the first embodiment described above will be denoted by the same reference numerals. Further, in the following description, the part different from the above-described first embodiment will be mainly described.

FIG. 8 shows an example of the configuration of the inventory management system (network system) in this embodiment.

As shown in FIG. 8, the inventory management system includes an inventory management device 10, a first store terminal 20a, and a second store terminal 20b. The inventory management device 10 is communicably connected to each of the first store terminal 20a and the second store terminal 20b via the network 30.

In the present embodiment, the inventory management device 10 includes an inventory of medicines in a dispensing pharmacy in which the first store terminal 20a is installed (hereinafter, referred to as a first dispensing pharmacy) and a dispensing pharmacy in which the second store terminal 20b is installed. (Hereinafter, referred to as a second dispensing pharmacy) has a function of managing the inventory of medicines (hereinafter referred to as an inventory management function).

Further, the inventory management device 10 according to this embodiment has a matching function. In the present embodiment, the matching function is, for example, a function that enables the second dispensing pharmacy to purchase a drug exhibited by the first dispensing pharmacy. This embodiment is different from the above-described first embodiment in that it has a matching function. Details of this matching function will be described later.

The first shop terminal 20a and the second shop terminal 20b described above are the same terminals (electronic devices) as the shop terminal 20 described in the above-described first embodiment.

FIG. 9 is a block diagram showing an example of the functional configuration of the inventory management device 10 according to this embodiment. Here, parts different from those in FIG. 3 described above will be mainly described, and detailed description of parts common to FIG. 3 will be omitted.

The hardware configuration of the inventory management device 10 according to the present embodiment is the same as that of the first embodiment described above, and therefore will be described with reference to FIG. 3 as appropriate.

As shown in FIG. 9, the inventory management device 10 includes an exhibition processing unit 110, a purchase reservation processing unit 111, a matching processing unit 112, an exhibition data storage unit 113, and a purchase reservation data storage unit 114.

In the present embodiment, the respective units 110 to 112 are realized by, for example, the CPU 13 shown in FIG. 2 (that is, the computer of the inventory management device 10) executing the inventory management program stored in the nonvolatile memory 12, that is, software. Shall be done.

Here, the respective units 110 to 112 have been described as being realized by software, but the respective units 110 to 112 may be realized by hardware or may be realized by a combination of software and hardware.

In addition, in the present embodiment, each of the storage units 113 and 114 is realized by, for example, the nonvolatile memory 12 shown in FIG. 2 or another storage device.

The auction processing unit 110 executes, for example, a process of auctioning a drug in stock at the first dispensing pharmacy. In this case, when the stock quantity indicated by the stock data stored in the stock data storage section 105 has not changed for a predetermined period, the exhibition processing section 110 determines that the stock quantity has not changed. The exhibition data for putting up (medicine to which the JAN code is added) is generated. This exhibition data is data indicating a drug that is submitted by the first dispensing pharmacy, and the JAN code assigned to the drug (the drug in the packaging unit for sale) and information about the drug (hereinafter referred to as drug information). including. The exhibition data generated by the exhibition processing unit 110 is stored in the exhibition data storage unit 113. The inventory quantity indicated by the inventory data is the expected value of the inventory quantity (that is, the expected inventory quantity) as described in the first embodiment.

The purchase reservation processing unit 111 generates, for example, purchase reservation data for the second dispensing pharmacy to reserve the purchase of a drug put up by another dispensing pharmacy. The purchase reservation data includes the type (YJ code) of the medicine reserved for purchase by the second dispensing pharmacy and the condition designated by the second dispensing pharmacy. The purchase reservation data generated by the purchase reservation processing unit 111 is stored in the purchase reservation data storage unit 114.

The matching processing unit 112 matches the exhibition data stored in the exhibition data storage unit 113 with the purchase reservation data stored in the purchase reservation data storage unit 114. In this case, the matching processing unit 112 determines that the JAN code included in the exhibition data and the YJ code included in the purchase reservation data have a correspondence relationship, and the drug information included in the exhibition data is included in the purchase reservation data. When it is satisfied, the exhibition data is matched with the purchase reservation data.

When the auction data and the purchase reservation data are matched by the matching processing unit 112, a process for the second dispensing pharmacy to purchase a drug to which the JAN code included in the auction data is attached is executed.

As described above, in the inventory management device 10 according to the present embodiment, the inventory of the drug in the first dispensing pharmacy and the inventory of the drug in the second dispensing pharmacy are managed. In this case, the inventory data storage unit 105 stores inventory data indicating the number of stocks of each drug (medicine to which a JAN code is assigned) at the first dispensing pharmacy and the drug (JAN code at the second dispensing pharmacy). The stock data indicating the number of stocks of each drug) is stored.

The operation of the inventory management device 10 according to this embodiment will be described below. Here, the processing relating to the matching function described above will be mainly described. Specifically, the process for the first dispensing pharmacy to list the drug (hereinafter referred to as the listing process), the process for the second dispensing pharmacy to reserve the purchase of the drug (hereinafter referred to as the purchase reservation process), and A process for matching auction data with purchase reservation data (hereinafter referred to as matching process) will be described.

Although the inventory management device 10 according to the present embodiment has the above-described inventory management function, the processing for realizing the inventory management function is as described in, for example, FIG. The detailed description is omitted.

First, an example of the processing procedure of the above-described exhibition processing will be described with reference to the flowchart shown in FIG. The selling process shown in FIG. 10 may be executed at the timing when the above-described process shown in FIG. 7 is executed, or may be executed periodically independently of the process shown in FIG. ..

Here, by executing the processing shown in FIG. 7 described above, the inventory data storage unit 105 has already stored the inventory data indicating the inventory quantity of the drug (medicine to which the JAN code is attached) in the first dispensing pharmacy. (Managed).

In this case, the processes of steps S21 to S24 are executed for each JAN code included in the inventory data indicating the inventory quantity of the drug in the first dispensing pharmacy. Hereinafter, the JAN code that is the target of the processing of steps S21 to S24 will be referred to as the target JAN code.

First, the exhibition processing unit 110 acquires inventory data including the target JAN code (step S21).

Next, the exhibition processing unit 110 has a change in the stock quantity (that is, the stock quantity of the drug to which the target JAN code is added) included in the stock data acquired in step S21 within a predetermined period. It is determined whether or not (step S22).

Here, it is assumed that the inventory data stored in the inventory data storage unit 105 includes update date information indicating the date when the inventory quantity included in the inventory data is updated (changed).

According to this, when the period from the date indicated by the update date information included in the inventory data acquired in step S21 (that is, the update date) to the current date is shorter than the predetermined period, the exhibition processing unit 110 can determine that the inventory quantity has changed within a predetermined period. On the other hand, when the period from the date indicated by the update date information included in the inventory data acquired in step S21 (that is, the update date) to the current date is longer than the predetermined period, the exhibition processing unit 110 It can be determined that the number of stocks does not change within a predetermined period.

When it is determined that the stock quantity does not change (NO in step S22), the auction processing unit 110 puts up the medicine to which the target JAN code is added (that is, the immovable stock medicine whose stock quantity does not change). To generate exhibition data (step S23).

In step S23, the exhibition data including the target JAN code and the drug information on the drug to which the target JAN code is given is generated.

The auction data generated in step S23 is registered (stored) in the auction data storage unit 113 (step S24).

Here, FIG. 11 shows an example of the data structure of the exhibition data stored in the exhibition data storage unit 113. As shown in FIG. 11, the exhibition data includes a store ID, JAN code, quantity, drug price ratio, and expiration date.

The store ID is identification information for identifying a dispensing pharmacy that sells medicines. The JAN code is a JAN code given to a drug (medicine in a packaging unit for sale) put up by a dispensing pharmacy identified by the associated store ID.

The quantity is the quantity of the drug (medicine to which the associated JAN code is attached) put up by the dispensing pharmacy identified by the associated store ID.

The drug price ratio is the ratio of the selling price to the official price of the drug (medicine to which the associated JAN code is assigned) put up by the dispensing pharmacy identified by the associated store ID. The official price of a drug is a price that is set in advance for the drug by the country or a prescribed institution.

The expiration date is the remaining period until the expiration date of the drug (medicine to which the associated JAN code is assigned) put up by the dispensing pharmacy identified by the associated store ID.

The quantity, the drug price ratio, and the expiration date included in the auction data correspond to the drug information on the drug auctioned by the dispensing pharmacy identified by the associated store ID.

The quantity included in the exhibition data corresponds to the number of stocks included in the inventory data (inventory data including the JAN code included in the exhibition data) stored in the inventory data storage unit 105. The drug price ratio included in the auction data may be, for example, a preset value, or may be designated (input by the staff of the first dispensing pharmacy when the process of step S23 shown in FIG. 10 is executed). ). The expiration date included in the auction data may be based on the expiration date set when the drug to which the JAN code included in the auction data is attached is purchased. It may be designated (input) by the staff or the like of the first dispensing pharmacy when the processing of step S23 shown is executed. Regarding the quantity included in the exhibition data, the staff of the first dispensing pharmacy may make a final decision by confirming the actual stock quantity.

In the example shown in FIG. 11, the exhibition data storage unit 113 stores exhibition data 113a and 113b.

The exhibition data 113a includes a store ID “X1”, a JAN code “JAN code 11”, a quantity “500 tablets×1 bottle”, a drug price ratio “80%”, and an expiration date “◯month”. According to this exhibition data 113a, the dispensing pharmacy identified by the store ID "X1" is exhibiting a drug to which the "JAN code 11" is assigned, and the quantity of the drug is 500 tablets x 1 bottle, It is shown that the drug price ratio of the drug is 80% and the expiration date (remaining until) of the drug is ◯ months.

Further, the exhibition data 113b includes a store ID “X2”, a JAN code “JAN code 12”, a quantity “10 tablet sheets×20”, a drug price ratio “70%”, and an expiration date “×month”. According to this auction data 113b, the dispensing pharmacy identified by the store ID “X2” is exhibiting a drug to which the “JAN code 12” is attached, and the quantity of the drug is 10 tablets sheet×20. It is shown that the drug price ratio of the drug is 70% and the expiration date (remaining until) of the drug is x months.

Although only the exhibition data 113a and 113b have been described here, other exhibition data may be stored in the exhibition data storage unit 113.

Returning to FIG. 10 again, when the process of step S24 is executed, whether or not the processes of steps S21 to S24 have been executed for all JAN codes included in the inventory data indicating the stock quantity of the drug in the first dispensing pharmacy. Is determined (step S25).

When it is determined that the process has not been executed for all JAN codes (NO in step S25), the process returns to step S21 and the process is repeated. In this case, the processing is executed with the JAN code for which the processing of steps S21 to S24 has not been executed as the target JAN code.

On the other hand, if it is determined that the processing has been executed for all JAN codes (YES in step S25), the processing shown in FIG. 10 is ended.

According to the auctioning process shown in FIG. 10 described above, it is possible to automatically place an auction for a drug in immovable inventory in which the inventory quantity managed by the inventory management device 10 does not change.

In the present embodiment, the exhibition data has been described as being generated in step S23 shown in FIG. 10 described above, but the exhibition data may be generated at the first store terminal 20a provided in the first dispensing pharmacy, for example. It may be generated by the staff of the first dispensing pharmacy specifying a JAN code or the like. That is, the medicine managed in the first dispensing pharmacy may be automatically put up, for example, when the stock quantity is not changed, or may be put up manually by the staff of the first dispensing pharmacy.

Further, although the case where the drug is put up from the first dispensing pharmacy has been described in FIG. 10, it is also possible to put the drug at another dispensing pharmacy such as the second dispensing pharmacy.

Next, an example of the processing procedure of the above-mentioned purchase reservation processing will be described with reference to the flowchart shown in FIG. The purchase reservation process shown in FIG. 12 is executed, for example, according to the operation of the staff of the second dispensing pharmacy with respect to the second store terminal 20b.

Here, the staff of the second dispensing pharmacy can reserve the purchase of the desired drug in advance, for example, expecting to be put up by another dispensing pharmacy (for example, the first dispensing pharmacy). In this case, the staff of the second dispensing pharmacy can specify the type of drug to be reserved for purchase and the conditions regarding the drug by operating the second store terminal 20b provided in the second drug dispensing pharmacy. .. It should be noted that, for example, a YJ code is designated as the type of drug.

In this case, the purchase reservation processing unit 111 receives the purchase reservation data including the YJ code and the condition designated by the staff of the second dispensing pharmacy according to the operation of the staff of the second dispensing pharmacy on the second store terminal 20b. It is generated (step S31).

The purchase reservation data generated in step S31 is registered (stored) in the purchase reservation data storage unit 114 (step S32).

According to the purchase reservation process shown in FIG. 12 described above, the staff of the second dispensing pharmacy operates the second store terminal 20b, and thereby the medicines that meet the YJ code and the conditions specified by the staff of the second dispensing pharmacy. You can book the purchase of.

Here, FIG. 13 shows an example of the data structure of the purchase reservation data stored in the purchase reservation data storage unit 114. As shown in FIG. 13, the purchase reservation data includes a store ID, registration date and time, YJ code, standard capacity, quantity, drug price ratio, and expiration date.

The store ID is identification information for identifying a dispensing pharmacy that reserves the purchase of medicines. The registration date and time is the date and time when the dispensing pharmacy identified by the associated store ID reserved the purchase of the drug (that is, the date and time when the purchase reservation data was registered). The YJ code is the YJ code assigned to (the type of) the medicine reserved for purchase by the dispensing pharmacy identified by the associated store ID.

The standard capacity is the standard capacity for the medicine (the medicine to which the associated YJ code is assigned) reserved for purchase by the dispensing pharmacy identified by the associated store ID. The standard capacity corresponds to the packaging unit for sale, and includes, for example, a bottle or a 10-tablet sheet.

The quantity is the lower limit of the quantity of the medicine (the medicine to which the associated YJ code is assigned) reserved for purchase by the dispensing pharmacy identified by the associated store ID.

The drug price ratio is the ratio of the selling price to the official price of the drug (the drug with the associated YJ code) reserved for purchase by the dispensing pharmacy identified by the associated store ID. It is a range.

The expiration date is the lower limit of the remaining period until the expiration date of the drug (the drug with the associated YJ code) reserved for purchase by the dispensing pharmacy identified by the associated store ID. It is a value.

The standard capacity, the quantity, the drug price ratio, and the expiration date included in the purchase reservation data correspond to the conditions regarding the drug for which the dispensing pharmacy identified by the store ID included in the purchase reservation data reserves the purchase.

In the example shown in FIG. 13, the purchase reservation data storage unit 114 stores purchase reservation data 114a and 114b.

The purchase reservation data 114a includes a store ID "Y1", a registration date and time "10:30 on November 10, 2018", a YJ code "YJ code 1", a standard capacity "bottle", a quantity "400 tablets", and a drug price. Including the rate "65% to 75%" and the expiration date "Δ months". According to the purchase reservation data 114a, the dispensing pharmacy identified by the store ID "Y1" reserves the purchase of the drug to which the "YJ code 1" is given at 10:30 on November 10, 2018. The condition for the drug is that the standard capacity is a bottle, the quantity is 400 tablets or more, the drug price ratio is 65% to 75%, and the expiration date (remaining period until) is Δ months or more. Has been shown to be.

Further, the purchase reservation data 114b includes the store ID “Y2”, the registration date and time “November 11, 2018 11:10”, the YJ code “YJ code 2”, the standard capacity “10 tablets/sheet”, and the quantity “30”. The drug price ratio "60% to 70%" and the expiration date "□ months" are included. According to the purchase reservation data 114b, the dispensing pharmacy identified by the store ID "Y2" reserves the purchase of the drug to which the "YJ code 2" is given at 11:10 on November 11, 2018. The condition for the drug is that the standard capacity is 10 tablet sheets, the quantity is 30 or more, the drug price ratio is 60% to 70%, and the expiration date (remaining period until) is □ months or more. Is shown.

Although only the purchase reservation data 114a and 114b have been described here, other purchase reservation data may be stored in the purchase reservation data storage unit 114.

Further, in the example shown in FIG. 13, the purchase reservation data includes a YJ code, but a JAN code may be included instead of the YJ code.

Next, an example of the processing procedure of the above-described matching processing will be described with reference to the flowchart in FIG.

The matching process shown in FIG. 14 is executed when, for example, new exhibition data is registered in the exhibition data storage unit 113.

In the following description, the new exhibition data registered in the exhibition data storage unit 113 will be referred to as target exhibition data. Here, it is assumed that the target exhibition data is data indicating the medicine exhibited by the above-mentioned first dispensing pharmacy. That is, the dispensing pharmacy identified by the store ID included in the target exhibition data is the first dispensing pharmacy.

First, the matching processing unit 112 acquires target exhibition data from the exhibition data storage unit 113 (step S41).

Next, the matching processing unit 112 executes the processing of steps S42 to S45 for each of the purchase reservation data stored in the purchase reservation data storage unit 114. Hereinafter, the purchase reservation data for which the processes of steps S42 to S45 are executed will be referred to as target purchase reservation data.

In this case, the matching processing unit 112 acquires the target purchase reservation data from the purchase reservation data storage unit 114 (step S42).

When the process of step S42 is executed, the matching processing unit 112 identifies the YJ code corresponding to the JAN code included in the target exhibition data based on the corresponding data stored in the corresponding data storage unit 103, and the JAN concerned. It is determined whether the YJ code specified from the code matches the YJ code included in the target purchase reservation data. Accordingly, the matching processing unit 112 determines whether the JAN code included in the target exhibition data is the JAN code corresponding to the YJ code included in the target purchase reservation data (step S43).

When it is determined that the JAN code included in the target exhibition data is the JAN code corresponding to the YJ code included in the target purchase reservation data (YES in step S43), the matching processing unit 112 causes the drug included in the target exhibition data. It is determined whether the information satisfies the conditions included in the target purchase reservation data (step S44).

In step S44, the packaging unit for sale of the drug to which the JAN code included in the target exhibition data is attached matches the standard capacity included in the target purchase reservation data, and the quantity included in the target exhibition data is the target purchase reservation data. Is greater than or equal to the quantity included in, the drug price ratio included in the target auction data is within the drug price ratio included in the target purchase reservation data, and the expiration date included in the target auction data is included in the target purchase reservation data. If the expiration date is not less than the expiration date, it is determined that the drug information included in the target exhibition data satisfies the condition included in the target purchase reservation data.

Although detailed description is omitted, specifically, for example, when the target exhibition data is the exhibition data 113a shown in FIG. 11 and the target purchase reservation data is the purchase reservation data 114a shown in FIG. Since the drug price ratio included in the data 113a is not within the range of the drug price ratio included in the purchase reservation data 114a, it is determined that the drug information included in the target exhibition data does not satisfy the condition included in the target purchase reservation data. ..

On the other hand, for example, when the target exhibition data is the exhibition data 113b shown in FIG. 11 and the target purchase reservation data is the purchase reservation data 114b shown in FIG. 13, the expiration date included in the exhibition data 113b becomes the purchase reservation data 114b. If it is equal to or longer than the included expiration date, it is determined that the drug information included in the target exhibition data satisfies the condition included in the target purchase reservation data.

When it is determined that the drug information included in the target exhibition data satisfies the condition included in the target purchase reservation data (YES in step S44), the matching processing unit 112 stores the target purchase reservation data in the matching list with the target exhibition data. Add (step S45).

Although the case where the target purchase reservation data includes the YJ code has been described here, when the target purchase reservation data includes the JAN code, the target purchase reservation data includes the JAN code and the target exhibition data. When it is determined that the included JAN code matches and the drug information included in the target exhibition data satisfies the condition included in the target purchase reservation data, the target purchase reservation data is added to the matching list.

If it is determined in step S43 that the JAN code included in the target exhibition data is not the JAN code corresponding to the YJ code included in the target purchase reservation data (NO in step S43), the processes in steps S44 and S45 are not executed. .. When it is determined in step S44 that the drug information included in the target exhibition data does not satisfy the condition included in the target purchase reservation data (NO in step S44), the process of step S45 is not executed.

Next, it is determined whether or not the processes of steps S42 to S45 have been executed for all purchase reservation data stored in the purchase reservation data storage unit 114 (step S46).

If it is determined that the process has not been executed for all purchase reservation data (NO in step S46), the process returns to step S42 and the process is repeated. In this case, the purchase reservation data for which the processing of steps S42 to S45 has not been executed is used as the target purchase reservation data, and the processing is executed.

On the other hand, when it is determined that the processing has been executed for all the purchase reservation data (YES in step S46), the matching processing unit 112 selects the purchase reservation data from the purchase reservation data added to the matching list in step S45. The purchase reservation data with the earliest registration date and time included in the data is specified, and the target exhibition data is matched with the specified purchase reservation data. In this case, the matching processing unit 112 transmits the target exhibition data to the store terminal provided in the dispensing pharmacy identified by the store ID included in the purchase reservation data matched with the target exhibition data (step). S44).

In the following description, the dispensing pharmacy identified by the store ID included in the purchase reservation data matched with the target exhibition data is the second dispensing pharmacy, and the store terminal to which the target exhibition data is transmitted is the second store terminal. 20b.

When the target exhibition data is transmitted to the second shop terminal 20b in step S44, the target exhibition data is displayed on the second shop terminal 20b.

Here, when the target exhibition data is displayed on the second store terminal 20b, the staff of the second dispensing pharmacy confirms the content of the target exhibition data (that is, the content of the drug listing from the first dispensing pharmacy), It is possible to perform an operation (hereinafter, referred to as a purchase instruction operation) to instruct the second store terminal 20b to purchase the drug. When the purchase instruction operation is performed on the second store terminal 20b, the purchase instruction operation (that is performed) is notified from the second store terminal 20b to the inventory management device 10.

The matching processing unit 112 determines whether or not a purchase instruction operation has been performed on the second store terminal 20b based on the presence or absence of the notification from the second store terminal 20b (step S48).

When it is determined that the purchase instruction operation has been performed (YES in step S48), the matching processing unit 112 is indicated by the target exhibition data based on the target exhibition data and the purchase reservation data matched with the target exhibition data. A process for purchasing the medicine (medicine put up by the first dispensing pharmacy) by the second dispensing pharmacy identified by the store ID included in the purchase reservation data is executed (step S49).

Here, if the second dispensing pharmacy purchases a drug (hereinafter referred to as a target drug) submitted from the first dispensing pharmacy as described above, the first dispensing pharmacy stores the target drug in the second dispensing pharmacy. Need to be shipped to. Therefore, in step S49, the first dispensing pharmacy is notified that the target drug needs to be shipped to the second dispensing pharmacy, for example, via the first store terminal 20a provided in the first dispensing pharmacy. To do. The information necessary for shipping the target drug (for example, the address of the second dispensing pharmacy) may be managed in advance in the inventory management device 10, or may be acquired from an external device different from the inventory management device 10. May be done. Here, although it is described that the target drug is directly shipped to the second dispensing pharmacy, the target drug is once shipped to, for example, a predetermined distribution center, and then from the distribution center to the second dispensing pharmacy. It may be shipped.

Further, when the second dispensing pharmacy purchases the target drug, the second dispensing pharmacy needs to pay the first dispensing pharmacy. Therefore, in step S49, processing (payment processing) relating to payment of the target drug by the second dispensing pharmacy is executed based on the drug price ratio included in the target exhibition data. This payment processing is executed using, for example, information of a credit card registered in advance. The information necessary for calculating the amount to be paid by the second dispensing pharmacy to the first dispensing pharmacy (for example, the official price of the drug indicated by the target exhibition data) may be managed in advance by the inventory management device 10. However, it may be acquired from an external device different from the inventory management device 10.

When the process of step S49 described above is executed, the matching processing unit 112 stores, in the order data storage unit 102, order data indicating that the target drug has been ordered by the second dispensing pharmacy, for example. In this case, the order quantity of the target drug is reflected in the inventory quantity (inventory data) of the target drug at the second dispensing pharmacy. Further, the matching processing unit 112 updates the stock quantity of the target drug in the first dispensing pharmacy included in the inventory data stored in the inventory data storage unit 105, for example, based on the quantity included in the target exhibition data (that is, , If the target drug of the first dispensing pharmacy is sold, the sales number is subtracted from the inventory number of the target drug of the first dispensing pharmacy).

On the other hand, when it is determined that the purchase instruction operation is not performed (NO in step S48), the process returns to step S47 and the process is repeated. In this case, the purchase reservation data with the earliest registration date and time is specified from the purchase reservation data other than the purchase reservation data for which the process of step S47 has already been executed among the purchase reservation data added to the matching list, and the purchase reservation data with the earliest registration date is specified. The process is executed.

That is, in the present embodiment, the purchase reservation data added to the matching list is matched with the target exhibition data in the order of earlier registration date and time, and the staff of the dispensing pharmacy identified by the store ID included in the matched purchase reservation data is The target drug can be purchased by performing a purchase instruction operation on a store terminal provided in the dispensing pharmacy.

Although not shown in FIG. 14, if it is determined that the purchase instruction operation is not performed on all of the purchase reservation data added to the matching list, the process of FIG. 14 is terminated. To do. As for the exhibition data for which the purchase instruction operation has not been performed (that is, the exhibition data for which the purchase processing has not been executed), the processing shown in FIG. 14 is executed again after, for example, a predetermined period has elapsed. Shall be.

Here, the description has been made assuming that the purchase process is executed when the purchase instruction operation is performed. However, for example, when the purchase cancel operation is not performed within a predetermined period (for example, 24 hours). Alternatively, the purchase process may be automatically executed.

Although the purchase reservation data added to the matching list has been described as being matched with the target exhibition data in the order of the registration date and time, the purchase reservation data has a high compatibility rate with the conditions included in the target exhibition data, for example. It may be matched with the target exhibition data in order, or may be matched based on another viewpoint.

As described above, in the present embodiment, when the inventory quantity indicated by the inventory data stored in the inventory data storage unit 105 has not changed for a predetermined period, the inventory quantity has not changed. The auction data for selling a drug is generated, and the generated auction data is stored in the auction data storage unit 113.

In the present embodiment, with such a configuration, for example, a drug that has been purchased (ordered) at the first dispensing pharmacy but is stored for a long time (that is, a drug in immovable inventory) is automatically It is possible to sell at. That is, in the present embodiment, it becomes possible to avoid the situation in which a fixed inventory drug must be discarded due to the expiration of the usage period, and to effectively utilize the drug.

Further, in the present embodiment, purchase reservation data for the second dispensing pharmacy (other dispensing pharmacy) to reserve the purchase of the drug is stored in the purchase reservation data storage unit 114 and stored in the exhibition data storage unit 113. The exhibition data and the purchase reservation data are matched.

In the present embodiment, the auction data includes the JAN code given to the drug put up by the first dispensing pharmacy and the drug information about the drug. Further, the purchase reservation data includes the type of medicine (YJ code) for which the second dispensing pharmacy reserves the purchase and the condition designated by the second dispensing pharmacy.

In the present embodiment, the JAN code included in the exhibition data and the YJ code included in the purchase reservation data have a correspondence relationship, and the drug information included in the exhibition data is included in the purchase reservation data. If the conditions are satisfied, the exhibition data is matched with the purchase reservation data. When the exhibition data and the purchase reservation data are matched, the process for the second dispensing pharmacy to purchase the drug indicated by the exhibition data (the drug with the JAN code included in the exhibition data). To be executed.

In the present embodiment, with such a configuration, for example, when reservation of purchase of a desired drug by the second dispensing pharmacy is reserved and the drug is put up by another dispensing pharmacy (for example, the first dispensing pharmacy), It is possible to realize that the second dispensing pharmacy purchases the drug.

Although the inventory management device 10 has been described as including the storage units 113 and 114 in the present embodiment, at least a part of the storage units 113 and 114 is provided in an external device or the like of the inventory management device 10. Good. In this case, the inventory management device 10 may be configured to acquire (receive) necessary data from an external device.

Further, although the inventory management device 10 has been described as one device in the present embodiment, the inventory management device 10 is realized by, for example, a cooperative operation of a plurality of devices as described in the first embodiment. It doesn't matter.

The method described in each of the above-described embodiments is a program that can be executed by a computer as a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), optical disk (CD-ROM, DVD, etc.) magneto-optical disk ( MO), a semiconductor memory, or other storage medium for distribution.

The storage medium may have any storage format as long as it can store a program and is readable by a computer.

Further, an OS (operating system) operating on the computer based on an instruction of a program installed in the computer from the storage medium, MW (middleware) such as database management software, network software, or the like realizes this embodiment. A part of each processing of may be executed.

Further, the storage medium in the present invention is not limited to a medium independent of a computer, and includes a storage medium in which a program transmitted via a LAN, the Internet, etc. is downloaded and stored or temporarily stored.

Further, the number of storage media is not limited to one, and the case where the processing in each embodiment is executed from a plurality of media is also included in the storage media of the present invention, and the medium configuration may be any configuration.

The computer according to the present invention executes each process in the present embodiment based on the program stored in the storage medium, and one device such as a personal computer or a plurality of devices are network-connected. It may have any configuration such as a system.

In addition, the computer in the present invention is not limited to a personal computer, but also includes an arithmetic processing unit, a microcomputer, and the like included in information processing equipment, and is a generic term for equipment and devices that can realize the functions of the present invention by a program. There is.

The invention of the present application is not limited to the above embodiments as they are, and can be embodied by modifying the constituent elements within a range not departing from the gist of the invention in an implementation stage. Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, the constituent elements in different embodiments may be combined appropriately.

10... Inventory management device, 20... Store terminal, 20a... First store terminal, 20b... Second store terminal, 11... Bus, 12... Nonvolatile memory, 13... CPU, 14... Main memory, 15... Communication device, 101 Dispensing data storage unit (first storage unit), 102... Order data storage unit (fourth storage unit), 103... Corresponding data storage unit, 104... Handling item data storage unit (second storage unit), 105... Inventory data Storage unit (third storage unit), 106... First calculation unit, 107... Correction unit, 108... Second calculation unit, 109... Order processing unit, 110... Exhibition processing unit, 111... Purchase reservation processing unit, 112... Matching Processing section, 113... Exhibition data storage section (fifth storage means), 114... Purchase reservation data storage section (sixth storage means).

Claims (14)

A first storage means for storing dispensing data including a first code given to a drug dispensed at a dispensing pharmacy and a first usage amount of the drug in the dispensing;
Second storing means for storing handling item data including a second code given to the medicine in the packaging unit for sale handled in the dispensing pharmacy;
The first usage amount of the medicine to which the first code included in the dispensing data stored in the first storage means is given and the second code included in the handling item data stored in the second storage means A first calculating means for calculating a second usage amount of the medicine for each of the sales packaging units based on the
Second calculating means for calculating the expected stock quantity of the medicine for each of the sales packaging units based on the calculated second usage amount;
A third storage unit for storing the inventory data indicating the calculated expected inventory quantity. The inventory according to claim 1, wherein the second calculation unit calculates the expected inventory quantity of the drug by subtracting the calculated second usage amount from the inventory quantity of the drug managed by the inventory management device. Management device. The dispensing data further includes packaging information indicating whether or not to package the drug to which the first code included in the dispensing data is added,
The first calculating means is configured to determine the second amount based on a ratio of the first usage amount of the packaged drug to the first usage amount of the drug to which the first code included in the dispensing data is added. The inventory management device according to claim 1, which calculates a usage amount. Fourth storing means for storing order data including a second code given to the medicine of the packaging unit for sale ordered at the dispensing pharmacy and an order amount of the medicine given the second code;
Correction means for correcting the calculated second usage amount based on the ratio of the order amount of the medicine to which the second code included in the order data stored in the fourth storage means is added. The inventory management device according to any one of claims 1 to 3, further comprising: It further comprises ordering processing means for ordering the medicine to which the second code is attached or executing processing of notifying the order based on the expected stock quantity indicated by the inventory data stored in the third storage means. The inventory management device according to claim 1. A third calculating the remaining number of days of dispensing of the medicine to which the second code is given, based on the expected stock quantity indicated by the inventory data stored in the third storing means and the calculated second usage amount. Further comprising a calculating means,
The inventory according to claim 5, wherein when the calculated number of dispensing days is less than or equal to a predetermined value, the order processing unit orders a drug for which the number of dispensing days is calculated or notifies the order. Management device. The order processing means orders the number of the medicines obtained by subtracting an expected stock quantity indicated by the stock data stored in the third storage means from a predetermined upper limit quantity or executes processing for notifying the order. The inventory management device according to claim 5 or 6. Change to change the expected stock quantity indicated by the stock data stored in the third storage means when the order contents by the order processing means are changed based on the operation on the terminal installed in the dispensing pharmacy The inventory management device according to any one of claims 5 to 7, further comprising means. When the expected inventory quantity indicated by the inventory data stored in the third storage means has not changed for a predetermined period, the exhibition data for exhibiting a drug for which the expected inventory quantity has not changed. A listing processing means for generating
The inventory management device according to claim 1, further comprising: a fifth storage unit that stores the generated auction data. A sixth storage means for storing purchase reservation data for the other dispensing pharmacy to purchase the medicine;
Matching processing means for matching the auction data with the purchase reservation data,
The auction data includes a second code given to a drug put up by the dispensing pharmacy and drug information about the drug,
The purchase reservation data includes a first code or a second code given to a drug for which the other dispensing pharmacy reserves a purchase, and a condition designated by the other dispensing pharmacy.
The matching processing means,
When the purchase reservation data includes the first code, the second code included in the exhibition data and the first code included in the purchase reservation data have a correspondence relationship, and the drug information is When the condition is satisfied, the auction data is matched with the purchase reservation data, and when the purchase reservation data includes a second code, the second code included in the auction data and the purchase reservation data are included. The inventory management device according to claim 9, wherein the auction data is matched with the purchase reservation data when the included second code matches and the drug information satisfies the condition. 11. The process for the other dispensing pharmacy to purchase a drug to which the second code included in the auction data is attached when the auction data and the purchase reservation data are matched. Inventory management equipment. The drug information included in the auction data includes the quantity of the drug auctioned from the dispensing pharmacy,
The expected stock quantity indicated by the stock data stored in the third storage means is updated based on the quantity included in the drug information when the exhibition data is matched with the purchase reservation data. Inventory management device described. A first storage means for storing dispensing data including a first code given to a drug dispensed in a dispensing pharmacy and a first usage amount of the drug in the dispensing, and a sales packaging unit handled in the dispensing pharmacy. An inventory management method executed by an inventory management device, comprising: a second storage means for storing handling item data including a second code assigned to the medicine.
The first usage amount of the medicine to which the first code included in the dispensing data stored in the first storage means is given and the second code included in the handling item data stored in the second storage means Calculating a second usage amount of the pharmaceutical product for each of the packaging units for sale based on the following:
Calculating the expected stock quantity of the medicine for each of the packaging units for sale based on the calculated second usage amount;
Storing the inventory data indicating the calculated expected inventory quantity in a third storage means. A first storage means for storing dispensing data including a first code given to a drug dispensed in a dispensing pharmacy and a first usage amount of the drug in the dispensing, and a packaging unit for sale handled in the dispensing pharmacy. A program executed by a computer of an inventory management device, comprising: a second storage means for storing handling item data including a second code assigned to the medicine;
On the computer,
The first code used in the dispensing data stored in the first storage means is assigned the first usage amount of the drug, and the second code is included in the handling item data stored in the second storage means. Calculating a second usage amount of the pharmaceutical product for each of the packaging units for sale based on the following:
Calculating the expected stock quantity of the medicine for each of the packaging units for sale based on the calculated second usage amount;
A step of storing the inventory data indicating the calculated expected inventory quantity in a third storage means.

Images