Server, program, and information processing method

Abstract

To provide an environment in which various information can be exchanged between a clinic and a pharmacy.SOLUTION: A server is connectable to a clinic client device arranged in a clinic and a pharmacy client device arranged in a pharmacy includes means for acquiring a linkage request from the clinic client device or the pharmacy client device, means for acquiring an approval of the linkage request from the clinic client device or the pharmacy client device, and means for storing clinic information regarding the clinic and pharmacy information regarding the pharmacy in association, when the approval is acquired.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] In recent years, services that connect medical institutions via networks have been attracting attention. For example, Patent Document 1 discloses a technique for managing the authority to execute medical-related processing in a more suitable manner even in a situation where the processing is executed via a network. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-067197 Summary of the Invention [Problem to be solved by the invention]

[0004] Various information, including prescriptions, needs to be shared between clinics and pharmacies. However, the technology of Patent Document 1 does not disclose or suggest an environment in which information can be exchanged between clinics and pharmacies.

[0005] An object of the present invention is to provide an environment in which various information can be exchanged between a clinic and a pharmacy. [Means for solving the problem]

[0006] One aspect of the present invention is A server connectable to a clinic client device located in a clinic and a pharmacy client device located in a pharmacy, a means for receiving a link request from the clinic client device or the pharmacy client device; It is provided with means for obtaining approval for the cooperation request from the clinic client device or the pharmacy client device. When the approval is obtained, it is provided with means for associating and storing clinic information regarding the clinic and pharmacy information regarding the pharmacy. It is a server.

Brief Description of Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Mode for Carrying Out 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 denoted by the same reference numerals, and the repeated description thereof will be omitted.

[0009] (1) Configuration of the 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 according to 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 clinic client device 20, a server 30, and a patient client device 50. The pharmacy client device 10, the clinic client device 20, 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 a request 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 pharmacy staff member belonging to a pharmacy. The pharmacy client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0012] The clinic client device 20 is a computer (an example of an "information processing device") that sends requests to the server 30. The clinic client device 20 is operated by a clinic user. The clinic user is, for example, a doctor or a medical staff member belonging to the clinic. The clinic client device 20 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0013] 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. The patient client device 50 is, for example, a smartphone, a tablet terminal, or a personal computer.

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

[0015] (1-1) Configuration of the pharmacy client device The configuration of the pharmacy client device 10 will be described.

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

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

[0018] The program includes, for example, the following programs. · Programs of the OS (Operating System) · Programs of applications that execute information processing (e.g., web browsers)

[0019] The data includes, for example, the following data. · Databases referred to in information processing · Data obtained by executing information processing (i.e., the execution results of information processing)

[0020] The processor 12 is configured to realize the functions of the pharmacy client device 10 by starting the 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 thereof.

[0021] The input / output interface 13 is configured to acquire a user's instruction from an input device connected to the pharmacy client device 10 and 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.

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

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

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

[0025] The storage device 21 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).

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

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

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

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

[0030] The communication interface 24 is configured to control communications between the clinic client device 20 and the server 30 .

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

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

[0033] 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).

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

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

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

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

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

[0039] (1-4) Configuration of the server The configuration of the server 30 will be described.

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

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

[0042] The programs include, for example, the following programs. · Program of the OS · Program of an application that executes information processing

[0043] The data includes, for example, the following data. · Database referred to in information processing · Execution result of information processing

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

[0045] The input / output interface 33 is configured to obtain a user's instruction from an input device connected to the server 30 and 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.

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

[0047] (2) Overview of the embodiment An outline of this embodiment will be described. The server 30 of this embodiment provides a linking function and a prescription sharing function.

[0048] (2-1) Overview of the collaboration function An overview of the link function of this embodiment will be described. FIG. 3 is an explanatory diagram of an outline of the link function of this embodiment.

[0049] As shown in FIG. 3A, in response to an instruction from a clinic user of clinic CL1, clinic client device 20 notifies pharmacy client device 10 via server 30 of an application for cooperation with pharmacy PH1.

[0050] 3B, in response to an instruction from a pharmacy user of pharmacy PH1, pharmacy client device 10 approves the cooperation application from clinic CL1 via server 30. The cooperation application is notified to pharmacy client device 10.

[0051] This establishes a partnership between clinic CL1 and pharmacy PH1.

[0052] (2-2) Overview of prescription sharing function An overview of the prescription sharing function of this embodiment will be described. FIG. 4 is an explanatory diagram illustrating an outline of the prescription sharing function of this embodiment.

[0053] As shown in Figure 4A, when a patient who has received medical treatment at clinic CL1 specifies an arbitrary pharmacy PH1, in response to the clinic user's instructions, the clinic client device 20 transmits prescription information to the pharmacy client device 10 located at pharmacy PH1 via the server 30.

[0054] As shown in Figure 4B, when a pharmacy user completes the prescription using the prescription information sent from the server 30, in response to the pharmacy user's instructions, the pharmacy client device 10 sends a prescription completion notification to the clinic client device 20 located in clinic CL1 via the server 30.

[0055] The clinic client device 20 displays a prescription completion notification.

[0056] As a result, the server 30 allows the clinic CL1 and the pharmacy PH1, which are linked to each other, to share prescription information and notify the patient that the prescription has been completed.

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

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

[0059] Pharmacy information is stored in the pharmacy information database of Figure 5. The pharmacy information is information relating to pharmacies. The pharmacy information database includes 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 the others.

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

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

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

[0063] In the "Number of pharmacists" field, information on the number of pharmacists is stored. The information on the number of pharmacists is information regarding the number of pharmacists in the pharmacy.

[0064] In the "Pharmacy contact" field, pharmacy contact information is stored. The pharmacy contact information is information regarding the contact details of the pharmacy (for example, at least one of a telephone number, a facsimile number, an email address, and an account for a web service).

[0065] (3-2) Clinic information database The clinic information database of this embodiment will be described. FIG. 6 is a diagram showing the data structure of the clinic information database of this embodiment.

[0066] Clinic information is stored in the clinic information database shown in FIG. 6. The clinic information is information regarding the clinic. The clinic information database includes a "Clinic ID" field, a "Clinic name" field, an "Address" field, a "Number of doctors" field, a "Medical department" field, and a "Clinic contact" field. Each field is associated with each other.

[0067] In the "Clinic ID" field, clinic identification information is stored. The clinic identification information is information for identifying the clinic.

[0068] In the "Clinic name" field, clinic name information is stored. The clinic name information is information regarding the clinic name.

[0069] In the "Address" field, address information is stored. The address information is information regarding the address of the clinic.

[0070] In the "Number of doctors" field, information on the number of doctors is stored. The information on the number of doctors is information regarding the number of doctors in the clinic.

[0071] Clinic subject information is stored in the "Clinic Subject" field. The clinic subject information is information regarding clinic subjects that the clinic can handle.

[0072] Clinic contact information is stored in the "Clinic Contact" field. The clinic contact information is information regarding the contact information of the clinic (for example, at least one of a telephone number, a facsimile number, an email address, and an account of a web service).

[0073] (3-3) Patient Information Database The patient information database of the present embodiment will be described. FIG. 7 is a diagram showing the data structure of the patient information database of the present embodiment.

[0074] Patient information is stored in the patient information database of FIG. 7. The patient information is information regarding the patient. The patient information database includes a "Patient ID" field, a "Patient Name" field, a "Patient Attribute" field, and a "Patient Contact" field. Each field is associated with each other.

[0075] Patient identification information is stored in the "Patient ID" field. The patient identification information is information for identifying the patient.

[0076] Patient name information is stored in the "Patient Name" field. The patient name information is information regarding the patient name.

[0077] Patient attribute information is stored in the "Patient Attribute" field. The patient attribute information is information regarding the attributes of the patient. The "Patient Attribute" field includes a "Gender" field and an "Age" field.

[0078] Gender information is stored in the "Gender" field. The gender information is information regarding the gender of the patient.

[0079] Age information is stored in the "Age" field. The age information is information regarding the age of the patient.

[0080] Patient contact information is stored in the "Patient Contact" field. The patient contact information is information regarding the contact details of the patient (e.g., at least one of a phone number, a fax number, an email address, and an account of a web service).

[0081] (3-4) Physician Information Database The physician information database of the present embodiment will be described. FIG. 8 is a diagram showing the data structure of the physician information database of the present embodiment.

[0082] Physician information is stored in the physician information database of FIG. 8. The physician information is information regarding the physician. The physician information database includes a "Physician ID" field, a "Physician Name" field, and a "Clinic ID" field. Each field is associated with each other.

[0083] Physician identification information is stored in the "Physician ID" field. The physician identification information is information for identifying the physician.

[0084] Physician name information is stored in the "Physician Name" field. The physician name information is information regarding the name of the physician.

[0085] Clinic identification information of the clinic to which the physician belongs is stored in the "Clinic ID" field.

[0086] (3-5) Linkage Information Database The linkage information database of the present embodiment will be described. FIG. 9 is a diagram showing the data structure of the linkage information database of the present embodiment.

[0087] Linkage information is stored in the linkage information database of FIG. 9. The linkage information is information regarding the linkage relationship between the clinic and the pharmacy. The linkage information database includes a "linkage ID" field, a "pharmacy ID" field, and a "clinic ID" field. Each field is associated with each other.

[0088] Linkage identification information is stored in the "linkage ID" field. The linkage identification information is information that identifies the linkage between a pharmacy and a clinic.

[0089] Pharmacy identification information is stored in the "pharmacy ID" field.

[0090] Clinic identification information of the clinic that links with the pharmacy is stored in the "clinic ID" field.

[0091] (3-6) Prescription sharing information database The prescription sharing information database of this embodiment will be described. FIG. 10 is a diagram showing the data structure of the prescription sharing information database of this embodiment.

[0092] Prescription sharing information is stored in the prescription sharing information database of FIG. 10. The prescription sharing information is information related to the sharing of prescriptions. The prescription sharing information database includes a "prescription ID" field, a "patient ID" field, a "clinic ID" field, a "shared pharmacy ID" field, a "prescription" field, a "sharing date and time" field, a "prescription" field, a "message" field, and a "status" field. Each field is associated with each other.

[0093] Prescription identification information is stored in the "prescription ID" field. The prescription identification information is information that identifies a prescription.

[0094] Patient identification information of the patient (hereinafter referred to as the "target patient") for whom the prescription is made is stored in the "patient ID" field.

[0095] The "Clinic ID" field stores the clinic identification information of the clinic that issues the prescription.

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

[0097] 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 clinic and the shared pharmacy.

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

[0099] The "Message" field stores a message. The message is a message exchanged between the clinic and the shared pharmacy. The message may be, for example, at least one of text, audio, a still image, and a video.

[0100] 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

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

[0102] (4-1) Collaboration processing The cooperative processing of this embodiment will be described below with reference to Fig. 11. Fig. 12 is a diagram showing an example of a screen displayed in the information processing of Fig. 11.

[0103] The trigger for the process in FIG. 11 is, for example, a user instruction from a clinic user (e.g., an instruction for specifying a cooperation function).

[0104] As shown in FIG. 11, the clinic client device 20 executes acquisition of a user instruction (S1120). Specifically, the processor 22 displays the screen P120 (FIG. 12) on the display.

[0105] The screen P120 includes an operation object B1200 and field objects F1200 to F1201.

[0106] The field object F1200 is an object that receives a user instruction for designating pharmacy identification information of a candidate pharmacy for cooperation (hereinafter referred to as "cooperation candidate pharmacy") from among pharmacies corresponding to the pharmacy information stored in the pharmacy information database (FIG. 5) (hereinafter referred to as "member pharmacies").

[0107] The field object F1201 is an object that receives a user instruction for registering information of a pharmacy other than the pharmacy corresponding to the pharmacy information stored in the pharmacy information database (FIG. 5) (hereinafter referred to as "non-member pharmacy") (e.g., pharmacy name, branch name, address, telephone number, and facsimile number of the non-member pharmacy). For non-member pharmacies, prescription information cannot be shared, but it can be presented to the patient as a candidate for the transmission destination of the prescription information (e.g., the transmission destination of the prescription image by facsimile).

[0108] The operation object B1200 is an object that receives a user instruction for finalizing an input to the field object F1200 or F1201.

[0109] After step S1120, the clinic client device 20 executes a cooperation request (S1121). Specifically, when a user of the clinic client device 20 inputs arbitrary pharmacy identification information to the field object F1200 and operates the operation object B1200, the processor 22 transmits cooperation request data to the server 30. The cooperation request data includes, for example, the following information. · Clinic identification information of the clinic where the clinic client device 20 is located · Pharmacy identification information given to the field object F1200

[0110] After step S1121, the server 30 executes a cooperation request notification (S1130). Specifically, the processor 32 refers to the pharmacy information database (FIG. 5) to identify pharmacy contact information associated with the pharmacy identification information included in the cooperation request data. The processor 32 refers to the clinic information database (FIG. 6) to identify clinic information associated with the clinic identification information included in the cooperation request data. The processor 32 transmits the identified clinic information (for example, clinic name information) to the contact corresponding to the identified pharmacy contact information.

[0111] After step S1130, the pharmacy client device 10 executes acquisition of a user instruction (S1110). Specifically, the processor 12 displays the screen P110 (FIG. 12) on the display.

[0112] The screen P110 includes operation objects B1100 to B1104. Clinic identification information is associated with the operation objects B1101 to B1104, respectively.

[0113] The operation objects B1100 and B1102 are objects for receiving a user instruction to approve a cooperation request from the clinic.

[0114] The operation objects B1101 and B1103 are objects that receive user instructions to reject the cooperation request from the clinic.

[0115] The operation object B1104 is an object that receives user instructions to cancel the cooperation with the already cooperated clinic.

[0116] After step S1110, the pharmacy client device 10 executes a cooperation approval request (S1111). Specifically, when the pharmacy user operates the operation object B1100, the processor 12 sends the cooperation approval request data to the server 30. The cooperation approval request data includes, for example, the following information. · Pharmacy identification information of the pharmacy · Clinic identification information assigned to the operation object B1100 operated by the user

[0117] After step S1111, the server 30 executes an update of the database (S1131). Specifically, when the processor 32 obtains the cooperation approval request data from the pharmacy client device 10, it adds a new record to the cooperation information database (Figure 9). The following information is stored in each field of the new record. · "Cooperation ID" field: New cooperation identification information · "Pharmacy ID" field: Pharmacy identification information included in the cooperation approval request data · "Clinic ID" field: Clinic identification information included in the cooperation approval request data

[0118] After step S1131, the server 30 executes a cooperation completion notification (S1132). Specifically, the processor 32 sends a cooperation completion notification to the pharmacy client device 10 and the clinic client device 20.

[0119] After step S1132, the clinic client device 20 executes a cooperation completion display (S1122). Specifically, the processor 22 displays the screen P121 (FIG. 12) on the display.

[0120] The screen P121 includes a message indicating that the cooperation with the candidate pharmacy for cooperation (pharmacy ID = PH01) has been completed.

[0121] After step S1112, the pharmacy client device 10 executes a cooperation completion display (S1112). Specifically, the processor 12 displays the screen P111 (FIG. 12) on the display.

[0122] The screen P111 includes a message indicating that the cooperation with the clinic (clinic ID = CL01) that made the cooperation request has been completed.

[0123] (4-2) Prescription Sharing Process The prescription sharing process of the present embodiment will be described. FIG. 13 is a sequence diagram of the prescription sharing process of the present embodiment. FIG. 14 is a diagram showing an example of a screen displayed in the information processing of FIG. 13.

[0124] The trigger for the process in FIG. 13 is, for example, a user instruction from a clinic user (for example, an instruction for specifying a prescription sharing function).

[0125] As shown in FIG. 13, the clinic client device 20 executes acquisition of prescription information (S1220). Specifically, the processor 22 displays the screen P220 (FIG. 14) on the display.

[0126] The screen P220 includes an operation object B2200, field objects F2200 to F2202, and an image object IMG2200.

[0127] The field object F2200 is an object that accepts input of patient identification information of the target patient.

[0128] The field object F2201 is an object that receives input of pharmacy identification information of a shared pharmacy.

[0129] The field object F2202 is an object that receives input of a message to the shared pharmacy.

[0130] Image object IMG2200 is an image of a prescription. Image object IMG2200 is one of the following: An image captured by a camera (not shown) included in the clinic client device 20 An image captured by a camera (not shown) connected to the clinic client device 20 Images read from a storage device connected to the clinic client device 20 Image read from storage device 21

[0131] The operation object B2200 is an object that receives inputs to the field objects F2200 to F2202 and a user instruction for finalizing the image object IMG2200.

[0132] After step S1220, the clinic client device 20 executes a share request (S1221). Specifically, when a clinic user confirms a pharmacy of their choice for the target patient (e.g., a pharmacy where the patient wishes to receive prescription medication), enters the patient identification information of the target patient into field object F2200, enters the pharmacy identification information of the shared pharmacy into field object F2201, enters a message into field object F2202, performs an operation to acquire image object IMG2200 (e.g., an operation to release the shutter of the camera provided in clinic client device 20), and operates operation object B2200, processor 22 sends the shared request data to the patient client device 50. The sharing request data includes, for example, the following information: · Clinic identification information of the clinic where the clinic client device 20 is located · Patient identification information input to the field object F2200 · Pharmacy identification information input to the field object F2201 · Message input to the field object F2202 · Prescription image corresponding to the image object IMG2200

[0133] After step S1221, the server 30 executes database update (S1230). Specifically, the processor 32 adds a new record to the prescription sharing information database (Figure 10). The following information is stored in each field of the new record. · "Prescription ID" field: New prescription identification information · "Patient ID" field: Patient identification information included in the sharing request data · "Clinic ID" field: Clinic identification information included in the sharing request data · "Shared Pharmacy ID" field: Shared pharmacy information included in the sharing request data · "Shared Date and Time" field: Information regarding the execution date and time of step S1221 · "Prescription" field: Prescription image included in the sharing request data · "Message" field: Message included in the sharing request data

[0134] (4-3) Prescription Completion Notification Process The prescription completion notification process of this embodiment will be described.

[0135] (4-3-1) First Example of Prescription Completion Notification Process The first example of the prescription completion notification process of this embodiment will be described. The first example of the prescription completion notification process is an example in which the server 30 provides a prescription completion notification to the clinic client device 20 to prompt the patient of the completion of the prescription medicine. 15 is a sequence diagram of a first example of a prescription drug completion notification process according to this embodiment. FIG. 16 is a diagram showing an example of a screen displayed in the information processing of FIG.

[0136] The process of FIG. 15 is triggered, for example, by a user instruction from a pharmacy user (for example, an instruction to start an application of the pharmacy client device 10).

[0137] As shown in FIG. 15, the pharmacy client device 10 executes a prescription request (S1310). Specifically, the processor 12 displays a screen P310 on the display.

[0138] Screen P310 displays a list of prescription status information, patient name information, patient identification information, and clinic name information corresponding to the prescription identification information associated with the pharmacy's pharmacy identification information in the "Shared Pharmacy ID" field of the prescription sharing information database (Figure 10). The screen P310 includes an operation object B3100 and a field object F3100 for each prescription.

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

[0140] The operation object B3100 is an object that receives a user instruction to view prescription information. Each operation object B3100 is assigned prescription identification information.

[0141] When the pharmacy user operates the operation object B3100, the processor 12 transmits prescription request data to the server 30. The prescription request data includes, for example, the following information. · Pharmacy identification information where the pharmacy client device 10 is located · Prescription identification information assigned to the operation object B3110 operated by the user

[0142] After step S1310, the server 30 executes identification of prescription information (S1330). Specifically, the processor 32 refers to the prescription sharing information database (FIG. 10) to identify patient identification information, clinic identification information, prescription image, and message associated with the prescription identification information included in the prescription request data. The processor 32 refers to the patient information database (FIG. 7) to identify patient name information associated with the identified patient identification information. The processor 32 refers to the clinic information database (FIG. 6) to identify clinic name information associated with the identified clinic identification information.

[0143] After step S1330, the server 30 executes a prescription response (S1331). Specifically, the processor 32 transmits the prescription response data to the pharmacy client device 10. The prescription response data includes, for example, the following information. · Patient name information identified in step S1330 · Patient identification information identified in step S1330 · Clinic name information identified in step S1330 · Prescription image identified in step S1330 · Message identified in step S1330

[0144] After step S1331, the pharmacy client device 10 executes display of the prescription (S1311). Specifically, the processor 12 displays a screen P311 (FIG. 16) on the display.

[0145] The screen P311 includes a display object A3110, a field object F3110, and an image object IMG3110.

[0146] Display object A3110 displays patient name information, patient identification information, clinic name information, and a message contained in the prescription response data.

[0147] The field object F3110 is an object that receives a user instruction to input a message from the pharmacy to the clinic (for example, an inquiry about a prescription).

[0148] The image object IMG3110 is a prescription image included in the prescription response data. A pharmacist at the target pharmacy dispenses the prescribed medicine by referring to the prescription image.

[0149] After step S1311, the pharmacy client device 10 executes a prescription completion request (S1312). Specifically, when the pharmacy user completes dispensing of a prescription and specifies "Waiting for delivery" in the field object F3100, 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 F3100 - Prescription status information "Waiting for collection" specified in field object F3100

[0150] After step S1312, the server 30 updates the database (S1332). Specifically, the processor 32 refers to the prescription sharing information database (FIG. 10) and stores the prescription status information "awaiting 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.

[0151] After step S1332, the server 30 executes a prescription completion response (S1333). When the prescription completion request data includes the prescription status information "awaiting delivery" (that is, when the prescription drug is completed), the processor 32 refers to the prescription sharing information database (FIG. 10) and identifies the patient identification information, clinic identification information, and shared pharmacy identification information associated with the prescription identification information included in the prescription completion request data. The processor 32 refers to the patient information database (FIG. 7) and identifies the patient name information associated with the identified patient identification information. The processor 32 refers to the pharmacy information database (FIG. 5) and identifies the pharmacy name information associated with the identified shared pharmacy identification information. The processor 32 refers to the clinic information database (FIG. 6) and identifies the clinic contact information associated with the identified clinic identification information. The processor 32 transmits the prescription completion response data to the contact indicated by the clinic contact information (for example, the clinic client device 20). The prescription completion response data includes, for example, the following information. · Prescription status information updated in step S1332 · Identified patient name information · Identified patient identification information · Identified pharmacy name information

[0152] After step S1333, the clinic client device 20 executes a display of the prescription completion notification (S1320). Specifically, the processor 22 displays the screen P320 (FIG. 16) on a display (for example, the display of the clinic client device 20 and the display arranged in the clinic).

[0153] The screen P320 includes display objects A3200 to A3203.

[0154] The prescription status information included in the prescription response data is displayed on the display object A3200.

[0155] The patient name information included in the prescription response data is displayed on the display object A3201.

[0156] The patient identification information included in the prescription response data is displayed on the display object A3202.

[0157] The pharmacy name information included in the prescription response data is displayed on the display object A3203.

[0158] (4-3-2) Second Example of Prescription Medicine Completion Notification Processing A second example of the prescription medicine completion notification processing according to this embodiment will be described. The second example of the prescription medicine completion notification processing is an example in which the server 30 provides a prescription medicine completion notification to the patient client device 50 to prompt the patient of the completion of the prescription medicine. FIG. 17 is a sequence diagram of the second example of the prescription medicine completion notification processing according to this embodiment. FIG. 18 is a diagram showing an example of a screen displayed in the information processing of FIG. 17.

[0159] The trigger for the processing in FIG. 17 is, for example, a user instruction of the pharmacy user (for example, an instruction to start the application of the pharmacy client device 10).

[0160] As shown in FIG. 17, the following processing is the same as that in FIG. 15. · Prescription Request (S1310) to Prescription Medicine Completion Request (S1312) Identifying prescription information (S1330) - Updating the database (S1332)

[0161] After step S1332, the server 30 executes a prescription completion response (S1430). If the prescription completion request data includes the prescription status information "waiting for delivery" (i.e., the prescription has been completed), the processor 32 refers to the prescription shared information database (Figure 10) to identify the patient identification information and shared pharmacy identification information associated with the prescription identification information included in the prescription completion request data. Processor 32 refers to the pharmacy information database (FIG. 5) to identify pharmacy name information associated with the identified shared pharmacy identification information. The processor 32 references the patient information database (FIG. 7) to identify patient name information and patient contact information associated with the identified patient identification information. The processor 32 transmits the prescription completion response data to the contact indicated by the patient contact information (e.g., the patient client device 50). The prescription completion response data includes, for example, the following information: Identified pharmacy name information

[0162] After step S1430, the patient client device 50 executes a prescription completion notification (S1450). Specifically, the processor 52 displays a screen P450 (FIG. 17) on the display. Screen P450 displays a notification that the prescription has been completed at the pharmacy specified by the patient (pharmacy name = PH1).

[0163] According to this embodiment, the server 30 manages the cooperation between the clinic CL1 and the pharmacy PH1 in response to an instruction from a clinic user or a pharmacy user. This allows various information to be exchanged between clinic CL1 and pharmacy PH1.

[0164] According to this embodiment, the server 30 may share prescriptions issued by the clinic with the pharmacy. As a result, the pharmacy can obtain the prescription without the patient submitting the prescription to the pharmacy. As a result, the pharmacy can start dispensing the prescription medicine without waiting for the patient to visit the pharmacy. Therefore, since it is possible to dispense the prescription medicine even while the patient is moving from the clinic to the pharmacy, the time from the patient's visit to the pharmacy to receiving the prescription medicine can be shortened.

[0165] According to the present embodiment, the pharmacy client device 10 may acquire a prescription completion request and transmit a prescription completion notification to the clinic client device 20. As a result, it is possible to notify the patient staying at the clinic of the completion of the prescription medicine. As a result, the waiting time from the patient's visit to the pharmacy to receiving the prescription medicine can be eliminated.

[0166] According to the present embodiment, the pharmacy client device 10 may acquire a prescription completion request and transmit a prescription completion notification to the patient client device 50. As a result, it is possible to notify the patient of the completion of the prescription medicine in real time. As a result, the waiting time from the patient's visit to the pharmacy to receiving the prescription medicine can be eliminated.

[0167] According to the present embodiment, the server 30 provides a message regarding the prescription exchanged between the clinic and the pharmacy. As a result, the clinic and the pharmacy can easily resolve doubts regarding the prescription with each other.

[0168] (5) Other Modifications Other modifications will be described.

[0169] The storage device 11 may be connected to the pharmacy client device 10 via the network NW. The storage device 21 may be connected to the clinic client device 20 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.

[0170] The cooperation process (Fig. 11) may obtain a cooperation request from the pharmacy client device 10 and also obtain approval from the clinic client device 20. In this case, steps S1120 to S1122 are executed by the clinic client device 20. Steps S1110 to S1112 are executed by the pharmacy client device 10.

[0171] The server 30 may provide a function of creating a tracing report. Specifically, in response to an instruction from a pharmacy user to the pharmacy client device 10, the processor 32 creates a tracing report using the information stored in the database (Figs. 5 to 11) stored in the storage device 31. The processor 32 transmits the tracing report to the pharmacy client device 10. The processor 12 of the pharmacy client device 10 displays the tracing report on the display. Thereby, the pharmacy user can easily create a tracing report.

[0172] The server 30 may provide a function of presenting a comparison result (for example, the price difference) between a prescription drug and a generic drug. Specifically, the processor 32 calculates the price difference by referring to the information stored in the storage device (the price of the prescription drug and the price of the generic drug that substitutes for the prescription drug). The processor 32 transmits information regarding the price difference to the pharmacy client device 10 and the patient client device 50. The pharmacy client device 10 and the patient client device 50 display the information regarding the price difference on the display. Thereby, the pharmacy user and the patient can easily know the price difference between the prescription drug and the generic drug.

[0173] If the server 30 meets a predetermined condition, it may delete the record in the prescription sharing information database (Figure 10). Specifically, the processor 32 deletes the record that meets at least one of the following conditions from the prescription sharing information database. · A predetermined period (for example, one month) has elapsed since the date and time indicated by the shared date and time information · A deletion instruction has been given by the clinic user

[0174] In Figure 13, an example where the clinic user designates a shared pharmacy is shown, but the present embodiment is not limited to this. The present embodiment is also applicable to an example where the patient designates a shared pharmacy. Specifically, the server 30 transmits a list of pharmacies linked to the clinic to the patient client device 50. The patient client device 50 displays the list on the display. When the patient designates an arbitrary pharmacy from the list, the patient client device 50 transmits the pharmacy identification information of the pharmacy designated by the patient to the server 30. Thereby, the clinic user can share the prescription information with the shared pharmacy in a shorter time without having the patient confirm the pharmacy.

[0175] In Figure 15, an example of displaying a prescription drug completion notice for a specific patient is shown, but the scope of the present embodiment is not limited to this. The present embodiment may display the patient identification information of the target patient who should receive the completed prescription drug, or the reception number of the target patient (for example, the number received when the patient visits the clinic). Specifically, the prescription drug completion notice includes the patient identification information included in the prescription drug completion request, or the reception number associated with the patient identification information. In step S1320, the clinic client device 20 displays the patient identification information or the reception number included in the prescription drug completion notice on a common display (for example, a large display arranged at the reception of Clinic CL1) that can be simultaneously viewed by a plurality of patients. As a result, it is possible to notify a plurality of patients staying at the clinic of the completion of the prescription drug. Consequently, it is possible to eliminate the waiting time from the visit of each patient to the pharmacy until the receipt of the prescription drug.

[0176] In the present embodiment, in response to a request from the clinic client device 20, the sharing of the prescription information may be cancelled. Specifically, when the clinic user gives an instruction to cancel the sharing of the prescription information whose prescription status information is "new" on the screen P320 (FIG. 16), the processor 22 transmits prescription sharing cancellation request data to the server 30. The server 30 refers to the prescription sharing information database (FIG. 10) in response to the prescription sharing cancellation request data, and deletes the record of the prescription identification information corresponding to the instruction of the clinic user. Thereby, the sharing of the prescription information between the clinic and the pharmacy is cancelled. In this case, when the clinic discovers an error in the sharing of the prescription information (for example, sharing the prescription information of another patient), the clinic can correct the error. As a result, personal information can be reliably protected.

[0177] As described above, the embodiments of the present invention have been described in detail, but the scope of the present invention is not limited to the above embodiments. Further, the above embodiments can be variously improved and modified without departing from the gist of the present invention. Also, the above embodiments and modifications can be combined.

Description of Reference Numerals

[0178] 1: Information processing system 10: Pharmacy client device 11: Storage device 12: Processor 13: Input / output interface 14: Communication interface 20: Client device 20: Clinic 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 50: Patient client device 51:Storage device 52: Processor 53: Input / output interface 54: Communication interface

Claims

1. A server connectable to a clinic client device arranged at a clinic and a pharmacy client device arranged at a pharmacy, comprising: means for obtaining a cooperation request from the clinic client device; means for obtaining approval for the cooperation request from the pharmacy client device; means for storing, in association with each other, clinic information regarding the clinic and pharmacy information regarding the pharmacy when the approval is obtained; means for obtaining prescription information of a patient who has received medical treatment at the clinic from the clinic client device; means for presenting at least one piece of pharmacy information associated with the clinic information of the clinic to a patient client device used by the patient; means for obtaining designation of arbitrary pharmacy information from among the presented pharmacy information from the patient client device; means for linking the clinic and the pharmacy by storing in association with each other pharmacy identification information corresponding to the designated pharmacy information, patient identification information for identifying the patient, and the prescription information; A server.

2. A server connectable to a clinic client device arranged at a clinic and a pharmacy client device arranged at a pharmacy, comprising: means for obtaining a cooperation request from the pharmacy client device; means for obtaining approval for the cooperation request from the clinic client device; means for storing, in association with each other, clinic information regarding the clinic and pharmacy information regarding the pharmacy when the approval is obtained; means for obtaining prescription information of a patient who has received medical treatment at the clinic from the clinic client device; means for presenting at least one piece of pharmacy information associated with the clinic information of the clinic to a patient client device used by the patient; means for obtaining designation of arbitrary pharmacy information from among the presented pharmacy information from the patient client device; means for linking the clinic and the pharmacy by storing in association with each other pharmacy identification information corresponding to the pharmacy information, patient identification information for identifying the patient, and the prescription information; A server.

3. means for obtaining a prescription drug completion request from the pharmacy client device; Means for transmitting a prescription drug completion notice indicating that the prescription drug corresponding to the prescription information has been completed to the clinic client device in response to the prescription drug completion request. The server according to claim 1 or claim 2.

4. The prescription drug completion notice includes the reception number of the patient at the clinic. The server according to claim 3.

5. Means for obtaining a prescription drug completion request from the pharmacy client device, Means for transmitting a prescription drug completion notice indicating that the prescription drug corresponding to the prescription information has been completed to the patient client device in response to the prescription drug completion request. The server according to claim 1 or claim 2.

6. The prescription information includes at least one of a message obtained from the clinic client device and a message obtained from the pharmacy client device. The server according to claim 1 or claim 2.

7. The means for storing stores in association a message exchanged between the clinic and the pharmacy, clinic information regarding the clinic, and pharmacy information regarding the pharmacy. The server according to claim 1 or claim 2.

8. Means for obtaining an instruction to create a tracing report from the pharmacy client device, Means for creating the tracing report in response to the instruction, Means for transmitting the tracing report to the pharmacy client device. The server according to claim 1 or claim 2.

9. Means for transmitting the comparison result between the prescription drug and the generic drug to the pharmacy client device and the patient client device. The server according to claim 1 or claim 2.

10. Means for deleting the prescription information when a predetermined period has elapsed since it was associated with the pharmacy identification information corresponding to the pharmacy information, the patient identification information, and the prescription information. The server according to claim 1 or claim 2.

11. Means for obtaining an instruction to cancel the sharing of the prescription information from the clinic client device, Means for canceling the association between the pharmacy identification information corresponding to the pharmacy information, the patient identification information, and the prescription information in response to the instruction. The server according to claim 1 or claim 2.

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

13. An information processing method for coordinating a clinic and a pharmacy to share prescription information between the clinic and the pharmacy, using a clinic client device disposed in the clinic and a server connectable to a pharmacy client device disposed in the pharmacy, comprising: obtaining a cooperation request from the clinic client device; obtaining approval for the cooperation request from the pharmacy client device; when the approval is obtained, storing by associating clinic information regarding the clinic and pharmacy information regarding the pharmacy; obtaining prescription information of a patient who has received medical treatment at the clinic from the clinic client device; presenting at least one pharmacy information associated with the clinic information of the clinic to a patient client device used by the patient; obtaining a designation of any pharmacy information from among the presented pharmacy information from the patient client device; coordinating the clinic and the pharmacy by storing by associating pharmacy identification information corresponding to the pharmacy information, patient identification information for identifying the patient, and the prescription information; a method.

14. An information processing method for coordinating a clinic and a pharmacy to share prescription information between the clinic and the pharmacy, using a clinic client device disposed in the clinic and a server connectable to a pharmacy client device disposed in the pharmacy, comprising: obtaining a cooperation request from the pharmacy client device; obtaining approval for the cooperation request from the clinic client device; when the approval is obtained, storing by associating clinic information regarding the clinic and pharmacy information regarding the pharmacy; obtaining prescription information of a patient who has received medical treatment at the clinic from the clinic client device; presenting at least one pharmacy information associated with the clinic information of the clinic to a patient client device used by the patient; obtaining a designation of any pharmacy information from among the presented pharmacy information from the patient client device; A step of associating and storing pharmacy identification information corresponding to the pharmacy information, patient identification information for identifying the patient, and the prescription information to link the clinic and the pharmacy is provided. Method.

Images