JP2021041138A - Information processing device and program - Google Patents

Abstract

To assist execution of more satisfactory follow up.SOLUTION: An information processing device comprises: means for storing patient identification information for identifying a patient and patient contact address information on a contact address of the patient in association with each other; means for receiving, from a user, designation of the content of follow up for a first patient for whom medicine has been prepared; and means for presenting information corresponding to the content of the follow up.SELECTED DRAWING: Figure 3

Description

The present invention relates to an information processing device and a program.

Pharmacists and pharmacies are expected to provide appropriate follow-up to patients who have dispensed the drug during the period of administration. Follow-up includes, for example, confirmation of the presence or absence of effects, confirmation of the presence or absence of side effects, confirmation of the medication status, guidance in these, and the like. Since pharmacists and pharmacies are usually responsible for a large number of patients, the burden of managing follow-up implementation for each patient is very high.

As a technique for supporting medication instruction after dispensing, for example, in Patent Document 1, a sensor of a drug container detects a patient's medication movement during the administration period, and the medication history is distributed to a dispensing pharmacy terminal. The medication management system is described. The medication management system can further send a medication guidance message according to the medication history to the patient terminal.

JP-A-2019-76119

In Patent Document 1, since the medication instruction is limited to the content according to the medication history (for example, the content related to the dosage usage such as the medication reminder), the content is not always sufficient as a follow-up after dispensing.

One of the objects of the present invention is to support the implementation of a more fulfilling follow-up.

One aspect of the present invention is
A means for associating and storing the patient identification information for identifying the patient and the patient contact information regarding the patient's contact information is provided.
Provided a means for accepting the specification of follow-up contents for the first patient to whom the drug was dispensed from the user.
A means for presenting information according to the content of the follow-up is provided.
It is an information processing device.

According to the present invention, it is possible to support the implementation of a more fulfilling follow-up.

It is a block diagram which shows the structure of the information processing system of this embodiment. It is a functional block diagram of the information processing system of FIG. It is explanatory drawing of the outline of this embodiment. It is a figure which shows the data structure of the dispenser information database of this embodiment. It is a figure which shows the data structure of the patient information database of this embodiment. It is a figure which shows the data structure of the reservation information database of this embodiment. It is a sequence diagram of information processing of this embodiment. It is a figure which shows the screen example which is displayed in the information processing of this embodiment. It is a figure which shows the data structure of the candidate information database of the modification 1. It is a sequence diagram of the information processing of the modification 1. It is a figure which shows the screen example which is displayed in the information processing of the modification 1. It is a figure which shows the data structure of the communication information database of the modification 2. It is a sequence diagram of the information processing of the modification 2. It is a figure which shows the screen example which is displayed in the information processing of the modification 2. It is a figure which shows the screen example which is displayed in the information processing of the modification 2. It is a figure which shows the screen example which is displayed in the information processing of the modification 2. It is a figure which shows the data structure of the reservation information database of the modification 3. It is a sequence diagram of the information processing of the modification 3. It is a figure which shows the screen example which is displayed in the information processing of the modification 3. It is a figure which shows the screen example which is displayed in the information processing of the modification 3. It is a figure which shows the data structure of the prescriber information database of the modification 4. It is a figure which shows the data structure of the communication information database of the modification 4. It is a sequence diagram of information processing of the modification 4. It is a sequence diagram of information processing of the modification 4. It is a figure which shows the screen example which is displayed in the information processing of the modification 4. It is a figure which shows the screen example which is displayed in the information processing of the modification 4. It is a figure which shows the data structure of the candidate information database of the modification 5. It is a sequence diagram of the information processing of the modification 5. It is a figure which shows the screen example which is displayed in the information processing of the modification 5. It is a figure which shows the screen example which is displayed in the information processing of the modification 5.

Hereinafter, one embodiment of the present invention will be described in detail with reference to the drawings. In addition, in the drawing for demonstrating the embodiment, the same components are in principle the same reference numerals, and the repeated description thereof will be omitted.

(1) Configuration of information processing system The configuration of the information processing system will be described. FIG. 1 is a block diagram showing a configuration of an information processing system of the present embodiment. FIG. 2 is a functional block diagram of the information processing system of FIG.

As shown in FIG. 1, the information processing system 1 includes a dispenser terminal 10, a server 30, and a patient terminal 50.
The dispenser terminal 10 and the server 30 are connected via a network (for example, the Internet or an intranet) NW.
The server 30 and the patient terminal 50 are connected via a network (for example, the Internet or an intranet) NW.

The dispenser terminal 10 is a computer (an example of an "information processing device") that transmits a request to the server 30. The dispenser terminal 10 is, for example, a smartphone, a tablet terminal, or a personal computer. The dispenser terminal 10 is, for example, a computer used by a person who wants to dispense a drug to a patient and perform follow-up for the patient (hereinafter referred to as “dispenser”). Dispensers are, for example, pharmacies or pharmacists.

The server 30 is a computer (an example of an "information processing device") that provides the dispenser terminal 10 or the patient terminal 50 with a response in response to a request transmitted from the dispenser terminal 10 or the patient terminal 50. The server 30 is, for example, a web server.

The patient terminal 50 is a computer (an example of an "information processing device") that transmits a request to the server 30. The patient terminal 50 is, for example, a smartphone, a tablet terminal, or a personal computer. The patient terminal 50 is, for example, a computer used by a patient who has been dispensed a drug. Patients are, for example, patients who have a high need for follow-up after dispensing. Patients with a high need for follow-up after dispensing include, specifically, patients with chronic diseases who have been dispensed with new drugs, patients with acute diseases, and patients with strong or controlled side effects such as anticancer drugs or drugs. Examples include patients who have been dispensed with difficult drugs.

(1-1) Configuration of Dispenser Terminal The configuration of the dispenser terminal 10 will be described.

As shown in FIG. 2, the dispenser terminal 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14.

The storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of a ROM (Read Only Memory), a RAM (Random Access Memory), and a storage (for example, a flash memory or a hard disk).

The program includes, for example, the following program.
・ OS (Operating System) program ・ Application (for example, web browser) program that executes information processing

The data includes, for example, the following data.
-Database referenced in information processing-Data obtained by executing information processing (that is, the execution result of information processing)

The processor 12 is configured to realize the function of the dispenser terminal 10 by activating the program stored in the storage device 11. The processor 12 is, for example, a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

The input / output interface 13 is configured to acquire a user's instruction from an input device connected to the dispenser terminal 10 and output information to an output device connected to the dispenser terminal 10.
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display.

The communication interface 14 is configured to control communication between the dispenser terminal 10 and the server 30.

(1-2) Server Configuration The configuration of the server 30 will be described.

As shown in FIG. 2, the server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface 34.

The storage device 31 is configured to store programs and data. The storage device 31 is, for example, a combination of a ROM, a RAM, and a storage (for example, a flash memory or a hard disk).

The program includes, for example, the following program.
・ OS program ・ Application program that executes information processing

The data includes, for example, the following data.
・ Database referenced in information processing ・ Execution result of information processing

The processor 32 is configured to realize the function of the server 30 by activating the program stored in the storage device 31. The processor 32 is, for example, a CPU, an ASIC, an FPGA, or a combination thereof.

The input / output interface 33 is configured to acquire a user's instruction from an input device connected to the server 30 and output information to an output device connected to the server 30.
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display.

The communication interface 34 is configured to control communication between the server 30 and the dispenser terminal 10 and communication between the server 30 and the patient terminal 50.

(1-3) Configuration of Patient Terminal The configuration of the patient terminal 50 will be described.

As shown in FIG. 2, the patient terminal 50 includes a storage device 51, a processor 52, an input / output interface 53, and a communication interface 54.

The storage device 51 is configured to store programs and data. The storage device 51 is, for example, a combination of a ROM (Read Only Memory), a RAM (Random Access Memory), and a storage (for example, a flash memory or a hard disk).

The program includes, for example, the following program.
・ OS (Operating System) program ・ Application (for example, web browser) program that executes information processing

The data includes, for example, the following data.
-Database referenced in information processing-Data obtained by executing information processing (that is, the execution result of information processing)

The processor 52 is configured to realize the function of the patient terminal 50 by activating the program stored in the storage device 51. The processor 52 is, for example, a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

The input / output interface 53 is configured to acquire a user's instruction from an input device connected to the patient terminal 50 and output information to an output device connected to the patient terminal 50.
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display.

The communication interface 54 is configured to control communication between the patient terminal 50 and the server 30.

(2) Outline of the Embodiment The outline of the present embodiment will be described. FIG. 3 is an explanatory diagram of an outline of the present embodiment.

As shown in FIG. 3, the server 30 stores the patient identification information for identifying the patient and the patient contact information regarding the patient's contact information in association with each other.
The server 30 receives the designation of the follow-up content for the first patient to whom the drug has been dispensed from the user (dispenser) via the dispenser terminal 10.
The server 30 presents information according to the content of the follow-up.

(3) Database The database of the present embodiment will be described. The following database is stored in the storage device 31.

(3-1) Dispenser Information Database The dispenser information database of the present embodiment will be described. FIG. 4 is a diagram showing a data structure of the dispenser information database of the present embodiment.

Dispenser information related to the dispenser is stored in the dispenser information database of FIG.
The dispenser information database includes a "dispenser ID" field, a "dispenser name" field, and a "dispenser contact information" field. Each field is associated with each other.

The Dispenser ID is stored in the Dispenser ID field. The dispenser ID is an example of the dispenser identification information that identifies the dispenser.

The Dispenser Name field stores information about the Dispenser Name (eg, text). The dispenser name is an example of the dispenser identification information.

The Dispenser Contact field contains the dispenser contact information for the dispenser contact. Dispenser contact information is, for example:
-Message account of the service provided by the server 30-Message account of the service provided by an external server other than the server 30 (for example, an account of a social network service)
·mail address

One "dispenser" may be registered for each company, or may be registered for each store, each person in charge, or the like.

(3-2) Patient Information Database The patient information database of the present embodiment will be described. FIG. 5 is a diagram showing a data structure of the patient information database of the present embodiment.

The patient information database of FIG. 5 stores patient information about the patient.
The patient information database includes a "patient ID" field, a "patient name" field, a "patient contact" field, and a "drug history" field. Each field is associated with each other.

The patient ID is stored in the "patient ID" field. The patient ID is an example of patient identification information that identifies a patient.

The "Patient Name" field stores information (eg, text) about the patient name (patient's name). The patient name is an example of patient identification information.

The Patient Contact field stores patient contact information about the patient's contact. The patient contact information is, for example,:
-Message account of the service provided by the server 30-Message account of the service provided by an external server other than the server 30 (for example, an account of a social network service)
・ Email address ・ Phone number

The "drug history" field stores drug history information regarding the history of drugs dispensed to the patient (hereinafter referred to as "drug history"). The drug history information is, for example, a combination of the following information.
-Date when the drug was dispensed-Drug identification information that identifies the drug (as an example, the name of the drug)

(3-3) Reservation Information Database The reservation information database of the present embodiment will be described. FIG. 6 is a diagram showing a data structure of the reservation information database of the present embodiment.

The reservation information database of FIG. 6 stores reservation information regarding the reservation of follow-up for the patient.
The reservation information database includes a "reservation ID" field, a "follow-up content" field, and a "status" field. Each field is associated with each other.
The reservation information database is associated with the dispenser ID and the patient ID.

The reservation ID is stored in the "reservation ID" field. The reservation ID is an example of identification information that identifies a follow-up reservation.

The "Follow-up content" field stores follow-up content information regarding the content of the follow-up. The "Follow-up content" field includes a plurality of subfields ("Date and time" field and "Message" field).

The "date and time" field stores date and time information regarding the date and time (date and time) for follow-up.

The Message field contains the message (eg, text) that corresponds to the follow-up. Follow-up includes, for example, confirmation of the presence or absence of effects, confirmation of the presence or absence of side effects, confirmation of the medication status, guidance in these, guidance on the next scheduled dispensing date, and the like.

The Status field stores status information about the status of follow-up implementation. The data information is either "processed" or "unprocessed".

(4) Information processing The information processing of the present embodiment will be described. FIG. 7 is a sequence diagram of information processing of the present embodiment. FIG. 8 is a diagram showing an example of a screen displayed in the information processing of the present embodiment.

As shown in FIG. 7, the dispenser terminal 10 executes the reception of follow-up contents (S110).
Specifically, the processor 12 displays the screen P100 (FIG. 8) on the display.

The screen P100 includes field objects F100a to F100b and operation objects B100.
The field object F100a is an object that receives a user instruction for designating a patient name of a patient (hereinafter, also referred to as “first patient”) to be followed up.
The field object F100b is an object that receives a user instruction for designating the content of the follow-up. The content of the follow-up is, for example, a combination of the date and time of the follow-up and the follow-up message.
The operation object B100 is an object that receives a user instruction for transmitting the user instruction input to the field objects F100a to F100b to the server 30.

After step S110, the dispenser terminal 10 executes a reservation request (S111).
Specifically, when the dispenser inputs a user instruction to the field objects F100a to F100b and operates the operation object B100, the processor 12 transmits the reservation request data to the server 30.
The reservation request data includes the following information.
・ Dispenser ID
-Information about the patient name specified in the field object F100a-Information about the content of the follow-up specified in the field object F100b (combination of the date and time of follow-up and the follow-up message)

After step S111, the server 30 executes the update of the reservation information database (S310).
Specifically, the processor 32 refers to the patient information database (FIG. 5) and refers to the patient ID associated with the patient name included in the appointment request data (that is, the patient ID of the first patient to be followed up). ) Is specified. The processor 32 adds a new record to the reservation information database (FIG. 6) associated with the dispenser ID included in the reservation request data and the identified patient ID. The following information is stored in each field of the new record.
-A new reservation ID is stored in the "reservation ID" field.
-The date and time included in the reservation request data (hereinafter referred to as "reservation date and time") is stored in the "date and time" field. One date and time is stored in one record.
-The "Message" field stores the follow-up message included in the reservation request data. Follow-up messages are stored in the corresponding date and time records.
-"Unprocessed" is stored in the "Status" field.

After step S310, the server 30 executes the presentation of the follow-up message (S311).
Specifically, the processor 32 refers to the "date and time" field of the reservation information database (FIG. 6), and when the date and time arrives, the presented response data is transmitted to the patient contact of the patient contact information of the first patient. Send first.
More specifically, the processor 32 identifies the patient ID associated with the appointment information database (FIG. 6). The processor 32 refers to the patient information database (FIG. 5) to identify patient contact information associated with the identified patient ID. The processor 32 refers to the reservation information database (FIG. 6) to identify the follow-up message associated with the date and time. The processor 32 transmits the presented response data to the patient contact in the identified patient contact information. The presentation response data includes the following information.
・ Specified follow-up message (an example of "information according to the content of follow-up")
The processor 32 updates the "status" field of the record of the date and time in the reservation information database (FIG. 6). Specifically, change from "unprocessed" to "processed".

After step S311 the patient terminal 50 executes a follow-up message display (S510).
Specifically, the processor 52 displays the screen P101 (FIG. 8) on the display based on the presented response data.

The screen P101 includes the display object A101.
The display object A101 includes a follow-up message included in the presentation response data.

According to this embodiment, the dispenser can specify the desired follow-up content for the patient. As a result, the dispenser can carry out follow-up from various viewpoints such as effects, side effects, and medication status. Therefore, the dispenser can carry out a more complete follow-up for the patient.
Further, in the present embodiment, the date and time when the follow-up is performed can be specified as the content of the follow-up. Therefore, the dispenser can perform follow-up on the patient at a desired date and time.
Further, in the present embodiment, the follow-up message corresponding to the follow-up is presented to the contact corresponding to the patient contact information associated with the first patient. Therefore, the dispenser does not need to perform oral follow-up on the first patient, and the effort in performing the follow-up on the first patient is reduced.
Further, in the present embodiment, the dispenser can automatically perform follow-up at a desired date and time by designating the date and time and the follow-up message. Therefore, the dispenser has less effort in managing the implementation of follow-up.

(5) Modification Example A modification of the present embodiment will be described.

(5-1) Modification 1
Modification 1 will be described. The first modification is an example in which a candidate for a date for follow-up is presented to the dispenser based on at least one of the date on which the drug is dispensed and the number of prescription days. In the first modification, a candidate for the time for follow-up and a candidate for the follow-up message will be presented to the dispenser, but the modification 1 is not limited to this.

(5-1-1) Candidate Information Database The candidate information database of Modification 1 will be described. FIG. 9 is a diagram showing a data structure of the candidate information database of the first modification.

The candidate information database of FIG. 9 stores information about candidates for follow-up contents.
The candidate information database includes a "candidate ID" field, a "follow-up content candidate" field, and a "non-presentation condition" field. Each field is associated with each other.

A candidate ID is stored in the "candidate ID" field. The candidate ID is an example of identification information that identifies a candidate for follow-up content.

The "follow-up content candidate" field stores follow-up content candidate information regarding the follow-up content candidate. The "follow-up content candidate" field includes a plurality of subfields ("candidate follow-up name" field, "candidate date and time" field, and "candidate message" field).

In the "candidate follow-up name" field, information (for example, text) regarding a name (hereinafter referred to as "follow-up name") that simply expresses the content of the follow-up is stored.

The "candidate date and time" field stores candidate date and time information regarding candidates for the date and time to be followed up. Specifically, a calculation formula for calculating a follow-up date based on at least one of a dispensing date and a prescription date, and information on time candidates are stored.

The Candidate Message field contains message candidates (eg, text) that correspond to follow-up.

The "non-presentation condition" field stores information about the condition that is not presented as a candidate. If there is no condition not to be presented as a candidate, nothing is stored.

(5-1-2) Information Processing The information processing of Modification 1 will be described. FIG. 10 is a sequence diagram of information processing of the first modification. FIG. 11 is a diagram showing an example of a screen displayed in the information processing of the modified example 1.

As shown in FIG. 10, the dispensing person terminal 10 executes the reception of the dispensing date and the number of prescription days (S120).
Specifically, the processor 12 displays the screen P200 (FIG. 11) on the display.

The screen P200 includes field objects F200a to F200c and operation objects B200.
The field object F200a is an object that receives a user instruction for designating a patient name of a patient (first patient) to be followed up.
The field object F200b is an object that receives a user instruction for designating a date (dispensing date) when the drug is dispensed to the first patient.
The field object F200c is an object that receives a user instruction for designating the number of prescription days for the drug.
The operation object B200 is an object that receives a user instruction for transmitting the user instruction input to the field objects F200a to F200c to the server 30.

After step S120, the dispenser terminal 10 executes the candidate presentation request (S121).
Specifically, when the dispenser inputs a user instruction to the field objects F200a to F200c and operates the operation object B200, the processor 12 transmits the candidate presentation request data to the server 30.
The candidate presentation request data includes the following information.
・ Dispenser ID
-Information on the patient name specified in the field object F200a-Information on the dispensing date specified in the field object F200b-Information on the number of prescription days specified in the field object F200c

After step S121, the server 30 executes the candidate presentation (S320).
Specifically, the processor 32 uses a calculation formula stored in the “candidate date / time” field of the candidate information database (FIG. 9) based on at least one of the dispensing date and the prescription day included in the candidate presentation request data. Calculate the date. Further, the processor 32 determines whether or not it corresponds to the "non-presentation condition" field of the candidate information database (FIG. 9) based on at least one of the dispensing date and the prescription days included in the candidate presentation request data. For example, when the number of prescription days is 8 days, the follow-up content candidate with candidate ID = T002 corresponds to the non-presentation condition. The processor 32 identifies follow-up content candidates that do not meet the non-presentation condition.
The processor 32 transmits the candidate presentation response data to the dispenser terminal 10. The candidate presentation response data includes the following information.
-Information about identified follow-up content candidates (combination of calculated date, follow-up time and follow-up message)

After step S320, the dispenser terminal 10 executes the reception of follow-up contents (S122).
Specifically, the processor 12 displays the screen P201 (FIG. 11) on the display.

The screen P201 includes a field object F201 and an operation object B201.
The field object F201 is an object that receives a user instruction for designating the content of the follow-up. The field object F201 displays information about follow-up content candidates included in the candidate presentation response data.
The operation object B201 is an object that receives a user instruction for transmitting the user instruction input to the field object F201 to the server 30.

After step S122, the dispenser terminal 10 executes a reservation request (S123).
Specifically, when the dispenser inputs a user instruction to the field object F201 and operates the operation object B201, the processor 12 transmits the reservation request data to the server 30. Specifically, when the dispenser does not wish to change from the follow-up content candidate, the dispenser operates the operation object B201 with the content displayed in the field object F201 as it is. On the other hand, when the dispenser wishes to change from the follow-up content candidate, he / she changes the follow-up content displayed in the field object F201 and operates the operation object B201. Changes in follow-up content include, for example, changing the date and time, changing the message, deleting a part of a plurality of date and time and a combination of messages, or adding a date and time and a message.
The reservation request data includes the following information.
・ Dispenser ID
-Information about the patient name specified in the field object F200a-Information about the content of the follow-up specified in the field object F201 (combination of the date and time of follow-up and the follow-up message)

After step S123, the server 30 executes the update of the reservation information database (S310) and the presentation of the follow-up message (S311) as in the present embodiment.

After step S311 the patient terminal 50 executes the display of the follow-up message (S510) as in the present embodiment.

According to the first modification, a candidate date for follow-up can be presented to the dispenser based on at least one of the dispensing date and the number of prescription days. Therefore, the dispenser can easily specify the date for follow-up. Dispensers can also specify an appropriate date for follow-up.
Further, according to the first modification, a candidate for a time for follow-up can be presented to the dispenser. Therefore, the dispenser can easily specify the time for follow-up. Dispensers can also specify an appropriate time for follow-up.
Further, according to the first modification, a candidate for a follow-up message can be presented to the dispenser. Therefore, the dispenser can easily specify the follow-up message. Dispensers can also specify appropriate follow-up messages.

(5-2) Modification 2
Modification 2 will be described. The second modification is an example of receiving and presenting a reply message from the first patient to the dispenser. In the second modification, an example of receiving and presenting a re-reply message from the dispenser to the first patient will also be described, but the second modification is not limited to this.

(5-2-1) Communication information database The communication information database of the second modification will be described. FIG. 12 is a diagram showing a data structure of the communication information database of the second modification.

The communication information database of FIG. 12 stores communication information regarding the exchange of messages between the dispenser and the patient.
The communication information database includes a "communication ID" field, a "sending date and time" field, a "sender" field, a "destination" field, and a "message" field. Each field is associated with each other.
The communication information database is associated with the dispenser ID and the patient ID.

A communication ID is stored in the "communication ID" field. The communication ID is an example of identification information that identifies the content of communication.

The "send date and time" field stores date and time information regarding the date and time (date and time) when the message was sent.

The "sender" field stores identification information (dispenser ID or patient ID) of the person who sent the message.

The "destination" field stores identification information (dispenser ID or patient ID) of the person who received the message.

The Message field contains the transmitted message (eg, text).

(5-2-2) Information processing The information processing of the modified example 2 will be described. FIG. 13 is a sequence diagram of information processing of the second modification. FIG. 14 is a diagram showing an example of a screen displayed in the information processing of the second modification. FIG. 15 is a diagram showing an example of a screen displayed in the information processing of the modified example 2. FIG. 16 is a diagram showing an example of a screen displayed in the information processing of the second modification.

In the second modification, steps S110 to S310 (FIG. 7) are executed in the same manner as in the present embodiment.

After step S310, as shown in FIG. 13, the server 30 executes the presentation of the follow-up message (S330).
Specifically, the processor 32 refers to the "date and time" field of the reservation information database (FIG. 6), and when the date and time arrives, the presented response data is transmitted to the patient contact of the patient contact information of the first patient. Send first.
More specifically, the processor 32 identifies the patient ID associated with the appointment information database (FIG. 6). The processor 32 refers to the patient information database (FIG. 5) to identify patient contact information associated with the identified patient ID. The processor 32 refers to the reservation information database (FIG. 6) to identify the follow-up message associated with the date and time. The processor 32 transmits the presented response data to the patient contact in the identified patient contact information. The presentation response data includes the following information.
・ Identified follow-up message ・ New communication ID
The processor 32 updates the "status" field of the record of the date and time in the reservation information database (FIG. 6). Specifically, change from "unprocessed" to "processed".
Processor 32 adds a new record to the dispenser ID and the communication information database (FIG. 12) associated with the identified patient ID. The following information is stored in each field of the new record.
-A new communication ID included in the presentation response data in step S330 is stored in the "communication ID" field.
-The date and time when step S330 is executed is stored in the "transmission date and time" field.
-The Dispenser ID is stored in the "Sender" field.
-The patient ID is stored in the "destination" field.
-The "Message" field stores the identified follow-up message.

After step S330, the patient terminal 50 executes a follow-up message display (S530).
Specifically, the processor 52 displays the screen P301 (FIG. 14) on the display based on the presentation response data in step S330.

The screen P301 includes a display object A301, a field object F301, and an operation object B301.
The display object A301 includes a follow-up message included in the presentation response data in step S330.
The field object F301 is an object that receives a user instruction for designating a reply message.
The operation object B301 is an object that receives a user instruction for executing the reply request (S531).

After step S530, the patient terminal 50 executes a reply request (S531).
Specifically, when the patient inputs a user instruction to the field object F301 and operates the operation object B301, the processor 52 transmits the reply request data to the server 30.
The reply request data includes the following information.
・ Patient ID
-Reply message specified in field object F301-Communication ID included in the presentation response data in step S330

After step S531, the server 30 executes the presentation of the reply message (S331).
Specifically, the processor 32 refers to the communication information database (FIG. 12) to identify the sender and the destination associated with the communication ID included in the reply request data. The processor 32 compares the specified sender and destination with the patient ID included in the reply request data, and identifies the destination (here, the dispenser ID) of the reply message. The processor 32 refers to the dispenser information database (FIG. 4) to identify the dispenser contact information associated with the identified destination (dispenser ID). The processor 32 transmits the presented response data to the dispenser contact of the specified dispenser contact information. The presentation response data includes the following information.
・ Follow-up message ・ Reply message included in reply request data ・ New communication ID
The processor 32 adds a new record to the communication information database (FIG. 12) associated with the dispenser ID and the patient ID. The following information is stored in each field of the new record.
-In the "communication ID" field, a new communication ID included in the presentation response data in step S331 is stored.
-The date and time when step S331 is executed is stored in the "transmission date and time" field.
-The patient ID is stored in the "sender" field.
-The Dispenser ID is stored in the "Destination" field.
-The reply message included in the reply request data is stored in the "Message" field.

After step S331, the dispenser terminal 10 executes the display of the reply message (S130).
Specifically, the processor 12 displays the screen P302 (FIG. 15) on the display based on the presentation response data in step S331.

The screen P302 includes display objects A302a to A302b, a field object F302, and an operation object B302.
The display object A302a includes a follow-up message included in the presentation response data of step S331.
The display object A302b includes a reply message included in the presentation response data in step S331.
The field object F302 is an object that receives a user instruction for designating a re-reply message.
The operation object B302 is an object that receives a user instruction for executing the re-reply request (S131).

After step S131, the dispenser terminal 10 executes a re-reply request (S332).
Specifically, when the dispenser inputs a user instruction to the field object F302 and operates the operation object B302, the processor 12 transmits the re-reply request data to the server 30.
The re-reply request data includes the following information.
・ Dispenser ID
-Re-reply message specified in field object F302-Communication ID included in the presentation response data in step S331

After step S131, the server 30 executes the presentation of the re-reply message (S332).
Specifically, the processor 32 refers to the communication information database (FIG. 12) to identify the sender and the destination associated with the communication ID included in the re-reply request data. The processor 32 compares the specified sender and destination with the dispenser ID included in the re-reply request data, and identifies the destination (here, the patient ID) of the re-reply message. The processor 32 refers to the patient information database (FIG. 5) to identify patient contact information associated with the identified destination (patient ID). The processor 32 transmits the presented response data to the patient contact in the identified patient contact information. The presentation response data includes the following information.
・ Follow-up message ・ Reply message ・ Re-reply message included in re-reply request data ・ New communication ID
The processor 32 adds a new record to the communication information database (FIG. 12) associated with the dispenser ID and the patient ID. The following information is stored in each field of the new record.
-In the "communication ID" field, a new communication ID included in the presentation response data in step S332 is stored.
-The date and time when step S332 is executed is stored in the "transmission date and time" field.
-The Dispenser ID is stored in the "Sender" field.
-The patient ID is stored in the "destination" field.
-The "Message" field stores the re-reply message included in the re-reply request data.

After step S332, the patient terminal 50 executes the display of the re-reply message (S533).
Specifically, the processor 52 displays the screen P303 (FIG. 16) on the display based on the presentation response data in step S332.

The screen P303 includes display objects A303a to A303c, a field object F303, and an operation object B303.
The display object A303a includes a follow-up message included in the presentation response data in step S332.
The display object A303b includes a reply message included in the presentation response data in step S332.
The display object A303c includes a re-reply message included in the presentation response data in step S332.
The field object F303 is an object that receives a user instruction for designating a reply message again.
The operation object B303 is an object that receives a user instruction for executing the reply request again.

After step S533, steps S531 to S130 and steps S131 to S533 may be repeated in the same manner. This allows the dispenser and the patient to exchange messages in both directions.

According to the second modification, a reply message from the first patient to the dispenser can be presented to the dispenser. That is, the first patient can send a reply message to the follow-up message from the dispenser. As a result, the dispenser can know the situation of the first patient and the like. Therefore, the dispenser can perform a more complete follow-up.
Further, according to the second modification, a re-reply message from the dispenser to the first patient can be presented to the first patient. That is, the dispenser can send a re-reply message to the reply message from the first patient. As a result, the dispenser can perform follow-up according to the situation of the first patient and the like. Therefore, the dispenser can perform a more complete follow-up.

(5-3) Modification 3
Modification 3 will be described. The third modification is an example in which a patient contact that cannot present the text of the message (for example, a telephone number of a fixed telephone) is used.

(5-3-1) Reservation Information Database The communication information database of Modification 3 will be described. FIG. 17 is a diagram showing a data structure of the reservation information database of the third modification.

The reservation information database of FIG. 17 stores reservation information regarding the reservation of follow-up for the patient.
The reservation information database includes a "reservation ID" field, a "follow-up content" field, and a "status" field. Each field is associated with each other.
The reservation information database is associated with the dispenser ID and the patient ID.

The reservation ID is stored in the "reservation ID" field. The reservation ID is an example of identification information that identifies a follow-up reservation.

The "Follow-up content" field stores follow-up content information regarding the content of the follow-up. The "Follow-up content" field includes a plurality of subfields ("Date and time" field and "Follow-up name" field).

The "date and time" field stores date and time information regarding the date and time (date and time) for follow-up.

In the "follow-up name" field, information (for example, text) regarding a name (hereinafter referred to as "follow-up name") that simply expresses the content of the follow-up is stored.

The Status field stores status information about the status of follow-up implementation. The data information is either "processed" or "unprocessed".

(5-3-2) Information processing The information processing of the modified example 3 will be described. FIG. 18 is a sequence diagram of information processing of the third modification. FIG. 19 is a diagram showing an example of a screen displayed in the information processing of the modified example 3. FIG. 20 is a diagram showing an example of a screen displayed in the information processing of the modified example 3.

As shown in FIG. 18, the dispenser terminal 10 executes the reception of patient information (S140).
Specifically, the processor 12 displays the screen P400 (FIG. 19) on the display.

The screen P400 includes a field object F400 and an operation object B400.
The field object F400 is an object that receives a user instruction for designating an image of the electronic version of the two-dimensional code for the medicine notebook of the patient (first patient) to be followed up.
The operation object B400 is an object that receives a user instruction for transmitting the user instruction input to the field object F400 to the server 30.

After step S140, the dispenser terminal 10 executes the patient information registration request (S141).
Specifically, when the dispenser inputs the image data of the two-dimensional code for the electronic version of the medicine notebook of the first patient into the field object F400 and operates the operation object B400, the processor 12 requests the patient information registration. The data is transmitted to the server 30. The two-dimensional code for the electronic version of the medicine notebook is, for example, a QR code (registered trademark) (for example, a QR code in JAHIS format). The image data is input via, for example, a camera (not shown) connected to the dispenser terminal 10. The two-dimensional code for the electronic version of the medicine notebook can be used, for example, on a paper medium such as a dispensing fee statement, a dosing instruction, or a sticker to be attached to the medicine notebook, which is given from the dispenser to the patient together with the medicine. Have been described.
The patient information registration request data includes the following information.
・ Dispenser ID
-Image data of the two-dimensional code for the electronic version of the medicine notebook specified in the field object F400

After step S141, the server 30 executes the update of the patient information database (S340).
Specifically, the processor 32 processes the image data included in the patient information registration request data to acquire the patient identification information (for example, patient name) and the contact information (for example, telephone number) of the first patient. To do. Processor 32 adds a new record to the patient information database (FIG. 5). The following information is stored in each field of the new record.
-A new patient ID is stored in the "patient ID" field.
-The acquired patient name is stored in the "Patient name" field.
-The "Patient Contact" field stores the acquired patient contact.
The processor 32 newly generates a reservation information database (FIG. 17) associated with the new patient ID and the dispenser ID included in the patient information registration request data. At the time of step S340, nothing is stored in each field.

After step S340, the dispenser terminal 10 executes the reception of the follow-up content (S142).
Specifically, the processor 12 displays the screen P401 (FIG. 19) on the display.

The screen P401 includes a field object F401 and an operation object B401.
The field object F401 is an object that receives a user instruction for specifying the content of the follow-up. The content of the follow-up is, for example, a combination of the date and time of the follow-up and the follow-up name.
The operation object B401 is an object that receives a user instruction for transmitting the user instruction input to the field object F401 to the server 30.

After step S142, the dispenser terminal 10 executes a reservation request (S143).
Specifically, when the dispenser inputs a user instruction to the field object F401 and operates the operation object B401, the processor 12 transmits the reservation request data to the server 30.
The reservation request data includes the following information.
-Information about the content of the follow-up specified in the field object F401 (combination of the date and time of the follow-up and the follow-up name).

After step S143, the server 30 executes the update of the reservation information database (S341).
Specifically, the processor 32 adds a new record to the reservation information database (FIG. 17) generated in step S340. The following information is stored in each field of the new record.
-A new reservation ID is stored in the "reservation ID" field.
-The date and time included in the reservation request data is stored in the "Date and time" field. One date and time is stored in one record.
-In the "Follow-up name" field, the follow-up name included in the reservation request data is stored. The follow-up name is stored in the corresponding date and time record.
-"Unprocessed" is stored in the "Status" field.

After step S341, the server 30 executes the presentation of reservation information (S342).
Specifically, the processor 32 refers to the "date and time" field of the reservation information database (FIG. 17), and when the date and time arrives at, or before the date and time and at a predetermined timing. (For example, 2 hours before the date and time in the "Date and time" field, or 9:00 am on the date in the "Date and time" field, etc.), the presented response data is sent to the dispenser contact information in the dispenser contact information. Send to.
More specifically, the processor 32 identifies the dispenser ID and the patient ID associated with the appointment information database (FIG. 17). The processor 32 refers to the dispenser information database (FIG. 4) to identify the dispenser contact information associated with the identified dispenser ID. The processor 32 refers to the patient information database (FIG. 5) to identify the patient name and patient contact information associated with the identified patient ID. The processor 32 refers to the reservation information database (FIG. 17) to identify the follow-up name associated with the date and time. The processor 32 transmits the presented response data to the dispenser contact of the specified dispenser contact information. The presentation response data includes the following information.
・ Reservation ID
-Specified patient name and patient contact information-Information on the specified follow-up content (combination of the date and time of follow-up and the follow-up name) (an example of "information according to the follow-up content")

After step S342, the dispenser terminal 10 executes the display of reservation information (S144).
Specifically, the processor 12 displays the screen P402 (FIG. 20) on the display based on the presented response data.

The screen P402 includes a display object A402 and an operation object B402.
The display object A402 includes the patient name, patient contact information, and follow-up content included in the presentation response data.
The operation object B402 is an object that receives a user instruction to the effect that the follow-up has been performed, and also receives a user instruction for executing the status update request (S145).

After step S144, the dispenser terminal 10 executes a status update request (S145).
Specifically, when the dispenser operates the operation object B402 after performing a telephone follow-up to the first patient based on the information contained in the display object A402, the processor 12 sends the status update request data. Send to server 30. The status update request data includes the following information.
・ Reservation ID
・ Information that follow-up was performed

After step S145, the server 30 executes the update of the status information database (S343).
Specifically, the processor 32 updates the "status" field associated with the reservation ID included in the status update request data in the reservation information database (FIG. 17). Specifically, change from "unprocessed" to "processed".

According to the third modification, the patient identification information and the patient contact information are acquired based on the information of the two-dimensional code for the electronic version of the medicine notebook. Therefore, it is possible to avoid erroneous input that may occur due to manual input. Further, as compared with the case of acquiring from the external system, the patient identification information and the patient contact information can be easily acquired without depending on the specifications of the external system.
Further, according to the third modification, the dispenser is presented with information on the content of the follow-up and patient contact information associated with the first patient. As a result, when using a patient contact that cannot present the text of the message (for example, a landline telephone number), information on the content of follow-up and patient contact information of the first patient are given to the dispenser. Can be presented. Therefore, the dispenser has less effort in managing the implementation of follow-up. Also, the dispenser can follow up with the patient even if the patient does not have a device capable of presenting the text of the message.
Further, when the patient has a device capable of presenting the text of the message, as in the present embodiment, the patient is presented with a follow-up message corresponding to the follow-up, while the patient presents the message. If the patient does not have a device that can present the text, the patient's device possession status is provided by presenting the information on the content of the follow-up and the patient contact information to the dispenser as in the modified example 3. Regardless, the dispenser can easily follow up in an appropriate manner.
Further, according to the third modification, the dispenser can specify the desired follow-up content for the patient. As a result, the dispenser can carry out follow-up from various viewpoints such as effects, side effects, and medication status. Therefore, the dispenser can carry out a more complete follow-up for the patient.

(5-4) Modification 4
Modification 4 will be described. The fourth modification is an example of generating a tracing report including patient identification information and information based on a reply message. A "tracing report" is also called a "medicine information provision form", and when a pharmacy obtains useful information for drug therapy, etc. of a patient, although the urgency and immediacy are low, the information is used for the drug. This document is used to convey to the prescriber. In the modified example 4, an example in which the tracing report is transmitted to the person who prescribes the drug (hereinafter referred to as “prescriber”) will also be described. The prescribing person is, for example, at least one of the following.
・ Hospital ・ Clinic ・ Medical office ・ Doctor ・ Dentist

(5-4-1) Prescriber Information Database The prescriber information database of the modified example 4 will be described. FIG. 21 is a diagram showing a data structure of the prescriber information database of the modified example 4.

The prescriber information database of FIG. 21 stores prescriber information regarding the prescriber.
The prescriber information database includes a "prescriber ID" field, a "prescriber name" field, and a "prescriber contact information" field. Each field is associated with each other.

The prescriber ID is stored in the "prescriber ID" field. The prescriber ID is an example of prescriber identification information that identifies the prescriber.

The Prescriber Name field stores prescriber name information (eg, text) for the prescriber's name. The prescriber name information is an example of prescriber identification information. When the prescriber is a doctor, for example, only the name of the doctor may be stored as the name of the prescriber, or a combination of the name of the doctor and the name of the medical institution to which the doctor belongs may be stored.

The Prescriber Contact field contains prescriber contact information about the prescriber's contact information. The prescriber contact information is, for example, at least one of the following:
-FAX number-Message account of the service provided by the server 30-Message account of the service provided by an external server other than the server 30 (for example, the account of the social network service)
・ Email address ・ Phone number

(5-4-2) Communication Information Database The communication information database of Modification 4 will be described. FIG. 22 is a diagram showing a data structure of the communication information database of the modified example 4.

The communication information database of FIG. 22 stores communication information regarding the exchange of messages between the dispenser and the patient.
The communication information database includes a "communication ID" field, a "reservation ID" field, a "send date and time" field, a "sender" field, a "destination" field, a "message" field, and a "report status" field. including. Each field is associated with each other.
The communication information database is associated with a combination of dispenser ID and patient ID.

A communication ID is stored in the "communication ID" field. The communication ID is an example of communication identification information that identifies the content of communication.

The reservation ID corresponding to the communication information is stored in the "reservation ID" field.

In the "Send date and time" field, transmission date and time information regarding the date and time (date and time) when the message was sent is stored.

The "Sender" field stores the sender identification information of the person who sent the message. When the dispenser is the sender, the sender identification information is the dispenser ID. When the patient is the sender, the sender identification information is the patient ID.

The Destination field stores the destination identification information of the person who received the message. When the dispenser is the destination, the destination identification information is the dispenser ID. When the patient is the destination, the destination identification information is the patient ID.

The Message field contains the transmitted message (eg, text).

The Report Status field stores report status information regarding the status of the generation and transmission of tracing reports. The report status information is either "processed" or "unprocessed".

(5-4-3) Information processing The information processing of the modified example 4 will be described. FIG. 23 is a sequence diagram of information processing of the modified example 4. FIG. 24 is a sequence diagram of information processing of the modified example 4. FIG. 25 is a diagram showing an example of a screen displayed in the information processing of the modified example 4. FIG. 26 is a diagram showing an example of a screen displayed in the information processing of the modified example 4.

As shown in FIG. 23, the dispenser terminal 10 executes steps S110 to S111 as in the present embodiment.

After step S111, the server 30 executes step S310 as in the present embodiment.

After step S310, when the reservation date and time arrives, the server 30 executes the presentation of the follow-up message (S350).
Specifically, the processor 32 refers to the reservation information database (FIG. 6) to identify the follow-up message associated with the arrival reservation date and time.
The processor 32 identifies the patient ID associated with the appointment information database (FIG. 6). The processor 32 refers to the patient information database (FIG. 5) to identify patient contact information associated with the identified patient ID.
The processor 32 transmits the presented response data to the patient contact in the identified patient contact information. The presentation response data includes the following information.
・ Identified follow-up message ・ New communication ID

After step S350, the server 30 executes the database update (S351).
Specifically, the processor 32 changes the information in the "status" field of the record of the date and time from "unprocessed" to "processed" in the reservation information database (FIG. 6).
Processor 32 adds a new record to the dispenser ID and the communication information database (FIG. 22) associated with the identified patient ID. The following information is stored in each field of the new record.
-A new communication ID included in the presentation response data in step S350 is stored in the "communication ID" field.
-The "Reservation ID" field stores the reservation ID associated with the specified follow-up message.
-The date and time when step S350 is executed is stored in the "transmission date and time" field.
-The Dispenser ID is stored in the "Sender" field.
-The patient ID is stored in the "destination" field.
-The "Message" field stores the identified follow-up message.
-"Unprocessed" is stored in the "Report Status" field.

After step S350, the patient terminal 50 executes steps S530 to S531 as in the second modification.

After step S531, the server 30 executes the presentation of the reply message (S352).
Specifically, the processor 32 refers to the communication information database (FIG. 22) and identifies a combination of a sender and a destination (that is, a subject of communication) associated with the communication ID included in the reply request data.
The processor 32 compares the specified combination of the sender and the destination with the patient ID included in the reply request data, and identifies the destination (here, the dispenser ID) of the reply message.
The processor 32 refers to the dispenser information database (FIG. 4) to identify the dispenser contact information associated with the identified destination (dispenser ID).
The processor 32 transmits the presented response data to the dispenser contact of the specified dispenser contact information. The presentation response data includes the following information.
-Follow-up message-Reply message included in reply request data-Communication ID included in presentation response data in step S350

After step S352, the server 30 executes a database update (S353).
Specifically, the processor 32 adds a new record to the communication information database (FIG. 22) associated with the combination of the dispenser ID and the patient ID. The new record is added in the record associated with the communication ID included in the presentation response data in step S350. The following information is stored in each field of the new record.
-The date and time when step S352 is executed is stored in the "transmission date and time" field.
-The patient ID is stored in the "sender" field.
-The Dispenser ID is stored in the "Destination" field.
-The reply message included in the reply request data is stored in the "Message" field.

After step S352, step S130 is executed in the same manner as in the second modification.

Next, information processing for generating and transmitting a tracing report will be described.
As shown in FIG. 24, the dispenser terminal 10 executes the reception of the history viewing instruction (S150).
Specifically, the processor 12 displays the screen P500 (FIG. 25) on the display.

The screen P500 includes a field object F500 and an operation object B500.
The field object F500 is an object that receives a user instruction for designating patient identification information (for example, a patient name, a patient ID, or a combination of a patient name and a patient ID) of a patient whose history is to be browsed.
The operation object B500 is an object that receives a user instruction for transmitting the user instruction input to the field object F500 to the server 30.

After step S150, the dispenser terminal 10 executes a history viewing request (S151).
Specifically, when the dispenser inputs a user instruction to the field object F500 and operates the operation object B500, the processor 12 transmits the history browsing request data to the server 30. The history browsing request data includes the following information.
・ Dispenser ID
-Patient identification information specified in the field object F500

After step S151, the server 30 executes the presentation of history information (S354).
Specifically, the processor 32 refers to the patient information database (FIG. 5) and refers to the patient ID associated with the patient identification information included in the history browsing request data (that is, the first patient to be browsed in the history). Patient ID). The processor 32 identifies the communication information related to the dispenser and the first patient by referring to the dispenser ID included in the history browsing request data and the communication information database (FIG. 22) associated with the identified patient ID. ..
The processor 32 transmits the history browsing response data to the dispenser terminal 10. The history browsing response data includes the following information.
・ Identified communication information

After step S354, the dispenser terminal 10 executes the reception of the report generation instruction (S152).
Specifically, the processor 12 displays the screen P501 (FIG. 25) on the display.

The screen P501 includes a display object A501 and a plurality of operation objects B501 (B501a, B501b, ...). In one example, each operation object B501 is associated with each communication ID in which "unprocessed" is stored in the "report status" field and a reply message is stored in the "message" field in the communication information database (FIG. 22). Has been done. Further, in one example, each operation object B501 may be associated with each communication ID in which a reply message is stored in the "message" field so that the tracing report can be generated and transmitted again. Further, in one example, the operation object B501 may also target a communication ID in which a reply message is not stored in the "message" field.
The display object A501 includes communication information included in the history browsing response data.
The operation object B501 is an object that receives a user instruction for generating a tracing report. The operation object B501a is an object that receives a user instruction for generating a tracing report corresponding to the communication information identified by the communication ID = C101 (FIG. 22). The operation object B501b is an object that receives a user instruction for generating a tracing report corresponding to the communication information identified by the communication ID = C102 (FIG. 22).

After step S152, the dispenser terminal 10 executes a report generation request (S153).
Specifically, when the dispenser operates one of the plurality of operation objects B501 (here, a case where the operation object B501b is selected) is operated, the processor 12 sends the report generation request data to the server 30. Send. The report generation request data includes the following information.
-Communication ID associated with operation object B501b

After step S153, the server 30 executes the presentation of the report (S355).
Specifically, the processor 32 refers to the communication information database (FIG. 22) to specify the transmission date / time, the sender, the destination, and the message associated with the communication ID included in the report generation request data. The processor 32 generates a draft tracing report based on the specified transmission date and time, sender, destination, and message.
The processor 32 transmits the report presentation response data to the dispenser terminal 10. The report presentation response data includes the following information.
・ Information about the draft of the generated tracing report

After step S355, the dispenser terminal 10 executes the display of the report (S154).
Specifically, the processor 12 displays the screen P502 (FIG. 26) on the display based on the report presentation response data.

The screen P502 includes field objects F502a to F502d and operation objects B502.
The field object F502a is a prescriber identification information (for example, a prescriber name, a prescriber ID, or a prescriber name and a prescriber ID) of a prescriber who has prescribed a drug corresponding to a communication ID associated with the operation object B501b. It is an object that accepts user instructions to specify (combination).
The field object F502b is an object that receives a user instruction for designating a dispenser name. The field object F502b displays information about the dispenser name corresponding to the communication ID associated with the operation object B501b.
The field object F502c is an object that receives a user instruction for designating a patient name. The field object F502c displays information about the patient name corresponding to the communication ID associated with the operation object B501b.
The field object F502d is an object that receives a user instruction for designating the information provision content. The field object F502d displays a message (follow-up message and reply message) corresponding to the communication ID associated with the operation object B501b and information based on the transmission date and time.
The operation object B502 is an object that receives a user instruction for transmitting the user instruction input to the field objects F502a to F502d to the server 30.

After step S154, the dispenser terminal 10 executes a report transmission request (S155).
Specifically, when the dispenser inputs user instructions to the field objects F502a to F502d and operates the operation object B502, the processor 12 transmits the report transmission request data to the server 30.
More specifically, when the dispenser inputs the prescriber identification information in the field object F502a and wishes to change the contents of the field objects F502b to F502d from those displayed, the field objects F502b to F502d When the displayed dispenser name, patient name, and information provision content are changed and the operation object B502 is operated, the processor 12 transmits the report transmission request data to the server 30.
The report transmission request data includes the following information.
-Prescriber identification information specified in the field object F502a-Information on the dispenser name specified in the field object F502b-Information on the patient name specified in the field object F502c (an example of "patient identification information of the first patient")
-Information about the information provided in the field object F502d (an example of "information based on the reply message")

After step S155, the server 30 executes the transmission of the report (S356).
Specifically, the processor 32 generates a tracing report for transmission based on each information included in the report transmission request data. The tracing report for transmission includes information on the content of information provided (an example of "information based on a reply message") and information on the patient name of the first patient (an example of "patient identification information of the first patient").
The tracing report for transmission may further include, for example, drug history information of the first patient (an example of "information about the first patient"). In this case, the processor 32 refers to the patient database (FIG. 5) to identify drug history information associated with the patient ID identified in step S354. The processor 32 generates a tracing report for transmission based on each information contained in the report transmission request data and the identified drug history information.
The processor 32 refers to the prescription information database (FIG. 21) to identify the prescribing contact information associated with the prescribing identification information included in the report transmission request data. The processor 32 transmits the generated tracing report for transmission to the prescriber contact of the identified prescriber contact information.
Processor 32 updates the corresponding "report status" field in the communication information database (FIG. 22). Specifically, change from "unprocessed" to "processed".

In the fourth modification, an example in which the tracing report for transmission includes drug history information in addition to the information regarding the information provision content and the patient name has been described, but the present invention is not limited to this. The tracing report for transmission may include, for example, at least one of the following.
・ Information about the first patient (patient ID, date of birth, age, gender, patient contact information, medical history, current medical history, etc.)
・ Information about the dispenser (dispenser ID, dispenser name, dispenser contact information, dispenser address, etc.)
・ Information about the prescriber (prescriber ID, prescriber name, prescriber contact information, etc.)
・ Information about the dispensed medicine (drug name, dispensing date, prescription days, prescription date, dose, usage, remaining medicine, etc.)
-Information regarding the patient's consent to the information provision-Tracing report generation date-Tracing report transmission date-Information regarding the type of information provision (classification of prescription change proposals, adverse event reports, etc.) These information can be found on the server 30. It may be obtained from a database, or it may be obtained from a database other than the server 30.

Further, in the modified example 4, after the step S130, the steps S131 (FIG. 13) and subsequent steps may be executed in the same manner as in the modified example 2. In this case, the new record is added in the record associated with the communication ID included in the presentation response data in step S350. That is, in the communication information database (FIG. 22), the exchange of messages related to a certain reservation ID is stored in association with one communication ID.

Further, in the modification 4, the server 30 transmits the tracing report for transmission to the prescriber contact, but the server 30 transmits the tracing report for transmission generated in step S356 to the dispenser terminal. It may be transmitted to 10 and displayed and printed on the dispenser terminal 10. Then, the prescribing person may manually send the printed tracing report for transmission to the prescribing person's contact information via a normal fax or the like.

Further, in the fourth modification, the prescriber identification information is specified by the dispenser in step S155, but the dispenser may specify it in step S110, for example. In this case, for example, the prescriber name is associated with the reservation ID of the reservation information database (FIG. 6) and stored, and based on the reservation ID (FIG. 22) associated with the communication ID included in the report generation request data in step S355. Prescriber identification information is identified. Then, the prescriber identification information specified in the field object F502a on the screen P502 is displayed.

According to the fourth modification, it is possible to generate a tracing report including the patient identification information and the information based on the reply message. Therefore, the dispenser can easily create a tracing report to be sent to the prescriber.
Further, according to the modification 4, the generated tracing report can be transmitted to the prescribing person via the server. Therefore, the dispenser can more easily send the tracing report to the prescriber than manually sending it via a normal fax or the like.

(5-5) Modification 5
Modification 5 will be described. Modification 5 is an example of determining whether or not it is recommended that the patient be subject to follow-up as the first patient, based on at least one of the patient information about the patient and the dispensing drug information about the dispensed drug. Is. Here, an example of using drug history information as patient information will be described. Further, in the modified example 5, an example of presenting a candidate for the follow-up content based on at least one of the patient information and the dispensing drug information will also be described.

(5-5-1) Candidate Information Database The candidate information database of the modification 5 will be described. FIG. 27 is a diagram showing a data structure of the candidate information database of the modification example 5.

The candidate information database of FIG. 27 stores information about candidates for follow-up content.
The candidate information database includes a "candidate ID" field, a "condition" field, and a "follow-up content candidate" field. Each field is associated with each other.

A candidate ID is stored in the "candidate ID" field. The candidate ID is an example of identification information that identifies a candidate for follow-up content.

The "Condition" field stores condition information regarding the condition for presenting the corresponding follow-up content candidate. The conditions are set, for example, in the following cases.
・ When a specific drug (for example, a drug with strong side effects or difficult to control) is dispensed ・ When a drug that has never been taken is dispensed ・ The dose or usage is changed from before When dispensed ・ When another medicine is dispensed while taking a specific medicine

The "follow-up content candidate" field stores follow-up content candidate information regarding the follow-up content candidate. Follow-up content Candidate information is, for example, calculation for calculating a follow-up date based on at least one of a candidate follow-up name and a candidate date and time for follow-up (dispensing date and prescription days). Includes at least one of the formula and information about the candidate time) and the candidate message. One or more follow-up content candidate information is included for one candidate ID.

(5-5-2) Information Processing The information processing of the modified example 5 will be described. FIG. 28 is a sequence diagram of information processing of the modified example 5. FIG. 29 is a diagram showing an example of a screen displayed in the information processing of the modified example 5. FIG. 30 is a diagram showing an example of a screen displayed in the information processing of the modified example 5.

As shown in FIG. 28, the dispensing person terminal 10 executes the reception of dispensing drug information (S160).
Specifically, the processor 12 displays the screen P600 (FIG. 29) on the display.

The screen P600 includes field objects F600a to F600d and operation objects B600.
The field object F600a is an object that receives a user instruction for designating patient identification information (for example, a patient name, a patient ID, or a combination of a patient name and a patient ID) of a patient to whom a drug has been dispensed by a dispenser. ..
The field object F600b is an object that receives a user instruction for designating a date (dispensing date) of dispensing a drug to a patient.
The field object F600c is an object that receives a user instruction for designating the number of prescription days for the drug.
The field object F600d is an object that receives a user instruction for designating the name (drug name) of the drug.
The operation object B600 is an object that receives a user instruction for transmitting the user instruction input to the field objects F600a to F600d to the server 30.

After step S160, the dispenser terminal 10 executes the recommendation determination request (S161).
Specifically, when the dispenser inputs user instructions to the field objects F600a to F600d and operates the operation object B600, the processor 12 transmits the recommended determination request data to the server 30.
The recommended judgment request data includes the following information.
・ Dispenser ID
-Patient identification information specified in the field object F600a-Information on the dispensing date specified in the field object F600b (an example of "dispensing drug information")
-Information on the number of prescription days specified in the field object F600c (an example of "dispensing drug information")
-Information on the drug name specified in the field object F600d (an example of "dispensing drug information")

After step S161, the server 30 executes the presentation of the recommended determination result (S360).
Specifically, the processor 32 refers to the patient information database (FIG. 5) to identify the drug history associated with the patient identification information included in the recommendation determination request data.
The processor 32 is included in the identified drug history, the dispensing date included in the recommended determination request data, the number of prescription days included in the recommended determination request data, and the recommended determination request data with reference to the candidate information database (FIG. 27). Determine if the patient is recommended for follow-up based on the drug name given. More specifically, the processor 32 is based on the identified drug history, the dispensing date included in the recommended determination request data, the number of prescription days included in the recommended determination request data, and the drug name included in the recommended determination request data. It is determined whether or not each condition included in the "condition" field of the candidate information database (FIG. 27) is satisfied.
If there are applicable conditions, the processor 32 determines that it is recommended that the patient be subject to follow-up. On the other hand, if none of the conditions are met, the processor 32 determines that the patient does not have to be subject to follow-up. The processor 32 specifies the applicable condition, if any.
The processor 32 transmits the recommended determination response data to the dispenser terminal 10. The recommended judgment response data includes the following information.
・ Information on the judgment result of whether or not the patient is recommended to be subject to follow-up ・ Information on applicable conditions (only if applicable conditions are available)

After step S360, the dispenser terminal 10 executes the display of the recommended determination result (S162).
Specifically, the processor 12 displays the screen P601 (FIG. 29) on the display.

The screen P601 includes a display object A601 and operation objects B601a to B601b.
The display object A601 includes information on the determination result included in the recommended determination response data and information on the applicable conditions (only when there are applicable conditions).
The operation object B601a is an object that receives a user instruction for transmitting a user instruction that the follow-up content is not set to the server 30.
The operation object B601b is an object that receives a user instruction for transmitting a user instruction for setting the follow-up content to the server 30.
Even when it is determined that the follow-up target does not have to be applied, the operation object B601a and the operation object B601b are displayed, and the dispenser can set the follow-up content as necessary.

After step S162, when the dispenser operates the operation object B601a, the processor 12 transmits request data including user instruction information that the follow-up content is not set to the server 30. This ends the process.

On the other hand, when the dispenser operates the operation object B601b after step S162, the dispenser terminal 10 executes the setting request (S163).
Specifically, when the dispenser operates the operation object B601b, the processor 12 transmits the setting request data to the server 30.

After step S163, the server 30 executes the candidate presentation (S361).
Specifically, the processor 32 identifies follow-up content candidates associated with the conditions identified in step S360. Similar to step S320 of the first modification, the processor 32 calculates a specific date in the candidate date and time using the calculation formula stored in the “follow-up content candidate” field.
The processor 32 transmits the candidate presentation response data to the dispenser terminal 10. The candidate presentation response data includes the following information.
-Information about identified follow-up content candidates (combination of calculated date, follow-up time and follow-up message)

After step S361, the dispenser terminal 10 executes the reception of the follow-up content (S164).
Specifically, the processor 12 displays the screen P602 (FIG. 30) on the display.

The screen P602 includes a field object F602 and an operation object B602.
The field object F602 is an object that receives a user instruction for designating the content of the follow-up. The field object F602 displays information about follow-up content candidates included in the candidate presentation response data.
The operation object B602 is an object that receives a user instruction for transmitting the user instruction input to the field object F602 to the server 30.

After step S164, the dispenser terminal 10 executes a reservation request (S165).
Specifically, when the dispenser inputs a user instruction to the field object F602 and operates the operation object B602, the processor 12 transmits the reservation request data to the server 30.
More specifically, when the dispenser does not wish to change from the follow-up content candidate, the dispenser operates the operation object B602 with the content displayed in the field object F602. On the other hand, when the dispenser wishes to change from the follow-up content candidate, the dispenser changes the follow-up content displayed in the field object F602 and operates the operation object B602. Changes in follow-up content include, for example, changing the date and time, changing the message, deleting a part of a plurality of date and time and a combination of messages, or adding a date and time and a message.
The reservation request data includes the following information.
・ Dispenser ID
-Information on patient identification information specified in field object F600a-Information on follow-up content (combination of follow-up date and time and follow-up message) specified in field object F602

After step S165, the server 30 executes the update of the reservation information database (S362).
Specifically, the processor 32 refers to the patient information database (FIG. 5) and refers to the patient ID (that is, the patient of the first patient to be followed up) associated with the patient identification information included in the appointment request data. ID) is specified. The processor 32 adds a new record to the reservation information database (FIG. 6) associated with the dispenser ID included in the reservation request data and the identified patient ID. The following information is stored in each field of the new record.
-A new reservation ID is stored in the "reservation ID" field.
-The date and time included in the reservation request data is stored in the "Date and time" field. One date and time is stored in one record.
-The "Message" field stores the follow-up message included in the reservation request data. Follow-up messages are stored in the corresponding date and time records.
-"Unprocessed" is stored in the "Status" field.

After step S362, the server 30 executes the presentation of the follow-up message (S311) as in the present embodiment.

After step S311 the patient terminal 50 executes a follow-up message display (S560).
Specifically, the processor 52 displays the screen P603 (FIG. 30) on the display based on the presentation response data.

The screen P603 includes the display object A603.
The display object A603 includes a follow-up message included in the presentation response data.

In the modified example 5, the drug history is used as the patient information, but the present invention is not limited to this. Examples of patient information include the following.
・ Medical history ・ Current medical history ・ Attributes (age, gender)
・ Lifestyle (drinking, smoking, sleeping, eating, exercising, etc.)
・ Allergy history ・ Family history ・ Pregnancy ・ Questionnaire results (for example, questionnaire results for determining the presence or absence of risk in taking medicine or the degree of the risk (for example, questionnaire result for determining dementia risk or swallowing function) )
-Presence or absence of risk in taking other drugs In addition, as an example based on the combination of patient information and dispensing drug information, there is a case where a pregnant patient is dispensed a specific drug.

Further, in step S160, the patient identification information and the dispensing drug information do not have to be input by the dispensing person. For example, the patient identification information and the dispensing drug information may be acquired from an external server (for example, a dispensing management system) other than the server 30. For example, when information about dispensing is newly input to an external server (for example, a dispensing management system) other than the server 30, patient identification information and dispensing drug information may be transmitted to the server 30.

Further, in step S360, when there are a plurality of applicable conditions, the processor 32 identifies the condition having the highest degree of conformity, and the recommended determination response data may include only the information related to the condition. In this case, in step S164, only follow-up content candidates for the condition are presented.
Alternatively, if there are a plurality of applicable conditions, follow-up content candidates for all applicable conditions may be presented.

According to the fifth modification, it is determined whether or not it is recommended that the patient be the subject of follow-up as the first patient, based on at least one of the patient information and the dispensing drug information. Therefore, it is suggested that patients who meet the predetermined conditions are recommended to be subject to follow-up. Therefore, the dispenser can easily know the patients who have a high need for follow-up.
Further, according to the modified example 5, a candidate for follow-up content is presented to the dispenser based on at least one of the patient information and the dispensing drug information regarding the first patient. Therefore, the dispenser can easily know the appropriate follow-up content for the first patient. In addition, the dispenser can perform appropriate follow-up for the first patient.

(6) Summary of the present embodiment A summary of the present embodiment will be given.

The first aspect of this embodiment is
A means for associating and storing the patient identification information for identifying the patient and the patient contact information regarding the patient's contact information (for example, the processor 32 for managing the patient information database (FIG. 5)) is provided.
A means for receiving a follow-up content designation from a user (for example, a dispenser) for a first patient to whom a drug has been dispensed (for example, a processor 32 that executes the process of step S310, or a processor that executes the process of step S341). 32)
A means for presenting information according to the content of the follow-up (for example, a processor 32 that executes the process of step S311 or a processor 32 that executes the process of step S342) is provided.
An information processing device (for example, a server 30).

According to the first aspect, the dispenser can specify the desired follow-up content for the patient. As a result, the dispenser can carry out follow-up from various viewpoints such as effects, side effects, and medication status. Therefore, the dispenser can carry out a more complete follow-up for the patient.

The second aspect of this embodiment is
The means of accepting accepts the designation of the date and time for follow-up,
It is an information processing device.

According to the second aspect, the dispenser can perform follow-up on the patient at a desired date and time.

The third aspect of this embodiment is
A means for obtaining information on at least one of the drug dispensing date and the number of prescription days (eg, processor 32 performing the process of step S320) is provided.
The receiving means presents to the user (eg, the dispenser) a candidate date for follow-up based on at least one of the date the drug was dispensed and the number of prescription days.
It is an information processing device.

According to the third aspect, the dispenser can easily specify the date for follow-up. Dispensers can also specify an appropriate date for follow-up.

The fourth aspect of this embodiment is
The means of presentation presents a follow-up message corresponding to the content of the follow-up to the contact corresponding to the patient contact information associated with the first patient.
It is an information processing device.

According to the fourth aspect, the dispenser does not need to perform oral follow-up on the first patient, and the effort in performing the follow-up on the first patient is reduced.

A fifth aspect of this embodiment is
A means for receiving a reply message designation to a user (for example, a dispenser) from a first patient (for example, a processor 32 for executing the process of step S331) is provided.
A means for presenting a reply message to a user (for example, a dispenser) (for example, a processor 32 that executes the process of step S331) is provided.
It is an information processing device.

According to the fifth aspect, the first patient can send a reply message to the follow-up message from the dispenser. As a result, the dispenser can know the situation of the first patient and the like. Therefore, the dispenser can perform a more complete follow-up.

The sixth aspect of this embodiment is
A means for acquiring patient identification information and patient contact information based on the information of the two-dimensional code for the electronic version of the medicine notebook (for example, the processor 32 that executes the process of step S340) is provided.
The presenting means presents the user (eg, the dispenser) with information about the content of the follow-up and patient contact information associated with the first patient.
It is an information processing device.

According to the sixth aspect, it is possible to avoid erroneous input that may occur due to manual input. Further, as compared with the case of acquiring from the external system, the patient identification information and the patient contact information can be easily acquired without depending on the specifications of the external system. In addition, when using a patient contact that cannot present the text of the message (for example, a fixed-line telephone number), the dispenser is provided with information on the content of the follow-up and the patient contact information of the first patient. Can be presented. Therefore, the dispenser has less effort in managing the implementation of follow-up. Also, the dispenser can follow up with the patient even if the patient does not have a device capable of presenting the text of the message.

The seventh aspect of this embodiment is
A means for generating a tracing report including patient identification information of a first patient and information based on a reply message (for example, a processor 32 that executes the process of step S356) is provided.
It is an information processing device.

According to the seventh aspect, the dispenser can easily prepare a tracing report to be sent to the prescriber.

The eighth aspect of this embodiment is
A means of transmitting a tracing report to a person who prescribes a drug (for example, a processor 32 that executes the process of step S356).
It is an information processing device.

According to the eighth aspect, the dispenser can send the tracing report to the prescriber more easily than manually sending it via a normal fax or the like.

A ninth aspect of the present embodiment is a means for presenting a candidate for follow-up content (for example, performing the process of step S361) based on at least one of the patient information regarding the first patient and the dispensing drug information regarding the dispensed drug. Processor 32)
It is an information processing device.

According to the ninth aspect, the dispenser can easily know the appropriate follow-up content for the first patient. In addition, the dispenser can perform appropriate follow-up for the first patient.

The tenth aspect of the present embodiment is whether or not it is recommended that the patient be subject to follow-up as the first patient based on at least one of the patient information regarding the patient and the dispensing drug information regarding the dispensed drug. (For example, the processor 32 that executes the process of step S360) is provided.
It is an information processing device.

According to the tenth aspect, the dispenser can easily know the patient who has a high need for follow-up.

The eleventh aspect of this embodiment is
It is a program for making a computer (for example, a processor 32) function as each of the above means.

(7) Other Modification Examples Other modification examples will be described.

The storage device 11 may be connected to the dispenser terminal 10 via the network NW. The storage device 31 may be connected to the server 30 via the network NW. The storage device 51 may be connected to the patient terminal 50 via the network NW.

Each step of the above information processing can be executed by any of the dispenser terminal 10, the server 30, and the patient terminal 50.
For example, when the dispenser terminal 10 can execute all the steps of the above information processing, the dispenser terminal 10 functions as an information processing device that operates standalone without sending a request to the server 30.

In this embodiment and each modification, each message is a text, but the present invention is not limited to this. The message may be image data, various file data such as PDF files, and the like. Further, the message may be in the form of an input form. For example, as a follow-up message, an input form containing one or more questions from the dispenser to the first patient is presented to the first patient, and as a reply message, the first patient inputs an answer to the question in the input form (eg,). (Select an option or enter text).

In the first modification, the dispensing date and the number of prescription days of the drug are, for example, to be affixed to image data (a dispensing fee statement given from the dispenser to the first patient together with the drug, a dosing manual, or a medication notebook). It may be obtained from the seal, etc.). The image data of the dispensing fee statement or the like may be an entire image of the dispensing fee statement or the like, or may be a partial image of the dispensing fee statement or the like. Examples of a partial image of the dispensing fee statement or the like include an image of a two-dimensional code described in the dispensing fee statement or the like. The screen P200 (FIG. 11) includes, instead of the field objects F200b to F200c, an object that receives a user instruction for designating an image such as a dispensing fee statement of the first patient. The image data is input via, for example, a camera (not shown) connected to the dispenser terminal 10. The dispensing person terminal 10 or the server 30 processes the image data to acquire information on the dispensing date and the number of prescription days. As a method of image processing, in addition to the two-dimensional code, OCR processing of characters described in a dispensing fee statement or the like can be mentioned. As a result, it is possible to avoid erroneous input that may occur due to manual input.

Further, in the first modification, the dispensing date and the prescribing date of the drug may be obtained from, for example, a system provided by an external server (for example, a system for managing the drug history).

In the first modification, the follow-up name may be included as the follow-up content candidate presented. Since the follow-up name is a name that simply expresses the content of the follow-up, the dispenser can quickly grasp the follow-up content candidate on the screen P201.

In the second modification, the reply message and the re-reply message may be able to be selected and edited from the message candidates. For example, message candidates such as "effective" and "not effective" are presented as reply message candidates to the follow-up message about the effect. As a result, the patient can easily specify the reply message. In addition, the dispenser can easily specify the re-reply message.

In the third modification, the image data may be processed by the dispenser terminal 10. In this case, the patient information registration request data includes the patient identification information and the patient contact information acquired by the dispenser terminal 10 instead of the image data, and the server 30 uses the patient information registration request data to provide the patient identification information and the patient identification information. Get patient contact information. In addition to the two-dimensional code, the image processing method includes OCR processing of characters described on a paper medium such as a dispensing fee statement or an instruction manual for administration.

The information processing apparatus of the present invention may include means for outputting the follow-up contents for the first patient as a CSV file. Further, the information processing apparatus of the present invention may include means for outputting the content of the reply message as a CSV file. This facilitates posting to a system provided by an external server (for example, a system for managing drug history).

The information processing apparatus of the present invention may include means for transcribing a CSV file to another system (for example, a system for managing drug history). This facilitates posting to a system provided by an external server (for example, a system for managing drug history).

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above embodiments. Further, the above-described embodiment can be improved or modified in various ways without departing from the spirit of the present invention. Moreover, the above-described embodiment and modification can be combined.

1: Information processing system 10: Dispenser terminal 11: Storage device 12: Processor 13: Input / output interface 14: Communication interface 30: Server 31: Storage device 32: Processor 33: Input / output interface 34: Communication interface 50: Patient terminal 51 : Storage device 52: Processor 53: Input / output interface 54: Communication interface

Claims (11)

A means for associating and storing the patient identification information for identifying the patient and the patient contact information regarding the patient's contact information is provided.
Provided a means for accepting the specification of follow-up contents for the first patient to whom the drug was dispensed from the user.
A means for presenting information according to the content of the follow-up is provided.
Information processing device. The receiving means accepts the designation of the date and time for performing the follow-up.
The information processing device according to claim 1. Provided with means for obtaining information on at least one of the date of dispensing and the number of prescription days of the drug.
The accepting means presents to the user a candidate date for the follow-up based on at least one of the date and the number of prescription days.
The information processing device according to claim 2. The presenting means presents a follow-up message corresponding to the follow-up to a contact corresponding to the patient contact information associated with the first patient.
The information processing device according to any one of claims 1 to 3. A means for receiving a reply message to the user from the first patient is provided.
A means for presenting the reply message to the user.
The information processing device according to any one of claims 1 to 4. A means for acquiring the patient identification information and the patient contact information based on the information of the two-dimensional code for the electronic version of the medicine notebook is provided.
The presenting means presents to the user information about the content of the follow-up and patient contact information associated with the first patient.
The information processing device according to any one of claims 1 to 5. A means for generating a tracing report including the patient identification information of the first patient and the information based on the reply message.
The information processing device according to claim 5. A means for transmitting the tracing report to the person who prescribed the drug.
The information processing device according to claim 7. A means for presenting a candidate for the content of the follow-up based on at least one of the patient information regarding the first patient and the dispensing drug information regarding the dispensed drug.
The information processing device according to any one of claims 1 to 8. A means for determining whether or not the patient is recommended to be followed up as the first patient based on at least one of the patient information about the patient and the dispensing drug information about the dispensed drug.
The information processing device according to any one of claims 1 to 9. A program for operating a computer as each means according to claims 1 to 10.

Images