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 apparatus, a program, and an information processing method.

Background Art

[0002] In general, in order for a patient to receive a drug corresponding to a prescription issued by a medical institution, the patient visits a pharmacy, presents the prescription to the pharmacy, and receives the drug dispensed by a pharmacist as well as medication guidance from the pharmacist. That is, the provision of the prescription to the pharmacy and the medication guidance are conducted in person. This is referred to as the principle of in-person medication guidance.

[0003] In recent years, regulatory reforms that allow medication guidance provided by pharmacies in the provision of ethical drugs based on prescriptions to be conducted online have been advancing. This is called online medication guidance, and its widespread use is currently expected.

[0004] For example, Patent Document 1 discloses a technology for supporting pharmacist users, in which specific medical information can be collected accurately and quickly within the range required by pharmacists without imposing a burden on the pharmacists and can be provided as information, so that the pharmacists can make use of their professional capabilities to accurately and easily provide guidance and advice specific to the corresponding user based on the prescribed drug information.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0006] On the other hand, when conducting online medication guidance, patients do not visit pharmacies, so they need to submit their prescriptions without going to a pharmacy. Currently, when conducting online medication guidance, the method of submitting prescriptions to pharmacies is not done by the patient themselves, but by the prescribing medical institution sending a copy via fax or data to the pharmacy of the patient's choice, with the original being sent later. In other words, when conducting online medication guidance, medical institutions need to be responsible not only for issuing prescriptions but also for sending them to pharmacies, and in order to promote the spread of online medication guidance, it is important to reduce the burden on medical institutions of submitting prescription information to pharmacies, which is an additional burden.

[0007] Patent Document 1 focuses on supporting pharmacists, but does not focus on supporting healthcare users (e.g., doctors and healthcare staff). Therefore, providing prescriptions to pharmacies and medication guidance online places a burden on healthcare institutions.

[0008] The objective of this invention is to reduce the burden on medical institutions when providing prescriptions to pharmacies and conducting medication guidance online. [Means for solving the problem]

[0009] One aspect of the present invention is, An information processing device that supports the handling of prescriptions by medical institutions, The system is equipped with a means to receive prescription images and the designation of the pharmacy to which the prescription should be sent from the patient. The system includes means for receiving instructions from a medical institution user for approval of the aforementioned prescription image, The system includes means for transmitting a prescription image corresponding to the approval instruction to the designated pharmacy. It is an information processing device. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing the configuration of the information processing system in this embodiment. [Figure 2] Figure 1 is a functional block diagram of the information processing system. [Figure 3] It is an explanatory diagram of the overview of the present embodiment. [Figure 4] It is a diagram showing the data structure of the medical institution database of the present embodiment. [Figure 5] It is a diagram showing the data structure of the pharmacy database of the present embodiment. [Figure 6] It is a diagram showing the data structure of the medical institution prescription database of the present embodiment. [Figure 7] It is a diagram showing the data structure of the pharmacy prescription database of the present embodiment. [Figure 8] It is a sequence diagram of prescription registration processing of the present embodiment. [Figure 9] It is a diagram showing an example of a screen displayed in the information processing of Fig. 8. [Figure 10] It is a sequence diagram of prescription approval processing of the present embodiment. [Figure 11] It is a diagram showing an example of a screen displayed in the information processing of Fig. 10. [Figure 12] It is a sequence diagram of medication guidance processing of the present embodiment. [Figure 13] It is a diagram showing an example of a screen displayed in the information processing of Fig. 12. [Figure 14] It is a sequence diagram of the destination pharmacy change processing of Modification 1. [Figure 15] It is a diagram showing the data structure of the pharmacy prescription database of Modification 2. [Figure 16] It is a sequence diagram of prescription transmission processing of Modification 2. [Figure 17] It is a diagram showing an example of a screen displayed in the information processing of Fig. 16. [Figure 18] It is a sequence diagram of prescription status change processing of Modification 2. [Figure 19] It is a diagram showing an example of a screen displayed in the information processing of Fig. 18. [Figure 20] It is a diagram showing an example of a screen displayed in the information processing of Fig. 18. [Modes for Carrying Out the Invention]

[0011] Hereinafter, one embodiment of the present invention will be described in detail based on the drawings. Note that in the drawings for describing the embodiment, the same reference numerals are assigned to the same constituent elements in principle, and repeated descriptions thereof will be omitted.

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

[0013] As shown in Figure 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 (for example, the Internet or an intranet) NW.

[0014] The medical institution client device 10 is a computer (an example of an "information processing apparatus") that transmits a request to the server 30. The medical institution client device 10 is used by a user of a medical institution (for example, a hospital) (hereinafter referred to as a "medical institution user"). The medical institution user includes, for example, medical personnel belonging to the hospital (as an example, doctors and pharmacists), 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 apparatus") 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 arranged 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 sends requests to the server 30. The pharmacy client device 40 is used by users of the pharmacy (hereinafter referred to as "pharmacy users"). Pharmacy users include, for example, pharmacists and pharmacy staff belonging to the pharmacy. The pharmacy client device 40 is, for example, a smartphone, a tablet device, or a personal computer.

[0017] Server 30 provides services to support the handling of prescriptions by medical institutions. Server 30 is a computer (an example of an "information processing device") that provides responses to requests sent from medical institution client device 10, patient client device 20, or pharmacy client device 40 to the medical institution client device 10, patient client device 20, or pharmacy client device 40. Server 30 is, for example, a web server.

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

[0019] As shown in Figure 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 ROM (Read Only Memory), RAM (Random Access Memory), and storage (e.g., flash memory or hard disk).

[0021] The program includes, for example, the following: • OS (Operating System) programs • Programs for applications that perform information processing (e.g., web browsers)

[0022] The data includes, for example, the following: • 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 launching 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 acquire 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. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. An output device is, for example, a display.

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

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

[0027] As shown in Figure 2, the patient client device 20 includes a storage 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. The storage device 21 is, for example, a combination of ROM, RAM, and storage (e.g., flash memory or hard disk).

[0029] The program includes, for example, the following: • OS programs • Programs for applications that perform information processing (e.g., web browsers)

[0030] The data includes, for example, the following: • 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 realize the functions of the patient client device 20 by launching a program stored in the storage device 21. The processor 22 is, for example, a CPU, ASIC, FPGA, or a combination thereof.

[0032] The input / output interface 23 is configured to acquire user instructions from an input device connected to the patient client device 20 and to output information to an output device connected to the patient client device 20. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. An output device is, for example, a display.

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

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

[0035] As shown in Figure 2, the pharmacy client device 40 includes a storage 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. The storage device 41 is, for example, a combination of ROM, RAM, and storage (e.g., flash memory or hard disk).

[0037] The program includes, for example, the following: • OS programs • Programs for applications that perform information processing (e.g., web browsers)

[0038] The data includes, for example, the following: • 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 launching a program stored in the storage device 41. The processor 42 is, for example, a CPU, ASIC, FPGA, or a combination thereof.

[0040] The input / output interface 43 is configured to receive user instructions from an input device connected to the pharmacy client device 40 and to output information to an output device connected to the pharmacy client device 40. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. An output device is, for example, a display.

[0041] The communication interface 44 is configured to control communication between the pharmacy client device 40 and the server 30.

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

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

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

[0045] The program includes, for example, the following: • OS programs • Programs for applications that perform information processing.

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

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

[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. Input devices include, for example, keyboards, pointing devices, touch panels, or combinations thereof. An output device is, for example, a display.

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

[0050] (2) Outline of the Embodiment This embodiment will now be outlined. Figure 3 is an explanatory diagram of this embodiment.

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

[0052] The healthcare user uses the healthcare client device 10 to approve the contents of the prescription image information (i.e., the contents of the prescription) sent to the server 30.

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

[0054] The pharmacy user dispenses medications corresponding to the prescription image information transmitted to the pharmacy client device 40, and also provides online medication guidance.

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

[0056] (3) Database The database of this embodiment will now be described. The following database is stored in the storage device 31.

[0057] (3-1) Medical Institution Database The medical institution database of this embodiment will now be described. Figure 4 is a diagram showing the data structure of the medical institution database of this embodiment.

[0058] The medical institution database in Figure 4 stores medical institution information. Medical institution information is information about medical institutions. The healthcare database includes the fields "Healthcare ID," "Healthcare Name," and "Healthcare Contact." Each field is related to the others.

[0059] The "Medical Institution ID" field stores medical institution identification information. Medical institution identification information is information that identifies a medical institution.

[0060] The "Medical Institution Name" field stores information about the name of the medical institution. This information pertains to the name of the medical institution.

[0061] The "Medical Institution Contact" field stores medical institution contact information. This information contains contact details for medical institutions.

[0062] (3-2) Pharmacy Database The pharmacy database of this embodiment will now be described. Figure 5 shows the data structure of the pharmacy database of this embodiment.

[0063] The pharmacy database in Figure 5 stores pharmacy information. Pharmacy information is information about pharmacies. The pharmacy database includes a "Pharmacy ID" field, a "Pharmacy Name" field, and a "Pharmacy Contact" field. Each field is related to the others.

[0064] The "Pharmacy ID" field stores pharmacy identification information. This pharmacy identification information is used to identify a pharmacy.

[0065] The "Pharmacy Name" field stores the pharmacy name information. This information pertains to the name of the pharmacy.

[0066] The "Pharmacy Contact" field stores pharmacy contact information. This information contains the contact details for the pharmacy.

[0067] (3-3) Medical Institution Prescription Database This embodiment describes the medical institution prescription database. Figure 6 shows the data structure of the medical institution prescription database according to this embodiment.

[0068] The medical institution prescription database in Figure 6 stores prescription information. Prescription information is information related to prescriptions. The medical institution prescription database includes the following fields: "Prescription ID," "Prescription Submission Date and Time," "Recipient Pharmacy ID," "Desired Consultation Date and Time," "Prescription Image," "Generic," "Patient Name," "Patient Contact," and "Medical Institution Prescription Status." Each field is related to 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. Prescription identification information is information that identifies the prescription.

[0070] The "Prescription Submission Date and Time" field stores prescription submission date and time information. This information concerns the date and time when the patient sent the prescription image to the medical institution.

[0071] The "Recipient Pharmacy ID" field stores the recipient pharmacy identification information. This recipient pharmacy identification information identifies the pharmacy to which the prescription should be sent (hereinafter referred to as the "recipient pharmacy").

[0072] The "Desired Consultation Date and Time" field stores information about the desired consultation date and time. This information concerns the date and time when the patient wishes to receive medication guidance from a pharmacist.

[0073] The "Prescription Image" field stores prescription image information. Prescription image information is information about the prescription image.

[0074] The "Generic" field stores generic information. This generic information concerns whether the patient prefers generic medications.

[0075] The "Patient Name" field stores patient name information. This patient name information is related to the name of the patient to whom the prescription is issued.

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

[0077] The "Medical Institution Prescription Status" field stores the medical institution prescription status information. This medical institution prescription status information is information about the status of the prescription at the medical institution. Medical institution prescription status includes, for example, the following: • "Pending Approval" - This means that the patient has successfully sent the prescription image to the medical institution, but the medical institution has not yet approved the prescription. • "Data transmitted" - This means that the prescription has been approved by the medical institution, but the dispensing by the pharmacy has not yet been completed. • "Original document sent" - This means that the medical institution has sent the original prescription to the pharmacy, but the original prescription has not yet arrived at the pharmacy.

[0078] (3-4) Pharmacy prescription database This embodiment describes the pharmacy prescription database. Figure 7 shows the data structure of the pharmacy prescription database in this embodiment.

[0079] The pharmacy prescription database in Figure 7 stores prescription information. The pharmacy prescription database includes the following fields: "Prescription ID," "Prescription Received Date and Time," "Sending Medical Institution ID," "Desired Consultation Date and Time," "Prescription Image," "Generic," "Patient Name," "Patient Contact," and "Pharmacy Prescription Status." Each field is related to the others. The pharmacy prescription database is associated with the pharmacy identification information of the pharmacy that received the prescription.

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

[0081] The "Prescription Received Date and Time" field stores the prescription received date and time information. This information concerns the date and time the prescription was received from the medical institution.

[0082] The "Sending Medical Institution ID" field stores the sending medical institution identification information. This information identifies the medical institution that sent the prescription (hereinafter referred to as the "sending medical institution").

[0083] The "Desired Instruction Date and Time" field stores the desired instruction date and time information.

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

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

[0086] The "Patient Name" field stores the patient's name information.

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

[0088] The "Pharmacy Prescription Status" field stores pharmacy prescription status information. This information concerns the status of the prescription at the pharmacy. Pharmacy prescription statuses include, for example, the following: • "New application"... This means that the prescription information has been received (i.e., the prescription has been approved by the medical institution), but the dispensing by the pharmacy has not yet been completed. • "Dispensed" - This means that the pharmacy has completed dispensing the medication, but has not yet completed medication guidance by the pharmacy. • "Medication guidance completed" - This means that medication guidance by the pharmacy has been completed, but the pharmacy has not yet arranged for the delivery of the medication. • "Delivery arranged" - This means that the pharmacy has completed the arrangements for the delivery of the medication, but the medication has not yet arrived at the patient's location. • "Delivery Confirmed" - This means the medication has arrived at the patient's location, but the medical institution has not yet sent the original prescription to the pharmacy.

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

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

[0091] The trigger for the process shown in Figure 8 is, for example, access to a pre-configured medical institution-only site on the patient client device 20. The medical institution-only site is assigned medical institution identification information.

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

[0093] Screen P1120 includes the operation object B11200 and the field objects F11200 to F11203.

[0094] The field object F11200 is an object that accepts user instructions to specify the format of medication guidance (e.g., in-person medication guidance or online medication guidance).

[0095] Field object F11201 is an object that accepts user instructions for specifying the destination pharmacy.

[0096] Field object F11202 is an object that accepts user instructions for specifying patient name information and patient contact information.

[0097] Field object F11203 is an object that accepts user instructions for specifying generic information.

[0098] Operation object B11200 is an object that receives user instructions to confirm the user instructions given to field objects F11200 to F11203. When "Online Medication Guidance" is specified in field object F11200 and operation object B11200 is operated, processor 22 stores the contents of the user instructions given to field objects F11200 to F11203 in storage device 21 and displays screen P1121 (Figure 9) on the display.

[0099] Screen P1121 includes display object A11210 and operation object B11210.

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

[0101] Operation object B11210 is an object that receives user instructions to confirm the prescription image displayed on display object A11210.

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

[0103] Screen P1122 includes the operation object B11220 and the field object F11220.

[0104] Field object F11220 is an object that accepts user instructions for specifying the desired date and time for medication guidance.

[0105] Operation object B11220 is an object that receives user instructions to confirm the user instructions given to field object F11220. When a patient user operates the operation object B11220, the processor 22 stores the contents of the user instruction given to the field object F11220 in the storage device 21.

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

[0107] After step S1121, the server 30 performs prescription registration (S1130). Specifically, the processor 32 adds a new record to the medical institution prescription database (Figure 6) associated with the medical institution identification information assigned to the medical institution's dedicated site. Each field in a new record will contain the following information: • "Prescription ID" field: New prescription identification information • "Prescription Submission Date and Time" field: Information regarding the execution date and time of step S1121. • "Recipient Pharmacy ID" field: Pharmacy identification information of the recipient pharmacy included in the prescription registration request data. • "Preferred date and time for instruction" field: Information on the preferred date and time for 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 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 prescription registration request data • "Medical Institution Prescription Status" field: Medical Institution Prescription Status Information "Pending Approval"

[0108] The processor 32 adds a new record to the pharmacy prescription database (Figure 7) associated with the pharmacy identification information of the recipient pharmacy. Each field in a new record will contain the following information: • "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: Identifying information of the sending medical institution included in the prescription registration request data. • "Desired date and time for instruction" field: Instruction preference 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 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 prescription registration request data • "Pharmacy Prescription Status" field: Pharmacy prescription status information "Newly received"

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

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

[0111] Screen P1123 displays a message indicating that prescription registration is complete, and a message prompting the user to submit the original prescription to the medical institution.

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

[0113] The trigger for the process shown in Figure 10 is, for example, when a healthcare facility user successfully logs in to the server 30's service using healthcare facility identification information via the healthcare facility client device 10.

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

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

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

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

[0118] Screen P1210 includes the "Medical Institution Prescription Status" object, the "Prescription Submission Date and Time" object, the "Patient Name" object, the "Patient Contact" object, the "Recipient Pharmacy Name" object, and the "Desired Online Medication Guidance Date and Time" object.

[0119] The "Medical Institution Prescription Status" object displays the medical institution prescription status information. The "Medical Institution Prescription Status" object is operation object B12100. Operation object B12100 is an object that accepts user instructions to change the medical institution prescription status information.

[0120] The "Prescription Submission Date and Time" object displays the prescription submission date and time information.

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

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

[0123] The "Recipient Pharmacy Name" object displays the recipient pharmacy name information. The "Recipient Pharmacy Name" object is operation object B12101. Operation object B12101 is an object that accepts user instructions to change the recipient pharmacy.

[0124] The "Requested Online Medication Counseling Date and Time" object displays the requested date and time for online medication counseling.

[0125] After step S1211, the medical institution client device 10 executes an approval request (S1212). Specifically, when a healthcare user interacts with the operation object B12100, which is a healthcare prescription status information "pending approval", the processor 12 sends approval request data to the server 30. The approval request data includes prescription identification information assigned to the operation object B12100 manipulated by the healthcare user (i.e., prescription identification information of the prescription subject to approval).

[0126] After step S1212, the server 30 performs the transmission of prescription data (S1232). Specifically, the processor 32 refers to the medical institution prescription database (Figure 6) to identify the record corresponding to the prescription identification information included in the approval request data (hereinafter referred to as the "record to be transmitted"). The processor 32 identifies the recipient pharmacy identification information for the record to be sent. The processor 32 refers to the pharmacy database (Figure 5) to identify the pharmacy contact information associated with the recipient pharmacy information. The processor 32 transmits the prescription image information included in the record to be transmitted to the contact indicated in the pharmacy contact information.

[0127] After step S1232, server 30 performs a database update (S1233). Specifically, processor 32 changes the medical institution prescription status information of the record to be sent to "Data Sent".

[0128] (4-3) Medication guidance The medication guidance process of this embodiment will now be explained. Figure 12 is a sequence diagram of the medication guidance process of this embodiment. Figure 13 is a diagram showing an example of a screen displayed in the information processing shown in Figure 12.

[0129] The trigger for the process shown in Figure 12 is, for example, when a pharmacy user successfully logs in to the server 30's service using pharmacy identification information via the pharmacy client device 40.

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

[0131] After step S1340, the server 30 performs the extraction of the prescription list (S1330). Specifically, the processor 32 identifies the record in the pharmacy medical institution prescription database (Figure 7) associated with the pharmacy identification information used for login.

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

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

[0134] Screen P1340 includes the "Pharmacy Prescription Status" object, the "Prescription Received Date and Time" object, the "Sending Medical Institution Name" object, the "Patient Name" object, the "Patient Contact" object, and the "Desired Date and Time for Online Medication Guidance" object.

[0135] The "Pharmacy Prescription Status" object displays pharmacy prescription status information. The "Pharmacy Prescription Status" object is operation object B13400. Operation object B13400 is an object that accepts user instructions to change pharmacy prescription status information.

[0136] The "Prescription Received Date and Time" object displays the prescription received date and time information.

[0137] The "Sending Medical Institution Name" object displays the name information of the sending medical institution.

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

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

[0140] The "Requested Online Medication Counseling Date and Time" object displays the requested date and time for online medication counseling.

[0141] After step S1331, the pharmacy client device 40 executes a prescription status change request (S1342). Specifically, when a pharmacy user dispenses medication and conducts online medication guidance, and then operates on the prescription operation object B13400 which should change the pharmacy prescription status, the processor 42 sends 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 operation object B13400 operated by the pharmacy user

[0142] After step S1343, server 30 performs a database update (S1332). Specifically, the processor 32 refers to the pharmacy prescription database (Figure 7) and stores "Medication guidance 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 this embodiment According to this embodiment, an information processing device (for example, a server 30) is provided that supports the handling of prescriptions by a medical institution, and includes means (S1130) for receiving a prescription image and a designation of a destination pharmacy from a patient, means (S1232) for receiving an instruction from a medical institution user for approval of the prescription image, and means (S1232) for transmitting a prescription image corresponding to the approval instruction to the destination pharmacy. In this way, once a healthcare provider gives approval instructions, the prescription image taken by the patient user is sent to the designated pharmacy. This reduces the burden on healthcare providers when providing prescriptions and medication guidance to pharmacies online.

[0144] According to this embodiment, the system includes means for associating and storing a prescription image with the status of the prescription, and when a prescription image is received, it includes means for setting the status to "awaiting approval". The setting means may also set the status to "data sent" when the prescription image has been sent to the receiving pharmacy. In this way, the status of a prescription changes depending on the actions taken on it. This allows healthcare users to easily understand the progress of prescriptions.

[0145] According to this embodiment, when a medical institution sends the original prescription to the receiving pharmacy, the status may be set to "original sent." In this way, the status of a prescription changes depending on the actions taken on it. This allows healthcare users to easily understand the progress of prescriptions.

[0146] (6) Variant A modified example of this embodiment will be described.

[0147] (6-1) Torture 1 Modification 1 of this embodiment will now be described. Modification 1 is an example in which, when a pharmacy is unable to accept a prescription, the destination pharmacy is changed according to the instructions of the medical institution user. Figure 14 is a sequence diagram of the process for changing the recipient pharmacy in Modification Example 1.

[0148] The trigger for the process shown in Figure 14 is, for example, when a healthcare user receives notification from the receiving pharmacy (hereinafter referred to as the "pharmacy subject to change") that "the prescription cannot be accepted," and then successfully logs in to the server 30 service using healthcare identification information via the healthcare client device 10.

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

[0150] After step S1211, the medical institution client device 10 executes a change request (S1410). Specifically, when a healthcare user operates the operation object B12101 of the "Recipient Pharmacy Name" object corresponding to the pharmacy to be changed on screen P1210 (Figure 11), and specifies a new recipient pharmacy (hereinafter referred to as the "changed pharmacy"), the processor 12 sends a recipient pharmacy change request data to the server 30. The request data for changing the recipient pharmacy includes the following information: • Prescription identification information assigned to operation object B12101 operated by the healthcare user (i.e., prescription identification information of the prescription being modified) • Pharmacy identification information of the changed pharmacy

[0151] After step S1410, the server 30 performs the transmission of prescription data (S1430). Specifically, the processor 32 identifies the record corresponding to the prescription identification information included in the change request data (hereinafter referred to as the "record to be changed"). The processor 32 refers to the pharmacy database (Figure 5) to identify pharmacy contact information associated with the pharmacy identification information contained in the change request data. The processor 32 sends the prescription image information included in the record to be modified to the contact person indicated in the pharmacy contact information.

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

[0153] According to Modification 1, even if the pharmacy designated by the patient is unable to accept the prescription, the healthcare provider can easily change the designated pharmacy. This further reduces the burden on healthcare providers when providing prescriptions and medication guidance to pharmacies online.

[0154] (6-2) Modification 2 Let's explain variation 2. Variation 2 is an example of managing prescriptions for online medication guidance and prescriptions for in-person medication guidance together.

[0155] (6-2-1) Pharmacy Prescription Database The pharmacy prescription database of Modification 2 will be explained. Figure 15 shows the data structure of the pharmacy prescription database of Modification 2.

[0156] The pharmacy prescription database in Figure 15 stores prescription information. The pharmacy prescription database includes the following fields: "Prescription ID," "Prescription Received Date and Time," "Sending Medical Institution ID," "Desired Counseling Date and Time," "Prescription Image," "Generic," "Patient Name," "Patient Contact," "Pharmacy Prescription Status," "Medication Counseling Format," and "Desired Pickup Date and Time." Each field is related to the others. The pharmacy prescription database is associated with the pharmacy identification information of the pharmacy that received the prescription.

[0157] The "Prescription ID" field, "Prescription Received Date and Time" field, "Sending Medical Institution ID" field, "Desired Guidance 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. This information concerns the status of the prescription at the pharmacy. The pharmacy prescription status includes, for example, the pharmacy prescription status of this embodiment, plus the following: • "New registration"... This means that medication guidance and provision of medication by the pharmacy have not yet been completed. • "Received" - This means that the pharmacy has completed providing medication guidance and supplying the medication.

[0159] The "Medication Counseling Format Field" stores information about the medication counseling format. This information pertains to the format of the medication counseling (online or in-person).

[0160] The "Desired Pickup Date and Time" field stores the desired pickup date and time information. This information concerns the date and time the patient wishes to receive the medication (hereinafter referred to as "Desired Pickup Date and Time").

[0161] (6-2-2) Prescription transmission process The prescription transmission process of Modification 2 will now be explained. Figure 16 is a sequence diagram of the prescription transmission process of Modification 2. Figure 17 is a diagram showing an example of the screen displayed in the information processing in Figure 16.

[0162] The trigger for the process shown in Figure 16 is, for example, access to a pre-configured medical institution-only site on the patient client device 20. The medical institution-only site is assigned medical institution identification information.

[0163] As shown in Figure 16, the patient client device 20 performs prescription image reception (S1120), similar to Figure 8.

[0164] After step S1120, the patient client device 20 executes a prescription transmission request (S2120). Specifically, when a patient user selects "In-person medication guidance" in the field object F11200 and operates the operation object B11210, the processor 22 displays screen P2120 (Figure 17) on the display.

[0165] Screen P2120 includes the operation object B21200 and the field object F21200.

[0166] The field object F21200 is an object that accepts user instructions to specify the desired delivery date and time.

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

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

[0169] After step S2120, the server 30 performs the transmission of prescription data (S2130). Specifically, the processor 32 refers to the pharmacy database (Figure 5) to identify pharmacy contact information associated with the pharmacy identification information of the recipient pharmacy included in the prescription transmission request data. The processor 32 transmits the prescription image information included in the prescription transmission request data to the contact person indicated in the pharmacy contact information.

[0170] After step S2130, server 30 performs a database update (S2131). Specifically, the processor 32 adds a new record to the medical institution prescription database (Figure 6) associated with the medical institution identification information assigned to the medical institution's dedicated site. Each field in a new record will contain the following information: • "Prescription ID" field: New prescription identification information • "Prescription Submission Date and Time" field: Information regarding the execution date and time of step S2120. • "Recipient Pharmacy ID" field: Pharmacy identification information of the recipient pharmacy included in the prescription transmission request data. • "Desired pickup date and time" field: Information about the desired pickup date and time included in the prescription submission request data. • "Prescription Image" field: Prescription image information included in the prescription submission request data. • "Generic" field: Generic information included in prescription submission request data • "Patient Name" field: Patient name information included in the prescription submission request data. • "Patient Contact" field: Patient contact information included in prescription submission request data • "Medical Institution Prescription Status" field: NULL

[0171] The processor 32 adds a new record to the pharmacy prescription database (Figure 15) associated with the pharmacy identification information of the recipient pharmacy. Each field in a new record will contain the following information: • "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: Identifying information of the sending medical institution included in the prescription transmission request data. • "Desired date and time for instruction" field: NULL • "Prescription Image" field: Prescription image information included in the prescription submission request data. • "Generic" field: Generic information included in prescription submission request data • "Patient Name" field: Patient name information included in the prescription submission request data. • "Patient Contact" field: Patient contact information included in prescription submission request data • "Pharmacy Prescription Status" field: Pharmacy prescription status information "Newly received" • "Desired pickup date and time" field: Information about the desired pickup date and time included in the prescription submission request data.

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

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

[0174] Screen P2121 displays a message indicating that the prescription has been successfully submitted.

[0175] (6-2-3) Processing of changes to prescription status The prescription status change process in Modification Example 2 will be explained. Figure 18 is a sequence diagram of the prescription status change process in Modification Example 2. Figure 19 is a diagram showing an example of the screen displayed in the information processing in Figure 18. Figure 20 is a diagram showing an example of the screen displayed in the information processing in Figure 18.

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

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

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

[0179] After step S1340 or S2210, the server 30 performs the extraction of the prescription list (S2230). Specifically, the processor 32 identifies the record in the medical institution prescription database (Figure 6) associated with the medical institution identification information used for login. The processor 32 identifies the record in the pharmacy prescription database (Figure 7) associated with the pharmacy identification information used for login.

[0180] After step S2230, the server 30 executes the 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 sent to the pharmacy client device 40 includes, for example, prescription information for the record in the pharmacy prescription database (Figure 7) identified in step S2230. The prescription list response data sent to the medical institution client device 10 includes, for example, prescription information for the records in the medical institution prescription database (Figure 6) identified in step S2230.

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

[0182] Screen P2210 includes the "Pharmacy Prescription Status" object, the "Prescription Received Date and Time" object, the "Patient Name" object, the "Patient Contact" object, the "Recipient Pharmacy Name" object, the "Desired Pickup Date and Time" object, and the operation objects B22100 to B22101.

[0183] The operation objects B22100 to B22101 are also displayed on page P1210 (Figure 11). Operation object B22100 is an object that accepts user instructions to display prescription information for patients who wish to receive online medication guidance. When operation object B22100, which is displayed on screen P2210, is operated, screen P1210 is displayed. Operation object B22101 is an object that accepts user instructions to display prescription information for patients who wish to receive in-person medication guidance. When operation object B22101, which is displayed on screen P1210, is operated, screen P2210 is displayed.

[0184] The "Pharmacy Prescription Status" object, the "Prescription Received Date and Time" object, the "Sending Medical Institution ID" object, the "Patient Name" object, and the "Patient Contact" object are the same as in Figure 13.

[0185] The "Desired Delivery Date and Time" object displays the desired delivery date and time information.

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

[0187] Screen P2240 includes the "Pharmacy Prescription Status" object, the "Prescription Received Date and Time" object, the "Sending Medical Institution Name" object, the "Patient Name" object, the "Patient Contact" object, the "Desired Pickup Date and Time" object, and operation objects B22400 to B22402.

[0188] The operation objects B22400~B22401 are also displayed on page 1340 (Figure 13). Operation object B22400 is an object that accepts user instructions to display prescription information for patients who wish to receive online medication guidance. When operation object B22400, which is displayed on screen P2240, is operated, screen P1340 is displayed. Operation object B22401 is an object that receives user instructions to display prescription information for patients who wish to receive in-person medication guidance. When operation object B22400, which is displayed on screen P1340, is operated, screen P2240 is displayed.

[0189] The "Pharmacy Prescription Status" object, the "Prescription Received Date and Time" object, the "Sending Medical Institution Name" object, the "Patient Name" object, and the "Patient Contact" object are the same as in Figure 13. The "Pharmacy Prescription Status" object is operation object B22402. Operation object B22402 is an object that accepts user instructions to change pharmacy prescription status information.

[0190] The "Desired Delivery Date and Time" object displays the desired delivery 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 dispenses medication and provides face-to-face medication guidance, and then operates on the prescription operation object B22402 which should change the pharmacy prescription status, the processor 42 sends 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 operation object B22402 operated by the pharmacy user

[0192] After step S2241, server 30 performs a database update (S2232). Specifically, the processor 32 refers to the pharmacy prescription database (Figure 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 Variation 2 According to Modification 2, when the patient user takes a picture of the prescription, they select either in-person medication guidance or online medication guidance on the common screen P1120 (S1120). If in-person medication guidance is selected, the server 30 sends the prescription image to the receiving pharmacy without receiving approval instructions from the medical institution user (S2130). This makes it easy to send prescriptions to pharmacies regardless of the format of medication guidance.

[0194] According to Modification 2, when a pharmacy user logs into the server 30 service, prescription information for patients who wish to receive online medication guidance and prescription information for patients who wish to receive in-person medication guidance are presented. This allows the pharmacy to centrally check prescription information that it should handle, regardless of the format of medication guidance.

[0195] According to Modification 2, when a healthcare institution user logs into the server 30 service, prescription information for patients who wish to receive online medication guidance and prescription information for patients who wish to receive in-person medication guidance are presented. This allows healthcare institutions to centrally check prescription information issued by their own healthcare institution, regardless of the format of medication guidance.

[0196] (7) Other variations Other variations will be explained.

[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 embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the embodiments described above. Furthermore, the embodiments described above can be improved or modified in various ways without departing from the spirit of the present invention. In addition, the embodiments and modifications described above 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 the handling of prescriptions by medical institutions, The system is equipped with a means to receive prescription images, the designated pharmacy for delivery, and the designation of online or in-person medication guidance from patients. If the medication guidance format specified by the patient is face-to-face medication guidance, the system includes means for transmitting the prescription image to the designated pharmacy without receiving approval instructions from the healthcare institution user. Information processing device.

2. The system includes means for receiving instructions from a medical institution user for approval of the aforementioned prescription image, If the medication guidance format specified by the patient is online medication guidance, the system is equipped with means for receiving the approval instruction. The means of transmission transmits the prescription image corresponding to the approval instruction to the recipient pharmacy. The information processing apparatus according to claim 1.

3. The system includes means for associating and storing the prescription image and the status of the prescription, The system includes means for setting the status to "pending approval" when the aforementioned prescription image is received. The means for setting the status is to set the status to "Data sent" when the prescription image is sent to the recipient pharmacy. The information processing apparatus according to claim 2.

4. The means for setting the status is to set the status to "original sent" when the medical institution sends the original prescription to the designated pharmacy. The information processing apparatus according to claim 3.

5. The system includes means for receiving instructions from the medical institution user to change the destination pharmacy, The means for transmitting the prescription image, upon receiving the instruction to change the recipient pharmacy, transmits the prescription image to the recipient pharmacy corresponding to the instruction to change the recipient pharmacy. An information processing apparatus according to any one of claims 1 to 4.

6. The system includes means for displaying to at least one of the pharmacy user and the medical institution user the status of prescriptions for which online medication guidance has been selected and the status of prescriptions for which in-person medication guidance has been selected. An information processing apparatus according to any one of claims 1 to 5.

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

8. An information processing method that uses a computer to support the handling of prescriptions at medical institutions, The computer includes a step of receiving from the patient an image of the prescription, a designation of the pharmacy to which the prescription will be sent, and a designation of online or in-person medication guidance. Information processing method comprising the step of transmitting the prescription image to the destination pharmacy without receiving approval instructions from the medical institution user if the medication guidance format specified by the patient is face-to-face medication guidance.

Images