Medication management system, management server, and management server control program

Abstract

To provide a medication management system, a management server, and a control program for the management server with which it is possible to appropriately manage medication to patients and reduce the burdens of caregivers, etc. related to the management of medication to patients.SOLUTION: A medication management system comprises a receipt computer 151, a management server 152, and a caregiver's portable terminal 352. The management server 152 acquires patient identification information and patient medicine information from the receipt computer 151 and stores it in a database. The portable terminal 352 acquires the identification information and administered medicine information of a care-receiver. Whether or not medication to the care-receiver is appropriate, is determined on the basis of the patient identification information, patient medicine information and the identification information and administered medicine information of the care-receiver, and the determination result is displayed to the portable terminal 352.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a medication management system, a management server, and a control program for the management server. More particularly, the present invention relates to a medication management system for managing medication, a management server, and a control program for the management server. [Background technology]

[0002] In nursing care facilities and the like, a caregiver (such as a staff member at the nursing care facility) may assist a person receiving care (such as a resident of the nursing care facility) in administering medication prescribed to that person. In this case, the medication prescribed to the person receiving care is delivered to that person by a delivery person (such as a pharmacy staff member). When delivering the medication, the delivery person visually confirms that the information written on the medication packaging, such as the patient's name, medication name, date of administration, and directions for use, is correct. In addition, when administering the medication, the caregiver visually confirms that the information written on the medication packaging, such as the patient's name, medication name, date of administration, and directions for use, is correct. These confirmations prevent the wrong medication, such as administering medication for another patient to a person receiving care, or the wrong timing of administering medication to a person receiving care.

[0003] However, in situations where there are many people receiving care, such as in nursing homes, visual inspection by delivery personnel or caregivers alone is still prone to medication errors and mistakes in the timing of medication administration.

[0004] As a technique for preventing medication errors, a technique for providing a determination result as to whether or not medication is appropriate for a patient has been proposed. For example, Patent Document 1 below discloses a three-point authentication technique. In Patent Document 1 below, a small terminal reads the information code of the medication to be administered, the information code of the caregiver administering the medication, and the information code of the patient receiving the medication, and transmits them to a management server. The management server determines whether or not the medication is appropriate for the patient based on the received information, and displays the determination result on the small terminal. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-84159 DISCLOSURE OF THE INVENTION [Problem to be solved by the invention]

[0006] In conventional technology, various types of medication-related information were managed by a management server. The various types of medication-related information managed by the management server were entered by caregivers or other personnel when the prescribed medications were delivered. When entering the various types of information, the caregivers or other personnel visually checked the various types of information displayed on the medications and manually entered them into the management server. As a result, due to visual inspection errors or input errors, incorrect medication-related information (in other words, information different from the information written on the prescription) was managed by the management server. As a result, the results of the judgment on whether medication was appropriate for the patient were inaccurate, and problems arose in which medication for the patient could not be managed appropriately.

[0007] The present invention is intended to solve the above-mentioned problems, and one of its objectives is to provide a medication management system, a management server, and a control program for the management server that can appropriately manage medication for patients.

[0008] Furthermore, with conventional technology, pharmacists and pharmacy staff simply delivered prescribed medications to patients. The various medication-related information managed by the management server had to be entered by caregivers, placing a heavy burden on caregivers to manage medication administration to patients.

[0009] The present invention is intended to solve the above-mentioned problems, and another object is to provide a medication management system, a management server, and a control program for the management server that can reduce the burden on caregivers and others involved in managing medication for patients. [Means for solving the problem]

[0010] A medication management system according to one aspect of the present invention is a medication management system comprising a management server that manages medication, and an assistant terminal used by an assistant who assists in administering medication to an assisted person, the system comprising: a first acquisition means in the management server that acquires patient identification information, which is information that identifies the patient, and patient medication information, which is information that specifies medication prescribed to the patient, from a receipt computer that accepts input of information written on a prescription or an electronic prescription; a patient information storage means in the management server that associates the patient identification information and the patient medication information acquired by the first acquisition means with each other and stores them in a database; a second acquisition means in the assistant terminal that acquires identification information of a person being assisted, which is information that identifies the person being assisted, and administered medication information, which is information on medication to be administered to the person being assisted; medication determination means that determines whether medication is appropriate for the person being assisted, based on the patient identification information and patient medication information stored in the database and the assisted person identification information and administered medication information acquired by the second acquisition means; and a medication determination result display means that displays the result of the determination made by the medication determination means on the assistant terminal. When the type of drug prescribed to the patient is a first drug including patient medication information that is information regarding the timing of medication to the patient, the first acquisition means further acquires patient medication information that is information regarding the timing of medication to the patient from the receipt computer or the electronic prescription in the management server, and when the type of drug prescribed to the patient is a second drug that does not include patient medication information, the first acquisition means does not acquire patient medication information that is information regarding the timing of medication to the patient from the receipt computer or the electronic prescription in the management server, and the patient information storage means stores the patient medication information acquired by the first acquisition means in the database in the management server in association with the patient's identification information and the patient's drug information. The medication determination means includes a first medication determination means for determining whether a combination of the person being assisted and the medication to be administered is appropriate based on the patient's identification information and the patient's medication information stored in the database and the identification information of the person being assisted and the administered medication information acquired by the second acquisition means, when the type of medication prescribed to the patient is a first or second medication; and a second medication determination means for determining whether administration to the person being assisted is appropriate based further on the patient's medication information stored in the database and the timing of acquisition of the identification information of the person being assisted and the administered medication information, when the type of medication prescribed to the patient is a second medication. .

[0011] Preferably, the medication management system comprises: The system further includes an event receiving means for receiving an input of a drop, which is an event in which the medicine prescribed to the person being assisted is insufficient, or a skip, which is an event in which the medicine prescribed to the person being assisted is left over, and an event storage means for storing the event in a database in the management server when the event receiving means receives the input, in association with patient identification information, patient medicine information, and patient medication information regarding the person being assisted. .

[0012] In the above medication management system, preferably, the second acquisition means further acquires medication timing information which is information regarding the administration timing of a medication to be administered to the person being assisted, Second The medication determination means determines whether or not medication is appropriate for the person being assisted, further based on the medication timing information acquired by the second acquisition means.

[0013] Preferably, the above medication management system further comprises an information addition device, a third acquisition means in the information addition device for acquiring patient identification information, patient medication information, and patient medication information, and a code addition means in the information addition device for adding a code including the patient identification information, patient medication information, and patient medication information acquired by the third acquisition means to the medication packaged for the patient, and the second acquisition means includes a reading means for reading the code attached to the medication to be administered to the person being assisted.

[0014] Preferably, in the above medication management system, the information addition device further comprises packaging means for packaging the medicines in predetermined amounts.

[0015] Preferably, in the medication management system, Second The medication determination means further includes an identification information storage means in the management server that determines whether medication is appropriate for the assisted person and stores authorized person information, which is the identification information of a person who is authorized to use a specified function, in a database, and a fourth acquisition means in the management server that acquires the assistant's identification information, which is information that identifies the assistant, from the assistant terminal, and if the assistant's identification information acquired by the fourth acquisition means is not included in the authorized person information, the medication determination means does not make a determination.

[0016] Preferably, the above medication management system further comprises a medication completion receiving means at the attendant terminal for receiving a medication completion input indicating that medication to the assisted person has been completed, and a medication completion sending means at the attendant terminal for sending a notification of medication completion to the management server when the medication completion receiving means receives the input, and the management server further comprises a completion storage means for storing the fact of medication completion in a database in association with the patient identification information, the patient's drug information, and the patient's medication information regarding the assisted person when the notification of medication completion is received.

[0017] Preferably, the above medication management system further comprises contact information storing information for storing in a database the contact information of a manager who manages medication to patients, and a notification means in the management server for notifying the manager's contact information that medication to the patient has been forgotten if the fact that medication has been completed is not stored in the database after the time determined based on the patient's medication information has passed.

[0018] Preferably, the above medication management system further comprises a delivery terminal used by a delivery person who delivers medication to an assisted person, a delivery information receiving means in the delivery terminal that receives input of the identification information of the assisted person and delivery medication information, which is information about the medication to be delivered to the assisted person, a delivery determination means that determines whether the medication delivery location is correct based on the patient's identification information and patient's medication information stored in the database, and the identification information of the assisted person and delivery medication information received as input by the delivery information receiving means, and a delivery determination result display means that displays the result of the determination made by the delivery determination means on the delivery terminal.

[0019] A management server according to another aspect of the present invention is a management server that manages medication and is equipped with: a first acquisition means that acquires patient identification information, which is information that identifies the patient, and patient medication information, which is information that specifies the medication prescribed for the patient, from a receipt computer or an electronic prescription that accepts input of information written on a prescription; a patient information storage means that associates the patient identification information and the patient medication information acquired by the first acquisition means and stores them in a database; a second acquisition means that acquires, from an assistant terminal used by the assistant who assists the assisted person in administering medication to the assisted person, identification information of the assisted person, which is information that identifies the assisted person, and administered medication information, which is information on the medication to be administered to the assisted person; a medication determination means that determines whether medication is appropriate for the assisted person based on the patient identification information and patient medication information stored in the database and the assisted person identification information and administered medication information acquired by the second acquisition means; and a medication determination result display means that displays the result of the determination made by the medication determination means on the assistant terminal.

[0020] A control program of a management server according to yet another aspect of the present invention is a control program of a management server that manages medication, and causes a computer to execute: a first acquisition step of acquiring patient identification information, which is information that identifies a patient, and patient medication information, which is information that specifies medication prescribed for the patient, from a receipt computer that accepts input of information written on a prescription or an electronic prescription; a patient information storage step of storing the patient identification information and the patient medication information acquired in the first acquisition step in a database in association with each other; a second acquisition step of acquiring identification information of a person being assisted, which is information that identifies the person being assisted, and administered medication information, which is information on medication to be administered to the person being assisted, from an assistant terminal used by an assistant who assists the person being assisted with medication; a medication determination step of determining whether medication is appropriate for the person being assisted, based on the patient identification information and the patient medication information stored in the database and the identification information of the person being assisted and the administered medication information acquired in the second acquisition step; and a medication determination result display step of displaying the result of the determination in the medication determination step on the assistant terminal. and if the type of drug prescribed to the patient is a first drug including patient medication information that is information regarding the timing of medication to the patient, in a first acquisition step, the management server further acquires patient medication information that is information regarding the timing of medication to the patient from a receipt computer or an electronic prescription, and if the type of drug prescribed to the patient is a second drug that does not include patient medication information, in the first acquisition step, the management server does not acquire patient medication information that is information regarding the timing of medication to the patient from the receipt computer or the electronic prescription, and in a patient information storage step, the management server stores the patient medication information acquired by the first acquisition means in a database in association with patient identification information and patient medication information. The medication determination step includes a first medication determination step of determining whether the combination of the assisted person and the medication to be administered is appropriate based on the patient's identification information and the patient's medication information stored in the database and the assisted person's identification information and administered medication information acquired in the second acquisition step, when the type of medication prescribed to the patient is a first or second medication, and a second medication determination step of determining whether the medication to be administered to the assisted person is appropriate, when the type of medication prescribed to the patient is the first medication, further based on the patient's medication information stored in the database and the timing at which the assisted person's identification information and administered medication information were acquired, and when the type of medication prescribed to the patient is the second medication, the second medication determination step does not determine whether the medication to the assisted person is appropriate. [Effects of the Invention]

[0021] According to the present invention, it is possible to provide a medication management system, a management server, and a control program for the management server that can appropriately manage medication for patients, and also to provide a medication management system, a management server, and a control program for the management server that can reduce the burden on caregivers and others involved in managing medication for patients. [Brief explanation of the drawings]

[0022] [Figure 1] 1 is a conceptual diagram showing the configuration of a medication management system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram showing the configuration of a receipt computer 151, a management server 152, and a pharmacy terminal 153. FIG. [Figure 3] FIG. 2 is a block diagram showing the configuration of a packaging machine 251. [Figure 4]FIG. 3 is a block diagram showing the configuration of each of mobile terminals 351, 352, and 353. [Figure 5] 10 is a diagram schematically illustrating a patient information table 121 stored in a storage device 105 of a management server 152. FIG. [Figure 6] 10 is a diagram schematically illustrating an authorized person information table 122 stored in a storage device 105 of a management server 152. FIG. [Figure 7] 10 is a diagram schematically illustrating a prescription information table 123 stored in a storage device 105 of a management server 152. FIG. [Figure 8] 10 is a diagram schematically showing a medication schedule information table 124 stored in the storage device 105 of the management server 152. FIG. [Figure 9] FIG. 1 is a diagram illustrating the steps of preparing a prescribed drug PH in one embodiment of the present invention. [Figure 10] 10 is a flowchart illustrating operations performed by a medication management system when preparing a prescribed medication PH in one embodiment of the present invention. [Figure 11] FIG. 10 is a diagram illustrating an operation of delivering a medicine PH prepared at a pharmacy to a person being assisted CP in one embodiment of the present invention. [Figure 12] 10 is a flowchart illustrating operations performed by a medication management system when delivering medication PH prepared at a pharmacy to a person being assisted CP in one embodiment of the present invention. [Figure 13] 1A to 1C are diagrams illustrating the steps of administering medication to a person being assisted CP in one embodiment of the present invention. [Figure 14] 10 is a flowchart illustrating an operation performed by a medication management system when administering medication to a person being assisted CP in one embodiment of the present invention. [Figure 15] FIG. 1 is a diagram illustrating the operations for managing medication to a patient in one embodiment of the present invention. [Figure 16] 1 is a flowchart illustrating operations performed by a medication management system when managing medication for a patient in one embodiment of the present invention. [Figure 17]FIG. 10 is a diagram illustrating the work that the caregiver PN2 performs to register a dropped or skipped medication in the medication schedule information table 124 in one embodiment of the present invention. [Figure 18] 10 is a flowchart illustrating the operation of the medication management system when a caregiver PN2 registers a drop or skip in the medication schedule information table 124 in one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0023] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0024] [Configuration of medication management system]

[0025] FIG. 1 is a conceptual diagram showing the configuration of a medication management system according to an embodiment of the present invention.

[0026] 1, the medication management system in this embodiment is a system for managing medication, and includes a receipt computer (hereinafter sometimes referred to as receipt computer) 151, a management server 152, a pharmacy terminal 153, a packaging machine 251, and mobile terminals 351, 352, and 353. Receipt computer 151, management server 152, pharmacy terminal 153, packaging machine 251, and mobile terminals 351, 352, and 353 are each connected to one another via network 401 and communicate with one another.

[0027] The network 401 may be a wired or wireless LAN (Local Area Network) or WAN (Wide Area Network). The network 401 connects various devices using the TCP / IP (Transmission Control Protocol / Internet Protocol) protocol. The devices connected to the network 401 can exchange various types of data with each other.

[0028] Each of receipt computer 151, management server 152, pharmacy terminal 153, and packaging machine 251 is located, for example, within a pharmacy. Management server 152 may be installed anywhere, and may be located outside the pharmacy.

[0029] The receipt computer 151 accepts input of information written on a prescription. The receipt computer 151 creates a receipt (medical fee statement) based on the information written on the prescription. A receipt is a document used by a medical facility to claim medical fees from a payment institution such as a health insurance association.

[0030] The management server 152 manages medication administration.

[0031] The pharmacy terminal 153 is a terminal used by pharmacy staff for tasks such as creating a medication record.

[0032] The packaging machine 251 packages medicines in predetermined amounts and adds necessary information to the packaged medicines.

[0033] The mobile terminal 351 is a terminal used by a delivery person PN1 who delivers medicines to the person being assisted CP. In this example, the delivery person PN1 is a staff member of a pharmacy.

[0034] The mobile terminal 352 is a mobile terminal used by a caregiver PN2 who assists the person being assisted CP with administering medication. Here, the person being assisted CP is a resident of a nursing home, and the caregiver PN2 is a staff member of the nursing home. The person being assisted CP does not have to be a resident of the nursing home, and may be any person. The caregiver PN2 does not have to be a staff member of the nursing home, and may be any person. Alternatively, the person being assisted CP may be a patient hospitalized in a hospital, and the caregiver PN2 may be a person who assists the person being assisted CP in the hospital (such as a hospital staff member or a relative of the person being assisted).

[0035] The mobile terminal 353 is a mobile terminal used by a pharmacist PN3 who is a staff member of the pharmacy.

[0036] 2 is a block diagram showing the configuration of each of receipt computer 151, management server 152, and pharmacy terminal 153. Here, the configuration of receipt computer 151 will be described. Unless otherwise specified, it is assumed that each of management server 152 and pharmacy terminal 153 has the same configuration as receipt computer 151.

[0037] 2, receipt computer 151 is a computer and includes control unit 101, display unit 102, operation unit 103, network interface 104, and storage device 105. Control unit 101, display unit 102, operation unit 103, network interface 104, and storage device 105 are each connected to one another via a bus or the like.

[0038] The control unit 101 includes a CPU (Central Processing Unit) 111, a ROM (Read Only Memory) 112, and a RAM (Random Access Memory) 113. The CPU 111 controls the entire device. The CPU 111 executes a control program stored in the ROM 112.

[0039] The ROM 112 is, for example, a flash ROM. The ROM 112 stores various programs executed by the CPU 111 and various fixed data. The ROM 112 may be non-rewritable.

[0040] The RAM 113 is the main memory of the CPU 111. The RAM 113 is used to temporarily store data and the like required when the CPU 111 executes a control program.

[0041] The display unit 102 is made up of a monitor or the like and displays various information.

[0042] The operation unit 103 includes a keyboard, a mouse, and the like, and accepts various inputs.

[0043] The network interface 104 communicates with other devices according to instructions from the control unit 101 using a communication protocol such as TCP / IP.

[0044] The storage device 105 is, for example, a hard disk drive (HDD) or a solid state drive (SSD), and stores various data.

[0045] At least one of receipt computer 151, management server 152, and pharmacy terminal 153 may further include information addition unit 106. Information addition unit 106 adds necessary information to the medicine. As an example, information addition unit 106 generates a printed matter to which a code (such as a barcode or a QR (Quick Response) code (registered trademark)) including the necessary information has been added (printed).

[0046] In particular, as a configuration of management server 152 different from receipt computer 151 and pharmacy terminal 153, storage device 105 (an example of patient information storage means, identification information storage means, completion storage means, and contact information storage means) of management server 152 stores patient information table 121, authorizer information table (staff information table) 122, prescription information table (patient prescription set table) 123, and medication schedule information table (medication schedule and actual results management table) 124. Patient information table 121, authorizer information table 122, prescription information table 123, and medication schedule information table 124 are examples of databases, and may be stored in a storage device of a device external to management server 152. The above database stored in management server 152 or the like may be considered an original database, and at least a partial copy of the original database may be stored in other devices such as receipt computer 151, packing machine 251, or mobile terminals 351-353. In this case, a copy of at least a portion of the database stored in another device may be synchronized with the necessary portion of the original database stored in the management server 152 or the like at the necessary timing.

[0047] FIG. 3 is a block diagram showing the configuration of the packaging machine 251.

[0048] 3, packing machine 251 includes control unit 201, display unit 202, operation unit 203, network interface 204, storage device 205, packing unit 206, and information addition unit 207. Control unit 201 includes CPU 211, ROM 212, and RAM 213. The functions of control unit 201, display unit 202, operation unit 203, network interface 204, storage device 205, CPU 211, ROM 212, and RAM 213 are the same as the functions of control unit 101, display unit 102, operation unit 103, network interface 104, storage device 105, CPU 111, ROM 112, and RAM 113 in receipt computer 151, and therefore will not be described repeatedly.

[0049] Packaging section 206 receives input of medicines and packages the input medicines in predetermined amounts (for example, in single doses).

[0050] The information addition unit 207 adds necessary information to the medicine packaged by the packing unit 206. As an example, the information addition unit 207 adds (prints) a code (such as a barcode or a QR code (registered trademark)) including the necessary information.

[0051] 4 is a block diagram showing the configuration of each of mobile terminals 351, 352, and 353. Here, the configuration of mobile terminal 351 will be described. Unless otherwise specified, each of mobile terminals 352 and 353 has the same configuration as mobile terminal 351.

[0052] 4, mobile terminal 351 includes control unit 301, display unit 302, operation unit 303, network interface 304, storage device 305, and image reading unit 306. Control unit 301 includes CPU 311, ROM 312, and RAM 313. The functions of control unit 301, display unit 302, operation unit 303, network interface 304, storage device 305, CPU 311, ROM 312, and RAM 313 are the same as the functions of control unit 101, display unit 102, operation unit 103, network interface 104, storage device 105, CPU 111, ROM 112, and RAM 113 in receipt computer 151, and therefore will not be described repeatedly.

[0053] The storage device 305 stores an application (hereinafter, sometimes referred to as an app) 321. The app 321 is an application program for performing various processes of the medication management system.

[0054] The image reader 306 reads the code and extracts various pieces of information from the code.

[0055] FIG. 5 is a diagram schematically illustrating the patient information table 121 stored in the storage device 105 of the management server 152. As shown in FIG.

[0056] 5, the patient information table 121 is a table that lists information 1211 of patients whose medication is managed by the management server 152. The patient information 1211 is information about one patient, and includes a patient ID (Identification), the patient's name, the patient's physical information (gender, height, weight, age, date of birth, etc.), and the name of the nursing care facility where the patient resides. The nursing care facility where the patient resides is the delivery destination of medications prescribed for that patient.

[0057] Registration, modification, and deletion of patient information 1211 are performed by pharmacy staff, pharmacists, etc. via operation unit 103 of management server 152, etc.

[0058] FIG. 6 is a diagram showing a schematic diagram of the authorized person information table 122 stored in the storage device 105 of the management server 152. As shown in FIG.

[0059] 6, the authorized person information table 122 is a table listing authorized person information 1221, which is identification information of persons (authorizers) who are authorized to use predetermined functions of the medication management system. Authorizers include pharmacists at the pharmacy, pharmacy staff, and caregivers (staff at nursing facilities). The authorized person information 1221 is information about one authorized person, and includes the authorized person's ID, the authorized person's name, the authorized person's identity, and the authorized person's contact information (such as a telephone number, an email address, and the app ID of an app 321 installed on the authorized person's mobile terminal). The authorized person information 121 may further include information about the authority that the authorized person is authorized to have in the medication management system (for example, the authority to register, change, or delete prescription information, which will be described later, and the authority to view various information).

[0060] The registration, modification, and deletion of the authorized person information 1221 are performed by a pharmacy staff member, a pharmacist, or the like via the operation unit 103 of the management server 152 or the like.

[0061] FIG. 7 is a diagram schematically illustrating the prescription information table 123 stored in the storage device 105 of the management server 152. As shown in FIG.

[0062] 7, prescription information table 123 is a table that lists prescription information 1231, which is information about drugs prescribed to patients. Prescription information 1231 is created for each patient. Prescription information 1231 includes a patient ID, a patient name, the name of the nursing facility where the patient resides, the name of the pharmacy that prepared the drugs, the date on which input of the information written on the patient's prescription was accepted, the date on which delivery of the drugs to the patient was completed, detailed information about the drugs prescribed to the patient, and the like. The detailed information about the drugs prescribed to the patient includes the drug name, ingredients and efficacy, directions for use, the date of administration (the date on which the drugs are administered), the number of packets, and remarks.

[0063] Generally, for oral medications, the dosage instructions specify the specific timing of administration during the day. On the other hand, for topical medications such as ointments and eye drops, the dosage instructions specify the number of times per day they should be administered, but not the specific timing of administration during the day. Therefore, medications prescribed to patients include those for which the timing of administration to the patient is specified (sometimes referred to herein as "first medications"), such as oral medications, and those for which the timing of administration to the patient is not specified (sometimes referred to herein as "second medications"). The dosage instructions for the first medication include patient administration information (an example of patient administration information), which is information regarding the timing of administration to the patient, while the dosage instructions for the second medication do not include the patient administration information. The patient administration information is information regarding the timing of administration of the medication, such as the time period for administration (e.g., before dinner, after each meal, or before bedtime) or the time interval for administration (e.g., every four hours). The directions for use may further include information such as the site of administration and the dosage.

[0064] The prescription information 1231 in the prescription information table 123 is registered, changed, and deleted by the management server 152 or a person authorized in the authorizer information 121 in the authorizer information table 122 (such as a pharmacist) at the necessary timing.

[0065] FIG. 8 is a diagram schematically showing the medication schedule information table 124 stored in the storage device 105 of the management server 152.

[0066] Referring to FIG. 8, the medication schedule information table 124 is a table listing medication schedule information 1241, which is information on a schedule for administering medication to a patient. The medication schedule information 1241 is created for each patient. The medication schedule information 1241 includes the patient's name, the name and contact information of the caregiver assisting the patient with medication, the name and contact information of the manager managing the patient's medication, the name of the medication to be administered on each scheduled medication date, the medication timing, the date and time of completion of medication, and a remarks column. In this example, the manager is pharmacist PN3 of the pharmacy who prepared the medication prescribed for the patient. The medication schedule information 1241 for the first medication (the medications designated "PH1," "PH2," and "PH3" in FIG. 8) may further include information on the medication timing. The medication schedule information 1241 for the second medication (the medication designated "PH4" in FIG. 8) does not need to include information on the medication timing.

[0067] In the remarks column, dropped medication or skipped medication is entered by the caregiver PN2 or other person at the appropriate time. Dropped medication means that the medication was discarded without being used because it was dropped or for other reasons. Skipped medication means that the medication was forgotten to be used or that the CP being assisted was in poor health, leaving the medication unused. Each time a dropped medication occurs, one medication is missing, and each time a skip occurs, one medication is left over. The entries of dropped medication or skipped medication in the remarks column may be used by the pharmacist PN1 as a reference for dispensing medication.

[0068] [Preparing prescribed medications]

[0069] FIG. 9 is a diagram illustrating the steps of preparing a prescribed drug PH in one embodiment of the present invention.

[0070] 9, the prescribed drug PH for the patient is prepared at the pharmacy by the pharmacist PN3. The flow of this preparation will be described below.

[0071] In this specification, the person to whom a prescription is given a drug is referred to as a patient, and the person to whom the drug is actually administered is referred to as a person receiving care. If the drug is administered to a patient appropriately, the patient and the person receiving care are the same person.

[0072] When pharmacist PN3 obtains the prescription issued by the doctor, he / she inputs prescription information IN1, which is the information written on the prescription, into receipt computer 151. Receipt computer 151 accepts the input of prescription information IN1 through operation unit 103 (an example of prescription receiving means) of receipt computer 151 (operation PR11). Prescription information IN1 includes patient identification information (an example of patient identification information), patient drug information (an example of patient drug information), etc. If the prescribed drug PH includes a first drug, prescription information IN1 further includes patient medication information regarding that drug.

[0073] The patient identification information is information for identifying the patient, and includes, for example, a patient ID, a patient name, and physical information of the patient (sex, height, weight, age, date of birth, etc.).

[0074] The patient's medication information is information that identifies the medication prescribed to the patient, and includes, for example, the name, ingredients, and effects of the medication prescribed to the patient (medication name).

[0075] When pharmacist PN3 obtains the prescription issued by the doctor, he / she inputs additional information IN2 into each of management server 152 and packing machine 251. Each of management server 152 and packing machine 251 accepts the input of additional information IN2 (operation PR12). Pharmacist PN3 measures the necessary medication, inserts the measured medication into packing machine 251, and starts the operation of packing machine 251 (operation PR13).

[0076] The additional information IN2 includes information necessary for creating the database. Specifically, the additional information IN2 includes the medication administration date and number of packets, information about the person assisting the patient in administering the medication, information about the person in charge of administering the medication to the patient, and the name of the nursing facility where the patient resides. The medication administration date and number of packets are determined based on the prescription, etc. The pharmacist PN3 may view the patient's medication schedule information 1241 (FIG. 8) and medication record SH2, etc., and increase or decrease the number of packets in the additional information IN2, taking into account any past missed or skipped doses.

[0077] At least some of the above-mentioned tasks performed by the pharmacist PN3 may be performed by a pharmacy staff member other than the pharmacist PN3.

[0078] When the receipt computer 151 accepts the input of prescription information IN1, it creates a receipt SH1 based on the prescription information IN1 (operation PR14). The receipt computer 151 uses the network interface 104 of the receipt computer 151 to transmit the input prescription information IN1 to each of the management server 152 and the packing machine 251. Each of the management server 152 and the packing machine 251 receives (acquires) the prescription information IN1 using the network interface 104 (an example of a first acquisition means and a third acquisition means) (operation PR15).

[0079] In process PR15, the management server 152 or the packing machine 152 may indirectly acquire the prescription information IN1 from the receipt computer 151. For example, the receipt computer 151 may generate a code (for example, a two-dimensional barcode such as a QR code (registered trademark)) including the input prescription information IN1, and the management server 152 or the packing machine 251 may acquire the prescription information IN1 by reading the code using a camera (not shown) mounted on the machine itself.

[0080] The packing machine 251 receives prescription information IN1 from the receipt computer 151 or the like, accepts input of additional information IN2 from the pharmacist PN3, and accepts an operation to start the operation. Then, using the packing unit 206 (an example of a packing means), the packing machine 251 packs the medicines into predetermined amounts. The packing machine 251 then uses the information addition unit 207 (an example of a code addition means) to add (print) a code CD1, such as a two-dimensional barcode, to the packaged medicines PH (operation PR16). The code CD1 includes patient identification information, the patient's medicine information, the patient's medication information, and the patient's medication information. The code CD1 may further include information such as the medication date and the number of packets. It is preferable that, together with the code CD1, characters including the patient's identification information, the patient's medicine information, the patient's medication information, and the patient's medication information are added to the medicine packaging.

[0081] Generally, the second medicine, etc., is not packaged by the packing machine 251, but is manually placed in a medicine bag (such as a polyethylene bag with a zipper) by the pharmacist PN3. For this reason, when the medicine is the second type of medicine, it is often difficult to add the code CD1 to the medicine packaging as described above. If it is difficult to add the code CD1 to the medicine packaging, the receipt computer 151, management server 152, or pharmacy terminal 153 may add information to the medicine by creating a printout of the code CD1, such as a two-dimensional barcode, using the information addition unit 106 (an example of a code addition means). In this case, the pharmacist PN1 may place the printout with the code CD1 in the medicine bag together with the medicine, or may attach the printout to the surface of the medicine bag.

[0082] When the management server 152 accepts input of additional information IN2 from the pharmacist PN3 and receives prescription information IN1 from the receipt computer 151, the control unit 101 creates prescription information 1231 based on the prescription information IN1 and additional information IN2, and stores the created prescription information 1231 in the prescription information table 123 (operation PR17). However, in operation PR17, the delivery completion date column in the prescription information 1231 is left blank. In the prescription information 1231, the patient's identification information, the patient's medication information, and the patient's medication information are associated with each other. If the medication type is a second medication, the processing information 1231 may not include the patient's medication information, and the patient's identification information and the patient's medication information may be associated with each other.

[0083] The management server 152 creates medication schedule information 1241 using the control unit 101 of the management server 152 based on the prescription information IN1 and the additional information IN2, and adds the created medication schedule information 1241 to the medication schedule information table 124 (operation PR18). However, in operation PR18, the column for medication completion date and time in the medication schedule information 1241 is left blank.

[0084] Furthermore, if the patient information 1211 included in the prescription information IN1 does not exist in the patient information table, the management server 152 creates patient information 1211 using the control unit 101 of the management server 152 based on the prescription information IN1 and the additional information IN2, and registers the created patient information 1211 in the patient information table 121 (operation PR19).

[0085] The prescribed medicine is prepared through the above process. Next, delivery preparations are made by the delivery person PN1 as follows:

[0086] The deliverer PN1 requests the management server 152 to send prescription information IN1 and additional information IN2 via the pharmacy terminal 153 (task PR20). The management server 152 sends the prescription information IN1 and additional information IN2 to the pharmacy terminal 153 in response to the request (task PR21). The pharmacy terminal 153 creates a medication record SH2 based on the received prescription information IN1 and additional information IN2 (task PR22). The deliverer PN1 then takes the packaged medication PH collected from the pharmacy and the medication record SH2 and heads to the nursing care facility where the person being assisted CP resides to make the delivery (task PR23).

[0087] The medication record SH2 contains information for confirming medication. The medication record SH2 includes patient identification information, medication information for the medication, the administration date, the number of packets, etc. If the medication type is a first medication, the medication record SH2 may further include medication information for the patient. The medication record SH2 may also include information on dropped and skipped medications included in the patient's medication information 1241 (FIG. 8). The medication record SH2 may be printed on paper, or may be data stored in the mobile terminal 351 used by the delivery person PN1. Furthermore, as will be described later, the medication record SH2 may be used by the delivery person PN1 to confirm whether the medication to be delivered is correct.

[0088] The receipt computer 151 may store the input prescription information IN1 in a storage device of an external device (a device external to the medication management system). The management server 152 and the packing machine 251 may each acquire (receive) the prescription information IN1 from the storage device of the external device at an appropriate timing. The prescription information IN1 may be automatically transmitted to the management server 152 or the packing machine 251 (without a request from the management server 152 or the packing machine 251).

[0089] Furthermore, instead of acquiring the prescription information 1231 from the prescription information IN1 of the receipt computer 151 as described above, the management server 152 may acquire the prescription information 1231 from an electronic prescription. The electronic prescription from which the prescription information 1231 is acquired may be stored in any location accessible to the management server 152. As an example, the electronic prescription may be stored in the receipt computer 151, may be stored in a patient's mobile terminal (not shown) that can communicate with the management server 152, or may be stored in a server (not shown) of an electronic prescription management service that can communicate with the management server 152. When the prescription information 1231 is acquired from an electronic prescription, errors in the prescription information 1231 due to input errors in the prescription information IN1 can be prevented compared to when the prescription information 1231 is acquired from the receipt computer 151.

[0090] Furthermore, at any timing after management server 152 acquires prescription information IN1 and additional information IN2, management server 152 may create medication record SH2 instead of pharmacy terminal 153 and store it in storage device 105 or the like of management server 152. In this case, pharmacy terminal 153 may acquire medication record SH2 from management server 152 or the like.

[0091] 10 is a flowchart illustrating the operations performed by the medication management system when preparing a prescribed medication PH in one embodiment of the present invention. This flowchart is realized by the CPU executing a control program stored in the ROM.

[0092] 10, the receipt computer 151 receives input of prescription information IN1 (S101). Next, the receipt computer 151 transmits the prescription information IN1 to each of the management server 152 and the packing machine 251 (S103), and creates a prescription based on the prescription information IN1 (S105).

[0093] The management server 152 receives prescription information IN1 from the receipt computer 151 (S107) and accepts input of additional information IN2 (S109). The management server 152 creates patient information 1211, prescription information 1231, and medication schedule information 1241 based on the prescription information IN1 and the additional information IN2, and adds them to the patient information table 121, prescription information table 123, and medication schedule information table 124, respectively (S111).

[0094] The packing machine 251 receives prescription information IN1 from the receipt computer 151 (S113) and accepts input of additional information IN2 (S115). When the packing machine 251 accepts an operation to start the operation (S117), it packs the medicine (S119) and adds a code CD1 to the medicine package (S121).

[0095] When pharmacy terminal 153 receives a predetermined input, it requests management server 152 to transmit prescription information IN1 and additional information IN2 (S151). Management server 152 transmits prescription information IN1 and additional information IN2 to pharmacy terminal 153 in response to the request (S153). Pharmacy terminal 153 receives prescription information IN1 and additional information IN2 (S155) and creates medication log SH2 based on the received prescription information IN1 and additional information IN2 (S157).

[0096] [Prescribed medication delivery]

[0097] FIG. 11 is a diagram illustrating an operation of delivering a medicine PH prepared at a pharmacy to a person being assisted CP in one embodiment of the present invention.

[0098] 11, the medication PH prepared at the pharmacy is delivered to the person being assisted CP by a delivery person PN1. The flow of this delivery will be described below. The delivery person PN1 may be any person other than a pharmacy employee.

[0099] When the delivery person PN1 arrives at the nursing care facility where the medicines are to be delivered, the delivery person PN1 starts up the app 321 on the mobile terminal 351 and inputs the identification information of the delivery person PN1, which is information that identifies the delivery person PN1, into the mobile terminal 351. The mobile terminal 351 accepts the input of the identification information of the delivery person PN1 via the operation unit 303 of the mobile terminal 351 or the like (operation PR31). The input identification information may be information that identifies the delivery person PN1, and may be the ID and name of the delivery person PN1, for example.

[0100] In this example, a code CD2 containing information about the ID and name of the deliverer PN1 is attached to a nameplate NP1 or the like held by the deliverer PN1. The mobile terminal 351 reads this code CD2 to accept input of the identification information of the deliverer PN1, which is information that identifies the deliverer PN1. The method for inputting the identification information of the deliverer PN1 is arbitrary. Instead of reading the code CD2, the mobile terminal 351 may accept manual input of the identification information of the deliverer PN1, or may read out the identification information of the deliverer PN1 registered in the app 321 of the mobile terminal 351.

[0101] The mobile terminal 351 transmits the input identification information of the deliverer PN1 to the management server 152. The management server 152 receives the identification information of the deliverer PN1 through the network interface 104 of the management server 152 (operation PR32).

[0102] When the management server 152 receives the identification information of the deliverer PN1, it performs authentication work for the deliverer PN1 (work PR33). The management server 152 determines whether the authorized party information 1221 corresponding to the identification information of the deliverer PN1 is registered in the authorized party information table 122. The management server 152 transmits the determination result to the mobile terminal 351 (work PR34).

[0103] If the management server 152 determines that the authorized person information 1221 (authorized person ID and authorized person name) that matches the identification information of the deliverer PN1 (the ID and name of the deliverer PN1) is registered in the authorized person information table 122, it authenticates the deliverer PN1 and determines whether the delivery location of the medicine PH, which will be described later, is correct. If the management server 152 determines that the authorized person information 1221 that matches the identification information of the deliverer PN1 is not registered in the authorized person information table 122, it does not authenticate the deliverer PN1 and does not determine whether the delivery location of the medicine PH is correct.

[0104] If authenticated, the delivery person PN1 confirms that the delivery location of the drug PH is correct by visually checking the characters written in the medication record SH2, the characters added to the packaging of the drug PH, and the characters displayed on the location where the drug is to be placed for the assisted person CP (such as a medication cart). Next, the delivery person PN1 inputs the identification information of the assisted person CP (an example of identification information for a person receiving care), which is information that identifies the assisted person CP, and the drug delivery information into the mobile terminal 351. The mobile terminal 351 accepts the input of the identification information of the assisted person CP and the drug delivery information (operation PR35).

[0105] The delivery drug information is information about the drug PH to be delivered to the person being assisted CP.

[0106] Here, a code CD3 including identification information of the person being assisted CP, which is information that identifies the person being assisted CP, is displayed at the location where the medication for the person being assisted CP is placed. The portable terminal 351 reads this code CD3 to accept input of the identification information of the person being assisted CP. The portable terminal 351 also reads the code CD1 displayed on the packaging of the medication PH that the person brought with them accepts input of delivery medication information.

[0107] The mobile terminal 351 transmits the input identification information of the person being assisted CP and the medication delivery information to the management server 152. The management server 152 receives (acquires) the identification information of the person being assisted CP and the medication delivery information (operation PR36).

[0108] When the management server 152 receives the identification information of the assisted person CP and the drug delivery information, the control unit 101 (an example of a delivery determination means) of the management server 152 determines whether the delivery location of the drug PH is correct (operation PR37). This determination is made based on the patient identification information and the patient's drug information stored in the prescription information table 123 and the received identification information of the assisted person CP and drug delivery information. Specifically, this determination is made based on whether prescription information 1231 including the patient identification information and drug information of the patient that match the received identification information and drug delivery information of the assisted person CP is registered in the prescription information table 123.

[0109] If prescription information 1231 including patient identification information and patient medication information that match the received identification information of the assisted person CP and delivery medication information is registered in the prescription information table 123, the management server 152 determines that the delivery location of the medication PH is correct. If prescription information 1231 including patient identification information and patient medication information that match the received identification information of the assisted person CP and delivery medication information is not registered in the prescription information table 123, the management server 152 determines that the delivery location of the medication PH is incorrect.

[0110] Management server 152 transmits the determination result to mobile terminal 351 via network interface 104 (an example of a delivery determination result display means) of management server 152, and displays it on mobile terminal 351 (operation PR38).

[0111] When the delivery person PN1 confirms on the portable terminal 351 that the medicine delivery location is correct, the delivery person PN1 delivers the medicine PH to the medicine placement location for the assisted person CP and inputs delivery completion into the portable terminal 351. Upon receiving the input of delivery completion, the portable terminal 351 notifies the management server 152 of the delivery completion (operation PR39).

[0112] When the management server 152 receives a delivery completion notification from the mobile terminal 351, it records the completion of delivery of the medicine related to the prescription information by entering the date in the delivery completion date field of the related prescription information 1231 in the prescription information table 123 (task PR40). In task PR40, it is sufficient that at least the fact that delivery has been completed is recorded in the prescription information 1231.

[0113] The mobile terminal 351 may acquire in advance a copy of at least a portion of the original database stored in the management server 152 or the like and store it in the storage device 305 of the mobile terminal 351. In this case, the mobile terminal 351 may determine by itself whether the delivery location of the drug PH is correct, without transmitting the input identification information of the person being assisted CP and drug delivery information to the management server 152. This determination may be made based on the patient identification information and drug information of the patient stored in the storage device 305 of the mobile terminal 351, and the input identification information of the person being assisted CP and drug delivery information. According to this determination method, it is possible to determine whether the delivery location of the drug PH is correct even when the mobile terminal 351 is in a state where communication is not possible (offline state).

[0114] 12 is a flowchart illustrating the operations performed by the medication management system when delivering a medication PH prepared at a pharmacy to a person being assisted CP in one embodiment of the present invention. This flowchart is realized by the CPU executing a control program stored in the ROM.

[0115] Referring to FIG. 12, when the mobile terminal 351 of the deliverer PN1 receives input of the identification information of the deliverer PN1 (S301), the mobile terminal 351 transmits the input identification information to the management server 152 (S303).

[0116] When the management server 152 receives the identification information of the deliverer PN1, it authenticates the deliverer PN1 based on the received identification information of the deliverer PN1 and the authorized party information table 122 (S305), and transmits the authentication result to the mobile terminal 351 (S307).

[0117] If the mobile terminal 351 receives an authentication result indicating successful authentication, it accepts input of the identification information and delivery drug information of the assisted person CP (S309) and transmits the identification information and delivery drug information of the assisted person CP to the management server 152 (S311).

[0118] When the management server 152 receives the identification information of the assisted person CP and the drug delivery information, it determines whether the delivery location of the drug PH is correct based on the patient's identification information and the patient's drug information stored in the prescription information table 123 and the received identification information of the assisted person CP and the drug delivery information (S313), and sends the determination result to the mobile terminal 351 (S315).

[0119] When the portable terminal 351 receives the determination result, it displays the determination result on the display unit 302 of the portable terminal 351 (S317). After that, when the portable terminal 351 receives an input of delivery completion (S319), it transmits a delivery completion notification to the management server 152 (S321).

[0120] When the management server 152 receives the notification of delivery completion, it records the delivery completion in the prescription information 1231 of the assisted person CP in the prescription information table 123 (S323).

[0121] [dosage]

[0122] FIG. 13 is a diagram illustrating the procedure for administering medication to the person being assisted CP in one embodiment of the present invention.

[0123] 13, the delivered medication PH is administered to the assisted person CP at the required timing. The administration of the medication PH to the assisted person CP is assisted by the caregiver PN2. The administration flow will be described below.

[0124] The caregiver PN2 starts up the app 321 on the mobile terminal 352 and inputs the identification information of the caregiver PN2, which is information that identifies the caregiver PN2, into the mobile terminal 352. The mobile terminal 352 accepts the input of the identification information of the caregiver PN2 (operation PR51). The input identification information may be any information that identifies the caregiver PN2, and may be the ID and name of the caregiver PN2, for example.

[0125] In this example, a code CD4 containing information about the ID and name of the caregiver PN2 is attached to a nameplate NP2 or the like carried by the caregiver PN2. The mobile terminal 352 reads this code CD4 to accept input of the identification information of the caregiver PN2. The method of inputting the identification information of the caregiver PN2 is arbitrary. Instead of reading the code CD4, the mobile terminal 352 may accept manual input of the identification information of the caregiver PN2, or may read out the identification information of the caregiver PN2 registered in the app 321 of the mobile terminal 352.

[0126] The mobile terminal 352 transmits the input identification information of the assistant PN2 to the management server 152. The management server 152 receives (acquires) the identification information of the assistant PN2 through the network interface 104 (an example of a fourth acquisition means) of the management server 152 (operation PR52).

[0127] When the management server 152 receives the identification information of the caregiver PN2, it performs authentication work for the caregiver PN2 (work PR53). The management server 152 determines whether or not authorized person information 1221 corresponding to the identification information of the caregiver PN2 is registered in the authorized person information table 122. The management server 152 transmits the determination result to the mobile terminal 352 (work PR54).

[0128] If the management server 152 determines that the authorized person information 1221 (authorized person ID and authorized person name) that matches the identification information of the caregiver PN2 (the ID and name of the caregiver PN2) is registered in the authorized person information table 122, it authenticates the caregiver PN2 and determines whether or not it is appropriate to administer the drug PH to the assisted person CP (this determination will be described later).If the management server 152 determines that the authorized person information 1221 that matches the identification information of the caregiver PN2 is not registered in the authorized person information table 122, it does not authenticate the caregiver PN2 and does not determine whether or not it is appropriate to administer the drug PH to the assisted person CP.

[0129] If authenticated, the caregiver PN2 visually checks the name of the assisted person CP and the characters attached to the packaging of the medication PH to be administered to the assisted person CP to confirm that the medication to be administered to the assisted person CP is correct, and further confirms that the timing of administering the first medication to the assisted person CP is correct. Next, the caregiver PN2 inputs the identification information of the assisted person CP and the medication information into the mobile terminal 352. The mobile terminal 352 acquires the identification information of the assisted person CP and the medication information via the operation unit 303 (an example of a second acquisition means) of the mobile terminal 352 or the like (operation PR55).

[0130] The administration drug information is information about the drug PH to be administered to the person being assisted CP.

[0131] Here, the person being assisted CP is wearing a wristband WB. A code CD5 containing identification information of the person being assisted CP is displayed on the wristband WB. It is preferable that characters containing the name and physical information of the person being assisted CP are added to the wristband WB along with the code CD5. Instead of being displayed on the wristband WB, the code CD5 may be displayed on the serving tray used by the person being assisted CP or on the seat of the person being assisted when eating. The portable terminal 352 acquires the identification information of the person being assisted CP by reading this code CD5 using the image reading unit 306 of the portable terminal 352. Furthermore, the portable terminal 352 acquires administration drug information by reading the code CD1 displayed on the drug PH to be administered to the person being assisted CP using the image reading unit 306 of the portable terminal 352 (an example of a reading means).

[0132] The mobile terminal 352 transmits the acquired identification information of the assisted person CP and the administered medication information to the management server 152. The management server 152 receives the identification information of the assisted person CP and the administered medication information via the network interface 104 of the management server 152 (operation PR56).

[0133] When the management server 152 receives the identification information and the administered drug information of the assisted person CP, the control unit 101 (an example of a medication determination means) of the management server 152 determines whether or not it is appropriate to administer the drug PH to the assisted person CP (operation PR57). This determination is made based on the patient's identification information and the patient's drug information stored in the prescription information table 123, and the identification information and administered drug information of the assisted person CP acquired by the mobile terminal 352. If the type of drug is a first drug, this determination is further made based on the patient's medication information stored in the processing table 123 and the timing at which the mobile terminal 352 acquired the identification information and administered drug information of the assisted person CP. The timing at which the identification information and administered drug information of the assisted person CP are acquired may be the timing at which the management server 152 receives the identification information and administered drug information of the assisted person CP, or the timing at which the mobile terminal 352 acquires the identification information and administered drug information of the assisted person CP.

[0134] When the type of drug is a first drug, the determination of whether or not the administration of the drug PH to the assisted person CP is appropriate involves determining whether or not the combination of the assisted person CP and the drug PH is appropriate (first determination) and whether or not the timing of administration of the drug PH is appropriate (second determination). When the type of drug is a second drug, the second determination is omitted and only the first determination is made. Furthermore, regardless of the type of drug, the second determination may be omitted and only the first determination may be made.

[0135] In the first determination, it is determined whether prescription information 1231 including the patient's identification information and the patient's drug information that match the identification information and delivery drug information of the assisted person CP obtained by the mobile terminal 352 is registered in the prescription information table 123.

[0136] In the first judgment, if it is determined that prescription information 1231 including the patient's identification information and the patient's drug information that match the identification information and delivery drug information of the assisted person CP acquired by the mobile terminal 352 is registered in the prescription information table 123, and if the drug indicated in the patient's drug information is the first drug, the management server 152 makes a second judgment.

[0137] In the second determination, the patient's medication schedule information 1241 stored in the prescription information table 123 is identified based on the identification information of the assisted person CP acquired by the mobile terminal 352. A time range in which medication can be administered is determined based on the medication timing included in the identified medication schedule information 1241. Then, it is determined whether the timing (date and time) at which the identification information of the assisted person CP and the administered drug information were acquired is within the time range in which medication can be administered.

[0138] As an example, if the timing of medication included in the patient's medication information is before breakfast or after breakfast, 6:00 to 10:00 is determined as the time range in which medication can be administered. If the timing of medication included in the patient's medication information is before lunch or after lunch, 11:00 to 14:00 is determined as the time range in which medication can be administered. If the timing of medication included in the patient's medication information is before dinner or after dinner, 17:00 to 21:00 is determined as the time range in which medication can be administered. If the timing of medication included in the patient's medication information is before going to bed, 21:00 to 24:00 is determined as the time range in which medication can be administered. If the timing of medication included in the patient's medication information is every six hours, a time range of 5 to 7 hours converted from the latest medication completion date and time included in the medication schedule information 1241 is determined as the time range in which medication can be administered.

[0139] In the second judgment, if it is determined that the timing at which the identification information and administered drug information of the assisted person CP were acquired is within the time range in which medication can be administered, the management server 152 determines that it is appropriate to administer the drug PH to the assisted person CP.

[0140] On the other hand, in the first judgment, if it is determined that prescription information 1231 including the patient's identification information and the patient's drug information that match the identification information and delivery drug information of the assisted person CP acquired by the mobile terminal 352 is registered in the prescription information table 123, and the drug indicated in the patient's drug information is the second drug, the management server 152 determines that it is appropriate to administer the drug PH to the assisted person CP.

[0141] If, in the first judgment, it is determined that prescription information 1231 including the patient's identification information and the patient's drug information that match the acquired identification information and delivery drug information of the assisted person CP is not registered in the prescription information table 123, or if, in the second judgment, it is determined that the timing at which the assisted person CP's identification information and administered drug information were acquired is outside the time range in which medication can be administered, it is determined that administration of the drug PH to the assisted person CP is inappropriate.

[0142] In operation PR55, the mobile terminal 352 may further receive input of administration timing information in addition to input of the identification information and administered drug information of the assisted person CP. In operation PR56, the management server 152 may further receive administration timing information from the mobile terminal 352 in addition to input of the identification information and administered drug information of the assisted person CP. In operation PR57, the management server 152 may determine whether or not medication is appropriate for the assisted person CP based further on the medication timing information acquired by the mobile terminal 352. In this case, the first determination is made as to whether or not prescription information 1231 including each of the patient identification information, the patient's drug information, and the patient's medication information that match each of the identification information, delivery drug information, and administration timing information of the assisted person CP acquired by the mobile terminal 352 is registered in the prescription information table 123.

[0143] The administration timing information is information regarding the administration timing of a drug to be administered to the person being assisted CP.

[0144] Management server 152 uses network interface 104 (an example of a medication determination result display means) of management server 152 to transmit the determination result to mobile terminal 352 and display it on mobile terminal 352 (operation PR58).

[0145] When the caregiver PN2 confirms on the portable terminal 352 the determination result that administration of the drug PH to the assisted person CP is appropriate, the caregiver PN2 administers the drug PH to the assisted person CP and inputs administration completion for the drug PH into the portable terminal 352. The portable terminal 352 accepts the input of administration completion for the drug PH through the operation unit 303 (an example of administration completion receiving means) of the portable terminal 352 (operation PR59). Upon accepting the input of administration completion for the drug PH, the portable terminal 352 transmits a notification of administration completion for the drug PH to the management server 152 through the network interface 304 (an example of administration completion sending means) of the portable terminal 352 (operation PR60). The management server 152 receives the notification of administration completion for the drug PH.

[0146] When the management server 152 receives a notification of completion of administration of the drug PH from the mobile terminal 352, the management server 152 associates the date and time when the notification of completion of administration of the drug PH was received with the patient identification information, the patient's drug information, and the patient's medication information (patient's medication information exists only when the drug is the first drug) of the assisted person CP, and stores the date and time when the notification of completion of administration of the drug PH was received in a database stored in the storage device 105 (completion storage means) of the management server 152. The management server 152 records the completion of administration by entering the date and time when the notification of completion of administration was received in the medication completion date and time column for the drug PH in the medication schedule information 1241 of the assisted person CP in the medication schedule information table 124 (operation PR61). In operation PR61, it is sufficient that at least the fact that administration is completed is recorded in the medication schedule information 1241.

[0147] The mobile terminal 352 may acquire in advance a copy of at least a portion of the original database stored in the management server 152 or the like and store it in the storage device 305 of the mobile terminal 352. In this case, the mobile terminal 352 may determine by itself whether or not it is appropriate to administer the drug PH to the assisted person CP, without transmitting the input identification information and delivery drug information of the assisted person CP to the management server 152. This determination may be made based on the patient identification information and patient drug information stored in the storage device 305 of the mobile terminal 352, and the identification information and administered drug information of the assisted person CP input by the mobile terminal 352. If the drug is a first drug, this determination may further be made based on the patient's medication information stored in the storage device 305 of the mobile terminal 352 and the timing at which the identification information and administered drug information of the assisted person CP were acquired. This determination method allows the mobile terminal 352 to determine whether or not it is appropriate to administer the drug PH to the assisted person CP even when the mobile terminal 352 is in a state where communication is unavailable (offline state).

[0148] 14 is a flowchart illustrating the operations performed by the medication management system when administering medication to a person being assisted CP in one embodiment of the present invention. This flowchart is realized by the CPU executing a control program stored in the ROM.

[0149] Referring to FIG. 14, when the portable terminal 352 of the caregiver PN2 receives input of the identification information of the caregiver PN2 (S501), the portable terminal 352 transmits the input identification information to the management server 152 (S503).

[0150] When the management server 152 receives the identification information of the caregiver PN2, it authenticates the caregiver PN2 based on the received identification information of the caregiver PN2 and the authorized person information table 122 (S505), and transmits the authentication result to the mobile terminal 352 (S507).

[0151] If the portable terminal 352 receives an authentication result indicating successful authentication, it accepts input of the identification information and medication information of the assisted person CP (S509) and transmits the identification information and medication information of the assisted person CP to the management server 152 (S511).

[0152] When the management server 152 receives the identification information and administered drug information of the assisted person CP, it determines whether it is appropriate to administer the drug PH to the assisted person CP based on the patient's identification information and patient's drug information stored in the prescription information table 123 and the received identification information and administered drug information of the assisted person CP (S515), and transmits the determination result to the mobile terminal 352 (S517).

[0153] When the portable terminal 352 receives the determination result, it displays the determination result on the display unit 302 of the portable terminal 352 (S519). After that, when the portable terminal 352 receives an input of medication completion indicating that the administration of medication to the assisted person CP has been completed (S521), it transmits a notification of the administration completion to the management server 152 (S523).

[0154] When the management server 152 receives the notification of the completion of medication, it records the completion of medication in the medication schedule information 1241 of the assisted person CP in the medication schedule information table 124 (S525).

[0155] [Medication management]

[0156] FIG. 15 is a diagram illustrating the operations for managing medication to a patient in one embodiment of the present invention.

[0157] 15, the management server 152 determines whether or not a medication has been forgotten at the required timing in the control unit 101 (an example of a medication schedule information creating means, a completion determining means, and a timing calculating means) of the management server 152 (task PR71). The determination of whether or not a task has been forgotten is made based on whether or not there is medication schedule information 1241 in which medication completion (the date and time when a medication completion notification was received) has not been recorded, even after the time determined based on the medication schedule information 1241 has passed. Specifically, this determination is made in the following manner.

[0158] The management server 152 refers to the medication schedule information 1241 in the medication schedule information table 124, and extracts medications for which the medication completion date and time column is not recorded from among the medications listed in the medication schedule information 1241 and for which the scheduled medication date is that day. The management server 152 determines, for each extracted medication, the time range within which the medication can be administered based on the medication schedule. The time range within which the medication can be administered is determined by a method similar to the determination method used in the second determination described above.

[0159] The management server 152 refers to the current date and time and determines whether the end time of the determined time range in which medication can be administered (in other words, the medication timing) has passed. If the end time of the determined time range in which medication can be administered has passed, the management server 152 determines that a missed dose has occurred. If there are no medications to extract or if the end time of the determined time range in which medication can be administered has not passed, the management server 152 determines that a missed dose has not occurred. For example, in the medication schedule information 1241 of the medication schedule information table 124 shown in FIG. 8, the end time of the time range in which medication can be administered for each of the medications named "Drug PH1" and "Drug PH2" whose administration timing is "after dinner on January 13, 2022" is determined to be 9:00 p.m. on January 13, 2022. In this case, if the current date and time is after 9:00 p.m. on January 13, 2022, it is determined that the current date and time has passed the end time of the time range in which "Drug PH1" and "Drug PH2" can be administered.

[0160] The storage device 105 (an example of contact information storage information) of the management server 152 stores the contact information of the manager regarding medication in medication schedule information 1241 of the medication schedule information table 124. When the management server 152 determines that a missed medication has occurred, it notifies the contact information of the manager via the network interface 104 (an example of a notification means) of the management server 152, and displays the notification of the missed medication on the display unit 302 of the mobile terminal 353 (operation PR72). The management server 152 includes in the notification of the missed medication the name of the patient on whom the missed medication occurred, the date and time, the contact information of the caregiver PN2, etc.

[0161] The pharmacist PN3, who is the manager, recognizes the missed medication by looking at the missed medication notification displayed on the display unit 302 of the mobile terminal 353. The pharmacist PN3 takes the necessary action, such as contacting the contact details of the caregiver PN2 (task PR73). Communication with the caregiver PN2 can be carried out by telephone, chat tool, or the like. In this way, the pharmacist PN3 can manage the medication given to the patient. The manager does not have to be the pharmacist PN3, and can be any person.

[0162] Furthermore, an authorized person such as the caregiver PN2 can obtain information such as the status of medication for the care recipient CP and contact information for the administrator from the management server 152 at any time necessary.

[0163] The caregiver PN2 starts up the app 321 on the mobile terminal 352 at the necessary timing and inputs the identification information of the caregiver PN2 into the mobile terminal 352. The caregiver PN2 also inputs a request to send necessary information (such as patient information 1211, prescription information 1231, medication schedule information 1241, or contact information of the administrator regarding the care recipient CP) along with the identification information of the caregiver PN2. The mobile terminal 352 accepts the input of the identification information of the caregiver PN2 and the request to send the necessary information (operation PR81). Here, the mobile terminal 352 accepts the input of the identification information of the caregiver PN2 by reading the code CD4 attached to a nameplate NP2 or the like carried by the caregiver PN2. The method of inputting the identification information of the caregiver PN2 is arbitrary.

[0164] The mobile terminal 352 transmits the input identification information of the caregiver PN2 and a request to send the necessary information to the management server 152. The management server 152 receives the identification information of the caregiver PN2 and the request to send the necessary information (operation PR82).

[0165] When the management server 152 receives the identification information of the caregiver PN2 and the request to send the necessary information, it performs authentication work for the caregiver PN2 (work PR83). The management server 152 determines whether the authorized person information 1221 corresponding to the identification information of the caregiver PN2 is registered in the authorized person information table 122.

[0166] If the management server 152 determines that authorized person information 1221 (authorized person ID and authorized person name) that matches the identification information of the caregiver PN2 (caregiver PN2's ID and name) is registered in the authorized person information table 122, it authenticates the caregiver PN2, sends the requested information to the mobile terminal 352, and displays it on the display unit 302 of the mobile terminal 352 (operation PR84).If the management server 152 determines that authorized person information 1221 that matches the identification information of the caregiver PN2 is not registered in the authorized person information table 122, it does not authenticate the caregiver PN2 and does not send the requested information to the mobile terminal 352.

[0167] This allows the caregiver PN2 to check the medication status of the person being assisted CP based on the information displayed on the display unit 302 of the mobile terminal 352, and to make necessary contact with the manager (for example, contact regarding irregular movements of the person being assisted CP, such as hospitalization or death of the person being assisted CP).

[0168] 16 is a flowchart illustrating the operations performed by the medication management system when managing medication for a patient in one embodiment of the present invention. This flowchart is realized by the CPU executing a control program stored in the ROM.

[0169] Referring to Figure 16, the management server 152 refers to the medication schedule information 1241 and determines whether or not there are any medications listed in the medication schedule information 1241 for which the scheduled medication date is that day and for which the medication completion date and time is not recorded (S701).

[0170] In step S701, if it is determined that there is a drug for which the administration completion date and time is not recorded (YES in S701), the administration timing of the drug for which the administration completion date and time is not recorded is calculated (S702), and it is determined whether the current time has passed the calculated administration timing (S703).

[0171] In step S701, if it is determined that there are no drugs for which the scheduled administration date is that day and for which the administration completion date and time is not recorded (NO in S701), or if it is determined in step S703 that the current time has not passed the calculated administration timing (NO in S703), the management server proceeds to processing in step S701.

[0172] In step S703, if it is determined that the current time has passed the calculated medication timing (YES in S703), the management server 152 sends a notification of missed medication to the mobile terminal 353 of pharmacist PN3, who is the manager's contact information listed in the medication schedule information 1241 (S705).

[0173] When the mobile terminal 353 receives the notification of the missed medication, the mobile terminal 353 displays the notification of the missed medication on the display unit 302 of the mobile terminal 353 (S707).

[0174] The mobile terminal 352 receives input of a request to send the identification information of the caregiver PN2 and the necessary information (S801), and then transmits the request to send the identification information of the caregiver PN2 and the necessary information to the management server 152 (S803).

[0175] When the management server 152 receives the identification information of the caregiver PN2 and a request to send the necessary information, it authenticates the caregiver PN2 based on the received identification information of the caregiver PN2 and the authorized person information table 122 (S805). If the authentication of the caregiver PN2 is successful, the management server 152 transmits the requested necessary information together with the authentication result to the mobile terminal 352 (S807).

[0176] When the mobile terminal 352 receives the necessary information, it displays the information (S809).

[0177] [Drop or skip registration]

[0178] FIG. 17 is a diagram illustrating the work that the caregiver PN2 performs to register a dropped or skipped medication in the medication schedule information table 124 in one embodiment of the present invention.

[0179] 17, when a dropped or skipped medication occurs, the caregiver CP registers this fact in the medication schedule information table 124 (FIG. 8). The flow of this registration will be described below.

[0180] First, the management server 152 authenticates the caregiver PN2 through processes PR51 to PR54 in Fig. 13. If authenticated in process PR54, the caregiver PN2 uses the operation unit 103 of the mobile terminal 352 to perform a predetermined operation (for example, pressing a predetermined key displayed on the application screen) to register a drop or skip in the medication schedule information table 124 (process PR91).

[0181] Next, the caregiver PN2 uses the image reading unit 306 of the portable terminal 352 to read the code CD1 displayed on the medication PH related to the dropping or skipping. As a result, the portable terminal 352 acquires the patient's identification information, the patient's medication information, and the patient's medication information related to the dropping or skipping (process PR92). In process PR92, the caregiver PN2 may use the operation unit 103 of the portable terminal 352 to input the patient's identification information, the patient's medication information, and the patient's medication information related to the dropping or skipping into the portable terminal 352.

[0182] When the mobile terminal 352 accepts input of the patient's identification information, the patient's drug information, and the patient's medication information, it transmits this information together with information on whether to drop or skip the medication to the management server 152. The management server 152 receives the information on whether to drop or skip the medication, the patient's identification information, the patient's drug information, and the patient's medication information from the mobile terminal 352 (process PR93). The management server 152 extracts the medication schedule information 1241 related to the patient's identification information from the medication schedule information table 124, and enters whether to drop or skip the medication in the remarks column of the item (row) indicated by the patient's drug information and the patient's medication information in the medication schedule information 1241 (process PR94).

[0183] 18 is a flowchart illustrating the operation of the medication management system when the caregiver PN2 registers a drop or skip in the medication schedule information table 124 in one embodiment of the present invention. This flowchart is realized by the CPU executing a control program stored in the ROM.

[0184] 18, each of the mobile terminal 352 of the caregiver PN2 and the management server 152 performs the processes of steps S501 to S507 in FIG.

[0185] If the authentication result indicating successful authentication is received in step S507, the mobile terminal 352 accepts an operation to register a drop or skip (S901), and accepts input of the patient's identification information, the patient's drug information, and the patient's medication information (S903). Next, the mobile terminal 352 transmits the drop or skip information, the patient's identification information, the patient's drug information, and the patient's medication information to the management server 152 (S905).

[0186] When the management server 153 receives the information on dropping or skipping the medication, the patient's identification information, the patient's drug information, and the patient's medication information from the mobile terminal 352, it extracts the medication schedule information 1241 related to the patient's identification information from the medication schedule information table 124 (S907). The management server 153 enters dropping or skipping the medication in the remarks column of the item (row) indicated by the patient's drug information and the patient's medication information in the medication schedule information 1241 (S909), and ends the processing.

[0187] [Effects of the embodiment]

[0188] In the above-described embodiment, the patient identification information and patient medication information stored in the database are information obtained from the receipt computer 151, which is a device that accepts input of information written on a prescription, or from an electronic prescription, and are the same information as the information written on the prescription. The determination of whether or not it is appropriate to administer medication to the assisted person CP is accurately made based on the same information as the information written on the prescription. Therefore, the caregiver PN2 can obtain an accurate determination result as to whether or not it is appropriate to administer medication to the assisted person CP. This reliably prevents the assisted person CP from mistakenly administering medication prescribed for someone other than the assisted person CP. As a result, medication for patients can be properly managed.

[0189] Furthermore, the determination of whether or not the administration of medication to the assisted person CP is appropriate is further based on the patient's medication information stored in the database and the timing at which the assisted person's identification information and the administered medication information were acquired. This reliably prevents the assisted person CP from receiving medication at the administration timing contrary to that specified on the prescription. As a result, medication administration to patients can be properly managed.

[0190] The patient identification information, patient drug information, patient medication information, and patient medication information stored in the database are information received from the receipt computer 151, which is a device that accepts input of information written on prescriptions. There is no need for caregivers or others to manually input this information into the management server 152. This reduces the burden on caregivers or others involved in managing medication for patients.

[0191] The portable terminal 352 reads the code CD1 attached to the medicine PH and accepts input of the patient's identification information, the patient's medicine information, and the patient's medication information. This eliminates the need for the caregiver PN2 to manually input the patient's identification information, the patient's medicine information, and the patient's medication information.

[0192] By making various decisions only if authentication is successful, it is possible to prevent unauthorized use of the system.

[0193] When delivering medicines, it is determined whether the delivery location of the medicines is correct, so that it is possible to avoid a situation where medicines are delivered to an incorrect delivery location.

[0194] Furthermore, by notifying the administrator when a medication is forgotten, it becomes easier for the administrator to manage medication. This reduces the burden on caregivers and others involved in managing medication for patients. In particular, by appointing a pharmacist, who is the person who should be managing medication, as the administrator, medication can be managed more appropriately.

[0195] [others]

[0196] The above-described embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0197] 101, 201, 301 Control unit (an example of a medication determination means, a delivery determination means, a medication schedule information creation means, a completion determination means, and a timing calculation means) 102,202,302 Display section 103, 203, 303 Operation unit (an example of a prescription receiving means, a medication completion receiving means, and a delivery information receiving means) 104, 204, 304 Network interface (examples of the first acquisition means, second acquisition means, medication determination result display means, third acquisition means, fourth acquisition means, medication completion sending means, notification means, and delivery determination result display means) 105,205,305 Storage device (example of patient information storage means, identification information storage means, completion storage means, contact information storage information) 111,211,311 CPU(Central Processing Unit) 112,212,312 ROM(Read Only Memory) 113,213,313 RAM (Random Access Memory) 121 Patient Information Table 122 Authorizer Information Table 123 Prescription Information Table 124 Medication Schedule Information Table 151 Receipt computer (example of a receipt computer) 152 Management Server (Example of a management server) 153 Pharmacy terminal 206 Packaging section (an example of packaging means) 207 Information adding unit (an example of code adding means) 251 Packaging machine (an example of information adding equipment) 306 Image reading unit (an example of a reading means) 321 Applications 351, 352, 353 Mobile terminal (example of caregiver terminal, delivery person terminal) 401 Network 1211 Patient Information 1221 Permit information 1231 Prescribing Information 1241 Medication Information CD1, CD2, CD3, CD4, CD5 code CP person being cared for IN1 Prescription Information IN2 Additional Information NP1, NP2 nameplate PN1 Delivery Person PN2 Caregiver PN3 Pharmacist SH1 Receipt SH2 Medication Record WB Wristband

Claims

1. A medication management system including a management server that manages medication and an assistant terminal used by an assistant who assists a person receiving care with medication, In the management server, a first acquisition means acquires patient identification information, which is information for identifying a patient, and patient drug information, which is information for specifying drugs prescribed to the patient, from a receipt computer or an electronic prescription that accepts input of information written on a prescription; a patient information storage means in the management server for storing the patient identification information and the patient medication information acquired by the first acquisition means in a database in association with each other; a second acquisition means for acquiring, in the caregiver terminal, identification information of the person being assisted, which is information for identifying the person being assisted, and administration drug information, which is information on drugs to be administered to the person being assisted; a medication determination means for determining whether or not medication is appropriate for the person being assisted, based on the patient's identification information and medication information stored in the database, and the person being assisted's identification information and the administered medication information acquired by the second acquisition means; a medication determination result display means for displaying the result determined by the medication determination means on the caregiver terminal; When the type of drug prescribed to the patient is a first drug including patient medication information which is information regarding the timing of medication to the patient, the first acquisition means further acquires, in the management server, patient medication information which is information regarding the timing of medication to the patient from the receipt computer or the electronic prescription; When the type of drug prescribed to the patient is a second drug that does not include the patient's medication information, the first acquisition means does not acquire the patient's medication information, which is information regarding the timing of medication to the patient, from the receipt computer or the electronic prescription in the management server, The patient information storage means stores the medication information of the patient acquired by the first acquisition means in the management server in the database in association with the patient's identification information and the patient's drug information; The medication determination means a first medication determination means for determining whether a combination of the patient and the medication to be administered is appropriate based on the patient's identification information and medication information stored in the database, and the patient's identification information and the administered medication information acquired by the second acquisition means, when the types of medication prescribed to the patient are the first and second medications; and a second medication determination means for determining whether or not the medication to the patient being assisted is appropriate, when the type of medication prescribed to the patient is the first medication, based on the medication information of the patient stored in the database, and further based on the identification information of the patient being assisted and the timing of acquisition of the administered medication information; A medication management system in which, when the type of medication prescribed for the patient is the second medication, the second medication determination means does not determine whether medication for the person being assisted is appropriate.

2. An event receiving means for receiving an input of a drop, which is an event in which the medicine prescribed to the person being assisted is insufficient, or a skip, which is an event in which the medicine prescribed to the person being assisted is left over; The medication management system of claim 1, further comprising an event storage means for storing the event in the database in association with the patient identification information, the patient's medication information, and the patient's medication information regarding the assisted person when input is received by the event receiving means in the management server.

3. The second acquisition means further acquires medication timing information which is information regarding the administration timing of a drug to be administered to the person being assisted, The medication management system according to claim 1 , wherein the second medication determination means determines whether medication is appropriate for the person being assisted, further based on the medication timing information acquired by the second acquisition means.

4. an information addition device; a third acquiring means for acquiring, in the information adding device, identification information of the patient, drug information of the patient, and medication information of the patient; the information addition device further comprises a code addition means for adding a code including the patient's identification information, the patient's drug information, and the patient's medication information acquired by the third acquisition means to the drug packaged for the patient, The medication management system according to claim 1 , wherein the second acquisition means includes a reading means for reading the code attached to the medication to be administered to the person being assisted.

5. 5. The medication management system according to claim 4, wherein said information adding device further comprises packaging means for packaging medicines in predetermined amounts.

6. The second medication determination means determines whether or not medication is appropriate for the person being assisted in the management server, an identification information storage means for storing authorized person information, which is identification information of a person authorized to use a predetermined function, in the database; The management server further includes a fourth acquisition means for acquiring, from the caregiver terminal, identification information of the caregiver, which is information for identifying the caregiver; The medication management system according to claim 1 , wherein the medication determination means does not make a determination if the identification information of the caregiver acquired by the fourth acquisition means is not included in the authorized person information.

7. a medication completion receiving means in the caregiver terminal for receiving an input of medication completion indicating that medication to the person being assisted has been completed; a medication completion sending means for sending a notification of the medication completion to the management server in the caregiver terminal when the medication completion receiving means receives an input of the medication completion; The medication management system of claim 1, further comprising a completion storage means for storing the fact that medication has been completed in the database in association with the patient's identification information, the patient's drug information, and the patient's medication information regarding the assisted person when the management server receives notification of the medication completion.

8. Contact information storage information for storing contact information of a manager who manages the administration of medication to the patient in the database; The medication management system of claim 7, further comprising an alerting means in the management server that alerts the administrator to a contact point of the administrator that medication has been forgotten to the patient if the fact that the medication has been completed is not stored in the database even after a time determined based on the patient's medication information has passed.

9. a delivery person terminal used by a delivery person who delivers medicine to the person being assisted; a delivery information receiving means in the delivery person terminal for receiving input of identification information of the person being assisted and delivery drug information, which is information on drugs to be delivered to the person being assisted; a delivery determination means for determining whether the delivery location of the medicine is correct based on the patient's identification information and the patient's medicine information stored in the database, and the patient's identification information and the medicine delivery information received by the delivery information receiving means; The medication management system according to claim 1, further comprising a delivery determination result display means for displaying the result determined by the delivery determination means on the deliverer terminal.

10. A management server for managing medication, a first acquiring means for acquiring patient identification information, which is information for identifying a patient, and patient drug information, which is information for specifying drugs prescribed to the patient, from a receipt computer or an electronic prescription that accepts input of information written on a prescription; a patient information storage means for storing the patient identification information and the patient medication information acquired by the first acquisition means in a database in association with each other; a second acquisition means for acquiring, from an assistant terminal used by an assistant who assists the assistant in administering medication to the assistant, identification information of the assistant, which is information that identifies the assistant, and administered medication information, which is information on the medication to be administered to the assistant; a medication determination means for determining whether or not medication is appropriate for the person being assisted, based on the patient's identification information and medication information stored in the database, and the person being assisted's identification information and the administered medication information acquired by the second acquisition means; a medication determination result display means for displaying the result determined by the medication determination means on the caregiver terminal; When the type of drug prescribed to the patient is a first drug including patient medication information which is information regarding the timing of medication to the patient, the first acquisition means further acquires, in the management server, patient medication information which is information regarding the timing of medication to the patient from the receipt computer or the electronic prescription; When the type of drug prescribed to the patient is a second drug that does not include the patient's medication information, the first acquisition means does not acquire the patient's medication information, which is information regarding the timing of medication to the patient, from the receipt computer or the electronic prescription in the management server, The patient information storage means stores the medication information of the patient acquired by the first acquisition means in the management server in the database in association with the patient's identification information and the patient's drug information; The medication determination means a first medication determination means for determining whether a combination of the patient and the medication to be administered is appropriate based on the patient's identification information and medication information stored in the database, and the patient's identification information and the administered medication information acquired by the second acquisition means, when the types of medication prescribed to the patient are the first and second medications; and a second medication determination means for determining whether or not the medication to the patient being assisted is appropriate, when the type of medication prescribed to the patient is the first medication, based on the medication information of the patient stored in the database, and further based on the identification information of the patient being assisted and the timing of acquisition of the administered medication information; A management server, wherein when the type of medication prescribed to the patient is the second medication, the second medication determination means does not determine whether the medication to the person being assisted is appropriate.

11. A control program of a management server for managing medication, A first acquisition step of acquiring patient identification information, which is information for identifying a patient, and patient drug information, which is information for specifying drugs prescribed to the patient, from a receipt computer or an electronic prescription that accepts input of information described on a prescription; a patient information storage step of storing the patient identification information and the patient medication information acquired in the first acquisition step in a database in association with each other; a second acquisition step of acquiring, from an assistant terminal used by an assistant assisting the assisted person with medication, identification information of the assisted person, which is information identifying the assisted person, and administered medication information, which is information on the medication to be administered to the assisted person; a medication determination step of determining whether or not medication is appropriate for the person being assisted, based on the patient's identification information and medication information stored in the database, and the assisted person's identification information and the administered medication information acquired in the second acquisition step; and a medication determination result display step of displaying the result determined in the medication determination step on the caregiver terminal, When the type of drug prescribed to the patient is a first drug including patient medication information, which is information regarding the timing of medication to the patient, in the first acquisition step, the management server further acquires patient medication information, which is information regarding the timing of medication to the patient, from the receipt computer or electronic prescription; If the type of drug prescribed to the patient is a second drug that does not include the patient's medication information, in the first acquisition step, the management server does not acquire the patient's medication information, which is information regarding the timing of medication to the patient, from the receipt computer or electronic prescription; In the patient information storage step, the management server stores the medication information of the patient acquired by the first acquisition means in the database in association with the patient's identification information and the patient's drug information; The medication determination step includes: a first medication determination step for determining whether a combination of the patient and the medication to be administered is appropriate based on the patient's identification information and medication information stored in the database when the types of medication prescribed to the patient are the first and second medications, and the patient's identification information and medication information acquired in the second acquisition step; and a second medication determination step of determining whether or not the medication to the patient being assisted is appropriate, when the type of medication prescribed to the patient is the first medication, based on the medication information of the patient stored in the database, and the identification information of the patient being assisted and the timing of acquisition of the administered medication information; A control program of a management server that, when the type of medication prescribed for the patient is the second medication, does not determine whether the medication to the assisted person is appropriate in the second medication determination step.

Images