Medicine management system, medicine management method and medicine management program

Abstract

To provide a medicine management system, a medicine management method, and a medicine management program capable of easily specifying a patient who is prescribed a medicine in which a defect has occurred.SOLUTION: A registration processing part 112 registers medicine identification information capable of identifying prepared medicines, lot identification information showing the lot of medicines, and patient information showing the patient who is the medicine prescription object by associating them with each other. A search processing part 114 executes search processing of the patient information based at least on any one of the medicine identification information and the lot identification information set as search conditions. An output processing part 115 outputs the medicine identification information, the lot identification information, and the patient information by associating them with each other according to the search processing.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a medicine management system, a medicine management method, and a medicine management program for managing information on medicines to be prescribed. [Background technology]

[0002] In medical institutions such as pharmacies and hospitals, a system is known for managing information such as drug prescription history based on prescription data for each patient (see, for example, Patent Document 1). By managing the medical history, it becomes possible to check the prescription contents for each patient. [Prior art documents] [Patent documents]

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

[0004] However, there are cases where a defect (abnormality) occurs in a drug provided by a pharmaceutical manufacturer or the like. When a defect occurs in a drug, it is necessary to identify the patient to whom the drug was prescribed in order to discontinue use of the drug. Conventionally, when a defect occurs in a drug, the medical institution checks the period during which the defective drug was dispensed, and identifies the patient to whom the drug was prescribed during that period. In the conventional method, the patient is searched for only by information on the period, which is time-consuming to identify. In addition, there is also a problem that patients who were prescribed a drug with a lot number that does not have a defect may be included in the search results.

[0005] An object of the present invention is to provide a medicine management system, a medicine management method, and a medicine management program that can easily identify a patient who has been prescribed a medicine that has a defect. [Means for solving the problem]

[0006] A drug management system according to one aspect of the present invention includes a registration processing unit, a search processing unit, and an output processing unit. The registration processing unit registers drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating the patient for whom the drug is prescribed, in association with each other. The search processing unit executes a search process for patient information based on at least one of the drug identification information and lot identification information set as a search condition. The output processing unit outputs the drug identification information, the lot identification information, and the patient information in association with each other in response to the search process.

[0007] A drug management method according to another aspect of the present invention is a method executed by one or more processors to register drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating the patient for whom the drug is prescribed, in association with each other; perform a search process for patient information based on at least one of the drug identification information and the lot identification information set as search conditions; and output the drug identification information, the lot identification information, and the patient information in association with each other in accordance with the search process.

[0008] A drug management program according to another aspect of the present invention is a program for causing one or more processors to execute the following steps: registering drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating the patient for whom the drug is prescribed, in association with each other; performing a search process for patient information based on at least one of the drug identification information and the lot identification information set as search conditions; and outputting the drug identification information, the lot identification information, and the patient information in association with each other in accordance with the search process. Effect of the Invention

[0009] According to the present invention, it is possible to provide a medicine management system, a medicine management method, and a medicine management program that can easily identify a patient who has been prescribed a defective medicine. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing an example of a medicine management system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of dispensing performance attribute data used in the medicine management system according to the embodiment of the present invention. [Diagram 3] FIG. 3 is a diagram showing an example of dispensing record detail data used in the medicine management system according to the embodiment of the present invention. [Figure 4] FIG. 4 is a diagram showing an example of a dispensing history search screen displayed in the medicine management system according to the embodiment of the present invention. [Diagram 5] FIG. 5 is a diagram showing an example of a search result displayed in the medicine management system according to the embodiment of the present invention. [Figure 6] FIG. 6 is a diagram showing an example of a lot number selection screen displayed in the medicine management system according to the embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing an example of a search result displayed in the medicine management system according to the embodiment of the present invention. [Figure 8] FIG. 8 is a flowchart showing an example of a procedure of a dispensing process executed in the medicine management system according to the embodiment of the present invention. [Figure 9] FIG. 9 is a diagram showing an example of a screen displayed in the medicine management system according to the embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a tablet packaging device according to an embodiment of the present invention. [Figure 11] FIG. 11 is a diagram showing an example of dispensing record detail data used in the medicine management system according to the embodiment of the present invention. [Figure 12] FIG. 12 is a diagram showing an example of a search result displayed in the medicine management system according to the embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing an example of a search result displayed in the medicine management system according to the embodiment of the present invention. [Figure 14] FIG. 14 is a diagram showing an example of a search result displayed in the medicine management system according to the embodiment of the present invention. [Figure 15] FIG. 15 is a block diagram showing an example of a control device of a dispensing device according to an embodiment of the present invention. [Figure 16] FIG. 16 is an external view showing an example of a tray used in an injection drug dispensing device which is an example of a dispensing device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings to facilitate understanding of the present invention. Note that the following embodiment is an example of the present invention and is not intended to limit the technical scope of the present invention. In addition, the configurations and processing functions described in the following embodiment can be selected and combined as desired.

[0012] [Drug Management System 10] As shown in FIG. 1, a medicine management system 10 according to an embodiment of the present invention includes a server 1, a client terminal 2, a dispensing device 3, and a printer 4. The server 1, the client terminal 2, the dispensing device 3, and the printer 4 are connected to each other via a communication network N1 so as to be able to communicate wirelessly or wired. The communication network N1 includes a local area network (LAN), a wide area network (WAN), the Internet, an intranet, and the like. A higher-level system 5 is also connected to the server 1 via the communication network N1. The medicine management system 10 may include a plurality of at least one of the server 1, the client terminal 2, the dispensing device 3, and the printer 4.

[0013] The users of the drug management system 10 are, for example, pharmacists, doctors, nurses, medical staff, facility managers, etc. in medical institutions such as hospitals, nursing homes for the elderly, pharmacies, etc. In this embodiment, as an example, the drug management system 10 is used in a hospital, and the users of the drug management system 10 are pharmacists (hospital pharmacists) at the hospital.

[0014] The medicine management system 10 has a function of managing information on the dispensing of medicines, information on the prescription of dispensed medicines, and the like. In particular, in this embodiment, the medicine management system 10 is used to manage lot identification information (lot number) that can identify the lot of a prescribed medicine for each patient. That is, the medicine management system 10 according to this embodiment is a management system for managing information on dispensing and prescription of medicines, and has a function of managing the lot number of a prescribed medicine for each patient as one of its functions. In this embodiment, a "lot" refers to a group (minimum unit) of products manufactured to have homogeneity through a series of manufacturing processes within one manufacturing period, and a "lot number" refers to an identification number issued for each of the minimum units. For example, a "lot" refers to a group of products that are the subject of one defect notification issued by a pharmaceutical manufacturer. Even if the medicines are the same type, different lot numbers are assigned to each minimum unit. In addition, the lot number is printed, for example, on the packaging material, container, etc. of the medicine.

[0015] In this embodiment, unless otherwise specified, the "medicines" to be managed by the medicine management system 10 include one or more types of medicines including oral medications.

[0016] In the medicine management system 10, the server 1 can display dispensing and prescription information (dispensing record, prescription record) for each patient on the client terminal 2 in response to a user's operation of the client terminal 2. The client terminal 2 controls the display screen based on display data transmitted from the server 1, or controls the display screen by referring to various data stored in the server 1. The server 1 can also accept operation input to the client terminal 2 by the user.

[0017] Specifically, in this embodiment, a server-client system is configured by a server 1 and a client terminal 2, and a case will be described in which the server 1 executes various processes such as display and printing in response to user operations of the client terminal 2. Therefore, in this embodiment, the "display," "operation," "selection," "input," and the like described below will be described as being performed using the client terminal 2. Note that similar displays and operations may also be performed by the server 1.

[0018] The upper system 5 is a medical-related system such as an electronic medical record system or a regimen ordering system. The upper system 5 is a system separate from the drug management system 10, and it is sufficient that the upper system 5 can communicate with the drug management system 10, and does not necessarily have a "higher" relationship with the drug management system 10. The upper system 5 can receive inputs of prescription data related to the prescription or use of drugs for patients, and test data related to the results of various tests performed on patients. The upper system 5 inputs the prescription data and the test data to the server 1 in response to a user operation, or automatically inputs the data to the server 1 at a predetermined timing such as a preset closing time. The server 1 may also be configured to actively read out the prescription data and the test data from the upper system 5. A plurality of upper systems 5 may be provided, and the plurality of upper systems 5 may include different types of systems. At least one of the prescription data and the test data may be directly input to the drug management system 10 by a user operation on the client terminal 2 or the server 1.

[0019] Here, the prescription data includes information such as patient data, prescription ID, drug name, date of use, date of prescription, amount of use, usage, doctor in charge, pharmacist in charge, medical department, and ward. The prescription data may further include information such as preparation date and start date of use. The patient data includes various information related to the patient, such as patient identification information for identifying an individual patient, such as a patient ID or patient name (first and last name), as well as the patient's age, sex, medical history, prescription drug history, whether or not the patient drinks alcohol, whether or not the patient smokes, family information, and physical information such as the patient's height, weight, and body surface area. The date of use indicates the date on which the drug is used based on the prescription data. The amount of use indicates the amount of the drug used based on the prescription data.

[0020] However, there are cases where a defect (abnormality) occurs in a drug provided by a pharmaceutical manufacturer or the like. When a defect occurs in a drug (for example, contamination with a foreign object, unexpected side effects, etc.), it is necessary to identify the patient to whom the drug was prescribed in order to discontinue use of the drug. Conventionally, when a defect occurs in a drug, the medical institution checks the period during which the defective drug was dispensed, and identifies the patient to whom the drug was prescribed during that period. In the conventional method, the patient is searched for only based on information about the period, which makes it time-consuming to identify the patient. In addition, there is also a problem that patients who were prescribed a drug with a lot number that does not have a defect may be included in the search results.

[0021] In consideration of such circumstances, the medicine management system 10 according to this embodiment has a configuration capable of easily identifying patients who have been prescribed the defective medicine. Specifically, the medicine management system 10 has a registration processing unit 112 that registers dispensing records (dispensing history), a search processing unit 114 that searches for search target patients (patients who have been prescribed the medicine with the defective lot number) from the dispensing records, and an output processing unit 115 that outputs the search results. The functions of the registration processing unit 112, the search processing unit 114, and the output processing unit 115 will be described in detail later.

[0022] [Pharmacy equipment 3] The dispensing equipment 3 is equipment used when dispensing medicines based on the prescription data. The dispensing equipment 3 includes a tablet packaging device, a sheet dispensing device, a powdered medicine packaging device, a liquid medicine dispensing machine, and a picking device. In the medicine management system 10, one or more dispensing equipment 3 may be provided. In addition, in the medicine management system 10, a plurality of dispensing equipment 3 of the same type may be provided, or a plurality of dispensing equipment 3 of different types may be provided.

[0023] The tablet packaging device has a plurality of tablet cassettes containing a plurality of types of tablets, and automatically packages and dispenses a predetermined amount of tablets contained in the tablet cassettes according to the prescription data. The sheet dispensing device automatically dispenses a predetermined amount of PTP sheets from a plurality of sheet cassettes containing PTP sheets in which tablets are prepackaged according to the prescription data. The powdered medicine packaging device has a plurality of powdered medicine cassettes containing a plurality of types of powdered medicine, and automatically packages and dispenses a predetermined amount of powdered medicine contained in the powdered medicine cassettes according to the prescription data. The liquid medicine dispensing machine has a plurality of medicine bottles containing a plurality of types of liquid medicine, and dispenses a required amount of liquid medicine from the medicine bottles according to the prescription data. The picking device is used when a pharmacist manually dispenses medicine, and reads the medicine name from identification information (such as a barcode) given to a medicine shelf or medicine bottle, and compares the read medicine name with the medicine name included in the prescription data.

[0024] The dispensing device 3 is filled with one or more types of medicine, and the dispensing device 3 dispenses a required amount of one or more types of medicine according to the prescription data from among the filled medicines. When the dispensing device 3 is filled with medicine, information about the medicine is registered in a storage unit (drug master) of the dispensing device 3. The drug master includes, for example, information corresponding to each medicine, such as a drug ID (including YJ code, etc.), drug code, drug name, JAN code, RSS code, lot number, expiration date, use by date, dosage form, unit, specific gravity, compounding change, excipient drug, cautions, allergy information, and package insert information. These information may be included in an identification code (barcode, GS1 code, etc.) given to the medicine or packaging material received from a pharmaceutical manufacturer. For example, in a drug filling operation in the dispensing device 3, a barcode reader reads a barcode given to the medicine, and the information is associated with the medicine ID and registered in the drug master. The expiration date and the use by date are set corresponding to the lot number. The expiration date is a date by which the validity of the medicine is guaranteed, and the use-by date is a date by which the quality of the medicine in an unopened state under specified storage conditions is guaranteed. For example, the expiration date of medicine A with lot number "1" is set to "A11" and the use-by date to "A12", and the expiration date of medicine A with lot number "2" is set to "A21" and the use-by date to "A22". For example, the expiration date of medicine B with lot number "10" is set to "B11" and the use-by date to "B12", and the expiration date of medicine B with lot number "11" is set to "B21" and the use-by date to "B22". In this way, even for the same type of medicine, the expiration date and use-by date are different for each lot number.

[0025] Here, an example of the registration process of lot numbers, etc. in the tablet packaging device will be described. An example of a tablet packaging device 3A is shown in Figure 10. The tablet packaging device 3A has a plurality of tablet cassettes C1 containing a plurality of types of tablets, and automatically packages and dispenses a predetermined amount of tablets contained in the tablet cassettes C1 according to the prescription data.

[0026] In the tablet packaging device 3A, when filling the tablet cassette C1 with medicine, a control unit of the tablet packaging device 3A reads the barcode attached to the medicine with a barcode reader, and registers information on the medicine code, medicine name, lot number, expiration date, and use-by date in the medicine master in association with the medicine ID. Identification information of the tablet cassette C1 (cassette ID, etc.) is associated and registered in the medicine master. Therefore, in the medicine master, information on the cassette ID, medicine code, medicine name, lot number, expiration date, and use-by date are associated and registered for each tablet cassette C1.

[0027] For example, when filling the tablet packaging device 3A with medicines, a tablet cassette C1 in which medicines are to be stored and registered is placed in a filling station that can be pulled out from the front of the device, and a reader provided in the filling station reads the cassette ID from a tag (e.g., an RFID tag) attached to the tablet cassette C1, and code information such as the GS1 code attached to the medicine is read by another reader (e.g., a barcode reader) to obtain a lot number, which is then associated with the cassette ID. Also, the cassette ID and medicine information may be entered manually without being read by a reader.

[0028] Also, basically, one lot number is registered for one tablet cassette C1, but it is also possible to register multiple lot numbers for one tablet cassette C1 (details will be described later). For example, a reader may be made to read multiple medicines with different lot numbers in succession while the tablet cassette C1 is placed in the filling station. When refilling (topping up) medicines with different lot numbers while medicines remain in the tablet cassette C1, the lot number of the medicine to be refilled may be added while leaving the already registered lot number (see [Topping up filling process] described later). In this way, when the dispensing device 3 includes multiple tablet cassettes C1 (containers) capable of containing medicines, when multiple medicines of the same type but different lots are filled into one tablet cassette C1, the registration processing unit 112 registers the cassette ID (container identification information) of the tablet cassette C1 and the medicine identification information and lot numbers corresponding to each of the multiple medicines contained in the tablet cassette C1 in association with each other.

[0029] In the case of a powdered medicine packaging device, the lot number etc. may be registered as follows. For example, when packaging medicines picked by a picking device, the lot number etc. is registered by reading a barcode attached to the medicine shelf or by reading a barcode attached to the medicine (details will be described later). For example, when packaging medicines weighed by a weighing device, the lot number etc. is registered by reading a barcode attached to the medicine by the weighing device. In pharmacies that do not employ a picking device, weighing device, etc., the lot number etc. may be registered in the powdered medicine packaging device or in a system higher up than the powdered medicine packaging device.

[0030] Furthermore, when dispensing (dispensing of medicine) is completed, the dispensing device 3 outputs dispensing performance data (dispensing history data) including information related to dispensing (information related to dispensed medicine, information related to the dispensing device 3, information related to the prescription data, etc.) to the server 1. Furthermore, the dispensing device 3 outputs the dispensing performance data to the server 1 in the form of, for example, a text file. The dispensing device 3 may output the dispensing performance data to the server 1 every time dispensing of one prescription data is completed, may output the dispensing performance data to the server 1 at a predetermined timing such as a preset closing processing time, or may output the dispensing performance data to the server 1 in response to a user operation.

[0031] The dispensing performance data includes drug identification information (drug code, drug name, YJ code) and lot number acquired when the drug is filled into the dispensing device 3, and patient information included in the prescription data corresponding to the drug input to the dispensing device 3. For example, the dispensing performance data includes information such as a data ID, a model type, a model number, a prescription number, an order number, a prescription type, a dispensing date and time, a patient ID, a patient name, a drug code, a drug name, a YJ code, a total amount used, a lot number, an expiration date, an expiration date, and a lot usage amount. The drug code, drug name, YJ code, lot number, expiration date, and expiration date included in the dispensing performance data correspond to information registered in the drug master. The model type is information indicating the type (model) of the dispensing device 3, and is information indicating the model such as a tablet packaging device, a sheet dispensing device, a powdered medicine packaging device, a liquid medicine dispensing device, and a picking device. The model number is information indicating the model of the dispensing equipment 3, and for example, in a case where three tablet packaging devices are installed, the information indicates No. 1, No. 2, No. 3, etc. The dispensing history data is an example of dispensing history information of the present invention. The model category and the model number are examples of equipment identification information of the present invention. The drug code, the drug name, and the YJ code are examples of drug identification information of the present invention.

[0032] The dispensing device 3 generates one dispensing performance data for one prescription data, for example, and outputs it to the server 1. Therefore, when one prescription data includes multiple types of medicines, one dispensing performance data includes information corresponding to each of the multiple types of medicines (medicine code, medicine name, YJ code, total usage amount, lot number, expiration date, use date, etc.). For example, when the prescription data of patient X includes medicine A, medicine B, and medicine C, and the tablet packaging device dispenses medicine A, medicine B, and medicine C, the tablet packaging device generates one dispensing performance data (text file) including information on medicine code, medicine name, YJ code, total usage amount, lot number, expiration date, and use date corresponding to medicine A, information on medicine code, medicine name, YJ code, total usage amount, lot number, expiration date, and use date corresponding to medicine B, and information on medicine code, medicine name, YJ code, total usage amount, lot number, expiration date, and use date corresponding to medicine C, and outputs it to the server 1.

[0033] [Client terminal 2] The client terminal 2 is a personal computer including a control unit 21, a storage unit 22, a communication I / F 23, a display unit 24, and an operation unit 25. The client terminal 2 is an operation terminal that is placed in a medical institution (such as a hospital or a pharmacy) where the medicine management system 10 is used, and is operated by a user. For example, the client terminal 2 is used by a pharmacist who prepares medicines prescribed for patients at the medical institution. The client terminal 2 may be a portable information processing device such as a smartphone, a tablet terminal, a wearable terminal, or a laptop computer.

[0034] The control unit 21 has control devices such as a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and an EEPROM (registered trademark). The CPU is a processor that executes various arithmetic operations. The ROM is a non-volatile storage unit in which information such as a control program for causing the CPU to execute various operations is stored in advance. The RAM is a volatile storage unit, and the EEPROM is a non-volatile storage unit. The RAM and the EEPROM are used as temporary storage memories (work areas) for the various operations executed by the CPU. Then, the control unit 21 uses the CPU to execute various operations in accordance with the various control programs stored in advance in the ROM, the EEPROM, or the storage unit 22.

[0035] The storage unit 22 is a non-volatile storage unit such as a hard disk or SSD (Solid State Drive) in which various control programs and various data executed by the control unit 21 are stored. Specifically, the storage unit 22 includes a program storage unit in which an operating system (OS) and application programs such as browser software are stored. The browser software is application software for displaying various operation screens and the like on the display unit 24 by accessing the server 1 via the communication network N1, and for transmitting input operations on the operation screen using the operation unit 25 to the server 1. For example, when address information such as a URL (Universal Resource Locator) corresponding to the server 1 is input at a predetermined position on the operation screen displayed by the browser software, the control unit 21 accesses the server 1 based on the address information.

[0036] The communication I / F 23 is a communication interface having a network card or the like that executes wireless or wired data communication in accordance with a predetermined communication protocol between the server 1 and external devices such as the printer 4 via the communication network N1.

[0037] The display unit 24 is a device such as a liquid crystal display or an organic EL (Electro-Luminescence) display that displays various information in accordance with control instructions from the control unit 21. For example, the control unit 21 executes various processes in accordance with the browser software, thereby causing the display unit 24 to display various information based on the display data received from the server 1.

[0038] The operation unit 25 is a device operated by a user to input various information to the client terminal 2. Specifically, the operation unit 25 includes a keyboard and a pointing device (mouse, etc.) that accept input operations on various operation screens displayed on the display unit 24. The operation unit 25 may also include a touch panel that accepts touch operations on various operation screens displayed on the display unit 24, or a voice input device that accepts input of various information by voice recognition. The control unit 21 then executes various processes in accordance with the browser software to accept user operations on the operation unit 25 and inputs the contents of the user operations to the server 1.

[0039] Specifically, the server 1 transmits data described in a Web page description language such as HTML (Hyper Text Markup Language) to the client terminal 2, thereby causing the display unit 24 of the client terminal 2 to display various screens. In addition, the control unit 21 of the client terminal 2 transmits an operation signal to the server 1 in response to an operation input to the operation unit 25.

[0040] [Printer 4] The printer 4 is an image forming device such as a color printer or a monochrome printer capable of executing a printing process to record information contained in print data input from the server 1 or the client terminal 2 via the communication network N1 onto a sheet of paper or the like. For example, at the medical institution, the printer 4 may print a prescription based on the prescription data. The printer 4 is also used in the medicine management system 10 to print search results (see FIGS. 5, 7, etc.) described below.

[0041] [Server 1] 1, the server 1 is a computer including a control unit 11, a storage unit 12, a communication I / F 13, a display unit 14, an operation unit 15, and a drive device 16. The server 1 may be provided outside the medical institution such as a hospital or a pharmacy where the medicine management system 10 is used. The server 1 may also be an information processing device such as a smartphone, a tablet terminal, or a laptop computer.

[0042] The control unit 11 has a similar configuration to the control unit 21, and has control devices such as a CPU, ROM, RAM, and EEPROM, and uses the CPU to execute various processes in accordance with various control programs pre-stored in the ROM, the EEPROM, or the memory unit 12.

[0043] The storage unit 12 is a non-volatile storage unit such as a hard disk or SSD that stores various control programs and various data executed by the control unit 11. The storage unit 12 also includes a program storage unit 121, a master storage unit 122, and an information storage unit 123.

[0044] The program storage unit 121 is a storage area in which a medicine management program for causing the control unit 11 to execute various processes related to a medicine management method described below and the like are stored. The program storage unit 121 also stores programs such as an operating system (OS).

[0045] The master storage unit 122 is a storage area in which various master information such as a patient master, a medicine master, and a medicine search master is stored. The patient master includes information such as a patient ID, a patient name, an age, a sex, a medical history, a prescription history, whether or not drinking is done, whether or not smoking is done, family information, a medical department, a ward, a hospital room, and a doctor in charge, which correspond to each patient. The medicine master includes information such as a medicine ID (including YJ code, etc.), a medicine code, a medicine name, a JAN code, an RSS code, a lot number, an expiration date, an expiration date, a dosage form, a unit, a specific gravity, a compounding change, an excipient medicine, a caution, an allergy information, and an attached sheet information, which correspond to each medicine. The medicine master also stores information on all medicines dispensed by each of the multiple dispensing devices 3 included in the medicine management system 10. The medicine search master registers information on search items included in search conditions (corresponding to "search conditions" in FIG. 4) described later, such as search item information such as a medicine name, a medicine code, and a YJ code.

[0046] The master information stored in the master storage unit 122 is read from a computer-readable recording medium 161 by the drive device 16, for example, and stored in the storage unit 12. The various pieces of master information may be stored in advance in the storage unit 12, or the server 1 may receive the master information from an external device via the communication network N1. The control unit 11 can update the various pieces of master information stored in the master storage unit 122 at any time based on information acquired from the higher-level system 5 or other systems, or information read from a recording medium using the drive device 16. The control unit 11 can also edit the various pieces of master information in response to a user operation using the server 1 or the client terminal 2.

[0047] The information storage unit 123 is a storage area in which various information such as the prescription data, dispensing performance attribute data D1, and dispensing performance detail data D2 are stored in association with each patient. The control unit 11 accumulates and stores the prescription data input from the upper system 5 in the information storage unit 123 in association with each patient. The control unit 11 also generates dispensing performance attribute data D1 (see FIG. 2) including attribute information on the attributes of dispensing processing (equipment information on the dispensing equipment 3, patient information, etc.) and dispensing performance detail data D2 (see FIG. 3) including detail information on dispensed medicines (medicine code, total usage amount, lot number, etc.) based on the dispensing performance data input from the dispensing equipment 3, and stores them in the information storage unit 123. The dispensing performance attribute data D1 includes a data ID, a machine type category, a machine type number, a prescription number, a dispensing date and time, a patient ID, a patient name, an order number, a prescription category, etc. The dispensing performance detail data D2 includes the drug code, drug name, YJ code, total amount used, lot number, expiry date, expiration date, lot usage amount, and the like.

[0048] 2 and 3 show an example of dispensing performance attribute data D1 and dispensing performance detail data D2 corresponding to prescription number "101" (data ID "0001"), and dispensing performance attribute data D1 and dispensing performance detail data D2 corresponding to prescription number "102" (data ID "0002"). For example, when the tablet packaging device of "Unit No. 1" dispenses drug A with lot number "L0001", drug B with lot number "L0011", and drug C with lot number "L0031" for the prescription data of prescription number "101" (data ID "0001") for patient ID "30001", the control unit 11 registers dispensing performance attribute data D1 and dispensing performance detail data D2 (information associated with data ID "0001" in FIGS. 2 and 3) based on the dispensing performance data acquired from the tablet packaging device. In addition, for example, when the tablet packaging device "Machine No. 2" dispenses drug A with lot number "L0002" and drug A with lot number "L0003" for the prescription data of prescription number "102" (data ID "0002") for patient ID "30002", the control unit 11 registers dispensing history attribute data D1 and dispensing history detail data D2 (information associated with data ID "0002" in Figures 2 and 3) based on the dispensing history data acquired from the tablet packaging device.

[0049] The control unit 11 updates the prescription data in the information storage unit 123 based on information acquired from the higher-level system 5 or other systems, or information read from a recording medium by the server 1 or the client terminal 2. Furthermore, the control unit 11 can update the prescription data with data directly input to the medicine management system 10 by a user's operation on the client terminal 2 or the server 1.

[0050] The control unit 11 also updates the dispensing performance attribute data D1 and the dispensing performance detail data D2 in the information storage unit 123 based on information (the dispensing performance data) acquired from the dispensing device 3. Furthermore, the control unit 11 can update the dispensing performance attribute data D1 and the dispensing performance detail data D2 with data directly input to the medicine management system 10 by a user's operation on the client terminal 2 or the server 1.

[0051] The control unit 11 updates various data in the information storage unit 123, for example, when new data occurs in the upper system 5, the dispensing equipment 3, etc., when a preset time arrives, when a preset time interval has elapsed, or when an update operation is performed by the user.

[0052] The communication I / F 13 has a similar configuration to the communication I / F 23, and executes data communication with the client terminal 2 and external devices such as the printer 4 via the communication network N1. The communication I / F 13 also executes data communication with the upper system 5.

[0053] The display unit 14 is a device such as a liquid crystal display or an organic EL display that displays various information according to control instructions from the control unit 11. The operation unit 15 has a configuration similar to that of the operation unit 25, and is a device operated by a user to input various information to the server 1. The control unit 11 accepts a user operation on the operation unit 15, and executes processing according to the content of the user operation.

[0054] Drive device 16 is a device that reads the medicine management program from a computer-readable recording medium 161 on which the medicine management program is non-temporarily recorded. Then, in the server 1, the control unit 11 installs the medicine management program read from recording medium 161 using drive device 16 into program storage unit 121 of storage unit 12. Note that the medicine management program may be stored in storage unit 12 in advance, or may be received by server 1 from an external device via communication network N1.

[0055] As shown in FIG. 1, the control unit 11 of the server 1 includes an acquisition processing unit 111, a registration processing unit 112, a display processing unit 113, a search processing unit 114, and an output processing unit 115. Specifically, the control unit 11 executes various processes related to a medicine management method described later according to the medicine management program, thereby functioning as various processing units such as the acquisition processing unit 111, the registration processing unit 112, the display processing unit 113, the search processing unit 114, and the output processing unit 115. That is, in this embodiment, the server 1 embodies the main functions of the medicine management system 10. In other words, the medicine management system 10 according to this embodiment only needs to include the server 1, and may not include the client terminal 2, the dispensing device 3, the printer 4, and the like as components. The control unit 11 may include multiple processors, and any of the multiple processors may function as the various processing units. In addition, a part or all of the various processing units may be configured with an electronic circuit.

[0056] Another embodiment may also be considered in which some or all of the functions of the server 1 are provided in the client terminal 2. For example, it is also possible that some or all of the medicine management program is installed in the client terminal 2, and the control unit 21 of the client terminal 2 appropriately acquires necessary information from the server 1 and executes various processes related to the medicine management method described below. In this case, the client terminal 2 embodies the main functions of the medicine management system 10. Furthermore, it is also possible that in the medicine management system 10, the server 1 and the client terminal 2 work together to execute various processes related to the medicine management method described below.

[0057] The acquisition processing unit 111 acquires the prescription data. The prescription data is at least data related to prescriptions of medicines to be managed by the medicine management system 10. The acquisition processing unit 111 can acquire one or more pieces of prescription data for one or more patients. Specifically, the acquisition processing unit 111 acquires the prescription data by reading it from the information storage unit 123. That is, the acquisition processing unit 111 acquires, from the information storage unit 123, the prescription data that has been input to the server 1 from the higher-level system 5 and stored in the information storage unit 123 of the storage unit 12, for example.

[0058] Furthermore, the acquisition processing unit 111 acquires the dispensing history data from the dispensing devices 3. When the medicine management system 10 includes a plurality of dispensing devices 3, the acquisition processing unit 111 acquires the dispensing history data from each of the plurality of dispensing devices 3.

[0059] The registration processing unit 112 registers the dispensing performance attribute data D1 and the dispensing performance detail data D2 in the information storage unit 123. Specifically, the registration processing unit 112 generates dispensing performance attribute data D1 (see FIG. 2) including attribute information on the attributes of the dispensing process and dispensing performance detail data D2 (see FIG. 3) including detail information on the medicine to be dispensed, based on the dispensing performance data acquired from the dispensing device 3, and stores them in the information storage unit 123.

[0060] For example, when the tablet packaging device of "Machine No. 1" dispenses drug A of lot number "L0001", drug B of lot number "L0011", and drug C of lot number "L0031" for the prescription data of prescription number "101" (data ID "0001") for patient ID "30001", and outputs dispensing history data, when the acquisition processing unit 111 acquires the dispensing history data, the registration processing unit 112 stores dispensing history attribute data D1 including attribute information on the attributes of the dispensing process included in the dispensing history data (model type "tablet packaging device", model number "Machine No. 1", prescription number "101", dispensing date and time "April 1, 2023", patient ID "30001", order number, prescription category, etc.) in the information storage unit 12. 3 (see FIG. 2), and dispensing performance detailed data D2 including detailed information on drug A included in the dispensing performance data (drug code "M001", drug name "drug A", YJ code "YJ001", total usage amount, lot number "L0001", expiration date, "expiration date", etc.), detailed information on drug B (drug code "M002", drug name "drug B", YJ code "YJ002", total usage amount, lot number "L0011", expiration date, "expiration date", etc.), and detailed information on drug C (drug code "M003", drug name "drug C", YJ code "YJ003", total usage amount, lot number "L0031", expiration date, "expiration date", etc.) is registered in information storage unit 123 (see FIG. 3). Note that although the YJ code is information consisting of 12 digits, it is represented as "YJxxx" in this specification and drawings for convenience of explanation.

[0061] In addition, for example, when the tablet packing device "Machine No. 2" dispenses drug A with lot number "L0002" and drug A with lot number "L0003" for the prescription data of prescription number "102" (data ID "0002") for patient ID "30002", and outputs dispensing history data, when the acquisition processing unit 111 acquires the dispensing history data, the registration processing unit 112 registers attribute information related to the attributes of the dispensing process included in the dispensing history data (machine type classification "tablet packing device", machine type number "Machine No. 2", prescription number "102", dispensing date and time "April 3, 2023", patient ID "30002", order number, prescription category, etc.) Dispensing performance attribute data D1 including the above information is registered in the information storage unit 123 (see FIG. 2), and dispensing performance detailed data D2 including detailed information about drug A with lot number "L0002" included in the dispensing performance data (drug code "M001", drug name "drug A", YJ code "YJ001", total usage, lot number "L0002", expiration date, "use by date", etc.) and detailed information about drug A with lot number "L0003" (drug code "M001", drug name "drug A", YJ code "YJ001", total usage, lot number "L0003", expiration date, use by date, etc.) is registered in the information storage unit 123 (see FIG. 3).

[0062] In this way, the registration processing unit 112 generates and registers dispensing performance attribute data D1 for each of the prescription data and each patient based on the dispensing performance data input from the dispensing device 3 (see FIG. 2), and generates and registers dispensing performance detail data D2 for each dispensed drug and the lot number of the drug (see FIG. 3). That is, the registration processing unit 112 registers drug identification information (drug code, drug name, etc.) capable of identifying the dispensed drug, lot identification information (lot number, etc.) indicating the lot of the drug, and patient information indicating the patient for whom the drug is prescribed, in association with each other. Furthermore, the registration processing unit 112 registers device identification information (model category, model number, etc.) capable of identifying the dispensing device 3, the drug identification information, the lot identification information, and the patient information in association with each other, based on the dispensing performance data acquired from each of the multiple dispensing devices 3.

[0063] The display processing unit 113 displays a search screen (dispensing history search screen G1) for searching dispensing history (dispensing history) on the client terminal 2. Fig. 4 shows an example of the dispensing history search screen G1. When checking dispensing history (dispensing history), users such as pharmacists, doctors, nurses, medical staff, and facility managers at a medical institution input predetermined search items on the dispensing history search screen G1. The dispensing history search screen G1 includes input fields for search items such as "dispensing date," "lot number," "search conditions," and "drug name."

[0064] The search processing unit 114 executes a search process to search for dispensing records. Specifically, when a user inputs search items and presses a search button K1 on the dispensing record search screen G1 shown in Fig. 4, the search processing unit 114 accepts the user's operation and searches for information on the search records that match the search items. Furthermore, the search processing unit 114 refers to the dispensing record attribute data D1 (see Fig. 2) and the dispensing record detail data D2 (see Fig. 3) to search for information that matches the search items.

[0065] For example, when a user inputs a predetermined date (predetermined period) in "dispensing date", inputs "drug A" in "drug name", and presses search button K1, the search processing unit 114 searches for dispensing records in which "drug A" was dispensed among dispensing records in which dispensing was performed during the inputted predetermined period. Specifically, the search processing unit 114 searches for detailed information (data ID, lot number, expiration date, total usage amount, etc.) associated with "drug A" from dispensing record detailed data D2 (see FIG. 3), and searches for attribute information (patient ID, patient name, dispensing date and time, prescription category, order number, prescription number, dispensing device (model category, model number), etc.) associated with the data ID (here, "0001", "0002") from dispensing record attribute data D1 (see FIG. 2). Then, the search processing unit 114 acquires the attribute information and detailed information in which the dispensing date falls within the predetermined period. In this manner, the search processing unit 114 extracts information (dispensing history) that matches the search conditions set by the user from the dispensing history attribute data D1 and the dispensing history detail data D2.

[0066] The output processing unit 115 outputs the results of the search process (search result) by the search processing unit 114. For example, as shown in FIG. 5, the output processing unit 115 displays the search result F1 on a dispensing record search screen G1. The output processing unit 115 may also cause the printer 4 to execute a print process of the search result F1. This allows information on the dispensing record (dispensing history) in which the target drug ("Drug A" in the above example) was dispensed during a predetermined period to be displayed in a list, allowing the user to easily check the dispensing record during the predetermined period. Furthermore, the user can specify, for example, a patient who was prescribed a drug with a lot number in which a defect occurred, from the search result F1. The output processing unit 115 may display the information on the dispensing record arranged by lot number or by patient name in the search result F1.

[0067] In this embodiment, when a problem occurs with a drug of a specific lot number among certain drugs, the search processing unit 114 can search for information on dispensing records (dispensing history) in which the drug of that lot number has been dispensed. For example, when defect information for a specific lot number is acquired from the pharmaceutical manufacturer of drug A, a user at a medical institution performs a search to narrow down the search results F1 (see FIG. 5) for drug A by lot number (narrowed search). For example, when narrowing down the search results F1 by lot number, the user presses the narrow down button K2 on the dispensing record search screen G1 shown in FIG. 5.

[0068] When the user presses the narrowing down button K2, the display processing unit 113 causes the client terminal 2 to display a lot number selection screen G2 for narrowing down the search results F1 by lot number. An example of the lot number selection screen G2 is shown in Fig. 6. The display processing unit 113 may display the lot number selection screen G2 alongside the dispensing history search screen G1, or may display it overlaid on the dispensing history search screen G1. The display processing unit 113 may also display the lot number selection screen G2 on a page different from the dispensing history search screen G1.

[0069] Furthermore, the display processing unit 113 acquires information on all lot numbers used in dispensing the target drug (here, "drug A") based on the dispensing performance data input from each dispensing machine 3, and displays a list of the acquired lot numbers (lot number list K4) on the lot number selection screen G2. Furthermore, the display processing unit 113 displays each selection section on the lot number selection screen G2 so that a lot number can be individually selected from the lot number list K4, or all lot numbers in the lot number list K4 can be selected together (select all button K3).

[0070] For example, when defect information for lot number "L0002" is acquired from the pharmaceutical manufacturer of drug A, the user selects "L0002" from the lot number list K4 on the lot number selection screen G2 (see FIG. 6) and presses the OK button. When the user selects lot number "L0002" and presses the OK button, the search processing unit 114 accepts the user's operation and searches for search history information associated with lot number "L0002" from the search result F1 (see FIG. 5). In addition, the search processing unit 114 searches for information matching the search items (dispensing date, drug name, lot number) by referring to the dispensing history attribute data D1 (see FIG. 2) and the dispensing history detail data D2 (see FIG. 3). Note that the information on the lot number selected by the user from the lot number list K4 may be reflected in the search item "lot number" on the dispensing history search screen G1 (see FIG. 7).

[0071] The output processing unit 115 outputs the result of the narrowed search by the search processing unit 114 (search result F2). For example, as shown in FIG. 7, the output processing unit 115 displays the search result F2 on the dispensing record search screen G1. The output processing unit 115 may also cause the printer 4 to execute a print process of the search result F2. This allows a list of information on dispensing records (dispensing history) in which a drug with a target lot number ("L0002" in the above example) among the target drug ("Drug A" in the above example) has been dispensed during a predetermined period, so that the user can easily check the information. Furthermore, the user can easily and reliably identify a patient to whom a drug with a defective lot number has been prescribed. When the user identifies the patient, the user can request the patient to stop using the target drug or request the target drug to be recalled (returned).

[0072] In this way, the control unit 11 searches for dispensing records of dispensing "drug A" set as a search condition (search result F1), and then accepts a selection operation of a lot number (see FIG. 6) to narrow down the dispensing records (search result F2). That is, the search processing unit 114 executes a first search process to search for patient information based on the drug name set as a search condition, and when an operation to set a lot number as a search condition is accepted in the result of the first search process, executes a second search process to further search for patient information based on the lot number.

[0073] As another embodiment, the control unit 11 may accept a setting operation of a drug name and a lot number as search conditions together on the dispensing history search screen G1 (see FIG. 4) and search for information on search results that match the set drug name and lot number. That is, when the search processing unit 114 accepts an operation to set a drug name and a lot number as search conditions, the search processing unit 114 may execute a search process to search for patient information based on the drug name and the lot number. In the above example, when the user inputs a predetermined period for the dispensing date, inputs "Drug A" as the drug name, and inputs "L0002" as the lot number on the dispensing history search screen G1 and presses the search button K1, the control unit 11 searches for detailed information (data ID, expiration date, total amount used, etc.) associated with "Drug A" and "L0002" from the dispensing history detailed data D2, searches for attribute information (patient ID, patient name, dispensing date and time, prescription category, order number, prescription number, dispensing equipment (model category, model number), etc.) associated with the data ID from the dispensing history attribute data D1, and outputs the attribute information and detailed information for which the dispensing date falls within the predetermined period as search result F2.

[0074] [Chemical management method] An example of the medicine management method executed mainly by the control unit 11 of the server 1 will be described below. The control unit 11 executes various processes related to the medicine management method when a specific start operation set in advance for executing the medicine management program is performed on the client terminal 2. When a specific start operation is performed on a plurality of client terminals 2, the control unit 11 can execute the medicine management method substantially in parallel for each of the client terminals 2. The medicine management method may be terminated in response to a specific end operation on the client terminal 2 even during execution of the medicine management method. The present invention may be understood as an invention of a method (medicine management method) for executing part or all of the processes of the medicine management method by a computer such as the server 1.

[0075] Here, the start operation includes connection of the client terminal 2 to the server 1 (launch of application software) and login involving input of a user ID and password, while the end operation includes logout and disconnection between the server 1 and the client terminal 2.

[0076] In this embodiment, the dispensing device 3 executes a process (dispensing process) of generating data on dispensing performance (dispensing performance data) when dispensing of medicine according to the prescription data and outputting the data to the server 1. Furthermore, the control unit 11 of the server 1 executes a process of registering various information on the dispensing performance when acquiring the dispensing performance data from the dispensing device 3, and a process of searching for information (patient information) according to a predetermined search condition (such as the lot number of the dispensed medicine) from the registered dispensing performance information.

[0077] [Pharmaceutical processing] An example of a procedure of the processing of the dispensing device 3 related to the dispensing process will be described below with reference to Fig. 8. In the dispensing device 3, in the drug filling operation, a barcode attached to the drug or packaging material is read by a barcode reader, and information on the drug code, drug name, lot number, expiry date, and use-by date is associated with the drug ID and registered in the drug master.

[0078] <Step S11> In step S11, the dispensing device 3 judges whether or not a dispensing instruction has been acquired. When the prescription data of the prescription target is input from the upper system 5 or the server 1 and the dispensing device 3 acquires a dispensing instruction for the prescription data (S11: Yes), the process proceeds to step S12. The dispensing device 3 waits until the dispensing instruction is acquired (S11: No).

[0079] <Step S12> In step S12, the dispensing device 3 executes dispensing processing. For example, when the dispensing device 3 is the tablet packaging device, the tablet packaging device automatically packages and dispenses a predetermined amount of tablets stored in the tablet cassette according to the prescription data. Also, for example, when the dispensing device 3 is the sheet dispensing device, the sheet dispensing device automatically dispenses a predetermined amount of PTP sheets from a plurality of sheet cassettes that contain PTP sheets in which tablets are prepackaged, according to the prescription data.

[0080] <Step S13> In step S13, the dispensing device 3 generates the dispensing performance data including information about dispensing. Specifically, the dispensing device 3 generates the dispensing performance data including information about the performance (history) of dispensing processing, such as a data ID, a model type, a model number, a prescription number, an order number, a prescription type, a dispensing date and time, a patient ID, a patient name, a drug code, a drug name, a YJ code, a total amount used, a lot number, an expiration date, a use-by date, and a lot use amount, corresponding to the prescription data. The dispensing performance data may be composed of, for example, a text file. When the prescription data includes multiple types of drugs, the dispensing device 3 generates the dispensing performance data including the drug code, drug name, YJ code, a total amount used, a lot number, an expiration date, and a use-by date for each of the multiple types of drugs.

[0081] For example, the tablet packaging device 3A is equipped with a medicine master that stores the cassette ID of each tablet cassette C1 in association with medicine information (YJ code, lot number, etc.). When the tablet packaging device 3A acquires prescription data, it identifies the cassette ID of the tablet cassette C1 that contains the medicine corresponding to the prescribed medicine, and further identifies the lot number associated with the identified cassette ID. The tablet packaging device 3A includes the type of prescribed medicine (YJ code) and the identified lot number in the dispensing record data.

[0082] <Step S14> In step S14, the dispensing device 3 outputs the dispensing performance data to the server 1. The dispensing device 3 may output the dispensing performance data to the server 1 when dispensing is completed, or may output the dispensing performance data to the server 1 when a preset time arrives.

[0083] As described above, when the dispensing corresponding to the prescription data is completed, the dispensing device 3 generates the dispensing performance data and outputs it to the server 1. The dispensing device 3 executes the dispensing process every time it acquires the prescription data and the dispensing instruction. When the medicine management system 10 includes multiple dispensing devices 3, each dispensing device 3 executes the dispensing process in parallel.

[0084] [Chemical management processing] Hereinafter, with reference to FIG. 9, an example of a procedure of the process performed by the control unit 11 of the server 1 for the medicine management process corresponding to the medicine management method will be described.

[0085] <Step S21> In step S21, the control unit 11 determines whether or not the dispensing performance data has been acquired from the dispensing device 3. When the dispensing performance data is input from the dispensing device 3 (S21: Yes), the control unit 11 shifts the process to step S22. The control unit 11 waits until the dispensing performance data is input from the dispensing device 3 (S21: No).

[0086] <Step S22> In step S22, the control unit 11 generates dispensing performance attribute data D1 (see FIG. 2) including attribute information related to attributes of dispensing processing and dispensing performance detailed data D2 (see FIG. 3) including detailed information related to the drug to be dispensed based on the dispensing performance data, and registers them in the information storage unit 123. Specifically, the control unit 11 extracts the attribute information (model type, model number, prescription number, dispensing date and time, patient ID, order number, prescription type, etc.) from the dispensing performance data configured in a text file, and generates dispensing performance attribute data D1 including this information. In addition, the control unit 11 extracts the detailed information (drug code, drug name, YJ code, total usage amount, lot number, expiration date, use by date, etc.) from the dispensing performance data configured in a text file, and generates dispensing performance detailed data D2 including this information. The control unit 11 registers the dispensing performance attribute data D1 and the dispensing performance detailed data D2 in the information storage unit 123.

[0087] In another embodiment, the control unit 11 may classify the dispensing performance data acquired from the dispensing equipment 3 by item (model type, model number, prescription number, dispensing date and time, patient ID, order number, prescription type, drug code, drug name, YJ code, total amount used, lot number, expiration date, expiration date, etc.) instead of the dispensing performance attribute data D1 and the dispensing performance detail data D2, and register the classified data in the information storage unit 123.

[0088] <Step S23> In step S23, the control unit 11 determines whether or not to start a search process for dispensing history. For example, when the user starts an application (such as a Web application) for searching for dispensing history on the client terminal 2 and performs a login operation, the control unit 11 determines to start the search process for dispensing history (S23: Yes) and moves the process to step S24. When the control unit 11 does not want to start the search process for dispensing history (S23: No), it repeatedly executes the processes of steps S21 and S22. That is, the control unit 11 executes the process of acquiring the dispensing history data from the dispensing device 3 and registering the dispensing history attribute data D1 and the dispensing history detail data D2 in the information storage unit 123, and when it receives an operation from the user to start the search process for dispensing history, starts the search process described below.

[0089] <Step S24> In step S24, the control unit 11 causes the client terminal 2 to display a dispensing history search screen G1 (see FIG. 4) for searching dispensing history. As shown in FIG. 4, the user can set the dispensing date (dispensing period), lot number, drug code, drug name, YJ code, etc. as search conditions on the dispensing history search screen G1. The following describes an example in which the user sets (inputs) "drug name" as a search condition.

[0090] <Step S25> In step S25, the control unit 11 judges whether or not the search target drug name has been acquired. When the user inputs the search target drug name in the "Drug Name" input field on the dispensing history search screen G1 and presses the search button K1, the control unit 11 judges that the search target drug name has been acquired (S25: Yes) and moves the process to step S26. The control unit 11 waits until the search target drug name is acquired (S25: No).

[0091] When the user sets another search item on the dispensing record search screen G1 and presses the search button K1, the control unit 11 executes a search process according to the search conditions of that search item.

[0092] <Step S26> In step S26, the control unit 11 executes a search process based on the drug name set in the search conditions and outputs the search results. For example, when the user inputs a predetermined date (predetermined period) in "dispensing date", inputs "drug A" in "drug name", and presses the search button K1, the control unit 11 searches for dispensing records in which "drug A" was dispensed among dispensing records in which dispensing was performed during the inputted predetermined period. Specifically, the control unit 11 searches for detailed information (data ID, lot number, expiration date, total usage amount, etc.) associated with "drug A" from the dispensing record detailed data D2, and searches for attribute information (patient ID, patient name, dispensing date and time, prescription classification, order number, prescription number, dispensing device (model classification, model number), etc.) associated with the data ID (here, "0001", "0002") from the dispensing record attribute data D1. Then, the control unit 11 acquires the attribute information and detailed information in which the dispensing date falls within the predetermined period.

[0093] Furthermore, the control unit 11 outputs the results of the search process (search result F1). For example, as shown in Fig. 5, the control unit 11 causes the search result F1 to be displayed on a dispensing history search screen G1. As another embodiment, the control unit 11 may cause the printer 4 to execute a print process of the search result F1. This allows the user to identify, for example, a patient who has been prescribed a drug with a defective lot number, based on the search result F1.

[0094] <Step S27> In step S27, the control unit 11 judges whether or not an instruction to narrow down the search results by lot number has been acquired. When the user presses the narrow down button K2 on the dispensing history search screen G1 (see FIG. 5) on which the search result F1 is displayed, the control unit 11 judges that an instruction to narrow down the search results by lot number has been acquired (S26: Yes), and moves the process to step S28. The control unit 11 waits until an instruction to narrow down the search results by lot number is acquired (S27: No).

[0095] As another embodiment, when the user performs an operation to terminate the application (logoff operation) after obtaining the search result F1, the control unit 11 may return the process to step S21.

[0096] <Step S28> In step S28, the control unit 11 performs a narrowing search by lot number and outputs the search results. Specifically, when the user presses the narrowing button K2 on the dispensing history search screen G1 (see FIG. 5), the control unit 11 causes the client terminal 2 to display a lot number selection screen G2 (see FIG. 6) for narrowing down the search results F1 by lot number. For example, the control unit 11 acquires information on all lot numbers used in dispensing the target drug (here, "drug A") based on the dispensing history data input from each dispensing device 3, and displays a list of the acquired lot numbers (lot number list K4) on the lot number selection screen G2.

[0097] For example, when defect information for lot number "L0002" is obtained from the pharmaceutical manufacturer of drug A, the user selects "L0002" from lot number list K4 on lot number selection screen G2 (see FIG. 6) and presses the OK button. When the user selects lot number "L0002" and presses the OK button, control unit 11 searches for search history information associated with lot number "L0002" from search result F1 (see FIG. 5). Control unit 11 also refers to dispensing history attribute data D1 (see FIG. 2) and dispensing history detail data D2 (see FIG. 3) to search for information matching the search items.

[0098] Then, the control unit 11 outputs the result of the narrowed search (search result F2). For example, as shown in FIG. 7, the control unit 11 displays the search result F2 on the dispensing record search screen G1. That is, the control unit 11 displays a list of dispensing records (dispensing history) in which a drug with a target lot number ("L0002" in the above example) among target drugs ("drug A" in the above example) has been dispensed during a predetermined period, particularly information on patients to whom a drug with the target lot number has been prescribed. This allows the user to identify patients to whom a drug with a defective lot number has been prescribed. In particular, by performing a narrowed search by lot number, patients to whom a drug with the lot number has been prescribed can be easily and reliably identified.

[0099] The control unit 11 repeatedly executes the registration process and search process of the dispensing record attribute data D1 and the dispensing record detail data D2, which are included in the above-mentioned steps S21 to S28.

[0100] As another embodiment of the drug management process, the control unit 11 may accept an operation from the user to set a drug name and a lot number together as search conditions on the dispensing history search screen G1 (see FIG. 4). In this case, the control unit 11 searches for search history information that matches the set drug name and lot number. That is, the control unit 11 may omit the narrowing search by lot number (see FIG. 6) and search for patients who have been prescribed a drug with the lot number by a single search process.

[0101] [Top-up filling (replenishment) process] As described above, in the tablet packaging device 3A, when filling the tablet cassette C1 with medicine, the control unit of the tablet packaging device 3A reads the barcode attached to the medicine with a barcode reader, and registers the information of the medicine code, medicine name, lot number, expiration date, and use-by date in the medicine master in association with the medicine ID. Identification information of the tablet cassette C1 (cassette ID, etc.) is associated and registered in the medicine master. Therefore, in the medicine master, the information of the cassette ID, medicine code, medicine name, lot number, expiration date, and use-by date are associated and registered for each tablet cassette C1.

[0102] Furthermore, when the drug in the tablet cassette C1 runs out due to dispensing processing (when the tablet cassette C1 becomes empty), a drug refilling operation is performed, and the control unit updates the drug master. For example, when a drug with a new lot number is refilled into the tablet cassette C1, the control unit updates the information on the lot number, expiration date, and use-by date associated with the cassette ID of the tablet cassette C1. Basically, one lot number is linked to one tablet cassette C1. When linking the lot numbers, the new lot number is overwritten over the original lot number. However, as described later, when a top-up refilling process is performed, multiple lot numbers (the original lot number and the new lot number) may be linked to one tablet cassette C1 without overwriting the new lot number.

[0103] Here, a filling operation (top-up filling, refilling operation) may be performed when the medicine in the tablet cassette C1 reaches a specified amount. The filling operation is performed, for example, when the medicine in the tablet cassette C1 falls below a predetermined amount (for example, 50 tablets), when the dispensed amount of the received prescription exceeds the filled amount (current amount), etc. In this way, by performing the filling operation before the medicine in the tablet cassette C1 runs out of stock, it is possible to avoid the medicine running out of stock and the interruption of the dispensing process. If the filling operation (top-up filling) is performed when the medicine in the tablet cassette C1 reaches a specified amount, a situation may occur in which tablets with different lot numbers are mixed in the tablet cassette C1. That is, one tablet cassette C1 will contain medicines with multiple lot numbers. In this case, multiple lot numbers are associated with one cassette ID and registered in the medicine master.

[0104] When drugs are dispensed from a tablet cassette C1 that contains drugs with multiple lot numbers for the target prescription data, there is a possibility that the same type of drug but with a different lot number may be prescribed for a single patient of the prescription data. In this case, for example, if a problem occurs with a drug with one of the multiple lot numbers prescribed for the patient, it is necessary to reliably identify the patient.

[0105] Therefore, when a medicine is dispensed from tablet cassette C1 containing medicines with multiple lot numbers, the control unit of tablet packaging device 3A generates the dispensing history data including information on each of the multiple lot numbers (including information on the expiration date and use-by date), and outputs the data to server 1. Furthermore, the control unit may add a flag to the dispensing history data indicating that a medicine with any one of the multiple lot numbers has been dispensed.

[0106] When the control unit 11 of the server 1 acquires the dispensing history data including the flag, it displays information on the multiple lot numbers that may have been prescribed for the drug on the dispensing history search screen G1. For example, as shown in FIG. 5, the control unit 11 displays "◯" in the "multiple lots" column of the search result F1. "Multiple lots" is information that identifies whether or not the dispensed drug was dispensed from a tablet cassette C1 that contains drugs with multiple lot numbers. The control unit 11 displays "◯" in the "multiple lots" column for dispensing history in which a drug was dispensed from a tablet cassette C1 that contains multiple drugs with different lot numbers, and leaves the "multiple lots" column blank for dispensing history in which a drug was dispensed from a tablet cassette C1 that contains a drug with a single lot number.

[0107] As another embodiment, when the control unit 11 acquires the dispensing record data including the flag, as shown in Fig. 11, the control unit 11 may provide an "other lot number" field in the dispensing record detail data D2 and register the lot number of the drug that has been topped up. Then, as shown in Fig. 12, the control unit 11 may display the lot number of the drug that has been topped up in the "other lot number" field on the dispensing record search screen G1. For example, the control unit 11 may display the lot number of drug A that was previously filled in the tablet packaging device 3A (tablet cassette C1) in the "lot number" field, and may display the lot number of drug A that has been topped up in the tablet cassette C1 in the "other lot number" field.

[0108] As another embodiment, the expiration date and expiration date corresponding to the drug with the "other lot number" may be displayed on the dispensing history search screen G1 shown in Fig. 12. As another embodiment, when the dispensing device 3 dispenses drugs with multiple lot numbers from a tablet cassette C1 filled with the drugs, each of the multiple lot numbers may be included in the dispensing history data. In this case, the control unit 11 of the server 1 may register the multiple lot numbers in the "lot number" of the dispensing history detail data D2, and display the multiple lot numbers in the "lot number" field on the dispensing history search screen G1.

[0109] Furthermore, when narrowing down the search by lot number, the control unit 11 searches for dispensing record information in which the lot number selected by the user (see FIG. 6) matches any one of the plurality of lot numbers.

[0110] For example, in a case where a drug A with a lot number "L0002" and a drug A with a lot number "L0040" are contained in a certain tablet cassette C1, and a drug A with a lot number "L0040" and a drug A with a lot number "L0060" are contained in another tablet cassette C1, and the drug A is dispensed from these tablet cassettes C1, when a user sets the lot number "L0040" of the defective drug A as a search condition and searches, the control unit 11 extracts and outputs patient information of the dispensing history where "L0040" is registered in the "lot number" or "other lot number" in the dispensing history detail data D2 (see FIG. 11). In the example shown in FIG. 11, the control unit 11 extracts and outputs patient information of data IDs "0010" and "0040".

[0111] The control unit 11 may display the plurality of lot numbers as one option on the lot number selection screen G2.

[0112] In this way, when the same type of medicine is refilled in the dispensing device 3, the original lot number is not updated to the lot number of the newly refilled medicine, and the information of the original lot number and the new lot number are held, thereby preventing the occurrence of omission of information corresponding to the other lot number in a search process by one of the lot numbers. For example, when the medicine A is dispensed from the tablet cassette C1 containing the medicine A with the lot number "L0002" and the medicine A with the lot number "L0040", it is unclear whether the medicine prescribed to the patient is the medicine A with the lot number "L0002", the medicine A with the lot number "L0040", or a mixture of the medicine A with each lot number. However, according to the above configuration, it is possible to search for the patient without omission. As a result, for example, even in the case where the medicine A with the lot number "L0002" is defective or the medicine A with the lot number "L0040" is defective, the patient to whom the medicine A was prescribed can be identified.

[0113] The dispensing device 3 may be capable of registering up to 10 lot numbers. For example, the tablet packaging device 3A may be capable of registering up to 10 lot numbers for each tablet cassette C1. The control unit of the tablet packaging device 3A may be configured not to accept further filling operations when the number of registered lot numbers reaches 10.

[0114] As described above, in the replenishment filling process, when multiple drugs of the same type but different lot numbers are filled into the dispensing device 3, when the dispensing of the drugs is completed in the dispensing device 3, the output processing unit 115 outputs the drug identification information corresponding to the drug, the multiple different lot numbers, and the patient information in association with each other in accordance with the search process.

[0115] [Reset process] As described above, when refilling medicines in the dispensing device 3, a situation may occur in which medicines with multiple lot numbers are always mixed in the dispensing device 3. In this case, there is a possibility that the search efficiency may decrease in a search process by lot number, such as by extracting information on a patient who has not actually been prescribed a medicine with the target lot number.

[0116] Therefore, a process of resetting the registered lot number may be executed in the dispensing device 3. For example, when the medicine in the tablet cassette C1 is out of stock, the control unit of the tablet packaging device 3A resets (deletes) the lot number associated with the tablet cassette C1 (cassette ID). When multiple lot numbers are associated with a cassette ID, the control unit resets all the lot numbers. Then, when the tablet cassette C1 is filled with medicine after the reset (after it becomes empty), the control unit newly registers the lot number of the medicine.

[0117] In another embodiment, the control unit of the tablet packaging device 3A may reset the lot number associated with the tablet cassette C1 in response to a reset operation by the user. For example, in a case where a drug A with a lot number "L0002" is stored in a tablet cassette C1 and a drug A with a lot number "L0040" is added, the user performs a reset operation when the user determines that substantially all of the drug A with the lot number "L0002" has been dispensed from the tablet cassette C1. When the user performs a reset operation, the control unit deletes the original lot number "L0002" and updates the lot number to "L0040". As a result, in the subsequent search process, information (actual information) of the drug A dispensed from the tablet cassette C1 is excluded from the search process using the lot number "L0002" as a search condition.

[0118] In another embodiment, the control unit of the tablet packaging device 3A may reset the lot number associated with the tablet cassette C1 based on the information of the dispensing process. For example, when the number of times that the drug A has been dispensed from the tablet cassette C1 reaches a predetermined number of times after the drug A with the lot number "L0002" is added to the tablet cassette C1 containing the drug A with the lot number "L0040", or when the dispensed amount reaches a predetermined amount, the control unit deletes the original lot number "L0002" and updates it to the lot number "L0040". The predetermined number of times and the predetermined amount may be preset by the user or may be appropriately changeable.

[0119] In another embodiment, the control unit of the tablet packaging device 3A may reset the lot number associated with the tablet cassette C1 when a preset time has elapsed. For example, when a preset time has elapsed since drug A with lot number "L0040" was added to the tablet cassette C1 containing drug A with lot number "L0002", the control unit deletes the original lot number "L0002" and updates it to lot number "L0040". The preset time may be set in advance by the user, or may be changeable as appropriate.

[0120] As described above, in the reset process, when the drug is filled in the dispensing device 3, the registration processing unit 112 registers device identification information capable of identifying the dispensing device 3 in association with the drug identification information and the lot number. Also, when the drug filled in the dispensing device 3 runs out of stock in the dispensing device 3, or when a predetermined operation by the user is received, the registration processing unit 112 deletes (resets) the lot number associated with the device identification information. Also, when the dispensing device 3 includes a plurality of tablet cassettes C1 (tablet cassettes C1) capable of storing drugs, when a drug is filled in one tablet cassette C1, the registration processing unit 112 registers a cassette ID (storage unit identification information) capable of identifying the tablet cassette C1 in association with the drug identification information and the lot number, and when the drug filled in the tablet cassette C1 runs out of stock in the tablet cassette C1, or when a predetermined operation by the user is received, the registration processing unit 112 deletes the lot number associated with the tablet cassette C1.

[0121] [Registration process for unknown lots] When medicines are filled into the dispensing device 3, there are cases where the lot number is not registered. Also, there are cases where lot numbers are not assigned to medicines received from pharmaceutical manufacturers. Such medicines may be missed in the search process based on lot numbers.

[0122] Therefore, the control unit of the dispensing device 3 may manage the drug for which the lot number cannot be obtained (e.g., drug A) as the lot number "unknown." For example, the control unit registers "unknown" in the information of the lot number of the target drug A included in the dispensing record data.

[0123] When the control unit 11 of the server 1 acquires the dispensing performance data including information of the lot number "unknown", it registers "unknown" in the "lot number" of the dispensing performance detail data D2 (see FIG. 3). Furthermore, when drug A is set as a search condition in the search process, the control unit 11 also extracts drug A with an unknown lot number as a search target (see FIG. 5). Furthermore, the control unit 11 may display the lot number "unknown" selectable on the lot number selection screen G2, as shown in FIG. 6.

[0124] In this way, for example, if a problem occurs with drug A, the dispensed drug A may include drug A with a known lot number and drug A with an unknown lot number. In this regard, with the above configuration, drug A with an unknown lot number can always be included in the search results, making it possible to identify patients who have been prescribed drug A with an unknown lot number. Also, as shown in FIG. 6, the user can select "unknown" to search for only patients who have been prescribed a drug with an unknown lot number.

[0125] As described above, in the unknown lot registration process, if the dispensed medicines include a medicine with an unknown lot number, the output processing unit 115 outputs the medicine identification information corresponding to the medicine with an unknown lot number, information that can identify that the lot number is unknown, and the patient information in association with each other in accordance with the search process.

[0126] [Other embodiments] In another embodiment of the present invention, when a drug and a lot number are set as search conditions, the control unit 11 of the server 1 may output only patient information of patients who satisfy the search conditions. For example, as shown in Fig. 13, the control unit 11 searches for patient information (patient ID and patient name) that satisfies the search conditions of the dispensing date, drug name ("Drug A"), and lot number ("L0002") input by the user, and outputs a search result F3 including the patient ID and the patient name.

[0127] The control unit 11 may include, in the search result F3, information on patients prescribed drugs with unknown lot numbers.

[0128] As another embodiment of the present invention, the control unit 11 (output processing unit 115) of the server 1 may output search results for each prescription. FIG. 14 shows search result F2 narrowed down by lot number "L0002". As shown in FIG. 14, dispensing records of prescriptions including drugs with lot number "L0002" may be displayed in a list. As another embodiment, the control unit 11 may output search result F2 for each patient.

[0129] In addition, in each of the above-described embodiments, the tablet packing device 3A is given as an example of the dispensing device 3, but the dispensing device 3 of the present invention is not limited to the tablet packing device 3A. For example, the dispensing device 3 may be a picking device. The picking device includes a control device, an operation terminal (e.g., a smartphone, a handheld terminal), and the like. The picking device is used when a user manually dispenses medicine, reads the name of a medicine from a medicine shelf that stores the medicine or from identification information (such as a barcode) given to the medicine, and compares the read medicine name with the medicine name included in the prescription data.

[0130] Specifically, in the picking device, when a medicine is filled into a medicine shelf, the user uses a barcode reader to read the barcode attached to the medicine and the barcode attached to the medicine shelf, and the control device registers information on the medicine code, medicine name, lot number, expiration date, and use-by date in the medicine master in association with the medicine ID and medicine shelf identification information (shelf ID (shelf number)). In other words, when a medicine is filled into a medicine shelf, the medicine ID, lot number, and shelf ID are registered in association with each other. Note that instead of the medicine ID, the medicine code, lot number, and shelf ID may be registered in association with each other.

[0131] When a user manually dispenses medicine in the picking device, the user performs the picking work by checking the shelf ID and drug name displayed on the operation terminal. For example, the user reads the barcode attached to the medicine shelf of the shelf ID displayed on the operation terminal, and compares the drug name associated with the read shelf ID with the drug name included in the prescription data. In addition, when the control device reads the barcode attached to the medicine shelf, it obtains the lot number associated with the shelf ID.

[0132] In another embodiment, for example, when a medicine of a certain type of PTP sheet is filled in a medicine shelf, the GS1 code given to the packaging box is read and the identified lot number and medicine code are stored in association with each other. When the medicine is picked, the GS1 code given to the medicine is read to identify the type of the medicine, and the type of the medicine is matched with the type of medicine specified in the prescription data, and the lot number registered in association with the type of the medicine (medicine code) is obtained. In this way, in the picking work, the process of reading the GS1 code given to the medicine may be used as a trigger to execute the medicine matching process and the lot number acquisition process. Note that, although the lot number can usually be known by reading the GS1 code given to the medicine, there are cases where the lot number is unknown, so the above-mentioned lot number acquisition process may be performed. That is, according to the above configuration, even if the lot number cannot be directly obtained by reading the GS1 code, it is possible to acquire the lot number by going through the process of identifying the type of the medicine.

[0133] As described above, the control device may include a memory processing unit that associates the drug ID of a drug stored in a drug shelf (storage shelf) with the lot number of the drug and stores them in a memory unit, an acquisition processing unit that acquires the drug ID of the drug to be dispensed, a reading processing unit that reads a code assigned to the drug, a matching record processing unit that matches the drug ID acquired by the acquisition means with the drug ID read by the reading processing unit and acquires from the memory unit the lot number stored in association with the drug ID acquired by the acquisition means, and a memory processing unit that associates the matching result by the matching record processing unit with the lot number acquired by the matching record processing unit and stores them in association with each other.

[0134] When the user picks the target medicine and completes dispensing, the control device outputs the dispensing performance data to server 1. In this manner, in the picking device, the dispensing performance data is generated in accordance with the picking work and dispensing work performed by the user, and is output to server 1. Server 1 executes the registration process and the search process based on the dispensing performance data input from the picking device.

[0135] In each of the above-mentioned embodiments, the server 1 acquires the dispensing performance data from the dispensing device 3, generates the dispensing performance attribute data D1 (see FIG. 2) and the dispensing performance detail data D2 (see FIG. 3), and executes the search process. As another embodiment, the control device 30 that controls the dispensing device 3 may generate the dispensing performance attribute data D1 and the dispensing performance detail data D2 based on the dispensing performance data, and execute the search process. Specifically, as shown in FIG. 15, the control device 30 is a personal computer including a control unit 31, a storage unit 32, a communication I / F 33, a display unit 34, an operation unit 35, and a drive device 36. For example, one control device 30 is connected to one dispensing device 3 and controls the dispensing device 3. When a plurality of dispensing devices 3 are set, one control device 30 may be provided for each dispensing device 3.

[0136] The control unit 31 has a configuration similar to that of the control unit 11, and has control devices such as a CPU, ROM, RAM, and EEPROM, and uses the CPU to execute various processes in accordance with various control programs pre-stored in the ROM, the EEPROM, or the memory unit 32.

[0137] The storage unit 32 is a non-volatile storage unit such as a hard disk or SSD that stores various control programs and various data executed by the control unit 31. The storage unit 32 also includes a program storage unit 321, a master storage unit 322, and an information storage unit 323.

[0138] The program storage unit 321 has the same configuration as the program storage unit 121, and is a storage area in which a medicine management program for causing the control unit 31 to execute various processes related to the medicine management method is stored. The program storage unit 321 also stores programs such as an operating system (OS).

[0139] The master storage unit 322 has a configuration similar to that of the master storage unit 122, and stores various master information such as a patient master, a medicine master, a medicine search master, etc. The master information stored in the master storage unit 322 is read from the computer-readable recording medium 161 by, for example, the drive device 36, and stored in the storage unit 32.

[0140] The information storage unit 323 has the same configuration as the information storage unit 123, and stores various information such as the prescription data, dispensing performance attribute data D1, and dispensing performance detail data D2 in association with each patient.

[0141] The communication I / F 33, the display unit 34, the operation unit 35, and the drive device 36 have the same configurations as the communication I / F 13, the display unit 14, the operation unit 15, and the drive device 16, respectively.

[0142] The control unit 31 includes an acquisition processing unit 311, a registration processing unit 312, a display processing unit 313, a search processing unit 314, and an output processing unit 315, and each processing unit has the same configuration as the acquisition processing unit 111, the registration processing unit 112, the display processing unit 113, the search processing unit 114, and the output processing unit 115, respectively.

[0143] For example, the acquisition processing unit 311 acquires the prescription data input from the higher-level system 5 to the control device 30 and stored in the information storage unit 323 of the storage unit 32 from the information storage unit 323. Furthermore, when dispensing is completed at the dispensing device 3, the registration processing unit 312 generates dispensing performance attribute data D1 and dispensing performance detail data D2 based on the dispensing performance data input from the dispensing device 3, and stores them in the information storage unit 323.

[0144] In addition, the display processing unit 313 causes the display unit 34 or the client terminal 2 to display a search screen for searching for dispensing records (dispensing record search screen G1).

[0145] Furthermore, the search processing unit 314 executes a search process for searching for dispensing records, and the output processing unit 315 outputs the search results. For example, the output processing unit 315 displays search results F1 (see FIG. 5), F2 (see FIG. 7), and F3 (see FIG. 13) on the display unit 34 or the client terminal 2, or causes the printer 4 to print them.

[0146] In the control device 30, the search processing unit 314 may execute the search process based on the drug name set in the search conditions, similar to the search processing unit 114, and then execute the search process based on the lot number set in the search conditions of a refined search, or execute the search process based on the drug name and lot number set together in the search conditions. In addition, when the control device 30 controls a dispensing device 3 that dispenses one type of drug, the search processing unit 314 may execute the search process based only on the lot number set in the search conditions.

[0147] In this way, in the present invention, the search processing unit may execute a search process for patient information based on at least one of drug identification information (such as drug name) and lot identification information (such as lot number) set as search conditions. Then, in the present invention, the output processing unit may output the drug identification information, the lot identification information, and the patient information in association with each other in accordance with the search process.

[0148] In this way, the control device 30 may execute the medicine management process for each individual dispensing device 3. That is, the control device 30 may be provided for each dispensing device 3 individually. The medicine management system 10 according to the present invention may have the following configuration.

[0149] [Lot management using storage trays] In the injection drug dispensing device (an example of a dispensing device 3), trays (cassettes) containing injection drugs by drug type are stored on a tray shelf. When dispensing an injection drug, the injection drug dispensing device moves a tray corresponding to the type of injection drug to be dispensed from the tray shelf based on input prescription data, takes out the injection drug contained in the tray, and determines whether the type and expiration date are appropriate. If the type and expiration date of the injection drug are appropriate, the injection drug dispensing device dispenses the injection drug.

[0150] When filling the injection drug dispensing device with an injection drug, the injection drug dispensing device registers the lot number of the injection drug and the identification information of the tray in association with each other. An example of a tray Ca is shown in Fig. 16. The tray Ca has two storage sections, a front section and a rear section, which are divided by a dividing member SP (partition plate). A barcode BC1 is provided on the tray Ca, a barcode BC2 is provided in the front storage section of the tray Ca, and a barcode BC3 is provided in the rear storage section of the tray Ca. Unique information and storage position information of the tray Ca are registered in association with the barcode BC1.

[0151] For example, the front storage section is filled with a first lot of the injection drug T, and the rear storage section is filled with a second lot of the injection drug T. As a result, the identification information of the injection drug T and the first lot number of the injection drug T are associated and registered in the barcode BC2, and similarly, the identification information of the injection drug T and the second lot number of the injection drug T are associated and registered in the barcode BC3. In this way, one tray Ca is divided into front and rear storage sections, and the same type of injection drug is stored in each of the front storage section and the rear storage section, and different lot numbers are set for each section.

[0152] In the above configuration, one tray Ca can store drugs with different lot numbers in the front and rear storage sections. As a result, even if the previous lot of drugs does not fill one tray Ca, one tray Ca can be divided into front and rear sections and the current lot and the next lot are separately filled, allowing for sufficient filling and smooth operation. The same type of drug may be stored in multiple trays, and different lot numbers may be set for each tray. Also, when the dividing member SP is removed from the tray Ca, the same type of drug with the same lot number is stored.

[0153] As an example of the injection drug dispensing device and tray, the configuration disclosed in JP 2020-89720 can be applied.

[0154] [Lot number reflection function] When filling medicines with a medicine packaging device, there are two cases: the lot number printed on the medicine box is manually entered, and the GS1 code printed on the medicine box or medicine sheet (PTP sheet) is read and entered by the medicine packaging device. Here, for example, when a medicine is removed from the PTP sheet and placed in a bottle, the GS1 code may not be read. Also, if the PTP sheet is partial (fractional), the GS1 code may not be read. In such cases, it is necessary to check the medicine box and manually enter the lot number, but if the medicine box has been discarded, it becomes impossible to register the lot number.

[0155] Therefore, the medicine packaging device has a configuration for reflecting the lot number previously input in the current filling operation if a lot number was previously input. For example, a "reflect previous input" button is displayed on the operation screen of the medicine packaging device. For example, when medicine A is filled and the "reflect previous input" button is pressed, the medicine packaging device registers the lot number previously registered for that medicine A in association with the medicine A filled this time.

[0156] In addition, in the medicine packaging device, information on the lot number previously inputted for each medicine is registered.

[0157] This allows the worker, for example, when repeatedly filling a chemical with the same lot number, to simply press the "Reflect Previous Input" button to register the lot number without having to manually input the lot number each time. This reduces the workload of the filling operation. When a new lot number is entered, the lot number corresponding to the "Reflect Previous Input" button is updated to the new lot number.

[0158] The medicine management system of the present invention may be configured with the server 1 alone, or may be configured with the dispensing device 3 alone. Moreover, the medicine management system of the present invention may be configured with a combination of the server 1 and the dispensing device 3. Moreover, the client terminal 2 may have the function of the server 1.

[0159] [Notes on the invention] The following will provide an overview of the invention extracted from the above-described embodiment. Note that the configurations and processing functions described in the following supplementary notes can be selected and combined as desired.

[0160] <Appendix 1> a registration processing unit that registers, in association with one another, drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating a patient for whom the drug is prescribed; a search processing unit that executes a search process for patient information based on at least one of drug identification information and lot identification information that are set as search conditions; an output processing unit that outputs the drug identification information, the lot identification information, and the patient information in association with each other in response to the search processing; A drug management system comprising:

[0161] <Appendix 2> the registration processing unit registers device identification information capable of identifying the dispensing device, the drug identification information, the lot identification information, and the patient information in association with each other based on dispensing performance information acquired from each of the plurality of dispensing devices; 2. A drug management system as described in appendix 1.

[0162] <Appendix 3> The dispensing record information includes the drug identification information and the lot identification information acquired when the drug is filled into the dispensing device, and the patient information included in prescription data corresponding to the drug input to the dispensing device. 2. A drug management system as described in appendix 2.

[0163] <Appendix 4> the search processing unit executes a first search process for searching for the patient information based on the medicine identification information set as the search condition, and when an operation for setting the lot identification information as the search condition is received as a result of the first search process, executes a second search process for further searching for the patient information based on the lot identification information. 4. The medicine management system according to any one of claims 1 to 3.

[0164] <Appendix 5> When a plurality of drugs having the same type but different lot identification information are filled in a dispensing device, when dispensing of the drugs in the dispensing device is completed, the output processing unit outputs the drug identification information corresponding to the drug, the plurality of different lot identification information, and the patient information in association with each other in accordance with the search process. 5. The medicine management system according to any one of claims 1 to 4.

[0165] <Appendix 6> The dispensing device includes a plurality of storage units capable of storing medicines, When a plurality of the medicines having the same type but different lot identification information are filled in one storage unit, the registration processing unit registers storage unit identification information capable of identifying the storage unit, and the medicine identification information and the lot identification information corresponding to each of the plurality of the medicines stored in the storage unit in association with each other. 6. A drug management system as described in appendix 5.

[0166] <Appendix 7> When the medicine is filled into the dispensing device, the registration processing unit registers device identification information capable of identifying the dispensing device in association with the medicine identification information and the lot identification information; When the drug filled in the dispensing device is out of stock in the dispensing device, or when a predetermined operation by a user is received, the registration processing unit deletes the lot identification information associated with the device identification information. 6. A medicine management system according to any one of appendices 1 to 5.

[0167] <Appendix 8> the registration processing unit, when the drug is filled into one of the storage units of a dispensing device including a plurality of storage units capable of storing a drug, registers storage unit identification information capable of identifying the storage unit in association with the drug identification information and the lot identification information; when the drug filled in the storage unit is out of stock in the storage unit, or when a predetermined operation by a user is received, the registration processing unit deletes the lot identification information associated with the storage unit identification information. 8. A medicine management system according to any one of claims 1 to 7.

[0168] <Appendix 9> When the dispensed medicine includes a medicine whose lot identification information is unknown, the output processing unit outputs, in response to the search process, the medicine identification information corresponding to the medicine whose lot identification information is unknown, information capable of identifying that the lot identification information is unknown, and the patient information in association with each other. 9. A medicine management system according to any one of appendices 1 to 8.

[0169] <Appendix 10> the output processing unit causes an operation terminal that accepts an input operation of the search conditions to display the drug identification information, the lot identification information, and the patient information in association with each other. 10. A medicine management system according to any one of appendices 1 to 9.

[0170] <Appendix 11> a registration processing unit that registers, in association with each other, drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating a patient for whom the drug is prescribed; an output processing unit that outputs the medicine identification information, the lot identification information, and the patient information in association with each other; A drug management system comprising: [Explanation of symbols]

[0171] 10: Drug management system 1: Server 2: Client terminal 3: Pharmacy equipment 3A: Tablet packaging device 4: Printer 111: Acquisition processing unit 112: Registration processing unit 113: Display processing unit 114: Search processing unit 115: Output processing section 121: Program memory section 122: Master memory section 123: Information storage section D1: Dispensing performance attribute data D2: Dispensing performance details data F1 :Search results F2 :Search results F3 :Search results G1: Dispensing record search screen G2: Lot number selection screen

Claims

1. a registration processing unit that registers, in association with one another, drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating a patient for whom the drug is prescribed; a search processing unit that executes a search process for patient information based on at least one of drug identification information and lot identification information that are set as search conditions; an output processing unit that outputs the drug identification information, the lot identification information, and the patient information in association with each other in response to the search processing; A drug management system comprising:

2. the registration processing unit registers device identification information capable of identifying the dispensing device, the drug identification information, the lot identification information, and the patient information in association with each other based on dispensing performance information acquired from each of the plurality of dispensing devices; The medicine management system according to claim 1 .

3. The dispensing record information includes the drug identification information and the lot identification information acquired when the drug is filled into the dispensing device, and the patient information included in prescription data corresponding to the drug input to the dispensing device. The medicine management system according to claim 2 .

4. the search processing unit executes a first search process for searching for the patient information based on the drug identification information set as the search condition, and when an operation for setting the lot identification information as the search condition is received as a result of the first search process, executes a second search process for further searching for the patient information based on the lot identification information. The medicine management system according to claim 1 .

5. When a plurality of drugs having the same type but different lot identification information are filled in a dispensing device, when dispensing of the drugs in the dispensing device is completed, the output processing unit outputs the drug identification information corresponding to the drug, the plurality of different lot identification information, and the patient information in association with each other in accordance with the search process. The medicine management system according to claim 1 .

6. The dispensing device includes a plurality of storage units capable of storing medicines, When a plurality of the medicines having the same type but different lot identification information are filled in one storage unit, the registration processing unit registers storage unit identification information capable of identifying the storage unit, and the medicine identification information and the lot identification information corresponding to each of the plurality of the medicines stored in the storage unit in association with each other. The medicine management system according to claim 5 .

7. When the medicine is filled into the dispensing device, the registration processing unit registers device identification information capable of identifying the dispensing device in association with the medicine identification information and the lot identification information; When the drug filled in the dispensing device is out of stock in the dispensing device, or when a predetermined operation by a user is received, the registration processing unit deletes the lot identification information associated with the device identification information. The medicine management system according to any one of claims 1 to 6.

8. the registration processing unit, when the drug is filled into one of the storage units of a dispensing device including a plurality of storage units capable of storing a drug, registers storage unit identification information capable of identifying the storage unit in association with the drug identification information and the lot identification information; when the drug filled in the storage unit is out of stock in the storage unit, or when a predetermined operation by a user is received, the registration processing unit deletes the lot identification information associated with the storage unit identification information. The medicine management system according to any one of claims 1 to 6.

9. When the dispensed medicine includes a medicine whose lot identification information is unknown, the output processing unit outputs, in response to the search process, the medicine identification information corresponding to the medicine whose lot identification information is unknown, information capable of identifying that the lot identification information is unknown, and the patient information in association with each other. The medicine management system according to claim 1 .

10. the output processing unit causes an operation terminal that accepts an input operation of the search conditions to display the drug identification information, the lot identification information, and the patient information in association with each other. The medicine management system according to any one of claims 1 to 6.

11. a registration processing unit that registers, in association with each other, drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating a patient for whom the drug is prescribed; an output processing unit that outputs the medicine identification information, the lot identification information, and the patient information in association with each other; A drug management system comprising:

12. registering drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating the patient for whom the drug is prescribed in association with each other; executing a search process for patient information based on at least one of drug identification information and lot identification information set as a search condition; outputting the drug identification information, the lot identification information, and the patient information in association with each other in response to the search process; A drug management method executed by one or more processors.

13. registering drug identification information capable of identifying a dispensed drug, lot identification information indicating the lot of the drug, and patient information indicating the patient for whom the drug is prescribed in association with each other; executing a search process for patient information based on at least one of drug identification information and lot identification information set as a search condition; outputting the drug identification information, the lot identification information, and the patient information in association with each other in response to the search process; A drug management program for causing one or more processors to execute the above.

Images