JP7463570B2 - Information processing system, information processing device, information processing method, and program - Google Patents

Description

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

Conventionally, when dispensing medicines at a dispensing pharmacy, a patient submits a prescription, and a pharmacist prepares medicines based on the prescription after interviewing the patient, etc. Then, the pharmacist explains the medicine to the patient, etc., and the medicine is issued to the patient.
As a technique for supporting communication between pharmacists and patients in such dispensing activities, the technique described in Patent Document 1 is known.
In other words, Patent Document 1 discloses a medication information system that outputs medication-related information based on the situation of each prescription recipient and a protocol for selecting the medication-related information to be output according to that situation, thereby providing appropriate and detailed medication instructions to each prescription recipient, regardless of the pharmacist's ability.

JP 2016-122253 A

However, in conventional techniques, including the technique described in Patent Document 1, patients find it difficult to feel familiar with pharmacists, which may be an impediment to the pharmacist's communication with the patient. In addition, the patient may not fully understand the information about the drug (such as changes in the prescribed drug) that the pharmacist has explained to the patient, and the patient may not be able to fully utilize the pharmacist's explanation when taking the drug. Furthermore, when multiple drugs are prescribed or when the pharmacist provides special instructions to the patient (such as instructions on a drug taking schedule that takes daily life into consideration), the method of taking the drug may become complicated, and the patient may not be able to take the drug appropriately.
As described above, with conventional techniques, it has been difficult to appropriately support communication between pharmacists and patients.

The objective of this invention is to better support communication between pharmacists and patients.

In order to solve the above problems, an information processing system according to one aspect of the present invention comprises:
An information processing system including a pharmacy computer installed in a pharmacy, a pharmacist terminal used by a pharmacist, and a server for managing data used in the pharmacy,
The pharmacy computer includes:
A prescription data acquisition means for acquiring data of a patient's prescription;
A prescription data transmission means for transmitting the prescription data acquired by the prescription data acquisition means to the server;
Equipped with
The server,
a change acquisition means for acquiring change information regarding drugs that have been changed between the past prescription content and the current prescription content for the patient based on the prescription data transmitted from the pharmacy computer and the past prescription data for the patient corresponding to the prescription data;
A change data transmission means for transmitting the change drug information data to the pharmacist terminal;
Equipped with
The pharmacist terminal includes:
A screen display means for displaying a screen for presenting information on a drug related to the prescription, including the changed drug information, to the patient based on the changed drug information data transmitted from the server;
an operation receiving means for receiving an operation input to the screen displayed by the screen display means;
Equipped with
The screen display means changes the display contents of the drug information in response to an operation input to the screen.

The present invention can better support communication between pharmacists and patients.

1 is a diagram showing a system configuration of an information processing system 1 according to an embodiment of the present invention. FIG. 8 is a diagram showing a hardware configuration of an information processing device 800 constituting each device. 2 is a block diagram showing the functional configuration of the pharmacy computer 10. FIG. FIG. 2 is a block diagram showing the functional configuration of the server 20. 2 is a block diagram showing the functional configuration of a pharmacist terminal 30. FIG. 10 is a flowchart showing the flow of a drug information output process executed by the pharmacy computer 10. 13 is a flowchart showing the flow of a data generation process executed by the server 20. 13 is a flowchart showing the flow of a communication support process executed by the pharmacist terminal 30. FIG. 13 is a schematic diagram showing an example of an initial screen displayed in the communication support process. FIG. 13 is a schematic diagram showing an example of a pharmacist's profile screen. FIG. 13 is a schematic diagram showing an example of a questionnaire screen. FIG. 13 is a schematic diagram showing an example of a state in which a questionnaire has been answered; FIG. 13 is a schematic diagram showing an example of a display screen showing the contents of changed drug information. 14 is a schematic diagram showing an example of a state in which a pharmacist has performed an operation to explain the prescription contents to a patient on the display screen shown in FIG. 13. FIG. 13 is a schematic diagram showing an example of a state in which the arrangement of items displayed in a list is changed; FIG. FIG. 13 is a schematic diagram showing an example of a schedule presented to a patient. FIG. 13 is a schematic diagram showing an example of an interface screen for inputting stamp data. FIG. 13 is a schematic diagram showing an example of an interface screen for inputting handwritten characters. FIG. 13 is a schematic diagram showing an example of an interface screen for registering a new schedule. FIG. 13 is a schematic diagram showing an example of an interface screen for editing an already input schedule. FIG. 13 is a schematic diagram showing an example of a screen displaying a message to the effect that any consultation matter is accepted. FIG. 13 is a schematic diagram showing an example of a provision document (changes in medication information) provided to a patient. FIG. 13 is a schematic diagram showing an example of a provision document (changes in medication information) provided to a patient. FIG. 2 is a schematic diagram showing an example of a provided document (related document) provided to a patient.

The following describes an embodiment of the present invention with reference to the drawings.

The information processing system 1 according to the present embodiment is for displaying information about drugs while displaying a predetermined profile of the pharmacist when a pharmacist and a patient converse in a dispensing pharmacy, thereby stimulating the patient's interest and affinity with the pharmacist and supporting smoother dialogue. In addition, the information processing system 1 according to the present embodiment supports the patient to more easily refer to the explanation contents from the pharmacist to the patient even when taking the drug by issuing a drug information provision document (hereinafter, appropriately referred to as "drug information") that reflects the explanation contents when the pharmacist explains information about the drug (such as changes in the prescribed drug between the past prescription contents and the current prescription contents) to the patient regarding the information (prescription contents) written on the prescription issued to the patient. Furthermore, the information processing system 1 according to the present embodiment supports the patient to take the appropriate drug by presenting the explanation contents from the pharmacist to the patient, such as the method of taking the prescribed drug, as information in a form that is easy for the patient to understand.
A specific configuration will be described below.

[System configuration of information processing system 1]
FIG. 1 is a diagram showing a system configuration of an information processing system 1 according to an embodiment of the present invention.
As shown in Fig. 1, the information processing system 1 includes a pharmacy computer 10, a server 20, and a pharmacist terminal 30, and the pharmacy computer 10, the server 20, and the pharmacist terminal 30 are configured to be able to communicate with each other via a network 40. The pharmacy computer 10 and the pharmacist terminal 30 are installed in the same dispensing pharmacy. Furthermore, the information processing system 1 according to this embodiment is operated, for example, in a predetermined region, and one server 20 is installed for the pharmacy computers 10 and the pharmacist terminals 30 installed in multiple dispensing pharmacies belonging to that region. For convenience of explanation, only one pharmacy computer 10 and one pharmacist terminal 30 are shown in Fig. 1.

The pharmacy computer 10 is configured as a PC (Personal Computer) or a server computer, and has a function of managing medical history and creating a medical fee statement (receipt). The pharmacy computer 10 accepts input of prescription data from patients, and accumulates and manages the accepted prescription data. The pharmacy computer 10 also calculates details of medical fees for dispensing to patients based on prescriptions. The pharmacy computer also receives print data of a drug information document (medication information) and a document to be provided to patients (described below) including predetermined related documents from the server 20, and prints the document to be provided by a printer installed in the dispensing pharmacy. In this embodiment, the drug information document (medication information) is configured as a document or a document equivalent (for example, a sticker that can be attached to a notebook) that shows information on the name, usage, dosage, efficacy, effect, side effects, and interactions of the drug.

The server 20 is composed of a server computer, acquires prescription data accepted by the pharmacy computer 10, and generates data for a pharmacist profile screen to be presented to the patient. The server 20 also accumulates and manages prescription data accepted by the pharmacy computer 10, and generates data on changes to the medication prescribed to the patient (changes between the past (previous) prescription and the current prescription). This data on changes is sent to the pharmacist terminal 30 and displayed on the screen, or sent to the pharmacy computer 10 and printed out as part of the medication information. Furthermore, the server 20 manages schedule data, such as a medication schedule (medication schedule) or a pharmacy visit schedule, for each patient.

The pharmacist terminal 30 is configured as a tablet terminal or a notebook PC, acquires profile screen data generated by the server 20, and displays the pharmacist's profile on the display screen when the pharmacist communicates with the patient. The pharmacist terminal 30 also acquires data on changes to medications generated by the server 20, and displays a comparison of the medication before and after the change when the pharmacist communicates with the patient. Furthermore, the pharmacist terminal 30 accepts input of schedule data for the patient, such as a medication administration schedule or a visit schedule, and transmits the input schedule data to the server 20.

[Hardware configuration]
Next, the hardware configuration of each device in the information processing system 1 will be described.
In the information processing system 1, each device is configured by an information processing device such as a PC, a server computer, or a tablet terminal, and the basic configurations of the devices are the same.

FIG. 2 is a diagram showing the hardware configuration of the information processing device 800 constituting each device.
As shown in FIG. 2 , the information processing device 800 constituting each device includes a CPU (Central Processing Unit) 811, a ROM (Read Only Memory) 812, a RAM (Random Access Memory) 813, a bus 814, an input unit 815, an output unit 816, a storage unit 817, a communication unit 818, a drive 819, and an imaging unit 820.

The CPU 811 executes various processes according to a program recorded in the ROM 812 or a program loaded from the storage unit 817 to the RAM 813 .
The RAM 813 also stores data and the like necessary for the CPU 811 to execute various processes.

The CPU 811, ROM 812, and RAM 813 are connected to each other via a bus 814. The input unit 815, output unit 816, memory unit 817, communication unit 818, drive 819, and imaging unit 820 are also connected to the bus 814.

The input unit 815 is made up of various buttons and the like, and inputs various information in response to instruction operations.
The output unit 816 is composed of a display, a speaker, etc., and outputs images and sounds.
In addition, when the information processing device 800 is configured as a smartphone or a tablet terminal, the displays of the input unit 815 and the output unit 816 may be arranged so as to overlap each other to configure a touch panel.
The storage unit 817 is configured with a hard disk or a dynamic random access memory (DRAM) or the like, and stores various data managed by each server.
The communication unit 818 controls communication with other devices via the network.

Removable media 831, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is appropriately loaded into the drive 819. A program read from the removable media 831 by the drive 819 is installed in the storage unit 817 as necessary.
The imaging unit 820 is configured with an imaging device including a lens, an imaging element, etc., and captures a digital image of a subject.
When the information processing device 800 is configured as the server 20, it is also possible to omit the imaging unit 820. When the information processing device 800 is configured as a tablet terminal, it is also possible to configure the input unit 815 using a touch sensor and arrange it over the display of the output unit 816, thereby providing a touch panel.

[Functional configuration]
Next, the functional configuration of each device in the information processing system 1 will be described.
[Functional Configuration of Pharmacy Computer 10]
FIG. 3 is a block diagram showing the functional configuration of the pharmacy computer 10. As shown in FIG.
3, a prescription data acquisition unit 51, a prescription data transmission unit 52, a patient attribute acquisition unit 53, a patient attribute transmission unit 54, a print data receiving unit 55, and a print control unit 56 function in the CPU 811 of the pharmacy computer 10. In addition, a prescription database (prescription DB) 71 and a patient attribute database (patient attribute DB) 72 are formed in the storage unit 817 of the pharmacy computer 10.

The prescription DB 71 stores data on prescriptions accepted by the pharmacy computer 10. This prescription data includes information for identifying the patient, such as the patient's name, age, sex, and insurer number, information for identifying the medical institution that issued the prescription, such as the name of the medical institution, the doctor's name, and the medical institution's contact information, and information indicating the prescription contents, such as the name of the prescribed drug, dosage form, usage and dosage, and whether or not it can be changed to a generic drug.
The patient attribute DB 72 stores data on the address, name, age, sex, and information (patient attributes) that represents the characteristics of each patient. The patient attributes are composed of information acquired by the pharmacist in conversation with the patient, information provided by the patient in response to a questionnaire (interview), etc., and include, for example, the patient's hobbies, work, family structure, favorite food, favorite color, favorite character, and concerns in daily life (physical pain, etc., directly related to medical care, or concerns about a child's education, etc., not directly related to medical care).

The prescription data acquisition unit 51 acquires data (prescription data) representing the contents of a prescription brought by a patient and accepted by a dispensing pharmacy. In this embodiment, the prescription data acquisition unit 51 acquires prescription data generated when a pharmacist or operator at the dispensing pharmacy inputs the contents of the prescription brought by the patient via the input unit 815. Note that if the prescription is issued as electronic data, the prescription data acquisition unit 51 may acquire the prescription data by reading the data from a storage medium in which the prescription data is stored, or by receiving the data via a network.

In addition, the prescription data acquisition unit 51 stores the acquired prescription data in the prescription DB 71. Among the prescription data, information for identifying a patient is also appropriately stored in the patient attribute DB 72 when the patient is a new patient or when the information for identifying the patient has changed.
The prescription data transmission unit 52 transmits the prescription data acquired by the prescription data acquisition unit 51 to the server 20.

The patient attribute acquisition unit 53 acquires data on the patient attributes of the patient corresponding to the prescription data. The patient attribute data is generated by a pharmacist having a conversation with the patient prior to the patient's visit and inputting the data using the pharmacist's terminal 30, or by a pharmacist or operator at the dispensing pharmacy inputting the results of a questionnaire given to the patient via the input unit 815, and is stored in the patient attribute DB 72.

The patient attribute transmission unit 54 transmits the patient attribute data acquired by the patient attribute acquisition unit 53 to the server 20 .
The print data receiving unit 55 receives print data of documents to be provided to patients, including drug information documents (drug information), transmitted from the server 20 .
Based on the print data received by the print data receiving unit 55, the print control unit 56 prints a document to be provided to the patient, including the medication information, from a printer installed in the dispensing pharmacy.

[Functional configuration of server 20]
FIG. 4 is a block diagram showing the functional configuration of the server 20. As shown in FIG.
4, in the CPU 811 of the server 20, a prescription data receiving unit 151, a patient attribute receiving unit 152, a profile screen data generating unit 153, a profile screen data transmitting unit 154, a change acquisition unit 155, a change data transmitting unit 156, an operation content receiving unit 157, a print data generating unit 158, and a print data transmitting unit 159 function. In addition, in the storage unit 817 of the server 20, a pharmacist profile database (pharmacist profile DB) 171, a prescription database (prescription DB) 172, a patient attribute database (patient attribute DB) 173, a drug database (drug DB) 174, a pharmacy-specific drug use database (pharmacy-specific drug use DB) 175, a change point drug information database (change point drug information DB) 176, and a schedule database (schedule DB) 177 are formed.

Pharmacist profile DB171 stores data on the profiles of pharmacists affiliated with each dispensing pharmacy (pharmacist's photo, name, age, marital status, gender, specialty, details of community activities, current area of focus and motivation for becoming a pharmacist, reasons for becoming a pharmacist, joys of becoming a pharmacist, hobbies, etc.). This pharmacist profile data is input and stored each time a pharmacist joins a dispensing pharmacy. It is also possible to change a pharmacist's profile as appropriate according to the pharmacist's wishes, etc.

The prescription DB 172 stores data of the prescription DB 71 stored in the pharmacy computer 10 of each dispensing pharmacy. That is, the prescription DB 172 stores data of the prescription DB 71 of each dispensing pharmacy in a consolidated manner for a predetermined area in which the server 20 is operated.
The patient attribute DB 173 stores data of the patient attribute DB 72 stored in the pharmacy computer 10 of each dispensing pharmacy. That is, the patient attribute DB 173 stores an aggregate of data of the patient attribute DB 72 of each dispensing pharmacy for a predetermined area in which the server 20 is operated.

Data representing information on various drugs is stored in the drug DB 174. For example, data such as information on package inserts and drug prices of various drugs is stored in the drug DB 174.
Data representing drugs used for dispensing at each dispensing pharmacy is stored in the drug-used-by-pharmacy DB 175. The data stored in the drug-used-by-pharmacy DB 175 is updated as appropriate based on an application from each dispensing pharmacy when the drug used at each dispensing pharmacy is changed, for example.

The changed drug information DB 176 stores information on drugs that have been changed between the previous prescription content and the current prescription content for a patient (hereinafter referred to as "changed drug information" as appropriate). For example, the changed drug information DB 176 stores, as changed drug information, information on drugs that have been added to the previous prescription content for the same patient, drugs that have been discontinued from the previous prescription content, or other drugs that have been changed from drugs included in the previous prescription content.
Schedule data for each patient is stored in the schedule DB 177. This schedule data reflects various specific schedules of the patient (such as a drug intake schedule and a visit schedule) that the pharmacist has entered through a conversation with the patient using the pharmacist terminal 30.

The prescription data receiving unit 151 receives prescription data transmitted from the pharmacy computer 10. Then, the prescription data receiving unit 151 stores the received prescription data in the prescription DB 172.
The patient attribute receiving unit 152 receives the data of the patient attributes transmitted from the pharmacy computer 10. Then, the patient attribute receiving unit 152 stores the received data of the patient attributes in the patient attribute DB 173.

When the pharmacist terminal 30 requests the generation of a profile screen for presenting a pharmacist's profile to a patient, the profile screen data generation unit 153 reads out the profile data of the pharmacist for which the profile screen is to be generated and the patient attributes of the patient to whom the profile screen is to be presented from the pharmacist profile DB 171 and the patient attribute DB 173, respectively. Then, the profile screen data generation unit 153 generates profile screen data for presenting the pharmacist's profile to the patient based on the profile data of the pharmacist for which the profile screen is to be generated and the patient attributes of the patient to whom the profile screen is to be presented. When the profile screen data generation unit 153 generates profile screen data, it selects profile items that are displayed fixedly and items of all the pharmacist's profile data that have attributes in common with the patient. At this time, the profile screen data generation unit 153 may select screen elements other than the pharmacist's profile (background, color, font size, type of display frame, etc.) according to the patient's attributes.

The profile screen data transmission unit 154 transmits the data of the profile screen generated by the profile screen data generation unit 153 to the pharmacist terminal 30 that requested the generation of the profile screen.
When the prescription data receiving unit 151 receives prescription data, the change acquisition unit 155 reads out the previous prescription data for the patient indicated by the prescription data from the prescription DB 172. The change acquisition unit 155 then compares the prescription data received by the prescription data receiving unit 151 with the previous prescription data read out from the prescription DB 172, and acquires information (changed drug information) on drugs that have been changed between the previous prescription content and the current prescription content for the patient. Furthermore, the change acquisition unit 155 stores the acquired data on changed drug information in the changed drug information DB 176. Note that images (such as packaging and the appearance of the drug itself) such as photos (e.g., color photos) of drugs may be stored in the drug DB 174, and when the same drug is prescribed but the packaging of the drug has been changed between the previous prescription and the current prescription for the patient, the image such as the photo of the drug may be included in the changed drug information.

When a request for transmission of changed drug information for a specific patient is received from the pharmacist terminal 30, the changed data transmission unit 156 transmits the data of changed drug information stored in the changed drug information DB 17 to the pharmacist terminal 30.
The operation content receiving unit 157 receives the contents of operations on the display screen inputted on the pharmacist terminal 30 from the pharmacist terminal 30. The contents of operations on the display screen inputted on the pharmacist terminal 30 include, for example, designation of printing targets for items in the drug information, changing the arrangement of items in the drug information, designation of display of detailed explanations in the drug information, and instructions to print documents to be provided to patients that include drug information. These operation contents are transmitted collectively from the pharmacist terminal 30 to the server 20 each time an operation is performed on the display screen on the pharmacist terminal 30, or when an instruction to print documents to be provided to patients that include drug information is given.

When a print instruction for a document to be provided to a patient, including drug information, is transmitted from the pharmacist terminal 30 to the server 20, the print data generating unit 158 generates print data for the document to be provided, including the drug information to be provided to the patient and a predetermined related document describing various contents explained to the patient by the pharmacist. For example, the drug information describes drug information including changes in drug information, and the predetermined related document describes information regarding schedules, such as a drug taking schedule or a visit schedule, that the pharmacist explained to the patient on the pharmacist terminal 30.
The print data transmission unit 159 transmits the print data generated by the print data generation unit 158 to the pharmacy computer 10 .

[Functional configuration of the pharmacist terminal 30]
FIG. 5 is a block diagram showing the functional configuration of the pharmacist terminal 30. As shown in FIG.
As shown in FIG. 5, in the CPU 811 of the pharmacist terminal 30, an operation acceptance unit 251, a profile screen data receiving unit 252, a changes data receiving unit 253, a screen display unit 254, and an operation content transmission unit 255 function.
The operation reception unit 251 receives various operations input for the contents displayed on the display screen. For example, the operation reception unit 251 receives operations such as designating the printing target of items in the drug information, changing the arrangement of items in the drug information, designating the display of detailed explanations in the drug information, writing on the schedule presented to the patient, and issuing a print instruction for documents to be provided to the patient including the drug information.

The profile screen data receiving unit 252 receives data for the profile screen transmitted from the server 20 .
The change data receiving unit 253 receives data on changed drug information transmitted from the server 20 .
The screen display unit 254 displays various display screens on the display, such as an initial screen (such as a selection screen for various menus) on the pharmacist terminal 30, a profile screen based on the data of the profile screen, a display screen of changed drug information based on the data of changed drug information, or a screen of a schedule related to a patient. At this time, the screen display unit 254 displays various display screens on the display by appropriately requesting the server 20 to generate data for the profile screen, transmit changed drug information, etc.

The operation content sending unit 255 sends the contents of the operations on the display screen accepted by the operation accepting unit 251 to the server 20. As described above, these operation contents are sent to the server 20 all at once each time an operation is performed on the display screen on the pharmacist terminal 30, or when an instruction is given to print a document to be provided to the patient that includes drug information.

[motion]
Next, the operation of the information processing system 1 will be described.

[Processing of Pharmacy Computer 10]
FIG. 6 is a flowchart showing the flow of the drug information output process executed by the pharmacy computer 10.
The drug information output process is started in response to an instruction to execute the drug information output process being input via the input unit 815 of the pharmacy computer 10 .

When the drug information output process is started, in step S1, the prescription data acquisition unit 51 acquires data (prescription data) representing the contents of the prescription brought by the patient and accepted at the dispensing pharmacy. The acquired prescription data is stored in the prescription DB 71.
In step S2, the prescription data transmission unit 52 transmits the prescription data acquired by the prescription data acquisition unit 51 to the server 20.
In step S3, data on the patient attributes of the patient corresponding to the prescription data is obtained.
In step S4, the patient attribute transmission unit 54 transmits the data of the patient attributes acquired by the patient attribute acquisition unit 53 to the server 20. Thereafter, the pharmacy computer 10 goes into a standby state to wait for reception of the print data transmitted from the server 20.

In step S5, the print data receiving unit 55 receives print data for a document to be provided to a patient, including a drug information document (drug information), transmitted from the server 20.
In step S6, the print control unit 56 prints a document to be provided to the patient, including the medication information, from a printer installed in the dispensing pharmacy based on the print data received by the print data receiving unit 55.
After step S6, the drug information output process ends.

[Processing of Server 20]
FIG. 7 is a flowchart showing the flow of the data generation process executed by the server 20.
The data generation process is started when the server 20 is started, and is executed repeatedly.

When the data generation process is started, in step S11, the prescription data receiving unit 151 receives the prescription data transmitted from the pharmacy computer 10. The prescription data received at this time is stored in the prescription DB 172.
In step S12, the patient attribute receiving unit 152 receives the data of the patient attributes transmitted from the pharmacy computer 10. The received data of the patient attributes is stored in the patient attribute DB 173.

In step S13, in response to a request from the pharmacist terminal 30 to generate data for a profile screen to present the pharmacist's profile to the patient, the profile screen data generation unit 153 generates data for the pharmacist's profile screen.
In step S14, the profile screen data transmitting unit 154 transmits the data of the profile screen generated by the profile screen data generating unit 153 to the pharmacist terminal 30 that has requested the generation of the profile screen.

In step S15, in response to the prescription data being received by the prescription data receiving unit 151, the changes acquisition unit 155 acquires information (changes in drug information) about drugs that have changed between the previous prescription content and the current prescription content for the patient corresponding to the prescription data. The data on changes in drug information acquired at this time is stored in the changes in drug information DB 176.

In step S16, in response to a request from the pharmacist terminal 30 to transmit the changed drug information for a specific patient, the changed drug information transmission unit 156 transmits the data of the changed drug information stored in the changed drug information DB 17 to the pharmacist terminal 30. After this, the server 20 goes into a standby state to wait for the reception of the contents of the operation on the display screen transmitted from the pharmacist terminal 30.
In step S<b>17 , the operation content receiving unit 157 receives from the pharmacist terminal 30 the content of the operation on the display screen that has been input at the pharmacist terminal 30 .

In step S18, in response to a print instruction being sent from the pharmacist terminal 30 to the server 20 to print a document to be provided to the patient, including medication information, the print data generation unit 158 generates print data for the document to be provided, including the medication information to be provided to the patient and specified related documents describing various contents explained to the patient by the pharmacist.
In step S<b>19 , the print data transmission unit 159 transmits the print data generated by the print data generation unit 158 to the pharmacy computer 10 .
After step S19, the data generation process is repeated.

[Processing of pharmacist terminal 30]
FIG. 8 is a flowchart showing the flow of the communication support process executed by the pharmacist terminal 30.
The communication support process is started in response to an instruction to execute the communication support process being input via the input unit 815 of the pharmacist terminal 30 .

When the communication assistance process is started, in step S21, the screen display unit 254 requests the server 20 to generate data for a profile screen.
In step S 22 , the profile screen data receiving section 252 receives the data of the profile screen transmitted from the server 20 .
In step S23, the screen display unit 254 requests the server 20 to transmit data on the changed drug information.

In step S24, the changes data receiving unit 253 receives the changes in the drug information transmitted from the server 20.
In step S25, the screen display unit 254 sequentially displays various display screens including a pharmacist profile screen and a screen displaying changed drug information on the display.
In step S26, the operation acceptance unit 251 accepts various operations inputted in response to the content displayed on the display screen.

In step S27, the operation content transmitting unit 255 transmits the content of the operation on the display screen accepted by the operation accepting unit 251 to the server 20.
In step S28, the screen display unit 254 determines whether or not an instruction to end the communication support process has been given.
If the end of the communication support process has not been instructed, the result of the determination in step S28 is NO, and the process proceeds to step S25.
On the other hand, if an instruction to end the communication assistance process is given, a YES determination is made in step S28, and the communication assistance process ends.

[Display screen example]
Next, examples of display screens displayed in the communication support process will be described.
FIG. 9 is a schematic diagram showing an example of an initial screen displayed in the communication support process.
9, the screen display unit 254 first displays an initial screen showing the patient's name, date of birth, age, etc. In this embodiment, the background, color, type of display frame, etc. of the initial screen are selected by the server 20 according to the patient's attributes.

FIG. 10 is a schematic diagram showing an example of a pharmacist profile screen.
As shown in FIG. 10, following the initial screen, the screen display unit 254 displays a pharmacist's profile screen. The pharmacist's profile screen includes fixedly displayed profile items and items selected in the server 20 according to the patient attributes. For example, in the example shown in FIG. 10, the pharmacist's photo, name, age, marital status, details of local activities, and current focus area are displayed as fixedly displayed profile items. In addition, in the example shown in FIG. 10, "Hobby: Walking" is displayed as an item selected according to the patient attributes. That is, the patient attributes of the patient for whom the profile screen of FIG. 10 is presented include data of "Hobby: Walking", and in the pharmacist's profile data, the item "Hobby: Walking" that is common to the patient's attribute information is selected and displayed on the profile screen.

FIG. 11 is a schematic diagram showing an example of the questionnaire screen.
As shown in FIG. 11, the screen display unit 254 displays the contents of a questionnaire regarding the taking of medicines in response to the pharmacist's operation on the display screen, and the operation receiving unit 251 receives the selection operation of options for the items in the questionnaire.

FIG. 12 is a schematic diagram showing an example of a state in which a questionnaire has been answered.
In the example shown in Fig. 12, in response to the questionnaire "Do you like taking medicine?", the patient selects the option "I want to take it to feel safe." In addition, in the example shown in Fig. 12, in response to the questionnaire "Do you ever forget to take your medicine?", the patient selects the option "Sometimes." In this embodiment, the pharmacist's profile, with simplified content, is displayed on display screens other than the pharmacist's profile screen, such as the questionnaire display screen, as shown in Fig. 12.

FIG. 13 is a schematic diagram showing an example of a display screen showing the contents of the changed drug information.
As shown in Fig. 13, the screen display unit 254 displays the contents of the changed drug information in response to the pharmacist's operation on the display screen. In the example shown in Fig. 13, the name of the medical institution to which the prescribing doctor belongs, the medical department, the doctor's name, the prescription date, etc., and a list of the drugs prescribed last time are displayed as the contents of the previous prescription. Similarly, in the example shown in Fig. 13, the name of the medical institution to which the prescribing doctor belongs, the medical department, the doctor's name, the prescription date, etc., and a list of the drugs prescribed this time are displayed as the contents of the current prescription. The pharmacist can operate the display screen while presenting the display screen shown in Fig. 13 to the patient to explain the contents of the prescription change in an easy-to-understand manner to the patient.

FIG. 14 is a schematic diagram showing an example of a state in which a pharmacist has performed an operation to explain the prescription contents to a patient on the display screen shown in FIG.
As shown in FIG. 14, for "Tablet A" and "Tablet B", there is no change between the previous prescription and the current prescription, so when the pharmacist operates the items of "Tablet A" and "Tablet B", the absence of a change in the prescription is identified and represented by an arrow indicating that the prescription is the same. On the other hand, for "Tablet C", although it was included in the previous prescription, it is not included in the current prescription, so when the pharmacist operates the item of "Tablet C", a dashed x mark indicating that the prescription has been discontinued and a message saying "Bring it without taking x" are superimposed on the item of "Tablet C". Furthermore, for "Capsule D", although the prescription has been switched to "Capsule G", it is necessary to switch to "Capsule G" after drinking up the prescribed "Capsule D", so when the pharmacist operates the item of "Capsule D", a message saying "Drink it up" to instruct the user to drink up the remaining medicine in "Capsule D" is superimposed on the item of "Capsule D". In addition, the method of changing the prescription is identified and represented by an arrow indicating that the prescription has been changed from "Capsule D" to "Capsule G" and a message saying "Change after drinking up".

In addition, when the pharmacist operates the item of the drug prescribed in the current prescription, such as "A tablets" and "F capsules," a message such as "◎ Don't forget to take it" is displayed over these items. Furthermore, when the pharmacist operates an item in the current prescription, such as "G capsules," which has been changed from the previous prescription and has benefits for the patient, a message indicating the benefits for the patient (for example, "You can eat XX from today!", which improves the patient's quality of life) is displayed over this item. In addition, when there is a change in the packaging of the drug or the appearance of the drug itself, it is also possible to display a message such as "The packaging (appearance) has changed" to notify the patient of the change in the packaging of the drug or the appearance of the drug itself. In this case, an image such as a photo showing the packaging of the drug before the change or the appearance of the drug itself is displayed in the previous prescription, and an image such as a photo showing the packaging of the drug after the change or the appearance of the drug itself is displayed in the current prescription. Messages such as "Bring it without taking it,""Drink it all,""Don't forget to take it,""Starting today, you can eat XX!", and "The packaging (appearance) has changed" can be displayed automatically based on the results of comparing the data from the previous prescription with the data from the current prescription and the results of the pharmacist's operations.
In addition to the above examples, the display contents of these messages can also include information to be notified to the patient in response to changes in the prescription (such as warnings and advice from the pharmacist), which can encourage the patient to be more aware of the changes in the prescription.

Here, on the display screen showing the contents of the changed medication information, the arrangement of each listed item can be changed within the previous prescription contents and the current prescription contents for purposes such as ease of explanation.
FIG. 15 is a schematic diagram showing an example of a state in which the arrangement of items displayed in a list is changed.
As shown in Figure 15, if "Tablet C" in the previous prescription has been changed to "Capsule F" with the same efficacy in the current prescription, the position of "Tablet C" can be changed by moving it to a position next to "Capsule F." This makes it possible to display the prescription change in a way that is easier for patients to understand.

FIG. 16 is a schematic diagram showing an example of a schedule presented to a patient.
In FIG. 16, a two-week schedule for a patient is displayed. In the example of the schedule shown in FIG. 16, a band including the character "medicine" indicating the period during which the dispensed medicine is taken, the character "class reunion" indicating the date of the patient's class reunion, and a double-headed arrow with the character "trip" indicating the date of the patient's trip are input in the schedule column consisting of the date, day of the week, and weather forecast. In addition, the pharmacist can input handwritten input or stamp data for this schedule. For example, the pharmacist inputs stamp data of "be careful not to forget to take your medicine" into the date of the "class reunion", and the pharmacist inputs stamp data of "take your medicine" into the first day of the "trip". In addition, on the last day of the period during which the dispensed medicine is taken, stamp data of "next visit" is input to encourage the patient to visit the pharmacy next time. The stamp data of "next visit" can be automatically input on the last day of the period during which the dispensed medicine is taken, or can be input at the discretion of the pharmacist. Furthermore, in the example schedule shown in FIG. 16, the pharmacist's work schedule is shown at the bottom of the schedule column, allowing the patient to decide the date to visit the dispensing pharmacy based on the pharmacist's work schedule.
Using this scheduling function, pharmacists can set a drug-taking schedule that takes into full consideration the patient's daily life. For example, if a patient who has been prescribed a drug for headaches wants to be in good shape for their child's athletic meet, the pharmacist can provide guidance on the drug-taking schedule so that the patient's symptoms are alleviated on the day of the athletic meet.

FIG. 17 is a schematic diagram showing an example of an interface screen for inputting stamp data.
In the schedule display screen shown in Fig. 16, when a schedule column for any date is selected, by performing an operation to select (e.g., tap) the "stamp" icon located in the bottom column of the schedule display screen, an interface screen for inputting stamps is displayed as shown in Fig. 17. By performing an operation to select any stamp, the pharmacist can input data of the desired stamp for the desired date.

FIG. 18 is a schematic diagram showing an example of an interface screen for inputting handwritten characters.
In the schedule display screen shown in FIG. 16, when a schedule column for any date is selected, and an operation to select (e.g., tap) the "Handwritten" icon located in the bottom column of the schedule display screen is performed, an interface screen for inputting handwritten characters is displayed as shown in FIG. 18. The pharmacist can handwrite any character in the area for inputting handwritten characters, and the input character is recognized, allowing the pharmacist to input the desired character data for the desired date. In addition, in the interface screen for inputting handwritten characters, the color of the input character can be selected, and by selecting a color and then inputting handwritten characters, characters of the desired color can be input.

FIG. 19 is a schematic diagram showing an example of an interface screen for registering a new schedule.
When an operation to select (e.g., tap) the "Add Schedule" icon located in the bottom section of the schedule display screen shown in Fig. 16 is performed, an interface screen for registering a new schedule is displayed as shown in Fig. 19. By selecting a period, a schedule option, and a display color of the double-headed arrow, the pharmacist can display the double-headed arrow indicating the selected period in the selected color and input characters indicating the schedule selected from the schedule options.

FIG. 20 is a schematic diagram showing an example of an interface screen for editing an already input schedule.
When an operation to select an already inputted plan (such as a double tap) is performed on the schedule display screen shown in Fig. 16, an interface screen for editing the plan is displayed as shown in Fig. 19. The pharmacist can select to change the display color of the period, plan options, and double-arrow to the desired color, so that the double-arrow indicating the selected period is displayed in the selected color, and the pharmacist can input characters indicating the plan selected from the plan options.

FIG. 21 is a schematic diagram showing an example of a screen displaying a message to the effect that any consultation matter is accepted.
In the example screen shown in Fig. 21, messages such as "Is there anything you are concerned about?", "I know it's difficult to talk about, but please feel free to ask me any questions you may have", "Even if it's about your family", and "Even if it's something other than medicine" are displayed. By presenting such a screen, the pharmacist can create an atmosphere where the patient feels comfortable asking for advice.

[Examples of drug information documents]
Next, a specific example of the document provided to the patient will be described.
22 and 23 are schematic diagrams showing an example of a provision document (changes in medication information) provided to a patient.
In the display screens showing the contents of the modified medication information exemplified in the above-mentioned Figs. 13 to 15, the pharmacist can appropriately select the medication to be printed on the medication information based on the conversation with the patient, etc.
For example, Fig. 22 shows an example in which major drugs, including drugs whose prescriptions have been changed and drugs whose prescriptions have not been changed, are selected as the print targets. In Fig. 22, "Tablet A" and "Tablet B" whose prescriptions have not been changed, "Tablet C" whose prescription has been discontinued, "Capsule F" that has been newly prescribed, and "Capsule D" and "Capsule G" whose prescriptions have been changed are selected as the print targets.

On the other hand, Fig. 23 shows an example in which drugs whose prescriptions have been changed are selected as the printing targets. In Fig. 23, the newly prescribed "F Capsule," the "D Capsule" and "G Capsule" whose prescriptions have been changed, and the "C Tablet" whose prescription has been discontinued are selected as the printing targets.
As shown in Figs. 22 and 23, among the drugs for which prescriptions have been changed, those that require caution when taking are marked with a "Don't take it, bring it with you" mark, which encourages the patient to take the drug to the pharmacy without taking it because the prescription has run out, a "Take it all up" mark, which encourages the patient to take the last prescribed drug before taking the current prescribed drug, a "Don't forget to take it" mark, which warns the patient not to forget to take the drug because it has been newly added to the current prescription, and a "You can eat XX from today!" mark, which indicates that the patient's quality of life will improve with the change in prescription. In addition, if there is a change in the packaging of the drug or the appearance of the drug itself, it is also possible to add a mark such as "The packaging (appearance) has changed" to notify the patient of the change in the packaging of the drug or the appearance of the drug itself. In this case, an image such as a photo showing the packaging of the drug before the change or the appearance of the drug itself is printed on the previous prescription, and an image such as a photo showing the packaging of the drug after the change or the appearance of the drug itself is printed on the current prescription. These marks, such as "Bring it without taking it,""Drink it all,""Don't forget to take it,""You can eat XX from today!", and "The packaging (appearance) has changed," can be added automatically based on the results of comparing the data from the previous prescription with the data from the current prescription or the results of the pharmacist's operations.
In addition to the above examples, the display contents indicated by these marks can also include information to be notified to patients in response to changes in prescription contents (such as warnings and advice from pharmacists), which can encourage patients to be more aware of changes in prescription contents.

FIG. 24 is a schematic diagram showing an example of a provided document (related document) provided to a patient.
The related document shown in Figure 24 is a document given to patients to post in a conspicuous place, such as a wall or refrigerator in their home, to make casual notes about things that concern them, and to bring with them the next time they visit the clinic.
As shown in Fig. 24, among the documents provided to the patient, a predetermined related document describes information related to schedules such as a drug-taking schedule, a visit schedule, and the patient's plans, which the pharmacist explained to the patient on the display screen shown in Fig. 16. Also, for each day in the schedule, check boxes for taking medication in the morning, afternoon, evening, and before going to bed (before going to bed) are described.

In addition, in the predetermined related document, the time that is the guideline for the timing of taking the medicine in a day is shown on the time axis under the schedule column. That is, in the example shown in Fig. 24, 7:00 in the morning, 13:00 in the afternoon, and 19:00 in the evening are shown as the guideline for the timing of taking the medicine.
Further below the time axis showing the approximate timing of taking the medicine, there is a section for the patient to note anything that concerns them, and images such as photographs of medicines that require special care when taking them are printed.
Furthermore, a message from the pharmacist to the patient and contact information for the dispensing pharmacy are printed in the bottom section of the specified related document shown in FIG.

As described above, in the information processing system 1 of this embodiment, when a pharmacist interacts with a patient at a dispensing pharmacy, a specific profile of the pharmacist is displayed while information about the drug is displayed, thereby stimulating the patient's interest and affinity with the pharmacist and supporting a smoother conversation.
In addition, in the information processing system 1, when a pharmacist explains information about a medication (such as changes to a prescribed medication) to a patient, a medication information document (medication information) reflecting the contents of that explanation is issued, allowing the patient to more easily refer to the contents of the explanation provided by the pharmacist even when taking the medication.
Furthermore, the information processing system 1 can present the contents explained to the patient by the pharmacist, such as how to take the prescribed medication, in a form that is easy for the patient to understand (such as a schedule), thereby supporting the patient in taking the appropriate medication.
Therefore, the information processing system 1 according to this embodiment can more appropriately support communication between pharmacists and patients.

[Modification 1]
In the above-described embodiment, when the print data generating unit 158 generates print data for the provision document, an image explaining how to use the medicine included in the current prescription may be included in the medicine information.
For example, if it is an oral medication, a pictogram of the medication being taken by mouth; if it is a patch, a pictogram of the medication being applied to the body; if it is a suppository, a pictogram of the medication being inserted through the anus; and if it is an ointment, a pictogram of the medication being applied to the body can be printed on the medication information.
This can prevent patients from misusing the drug.

[Modification 2]
In the above-described embodiment, when the currently prescribed medication is displayed on the display screen of the pharmacist terminal 30 or printed on the medication information, the order in which the prescribed medication is displayed or printed may be automatically set according to specified conditions.
For example, the doctor who prescribed the drug may display the main drug on the top row, and drugs with lower relative importance such as supplementary drugs may be displayed on the bottom row. As an example, a drug prescribed to suppress headaches may be displayed on the top row, and drugs to suppress side effects caused by taking the drug (such as drugs to protect the gastric mucosa to suppress side effects such as stomach irritation) may be displayed on the bottom row.
In addition, for example, if a medicine is taken at different times such as in the morning, afternoon, or evening, it is possible to display the medicine in the order of the taking timing from top to bottom.

[Modification 3]
In the above embodiment, the provided document is provided to a patient, but the present invention is not limited to this. In other words, the provided document may be provided to various entities that may refer to the patient's prescription, such as the patient's family, caregivers (care workers, etc.), nurses, etc., in addition to the patient. In this case, the content of the information shown in the provided document (e.g., difficulty level, granularity, etc.) may be changed depending on the knowledge of the provider who receives the provided document.
In addition, among the documents provided, the drug information document (drug information) and the specified related documents can be intended for different recipients. For example, the contents of the document provided can be generated assuming that the drug information document (drug information) will be provided to a caregiver of a patient and the specified related documents will be provided to the patient. This makes it possible to generate documents provided (drug information or related documents) with content suited to the purpose depending on the recipient of the document provided.

In the above-mentioned embodiment and modified example, the document provided to the patient is in the form of a prescribed document, such as a changed medication information or related documents, but the present invention is not limited to this. For example, the document provided may be provided to the patient in the form of a medicine envelope. That is, in this embodiment, the print data generated by the print data generating unit 158 can be provided to the patient by printing information such as a medicine envelope or medication information on various media on which information can be printed. The materials of the various media on which information can be printed can be any type, such as paper, vinyl, or electronic paper. It is also possible to print the print data divided onto multiple media. For example, a single medium can be formed by a medication information providing document on which the current prescription data is printed, and a sticker (such as a sticker on which the past prescription data and the contents of the prescription change are printed) that is attached to the providing document to present the patient with the changes in the prescription data as a whole.
Furthermore, the documents provided to the patient may be provided to the patient by printing them on various media capable of printing information, or may be provided to the patient by outputting the information in the form of electronic data that can be viewed on an electronic medication notebook, an app on a smartphone or the like (an app such as a notebook or schedule book), or other electronic device (for example, provided via communication or storage media).

In the above-mentioned embodiment and modified example, the provided document provided to the patient shows the result of comparing one past prescription data with the current prescription data, such as the previous prescription data with the current prescription data, but the present invention is not limited to this. For example, the provided document may show the result of comparing the past prescription data with the current prescription data. As an example, if the previous and previous-previous prescription data are the same as the current prescription data, but there is a change in the prescription data three prescriptions ago, the provided document shows the result of comparing the prescription data three prescriptions ago, the previous (or previous-previous) prescription data, and the current prescription data. This makes it possible to extract past prescription data that is useful to present to the patient, not limited to the previous prescription data, and show the result of comparing the data with the current prescription data.
It is also possible that the prescription data to be compared does not include the current prescription data; for example, it is possible to show the results of comparing the previous prescription data with the prescription data before that.

In the above-mentioned embodiment and modified example, when the display screen showing the contents of the changed drug information shown in FIG. 13 is displayed, in the initial state, drugs with the same ingredients (or efficacy) can be automatically associated and arranged in the past prescription data and the current prescription data. In this case, for example, drugs that have not been changed or drugs before and after the change that have the same ingredients (or efficacy) are displayed in association with each other. When the pharmacist moves the display position of any drug on the display screen showing the contents of the changed drug information displayed in this way, the display content that is set in advance can be automatically displayed corresponding to the position resulting from the movement. For example, when any drug in the past prescription data is moved to a display position that does not correspond to the current prescription data, a message indicating that the prescription of the drug has been discontinued (such as "the drug has run out") can be displayed. Similarly, when any drug in the current prescription data is moved to a display position that does not correspond to the past prescription data, a message indicating that the prescription of the drug has been added (such as "a drug has been added") can be displayed. This makes it possible to more clearly show the patient the contents of the changes to the prescribed drug.

As described above, the information processing system 1 according to this embodiment includes the pharmacy computer 10, the server 20, and the pharmacist terminal 30.
The pharmacy computer 10 includes a prescription data acquisition unit 51 and a prescription data transmission unit 52 .
The prescription data acquisition unit 51 acquires the patient's prescription data.
The prescription data transmission unit 52 transmits the prescription data acquired by the prescription data acquisition unit 51 to the server 20.
The server 20 includes a changes acquisition section 155 and a changes data transmission section 156 .
The change acquisition unit 155 acquires change information regarding drugs that have been changed between the patient's past prescription contents and the current prescription contents based on the prescription data transmitted from the pharmacy computer 10 and the patient's past prescription data corresponding to the prescription data.
The changed data transmission unit 156 transmits data on the changed drug information to the pharmacist terminal 30.
The pharmacist terminal 30 includes a screen display unit 254 and an operation reception unit 251 .
The screen display unit 254 displays a screen for presenting information on drugs related to the prescription including the changed drug information to the patient based on the data on the changed drug information transmitted from the server 20 .
The operation reception unit 251 receives operations input to the screen displayed by the screen display unit 254 .
The screen display unit 254 changes the display content of the drug information in response to an operation input to the screen.
With this configuration, in the information processing system 1, when a pharmacist is interacting with a patient at a pharmacy, information about the drug related to the prescription, including changes to the drug information, can be displayed, and the displayed content of the drug information can be changed depending on the operations entered on the screen.
Therefore, communication between pharmacists and patients can be more appropriately supported.

The pharmacist terminal 30 is equipped with an operation content transmission unit 255 .
The operation content transmitting unit 255 transmits the content of the operation accepted by the operation accepting unit 251 to the server 20 .
This allows the server 20 to grasp the content of operations on the screen that have been input at the pharmacist terminal 30 .

The server 20 includes a print data generating unit 158 and a print data transmitting unit 159 .
The print data generation unit 158 generates data for outputting a document to be provided to the patient, including changed medication information, based on the content of the operation transmitted by the operation content transmission unit 255 (print data or data for output to a storage medium, etc.).
The print data transmission unit 159 transmits the output data generated by the print data generation unit 158 to the pharmacy computer 10 .
The pharmacy computer 10 includes a print control unit 56 .
The print control unit 56 outputs the provided document as a medium to be handed over to the patient based on the output data transmitted from the server 20 .
This allows the pharmacy computer 10 to output (print or store, etc.) a document to be provided in accordance with the operation content input at the pharmacist terminal 30 .

The server 20 includes a profile screen data generating unit 153 and a profile screen data transmitting unit 154 .
The profile screen data generating unit 153 generates data of a pharmacist's profile screen to be presented to a patient, based on the pharmacist's profile data and the attributes of the patient.
The profile screen data transmission unit 154 transmits data of the profile screen to the pharmacist terminal 30 .
The screen display unit 254 of the pharmacist terminal 30 displays the pharmacist's profile screen based on the profile screen data transmitted from the server 20.
This allows a profile screen of the pharmacist to be displayed that matches the patient's attributes, which stimulates the patient's interest and sense of closeness to the pharmacist and supports smoother dialogue between the pharmacist and the patient.

The profile screen data generating unit 153 selects data common to the attributes of the patient from the data of the pharmacist's profile, and generates data for the pharmacist's profile screen.
This can arouse patients' interest and sense of closeness to pharmacists more strongly.

The screen display unit 254 displays a screen of a schedule relating to the patient, including a schedule for taking the medicines included in the patient's prescription.
The operation reception unit 251 receives operations input to the schedule screen.
The operation content transmitting unit 255 transmits the content of the operation on the schedule screen accepted by the operation accepting unit 251 to the server 20 .
This enables the server 20 to generate data for the patient's schedule and generate print data by reflecting the input contents in the patient's schedule.

The present invention is not limited to the above-described embodiment, and modifications and improvements within the scope of the present invention that can achieve the object of the present invention are included in the present invention.
For example, in the above-described embodiment, the pharmacy computer 10 may not include the prescription DB 71 or the patient attribute DB 72, and the server 20 may collectively manage the data. In this case, the pharmacy computer 10 can execute the same processing as in the above-described embodiment by sequentially transmitting and receiving data to and from the server 20 and using the data stored in the prescription DB 172 or the patient attribute DB 173 of the server 20.
In addition, the information processing system 1 according to the present invention can be configured using each device in the above-described embodiments, or the functions of multiple devices in the above-described embodiments can be implemented together in one device, or the functions of one device can be distributed and implemented across multiple devices.

The above-described series of processes can be executed by hardware or software.
In other words, the functional configurations in the above-described embodiments are merely examples and are not particularly limited. That is, it is sufficient that any of the computers constituting the information processing system 1 has a function capable of executing the above-described series of processes as a whole, and the type of functional block used to realize this function is not particularly limited to the examples shown.
Furthermore, one functional block may be configured as a single piece of hardware, a single piece of software, or a combination of both.

The recording medium containing the program for executing the above-mentioned series of processes may be configured not only as a removable medium distributed separately from the device body in order to provide the program to the user, but also as a recording medium etc. provided to the user in a state where it is already installed in the device body.

Although the embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment. Furthermore, the effects described in this embodiment are merely a list of the most favorable effects resulting from the present invention, and the effects of the present invention are not limited to those described in this embodiment.

1 Information processing system, 10 Pharmacy computer, 20 Server, 30 Pharmacist terminal, 40 Network, 51 Prescription data acquisition unit, 52 Prescription data transmission unit, 53 Patient attribute acquisition unit, 54 Patient attribute transmission unit, 55 Print data reception unit, 56 Print control unit, 71 Prescription database, 72 Patient attribute database, 151 Prescription data reception unit, 152 Patient attribute reception unit, 153 Profile screen data generation unit, 154 Profile screen data transmission unit, 155 Change acquisition unit, 156 Change data transmission unit, 157 Operation content reception unit, 158 Print data generation unit, 159 Print data transmission unit, 171 Pharmacist profile database, 172 Prescription database, 173 Patient attribute database, 174 Drug database, 175 Pharmacy-specific drug use database, 176 Change drug information database, 177 Schedule database, 251 Operation reception unit, 252 Profile screen data receiving unit, 253 Change data receiving unit, 254 Screen display unit, 255 Operation content transmitting unit, 800 Information processing device, 811 CPU, 812 ROM, 813 RAM, 814 Bus, 815 Input unit, 816 Output unit, 817 Storage unit, 818 Communication unit, 819 Drive, 820 Imaging unit, 831 Removable media

Claims (8)

An information processing system including an information processing device that manages data related to patients used in a pharmacy, and a terminal device that displays information transmitted from the information processing device,
The information processing device includes:
A profile data acquisition means for acquiring profile data of a pharmacist who communicates with the patient;
a profile screen data generating means for generating data of the pharmacist's profile screen to be presented to the patient based on the data of the pharmacist's profile;
a profile screen data transmission means for transmitting data of the profile screen to the terminal device;
A prescription data acquisition means for acquiring data of the patient's prescription;
A change acquisition means for acquiring change information regarding a drug that has been changed between a past prescription content and a current prescription content for the patient based on the prescription data and past prescription data for the patient that corresponds to the prescription data;
A change data transmission means for transmitting the change drug information data to the terminal device;
Equipped with
The terminal device
a screen display means for displaying a profile screen of the pharmacist who communicates with the patient based on data of the pharmacist's profile screen transmitted from the information processing device, and switching from the pharmacist's profile screen to display a screen for presenting information on drugs related to the prescription, including the changed drug information, to the patient based on the data of the changed drug information;
An information processing system comprising: The information processing device includes:
an operation content receiving means for receiving an operation content for changing the information to be displayed on the screen display means,
2. The information processing system according to claim 1, wherein the screen display means changes the drug information displayed on the screen in accordance with the operation content. The information processing device includes:
an output data generating means for generating output data of a document to be provided to the patient, the document including the changed drug information, based on the operation content received by the operation content receiving means;
3. The information processing system according to claim 2, further comprising output data transmitting means for transmitting the output data generated by the output data generating means to the terminal device or to a terminal device other than the terminal device. The information processing device includes:
a prescription database for storing data of prescriptions of said patients;
4. The information processing system according to claim 1, wherein the prescription database accumulates and stores data on the current prescription of the patient acquired by the prescription data acquisition means. The information processing system according to any one of claims 1 to 4, characterized in that the profile screen data generating means generates the data of the profile screen of the pharmacist by selecting data from the data of the pharmacist's profile that is common to the attributes of the patient. An information processing device constituting an information processing system including an information processing device that manages data related to patients used in a pharmacy and a terminal device that displays information transmitted from the information processing device,
A profile data acquisition means for acquiring profile data of a pharmacist who communicates with the patient;
a profile screen data generating means for generating data of the pharmacist's profile screen to be presented to the patient based on the data of the pharmacist's profile;
a profile screen data transmission means for transmitting data of the profile screen to the terminal device;
A prescription data acquisition means for acquiring data of the patient's prescription;
A change acquisition means for acquiring change information regarding a drug that has been changed between a past prescription content and a current prescription content for the patient based on the prescription data and past prescription data for the patient that corresponds to the prescription data;
A change data transmission means for transmitting the change drug information data to the terminal device;
Equipped with
An information processing device characterized in that the terminal device displays a profile screen of the pharmacist who communicates with the patient based on the data of the pharmacist's profile screen , and switches from the pharmacist's profile screen to display a screen for presenting to the patient information about drugs related to the prescription, including the changed drug information, based on the data of the changed drug information. An information processing method executed by an information processing system including an information processing device that manages data related to patients used in a pharmacy, and a terminal device that displays information transmitted from the information processing device,
The information processing device,
A profile data acquisition step of acquiring profile data of a pharmacist who communicates with the patient;
a profile screen data generating step of generating data of the pharmacist's profile screen to be presented to the patient based on the data of the pharmacist's profile;
a profile screen data transmission step of transmitting data of the profile screen to the terminal device;
A prescription data acquisition step of acquiring data of the patient's prescription;
a change acquisition step of acquiring change information regarding a drug that has been changed between the past prescription content and the current prescription content for the patient based on the prescription data and the past prescription data of the patient corresponding to the prescription data;
a change data transmission step of transmitting the change drug information data to the terminal device;
Including,
The terminal device,
a screen display step of displaying a profile screen of the pharmacist who communicates with the patient based on the data of the profile screen of the pharmacist transmitted from the information processing device, and switching from the profile screen of the pharmacist to display a screen for presenting information on drugs related to the prescription, including the changed drug information, to the patient based on the data of the changed drug information;
13. An information processing method comprising: A computer constituting an information processing device in an information processing system including an information processing device for managing data related to patients used in a pharmacy and a terminal device for displaying information transmitted from the information processing device,
A profile data acquisition function for acquiring profile data of a pharmacist who communicates with the patient;
a profile screen data generation function for generating data of the pharmacist's profile screen to be presented to the patient based on the data of the pharmacist's profile;
a profile screen data transmission function for transmitting data of the profile screen to the terminal device;
A prescription data acquisition function for acquiring data of the patient's prescription;
A change acquisition function for acquiring change information regarding a drug that has been changed between the past prescription content and the current prescription content for the patient based on the prescription data and the past prescription data of the patient corresponding to the prescription data;
A change data transmission function for transmitting the change drug information data to the terminal device;
Realize this,
A program characterized by causing the terminal device to display a profile screen of the pharmacist who communicates with the patient based on data from the pharmacist's profile screen , and switching from the pharmacist's profile screen to display a screen for presenting to the patient information about drugs related to the prescription, including the changed drug information, based on the data of the changed drug information.

Images