Information processing system, information processing device, information processing method, and program
The information processing system improves pharmacist-patient communication by displaying medication changes and schedules tailored to patient attributes, addressing the challenge of understanding complex medication information.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- HIGASHI NIHON MEDICOM
- Filing Date
- 2026-01-30
- Publication Date
- 2026-04-28
AI Technical Summary
Conventional technologies hinder effective communication between pharmacists and patients, with patients often perceiving pharmacists as unapproachable and struggling to understand medication information, especially when changes occur or multiple medications are involved, leading to potential misuse.
An information processing system comprising a pharmacy computer, server, and pharmacist's terminal that acquires, transmits, and displays prescription data, including changes in medication, using a pharmacist's profile and patient attributes to facilitate communication, and provides easy-to-understand medication information and schedules.
Enhances communication support by making medication information more accessible and understandable for patients, ensuring they take medications appropriately, even with changes or multiple prescriptions.
Smart Images

Figure 2026071279000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an information processing system, an information processing apparatus, an information processing method, and a program.
Background Art
[0002] Conventionally, when dispensing is performed at a pharmacy, a patient submits a prescription, and after a pharmacist conducts an interview with the patient, etc., the pharmacist prepares the medicine based on the prescription. Then, after the pharmacist explains the medicine to the patient, etc., the medicine is dispensed to the patient. In such a dispensing operation, as a technique for supporting communication between a pharmacist and a patient, the technique described in Patent Document 1 is known. That is, Patent Document 1 discloses a medication information system for providing appropriate and detailed medication guidance for each recipient by outputting medication-related information based on a protocol for selecting the situation for each recipient and the medication-related information to be output according to the situation, regardless of the ability of the pharmacist.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] However, in conventional technologies, including the technology described in Patent Document 1, pharmacists are often perceived as unapproachable by patients, which can hinder pharmacists from communicating effectively with patients. Furthermore, patients may not fully understand the information about their medications (such as changes in prescribed medications) provided by pharmacists, and may not be able to fully utilize the information provided by pharmacists when taking their medications. In addition, when multiple medications are prescribed or when pharmacists provide special instructions to patients (such as guidance on medication schedules that take daily life into consideration), the method of taking the medications can become complicated, and patients may not be able to take their medications properly. Thus, conventional technologies have made it difficult to adequately support communication between pharmacists and patients.
[0005] The objective of this invention is to provide more appropriate support for communication between pharmacists and patients. [Means for solving the problem]
[0006] To solve the above problems, an information processing system according to one aspect of the present invention is: An information processing system including a pharmacy computer installed in a pharmacy, a pharmacist's terminal used by a pharmacist, and a server that manages data used in the pharmacy, The aforementioned pharmacy computer is A prescription data acquisition method for obtaining patient prescription data, A prescription data transmission means that transmits the prescription data acquired by the prescription data acquisition means to the server, Equipped with, The aforementioned server, A change acquisition means for acquiring change information regarding medications that have been changed between past prescriptions and current prescriptions for a patient, based on the prescription data transmitted from the pharmacy computer and the patient's past prescription data corresponding to the said prescription data. A change data transmission means for transmitting the data of the changed drug information to the pharmacist's terminal, Equipped with, The aforementioned pharmacist terminal is A screen display means for displaying a screen to present to the patient information on medications related to the prescription, including the changed medication information, based on the changed medication information data transmitted from the server, An operation receiving means for receiving operations input to the screen displayed by the screen display means, Equipped with, The screen display means is characterized by changing 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, it is possible to more appropriately support communication between pharmacists and patients. [Brief explanation of the drawing]
[0008] [Figure 1] This figure shows the system configuration of an information processing system 1 according to one embodiment of the present invention. [Figure 2] This diagram shows the hardware configuration of the information processing device 800 that makes up each device. [Figure 3] This is a block diagram showing the functional configuration of a pharmacy computer 10. [Figure 4] This block shows the functional configuration of Server 20. [Figure 5] This is a block diagram showing the functional configuration of the pharmacist's terminal 30. [Figure 6] This is a flowchart showing the flow of drug information output processing performed by the pharmacy computer 10. [Figure 7] This flowchart shows the flow of the data generation process performed by server 20. [Figure 8] This is a flowchart showing the flow of communication support processing performed by the pharmacist's terminal 30. [Figure 9] This is a schematic diagram showing an example of the initial screen displayed during communication support processing. [Figure 10] It is a schematic diagram showing an example of a pharmacist's profile screen. [Figure 11] It is a schematic diagram showing an example of a questionnaire screen. [Figure 12] It is a schematic diagram showing an example of a state where answers to a questionnaire have been given. [Figure 13] It is a schematic diagram showing an example of a display screen showing the content of the changed drug information. [Figure 14] In the display screen shown in FIG. 13, it is a schematic diagram showing an example of a state where a pharmacist has performed an operation for explaining the prescription content to a patient. [Figure 15] It is a schematic diagram showing an example of a state where the arrangement of the items displayed in a list is changed. [Figure 16] It is a schematic diagram showing an example of a schedule presented to a patient. [Figure 17] It is a schematic diagram showing an example of an interface screen for inputting stamp data. [Figure 18] It is a schematic diagram showing an example of an interface screen for inputting handwritten characters. [Figure 19] It is a schematic diagram showing an example of an interface screen for registering a new schedule. [Figure 20] It is a schematic diagram showing an example of an interface screen for editing a schedule that has already been input. [Figure 21] It is a schematic diagram showing an example of a screen for displaying a message indicating that any consultation matters are accepted. [Figure 22] It is a schematic diagram showing an example of a provided document (changed drug information) provided to a patient. [Figure 23] It is a schematic diagram showing an example of a provided document (changed drug information) provided to a patient. [Figure 24] It is a schematic diagram showing an example of a provided document (related document) provided to a patient.
Embodiments for Carrying Out the Invention
[0009] Embodiments of the present invention will be described below with reference to the drawings.
[0010] The information processing system 1 according to this embodiment supports smoother dialogue by displaying information about medications while showing a predetermined profile of the pharmacist when a pharmacist interacts with a patient in a dispensing pharmacy, thereby stimulating the patient's interest in and familiarity with the pharmacist. Furthermore, regarding the information (prescription details) written on the prescription issued to the patient, when the pharmacist explains information about the medication (such as changes in prescribed medications between past and current prescriptions) to the patient, the information processing system 1 according to this embodiment issues a medication information document (hereinafter referred to as "medication information" as appropriate) that reflects the content of that explanation, thereby supporting the patient in easily referring to the explanation given by the pharmacist when taking the medication. In addition, the information processing system 1 according to this embodiment presents the content explained by the pharmacist to the patient, such as how to take the prescribed medication, in an information format that is easy for the patient to understand, thereby supporting the patient in taking the medication appropriately. The specific configuration will be explained below.
[0011] [System configuration of Information Processing System 1] Figure 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 Figure 1, the information processing system 1 comprises a pharmacy computer 10, a server 20, and a pharmacist terminal 30. The pharmacy computer 10, server 20, and pharmacist terminal 30 are configured to communicate with each other via a network 40. The pharmacy computer 10 and pharmacist terminal 30 are installed in the same dispensing pharmacy. Furthermore, the information processing system 1 according to this embodiment is operated on a predetermined regional basis, with one server 20 installed for multiple pharmacy computers 10 and pharmacist terminals 30 belonging to that region. Note that in Figure 1, for the sake of explanation, only one pharmacy computer 10 and one pharmacist terminal 30 are shown.
[0012] The pharmacy computer 10 is composed of a PC (Personal Computer) or a server computer and is equipped with medication history management functions and medical fee statement (receipt) creation functions. The pharmacy computer 10 accepts input of patient prescription data and stores and manages the received prescription data. The pharmacy computer 10 also calculates the details of medical fees for dispensing medication to patients based on prescriptions. Furthermore, the pharmacy computer receives print data for patient provision documents (described later), including drug information provision documents (drug information) and prescribed related documents, from the server 20 and prints the provision documents using a printer installed in the dispensing pharmacy. In this embodiment, the drug information provision document (drug information) consists of a document or something equivalent to a document (for example, a sticker that can be attached to a notebook) that represents information such as the name of the drug, usage, dosage, efficacy, effects, side effects, and interactions.
[0013] Server 20 is composed of a server computer and acquires prescription data received by the pharmacy computer 10, and generates data for the pharmacist's profile screen that is presented to the patient. Server 20 also stores and manages prescription data received by the pharmacy computer 10 and generates data on changes to the medication prescribed to the patient (changes between the previous prescription and the current prescription). This change data is transmitted to the pharmacist's terminal 30 for screen display, or transmitted to the pharmacy computer 10 for printing as part of the medication information. Furthermore, Server 20 manages schedule data for each patient, such as medication schedules or visit schedules.
[0014] The pharmacist terminal 30 consists of a tablet or notebook PC and acquires profile screen data generated by the server 20. When the pharmacist communicates with the patient, the pharmacist's profile is displayed on the screen. The pharmacist terminal 30 also acquires medication change data generated by the server 20 and displays the medication before and after the change for comparison when the pharmacist communicates with the patient. Furthermore, the pharmacist terminal 30 accepts input of schedule data for the patient, such as medication administration schedules or visit schedules, and transmits the entered schedule data to the server 20.
[0015] [Hardware configuration] Next, we will describe the hardware configuration of each device in Information Processing System 1. In Information Processing System 1, each device consists of an information processing device such as a PC, server computer, or tablet terminal, and their basic configurations are the same.
[0016] Figure 2 shows the hardware configuration of the information processing device 800 that constitutes each device. As shown in Figure 2, each information processing device 800 comprises 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.
[0017] The CPU 811 executes various processes according to the program recorded in the ROM 812 or the program loaded into the RAM 813 from the storage unit 817. RAM813 also stores data necessary for CPU811 to perform various processes.
[0018] The CPU 811, ROM 812, and RAM 813 are interconnected via a bus 814. The input unit 815, output unit 816, storage unit 817, communication unit 818, drive 819, and imaging unit 820 are connected to the bus 814.
[0019] The input unit 815 consists of various buttons and other components, and inputs various types of information according to the instructions and operations. The output unit 816 consists of a display, speakers, etc., and outputs images and sound. Furthermore, if the information processing device 800 is configured as a smartphone or tablet terminal, the input unit 815 and the output unit 816 display may be placed on top of each other to form a touch panel. The memory unit 817 consists of a hard disk or DRAM (Dynamic Random Access Memory), and stores various types of data managed by each server. The communication unit 818 controls communication with other devices via the network.
[0020] A removable media 831, consisting of a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, is appropriately mounted in the drive 819. Programs read from the removable media 831 by the drive 819 are installed in the storage unit 817 as needed. The imaging unit 820 is composed of an imaging device equipped with a lens and an image sensor, and captures a digital image of the subject. Furthermore, if the information processing device 800 is configured as a server 20, it is possible to omit the imaging unit 820. Also, if the information processing device 800 is configured as a tablet terminal, it is possible to configure the input unit 815 with a touch sensor and place it on top of the display of the output unit 816 to provide a touch panel.
[0021] [Functional configuration] Next, the functional configuration of each device in Information Processing System 1 will be described. [Functional configuration of the pharmacy computer 10] Figure 3 is a block diagram showing the functional configuration of the pharmacy computer 10. As shown in Figure 3, the CPU 811 of the pharmacy computer 10 functions as 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. In addition, the storage unit 817 of the pharmacy computer 10 contains a prescription database (prescription DB) 71 and a patient attribute database (patient attribute DB) 72.
[0022] The prescription database 71 stores data on prescriptions received by the pharmacy computer 10. This prescription data includes patient identification information such as the patient's name, age, gender, and insurer number; medical institution identification information such as the name of the issuing medical institution, the doctor's name, and the medical institution's contact information; and prescription details such as the name of the prescribed medication, dosage form, administration and dosage, and whether or not generic drugs can be used. The patient attribute database (DB72) stores data such as the patient's address, name, age, gender, and information representing the patient's individual characteristics (patient attributes). These patient attributes are compiled from information obtained by pharmacists through conversations with patients and information provided by patients through questionnaires (interviews), etc. For example, they include the patient's hobbies, occupation, family structure, favorite foods, favorite colors, favorite characters, and things that concern them in their daily life (things directly related to medical care, such as physical pain, or things not directly related to medical care, such as concerns about their children's education).
[0023] The prescription data acquisition unit 51 acquires data representing the contents of a prescription (prescription data) that is accepted at a pharmacy when brought in by a patient. In this embodiment, the prescription data acquisition unit 51 acquires prescription data that is generated when the contents of the prescription brought in by the patient are entered by a pharmacist or operator at the pharmacy via the input unit 815. 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. In addition, patient identification information from the prescription data is also appropriately stored in the patient attribute DB 72 if it is a new patient or if there are changes to the patient identification information. 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 for patients corresponding to prescription data. The patient attribute data is generated before the current visit by a pharmacist interacting with the patient and inputting it using the pharmacist's terminal 30, or by the pharmacist or operator at the dispensing pharmacy inputting the results of questionnaires given to the patient 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 documents provided to patients, including drug information documents, which are sent from the server 20. The print control unit 56 prints documents to be provided to patients, including medication information, from a printer installed in the pharmacy, based on the print data received by the print data receiving unit 55.
[0027] [Functional configuration of Server 20] Figure 4 is a block diagram showing the functional configuration of server 20. As shown in Figure 4, the CPU 811 of the server 20 functions as follows: prescription data receiving unit 151, patient attribute receiving unit 152, profile screen data generation unit 153, profile screen data transmission unit 154, change acquisition unit 155, change data transmission unit 156, operation content receiving unit 157, print data generation unit 158, and print data transmission unit 159. In addition, the storage unit 817 of the server 20 contains 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 usage database (pharmacy-specific drug usage DB) 175, a change drug information database (change drug information DB) 176, and a schedule database (schedule DB) 177.
[0028] The Pharmacist Profile DB171 stores data on the profiles of pharmacists belonging to each dispensing pharmacy (pharmacist's photo, name, age, marital status, gender, specialty, community activities, current areas of focus and the reasons for focusing on them, reason for becoming a pharmacist, what made them happy as a pharmacist, hobbies, etc.). This pharmacist profile data is entered and stored sequentially when each pharmacist joins a dispensing pharmacy. It is also possible to modify pharmacist profiles as needed, according to the pharmacist's wishes.
[0029] The prescription database 172 stores the data from each prescription database 71 stored in the pharmacy computer 10 of each dispensing pharmacy. In other words, the prescription database 172 aggregates and stores the data from each prescription database 71 of each dispensing pharmacy for a predetermined region where the server 20 is operated. The patient attribute database 173 stores the data from each patient attribute database 72 stored in the pharmacy computer 10 of each dispensing pharmacy. In other words, the patient attribute database 173 aggregates and stores the data from each dispensing pharmacy's patient attribute database 72 for a predetermined region where the server 20 is operated.
[0030] Drug DB174 stores data representing information about various drugs. For example, Drug DB174 stores data such as information described in package inserts and information about drug prices for various drugs. The Pharmacy-Specific Drug Usage Database (DB175) stores data representing the drugs used in dispensing at each pharmacy. This data is updated as needed based on requests from the pharmacy when the drugs used at that pharmacy are changed or for other reasons.
[0031] The Changed Drug Information DB176 stores information about medications that have been changed between a patient's previous prescription and the current prescription (hereinafter referred to as "Changed Drug Information"). For example, the Changed Drug Information DB176 stores information about medications added to the previous prescription for the same patient, medications that were discontinued from the previous prescription, or other medications that were changed from those included in the previous prescription, as Changed Drug Information. The schedule database 177 stores schedule data for each patient. This schedule data reflects the specific schedules (medication schedule, visit schedule, etc.) of patients that pharmacists have interacted with and entered using the pharmacist's terminal 30.
[0032] The prescription data receiving unit 151 receives prescription data transmitted from the pharmacy computer 10. The prescription data receiving unit 151 then stores the received prescription data in the prescription DB 172. The patient attribute receiving unit 152 receives patient attribute data transmitted from the pharmacy computer 10. The patient attribute receiving unit 152 then stores the received patient attribute data 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 the profile data of the pharmacist to be featured and the patient attributes of the patient who will receive the profile screen from the pharmacist profile DB 171 and the patient attribute DB 173, respectively. Then, based on the profile data of the pharmacist to be featured and the patient attributes of the patient who will receive the profile screen, the profile screen data generation unit 153 generates the profile screen data for presenting the pharmacist's profile to the patient. When the profile screen data generation unit 153 generates the profile screen data, it selects the profile items that will be displayed permanently and the items from all of the pharmacist's profile data that have common attributes with the patient. At this time, the profile screen data generation unit 153 may also select screen elements other than the pharmacist's profile (background, color scheme, font size, type of display frame, etc.) according to the patient's attributes.
[0034] The profile screen data transmission unit 154 transmits the profile screen data generated by the profile screen data generation unit 153 to the pharmacist terminal 30 that requested the generation of the profile screen. When prescription data is received by the prescription data receiving unit 151, the change acquisition unit 155 reads 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 from the prescription DB 172 and acquires information (changed drug information) about the medications that have been changed between the previous prescription and the current prescription for that patient. Furthermore, the change acquisition unit 155 stores the acquired changed drug information data in the changed drug information DB 176. In addition, images such as photographs of medications (e.g., color photographs) (appearance of packaging or the medication itself, etc.) may be stored in the drug DB 174, and if the same medication is prescribed but there have been changes to the packaging, etc. of the medication between the previous prescription and the current prescription for that patient, the images such as photographs of the medication may be included in the changed drug information.
[0035] When the pharmacist terminal 30 requests the transmission of modified drug information for a specific patient, the modified drug information data stored in the modified drug information DB 17 is transmitted to the pharmacist terminal 30. The operation content receiving unit 157 receives the content of operations performed on the display screen from the pharmacist terminal 30. The content of operations performed on the display screen from the pharmacist terminal 30 includes, for example, specifying which items to print in the drug information, changing the arrangement of items in the drug information, specifying whether to display detailed explanations in the drug information, and printing instructions for documents provided to patients, including drug information. These operation details are sent from the pharmacist terminal 30 to the server 20 in batches each time an operation is performed on the display screen, or when a printing instruction for documents provided to patients, including drug information, is given.
[0036] When a print data generation unit 158 receives a print instruction from the pharmacist's terminal 30 to the server 20 for a document to be provided to a patient, including medication information, it generates print data for the document, which includes medication information provided to the patient and predetermined related documents containing various information explained to the patient by the pharmacist. For example, the medication information includes drug information, including changes to the medication information, and the predetermined related documents contain information about the schedule, such as the medication administration schedule or the schedule of visits to the pharmacy, which the pharmacist explained to the patient at the pharmacist's 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 the pharmacist's terminal 30] Figure 5 is a block diagram showing the functional configuration of the pharmacist's terminal 30. As shown in Figure 5, the CPU 811 of the pharmacist terminal 30 functions as follows: operation reception unit 251, profile screen data reception unit 252, change data reception unit 253, screen display unit 254, and operation content transmission unit 255. The operation reception unit 251 accepts various operations that are entered in response to the content displayed on the display screen. For example, the operation reception unit 251 accepts operations such as specifying which items in the drug information to print, changing the arrangement of items in the drug information, specifying whether to display detailed explanations in the drug information, writing on the schedule presented to the patient, and printing instructions for documents provided to the patient, including the drug information.
[0038] The profile screen data receiving unit 252 receives profile screen data transmitted from the server 20. The change data receiving unit 253 receives the change information data transmitted from the server 20. The screen display unit 254 displays various display screens on the display, such as the initial screen of the pharmacist terminal 30 (selection screen for various menus, etc.), the profile screen based on the data on the profile screen, the display screen for changed medication information based on the data on changed medication information, or the patient schedule screen. 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, send changed medication information, etc.
[0039] The operation content transmission unit 255 transmits the content of the operation on the display screen received by the operation reception unit 251 to the server 20. These operation contents are transmitted to the server 20 in batches each time an operation is performed on the display screen of the pharmacist terminal 30, or when a print instruction is given for patient documents, including medication information.
[0040] [Operation] Next, we will explain the operation of information processing system 1.
[0041] [Processing by Pharmacy Computer 10] Figure 6 is a flowchart showing the flow of drug information output processing performed by the pharmacy computer 10. The drug information output processing is initiated in response to an instruction input to execute drug information output processing via the input unit 815 of the pharmacy computer 10.
[0042] When the drug information output process begins, in step S1, the prescription data acquisition unit 51 acquires data (prescription data) representing the contents of the prescription received at the pharmacy by the patient. The prescription data acquired at this time 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, patient attribute data for 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. After this, the pharmacy computer 10 enters a standby state, waiting to receive the print data transmitted from the server 20.
[0043] In step S5, the print data receiving unit 55 receives print data of documents to be provided to the patient, including drug information documents (drug information), which have been sent from the server 20. In step S6, the print control unit 56 prints documents to be provided to the patient, including medication information, from a printer installed in the pharmacy, based on the print data received by the print data receiving unit 55. After step S6, the drug information output process is completed.
[0044] [Processing by Server 20] Figure 7 is a flowchart showing the flow of the data generation process performed by server 20. The data generation process starts when server 20 boots up and is executed repeatedly.
[0045] When the data generation process begins, 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 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 receives a request from the pharmacist terminal 30 to generate profile screen data for presenting the pharmacist's profile to the patient, and generates the pharmacist's profile screen data. In step S14, the profile screen data transmission unit 154 transmits the profile screen data generated by the profile screen data generation unit 153 to the pharmacist terminal 30 that requested the generation of the profile screen.
[0047] In step S15, the change acquisition unit 155, in response to the prescription data being received by the prescription data receiving unit 151, acquires information (changed drug information) regarding the medications that have been changed between the previous prescription and the current prescription for the patient corresponding to the prescription data. The acquired changed drug information data is stored in the changed drug information DB 176.
[0048] In step S16, the change data transmission unit 156, in response to a request from the pharmacist terminal 30 to transmit change medication information for a specific patient, transmits the change medication information data stored in the change medication 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 unit 157 receives from the pharmacist terminal 30 the content of the operation on the display screen that was entered on the pharmacist terminal 30.
[0049] In step S18, the print data generation unit 158 receives a print instruction from the pharmacist terminal 30 to the server 20 for a document to be provided to the patient, including medication information. In response, the unit generates print data for the document, which includes medication information to be provided to the patient and a predetermined related document containing various information explained to the patient by the pharmacist. In step S19, 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.
[0050] [Processing on pharmacist terminal 30] Figure 8 is a flowchart showing the flow of communication support processing performed by the pharmacist terminal 30. The communication support process is initiated in response to an instruction to execute the communication support process being input via the input unit 815 of the pharmacist's terminal 30.
[0051] When the communication support process is initiated, in step S21, the screen display unit 254 requests the server 20 to generate data for the profile screen. In step S22, the profile screen data receiving unit 252 receives the profile screen data transmitted from the server 20. In step S23, the screen display unit 254 requests the server 20 to send data on the changed drug information.
[0052] In step S24, the change data receiving unit 253 receives the change drug information data transmitted from the server 20. In step S25, the screen display unit 254 sequentially displays various display screens on the display, including the pharmacist's profile screen and the screen displaying the changes to the medication information. In step S26, the operation reception unit 251 receives various operations to be entered in response to the content displayed on the display screen.
[0053] In step S27, the operation content transmission unit 255 transmits the content of the operation on the display screen received by the operation reception unit 251 to the server 20. In step S28, the screen display unit 254 determines whether or not the termination of the communication support process has been instructed. If the termination of the communication support process is not instructed, the result is determined to be NO in step S28, and the process proceeds to step S25. On the other hand, if the termination of the communication support process is instructed, the result in step S28 is determined to be YES, and the communication support process is terminated.
[0054] [Display screen example] Next, we will explain an example of a display screen that appears during communication support processing. Figure 9 is a schematic diagram showing an example of the initial screen displayed during the communication support process. As shown in Figure 9, the screen display unit 254 initially displays an initial screen showing the patient's name, date of birth, age, etc. In this embodiment, the background, color scheme, and type of display frame of the initial screen are selected by the server 20 according to the patient's attributes.
[0055] Figure 10 is a schematic diagram showing an example of a pharmacist's profile screen. As shown in Figure 10, following the initial screen, the screen display unit 254 displays the pharmacist's profile screen. The pharmacist's profile screen includes fixed profile items and items selected by the server 20 according to the patient's attributes. For example, in the example shown in Figure 10, the fixed profile items displayed include the pharmacist's photo, name, age, marital status, community activities, and areas of focus. Also, in the example shown in Figure 10, "Hobby: Walking" is displayed as an item selected according to the patient's attributes. That is, the patient attributes of the patient to whom the profile screen in Figure 10 is presented include the data "Hobby: Walking," and in the pharmacist's profile data, the item "Hobby: Walking," which is common to the patient's attribute information, is selected and displayed on the profile screen.
[0056] Figure 11 is a schematic diagram showing an example of a survey screen. As shown in Figure 11, the screen display unit 254 displays questionnaire content regarding medication use in response to the pharmacist's operation on the display screen, and the operation reception unit 251 receives the pharmacist's selection operation for the items of this questionnaire.
[0057] Figure 12 is a schematic diagram showing an example of a state in which responses to a questionnaire have been received. In the example shown in Figure 12, the patient selected the option "I like taking medicine to feel at ease" in response to the question "Do you like medicine?". Also in the example shown in Figure 12, the patient selected the option "Sometimes" in response to the question "Do you ever forget to take your medicine?". In this embodiment, as shown in Figure 12, a simplified version of the pharmacist's profile is displayed on screens other than the pharmacist's profile screen, such as the questionnaire display screen.
[0058] Figure 13 is a schematic diagram showing an example of a display screen that shows the contents of the changed drug information. As shown in Figure 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 Figure 13, the previous prescription contents are displayed, including the name of the medical institution to which the prescribing physician belongs, the department, the physician's name, the date of prescription, etc., and a list of the medications prescribed last time. Similarly, in the example shown in Figure 13, the current prescription contents are displayed, including the name of the medical institution to which the prescribing physician belongs, the department, the physician's name, the date of prescription, etc., and a list of the medications prescribed this time. The pharmacist can explain the contents of the prescription change to the patient in an easy-to-understand manner by showing the display screen shown in Figure 13 to the patient and operating the display screen.
[0059] Figure 14 is a schematic diagram showing an example of a pharmacist performing operations to explain the prescription details to a patient on the display screen shown in Figure 13. As shown in Figure 14, for "Tablet A" and "Tablet B," there are no changes between the previous and current prescriptions. When the pharmacist manipulates the "Tablet A" and "Tablet B" entries, an arrow indicating that they are the same prescription is displayed, clearly indicating that there are no changes to the prescription. On the other hand, for "Tablet C," although it was included in the previous prescription, it is not included in the current prescription. When the pharmacist manipulates the "Tablet C" entry, a dashed "x" indicating that the prescription has been discontinued, along with the message "x Do not take, bring it with you," is displayed overlaid on the "Tablet C" entry. Furthermore, for "Capsule D," although the prescription has been switched to "Capsule G," it is necessary to finish the prescribed "Capsule D" before switching to "Capsule G." When the pharmacist manipulates the "Capsule D" entry, a message instructing the pharmacist to finish the remaining "Capsule D," "○ Finish taking it," is displayed overlaid on the "Capsule D" entry. Additionally, an arrow indicating that the prescription has been changed from "Capsule D" to "Capsule G," along with the message "Finish taking it before changing," clearly indicate how the prescription has been changed.
[0060] Furthermore, when a pharmacist manipulates the items of medications prescribed in the current prescription, such as "Tablet A" and "Capsule F," a message such as "◎Don't forget to take your medication" will be displayed over these items. Additionally, when a pharmacist manipulates an item in the current prescription that has been changed from the previous prescription and benefits the patient, such as "Capsule G," a message indicating the benefit to the patient (for example, "You can start eating ○○ from today!", improving the patient's quality of life) will be displayed over this item. In addition, if there are changes to the packaging or appearance of the medication itself, it is also possible to display a message such as "Packaging (appearance) has changed" to notify the patient of the changes. In this case, the previous prescription will display images such as photographs showing the packaging or appearance of the medication before the change, and the current prescription will display images such as photographs showing the packaging or appearance of the medication after the change. Messages such as "Don't drink it, bring it with you," "Finish drinking it," "Don't forget to take it," "You can eat XX starting today!", and "The packaging (appearance) has changed" can be displayed automatically based on a comparison of the data from the previous prescription with the data from the current prescription, as well as the pharmacist's actions. In addition to the examples mentioned above, these messages can also include information that should be communicated to the patient regarding changes in their prescription (such as warnings and advice from the pharmacist). This can help patients become more aware of changes in their prescription.
[0061] Here, on the display screen showing the changes to the medication information, the items listed can be rearranged within the previous prescription details and the current prescription details for purposes such as ease of explanation. Figure 15 is a schematic diagram illustrating an example of how the arrangement of items in a list is changed. As shown in Figure 15, if "Tablet C" in the previous prescription has been changed to "Capsule F," which has the same efficacy, in the current prescription, the position of "Tablet C" can be moved to a position next to "Capsule F" to change its arrangement. This makes the changes to the prescription easier for patients to understand.
[0062] Figure 16 is a schematic diagram showing an example of a schedule presented to a patient. Figure 16 displays a patient's schedule for two weeks. In the example schedule shown in Figure 16, the schedule column, which consists of the date, day of the week, and weather forecast, includes a band with the word "Medicine" indicating the duration of prescribed medication, the word "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. Furthermore, pharmacists can input data into this schedule using handwritten input or stamp data. For example, the pharmacist has entered "Remember to take medication" stamp data for the date of the "Reunion," and the pharmacist has entered "Take medication with you" stamp data for the first day of the "Travel." In addition, the pharmacist has entered "Next visit" stamp data at the end of the prescribed medication period to encourage the next visit. The "Next visit" stamp data can be entered automatically at the end of the prescribed medication period or at the pharmacist's discretion. Furthermore, in the example schedule shown in Figure 16, the pharmacist's work schedule is indicated at the bottom of the schedule column, allowing patients to decide when to visit the pharmacy based on the pharmacist's work schedule. By utilizing this scheduling function, pharmacists can create medication schedules that take into full consideration the patient's daily life. For example, if a patient prescribed medication for headaches wants to be in good health for their child's sports day, the pharmacist can guide them through a medication schedule to ensure the patient's symptoms are alleviated on the day of the event.
[0063] Figure 17 is a schematic diagram showing an example of an interface screen for inputting stamp data. In the schedule display screen shown in Figure 16, if you select a schedule entry for any day and then perform an action (such as tapping) to select the "stamp" icon located at the bottom of the schedule display screen, an interface screen for entering stamps will appear, as shown in Figure 17. By selecting one of the stamps, the pharmacist can enter the data for the desired stamp on the desired date.
[0064] Figure 18 is a schematic diagram showing an example of an interface screen for inputting handwritten characters. In the schedule display screen shown in Figure 16, if you select a schedule column for any day and then perform an action (such as tapping) to select the "Handwriting" icon located at the bottom of the schedule display screen, an interface screen for inputting handwritten characters will appear, as shown in Figure 18. The pharmacist can then handwrite any character in the designated area, and the entered character will be recognized, allowing the pharmacist to input the desired character data for the desired date. Furthermore, the interface screen for inputting handwritten characters allows the user to select the color of the characters to be entered. By selecting a color and then handwriting the character, the user can input the character of the desired color.
[0065] Figure 19 is a schematic diagram showing an example of an interface screen for registering a new appointment. In the schedule display screen shown in Figure 16, selecting (tapping, etc.) the "Add Appointment" icon located at the bottom of the schedule display screen will display an interface screen for registering a new appointment, as shown in Figure 19. The pharmacist can select the period, the appointment options, and the color of the double-headed arrow. The double-headed arrow indicating the selected period will be displayed in the selected color, and the pharmacist can enter text indicating the selected appointment from the appointment options.
[0066] Figure 20 is a schematic diagram showing an example of an interface screen for editing an already entered schedule. In the schedule display screen shown in Figure 16, when an operation (such as double-tapping) is performed to select an already entered appointment, an interface screen for editing the appointment is displayed, as shown in Figure 19. The pharmacist can change the period, appointment options, and the display color of the double-headed arrow to their desired settings. The double-headed arrow indicating the selected period will then be displayed in the selected color, and the pharmacist can enter text indicating the selected appointment from the appointment options.
[0067] Figure 21 is a schematic diagram showing an example screen displaying a message indicating that any consultation topics are accepted. In the example screen shown in Figure 21, messages such as "Is there anything you're concerned about?", "I know it might be difficult to talk about, but please don't hesitate to ask," "Even about your family," and "Even about things other than medication" are displayed. By presenting such screens, pharmacists can create an atmosphere where patients feel comfortable asking questions.
[0068] [Specific examples of drug information documents] Next, we will describe specific examples of documents provided to patients. Figures 22 and 23 are schematic diagrams showing an example of a document (medication information regarding changes) provided to a patient. In the display screen showing the contents of the drug information document, as illustrated in Figures 13 to 15 above, the drugs to be printed on the drug information document can be appropriately selected by the pharmacist based on their conversation with the patient, etc. For example, Figure 22 shows an example of selecting major medications, including those whose prescriptions have been changed and those whose prescriptions have not been changed, as the print target. 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 switched, are selected as the print target.
[0069] On the other hand, Figure 23 shows an example of selecting medications whose prescriptions have been changed as the target for printing. In Figure 23, the newly prescribed "F capsules," the switched prescriptions for "D capsules" and "G capsules," and the discontinued prescription for "C tablets" are selected as the target for printing. As shown in Figures 22 and 23, for medications whose prescriptions have been changed and which require special attention, the following marks are added: a "Don't take it, bring it to the pharmacy" mark to encourage patients to bring the medication to the pharmacy without taking it, as the prescription has been discontinued; a "Finish taking it" mark to encourage patients to finish the previously prescribed medication before starting the newly prescribed medication; a "Don't forget to take it" mark to remind patients not to forget to take the medication as it has been newly added to the current prescription; and a "You can start eating XX from today!" mark to indicate that the patient's quality of life will improve as a result of the change in prescription. In addition, if there are changes to the packaging or appearance of the medication itself, it is also possible to add a "Packaging (Appearance) has changed" mark to notify the patient of the changes in packaging or appearance. In this case, the previous prescription will have images such as photographs showing the packaging or appearance of the medication before the change printed on it, and the current prescription will have images such as photographs showing the packaging or appearance of the medication after the change printed on it. These marks, such as "Please bring it with you without drinking it," "Please finish drinking it," "Don't forget to take it," "You can eat XX starting today!", and "The packaging (appearance) has changed," can be automatically added based on a comparison of the data from the previous prescription with the data from the current prescription, as well as the pharmacist's actions. In addition to the examples mentioned above, the information displayed by these marks can also include information that should be communicated to the patient regarding changes in prescriptions (such as warnings and advice from the pharmacist). This can encourage patients to be more aware of changes in their prescriptions.
[0070] Figure 24 is a schematic diagram showing an example of the documents (related documents) provided to the patient. The related documents shown in Figure 24 are given to patients primarily for the purpose of allowing them to easily jot down any concerns they may have by posting them in easily visible places such as on the walls or refrigerator at home, and to bring them with them on their next visit to the pharmacy. As shown in Figure 24, among the documents provided to the patient, the designated related documents include information about the patient's schedule, such as the medication schedule explained by the pharmacist to the patient, the appointment schedule, and the patient's appointments, as shown on the display screen exemplified in Figure 16. In addition, for each day in the schedule, there are check boxes for taking medication in the morning, at noon, in the evening, and before bedtime.
[0071] Furthermore, in the designated related documents, the timeframe below the schedule column shows the approximate timing for taking medication throughout the day. Specifically, in the example shown in Figure 24, 7:00 AM, 1:00 PM, and 7:00 PM are indicated as the approximate timings for taking medication. Furthermore, below the timeline indicating the recommended timing for medication, there is a section for patients to make notes about anything they are concerned about, as well as images such as photographs of medications that require special attention when taking them. Furthermore, the bottom section of the designated related document shown in Figure 24 contains a message from the pharmacist to the patient and contact information for the dispensing pharmacy.
[0072] As described above, in the information processing system 1 according to this embodiment, when a pharmacist interacts with a patient in a dispensing pharmacy, the system displays information about the medication while displaying a predetermined profile of the pharmacist, thereby stimulating the patient's interest in and sense of familiarity with the pharmacist, and supporting smoother interaction. Furthermore, in Information Processing System 1, when a pharmacist explains information about medication (such as changes in prescribed medication) to a patient, the system issues a medication information document (medication information) that reflects the content of that explanation, allowing patients to more easily refer to the pharmacist's explanation when taking their medication. Furthermore, the information processing system 1 can present information (such as a schedule) in a format that is easy for patients to understand, such as how to take prescribed medications, based on explanations given by the pharmacist to the patient, thereby supporting the patient in taking their medication appropriately. Therefore, according to the information processing system 1 of this embodiment, it is possible to more appropriately support communication between pharmacists and patients.
[0073] [Example 1] In the above-described embodiment, when the print data generation unit 158 generates print data for the provided document, it may also include images explaining the usage of the drugs included in the current prescription in the drug information. For example, if it is an oral medication, a pictogram of taking the medication by mouth can be printed on the medication information sheet; if it is a transdermal patch, a pictogram of applying the medication to the body can be printed on the information sheet; if it is a suppository, a pictogram of inserting the medication anally can be printed on the information sheet; and if it is a topical medication, a pictogram of applying the medication to the body can be printed on the information sheet. This can prevent patients from using medication incorrectly.
[0074] [Differentiation 2] In the above-described embodiment, when displaying the prescribed medication on the display screen of the pharmacist's terminal 30, or when printing it on the medication information sheet, the order in which the prescribed medications are displayed or printed may be automatically set according to predetermined conditions. For example, the primary medication prescribed by the prescribing physician can be displayed at the top, while less important medications, such as auxiliary medications, can be displayed at the bottom. As an example, medication prescribed to relieve headaches can be displayed at the top, and medications to mitigate side effects of that medication (such as medications to protect the gastric mucosa to reduce stomach irritation) can be displayed at the bottom. Furthermore, if, for example, medications are taken at different times of the day (morning, noon, and night), they can be displayed in order from top to bottom according to the timing of administration.
[0075] [Difference 3] In the embodiments described above, the provision of documents was explained using the example of providing documents to a patient, but it is not limited to this. That is, in addition to the patient, the recipients of the provision of documents can be various entities that may refer to the patient's prescription details, such as the patient's family, caregivers (certified care workers, etc.), and nurses. In this case, the content of the information presented in the provision documents (difficulty level, granularity, etc.) can be changed according to the knowledge of the provider receiving the documents. Furthermore, it is possible to designate different types of documents, such as drug information documents and designated related documents, for different target audiences. For example, the content of the documents can be generated assuming that drug information documents are provided to the patient's caregiver and designated related documents are provided to the patient. This allows for the generation of documents (drug information or related documents) with content appropriate to the purpose, depending on the recipient of the documents.
[0076] In the embodiments and modifications described above, the documents provided to the patient were described as being in the form of a predetermined document, such as a revised medication information sheet or related documents, but the invention is not limited to these. For example, the documents may be provided to the patient in the form of a medication bag. That is, in this embodiment, the print data generated by the print data generation unit 158 can be printed on various printable media, such as medication bags or medication information sheets, and provided to the patient. The material of the printable media can be any type, such as paper, vinyl, or electronic paper. It is also possible to divide the print data into multiple media for printing. For example, it is possible to constitute a single medium with a medication information document printed with the data of the current prescription and a sticker (such as a sticker printed with past prescription data and the details of the prescription change) that is attached to the document to show the patient the change in prescription data as a whole. Furthermore, in addition to providing patients with printed information on various printable media, the information provided may also be provided to patients in the form of electronic data that can be viewed on electronic devices, such as electronic medication records, smartphone apps (such as notebook or schedule apps), or other electronic devices (for example, provided via communication or storage media).
[0077] Furthermore, in the embodiments and modifications described above, the document provided to the patient was described as showing the results of comparing the data of one past prescription with the data of the current prescription, such as the data of the previous prescription with the data of the current prescription, but it is not limited to this. For example, the document may show the results of comparing the data of multiple past prescriptions with the data of the current prescription. For example, if the data of the previous and the prescription before that is the same as the data of the current prescription, but there was a change in the data of the prescription three prescriptions ago, the document may show the results of comparing the data of the prescription three prescriptions ago, the data of the previous (or the prescription before that) prescription, and the data of the current prescription. This makes it possible to extract past prescription data that is useful to present to the patient, not just the previous prescription, and show the results of comparing it with the data of the current prescription. It is also possible to exclude the data from the current prescription from the data used for comparison. For example, it is possible to show a comparison between the data from the previous prescription and the prescription before that.
[0078] Furthermore, in the embodiments and modifications described above, when the display screen showing the contents of the changed medication information as shown in Figure 13 is displayed, in the initial state, drugs with the same ingredients (or efficacy) can be automatically associated and arranged between past prescription data and 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) will be associated and arranged. When a pharmacist moves the display position of any drug on the display screen showing the contents of the changed medication information displayed in this way, the system can automatically display pre-set content corresponding to the resulting position. For example, if any drug in the past prescription data is moved to a display position in the current prescription data where there is no corresponding item, a message indicating that the prescription for that drug has been discontinued ("Your medication is out of stock," etc.) can be displayed. Similarly, if any drug in the current prescription data is moved to a display position where there is no corresponding item in the past prescription data, a message indicating that the prescription for that drug has been added ("Your medication has been added," etc.) can be displayed. This makes it easier to show patients the changes to their prescribed medication.
[0079] As described above, the information processing system 1 according to this embodiment comprises a pharmacy computer 10, a server 20, and a 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 patient 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 change acquisition unit 155 and a change data transmission unit 156. The change acquisition unit 155 acquires information on changes in medications between the patient's past prescriptions and the current prescription, based on the prescription data transmitted from the pharmacy computer 10 and the patient's past prescription data corresponding to the said prescription data. The change data transmission unit 156 transmits the data on the changes to the drug information to the pharmacist's terminal 30. The pharmacist's terminal 30 includes a screen display unit 254 and an operation reception unit 251. The screen display unit 254 displays a screen for presenting the patient with information about medications related to the prescription, including the changed medication information, based on the changed medication information data 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 displayed information about the drug in response to the operation entered on the screen. With this configuration, the information processing system 1 can display information about medications related to prescriptions, including changes to medication information, when a pharmacist interacts with a patient in a pharmacy, and can also change the displayed information about medications in response to operations entered on the screen. Therefore, it is possible to better support communication between pharmacists and patients.
[0080] The pharmacist's terminal 30 is equipped with an operation content transmission unit 255. The operation content transmission unit 255 transmits the content of the operation received by the operation reception unit 251 to the server 20. This allows the server 20 to understand the content of the operations performed on the screen entered by the pharmacist's terminal 30.
[0081] The server 20 includes a print data generation unit 158 and a print data transmission unit 159. The print data generation unit 158 generates output data (print data or data for output to a storage medium, etc.) for the document to be provided to the patient, including the changed drug 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. The print control unit 56 outputs a document 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.) documents corresponding to the operations entered on the pharmacist's terminal 30.
[0082] Server 20 includes a profile screen data generation unit 153 and a profile screen data transmission unit 154. The profile screen data generation unit 153 generates pharmacist profile screen data to be presented to the patient, based on the pharmacist's profile data and the patient's attributes. The profile screen data transmission unit 154 transmits the profile screen data to the pharmacist's 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 pharmacists to display profile screens tailored to the patient's attributes, thereby stimulating patient interest in and familiarity with pharmacists, and supporting smoother communication between pharmacists and patients.
[0083] The profile screen data generation unit 153 selects data from the pharmacist's profile that is common with the patient's attributes, and generates data for the pharmacist's profile screen. This can more strongly stimulate patients' interest in and sense of familiarity with pharmacists.
[0084] The screen display unit 254 displays a schedule screen related to the patient, including the medication schedule included in the patient's prescription. The operation reception unit 251 receives the operations entered on the schedule screen. The operation content transmission unit 255 transmits the details of the operation on the schedule screen, which were received by the operation reception unit 251, to the server 20. This allows the server 20 to generate patient schedule data and print data based on the information entered into the patient's schedule.
[0085] Furthermore, the present invention is not limited to the embodiments described above, and any modifications, improvements, etc., that can achieve the objectives of the present invention are included within the scope of the present invention. For example, in the above-described embodiment, the pharmacy computer 10 may not have a prescription DB 71 or a patient attribute DB 72, and the server 20 may manage the data collectively. In this case, the pharmacy computer 10 can perform the same processing as in the above-described embodiment by sequentially sending and receiving data with the server 20 and using the data stored in the server 20's prescription DB 172 or patient attribute DB 173. Furthermore, in addition to being composed of the devices described in the above-described embodiments, the information processing system 1 according to the present invention can also be configured by integrating the functions of multiple devices described in the above-described embodiments into a single device, or by distributing the functions of a single device across multiple devices.
[0086] The series of processes described above can be executed by hardware or by software. In other words, the functional configuration in the above-described embodiment is merely illustrative and not particularly limited. That is, it is sufficient that any computer constituting the information processing system 1 is equipped with a function that can execute the series of processes described above as a whole, and the type of functional block used to realize this function is not limited to the examples shown. Furthermore, a single functional block may consist of hardware alone, software alone, or a combination of both.
[0087] Furthermore, the recording medium containing the program for executing the series of processes described above consists not only of removable media distributed separately from the main unit to the user to provide the program, but also of recording media provided to the user in a state where they are pre-installed in the main unit.
[0088] Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above. Furthermore, the effects described in these embodiments are merely a list of the most preferred effects arising from the present invention, and the effects of the present invention are not limited to those described in these 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 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 usage database, 176 Change drug information database, 177 Schedule database, 251 811 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 unit, 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 for managing data used in a pharmacy and a terminal device for displaying information presented to patients in a pharmacy, The aforementioned information processing device is A prescription data acquisition means for acquiring the prescription data of the aforementioned patient, A patient data storage means for storing patient data including the patient's prescription data and the patient's daily life schedule data, A change acquisition means that acquires data on changes in medication information regarding the medications that have been changed between the patient's past prescriptions and the current prescription, based on the data of the said prescription and the data of the patient's past prescriptions corresponding to the said prescription. A schedule data generation means generates schedule information data representing the patient's schedule by associating the aforementioned changes in medication information with the patient's daily schedule, A data output means for outputting the data of the changed drug information and the data of the schedule information to the terminal device or output device, An information processing system characterized by comprising the following features.
2. The aforementioned terminal device is A display means that displays the changed drug information output from the information processing device and the schedule information on a display screen, An operation receiving means for receiving operations entered on the aforementioned display screen, Equipped with, The data output means of the information processing device is The information processing system according to claim 1, characterized in that it generates output data for a document to be provided to the patient, including the changed drug information and the schedule information, based on the content of the operation received by the operation receiving means.
3. The information processing system according to claim 1 or 2, characterized in that the data output means outputs together information on prescribed drugs and changes to medications based on the prescription data, the patient's schedule information, and a medication schedule corresponding to the prescription data, which is represented in association with the patient's schedule.
4. The aforementioned information processing device is The pharmacist who communicates with the patient is provided with a profile information generation means for generating profile information data of the pharmacist to be presented to the patient. The data output means is The information processing system according to claim 2, characterized in that the output data includes the pharmacist's profile information.
5. The information processing system according to claim 4, characterized in that the profile information generation means generates profile information of the pharmacist who communicates with the patient, based on the pharmacist's attributes that are common to the patient.
6. An information processing device that constitutes an information processing system including an information processing device for managing data used in a pharmacy and a terminal device for displaying information presented to patients in a pharmacy, A prescription data acquisition means for acquiring the prescription data of the aforementioned patient, A patient data storage means for storing patient data including the patient's prescription data and the patient's daily life schedule data, A change acquisition means that acquires data on changes in medication information regarding the medications that have been changed between the patient's past prescriptions and the current prescription, based on the data of the said prescription and the data of the patient's past prescriptions corresponding to the said prescription. A schedule data generation means generates schedule information data representing the patient's schedule by associating the aforementioned changes in medication information with the patient's daily schedule, A data output means for outputting the data of the changed drug information and the data of the schedule information to the terminal device or output device, An information processing device characterized by comprising:
7. An information processing method performed by an information processing system including an information processing device for managing data used in a pharmacy and a terminal device for displaying information presented to patients in a pharmacy, The aforementioned information processing device A prescription data acquisition step to acquire the prescription data of the aforementioned patient, A patient data storage step includes storing patient data, which includes the patient's prescription data and the patient's daily life schedule data. A change acquisition step involves acquiring data on changes in medication information regarding the medications that have been changed between the patient's past prescriptions and the current prescription, based on the data of the said prescription and the data of the patient's past prescriptions corresponding to the said prescription. A schedule data generation step generates schedule information data representing the patient's schedule by associating the aforementioned changes in medication information with the patient's daily schedule, A data output step of outputting the data of the changed drug information and the data of the schedule information to the terminal device or output device, An information processing method characterized by including
8. In an information processing system that includes an information processing device for managing data used in a pharmacy and a terminal device for displaying information presented to patients in the pharmacy, the computer constituting the information processing device includes: A prescription data acquisition function that acquires prescription data for the aforementioned patient, A patient data storage function that stores patient data including the patient's prescription data and the patient's daily life schedule data, A change acquisition function that acquires data on changes in medications between the patient's past prescriptions and the current prescription, based on the data of the said prescription and the data of the patient's past prescriptions corresponding to the said prescription. A schedule data generation function generates schedule information data representing the patient's schedule by associating the aforementioned changes in medication information with the patient's daily schedule, A data output function that outputs the data of the changed drug information and the data of the schedule information to the terminal device or output device, A program characterized by its ability to achieve this.
Citation Information
Patent Citations
Medication related information output device, analysis server, medication related information output system, operation method of medication related information output device, operation program of medication related information output device, operation method of analysis server, and operation program of analysis server
JP2016122253A