JP7733376B2 - Server, client device, program, and information processing method - Google Patents

Description

The present invention relates to a server, a client device, a program, and an information processing method.

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.

JP 2016-181296 A

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.

The purpose of this invention is to reduce the restrictions on pharmacies and patients in handling prescriptions as electronic data.

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.

1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; FIG. 2 is a functional block diagram of the information processing system of FIG. 1 . FIG. 1 is an explanatory diagram of an overview of the present embodiment. FIG. 2 is a diagram showing a data structure of a pharmacy information database according to the present embodiment. FIG. 2 is a diagram showing the data structure of a prescription sharing information database according to the present embodiment. FIG. 10 is a sequence diagram of a prescription sharing process according to this embodiment. 7A and 7B are diagrams showing examples of screens displayed in the information processing of FIG. 6; 7A and 7B are diagrams showing examples of screens displayed in the information processing of FIG. 6; FIG. 10 is a sequence diagram of a first example of a prescription drug completion notification process according to the present embodiment. 10A and 10B are diagrams showing examples of screens displayed in the information processing of FIG. 9; FIG. 10 is an explanatory diagram of an overview of Modification 1. FIG. 10 is a sequence diagram of a prescription sharing process according to the second modified example. 13A and 13B are diagrams showing examples of screens displayed in the information processing of FIG. 12;

One embodiment of the present invention will now be described in detail with reference to the drawings. In the drawings used to explain the embodiment, identical components will generally be assigned the same reference numerals, and repeated explanations will be omitted.

(1) Configuration of Information Processing System The configuration of the information processing system will be described. 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.

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 (e.g., the Internet or an intranet) NW.

The pharmacy client device 10 is a computer (an example of an "information processing device") that sends 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 staff member at the pharmacy. The pharmacy client device 10 is, for example, a smartphone, tablet terminal, or personal computer.

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

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.

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

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

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 a hard disk).

The programs include, for example, the following programs:
- OS (Operating System) programs - Applications that execute information processing (for example, web browsers)

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

The processor 12 is configured to realize the functions of the pharmacy client device 10 by running programs 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 of these.

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

The communication interface 14 is configured to control communication between the pharmacy client device 10 and the server 30.

(1-2) Configuration of the Patient Client Device The configuration of the patient client device 50 will be described.

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

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

The programs include, for example, the following programs:
・OS programs ・Application programs that execute information processing (for example, web browsers)

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

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

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.

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

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

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

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 a hard disk).

The programs include, for example, the following programs:
・OS programs ・Application programs that perform information processing

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

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

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.

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

(2) Overview of the Embodiment The overview of this embodiment will be described below with reference to FIG.

3A , in response to a patient's instruction, the patient client device 50 acquires pharmacy identification information embedded in a code image IMG (e.g., at least one of a character string, a graphic, a barcode image, and a two-dimensional code image) 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 .

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 at the pharmacy PH1.

As shown in FIG. 3B, in response to instructions from a pharmacy user (e.g., a pharmacist or pharmacy clerk) at pharmacy PH1, the pharmacy client device 10 sends a prescription request to the server 30.

In response to the prescription request, the server 30 sends prescription information to the pharmacy client device 10.

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

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

(3-1) Pharmacy Information Database The pharmacy information database of this embodiment will be described below. Fig. 4 is a diagram showing the data structure of the pharmacy information database of this embodiment.

Pharmacy information is stored in the pharmacy information database of Fig. 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.

The "Corporate ID" field stores corporate identification information. Corporate identification information identifies a corporation that operates multiple pharmacies.

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

The "Pharmacy ID" field stores pharmacy identification information. Pharmacy identification information is information that identifies a pharmacy.

The "Pharmacy Name" field stores pharmacy name information. Pharmacy name information is information about the pharmacy name.

The "Address" field stores address information. The address information is information about the pharmacy's address.

The "Number of Pharmacists" field stores information about the number of pharmacists at the pharmacy.

The "Pharmacy Contact" field stores pharmacy contact information. Pharmacy contact information is information related to the pharmacy's contact information (e.g., at least one of a telephone number, a facsimile number, an email address, and a web service account).

(3-2) Prescription Shared Information Database The prescription shared information database of this embodiment will be described below. Fig. 5 is a diagram showing the data structure of the prescription shared information database of this embodiment.

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.

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

The "Shared Pharmacy ID" field stores the pharmacy identification information of the pharmacy that shares prescription information (hereinafter referred to as the "shared pharmacy").

The "Shared Date and Time" field stores the 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.

The "Prescription" field stores a prescription image (an example of "Prescription Information").

The "Patient Name" field stores patient name information. Patient name information is information about the patient's name.

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 to switch to generic drugs ・Desired date and time of receipt of prescription drugs ・Relationship between the patient and the recipient of prescription drugs (for example, whether the patient himself/herself will receive them, or whether a family member will receive them)
- Whether or not you bring your medication notebook - What to communicate to the pharmacist

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

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 that are 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 provided to the patient by the pharmacy

The "Update Date and Time" field stores update date and time information. This information is about the date and time when the prescription status information was updated.

(4) Information Processing The information processing of this embodiment will be described.

(4-1) Prescription sharing processing The prescription sharing processing of this embodiment will be described. Fig. 6 is a sequence diagram of the prescription sharing processing 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.

The trigger for the processing in Figure 6 is, for example, a patient user instruction (for example, an instruction to launch a camera application installed on the patient client device 50).

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

Screen P150 includes operation object B1500.

Operation object B1500 is an object that accepts user instructions to obtain code image IMG1500.

When the patient photographs the code image IMG1500 with the 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.

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.

Screen P151 includes operation object B1510.

The operation object B1510 is an object that accepts a user instruction to acquire a prescription image IMG1510 of the target patient.
The image object IMG1510 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 read from a storage device connected to the patient client device 50 - Images read from the storage device 51

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.

Screen P152 includes operation object B1520 and field objects F1520 to F1522.

Field object F1520 is an object that accepts input of patient request information.

Field object F1521 is an object that accepts input of patient contact information.

Field object F1522 is an object that accepts input of patient name information.

Operation object B1520 is an object that accepts user instructions to confirm input into field objects F1520 to F1522.

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 sharing request data to the server 30.
The sharing request data includes, for example, the following information:
The pharmacy identification information obtained in step S1150. The prescription image IMG1510 stored in the storage device 51.
Patient request information entered in a field object F1520; Patient contact information entered in a field object F1521; Patient name information entered in a field object F1522.

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 sharing request data "Shared date and time" field: Information regarding the execution date and time of step S1131 "Prescription" field: Prescription image IMG1510 included in the sharing 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

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.
The 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/or the execution date and time into a hash model. The one-time access information is information (e.g., a uniform resource locator (URL)) 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.

After step S1131, the server 30 transmits one-time access information (S1132).
Specifically, the processor 32 refers to the pharmacy information database (FIG. 4) to identify the pharmacy contact information (i.e., the contact information of 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).

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

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.

After step S1110, the pharmacy client device 10 executes a 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.

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.

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

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.

Screen P111 includes display object A1110 and image object IMG1110.

The display object A 1110 is an object that displays the following information:
・Patient name information ・Patient request information (for example, 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 (for example, whether the patient will receive it themselves or a family member), whether or not to bring a medication record book, and matters to be communicated to the pharmacist)
・Patient contact information

Image object IMG1110 is prescription information included in the prescription response data.

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

The trigger for the processing in Figure 9 is, for example, a user instruction from a pharmacy user (for example, an instruction to specify the URL of a website that provides a prescription completion notification function).

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

Screen P210 includes display objects A2100-A2101 and field object F2100 for each prescription.

Display object A2100 is an object that displays the patient name information of a patient who has shared a prescription with a shared pharmacy.

Display object A2101 is an object that displays patient contact information for patients who have shared prescriptions with a shared pharmacy.

The field object F2100 is an object that receives a user instruction for specifying prescription status information of 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.

When the pharmacy user completes the dispensing of the prescription 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 the field object F2100 Prescription status information "waiting for delivery" specified in the field object F2100

After step S1210, the server 30 identifies patient contact information (S1230).
Specifically, the processor 32 refers to the prescription sharing 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.

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.

After step S1231, the server 30 executes a prescription drug completion response (S1232).
The 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 (i.e., the pharmacy name information of the shared pharmacy).
The processor 32 sends 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

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 (e.g., the display of the patient client device 50).

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

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 the field object F2100 Prescription status information "Given" specified in the field object F2100

After step S1211, the server 30 updates the database (S1233).
Specifically, the 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

(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, it is possible to reduce the restrictions on pharmacies and patients in handling prescriptions as electronic data.

According to this embodiment, the server 30 may obtain, from the patient client device 50, the pharmacy identification information embedded in the code image placed at the pharmacy PH1. This allows the pharmacy to accept prescription information from the patient simply by distributing the code image with its own pharmacy identification information embedded.

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

(6) Modifications Modifications will now be described.

(6-1) Modification 1
Modification 1 will be described below. Modification 1 is an example in which the same effect as in this embodiment can be obtained in a form other than a marker image.

(6-1-1) Overview of Modification 1 An overview of Modification 1 will be described. FIG.

As shown in FIG. 11A, a pharmacy application provided by the pharmacy is installed on the patient client device 50. The pharmacy application is assigned pharmacy identification information.

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

As shown in Figure 3A, the server 30 generates one-time access information corresponding to the prescription information transmitted from the patient client device 50 and transmits the one-time access information to the pharmacy client device 10 located at the pharmacy PH1.

Figure 11B is similar to Figure 3B.

(6-1-2) Prescription Sharing Processing The prescription sharing processing of the first modification will be described.

The trigger for the prescription sharing process in variant example 1 is, for example, a user instruction from the patient (for example, an instruction to launch a pharmacy application).

In the prescription sharing process of variant 1, obtaining the pharmacy ID (S1150) is omitted.

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

Variation 1 can also be applied when a website (e.g., a pharmacy website) contains information (e.g., a URL to which pharmacy identification information is assigned) to which pharmacy identification information is assigned.
In this case, the prescription sharing process of variant example 1 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, the 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.

(6-1-3) Summary of Modification 1 According to Modification 1, the server 30 may acquire, from the patient client device 50, the pharmacy's pharmacy identification information assigned to 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 to which the pharmacy identification information is assigned to the patient).

According to variant 1, the server 30 may obtain 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).

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

(6-2-1) Prescription Sharing Processing The following describes 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.

The trigger for the processing in Figure 12 is, for example, a patient user instruction (for example, an instruction to launch a camera application installed on the patient client device 50).

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.

Screen P250 includes operation object B2500.

Operation object B2500 is an object that accepts user instructions to obtain code image IMG2500. Corporate identification information is embedded in code image IMG2500.

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.

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.

Screen P251 includes operation object B2510 and field object F1510.

Field object F2510 displays the pharmacy name information associated with the corporate identification information obtained in step S2510 in the pharmacy information database (Figure 4). Each pharmacy name information is assigned pharmacy identification information associated with the pharmacy name information in the pharmacy information database. Field object F2510 is an object that accepts user instructions to specify pharmacy name information (i.e., pharmacy identification information).

Operation object B2510 is an object that accepts user instructions to confirm input to field object F2510.

When a patient specifies the pharmacy name information of the pharmacy where they wish to receive their prescription medication (i.e., the destination of the prescription information) 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.

After step S2151, the patient client device 50 acquires prescription information (S1151), as in Figure 6.

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 sharing request data to the server 30.
The sharing request data includes, for example, the following information:
The pharmacy identification information obtained in step S2151 The prescription image IMG1510 stored in the storage device 51
Patient request information entered in a field object F1520; Patient contact information entered in a field object F1521; Patient name information entered in a field object F1522.

After step S1152, the server 30 performs the steps from database update (S1130) to prescription response (S1134), as shown in Figure 6.

After step S11130, the pharmacy client device 10 executes the steps from displaying one-time access information (S1110) to displaying prescription information (S1112), as shown in Figure 6.

(6-2-2) Summary of Modification 2 According to Modification 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.

(7) Other Modifications Other modifications will now be described.

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

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 the screen P210 using the patient name information and patient contact information associated with the patient identification information transmitted from the patient client device 50.

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 to which the doctor who issued the prescription belongs)
・Drugstores ・Medication notebooks distributed to patients ・Pharmacy advertisements (for example, flyers or signs)

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 embodiments. Furthermore, the above embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above embodiments and modifications can be combined.

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 (7)

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. 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 . 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. 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. 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. A program for causing a computer to function as any of the means described in claims 1 to 5. 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.