Information processing system, information processing device, information processing method, and program

Abstract

To more appropriately support communication between pharmacists and patients.SOLUTION: In an information processing system 1, a prescription data acquisition unit 51 of a pharmacy computer 10 acquires prescription data of a patient. A prescription data transmitting unit 52 transmits the prescription data to a server 20. A change point acquisition unit 155 of the server 20 acquires change point drug information about drugs that have been changed between past prescription contents and current prescription contents based on the prescription data and past prescription data of the patient. A change point data transmitting unit 156 transmits change point drug information data to a pharmacist terminal 30. A screen display unit 254 of the pharmacist terminal 30 displays a screen for presenting, to the patient, drug information related to the prescription including the change point drug information based on the change point drug information data. An operation reception unit 251 accepts an operation inputted into the screen. The screen display unit 254 changes display contents of the drug information according to the operation.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing device, an information processing method, and a program. [Background technology]

[0002] Conventionally, when medication is dispensed at a dispensing pharmacy, the patient submits a prescription, and the pharmacist prepares the medication based on the prescription after interviewing the patient, etc. The pharmacist then explains the medication to the patient, etc., before issuing the medication to the patient. As a technique for supporting communication between pharmacists and patients in such dispensing actions, 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 patient 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 patient regardless of the pharmacist's ability. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-122253 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional technologies, including the technology described in Patent Document 1, patients find it difficult to feel close to pharmacists, which can be an obstacle to pharmacists' communication with patients. Furthermore, patients may not fully understand the information about medications (such as changes in prescribed medications) that the pharmacist explains to them, and may not be able to fully utilize the pharmacist's explanations when taking their medications. Furthermore, when multiple medications are prescribed or when the pharmacist provides special instructions to the patient (such as instructions on a medication schedule that takes daily life into consideration), the method of taking the medications can become complicated, and the patient may not be able to take their medications properly. As described above, with conventional techniques, it has been difficult to appropriately support communication between pharmacists and patients.

[0005] An object of the present invention is to more appropriately support communication between pharmacists and patients. [Means for solving the problem]

[0006] In order to solve the above problem, 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 that manages data used in the pharmacy, The pharmacy computer includes: a prescription data acquisition means for acquiring patient prescription data; 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 patient's past prescription content and the current prescription content based on the prescription data transmitted from the pharmacy computer and the patient's past prescription data 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 about drugs related to the prescription, including the changed drug information, to the patient based on the data about the changed drug information 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 is characterized in that it changes the displayed content of the drug information in response to an operation input to the screen. [Effects of the Invention]

[0007] According to the present invention, communication between pharmacists and patients can be more appropriately supported. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram showing a system configuration of an information processing system 1 according to an embodiment of the present invention. [Figure 2] FIG. 8 is a diagram showing the hardware configuration of an information processing device 800 that constitutes each device. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of the pharmacy computer 10. [Figure 4] FIG. 2 is a block diagram showing the functional configuration of the server 20. [Figure 5] FIG. 2 is a block diagram showing the functional configuration of a pharmacist terminal 30. [Figure 6] 10 is a flowchart showing the flow of a drug information output process executed by the pharmacy computer 10. [Figure 7] 10 is a flowchart showing the flow of a data generation process executed by the server 20. [Figure 8] 10 is a flowchart showing the flow of a communication support process executed by the pharmacist terminal 30. [Figure 9] FIG. 10 is a schematic diagram illustrating an example of an initial screen displayed in the communication support process. [Figure 10] FIG. 10 is a schematic diagram showing an example of a pharmacist profile screen. [Figure 11] FIG. 10 is a schematic diagram illustrating an example of a questionnaire screen. [Figure 12] FIG. 10 is a schematic diagram illustrating an example of a state in which a response to a questionnaire has been made. [Figure 13] FIG. 10 is a schematic diagram showing an example of a display screen showing the contents of changed drug information. [Figure 14] 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. 13. [Figure 15] FIG. 10 is a schematic diagram showing an example of a state in which the arrangement of items displayed in a list is changed. [Figure 16] FIG. 10 is a schematic diagram showing an example of a schedule presented to a patient. [Figure 17] FIG. 10 is a schematic diagram showing an example of an interface screen for inputting stamp data. [Figure 18] FIG. 10 is a schematic diagram illustrating an example of an interface screen for inputting handwritten characters. [Figure 19] FIG. 10 is a schematic diagram illustrating an example of an interface screen for registering a new schedule. [Figure 20] FIG. 10 is a schematic diagram illustrating an example of an interface screen for editing an already input schedule. [Figure 21] FIG. 10 is a schematic diagram showing an example of a screen displaying a message indicating that any consultation matter is accepted. [Figure 22] FIG. 1 is a schematic diagram showing an example of a document (medication information on changes) provided to a patient. [Figure 23] FIG. 1 is a schematic diagram showing an example of a document (medication information on changes) provided to a patient. [Figure 24] FIG. 2 is a schematic diagram showing an example of a document (related document) provided to a patient. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] The information processing system 1 according to this embodiment displays information about drugs while displaying a specific profile of the pharmacist when a pharmacist and a patient converse at a dispensing pharmacy, thereby stimulating the patient's interest and sense of familiarity with the pharmacist and supporting a smoother dialogue. Furthermore, when the pharmacist explains information about drugs (such as changes in the prescription between the previous and current prescriptions) to the patient based on the information (prescription content) written on the prescription issued to the patient, the information processing system 1 according to this embodiment issues a drug information document (hereinafter referred to as "drug information") that reflects the information, thereby enabling the patient to more easily refer to the explanation given by the pharmacist to the patient even when taking the drug. Furthermore, the information processing system 1 according to this embodiment presents the information explained by the pharmacist to the patient, such as how to take the prescribed drug, in a format that is easy for the patient to understand, thereby supporting the patient in taking the appropriate drug. A specific configuration will be described below.

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

[0012] The pharmacy computer 10 is configured as a PC (Personal Computer) or a server computer and has a medication history management function and a medical fee statement (receipt) creation function. The pharmacy computer 10 accepts input of patient prescription data and accumulates and manages the accepted prescription data. The pharmacy computer 10 also calculates a medical fee statement for dispensing medication to a patient based on the prescription. The pharmacy computer also receives print data for a patient provision document (described below) including a drug information provision document (drug information) and predetermined related documents from the server 20, and prints the provision document using a printer installed in the dispensing pharmacy. In this embodiment, the drug information provision document (drug information) is configured as a document or a document-like entity (for example, a sticker that can be attached to a notebook) that indicates information such as the name, usage, dosage, efficacy, effects, side effects, and interactions of the medication.

[0013] Server 20 is configured as a server computer, acquires prescription data received by pharmacy computer 10, and generates data for a pharmacist profile screen to be presented to the patient. Server 20 also accumulates and manages prescription data received by pharmacy computer 10, and generates data on changes to the medication prescribed to the patient (changes between the past (previous) prescription content and the current prescription content). This data on changes is sent to pharmacist terminal 30 and displayed on the screen, or sent to pharmacy computer 10 and included in the medication information and printed. Furthermore, server 20 manages schedule data, such as a medication intake schedule (medication schedule) or a pharmacy visit schedule, for each patient.

[0014] 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 medication changes 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 pharmacy visit schedule, and transmits the input schedule data to the server 20.

[0015] [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 thereof are the same.

[0016] FIG. 2 is a diagram showing the hardware configuration of an information processing device 800 that constitutes each device. As shown in Figure 2, the information processing device 800 that constitutes 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 memory unit 817, a communication unit 818, a drive 819, and an imaging unit 820.

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

[0018] The CPU 811, ROM 812, and RAM 813 are connected to one another via a bus 814. To the 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 are connected.

[0019] 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. 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 to overlap each other to configure a touch panel. The storage unit 817 is configured with a hard disk or a DRAM (Dynamic Random Access Memory), etc., and stores various data managed by each server. The communication unit 818 controls communication with other devices via the network.

[0020] Removable media 831, such as a magnetic disk, optical disk, magneto-optical disk, or 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 needed. The imaging unit 820 is configured by an imaging device equipped with 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 place it over the display of the output unit 816, thereby providing a touch panel.

[0021] [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 reception 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.

[0022] 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 contact information for the medical institution, and information indicating the prescription contents, such as the name, dosage form, directions for use and dosage, and whether or not substitution to a generic drug is possible, of the prescribed drug. The patient attribute DB 72 stores data on the patient's address, name, age, sex, and information (patient attributes) that represents the patient's individual characteristics. These 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, job details, family structure, favorite food, favorite color, favorite character, and concerns in daily life (bodily pain, etc., directly related to medical care, or concerns about a child's education, etc., not directly related to medical care).

[0023] The prescription data acquisition unit 51 acquires data (prescription data) representing the contents of a prescription brought by a patient and accepted at a dispensing pharmacy. In this embodiment, the prescription data acquisition unit 51 acquires prescription data that is 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.

[0024] Furthermore, 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.

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

[0026] 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 a document to be provided to a patient, including a drug information document (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.

[0027] [Functional configuration of Server 20] FIG. 4 is a block diagram showing the functional configuration of the server 20. As shown in FIG. 4, the CPU 811 of the server 20 functions as 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 changes obtaining unit 155, a changes data transmitting unit 156, an operation content receiving unit 157, a print data generating unit 158, and a print data transmitting unit 159. The storage unit 817 of the server 20 also has formed therein 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 changes drug information database (changes drug information DB) 176, and a schedule database (schedule DB) 177.

[0028] The 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 so, reasons for becoming a pharmacist, things that made them happy as 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 needed, depending on the pharmacist's wishes, etc.

[0029] The prescription DB 172 stores data of each prescription DB 71 stored in the pharmacy computer 10 of each dispensing pharmacy. That is, the prescription DB 172 stores an aggregate of data of the prescription DB 71 of each dispensing pharmacy for a predetermined area where the server 20 is operated. The patient attribute DB 173 stores data of each 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 where the server 20 is operated, etc.

[0030] Data representing information about various drugs is stored in the drug DB 174. For example, the drug DB 174 stores data about various drugs, such as information written on package inserts and information about drug prices. 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, for example, when the drugs used at each dispensing pharmacy are changed.

[0031] The changed drug information DB 176 stores information about drugs that have 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 about 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 medication schedules and pharmacy visit schedules) that the pharmacist has entered through conversations with the patient using the pharmacist terminal 30.

[0032] 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.

[0033] 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, from the pharmacist profile DB 171 and the patient attribute DB 173, the profile data of the pharmacist for whom the profile screen is to be generated and the patient attributes of the patient to whom the profile screen is to be presented. 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 whom the profile screen is to be generated and the patient attributes of the patient to whom the profile screen is to be presented. When generating profile screen data, the profile screen data generation unit 153 selects profile items to be displayed statically and items of all the pharmacist's profile data that share attributes with the patient. At this time, the profile screen data generation unit 153 may select screen elements other than the pharmacist's profile (e.g., background, color, font size, type of display frame) according to the patient's attributes.

[0034] 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 has requested the generation of the profile screen. When prescription data is received by the prescription data receiving unit 151, the changes acquiring unit 155 reads out data on the previous prescription for the patient indicated by the prescription data from the prescription DB 172. Then, the changes acquiring unit 155 compares the prescription data received by the prescription data receiving unit 151 with the data on the previous prescription read out from the prescription DB 172, and acquires information on drugs that have changed between the previous prescription content and the current prescription content for the patient (changes in drug information). Furthermore, the changes acquiring unit 155 stores the acquired data on changes in drug information in the changes in drug information DB 176. Note that images (such as photographs (e.g., color photographs) of drugs) may be stored in the drug DB 174, and if the same drug has been prescribed but the drug packaging or the like has 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 changes in drug information.

[0035] When a request is made from the pharmacist terminal 30 to send changed drug information for a specific patient, the changed drug information sending unit 156 sends the changed drug information data stored in the changed drug information DB 17 to the pharmacist terminal 30. The operation content receiving unit 157 receives from the pharmacist terminal 30 the content of an operation on the display screen that has been input at the pharmacist terminal 30. The content of an operation on the display screen that has been input at the pharmacist terminal 30 includes, for example, specifying which items in the drug information to print, changing the arrangement of items in the drug information, specifying the display of detailed explanations in the drug information, and issuing an instruction to print a document to be provided to the patient that includes the drug information. These operation contents are sent from the pharmacist terminal 30 to the server 20 all at once each time an operation is performed on the display screen at the pharmacist terminal 30, or when an instruction to print a document to be provided to the patient that includes the drug information is issued.

[0036] When a print instruction for a document to be provided to a patient, including medication information, is sent from pharmacist terminal 30 to server 20, 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 a predetermined related document describing various details explained to the patient by the pharmacist. For example, the medication information describes medication information including changes in medication information, and the predetermined related document describes information related to schedules, such as a medication schedule or a visit schedule, that the pharmacist explained to the patient on 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 .

[0037] [Functional configuration of 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 reception unit 251, a profile screen data reception unit 252, a change data reception unit 253, a screen display unit 254, and an operation content transmission unit 255 function. The operation accepting unit 251 accepts various operations input for the content displayed on the display screen. For example, the operation accepting unit 251 accepts operations such as specifying the items in the medication information to be printed, changing the arrangement of items in the medication information, specifying the display of detailed explanations in the medication information, writing to the schedule to be presented to the patient, and issuing an instruction to print documents to be provided to the patient including the medication information.

[0038] 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 the change 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.

[0039] The operation content sending unit 255 sends the contents of the operation 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 a patient that includes medication information.

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

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

[0042] 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 patient attribute data acquired by the patient attribute acquisition unit 53 to the server 20. Thereafter, the pharmacy computer 10 enters a standby state in which it waits for the reception of print data transmitted from the server 20.

[0043] In step S5, the print data receiving unit 55 receives print data of a document to be provided to a patient, including a drug information provision document (drug information), transmitted from the server 20. In step S6, 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. After step S6, the drug information output process ends.

[0044] [Server 20 processing] 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.

[0045] When the data generation process is started, in step S11, the prescription data receiving unit 151 receives 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 patient attribute data transmitted from the pharmacy computer 10. The patient attribute data received at this time is stored in the patient attribute DB 173.

[0046] In step S13, the profile screen data generation unit 153 generates data for the pharmacist's profile screen 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. In step S14, 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 has requested the generation of the profile screen.

[0047] In step S15, 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 in response to the prescription data being received by the prescription data receiving unit 151. The data of changes in drug information acquired at this time is stored in the changes in drug information DB 176.

[0048] 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 enters a standby state, waiting to receive the content of the operation on the display screen transmitted from the pharmacist terminal 30. In step S17, the operation content receiving section 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.

[0049] In step S18, in response to a print instruction for a document to be provided to a patient, including medication information, being sent from the pharmacist terminal 30 to the server 20, 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 that describe various contents explained to the patient by the pharmacist. In step S19, print data transmission unit 159 transmits the print data generated by print data generation unit 158 ​​to pharmacy computer 10. After step S19, the data generation process is repeated.

[0050] [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.

[0051] When the communication support process is started, in step S21, the screen display unit 254 requests the server 20 to generate data for a profile screen. In step S22, the profile screen data receiving unit 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.

[0052] In step S24, the change data receiving unit 253 receives the data of the change 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 change in medication information display screen on the display. In step S26, the operation accepting unit 251 accepts various operations input for the content displayed on the display screen.

[0053] 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 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, the result of the determination in step S28 is YES, and the communication assistance process ends.

[0054] [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.

[0055] 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 profile screen. The pharmacist profile screen includes statically displayed profile items and items selected by the server 20 according to patient attributes. For example, in the example shown in FIG. 10 , statically displayed profile items include the pharmacist's photo, name, age, marital status, details of community activities, and current areas of focus. In addition, in the example shown in FIG. 10 , "Hobby: Walking" is displayed as an item selected according to patient attributes. That is, the patient attributes of the patient for whom the profile screen of FIG. 10 is presented include data on "Hobby: Walking," and the item "Hobby: Walking" that is common to the patient's attribute information is selected in the pharmacist's profile data and displayed on the profile screen.

[0056] 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 medication intake in response to an operation on the display screen by the pharmacist, and the operation receiving unit 251 receives an operation to select an option for each item in the questionnaire.

[0057] FIG. 12 is a schematic diagram showing an example of a state in which responses to a questionnaire have been made. 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 and 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 also displayed on display screens other than the pharmacist's profile screen, such as the questionnaire display screen, as shown in Fig. 12.

[0058] FIG. 13 is a schematic diagram showing an example of a display screen showing the contents of the changed medicine information. As shown in Fig. 13, the screen display unit 254 displays the contents of the changed medication information in response to the pharmacist's operation on the display screen. In the example shown in Fig. 13, the previous prescription contents, such as 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 medications previously prescribed, are displayed. Similarly, in the example shown in Fig. 13, the current prescription contents, such as 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 medications currently prescribed, are displayed. 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.

[0059] 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 Figure 14, there are no changes between the previous and current prescriptions for "Tablet A" and "Tablet B." Therefore, when the pharmacist operates the "Tablet A" and "Tablet B" items, an arrow indicating that the prescription is the same is displayed, clearly indicating that the prescription has not changed. On the other hand, while "Tablet C" was included in the previous prescription, it is not included in the current prescription. Therefore, when the pharmacist operates the "Tablet C" item, a dashed X indicating that the prescription has been discontinued and a message saying "Bring it without taking X" are displayed overlaid on the "Tablet C" item. Furthermore, although the prescription for "Capsule D" has been switched to "Capsule G," the patient must consume the prescribed "Capsule D" before switching to "Capsule G." Therefore, when the pharmacist operates the "Capsule D" item, a message saying "Take it all" is displayed overlaid on the "Capsule D" item, instructing the patient to consume the remaining "Capsule D" medication. Furthermore, the method of changing the prescription is identified and displayed by an arrow indicating that the prescription has been changed from "Capsule D" to "Capsule G" and a message saying "Change after completing the prescription."

[0060] Furthermore, when the pharmacist operates a drug item in the current prescription, such as "Tablet A" or "Capsule F," a message such as "◎Don't forget to take it" is superimposed on the item. Furthermore, when the pharmacist operates an item in the current prescription, such as "Capsule G," that has been changed from the previous prescription and therefore has benefits for the patient, a message indicating the benefits to the patient (e.g., "You can eat XX from today!", which improves the patient's quality of life) is superimposed on the item. Additionally, if there are changes to the drug packaging or the appearance of the drug itself, a message such as "The packaging (appearance) has changed" can be displayed to notify the patient of the changes. In this case, the previous prescription will display an image such as a photograph showing the drug packaging and appearance before the change, while the current prescription will display an image such as a photograph showing the drug packaging and appearance after the change. Messages such as "Bring it before drinking it," "Drink it all," "Don't forget to take it," "You can eat XX from today!", 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 contents of these messages can also include information to be notified to patients in response to changes in prescription content (such as cautions and advice from pharmacists), which can encourage patients to be more aware of changes in prescription content.

[0061] 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 how 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 next to "Capsule F." This makes it possible to display the prescription change in a way that is easier for patients to understand.

[0062] FIG. 16 is a schematic diagram showing an example of a schedule presented to a patient. FIG. 16 displays a two-week schedule for a patient. In the example schedule shown in FIG. 16, a schedule field containing the date, day of the week, and weather forecast contains a bar containing the word "medicine" indicating the medication period for which the patient will take the prescribed medication, the word "class reunion" indicating the date of the patient's class reunion, and a double-headed arrow with the word "travel" indicating the date of the patient's trip. The pharmacist can also manually input data or stamp data into this schedule. For example, the pharmacist enters "be careful not to forget to take your medication" stamp data for the "class reunion" date, and "bring your medication" stamp data for the first day of the "trip." Furthermore, the pharmacist enters "next visit" stamp data on the last day of the medication period for which the patient will take the prescribed medication, encouraging the patient to visit the pharmacy again. The "next visit" stamp data can be entered automatically on the last day of the medication period for which the patient will take the prescribed medication, or can be entered at the pharmacist's discretion. Furthermore, in the example schedule shown in Figure 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 pharmacy based on the pharmacist's work schedule. Using this scheduling function, pharmacists can set a medication schedule that takes into full consideration the patient's daily life. For example, if a patient prescribed medication for headaches wants to be in good shape for their child's sports day, the pharmacist can provide guidance on a medication schedule that will alleviate the patient's symptoms on the day of the sports day.

[0063] FIG. 17 is a schematic diagram showing an example of an interface screen for inputting stamp data. On the schedule display screen shown in Fig. 16, when a schedule column for one of the days is selected, if an operation to select (tap, etc.) the "Stamp" icon located in the bottom column of the schedule display screen is performed, an interface screen for inputting stamps will be displayed, as shown in Fig. 17. By performing an operation to select one of the stamps, the pharmacist can input the data of the desired stamp for the desired date.

[0064] FIG. 18 is a schematic diagram showing an example of an interface screen for inputting handwritten characters. On the schedule display screen shown in FIG. 16, when a schedule field for one of the days 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 characters in the area for inputting handwritten characters, and the input characters are recognized, allowing the desired character data to be input for the desired date. In addition, on the interface screen for inputting handwritten characters, the color of the input characters can be selected, and by selecting a color and then inputting handwritten characters, characters of the desired color can be input.

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

[0066] 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 entered schedule (such as by double tapping) is performed on the schedule display screen shown in Fig. 16, an interface screen for editing the schedule is displayed, as shown in Fig. 19. By selecting to change the period, schedule options, and display color of the double-headed arrow to the desired one, 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.

[0067] FIG. 21 is a schematic diagram showing an example of a screen displaying a message indicating that any consultation matter is accepted. The example screen shown in Figure 21 displays messages such as "Is there anything you're concerned about?", "I know it's difficult to talk about, but please feel free to ask me any questions," "Even if it's about your family," and "Even if it's something other than medication." By displaying such a screen, pharmacists can create an atmosphere where patients feel comfortable asking for advice.

[0068] [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 examples of the document (medication information on changes) provided to the patient. On the display screens showing the contents of the modified medication information exemplified in the above-mentioned FIGS. 13 to 15, the pharmacist can select the medications to be printed on the medication information as appropriate based on the conversation with the patient, etc. For example, Figure 22 shows an example of selecting major drugs, including drugs whose prescriptions have been changed and drugs whose prescriptions have not been changed, as the items to be printed. In Figure 22, "Tablet A" and "Tablet B," whose prescriptions have not been changed, "Tablet C," whose prescription has been discontinued, "Capsule F," which has been newly prescribed, and "Capsule D" and "Capsule G," whose prescriptions have been changed, are selected as the items to be printed.

[0069] On the other hand, Figure 23 shows an example of selecting medications whose prescriptions have been changed as the items to be printed. In Figure 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 items to be printed. As shown in Figures 22 and 23, among the medications for which prescription changes have been made, those requiring caution are marked with a "Don't take it, bring it with you" symbol, which encourages the patient to bring the medication to the pharmacy without taking it because the prescription has run out; a "Finish it all" symbol, which encourages the patient to finish the previous prescription before starting the new one; a "Don't forget to take it" symbol, which warns the patient not to forget to take the new medication because it is a new addition to the current prescription; and a "You can eat XX from today!" symbol, which indicates that the change in prescription will improve the patient's quality of life. Additionally, if there are changes to the medication packaging or the appearance of the medication itself, a "Packaging (appearance) has changed" symbol can be added to notify the patient of the change. In this case, the previous prescription will be printed with a photo or other image showing the medication packaging and appearance before the change, and the current prescription will be printed with a photo or other image showing the medication packaging and appearance after the change. These marks, such as "Please bring it before drinking 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 content (such as cautions and advice from pharmacists), which can encourage patients to be more aware of changes in prescription content.

[0070] FIG. 24 is a schematic diagram showing an example of a provided document (related document) provided to a patient. The related documents shown in Figure 24 are written documents that are given to patients to post in a conspicuous place, such as on a wall or refrigerator in their home, to make notes about anything that concerns 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 contains information about the schedule, such as the medication schedule, visit schedule, and patient plans, that the pharmacist explained to the patient on the display screen shown in Fig. 16. Also, for each day in the schedule, check boxes are provided for taking medication in the morning, afternoon, evening, and before bedtime (before going to bed).

[0071] In addition, in the predetermined related document, the time that is the standard time to take the medicine is displayed on the time axis below the schedule column. That is, in the example shown in Figure 24, 7:00 AM, 1:00 PM, and 7:00 PM are displayed as the standard time to take the medicine. In addition, below the time axis showing the approximate timing of taking medication, there is a section for patients to note any concerns they may have, and images such as photographs of medications that require special care when taking the medication are printed. Furthermore, a message from the pharmacist to the patient and contact information for the dispensing pharmacy are printed at the bottom of the prescribed related document shown in FIG.

[0072] As described above, in the information processing system 1 of this embodiment, when a pharmacist interacts with a patient at a dispensing pharmacy, information about the drug is displayed while a predetermined profile of the pharmacist is displayed, thereby stimulating the patient's interest and affinity for the pharmacist and supporting a smoother interaction. In addition, in the information processing system 1, when a pharmacist explains information about a drug (such as a change in prescribed medication) to a patient, a drug information document (drug information) reflecting the contents of that explanation is issued, allowing the patient to more easily refer to the contents of the explanation from the pharmacist even when taking the medication. Furthermore, the information processing system 1 can present the information 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.

[0073] [Variation 1] In the above-described embodiment, when the print data generating unit 158 ​​generates print data for the provided document, an image explaining the usage of the medicine included in the current prescription content may be included in the medicine information. For example, if it is an oral medication, a pictogram of the medication being taken orally, 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 using the drug incorrectly.

[0074] [Variation 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 can display the main drug on the top row, and auxiliary drugs and other drugs with lower relative importance can be displayed in the lower rows. As an example, a drug prescribed to suppress headaches can be displayed on the top row, and drugs that suppress side effects caused by taking that drug (such as drugs that protect the gastric mucosa to suppress side effects such as stomach irritation) can be displayed in the lower rows. Furthermore, for example, if a medicine is taken at different times, such as in the morning, afternoon, or evening, it is possible to display the medicines in the order of their taking times from top to bottom.

[0075] [Variation 3] In the above-described embodiment, the provided document is provided to a patient as an example, but this 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 (such as level of difficulty and granularity) can be changed depending on the knowledge of the provider who receives the provided document. Furthermore, among the documents to be provided, the drug information document (drug information) and the predetermined related documents can be intended for different recipients. For example, the contents of the document to be provided can be generated assuming that the drug information document (drug information) will be provided to the patient's caregiver and the predetermined related documents will be provided to the patient. This makes it possible to generate documents to be provided (drug information or related documents) with content suited to the purpose, depending on the recipient of the document to be provided.

[0076] In the above-described embodiment and modified examples, the document provided to the patient is described as being in the form of a predetermined document, such as a medication information change list or related documents. However, this is not limited to this. For example, the document provided to the patient may be in the form of a medicine envelope. That is, in this embodiment, the print data generated by the print data generation unit 158 ​​can be provided to the patient by printing the medicine envelope, medication information, or other information-printable medium on various media. The various media on which information can be printed may be any material, such as paper, vinyl, or electronic paper. It is also possible to print the print data on multiple media. For example, a single medium may be composed of a medication information document on which the current prescription data is printed and a sticker (e.g., a sticker printed with the previous prescription data and the details of the prescription change) that can be attached to the provided document to indicate to the patient the changes to the prescription data as a whole. Furthermore, the documents provided to patients may be printed on various media capable of printing information, or may be output in the form of electronic data that can be viewed on an electronic medicine notebook, an app for a smartphone, etc. (an app for a notebook or schedule book, etc.), or other electronic device, and provided to the patient (for example, via communication or storage media).

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

[0078] Furthermore, in the above-described embodiment and modified examples, when the display screen showing the contents of the changed medication information shown in FIG. 13 is displayed, in the initial state, drugs with the same ingredients (or efficacy) can be automatically associated and displayed between the past prescription data and the current prescription data. In this case, for example, unchanged drugs or drugs with the same ingredients (or efficacy) before and after the change can be associated and displayed. When a pharmacist moves the display position of a drug on the display screen showing the contents of the changed medication information displayed in this manner, preset display content can be automatically displayed corresponding to the resulting position. For example, if a drug in the past prescription data is moved to a display position where there is no corresponding drug in the current prescription data, a message indicating that the prescription of that drug has been discontinued (e.g., "The drug has run out") can be displayed. Similarly, if a drug in the current prescription data is moved to a display position where there is no corresponding drug in the past prescription data, a message indicating that the prescription of that drug has been added (e.g., "A new drug has been added") can be displayed. This makes it possible to more clearly explain the changes to the prescribed drugs to the patient.

[0079] 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 prescription data of the patient. 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 unit 155 and a changes data transmission unit 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 sent from the pharmacy computer 10 and the patient's past prescription data corresponding to the prescription data. The change 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. Based on the data of the changed drug information transmitted from the server 20, the screen display unit 254 displays a screen for presenting to the patient information on drugs related to the prescription including the changed drug information. The operation receiving unit 251 receives an operation input to the screen displayed by the screen display unit 254 . The screen display unit 254 changes the displayed content of the drug information in response to an operation input to the screen. With this configuration, the information processing system 1 can display information about drugs related to a prescription, including changed drug information, when a pharmacist is interacting with a patient at a pharmacy, and can also change the displayed content of the drug information depending on the operations entered on the screen. Therefore, communication between pharmacists and patients can be more appropriately supported.

[0080] The pharmacist terminal 30 includes 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 the operation on the screen input at the pharmacist terminal 30.

[0081] 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 a patient (print data or data for output to a storage medium, etc.) including changed medication information based on the content of the operation transmitted by the operation content transmission unit 255. 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 . Based on the output data transmitted from the server 20, the print control unit 56 outputs the provided document as a medium to be handed over to the patient. 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.

[0082] 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 for a pharmacist profile screen to be presented to a patient based on the data of the pharmacist's profile and the attributes of the patient. The profile screen data transmission unit 154 transmits the 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 pharmacist's profile screen to be displayed according to the patient's attributes, which stimulates the patient's interest and sense of affinity with the pharmacist and supports smoother dialogue between the pharmacist and the patient.

[0083] 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 more strongly stimulate patients' interest and affinity towards pharmacists.

[0084] The screen display unit 254 displays a screen of a schedule relating to the patient, including a schedule for taking medicines included in the patient's prescription. The operation receiving unit 251 receives operations input on 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 allows the server 20 to generate data for the patient's schedule and generate print data by reflecting the inputted content in the patient's schedule.

[0085] The present invention is not limited to the above-described embodiment, and any modifications and improvements 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 be provided with 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, using the data stored in the prescription DB 172 or the patient attribute DB 173 of the server 20. Furthermore, the information processing system 1 according to the present invention can be configured by 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.

[0086] 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 functional blocks used to realize this function are 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 thereof.

[0087] Furthermore, 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 main body in order to provide the program to the user, but also as a recording medium provided to the user in a state where it is pre-installed in the device main body.

[0088] Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments. Furthermore, the effects described in the present embodiments are merely a list of the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described in the present embodiments. [Explanation of symbols]

[0089] 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 receiving unit, 56 print control unit, 71 prescription database, 72 patient attribute database, 151 prescription data receiving unit, 152 patient attribute receiving 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 receiving 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 usage database, 176 change drug information database, 177 schedule database, 251 Operation reception unit, 252 profile screen data reception unit, 253 change data reception unit, 254 screen display unit, 255 operation content transmission 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

1. An information processing system including an information processing device that manages patient-related data 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 prescription data of the patient; a change acquisition means for acquiring change information regarding drugs that have been changed between the patient's past prescription content and the current prescription content based on the prescription data and the patient's past prescription data corresponding 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 the 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:

2. 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.

3. The information processing device includes: an output data generating means for generating output data of a document to be provided to the patient, including the changed medication 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.

4. The information processing device includes: a prescription database for storing data on prescriptions of said patients; 4. The information processing system according to claim 1, wherein the prescription database accumulates and stores data on the patient's current prescription acquired by the prescription data acquisition means.

5. An information processing system as described in any one of claims 1 to 4, characterized in that the profile screen data generation means selects data from the pharmacist's profile data that is common to the patient's attributes and generates the data for the pharmacist's profile screen.

6. 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 prescription data of the patient; a change acquisition means for acquiring change information regarding drugs that have been changed between the patient's past prescription content and the current prescription content based on the prescription data and the patient's past prescription data corresponding 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 data from 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 from the changed drug information.

7. An information processing method executed by an information processing system including an information processing device that manages patient-related data 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 generation 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 drugs that have been changed between the patient's past prescription content and the current prescription content based on the prescription data and the patient's past prescription data 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 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 method comprising:

8. A computer constituting an information processing device in an information processing system including an information processing device for managing patient-related data 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 that generates 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 that acquires change information regarding drugs that have been changed between the patient's past prescription content and the current prescription content based on the prescription data and the patient's past prescription data corresponding to the prescription data; a change data transmission function for transmitting the change drug information data to the terminal device; To achieve 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 from the changed drug information.

Images