JP6896780B2 - Inventory management equipment, inventory management methods and programs - Google Patents

Description

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

Generally, in a dispensing pharmacy, a drug (drug) is dispensed to a patient based on a prescription issued by a hospital.

However, if the dispensing pharmacy lacks the medicines required for dispensing, even if the patient brings a prescription to the dispensing pharmacy, the dispensing may not be possible.

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

Japanese Unexamined Patent Publication No. 2004-062607

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 pharmaceutical products in a dispensing pharmacy.

According to one aspect of the present invention, the inventory management device includes a first storage means, a second storage means, a first calculation means, a second calculation means, a third storage means, and a fourth storage means. Equipped with. 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 the handling item data including the second code given to the drug of the packaging unit for sale handled in the dispensing pharmacy. The first calculation means is the first usage amount of the drug to which the first code included in the dispensing data stored in the first storage means is given, and the handling item data stored in the second storage means. Based on the second code contained in the above, the second usage amount of the drug is calculated for each packaging unit for sale. The second calculation means calculates the expected number of pharmaceutical products in stock for each packaging unit for sale based on the calculated second usage amount. The third storage means stores inventory data indicating the calculated inventory quantity. The fourth storage means is a second code given to the drug for each packaging unit for sale ordered at the dispensing pharmacy and the drug for each packaging unit for sale to which the second code is given. Stores order data including order quantity. The second usage amount is corrected based on the ratio of the ordering amount for each sales packaging unit of the drug to which the second code included in the ordering data stored in the fourth storage means is given. ..

The present invention makes it possible to manage the inventory of pharmaceutical products in dispensing pharmacies.

The figure which shows an example of the structure of the inventory management system in 1st Embodiment of this invention. The figure which shows an example of the hardware composition of the inventory management apparatus. The block diagram which shows an example of the functional structure of the inventory management apparatus. 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 correspondence data stored in the correspondence data storage part. The flowchart which shows an example of the processing procedure of the inventory management apparatus. The figure which shows an example of the structure of the inventory management system in 2nd Embodiment of this invention. The block diagram which shows an example of the functional structure of the inventory management apparatus. A flowchart showing an example of the processing procedure of the listing process. 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 processing procedure of a matching process.

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

The inventory management system in the present embodiment is, for example, a drug required for dispensing in a store (hereinafter, simply referred to as a dispensing pharmacy) such as a dispensing pharmacy that dispenses a drug based on a prescription issued by a hospital to a patient. It 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 connected so as to be able to communicate with each other 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 pharmaceutical products in the above-mentioned dispensing pharmacy.

The store terminal 20 is a terminal (electronic device) installed in a dispensing pharmacy in which the inventory of pharmaceutical products is managed, and is used by the staff of the dispensing pharmacy (for example, a pharmacist). For example, a personal computer (PC) can be used as the store terminal 20, but other electronic devices such as smartphones and tablet terminals 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, the non-volatile memory 12, the CPU 13, the main memory 14, the communication device 15, and the like are connected to the bus 11. The non-volatile memory 12 and the main memory 14 constitute a storage device of the inventory management device 10.

The non-volatile memory 12 stores, for example, various programs including an operating system (OS) and a program for managing the inventory of the above-mentioned pharmaceutical products (hereinafter, referred to as an inventory management program).

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

The main memory 14 is used, for example, as a work area or the like 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). May be good.

The communication device 15 controls communication executed with an external device such as a store terminal 20 via the network 30 described above, for example. According to the communication device 15, for example, a wireless communication function such as a wireless LAN and Wifi (registered trademark) can be realized.

FIG. 3 is a block diagram showing an example of the functional configuration of the inventory management device 10 according to the present 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 handling item data storage unit 104, an inventory data storage unit 105, and a first calculation unit 106. It includes a correction unit 107, a second calculation unit 108, and an order processing unit 109.

In the present embodiment, each of the storage units 101 to 105 is realized by, for example, the non-volatile memory 12 shown in FIG. 2 or another storage device or the like.

Further, in the present embodiment, each unit 106 to 109 executes, for example, an inventory management program in which the CPU 13 (that is, the computer of the inventory management device 10) shown in FIG. 2 is stored in the non-volatile memory 12, that is, software. It shall be realized by. This inventory management program can be stored in advance in a computer-readable storage medium and distributed. Further, the inventory management program may be downloaded to the inventory management device 10 via, for example, a network 30 or the like.

Here, each part 106 to 109 has been described as being realized by software, but each part 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 related to dispensing that has already been performed at the dispensing pharmacy where the store terminal 20 is installed. The dispensing data stores the dispensing data including the first code given to the drug dispensed at the dispensing pharmacy and the amount of the drug used in the dispensing. The first code is a code given to a drug in units of type (for example, drug name).

The dispensing data is, for example, data stored in a receipt computer used for creating a medical fee statement called a receipt, and can be acquired from the receipt computer.

The ordering data storage unit 102 stores ordering data (ordering data indicating that the drug has been ordered at the dispensing pharmacy) regarding the past ordering of the drug at the dispensing pharmacy where the store terminal 20 is installed. The ordering data includes the second code given to the drug in the packaging unit for sale ordered at the dispensing pharmacy and the order quantity of the drug to which the second code is given. The second code is a packaging unit for sale, that is, a code given to a drug as a product in distribution to, for example, a dispensing pharmacy.

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

That is, even if the same first code is given on the dispensing data, the drugs having different packaging units for sale are managed by being given different second codes on the order data. That is, in the present 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 medicines is managed based on the amount of medicines used to which the first code included in the dispensing data is attached. In this case, the first code included in the dispensing data is used. From the amount of medicines used, it is necessary to estimate the amount of medicines given to each of the second codes corresponding to the first code.

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

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

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

The drugs handled at the dispensing pharmacy include not only drugs that have already been ordered at 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 ordering data. In the present embodiment, it is assumed that the handling item data is managed separately from the ordering data as described above, 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 assigned, the corresponding data stored in the corresponding data storage unit 103, and the handling item data. 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 the drug used calculated by the first calculation unit 106 is an expected 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 number of inventories of the drug for each packaging unit for sale based on the amount of the drug used corrected by the correction unit 107. The number of pharmaceutical products in stock calculated by the second calculation unit 108 is an expected value (that is, the expected number of inventories).

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

The order processing unit 109 orders medicines 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 medicines to which a JAN code is assigned). ) Execute 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 remarks.

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

Prescription drug refers to a drug dispensed based on a 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 given to the drug with the drug name.

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

The remarks indicate the contents described in, for example, the remarks column of the prescription identified by the associated prescription ID. In the remarks column of the prescription, for example, whether or not to package the medicines dispensed based on the prescription is described. Therefore, the remarks included in the dispensing data include information indicating whether or not the drug is packaged (hereinafter referred to as package information). In addition, one package means, for example, the delivery of different medicines (tablets, etc.) of the same type at the same time zone (dose time) in one bag. The necessity of packaging (that is, whether or not to package) is instructed by the doctor at the hospital issuing the prescription.

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

Dispensing data 101a contains prescription ID "1", patient name "A", dispensing date "November 22, 2018", prescription content "YJ code 1", quantity "quantity 1" and remarks "-". Including. According to this dispensing data 101a, on November 22, 2018, the "quantity 1" of "quantity 1" is based on the prescription identified by the prescription ID "1" issued to the patient whose patient name is "A". It is shown that the drug to which "YJ Code 1" is given has been dispensed. Further, according to the dispensing data 101a, it is shown that the medicines to which the "YJ code 1" dispensed based on the prescription identified by the prescription ID "1" is given are not packaged. ..

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

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

Dispensing data 101c includes prescription ID "2", patient name "B", dispensing date "November 23, 2018", prescription content "YJ code 3" quantity "quantity 3" and remarks "packaged". including. According to this dispensing data 101c, on November 23, 2018, "Quantity 3" "" based on the prescription identified by the prescription ID "2" issued to the patient whose patient name is "B". It is shown that the drug to which "YJ Code 3" has been given has been dispensed. Further, according to the dispensing data 101c, it is shown that the medicines to which the "YJ code 3" dispensed based on the prescription identified by the prescription ID "2" is given are packaged.

Here, only the dispensing data 101a to 101c have been described, but the dispensing data storage unit 101 stores the 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, patient name, dispensing date, prescription content, quantity (usage amount) and remarks (packaged information). May include some of these omitted, or may further include other information.

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 is managed independently of the receipt computer. (That is, it does not have to be the data obtained from the receipt computer).

FIG. 5 shows an example of the data structure of the 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 order date and the order quantity.

The ordered drug indicates a drug ordered at a dispensing pharmacy. The content of the order includes the JAN code given to the drug as a product ordered at the dispensing pharmacy (that is, the drug in the packaging unit for sale).

The order date is the date on which the drug indicated by the associated ordered drug (that is, the drug in the packaging unit for sale to which the JAN code is attached) was ordered.

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

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

The ordering data 102a includes the ordered drug "JAN code 11", the ordering date "October 1, 2018", and the ordering quantity "500 tablets x 1 bottle". According to the ordering data 102a, it is shown that the drug in the packaging unit for sale to which the "JAN code 11" is given was ordered on October 1, 2018 in the quantity of 500 tablets x 1 bottle. ..

In addition, the ordering data 102b includes the ordered drug "JAN code 12", the ordering date "October 1, 2018", and the ordering quantity "10 tablet sheets x 50". According to this ordering data 102b, it is shown that the drug for sale packaging unit to which "JAN code 12" is given was ordered on October 1, 2018 in a quantity of 10 tablet sheets x 50. ..

Here, only the ordering data 102a and 102b have been described, but the ordering data storage unit 102 stores the ordering data for each drug ordered at the dispensing pharmacy.

Further, in the example shown in FIG. 5, the ordering data has been described as including the ordered drug, the ordering date, and the ordering quantity, but the ordering data may be partially 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 corresponding data includes the YJ code and the 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 drug for each packaging unit for sale, and is included in, for example, order data, handling item data, and inventory data.

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

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

On the other hand, the corresponding data 103b includes the YJ code "YJ code 1" and the JAN code "JAN code 12" in association with each other. According to the corresponding data 103b, the drug to which "YJ code 1" is given is sold (distributed) as a drug (that is, a product) in a packaging unit for sale to which "JAN code 12" is given. Is shown).

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

That is, in the present embodiment, as described above, a plurality of JAN codes (here, "JAN code 11" and "JAN code 12") are used for the same YJ code (here, "YJ code 1"). It is associated, and there is a one-to-many relationship between the YJ code and the JAN code.

Here, only the corresponding data 103a and 103b have been described, but the corresponding data storage unit 103 stores the corresponding 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. 3 is at least a drug in a packaging unit for sale that is handled (or will be handled) at a dispensing pharmacy. Anything that includes the JAN code given to.

Further, 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 number of stocks 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 of FIG. 7.

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

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

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

The process shown in FIG. 7 shall be executed at predetermined intervals. Specifically, the process shown in FIG. 7 shall be executed, for example, once a day 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 where processing is executed for one of the YJ codes included in the dispensing data (hereinafter, referred to as a target YJ code) will be described.

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

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

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

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

When the process of step S2 is executed, the first calculation unit 106 is assigned 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 amount of the drug used (hereinafter referred to as the amount of the JAN code used) is calculated (step S3).

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

Next, the first calculation unit 106 includes the JAN included in the handling item data stored in the handling 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 a JAN code given to a drug that may have been used (a drug in a packaging unit for sale) when a drug to which the target YJ code is given is dispensed. ..

Here, for example, a JAN code (hereinafter referred to as a first JAN code) given to a drug to which the target YJ code is given and whose packaging state is bottled (that is, the packaging unit for sale is a bottle). The JAN code (hereinafter referred to as the second JAN code) given to a drug whose packaging state is sheet-like (that is, the packaging unit for sale is a 10-tablet sheet or a 14-tablet sheet, etc.) is specified. It shall be.

Here, as described above, the dispensing data includes packaged information (information indicating whether or not the drug to which the target YJ code is assigned is packaged). Therefore, the first calculation unit 106 is packaged in the usage amount of the target YJ code calculated in step S2 above based on the packaged information included in the dispensing data acquired in step S1. Calculate the ratio of the amount of medicines used to the amount of unpackaged medicines used (hereinafter referred to as the one-pack ratio).

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

In the present embodiment, from the above viewpoint, the usage amount for each JAN code is calculated by applying the one-pack 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 specified amount of the packaged drug is 10%, and the usage amount of the unpackaged drug is 90%), It is estimated that 10% of the amount of the target YJ code used is from bottled drugs (drugs to which the 1st JAN code is given). Similarly, it is estimated that 90% of the amount of the target YJ code used is from the sheet-shaped drug (the drug 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-mentioned processing.

Next, the correction unit 107 corrects the usage amount 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 the order data including the above-mentioned first JAN code (hereinafter referred to as the first order data) and the second JAN code among the order data stored in the order data storage unit 102. Acquire ordering data (hereinafter referred to as second ordering data). In this case, the correction unit 107 acquires the first order data and the second order data whose order date corresponds to a predetermined period (that is, regarding the order placed within the predetermined period).

The correction unit 107 is a drug (for example, a drug) to which the first JAN code is assigned 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. Calculate the past order ratio between the bottled drug) and the drug to which the second JAN code is given (for example, the sheet-shaped drug).

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

The correction unit 107 applies the corrected one-pack ratio to the usage amount of the target YJ code to obtain the usage amount of the first JAN code and the usage amount of the second JAN code (that is, the usage amount after correction). 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.

Note that, for example, when sufficient order data is not stored in the order data storage unit 102, 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 a target JAN code.

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

In the present embodiment, the order quantity of the drug to which the target JAN code included in the order data stored in the order data storage unit 102 is assigned is added to the inventory 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 order data (that is, the target JAN code) relating to the ordering of the drug to which the target JAN code is assigned, which was performed from the previous execution of the process of FIG. 7 to the present, is used. The order quantity included in the included order data) may be added to the number of stocks.

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

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

Here, in the present embodiment, where the process shown in FIG. 7 is executed, for example, every day, the target JAN code is assigned to the usage amount of the target JAN code corrected in step S4 above during the day. Corresponds to the amount of medicine used.

Therefore, the order processing unit 109 divides the inventory quantity of the target JAN code calculated in step S5 (the inventory quantity included in the inventory data including the target JAN code) by the usage amount of the target JAN code, thereby dividing the target JAN code. The number of remaining dispensing days of the drug to which the code is assigned (that is, the number of remaining days that can be dispensed with the current inventory quantity) is calculated (step S6).

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

When it is determined that the number of dispensing days is not equal to or greater than the threshold value (NO in step S7), the order processing unit 109 generates order data regarding the ordering of the drug to which the target JAN code is assigned (step S8). In step S8, for example, the target JAN code is set as the ordered drug, the shortest date on which the drug can be ordered at the present time is set as the order date, and the current target is from the predetermined upper limit number (upper limit value) of the inventory quantity. Order data is generated with the value obtained by subtracting the number of JAN stocks as the order quantity. The ordering date included in the ordering data generated in step S8 is, for example, a date in consideration of the above-mentioned remaining dispensing days (for example, a date near the time when the remaining dispensing days have elapsed from the present time, etc.). 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 for the drug to which the target JAN code is assigned).

Here, the staff of the dispensing pharmacy can change the order contents by checking the contents of the order data displayed on the store terminal 20 (that is, the order contents) and operating the store terminal 20. Specifically, the staff of the dispensing pharmacy can change, for example, the order date or the order quantity included in the order data displayed on the store terminal 20. The staff of the dispensing pharmacy can also 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 contents 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 contents have been changed (YES in step S9), the order processing unit 109 reflects the change in the order contents 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 shall be fed back to the inventory data stored in the inventory data storage unit 105.

In this case, the order processing unit 109 changes the number of stocks included in the stock data including the target JAN code based on the change in the order contents (step S11).
For example, if a change is made to delay the ordering time (ordering date), the actual inventory quantity is larger than the inventory quantity of the target JAN code managed by the inventory management device 10, so dispensing is performed. It is presumed that the pharmacy staff made such a change. Therefore, if a change is made to delay the ordering time, the amount of the target JAN code used corrected in step S4 above (that is, the drug to which the target JAN code is assigned during the day is used. The quantity is changed (increased) by adding the quantity obtained by multiplying the quantity to be delayed by the number of days delayed to the quantity of stock included in the stock data including the target JAN code. Similarly, when a change is made to reduce the order quantity or a change is made to cancel the order itself, the number of stocks included in the inventory data including the target JAN code shall be increased.

On the other hand, if the ordering time (ordering date) is changed to be earlier, the actual inventory quantity is smaller than the inventory quantity of the target JAN code managed by the inventory management device 10. It is presumed that the staff of the dispensing pharmacy made such a change. Therefore, if a change is made to advance the ordering time, the amount obtained by multiplying the usage amount of the target JAN code corrected in step S4 by the number of days earlier is included in the inventory data including the target JAN code. The inventory quantity is changed (decreased) by subtracting from the inventory quantity. Similarly, when a change is made to increase the order quantity, the number of stocks included in the stock data including the target JAN code shall be reduced.

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 contents 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 drug from the dispensing pharmacy. The order data may be sent directly to a pharmaceutical 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 elapses after the process of step S8 or step S10 is executed, or is instructed by the staff of the dispensing pharmacy via the store terminal 20. It may be executed accordingly.

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

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

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

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), the process of step S13 is executed, assuming that it is not necessary to order the drug to which the target JAN code is assigned.

If it is determined in step S9 that the order details 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 process shown in FIG. 7, the order for the drug to which the target JAN code is assigned is explained as being notified to the staff of the dispensing pharmacy, but the order is automatically placed without being notified. It can also be configured. In this case, the processes of steps S9 to S11 shown in FIG. 7 may be omitted.

Although the process to be executed for one of the YJ codes included in the dispensing data has been described in FIG. 7, the process shown in FIG. 7 is applied to each of the YJ codes included in the dispensing data. It shall be executed. As a result, in the inventory management device 10 according to the present embodiment, the inventory for each JAN code corresponding to each of the YJ codes included in the dispensing data is managed.

For example, the upper limit of the number of ordering processes executed in 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 processes of steps S5 to S11 shown in FIG. 7 may be repeated for each of the JAN codes, and the ordering process (that is, the process of step S12) may be collectively executed for the drugs that need to be ordered.

As described above, in the present embodiment, the amount of the drug used and the handling item data storage unit 104 to which the YJ code (first code) included in the dispensing data stored in the dispensing data storage unit 101 is assigned is stored. Based on the JAN code (second code) included in the handling item data, the usage amount of the drug is calculated for each packaging unit for sale, and the number of drugs in stock is sold based on the calculated usage amount. It is calculated for each packaging unit, and inventory data indicating the calculated number of stocks is stored in the inventory data storage unit 105.

In the present embodiment, with such a configuration, the inventory of pharmaceutical products (JAN code) at the dispensing pharmacy is appropriately taken into consideration in consideration of the correspondence between the YJ code included in the dispensing data and the JAN code included in the ordering data and the like. Can be managed. Further, in the present embodiment, by realizing such inventory management of pharmaceutical products, it is possible to avoid a situation in which dispensing cannot be performed due to a shortage of pharmaceutical products, for example, when a patient visits a dispensing pharmacy. It becomes.

Further, in the present embodiment, the usage amount of the JAN code (that is, the usage amount for 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. Is calculated. 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 packaged 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 drug to which the JAN code included in the ordering data stored in the ordering data storage unit 102 is assigned. Therefore, the estimated usage amount of each JAN code can be corrected so as to be in line with the past ordering record.

Further, in the present embodiment, after managing the inventory quantity of each JAN code as described above, the order processing for ordering the drug to which the JAN code is given is executed based on the inventory quantity.

Specifically, the order processing is executed when the remaining number of dispensing days is calculated based on the current number of JAN codes in stock and the daily usage of the JAN code, and 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 inventory quantity from the predetermined upper limit number.

In the present embodiment, with such a configuration, it is possible to automatically order medicines whose inventory has decreased at an appropriate timing and at an appropriate quantity, and it is possible to reduce the time and effort required for the staff of the dispensing pharmacy to place an order. .. When a drug is automatically ordered for each JAN code, the order data related 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 stock quantity of the JAN code. (That is, 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 store terminal 20, the inventory management is configured by changing the inventory quantity indicated by the inventory data stored in the inventory data storage unit 105. Even if the inventory quantity managed by the device 10 is different from the actual inventory quantity, it is managed by the inventory management device 10 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 pharmaceutical products (JAN code) in one dispensing pharmacy has been mainly described, but the inventory management device 10 according to the present embodiment performs the process described in FIG. 7 described above at the dispensing pharmacy. It is also possible to manage the inventory of medicines in multiple dispensing pharmacies by executing each time. In this case, the above-mentioned dispensing data, ordering 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 or the like of the inventory management device 10. You may. In this case, the inventory management device 10 may be configured to acquire (receive) necessary data from the external device.

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

(Second Embodiment)
Next, the second embodiment of the present invention will be described. In the present embodiment, the same reference numerals as those in the drawings used in the above-described description of the first embodiment will be added to the description. Further, in the following description, the parts 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 the present 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 is a dispensing pharmacy in which the first store terminal 20a is installed (hereinafter referred to as the first dispensing pharmacy) and a dispensing pharmacy in which the second store terminal 20b is installed. It has a function of managing the inventory of pharmaceutical products (hereinafter referred to as the second dispensing pharmacy) (hereinafter referred to as the inventory management function).

Further, the inventory management device 10 according to the present embodiment has a matching function. In the present embodiment, the matching function is a function that enables the second dispensing pharmacy to purchase, for example, 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. The details of this matching function will be described later.

The first store terminal 20a and the second store terminal 20b described above are terminals (electronic devices) similar to the store terminal 20 described in the first embodiment described above.

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

Since 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, it 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, each unit 110-112 is realized by, for example, executing an inventory management program in which the CPU 13 (that is, the computer of the inventory management device 10) shown in FIG. 2 is stored in the non-volatile memory 12, that is, by software. It shall be done.

Here, each unit 110-112 has been described as being realized by software, but each unit 110-112 may be realized by hardware or may be realized by a combination of software and hardware.

Further, in the present embodiment, the storage units 113 and 114 are realized by, for example, the non-volatile memory 12 shown in FIG. 2 or another storage device or the like.

The listing processing unit 110 executes a process of listing a drug in stock at, for example, the first dispensing pharmacy. In this case, the listing processing unit 110 determines that the inventory quantity does not change when the inventory quantity indicated by the inventory data stored in the inventory data storage unit 105 does not change for a predetermined period. Generate listing data for listing (medicines with a JAN code). This listing data is data indicating a drug to be listed from the first dispensing pharmacy, and is the JAN code given to the drug (drug in the packaging unit for sale) and information on the drug (hereinafter referred to as drug information). including. The listing data generated by the listing processing unit 110 is stored in the listing data storage unit 113. The inventory quantity indicated by the inventory data is an expected value of the inventory quantity (that is, the expected inventory quantity) as described in the first embodiment described above.

The purchase reservation processing unit 111 generates, for example, purchase reservation data for the second dispensing pharmacy to reserve the purchase of a drug to be exhibited by another dispensing pharmacy. This purchase reservation data includes the type of drug (YJ code) reserved for purchase by the second dispensing pharmacy and the conditions specified 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 sets a condition that the JAN code included in the listing data and the YJ code included in the purchase reservation data are in a corresponding relationship, and the drug information included in the listing data is included in the purchase reservation data. If so, the listing data is matched with the purchase reservation data.

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

As described above, in the inventory management device 10 according to the present embodiment, the inventory of pharmaceutical products in the first dispensing pharmacy and the inventory of pharmaceutical products in the second dispensing pharmacy are managed. In this case, the inventory data storage unit 105 is provided with inventory data indicating the number of inventories of each drug (drug to which the JAN code is assigned) at the first dispensing pharmacy and the drug (JAN code) at the second dispensing pharmacy. Inventory data indicating the number of inventories of each drug) is stored.

Hereinafter, the operation of the inventory management device 10 according to the present embodiment will be described. Here, the processing related to the above-mentioned matching function 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 The process for matching the listing data with the purchase reservation data (hereinafter referred to as matching process) will be described.

The inventory management device 10 according to the present embodiment has the above-mentioned inventory management function, but since the processing for realizing the above-mentioned inventory management function is as described in FIG. 7 and the like described above, for example, here. The detailed description will be omitted.

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

Here, by executing the process shown in FIG. 7 described above, the inventory data storage unit 105 has already stored inventory data indicating the number of drugs (pharmaceuticals to which the JAN code is assigned) in stock at the first dispensing pharmacy. It shall be (managed).

In this case, the processes of steps S21 to S24 are executed for each of the JAN codes included in the inventory data indicating the number of pharmaceutical products in stock at the first dispensing pharmacy. Hereinafter, the JAN code to be processed in steps S21 to S24 will be referred to as a target JAN code.

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

Next, the listing processing unit 110 has a change in the number of inventories included in the inventory data acquired in step S21 (that is, the number of inventories of pharmaceutical products to which the target JAN code is assigned) within a predetermined period. Whether or not it is determined (step S22).

Here, it is assumed that the inventory data stored in the inventory data storage unit 105 includes the update date information indicating the date when the number of stocks 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 listing processing unit 110 can determine that the number of stocks fluctuates within a predetermined period. On the other hand, if 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 listing processing unit 110 will perform the listing processing unit 110. It can be determined that there is no change in the number of stocks within a predetermined period.

When it is determined that there is no change in the number of stocks (NO in step S22), the listing processing unit 110 sells a drug to which the target JAN code is assigned (that is, a drug in immovable inventory in which the number of stocks does not change). Generate listing data for (step S23).

In step S23, listing data including the target JAN code and drug information related to the drug to which the target JAN code is attached is generated.

The listing data generated in step S23 is registered (stored) in the listing 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, a JAN code, a quantity, a drug price ratio, and an expiration date.

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

The quantity is the quantity of the drug (the drug to which the associated JAN code is given) listed 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 to which the associated JAN code is given) listed by the dispensing pharmacy identified by the associated store ID. The official price of a drug is a price predetermined for the drug by the national government or a designated institution.

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

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

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

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

The exhibition data 113a includes the store ID "X1", the JAN code "JAN code 11", the quantity "500 tablets x 1 bottle", the drug price rate "80%", and the expiration date "○ months". According to this exhibition data 113a, the dispensing pharmacy identified by the store ID "X1" is selling a drug to which "JAN code 11" is given, 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.

In addition, the exhibition data 113b includes the store ID "X2", the JAN code "JAN code 12", the quantity "10 tablet sheets x 20", the drug price rate "70%", and the expiration date "x months". According to this exhibition data 113b, the dispensing pharmacy identified by the store ID "X2" is selling a drug to which "JAN code 12" is given, and the quantity of the drug is 10 tablet sheets x 20. It is shown that the drug price ratio of the drug is 70%, and the expiration date (remaining until) of the drug is × months.

Here, only the exhibition data 113a and 113b have been described, but 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 process of steps S21 to S24 is executed for all the JAN codes included in the inventory data indicating the number of medicines in stock at the first dispensing pharmacy. Is determined (step S25).

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

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

According to the listing process shown in FIG. 10 described above, a drug in immovable inventory whose inventory quantity managed by the inventory management device 10 does not change can be automatically listed.

In the present embodiment, the exhibition data has been described as being generated in step S23 shown in FIG. 10, but the exhibition data is, for example, in the first store terminal 20a provided in the first dispensing pharmacy. It may be generated by the staff of the first dispensing pharmacy specifying a JAN code or the like. That is, the drug managed in the first dispensing pharmacy may be automatically listed, for example, when the number of stocks does not fluctuate, or may be manually listed by the staff of the first dispensing pharmacy.

Further, in FIG. 10, the case where the drug is listed from the first dispensing pharmacy has been described, but it is also possible for another dispensing pharmacy such as the second dispensing pharmacy to list the drug.

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, in response 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 in the expectation that it will be put up for sale from, for example, another dispensing pharmacy (for example, the first dispensing pharmacy). In this case, the staff of the second dispensing pharmacy can specify the type of the drug to be reserved for purchase and the conditions related to the drug by operating the second store terminal 20b provided in the second dispensing pharmacy. .. As the type of drug, for example, a YJ code is specified.

In this case, the purchase reservation processing unit 111 receives the purchase reservation data including the YJ code and conditions specified by the staff of the second dispensing pharmacy in response to the operation of the staff of the second dispensing pharmacy with respect to the second store terminal 20b. Generate (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 to operate the drug that matches the YJ code and the conditions specified by the staff of the second dispensing pharmacy. You can book your purchase.

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, a registration date and time, a YJ code, a standard capacity, a quantity, a drug price rate, and an expiration date.

The store ID is identification information for identifying a dispensing pharmacy that has reserved the purchase of a drug. 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 a YJ code given to (type of) a drug reserved for purchase by a dispensing pharmacy identified by the associated store ID.

The standard capacity is a standard capacity for a drug (a drug to which the associated YJ code is assigned) reserved for purchase by a dispensing pharmacy identified by the associated store ID. The standard capacity corresponds to a 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 drug (the drug to which the associated YJ code is given) 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. The 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. The value.

The standard capacity, quantity, drug price rate, and expiration date included in the purchase reservation data correspond to the conditions relating to the drug reserved for purchase by the dispensing pharmacy identified by the store ID included in the purchase reservation data.

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

The purchase reservation data 114a includes the store ID "Y1", the registration date and time "10:30 on November 10, 2018", the YJ code "YJ code 1", the standard capacity "bottle", the quantity "400 tablets", and the drug price. Includes rate "65% -75%" and expiration date "△ months". According to this purchase reservation data 114a, the dispensing pharmacy identified by the store ID "Y1" makes a reservation for the purchase of the drug to which "YJ code 1" is given at 10:30 on November 10, 2018. The conditions for the drug are 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 (the remaining period until) is △ months or more. It is shown that there is.

In addition, the purchase reservation data 114b includes the store ID "Y2", the registration date and time "11:10 on November 11, 2018", the YJ code "YJ code 2", the standard capacity "10 lock sheets", and the quantity "30". , Includes drug price ratio "60% -70%" and expiration date "□ months". According to this purchase reservation data 114b, the dispensing pharmacy identified by the store ID "Y2" makes a reservation for the purchase of the drug to which "YJ code 2" is given at 11:10 on November 11, 2018. The conditions for the drug are that the standard capacity is 10 tablets, the quantity is 30 or more, the drug price ratio is 60% to 70%, and the expiration date (the remaining period until) is □ months or more. It is shown to be.

Here, only the purchase reservation data 114a and 114b have been described, but 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 the YJ code, but the JAN code may be included instead of the YJ code.

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

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

In the following description, the new listing data registered in the listing data storage unit 113 is referred to as the target listing data. Here, it is assumed that the target listing data is data indicating the medicines listed from the first dispensing pharmacy described above. That is, it is assumed that 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 the target exhibition data from the exhibition data storage unit 113 (step S41).

Next, the matching processing unit 112 executes the processes 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 in 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 It is determined whether or not the YJ code specified from the code matches the YJ code included in the target purchase reservation data. As a result, the matching processing unit 112 determines whether or not 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 listing 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 determines the drug included in the target listing data. It is determined whether or not the information satisfies the condition 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 listing data is attached matches the standard capacity included in the target purchase reservation data, and the quantity included in the target listing data is the target purchase reservation data. The drug price rate included in the target listing data is within the range of the drug price rate included in the target purchase reservation data, and the expiration date included in the target listing data is included in the target purchase reservation data. When the expiration date is exceeded, it is determined that the drug information included in the target listing data satisfies the condition included in the target purchase reservation data.

Although detailed description will be omitted, specifically, for example, when the target listing data is the listing data 113a shown in FIG. 11 and the target purchase reservation data is the purchase reservation data 114a shown in FIG. 13, the listing is concerned. Since the drug price rate included in the data 113a is not within the range of the drug price rate included in the purchase reservation data 114a, it is determined that the drug information included in the target listing data does not satisfy the conditions included in the target purchase reservation data. ..

On the other hand, for example, when the target listing data is the listing 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 listing data 113b is 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 listing data satisfies the condition included in the target purchase reservation data.

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

Here, the case where the target purchase reservation data includes the YJ code has been described, but when the target purchase reservation data includes the JAN code, the JAN code and the target exhibition data included in the target purchase reservation data When it is determined that the included JAN code matches and the drug information included in the target listing data satisfies the conditions 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 of steps S44 and S45 are not executed. .. Further, if it is determined in step S44 that the drug information included in the target listing 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 the purchase reservation data stored in the purchase reservation data storage unit 114 (step S46).

When it is determined that the processing has not been executed for all the purchase reservation data (NO in step S46), the process returns to step S42 and the processing is repeated. In this case, the purchase reservation data in which the processes of steps S42 to S45 have not been executed is set as the target purchase reservation data, and the process 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 from the purchase reservation data added to the matching list in step S45 described above. The purchase reservation data with the earliest registration date and time included in the data is specified, and the target listing data is matched with the specified purchase reservation data. In this case, the matching processing unit 112 transmits the target listing 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 listing 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 listing data is the second dispensing pharmacy, and the store terminal to which the target listing data is transmitted is the second store terminal. It is assumed that it is 20b.

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

Here, when the target listing data is displayed on the second store terminal 20b, the staff of the second dispensing pharmacy confirms the content of the target listing data (that is, the listing content of the drug from the first dispensing pharmacy). An operation for instructing the purchase of the drug to the second store terminal 20b (hereinafter referred to as a purchase instruction operation) can be performed. When the purchase instruction operation is performed on the second store terminal 20b, the purchase instruction operation (that the purchase instruction operation has been performed) is notified from the second store terminal 20b to the inventory management device 10.

The matching processing unit 112 determines whether or not the 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 listing data based on the target listing data and the purchase reservation data matched with the target listing data. A process for the second dispensing pharmacy identified by the store ID included in the purchase reservation data to purchase the drug (the drug exhibited by the first dispensing pharmacy) is executed (step S49).

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

In addition, when the second dispensing pharmacy purchases the target drug, the second dispensing pharmacy needs to pay to the first dispensing pharmacy. Therefore, in step S49, a process (settlement process) related to payment for the target drug of the second dispensing pharmacy is executed based on the drug price rate and the like included in the target listing data. This payment process is executed using, for example, pre-registered credit card information or the like. 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 listing data) may be managed in advance in 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, for example, ordering data indicating that the target drug has been ordered at the second dispensing pharmacy in the ordering data storage unit 102. 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, for example, the number of target drugs in stock at the first dispensing pharmacy included in the inventory data stored in the inventory data storage unit 105 based on the quantity included in the target listing data (that is,). , When the target drug of the first dispensing pharmacy is sold, the number of the target drug is subtracted from the number of the target drug in stock at the first dispensing pharmacy).

On the other hand, if it is determined that the purchase instruction operation has not been performed (NO in step S48), the process returns to step S47 and the process is repeated. In this case, among the purchase reservation data added to the matching list, the purchase reservation data having 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, and in step S47 The process is executed.

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

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

Here, it has been described that the purchase process is executed when the purchase instruction operation is performed, but for example, when the operation of canceling the purchase is not performed within a predetermined period (for example, 24 hours). , The purchase process may be automatically executed.

In addition, the purchase reservation data added to the matching list has been described as being matched with the target listing data in the order of the earliest registration date and time, but the purchase reservation data has a high degree of conformity with the conditions included in the target listing data, for example. It may be matched with the target listing data in order, or may be matched based on other viewpoints.

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. Listing data for listing a drug is generated, and the generated listing data is stored in the listing 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 has been stored for a long period of time (that is, a drug in immovable stock) is automatically set. It will be possible to list in. That is, in the present embodiment, it is possible to avoid a situation in which a drug in immovable stock must be discarded due to the lapse of the expiration date, and it is possible to effectively utilize the drug.

Further, in the present embodiment, the purchase reservation data for the second dispensing pharmacy (another 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. Match the listing data with the purchase reservation data.

In the present embodiment, the listing data includes the JAN code given to the drug listed by the first dispensing pharmacy and the drug information related to the drug. In addition, the purchase reservation data includes the type of drug (YJ code) reserved for purchase by the second dispensing pharmacy and the conditions specified by the second dispensing pharmacy.

In the present embodiment, the JAN code included in the listing data and the YJ code included in the purchase reservation data have a corresponding relationship, and the drug information included in the listing data is included in the purchase reservation data. When the above conditions are met, the exhibition data is matched with the purchase reservation data. If the listing data and the purchase reservation data are matched, the process for the second dispensing pharmacy to purchase the drug indicated by the listing data (the drug to which the JAN code included in the listing data is attached) is processed. Will be executed.

In the present embodiment, with such a configuration, for example, when the purchase of the desired drug of the second dispensing pharmacy is reserved and the drug is exhibited by another dispensing pharmacy (for example, the first dispensing pharmacy). , It can be realized 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. May be good. In this case, the inventory management device 10 may be configured to acquire (receive) necessary data from the external device.

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

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

Further, the storage medium may be in any form as long as it is a storage medium capable of storing a program and readable by a computer.

Further, in order to realize this embodiment, an OS (operating system) running on the computer based on instructions of a program installed on the computer from a storage medium, MW (middleware) such as database management software and network software, etc. You may execute a part of each process of.

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

Further, the storage medium 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 medium in the present invention, and the medium configuration may be any configuration.

The computer in 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 and a plurality of devices are connected to the network. Any configuration such as a system may be used.

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 an information processing device, and is a general term for devices and devices capable of realizing the functions of the present invention by a program. There is.

The present invention is not limited to the above-described embodiment as it is, and at the implementation stage, the components can be modified and embodied within a range that does not deviate from the gist thereof. In addition, various inventions can be formed by an appropriate combination of the plurality of components disclosed in the above-described embodiment. For example, some components may be removed from all the components shown in the embodiments. Further, the components of different embodiments may be combined as appropriate.

10 ... Inventory management device, 20 ... Store terminal, 20a ... First store terminal, 20b ... Second store terminal, 11 ... Bus, 12 ... Non-volatile memory, 13 ... CPU, 14 ... Main memory, 15 ... Communication device, 101 ... Dispensing data storage unit (first storage means), 102 ... Order data storage unit (fourth storage means), 103 ... Corresponding data storage unit, 104 ... Handling item data storage unit (second storage means), 105 ... Inventory data Storage unit (third storage means), 106 ... 1st 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 unit, 113 ... Exhibition data storage unit (fifth storage means), 114 ... Purchase reservation data storage unit (sixth storage means).

Claims (13)

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, and a first storage means.
A second storage means for storing handling item data including a second code given to the drug of the packaging unit for sale handled in the dispensing pharmacy, and a second storage means.
In the first usage amount of the drug to which the first code included in the dispensing data stored in the first storage means is given, and in the second code included in the handling item data stored in the second storage means. Based on the first calculation means for calculating the second usage amount of the drug for each packaging unit for sale,
Based on the calculated second usage amount, a second calculation means for calculating the expected inventory quantity of the drug for each packaging unit for sale, and
A third storage means for storing inventory data indicating the expected number inventory the calculated,
Order data including the second code given to the drug for each sales packaging unit ordered at the dispensing pharmacy and the order quantity of the drug for each sales packaging unit to which the second code is given. A fourth storage means for storing is provided , and the storage means is provided.
The second usage amount is corrected based on the ratio of the ordering amount for each sales packaging unit of the drug to which the second code included in the ordering data stored in the fourth storage means is given.
Inventory management device. The inventory according to claim 1, wherein the second calculation means calculates the expected inventory number of the drug by subtracting the calculated second usage amount from the inventory number 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 attached.
The first calculation means is based on the 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 given. The inventory management device according to claim 1 or 2, which calculates the usage amount. Further provided with an order processing means for ordering a drug to which the second code is assigned or executing a process of notifying the order based on the expected inventory quantity indicated by the inventory data stored in the third storage means. The inventory management device according to any one of claims 1 to 3. A third calculation of the remaining dispensing days of a drug to which the second code is given, based on the expected inventory quantity indicated by the inventory data stored in the third storage means and the calculated second usage amount. Further equipped with calculation means,
The inventory according to claim 4 , wherein the order processing means executes a process of ordering a drug for which the calculated dispensing days are calculated or notifying the order when the calculated dispensing days are equal to or less than a predetermined value. Management device. The order processing means executes a process of ordering or notifying the order of the drug in a number obtained by subtracting the expected inventory number indicated by the inventory data stored in the third storage means from the predetermined upper limit number. The inventory management device according to claim 4 or 5. Change to change the expected inventory quantity indicated by the inventory 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 4 to 6 , further comprising means. When the expected inventory quantity indicated by the inventory data stored in the third storage means does not fluctuate for a predetermined period, listing data for listing a drug whose expected inventory quantity does not fluctuate. And the listing processing means to generate
The inventory management device according to any one of claims 1 to 7 , further comprising a fifth storage means for storing the generated listing data. A sixth storage means for storing purchase reservation data for other dispensing pharmacies to purchase medicines,
Further provided with a matching processing means for matching the exhibition data with the purchase reservation data,
The listing data includes a second code given to a drug listed 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 reserved for purchase by the other dispensing pharmacy and conditions specified 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 are in a corresponding relationship, and the drug information is obtained. When the above conditions are satisfied, the listing data is matched with the purchase reservation data, and when the purchase reservation data includes a second code, the second code included in the listing data and the purchase reservation data The inventory management device according to claim 8 , wherein the listing data is matched with the purchase reservation data when the included second code matches and the drug information satisfies the above conditions. The ninth aspect of claim 9, wherein when the listing data and the purchase reservation data are matched, a process for the other dispensing pharmacy to purchase the drug to which the second code included in the listing data is attached is executed. Inventory management device. The drug information included in the listing data includes the quantity of drugs listed from the dispensing pharmacy.
If the exhibition data to the ordered book data and matching the expected inventory is indicated by stored in and inventory data to a third storage unit, according to claim 10, which is updated based on the quantity contained in the drug information The listed inventory management device. A first storage means for storing a first code given to a drug dispensed at a dispensing pharmacy and dispensing data including a first usage amount of the drug in the dispensing, and a packaging unit for sale handled at the dispensing pharmacy. An inventory management method executed by an inventory management device including a second storage means for storing handling item data including a second code given to the drug.
In the first usage amount of the drug to which the first code included in the dispensing data stored in the first storage means is given, and in the second code included in the handling item data stored in the second storage means. Based on the step of calculating the second usage amount of the drug for each packaging unit for sale,
Based on the calculated second usage amount, the step of calculating the expected inventory quantity of the drug for each packaging unit for sale, and
And storing the inventory data indicating an expected number inventory the calculated Third storage means,
Order data including the second code given to the drug for each sales packaging unit ordered at the dispensing pharmacy and the order quantity of the drug for each sales packaging unit to which the second code is given. It is provided with a step of storing in the fourth storage means.
The second usage amount is corrected based on the ratio of the ordering amount for each sales packaging unit of the drug to which the second code included in the ordering data stored in the fourth storage means is given.
Inventory management method. A first storage means for storing a first code given to a drug dispensed at a dispensing pharmacy and dispensing data including a first usage amount of the drug in the dispensing, and a packaging unit for sale handled at the dispensing pharmacy. A program executed by a computer of an inventory management device including a second storage means for storing handling item data including a second code given to the drug.
On the computer
In the first usage amount of the drug to which the first code included in the dispensing data stored in the first storage means is given, and in the second code included in the handling item data stored in the second storage means. Based on the step of calculating the second usage amount of the drug for each packaging unit for sale,
Based on the calculated second usage amount, the step of calculating the expected inventory quantity of the drug for each packaging unit for sale, and
And storing the inventory data indicating an expected number inventory the calculated Third storage means,
Order data including the second code given to the drug for each sales packaging unit ordered at the dispensing pharmacy and the order quantity of the drug for each sales packaging unit to which the second code is given. Execute the step of storing in the fourth storage means ,
The second usage amount is corrected based on the ratio of the ordering amount for each sales packaging unit of the drug to which the second code included in the ordering data stored in the fourth storage means is given.
Program.

Images