JP2024027544A - Program, method and information processing device - Google Patents

Abstract

To provide a technique allowing a pharmacist to further easily acquire a medication state of a patient.SOLUTION: Provided is a program causing a computer including a processor and a memory to execute processing. The program causes the processor to execute: a first step of acquiring first information representing content of a prescription for prescribing a medicine to a patient; a second step of, when the prescription can be prescribed a plurality of predefined times and the number of prescribed times of the prescription does not reach an upper limit of the plurality of predefined times, calculating, based on the first information, a time when the patient receives the medicine based on the prescription; and a third step of presenting the time calculated in the second step to a user.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to a program, a method, and an information processing device.

When pharmacists provide medicines to patients at medical institutions such as pharmacies, they explain things to keep in mind when taking medicines. For example, a pharmacist may be able to treat a patient suffering from a chronic disease by visiting the hospital again before the medicines provided are exhausted, having the doctor prescribe the medicine, and visiting the pharmacy to administer the medicine. In some cases, it may be explained that you will be provided with There is Patent Document 1 as a system for notifying patients in advance of their next visit to the hospital and the timing of their next visit.

Patent Document 1 discloses a patient information storage means that associates and stores prescription information of a patient and an e-mail address of a mobile terminal owned by the patient, the date and time of taking a drug specified based on the prescription information, and/or Alternatively, a dispensing device is equipped with an automatic notification e-mail distribution means that creates a notification e-mail to notify in advance of the next visit to the hospital/office, and automatically sends it to the e-mail address associated with the prescription information. The pharmacy system is described.

Japanese Patent Application Publication No. 2013-105302

If a prescription received from a patient can be used repeatedly, a doctor's examination to prescribe the drug may not be conducted. Therefore, pharmacists may need to further support patients in taking medication, such as by encouraging patients to continue receiving medication.

Therefore, the present disclosure provides a technology that enables pharmacists to further enhance medication support for patients.

According to one embodiment, a program is provided that is executed by a computer including a processor and a memory. The program includes, in a first step, obtaining first information indicating to the processor the contents of a prescription for prescribing a drug to a patient; and if the prescription can be used again at a next visit. , based on the first information, a second step of calculating the time when the patient will next visit the hospital, and a third step of presenting the time calculated in the second step to the user.

According to the present disclosure, pharmacists can further enhance medication support for patients.

1 is a diagram showing the overall configuration of a system 1. FIG. It is a block diagram of terminal device 10 which constitutes system 1 of a 1st embodiment. It is a diagram showing the functional configuration of a server 20 that constitutes the system 1 of the first embodiment. It is a diagram showing the data structure of a prescription database 281, a reminder database 282, a contact history database 283, and a patient information database 284 stored in the server 20. 2 is a flowchart illustrating an example of a flow in which the system 1 according to the first embodiment calculates a time when medicine can be delivered to a patient and presents it to a user. The system 1 according to the first embodiment provides a system in a case where the number of times a drug is delivered reaches a predetermined upper limit of the number of times the prescription can be used in a prescription that allows the delivery of a drug multiple times. 2 is a flowchart illustrating an example of processing in step 1; It is a figure which shows the example of a screen of the terminal device 10 of the pharmacist who is a user in 1st Embodiment. It is a figure showing an example of a screen of terminal device 30 of a patient who is a user in a 1st embodiment. 12 is a flowchart illustrating an example of the flow when a patient receives a drug at a pharmacy different from the pharmacy where the drug was most recently delivered, according to the second embodiment. 12 is a flowchart illustrating an example of a flow when a patient's terminal device is used to share information between pharmacies regarding a patient's medication status in the second embodiment. It is a figure which shows the example of a screen of the pharmacist's terminal device 10 or the patient's terminal device 30 in 2nd Embodiment. 12 is a flowchart illustrating processing when a pharmacist determines to stop delivering medicine to a patient in the third embodiment. It is a flow chart which shows an example of a flow of displaying a pharmacist's schedule in a 4th embodiment. It is a figure which shows the example of a screen of the pharmacist's terminal device 10 in 4th Embodiment.

Embodiments of the present disclosure will be described below with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

<First embodiment>
<1. Overall configuration of system 1>
System 1 is a system for assisting pharmacists in medical institutions to provide drugs to patients while also presenting and reminding users when they can receive the patient's drugs. . Here, a medical institution is a facility for providing medical care, and includes, for example, a hospital, a clinic, a pharmacy, a visiting nursing station, and a health facility. In the following, explanation will be given using an example of a pharmacy as a medical institution. Moreover, the user here is at least one of a patient, a doctor who is a medical worker, and a pharmacist. FIG. 1 is a diagram showing the overall configuration of a system 1. As shown in FIG.

As shown in FIG. 1, the system 1 includes a terminal device 10, a server 20, and a terminal device 30. The terminal device 10 is a terminal installed at a medical institution or a terminal operated by a medical worker at the medical institution. The terminal device 10 is a terminal installed in a medical institution such as a pharmacy or a hospital. The terminal device 30 is a terminal operated by a patient. The terminal device 10 and the terminal device 30 and the server 20 are communicably connected via a network 80.

The terminal device 10 is a device operated by each medical worker at a medical institution. The medical personnel referred to here are those who prescribe medicines to patients or those who deliver medicines to patients, and include, for example, doctors and pharmacists. The following is an example of a pharmacist as a medical worker. The terminal device 10 is, for example, a stationary PC (Personal Computer), a laptop PC, or a tablet.

Terminal device 30 is a device carried by a patient. The patient here is a person who has been prescribed a drug by a doctor at a medical institution. For example, the terminal device 30 is a tablet or a smartphone.

As shown in FIG. 1 as a terminal device 10, the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage section 16, and a processor 19.

The terminal device 10 is communicably connected to the server 20 via the network 80. The communication line of the network 80 may be wired or wireless.

The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 communicates with an external device. The input device 13 is an input device (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.) for receiving input operations from a pharmacist. The output device 14 is an output device (display, speaker, etc.) for presenting information to the pharmacist. The memory 15 is for temporarily storing programs and data processed by the programs, and is, for example, a volatile memory such as DRA (Dynamic Random Access Memory). The storage unit 16 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive). The processor 19 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

The server 20 is a device that manages patient information and pharmacist contact history with patients. Server 20 is a computer connected to network 80.

As shown in FIG. 1, the server 20 includes a communication IF 22, an input/output IF 23, a memory 25, a storage 26, and a processor 29.

The communication IF 22 is an interface for inputting and outputting signals so that the server 20 communicates with external devices. The input/output IF 23 functions as an interface with an input device for receiving input operations from a pharmacist and an output device for presenting information to the pharmacist. The memory 25 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory), for example. The storage 26 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive). The processor 29 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

<1.1 Configuration of terminal device 10>
FIG. 2 is a block diagram of the terminal device 10 that constitutes the system 1 of the first embodiment. As shown in FIG. 2, the terminal device 10 includes a communication section 120, an operation reception section 130, a display section 160, a storage section 170, and a control section 180. The terminal device 10 also has functions and configurations that are not particularly illustrated in FIG. 2 (for example, a battery for holding power, a power supply circuit that controls the supply of power from the battery to each circuit, etc.). As shown in FIG. 2, each block included in the terminal device 10 is electrically connected by a bus or the like.

The communication unit 120 is communicably connected to the server 20 via the network 80 so that the terminal device 10 communicates with other devices.

The operation reception unit 130 has a mechanism for accepting input operations from a pharmacist. For example, the operation reception unit 130 includes a mouse, a keyboard, a touch panel, or the like.

The display unit 160 displays data such as images, videos, and text under the control of the control unit 180. The display unit 160 is realized by, for example, a liquid crystal display.

The storage unit 170 is configured of, for example, a flash memory, and stores data and programs used by the terminal device 10. In one aspect, storage unit 170 stores prescription information 171 and patient information 172.

The prescription information 171 is information indicating the contents of a prescription prescribed by a doctor to a patient. The terminal device 10 receives an operation to input the contents of a prescription from a pharmacist via the network 80. Alternatively, the terminal device 10 may acquire information indicating the contents of a prescription to be prescribed to a patient from a terminal at a medical institution.

The patient information 172 is information regarding the patient, such as the patient's name, contact information, and medication status. The terminal device 10 receives an operation to input patient information from a pharmacist via the network 80. Further, the terminal device 10 may acquire patient information from the server 20.

The control unit 180 controls the operation of the terminal device 10 by reading a program stored in the storage unit 170 and executing instructions included in the program. The control unit 180 functions as an input operation reception unit 181, a transmission/reception unit 182, a display control unit 183, and a notification control unit 184 by operating according to a program.

The input operation reception unit 181 performs a process of accepting a pharmacist's input operation on an input device such as a mouse or a keyboard.

The transmitting/receiving unit 182 performs processing for transmitting and receiving data with an external device such as the server 20 in the terminal device 10 according to a communication protocol.

The display control unit 183 controls display processing of the display unit 160. For example, the display control unit 183 controls display processing of the display unit 160. For example, the display control unit 183 reads the contents of the video memory, generates a signal for displaying on the display, and controls the signal to be sent to the display.

The notification control unit 184 performs a process of presenting information to be notified to the pharmacist. The notification control unit 184 performs processing such as displaying the notified information on the display unit 160.

<1.2 Functional configuration of server 20>
FIG. 3 is a diagram showing the functional configuration of the server 20 that constitutes the system 1 of the first embodiment. As shown in FIG. 3, the server 20 functions as a communication section 201, a storage section 202, and a control section 203.

The communication unit 201 performs processing for communicating with an external device in the server 20 .

The storage unit 202 stores data and programs used in the server 20. The storage unit 202 stores a prescription database 281, a reminder database 282, a contact history database 283, and a patient information database 284.

The prescription database 281 is a database for holding information on prescriptions accepted at pharmacies. Details will be described later.

The reminder database 282 is a database for holding the contents of a pharmacist's notification to a patient of a period during which medicine can be delivered. Details will be described later.

The contact history database 283 is a database for holding a history of contacts made by pharmacists to patients and/or other pharmacists. Details will be described later.

The patient information database 284 is a database for holding patient information. Specifically, the patient information database 284 is a database for holding, as patient information, information regarding the patient's contact information and information indicating the medication intake status. Details will be described later.

The control unit 203 performs functions shown as various modules by the processor of the server 20 performing processing according to a program.

The reception control module 2031 controls the process of receiving a signal from an external device in the server 20 according to a communication protocol.

The transmission control module 2032 controls the process of transmitting a signal to an external device in the server 20 according to a communication protocol.

The reception module 2033 controls the process by which the server 20 receives input and registration of information via the network 80. For example, the reception module 2033 performs the following to receive information registration from the user.
- Accept registration of prescription information entered by pharmacists.
・Receive registration of information entered by patients regarding scheduled visits to the pharmacy.

The number-of-use determination module 2034 controls the process of determining the number of times a patient can use the prescription again, based on the prescription information received by the reception module 2033. The number-of-use determination module 2034 may determine the number of times a prescription can be used again, based on the number of times the prescription can be used, which the server 20 has received input from the pharmacist via the network 80.

The calculation module 2035 controls processing performed by the server 20 to output information to the terminal device 10 and the terminal device 30 based on the information received by the reception module 2033 via the network 80 . For example, when the number of times the drug is delivered based on the prescription received by the reception module 2033 has not reached the predetermined upper limit of the number of times, the calculation module 2035 determines when to deliver the drug to the patient based on the prescription information; , Calculate the reminder time to notify that it is time to issue the medicine. The calculation module 2035 calculates, for example, the time to deliver the medicine to the patient and the reminder time to notify the arrival of the time to deliver the medicine, based on the date of reception of the prescription and the period of taking the medicine in the prescription database 281. A method for calculating the time to deliver the medicine to the patient and the reminder time by the calculation module 2035 will be described later.

The presentation module 2036 controls the process by which the server 20 presents information to the user via the network 80. For example, the presentation module 2036 sends a signal to the terminal device 10 for displaying the patient's next visit time calculated by the calculation module 2035 and the pharmacist's reminder time for the patient on the display unit 160 of the terminal device 10. Control the processing to send to.
<2. Data structure>

FIG. 4 is a diagram showing the data structure of the prescription database 281, the reminder database 282, the contact history database 283, and the patient information database 284 stored in the server 20.

The prescription database 281 is a database for holding information on prescriptions received at pharmacies. As shown in FIG. 4, each record in the prescription database 281 includes an item "reception ID", an item "prescription ID", an item "prescription date", an item "reception date", and an item "pharmacy ID". , the item ``Patient ID'', the item ``Publisher ID'', the item ``Drug'', the item ``Prescription amount'', the item ``Dose period'', the item ``Usable number of times'', and the item ``Remaining number of times''. , includes the item "next drug delivery period", the item "discontinuation date and time", and the item "physician contact date". For example, the server 20 adds a record to the prescription database 281 by having the reception module 2033 accept information on a prescription issued to a patient at a medical institution. The server 20 may, for example, add a record to the prescription database 281 by accepting input of prescription information from a pharmacist at the terminal device 10 through the reception module 2033.

The item "reception ID" is information that identifies each history of prescriptions received from patients. For example, the server 20 may issue a reception ID in response to the reception module 2033 accepting input of prescription information from a pharmacist on the terminal device 10. When receiving the same prescription multiple times, the server 20 may issue a reception ID each time it receives a prescription.

The item "prescription ID" is information that identifies prescription information received from a patient. The server 20 issues the same prescription ID for the same prescription.

The item "prescription date" is information indicating the date of issue of the prescription identified by the item "prescription ID."

The item "reception date" is information indicating the date when the prescription information was received at the pharmacy.

The item "pharmacy ID" is information that identifies each pharmacy.

The item "patient ID" is information that identifies each patient.

The item "Issuer ID" is information that identifies each medical institution that issues the prescription identified by the item "Prescription ID."

The item "drug" is information indicating each drug prescribed to the patient identified by the item "prescription ID."

The item "prescription amount" is information indicating the amount of medicine prescribed to the patient identified by the item "patient ID". Specifically, the item "prescription amount" is information input from the pharmacist based on the information written in the prescription. The item "prescription amount" is, for example, information shown in the prescription information when the server 20 acquires data on a prescription issued to a patient at a medical institution.

The item "dose period" is information indicating the period during which the drug identified by the item "patient ID" is taken. Specifically, the item "dose period" is information input from the pharmacist based on information written in the prescription. The item "dose period" is, for example, information shown in the prescription information when the server 20 acquires data on a prescription issued to a patient at a medical institution.

The item "number of times a prescription can be used" is information indicating the number of times a prescription can be used. Specifically, the item "usable number of times" may be information determined by a doctor when a prescription is issued to a patient at a medical institution.

The item "remaining number of times" is information indicating the remaining number of times the prescription can be used again by the patient at the time when the server 20 acquires the prescription information. Specifically, the item "remaining number of times" is information calculated based on data on prescriptions issued to patients at medical institutions. The item "remaining number of times" is, for example, when the server 20 acquires the prescription information assuming that the pharmacy accepts the prescription from the patient. This is information indicating the number of times the number of receptions has been subtracted. Moreover, specifically, the item "remaining number of times" may be information indicating the remaining number of times a prescription can be used again, and which is information that has been received as an operation input from a pharmacist.

The item "next drug delivery period" is information indicating the period during which the next drug can be delivered when the prescription can be used again by the patient. Specifically, the item "next drug delivery period" may be calculated based on prescription information input from the pharmacist. The detailed method for calculating the drug delivery period will be described later.

The item "date and time of discontinuation" is information indicating the date and time when at least one of the doctor and pharmacist decided to use the prescription again for the patient.
Specifically, the item "date and time of discontinuation" is used when the pharmacist determines that the patient should not use the prescription again based on the patient's physical condition observed at the time of the patient's visit or the patient's medication status. , the date and time when the discontinuation input was received from the pharmacist may be stored. The item "date and time of discontinuation" may store the date and time when the input of discontinuation was received from the doctor, when the doctor has determined to discontinue the use of the prescription for the patient again based on the physical condition of the patient examined. Specifically, the item "date and time of discontinuation" stores the date and time when the doctor sends a notice to the pharmacist to determine that the patient will not be allowed to use the prescription again, and the pharmacist who received the notice confirms the notice. You can.

The item "Doctor contact date" is information indicating the date on which the pharmacist contacted the doctor who issued the prescription. Specifically, the item "doctor contact date" is information indicating the date on which the pharmacist contacted the doctor when the patient stopped using the prescription again. The item "doctor contact date" may be information indicating the date on which the doctor who issued the prescription contacted the pharmacist. The item "doctor contact date" may be information indicating the date on which the doctor contacted the pharmacist when the doctor informed the patient that he or she would not use the prescription again.

The reminder database 282 is a database for holding the contents of a pharmacist's notification to a patient of the period during which medicine can be delivered. As shown in FIG. 4, each record in the reminder database 282 includes the item "reminder ID", the item "reception ID", the item "remaining number of times", the item "next drug delivery period", and the item "reminder schedule". day” and the item “scheduled reminder date.” For example, the server 20 adds a record to the reminder database 282 by receiving prescription information through the reception module 2033 and determining when to notify the patient of the reminder based on the acquired prescription information.

The item "remind ID" is information that identifies each reminder schedule to be performed for a patient.

The item "reception ID" is information that identifies each history of prescriptions received from patients. For example, when a pharmacist accepts a prescription from a patient, the server 20 may issue a reception ID in response to registering prescription information received via the terminal device 10. When receiving the same prescription multiple times, the server 20 may issue an ID each time it receives a prescription. The item “reception ID” is the same as the item “reception ID” in the prescription database 281.

The item "remaining number of times" is information indicating the remaining number of times the prescription can be used again by the patient at the time when the server 20 acquires the prescription information. Specifically, the item "remaining number of times" is information calculated based on data on prescriptions issued to patients at medical institutions. The item "remaining number of times" is, for example, the number of times a patient has already submitted a prescription to a pharmacist after subtracting it from the number of times a predetermined prescription can be used again at the time when the server 20 acquires the prescription information. This is the information shown. Moreover, specifically, the item "remaining number of times" may be information that has been input by a pharmacist as information indicating the remaining number of times the prescription can be used again.

The item "next drug delivery period" is information indicating the period during which the next drug can be delivered when the prescription can be used again by the patient. The detailed method for calculating the drug delivery period will be described later.

The item "scheduled reminder date" is information indicating the scheduled date for reminding the patient based on the delivery period of the next drug. Specifically, the item "scheduled reminder date" is, for example, information indicating a scheduled reminder date a predetermined period before the start date of the next drug delivery period.

The item "scheduled reminder date" is information indicating a scheduled date different from the item "scheduled reminder date" when a plurality of scheduled reminder dates are provided. Specifically, the item "re-reminder scheduled date" is information indicating the scheduled reminder date a predetermined period before the end date of the next drug delivery period. The item "scheduled date for re-reminder" may be, for example, the scheduled date for notifying the patient of another reminder if the patient does not come to the clinic by the arrival of the scheduled re-reminder date.

The contact history database 283 is a database for holding a history of contacts from pharmacists to patients and/or other pharmacists. As shown in FIG. 4, each record in the contact history database 283 includes an item "contact ID", an item "person in charge ID", an item "reception ID", an item "reminder date and time", and an item "reminder content". , the item "Reply date and time", the item "Response content", and the item "Information transmission date". In response to the presentation module 2036 notifying the patient of the reminder, the server 20 generates a reminder ID and adds a record to the contact history database 283. For example, the server 20 stores the data in the contact history database 283 by determining, by the calculation module 2035, that the timing for reminding the patient has arrived and by issuing a reminder notification to the patient from the presentation module 2036. Furthermore, when the reception module 2033 receives a response to the reminder notification from the patient, the server 20 stores the received data in the communication history database 283.

The item "contact ID" is information that identifies each history of actual contact from the pharmacist to the patient.

The item "in charge ID" is information that identifies each pharmacist in charge of contacting the patient in the communication identified by the item "contact ID."

The item "reception ID" is information that identifies each history of prescriptions received from patients. For example, when a pharmacist accepts a prescription from a patient, the server 20 may issue a reception ID in response to registering prescription information received via the terminal device 10. When receiving the same prescription multiple times, the server 20 may issue an ID each time it receives a prescription.
The item “reception ID” is common to the item “reception ID” of the prescription database 281 and the reminder database 282.

The item "reminder date and time" is information indicating the date and time when the pharmacist notified the patient of the reminder.

The item "reminder content" is information indicating the content of the reminder from the pharmacist to the patient. Specifically, the item "reminder content" is information indicating the patient's next drug delivery period and the content for notifying the patient of the arrival of the drug delivery period. The item "reminder content" is information indicating, for example, the content of the pharmacist's reminder to the patient to inform the patient of the arrival of the drug delivery period.

The item "response date and time" is information indicating the date and time when the patient notified the pharmacist of the response to the reminder notification received by the patient.

The item "response content" is information indicating the content of the patient's response to the pharmacist in response to the reminder notification received by the patient.

The item "information transmission date" is information indicating the date on which information was transmitted from a pharmacist to another pharmacy. Specifically, the item "Information transmission date" is information indicating the date on which patient information was transmitted to another pharmacy when the patient has notified that the drug will be delivered at another pharmacy. .

The patient information database 284 is a database for holding patient information. The patient information database 284 is a database for holding patient's own information and patient's medication information. The patient information database 284 is a database for holding information indicating, for example, a patient's name, contact information, medication status, and the like. As shown in FIG. 4, each record in the patient information database 284 includes an item "Patient ID", an item "Patient Name", an item "Gender", an item "Age", an item "Contact Information", Includes the item "Status" and the item "Special notes." Each of the records in the patient information database 284 may be registered by a pharmacist when receiving a drug from a patient. The server 20 may add a record to the patient information database 284 by having the reception module 2033 accept input of patient information from the pharmacist on the terminal device 10 .

The item "patient ID" is information that identifies each patient. The item “Patient ID” is the same as the item “Patient ID” in the prescription database 281.

The item "patient name" is information indicating the patient's name.

The item "gender" is information indicating the gender of the patient identified by the item "patient ID."

The item "age" is information indicating the age of the patient identified by the item "patient ID."

The item "contact information" is information indicating the contact information of the patient identified by the item "patient ID."

The item "Status" is information indicating the delivery status of medicines to patients by pharmacists. Specifically, the item "Status" is information related to at least one of information indicating that the period for delivering medicine to the patient has arrived, and information indicating the patient's scheduled visit to the clinic.

The item “special notes” is information indicating noteworthy items regarding the patient. Specifically, the item "special notes" may be information indicating conditions for the patient to stop using the prescription again and decide to visit a medical institution. The item "special notes" may be information presented by the doctor who issued the prescription to the patient. The item "special notes" may be information input from a pharmacist via the terminal device 10.
<3. Operation＞

Hereinafter, with reference to FIGS. 5 to 8, a description will be given of a process in which the system 1 supports a pharmacist in explaining drugs to a patient.

FIG. 5 is a flowchart illustrating an example of a flow in which the system 1 according to the first embodiment calculates the timing at which medicine can be delivered to a patient and presents it to the user. The user here is at least one of a pharmacist and a patient. In the following, an example of a pharmacist as a user will be explained.

Here, the present system 1 is a system that targets a prescription that allows the issuance of a drug multiple times in one prescription. As an example, a prescription that allows delivery of medicine multiple times is a refill prescription. A prescription that allows multiple delivery of drugs is a prescription that allows the patient to receive the drug multiple times without having to visit a medical institution again until the predetermined upper limit is reached. Say something. The number of times a drug can be issued with one prescription may be determined by a doctor when a prescription is issued at a medical institution. Hereinafter, a description will be given of a prescription that allows the delivery of drugs multiple times.

In step S511, the terminal device 10 receives an operation from the pharmacist to input prescription information. The terminal device 10 inputs prescription information such as the date the prescription was received from the patient, the type of drug listed in the prescription, the prescription date, the number of prescription days, the patient name, and the possible prescriptions for the prescription. Receives an operation from the pharmacist to input information regarding the number of times. The terminal device 10 transmits the information accepted through the operation input by the pharmacist in S511 to the server 20 via the communication unit 120 or the like.

In step S521, the server 20 calculates the time when the medicine can be delivered based on the prescription information received in step S511. In step S521, the server 20 determines whether it is possible to issue the drug to the patient again based on the prescription. For example, the determination method may be as follows.
- If the number of times a prescription can be used is greater than the number of times the pharmacy has already received a prescription from a patient, it is determined that the drug can be delivered to the patient again.
The server 20 may specify the number of times the pharmacy has already received a prescription from a patient, for example, in any of the following ways.
- Receive input from pharmacists regarding the number of times the pharmacy has already accepted prescriptions from patients.
- By referring to the prescription database 281, the number of times the same prescription has been received is determined. For example, the server 20 extracts records whose item "prescription ID" matches each record stored in the prescription database 281. The server 20 identifies the extracted records as records in which the same prescription was received. The server 20 specifies the number of times prescriptions have already been accepted by adding up the number of extracted records.
The server 20 registers the calculated remaining number of times the prescription can be used in the prescription database 281.

In addition, in step S521, whether or not it is possible to issue the medicine again according to the prescription may be determined by the server 20 as described above, or an input operation may be received from the pharmacist. The pharmacist may determine whether or not it is possible to issue the drug again based on information on the prescription received from the patient. The terminal device 10 may receive an operation from the pharmacist to input the result determined by the pharmacist.

Further, if it is determined in step 521 that the medicine can be delivered again, the server 20 calculates the time when the medicine can be delivered again. In step S521, the server 20 calculates the timing based on the date the prescription was received from the patient and the number of prescription days, which are the information received in step S511, as a method of calculating the timing when the medicine can be delivered. . For example, the server 20 takes the date when delivery of the medicine is accepted as the starting date, and specifies the date obtained by adding the number of prescription days to the starting date as the delivery date of the next medicine. Furthermore, the server 20 sets the identified next drug delivery date as a reference date, and the server 20 sets the specified date of delivery of the next drug as a reference date, and specifies that the drug is delivered for at least one of a predetermined period including the reference date and a predetermined period before and after the reference date. This will be decided as the time when the issuance will be possible.

In step S522, the server 20 determines a reminder date for the patient based on the time when the medicine can be delivered, which was calculated in step S521. For example, the server 20 sets the start date of the medicine delivery period identified in step S521 as the starting date, and determines a timing a certain period before the starting date as the reminder date. For example, the server 20 sets the start date of the next medicine delivery period specified in step S521 as the starting date, and determines the timing 3 days before the starting date as the reminder date. Furthermore, in step S522, the server 20 presents the determined reminder date to the pharmacist. For example, the server 20 may present the determined reminder date to the patient. In step S522, the server 20 may add a record to the reminder database 282 in response to the determination of the reminder date.

In step S523, the server 20 presents the pharmacist with the time calculated in step S521 when the medicine can be issued and the reminder date determined in step S522. Here, the server 20 may present to the patient the time when the medicine can be delivered, calculated in step S521, and the reminder date determined in step S522.

In step S524, the server 20 determines that the timing is a predetermined period before the start date of the next drug issuance period, and determines the timing when the drug that will arrive after the predetermined period can be delivered to the terminal owned by the patient. The device 30 is notified. The server 20 uses the arithmetic module 2035 to compare the current date with the scheduled reminder date in the reminder database 282, and if the two match, determines that "the reminder date has arrived." For example, the server 20 determines the arrival of the reminder date based on the data stored in the reminder database 282, and notifies the patient's terminal device 30 of the timing when the medicine can be delivered after a certain period of time. Good too. The server 20 may determine that the reminder date has arrived and display the operating member on the display unit 160 of the terminal device 10. The server 20 may notify the patient's terminal device 30 of a time when the medicine can be delivered after a certain period of time in response to receiving an input to operate the operation member from the pharmacist.

In step S524, the server 20 may notify the terminal device 30 of the reminder using, for example, the patient's email address or SMS (Short Message Service). Further, the server 20 may notify the reminder by cooperating with an SNS (Social Network Service) used by the patient as a notification means. Here, the ID of the SNS used by the patient may be managed by the server 20. The pharmacist may designate a patient to whom a reminder is to be sent, but may not be able to view the patient's SNS ID or the like. Additionally, server 20 may contact the patient via an automated voice call.

In step S531, upon receiving the notification received from the server 20 in step S524, the terminal device 30 receives an operational input from the patient regarding information regarding the schedule for receiving the drug. For example, the terminal device 30 may receive input from the patient of information indicating the date and time of the patient's visit to the pharmacy. For example, the terminal device 30 may receive input from the patient of information indicating the pharmacy where the patient is scheduled to visit. The terminal device 30 sends the information accepted from the patient to the server 20 in step S531. The server 20 registers the information input by the terminal device 30 in step S531 into the contact history database 283.

It is not essential for the terminal device 30 to accept input from the patient regarding the schedule for receiving the medicine, and a configuration in which this input is not accepted is also possible. In this case, the patient may, for example, directly visit the pharmacy without notifying the pharmacy of his or her planned visit.

In step S512, the terminal device 10 receives an operational input of prescription information from the pharmacist. For example, the terminal device 10 may also receive operation input from a pharmacist of information indicating the track record of dispensing medicines to patients. The terminal device 10 receives, for example, an input from the pharmacist of information indicating at least one of the date and time of delivery of the medicine to the patient, and the type and amount of the medicine delivered.

Further, in step S512, the terminal device 10 may determine the time when the next medicine can be delivered and the date of the reminder to the patient, and present the determined time to the pharmacist. For example, the terminal device 10 is capable of re-issuing a drug based on the prescription based on information on the number of times the drug can be delivered based on the prescription and the number of times the pharmacy has accepted the delivery of the drug based on the prescription so far. Determine whether or not to do so. When the server 20 determines that it is possible to issue the medicine again, the server 20 may decide the time when the next medicine can be delivered and the date to remind the patient, and present it to the pharmacist.

Through the above series of processes, pharmacists can further enhance medication support for patients by calculating and presenting to pharmacists the timing when drugs can be delivered for prescriptions that allow multiple delivery of drugs. make it possible to Additionally, pharmacists can reduce the burden of explanations to patients. Furthermore, by notifying patients about medication delivery, it can be expected that the possibility of patients coming to the clinic will increase, and the need for pharmacists to individually remind patients can be reduced. In addition, by receiving reminder notifications, patients can reduce the likelihood of forgetting to receive their medication, allowing them to continue taking medication stably.

FIG. 6 shows the system 1 according to the first embodiment when, in a prescription that allows the delivery of drugs multiple times, the number of times the drug is delivered reaches the predetermined upper limit of the number of times the prescription can be used. 3 is a flowchart illustrating an example of processing of the system 1 in the case of FIG. Note that step S511 has the same content as in FIG. 5, so the description will not be repeated.

In step S621, the server 20 determines whether the drug can be delivered to the patient again based on the prescription information received in step S511. In step S621, the server 20 refers to the item “usable number of times” and the item “prescription ID” in the prescription database 281. The server 20 determines whether it is possible to issue a drug again according to the prescription, based on, for example, the number of times that the drug can be issued for the prescription and the number of times that the prescription has already been accepted for delivery. For example, if the number of times a prescription can be used matches the number of times the prescription has already been issued, the server 20 determines that the remaining number of times the prescription can be used is zero. For example, in a case where the number of times that medicines can be delivered for the prescription is the same as the number of times that medicines have already been delivered for the prescription, the server 20 determines that the medicines received in step S511 are the final medicines for the prescription. It is determined that the drug is issued. Note that the method for calculating the number of times delivery of medicines based on the prescription has already been accepted may be the same as the method described in step S521 of FIG. 5.

In step S622, the server 20 generates information for indicating to the patient a guideline for visiting the hospital in response to the determination in step S621. For example, the server 20 may generate information indicating the timing at which the medicine the patient is taking will run out, in order to generate information for indicating to the patient a guideline for visiting a hospital. Further, the server 20 may generate information indicating changes in physical condition, for example. For example, the server 20 may refer to at least one of the prescription database 281 and the patient information database 284 to generate information for indicating to the patient a guideline for visiting the above hospital. For example, the server 20 may generate information by calculating the timing at which the medicine runs out as described below.
・The date of receipt of the prescription is the starting date, and the period of taking the drug is added to the starting date.
For example, the server 20 may extract information indicating special notes regarding the patient from the patient information database 284 in order to generate information indicating changes in physical condition.

In step S623, the server 20 sends the information that there is no remaining usable prescription determined in step S621 and the information generated in step S622 to the terminal device 10, and sends the information to the pharmacist via this terminal device 10. present.

Through the series of processes described above, the pharmacist can more easily grasp the patient's medication status. At the time of accepting a prescription from a patient, the pharmacist can grasp the remaining number of uses of the prescription displayed on the display of the pharmacy, and therefore can provide appropriate medication guidance to the patient. In addition, the patient can understand the remaining number of uses of the prescription by receiving an explanation from the pharmacist, thereby reducing the possibility of accidentally visiting the pharmacy again.
<Screen example>

7 to 8 are diagrams showing examples of screens of the user's terminal device 10 or 30 in the first embodiment. FIG. 7 is a diagram showing an example of a screen of the terminal device 10 of a pharmacist who is a user in the first embodiment. FIG. 7 is a diagram showing a screen in which the terminal device 10 receives operational input of information from the pharmacist in step S511 of FIG.

As shown in FIG. 7, the display screen 131 displayed on the display unit 160 of the terminal device 10 includes an area 132, an area 133, an area 134, an area 135, and an operation member 136. Area 132 is an area for displaying patient's personal information. Area 133 is an area for receiving input of prescription information from the pharmacist. The pharmacist performs an operation to input prescription information into a portion of the display screen 131 corresponding to the area 133 via the input device 13, such as a keyboard. The terminal device 10 may detect that an operation input has been made in a portion corresponding to the area 133, and may accept the operation input from the pharmacist. When the display unit 160 is a touch panel, the pharmacist performs an operation of touching or clicking a portion of the display screen 131 that corresponds to the area 133. The terminal device 10 may detect that an operation input has been made in a portion corresponding to the area 133, and may accept the operation input from the pharmacist. The area 134 is an area for displaying the period during which the medicine can be delivered again and the scheduled date for notifying the patient of the reminder. The operation member 136 is an operation member that accepts an operation input for viewing a patient's past visit history.

In the example screen of FIG. 7, in response to the terminal device 10 receiving an operation input from the pharmacist in the area 133, the server 20 determines when the medicine can be delivered and when to notify the patient of the reminder. It is displayed on the display of the terminal device 10. In response to the terminal device 10 receiving an operation input from the patient indicating the reception date of the prescription and the number of prescription days from the patient as prescription information, the server 20 changes the area 134 of FIG. 7 to the terminal device 10. display it on the display.

Furthermore, the terminal device 10 displays in area 135 the possibility that the patient will visit the same pharmacy. The server 20 evaluates the possibility of a patient visiting the same pharmacy based on the patient's past visit history. For example, the server 20 refers to the prescription database 281 and the contact history database 283 to evaluate the possibility of a patient visiting the same pharmacy in multiple stages. The server 20 evaluates the possibility of a patient visiting the same pharmacy in multiple stages. It is evaluated that there is a high possibility of visiting the same pharmacy. In particular, the server 20 may evaluate the possibility of a patient visiting the same pharmacy highly as the ratio of the number of times the patient visits the same pharmacy to the number of times the patient receives medicines based on the same prescription is higher. Server 20 displays the evaluation results in area 135.

Further, the pharmacist performs an operation of touching or clicking the operation member 136. The terminal device 10 receives an input by detecting that an operation input is made to the operation member 136. In response to receiving the input, the terminal device 10 changes the display content displayed on the display unit 160 of the terminal device 10 from the content shown in FIG. 7 to content displaying the patient's visit history. This allows the pharmacist to refer to the patient's past history of visits to the pharmacy, allowing the pharmacist to accurately grasp the possibility of the patient visiting the same pharmacy. Therefore, the pharmacist can further utilize the possibility of the patient's visit to the clinic for drug inventory management.

FIG. 8 is a diagram showing an example of the screen of the terminal device 30 of the patient, who is the user, in the first embodiment. FIG. 8 is a diagram showing a screen of the terminal device 30 that receives notification from the server 20 about the arrival of the medicine delivery time in step S524 of FIG.

As shown in FIG. 8, the display screen 131 displayed on the display section of the terminal device 30 includes an area 137, an operating member 138, and an operating member 139. Area 137 is an area that shows schedule information regarding delivery of medicines to patients. The operation member 138 is an operation member for receiving an operation input from a patient regarding a schedule for receiving a medicine. The operating member 139 is an operating member for receiving an operation from the patient to input a schedule to visit a pharmacy different from the pharmacy where the medicine was most recently delivered.

The operation member 138 receives an operation input from the patient regarding the schedule for receiving the medicine. The operating member 138 may receive an operation from the patient to input a schedule for receiving medicine, for example, in step S531 of FIG. 5. For example, when a patient plans to receive a drug at the same pharmacy where the drug was recently delivered, the operating member 138 may receive an input operation from the patient indicating that he or she plans to visit the pharmacy. . For example, the terminal device 30 allows the patient to press the operation member 138 as an operation for changing the display content displayed on the display from the content shown in FIG. 8 to the display content for registering a schedule for receiving medicine. You may also accept operations to do so.

The operation member 139 may receive an operation input from the patient indicating that the patient plans to visit a pharmacy different from the pharmacy displayed in the area 137. A case in which a patient visits a different pharmacy will be explained in a second embodiment.

As described above, by the server 20 notifying the patient of the arrival of the period in which the medicine can be delivered, the patient can reduce the likelihood of forgetting to receive the medicine. Therefore, patients can continue to take their medication in a stable manner. Further, since the pharmacist receives notification from the patient of the scheduled visit to the pharmacy, it becomes possible to grasp the patient's scheduled visit and manage the inventory of drugs.

<Modified example>
As described above, the technology in which the server 20 determines the time when medicine can be delivered and the date to remind the patient and presents it to the user has been described. In addition to this, the following configuration may be used.

Method for accepting prescription information: Regarding step S511 in FIG. 5, the server 20 may accept prescription information as follows: Display the prescription information on the terminal device in the form of a two-dimensional code such as a QR code (registered trademark) or written on the prescription document in the form of a two-dimensional code such as a QR code (registered trademark), the two-dimensional code is read by a reading device. The server 20 acquires the information read through the two-dimensional code.
- The server 20 reads prescription information using at least one of a scanner or a digital camera, and obtains information obtained by converting characters written on the prescription into character codes.
- The server 20 receives prescription information received via the terminal of the medical institution that issued the prescription.
- Information on prescriptions issued by medical institutions is stored in a server, and the terminal device 10 acquires prescription information by accessing the server.

Setting multiple reminder dates: In step S522 of FIG. 5, the server 20 may set multiple reminder dates for the patient. For example, in a case where the time when medicines can be delivered is set over multiple days, the server 20 may set a timing a certain period before the time when medicines can be delivered as the first reminder date. good. Furthermore, the server 20 may set the timing after the start and before the end of the time when the medicine can be delivered as the second reminder date. If a pharmacist issues a drug to a patient after the first reminder date and before the second reminder date, the server 20 does not notify the patient of the reminder set on the second reminder date. Good too. If the pharmacist issues the drug to the patient after the first reminder date and before the second reminder date, the terminal device 10 will set the second reminder date in step S512 of FIG. An operation input to cancel the reminder may be received from the pharmacist.

Method for determining reminder date and reminder content: Regarding the determination of the reminder date for the patient in step S522 of FIG. 5, the server 20 may determine the reminder date based on the patient's behavior history. The server 20 may, for example, refer to information stored in at least one of the prescription database 281, the reminder database 282, and the contact history database 283 to identify the behavior history of each patient. For example, the server 20 may determine a certain period of time before a predetermined day of the week or date as a reminder date for a patient who appears to visit the hospital frequently on a predetermined day of the week or date based on the patient's behavior history. For example, the server 20 may decide to further increase the number of reminders for a patient who, based on the patient's behavior history, seems to have a high frequency of forgetting to receive medication. The server 20 may use the following method to determine the number of times a patient has forgotten to receive medicine. First, among the records having the same prescription ID, the server 20 determines the record with the latest reception date. The server 20 extracts records whose “remaining count” value is 1 or more from among the records to be determined. The server 20 adds up the number of records for which the "next drug delivery period" has already passed among the extracted records. The server may determine that the accumulated number of records indicates the number of times the patient has forgotten to receive medication. The server 20 refers to the prescription database 281 and determines whether the patient will receive the medication if the number of times the patient has forgotten to receive the medication is high compared to the number of times the patient has visited the hospital. It may be determined that the frequency of forgetting is high. Further, the server 20 may, for example, decide to add information indicating the patient's follow-up to the content of the reminder notification for a patient who is unlikely to visit the same pharmacy based on the patient's behavior history. You can. A method for determining the possibility of a patient visiting the same pharmacy will be described later. For example, the server 20 may decide to add the following as information indicating the follow-up observation of the patient.
・Physical condition and medication status as determined by pharmacist interviews with patients when they visited our office in the past.
・Results of patient physical condition checks conducted by pharmacists when patients visited our office in the past.

The server 20 may determine the reminder date as follows. The server 20 may determine the reminder date based on the content of the notification received from the patient. For example, the server 20 may determine the reminder date based on the scheduled date of the patient's visit to the pharmacy, which is the content input from the patient in step S531 of FIG. 5. The server 20 may determine a certain period of time before the patient's scheduled visit to the pharmacy as the reminder date.

As a result, the patient can receive a reminder notification from the pharmacist according to his/her own action history and the scheduled date of visit, thereby further reducing the possibility of forgetting to pick up the medicine. Pharmacists can expect that patients will be more likely to visit the same pharmacy. This increases the possibility that pharmacists can continue to monitor patients.

<Second embodiment>
In the above embodiment, it has been explained that the server 20 determines when the medicine can be delivered and when to remind the patient in a prescription that allows the medicine to be delivered a plurality of times. In the above embodiment, it has been further explained that the server 20 receives a notification from the patient regarding the schedule for receiving the medicine as a response to the reminder sent to the patient.

In the following embodiment, the server 20 is used when the server 20 receives a response from the patient to the patient's reminder that the patient will receive the drug at a pharmacy different from the pharmacy where the drug was most recently delivered. The processing will be explained.

FIG. 9 is a flowchart showing an example of a case in which a response is received from a patient indicating that the drug will be delivered at a pharmacy different from the pharmacy where the drug was most recently delivered, according to the second embodiment. Note that step S524 has the same content as in FIG. 5, so the description will not be repeated. Further, the terminal device 10 shown in FIG. 9 will be described below assuming that it is installed in a pharmacy where a patient is scheduled to visit or is operated by a pharmacist or the like at the pharmacy.

In step S931, the terminal device 30 receives, as a response to the notification received from the server 20 in step S524, an input from the patient indicating that the drug is scheduled to be delivered at a pharmacy different from the pharmacy where the drug was most recently delivered. accept. Further, the terminal device 30 receives and notifies an input from the patient of a schedule to receive medicine. In step S931, the terminal device 30 performs an operation from the patient to change the display content displayed on the display from the content shown in FIG. 8 to the display content for registering the schedule for receiving the drug. An operation of pressing down the member 139 may also be accepted. For example, the terminal device 30 may receive input from the patient of information indicating the pharmacy to which the patient plans to visit. The terminal device 30 transmits information input from the patient to the server 20.

In step S921, the server 20 registers the input content that the terminal device 30 received from the patient and transmitted to the server 20 in step S931. The server 20 may register the input content received from the terminal device 30 in the reminder database 282.

In step S922, the server 20 generates an access right for a page displaying the patient's medication status for the terminal device 10 related to the pharmacy specified via the terminal device 30 in step S931. For example, the server 20 generates, for the patient who specified the pharmacy in step S931, an access right to the page displaying the patient's medication status, which is displayed on the screen of FIG. For example, the server 20 identifies the pharmacy where the patient is scheduled to visit from the information received from the patient in step S931. The server 20 configures the terminal device 10 of the specified pharmacy so that a page displaying the patient's medication status can be viewed. The server 20 adds, for example, the ID of the terminal device 10 of the specified pharmacy to the database of the storage unit in which viewable IDs of pages displaying the patient's medication status are stored. The server 20 notifies the pharmacist of the pharmacy where the patient is scheduled to visit via the terminal device 10 that the access right has been granted. For example, in addition to presenting the fact that access rights have been granted, the server 20 may do the following.
- Provide the pharmacist with a password to access the page that displays the patient's medication status.
- Present the URL of the page that displays the patient's medication status to the pharmacist.

In step S911, the terminal device 10 receives an operation from the pharmacist to access a page displaying the patient's medication status.

In step S923, the server 20 displays patient information on the display of the terminal device 10 in response to receiving the operation from the pharmacist in step S911. For example, the server 20 presents the pharmacist with a page that displays the patient's medication status.

As a result of the above, even if a patient does not receive the drug at the same pharmacy, the pharmacist who is planning to issue the drug to the patient will not be able to share information indicating the patient's drug usage status with other pharmacists. You can receive it. Therefore, pharmacists are more likely to be able to continue to monitor patients. Furthermore, the pharmacist can provide medication guidance to each patient in accordance with the patient's situation.

FIG. 10 is a flowchart showing an example of the flow when using the patient's terminal device 30 to share patient information with other pharmacists in the second embodiment. Note that step S524, step S931, and step S921 are the same as those in FIG. 9, so the description will not be repeated. Further, the terminal device 10 in FIG. 10 will be explained below assuming that it is a terminal device of a pharmacy to which the patient has recently received medicine.

In step S1021, the server 20 notifies the terminal device 10 of information that the patient is scheduled to receive medicine at another pharmacy based on the information registered in step S921. For example, the server 20 may notify the terminal device 10 of information indicating another pharmacy where the patient is scheduled to visit. For example, the server 20 may notify the terminal device 10 of information indicating the date and time when the patient is scheduled to visit another pharmacy.

In step S1011, the terminal device 10 receives an input of information about the patient to be shared with a pharmacist at another pharmacy from the pharmacist who most recently delivered the medicine to the patient. The terminal device 10 may, for example, receive input from the pharmacist of at least one of the patient's medication status, information indicating the patient's physical condition, and other matters to be submitted. In step S1011, when the terminal device 10 receives information to be shared with a pharmacist at another pharmacy from the pharmacist, the terminal device 10 may display information indicating the patient's medication status on the display. Then, the terminal device 10 transmits the information received in step S1011 to the server 20. The terminal device 10 transmits information to the server 20 in response, for example, by receiving an operation of pressing a member from the pharmacist.

In step S1022, the server 20 transmits the information input from the pharmacist through the terminal device 10 in step S1011 to the terminal device 30 owned by the patient. The server 20 may transmit information about the patient extracted from at least one of the prescription database 281 and the patient information database 284 to the terminal device 30. The server 20 may record at least part of the information to be transmitted to the terminal device 30 in a two-dimensional code, and transmit data for displaying this two-dimensional code on the terminal device 30. .

In step S1031, the terminal device 30 displays the information received from the server 20 in step S1022 on the display unit. For example, when a patient receives medicine, the terminal device 30 displays information on the display section and presents it to the patient. For example, the terminal device 30 may display the two-dimensional code generated in step S1022 on the display unit.

As described above, when distributing medicine, the pharmacist can check the information displayed on the patient's terminal device 30 indicating the patient's medication status. Therefore, the pharmacist can grasp the patient's past medication status, and can provide medication guidance tailored to each patient. Further, even if the pharmacist does not know the pharmacy where the patient visits, the pharmacist can check the patient's medication status via the patient's terminal device 30 when the patient visits the clinic. Furthermore, when a two-dimensional code is displayed on the patient's terminal device 30, the pharmacist can read the two-dimensional code displayed on the patient's terminal device 30 via the terminal device 10. Therefore, the pharmacist can easily acquire information.

In FIG. 9, in addition to granting access rights to the patient's personal page, for example, the server 20 may transmit information indicating the patient's medication status to the terminal device 10.

<Screen example>
FIG. 11 is a diagram showing an example screen of the pharmacist's terminal device 10 in the second embodiment. FIG. 11 is a diagram showing a screen displayed on the display unit 160 of the pharmacist's terminal device 10 in step S923 of FIG.

As shown in FIG. 11, the display screen 131 displayed on the display unit 160 of the terminal device 10 includes an area 140, an area 141, an area 142, an area 143, and an operation member 144. Area 140 is an area for displaying patient information. Area 141 is an area for displaying patient's prescription information. The area 142 is an area for displaying the period during which the drug can be delivered again according to the prescription. The area 143 is an area for displaying transfer items as information to be shared between pharmacies or pharmacists. The operating member 144 is an operating member for receiving an operating input from the user to send the information displayed on the display screen 131 to another terminal device 10.

FIG. 11 shows that, for example, when the terminal device 10 receives an operation from a pharmacist to present information indicating the patient's medication status, the server 20 transmits information to the terminal device 10 in step S923 of FIG. , which is an example of a screen displayed on the display unit 160 of the terminal device 10. Alternatively, the operation member 144 can transmit the information displayed on the display of the terminal device 10 to another terminal device by receiving an operation input from the pharmacist.

Further, FIG. 11 may be a diagram showing an example of the screen of the patient's terminal device 30. FIG. 11 may be a diagram showing a screen displayed on the display unit of the patient's terminal device 30 based on the data transmitted by the server 20 to the terminal device 30 in step S1022 of FIG. 10. As the screen displayed on the display section of the patient's terminal device 30 in FIG. 11, the two-dimensional code generated in step S1022 in FIG. 10 may be displayed instead of the operating member 144. By having another terminal device read the two-dimensional code displayed on the display section of the terminal device 30, the information can be displayed on the display section of the terminal device that read the two-dimensional code.

As a result of the above, the pharmacist can easily grasp the patient's past medication delivery status and medication taking status. Therefore, even if the same pharmacist is unable to continuously deliver medicines to a patient, the pharmacist can provide medication guidance according to the patient's situation.
<Modified example>

The case in which input of information is received from the patient in step S931 of FIG. 9 is not limited to receiving input from the patient as a response to the reminder notification to the patient in step S524. Before receiving the reminder notification, the terminal device 30 may receive an input from the patient that the patient plans to visit another pharmacy. For example, the terminal device 30 may receive input from the patient of information for specifying the pharmacy that the patient plans to visit.

In step S1022 of FIG. 10, the server 20 may notify the terminal device 30 of the information by email to the patient's email address or by SMS (Short Message Service). The server 20 may also notify the patient of information by using an SNS (Social Network Service) used by the patient as a means of notifying the patient. Here, the ID of the SNS used by the patient may be managed by the server 20. The pharmacist can specify the patient to whom the reminder is to be sent, but may also set the patient's SNS ID etc. to not be viewable.

<Third embodiment>
In the above embodiment, in the case of a prescription that allows the delivery of the drug multiple times, the server 20 determines when the drug can be delivered and when to remind the patient. explained. In addition, in the above description of the embodiment, when a response is received from a patient stating that the drug will be delivered at a pharmacy different from the pharmacy where the drug was most recently delivered, information regarding the patient's taking of the drug will be exchanged between the pharmacies. Explained about sharing information.

In the embodiment below, in the case of a prescription that allows delivery of the drug multiple times, the pharmacist determines to stop delivering the drug to the patient even though the number of times the prescription can be used remains. An example of the processing of the server 20 in this case will be described.

FIG. 12 is a flowchart showing the process in the third embodiment when the pharmacist determines to stop delivering medicine to the patient.

In step S1211, the terminal device 10 receives an operation input from the pharmacist to cancel delivery of the medicine. In step S1211, the terminal device 10 receives an operation input for stopping delivery of medicine from a pharmacist who has determined to stop delivering medicine to the patient due to a change in the patient's physical condition, for example. The terminal device 10 also receives an operation input for canceling the delivery of the drug from a pharmacist who has decided to stop delivering the drug to the patient due to the patient's request that symptoms of side effects have appeared, for example. may be accepted. Further, the terminal device 10 is configured to, for example, cause a pharmacist who has determined that the patient should change the medication to take due to a change in the patient's physical condition to stop issuing the medication to the patient. may also accept operation input. Then, the terminal device 10 notifies the server 20 that there has been an operation input from the pharmacist to cancel delivery of the medicine. The server 20 may store the date and time of the operation input from the pharmacist in the prescription database 281.

In step S1221, in response to receiving the notification from the terminal device 10 in step S1211, the server 20 sends information on the medication intake status and prescription to the patient who received the operational input to discontinue delivery of the medication. is extracted from the prescription database 281 and patient information database 284. The server 20 extracts, for example, information indicating the patient's medication intake period and prescription date, and information indicating the type of medication the patient is taking from the prescription database 281 and the patient information database 284.

In step S1222, the server 20 generates a contact form for contacting the doctor. For example, the server 20 inputs the patient information extracted in step S1221 into a predetermined form for contacting the doctor. Furthermore, the server 20 generates data for displaying a contact form with patient information input on the terminal device 10, and presents this data to the pharmacist via the terminal device 10.

In step S1212, the terminal device 10 displays the doctor contact form generated in step S1222 and sent to the terminal device 10 on the display unit 160 of the terminal device 10, and in this state, the terminal device 10 displays the doctor contact form generated in step S1222 and sent to the terminal device 10, and in this state, the terminal device 10 displays the doctor contact form generated in step S1222 and sent to the terminal device 10. Receives operation input from the pharmacist. For example, the terminal device 10 may receive, from the pharmacist, an operation input of information indicating the reason for the decision to stop dispensing the medicine, as an operation input for accepting an item to be sent to a doctor. Then, the terminal device 10 transmits information related to the operation input received in step S1212 to the server 20.

In step S1223, the server 20 transmits the doctor contact form that received input from the pharmacist in step S1212 to the doctor's terminal device 10B. Further, the server 20 registers, for example, the information received from the pharmacist in step S1212 in the patient information database 284.

As a result, the doctor can grasp information about the pharmacist's discontinuation of dispensing drugs to the patient, so that when the patient visits the medical institution again, the doctor can provide a medical examination that is more tailored to the patient's situation.

Regarding the pharmacist's decision to stop dispensing medicine to the patient in step S1211, the server 20 may accept in advance input of conditions for determining discontinuation from the doctor who examined the patient. For example, the terminal device 10B in FIG. 12 receives in advance an operation from a doctor to input information indicating conditions for deciding to stop delivering medicine to a patient. Further, the server 20 registers information received from the doctor in the patient information database 284. The server 20 displays the information received from the doctor on the display of the terminal device 10 in step S1211 of FIG. 12, when the pharmacist determines whether to stop dispensing medicine to the patient. As a result, the pharmacist can easily decide to stop dispensing the medicine to the patient because the pharmacist has been provided with the information in advance by the doctor.

In the following cases, the terminal device 10B owned by the doctor may receive an operation input from the doctor to cancel delivery of the medicine even though the number of times the prescription can be used remains.
・When a doctor determines that it is not appropriate to continue dispensing drugs according to the prescription to the patient based on the results of a patient's examination at the hospital.
- When a doctor determines that the medication the patient is taking should be changed based on the results of the patient's examination at the hospital.
The terminal device 10B owned by the doctor may receive input from the doctor of information identifying the prescription and information indicating discontinuation of use of the prescription. The terminal device 10B transmits information accepted through the operation input by the doctor to the server 20 via the communication unit 120. The server 20 presents the information received from the terminal device 10B to the pharmacist via the terminal device 10. The server 20 registers the information received from the terminal device 10B in at least one of the prescription database 281 and the patient information database 284. Further, the server 20 may register the date and time of receiving the information from the terminal device 10B in the prescription database 281. Here, the terminal device 10 owned by the pharmacist may receive an input from the pharmacist to cancel the setting of the reminder notification for the patient. The terminal device 10 transmits information received through input by a pharmacist to the server 20 via the communication unit 120, for example. The server 20 receives the input content received from the terminal device 10 via the reception module 2033. The server 20 may extract the record of the prescription stored in the reminder database 282 from the received input contents, and delete the data stored in the item "scheduled reminder date." The server 20 may extract the record of the prescription stored in the reminder database 282 from the received input contents, and delete the data stored in the item "Re-reminder scheduled date". As described above, the pharmacist can grasp the patient's medication status by obtaining information from the doctor to discontinue delivery of prescription drugs. Moreover, the pharmacist can avoid issuing drugs to patients who come to the office by mistake. Further, by canceling the reminder notification set for the patient by the pharmacist, it is possible to avoid sending unnecessary reminder notifications to the patient.

Furthermore, the pharmacist may obtain information from the doctor to discontinue delivery of prescription drugs by using at least one of communication methods such as telephone and fax. Additionally, the pharmacist may obtain information from the patient that the doctor has stopped dispensing prescription drugs. For example, the pharmacist may obtain information for the doctor to stop dispensing prescription drugs from the patient through at least one of a telephone and a fax. As a response to the reminder sent to the patient in step S524 in FIG. 5, the pharmacist may obtain information from the patient to discontinue delivery of prescription drugs. In these cases, the server 20 may receive an operational input from the pharmacist, including information for identifying the prescription, to the effect of discontinuing delivery of the drug based on the prescription, via the terminal device 10 owned by the pharmacist. The server 20 receives the input content received from the terminal device 10 via the reception module 2033. The server 20 may extract the record of the prescription stored in the reminder database 282 from the received input contents, and delete the data stored in the item "scheduled reminder date." The server 20 may extract the record of the prescription stored in the reminder database 282 from the received input contents, and delete the data stored in the item "Re-reminder scheduled date."

Further, although an example has been described in which the server 20 presents the contact form to the terminal device 10 in step S1222 of FIG. 12, the present invention is not limited to this. For example, the server 20 may output a contact form for contacting a doctor on paper. This makes it easy for pharmacists to contact doctors by fax. Furthermore, in step S1222 of FIG. 12, while displaying the extracted patient information on the display of the terminal device 10, the server 20 may also display the contact information of the doctor who examined the patient. This reduces the burden on the pharmacist to explain the patient's situation to the doctor over the phone.

<Fourth embodiment>
In the above embodiment, in the case of a prescription that allows the delivery of the drug multiple times, the server 20 determines when the drug can be delivered and when to remind the patient. explained. Furthermore, in the above description of the embodiment, processing according to the patient's response to the reminder notified to the patient has been described. Furthermore, we also explained the process when a pharmacist cancels the delivery of medicines.

In the following embodiment, an example will be described in which the server 20 displays a page for managing schedules for patient visits, reminders to patients, and drug inventory management to the pharmacist. Specifically, in response to receiving a designation operation from the pharmacist, the server 20 displays the schedule for the period designated by the pharmacist.

FIG. 13 is a flowchart showing an example of the flow of displaying a schedule managed by a pharmacist in the fourth embodiment.

In step S1311, the terminal device 10 receives an operation input specifying a pharmacy ID and an arbitrary period from the pharmacist. For example, the terminal device 10 may receive an operation from a pharmacist to specify a specific date or week as a period. The terminal device 10 transmits the pharmacy ID received in step S1311 and information specifying an arbitrary period to the server 20.

In step S1321, the server 20, based on the pharmacy ID and period specified by the pharmacist in step S1311, schedules delivery of drugs to patients associated with these pharmacy IDs and periods, and schedules delivery of drugs to patients. Information indicating the reminder implementation schedule is extracted from the reminder database 282. For example, in addition to the above information, the server 20 may also extract information on prescriptions associated with the patient from the prescription database 281.

In step S1322, the server 20 causes the display of the terminal device 10 to display information indicating the schedule for delivery of medicine to the patient extracted in step S1321. The server 20 causes the display of the terminal device 10 to display information indicating the patient reminder schedule extracted in step S1321. The server 20 may also display on the terminal device 10 the type of medicine and the amount of medicine required during the period in which the specification is accepted, based on the prescription information extracted in step S1321. For example, among the prescription information extracted in step S1321, the server 20 aggregates information indicating the specifications and quantities of drugs to be delivered to patients for each type of drug, and uses the information as information indicating the amount of necessary drugs in stock. , may be displayed on the display of the terminal device 10.

<Screen example>
FIG. 14 is a diagram showing an example of a screen displayed on the display unit 160 of the terminal device 10 in the fourth embodiment. FIG. 14 is a diagram showing an example of a screen displayed on the display unit 160 of the terminal device 10 in step S1322 of FIG. 13, for example.

The example screen in FIG. 14 is a diagram showing a display for grasping the schedule for delivering medicine to the patient and the schedule for reminding the patient in an arbitrary period specified by the pharmacist. As shown in FIG. 14, the display screen 131 displayed on the display unit 160 of the terminal device 10 includes an area 145, an area 146, an area 147, an operation member 148, and an area 149. Area 145 is an area for displaying the pharmacy and period for which the pharmacist's designation was received in step S1311 of FIG. 13. Area 146 is an area for displaying patients to whom medicines are scheduled to be delivered during the period whose designation is received from the pharmacist. The area 147 is an area for displaying patients who are scheduled to receive reminder notifications during the period for which the pharmacist's designation is received. The operating member 148 is an operating member that receives an operating input from the pharmacist for starting the process of contacting the patient displayed in the area 147. The area 149 is an area for displaying the type and total amount of drugs predicted to be required for a period specified by the pharmacist.

This allows the pharmacist to grasp information on patients to whom medicines are scheduled to be delivered and patients to whom reminder notifications are scheduled for the specified period. Further, when the pharmacist presses the operation member 148 provided for each patient, the pharmacist can start the process of contacting the patient, so it is possible to easily contact the patient. Furthermore, since the type and total amount of drugs required for a specified period can be ascertained, pharmacists can easily manage the inventory of necessary drugs. For example, by referring to the patient visit prediction displayed in the area 135 of FIG. 7, the pharmacist can more accurately grasp the type and amount of the necessary drug. Further, by referring to the patient's visit history displayed by pressing the operating member 136 in FIG. 7, the pharmacist can more accurately grasp the type and amount of the necessary drug. Particularly, when a special drug is scheduled to be delivered to a patient, the pharmacist can avoid a situation where the drug cannot be delivered to the patient due to an out-of-stock drug even though the patient comes to the office.

<Additional notes>
The matters described in each of the above embodiments are additionally described below.

(Additional Note 1) A program that is executed by a computer including a processor and a memory, the program causes the processor to acquire first information indicating the contents of a prescription for prescribing a drug to a patient. Step (step S511), if the prescription is a prescription that allows delivery of the drug a predefined number of times, and the number of times the drug is delivered according to the prescription has not reached the upper limit of the number of times specified; , a second step (step S521) of calculating, based on the first information, the time when the patient will receive the drug based on the prescription; and a third step of presenting the time calculated in the second step to the user. A program that executes step (step S523).

(Additional Note 2) The program further causes the processor to execute a fourth step (step S524) of notifying the patient of the time to receive the drug calculated in the second step, as described in (Additional Note 1). program.

(Additional Note 3) The program according to (Additional Note 2), wherein in the fourth step, the patient is notified of the time to receive the drug a certain period of time before the time to receive the drug.

(Additional note 4) The program further causes the processor to receive input from the patient of information related to receiving the drug in response to the notification to the patient in the fourth step, and to notify the pharmacist of the received information. The program according to (Appendix 2) or (Appendix 3), which causes the step (step S531) to be executed.

(Additional note 5) In the fourth step, the timing of notifying the patient is determined based on at least one of the patient's behavioral history or the information to be notified to the pharmacist in the fifth step. program.

(Additional Note 6) The program further includes a step of receiving a designation of a predetermined period from the pharmacist, and, in response to receiving the designation of the predetermined period from the pharmacist, registering the program in association with the specified period. The program described in (Appendix 1) or (Appendix 2) that executes the sixth step (step S1322) of causing the pharmacist to present information regarding the pharmacist's schedule based on delivery of medicines to patients.

(Additional note 7) In the sixth step, information regarding the pharmacist's schedule is presented to the pharmacist, such as delivering the medicine to the patient who comes to the pharmacy, the pharmacist notifying the patient when to receive the medicine, or , the program according to Supplementary Note 6, wherein the program presents information regarding at least one schedule of the group consisting of: , inventory management of necessary drugs to a pharmacist.

(Additional note 8) The program further receives a notification from the patient to the processor that the pharmacist who is scheduled to issue the medication to the patient will not be able to view the information about the patient's most recent prescription medication delivery. In this case, the seventh step (steps S923 and S1031) of presenting information regarding the history of delivery of drugs based on prescriptions to at least one of the patient and the pharmacist who is scheduled to deliver the drugs to the patient is executed (Appendix 1). ).

(Additional Note 9) The program shall further allow the processor to receive a notification from the patient that the pharmacist who is scheduled to issue the medication to the patient will not be able to view the information regarding the patient's most recent prescription medication delivery. If we receive a notification from a patient that he plans to visit a pharmacy other than the one where he most recently received prescription drugs, we will collect information about the history of receiving prescription drugs from the patient. Alternatively, the program according to (Appendix 8) causes the program to execute the seventh step of presenting the drug to at least one of the pharmacists who are scheduled to deliver the drug to the patient.

(Appendix 10) In the seventh step, the pharmacist receives a notification from the patient, and in the fourth step, the pharmacist receives a notification in response to the notification to the patient (Appendix 8) or (Appendix 9) The program described in.

(Additional note 11) The program further causes the processor to respond to the acquisition of the first information in the first step when the number of prescription drug deliveries has reached the predetermined upper limit of multiple times. The program according to Supplementary Note 1, wherein the program executes the eighth step (S623) of notifying the user that the prescribed number of times the prescription drug is delivered has reached the upper limit.

(Additional Note 12) The program according to (Additional Note 11), in which, in the eighth step, information for indicating to the patient a guideline for the patient to visit a medical institution is presented to the user (step S623).

(Additional note 13) The program further prompts the processor to discontinue dispensing drugs to the patient according to the prescription even though the number of dispensing drugs according to the prescription has not reached the specified upper limit of multiple times. A ninth step (step S1211) of accepting an input from the pharmacist, and a tenth step (step S1222) of starting a process for contacting a medical institution in response to receiving the input (Additional Note 1) ).

(Additional Note 14) The program according to (Additional Note 13), wherein in the ninth step, the program presents to the pharmacist information necessary for making a decision to stop delivering the drug to the patient according to the prescription.

1: System 10: Terminal device 13: Input device 14: Output device 15: Memory 16: Storage section 19: Processor 20: Server 25: Memory 26: Storage 29: Processor 30: Terminal device 80: Network 120: Communication section 130: Operation reception section 131: Display screen 171: Prescription information 172: Patient information 180: Control section 181: Input operation reception section 182: Transmission/reception section 183: Display control section 184: Notification control section 201: Communication section 202: Storage section 203: Control Department 281: Prescription database 282: Reminder database 283: Contact history database 284: Patient information database 2031: Reception control module 2032: Transmission control module 2033: Reception module 2034: Usage frequency determination module 2035: Calculation module 2036: Presentation module

Claims (16)

A program that is executed by a computer including a processor and a memory,
The program causes the processor to:
a first step of acquiring first information indicating the contents of a prescription for prescribing a drug to a patient;
If the prescription is a prescription that allows delivery of the drug a predefined number of times, and the number of times the drug is delivered according to the prescription has not reached the predetermined upper limit of the number of times,
a second step of calculating, based on the first information, when the patient will receive the drug based on the prescription;
A program that executes a third step of presenting the time calculated in the second step to a user. 2. The program according to claim 1, wherein the program further causes the processor to execute a fourth step of notifying the patient of the time to receive the drug calculated in the second step. 3. The program according to claim 2, wherein in the fourth step, the patient is notified of the time to receive the drug a certain period of time before the time to receive the drug. The program further causes the processor to:
In response to the notification to the patient in the fourth step, a fifth step of receiving input of information regarding receiving the drug from the patient and notifying the pharmacist of the received information is requested. The program described in Section 2. The program according to claim 4, wherein in the fourth step, the timing of notifying the patient is determined based on at least one of the patient's action history or the information to be notified to the pharmacist in the fifth step. . The program further causes the processor to:
a step of receiving a designation of a predetermined period from a pharmacist;
In response to receiving the designation of the predetermined period from the pharmacist, information regarding the pharmacist's schedule based on the delivery of the drug to the patient, which is registered in association with the designated period, is presented to the pharmacist. The program according to claim 2, which causes the program to execute the sixth step of causing the computer to perform the program. In the sixth step, the information regarding the schedule of the pharmacist is presented to the pharmacist, such as delivering the medicine to the patient who comes to the pharmacy, the pharmacist notifying the patient when to receive the medicine, or the pharmacist's schedule. 7. The program according to claim 6, wherein the program presents information regarding at least one schedule of the group consisting of inventory management of drugs to the pharmacist. The program further causes the processor to:
If a notification is received from the patient that the pharmacist who is scheduled to issue the drug to the patient will not be able to view information about the patient's recent delivery of the drug according to the prescription, 5. The program according to claim 4, which causes the program to execute a seventh step of presenting information regarding a history of delivery of the drug to at least one of the patient and a pharmacist who is scheduled to deliver the drug to the patient. The program further causes the processor to:
Receiving from the patient a notification that the pharmacist who is scheduled to issue the drug to the patient will not be able to view information about the patient's recent delivery of the drug according to the prescription, and the patient: If a notification is received from the patient that he plans to visit a pharmacy different from the pharmacy where the drug was most recently delivered based on the prescription, the patient or 9. The program according to claim 8, causing the program to execute the seventh step of presenting the drug to at least one pharmacist who is scheduled to issue the drug to the patient. The program according to claim 8, wherein in the seventh step, the pharmacist receives a notification from the patient, and in the fourth step, the pharmacist receives a notification in response to the notification to the patient. . The program further causes the processor to:
In a case where the number of deliveries of the medicine according to the prescription has reached the upper limit of the prescribed plurality of times, in response to acquiring the first information in the first step, the medicine according to the prescription is delivered. 2. The program according to claim 1, wherein the program executes an eighth step of notifying the user that the number of issuances has reached the predetermined upper limit of the plurality of times. 12. The program according to claim 11, wherein in the eighth step, information for indicating to the patient a guideline for the patient to visit a medical institution is presented to the user. The program further causes the processor to:
Even though the number of times the drug is delivered according to the prescription has not reached the specified upper limit of multiple times,
a ninth step of receiving from a pharmacist an input for discontinuing delivery of the drug to the patient according to the prescription; and a tenth step of starting a process for contacting a medical institution in response to receiving the input. The program according to claim 1, which performs the steps of. In the ninth step,
14. The program according to claim 13, wherein the program presents to the pharmacist information necessary for making a decision to stop delivering the drug to the patient according to the prescription. A method for causing a computer comprising a processor and a memory to execute the process,
The method includes the processor:
a first step of acquiring first information indicating the contents of a prescription for prescribing a drug to a patient;
If the prescription is a prescription that allows delivery of the drug a predefined number of times, and the number of times the drug is delivered according to the prescription has not reached the predetermined upper limit of the number of times,
a second step of calculating, based on the first information, when the patient will receive the drug based on the prescription;
a third step of presenting the time calculated in the second step to the user;
How to do it. An information processing device including a control unit and a storage unit,
The control unit includes:
a first step of acquiring first information indicating the contents of a prescription for prescribing a drug to a patient;
If the prescription is a prescription that allows delivery of the drug a predefined number of times, and the number of times the drug is delivered according to the prescription has not reached the predetermined upper limit of the number of times,
a second step of calculating, based on the first information, when the patient will receive the drug based on the prescription;
a third step of presenting the time calculated in the second step to the user;
An information processing device that executes.