Server, information processing system, information processing method, and program

Abstract

To provide an information processing system, an information processing method and a program for enabling a pharmacy or a pharmacist to construct a close relation with a patient, and for supporting the patient.SOLUTION: The server receives an input expressing that the patient agrees to the regular contract with the pharmacist or the pharmacy from the patient terminal, and electronically stores the contents of the agreement in a storage device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a server, an information processing system, an information processing method and a program, and more particularly to a technology that enables pharmacies and pharmacists to build close relationships with patients and support them. [Background technology]

[0002] Various attempts have been proposed to improve the quality and convenience of services such as medical treatment and medication advice.

[0003] Patent document 1 describes a system in which a medical support device that supports patients' medical treatment creates and transmits a medical treatment policy proposal to a medical institution that provides online medical treatment to the patient, and provides the necessary medication. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6764202 Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, an increasing number of patients are using their own medication notebooks to manage their own medication history. Pharmacies and pharmacists are well-positioned to support patients by ensuring they receive appropriate advice and medical treatment based on their medication history. There is a need for a technological foundation to realize such patient support.

[0006] The present invention is intended to solve these problems, and aims to provide a server, information processing system, information processing method, and program that enable pharmacies and pharmacists to build close relationships with patients and provide support to them. [Means for solving the problem]

[0007] According to one embodiment, the server accepts input from the patient terminal indicating that the patient has agreed to a patient care agreement with the pharmacist or pharmacy, and electronically stores the content of the agreement in a storage device. According to one embodiment, the server detects when activity related to the patient's health condition occurs and makes the activity viewable on a pharmacy terminal used by the pharmacist or pharmacy that is a party to the patient care agreement. According to one embodiment, the server provides an incentive to the pharmacist or pharmacy when the activity is viewable by the pharmacy terminal used by the pharmacist or pharmacy that is a party to the primary care agreement. According to one embodiment, the server prints out a document containing the consent. According to one embodiment, the server prompts the patient to enter information about the activity by sending a push notification to the patient terminal. According to one embodiment, the activity includes medication history information, and the server uses the medication history information to estimate the next visit date and notify the patient terminal of a reminder to visit the pharmacy. According to one embodiment, the server accepts input from the patient terminal indicating that the patient has agreed to the primary care contract with the new pharmacist or pharmacy, and electronically stores the content of the agreement in the storage device. According to one embodiment, the server reads from the storage device the contents of the consents relating to the multiple family care contracts that the patient has previously concluded, sorts them by the contract establishment date, and displays them on the screen. According to one embodiment, the information processing system includes a patient terminal, a pharmacy terminal, and a server, and the patient terminal sends an input to the server indicating that the patient has agreed to a primary care contract with a pharmacist or pharmacy. The server electronically stores the content of the agreement in a storage device, and when it detects that an activity related to the patient's health condition has occurred, makes the activity viewable on a pharmacy terminal used by the pharmacist or pharmacy that is a party to the primary care contract. According to one embodiment, the information processing method includes a step in which a server receives input from a patient terminal indicating that the patient has agreed to a primary care contract with a pharmacist or pharmacy, and a step in which the content of the agreement is electronically stored in a storage device. According to one embodiment, the program causes a computer to carry out the method according to claim 7. [Effects of the Invention]

[0008] The present invention can provide a server, an information processing system, an information processing method, and a program that enable pharmacies and pharmacists to build close relationships with patients and provide support to patients. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of a hardware configuration of an information processing system 1. FIG. [Figure 2] FIG. 2 is a diagram illustrating an example of a functional configuration of the information processing system 1. [Figure 3] FIG. 2 is a diagram illustrating an example of a functional configuration of the information processing system 1. [Figure 4] 10 is a flowchart of a process for supporting the conclusion of a medical treatment contract executed by the information processing system 1. [Figure 5] 10 is a flowchart of an activity recording and reference process executed by the information processing system 1. [Figure 6] 10 is a flowchart of a patient health management support process executed by the information processing system 1. [Figure 7] 10 is a flowchart of a patient visit reminder process executed by the information processing system 1. [Figure 8] 10 is a flowchart of a process for updating a primary care contract and managing a contract history, which is executed by the information processing system 1. DETAILED DESCRIPTION OF THE INVENTION

[0010] <First Embodiment> The information processing system 1 according to the first embodiment manages a personal pharmacist or a personal pharmacy in association with a patient.

[0011] 1 is a block diagram showing the system configuration of an information processing system 1. The information processing system 1 includes a server 10, a patient terminal 20, and a pharmacy terminal 30.

[0012] The server 10 is an information processing device that includes a processing device, a storage device, a communication device, etc., and realizes predetermined functions by the processing device executing a program stored in the storage device. The program may be stored and distributed on a computer-readable storage medium, or may be downloaded from a network via a communication device. Note that the server 10 does not have to be a single information processing device, but may be realized by multiple information processing devices working together, or may be a virtualized information processing environment such as cloud computing.

[0013] The server 10 is connected to the patient terminal 20 and the pharmacy terminal 30 via a network such as the Internet so that they can communicate with each other.

[0014] The patient terminal 20 is an information processing device used by the patient. The patient terminal 20 is typically a smartphone, tablet terminal, or the like. In addition to a processing device, a storage device, and a communication device, the patient terminal 20 includes a camera, an input device, a display device, and the like. Typically, a medication notebook app or the like installed on the patient's smartphone or the like realizes various processing functions as described below.

[0015] Pharmacy terminal 30 is an information processing device used by pharmacists or pharmacy staff, etc. Pharmacy terminal 30 is typically a smartphone, tablet terminal, etc. It includes a processing device, a storage device, a communication device, etc., as well as an input device, a display device, etc.

[0016] Although only one patient terminal 20 and one pharmacy terminal 30 are shown in FIG. 1, a plurality of patient terminals 20 and a plurality of pharmacy terminals 30 can be connected to server 10.

[0017] 2 is a block diagram showing the functional configuration of the server 10. The server 10 includes a patient information management unit 101 and a contract management unit .

[0018] The patient information management unit 101 includes basic information, medication history information, purchase information, and health records of the patient. These information groups are typically linked to a patient ID that can uniquely identify the patient and stored in a storage device. The medication history information, purchase information, and health records are information groups related to the patient's health, and form part of a so-called PHR (Personal Health Record).

[0019] The basic information includes attribute information of the patient and information required when obtaining information about the patient from external storage. For example, the basic information may include the patient's name, age, sex, personal identification number (My Number), etc.

[0020] The medication history information includes history information (hereinafter referred to as medication history) of drugs prescribed or dispensed for a patient (prescription drugs). For example, the medication history information includes the date of prescription or dispensing, and the details of the prescription or dispensing (drug name, amount, etc.). Typically, the pharmacy terminal 30 of the pharmacy that prescribed or dispensed the drug or a terminal device (not shown) of the medical institution transmits the medication information to the server 10, which is then registered in the patient information management unit 101. Alternatively, the server 10 may access a medication history management server (not shown) on the network, acquire medication history information related to a specific patient, and store it in the medication history management unit 11. An example of a medication history management server is My Number Portal in Japan. In this case, the server 10 presents the patient's personal identification number (My Number) to My Number Portal and acquires the corresponding medication history information.

[0021] The purchase information includes purchase history information of items purchased by the patient (including over-the-counter drugs, supplements, health foods, etc.). The purchase information may include the name, quantity, ingredient names, purchase date and time, etc. of the item. When a pharmacy sells an item to a patient, the pharmacy terminal 30 at the pharmacy typically transmits the purchase information to the server 10, which is then registered in the patient information management unit 101. Alternatively, the server 10 may access a product distributor server (not shown) on the network, obtain purchase information related to a specific patient, and store it in the medical history management unit 11. Alternatively, the patient himself / herself may register information related to the purchased item via an interface provided by the patient terminal 20.

[0022] Health records store various information related to a patient's health, such as the patient's medical history, side effect information, allergy information, prescription drug use information, and intake information for over-the-counter drugs, supplements, health foods, etc. The medical history includes, for example, the name of the disease, the name of the medical institution where the treatment was performed, and the date and time of the treatment. Typically, a terminal device at the medical institution where the treatment was performed transmits the health record to the server 10, where it is registered in the patient information management unit 101. For example, if a patient has experienced a side effect after taking drug X or has developed an allergy to substance Y, information such as "drug X" is recorded as side effect information and "substance Y" as allergy information. For example, if a pharmacist obtains side effect information or allergy information by asking about side effects or allergies during or before or after online medication instruction, the pharmacy terminal 30 at the pharmacy typically transmits the health information to the server 10 and registers it in the patient information management unit 101. The intake information includes, for example, the name of the prescription drug taken, the date and time of intake, and whether or not there was any change in physical condition after taking the drug. The intake information includes, for example, the date and time of intake of the over-the-counter drug, supplement, health food, etc., and whether or not there was any change in physical condition after taking the drug. The medication information and intake information are typically input by the patient to the patient terminal 20 via a predetermined input interface, and the patient terminal 20 transmits the information to the server 10 and registers it in the patient information management unit 101 .

[0023] The contract management unit 102 is a processing unit that manages the relationship between pharmacists or pharmacies and patients. In recent years, the importance of a personal pharmacist or personal pharmacy, who provides advice to patients on maintaining their health through medication instructions and the like, has been highlighted. The contract management unit 102 supports the conclusion of a personal care contract between a patient and a pharmacist or pharmacy. It also links and manages patients who have concluded a personal care contract with pharmacists or pharmacies. It also makes it possible for the personal pharmacist or pharmacy to refer to information on any activity related to the patient's health condition (including prescriptions, dispensing, purchases, etc.) that occurs.

[0024] FIG. 4 is a flowchart of the process of supporting the conclusion of a medical treatment contract executed by the information processing system 1.

[0025] (Support for concluding a family doctor contract) Step S101: The contract management unit 102 displays on the display device of the patient terminal 20 a document (a consent form) requesting consent to conclude a family doctor contract with a predetermined pharmacist or pharmacy.

[0026] The predetermined pharmacist or pharmacy here may be, for example, the pharmacist or pharmacy that introduced or provided the medicine notebook app, the pharmacist or pharmacy that dispensed the medicine to the patient, or a pharmacist or pharmacy selected by the patient.

[0027] The consent screen may include, for example, a document (consent form) indicating the contents of the primary care contract and a checkbox or button as a consent field. After reading the document, the patient can be deemed to have consented to the primary care contract by pressing a checkbox or button. Alternatively, the patient's intention to enter into the contract may be expressed through a so-called electronic contract, in which an electromagnetic record is created according to a predetermined procedure to ensure the authenticity of the document and the parties' intention to enter into the contract. In this case, the patient can be deemed to have consented to the primary care contract when the electromagnetic record is created. Alternatively, the consent screen may request the upload (including taking a photo or scanning) of a paper contract already created between the patient and a designated pharmacist or pharmacy (typically, a contract with both parties' seals or signatures). In this case, the patient can be deemed to have consented to the primary care contract when the created contract is uploaded.

[0028] Step S102: If the patient agrees to enter into a family doctor contract, the contract management unit 102 stores in a storage device information indicating the contract contents (hereinafter, contract information), such as the date and time of contract establishment, the patient's name or identifier (hereinafter, patient ID), the name or identifier of the pharmacist or pharmacy (hereinafter, pharmacist ID or pharmacy ID), and the contents of the consent form. In this way, the contract management unit 102 starts managing the patient in association with the specified pharmacist or pharmacy.

[0029] Step S103: The contract management unit 102 allows the patient's personal pharmacist or pharmacy to refer to the PHR that has been accumulated so far.

[0030] For example, if medication history information, purchasing information, medication information, intake information, etc. associated with the ID of a patient who has concluded a family doctor contract have already been recorded in the patient information management unit 101, the contract management unit 102 transmits this information to the pharmacy terminal 30 linked to the pharmacist ID or pharmacy ID (for example, the pharmacy terminal 30 to which a pharmacist or pharmacy staff member has logged in using the pharmacist ID or pharmacy ID). Upon receiving this information, the pharmacy terminal 30 stores it in a storage device while linking it to the patient ID. At this time, the pharmacy terminal 30 may output a notification to the pharmacist or the like indicating that information related to this patient is now available for viewing. The pharmacist or the like can view various pieces of information linked to the patient by specifying the patient ID on the pharmacy terminal 30.

[0031] Alternatively, if medication history information, purchase information, medication information, intake information, etc. associated with the patient ID of a patient who has concluded a family care contract have already been recorded in the patient information management unit 101, the contract management unit 102 grants access rights to this information to the pharmacist ID or pharmacy ID of the patient who has concluded the family care contract. The pharmacist, etc. can log in to the pharmacy terminal 30 using the pharmacist ID or pharmacy ID and refer to the patient information management unit 101 of the server 10 to view various information linked to this patient.

[0032] This will allow pharmacists or pharmacies that have entered into a primary care contract to view and utilize a patient's PHR as if the pharmacist or pharmacy had been creating the patient's PHR up until now.

[0033] For example, the screen of the pharmacy terminal 30 can display a list of basic patient information, medication history information, purchase information, medication information, or intake information, etc. This allows pharmacists and others to give appropriate advice based on a wide range of chronological information about the patient.

[0034] FIG. 5 is a flowchart of the activity recording and reference process executed by the information processing system 1.

[0035] (Activity record and reference) Step S201: The contract management unit 102 detects that a patient has performed an activity related to their health condition (including prescription, dispensing, purchasing, etc.).

[0036] For example, when a patient receives a prescription or dispensing of a drug at any medical institution or pharmacy, medication history information is added to the patient information management unit 101 of the server 10. The contract management unit 102 detects that the medication history information has been added to the patient information management unit 101.

[0037] Alternatively, when a patient uses the medicine notebook app on the patient terminal 20 to purchase items such as over-the-counter medicines, supplements, or health foods from an in-app mall, the purchase information is added to the patient information management unit 101 of the server 10. The same applies to cases where a business providing the medicine notebook app sells items to patients through an e-commerce mall operated outside the app. The business recognizes that the patient has purchased an item from the e-commerce mall and adds the purchase information to the patient information management unit 101 of the server 10. Alternatively, the contract management unit 102 may occasionally send a push notification to the patient terminal 20, such as "Enter information about the supplements you purchased," to prompt the patient to register the information about the purchased item themselves. When the patient selects the push notification, the patient terminal 20 displays an input screen for information about the purchased item. The entered information is added as purchase information to the patient information management unit 101 of the server 10. The contract management unit 102 detects that the purchase information has been added to the patient information management unit 101.

[0038] Alternatively, when a patient uses the medicine notebook app on the patient terminal 20 to register prescription drug administration information or intake information for over-the-counter drugs, supplements, health foods, etc., the administration information or intake information is added to the patient information management unit 101 of the server 10. The contract management unit 102 detects that the administration information or intake information has been added to the patient information management unit 101.

[0039] Step S202: The contract management unit 102 allows the patient's personal pharmacist or pharmacy to refer to information about the patient's activities.

[0040] For example, when the contract management unit 102 detects that medication history information, purchasing information, medication information, intake information, etc. have been added to the patient information management unit 101, it transmits the added information to the pharmacy terminal 30. Upon receiving this information, the pharmacy terminal 30 stores the information in a storage device in association with the patient ID. At this time, the pharmacy terminal 30 may output a notification to a pharmacist or the like indicating that new information related to a specific patient has been acquired. By specifying the patient ID on the pharmacy terminal 30, the pharmacist or the like can view the various pieces of information associated with the patient.

[0041] Alternatively, when the contract management unit 102 detects that medication history information, purchasing information, medication information, intake information, etc. have been added to the patient information management unit 101, it notifies the pharmacy terminal 30 of this and grants the pharmacy terminal 30 access authority to the added information. Pharmacists and the like can view various information linked to patients by referring to the patient information management unit 101 of the server 10 via the pharmacy terminal 30.

[0042] At this time, the screen of the pharmacy terminal 30 can display a list of, for example, the patient's basic information, medication history information, purchase information, medication information, or intake information, etc. This allows pharmacists and others to give appropriate advice based on a wide range of chronological information about the patient.

[0043] In this way, the information processing system 1 can help a patient and a pharmacist or a pharmacy to easily conclude a family care contract, thereby helping the two parties to build a close relationship.

[0044] In addition, the information processing system 1 allows the patient's pharmacist or pharmacy to refer to information at any time when activity related to the patient's health condition occurs, thereby helping the pharmacist or pharmacy to provide close support to the patient to maintain their health.

[0045] <Variation 1> Pharmacy terminal 30 can provide a function to print documents showing the contents of the primary care contract. For example, the pharmacy terminal 30 outputs to a printer, multifunction device, fax machine, etc., documents including the text displayed on the consent request screen, the consent date and time, the text included in the electromagnetic record, the consent date and time, and an image of the uploaded contract and the upload date and time.

[0046] This allows a patient's pharmacist or pharmacy to easily prepare a document confirming the existence of a patient care contract, for example, if requested by authorities.

[0047] <Variation 2> When the information about the patient's activity becomes available to the patient's pharmacist or pharmacy in step S202, the server 10 can add a management fee to the patient. For example, when purchasing information about supplements is provided to the patient's pharmacist or pharmacy, the server 10 charges the patient a supplement management fee. Specifically, the server 10 collects a predetermined management fee from the patient using a payment method (e.g., a credit card) that the patient has registered in advance with the server 10, and transfers part or all of the fee to the payment method (e.g., a bank account) of the patient's pharmacist or pharmacy.

[0048] Alternatively, if the patient's personal pharmacist or pharmacy is able to refer to information about the patient's activity in step S202, the server 10 can return a portion of the sales of the product to the pharmacist. For example, if purchasing information about supplements is provided to the patient's personal pharmacist or pharmacy, the server 10 returns a portion of the sales price of the supplements to the patient's personal pharmacist or pharmacy. Specifically, the mall operator collects a portion of the sales price from a payment method (e.g., a bank account, etc.) registered in advance in the server 10, and transfers part or all of it to the payment method (e.g., a bank account, etc.) of the patient's personal pharmacist or pharmacy.

[0049] This provides an incentive for the pharmacist or pharmacy to provide advice to patients about health-related products (such as supplements).

[0050] <Variation 3> The information processing system 1 provides a predetermined incentive to a patient when the patient has already concluded a family doctor contract with a pharmacist or a pharmacy. For example, when a patient uses a medicine notebook app on the patient terminal 20 to purchase an item such as an over-the-counter drug, supplement, or health food from an in-app mall, the in-app mall operating system references the storage device of the server 10 and confirms whether the patient and the pharmacist or pharmacy are linked and managed. If they are linked, i.e., if a family doctor contract has been concluded, the mall operating system discounts a predetermined rate (e.g., 10%) from the purchase price. The same applies when a company that provides the medicine notebook app sells an item to a patient on an e-commerce mall operated outside the app. The e-commerce mall operating system references the storage device of the server 10 and confirms whether the patient and the pharmacist or pharmacy are linked and managed. If they are linked, i.e., if a family doctor contract has been concluded, the mall operating system discounts a predetermined rate (e.g., 10%) from the purchase price.

[0051] This provides an incentive for patients to enter into a family doctor contract.

[0052] <Variation 4> The server 10 can support consensus building not only for consent forms for primary care contracts, but also for any document exchanged between a patient and a pharmacist or a pharmacy, using the same procedure as in step S101.

[0053] <Variation 5> The server 10 can collect information on whether or not an activity related to the patient's health condition (including prescription, dispensing, purchase, etc.) has occurred by a push-type operation to the patient terminal 10.

[0054] For example, if a patient has installed a medicine notebook app on their smartphone (if there is a smartphone that functions as the patient terminal 20), the server 10 can prompt the patient terminal 20 to input medication information, etc., by sending a push notification to the patient terminal 20. Specifically, when a predetermined time has passed since prescription or dispensing, the contract management unit 102 of the server 10 sends a push notification message with the content, such as "How are you feeling after taking the medicine?" When the patient selects the push notification, the patient terminal 20 generates a medication information input screen and prompts the patient to input their physical condition after taking the medicine and whether or not they have experienced any side effects.

[0055] Alternatively, even if the patient does not have a medicine notebook app installed on their smartphone (i.e., if they do not have a smartphone that functions as the patient terminal 20), the server 10 can send a push message to the patient's smartphone using SMS (short message service) or the like. The message can include a link (URL) for downloading the medicine notebook app along with a phrase such as "How are you feeling after taking your medication?" The patient can download the medicine notebook app via the link and install it on their smartphone, allowing them to enter medication information such as their physical condition after taking the medication and whether or not they experienced any side effects.

[0056] <Embodiment 2> A pharmacist or pharmacy that has concluded a family doctor contract with a patient can use the patient's PHR to provide the patient with total health management support. In particular, the information processing system 1 enables electronic communication using a medication record app installed on the patient terminal 20 or the push notification function of the terminal itself. In the second embodiment, these features are actively utilized to suggest supplements, health foods, and treatment plans to patients, and to arrange online medical consultations.

[0057] 3 is a block diagram showing the functional configuration of the server 10 according to the embodiment 2. The server 10 includes a patient information analysis unit 103 and a proposing unit 104 in addition to the components of the embodiment 1.

[0058] FIG. 6 is a flowchart of the patient health management support process executed by the information processing system 1.

[0059] (Support for patient health management) Step S301: The patient information management unit 101 of the server 10 accumulates a PHR for each patient. As described above, the PHR for each patient includes the patient's medication history information, purchase information, and health record. That is, for example, when a patient receives a prescription or prescription for medication at a medical institution or pharmacy, the medication history information is added to the patient information management unit 101 of the server 10. When a patient uses the medicine notebook app on the patient terminal 20 to purchase items such as over-the-counter drugs, supplements, or health foods in an in-app mall, the purchase information is added to the patient information management unit 101 of the server 10. The same applies when a provider of the medicine notebook app sells items to patients in an e-commerce mall operated outside the app. When a patient uses the medicine notebook app on the patient terminal 20 to register prescription drug use information or intake information for over-the-counter drugs, supplements, or health foods, the intake information or intake information is added to the patient information management unit 101 of the server 10.

[0060] Step S302: The patient information analysis unit 103 of the server 10 analyzes the PHR for each patient stored in the patient information management unit 101 and generates suggested information suitable for the health condition inferred from each patient's PHR. The suggested information includes supplements, health foods, treatment plans, etc. suitable for the patient. The suggestion unit 104 notifies the generated suggested information to the patient terminal 20 and / or the pharmacy terminal 30. Notification can be made by means of, for example, push notification to a smartphone or PC, a voice call by telephone, email, a messaging app, or the like.

[0061] Here, the notification to the patient terminal 20 can be sent as if it is from the patient's regular pharmacy or pharmacist. For example, the name of the patient's regular pharmacy or pharmacist can be written in the message, or the name of the regular pharmacy or pharmacist can be set as the sender of the message. When the notification is sent to the patient terminal 20 by such means, the patient can receive the notification from the suggestion unit 103 as if it were a suggestion from the patient's regular pharmacy or pharmacist.

[0062] Several examples of the analysis of PHR by the patient information analysis unit 103 will be shown below. (1) To patients who have a history of taking or are currently taking certain medications, we recommend supplements, health foods, etc.

[0063] The patient information analysis unit 103 searches the medication history information stored in the patient information management unit 101 to extract patients who have been prescribed a hypoglycemic agent. As an example, by extracting patients who have been prescribed the drug within the past N months, it is possible to extract patients who are thought to be currently taking the drug. For example, by searching for patients whose medication history information includes a drug code assigned to the hypoglycemic agent, it is possible to extract the corresponding patient. The drug code may include, for example, a drug price list drug code managed by the Ministry of Health, Labor and Welfare, an individual drug code (YJ code), a code for the prescription computer processing system, a Japanese Article Number (JAN) code, a Global Trade Item Number (GTIN), a reference number (HOT code), an Anatomical Therapeutic Chemical Classification System (ATC) code, etc.

[0064] The suggestion unit 104 transmits a notification to the patient terminal 20 of the extracted patient, recommending, for example, supplements or health foods that have the effect of lowering or suppressing the rise of blood sugar. The notification may be sent to all relevant patients at once, or may be sent individually to only specific patients.

[0065] In addition to / instead of hypoglycemic agents, the patient information analysis unit 103 may search the purchase information stored in the patient information management unit 101 to extract patients with a purchase history of supplements that lower or suppress the rise of blood glucose. For supplements, by extracting patients who have been prescribed the supplement within the past N months, it is possible to extract patients who are thought to be currently taking the supplement. Furthermore, since supplements are also assigned a type similar to a pharmaceutical code, it is possible to extract corresponding patients using the type as a key.

[0066] The suggestion unit 104 sends a notification to the patient terminal 20 of the extracted patient, recommending, for example, other supplements or health foods that have similar effects to the supplements currently being taken. The notification may be sent to all relevant patients at once, or may be sent individually to specific patients only.

[0067] (2) We recommend supplements and health foods to patients who have symptoms that are difficult to diagnose as illnesses, such as overweight or early symptoms of dementia.

[0068] The patient information analysis unit 103 extracts patients whose medication history information and purchase information include prescription or purchase histories of drugs and supplements related to hypercholesterolemia and bulimia. So-called overweight is not recognized as a disease, but hypercholesterolemia and bulimia are known as symptoms closely related to overweight. Therefore, by extracting patients with hypercholesterolemia and bulimia, it is possible to identify patients who are likely to be overweight.

[0069] Alternatively, the patient information analysis unit 103 extracts patients whose health records include the results of a dementia check and whose scores meet a certain standard, and / or patients whose basic information includes an age of a certain age (for example, 40 years old) or above. This makes it possible to capture patients who are not recognized as having dementia but who may have early symptoms of dementia.

[0070] The suggestion unit 104 transmits to the patient terminal 20 of the extracted patient a notification recommending, for example, supplements or health foods that are effective against overweight or early symptoms of dementia. The notification may be sent to all relevant patients at once, or may be sent individually to specific patients only.

[0071] <Third Embodiment> In the third embodiment, medication history information is used to notify the patient of a reminder to come to the pharmacy next time.

[0072] The server 10 of the third embodiment has the same functional configuration as that of the second embodiment (FIG. 3).

[0073] FIG. 7 is a flowchart of the patient visit reminder process executed by the information processing system 1.

[0074] (Visit reminder) Step S401: The patient information analysis unit 103 of the server 10 analyzes the patient's medication history information and estimates the patient's next visit date, i.e., the scheduled dispensing date. For example, the number of days for which the prescription is issued (number of prescription days) is identified based on the quantity of medication prescribed in the latest prescription history. The next visit date can be estimated as the date obtained by adding the number of prescription days to the prescription date. Alternatively, if the same medication has been prescribed multiple times in the past, the patient information analysis unit 103 calculates the average value (average prescription interval) of the intervals between prescription dates (prescription interval). The next visit date can be estimated as the date obtained by adding the average prescription interval to the latest prescription date.

[0075] Step S402: The suggestion unit 104 sends a reminder notice to the patient terminal 20 of the patient, for example, N days before the next visit. The reminder notice may include a message such as "We look forward to your visit." The notice may be sent by means of, for example, a push notification to a smartphone or PC, a voice call by telephone, email, a communication app (LINE (registered trademark), etc.), etc. The history of the notice is recorded in the PHR, such as medication history information.

[0076] Here, the notification to the patient terminal 20 can be sent as if it is from the patient's regular pharmacy or pharmacist. For example, the name of the patient's regular pharmacy or pharmacist can be written in the message, or the name of the regular pharmacy or pharmacist can be set as the sender of the message. When the notification is sent to the patient terminal 20 by such means, the patient can receive the notification from the suggestion unit 103 as if the patient had been encouraged to visit the pharmacy by the regular pharmacy or pharmacist.

[0077] Step S403: The patient information analysis unit 103 of the server 10 calculates the estimated number of medications required on the next visit date. For example, the required number of medications can be estimated to be the same as the number of medications prescribed last time. The patient information estimation unit 103 references the current number of medications in stock at the pharmacy, and if the difference between the number in stock and the required number is less than a predetermined threshold, places an order for additional medications in advance. Alternatively, the suggestion unit 104 sends a message to the pharmacy terminal 30 prompting the user to place an additional medication order.

[0078] Here, the process in S403 may be limited to patients who have signed a family doctor contract. Since patients who have signed a family doctor contract are likely to have a high rate of repeat visits, this can minimize inventory oversupply caused by additional orders.

[0079] The patient information analysis unit 103 may perform the series of processes from S401 to S403 only for patients with chronic diseases. This is because patients with chronic diseases have a high rate of repeat visits and therefore a high need for reminders. Specifically, the patient information analysis unit 103 extracts only medication history information related to specific medications associated with the chronic disease from the patient's medication history information, and subjects this to the series of processes from S401 to S403. In this case, the patient information analysis unit 103 is assumed to have a list of medications associated with chronic diseases stored in advance or to be able to refer to it. This allows reminders to be implemented only for patients who are most in need.

[0080] <Fourth Embodiment> In a family care contract, one pharmacist or one pharmacy is registered in association with one patient. The patient can update their registered family pharmacist or pharmacy to another family pharmacist or pharmacy at any time. In the fourth embodiment, a means is provided to manage the update history of the family care contract and to clearly indicate who the patient's current family pharmacist or pharmacy is.

[0081] The server 10 of the fourth embodiment has the same functional configuration as that of the first embodiment (FIG. 2).

[0082] FIG. 8 is a flowchart of the process of updating a primary care contract and managing a contract history, which is executed by the information processing system 1.

[0083] (Renewal of primary care contract and management of contract history) Step S501: When a patient enters into a family care contract with a pharmacist or pharmacy other than their current family pharmacist or pharmacy, the contract management unit 102 displays a document (consent form) on the display device of the patient terminal 20, requesting consent to enter into a family care contract with the new pharmacist or pharmacy. Specifically, processing similar to step S101 is performed. It is preferable that the consent form for the new family care contract includes a sentence such as, "I agree to change my family pharmacist (or family pharmacy) to XX pharmacist (XX pharmacy)."

[0084] Step S502: If the patient agrees to enter into a new primary care contract, the contract management unit 102 adds new contract information to the storage device, including the date and time the contract was established, the patient's name or identifier, the name or identifier of the pharmacist or pharmacy, the contents of the consent form, etc.

[0085] Step S503: The contract management unit 102 allows the new family pharmacist or pharmacy to refer to the patient's PHR that has been accumulated up to that point.

[0086] For example, if medication history information, purchasing information, medication information, intake information, etc. associated with the patient ID of a patient with whom a new family care contract has been concluded are already recorded in the patient information management unit 101, the contract management unit 102 transmits this information to the pharmacy terminal 30 linked to the pharmacist ID or pharmacy ID of the patient with whom the new family care contract has been concluded (for example, the pharmacy terminal 30 to which a pharmacist or pharmacy staff member has logged in using the pharmacist ID or pharmacy ID). Upon receiving this information, the pharmacy terminal 30 stores it in a storage device in association with the patient ID. At this time, the pharmacy terminal 30 may output a notification to the pharmacist or the like indicating that information related to this patient is now available for viewing. The pharmacist or the like can view various pieces of information linked to the patient by specifying the patient ID on the pharmacy terminal 30.

[0087] Alternatively, if medication history information, purchase information, medication information, intake information, etc. associated with the patient ID of a patient with whom a new family care contract has been concluded are already recorded in the patient information management unit 101, the contract management unit 102 grants access rights to this information to the pharmacist ID or pharmacy ID of the patient with whom the new family care contract has been concluded. The pharmacist, etc. can log in to the pharmacy terminal 30 using the pharmacist ID or pharmacy ID and refer to the patient information management unit 101 of the server 10 to view various information linked to this patient.

[0088] This means that a pharmacist or pharmacy that has newly entered into a primary care contract will be able to view and utilize a patient's PHR as if the pharmacist or pharmacy had been creating the patient's PHR up until now.

[0089] When a new family care contract is concluded, the old family care contract is terminated. Accordingly, the contract management unit 102 can prevent the pharmacist or pharmacy with which the family care contract has been terminated from accessing the patient's PHR.

[0090] For example, if medication history information, purchase information, medication information, intake information, etc. associated with the patient ID of the patient whose family care contract has been terminated is stored in the pharmacy terminal 30 linked to the pharmacist ID or pharmacy ID with which the family care contract has been concluded (for example, the pharmacy terminal 30 to which a pharmacist or pharmacy staff member has logged in using the pharmacist ID or pharmacy ID), the contract management unit 102 can delete it. At this time, the pharmacy terminal 30 may output a notice to the pharmacist, etc., indicating that the information related to this patient can no longer be viewed.

[0091] Alternatively, if medication history information, purchasing information, medication information, intake information, etc. associated with the patient ID of a patient whose primary care contract has been terminated is recorded in the patient information management unit 101, the contract management unit 102 can delete the access rights to this information from the pharmacist ID or pharmacy ID of the patient whose primary care contract has been terminated.

[0092] Step S504: In response to a request from the patient terminal 20 or the pharmacy terminal 30, the contract management unit 102 can output the conclusion history of a personal care contract for any patient.

[0093] For example, the patient terminal 20 or the pharmacy terminal 30 requests the contract management unit 102 of the server 10 to display the history of the medical treatment contract, specifying the patient ID.

[0094] The contract management unit 102 extracts contract information related to the specified patient ID from the contract information stored in the storage device. If the patient has previously signed multiple primary care contracts, multiple pieces of contract information are extracted. The contract management unit 102 transmits the extracted contract information to the patient terminal 20 or the pharmacy terminal 30.

[0095] The patient terminal 20 or the pharmacy terminal 30 outputs one or more pieces of received contract information by screen display or the like. When multiple pieces of contract information exist, it is preferable to sort and output the contract information by the contract establishment date. Furthermore, the latest contract information can be output in a display format different from that of past contract information. This allows patients, pharmacists, and pharmacies to easily confirm the currently valid primary care contract. In other words, according to this system, the history of previously concluded primary care contracts (logs including electronically signed consent forms) is stored on the server 10, making it easy to determine which primary care contract is the most recent based on the contract establishment date.

[0096] The present invention can be implemented using hardware, and any process can be implemented by having a central processing unit (CPU) execute a computer program. In this case, the computer program can be stored and provided to a computer using various types of non-transitory computer-readable media. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, and semiconductor memories (e.g., mask ROMs, programmable ROMs (PROMs), erasable PROMs (EPROMs), flash ROMs, and random access memories (RAMs)). The program may also be provided to a computer by various types of transitory computer-readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire or an optical fiber, or via a wireless communication path. [Explanation of symbols]

[0097] 1. Information Processing Systems 10 Servers 20 Patient terminal 30 Pharmacy terminal 101 Patient Information Management Department 102 Contract Management Department

Claims

1. Accepting an input from the patient terminal indicating that the patient has agreed to a family care contract with the pharmacist or pharmacy; The contents of the consent will be electronically stored in a storage device. server.

2. Detecting that an activity related to the patient's health condition has occurred; The activity can be viewed on a pharmacy terminal used by the pharmacist or pharmacy who is a party to the family care contract. The server of claim 1.

3. When the activity becomes viewable by the pharmacy terminal used by the pharmacist or pharmacy that is a party to the family care contract, an incentive is given to the pharmacist or pharmacy. The server according to claim 2.

4. Print out a document containing the content of the consent. The server of claim 1.

5. Prompting the patient to input information about the activity by sending a push notification to the patient device. The server of claim 1.

6. the activity includes medication history information; The medication history information is used to estimate the next visit date, and a reminder to visit the pharmacy is sent to the patient terminal. The server according to claim 2.

7. receiving, from the patient terminal, an input indicating that the patient has agreed to the family care contract with the new pharmacist or pharmacy; The content of said consent is electronically stored in said storage device. The server of claim 1.

8. The contents of the consents relating to the plurality of family care contracts that the patient has previously concluded are read from the storage device, and the contents are sorted by the contract establishment date and displayed on the screen. The server of claim 7.

9. Includes a patient terminal, a pharmacy terminal, and a server, The patient terminal transmits an input to the server indicating that the patient has agreed to a patient care contract with the pharmacist or pharmacy; The server Electronically store the content of said consent in a storage device; When an occurrence of an activity related to the patient's health condition is detected, the activity can be viewed on a pharmacy terminal used by the pharmacist or pharmacy that is a party to the family care contract. Information processing system.

10. The server receiving an input from the patient terminal indicating that the patient has agreed to a family care contract with the pharmacist or pharmacy; and electronically storing the consent in a storage device. Information processing methods.

11. A program for causing a computer to execute the method according to claim 10.

Images