Server, client device, program, and information processing method

Abstract

To reduce constraints of a pharmacy and a patient for handling a prescription with electronic data.SOLUTION: A server is connectable to a patient client device used by a patient and a pharmacy client device used by a user of a pharmacy. The server includes means for: acquiring pharmacy identification information for identifying a pharmacy and prescription information of the patient from the patient client device; generating one time access information corresponding to the prescription information acquired from the patient client device; transmitting one time access information to the pharmacy client device; and transmitting prescription information to the pharmacy client device in response to an access request via the one time access information from the pharmacy client device.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] In recent years, the number of pharmacies that handle prescriptions electronically has been increasing. For example, Patent Document 1 discloses a technique for appropriately protecting personal information when handling prescriptions as electronic data. [Prior art documents] [Patent documents]

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

[0004] However, the technology of Patent Document 1 requires a dedicated environment in the pharmacy (for example, an identification information reader that wirelessly communicates with the patient's IC card or portable terminal device). Therefore, pharmacies that can handle patient prescriptions as electronic data are limited to those with a dedicated environment, which means that there are many restrictions on pharmacies and patients when handling prescriptions as electronic data.

[0005] An object of the present invention is to reduce the restrictions on pharmacies and patients for handling prescriptions as electronic data. [Means for solving the problem]

[0006] One aspect of the present invention is A server connectable to a patient client device used by a patient and a pharmacy client device used by a pharmacy user, means for obtaining, from the patient client device, pharmacy identification information that identifies the pharmacy and prescription information for the patient; means for generating one-time access information corresponding to prescription information obtained from the patient client device; means for transmitting the one-time access information to the pharmacy client device; means for transmitting the prescription information to the pharmacy client device in response to an access request from the pharmacy client device via the one-time access information; It is a server. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a functional block diagram of the information processing system of FIG. 1. [Figure 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 pharmacy information database according to the present embodiment. [Figure 5] FIG. 2 is a diagram showing the data structure of a prescription sharing information database according to the present embodiment. [Figure 6] FIG. 10 is a sequence diagram of a prescription sharing process according to this embodiment. [Figure 7] 7A and 7B are diagrams showing examples of screens displayed in the information processing of FIG. 6. [Figure 8] 7A and 7B are diagrams showing examples of screens displayed in the information processing of FIG. 6. [Figure 9] FIG. 10 is a sequence diagram of a first example of a prescription drug completion notification process according to the present embodiment. [Figure 10] 10A and 10B are diagrams showing examples of screens displayed in the information processing of FIG. 9. [Figure 11] FIG. 10 is an explanatory diagram of an overview of Modification 1. [Figure 12] FIG. 10 is a sequence diagram of a prescription sharing process according to the second modification. [Figure 13] 13 is a diagram showing an example of a screen displayed in the information processing of FIG. 12. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0008] 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 repeated description thereof will be omitted.

[0009] (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.

[0010] As shown in FIG. 1, the information processing system 1 includes a pharmacy client device 10, a server 30, and a patient client device 50. The pharmacy client device 10, the server 30, and the patient client device 50 are connected via a network (for example, the Internet or an intranet) NW.

[0011] The pharmacy client device 10 is a computer (an example of an "information processing device") that transmits requests to the server 30. The pharmacy client device 10 is operated by a pharmacy user. The pharmacy user is, for example, a pharmacist or a person in charge at a pharmacy. The pharmacy client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0012] The patient client device 50 is a computer (an example of an "information processing device") that sends a request to the server 30. The patient client device 50 is operated by a patient (for example, a patient who has received a prescription at a hospital). The patient client device 50 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0013] The server 30 is a computer (an example of an "information processing device") that provides the pharmacy client device 10 or the patient client device 50 with a response in response to a request sent from the pharmacy client device 10 or the patient client device 50. The server 30 is, for example, a web server.

[0014] (1-1) Configuration of Pharmacy Client Device The configuration of the pharmacy client device 10 will be described.

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

[0016] The storage device 11 is configured to store programs and data, and 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).

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

[0018] 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)

[0019] Processor 12 is configured to realize the functions of pharmacy client device 10 by running a program stored in storage device 11. 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.

[0020] Input / output interface 13 is configured to receive user instructions from an input device connected to pharmacy client device 10 and to output information to an output device connected to pharmacy 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.

[0021] Communications interface 14 is configured to control communications between pharmacy client device 10 and server 30 .

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

[0023] As shown in FIG. 2, the patient client device 50 includes a memory device 51, a processor 52, an input / output interface 53, and a communication interface .

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

[0025] The programs include, for example, the following programs: OS programs Applications that process information (e.g., web browsers)

[0026] 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)

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

[0028] The input / output interface 53 is configured to receive user instructions from an input device connected to the patient client device 50 and to output information to an output device connected to the patient client device 50 . 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.

[0029] The communications interface 54 is configured to control communications between the patient client device 50 and the server 30 .

[0030] (1-3) Server configuration The configuration of the server 30 will be described.

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

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

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

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

[0035] The processor 32 is configured to implement 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 thereof.

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

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

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

[0039] 3A, in response to a patient's instruction, the patient client device 50 acquires pharmacy identification information embedded in a code image (e.g., at least one of a character string, a graphic, a barcode image, and a two-dimensional code image) IMG placed at the pharmacy PH1. The pharmacy identification information is information that identifies the pharmacy PH1. The patient client device 50 transmits the pharmacy identification information and prescription information relating to the patient's prescription to the server 30.

[0040] The server 30 generates one-time access information corresponding to the prescription information sent from the patient client device 50 . The server 30 transmits the one-time access information to the pharmacy client device 10 located in the pharmacy PH1.

[0041] As shown in FIG. 3B, the pharmacy client device 10 transmits a prescription request to the server 30 in response to an instruction from a pharmacy user (for example, a pharmacist or a pharmacy clerk) of the pharmacy PH1.

[0042] In response to the prescription request, the server 30 transmits the prescription information to the pharmacy client device 10 .

[0043] The pharmacy client device 10 displays the prescription information on the display.

[0044] (3) Database The databases of this embodiment will be described below. The following databases are stored in the storage device 31.

[0045] (3-1) Pharmacy Information Database The pharmacy information database of this embodiment will be described below with reference to Fig. 4, which is a diagram showing the data structure of the pharmacy information database of this embodiment.

[0046] Pharmacy information is stored in the pharmacy information database of Figure 4. The pharmacy information is information relating to pharmacies. The pharmacy information database includes a "Corporate ID" field, a "Corporate Name" field, a "Pharmacy ID" field, a "Pharmacy Name" field, an "Address" field, a "Number of Pharmacists" field, and a "Pharmacy Contact" field. Each field is associated with another field.

[0047] The "Corporate ID" field stores corporate identification information, which identifies a corporation that operates multiple pharmacies.

[0048] The "Corporate Name" field stores corporate name information. The corporate identification information is information about the corporate name of the corporation that operates the pharmacy.

[0049] The "pharmacy ID" field stores pharmacy identification information. The pharmacy identification information is information that identifies a pharmacy.

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

[0051] The "Address" field stores address information, which is information about the address of the pharmacy.

[0052] The "number of pharmacists" field stores information about the number of pharmacists in the pharmacy.

[0053] The "Pharmacy Contact" field stores pharmacy contact information, which is information relating to the contact of the pharmacy (for example, at least one of a telephone number, a facsimile number, an email address, and a web service account).

[0054] (3-2) Prescription sharing information database The prescription sharing information database of this embodiment will be described below: Fig. 5 is a diagram showing the data structure of the prescription sharing information database of this embodiment.

[0055] Prescription sharing information is stored in the prescription sharing information database of Fig. 5. The prescription sharing information is information relating to the sharing of prescriptions. The prescription sharing information database includes a "Prescription ID" field, a "Shared Pharmacy ID" field, a "Shared Date and Time" field, a "Prescription" field, a "Patient Name" field, a "Patient Request" field, a "Patient Contact" field, a "Status" field, and an "Update Date and Time" field. Each field is associated with another field.

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

[0057] The "shared pharmacy ID" field stores pharmacy identification information of a pharmacy that shares prescription information (hereinafter referred to as a "shared pharmacy").

[0058] The "shared date and time" field stores shared date and time information. The shared date and time information is information about the date and time when prescription information was shared between the patient and the shared pharmacy.

[0059] The "Prescription" field stores a prescription image (an example of "Prescription information").

[0060] The "patient name" field stores patient name information, which is information about the patient's name.

[0061] The "patient request" field stores patient request information. The patient request information is information about the patient's request to the pharmacy. The patient request includes, for example, at least one of the following: ·Whether or not you have switched to generic drugs - Preferred date and time for receiving prescription medication The patient's relationship to the prescription drug recipient (e.g., whether the patient receives the prescription themselves or a family member receives it) ·Whether or not you bring your medicine notebook ·Information to pharmacists

[0062] The "Patient Contact" field stores patient contact information, which is information about the patient's contact information (e.g., email address, mobile phone number, or social network service account).

[0063] The "Status" field stores prescription status information. The prescription status information is information about the status of the prescription. The prescription status information includes, for example: "New": Prescription information that has not been viewed by the pharmacy "Dispensing": Prescription information corresponding to prescription drugs being dispensed by the pharmacy "Waiting for delivery": Prescription information corresponding to prescription drugs that have been dispensed by the pharmacy "Dispensed": Prescription information corresponding to prescription drugs that have been dispensed to patients by pharmacies

[0064] The "Update Date and Time" field stores update date and time information, which is information about the date and time when the prescription status information was updated.

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

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

[0067] The process of FIG. 6 is triggered, for example, by a patient user instruction (as an example, an instruction to launch a camera application installed on the patient client device 50).

[0068] As shown in FIG. 6, the patient client device 50 acquires the pharmacy ID (S1150). Specifically, the processor 52 displays a screen P150 (FIG. 7) on the display.

[0069] The screen P150 includes an operation object B1500.

[0070] The operation object B1500 is an object that receives a user instruction to acquire the code image IMG1500.

[0071] When the patient photographs the code image IMG1500 with a camera (not shown) of the patient client device 50 and operates the operation object B1500, the processor 52 identifies the pharmacy identification information embedded in the code image IMG1500.

[0072] After step S1150, the patient client device 50 acquires prescription information (S1151). Specifically, the processor 22 displays a screen P151 (FIG. 7) on the display.

[0073] The screen P151 includes an operation object B1510.

[0074] The operation object B1510 is an object that receives a user instruction to acquire a prescription image IMG1510 of the target patient. The image object IMG 1510 is one of the following: Images captured by a camera (not shown) included in the patient client device 50 Images captured by a camera (not shown) connected to the patient client device 50 Images retrieved from a storage device connected to the patient client device 50 Image read from storage device 51

[0075] When the target patient operates the operation object B1510, the processor 52 stores the image data of the prescription image IMG1510 in the storage device 51. The processor 52 displays screen P152 (FIG. 7) on the display.

[0076] The screen P152 includes an operation object B1520 and field objects F1520 to F1522.

[0077] The field object F1520 is an object that receives input of patient request information.

[0078] The field object F1521 is an object that accepts input of patient contact information.

[0079] The field object F1522 is an object that receives input of patient name information.

[0080] The operation object B1520 is an object that receives a user instruction to confirm input to the field objects F1520 to F1522.

[0081] After step S1151, the patient client device 50 executes a prescription sharing request (S1152). Specifically, when the target patient inputs any information into the field objects F1520 to F1522 and operates the operation object B1520, the processor 52 transmits the sharing request data to the server 30. The sharing request data includes, for example, the following information: Pharmacy identification information obtained in step S1150 A prescription image IMG1510 stored in the storage device 51 - Patient request information entered in field object F1520 Patient contact information entered in field object F1521 - Patient name information entered in field object F1522

[0082] After step S1152, the server 30 updates the database (S1130). Specifically, the processor 32 adds a new record to the prescription sharing information database (FIG. 5). The following information is stored in each field of the new record. "Prescription ID" field: Prescription identification information obtained in step S1131 "Shared Pharmacy ID" field: Pharmacy identification information included in the shared request data "Shared Date and Time" field: Information about the execution date and time of step S1131 "Prescription" field: Prescription image IMG1510 included in the shared request data "Patient Name" field: Patient name information included in the shared request data "Patient Request" field: Patient request information included in the shared request data "Patient Contact" field: Patient contact information included in the shared request data "Status" field: Prescription status information "New" "Update date and time" field: Information about the execution date and time of step S1130

[0083] After step S1131, the server 30 generates one-time access information (S1131). Specifically, a hash model is stored in the storage device 31. In the hash model, a function for converting any information into a hash value is described. The processor 32 determines new prescription identification information for the prescription image IMG1510 included in the shared request data. Processor 32 generates one-time access information corresponding to at least one of the prescription identification information and the execution date and time of step S1131 by inputting the prescription identification information and at least one of the execution date and time into a hash model. The one-time access information is information (e.g., a URL (Uniform Resource Locator)) for accessing the information included in the sharing request data for a certain period of time or a certain number of times. In other words, the one-time access information is configured to limit the time limit or number of times the prescription information can be viewed.

[0084] After step S1131, the server 30 transmits the one-time access information (S1132). Specifically, processor 32 refers to the pharmacy information database (FIG. 4) to identify pharmacy contact information (i.e., contact information for the shared pharmacy) associated with the pharmacy identification information obtained in step S1130. The processor 32 transmits the one-time access information obtained in step S1131 to the pharmacy client device 10 corresponding to the pharmacy contact information (for example, to the email address of the shared pharmacy).

[0085] After step S1132, the pharmacy client device 10 displays the one-time access information (S1110). Specifically, when the pharmacy user gives a user instruction to open the email sent from the server 30 to the pharmacy client device 10, the processor 12 displays a screen P110 (FIG. 8) on the display.

[0086] The screen P110 includes an operation object B1110. The operation object B 1110 is the one-time access information transmitted from the server 30 in step S1132.

[0087] After step S1110, the pharmacy client device 10 executes the prescription request (S1111). Specifically, when the pharmacy user operates the operation object B1110, the processor 12 transmits prescription request data (an example of an "access request") to the server 30. The prescription request data includes prescription identification information corresponding to the one-time access information.

[0088] After step S1111, the server 30 executes the specification of prescription information (S1133). Specifically, the processor 32 refers to the prescription sharing information database (FIG. 5) to identify the prescription information associated with the prescription identification information transmitted from the pharmacy client device 10 in step S1111.

[0089] After step S1133, the server 30 executes a prescription response (S1134). Specifically, processor 32 transmits prescription response data to pharmacy client device 10 that transmitted the prescription request data. The prescription response data transmits the prescription information obtained in step S1133.

[0090] After step S1134, the pharmacy client device 10 displays the prescription information (S1112). Specifically, the processor 12 displays a screen P111 (FIG. 8) on the display.

[0091] The screen P111 includes a display object A1110 and an image object IMG1110.

[0092] The display object A 1110 is an object that displays the following information: Patient name information Patient request information (e.g., whether or not to switch to generic drugs, desired date and time of receipt of prescription drugs, relationship between the patient and the recipient of the prescription drugs (e.g., whether the patient will receive it themselves or a family member), whether or not to bring a prescription notebook, matters to be communicated to the pharmacist) Patient contact information

[0093] An image object IMG1110 is prescription information included in the prescription response data.

[0094] (4-2) Prescription drug completion notification processing The prescription completion notification process of this embodiment will be described. Fig. 9 is a sequence diagram of a first example of the prescription completion notification process of this embodiment. Fig. 10 is a diagram showing an example of a screen displayed in the information processing of Fig. 9.

[0095] The process of FIG. 9 is triggered, for example, by a user instruction from a pharmacy user (as an example, an instruction to specify the URL of a website that provides a prescription completion notification function).

[0096] As shown in FIG. 9, the pharmacy client device 10 executes a prescription completion request (S1210). Specifically, the processor 12 displays a screen P210 (FIG. 10) on the display.

[0097] The screen P210 includes display objects A2100 to A2101 and a field object F2100 for each prescription.

[0098] Display object A2100 is an object that displays patient name information of a patient who shares a prescription with a shared pharmacy.

[0099] Display object A2101 is an object that displays patient contact information of a patient who has shared a prescription with a shared pharmacy.

[0100] The field object F2100 is an object that receives a user instruction to specify prescription status information for a target patient. Prescription identification information is assigned to each field object F2100. When the pharmacy user specifies any prescription status information in field object F2100, processor 32 sends the following information to server 30: Prescription identification information assigned to the field object F2100 specified by the pharmacy user Prescription status information specified by the pharmacy user

[0101] When the pharmacy user completes the prescription dispensing and specifies "waiting for delivery" in the field object F2100, the processor 12 sends prescription completion request data to the server 30. The prescription completion request data includes, for example, the following information: Prescription identification information assigned to field object F2100 Prescription status information "Waiting for collection" specified in field object F2100

[0102] After step S1210, the server 30 executes identification of patient contact information (S1230). Specifically, processor 32 refers to the prescription shared information database (Figure 5) to identify the shared pharmacy identification information, patient name information, and patient contact information associated with the prescription identification information included in the prescription completion request data.

[0103] After step S1230, the server 30 updates the database (S1231). Specifically, processor 32 refers to the prescription sharing information database (Figure 5) and stores the prescription status information "Waiting for delivery" included in the prescription completion request data in the "Status" field associated with the prescription identification information included in the prescription completion request data.

[0104] After step S1231, the server 30 executes a prescription completion response (S1232). Processor 32 refers to the pharmacy information database (FIG. 4) to identify the pharmacy name information associated with the shared pharmacy identification information identified in step S1230 (that is, the pharmacy name information of the shared pharmacy). The processor 32 transmits the prescription completion response data to the contact (e.g., the patient client device 50) indicated by the patient contact information identified in step S1230. The prescription completion response data includes, for example, the following information: A message indicating that a prescription has been filled at a shared pharmacy

[0105] After step S1232, the patient client device 50 displays a prescription completion notification (S1250). Specifically, the processor 52 displays screen P250 (FIG. 10) on a display (eg, the display of the patient client device 50).

[0106] Screen P250 displays the message included in the prescription completion response data.

[0107] After S1250, the pharmacy client device 10 executes a prescription drug provision request (S1211). Specifically, when a pharmacy user provides a prescription drug to a patient and performs a predetermined operation (e.g., a user instruction to display a screen for changing the prescription status), the processor 12 displays screen P212 (Figure 10) on the display. When the pharmacist has completed dispensing the prescription and has specified "waiting for delivery" in the field object F2100, the processor 12 sends prescription completion request data to the server 30. The prescription completion request data includes, for example, the following information: Prescription identification information assigned to field object F2100 - Prescription status information "Given" specified in field object F2100

[0108] After step S1211, the server 30 updates the database (S1233). Specifically, processor 32 refers to the prescription sharing information database (FIG. 5) and updates the following fields of the record associated with the prescription identification information included in the prescription completion request data: "Status" field: Prescription status information "Dispensed" included in the prescription drug completion request data "Update date and time" field: Information about the execution date and time of step S1233

[0109] (5) Summary of this embodiment According to this embodiment, even if a pharmacy does not have a dedicated environment for handling prescriptions as electronic data, it can handle prescriptions as electronic data as long as it has a general-purpose environment (e.g., a web browser). As a result, the restrictions on pharmacies and patients for handling prescriptions as electronic data can be reduced.

[0110] According to this embodiment, the server 30 may acquire the pharmacy identification information embedded in the code image placed in the pharmacy PH1 from the patient client device 50. This allows the pharmacy to accept prescription information from the patient simply by distributing the code image in which its own pharmacy identification information is embedded.

[0111] According to this embodiment, when the server 30 receives a prescription completion notification indicating that the prescription corresponding to the prescription information has been completed from the pharmacy client device 10, the server 30 may send the prescription completion notification to a contact point designated by the patient. This can reduce the time the patient has to wait at the pharmacy between sending the prescription information and receiving the prescription (i.e., waiting time).

[0112] (6) Variations A modified example will now be described.

[0113] (6-1) Variation 1 Modification 1 will be described below. Modification 1 is an example that achieves the same effect as this embodiment in a form other than a marker image.

[0114] (6-1-1) Overview of Modification 1 An outline of Modification 1 will be described below. Fig. 11 is an explanatory diagram of an outline of Modification 1.

[0115] 11A, a pharmacy application provided by the pharmacy is installed on the patient client device 50. The pharmacy application is assigned pharmacy identification information.

[0116] In response to the patient's instructions, the patient client device 50 transmits to the server 30 the pharmacy identification information assigned to the pharmacy application and prescription information relating to the patient's prescription.

[0117] As in FIG. 3A, the server 30 generates one-time access information corresponding to the prescription information sent from the patient client device 50 and sends the one-time access information to the pharmacy client device 10 located in the pharmacy PH1.

[0118] FIG. 11B is similar to FIG. 3B.

[0119] (6-1-2) Prescription sharing processing The prescription sharing process of the first modification will be described.

[0120] The prescription sharing process of the first modification is triggered, for example, by a user instruction from the patient (as an example, an instruction to launch a pharmacy application).

[0121] In the prescription sharing process of the first modification, obtaining the pharmacy ID (S1150) is omitted.

[0122] In step S1152, processor 52 includes the pharmacy identification information assigned to the pharmacy application in the shared request data instead of the pharmacy identification information obtained in step S1150.

[0123] Modification 1 is also applicable to cases where information (for example, a URL to which pharmacy identification information is assigned) is written on a website (for example, a pharmacy website). In this case, the prescription sharing process of the first modification is triggered by a user instruction from the patient (for example, an instruction to specify a URL listed on the pharmacy's website). In step S1152, processor 52 includes the pharmacy identification information assigned to the URL specified by the patient in the sharing request data, instead of the pharmacy identification information obtained in step S1150.

[0124] (6-1-3) Summary of Modification 1 According to the first modification, the server 30 may acquire the pharmacy identification information assigned to the patient client device 50 from the patient client device 50. This allows the pharmacy to accept prescription information from the patient simply by assigning its own pharmacy identification information to the patient client device 50 (for example, by distributing a pharmacy application assigned with the pharmacy identification information to the patient).

[0125] According to the first modification, the server 30 may acquire the pharmacy identification information listed on the website from the patient client device 50. This allows the pharmacy to accept prescription information from the patient simply by assigning its own pharmacy identification information to the website (e.g., by distributing a pharmacy application to which the pharmacy identification information is assigned to the patient).

[0126] (6-2) Variation 2 Modification 2 will now be described. Modification 2 is an example in which a patient designates a pharmacy to pick up a prescription after designating a corporation.

[0127] (6-2-1) Prescription sharing process A description will be given of prescription sharing processing according to Modification 2. Fig. 12 is a sequence diagram of prescription sharing processing according to Modification 2. Fig. 13 is a diagram showing an example of a screen displayed in the information processing of Fig. 12.

[0128] The process of FIG. 12 is triggered, for example, by a patient user instruction (for example, an instruction to launch a camera application installed on the patient client device 50).

[0129] As shown in FIG. 12, the patient client device 50 acquires a corporate ID (S2150). Specifically, the processor 52 displays a screen P250 (FIG. 13) on the display.

[0130] The screen P250 includes an operation object B2500.

[0131] Operation object B 2500 is an object that accepts a user instruction to acquire code image IMG 2500. Corporate identification information is embedded in code image IMG 2500.

[0132] When the patient photographs the code image IMG2500 with the camera (not shown) of the patient client device 50 and operates the operation object B2500, the processor 52 identifies the corporate identification information embedded in the code image IMG2500.

[0133] After step S2150, the patient client device 50 acquires a pharmacy ID (S2151). Specifically, the processor 52 displays a screen P251 (FIG. 13) on the display.

[0134] The screen P251 includes an operation object B2510 and a field object F1510.

[0135] The field object F2510 displays the pharmacy name information associated with the corporate identification information obtained in step S2510 in the pharmacy information database (FIG. 4). Each piece of pharmacy name information is assigned pharmacy identification information associated with the pharmacy name information in the pharmacy information database. The field object F2510 is an object that accepts a user instruction to specify the pharmacy name information (i.e., pharmacy identification information).

[0136] The operation object B2510 is an object that receives a user instruction to confirm an input to the field object F2510.

[0137] When a patient specifies the pharmacy name information of the pharmacy where they wish to receive their prescription medication (i.e., the destination to which the prescription information will be sent) in field object F2510 and operates operation object B2510, processor 52 identifies the pharmacy identification information assigned to the pharmacy name information specified in field object F2510.

[0138] After step S2151, the patient client device 50 acquires prescription information (S1151) in the same manner as in FIG.

[0139] After step S1151, the patient client device 50 executes a prescription sharing request (S2152). Specifically, when the target patient inputs any information into the field objects F1520 to F1522 and operates the operation object B1520, the processor 52 transmits the sharing request data to the server 30. The sharing request data includes, for example, the following information: Pharmacy identification information obtained in step S2151 A prescription image IMG1510 stored in the storage device 51 - Patient request information entered in field object F1520 Patient contact information entered in field object F1521 - Patient name information entered in field object F1522

[0140] After step S1152, the server 30 executes the processes from updating the database (S1130) to issuing a prescription response (S1134) in the same manner as in FIG.

[0141] After step S11130, the pharmacy client device 10 executes the processes of displaying one-time access information (S1110) to displaying prescription information (S1112) in the same manner as in FIG.

[0142] (6-2-2) Summary of Modification 2 According to variant example 2, even when a corporation distributes a code image to which corporate identification information is assigned (for example, by posting the code image in an advertising medium), the same effect as in this embodiment can be obtained through the code image.

[0143] (7) Other variations Other modifications will be described.

[0144] The storage device 11 may be connected to the pharmacy client device 10 via a network NW. The storage device 31 may be connected to the server 30 via a network NW. The storage device 51 may be connected to the patient client device 50 via a network NW.

[0145] In this embodiment, an example is shown in which the patient inputs the patient name information and patient contact information in step S1151, but the scope of this embodiment is not limited to this. In this embodiment, the input of the patient name information and patient contact information may be omitted. Specifically, patient identification information for identifying a patient is stored in the storage device 51. Patient identification information, patient name information, and patient contact information are stored in association with each other in the storage device 31. When the patient operates the operation object B1510, the processor 52 transmits the patient identification information stored in the storage device 11 to the server 30. The processor 32 generates a screen P210 using the patient name information and patient contact information associated with the patient identification information transmitted from the patient client device 50.

[0146] In the present embodiment, an example in which the code image is placed in a pharmacy has been described, but the code image may be placed in a place or medium other than a pharmacy. The place or medium other than a pharmacy includes, for example, at least one of the following: Hospital (for example, the hospital where the doctor who issued the prescription is affiliated) Drugstores -Medication notebooks distributed to patients Pharmacy advertising (e.g., flyers or signs)

[0147] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above-described embodiments. Furthermore, the above-described embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above-described embodiments and modifications can be combined. [Explanation of symbols]

[0148] 1: Information processing system 10: Pharmacy client device 11:Storage device 12: Processor 13: Input / output interface 14: Communication interface 22: Processor 30: Server 31:Storage device 32: Processor 33: Input / output interface 34: Communication interface 50: Patient client device 51:Storage device 52: Processor 53: Input / output interface 54: Communication interface

Claims

1. A server connectable to a patient client device used by a patient and a pharmacy client device used by a pharmacy user, means for obtaining, from the patient client device, pharmacy identification information that identifies the pharmacy and prescription information for the patient; means for generating one-time access information corresponding to prescription information obtained from the patient client device; means for transmitting the one-time access information to the pharmacy client device; means for transmitting the prescription information to the pharmacy client device in response to an access request from the pharmacy client device via the one-time access information; server.

2. the acquiring means acquires, from the patient client device, pharmacy identification information embedded in a code image placed at the pharmacy; The server of claim 1 .

3. the obtaining means obtains from the patient client device pharmacy identification information assigned to the patient client device; The server according to claim 1 or 2.

4. The acquiring means acquires, from the patient client device, pharmacy identification information assigned to information designated by the patient in response to the patient's designation of the information on a website including information assigned with the pharmacy identification information. The server according to any one of claims 1 to 3.

5. the acquiring means acquires patient contact information relating to contact points of the patient; a means for receiving, from the pharmacy client device, a prescription completion notification indicating that the prescription corresponding to the prescription information has been completed; and means for transmitting the prescription completion notification to a contact person corresponding to the patient contact information in response to the prescription completion notification. The server according to any one of claims 1 to 4.

6. A program for causing a computer to function as each of the means according to any one of claims 1 to 5.

7. A method for sharing prescription information of a patient with a pharmacy using a server connectable to a patient client device used by a patient and a pharmacy client device used by a user of the pharmacy, the method comprising: The server obtains, from the patient client device, pharmacy identification information that identifies the pharmacy and prescription information for the patient; generating, by the server, one-time access information corresponding to prescription information obtained from the patient client device; the server sending the one-time access information to the pharmacy client device; the server transmitting the prescription information to the pharmacy client device in response to an access request from the pharmacy client device via the one-time access information. method.

Images