Information processing device, program, and information processing method

Abstract

To reduce the burden on medical institutions when provision of prescription and administration guidance to pharmacies are done online.SOLUTION: An information processing device for assisting in handling of prescriptions of medical institutions is provided, comprising means of receiving a prescription image and designation of a destination pharmacy from a patient, means of receiving an approval instruction of a medical institution user for the prescription image, and means of transmitting the prescription image corresponding to the approval instruction to the destination pharmacy.SELECTED DRAWING: Figure 3

Description

[Technical field]

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

[0002] Generally, in order for a patient to receive medicines corresponding to a prescription issued by a medical institution, the patient visits a pharmacy, presents the prescription to the pharmacy, is provided with the medicines dispensed by a pharmacist, and receives medication instructions from the pharmacist. In other words, the presentation of the prescription to the pharmacy and medication instructions are conducted face-to-face. This is called the principle of face-to-face medication instructions.

[0003] In recent years, regulatory reforms have been underway to allow pharmacies to provide online medication instructions when providing prescription drugs. This is called online medication instructions, and it is expected to become more widespread.

[0004] For example, Patent Document 1 discloses a technology for pharmacist-user support in which specific medical information is collected and provided accurately and quickly to the extent required by the pharmacist without imposing a burden on the pharmacist, allowing the pharmacist to utilize their professional skills and provide accurate and simple guidance and advice specific to the user based on prescribed drug information. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2016-212829 A Summary of the Invention [Problem to be solved by the invention]

[0006] On the other hand, when implementing online medication instruction, patients do not visit pharmacies, so prescriptions must be submitted without going to the pharmacy. Currently, when implementing online medication instruction, prescriptions are submitted to pharmacies by the prescribing medical institution, not the patient, sending a copy by fax or digital to the pharmacy of the patient's choice, and the original is required to be sent at a later date. In other words, when implementing online medication instruction, medical institutions must not only issue prescriptions, but also send them to pharmacies. In order to popularize online medication instruction, it is important to reduce the burden on medical institutions of submitting prescription information to pharmacies, which is an additional burden on medical institutions.

[0007] Patent Document 1 focuses on supporting pharmacists, but does not focus on supporting medical institution users (e.g., doctors and medical institution staff). Therefore, a burden is placed on medical institutions when providing prescriptions to pharmacies and providing medication instructions online.

[0008] An object of the present invention is to reduce the burden on medical institutions when providing prescriptions to pharmacies and providing medication instructions online. [Means for solving the problem]

[0009] One aspect of the present invention is An information processing device that supports medical institutions in handling prescriptions, A means for receiving a prescription image and a destination pharmacy from a patient is provided, means for receiving an instruction of approval of the prescription image from a medical institution user; means for transmitting a prescription image corresponding to the approval instruction to the destination pharmacy; It is an information processing device. [Brief description of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a functional block diagram of the information processing system of FIG. 1. [Diagram 3] FIG. 1 is an explanatory diagram of an overview of the present embodiment. [Figure 4] FIG. 2 is a diagram showing a data structure of a medical institution database according to the present embodiment. [Diagram 5] 3 is a diagram showing a data structure of a pharmacy database according to the present embodiment. FIG. [Figure 6] A diagram showing the data structure of a medical institution prescription database in this embodiment. [Figure 7] 2 is a diagram showing a data structure of a pharmacy prescription database of the present embodiment. FIG. [Figure 8] FIG. 2 is a sequence diagram of a prescription registration process according to the present embodiment. [Figure 9] 9A to 9C are diagrams showing examples of screens displayed in the information processing of FIG. 8. [Figure 10] FIG. 2 is a sequence diagram of a prescription approval process according to the present embodiment. [Figure 11] 11A and 11B are diagrams showing examples of screens displayed in the information processing of FIG. 10. [Figure 12] FIG. 4 is a sequence diagram of a medication instruction process according to the present embodiment. [Figure 13] 13 is a diagram showing an example of a screen displayed in the information processing of FIG. 12. [Figure 14] FIG. 13 is a sequence diagram of a process for changing a delivery destination pharmacy in Modification 1. [Figure 15] A diagram showing the data structure of a pharmacy prescription database in the second modified example. [Figure 16] FIG. 11 is a sequence diagram of the prescription transmission process of the second modified example. [Figure 17] 17A and 17B are diagrams showing examples of screens displayed in the information processing of FIG. 16. [Figure 18] FIG. 11 is a sequence diagram of a prescription status change process according to the second modified example. [Figure 19] 19 is a diagram showing an example of a screen displayed in the information processing of FIG. 18. [Figure 20] 19 is a diagram showing an example of a screen displayed in the information processing of FIG. 18. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and the repeated description will be omitted.

[0012] (1) Information Processing System Configuration The configuration of the information processing system will be described below. Fig. 1 is a block diagram showing the configuration of the information processing system of this embodiment. Fig. 2 is a functional block diagram of the information processing system of Fig. 1.

[0013] As shown in FIG. 1, the information processing system 1 includes a medical institution client device 10, a patient client device 20, a server 30, and a pharmacy client device 40. The medical institution client device 10, the patient client device 20, the server 30, and the pharmacy client device 40 are connected via a network (eg, the Internet or an intranet) NW.

[0014] The medical institution client device 10 is a computer (an example of an "information processing device") that transmits a request to the server 30. The medical institution client device 10 is used by a user (hereinafter referred to as a "medical institution user") of a medical institution (e.g., a hospital). The medical institution user includes, for example, medical professionals (for example, doctors and pharmacists) belonging to a hospital, as well as medical staff. The medical institution client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0015] The patient client device 20 is a computer (an example of an "information processing device") that transmits a request to the server 30. The patient client device 20 is used by a patient user. The patient client device 20 is, for example, a smartphone, a tablet terminal, a dedicated terminal installed in a medical institution, or a personal computer.

[0016] The pharmacy client device 40 is a computer (an example of an "information processing device") that transmits requests to the server 30. The pharmacy client device 40 is used by users of the pharmacy (hereinafter referred to as "pharmacy users"). The pharmacy users include, for example, pharmacists and pharmacy staff who belong to the pharmacy. The pharmacy client device 40 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0017] The server 30 provides a service to support the handling of prescriptions at medical institutions. The server 30 is a computer (an example of an "information processing device") that provides a response to a request transmitted from the medical institution client device 10, the patient client device 20, or the pharmacy client device 40 to the medical institution client device 10, the patient client device 20, or the pharmacy client device 40. The server 30 is, for example, a web server.

[0018] (1-1) Configuration of medical institution client device The configuration of the medical institution client device 10 will be described.

[0019] As shown in FIG. 2, the medical institution client device 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14.

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

[0021] The programs include, for example, the following programs: ·OS (Operating System) programs · Programs for applications that process information (e.g. web browsers)

[0022] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0023] The processor 12 is configured to realize the functions of the medical institution client device 10 by starting a program stored in the storage device 11. The processor 12 is, for example, a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0024] The input / output interface 13 is configured to obtain user instructions from an input device connected to the medical institution client device 10 , and to output information to an output device connected to the medical institution client device 10 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0025] The communication interface 14 is configured to control communications between the medical institution client device 10 and the server 30 .

[0026] (1-2) Configuration of patient client device The configuration of the patient client device 20 will now be described.

[0027] As shown in FIG. 2, the patient client device 20 includes a memory device 21, a processor 22, an input / output interface 23, and a communication interface 24.

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

[0029] The programs include, for example, the following programs: -OS programs · Programs for applications that process information (e.g. web browsers)

[0030] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0031] The processor 22 is configured to implement the functions of the patient client device 20 by running the programs stored in the storage device 21. The processor 22 is, for example, a CPU, an ASIC, an FPGA, or a combination thereof.

[0032] The input / output interface 23 is configured to obtain user instructions from input devices connected to the patient client device 20 and to output information to output devices connected to the patient client device 20 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0033] The communications interface 24 is configured to control communications between the patient client device 20 and the server 30 .

[0034] (1-1) Configuration of medical institution client device The configuration of the pharmacy client device 40 will be described.

[0035] As shown in FIG. 2, pharmacy client device 40 includes a memory device 41, a processor 42, an input / output interface 43, and a communication interface 44.

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

[0037] The programs include, for example, the following programs: -OS programs · Programs for applications that process information (e.g. web browsers)

[0038] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0039] The processor 42 is configured to realize the functions of the pharmacy client device 40 by running a program stored in the storage device 41. The processor 42 is, for example, a CPU, an ASIC, an FPGA, or a combination thereof.

[0040] Input / output interface 43 is configured to obtain user instructions from an input device connected to pharmacy client device 40 and to output information to an output device connected to pharmacy client device 40 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0041] Communications interface 44 is configured to control communications between pharmacy client device 40 and server 30 .

[0042] (1-4) Server configuration The configuration of the server 30 will now be described.

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

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

[0045] The programs include, for example, the following programs: -OS programs Application programs that perform information processing

[0046] The data includes, for example, the following data: Databases referenced in information processing Results of information processing

[0047] The processor 32 is configured to realize the functions of the server 30 by running a program stored in the storage device 31. The processor 32 is, for example, a CPU, an ASIC, an FPGA, or a combination of these.

[0048] The input / output interface 33 is configured to receive user instructions from an input device connected to the server 30 , and to output information to an output device connected to the server 30 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0049] The communication interface 34 is configured to control communications between the server 30 and the medical institution client device 10 .

[0050] (2) Overview of the embodiment An overview of this embodiment will be described below with reference to Fig. 3, which is an explanatory diagram of the overview of this embodiment.

[0051] As shown in FIG. 3, the patient-user uses the patient client device 20 to transmit prescription image information to the server 30 .

[0052] The medical institution user uses the medical institution client device 10 to approve the contents of the prescription image information transmitted to the server 30 (that is, the contents of the prescription).

[0053] The server 30 transmits the prescription image information approved by the medical institution user to the pharmacy client device 40 .

[0054] The pharmacy user dispenses the medicine corresponding to the prescription image information transmitted to the pharmacy client device 40 and provides online medication instructions.

[0055] According to this embodiment, the medical institution user can create an environment in which the pharmacy user can dispense medicine and provide online medication instructions simply by approving the prescription image information sent by the patient user to the server 30. As a result, the burden on the medical institution when providing prescriptions to pharmacies and providing online medication instructions can be reduced.

[0056] (3) Database The databases of this embodiment are stored in the storage device 31.

[0057] (3-1) Medical institution database The medical institution database of this embodiment will be described below with reference to Fig. 4, which is a diagram showing the data structure of the medical institution database of this embodiment.

[0058] Medical institution information is stored in the medical institution database in Fig. 4. The medical institution information is information relating to medical institutions. The medical institution database includes a "medical institution ID" field, a "medical institution name" field, and a "medical institution contact" field. Each field is associated with the other fields.

[0059] The "medical institution ID" field stores medical institution identification information. The medical institution identification information is information for identifying a medical institution.

[0060] The "medical institution name" field stores medical institution name information. The medical institution name information is information about the name of the medical institution.

[0061] The "medical institution contact" field stores medical institution contact information. The medical institution contact information is information relating to the contact information of a medical institution.

[0062] (3-2) Pharmacy database The pharmacy database of this embodiment will be described below with reference to Fig. 5, which shows the data structure of the pharmacy database of this embodiment.

[0063] Pharmacy information is stored in the pharmacy database of Fig. 5. The pharmacy information is information related to pharmacies. The pharmacy database includes a "pharmacy ID" field, a "pharmacy name" field, and a "pharmacy contact" field. Each field is associated with the other fields.

[0064] The "pharmacy ID" field stores pharmacy identification information. The pharmacy identification information is information for identifying a pharmacy.

[0065] The "pharmacy name" field stores pharmacy name information. The pharmacy name information is information about the name of the pharmacy.

[0066] The "Pharmacy Contact" field stores pharmacy contact information. The pharmacy contact information is information about how to contact a pharmacy.

[0067] (3-3) Medical institution prescription database The medical institution prescription database of this embodiment will be described below. Fig. 6 is a diagram showing the data structure of the medical institution prescription database of this embodiment.

[0068] Prescription information is stored in the medical institution prescription database of Fig. 6. Prescription information is information related to prescriptions. The medical institution prescription database includes a "prescription ID" field, a "prescription transmission date and time" field, a "delivery pharmacy ID" field, a "desired consultation date and time" field, a "prescription image" field, a "generic" field, a "patient name" field, a "patient contact" field, and a "medical institution prescription status" field. Each field is associated with the others. The medical institution prescription database is associated with the medical institution identification information of the medical institution that issued the prescription.

[0069] The "Prescription ID" field stores prescription identification information. The prescription identification information is information that identifies a prescription.

[0070] The "prescription transmission date and time" field stores prescription transmission date and time information. The prescription transmission date and time information is information about the date and time when the patient transmitted the prescription image to the medical institution.

[0071] The "destination pharmacy ID" field stores destination pharmacy identification information. The destination pharmacy identification information is information for identifying the pharmacy to which the prescription should be sent (hereinafter referred to as the "destination pharmacy").

[0072] The "desired instruction date and time" field stores desired instruction date and time information. The desired instruction date and time information is information related to the desired instruction date and time. The desired instruction date and time is the date and time when the patient desires to receive medication instructions from a pharmacist.

[0073] The "Prescription Image" field stores prescription image information. The prescription image information is information related to a prescription image.

[0074] The "generic" field stores generic information. The generic information is information on whether or not the patient desires a generic drug.

[0075] The "patient name" field stores patient name information. The patient name information is information about the name of the patient for whom the prescription is written.

[0076] The "Patient Contact" field stores patient contact information. The patient contact information is information about the patient's contact information. The patient contact information includes, for example, at least one of the following: ·mobile number ·email address Social network service accounts

[0077] The "medical institution prescription status" field stores medical institution prescription status information. The medical institution prescription status information is information about the status of a prescription at a medical institution. Provider prescription status includes, for example: "Waiting for approval" means that the patient has sent an image of the prescription to the medical institution, but the medical institution has not yet approved the prescription. "Data sent" This means that the prescription has been approved by the medical institution, but the pharmacy has not yet dispensed the medication. "Original prescription sent" means that the medical institution has completed sending the original prescription to the pharmacy, but the original prescription has not yet arrived at the pharmacy.

[0078] (3-4) Pharmacy prescription database The pharmacy prescription database of this embodiment will be described below. Fig. 7 is a diagram showing the data structure of the pharmacy prescription database of this embodiment.

[0079] The pharmacy prescription database of FIG. 7 stores prescription information. The pharmacy prescription database includes a "prescription ID" field, a "prescription received date and time" field, a "sender medical institution ID" field, a "desired instruction date and time" field, a "prescription image" field, a "generic" field, a "patient name" field, a "patient contact" field, and a "pharmacy prescription status" field. Each field is associated with the others. The pharmacy prescription database is associated with pharmacy identification information for the pharmacy that received the prescription.

[0080] The "Prescription ID" field stores prescription identification information.

[0081] The "prescription receiving date and time" field stores prescription receiving date and time information. The prescription receiving date and time information is information about the date and time when the prescription was received from the medical institution.

[0082] The "sender medical institution ID" field stores sender medical institution identification information. The sender medical institution identification information is information for identifying the medical institution that sent the prescription (hereinafter referred to as the "sender medical institution").

[0083] The "desired lesson date and time" field stores information on the desired lesson date and time.

[0084] The "Prescription Image" field stores prescription image information.

[0085] The "Generic" field stores generic information.

[0086] The "patient name" field stores patient name information.

[0087] The "Patient Contact" field stores patient contact information.

[0088] The "pharmacy prescription status" field stores pharmacy prescription status information. The pharmacy prescription status information is information about the status of the prescription at the pharmacy. Pharmacy prescription statuses include, for example: · "New reception"··· This means that receipt of prescription information (i.e., approval of the prescription by the medical institution) has been completed, but dispensing by the pharmacy has not been completed. "Dispensed": This means that the pharmacy has completed dispensing the medication, but has not yet completed medication instructions. "Medication instructions completed" This means that the pharmacy has completed medication instructions, but has not yet completed arrangements for delivery of the medication. "Delivery arrangements completed" This means that the pharmacy has completed the arrangements for delivery of the medication, but the medication has not yet arrived at the patient. "Delivery confirmed" means that the medicine has arrived at the patient, but the medical institution has not yet completed sending the original prescription to the pharmacy.

[0089] (4) Information processing The information processing of this embodiment will be described.

[0090] (4-1) Prescription registration processing The prescription registration process of this embodiment will be described. Fig. 8 is a sequence diagram of the prescription registration process of this embodiment. Fig. 9 is a diagram showing an example of a screen displayed in the information processing of Fig. 8.

[0091] 8 is triggered, for example, by access to a site dedicated to a medical institution that is preset in the patient client device 20. Medical institution identification information is assigned to the site dedicated to a medical institution.

[0092] As shown in FIG. 8, the patient client device 20 receives a prescription image (S1120). Specifically, the processor 22 displays a screen P1120 (FIG. 9) on the display.

[0093] The screen P1120 includes an operation object B11200 and field objects F11200 to F11203.

[0094] A field object F11200 is an object that receives a user instruction for specifying a medication instruction format (for example, face-to-face medication instruction or online medication instruction).

[0095] A field object F11201 is an object that receives a user instruction to specify a destination pharmacy.

[0096] The field object F11202 is an object that receives a user instruction to specify patient name information and patient contact information.

[0097] The field object F11203 is an object that receives a user instruction for specifying generic information.

[0098] The operation object B11200 is an object that receives a user instruction for confirming the user instructions given to the field objects F11200 to F11203. When "online medication instructions" is specified in field object F11200 and operation object B11200 is operated, the processor 22 stores the contents of the user instructions given to field objects F11200 to F11203 in the storage device 21 and displays screen P1121 (Figure 9) on the display.

[0099] The screen P1121 includes a display object A11210 and an operation object B11210.

[0100] Display object A11210 is an object that displays a prescription image captured by a camera (not shown).

[0101] The operation object B 11210 is an object that receives a user instruction for finalizing the prescription image displayed on the display object A 11210.

[0102] After step S1120, the patient client device 20 executes a prescription registration request (S1121). Specifically, when the patient user operates the operation object B11210, the processor 22 stores the prescription image information corresponding to the user instruction given to the display object A11210 in the storage device 21, and displays the screen P1122 (FIG. 9) on the display.

[0103] The screen P1122 includes an operation object B11220 and a field object F11220.

[0104] A field object F11220 is an object that receives a user instruction to specify desired date and time for medication instruction.

[0105] The operation object B 11220 is an object that receives a user instruction for confirming a user instruction given to the field object F 11220. When the patient-user operates the operation object B11220, the processor 22 stores in the storage device 21 the contents of the user instruction given to the field object F11220.

[0106] The processor 22 transmits the prescription registration request data to the server 30. The prescription registration request data includes the following information: The prescription image information obtained in step S1120 Information corresponding to the user instructions obtained in steps S1120 to S1121

[0107] After step S1121, the server 30 executes prescription registration (S1130). Specifically, the processor 32 adds a new record to the medical institution prescription database (FIG. 6) associated with the medical institution identification information assigned to the medical institution dedicated site. The following information is stored in each field of the new record: "Prescription ID" field: New prescription identification information "Prescription transmission date and time" field: Information regarding the execution date and time of step S1121 "Destination pharmacy ID" field: Pharmacy identification information of the destination pharmacy included in the prescription registration request data "Desired date and time of instruction" field: Desired date and time of instruction included in the prescription registration request data "Prescription image" field: Prescription image information included in the prescription registration request data "Generic" field: Generic information included in the prescription registration request data "Patient name" field: Patient name information included in the prescription registration request data "Patient Contact" field: Patient contact information included in the prescription registration request data "Medical Institution Prescription Status" field: Medical institution prescription status information "Waiting for approval"

[0108] The processor 32 adds a new record to the pharmacy prescription database (FIG. 7) associated with the pharmacy identification information of the destination pharmacy. The following information is stored in each field of the new record: "Prescription ID" field: New prescription identification information "Prescription received date and time" field: Information regarding the execution date and time of step S1121 "Sender medical institution ID" field: Medical institution identification information of the sender medical institution included in the prescription registration request data "Desired date and time of instruction" field: Instruction request information included in the prescription registration request data "Prescription image" field: Prescription image information included in the prescription registration request data "Generic" field: Generic information included in the prescription registration request data "Patient name" field: Patient name information included in the prescription registration request data "Patient Contact" field: Patient contact information included in the prescription registration request data "Pharmacy prescription status" field: Pharmacy prescription status information "New receipt"

[0109] After step S1130, the server 30 executes a notification of completion of the prescription registration (S1131). Specifically, the processor 32 sends a notification to the patient client device 20 that the prescription registration is complete.

[0110] After step S1131, the patient client device 20 executes presentation of a notification of completion of prescription registration (S1110). Specifically, the processor 22 displays screen P1123 (FIG. 9) on the display.

[0111] A message indicating that prescription registration has been completed and a message urging the user to submit the original prescription to a medical institution are displayed on the screen P1123.

[0112] (4-2) Prescription approval processing The prescription registration process of this embodiment will be described. Fig. 10 is a sequence diagram of the prescription approval process of this embodiment. Fig. 11 is a diagram showing an example of a screen displayed in the information process of Fig. 10.

[0113] The process of FIG. 10 is triggered, for example, by a medical institution user successfully logging in to the service of the server 30 via the medical institution client device 10 using medical institution identification information.

[0114] As shown in FIG. 10, the medical institution client device 10 executes a prescription list request (S1210). Specifically, the processor 12 sends prescription list request data to the server 30. The prescription list request data includes the medical institution identification information used for login.

[0115] After step S1210, the server 30 extracts a prescription list (S1230). Specifically, the processor 32 extracts records from the medical institution prescription database (FIG. 6) associated with the medical institution identification information included in the prescription list request data of step S1210.

[0116] After step S1230, the server 30 executes a prescription list response (S1231). Specifically, the processor 32 transmits the prescription list response data to the medical institution client device 10. The prescription list response data includes, for example, the prescription information of the record identified in step S1230.

[0117] After step S1231, the medical institution client device 10 executes presentation of a prescription list (S1211). Specifically, the processor 12 displays screen P1210 (FIG. 11) on the display.

[0118] Screen P1210 includes an “Medical institution prescription status” object, a “Prescription sending date and time” object, a “Patient name” object, a “Patient contact” object, a “Destination pharmacy name” object, and a “Desired date and time for online medication instruction” object.

[0119] The "medical institution prescription status" object displays medical institution prescription status information. The "medical institution prescription status" object is an operation object B12100. The operation object B12100 is an object that receives a user instruction to change the medical institution prescription status information.

[0120] The "prescription sending date and time" object displays prescription sending date and time information.

[0121] The "Patient Name" object displays patient name information.

[0122] The "Patient Contact" object displays patient contact information.

[0123] The "destination pharmacy name" object displays destination pharmacy name information. The "destination pharmacy name" object is an operation object B12101. The operation object B12101 is an object that receives a user instruction to change the destination pharmacy.

[0124] The "online medication instruction desired date and time" object displays information on the online medication instruction desired date and time.

[0125] After step S1211, the medical institution client device 10 executes an approval request (S1212). Specifically, when the medical institution user operates the operation object B12100 having the medical institution prescription status information “waiting for approval”, the processor 12 transmits approval request data to the server 30. The approval request data includes prescription identification information (that is, prescription identification information of the prescription to be approved) assigned to the operation object B12100 operated by the medical institution user.

[0126] After step S1212, the server 30 executes transmission of prescription data (S1232). Specifically, the processor 32 refers to the medical institution prescription database (FIG. 6) to identify a record (hereinafter referred to as a "transmission target record") that corresponds to the prescription identification information included in the approval request data. The processor 32 identifies the destination pharmacy identification information of the record to be sent. Processor 32 refers to the pharmacy database (FIG. 5) to identify pharmacy contact information associated with the destination pharmacy information. The processor 32 transmits the prescription image information contained in the transmission target record to the contact information indicated by the pharmacy contact information.

[0127] After step S1232, the server 30 executes updating of the database (S1233). Specifically, the processor 32 changes the medical institution prescription status information of the record to be sent to "data sent."

[0128] (4-3) Medication Instructions The medication instruction process of this embodiment will be described below. Fig. 12 is a sequence diagram of the medication instruction process of this embodiment. Fig. 13 is a diagram showing an example of a screen displayed in the information processing of Fig. 12.

[0129] The process of FIG. 12 is triggered, for example, by a pharmacy user successfully logging in to the service of the server 30 via the pharmacy client device 40 using pharmacy identification information.

[0130] As shown in FIG. 12, the pharmacy client device 40 executes a prescription list request (S1340). Specifically, the processor 42 transmits prescription list request data to the server 30 . The prescription list request data includes the pharmacy identification information used for login.

[0131] After step S1340, the server 30 extracts a prescription list (S1330). Specifically, processor 32 identifies the record in the pharmacy-care prescription database (FIG. 7) associated with the pharmacy identification information used to log in.

[0132] After step S1330, the server 30 executes a prescription list response (S1331). Specifically, the processor 32 sends the prescription list response data to the pharmacy client device 40 . The prescription list response data includes, for example, the prescription information of the record identified in step S1330.

[0133] After step S1331, the pharmacy client device 40 executes presentation of a prescription list (S1341). Specifically, the processor 42 displays a screen P1340 (FIG. 13) on the display.

[0134] Screen P1340 includes a “Pharmacy prescription status” object, a “Prescription received date and time” object, a “Sender medical institution name” object, a “Patient name” object, a “Patient contact” object, and a “Desired date and time for online medication instruction” object.

[0135] The "pharmacy prescription status" object displays pharmacy prescription status information. The "pharmacy prescription status" object is an operation object B13400. The operation object B13400 is an object that receives a user instruction to change the pharmacy prescription status information.

[0136] The "prescription receiving date and time" object displays prescription receiving date and time information.

[0137] The "sender's medical institution name" object displays information about the name of the sender's medical institution.

[0138] The "Patient Name" object displays patient name information.

[0139] The "Patient Contact" object displays patient contact information.

[0140] The "online medication instruction desired date and time" object displays information on the online medication instruction desired date and time.

[0141] After step S1331, the pharmacy client device 40 executes a prescription status change request (S1342). Specifically, when a pharmacy user operates the operation object B13400 of a prescription for which the pharmacy prescription status should be changed after dispensing a drug and providing online medication instructions, the processor 42 transmits prescription status change request data to the server 30. The prescription status change request data includes, for example, the following information: Prescription identification information corresponding to the operation object B13400 operated by the pharmacy user

[0142] After step S1343, the server 30 executes updating of the database (S1332). Specifically, processor 32 refers to the pharmacy prescription database (FIG. 7) and stores "medication instructions completed" in the "pharmacy prescription status" field associated with the prescription identification information included in the prescription status change request data.

[0143] (5) Summary of the present embodiment According to this embodiment, there is provided an information processing device (e.g., server 30) that assists medical institutions in handling prescriptions, the information processing device having a means (S1130) for accepting a prescription image and a destination pharmacy designation from a patient, a means (S1232) for accepting an approval instruction from a medical institution user for the prescription image, and a means (S1232) for transmitting a prescription image corresponding to the approval instruction to the destination pharmacy. In this way, when the medical institution user gives the instruction of approval, the prescription image taken by the patient user is sent to the destination pharmacy. This reduces the burden on the medical institution when providing the prescription to the pharmacy and providing medication instructions online.

[0144] According to this embodiment, a means is provided for storing a prescription image and a prescription status in association with each other, and a means is provided for setting the status to "waiting for approval" when the prescription image is accepted, and the setting means may set the status to "data sent" when the prescription image is sent to the destination pharmacy. In this way, the status of a prescription changes depending on the execution of an action on the prescription, which allows the medical institution user to easily grasp the progress of the prescription.

[0145] According to this embodiment, when the medical institution sends the original of the prescription to the destination pharmacy, the status may be set to "original sent." In this way, the status of a prescription changes depending on the execution of an action on the prescription, which allows the medical institution user to easily grasp the progress of the prescription.

[0146] (6) Variations A modification of this embodiment will now be described.

[0147] (6-1) Variation 1 A first modified example of this embodiment will be described below. The first modified example is an example in which, when a pharmacy cannot accept dispensing, the delivery destination pharmacy is changed in response to an instruction from a medical institution user. FIG. 14 is a sequence diagram of the process of changing the delivery destination pharmacy in the first modification.

[0148] The trigger for the processing in Figure 14 is, for example, when a medical institution user successfully logs in to the service of the server 30 using medical institution identification information via the medical institution client device 10 after receiving a message from the destination pharmacy (hereinafter referred to as the "pharmacy to be changed") that "the prescription cannot be accepted."

[0149] As shown in FIG. 14, the medical institution client device 10 executes a prescription list request (S1210) in the same manner as in FIG. The server 30 executes extraction of a prescription list (S1230) and a prescription list response (S1231) in the same manner as in FIG. The medical institution client device 10 executes presentation of the prescription list (S1211) in the same manner as in FIG.

[0150] After step S1211, the medical institution client device 10 executes a change request (S1410). Specifically, when a medical institution user operates the operation object B12101 of the “Destination pharmacy name” object corresponding to the pharmacy to be changed on screen P1210 (Figure 11) and specifies a new destination pharmacy (hereinafter referred to as the “changed pharmacy”), the processor 12 sends destination pharmacy change request data to the server 30. The delivery pharmacy change request data includes the following information: Prescription identification information assigned to the operation object B12101 operated by the medical institution user (i.e., prescription identification information of the prescription to be changed) -Pharmacy identification information of the new pharmacy

[0151] After step S1410, the server 30 executes transmission of prescription data (S1430). Specifically, the processor 32 identifies a record (hereinafter referred to as a "record to be changed") that corresponds to the prescription identification information included in the change request data. Processor 32 references the pharmacy database (FIG. 5) to identify pharmacy contact information associated with the pharmacy identification information included in the change request data. The processor 32 sends the prescription image information contained in the record to be changed to the contact information indicated by the pharmacy contact information.

[0152] After step S1430, the server 30 executes updating of the database (S1431). Specifically, the processor 32 changes the destination pharmacy identification information of the record to be changed to the pharmacy identification information of the pharmacy after the change.

[0153] According to the first modification, even if the destination pharmacy designated by the patient cannot dispense medicine, the destination pharmacy can be changed by a simple operation of the medical institution user. This further reduces the burden on the medical institution when providing prescriptions to pharmacies and providing medication instructions online.

[0154] (6-2) Variation 2 A description will be given of Modification 2. Modification 2 is an example in which prescriptions for online medication instruction and prescriptions for face-to-face medication instruction are managed together.

[0155] (6-2-1) Pharmacy prescription database A description will be given of the pharmacy prescription database of the modified example 2. Fig. 15 is a diagram showing the data structure of the pharmacy prescription database of the modified example 2.

[0156] The pharmacy prescription database of FIG. 15 stores prescription information. The pharmacy prescription database includes a "prescription ID" field, a "prescription receiving date and time" field, a "sender medical institution ID" field, a "desired instruction date and time" field, a "prescription image" field, a "generic" field, a "patient name" field, a "patient contact" field, a "pharmacy prescription status" field, a "medication instruction format field", and a "desired receipt date and time" field. Each field is associated with the others. The pharmacy prescription database is associated with pharmacy identification information for the pharmacy that received the prescription.

[0157] The “Prescription ID” field, “Prescription received date and time” field, “Sending medical institution ID” field, “Desired consultation date and time” field, “Prescription image” field, “Generic” field, “Patient name” field, and “Patient contact” field are the same as in Figure 7.

[0158] The "pharmacy prescription status" field stores pharmacy prescription status information. The pharmacy prescription status information is information about the status of the prescription at the pharmacy. The pharmacy prescription status includes, for example, the following in addition to the pharmacy prescription status of this embodiment: · "New reception" · This means that the pharmacy has not yet completed medication instructions or provided the medication. "Received" means that the pharmacy has completed medication instructions and provision of the medication.

[0159] The "medication instruction format field" stores medication instruction format information. The medication instruction format information is information regarding the medication instruction format (online medication instruction or face-to-face medication instruction).

[0160] The "desired receipt date and time" field stores desired receipt date and time information. The desired receipt date and time information is information regarding the date and time when the patient desires to receive the medicine (hereinafter referred to as "desired receipt date and time").

[0161] (6-2-2) Prescription transmission process A description will be given of prescription transmission processing according to Modification 2. Fig. 16 is a sequence diagram of the prescription transmission processing according to Modification 2. Fig. 17 is a diagram showing an example of a screen displayed in the information processing of Fig. 16.

[0162] 16 is triggered, for example, by access to a site dedicated to a medical institution that is preset in the patient client device 20. Medical institution identification information is assigned to the site dedicated to a medical institution.

[0163] As shown in FIG. 16, the patient client device 20 receives a prescription image (S1120) in the same manner as in FIG.

[0164] After step S1120, the patient client device 20 executes a prescription transmission request (S2120). Specifically, when the patient user specifies "face-to-face medication instruction" in the field object F11200 and also operates the operation object B11210, the processor 22 displays the screen P2120 (FIG. 17) on the display.

[0165] The screen P2120 includes an operation object B21200 and a field object F21200.

[0166] The field object F21200 is an object that receives a user instruction for specifying desired receipt date and time information.

[0167] The operation object B21200 is an object that receives a user instruction for confirming a user instruction given to the field object F21200. When the patient-user operates the operation object B21200, the processor 22 stores in the storage device 21 the contents of the user instruction given to the field object F21200.

[0168] The processor 22 transmits the prescription transmission request data to the server 30. The prescription transmission request data includes the following information: The prescription image information obtained in step S1120 Information corresponding to the user instructions obtained in steps S1120 and S2120

[0169] After step S2120, the server 30 executes transmission of prescription data (S2130). Specifically, the processor 32 refers to the pharmacy database (FIG. 5) to identify pharmacy contact information associated with the pharmacy identification information of the destination pharmacy included in the prescription transmission request data. The processor 32 sends the prescription image information included in the prescription transmission request data to the contact information indicated by the pharmacy contact information.

[0170] After step S2130, the server 30 executes updating of the database (S2131). Specifically, the processor 32 adds a new record to the medical institution prescription database (FIG. 6) associated with the medical institution identification information assigned to the medical institution dedicated site. The following information is stored in each field of the new record: "Prescription ID" field: New prescription identification information "Prescription transmission date and time" field: Information regarding the execution date and time of step S2120 "Destination pharmacy ID" field: Pharmacy identification information of the destination pharmacy included in the prescription transmission request data "Desired receipt date and time" field: Desired receipt date and time information included in the prescription transmission request data "Prescription image" field: Prescription image information included in the prescription sending request data "Generic" field: Generic information included in the prescription transmission request data "Patient name" field: Patient name information included in the prescription transmission request data "Patient Contact" field: Patient contact information included in the prescription transmission request data "Medical Institution Prescription Status" field: NULL

[0171] The processor 32 adds a new record to the pharmacy prescription database (FIG. 15) associated with the pharmacy identification information of the destination pharmacy. The following information is stored in each field of the new record: "Prescription ID" field: New prescription identification information "Prescription received date and time" field: Information regarding the execution date and time of step S2130 "Sender medical institution ID" field: Medical institution identification information of the sender medical institution included in the prescription transmission request data "Desired date and time of instruction" field: NULL "Prescription image" field: Prescription image information included in the prescription sending request data "Generic" field: Generic information included in the prescription transmission request data "Patient name" field: Patient name information included in the prescription transmission request data "Patient Contact" field: Patient contact information included in the prescription transmission request data "Pharmacy prescription status" field: Pharmacy prescription status information "New receipt" "Desired receipt date and time" field: Desired receipt date and time information included in the prescription transmission request data

[0172] After step S2131, the server 30 executes a notification of completion of the prescription transmission (S2132). Specifically, a notification of completion of the prescription transmission is sent to the patient client device 20.

[0173] After step S2132, the patient client device 20 executes presentation of a notification of completion of the prescription transmission (S2120). Specifically, the processor 22 displays screen P2121 (FIG. 17) on the display.

[0174] Screen P2121 displays a message indicating that the prescription transmission has been completed.

[0175] (6-2-3) Prescription status change processing A prescription status change process of Modification 2 will be described. Fig. 18 is a sequence diagram of the prescription status change process of Modification 2. Fig. 19 is a diagram showing an example of a screen displayed in the information processing of Fig. 18. Fig. 20 is a diagram showing an example of a screen displayed in the information processing of Fig. 18.

[0176] The trigger for the process in FIG. 18 is, for example, at least one of the following: The pharmacy user successfully logs in to the server 30 service via the pharmacy client device 40 using the pharmacy identification information. The medical institution user has successfully logged in to the service of the server 30 using the medical institution identification information via the medical institution client device 10.

[0177] As shown in FIG. 18, the pharmacy client device 40 executes a prescription list request (S1340) in the same manner as in FIG.

[0178] The medical institution client device 10 executes a prescription list request (S2210). Specifically, the processor 12 sends prescription list request data to the server 30. The prescription list request data includes the medical institution identification information used for login.

[0179] After step S1340 or S2210, the server 30 extracts a prescription list (S2230). Specifically, the processor 32 identifies a record in the medical institution prescription database (FIG. 6) associated with the medical institution identification information used for login. Processor 32 identifies the record in the pharmacy prescription database (FIG. 7) associated with the pharmacy identification information used to log in.

[0180] After step S2230, the server 30 executes a prescription list response (S2231). Specifically, the processor 32 transmits prescription list response data to the pharmacy client device 40 and the medical institution client device 10. The prescription list response data transmitted to the pharmacy client device 40 includes, for example, the prescription information of the record in the pharmacy prescription database (FIG. 7) identified in step S2230. The prescription list response data transmitted to the medical institution client device 10 includes, for example, the prescription information of the record in the medical institution prescription database (FIG. 6) identified in step S2230.

[0181] After step S2231, the medical institution client device 10 executes presentation of a prescription list (S2211). Specifically, the processor 12 displays screen P2210 (FIG. 20) on the display.

[0182] Screen P2210 includes a "pharmacy prescription status" object, a "prescription receiving date and time" object, a "patient name" object, a "patient contact" object, a "destination pharmacy name" object, a "desired receipt date and time" object, and operation objects B22100 to B22101.

[0183] The operation objects B22100 to B22101 are also displayed on P1210 (FIG. 11). The operation object B22100 is an object that receives a user instruction for displaying prescription information of a patient who wishes to receive online medication instruction. When the operation object B22100 displayed on the screen P2210 is operated, the screen P1210 is displayed. The operation object B22101 is an object that receives a user instruction to display prescription information for a patient who wishes to receive face-to-face medication instruction. When the operation object B22101 displayed on the screen P1210 is operated, the screen P2210 is displayed.

[0184] The “pharmacy prescription status” object, “prescription received date and time” object, “sender medical institution ID” object, “patient name” object, and “patient contact” object are the same as those in FIG.

[0185] The "desired receipt date and time" object displays desired receipt date and time information.

[0186] After step S2231, the pharmacy client device 40 executes presentation of the prescription list (S2240). Specifically, the processor 42 displays a screen P2240 (FIG. 19) on the display.

[0187] Screen P2240 includes a "pharmacy prescription status" object, a "prescription receiving date and time" object, a "sender medical institution name" object, a "patient name" object, a "patient contact" object, a "desired receipt date and time" object, and operation objects B22400 to B22402.

[0188] The operation objects B22400 to B22401 are also displayed on P1340 (FIG. 13). The operation object B22400 is an object that accepts a user instruction for displaying prescription information for a patient who wishes to receive online medication instruction. When the operation object B22400 displayed on the screen P2240 is operated, the screen P1340 is displayed. The operation object B22401 is an object that receives a user instruction for displaying prescription information for a patient who wishes to receive face-to-face medication instruction. When the operation object B22400 displayed on the screen P1340 is operated, the screen P2240 is displayed.

[0189] The “pharmacy prescription status” object, “prescription received date and time” object, “sender medical institution name” object, “patient name” object, and “patient contact” object are the same as those in FIG. The "pharmacy prescription status" object is an operation object B 22402. The operation object B 22402 is an object that receives a user instruction to change the pharmacy prescription status information.

[0190] The "desired receipt date and time" object displays desired receipt date and time information.

[0191] After step S2240, the pharmacy client device 40 executes a prescription status change request (S2241). Specifically, when a pharmacy user operates the operation object B22402 of a prescription whose pharmacy prescription status should be changed after dispensing a drug and providing face-to-face medication instruction, the processor 42 transmits prescription status change request data to the server 30. The prescription status change request data includes, for example, the following information: Prescription identification information corresponding to the operation object B22402 operated by the pharmacy user

[0192] After step S2241, the server 30 executes updating of the database (S2232). Specifically, processor 32 refers to the pharmacy prescription database (FIG. 15) and stores "Received" in the "Pharmacy Prescription Status" field associated with the prescription identification information included in the prescription status change request data.

[0193] (6-3) Summary of Modification 2 According to the second modification, when the patient user photographs a prescription image, the patient user selects face-to-face medication instruction or online medication instruction on the common screen P1120 (S1120). If face-to-face medication instruction is selected, the server 30 transmits the prescription image to the destination pharmacy without receiving an approval instruction from the medical institution user (S2130). This allows the prescription to be easily sent to the pharmacy regardless of the medication instruction format.

[0194] According to the second modification, when a pharmacy user logs in to the service of the server 30, the pharmacy user is presented with prescription information of patients who wish to receive online medication instruction and prescription information of patients who wish to receive face-to-face medication instruction. This allows the pharmacy user to centrally check prescription information that should be handled by their pharmacy, regardless of the medication instruction format.

[0195] According to the second modification, when a medical institution user logs in to the service of the server 30, prescription information of a patient who desires online medication instruction and prescription information of a patient who desires face-to-face medication instruction are presented. This allows the user to centrally check prescription information issued by his / her own medical institution, regardless of the medication instruction format.

[0196] (7) Other modifications Other modifications will now be described.

[0197] The storage device 11 may be connected to the medical institution client device 10 via a network NW. The storage device 21 may be connected to the patient client device 20 via a network NW. The storage device 31 may be connected to the server 30 via a network NW. The storage device 41 may be connected to the pharmacy client device 40 via a network NW.

[0198] Although the embodiment of the present invention has been described in detail above, the scope of the present invention is not limited to the above embodiment. Furthermore, the above embodiment can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above embodiment and the modified examples can be combined. [Explanation of symbols]

[0199] 1: Information processing system 10: Medical institution client device 11:Storage device 12: Processor 13: Input / Output Interface 14: Communication interface 20: Patient client device 21:Storage device 22: Processor 23: Input / Output Interface 24: Communication interface 30: Server 31: Storage device 32 : Processor 33: Input / Output Interface 34: Communication interface 40: Pharmacy client device 41:Storage device 42: Processor 43: Input / Output Interface 44: Communication interface

Claims

1. An information processing device that supports medical institutions in handling prescriptions, A means for receiving a prescription image and a destination pharmacy from a patient is provided, means for receiving an instruction of approval of the prescription image from a medical institution user; means for transmitting a prescription image corresponding to the approval instruction to the destination pharmacy; Information processing device.

2. A means for storing the prescription image and the status of the prescription in association with each other, means for setting the status to "waiting for approval" when the prescription image is accepted; The setting means sets the status to "data transmitted" when the prescription image is transmitted to the destination pharmacy. The information processing device according to claim 1 .

3. The setting means sets the status to "original sent" when the medical institution sends the original of the prescription to the destination pharmacy. The information processing device according to claim 2 .

4. a means for receiving a destination pharmacy change instruction from the medical institution user to change the destination pharmacy; The means for transmitting the prescription image transmits, when the instruction to change the destination pharmacy is received, the prescription image to a destination pharmacy corresponding to the instruction to change the destination pharmacy.

4. The information processing device according to claim 1.

5. A means for receiving a designation of online medication instruction or face-to-face medication instruction from the patient, When the medication instruction format designated by the patient is face-to-face medication instruction, the sending means sends the prescription image to the destination pharmacy without accepting the instruction of approval.

5. The information processing device according to claim 1.

6. A means for presenting a status of the prescription for which the online medication instruction has been selected and a status of the prescription for which the face-to-face medication instruction has been selected to at least one of a pharmacy user and the medical institution user, The information processing device according to claim 5 .

7. A program for causing a computer to function as any one of the means recited in any one of claims 1 to 6.

8. An information processing method for supporting medical institutions in handling prescriptions using a computer, comprising: The computer includes a step of receiving, from a patient, a prescription image and a designation of a delivery destination pharmacy; The computer includes a step of receiving an instruction of approval of the prescription image from a medical institution user, An information processing method comprising a step of the computer sending a prescription image corresponding to the approval instruction to the destination pharmacy.

Images