Medical product provision application processing system, medical product provision application processing method, and medical product provision application processing program

Abstract

To provide a medical product provision application processing system, a medical product provision application processing method, and a medical product provision application processing program, which can provide a customer with an amount of the cost of providing a medical product in advance.SOLUTION: In a communication system in which a medical product pickup reservation server, a plurality of pharmacy terminals, a plurality of customer terminals, an electronic prescription management system, and a payment server are connected to a network, a system control section 11 of the medical product pickup reservation server includes: a prescription information acquisition section that acquires prescription information indicating a prescription of a medical product to be provided to a customer; a prescription information transmission section that transmits the acquired prescription information to a pharmacy terminal used by a pharmacy; an estimated amount information reception section that receives, from the pharmacy terminal, estimated amount information indicating an estimated amount of the cost of providing the medical product based on the prescription indicated by the transmitted prescription information; and an estimated amount information transmission section that transmits the received estimated amount information to the customer terminal used by the customer.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a method for processing an order for the provision of pharmaceutical products. [Background technology]

[0002] Conventionally, there has been known a system for supporting the operations of pharmacies by accepting online orders for prescription drugs that require a prescription to be provided to customers. For example, Patent Document 1 discloses a system for receiving prescription data, application data, and order data, storing order data, generating medication instruction data including the date and time of remote medication instruction implementation via two-way communication corresponding to the order data, managing the execution status of the remote medication instruction based on the medication instruction data, and, after confirming completion of the medication instruction and dispensing, transmitting delivery data to a delivery company server, and delivering the prescription drug based on the delivery data. [Prior art documents] [Patent documents]

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

[0004] After the drug has been dispensed and medication instructions have been provided, the customer pays the pharmacy for the cost of providing the drug. Conventionally, the pharmacy only notifies the customer of the cost at the time of payment. As a result, the customer was unable to know in advance the amount of the cost to be paid.

[0005] The present invention has been made in consideration of the above points, and one example of its objective is to provide a pharmaceutical supply application processing device, a pharmaceutical supply application processing method, and a pharmaceutical supply application processing program that can provide customers with the amount of costs associated with the provision of medical pharmaceuticals in advance. [Means for solving the problem]

[0006] (Application Example 1) The pharmaceutical supply application processing device of this application example is characterized by comprising: a prescription information acquisition means for acquiring prescription information indicating a prescription for a pharmaceutical to be provided to a customer; a prescription information transmission means for transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information receiving means for receiving, from the pharmacy device, estimated amount information indicating an estimated amount of the cost related to the supply of the pharmaceutical based on the prescription indicated by the transmitted prescription information, the estimated amount information receiving means receiving the estimated amount information transmitted from the pharmacy device before the implementation of medication instructions related to the supply of the pharmaceutical; and an estimated amount information transmission means for transmitting the acquired estimated amount information to a customer terminal device used by the customer.

[0007] According to this application example, after prescription information is transmitted to the pharmacy device, estimated amount information indicating an estimated cost for providing a pharmaceutical product based on the prescription is received from the pharmacy device. Here, the estimated amount information is transmitted from the pharmacy device to the pharmaceutical product provision application processing device before medication instructions for providing the pharmaceutical product based on the prescription indicated by the prescription information are provided. Therefore, the estimated amount information can be transmitted to the customer terminal device before medication instructions are provided. Therefore, the amount of costs for providing the pharmaceutical product can be provided to the customer in advance.

[0008] (Application Example 2) The pharmaceutical supply application processing device of this application example is characterized by further comprising a final amount information receiving means that receives final amount information indicating the final amount of the cost from the pharmacy device after the estimated amount information is received by the estimated amount information receiving means, and a payment means that executes payment of the cost of the final amount indicated by the received final amount information.

[0009] According to this application example, after the estimated amount information is received, final amount information indicating the final amount of the cost for providing the medicine based on the prescription is received from the pharmacy device. Then, payment for the final amount is executed. Therefore, the pharmacy can receive payment for the cost for providing the medicine.

[0010] (Application Example 3) The pharmaceutical supply application processing device of this application example further comprises a credit card information acquisition means for acquiring credit card information of the credit card designated by the customer, and an estimated amount payment confirmation means for confirming, based on the acquired credit card information, whether the estimated amount indicated by the acquired estimated amount information can be paid with the credit card, and the estimated amount information transmission means transmits the estimated amount information when it is confirmed by the estimated amount payment confirmation means that the payment is possible.

[0011] According to this application example, it is confirmed whether the estimated amount can be paid using a credit card. If payment is possible, the estimated amount information is transmitted to the customer terminal device. Therefore, it is possible to provide the customer with the amount of the cost related to the provision of the prescription drug in advance, after it has been confirmed that the customer can pay the cost.

[0012] (Application Example 4) The pharmaceutical provision application processing device of this application example further includes a fixed amount payment confirmation means for confirming whether the fixed amount can be paid with the credit card based on the acquired credit card information if the fixed amount indicated by the received fixed amount information is different from the estimated amount indicated by the transmitted estimated amount information, and the payment means executes the payment if the fixed amount payment confirmation means confirms that the fixed amount can be paid, and if the fixed amount indicated by the received fixed amount information matches the estimated amount indicated by the transmitted estimated amount information, the payment means executes the payment without the confirmation by the fixed amount payment confirmation means.

[0013] According to this application example, if the final amount differs from the estimated amount, confirmation of whether payment using a credit card is possible is performed again using the final amount. If payment is possible, payment is executed. If the final amount matches the estimated amount, confirmation of the final amount is skipped and payment is executed. Therefore, whether the final amount has changed from the estimated amount or not, payment can be executed after appropriate confirmation of whether payment using a credit card is possible has been performed.

[0014] (Application Example 5) The pharmaceutical supply application processing device according to this application example is characterized by further comprising: an application information receiving means for receiving application information indicating an application for supply of the pharmaceutical based on the prescription from the customer terminal device; an application payment confirmation means for confirming whether the credit card can be used based on the acquired credit card information in response to the application information being received by the application information receiving means; and an acceptance information sending means for sending acceptance information indicating that the application has been accepted to the customer terminal device when the application payment confirmation means confirms that the credit card can be used.

[0015] According to this application example, when an application for provision of a medicine based on a prescription is made, it is confirmed whether a credit card can be used. If a credit card can be used, the application for provision of the medicine is accepted. Therefore, the application for provision of the medicine can be accepted after it has been confirmed that the credit card can be used.

[0016] (Application Example 6) The pharmaceutical supply application processing device according to this application example further includes: a memory control means for storing in a memory means a dispensing status related to the dispensing of the pharmaceutical based on the prescription indicated by the acquired prescription information, the dispensing status being set to a dispensing incomplete state indicating that the dispensing of the pharmaceutical is incomplete; a change means for changing the dispensing status stored in the memory means to a dispensing completed state indicating that the dispensing of the pharmaceutical has been completed and the medication instruction is incomplete in response to communication from the pharmacy device that has received the transmitted prescription information; and an operation acceptance screen information sending means for sending to the pharmacy device, operation acceptance screen information that causes the pharmacy device to display an operation acceptance screen that can accept an operation for inputting the estimated amount, when the dispensing status stored in the memory means is the dispensing incomplete state, and the estimated amount information sending means receives the estimated amount information indicating the input estimated amount.

[0017] According to this application example, after prescription information is received, the dispensing status is stored as being set to a dispensing incomplete state. The dispensing incomplete state indicates that the dispensing of the medicine is incomplete. The pharmacy dispenses the medicine. When the dispensing is completed and medication instructions can be provided, predetermined communication is performed from the pharmacy device to the medicine provision application processing device. In response to this communication, the dispensing status is changed from the dispensing incomplete state to the dispensing completed state. The dispensing completed state indicates that the dispensing of the medicine is completed and medication instructions are incomplete. When the dispensing status is the dispensing incomplete state, an operation reception screen is sent to the pharmacy device. The operation reception screen is a screen that can accept an operation for inputting an estimated amount. Therefore, the pharmacy can input an estimated amount before medication instructions are provided. Therefore, the amount of the cost related to the provision of the prescription medicine can be provided to the customer in advance.

[0018] (Application Example 7) The pharmaceutical supply application processing device of this application example is characterized in that the estimated amount information sending means sends the estimated amount information, along with status information indicating the dispensing status stored in the storage means, to the customer terminal device.

[0019] According to this application example, the cost of providing prescription drugs and the status of dispensing are presented to the customer, so the customer can check the cost in advance and whether the drug is available for receipt.

[0020] (Application Example 8) The pharmaceutical provision application processing device of this application example is characterized in that the change means changes the dispensing status to the dispensing completed status in response to the estimated amount information being received by the estimated amount information sending means.

[0021] According to this application example, communication from the pharmacy device to the drug provision application processing device after the drug dispensing is completed includes sending estimated cost information, which makes it possible to estimate the cost of providing the drug before the dispensing is completed, and to provide the customer with the cost of providing the prescription drug in advance.

[0022] (Application Example 9) The pharmaceutical supply application processing device of this application example is characterized in that the estimated amount information receiving means receives the estimated amount information sent from the pharmacy device in response to the pharmacy device receiving the transmitted prescription information, and the estimated amount information sending means sends the estimated amount information together with acceptance information indicating that the application for the pharmaceutical supply has been accepted to the customer terminal device.

[0023] According to this application example, when an application for provision of a pharmaceutical product is accepted, the amount of the cost for providing the pharmaceutical product can be provided to the customer in advance.

[0024] (Application Example 10) A pharmaceutical supply application processing method according to this application example is a pharmaceutical supply application processing method executed by a computer, and is characterized by including: a prescription information acquisition step for acquiring prescription information indicating a prescription for a pharmaceutical to be provided to a customer; a prescription information transmission step for transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information reception step for receiving, from the pharmacy device, estimated amount information indicating an estimated amount of costs related to the provision of the pharmaceutical based on the prescription indicated by the transmitted prescription information, wherein the estimated amount information reception step receives estimated amount information transmitted from the pharmacy device in a state before medication instructions related to the provision of the pharmaceutical are implemented; and an estimated amount information transmission step for transmitting the acquired estimated amount information to a customer terminal device used by the customer.

[0025] (Application Example 11) The pharmaceutical supply application processing program of this application example is characterized in that it causes a computer to function as a prescription information acquisition means for acquiring prescription information indicating a prescription for a pharmaceutical to be provided to a customer, a prescription information transmission means for transmitting the acquired prescription information to a pharmacy device used by the pharmacy, an estimated amount information receiving means for receiving, from the pharmacy device, estimated amount information indicating an estimated amount of the cost related to the provision of the pharmaceutical based on the prescription indicated by the transmitted prescription information, wherein the estimated amount information receiving means receives the estimated amount information transmitted from the pharmacy device before the implementation of medication instructions related to the provision of the pharmaceutical, and an estimated amount information transmission means for transmitting the acquired estimated amount information to a customer terminal device used by the customer. [Effects of the Invention]

[0026] According to the present invention, the amount of the cost for providing a medical drug can be provided to the customer in advance. [Brief explanation of the drawings]

[0027] [Figure 1] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 2]1 is a block diagram showing an example of a schematic configuration of a medicine receipt reservation server 1 according to an embodiment. [Figure 3] 10 is a diagram showing an example of information stored in a database of the medicine receipt reservation server 1. FIG. [Figure 4] FIG. 10 is a diagram showing an example of the relationship between prescription status, payment status, and prescription-related processing. [Figure 5] FIG. 2 is a diagram showing an example of functional blocks of a system control unit 11 in a medicine receipt reservation server 1 according to an embodiment. [Figure 6] FIG. 10 is a diagram showing an example of a reservation application acceptance completion screen. [Figure 7] FIG. 10 is a diagram illustrating an example of a pharmacy reservation list screen. [Figure 8] FIG. 10 is a diagram showing an example of a patient information screen. [Figure 9] 10A is a diagram showing an example of an estimated amount confirmation screen, and FIG. 10B is a diagram showing an example of an estimated amount input screen. [Figure 10] 10A is a diagram showing an example of a payment amount confirmation screen, and FIG. 10B is a diagram showing an example of a payment amount input screen. [Figure 11] FIG. 10 is a diagram showing an example of a patient information screen. [Figure 12] FIG. 10 is a diagram illustrating an example of a customer reservation list screen. [Figure 13] FIG. 10 is a diagram illustrating an example of a reservation details screen. [Figure 14] FIG. 10 is a diagram showing another example of the reservation details screen. [Figure 15] FIG. 10 is a diagram showing an example of the relationship between prescription status, payment status, authorization, and payment. [Figure 16] FIG. 10 is a sequence diagram showing an example of the processing of the communication system S when a reservation is made to receive medicines. [Figure 17] FIG. 10 is a diagram showing an example of a patient information screen information transmission process executed by a system control unit 11 of the medicine receipt reservation server 1 according to an embodiment. [Figure 18] FIG. 10 is a sequence diagram showing an example of processing by the communication system S when an estimated amount is input. [Figure 19] FIG. 10 is a diagram showing an example of reservation details screen information transmission processing executed by the system control unit 11 of the medicine receipt reservation server 1 according to an embodiment. [Figure 20] FIG. 10 is a sequence diagram showing an example of processing by the communication system S when a payment amount is input. [Figure 21] FIG. 10 is a diagram showing an example of a reservation application acceptance completion screen. DETAILED DESCRIPTION OF THE INVENTION

[0028] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0029] [1. First embodiment] [1-1. Communication System Configuration] First, the configuration and functional overview of a communication system S according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the schematic configuration of a communication system S according to this embodiment.

[0030] As shown in Figure 1, the communication system S may be configured to include a medicine receipt reservation server 1, multiple pharmacy terminals 2, multiple customer terminals 3, an electronic prescription management system 4, and a payment server 5. The medicine receipt reservation server 1, each pharmacy terminal 2, each customer terminal 3, the electronic prescription management system 4, and the payment server 5 may be connected to a network NW. The network NW is constructed, for example, by the Internet, a dedicated communication line (e.g., a CATV (Community Antenna Television) line), a mobile communication network (including base stations, etc.), a gateway, etc.

[0031] The pharmaceutical pickup reservation server 1 may be a server device that performs processing related to a predetermined pharmaceutical pickup reservation site. The pharmaceutical pickup reservation site may be a website that allows online reservations for receiving prescription pharmaceuticals. Prescription pharmaceuticals may be pharmaceuticals dispensed based on a prescription. Hereinafter, prescription pharmaceuticals will be simply referred to as pharmaceuticals. A pharmaceutical pickup reservation can be referred to, for example, as a prescription reservation, a pharmacy reservation, or a pharmaceutical delivery reservation. The pharmaceutical pickup reservation server 1 may transmit content such as a webpage that constitutes the pharmaceutical pickup reservation site to at least one of the pharmacy terminal 2 and the customer terminal 3. The pharmaceutical pickup reservation server 1 may also perform processes such as searching for a pharmacy where the customer will receive the pharmaceutical, accepting the pharmaceutical pickup reservation, obtaining prescription information indicating the prescription, providing the prescription information to the pharmacy, and settling the costs related to the pharmaceutical delivery.

[0032] The medicine receipt reservation server 1 may transmit estimated amount information to the customer terminal 3 used by the customer before the pharmacy provides medication instructions to the customer to provide the medicine based on the reservation. The estimated amount information may indicate the estimated amount of costs related to providing the medicine. This cost may include, for example, the price of the medicine itself, a dispensing fee, a medication instruction fee, etc. The customer can know in advance the amount they plan to pay to the pharmacy before going to the pharmacy or receiving medication instructions.

[0033] Each pharmacy terminal 2 may be a terminal device used by a pharmacy employee such as a pharmacist. An example of the pharmacy terminal 2 is a personal computer. Each pharmacy terminal 2 may be equipped with software such as a web browser or an email client. Each pharmacy terminal 2 may receive and display content such as a web page from the medicine pickup reservation server 1 based on operations by an employee. Each pharmacy terminal 2 may be used, for example, to check the details of a medicine pickup reservation or a prescription, set and check the status of work related to the provision of medicines, input the amount of costs related to the provision of medicines, and request payment of those costs. At least one pharmacy terminal 2 may be equipped with a receipt computer. The receipt computer may be a computer, system, or software for creating a statement of medical fees related to the provision of medicines. At least one pharmacy terminal 2 may be equipped with a camera capable of capturing video or may be connectable to the camera. At least one pharmacy terminal 2 may be equipped with a microphone for audio input and a speaker for audio output, or may be connectable to the microphone and speaker. The cost of providing medicines may be calculated automatically by the pharmacy terminal 2, rather than being input by an employee into the pharmacy terminal 2. In this case, the pharmacy terminal 2 may be a terminal device, or may actually be a server device.

[0034] Each customer terminal 3 may be a terminal device used by a customer who uses the pharmaceutical pickup reservation site to make a pharmaceutical pickup reservation. Examples of the customer terminal 3 include a mobile information terminal such as a smartphone or tablet computer, a mobile phone, a personal digital assistant (PDA), a personal computer, and a set-top box. Each customer terminal 3 may be equipped with software such as a web browser or an email client. Each customer terminal 3 may receive and display content such as a web page from the pharmaceutical pickup reservation server 1 based on a customer's operation. At least one customer terminal 3 may be equipped with a camera capable of capturing at least one of still images and video, or may be connectable to such a camera. A paper prescription may be photographed using the camera. The customer terminal 3 may transmit prescription image data indicating the photographed image of the prescription to the pharmaceutical pickup reservation server 1. The prescription image data is an example of prescription information. At least one customer terminal 3 may be equipped with a microphone for inputting voice and a speaker for outputting voice, or may be connectable to a microphone and a speaker.

[0035] The electronic prescription management system may be a system that manages electronic prescriptions. An electronic prescription is another example of prescription information. The electronic prescription management system may include, for example, one or more server devices. The electronic prescription management system may, for example, obtain electronic prescriptions from medical institutions and provide electronic prescriptions to pharmacies.

[0036] The payment server 5 may be a server device managed by a credit card company or a payment agent. The payment server 5 may also be a server device that executes processes related to credit card payments. For example, the payment server 5 may execute authorization of a designated credit card or processing of payment using a credit card based on a request from the medicine receipt reservation server 1. Authorization may be processing to confirm whether payment can be made using that credit card. Authorization is also referred to as credit confirmation. Credit may be granting the credit card owner the trust to pay the price with a credit card.

[0037] [1-2. Configuration of the pharmaceutical receipt reservation server] Next, the configuration of the pharmaceutical receipt reservation server 1 will be described with reference to Figures 2 to 4. Figure 2 is a block diagram showing an example of the general configuration of the pharmaceutical receipt reservation server 1 according to this embodiment. As shown in Figure 2, the pharmaceutical receipt reservation server 1 includes a system control unit 11, a system bus 12, an input / output interface 13, a storage unit 14, and a communication unit 15. The system control unit 11 and the input / output interface 13 are connected via the system bus 12.

[0038] The system control unit 11 includes a CPU (Central Processing Unit) 11a, a ROM (Read Only Memory) 11b, a RAM (Random Access Memory) 11c, and the like.

[0039] The input / output interface 13 performs interface processing between the storage unit 14 and the communication unit 15 and the system control unit 11 .

[0040] The storage unit 14 is configured, for example, with a hard disk drive or the like. Databases such as a member DB 14a, a credit card information DB 14b, a patient DB 14c, a pharmacy DB 14d, and a reservation DB 14e may be stored in this storage unit 14. "DB" is an abbreviation for database. At least one database may be stored in a server device different from the medicine receipt reservation server 1. The medicine receipt reservation server 1 may be able to access the database via that server device.

[0041] Fig. 3 is a diagram showing an example of information stored in the database of the medicine receipt reservation server 1. The member DB 14a may store member information about each customer who can use the medicine receipt reservation site. For example, as shown in Fig. 3, the member DB 14a may store, as member information, a customer ID, name, sex, date of birth, address, telephone number, email address, etc., in association with one another. The customer ID may be identification information that identifies the customer.

[0042] The credit card information DB14b may store information about the credit card owned by each customer for each combination of customer and credit card. The medicine receipt reservation server 1 may be configured to allow customers to register information about their credit cards in advance. Furthermore, one customer may be able to register information about multiple credit cards. The credit card information DB14b may store, for example, a customer ID, a customer card ID, and credit card information in association with each other. The customer ID may indicate the customer who owns the credit card. The customer card ID may be information for identifying the credit card from among the credit cards registered by the customer. For example, the customer card ID may be a number such as "001" or "002." The credit card information may be specific information about the credit card. The credit card information may include, for example, the credit card number, expiration date, security code, and the name of the credit card owner.

[0043] The patient DB 14c may store, for each registered patient, patient information about patients registered by a customer as people who may become patients who will receive medicines from the pharmacy. For example, the medicine receipt reservation server 1 may be configured to allow each customer to register a patient. For example, a customer may be able to register their family members as patients. The medicine receipt reservation server 1 may automatically register the customer as a patient. The patient DB 14c may store, as patient information, for example, a customer ID, a patient ID, a patient name, gender, date of birth, etc., in association with one another. The customer ID may indicate the customer who registered the patient. The patient ID may be information for identifying the patient from among the patients registered by that customer.

[0044] The pharmacy DB 14d may store pharmacy information about each pharmacy for which a reservation can be made on the medicine pickup reservation site. For example, the pharmacy DB 14d may store, as pharmacy information, a pharmacy ID, a pharmacy name, an address, and the like, in association with one another. The pharmacy ID may be identification information that identifies a pharmacy.

[0045] The reservation DB 14e may store reservation information regarding a pharmaceutical pickup reservation each time the pharmaceutical pickup reservation server 1 accepts a reservation. For example, the reservation DB 14e may store the following reservation information in association with one another: a reception number, a reception date, a prescription ID, a customer ID, a patient ID, a pharmacy ID, a pickup date and time, a medication instruction method, a payment method, a billing amount, a customer card ID, an approval number, a prescription status, and a payment status. The reception number is a number that identifies the reservation. The reception date may indicate the date the reservation was accepted at the pharmaceutical pickup reservation site. The prescription ID may be identification information that identifies the prescription information that forms the basis for dispensing pharmaceuticals. The prescription ID may be, for example, the file name or URL (Uniform Resource Locator) of the prescription information, or other information. The customer ID may indicate the customer who made the reservation. The patient ID may indicate the patient who will use the pharmaceuticals to be received by the customer. The pharmacy ID may indicate the pharmacy reserved to receive the pharmaceuticals. The pickup date and time may indicate the date and time the pharmaceuticals are scheduled to be picked up. The receipt date and time can be set to a specific date and time, or may be set to information indicating "receive as soon as it is dispensed." "Receive as soon as it is dispensed" indicates that the customer will receive the medicine after the pharmacy has completed dispensing the medicine, without specifying a date and time. The medication instruction method may indicate a method for providing medication instruction to the customer when the pharmacy provides the medicine. The medication instruction method may be set to, for example, either "over the counter" or "online." "Over the counter" indicates that medication instruction is provided at the pharmacy. "Online" indicates that medication instruction is provided online. For example, the pharmacy terminal 2 and the customer terminal 3 may be connected under the control of the medicine receipt reservation server 1. Then, online medication instruction may be provided by transmitting and receiving information indicating video and audio of the pharmacist and the customer between the pharmacy terminal 2 and the customer terminal 3. The payment method may indicate a method by which the customer pays the costs associated with the provision of the medicine. The payment method may be set to, for example, either over the counter payment or online payment. In over the counter payment, the customer pays the costs at the pharmacy.In online payment, the medicine receipt reservation server 1 automatically executes payment based on the credit card information stored in the credit card information DB 14b. The billing amount may indicate the amount the customer plans to pay or has already paid as a cost for providing the medicine. The customer card ID and authorization number may be valid when the payment method is "online." The customer card ID may indicate the credit card designated by the customer. The authorization number may be a number that identifies credit when credit is confirmed in the authorization performed by the medicine receipt reservation server 1 before payment. The authorization number may be information transmitted, for example, from the payment server 5 to the medicine receipt reservation server 1. The prescription status may indicate the status of processing by the pharmacy regarding the prescription information indicated by the prescription ID. The prescription status may indicate the status of work related to providing the medicine based on the prescription information. The prescription status may be set to, for example, "sent," "accepted," "dispensing," "dispensing completed," or "delivered." "sent" may indicate that the prescription has been completely transmitted to the pharmacy. "Received" may indicate that the pharmacy has completed receiving the prescription. "Dispensing" may indicate that the pharmacy is dispensing the medicine. "Dispensing completed" may indicate that the dispensing of the medicine has been completed. "Delivered" may indicate that the delivery of the medicine from the pharmacy to the customer has been completed. The payment status may indicate the status of payment for the cost of providing the medicine. The payment status may be set to, for example, either "unpaid" or "payment completed." "Unpaid" may indicate that payment has not yet been completed. "Payment completed" may indicate that payment has been completed.

[0046] FIG. 4 is a diagram showing an example of the relationship between prescription status, payment status, and prescription-related processing. As shown in FIG. 4, when the medicine receipt reservation server 1 sends prescription information to the pharmacy terminal 2, the prescription status is set to "sent." The payment status is also set to "unpaid." The pharmacy employee checks the prescription information and confirms the reservation details. After checking, the employee performs an operation on the pharmacy terminal 2 to accept the prescription. In response to this operation, the prescription status is changed to "accepted." The employee then performs an operation on the pharmacy terminal 2 to start dispensing the medicine. In response to this operation, the prescription status is changed to "dispensing." The employee dispenses the medicine based on the prescription and estimates the billing amount. When dispensing is complete, the employee inputs the estimated amount into the pharmacy terminal 2. In response to this input, the prescription status is changed to "dispensing completed." Note that the medicine receipt reservation server 1 may be configured so that the operation to change the prescription status to "dispensing completed" can be performed separately from the operation to input the estimated amount. In this case, the estimated amount may be input before the prescription status becomes "dispensing completed." The prescription status may not change even if the estimated amount is input. After the prescription status changes to "dispensing completed," the employee provides medication instructions to the customer. The employee then causes the medicine receipt reservation server 1 to execute payment of the billed amount. Upon execution of this payment, the prescription status changes to "delivered." The payment status also changes to "payment completed." The employee then delivers the dispensed medication to the customer. If medication instructions are provided online, the employee may ship the medication to the customer's address. The relationship between the prescription status and the medication dispensing status will now be explained. As shown in Figure 4, "sent," "accepted," and "dispensing" indicate that the medication dispensing is incomplete. "dispensing completed" and "delivered" indicate that the medication dispensing is complete. The relationship between the prescription status and the implementation status of medication instructions will now be explained. As shown in Figure 4, "Sent," "Received," "Dispensing," and "Dispensing Completed" indicate that medication instructions have not yet been completed. "Delivered" indicates that medication instructions have been completed.At least one of changing the prescription status to "Accepted" and changing the prescription status to "Dispensing" may be omitted. For example, the prescription status may be changed from "Sent" to "Dispensing Completed." However, confirmation of the prescription and reservation details by the employee, dispensing work, and estimating the billing amount themselves may not be omitted.

[0047] The storage unit 14 may store prescription information transmitted from the customer terminal 3 or the electronic prescription management system 4 in association with a prescription ID. The storage unit 14 also stores various programs such as an operating system, a DBMS (Database Management System), and a server program. The server program is a program that causes the system control unit 11 to execute processing related to the medicine pickup reservation site. The server program may be obtained from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, optical disk, or memory card and read via a drive device.

[0048] The communication unit 15 is configured by, for example, a network interface card, etc. The communication unit 15 connects to the pharmacy terminal 2, the customer terminal 3, the electronic prescription management system 4, or the payment server 5 via the network NW, and controls the communication state with the connected devices.

[0049] [1-3. Functional overview of the system control unit] Next, an overview of the functions of the system control unit 11 in the pharmaceutical receipt reservation server 1 will be described with reference to Figures 5 to 15. Figure 5 is a diagram showing an example of functional blocks of the system control unit 11 in the pharmaceutical receipt reservation server 1 according to this embodiment. As shown in Figure 5, the system control unit 11 may function as a prescription information acquisition unit 1101, a reservation application acceptance information transmission unit 1102, a prescription information transmission unit 1103, a status management unit 1104, a pharmacy screen information transmission unit 1105, an estimated amount information reception unit 1106, an estimated amount information transmission unit 1107, a confirmed amount information reception unit 1108, a payment unit 1109, a credit card information acquisition unit 1110, a confirmation unit 1111, and the like, by the CPU 11a reading and executing various program codes included in the server program.

[0050] The prescription information acquisition unit 1101 may acquire prescription information indicating a prescription for a drug to be provided to a customer. The customer to whom the drug is provided may be the patient who uses the drug, or may not be a patient. For example, the customer may be a family member of a patient. The customer to whom the drug is provided may also be a person who pays for the cost of providing the drug.

[0051] The prescription information acquisition unit 1101 may acquire prescription information from, for example, the customer's customer terminal 3. For example, the prescription information acquisition unit 1101 may acquire prescription image data. The customer may photograph the prescription provided by the medical institution using the customer terminal 3. The customer terminal 3 may transmit the prescription image data generated by photographing to the medicine receipt reservation server 1.

[0052] The prescription information acquisition unit 1101 may acquire prescription information from, for example, the electronic prescription management system 4. For example, the prescription information acquisition unit 1101 may acquire an electronic prescription. For example, a customer may input information from the patient's My Number card or health insurance card into the customer terminal 3. This information may include information that identifies the patient. The customer terminal 3 may transmit the input information to the medicine receipt reservation server 1. The medicine receipt reservation server 1 may transmit information received from the customer terminal 3 to the electronic prescription management system 4. The electronic prescription management system 4, for example, stores each electronic prescription in association with information that identifies the patient. The electronic prescription management system 4 may search for an electronic prescription issued for the patient based on the information received from the medicine receipt reservation server 1, and transmit the electronic prescription to the medicine receipt reservation server 1.

[0053] The prescription information acquisition unit 1101 may receive application information from the customer terminal 3. The application information may indicate an application for provision of medicines. For example, the application information may be reservation application content information indicating the content of an application for a reservation to receive medicines. When acquiring prescription image data as prescription information, the prescription information acquisition unit 1101 may receive the prescription image data and reservation application content information from the customer terminal 3. The prescription information acquisition unit 1101 may send reservation application content input screen information to the customer terminal 3. The reservation application content input screen information may be information for displaying a reservation application content input screen on the customer terminal 3. The reservation application content input screen may be a screen that can accept input of the content of an application for a reservation to receive medicines. The reservation application content input screen may include, for example, multiple screens. The reservation application content input screen information may be an HTML (HyperText Markup Language) document of a web page corresponding to the reservation application content input screen, or may be other information. The reservation application content input screen may be capable of accepting, for example, selection of the type of prescription, selection of the pharmacy where the customer will receive the medicine, selection of the patient, selection of the payment method, selection of the credit card to be used for payment, selection of the date and time of receipt, etc. If a paper prescription is selected as the type of prescription between paper and electronic prescriptions, the reservation application content input screen may be capable of accepting selection of prescription image data to be sent to the medicine receipt reservation server 1. The customer terminal 3 may send reservation application content information including, for example, the customer ID, type of prescription, pharmacy ID of the selected pharmacy, patient ID of the selected patient, payment method, customer card ID of the selected credit card, date and time of receipt, etc. to the medicine receipt reservation server 1. The prescription information acquisition unit 1101 may generate reservation information based on the reservation application content information and store the generated reservation information in the reservation DB 14e.

[0054] The reservation application acceptance information sending unit 1102 may send reservation application acceptance information to the customer terminal 3 in response to the prescription information and reservation application acceptance information being acquired by the prescription information acquisition unit 1101. The reservation application acceptance information may indicate that the reservation for receiving the medicine has been accepted by the medicine receipt reservation site. The reservation application acceptance information may be, for example, an email addressed to the customer who has made the reservation for receiving the medicine. This email may include a message indicating that the reservation for receiving the medicine has been accepted and the contents of the reservation. The reservation application acceptance information may also be, for example, reservation application acceptance completion screen information. The reservation application acceptance completion screen information may be information for displaying a reservation application acceptance completion screen on the customer terminal 3. The reservation application acceptance completion screen may be a screen indicating that the reservation for receiving the medicine has been accepted. The reservation application acceptance completion screen information may be an HTML document of a webpage equivalent to the reservation application acceptance completion screen, or may be other information.

[0055] FIG. 6 is a diagram showing an example of a reservation application acceptance completion screen. As shown in FIG. 6, the reservation application acceptance completion screen 100 may include, for example, a message 110, a home button 120, and a reservation list button 130. The message 110 may be a sentence indicating that the reservation for receiving medicines has been accepted. The home button 120 may be a button for displaying the home screen of the medicine receiving reservation site. The reservation list button 130 may be a button for displaying a customer reservation list screen. The customer reservation list screen may display a list of medicine receiving reservations made by the customer.

[0056] The prescription information transmitting unit 1103 may transmit the prescription information acquired by the prescription information acquiring unit 1101 to the pharmacy terminal 2. For example, the prescription information transmitting unit 1103 may transmit the prescription information to the pharmacy terminal 2 of the pharmacy identified by the pharmacy ID included in the reservation application content information. The prescription information transmitting unit 1103 may transmit the prescription information, for example, at the timing when the prescription information is acquired. Alternatively, the prescription information transmitting unit 1103 may transmit the prescription information in response to a request from the pharmacy terminal 2.

[0057] The status management unit 1104 may manage the prescription status and payment status stored in the reservation DB 14e. The status management unit 1104 may store, in the reservation DB 14e, a prescription status indicating that dispensing of a medicine based on a prescription indicated by the prescription information acquired by the prescription information acquisition unit 1101 is incomplete. As described above, a prescription status corresponding to incomplete dispensing may be any one of "sent," "accepted," and "dispensing." For example, when prescription information is acquired by the prescription information acquisition unit 1101, the status management unit 1104 may set the prescription status to "sent." Alternatively, when prescription information is transmitted to the pharmacy terminal 2 by the prescription information transmission unit 1103, the status management unit 1104 may set the prescription status to "sent."

[0058] Furthermore, the status management unit 1104 may change the prescription status to a status indicating that dispensing has been completed but medication instructions have not been completed in response to communication from the pharmacy terminal 2 that has received the prescription information transmitted by the prescription information transmission unit 1103. As shown in FIG. 4, the prescription status corresponding to the completion of dispensing but the incomplete medication instructions may be "dispensing completed." For example, as will be described later, the status management unit 1104 may change the prescription status to "dispensing completed" in response to receiving estimated amount information from the pharmacy terminal 2. The estimated amount information may indicate the estimated cost of dispensing the medicine. Alternatively, the status management unit 1104 may change the prescription status to "dispensing completed" in response to an operation by an employee on the pharmacy terminal 2 indicating the completion of dispensing.

[0059] The pharmacy screen information sending unit 1105 may send the pharmacy screen information to the pharmacy terminal 2. The pharmacy screen information may be information that causes the pharmacy terminal 2 to display a pharmacy screen. The pharmacy screen may display, for example, information related to a drug pickup reservation. Alternatively, for example, the pharmacy screen may be a screen that can accept operations by employees. The pharmacy screen may be a general term for multiple types of screens. For example, the pharmacy screen may include a pharmacy reservation list screen, a patient information screen, an estimated amount confirmation screen, an estimated amount input screen, a payment amount confirmation screen, a payment amount input screen, etc., which will be described later. The pharmacy screen information may be an HTML document of a web page corresponding to the pharmacy screen, or may be other information.

[0060] FIG. 7 is a diagram showing an example of a pharmacy appointment list screen. The pharmacy appointment list screen may be a screen showing a list of pick-up appointments in which the pharmacy of the pharmacy terminal 2 displaying the screen is designated as the recipient of the pharmaceutical. As shown in FIG. 7, the pharmacy appointment list screen 200 may include, for example, multiple appointment information fields 210. Each appointment information field 210 may contain information simply indicating the details of the pharmaceutical pick-up appointment corresponding to that appointment information field 210. Each appointment information field 210 may include, for example, the pick-up date and time, the reception number, the patient name, the medication instruction method, the payment method, the prescription status, and the payment status. When an employee selects an appointment by selecting one of the appointment information fields 210 on the pharmacy appointment list screen 200, the pharmacy terminal 2 may display a patient information screen. For example, the pharmacy terminal 2 may display the patient information screen as an overlay on the pharmacy appointment list screen 200.

[0061] FIG. 8 is a diagram showing an example of a patient information screen. The patient information screen may be a screen showing the details of a selected appointment and the status of work for that appointment. As shown in FIG. 8, the patient information screen 300 may include patient information 310, an appointment information field 320, a payment status 330, a prescription status 340, a prescription receipt pane 350, a dispensing start pane 360, an estimated amount input pane 370, a payment execution pane 380, and a prescription display button 390. The patient information 310 may indicate, for example, the patient's name, date of birth, gender, etc. The appointment information field 320 may include, for example, the date and time of receipt and the payment method.

[0062] The prescription reception pane 350 may be an area related to prescription reception settings. The prescription reception pane 350 may include a settings button 351, etc. The settings button 351 may be a button that can be operated to display a prescription reception screen. The settings button 351 may be operable only when the prescription status 340 displayed on the patient information screen 300 is "Sent." In FIG. 8, the prescription status 340 is "Sent," and the outline of the settings button 351 is indicated by a solid line. The solid line indicates that the settings button 351 is operable. The prescription reception screen may be a screen that can accept settings for accepting a prescription corresponding to a selected reservation. The prescription reception screen may be displayed, for example, as an overlay on the patient information screen 300. When the prescription reception settings are accepted on the prescription reception screen, the pharmacy terminal 2 may clear the prescription reception screen and change the prescription status 340 to "Accepted."

[0063] The dispensing start pane 360 ​​may be an area related to settings for starting dispensing of medicines. The dispensing start pane 360 ​​may include a settings button 361, etc. The settings button 361 may be a button that can be operated to display a dispensing start screen. The settings button 361 may be operable only when the prescription status 340 is "Sent" or "Accepted." The dispensing start screen may be a screen that can accept a setting operation indicating that dispensing based on the prescription corresponding to the selected appointment will start. The dispensing start screen may be displayed, for example, in a manner that overlays the patient information screen 300. When the dispensing start settings are accepted on the dispensing start screen, the pharmacy terminal 2 may clear the dispensing start screen and change the prescription status 340 to "Dispensing."

[0064] The estimated amount input pane 370 may be an area for inputting an estimated amount estimated as a billing amount for the cost of providing the pharmaceutical product. The estimated amount input pane 370 may include a settings button 371, etc. The settings button 371 may be a button that can be operated to display an estimated amount confirmation screen. The settings button 371 may be operable only when the prescription status 340 is "Sent," "Received," or "Dispensing."

[0065] FIG. 9(a) illustrates an example of an estimate confirmation screen. The estimate confirmation screen may be a screen for an employee to confirm the estimate. As shown in FIG. 9(a), the estimate confirmation screen 400 may include patient information 410, an estimate 420, a change button 430, a return button 440, and a set button 450. The patient information 410 may indicate, for example, the patient's name, date of birth, and gender. The estimate 420 may indicate the current estimate. If the estimate has not yet been entered, the estimate 420 may indicate a predetermined amount. The change button 430 may be a button operable to display an estimate input screen, which will be described later. The estimate input screen may be displayed, for example, as an overlay on the estimate confirmation screen 400. The return button 440 may be a button operable to cancel the setting of the estimate. The set button 450 is a button operable to set the estimate to the amount indicated by the estimate 420.

[0066] FIG. 9(b) is a diagram showing an example of an estimated amount input screen. The estimated amount input screen may be a screen for inputting an estimated amount. As shown in FIG. 9(b), estimated amount input screen 500 may include estimated amount input field 510, confirmation button 520, and the like. Estimated amount input field 510 may be an area where the estimated amount is input. Confirm button 520 may be a button that can be operated to confirm the estimated amount input in estimated amount input field 510 on estimated amount confirmation screen 400. When confirm button 520 is operated, pharmacy terminal 2 may close estimated amount input screen 500 and change estimated amount 420 on estimated amount confirmation screen 400 to the amount entered in estimated amount input field 510. When set button 450 is operated, pharmacy terminal 2 may close estimated amount confirmation screen 400 and change prescription status 340 to "dispensing completed."

[0067] Returning to FIG. 8, the payment execution pane 380 may be an area related to the execution of payment for the cost of providing medicines. The payment execution pane 380 may include a settings button 381, etc. The settings button 381 may be a button that can be operated to display a payment amount confirmation screen. The settings button 381 may be operable only when the prescription status 340 is "dispensing." The outline of the settings button 381 shown in FIG. 8 is indicated by a dotted line. The dotted line indicates that the settings button 381 cannot be operated.

[0068] FIG. 10(a) illustrates an example of a payment amount confirmation screen. The payment amount confirmation screen may be a screen for an employee to confirm the payment amount for the cost of providing pharmaceuticals. As illustrated in FIG. 10(a), the payment amount confirmation screen 600 may include patient information 610, a payment amount 620, a change button 630, a return button 660, and a set button 670. The patient information 610 may indicate, for example, the patient's name, date of birth, and gender. The payment amount 620 may indicate the current payment amount. The payment amount may also be the amount to be paid as the invoice amount for the cost of providing pharmaceuticals. If the payment amount has not yet been entered, the payment amount 620 may indicate a pre-set estimated amount. The change button 630 may be a button operable to display a payment amount input screen (described later). The payment amount input screen may be displayed, for example, as an overlay on the payment amount confirmation screen 600. The return button 660 may be a button operable to cancel setting the payment amount. The set button 670 is a button that can be operated to set the payment amount to the amount indicated by the payment amount 620. If the payment amount is not to be changed from the estimated amount, the employee can operate the set button 670 without displaying the payment amount input screen. When the set button 670 is operated, the billing amount may be confirmed as the estimated amount indicated by the payment amount 620. Furthermore, in response to the operation of the set button 670, the medicine receipt reservation server 1 may execute payment at the confirmed billing amount. Furthermore, the pharmacy terminal 2 may erase the payment amount confirmation screen 600 and change the prescription status 340 to "dispensing completed."

[0069] FIG. 10(b) is a diagram showing an example of a payment amount input screen. The payment amount input screen may be a screen for inputting the payment amount. As shown in FIG. 10(b), payment amount input screen 700 may include a payment amount input field 710 and a confirmation button 720. The payment amount input field 710 may be an area where the payment amount is input. The confirmation button 720 may be a button that can be operated to confirm the payment amount input in the payment amount input field 710 on the payment amount confirmation screen 600. When the confirmation button 720 is operated, the pharmacy terminal 2 may clear the payment amount input screen 700 and change the payment amount 620 on the payment amount confirmation screen 600 to the amount input in the payment amount input field 710. When the set button 670 is operated, the billing amount may be confirmed as the changed payment amount indicated by the payment amount 620.

[0070] Returning to FIG. 8, the view prescription button 390 may be a button that can be operated to display the prescription corresponding to the selected appointment.

[0071] When the prescription status stored in the reservation DB 14e indicates that dispensing is incomplete, the pharmacy screen information transmission unit 1105 may transmit, to the pharmacy terminal 2, pharmacy screen information that displays a pharmacy screen that can accept an operation to input an estimated amount. As described above, prescription statuses corresponding to incomplete dispensing may be “Sent,” “Received,” and “Dispensing.” Furthermore, when the prescription status stored in the reservation DB 14e indicates that dispensing is complete, the pharmacy screen information transmission unit 1105 may transmit, to the pharmacy terminal 2, pharmacy screen information that displays a pharmacy screen that cannot accept an operation to input an estimated amount. As shown in FIG. 4, prescription statuses corresponding to completed dispensing may be “Dispensing Completed” and “Delivered.” The pharmacy screen that can accept an operation to input an estimated amount may be, for example, the patient information screen 300. In this case, the operation to input an estimated amount may be, for example, an operation on the setting button 371 of the estimated amount input pane 370. By operating the estimated amount input pane 370, the employee can cause the pharmacy terminal 2 to display the estimated amount confirmation screen 400, and ultimately the estimated amount input screen 500. The employee can then enter the estimated amount on the estimated amount input screen 500. On the other hand, if the employee cannot operate the estimated amount input pane 370, the estimated amount confirmation screen 400 and the estimated amount input screen 500 are not displayed. Therefore, the employee cannot enter the estimated amount.

[0072] 11 is a diagram showing an example of a patient information screen. As shown in FIG. 11, prescription status 340 included in patient information screen 300 is set to "dispensing completed." The outline of setting button 371 is dotted. Therefore, setting button 371 cannot be operated.

[0073] The pharmacy screen information transmission unit 1105 may allow the operation to input the estimated amount even while the prescription status is "dispensing completed" on the condition that the estimated amount has been input once while the prescription status is "sent," "accepted," or "dispensing." If the prescription status is "delivered," the operation to input the estimated amount may be disabled.

[0074] The pharmacy screen capable of accepting an operation for inputting an estimated amount may be the estimated amount confirmation screen 400 or the estimated amount input confirmation screen 500. When the prescription status is "Sent," "Accepted," or "Dispensing," the pharmacy screen information sending unit 1105 may send the pharmacy screen information for displaying the estimated amount confirmation screen 400 or the estimated amount input confirmation screen 500 to the customer terminal 3. When the prescription status is "Dispensing" or "Delivered," the pharmacy screen information sending unit 1105 may not need to send the pharmacy screen information for displaying the estimated amount confirmation screen 400 or the estimated amount input confirmation screen 500 to the customer terminal 3.

[0075] The estimated amount information receiving unit 1106 may receive estimated amount information indicating the estimated amount of the cost for providing a medicine based on the prescription indicated by the prescription information transmitted by the prescription information transmitting unit 1103 from the pharmacy terminal 2 to which the prescription information was transmitted. For example, the estimated amount information receiving unit 1106 may receive estimated amount information indicating the estimated amount entered on the estimated amount input screen 500 and set on the estimated amount confirmation screen 400. The estimated amount information receiving unit 1106 may set the billing amount included in the reservation information stored in the reservation DB 14e as the estimated amount.

[0076] Here, the estimated amount information receiving unit 1106 may receive estimated amount information transmitted from the pharmacy terminal 2 in a state before medication instruction for the provision of pharmaceuticals is provided. Prescription statuses corresponding to a state before medication instruction is provided may be "sent," "accepted," and "dispensing." Although "dispensing completed" indicates that medication instruction is incomplete, it is not necessary to exclude cases where medication instruction is currently being provided. Therefore, "dispensing completed" does not have to be included in the state before medication instruction is provided.

[0077] For example, as described above, the status management unit 1104 may change the prescription status to "dispensing completed" in response to the estimated amount information receiving unit 1106 receiving estimated amount information from the pharmacy terminal 2. This ensures that estimated amount information is transmitted from the pharmacy terminal 2 before medication instructions are provided. Alternatively, on the condition that estimated amount information has already been received from the pharmacy terminal 2, the pharmacy screen information transmitting unit 1105 may transmit to the pharmacy terminal 2 a patient information screen 300 that can accept an operation to change the prescription status to "dispensing completed." This also ensures this. If estimated amount information has not yet been received, the pharmacy screen information transmitting unit 1105 may transmit a patient information screen 300 that cannot accept an operation to change the prescription status to "dispensing completed."

[0078] The estimated amount information sending unit 1107 may send the estimated amount information received by the estimated amount information receiving unit 1106 to the customer terminal 3 of the customer who has made a reservation to receive the medicine. For example, the estimated amount information sending unit 1107 may send the estimated amount information by email to the customer. Alternatively, the estimated amount information sending unit 1107 may send the estimated amount information in response to a request from the customer terminal 3. The estimated amount information sending unit 1107 may send, for example, customer screen information including the estimated amount information. The customer screen information may be information for displaying a customer screen on the customer terminal 3. The customer screen may be a screen that displays information related to the reservation to receive the medicine. The customer screen information may be an HTML document of a web page corresponding to the customer screen, or may be other information. The item name of the estimated amount displayed on the screen of the customer terminal 2 as a customer screen or email, etc. may be, for example, "estimated amount," "to be paid," or "billed amount."

[0079] The estimated amount information sending unit 1107 may send a customer status indicating the prescription status stored in the reservation DB 14e together with the estimated amount information to the customer terminal 3. The customer status may be information indicating the prescription status in a way that is suitable for the customer.

[0080] FIG. 12 is a diagram showing an example of a customer reservation list screen. For example, an operation for displaying the customer reservation list screen may be possible on the home screen of the pharmaceutical pickup reservation site or the reservation application acceptance completion screen 100. As shown in FIG. 12, the customer reservation list screen 800 may include one or more reservation information fields 810. The reservation information fields 810 may include information about reservations made by customers using the customer terminal 3. For example, the reservation information fields 810 may include a pharmacy name 811, a pickup date and time 812, a patient name 813, and a customer prescription status 814. The customer prescription status 814 may correspond to the prescription status. For example, the customer prescription status 814 corresponding to "Sent" may be "Previewing prescription." The customer prescription status 814 corresponding to "Accepted" may be "Prescription acceptance completed." The customer prescription status 814 corresponding to "Dispensing" may be "Preparing medication." The customer prescription status 814 corresponding to "Dispensing completed" may be "Preparing medication." The customer prescription status 814 corresponding to "Delivered" may be "Medicine Delivered." When the customer selects a reservation by selecting any of the reservation information fields 810 from the customer reservation list screen 800, the customer terminal 3 may display a reservation details screen.

[0081] FIG. 13 is a diagram showing an example of a reservation details screen. The reservation details screen may be a screen showing detailed contents of a selected reservation. For example, as shown in FIG. 13, the reservation details screen 900 may include a customer prescription status 910 and a reservation content display field 920. The reservation content display field 920 may include, for example, a pharmacy name 921, a pickup date and time 922, and a payment method 923. The customer prescription status 910 shown in FIG. 13 is "Preparing medication." Therefore, an estimated amount has not been entered in the pharmacy terminal 2, and therefore the estimated amount is not displayed.

[0082] FIG. 14 is a diagram showing another example of the reservation details screen. In FIG. 14, the same elements as in FIG. 13 are denoted by the same reference numerals. As shown in FIG. 14, the reservation details display field 920 may include, for example, a pharmacy name 921, a pickup date and time 922, and a payment method 923, as well as a billing amount 924. The billing amount 924 may be displayed when the customer prescription status 910 is "medicine ready" or "medicine delivered." When the customer prescription status 910 is "medicine ready," the billing amount 924 may indicate an estimated amount. When the customer prescription status 910 is "medicine delivered," the billing amount 924 may indicate an amount that has already been paid. Since the customer prescription status 910 shown in FIG. 14 is "medicine ready," the billing amount 924 of 2,500 yen is an estimated amount. As mentioned above, in the case where the prescription status is not changed to "Dispensing Completed" even when an estimated amount is set, the billing amount 924 indicating the estimated amount may be displayed even if the customer prescription status 910 is "Prescription Confirming," "Prescription Accepted," or "Medicine Preparing."

[0083] After receiving the estimated amount information by the estimated amount information receiving unit 1106, the final amount information receiving unit 1108 may receive final amount information indicating the final amount of the cost related to the provision of the medicine from the pharmacy terminal 2. For example, the final amount information receiving unit 1108 may receive the payment amount entered on the payment amount input screen 700 and set on the payment amount confirmation screen 600 as the final amount information.

[0084] The settlement unit 1109 may execute payment of the cost of the finalized amount indicated by the finalized amount information received by the finalized amount information receiving unit 1108. The settlement unit 1109 may execute payment when the payment method is online payment. In the case of over-the-counter payment, payment is made at the pharmacy. The finalized amount information receiving unit 1108 may execute payment of the cost of the finalized amount, for example, by communicating with the payment server 5. When payment is executed, the status management unit 1104 may change the payment status to "payment completed." The status management unit 1104 may also change the prescription status to "delivered."

[0085] The credit card information acquiring unit 1110 may acquire credit card information of a customer who has applied for a reservation to receive a medicine. For example, if the payment method included in the reservation application content information acquired from the customer terminal 3 by the prescription information receiving unit 1101 is "online," the credit card information acquiring unit 1110 may acquire the credit card information. The credit card information acquiring unit 1110 may acquire the credit card information from the credit card information DB 14b based on the customer ID and customer card ID included in the reservation application content information.

[0086] The confirmation unit 1111 may execute authorization based on the credit card information acquired by the credit card information acquisition unit 1110. For example, the confirmation unit 1111 may confirm whether the estimated amount indicated by the estimated amount information received by the estimated amount information receiving unit 1106 can be paid using the credit card of the customer who has requested the reservation for receiving the medicine. If the confirmation unit 1111 confirms that the estimated amount can be paid, the estimated amount information sending unit 1107 may send the estimated amount information to the customer terminal 3 of the customer who has requested the reservation for receiving the medicine. This allows the customer to be notified of the estimated amount after it has been confirmed that the estimated amount can be paid using a credit card. For example, this may be achieved by the status management unit 1104 changing the prescription status to "dispensing completed" on the condition that it is confirmed that the estimated amount can be paid. Alternatively, this may be achieved by the estimated amount information receiving unit 1106 setting the billing amount to the estimated interest amount on the condition that it is confirmed that the estimated amount can be paid. If the estimated amount cannot be paid, the estimated amount information sending unit 1107 may not send the estimated amount information. In this case, the system control unit 11 may forcibly cancel the medicine pickup reservation. Alternatively, the system control unit 11 may cause the customer terminal 3 to display a screen for selecting a payment method. On this screen, the customer may be able to select a credit card different from the one initially selected, or to select over-the-counter payment. When a credit card is selected, the credit card information acquisition unit 1110 may acquire the credit card information, and the confirmation unit 1111 may execute authorization based on the credit card information. Alternatively, the payment unit 1109 may forcibly change the payment method to over-the-counter payment. In this case, the estimated amount information transmission unit 1107 may transmit the estimated amount information to the customer terminal 3.

[0087] Furthermore, the confirmation unit 1111 may confirm whether a credit card can be used based on credit card information in response to an application for a reservation to receive a medicine. If the confirmation unit 1111 confirms that a credit card can be used, the reservation application acceptance information sending unit 1102 may send the reservation application acceptance information to the customer terminal 3. The amount of use to be confirmed is not particularly limited as long as it is confirmed that a credit card can be used. Examples of the amount of use to be confirmed include 0 yen, 1 yen, etc. If a credit card cannot be used, the system control unit 11 may refuse to accept the reservation application, may have the customer select another payment method, or may forcibly change the payment method to over-the-counter payment.

[0088] Furthermore, if the final amount indicated by the final amount information received by the final amount information receiving unit 1108 differs from the estimated amount indicated by the estimated amount information received by the estimated amount information receiving unit 1106, the confirmation unit 1111 may confirm, based on the credit card information, whether the final amount can be paid by credit card. If it is confirmed that the final amount can be paid, the settlement unit 1109 may execute the settlement. If the final amount cannot be paid, the settlement unit 1109 may not execute the settlement. The settlement unit 1109 may, for example, forcibly change the payment method to over-the-counter settlement.

[0089] If the final amount matches the estimated amount, confirmation was already made when the estimated amount was set. Therefore, it is not necessary to confirm whether the final amount can be paid. Therefore, the settlement unit 1109 may execute the settlement without confirmation by the confirmation unit 1111.

[0090] FIG. 15 is a diagram illustrating an example of the relationship between prescription status, payment status, authorization, and payment. As shown in FIG. 15, when a request for a drug pickup reservation is made, the confirmation unit 1111 sets the credit card usage amount to 0 yen and executes authorization. If this authorization confirms that payment is possible, the pickup reservation request is accepted, and the customer's prescription information is sent to the pharmacy terminal 2. At this time, the prescription status is set to "Sent." The payment status is also set to "Unpaid." After that, when the employee sets the estimated amount as the billing amount, the confirmation unit 1111 sets the credit card usage amount to the estimated amount and executes authorization. If this authorization confirms that payment is possible, the prescription status is changed to "Dispensing Completed." After that, when medication instructions are completed and the employee sets the payment amount, the confirmation unit 1111 may determine whether the payment amount matches the estimated amount. If the payment amount matches the estimated amount, the payment unit 1109 executes payment as is. If the payment amount differs from the estimated amount, the confirmation unit 1111 sets the credit card usage amount as the payment amount and executes authorization. If this authorization confirms that payment is possible, the settlement unit 1109 executes the settlement.

[0091] [1-4. Operation of communication system] Next, the operation of the communication system S will be described with reference to Figures 16 to 20. The order of processing is not limited to the order shown in these figures. Furthermore, at least one of the steps shown in these figures may not be executed. The system control unit 11 of the medicine reservation reception server 1 may execute the processing shown in Figures 16 to 20 in accordance with various program codes included in the server program.

[0092] FIG. 16 is a sequence diagram showing an example of the processing of the communication system S when making a reservation to receive a medicine. The customer inputs reservation application details on a predetermined screen of the medicine reception reservation site. At this time, it is assumed that the customer selects a paper prescription. The customer takes a photo of the prescription, for example, with the camera of the customer terminal 3, and generates prescription image data. Then, based on the customer's operation, the customer terminal 3 transmits the reservation application information and prescription image data to the medicine reception reservation server 1 (step S101), as shown in FIG. 16. The credit card information acquisition unit 1110 of the medicine reception reservation server 1 determines whether the payment method included in the reservation application information is online payment (step S102). If the payment method is online payment (step S102: YES), the credit card information acquisition unit 1110 acquires credit card information associated with the same combination of customer ID and customer card ID included in the reservation application information from the credit card information DB 14b (step S102).

[0093] Next, the confirmation unit 1111 executes authorization for 0 yen (step S104). For example, the confirmation unit 1111 may send an authorization request to the payment server 5. The authorization request may include the credit card usage amount and credit card information. Here, the confirmation unit 1111 sets the usage amount to 0 yen. The payment server 5 that receives the authorization request may determine whether to approve credit. For example, the payment server 5 may determine whether the credit card information is information about a legitimate credit card. The payment server 5 may also determine whether the credit card expiration date has not expired. The payment server 5 may also determine whether the usage amount is equal to or less than the available credit limit stored in association with the credit card number included in the credit card information. The available credit limit may be the amount of the credit card that has not yet been used. The payment server 5 may approve credit if the credit card information is legitimate, the credit card expiration date has not expired, and the usage amount is equal to or less than the available credit limit. In other words, it is determined that payment using a credit card is possible. If credit is approved, the payment server 5 may set a credit limit. For example, the payment server 5 may generate a new approval number. The payment server 5 may store, as credit limit information, for example, a credit card number, an approval number, and a usage amount in association with each other. The payment server 5 may also subtract the usage amount from the available balance. Note that since the current usage amount is 0 yen, there is no change in the available balance. The payment server 5 may send an authorization response indicating the result of the determination as to whether or not to approve the credit to the medicine receipt reservation server 1. If the credit is approved, the authorization response may include the approval number.

[0094] The confirmation unit 1111 of the medicine receipt reservation server 1 determines whether payment is possible based on the authorization response (step S105). If payment is not possible (step S105: NO), the process shown in FIG. 16 ends. After this, for example, the customer may reselect a payment method. If payment is possible (step S105: YES) or if the payment method is over-the-counter payment (step S102: NO), the prescription information transmission unit 1103 transmits the prescription image data and prescription ID received from the customer terminal 3 to the pharmacy terminal 2 (step S106). At this time, the prescription information transmission unit 1103 may generate a prescription ID for the prescription image data. The prescription information transmission unit 1103 may also identify the pharmacy terminal 2 to which the prescription image data is to be transmitted based on the pharmacy ID included in the reservation application content information. The pharmacy terminal 2 may store the prescription image data and the prescription ID received from the medicine receipt reservation server 1 in association with each other. Next, the prescription information receiving unit 1101 stores the reservation information in the reservation DB 14e (step S107). For example, the prescription information receiving unit 1101 may generate a new reception number. The prescription information receiving unit 1101 may acquire the customer ID, patient ID, pharmacy ID, receipt date and time, medication instruction method, payment method, etc. from the reservation application content information. The prescription information receiving unit 1101 may generate reservation information including the information acquired from the reservation application content information, the reception number, the receipt date, the prescription ID, the prescription status indicating "sent," the payment status indicating "unpaid," etc. If authorization is executed, the prescription information receiving unit 1101 may include the customer card ID and the approval number in the reservation information. At this point, the prescription information receiving unit 1101 may not set the billing amount included in the reservation information. Next, the reservation application acceptance information sending unit 1102 sends the HTML text of the reservation application acceptance completion screen to the customer terminal 3 (step S108). The customer terminal 3 displays a reservation application acceptance completion screen based on the HTML text (step S109).

[0095] FIG. 17 is a diagram showing an example of a patient information screen information transmission process executed by the system control unit 11 of the medicine receipt reservation server 1 according to this embodiment. For example, when the pharmacy terminal 2 displays the pharmacy reservation list screen 200, a pharmacy employee selects a reservation from the pharmacy reservation list screen 200. Upon detecting this selection, the customer terminal 3 may transmit a patient information screen information request to the medicine receipt reservation server 1. The patient information screen information request may include, for example, the pharmacy ID of the pharmacy and the reception number of the selected reservation. In response to receiving the patient information screen information request from the pharmacy terminal 2, the system control unit 11 may execute a patient information screen information transmission process.

[0096] As shown in FIG. 17, the pharmacy screen information transmission unit 1105 acquires an HTML document template for the patient information screen 300 from the storage unit 14 (step S201). Next, the pharmacy screen information transmission unit 1105 acquires reservation information corresponding to the selected reservation from the reservation DB 14e based on the reception number included in the patient information screen information request (step S202). Next, the pharmacy screen information transmission unit 1105 adds information to the HTML document for the patient information screen 300 based on the acquired reservation information (step S203). For example, the pharmacy screen information transmission unit 1105 may acquire a patient ID, receipt date and time, payment method, payment status, prescription status, prescription ID, etc. from the reservation information. The prescription ID may be transmitted to the pharmacy terminal 2 and used to search for prescription information stored in the pharmacy terminal 2. The pharmacy screen information transmission unit 1105 may acquire patient information including a patient ID from the patient DB 14c. The pharmacy screen information sending unit 1105 may add patient information, receipt date and time, payment method, payment status, prescription status, and prescription ID to the HTML document.

[0097] Next, the pharmacy screen information transmission unit 1105 determines whether the prescription status is "Sent," "Received," or "Dispensing" (step S204). If the prescription status is "Sent," "Received," or "Dispensing" (step S204: YES), the pharmacy screen information transmission unit 1105 enables the setting button 371 in the estimated amount input pane 370 in the HTML document. If the prescription status is "Dispensing completed" or "Delivered" (step S204: NO), the pharmacy screen information transmission unit 1105 disables the setting button 371. A setting button that is enabled is operable. A setting button that is disabled is inoperable. The pharmacy screen information transmission unit 1105 may also enable or disable the setting buttons in the prescription reception pane 350, dispensing start pane 360, and payment execution pane 380 based on the prescription status. After step S205 or step S206, the pharmacy screen information transmission unit 1105 transmits the HTML document of the patient information screen 300 to the pharmacy terminal 2 (step S207), and the patient information screen information transmission process ends. The pharmacy terminal 2 displays the patient information screen 300 based on the HTML document.

[0098] FIG. 18 is a sequence diagram showing an example of the processing of communication system S when an estimated amount is input. For example, a pharmacy employee displays patient information screen 300 on pharmacy terminal 2 as described above. At this time, the prescription status is "Sent." The employee checks the prescription information on patient information screen 300 and dispenses the medication. When dispensing is complete, the employee calculates the estimated amount. Then, the employee operates set button 371. This operation is accepted if the prescription status is "Sent," "Received," or "Dispensing." In response to this operation, customer terminal 3 displays estimated amount confirmation screen 400. When the employee operates change button 430 on estimated amount confirmation screen 400, pharmacy terminal 2 displays estimated amount input screen 500 as shown in FIG. 18 (step S301). The employee enters the estimated amount on estimated amount input screen 500 and operates confirm button 520 (step S302). Upon detecting this operation, the pharmacy terminal 2 transmits estimated amount information indicating the estimated amount to the pharmaceutical receipt reservation server 1 (step S303). The pharmacy screen information transmission unit 1105 of the pharmaceutical receipt reservation server 1, which has received the estimated amount information, transmits the HTML document of the estimated amount confirmation screen 400 to the pharmacy terminal 2 (step S304). At this time, the pharmacy screen information transmission unit 1105 may set the estimated amount 420 on the estimated amount confirmation screen 400 to the estimated amount indicated by the received estimated amount information. The pharmacy terminal 2 displays the estimated amount confirmation screen 400 based on the HTML document (step S305). The employee operates the setting button 450 on the estimated amount confirmation screen 400 (step S306). Upon detecting this operation, the pharmacy terminal 2 transmits an estimated amount setting request to the pharmaceutical receipt reservation server 1 (step S307). The estimated amount setting request may include the reception number and estimated amount of the selected reservation.

[0099] The prescription information receiving unit 1101 of the medicine receipt reservation server 1 that has received the estimated price setting request searches the reservation DB 14e for reservation information including the reception number included in the estimated price setting request. The prescription information receiving unit 1101 sets the billing amount included in the searched reservation information as the estimated price included in the estimated price setting request (step S308). Next, the credit card information acquiring unit 1110 determines whether the payment method included in the reservation information is online payment (step S309). If the payment method is online payment (step S310: YES), the credit card information acquiring unit 1110 acquires credit card information and an approval number from the reservation information (step S311). Next, the confirmation unit 1111 executes authorization for the estimated price (step S104), similar to step S104 shown in FIG. 16. Before executing the authorization, the confirmation unit 1111 may cancel the previously executed authorization based on the approval number. As a result, the payment server 5 releases the set credit limit.

[0100] The confirmation unit 1111 determines whether payment is possible based on the authorization response from the payment server 5 (step S312). If payment is impossible (step S313: NO), the confirmation unit 1111 changes the payment method included in the reservation information to over-the-counter payment (step S313), and the process shown in Fig. 18 ends. After that, the employee may, for example, confirm that the payment method has been changed to over-the-counter payment, and then check the estimated amount again.

[0101] If payment is possible (step S312: YES), or if the payment method is over-the-counter payment (step S309: NO), the status management unit 1104 sets the prescription status included in the reservation information to "dispensing completed" (step S314).

[0102] FIG. 19 is a diagram showing an example of reservation details screen information transmission processing executed by the system control unit 11 of the pharmaceutical receipt reservation server 1 according to this embodiment. For example, when the customer terminal 3 displays the customer reservation list screen 800, the customer selects one of the reservations from the customer reservation list screen 800. Upon detecting this selection, the customer terminal 3 may transmit a reservation details screen information request to the pharmaceutical receipt reservation server 1. The reservation details screen information request may include, for example, the reception number of the selected reservation. In response to receiving the reservation details screen information request from the customer terminal 3, the system control unit 11 may execute the reservation details screen information transmission processing.

[0103] As shown in FIG. 19 , the estimated amount information sending unit 1107 acquires an HTML document template for the appointment details screen 900 from the storage unit 14 (step S401). Next, the estimated amount information sending unit 1107 acquires appointment information corresponding to the selected appointment from the appointment DB 14e based on the reception number included in the appointment details screen information request (step S402). Next, the estimated amount information sending unit 1107 adds information to the HTML document for the appointment details screen 900 based on the appointment information (step S403). For example, the estimated amount information sending unit 1107 may acquire a pharmacy ID, pickup date and time, payment method, prescription status, etc. from the appointment information. The estimated amount information sending unit 1107 may acquire a pharmacy name associated with the pharmacy ID from the pharmacy DB 14d. The estimated amount information sending unit 1107 may also acquire a customer prescription status corresponding to the prescription status. The estimated amount information sending unit 1107 may add the information acquired from the appointment information, the pharmacy name, and the customer prescription status to the HTML document.

[0104] Next, the estimated amount information sending unit 1107 determines whether the billing amount included in the reservation information has been set (step S404). If the billing amount has been set (step S404), the estimated amount information sending unit 1107 further adds the billing amount to the HTML document (step S405). After step S405, or if the billing amount has not been set (step S404: NO), the estimated amount information sending unit 1107 sends the HTML document of the reservation details screen to the customer terminal 3 (step S406), and the reservation details screen information sending process ends. The customer terminal 3 displays the reservation details screen 900 based on the HTML document.

[0105] FIG. 20 is a sequence diagram showing an example of the processing of communication system S when a payment amount is entered. For example, a pharmacy employee displays payment amount input screen 700 on pharmacy terminal 2 and enters the payment amount. Next, the employee operates confirmation button 720 on payment amount input screen 700. Detecting this operation, pharmacy terminal 2 displays payment amount confirmation screen 600. The employee operates set button 670 on payment amount confirmation screen 600. Detecting this operation, pharmacy terminal 2 transmits the payment amount and the reception number of the selected reservation to medicine receipt reservation server 1 (step S501), as shown in FIG. 20.

[0106] The credit card information acquisition unit 1110 of the medicine receipt reservation server 1 acquires reservation information including the reception number received from the pharmacy terminal 2 from the reservation DB 14e. The credit card information acquisition unit 1110 determines whether the payment method included in the reservation information is online payment (step S502). If the payment method is online payment (step S502: YES), the payment unit 1109 determines whether the payment amount received from the pharmacy terminal 2 differs from the billing amount included in the reservation information (step S503). If the payment amount differs from the billing amount (step S503: YES), the credit card information acquisition unit 1110 acquires credit card information and an approval number from the reservation information (step S504). Next, the confirmation unit 1111 executes authorization for the payment amount (step S505), similar to step S104 shown in FIG. 16 . Before executing the authorization, the confirmation unit 1111 may cancel the previously executed authorization based on the approval number.

[0107] The confirmation unit 1111 determines whether or not payment is possible based on the authorization response from the payment server 5 (step S506). If payment is impossible (step S506: NO), the confirmation unit 1111 changes the payment method included in the reservation information to over-the-counter payment (step S507), and the process shown in Fig. 20 ends.

[0108] If payment is possible (step S506: YES) or if the payment amount matches the estimated amount (step S503: NO), the payment unit 1109 executes payment (step S508). For example, the payment unit 1109 may send a payment request to the payment server 5. The payment request may include credit card information and the latest approval number. Upon receiving the payment request, the payment server 5 may search for the usage amount associated with the credit card number and approval number included in the payment request. The payment server 5 may confirm payment of the usage amount and may also confirm the invoice of the usage amount to the credit card user.

[0109] After step S508, or if the payment method is over-the-counter payment (step S502: NO), the status management unit 1104 changes the prescription status included in the reservation information to "delivered" (step S509). The status management unit 1104 also changes the payment status included in the reservation information to "payment completed" (step S510). Next, the pharmacy screen information transmission unit 1105 transmits an HTML document of a payment completion screen to the pharmacy terminal 2 (step S511). The payment completion screen may be a screen indicating that payment has been completed. The pharmacy terminal 2 displays the payment completion screen based on the HTML document (step S512). Note that, if the payment method is over-the-counter payment, the pharmacy screen information transmission unit 1105 may simply erase the payment amount confirmation screen 600 without causing the pharmacy terminal 2 to display the payment completion screen.

[0110] As described above, according to this embodiment, the pharmaceutical receipt reservation server 1 may acquire prescription information. Alternatively, the pharmaceutical receipt reservation server 1 may transmit the prescription information to the pharmacy terminal 2. Alternatively, the pharmaceutical receipt reservation server 1 may receive estimated cost information from the pharmacy terminal 2. In this case, the pharmaceutical receipt reservation server 1 may receive estimated cost information transmitted from the pharmacy terminal 2 before the implementation of medication instructions related to the provision of pharmaceuticals. Alternatively, the pharmaceutical receipt reservation server 1 may transmit estimated cost information to the customer terminal 3. Therefore, estimated cost information can be transmitted to the customer terminal 3 before the implementation of medication instructions. Therefore, the amount of costs related to the provision of medical pharmaceuticals can be provided to the customer in advance.

[0111] Here, after receiving the estimated amount information, the medicine receipt reservation server 1 may receive final amount information from the pharmacy terminal 2. The medicine receipt reservation server 1 may also execute payment for the final amount indicated by the final amount information. In this case, the pharmacy can receive payment for the cost related to the provision of the medicine.

[0112] Here, the pharmaceutical receipt reservation server 1 may acquire credit card information. Furthermore, the pharmaceutical receipt reservation server 1 may confirm whether payment of the estimated amount can be made by credit card based on the credit card information. If the pharmaceutical receipt reservation server 1 confirms that payment is possible, it may transmit estimated amount information to the customer terminal 3. In this case, once it has been confirmed that the cost of providing the medical drug can be paid, the amount of that cost can be provided to the customer in advance.

[0113] Here, if the confirmed amount differs from the estimated amount, the pharmaceutical receipt reservation server 1 may check, based on credit card information, whether the confirmed amount can be paid by credit card. Furthermore, if the pharmaceutical receipt reservation server 1 checks that the confirmed amount can be paid, it may execute payment. Furthermore, if the confirmed amount matches the estimated amount, the pharmaceutical receipt reservation server 1 may execute payment without checking whether the confirmed amount can be paid. Whether the confirmed amount has been changed from the estimated amount or not, payment can be executed after properly checking whether payment by credit card is possible.

[0114] Alternatively, the pharmaceutical receipt reservation server 1 may receive reservation application content information from the customer terminal 3. Alternatively, upon receiving the reservation application content information, the pharmaceutical receipt reservation server 1 may check, based on the credit card information, whether payment by credit card is possible. Alternatively, if payment is possible, the pharmaceutical receipt reservation server 1 may send reservation application acceptance information to the customer terminal 3. In this case, when an application for pharmaceutical delivery based on a prescription is made, it is checked whether payment by credit card is possible. If payment by credit card is possible, the application for pharmaceutical delivery is accepted. Therefore, the application for pharmaceutical delivery can be accepted after it has been confirmed that a credit card can be used.

[0115] The pharmaceutical receipt reservation server 1 may also store a prescription status indicating that the dispensing of the pharmaceutical is incomplete in the reservation DB 14e. The pharmaceutical receipt reservation server 1 may also change the prescription status to "dispensing completed" in response to communication from the pharmacy terminal 2 that has received the prescription information. When the prescription status indicates that the dispensing of the pharmaceutical is incomplete, the pharmaceutical receipt reservation server 1 may also transmit to the pharmacy terminal 2 patient information screen information that causes the pharmacy terminal 2 to display a patient information screen that can accept an operation for inputting an estimated amount. The pharmaceutical receipt reservation server 1 may also receive estimated amount information that indicates the estimated amount input on the patient information screen. In this case, the pharmacy can input the estimated amount before medication instructions are provided. Therefore, the amount of the cost related to the provision of the ethical pharmaceutical can be provided to the customer in advance.

[0116] Here, the medicine receipt reservation server 1 may transmit a customer prescription status indicating the prescription status together with estimated amount information to the customer terminal 3. In this case, the status of dispensing is presented to the customer along with the amount of the cost for providing the medical medicine. Therefore, the customer can check the amount of the cost in advance and can also confirm whether the medicine is ready for receipt.

[0117] Furthermore, the medicine receipt reservation server 1 may change the prescription status to "dispensing completed" in response to receiving the estimated amount information. In this case, communication from the pharmacy terminal 2 to the medicine receipt reservation server 1 after the dispensing of the medicine is completed includes sending the estimated amount information. Therefore, it is possible to provide the customer with the amount of the cost related to the provision of the ethical medicine in advance, while making it possible to estimate the costs related to the provision of the medicine by the time dispensing is completed.

[0118] [2. Second Embodiment] Next, a second embodiment will be described. Except for the points described below, the second embodiment may be the same as the first embodiment. In this embodiment, the estimated amount may be determined automatically, rather than having an employee input the estimated amount into the pharmacy terminal 2. For example, the pharmacy terminal 2 may automatically calculate the estimated amount. In this case, the pharmacy terminal 2 may be a terminal device or may actually be a server device. The pharmacy terminal 2 may automatically determine the estimated amount in response to receiving prescription information transmitted from the medicine pickup reservation server 1, for example. The prescription information transmission unit 1103 of the medicine reservation reception server 1 may transmit prescription information to the pharmacy terminal 2 in response to a medicine pickup reservation being made. The pharmacy terminal 2 may identify the medicine to be provided and the prescribed amount based on the prescription information. The pharmacy terminal 2 may calculate the price of the medicine based on the identified information. The pharmacy terminal 2 may also automatically determine or calculate the dispensing amount, medication instruction fee, etc. In this manner, the pharmacy terminal 2 may calculate the estimated amount. The pharmacy terminal 2 may transmit the estimated amount information in response to receiving the prescription information.

[0119] The prescription information sending unit 1103 of the pharmaceutical reservation reception server 1 may send to the customer terminal 3, together with the estimated price information received from the pharmacy terminal 2, reservation application acceptance information indicating that the application for pharmaceutical provision has been accepted. For example, the prescription information sending unit 1103 may operate as the reservation application acceptance information sending unit 1102. The prescription information sending unit 1103 may send, for example, an email addressed to the customer who has made the reservation. This email may include the estimated price along with a message indicating that the application for pharmaceutical receipt has been accepted. Alternatively, the prescription information sending unit 1103 may send an HTML document of a reservation application acceptance completion screen including the estimated price.

[0120] Fig. 21 is a diagram showing an example of a reservation application acceptance completion screen. In Fig. 21, the same elements as in Fig. 6 are assigned the same reference numerals. As shown in Fig. 21, the reservation application acceptance completion screen 100 may include, for example, a message 110, a home button 120, and a reservation list button 130, as well as an invoice amount 140. The invoice amount 140 indicates the estimated amount.

[0121] As described above, according to this embodiment, when an application for provision of a pharmaceutical product is accepted, the amount of the cost for provision of a medical pharmaceutical product can be provided to the customer in advance.

[0122] (Supplementary Note 1) A pharmaceutical supply application processing device characterized by comprising: a prescription information acquisition means for acquiring prescription information indicating a prescription for a pharmaceutical to be provided to a customer; a prescription information transmission means for transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information receiving means for receiving, from the pharmacy device, estimated amount information indicating an estimated amount of costs related to the provision of the pharmaceutical based on the prescription indicated by the transmitted prescription information, the estimated amount information receiving means receiving the estimated amount information transmitted from the pharmacy device in a state before medication instructions related to the provision of the pharmaceutical are implemented; and an estimated amount information transmission means for transmitting the acquired estimated amount information to a customer terminal device used by the customer.

[0123] (Appendix 2) The pharmaceutical provision application processing device described in Appendix 1 is further characterized in that it comprises a final amount information receiving means that receives final amount information indicating the final amount of the cost from the pharmacy device after the estimated amount information is received by the estimated amount information receiving means, and a payment means that executes payment for the final amount of the cost indicated by the received final amount information.

[0124] (Appendix 3) A pharmaceutical supply application processing device as described in Appendix 1 or 2, further comprising a credit card information acquisition means for acquiring credit card information of a credit card designated by the customer, and an estimated amount payment confirmation means for confirming, based on the acquired credit card information, whether the estimated amount indicated by the acquired estimated amount information can be paid with the credit card, wherein the estimated amount information sending means sends the estimated amount information when it is confirmed by the estimated amount payment confirmation means that the payment is possible.

[0125] (Appendix 4) The pharmaceutical provision application processing device described in Appendix 3 is further provided with a fixed amount payment confirmation means for confirming whether the fixed amount can be paid by credit card based on the acquired credit card information if the fixed amount indicated by the received fixed amount information differs from the estimated amount indicated by the transmitted estimated amount information, and the payment means executes the payment if the fixed amount payment confirmation means confirms that the fixed amount can be paid, and if the fixed amount indicated by the received fixed amount information matches the estimated amount indicated by the transmitted estimated amount information, the confirmation by the fixed amount payment confirmation means is omitted and the payment means executes the payment.

[0126] (Appendix 5) A pharmaceutical provision application processing device as described in Appendix 3 or 4, further comprising: an application information receiving means for receiving application information indicating an application for provision of the pharmaceutical based on the prescription from the customer terminal device; an application payment confirmation means for confirming whether the credit card can be used based on the acquired credit card information in response to the application information being received by the application information receiving means; and an acceptance information sending means for sending acceptance information indicating that the application has been accepted to the customer terminal device when the application payment confirmation means confirms that the credit card can be used.

[0127] (Supplementary Note 6) The pharmaceutical provision application processing device according to any one of Supplementary Notes 1 to 5, further comprising: a memory control means for storing in a memory means a dispensing status related to the dispensing of the pharmaceutical based on the prescription indicated by the acquired prescription information, the dispensing status being set to a dispensing incomplete status indicating that the dispensing of the pharmaceutical is incomplete; a change means for changing the dispensing status stored in the memory means to a dispensing completed status indicating that the dispensing of the pharmaceutical has been completed but the medication instruction is incomplete in response to communication from the pharmacy device that has received the transmitted prescription information; and an operation acceptance screen information sending means for sending to the pharmacy device, operation acceptance screen information that causes the pharmacy device to display an operation acceptance screen that can accept an operation for inputting the estimated amount, when the dispensing status stored in the memory means is the dispensing incomplete status,

[0128] (Appendix 7) The pharmaceutical supply application processing device described in Appendix 6, characterized in that the estimated amount information sending means sends status information indicating the dispensing status stored in the storage means to the customer terminal device along with the estimated amount information.

[0129] (Appendix 8) The pharmaceutical provision application processing device described in Appendix 6 or 7, characterized in that the change means changes the dispensing status to the dispensing completed status in response to the estimated amount information being received by the estimated amount information sending means.

[0130] (Appendix 9) A pharmaceutical supply application processing device described in any one of Appendices 1 to 5, characterized in that the estimated amount information receiving means receives the estimated amount information sent from the pharmacy device in response to the pharmacy device receiving the transmitted prescription information, and the estimated amount information sending means sends the estimated amount information together with acceptance information indicating that the application for the supply of the pharmaceutical has been accepted to the customer terminal device.

[0131] (Appendix 10) A pharmaceutical supply application processing method executed by a computer, comprising: a prescription information acquisition step of acquiring prescription information indicating a prescription for a pharmaceutical to be provided to a customer; a prescription information transmission step of transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information reception step of receiving, from the pharmacy device, estimated amount information indicating an estimated amount of costs related to the provision of the pharmaceutical based on the prescription indicated by the transmitted prescription information, wherein the estimated amount information reception step receives estimated amount information transmitted from the pharmacy device in a state before medication instructions related to the provision of the pharmaceutical are implemented; and an estimated amount information transmission step of transmitting the acquired estimated amount information to a customer terminal device used by the customer.

[0132] (Appendix 11) A pharmaceutical supply application processing program that causes a computer to function as: a prescription information acquisition means that acquires prescription information indicating a prescription for a pharmaceutical to be provided to a customer; a prescription information transmission means that transmits the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information receiving means that receives, from the pharmacy device, estimated amount information that indicates an estimated amount of the cost related to the provision of the pharmaceutical based on the prescription indicated by the transmitted prescription information, wherein the estimated amount information receiving means receives the estimated amount information transmitted from the pharmacy device before medication instructions related to the provision of the pharmaceutical are implemented; and an estimated amount information transmission means that transmits the acquired estimated amount information to a customer terminal device used by the customer. [Explanation of symbols]

[0133] 1. Medicine receipt reservation server 2 Pharmacy terminals 3. Customer terminal 4. Electronic prescription management system 5. Payment Server 11 System control section 12 System Bus 13 Input / Output Interface 14 Storage section 14a Member DB 14b Credit card information DB 14c Patient DB 14d Pharmacy DB 14e Reservation DB 1101 Prescription Information Acquisition Department 1102 Reservation application reception information transmission unit 1103 Prescription information transmission unit 1104 Status Management Department 1105 Pharmacy screen information transmission unit 1106 Estimated amount information receiving unit 1107 Estimated Amount Information Transmission Unit 1108 Final amount information receiving unit 1109 Payment Department 1110 Credit Card Information Acquisition Department 1111 Confirmation Department NW Network

Claims

1. prescription information acquisition means for acquiring prescription information indicating a prescription for a drug to be provided to a customer; a prescription information transmitting means for transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information receiving means for receiving, from the pharmacy device, estimated amount information indicating an estimated amount of costs related to the provision of the medicine based on the prescription indicated by the transmitted prescription information, the estimated amount information receiving means receiving the estimated amount information transmitted from the pharmacy device in a state before medication instruction related to the provision of the medicine is provided; an estimated price information transmitting means for transmitting the acquired estimated price information to a customer terminal device used by the customer; A pharmaceutical supply application processing device comprising:

2. a finalized amount information receiving means for receiving finalized amount information indicating a finalized amount of the cost from the pharmacy device after the estimated amount information receiving means receives the estimated amount information; a payment means for executing payment of the fixed amount indicated by the received fixed amount information; The pharmaceutical supply application processing device according to claim 1, further comprising:

3. a credit card information acquisition means for acquiring credit card information of a credit card designated by the customer; an estimated amount payment confirmation means for confirming whether the estimated amount indicated by the acquired estimated amount information can be paid by the credit card based on the acquired credit card information; Further provided with 3. The pharmaceutical supply application processing device according to claim 2, wherein the estimated amount information transmitting means transmits the estimated amount information when the estimated amount payment confirming means confirms that the payment is possible.

4. and a payment confirmation means for confirming whether the payment of the fixed amount can be made by the credit card based on the acquired credit card information when the fixed amount indicated by the received fixed amount information is different from the estimated amount indicated by the transmitted estimated amount information. The settlement means executes the settlement when the fixed amount payment confirmation means confirms that the fixed amount can be paid, A pharmaceutical supply application processing device as described in claim 3, characterized in that if the final amount indicated by the received final amount information matches the estimated amount indicated by the transmitted estimated amount information, the confirmation by the final amount payment confirmation means is omitted and the payment means executes the payment.

5. an application information receiving means for receiving application information indicating an application for provision of the medicine based on the prescription from the customer terminal device; an application payment confirmation means for confirming whether the credit card can be used based on the acquired credit card information in response to the application information being received by the application information receiving means; an acceptance information sending means for sending acceptance information indicating that the application has been accepted to the customer terminal device when the application and payment confirmation means has confirmed that the credit card can be used; The pharmaceutical supply application processing device according to claim 3 or 4, further comprising:

6. a storage control means for storing in a storage means a dispensing status regarding dispensing of the medicine based on the prescription indicated by the acquired prescription information, the dispensing status being set to a dispensing incomplete status indicating that dispensing of the medicine is incomplete; and a change means for changing the dispensing status stored in the storage means to a dispensing completion status indicating that dispensing of the medicine has been completed and that the medication instruction has not been completed in response to communication from the pharmacy device that has received the transmitted prescription information; and an operation reception screen information sending means for sending, to the pharmacy device, operation reception screen information that causes the pharmacy device to display an operation reception screen that can accept an operation for inputting the estimated amount when the dispensing status stored in the storage means is the dispensing incomplete state; Further provided with 2. The drug supply application processing device according to claim 1, wherein the estimated amount information transmitting means receives the estimated amount information indicating the input estimated amount.

7. 7. The pharmaceutical supply application processing device according to claim 6, wherein the estimated amount information transmitting means transmits, together with the estimated amount information, status information indicating the dispensing status stored in the storage means to the customer terminal device.

8. 8. The pharmaceutical supply application processing device according to claim 6, wherein the change means changes the dispensing status to the dispensing completed status in response to the estimated amount information being received by the estimated amount information transmission means.

9. the estimated amount information receiving means receives the estimated amount information transmitted from the pharmacy device in response to the pharmacy device receiving the transmitted prescription information; A pharmaceutical supply application processing device as described in any one of claims 1 to 4, characterized in that the estimated price information sending means sends to the customer terminal device, together with the estimated price information, acceptance information indicating that the application for the provision of the pharmaceutical has been accepted.

10. A computer-implemented pharmaceutical supply application processing method, comprising: a prescription information acquisition step of acquiring prescription information indicating a prescription for a drug to be provided to the customer; a prescription information transmitting step of transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information receiving step of receiving, from the pharmacy device, estimated amount information indicating an estimated amount of costs related to the provision of the medicine based on the prescription indicated by the transmitted prescription information, the estimated amount information receiving step receiving the estimated amount information transmitted from the pharmacy device in a state before medication instruction related to the provision of the medicine is provided; an estimated price information transmitting step of transmitting the acquired estimated price information to a customer terminal device used by the customer; A pharmaceutical supply application processing method comprising:

11. Computer, prescription information acquisition means for acquiring prescription information indicating a prescription for a drug to be provided to a customer; a prescription information transmitting means for transmitting the acquired prescription information to a pharmacy device used by the pharmacy; an estimated amount information receiving means for receiving, from the pharmacy device, estimated amount information indicating an estimated amount of costs related to the provision of the medicine based on the prescription indicated by the transmitted prescription information, the estimated amount information receiving means receiving the estimated amount information transmitted from the pharmacy device in a state before medication instruction related to the provision of the medicine is provided; an estimated price information transmitting means for transmitting the acquired estimated price information to a customer terminal device used by the customer; A pharmaceutical supply application processing program characterized by causing the program to function as a pharmaceutical supply application processing program.

Images