Medicine management device, medicine management method, and medicine management program

Abstract

To appropriately manage identification codes for identifying medicines.SOLUTION: A medicine management device comprises: an acquisition unit configured to acquire a first code indicating an identification code for identifying a medicine and the generation of the medicine; a storage control unit configured to refer to change history information of the identification code stored in a storage unit for each specific information for specifying the medicine, and, when the first code is not included in the change history information of the specific information corresponding to the acquired first code, to store the first code in the change history information of the corresponding specific information; and an assignment unit configured to assign a flag to the first code, when the first code is included in delivery data of the medicine acquired in response to order placement of the medicine that uses a second code different from the first code, assigned with the flag indicating that the medicine has been delivered in the past, and stored in the change history information.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present invention relates to a medicine management device, a medicine management method, and a medicine management program. [Background technology]

[0002] Conventionally, various identification information (codes) according to the purpose have been used for managing medicines. For example, a worldwide product identification number (JAN code) may be used for managing the ordering and inventory operations of medicines at a dispensing pharmacy. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-67484 A Summary of the Invention [Problem to be solved by the invention]

[0004] JAN codes are required to be changed even for the same drug if there is a change in function or ingredients, or in the external dimensions or content of the package. Changes to JAN codes should be reflected promptly by both dispensing pharmacies and wholesalers that use the JAN code.

[0005] However, in the past, changes to JAN codes were reflected at the discretion of the dispensing pharmacy and the wholesaler, and even for the same drug, the JAN codes used by the dispensing pharmacy and the wholesaler may not match, which can cause problems with ordering and inventory operations at the dispensing pharmacy.

[0006] In one aspect, the present invention aims to properly manage identification codes that identify pharmaceuticals. [Means for solving the problem]

[0007] In one aspect, the pharmaceutical management device has an acquisition unit that acquires a first code indicating an identification code that identifies a pharmaceutical and a generation of the pharmaceutical; a storage control unit that refers to change history information of the identification code stored in a memory unit for each specific information identifying the pharmaceutical, and stores the first code in the change history information of the corresponding specific information if the first code is not included in the change history information of the specific information corresponding to the acquired first code; and an assignment unit that assigns the flag to the first code if the first code is included in delivery data of the pharmaceutical acquired in response to an order for the pharmaceutical using a second code different from the first code, the second code being assigned a flag indicating that it has been delivered in the past and stored in the change history information. Effect of the Invention

[0008] Identification codes that identify pharmaceuticals can be properly managed. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of a medicine management system. [Diagram 2] FIG. 1 illustrates an example of a hardware configuration of a medicine management device. [Diagram 3] FIG. 13 is a diagram illustrating an example of a pharmaceutical database. [Figure 4] FIG. 13 is a diagram illustrating an example of a JAN code history database. [Diagram 5] FIG. 2 is a diagram illustrating a functional configuration of the medicine management device. [Figure 6] FIG. 4 is a diagram showing an example of JAN code information. [Figure 7] FIG. 11 is a sequence diagram illustrating the operation of the medicine management system. [Figure 8] 13 is a flowchart illustrating a process of a history management unit. [Figure 9] 13 is a flowchart illustrating a process of an order processing unit. [Figure 10]13 is a flowchart illustrating the process of a warehousing processing unit. [Figure 11] FIG. 1 is a first diagram illustrating data transition. [Figure 12] FIG. 11 is a second diagram illustrating data transition. [Figure 13] FIG. 11 is a third diagram illustrating data transition. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment will be described below with reference to the drawings. Fig. 1 is a diagram showing an example of a system configuration of a medicine management system.

[0011] The drug management system 100 of this embodiment includes a drug management device 200, an external server 300, and an information processing device 400. The drug management device 200 is connected to each of the external server 300 and the information processing device 400 via a network.

[0012] The medicine management device 200 manages medicines handled in, for example, a dispensing pharmacy, etc. More specifically, the medicine management device 200 manages the ordering / stocking of medicines in the dispensing pharmacy using a worldwide product identification number (hereinafter, JAN code).

[0013] The external server 300 may be, for example, a server device owned by a specific organization that manages JAN codes of medicines, and manages the JAN codes assigned to medicines. The external server 300 manages the JAN codes in association with product codes or product names. The product code is identification information that can uniquely identify a medicine. The product name is the name of the medicine as a product in the market. In contrast, the JAN code is identification information that requires a different code to be newly assigned when a change is made to the medicine, even if the medicine is the same. Here, the change in the product means, for example, "change in function or ingredients," "change in the outer dimensions or content of the package," etc. It is not uncommon for the generation of the product to change when a change is made to the product, but the JAN code is a code that can uniquely identify even the generation (version number) of such an identical product. In other words, the JAN code can be rephrased as a code that can uniquely identify a combination of a medicine and the generation of the product. Therefore, the external server 300 holds the original of the new JAN code that is assigned to the medicine, for example, when the packaging of the medicine is renewed.

[0014] The information processing device 400 is managed, for example, by a dispensing pharmacy in which the medicine management device 200 has been introduced and a wholesaler that trades medicines. For example, when the information processing device 400 receives medicine order data from the medicine management device 200, it transmits delivery data to the medicine management device 200 in response to delivery of the medicine to the dispensing pharmacy.

[0015] The medicine management device 200 of this embodiment includes a medicine database 210, a JAN code history database 220, and a medicine management unit 230.

[0016] The drug database 210 stores drug information on drugs handled at the dispensing pharmacy in which the drug management device 200 has been installed. The JAN code history database 220 stores change history information indicating the change history of the JAN codes assigned to drugs for which drug information is stored in the drug database 210.

[0017] The drug management unit 230 of this embodiment downloads the JAN codes of drugs whose drug information is stored in the drug database 210 from the external server 300 , and generates or updates the JAN code history database 220 .

[0018] At this time, the medicine management unit 230 assigns a flag indicating past usage history to JAN codes that have been used by the wholesaler in transactions in the past among the JAN codes stored in the JAN code history database 220. Also, the medicine management unit 230 does not assign a flag indicating usage history to JAN codes that have not been used by the wholesaler in transactions in the past among the JAN codes stored in the JAN code history database 220.

[0019] In other words, the medicine management unit 230 assigns a flag indicating a usage history to a JAN code stored in the JAN code history database 220 that has been included in delivery data received from the information processing device 400. Moreover, the medicine management unit 230 does not assign a flag indicating a usage history to a JAN code stored in the JAN code history database 220 that has never been included in delivery data received from the information processing device 400.

[0020] In addition, when generating order data for ordering pharmaceuticals from wholesalers, the pharmaceutical management unit 230 generates the order data using JAN codes assigned to the pharmaceuticals that have been assigned a flag indicating usage history.

[0021] Furthermore, when a JAN code that does not have a flag indicating usage history is included in the delivery data received from the information processing device 400, the pharmaceutical management unit 230 assigns a flag to the JAN code, thereby marking it as a JAN code with usage history.

[0022] In this embodiment, when ordering pharmaceuticals, only JAN codes that have been used by a wholesaler in past transactions with the wholesaler are used. In other words, in this embodiment, when generating order data, only JAN codes that have been used by a wholesaler in the past are considered to be valid JAN codes.

[0023] In this embodiment, by doing so, even if the timing of updating JAN code changes differs between the pharmaceutical management device 200 and the information processing device 400, it is possible to prevent disruptions to ordering and inventory operations at the dispensing pharmacy.

[0024] 1, the medicine management device 200 is a single computer, but is not limited to this. The medicine management device 200 may be executed by a plurality of computers.

[0025] 1, the drug database 210 and the JAN code history database 220 are provided in the drug management device 200, but this is not limiting. The drug database 210 and the JAN code history database 220 may be provided in a storage device other than the drug management device 200. In this case, this storage device is capable of communicating with the drug management device 200.

[0026] The hardware configuration of the drug management device 200 of this embodiment will be described below with reference to Fig. 2. Fig. 2 is a diagram showing an example of the hardware configuration of the drug management device.

[0027] The medicine management device 200 of this embodiment is a computer including an input device 21, an output device 22, a drive device 23, an auxiliary storage device 24, a memory device 25, an arithmetic processing device 26, and an interface device 27, all of which are interconnected via a bus B.

[0028] The input device 21 is a device for inputting various types of information and is realized by, for example, a keyboard, a pointing device, etc. The output device 22 is for outputting various types of information and is realized by, for example, a display, etc. The interface device 27 includes a LAN card, etc., and is used for connecting to a network.

[0029] The program that realizes the drug management unit 230 etc. of the drug management device 200 is at least a part of various programs that control the drug management device 200. The program is provided, for example, by distribution of a recording medium 28 or by downloading from a network. The recording medium 28 on which the program is recorded can be of various types, such as a recording medium that records information optically, electrically or magnetically, such as a CD-ROM, a flexible disk, a magneto-optical disk, etc., and a semiconductor memory that records information electrically, such as a ROM, a flash memory, etc.

[0030] When the recording medium 28 on which the program is recorded is set in the drive device 23, the program recorded on the recording medium 28 is installed in the auxiliary storage device 24 from the recording medium 28 via the drive device 23. The program downloaded from the network is installed in the auxiliary storage device 24 via the interface device 27.

[0031] The auxiliary storage device 24 realizes the drug database 210, the JAN code history database 220, etc., and stores the programs installed in the drug management device 200 as well as various files, data, etc. required by the drug management device 200. The memory device 25 reads out and stores the programs from the auxiliary storage device 24 when the drug management device 200 is started. The arithmetic processing device 26 realizes various processes as described below in accordance with the programs stored in the memory device 25.

[0032] Next, each database of the drug management device 200 of this embodiment will be described with reference to FIG. 3 and FIG.

[0033] 3 is a diagram showing an example of a drug database. The drug database 210 of this embodiment includes information items such as product codes and product names, which are associated with each other. The drug information of this embodiment is information including values ​​of each item in the drug database 210.

[0034] The value of the item "product code" is identification information for identifying a drug, and the value of the item "product name" indicates the product name of the drug.

[0035] In this embodiment, the product code and the product name are examples of specific information for identifying a medicine. Note that the specific information may be either the product code or the product name, or may include both the product code and the product name.

[0036] 4 is a diagram showing an example of a JAN code history database. The JAN code history database 220 of this embodiment includes information items such as JAN code, product code, product name, and application date, which are associated with each other. The change history information of this embodiment is information in which the values ​​of each item in the JAN code history database 220 are associated with each other.

[0037] The value of the item "JAN code" is the JAN code assigned to a pharmaceutical product, and is an example of an identification code that identifies a pharmaceutical product. As described above, a JAN code is a code that can uniquely identify a combination of a pharmaceutical product and its version. The values ​​of the items "product code" and "product name" indicate the product code and product name of the pharmaceutical product to which the JAN code is assigned.

[0038] The value of the "Applicable Date" field indicates the delivery date included in the delivery data that includes the JAN code. In other words, the value of the "Applicable Date" field indicates the date on which the JAN code was first used in a transaction with a wholesaler. In other words, the value of the "Applicable Date" field is a flag that indicates that the JAN code was used in the past.

[0039] In this embodiment, a JAN code with an application date entered in the JAN code history database 220 is a valid JAN code permitted for use in transactions with wholesalers.

[0040] Next, the functional configuration of the medicine management device 200 of this embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram illustrating the functional configuration of the medicine management device.

[0041] The drug management unit 230 of the drug management device 200 of this embodiment includes a history management unit 240, an order processing unit 250, and an inventory processing unit 260.

[0042] The history management unit 240 manages the JAN code history database 220. The history management unit 240 includes an acquisition unit 241, a storage control unit 242, and an assignment unit 243.

[0043] The acquiring unit 241 acquires JAN code information indicating the change history of the JAN code for each medicine from the external server 300. The JAN code information will be described in detail later.

[0044] The storage control unit 242 refers to the JAN code history database 220, and controls the storage of the JAN code information acquired by the acquisition unit 241 in the JAN code history database 220. The assignment unit 243 assigns a flag to the JAN code stored in the JAN code history database 220 in accordance with the processing of the inventory processing unit 260, which will be described later.

[0045] The order processing unit 250 generates order data in response to an operation on the drug management device 200 and transmits the order data to the information processing device 400.

[0046] The receiving processing unit 260 performs receiving processing of the delivered medicine in accordance with the delivery data received from the information processing device 400. The receiving processing in this embodiment may be processing performed on the medicine database 210 and the JAN code history database 220 when the delivered medicine is placed in a warehouse or storage location of the dispensing pharmacy.

[0047] The JAN code information of this embodiment will be described below with reference to Fig. 6. Fig. 6 is a diagram showing an example of JAN code information.

[0048] The JAN code information 60 of this embodiment includes information items such as product name, JAN code (before change), and JAN code (after change), which are associated with each other. Note that the JAN code information 60 is an example of identification code information that includes identification information for identifying a medicine, an identification code for the medicine, and an identification code that was used in the past.

[0049] The value of the item "Product name" indicates the product name of the drug. The value of the item "JAN code (before change)" indicates the JAN code that was assigned to the corresponding drug before the change. The value of the item "JAN code (after change)" indicates the new JAN code that was assigned to the corresponding drug after the change.

[0050] In the JAN code information 60 shown in FIG. 6, it can be seen that the JAN codes of the medicine with the product name "Product A" and the medicine with the product name "Product B" have both been changed.

[0051] In this embodiment, the JAN code information acquired from the external server 300 thus includes the JAN code before the change, the JAN code after the change, and the drug specification information.

[0052] Next, the operation of the medicine management system 100 of this embodiment will be described with reference to Fig. 7. Fig. 7 is a sequence diagram illustrating the operation of the medicine management system.

[0053] 7, the processes from step S701 to step S703 indicate processes by the history management unit 240, the processes from step S704 to step S706 indicate processes by the order processing unit 250, and steps S707 and S708 indicate processes by the inventory processing unit 260. The history management unit 240, the order processing unit 250, and the inventory processing unit 260 each execute processes at an independent timing.

[0054] More specifically, the history management unit 240 executes processing periodically. The order processing unit 250 executes processing when an operation to order medicines is performed by an employee of a dispensing pharmacy, etc. The inventory processing unit 260 executes processing when a delivery is made from a wholesaler in response to an order.

[0055] First, a description will be given of the process of the history management unit 240. In the medicine management device 200 of this embodiment, the acquisition unit 241 of the history management unit 240 transmits a request to acquire JAN code information to the external server 300 (step S701). Specifically, the acquisition unit 241 transmits a request to download the JAN code information to the external server 300.

[0056] Next, the acquisition unit 241 acquires JAN code information from the external server 300 (step S702). Next, the history management unit 240 generates or updates the JAN code history database 220 (step S703). The process of step S703 will be described in detail later.

[0057] Next, the processing of the order processing unit 250 will be described. The order processing unit 250 of the medicine management device 200 of this embodiment accepts an operation to order medicines (step S704). Note that the medicine management device 200 may be connected to, for example, a terminal device installed in a dispensing pharmacy, and may display an order screen for performing an order operation on the terminal device. Then, the order processing unit 250 may accept an operation on the order screen as an operation to order medicines.

[0058] Next, the order processing unit 250 generates order data according to the operation (step S705), and transmits the generated order data to the information processing device 400 (step S706). Details of the process of step S705 will be described later.

[0059] Next, the process of the inventory processing unit 260 will be described. The inventory processing unit 260 of the medicine management device 200 of this embodiment receives delivery data from the information processing device 400 (step S707). Then, the inventory processing unit 260 performs inventory processing corresponding to the delivery data (step S708). The process of step S708 will be described in detail later.

[0060] Next, the processing of the history management unit 240 of this embodiment will be further described with reference to Fig. 8. Fig. 8 is a flowchart for explaining the processing of the history management unit. Fig. 8 shows details of the processing of step S703 in Fig. 7.

[0061] In this embodiment, when the history management unit 240 acquires JAN code information from the external server 300, the storage control unit 242 determines whether the JAN code history database 220 has already been generated (step S801).

[0062] If the JAN code history database 220 has not been generated in step S801, the history management unit 240 generates the JAN code history database 220 (step S802) and ends the process. Specifically, the history management unit 240 extracts JAN codes corresponding to the medicines stored in the medicine database 210 from the acquired JAN code information by the storage control unit 242, and associates the JAN codes with the specific information of the medicines to create the JAN code history database 220. In this case, no application date is associated with any JAN code. That is, in this case, no flag is assigned to the JAN codes stored in the JAN code history database 220.

[0063] In step S801, if the JAN code history database 220 has already been generated, the storage control unit 242 determines whether or not there is a medicine whose JAN code has been changed in the JAN code history database 220 (step S803).

[0064] Specifically, the storage control unit 242 compares the JAN code stored in the JAN code history database 220 with the JAN code information, and determines whether or not there is a medicine whose JAN code has been changed.

[0065] In step S803, if there is no medicine whose JAN code has been changed, the history management unit 240 ends the process.

[0066] In step S803, if there is a medicine whose JAN code has been changed, the storage control unit 242 stores the product code of the corresponding medicine in the JAN code history database 220 in association with the changed JAN code (step S804), and ends the process. In other words, the storage control unit 242 stores the specific information of the medicine in the JAN code history database 220 in association with the changed JAN code acquired by the acquisition unit 241.

[0067] At this time, the JAN code is not associated with an application date, i.e., no flag is added to the JAN code stored in the JAN code history database 220 in step S804.

[0068] Next, the process of the order processing unit 250 will be described with reference to Fig. 9. Fig. 9 is a flowchart for explaining the process of the order processing unit 250. Fig. 9 shows details of the process of step S705 in Fig. 7.

[0069] The order processing unit 250 of this embodiment accepts input of a product code or a product name to the medicine management device 200 (step S901). At this time, both the product code and the product name may be input. In other words, the order processing unit 250 accepts input of specific information that identifies a medicine.

[0070] Next, the order processing unit 250 searches the JAN code history database 220 by the product code or product name (step S902). In other words, the order processing unit 250 searches the JAN code history database 220 by the specific information of the medicine.

[0071] Next, when multiple JAN codes corresponding to the product code or product name are identified, the order processing unit 250 extracts the JAN code with the latest application date from among the multiple JAN codes (step S903). In other words, the order processing unit 250 extracts the JAN code to which a flag was last added from among the multiple JAN codes associated with the inputted identification information.

[0072] If the JAN code corresponding to the input product code does not exist in the JAN code history database 220, the order processing unit 250 may output a notice indicating an error to the terminal device.

[0073] Next, the order processing unit 250 adds the JAN code extracted in step S903 to the order data (step S904), transmits the order data to the information processing device 400 (step S905), and ends the process. Details of the order data will be described later.

[0074] Next, the process of the storage processing unit 260 will be described with reference to Fig. 10. Fig. 10 is a flowchart for explaining the process of the storage processing unit. Fig. 10 shows details of the process of step S708 in Fig. 7.

[0075] The receiving processing unit 260 receives delivery data indicating that medicines according to the order contents indicated by the order data have been delivered from the information processing device 400 (step S1001).

[0076] Next, the warehousing processor 260 extracts the JAN code associated with the delivered medicine from the received delivery data (step S1002), and searches the JAN code history database 220 with the extracted JAN code (step S1003). Details of the delivery data will be described later.

[0077] Next, the receiving processor 260 determines whether or not a product code or product name associated with the JAN code has been identified in the JAN code history database 220 by searching (step S1004). In other words, the receiving processor 260 determines whether or not the JAN code history database 220 stores change history information including the JAN code extracted from the delivery data.

[0078] In step S1004, if the corresponding product code or product name is not identified, the warehousing processor 260 outputs an error notification to the terminal device (step S1005) and ends the process. If the corresponding product code or product name is not identified, it means that the JAN code history database 220 does not store the change history information including the JAN code extracted from the delivery data.

[0079] When the corresponding product code or product name is identified in step S1004, the warehousing processor 260 judges whether or not the change history information including the JAN code extracted from the delivery data includes an application date in the JAN code history database 220 (step S1006). In other words, the warehousing processor 260 judges whether or not a flag indicating that the JAN code extracted from the delivery data has been used in a transaction by the wholesaler in the past has been added.

[0080] In step S1006, if the change history information includes the application date, that is, if the JAN code extracted from the delivery data has been flagged as having been used by the wholesaler in a transaction in the past, the inventory processing unit 260 terminates the process.

[0081] In step S1006, if the change history information does not include an application date, that is, if the JAN code extracted from the delivery data has not been flagged as having been used by the wholesaler in a transaction in the past, the inventory processing unit 260 causes the assignment unit 243 of the history management unit 240 to enter the delivery date included in the delivery data as the application date corresponding to the JAN code extracted from the delivery data in the JAN code history database 220 (step S1007), and then terminates the processing.

[0082] In other words, if the JAN code extracted from the delivery data does not have a flag indicating that it has been used by the wholesaler in a transaction in the past, the inventory processing unit 260 causes the assignment unit 243 of the history management unit 240 to assign a flag to the JAN code extracted from the delivery data.

[0083] The processing of FIGS. 8 to 10 will be specifically described below with reference to FIGS.

[0084] Fig. 11 is a first diagram for explaining data transition. In Fig. 11, the process of the history management unit 240 shown in Fig. 8 will be specifically explained.

[0085] Fig. 11(A) shows JAN code information 60 acquired by the acquisition unit 241 of the medicine management device 200 from the information processing device 400, and is similar to the JAN code information 60 shown in Fig. 6. In addition, it can be seen from the JAN code information 60 that the JAN codes of product A and product B have both been changed.

[0086] When the history management unit 240 acquires the JAN code information 60, the storage control unit 242 refers to the JAN code information 60 and identifies the product whose JAN code has been changed.

[0087] 11(B), the storage control unit 242 searches the JAN code history database 220 with the JAN code (before change) included in the JAN code information 60, and identifies the medicine associated with the JAN code (before change) in the JAN code history database 220. The JAN code (before change) of product A is an example of another identification code to which a flag has been added, among the change history information of the identification code of the medicine stored in the storage unit.

[0088] 11B, for example, the JAN code (before change) of product A is "4650123456789," so the storage control unit 242 searches the JAN code history database 220 for "4650123456789" to identify the corresponding medicine. The corresponding medicine is the medicine with the product code "10000001" and the product name "Product A."

[0089] 11(C), the storage control unit 242 obtains the JAN code (after change) "465001345678" of product A from the JAN code information 60, and stores the product code "10000001", the product name "Product A" and the JAN code (after change) "465001345678" in association with each other in the JAN code history database 220. At this time, the application date is not associated with the JAN code (after change) "465001345678".

[0090] That is, the storage control unit 242 stores the change history information including the JAN code (after change) of the product A in the JAN code history database 220 with the application date left blank. The JAN code (after change) of the product A is an example of an identification code acquired by the acquisition unit 241.

[0091] The JAN code history database 220A shown in FIG. 11(C) shows a state in which change history information has been added that includes the product code "10000001", the product name "Product A", and the JAN code (after change) "465001345678", with the application date being blank.

[0092] Fig. 12 is a second diagram for explaining data transition, in which the processing of the order processing unit 250 shown in Fig. 9 is specifically explained.

[0093] 12 shows a case where order data is generated for product A. In this case, the order processing unit 250 of the medicine management device 200 searches the JAN code history database 220 for the product name or product code of product A, and identifies the JAN code corresponding to product A.

[0094] In the JAN code history database 220A, there are three JAN codes that correspond to product A. Here, the order processing unit 250 identifies, of the three JAN codes, the JAN code that is associated with the most recent application date.

[0095] In the example of Figure 12, of the three JAN codes corresponding to product A, "465001345678" does not have an application date associated with it. In addition, of the other two JAN codes corresponding to product A, the JAN code with the newer application date is "4650123456789."

[0096] Therefore, the order processing unit 250 generates the order data 110 by specifying the JAN code of the product A to be included in the order data as "4650123456789".

[0097] In the example of FIG. 12, the order data 110 may include an order number, an order date, a JAN code, and a quantity.

[0098] Fig. 13 is a third diagram for explaining data transition. In Fig. 13, the processing of the inventory processing unit 260 shown in Fig. 10 will be specifically explained.

[0099] FIG. 13 illustrates a case in which a medicine (product A) based on the order data 110 is delivered to a dispensing pharmacy, and the medicine management device 200 receives the delivery data 120 from the information processing device 400.

[0100] 13 may include a delivery number, a delivery date, a JAN code, and a quantity. The delivery data 120 also includes a JAN code of "465001345678."

[0101] Therefore, the receiving processor 260 searches the JAN code history database 220A for the JAN code "465001345678" to identify the corresponding medicine. In this example, the medicine with the product code "10000001" and the product name "Product A" is identified as the medicine that corresponds to "465001345678".

[0102] Next, the warehousing processor 260 determines whether or not an application date is associated with the JAN code "465001345678" associated with the identified medicine. In the JAN code history database 220A, an application date is not associated with the JAN code "465001345678".

[0103] Therefore, the warehousing processing unit 260 causes the assignment unit 243 to associate the delivery date included in the delivery data 120 with the JAN code "465001345678" and updates the JAN code history database 220A to the JAN code history database 220B.

[0104] In the JAN code history database 220B shown in Fig. 13, the application date "2022 / 11 / 16" is associated with the JAN code "465001345678". In other words, in the JAN code history database 220B, a flag indicating that the wholesaler used the JAN code (after change) of the product A is added.

[0105] In addition, since the order data 110 and the delivery data 120 specify the product (medicine) by the JAN code, the product name and product code do not need to be included.

[0106] Thus, according to this embodiment, when the JAN code acquired from the information processing device 400 is not included in the JAN code history database 220, the acquired JAN code is stored in the JAN code history database 220 with the application date left blank. This allows changes to the JAN code of a drug by a drug manufacturer or the like to be quickly reflected in the JAN code of the drug managed by the dispensing pharmacy.

[0107] Furthermore, in this embodiment, orders are placed with wholesalers using JAN codes with an inputted application date, rather than JAN codes stored in the JAN code history database 220 with a blank application date. In other words, even if a change to the JAN code is reflected in the dispensing pharmacy, the changed JAN code is not used until the changed JAN code is used in transactions with wholesalers. If the JAN code of a product delivered to the dispensing pharmacy is a JAN code (after change) stored with a blank application date, the delivery date of the product is registered as the application date.

[0108] In the case of pharmaceutical products, it is common to deliver a product with a new JAN code that is attached to a product corresponding to a JAN code included in the order data after the JAN code is attached. However, a system is in place that does not allow the delivery of a product with an old JAN code that was attached to a product corresponding to a JAN code included in the order data before the JAN code. Therefore, when a dispensing pharmacy processes an order with the latest JAN code, if the wholesaler does not handle a product with the latest JAN code, a problem occurs in that the product is not delivered. However, in this embodiment, a JAN code that is not used by the wholesaler is not included in the order data, so that the JAN code included in the order data and the JAN code included in the delivery data can be matched. In other words, the dispensing pharmacy can be made aware of the JAN codes of pharmaceutical products currently handled by the wholesaler.

[0109] Furthermore, in this embodiment, the first date (delivery date) on which the changed JAN code was used in a transaction between a wholesaler and a dispensing pharmacy is set as a flag indicating the history of use of the JAN code in the transaction. Therefore, according to this embodiment, the latest JAN code used in the transaction can be identified.

[0110] Thus, according to this embodiment, even if the dispensing pharmacy and the wholesaler each update the JAN code at their own discretion, it is possible to prevent disruption to ordering and warehousing operations at the dispensing pharmacy and to properly manage the JAN codes that identify pharmaceuticals.

[0111] The disclosed technology may take the following forms as described below. (Appendix 1) An acquisition unit that acquires a first code indicating an identification code that identifies a medicine and a generation of the medicine; a storage control unit that refers to change history information of the identification code stored in a storage unit for each piece of specific information identifying the drug, and when the first code is not included in the change history information of the specific information corresponding to the acquired first code, stores the first code in the change history information of the corresponding specific information; a flagging unit that, when the first code is included in delivery data of a pharmaceutical obtained in response to an order for the pharmaceutical using a second code that is different from the first code and that has been assigned a flag indicating that the pharmaceutical has been delivered in the past and stored in the change history information, assigns the flag to the first code. (Appendix 2) 2. The pharmaceutical management device according to claim 1, wherein the assignment unit assigns information indicating a delivery date included in the pharmaceutical delivery data as a flag indicating that the pharmaceutical has been used in the past. (Appendix 3) The pharmaceutical management device described in Appendix 2 has an order processing unit that accepts an operation to order the pharmaceutical, and generates and outputs order data including the second code extracted from the change history information of the identification code corresponding to the specific information, the second code having the latest delivery date indicated by the assigned flag. (Appendix 4) The acquisition unit is acquiring identification code information in which the specific information of the medicine, the first code, and the second identification code that has been used in the past are associated with each other; The storage control unit is A pharmaceutical management device described in any one of Appendices 1 to 3, which uses the specific information contained in the identification code information and the second code to determine whether the second code is included in the pharmaceutical change history information. (Appendix 5) A pharmaceutical management method by a computer, comprising: obtaining a first code indicating an identification code identifying a drug and a generation of the drug; referring to change history information of the identification code stored in a storage unit for each piece of specific information identifying the medicine, if the first code is not included in the change history information of the specific information corresponding to the acquired first code, storing the first code in the change history information of the corresponding specific information; A pharmaceutical management method comprising the steps of: when the first code is included in the pharmaceutical delivery data obtained in response to an order for the pharmaceutical using a second code different from the first code, which is assigned a flag indicating that the pharmaceutical has been delivered in the past and is stored in the first change history information, assigning the flag to the first code. (Appendix 6) obtaining a first code indicating an identification code identifying a drug and a generation of the drug; referring to change history information of the identification code stored in a storage unit for each piece of specific information identifying the medicine, if the first code is not included in the change history information of the specific information corresponding to the acquired first code, storing the first code in the change history information of the corresponding specific information; A pharmaceutical management program that, when the first code is included in the pharmaceutical delivery data obtained in response to an order for the pharmaceutical using a second code different from the first code, the second code is assigned a flag indicating that the pharmaceutical has been delivered in the past and is stored in the change history information, assigns the flag to the first code. The invention is not limited to the specifically disclosed embodiments, but various modifications and variations are possible without departing from the scope of the appended claims. [Explanation of symbols]

[0112] 100 Drug Management System 200 Drug management device 210 Pharmaceutical Database 220 JAN code history database 230 Pharmaceutical Management Department 240 History Management Department 241 Acquisition Department 242 Storage control section 243 Grant Department 250 Order Processing Unit 260 Inventory Processing Section

Claims

1. An acquisition unit that acquires a first code indicating an identification code that identifies a medicine and a generation of the medicine; a storage control unit that refers to change history information of the identification code stored in a storage unit for each piece of specific information that identifies the medicine, and when the first code is not included in the change history information of the specific information corresponding to the acquired first code, stores the first code in the change history information of the corresponding specific information; A pharmaceutical management device having an assignment unit that assigns the flag to the first code when the first code is included in pharmaceutical delivery data obtained in response to an order for the pharmaceutical using a second code that is different from the first code and has a flag assigned to it indicating that the pharmaceutical has been delivered in the past and is stored in the change history information.

2. The medicine management device according to claim 1 , wherein the assigning unit assigns information indicating a delivery date included in the delivery data of the medicine as the flag indicating that the medicine has been used in the past.

3. The pharmaceutical management device of claim 2 further comprises an order processing unit that accepts an operation to order the pharmaceutical and generates and outputs order data including the second code extracted from the change history information of the identification code associated with the specific information, the second code having the latest delivery date indicated by the assigned flag.

4. The acquisition unit is acquiring identification code information in which the specific information of the medicine, the first code, and the second code are associated with each other; The storage control unit is The drug management device according to claim 1 , further comprising: a step of determining whether or not the second code is included in the drug change history information by using the specific information included in the identification code information and the second code.

5. A pharmaceutical management method by a computer, comprising: obtaining a first code indicating an identification code identifying a medicine and a generation of the medicine; referring to change history information of the identification code stored in a storage unit for each piece of specific information identifying the medicine, if the first code is not included in the change history information of the specific information corresponding to the acquired first code, storing the first code in the change history information of the corresponding specific information; A pharmaceutical management method comprising: when the first code is included in pharmaceutical delivery data obtained in response to an order for the pharmaceutical using a second code different from the first code, the second code being assigned a flag indicating that the pharmaceutical has been delivered in the past and stored in the change history information, the flag is assigned to the first code.

6. obtaining a first code indicating an identification code identifying a medicine and a generation of the medicine; referring to change history information of the identification code stored in a storage unit for each piece of specific information identifying the medicine, if the first code is not included in the change history information of the specific information corresponding to the acquired first code, storing the first code in the change history information of the corresponding specific information; A pharmaceutical management program that assigns a flag to the first code when the first code is included in the pharmaceutical delivery data obtained in response to an order for the pharmaceutical using a second code that is different from the first code and that has been assigned a flag indicating that it has been delivered in the past and stored in the change history information.

Images