Information processing device and program

Abstract

To provide a user (a pharmacist or an administrator, for example) with information useful for suggestion for accepting a face prescription.SOLUTION: An information processing apparatus includes means of determining whether a target patient who is a target of patient compliance instruction corresponds to a recommendation patient who should be suggested for acceptance of a face prescription based on patient information on the target patient, and means of presenting a determination result of the means of determining to a user of a target pharmacy performing the patient compliance instruction.SELECTED DRAWING: Figure 3

Description

[Technical field]

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

[0002] Generally, a pharmacist who is in charge of providing medication instructions to a patient who visits a pharmacy provides medication instructions tailored to the patient, taking into consideration the prescription brought by the patient and information provided by the patient.

[0003] Patent document 1 discloses a technology in which a search target medication search term is obtained from medical terms included in a medical analysis item, medical information for the search target medication search term stored in a database is searched for regarding the user's medication information and medication-related medical information, the searched medical information is composite-processed by a staff member of a pharmacy support organization to obtain composite-processed medical information for pharmacists, and this is provided to a terminal of the dispensing pharmacy that accepted the search request. This reduces the burden on pharmacists when providing medication instructions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2016-212829 A Summary of the Invention [Problem to be solved by the invention]

[0005] From a business perspective, it is desirable for pharmacies to increase the number of prescriptions they fill. On the other hand, the proportion of prescriptions that pharmacies fill tends to be high for medical institutions located near the pharmacy (so-called "medical institutions near the pharmacy"). Therefore, in order to increase the number of prescriptions filled, it is effective to fill so-called "face prescriptions" - prescriptions from patients who visit your pharmacy that are also being filled by other pharmacy offices (for example, from medical institutions other than the pharmacy in front of your pharmacy). In order to suggest to patients that they should fill a prescription, it is important that the pharmacist in charge of the patient's medication instruction decides on the validity of filling a prescription by taking into account the patient's information. For this purpose, it is preferable to provide the pharmacist with patient information that is useful for deciding on the validity of filling a prescription by a prescription.

[0006] However, although the technology of Patent Document 1 can provide information useful for providing medication instructions to patients, it cannot provide information useful for proposing compliance with area prescriptions.

[0007] An object of the present invention is to provide a user (e.g., a pharmacist or administrator) with information useful in proposing prescription fulfillment. [Means for solving the problem]

[0008] One aspect of the present invention is A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered based on patient information on the target patient, A means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction, It is an information processing device. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a functional block diagram of the information processing system of FIG. 1. [Diagram 3] FIG. 1 is an explanatory diagram of an overview of the present embodiment. [Figure 4] 3 is a diagram showing a data structure of a pharmacy database according to the present embodiment. FIG. [Diagram 5] FIG. 2 is a diagram showing a data structure of a patient database according to the present embodiment. [Figure 6] 4 is a diagram showing a data structure of a pharmacy usage history database of the present embodiment. FIG. [Figure 7] FIG. 2 is a sequence diagram of information processing according to the present embodiment. [Figure 8] 8 is a diagram showing an example of a screen displayed in the information processing of FIG. 7. [Figure 9] FIG. 11 is a diagram showing a data structure of a patient database according to the second modified example. [Figure 10] FIG. 11 is a sequence diagram of information processing according to the second modified example. [Figure 11] 11A and 11B are diagrams showing examples of screens displayed in the information processing of FIG. 10. [Figure 12] FIG. 13 is an explanatory diagram of an overview of Modification 5. [Figure 13] FIG. 13 is a diagram showing the data structure of a pharmacy database according to the fifth modified example. [Figure 14] FIG. 13 is a sequence diagram of information processing in Modification 5. [Figure 15] 15 is a diagram showing an example of a screen displayed in the information processing of FIG. 14. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and the repeated description will be omitted.

[0011] (1) Information Processing System Configuration The configuration of the information processing system will be described below. Fig. 1 is a block diagram showing the configuration of the information processing system of this embodiment. Fig. 2 is a functional block diagram of the information processing system of Fig. 1.

[0012] As shown in FIG. 1, the information processing system 1 includes a client device 10 and a server 30. The client device 10 and the server 30 are connected via a network (eg, the Internet or an intranet) NW.

[0013] The client device 10 is a computer (an example of an "information processing device") that transmits a request to the server 30. The client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0014] The server 30 is a computer (an example of an "information processing device") that provides the client device 10 with a response in response to a request transmitted from the client device 10. The server 30 is, for example, a web server.

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

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

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

[0018] The programs include, for example, the following programs: ·OS (Operating System) programs · Programs for applications that process information (e.g. web browsers)

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

[0020] The processor 12 is configured to realize the functions of the client device 10 by starting a program stored in the storage device 11. The processor 12 is, for example, a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0021] The input / output interface 13 is configured to obtain user instructions from an input device connected to the client device 10 , and to output information to an output device connected to the client device 10 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

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

[0023] (1-2) Server configuration The configuration of the server 30 will now be described.

[0024] As shown in FIG. 2, the server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface .

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

[0026] The programs include, for example, the following programs: -OS programs Application programs that perform information processing

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

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

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

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

[0031] (2) Overview of the embodiment An overview of this embodiment will be described below with reference to Fig. 3, which is an explanatory diagram of the overview of this embodiment.

[0032] As shown in FIG. 3, a user (eg, a pharmacist) who provides medication instruction to a patient who is the subject of medication instruction (hereinafter referred to as a “target patient”) at a target pharmacy uses a client device 10.

[0033] When the user operates the client device 10 during medication instruction, the client device 10 makes a judgment request to the server 30. In response to a determination request from the client device 10, the server 30 determines whether or not the target patient is a patient to whom a face prescription should be proposed (hereinafter referred to as a "recommended patient") based on the patient information on the target patient. The server 30 transmits the determination result to the client device 10, thereby indicating to the user via the client device 10 whether the target patient is a recommended patient or not.

[0034] When the determination result that the target patient is a recommended patient is displayed on the client device 10, the user can propose filling the face prescription based on the determination result.

[0035] (3) Database The databases of this embodiment are stored in the storage device 31.

[0036] (3-1) Pharmacy database The pharmacy database of this embodiment will be described with reference to Fig. 4, which is a diagram showing the data structure of the pharmacy database of this embodiment.

[0037] Pharmacy information is stored in the pharmacy database of Fig. 4. The pharmacy information is information relating to pharmacies. The pharmacy database includes a "pharmacy ID" field, a "pharmacy name" field, a "corporation ID" field, a "corporation name" field, and a "location" field. Each field is associated with the others.

[0038] The "pharmacy ID" field stores pharmacy identification information. The pharmacy identification information is information for identifying a pharmacy.

[0039] The "pharmacy name" field stores pharmacy name information. The pharmacy name information is information related to the name of the pharmacy.

[0040] The "Corporate ID" field stores corporate identification information. The corporate identification information is information for identifying at least one of the corporate entity that operates the pharmacy and a group made up of multiple corporate entities.

[0041] The "Corporate name" field stores corporate name information. The corporate name information is information related to the name of a corporation.

[0042] The "location" field stores location information. The location information is information about the address of the location of the pharmacy.

[0043] (3-2) Patient Database The patient database of this embodiment will now be described with reference to Fig. 5, which is a diagram showing the data structure of the patient database of this embodiment.

[0044] Patient information is stored in the patient database in Figure 5. The patient information is information about patients. The patient database includes a "patient ID" field, a "patient name" field, a "patient attribute" field, a "place of residence" field, and a "family ID" field. Each field is associated with the others. The patient database is associated with the pharmacy identification information.

[0045] The "Patient ID" field stores patient identification information. The patient identification information is information for identifying a patient. The patient identification information is, for example, at least one of the following: · My Number -Patient identification information registered in advance at the target pharmacy Insurance card number

[0046] The "patient name" field stores patient name information. The patient name information is information related to the patient's name.

[0047] The "patient attribute" field stores patient attribute information. The patient attribute information is information relating to the attributes of a patient. The "patient attribute" field includes a "gender" field and an "age" field.

[0048] The "gender" field stores gender information. The gender information is information about the gender of the patient.

[0049] The "age" field stores age information. The age information is information about the age of the patient.

[0050] The "Residence" field stores residence information. The residence information is information about the address of the patient's residence.

[0051] The "Family ID" field stores patient identification information (hereinafter referred to as "family patient identification information") for the patient's family members (e.g., family members living with the patient). If family patient identification information is not associated, "N / A" is stored.

[0052] (3-3) Pharmacy usage history database The pharmacy usage history database of this embodiment will be described below with reference to Fig. 6, which is a diagram showing the data structure of the pharmacy usage history database of this embodiment.

[0053] 6 stores pharmacy usage history information. The pharmacy usage history information is information related to a patient's pharmacy usage history. The pharmacy usage history information is, for example, information recorded in an electronic medicine notebook. The patient database includes a "pharmacy usage history ID" field, a "timestamp" field, a "name of the prescribing medical institution" field, a "pharmacy used" field, a "prescribed drug" field, a "drug duration" field, and a "total drug price" field. Each field is associated with the others. The pharmacy usage history database is associated with patient identification information.

[0054] The "pharmacy usage history ID" field stores pharmacy usage history identification information. The pharmacy usage history identification information is information for identifying a pharmacy usage history. The pharmacy usage history identification information is information for identifying, for example, a prescription.

[0055] The "timestamp" field stores a timestamp of the pharmacy usage history. The timestamp is information about the date and time when the medicine was dispensed.

[0056] The "Name of Prescribing Medical Institution" field stores information about the name of the prescribing medical institution. The information about the name of the prescribing medical institution is information about the name of the medical institution that issued the prescription.

[0057] The "pharmacy used" field stores pharmacy used information. The pharmacy used information is information for identifying the pharmacy used by the patient. The pharmacy used information is pharmacy identification information or information related to the pharmacy name.

[0058] The "Prepared Drug" field stores dispensed drug information. The dispensed drug information is information about dispensed drugs provided to a patient. The dispensed drug information is, for example, information that identifies a dispensed drug or information about the dispensed drug name.

[0059] The "Drug Period" field stores drug period information. Drug period information is information about the drug period for each dispensed drug (for example, the period from the date indicated by the time stamp (hereinafter referred to as the "dispensing date") to the date when the number of prescription days is added to the dispensing date).

[0060] The "total drug price" field stores total drug price information. The total drug price information is information regarding the total price of drugs dispensed to a patient on a certain dispensing date.

[0061] (4) Information processing The information processing of this embodiment will be described with reference to Fig. 7. Fig. 8 is a diagram showing an example of a screen displayed in the information processing of Fig. 7.

[0062] In the example of FIG. 7, the user of the target pharmacy is a pharmacist who provides medication instructions to a target patient who visits the target pharmacy. The process in FIG. 7 is triggered, for example, by the client device 10 logging in to a service provided by the server 30 using the pharmacy identification information of the target pharmacy.

[0063] The client device 10 executes reception of a user instruction (S110). Specifically, the processor 12 displays a screen P10 (FIG. 8) on the display.

[0064] The screen P10 includes an operation object B10 and a field object F10.

[0065] The field object F10 is an object that displays a list of patient name information stored in the patient database (FIG. 5) associated with the pharmacy identification information used for login, and accepts the selection of any patient name information from the user. Patient identification information is assigned to each patient name information. When the user selects patient name information, the patient identification information assigned to the selected patient name information is identified as the patient identification information (hereinafter referred to as the "target patient identification information") of the patient (hereinafter referred to as the "target patient") who is to be determined as a recommended patient.

[0066] The operation object B10 is an object that receives a user instruction for executing a surface prescription request.

[0067] After step S110, the client device 10 executes a surface prescription request (S111). Specifically, when the user selects any patient name information in the field object F10 and operates the operation object B10, the processor 12 transmits surface prescription request data to the server 30. The surface prescription request data includes, for example, the following information: - Target patient identification information assigned to the patient name information selected in field object F10

[0068] After step S111, the server 30 executes the determination of recommended patients (S130).

[0069] A first example of step S130 will be described. Processor 32 refers to a pharmacy usage history database (Figure 6) associated with the target patient identification information included in the face-to-face prescription request data, and calculates the total number of times the target patient has used the pharmacy (i.e., the sum of the number of times the target pharmacy has been used and the number of times a non-target pharmacy has been used) during a certain period (e.g., three months prior to the date and time of execution of step S130) and the number of times the target patient has used the target pharmacy. Processor 32 calculates the target pharmacy utilization rate of the target patient using Equation 1. The target pharmacy utilization rate is the ratio of the number of times the target pharmacy is utilized to the number of times the target patient utilizes the pharmacy during a certain period of time. (Formula 1) Target pharmacy utilization rate = Number of visits to target pharmacy / Total number of visits to pharmacy The processor 32 determines that the target patient is a recommended patient if the target pharmacy utilization rate is equal to or lower than a predetermined threshold. In other words, the lower the utilization rate of the target pharmacies, the greater the potential for utilization of the target pharmacies, and therefore the recommendation to offer face-to-face prescription fulfillment is recommended.

[0070] A second example of step S130 will now be described. The second example of step S130 is an example that is combined with the first example of step S130. Processor 32 refers to a pharmacy usage history database (Figure 6) associated with the target patient identification information included in the face-to-face prescription request data, and calculates the total number of times the target patient has used the pharmacy over a certain period (e.g., three months prior to the date and time of execution of step S130). The processor 32 determines that the target patient is a recommended patient if the target pharmacy utilization rate is equal to or less than a predetermined threshold and the total number of utilization times is equal to or greater than a predetermined threshold. In other words, the lower the target pharmacy utilization rate and the higher the total number of utilizations, the higher the potential for utilization of the target pharmacy, and therefore the more likely it is that a proposal to fill prescriptions in the area will be recommended.

[0071] A third example of step S130 will be described. Processor 32 refers to a pharmacy usage history database (Figure 6) associated with the target patient identification information included in the face-to-face prescription request data, and identifies the total drug price information for the target patient for a certain period (e.g., three months prior to the date and time of execution of step S130). If the total drug price is equal to or greater than a predetermined threshold, the processor 32 determines that the target patient is a recommended patient. In other words, the higher the total drug price, the more the suggestion to fulfill the demand for face-to-face prescriptions is recommended.

[0072] A fourth example of step S130 will be described. Processor 32 refers to the pharmacy usage history database (FIG. 6) associated with the target patient identification information included in the face-to-face prescription request data to calculate the number of days that have passed since the medication period. The number of days that have passed is the difference between the end date of the medication period of the target patient and the execution date and time of step S130. If the execution date and time of step S130 is included in the medication period, the number of days that have passed is 0. If the number of days elapsed is zero or equal to or less than a predetermined threshold, the processor 32 determines that the subject patient is a recommended patient. In other words, the fewer the number of days that have passed, the more the suggestion to fill a face prescription is recommended.

[0073] The first to fourth examples of step S130 can be combined with each other.

[0074] After step S130, the server 30 executes distance determination (S131). Specifically, the processor 32 references the patient database (FIG. 5) to identify residence information associated with the target patient identification information. Processor 32 consults the pharmacy database (FIG. 4) to identify location information associated with the target pharmacy identification information. Processor 32 calculates the distance between the target patient's residence and the target pharmacy's location from the residence information and location information. The processor 32 determines whether or not the distance is equal to or less than a predetermined distance (that is, whether or not the target patient lives near the target pharmacy).

[0075] After step S131, the server 30 executes an area prescription response (S132). Specifically, the processor 32 transmits the surface prescription response data to the client device 10. The surface prescription response data includes, for example, the following information: Patient identification information of the patient Patient name information of the target patient Patient demographic information of the target patient (gender and age information) -Residence information of the target patient - Information on the target patient's pharmacy usage history (e.g., information on the recent usage history of pharmacies other than the target pharmacy (hereinafter referred to as "other pharmacies")) A message according to the determination result obtained in step S130 The result of distance determination obtained in step S131

[0076] After step S132, the client device 10 displays the determination result (S112). Specifically, the processor 12 displays a screen P11 (FIG. 8) on the display.

[0077] The screen P11 includes display objects A111 to A112 and operation objects B111 to B112.

[0078] The display object A111 displays the patient identification information, patient name information, patient attribute information, and place of residence information of the target patient.

[0079] A message according to the determination result is displayed on the display object A112.

[0080] The operation object B111 is an object that receives a user instruction for presenting detailed information useful for proposing a response to a demand for a face prescription.

[0081] The operation object B112 is an object that receives a user instruction for displaying the pharmacy usage history information of the target patient.

[0082] When the user operates the operation object B111, the processor 12 displays a screen P12 (FIG. 8) on the display.

[0083] The screen P12 displays detailed information about the target patient. The detailed information includes, for example, the following information: The name of the medical institution that issued the prescription that was used to fill the drug dispensed at another institution - The name of the doctor who issued the prescription - Name of the other station - Date of dispensing of the drug Number of days the drug has been prescribed Name of the drug The amount of the drug

[0084] Based on the information displayed on the screen P12, the user proposes to the target patient that he or she fill a face prescription.

[0085] (5) Summary of the present embodiment According to this embodiment, a recommended patient to whom a prescription should be filled is determined based on the patient information of the target patient. This allows the user to propose a prescription to an appropriate patient among the target patients. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0086] According to this embodiment, a patient whose target pharmacy usage rate is lower than a predetermined threshold may be determined to be a recommended patient. This allows the user to recognize a patient whose target pharmacy usage rate is relatively low (i.e., who has a large room to use the target pharmacy) as a recommended patient. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0087] According to this embodiment, a patient whose total number of visits to a target pharmacy is equal to or greater than a predetermined threshold may be determined to be a recommended patient. This allows the user to recognize a patient who has a relatively large total number of visits (i.e., who frequently visits a pharmacy) as a recommended patient. As a result, the target pharmacy can increase the opportunities to fill prescriptions.

[0088] According to this embodiment, a patient whose total drug price is equal to or greater than a predetermined threshold may be determined to be a recommended patient. This allows the user to recognize a patient whose total drug price is relatively high (i.e., who pays a large amount for medicine) as a recommended patient. As a result, the target pharmacy can increase the average customer price.

[0089] According to this embodiment, a patient for whom the number of days since the target patient's medication period is zero or less than a predetermined threshold may be determined to be a recommended patient. This allows the user to recognize a patient who has a short number of days since the medication period (i.e., who is more likely to take the medication next time) as a recommended patient. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0090] (6) Variations A modification of this embodiment will now be described.

[0091] (6-1) Variation 1 Modification 1 will be described. Modification 1 is an example in which it is determined whether a target patient is a recommended patient based on the patient information of the patient's family. Descriptions similar to those above will be omitted.

[0092] (6-1-1) Information processing The information processing of the first modification will be described.

[0093] The client device 10 executes the process from receiving a user instruction (S110) to requesting a surface prescription (S111) in the same manner as in FIG.

[0094] After step S111, the server 30 executes the determination of recommended patients (S310). Specifically, the processor 32 refers to the patient database (FIG. 5) to identify family patient identification information associated with the target patient identification information included in the face-to-face prescription request data. As in the first to fourth examples of step S130, the processor 32 refers to the pharmacy usage history database (FIG. 6) associated with the family patient identification information to determine whether or not a family member of the target patient is a recommended patient.

[0095] After step S310, the server 30 executes the steps from distance determination (S131) ​​to surface prescription response (S312) in the same manner as in FIG.

[0096] After step S312, the client device 10 executes display of the determination result (S111). Specifically, the processor 12 displays a screen P11 (FIG. 8) on the display. When the user operates the operation object B111, the processor 12 displays a screen P13 (FIG. 8) on the display.

[0097] The screen P13 displays detailed information about the family of the target patient. The detailed information includes, for example, the following information: The name of the medical institution that issued the prescription that was used to fill the drug dispensed at another institution - The name of the doctor who issued the prescription - Name of the other station - Date of dispensing of the drug Number of days the drug has been prescribed Name of the drug The amount of the drug

[0098] The user can view the information displayed on screen P13 and propose to the target patient that he or she fulfill a prescription for the target patient's family.

[0099] (6-1-2) Summary According to the first modification, a recommended patient to whom a prescription should be filled is determined based on the patient information of the family of the target patient. This allows the user to propose a prescription to an appropriate patient among the target patients. As a result, the target pharmacy can increase the opportunities to fill prescriptions.

[0100] (6-2) Variation 2 Modification 2 will be described. Modification 2 is an example of calculating an area prescription score. The area prescription score is an index showing the degree of room for expanding demand by acquiring area prescriptions of target patients. The same explanation as above will be omitted.

[0101] (6-2-1) Patient Database A description will be given of the patient database of the modified example 2. Fig. 9 is a diagram showing the data structure of the patient database of the modified example 2.

[0102] The patient database in FIG. 9 stores patient information. The patient database includes a "patient ID" field, a "patient name" field, a "patient attribute" field, a "residence" field, a "family ID" field, and a "surface prescription score" field. Each field is associated with each other. The patient database is associated with the pharmacy identification information.

[0103] The “Patient ID” field, “Patient Name” field, “Patient Attributes” field, “Place of Residence” field, and “Family ID” field are the same as those in FIG.

[0104] The "area prescription score" field stores the area prescription score. The area prescription score is an index showing the room for expansion of the demand for area prescriptions of patients.

[0105] (6-2-2) Information Processing A description will be given of information processing in Modification 2. Fig. 10 is a sequence diagram of the information processing in Modification 2. Fig. 11 is a diagram showing an example of a screen displayed in the information processing in Fig. 10.

[0106] In the example of FIG. 10, the user of the target pharmacy is a pharmacist who provides medication instructions to a target patient who visits the target pharmacy. The process of FIG. 10 is triggered, for example, by the client device 10 logging in to a service provided by the server 30 using the pharmacy identification information of the target pharmacy.

[0107] The client device 10 executes the process from receiving a user instruction (S110) to requesting a surface prescription (S111) in the same manner as in FIG.

[0108] After step S111, the server 30 executes calculation of the surface prescription score (S230). Specifically, an area prescription model is stored in the storage device 31. In the area prescription model, a correlation between patient information and an area prescription score is described.

[0109] A first example of step S230 will be described. The processor 32 calculates the target pharmacy utilization rate of the target patient, similarly to the first example of step S130. The processor 32 calculates an area prescription score according to the target pharmacy utilization rate by applying the target pharmacy utilization rate to the area prescription model. The face-to-face prescription model is designed so that the lower the target pharmacy utilization rate, the higher the face-to-face prescription score. In other words, the lower the target pharmacy utilization rate, the greater the room for expansion of face-to-face prescription demand.

[0110] A second example of step S230 will now be described. The second example of step S230 is an example that is combined with the first example of step S230. The processor 32 calculates the total number of times the subject patient uses the pharmacy, similar to the second example of step S130. The processor 32 calculates an area prescription score according to the combination of the target pharmacy utilization rate and the total number of uses by providing the target pharmacy utilization rate and the total number of uses to the area prescription model. The face prescription model is designed so that the face prescription score is higher the lower the target pharmacy utilization rate and the higher the total number of utilizations. In other words, the lower the target pharmacy utilization rate and the higher the total number of utilizations, the higher the room for expanding face prescriptions.

[0111] A third example of step S230 will be described. The processor 32 identifies the total drug price information of the target patient, similarly to the third example of step S130. The processor 32 provides the total drug price information to the area prescription model, thereby calculating an area prescription score according to the total drug price information. The face prescription model is designed so that the higher the total drug price, the higher the face prescription score. In other words, the higher the total drug price, the greater the room for expanding face prescriptions.

[0112] A fourth example of step S230 will be described. The processor 32 calculates the number of days that have passed since the taking period, similarly to the fourth example of step S130. The processor 32 calculates an area prescription score according to the number of elapsed days by providing the number of elapsed days to the area prescription model. The face-to-face prescription model is designed so that the fewer days that have passed, the higher the face-to-face prescription score. In other words, the fewer days that have passed, the greater the potential for expansion of face-to-face prescription demand.

[0113] The first to fourth examples of step S230 can be combined with each other.

[0114] After step S230, the server 30 executes updating of the database (S231). Specifically, the processor 32 stores the area prescription score obtained in step S230 in the "area prescription score" field associated with the target patient identification information in the patient database (FIG. 9).

[0115] After step S231, the server 30 executes the determination of recommended patients (S232). Specifically, when the area prescription score obtained in step S230 is equal to or greater than a predetermined threshold, the processor 32 determines that the target patient is a recommended patient.

[0116] After step S232, distance determination (S131) ​​is executed in the same manner as in FIG.

[0117] After step S131, the server 30 executes an area prescription response (S233). Specifically, the processor 32 transmits the surface prescription response data to the client device 10. The surface prescription response data includes, for example, the following information: Patient identification information of the patient Patient name information of the target patient Patient demographic information of the target patient (gender and age information) -Residence information of the target patient - Information on the target patient's pharmacy usage history (e.g., information on the recent usage history of pharmacies other than the target pharmacy (hereinafter referred to as "other pharmacies")) The surface prescription score obtained in step S230 -Messages based on surface prescription score The result of distance determination obtained in step S131

[0118] After step S233, the client device 10 executes display of the surface prescription score (S210). Specifically, the processor 12 displays a screen P11 (FIG. 8) on the display. When the user operates the operation object B111, a screen P20 (FIG. 11) is displayed on the display.

[0119] Detailed information on the target patient is displayed on the screen P20. The detailed information includes, for example, the following information: The name of the medical institution that issued the prescription that was used to fill the drug dispensed at another institution - The name of the doctor who issued the prescription - Name of the other station - Date of dispensing of the drug Area prescription score -Messages based on surface prescription score Name of the drug The amount of the drug

[0120] (6-2-3) Summary According to the second modification, the user is presented with a face-to-face prescription score based on the patient information of the target patient. This allows the user to recognize the room for expansion of the demand for face-to-face prescriptions of the target patient. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0121] In addition, in the second modification, similarly to the first modification, the area prescription score may be calculated not only for the target patient but also for the family members of the target patient based on the patient information of the family members.

[0122] (6-3) Variation 3 Modification 3 will be described. Modification 3 is an example in which calculation of the area prescription score (S230) is performed based on the number of pieces of patient information of family members. Descriptions similar to those above will be omitted.

[0123] (6-3-1) Information processing The information processing of the third modification will be described.

[0124] In step S230 (FIG. 10), the processor 32 refers to the patient database (FIG. 5) to determine the number of family patient identification information associated with the target patient identification information included in the face-to-face prescription request data (i.e., the number of family members of the target patient). The processor 32 calculates an area prescription score according to the number of family members by providing the number of family members to the area prescription model. The face-to-face prescription model is designed so that the more family members there are, the higher the face-to-face prescription score becomes. In other words, the more family members there are in a patient, the more the face-to-face prescription request is recommended.

[0125] (6-3-2) Summary According to the third modification, a face-to-face prescription score based on the number of family members may be presented to the user. This allows the user to recognize patients with a large family (i.e., many family members who may use the target pharmacy) as patients for whom face-to-face prescriptions are recommended. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0126] (6-4) Variation 4 Modification 4 will be described. Modification 4 is an example in which calculation of the surface prescription score (S230) is executed based on family information. Descriptions similar to those above will be omitted.

[0127] (6-4-1) Information Processing The information processing of the fourth modification will be described.

[0128] In step S230 (FIG. 10), the processor 32 refers to the patient database (FIG. 5) to identify family patient identification information (hereinafter referred to as "family patient identification information") associated with the target patient identification information included in the face-to-face prescription request data. Processor 32 refers to a pharmacy usage history database (FIG. 6) associated with the family patient identification information to calculate the target pharmacy usage rate for the family. The processor 32 calculates an area prescription score according to the target pharmacy utilization rate of the family by applying the target pharmacy utilization rate of the family to the area prescription model.

[0129] The first example of the face-to-face prescription model of the modified example 4 is designed so that the higher the family's target pharmacy usage rate, the higher the face-to-face prescription score. In other words, the higher the family's target pharmacy usage rate, the higher the room for expansion of the target patient's face-to-face prescription demand.

[0130] The second example of the face-to-face prescription model of the modified example 4 is designed so that the face-to-face prescription score is higher as the family's target pharmacy utilization rate is lower. In other words, the lower the family's target pharmacy utilization rate is, the greater the room for expansion of face-to-face prescription demand for target patients, including their families.

[0131] (6-4-2) Summary According to the fourth modification, the user may be presented with an area prescription score based on the family's target pharmacy utilization rate.

[0132] In the first example of the face-to-face prescription model of the fourth modification, the user can be made aware of the room for expanding face-to-face prescription fulfillment for patients who have family members who use the target pharmacy frequently (i.e., who have family members who use the target pharmacy as their family pharmacy). As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0133] In the second example of the face-to-face prescription model of the fourth modification, the user can be made aware of the room for expanding face-to-face prescription fulfillment for patients who have family members who have a low utilization rate of the target pharmacy (i.e., who have family members who have a high potential for utilization of the target pharmacy). As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0134] (6-5) Variation 5 Modification 5 will be described. Modification 5 is an example that presents room for expanding the scope of response to multiple pharmacy prescriptions. Explanations similar to those above will be omitted.

[0135] (6-5-1) Overview of Variation 5 An overview of Modification 5 will be described below. Fig. 12 is an explanatory diagram of an overview of Modification 5.

[0136] As shown in FIG. 12, the client device 10 of the fifth modification is used by each user of a plurality of pharmacies (eg, pharmacies PH1 to PH2) and an administrator user of a corporation that manages the plurality of pharmacies.

[0137] The area prescription scores of a plurality of patients are transmitted from the client devices 10 of the pharmacies PH1 to PH2 to the server 30. As a result, the server 30 accumulates the area prescription scores for each pharmacy.

[0138] The server 30 transmits the area prescription score for each pharmacy to the client device 10 used by the administrator user.

[0139] The client device 10 used by the administrator user presents the area prescription score for each pharmacy transmitted from the server 30 to the administrator user.

[0140] The administrator user can view the area prescription score presented by the client device 10 and recognize the room for expansion of the demand for area prescriptions for each pharmacy.

[0141] (6-5-2) Pharmacy database A description will be given of the pharmacy database of the fifth modification example.

[0142] The pharmacy database in FIG. 13 stores pharmacy information. The pharmacy database includes a "pharmacy ID" field, a "pharmacy name" field, a "corporation ID" field, a "corporation name" field, a "location" field, and a "pharmacy prescription score" field. Each field is associated with the other fields.

[0143] The "pharmacy ID" field, "pharmacy name" field, "corporation ID" field, "corporation name" field, and "location" field are the same as those in FIG.

[0144] The "pharmacy prescription score" field stores the pharmacy prescription score. The pharmacy prescription score is the prescription score for each pharmacy (i.e., an index showing the room for expansion of prescription fulfillment for each pharmacy). The pharmacy prescription score is, for example, one of the following: The sum of the pharmacy face prescription scores stored in the "face prescription score" field of the patient database (Figure 9) associated with the pharmacy identification information -Average pharmacy prescription score

[0145] (6-5-3) Information Processing A description will be given of information processing in Modification 5. Fig. 14 is a sequence diagram of the information processing in Modification 5. Fig. 15 is a diagram showing an example of a screen displayed in the information processing in Fig. 14.

[0146] In the example of FIG. 14, the user of the client device 10 is an administrator user. The process of FIG. 14 is triggered, for example, when the client device 10 logs in to a service provided by the server 30 using corporate identification information.

[0147] The client device 10 executes reception of a user instruction (S310). Specifically, the processor 12 displays a screen P30 (FIG. 15) on the display.

[0148] The screen P15 includes an operation object B30. The operation object B30 is an object that receives a user instruction for executing a pharmacy management request.

[0149] After step S310, the client device 10 executes a pharmacy management request (S311). Specifically, when the user operates the operation object B30, the processor 12 transmits the pharmacy management request data to the server 30. Pharmacy management request data may include, for example, the following information: -Corporate identification information used to log in (hereinafter referred to as "target corporate identification information")

[0150] After step S311, the server 30 executes determination of the pharmacy prescription score (S330). Specifically, the processor 32 refers to the pharmacy database (FIG. 13) to identify the pharmacy prescription score associated with the target corporate identification information included in the pharmacy management request data.

[0151] After step S330, the server 30 transmits the pharmacy management response data to the client device 10. The pharmacy management response data may include, for example, the following information: The pharmacy prescription score identified in step S330

[0152] After step S331, the client device 10 executes display of the pharmacy prescription score (S312). Specifically, the processor 12 displays a screen P31 (FIG. 15) on the display.

[0153] The screen P31 includes a display object A31. The display object A31 displays the pharmacy prescription scores included in the pharmacy management response data (that is, the pharmacy prescription scores of each of a plurality of pharmacies).

[0154] (6-5-4) Summary According to the fifth modification, the area prescription score for each pharmacy is presented to the administrator user. This allows the administrator user to recognize the room for expansion of the demand for area prescriptions for each pharmacy. As a result, the administrator user can create a plan to expand the demand for area prescriptions according to the room for expansion of the demand for area prescriptions for each pharmacy.

[0155] (7) Other modifications Other modifications will now be described.

[0156] The storage device 11 may be connected to the client device 10 via a network NW. The storage device 31 may be connected to the server 30 via the network NW.

[0157] Each step of the above information processing can be executed by either the client device 10 or the server 30. For example, if the client device 10 is capable of executing all the steps of the above-mentioned information processing, the client device 10 functions as an information processing device operating in a stand-alone manner without transmitting a request to the server 30 .

[0158] Although the embodiment of the present invention has been described in detail above, the scope of the present invention is not limited to the above embodiment. Furthermore, the above embodiment can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above embodiment and the modified examples can be combined. [Explanation of symbols]

[0159] 1: Information processing system 10: Client device 11:Storage device 12: Processor 13: Input / Output Interface 14: Communication interface 30: Server 31:Storage device 32 : Processor 33: Input / Output Interface 34: Communication interface

Claims

1. A method for determining whether a patient is a recommended patient for whom a face-to-face prescription should be offered based on patient information on the patient who is the subject of medication instruction, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; If a target pharmacy usage rate, which is a ratio of the number of times the target patient uses the target pharmacy to the number of times the target patient uses a pharmacy in a certain period of time, is lower than a predetermined threshold, the target patient is determined to be the recommended patient. Information processing device.

2. The determining means determines that the target patient is the recommended patient when a total number of times the target patient and at least one of the target patient's family members use a pharmacy during a certain period of time is equal to or greater than a predetermined threshold. The information processing device according to claim 1 .

3. A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered based on patient information on the target patient, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; The determining means determines that the target patient is the recommended patient when a total drug price calculation of the target patient and at least one of the target patient's family members for a certain period of time is equal to or greater than a predetermined threshold value. Information processing device.

4. A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered, based on patient information on the target patient, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; The determining means determines that the target patient is the recommended patient when the number of days elapsed since the period in which at least one of the target patient's family members has taken a drug dispensed at a pharmacy other than the target pharmacy is zero or a predetermined threshold or less. Information processing device.

5. The presenting means presents information on drugs dispensed at other pharmacies than the target pharmacy to the recommended patient and at least one of the family members of the target patient.

5. The information processing device according to claim 1.

6. A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered based on patient information on the target patient, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; The determining means determines whether the target patient is the recommended patient based on patient information of the family of the target patient. Information processing device.

7. A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered, based on patient information on the target patient, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; The determining means determines that the target patient is the recommended patient when the number of times that the family of the target patient has used the target pharmacy in a certain period of time is equal to or less than a predetermined threshold. Information processing device.

8. A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered, based on patient information on the target patient, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; The determining means determines whether or not the target patient corresponds to the recommended patient when the target patient's place of residence is within a predetermined distance from the location of the target pharmacy. Information processing device.

9. A means for determining whether or not a target patient who is a target of medication instruction corresponds to a recommended patient for whom a face-to-face prescription should be offered, based on patient information on the target patient, a means for presenting a result of the determination made by the determining means to a user of a target pharmacy that provides the medication instruction; A means for calculating an area prescription score indicating a room for expansion of the demand for the area prescription of the target patient based on the patient information of the target patient, The determining means determines whether or not the target patient is the recommended patient based on the area prescription score, The presenting means presents the judgment result and the surface prescription score. Information processing device.

10. A program for causing a computer to function as any one of the means according to any one of claims 1 to 9.

Images