JP7481053B1 - Medication support system, medication support method, and medication support program - Google Patents

Abstract

[Problem] To provide a drug support system that can deliver drugs even in foreign countries, taking into consideration factors such as drug regulations in the delivery destination. [Solution] The system includes a receiving unit that receives information written on a prescription from a patient's terminal, an information generating unit that generates dispensing data indicating drugs based on the information written on the prescription, an auditing unit that audits the dispensing data, and an instruction unit that issues an instruction to deliver a prescription drug consisting of drugs to a patient. [Selected Figure] Figure 1

Description

The present invention relates to a drug support system, a drug support method, and a drug support program in which, when a patient is attempting to obtain a prescription drug via the Internet, a pharmacist remotely dispenses the drug and delivers the dispensed prescription drug to the patient.

Traditionally, patients would bring their prescriptions to pharmacies and pharmacists would fill them on-site. With the spread of the Internet, more and more pharmacists are filling prescriptions online and delivering the filled medications to the patient's address.

The dispensing support system disclosed in Patent Document 1 has the function of remotely auditing dispensing actions by comparing dispensing information generated based on an image of the prescription with the prescription information written on the prescription, making it possible to reduce the workload of pharmacists.

The prescription drug order management system disclosed in Patent Document 2 includes an acquisition unit that acquires multiple data such as data indicating the contents of a prescription, a medication instruction data generation unit, a storage unit that stores various data, and a medication instruction management unit that manages the execution status of medication instructions. The prescription drug order management system acquires information indicating the contents of the prescription and application information of the patient, and generates this as order data. The prescription drug order management system also generates information such as the date and time of remote medication instructions to the patient based on the order data, and transmits this information to the pharmacist in charge. In this case, the pharmacist in charge can provide remote medication instructions to the patient at the specified date and time, thereby reducing the workload of the pharmacy.

JP 2023-107632 A JP 2023-096917 A

However, the systems described in Patent Documents 1 and 2 only disclose remote dispensing within Japan, and when attempting to deliver dispensed prescription drugs to a destination abroad, there is a possibility that the drugs cannot be delivered to the foreign country due to factors such as drug regulations in the foreign country.

The present invention has been made in consideration of the above problems, and aims to provide a drug support system, drug support method, and drug support program that can deliver drugs even in foreign countries, taking into account factors such as drug regulations in the delivery destination.

One embodiment of the present invention includes a receiving unit that receives information written on a prescription from a patient terminal, an information generating unit that generates dispensing data indicating a drug based on the information written on the prescription, an auditing unit that audits the dispensing data, and an instruction unit that issues an instruction to deliver a prescription drug consisting of the drug to the patient.

In the above-mentioned drug support system, a status acquisition unit is provided which acquires identifiers of drugs that are regulated at the delivery destination to which the prescribed drug is delivered as regulated data, and an information generation unit generates dispensing data by linking the drugs listed on the prescription with the drug identifiers, and an audit unit determines that the dispensing data is valid if none of the drug identifiers indicated in the dispensing data are included in the drug identifiers contained in the regulated data, and if the data is determined to be valid, the instruction unit issues delivery instructions.
If the information contained in the patient's personal information entered from the patient's terminal completely matches the information contained in the personal information listed on the prescription entered from the patient's terminal, the auditing unit may determine that the patient is legitimate as a user, and if it is determined that the patient is legitimate, the instruction unit may issue delivery instructions.
In the above-mentioned medication support system, when the auditing unit determines that the dispensing data is legitimate and that the user is legitimate, the system may be equipped with a calculation unit that generates information including the dispensing data as approved drug display information, and an identification code generation unit that links an identification code for identifying multiple pieces of information to information including the approved drug display information and generates identification information that can be identified on a patient's terminal to display information regarding prescription drugs.

This is a drug support method in which a computer executes a receiving step in which it receives information written on a prescription from a patient terminal, an information generating step in which it generates dispensing data indicating a drug based on the information written on the prescription, an auditing step in which it audits the dispensing data, and an instruction step in which it issues an instruction to deliver the prescription drug consisting of the drug to the patient.

This is a drug support program that enables a computer to perform the following functions: a receiving function that receives information written on a prescription from a patient's terminal; an information generating function that generates dispensing data indicating medication based on the information written on the prescription; an auditing function that audits the delivery destination of the dispensing data; and an instruction function that issues instructions to deliver prescription medication consisting of medication to the patient.

According to one embodiment of the present application, the drug support system of the present invention audits whether the prescribed drug can be delivered to the delivery destination. Therefore, the present invention makes it possible to provide the patient with a prescription drug that is suitable for the delivery destination.

1 is a schematic diagram showing the configuration of a medication support system. FIG. 2 is a block diagram showing an example of the configuration of an intermediate terminal. 11 is a data table showing data extracted from a personal information acquisition unit. 11 is a data table showing identification information. 11 is a data table showing data extracted from a prescription information identification unit. 13 is a flowchart showing an example of a process for generating drug display information. 13 is a flowchart illustrating an example of a process for generating identification information.

Below, an embodiment of the drug support system 10 according to the present invention will be explained using the drawings. Note that the present invention is not limited to the embodiment. Also, some components that are not important for the explanation will be omitted in each drawing.

＜Overview＞
1 is a schematic diagram showing the configuration of a medication support system 10 according to an embodiment of the present invention. In the medication support system 10 according to the present embodiment, an intermediate terminal 100, a patient terminal 200, and a pharmacist terminal 300 are communicably connected via the Internet NW.

The intermediate terminal 100 can receive various information (including, for example, information that can identify the patient, or drug information written on a prescription, etc.) from the patient-side terminal 200, and can transmit it to the pharmacist-side terminal 300. The intermediate terminal 100 can also audit information related to the patient's personal information transmitted from the patient-side terminal 200, and can audit various information (including, for example, drug information, etc.) transmitted from the pharmacist-side terminal 300.

The audit in the present invention means judging whether or not there is legitimacy by collating information. Here, if there is legitimacy, it may be indicated that the subject of the audit is not problematic. The audit in the present invention may be at least any of (i) auditing the contents of the prescription, (ii) auditing whether or not the owner of the prescription who applies for the drug is the patient himself/herself, (iii) auditing whether or not the drug prescribed based on the prescription is written in the delivery destination, (iv) auditing whether or not the drug prescribed based on the prescription is correct, and (v) auditing whether or not the dispensing action by the pharmacist is correct. If it is determined that at least one of (i) to (v) above is not valid, the prescription drug may not be delivered to the patient. Here, the criteria for judging whether or not the drug is valid, that is, whether or not the drug is regulated, include various regulations that may regulate drugs, such as laws, orders, ministerial orders, and ordinances in each country (hereinafter referred to as drug regulation ordinances, etc.), and may include, for example, laws regarding the import and export of drugs. The drug support system 10 can be audited based on the drug control ordinances of the country of the patient to which the drug is delivered. As an example, if the drug contained in the prescription is not regulated under the drug control ordinances, the prescription may be delivered to the patient. Conversely, if the drug contained in the prescription is regulated under the drug control ordinances, the prescription may not be delivered to the patient.

The intermediate terminal 100 can generate a patient-specific account based on information that can identify the patient (for example, but not limited to, an insurer number, date of birth, gender, email address, and telephone number) and grant the patient the right to use the medication support system 10. As an example, the patient may input his/her personal information into the patient-side terminal 200, and the patient-side terminal 200 may transmit the personal information input by the patient to the intermediate terminal 100. The intermediate terminal 100 can generate a patient-specific account based on the patient's personal information and then transmit the patient-specific account to the patient-side terminal 200.

The intermediate terminal 100 may also compare the personal information of the account holder with various information written on the prescription to determine whether the account holder and the prescription holder are the same person, and may audit for patient impersonation, and may also audit the pharmacist's dispensing actions (for example, whether the pharmacist's dispensing actions are fraudulent).

The patient-side terminal 200 can associate information written on the prescription entered by the patient (for example, but not limited to, the insurer number, date of birth, sex, telephone number, and information related to medication) with an account dedicated to the patient and transmit it to the intermediate terminal 100. In addition, there are no limitations on the means of inputting information, and the patient may manually input the various information written on the prescription, or may input the information by taking a picture of the prescription and uploading the picture to the patient-side terminal 200.

The prescription according to the present invention may be obtained by the patient from a doctor at a hospital, or may be obtained from a doctor online. In addition, when a patient consults a doctor online, the doctor may send an electronic file of the prescription (e.g., a photo of the prescription or a copy of the prescription) to the patient's email address, or may send the original prescription to the patient's address.

The pharmacist's terminal 300 can accept various information input from the pharmacist. The pharmacist's terminal 300 can acquire information from the intermediate terminal 100, for example, acquiring pass data including patient information and drug information. The pharmacist can check the drug information included in the pass data on the pharmacist's terminal 300 and perform dispensing.

<Configuration>
<Intermediate terminal 100>
Next, an intermediate terminal 100 according to an embodiment of the present invention will be described with reference to Fig. 2. The intermediate terminal 100 may include a receiving unit 110, a calculating unit 120, an information processing unit 130, an information generating unit 140, a storage unit 150, a transmitting unit 160, and an instruction unit 170. The intermediate terminal 100 is typically a computer system, and functions are realized by a CPU (Central Processing Unit), a GPU (Central Processing Unit), etc. Note that Fig. 2 is an example, and the configuration of the intermediate terminal 100 is not limited to that shown in the figure.

The receiving unit 110 can receive various information from the patient terminal 200 and the pharmacist terminal 300. The receiving unit 110 can receive, for example, the patient's personal information and information written on a prescription from the patient terminal 200. In addition, the various information received by the receiving unit 110 may be stored in the storage unit 150 as unprocessed information.

The calculation unit 120 can calculate various costs related to the prescription of medicine. The calculation unit 120 may also add up some or all of the various costs to calculate a total amount for some or all of them. Here, the various costs may include the cost of the medicine listed on the patient's prescription, the cost required for delivery of the prescribed medicine (hereinafter referred to as shipping fee), the dispensing cost due to the dispensing action of the pharmacist, and the fee for using the medicine support system 10. The calculation unit 120 may also be communicably connected to a receipt computer system (hereinafter referred to as a receipt computer) and request the receipt computer to calculate various costs (for example, medical fees, etc.). Here, the receipt computer system is a computer system that creates a "receipt (medical fee statement)" to claim medical fees for the payment period of a medical facility, a health insurance association, etc.

The information processing unit 130 may include a status acquisition unit 131, an audit unit 132, a personal information acquisition unit 133, and a prescription information identification unit 134. The information processing unit 130 may have a function of determining whether the prescription holder is the patient himself/herself, whether the drug contained in the prescription is regulated by overseas drug control regulations, and whether the dispensing action of the pharmacist complies with a certain prescription.

The status acquisition unit 131 can acquire various information. Here, the acquired various information may include the drug regulatory ordinance of the delivery destination of the prescription drug, and environmental information of the delivery destination of the prescription drug (for example, information that may affect the storage of the prescription drug, such as temperature, air pressure, humidity, and light irradiation). In addition, the status acquisition unit 131 may identify drugs that are regulated based on the drug regulatory ordinance of the delivery destination of the prescription drug, and link the identifier of the drug as regulatory data. The identifier used as the drug identifier is not limited, and the status acquisition unit 131 can assign a unique identifier to each drug based on information that can identify the drug, such as a medical drug search number. As an example of acquiring the drug regulatory ordinance of the delivery destination, when a patient in country A sends prescription information to a pharmacist in country B, the status acquisition unit 131 may automatically acquire the drug regulatory ordinance of country A, which is the country corresponding to the IP address, when the receiving unit 110 receives the sending IP address (Internet Protocol Address) of the patient. Furthermore, the status acquisition unit 131 may acquire drug regulatory ordinances, etc. of each country in advance and store them in the storage unit 150. The status acquisition unit 131 may identify the IP address of the patient and directly acquire regulatory data based on the patient's sending IP address from the storage unit 150. Furthermore, in addition to acquiring drug regulatory ordinances, etc., the status acquisition unit 131 may also acquire, for drugs that are regulated based on the drug regulatory ordinances, etc., by linking the identifiers of the drugs as regulatory data.

The audit unit 132 can compare the dispensing data indicating the medication generated by the information generating unit 140 based on the information written on the prescription received by the receiving unit 110 with the regulated data and audit it. Here, the dispensing data is generated by linking the medication written on the prescription with an identifier. If at least one of the identifiers of the medication indicated in the dispensing data is included in the identifier of the medication included in the regulated data, it may be determined that the prescribed medication cannot be delivered to the patient.

The auditing unit 132 may audit the prescription drug itself dispensed by the pharmacist. As an audit of the prescription drug, for example, the auditing unit 132 may audit the dispensing action of the pharmacist. In this case, the auditing unit 132 has a function of photographing the dispensing action of the pharmacist, and photographs and audits the actions of the pharmacist while dispensing, such as checking the drug, weighing, mixing, and checking the drug bag or drug tag. The photographed video and prescription may be stored in the storage unit 150 as audit data and audited by the auditing unit 132, or may be transmitted as audit data to an external terminal capable of auditing the dispensing action of the pharmacist and audited by the external terminal. The audit of the dispensing action of the pharmacist may be an audit of whether the dispensing action of the pharmacist complies with the local Pharmacist Act. If at least one of the above-mentioned dispensing actions violates the Pharmacist Act, the auditing unit 132 may determine that the dispensed prescription drug is not legitimate.

The personal information acquisition unit 133 can extract and acquire the patient's personal information from the unprocessed information stored in the storage unit 150. As an example, the personal information acquisition unit 133 may acquire the patient's personal information (which may include, but is not limited to, the patient's personal phone number, email address, insurer number, address, etc.) entered when creating a patient account, and the information generation unit 140 may generate a patient-specific account based on the patient's personal information. The personal information acquisition unit 133 may acquire information that can identify the account owner (which may include, but is not limited to, the patient's personal phone number, email address, insurer number, etc.) as unchangeable information, and may acquire information that cannot identify the account owner (which may include, but is not limited to, the patient's gender, location, age, etc.) as changeable information. This allows the information related to the account owner to be freely changed even if the patient's location changes due to moving, etc.

Figure 3 is an example of a data table showing information related to a patient-specific account generated based on personal information extracted by the personal information acquisition unit 133. The personal information acquisition unit 133 can acquire information that identifies the individual account owner from the personal information received by the receiving unit 110. The data table DT100 may include information such as "patient name", "insurer number", "date of birth", "gender", "email address" and "telephone number", but is not limited to these.

The prescription information identification unit 134 can extract and acquire information described on the prescription from the unprocessed information stored in the storage unit 150. The prescription information identification unit 134 may further identify various information described on the prescription and acquire it by classifying it into prescription owner information and drug information. For example, the prescription information identification unit 134 may identify various information described on the prescription and acquire it by classifying it into prescription owner information indicating the personal information of the prescription owner and drug information including the drug name and the drug dosage. As an example, the prescription information identification unit 134 may recognize the patient's name and a predetermined number of digits of the insurer number described on the prescription using morphological analysis and acquire it as prescription owner information. Based on the received information, the prescription information identification unit 134 may acquire information that can identify the prescription owner (for example, the patient's personal phone number, email address, insurer number, etc. described on the prescription, but are not limited to these) as the prescription owner's personal information, and may acquire information that cannot identify the prescription owner (for example, the patient's gender, age, etc., but are not limited to these) as not being the prescription owner's personal information. Additionally, the drug information may be stored directly in the storage unit 150.

The prescription information identification unit 134 may also have a function for recognizing the image of the prescription. As an example, when uploading an image of a prescription, the prescription information identification unit 134 can classify and identify the information written on the prescription from the image of the prescription into prescription owner information indicating the identity of the prescription owner and drug information including the drug name and dosage. For example, the prescription information identification unit 134 may identify the insurer number in the image of the prescription and acquire it as the identity information of the prescription owner. After acquiring the image, other information that cannot identify the identity of the prescription owner may be deleted without being stored in the storage unit 150. Note that, if the prescription is in a foreign language, the information processing unit 130 may further include a translation unit, and after acquisition by the prescription information identification unit 134, the foreign language portion included in the prescription photo may be translated into a language that the pharmacist can understand.

Figure 4 shows an example of a data table showing information obtained from a prescription extracted by the prescription information identification unit 134. Data table DT200 may include information such as "patient name," "telephone number," "date of birth," "country where prescription was obtained," and "drug information" written on the prescription, but is not limited to these.

After the personal information acquisition unit 133 and the prescription information identification unit 134 acquire the patient information (personal information of the account owner and personal information of the prescription owner), the audit unit 132 can audit the patient's identity. As an example, when the account owner A inputs various information (which may include, for example, the name of the patient B (prescription owner) in the drug support system 10, which may include the name of the patient B, the insurer number, the drug name, the drug dosage, etc.) described in the prescription of the patient B, the drug support system 10 may determine whether the account owner and the prescription owner are the same by comparing the personal information (which may include, for example, the insurer number and the insurer name) of the account owner A with the personal information (which may include, for example, the insurer number and the insurer name) described in the input prescription of the patient B. The drug support system 10 may also be connected to a database of a medical institution in the country where the patient is located. In this case, after obtaining connection permission from the medical institution in the country where the medication support system 10 is located, it searches the database of the medical institution in the country where patient B is located using personal information of account holder A (which may include, for example, the insurer number and insurer name) as a keyword, and determines whether or not there is a prescription record for account holder A. If there is a prescription record for account holder A, it compares the various information contained in that record (which may include, for example, the drug name and drug dosage) with the various information listed on patient B's prescription. If the various information does not match, it may be determined that account holder A and patient B listed on the prescription are not the same person.

If the medicine on the prescription complies with the Pharmaceutical Control Ordinance and the prescription owner and the account owner are the same person, the audit unit 132 may certify the dispensing data as acceptable data. In addition, the medicine support system 10 is connected to a receipt computer that supports the dispensing system prescription IF sharing specification (NSIPS (registered trademark): New Standard Interface of Pharmacy-system Specifications), and may send the acceptable data to a dispensing system such as a dispensing inspection system or an automatic tablet/powder packaging machine, and generate a sharing specification for dispensing.

The calculation unit 120 may link the calculated total amount with the pass data to generate passed drug display information. The passed drug display information may not include the total amount.

The information generating unit 140 may include a medication instruction information generating unit 141 and an identification code generating unit 142. The information generating unit 140 may generate an identification code for identifying medication instruction information and various information stored in the storage unit 150. The information generating unit 140 may generate dispensing data by linking a drug listed on a prescription with an identifier of the drug.

The medication instruction information generating unit 141 can generate information related to the prescription of a prescription drug. As an example, the memory unit 150 may store information to be communicated to the patient when prescribing the drug in advance in association with the drug contained in the prescription drug, and the medication instruction information generating unit 141 may generate information to be communicated to the patient when prescribing the drug by identifying the drug to be prescribed. For example, the medication instruction information generating unit 141 may generate information such as "Take this prescription drug at the same time every day before or after a meal," or "Avoid alcohol intake while taking this prescription drug." In association with the dispensing act, the pharmacist may input the type, dosage, efficacy of the dispensed prescription drug, how to take it, dosage instructions, and precautions when prescribing, etc., into the pharmacist-side terminal 300, and the medication instruction information generating unit 141 may generate medication instruction information based on the information input by the pharmacist. In addition, various information generated by the medication instruction information generating unit 141 may be linked to approved drug display information and used as patient-provided information. The patient-provided information may not include the various information generated by the medication instruction information generation unit 141.

The patient-provided information may be displayed in multiple languages. In this case, the information processing unit 130 further includes a translation unit that can translate the patient-provided information into multiple languages. For example, if the language of the patient-provided information is English and the pharmacist is Japanese, the translation unit can translate the English version of the patient-provided information into Japanese. Here, the obtained Japanese version of the patient-provided information and the English version of the patient-provided information may be stored as a set. The translation (i.e., obtained by translating the patient-provided information into another country's language) may be freely adjusted depending on the patient's nationality and the delivery destination of the prescribed drug.

The identification code generation unit 142 can generate a code for identifying the patient-provided information and generate identification information by linking it to the patient-provided information. The identification code may be a barcode (one-dimensional code) or a QR code (registered trademark) (two-dimensional code), but is not limited to these, and may be a character code. After generating the identification code, the identification code generation unit 142 may link the identification code to the patient-provided information. The patient can check the patient-provided information by reading the identification code.

The identification information can include patient information, drug information, dispensing data, approval data, total amount, approved drug display information, dosage instructions information, patient-provided information, and an identification code, and patients can use the identification code to obtain various information about their prescribed drugs.

Figure 5 shows an example of identification information generated by the identification code generation unit 142. In the data table DT300 shown in Figure 5, the identification information includes, but is not limited to, an identification code, a patient name, whether delivery is possible, medication instruction information, information about the prescription, shipping fee, and a total amount. The identification code generated by the identification code generation unit 142 is transmitted to the patient terminal 200 by the transmission unit 160 and displayed on the patient terminal 200, allowing the patient to read the identification code on the patient terminal 200. As an example, when patient 1 reads code 1, which is an identification code, "Patient name_1, mail possible, medication instruction (1) and medication instruction (2), drug name 1, drug dosage 1, drug cost 1, shipping fee 1, and total amount 1" may be displayed on the patient terminal 200.

The storage unit 150 is a recording medium that stores various programs and various data required by the intermediate terminal 100. The storage unit 150 is realized, for example, by a hard disc drive (HDD), a solid state drive (SSD), a flash memory, etc., but is not limited to these. The storage unit 150 may include, for example, a flash memory, a random access memory (RAM), a read only memory (ROM), etc.

The transmission unit 160 can transmit various information to the patient terminal 200 and the pharmacist terminal 300. The transmission unit 160 may transmit, for example, a digital delivery note including the identification information and the prescription to the patient terminal 200. This allows the patient to check the identification information on the patient terminal 200 while referring to the prescription.

The instruction unit 170 can issue delivery instructions to the pharmacist's terminal 300.

<Examples of operation and display screen>
Next, an embodiment of the medicine support system 10 according to the present invention will be described with reference to a flowchart and a data table. Fig. 6 is an example of a flowchart showing a part of the operation of the intermediate terminal 100, and the present invention is not limited thereto.

First, various information is received from the patient-side terminal 200 (S101). The auditing unit 132 audits whether the personal information entered by the patient from the patient-side terminal 200 matches the personal information listed on the prescription entered by the patient (S102). If at least one of the information included in the personal information entered by the patient and the information included in the personal information entered by the patient does not match, the auditing unit 132 determines that the patient who entered the information from the patient-side terminal 200 or the individual listed on the prescription is not a legitimate user and is not legitimate (NO in S102), and ends the operation of the intermediate terminal 100. If the information included in the personal information entered by the patient and the information included in the personal information entered by the patient completely match, the auditing unit 132 determines that the patient who entered the information from the patient-side terminal 200 and the individual listed on the prescription are the same and are legitimate users (YES in S102), and proceeds to the next step.

The information generating unit 140 generates dispensing data indicating the drug based on the information written on the prescription input from the patient side terminal 200 (S103). The status acquiring unit 131 acquires the drug control ordinance of the delivery destination of the prescription drug, recognizes and identifies the drug that is regulated based on the drug control ordinance of the delivery destination of the prescription drug, and links the identifier of the drug to the drug as regulated data (S104). The auditing unit 132 compares the dispensing data with the regulated data and audits it (S105). If at least one of the identifiers of the drug indicated in the dispensing data is included in the identifier of the drug included in the regulated data, the auditing unit 132 determines that the dispensing data is invalid (NO in S105) and ends the operation of the intermediate terminal 100.

If none of the drug identifiers indicated in the dispensing data are included in the drug identifiers included in the regulated data, the auditing unit 132 determines that the dispensing data is valid, recognizes the dispensing data as passed data (YES in S105), and proceeds to the next step. The auditing unit 132 audits the pharmacist's dispensing action (S106). If the auditing unit 132 determines that the pharmacist's dispensing action is invalid (NO in S106), it terminates the operation of the intermediate terminal 100. If the auditing unit 132 determines that the pharmacist's dispensing action is valid (YES in S106), it proceeds to the next step.

Then, the calculation unit 120 calculates the total amount (S107). The calculation unit 120 links the total amount with the pass data and generates pass drug display information (S108).

Figure 7 is a flowchart showing part of the operation of the intermediate terminal 100 to generate identification information. Note that Figure 7 is an example, and the present invention is not limited to this.

First, the medication instruction information generation unit 141 generates medication instruction information regarding the dispensed prescription drug (S201).

Next, the medication instruction information generating unit 141 links the medication instruction information generated by the medication instruction information generating unit 141 with the approved drug display information (S202) and generates it as patient-provided information (S203).

Then, the identification code generation unit 142 generates an identification code for identifying the patient-provided information (S204). The identification code generation unit 142 links the generated identification code to the patient-provided information (S205) and generates it as identification information (S206).

Here, the medication instruction information may include a video of the pharmacist providing medication instructions, etc., and this video may be transmitted from the pharmacist's terminal 300.

Furthermore, if the audit unit 132 determines that the request is not valid, the audit unit 132 may generate information indicating that the process has been interrupted, such as "Delivery not possible" or "Prescription not possible," and send this information to the patient-side terminal 200 before terminating the operation of the intermediate terminal 100. The audit unit 132 may generate information such as "Delivery not possible" or "Prescription not possible" as claim refusal information by linking it to the identification code, the patient's personal information, and information regarding the prescription. This allows the patient to understand the situation in which they are unable to obtain the prescribed drug.

If the information is determined to be invalid, the patient may be able to transmit a request for reconfirmation to the intermediate terminal 100. In this case, the intermediate terminal 100 may transmit the patient's request to the pharmacist's terminal 300. The pharmacist may be able to reconfirm the information included in the identification information at the pharmacist's terminal 300 in response to the patient's request, and may be able to repeat the process in the event of an incorrect response by the pharmacist or insufficient explanation, or may be able to add a more detailed explanation to the identification information, but is not limited to this.

When the instruction unit 170 receives a notice of remittance for the prescribed drug from the patient terminal 200, it sends a command to deliver the prescribed drug to the pharmacist terminal 300. At this time, information necessary for delivery may also be sent to the pharmacist terminal 300. The pharmacist may package the prescribed drug in accordance with the command and then deliver it to the address listed on the patient's account.

In addition, when issuing a command to deliver the prescription drug, an information list regarding payment information (e.g., a delivery note or receipt) and data for an information label indicating delivery destination information may be sent to the pharmacist's terminal 300, along with a command to print these data. In this case, the pharmacist may deliver the prescription drug, information list, and information label to the patient's address in accordance with the command.

<Additional Information>
Although one embodiment of the present invention has been described, it goes without saying that the present invention is not limited to the above embodiment. Various modifications and functions that can be implemented will be described below.

(1) In the above embodiment, after creating a patient-specific account, the medication support system 10 may send a notification of completion of account creation to the patient-side terminal 200. As an example, after a patient creates an account, the medication support system 10 sends a notification of completion of account creation to the patient's telephone number or email address. At this time, the notification of completion of account creation does not need to include personal information of the patient.

(2) In the above embodiment, the medication support system 10 may store information about a patient's dedicated account in an external server. As an example, the medication support system 10 may be connected to a NAS server (Network Attachment Storage). After the patient inputs his/her personal information, etc., into the medication support system 10, the medication support system 10 transmits the personal information to the NAS server. After that, the NAS server may automatically deliver the URL of the storage destination where various information is stored to the patient by email or text message in conjunction with the creation of the patient information folder. If the patient wishes to reconfirm his/her personal information, he/she may click on the URL of the storage destination and have his/her personal information automatically displayed. In addition, the owner of the medication support system 10 may manage information about the patient's dedicated account in the NAS server.

(3) In the above embodiment, the drug support system 10 may store the patient's medication history. As an example, after various processes of the intermediate terminal 100 are executed, the patient's medication history or medication instruction information may be stored in the storage unit 150 or the NAS server. If the patient suffers from the same disease, the patient may search for an existing medication history and take the prescribed medicine while referring to the medication history and medication instruction information. As another example, the patient's medication history before using the drug support system 10 may be stored in the storage unit 150 or the NAS server. After obtaining connection permission from a medical institution in the patient's country, the drug support system 10 connects to the database of the medical institution in the patient's country, and the drug support system 10 may extract the patient's medication history from the medical institution's database based on the patient's personal information, particularly the patient's name and insurer number, and store it in the storage unit 150 or the NAS server. In addition, the patient may manually input his or her medication history to the drug support system 10 and store it in the storage unit 150 or the NAS server. In this case, the patient may freely check the medication history linked to the patient's account on the patient terminal 200.

(4) In the above embodiment, the drug support system 10 may be connected to the generating AI program and may automatically obtain drug administration instructions. As an example, if the pharmacist's drug administration instruction information is insufficient, the patient may obtain drug administration instruction information for the prescribed drug in the form of a question and answer session by conversing with the generating AI program connected to the drug support system 10.

(5) In the above embodiment, the medication support system 10 may generate health advice for the patient based on prescription drug use instruction information when connected to the generation AI program. As an example, in the case of lower back pain, the medication support system 10 may generate advice such as "Avoid unnatural postures!" or "Manage your stress properly" and send it to the patient terminal 200.

(6) In the above embodiment, the medication support system 10 may be connected to an external terminal that generates an identification code. As an example, the information generation unit 140 may further include an identification code storage unit. The identification code generation unit 142 may obtain an identification code such as a QR code from the external terminal and store the identification code in the identification code storage unit.

(7) In the above embodiment, the medication support system 10 may provide an online medical consultation system. As an example, the patient terminal 200 and the pharmacist terminal 300 may be equipped with a camera function, and the pharmacist may provide the patient with an explanation of dispensing and instructions on how to take prescribed medication through online diagnosis.

(8) In the above embodiment, the medication support system 10 may further include a medical questionnaire input unit. As an example, the patient may input the information on the medical questionnaire acquired from the hospital or pharmacy to the medical questionnaire input unit on the patient-side terminal 200. In addition, the method of inputting the medical questionnaire is not limited, and the patient may manually input the information on the medical questionnaire to the medical questionnaire input unit, or the medical questionnaire input unit may further include a text recognition display function, and after the patient takes a photo of the medical questionnaire, the patient may upload the photo to the medical questionnaire input unit, so that the medical questionnaire input unit can read the information on the medical questionnaire photo. The information acquired from the medical questionnaire input unit is stored in the memory unit 150, so that the patient may reconfirm the photo of the medical questionnaire linked to the patient-specific account or the information on the medical questionnaire on the patient-side terminal 200.

REFERENCE SIGNS LIST 10 Medication support system 100 Intermediate terminal 200 Patient terminal 300 Pharmacist terminal 110 Receiving unit 120 Calculation unit 130 Information processing unit 131 Status acquisition unit 132 Audit unit 133 Personal information acquisition unit 134 Prescription information identification unit 140 Information generation unit 141 Medication instruction information generation unit 142 Identification code generation unit 150 Storage unit 160 Transmission unit 170 Instruction unit

Claims (5)

A receiving unit that receives information written on a prescription from a patient terminal;
an information generating unit that generates dispensing data indicating a drug based on information written on the prescription;
An auditing unit that audits the prescription data;
An instruction unit that issues an instruction to deliver a prescription drug consisting of the drug to a patient ;
a status acquisition unit that acquires, as regulatory data, an identifier of a drug that is regulated at a delivery destination to which the prescription drug is delivered;
The information generating unit generates dispensing data by linking the medicine described in the prescription with a medicine identifier,
The audit unit determines that the dispensing data is valid when none of the identifiers of the medicines indicated in the dispensing data is included in the identifiers of the medicines included in the regulatory data;
If the validity is determined, the instruction unit issues an instruction to deliver the document.
Medication support system. The audit unit determines that the patient is a legitimate user when the information included in the patient's personal information entered from the patient-side terminal completely matches the information included in the personal information on the prescription entered from the patient-side terminal,
When it is determined that the validity is present, the instruction unit issues an instruction for the delivery.
The medication support system according to claim 1. The drug support system includes:
a calculation unit which generates information including the dispensing data as approved drug display information when the audit unit determines that the patient is a legitimate user if the information included in the patient's personal information input from the patient-side terminal and the information included in the personal information on the prescription input from the patient-side terminal completely match, and when the audit unit determines that the patient is a legitimate user, the calculation unit generates information including the dispensing data as approved drug display information when the audit unit determines that the patient is a legitimate user when the audit unit determines that the dispensing data is legitimate.
The drug support system of claim 1, further comprising an identification code generation unit that links an identification code for identifying multiple pieces of information to information including the approved drug display information, and generates identification information that can be identified by the patient terminal to display information regarding the prescribed drug. The computer
A receiving step of receiving information written on a prescription from a patient terminal;
an information generating step of generating dispensing data indicating a drug based on information written on the prescription;
an auditing step of auditing the dispensing data;
issuing instructions to deliver a prescription of the drug to a patient ;
A situation acquisition step of acquiring, as regulatory data, an identifier of a drug regulated at a delivery destination to which the prescription drug is delivered;
The information generating step generates dispensing data by linking the medicine described in the prescription with a medicine identifier;
The audit step determines that the dispensing data is valid when none of the identifiers of the medicines indicated in the dispensing data are included in the identifiers of the medicines included in the regulatory data;
If the validity is determined, the instruction step issues an instruction to deliver the document.
Drug support methods. On the computer,
A receiving function for receiving information written on a prescription from a patient's terminal;
An information generating function for generating prescription data indicating a drug based on information written on the prescription;
an audit function for auditing the prescription data;
an instruction function for issuing an instruction to deliver a prescription of the drug to a patient ;
A status acquisition function for acquiring, as regulatory data, an identifier of a drug that is regulated at a delivery destination to which the prescription drug is delivered.
The information generating function generates dispensing data by linking the medicine described in the prescription with a medicine identifier;
The audit function determines that the dispensing data is valid when none of the identifiers of the medicines indicated in the dispensing data are included in the identifiers of the medicines included in the regulatory data;
If the validity is determined, the instruction function issues an instruction to deliver the information.
Medication assistance programs.

Images