Information processing device, program, information processing system, and information processing method

Abstract

To provide a user (e.g., pharmacist or administrator) with information useful for proposing open prescription dispensing.SOLUTION: An information processing device is provided, comprising means of determining whether a target patient is a recommended patient to be proposed with open prescription dispensing or not on the basis of patient information on the target patient to be subjected to medication guidance, and means of presenting a determination result of the determination means to a user at a target pharmacy providing the medication guidance.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to an information processing apparatus and a program.

Background Art

[0002] Generally, a pharmacist in charge of providing medication guidance to a patient who has come to a pharmacy provides medication guidance tailored to the patient, taking into account the prescription brought by the patient and the information obtained from the patient.

[0003] Patent Document 1 discloses a technique of obtaining a search target medication search term from medical terms included in medical analysis items, searching for medical information for the search target medication search term stored in a database regarding user medication information and medication-corresponding medical information, obtaining medical information for pharmacists that has been comprehensively processed by a person in charge of a dispensing pharmacy support institution through comprehensive processing of the searched medical information, and providing it to a terminal of the dispensing pharmacy that has received the search request. This can reduce the burden on pharmacists in providing medication guidance.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] From a business perspective, it is preferable for a pharmacy to increase the number of prescription requests. On the other hand, for the prescriptions demanded by the pharmacy, the proportion of prescriptions from medical institutions in the vicinity of the pharmacy (so-called "front-door medical institutions") tends to be high. Therefore, in order to increase the number of prescription requests, it is effective to demand prescriptions from other pharmacies (for example, medical institutions other than front-door medical institutions) among the prescriptions of patients who have come to the pharmacy, so-called "face prescriptions". In order to propose the on-demand prescription to the patient, it is important for the pharmacist in charge of the patient's medication guidance to judge the effectiveness of the on-demand prescription considering the patient information. For this purpose, it is preferable to provide the pharmacist with patient information useful for judging the effectiveness of the on-demand prescription.

[0006] However, the technology of Patent Document 1 can provide information useful for the medication guidance for the patient, but cannot provide information useful for the proposal of the on-demand prescription.

[0007] An object of the present invention is to provide a user (for example, a pharmacist or an administrator) with information useful for the proposal of the on-demand prescription.

Means for Solving the Problem

[0008] One aspect of the present invention is a means for determining whether or not the target patient corresponds to a recommended patient who should propose an on-demand prescription based on patient information regarding the target patient who is the subject of the medication guidance, a means for presenting the determination result of the determination means to a user of the target pharmacy where the medication guidance is implemented, an information processing apparatus.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Embodiments for Carrying Out the Invention

[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 reference numerals are generally given to the same components, and the repeated description thereof will be omitted.

[0011] (1) Configuration of the Information Processing System The configuration of the information processing system will be described. FIG. 1 is a block diagram showing the configuration of the information processing system of the present 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 (for example, the Internet or an intranet) NW.

[0013] The client device 10 is a computer (an example of an "information processing device") that sends requests 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 a response corresponding to the request sent from the client device 10 to the client device 10. The server 30 is, for example, a web server.

[0015] (1-1) Configuration of the client device 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 ROM (Read Only Memory), a RAM (Random Access Memory), and a storage (e.g., a flash memory or a hard disk).

[0018] The program includes, for example, the following programs. · Program of the OS (Operating System) · Program of an application that executes information processing (e.g., a web browser)

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

[0020] The processor 12 is configured to realize the functions of the client device 10 by starting the 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 a user instruction from an input device connected to the client device 10 and 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 communication between the client device 10 and the server 30.

[0023] (1-2) Configuration of the server The configuration of the server 30 will 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 34.

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

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

[0027] The data includes, for example, the following data. · Database referenced in information processing · Execution result of information processing

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

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

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

[0031] (2) Outline of the embodiment The outline of this embodiment will be described. FIG. 3 is an explanatory diagram of the outline of this embodiment.

[0032] As shown in FIG. 3, a user (e.g., a pharmacist) who conducts medication guidance for a patient (hereinafter referred to as the "target patient") who is the subject of medication guidance at the target pharmacy uses the client device 10.

[0033] During the medication guidance, when the user operates the client device 10, the client device 10 sends a determination request to the server 30. The server 30 determines, in response to the determination request from the client device 10, based on the patient information regarding the target patient, whether the target patient is a patient (hereinafter referred to as the "recommended patient") who should propose on-demand face-to-face prescriptions. The server 30 presents to the user whether the target patient is a recommended patient or not via the client device 10 by sending the determination result to the client device 10.

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

[0035] (3) Database The database of the present embodiment will be described. The following database is stored in the storage device 31.

[0036] (3-1) Pharmacy Database The pharmacy database of the present embodiment will be described. FIG. 4 is a diagram showing the data structure of the pharmacy database of the present embodiment.

[0037] The pharmacy information is stored in the pharmacy database of FIG. 4. The pharmacy information is information about the pharmacy. The pharmacy database includes a "Pharmacy ID" field, a "Pharmacy Name" field, a "Corporate ID" field, a "Corporate Name" field, and a "Location" field. Each field is associated with each other.

[0038] Pharmacy identification information is stored in the "Pharmacy ID" field. The pharmacy identification information is information for identifying the pharmacy.

[0039] Pharmacy name information is stored in the "Pharmacy Name" field. The pharmacy name information is information about the pharmacy name.

[0040] Corporate identification information is stored in the "Corporate ID" field. The corporate identification information is information for identifying at least one of the corporation operating the pharmacy and a group composed of a plurality of corporations.

[0041] Corporate name information is stored in the "Corporate Name" field. The corporate name information is information about the corporate name.

[0042] The "Location" field stores location information. The location information is information regarding the address of the pharmacy's location.

[0043] (3-2) Patient Database The patient database of this embodiment will be described. FIG. 5 is a diagram showing the data structure of the patient database of this embodiment.

[0044] The patient database in FIG. 5 stores patient information. The patient information is information regarding the patient. The patient database includes a "Patient ID" field, a "Patient Name" field, a "Patient Attribute" field, a "Residence" field, and a "Family ID" field. Each field is associated with each other. The patient database is associated with pharmacy identification information.

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

[0046] The "Patient Name" field stores patient name information. The patient name information is information regarding the patient name.

[0047] The "Patient Attribute" field stores patient attribute information. The patient attribute information is information regarding the patient's attributes. The "Patient Attribute" field includes a "Gender" field and an "Age" field.

[0048] The "Gender" field stores gender information. The gender information is information regarding the patient's gender.

[0049] The "Age" field stores age information. The age information is information regarding the patient's age.

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

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

[0052] (3-3) Pharmacy Utilization History Database The pharmacy utilization history database of this embodiment will be described. FIG. 6 is a diagram showing the data structure of the pharmacy utilization history database of this embodiment.

[0053] The pharmacy utilization history database in FIG. 6 stores pharmacy utilization history information. The pharmacy utilization history information is information regarding the patient's pharmacy utilization history. The pharmacy utilization history information is, for example, information recorded in an electronic medicine notebook. The patient database includes a "pharmacy utilization history ID" field, a "timestamp" field, a "prescribing medical institution name" field, a "utilized pharmacy" field, a "dispensed medicine" field, a "treatment period" field, and a "total medicine price" field. Each field is associated with each other. The pharmacy utilization history database is associated with patient identification information.

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

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

[0056] In the "Prescribing Medical Institution Name" field, prescribing medical institution name information is stored. The prescribing medical institution name information is information regarding the name of the medical institution that issued the prescription.

[0057] In the "Pharmacy Used" field, pharmacy used information is stored. The pharmacy used information is information for identifying the pharmacy used by the patient. The pharmacy used information is information regarding pharmacy identification information or the name of the pharmacy.

[0058] In the "Dispensed Medicine" field, dispensed medicine information is stored. The dispensed medicine information is information regarding the dispensed medicine provided to the patient. The dispensed medicine information is, for example, information for identifying the dispensed medicine or information regarding the name of the dispensed medicine.

[0059] In the "Taking Period" field, taking period information is stored. The taking period information is information regarding the taking period for each dispensed medicine (for example, the period from the date indicated by the time stamp (hereinafter referred to as the "dispensing date") to the date obtained by adding the prescribed number of days to the dispensing date).

[0060] In the "Total Medicine Price" field, total medicine price information is stored. The total medicine price information is information regarding the total value of the medicine prices of the medicines dispensed to the patient on a certain dispensing date.

[0061] (4) Information Processing The information processing of this embodiment will be described. FIG. 7 is a sequence diagram of the information processing of this embodiment. 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 guidance to the target patient who has come to the target pharmacy. The trigger for the process in FIG. 7 is, for example, that the client device 10 logs in to the 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 the 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 a patient database (FIG. 5) associated with the pharmacy identification information used for login, and receives a 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 specified as the patient identification information (hereinafter referred to as "target patient identification information") of the patient to be the target of the recommended patient determination (hereinafter referred to as the "target patient").

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

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

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

[0069] A first example of step S130 will be described. The processor 32 refers to the pharmacy utilization history database (Figure 6) associated with the target patient identification information included in the prescription request data, and calculates the total number of times the target patient has visited a pharmacy over a certain period (for example, three months back from the execution date and time of step S130), that is, the total number of times the target pharmacy and non-target pharmacies have been visited, and the number of times the target patient has visited the target pharmacy. The 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 has been visited to the number of times the pharmacy has been visited by the target patient over a certain period. (Equation 1) Target pharmacy utilization rate = Number of times the target pharmacy has been visited / Total number of times the pharmacy has been visited When the target pharmacy utilization rate is less than or equal to a predetermined threshold, the processor 32 determines that the target patient is a recommended patient. That is, the lower the target pharmacy utilization rate, the higher the room for using the target pharmacy, which means that it is recommended to propose the demand for face prescriptions.

[0070] Describe the second example of step S130. The second example of step S130 is an example combined with the first example of step S130. The processor 32 refers to the pharmacy utilization history database (Figure 6) associated with the target patient identification information included in the prescription request data, and calculates the total number of times the target patient has visited a pharmacy over a certain period (for example, three months back from the execution date and time of step S130). When the target pharmacy utilization rate is less than or equal to a predetermined threshold and the total number of visits is greater than or equal to a predetermined threshold, the processor 32 determines that the target patient is a recommended patient. That is, the lower the target pharmacy utilization rate and the higher the total number of visits, the higher the room for using the target pharmacy, which means that it is recommended to propose the demand for face prescriptions.

[0071] Describe the third example of step S130. The processor 32 refers to the pharmacy usage history database (Figure 6) associated with the target patient identification information included in the face prescription request data, and identifies the total drug price information of the target patient over a certain period (for example, three months back from the execution date and time of step S130). When the total drug price is equal to or higher than a predetermined threshold, the processor 32 determines that the target patient is a recommended patient. That is, the higher the total drug price, the more recommended it is to propose the demand for face prescriptions.

[0072] Explain the fourth example of step S130. The processor 32 refers to the pharmacy usage history database (Figure 6) associated with the target patient identification information included in the face prescription request data, and calculates the number of days elapsed from the dosing period. The number of days elapsed is the difference between the end date of the dosing period of the target patient and the execution date and time of step S130. When the execution date and time of step S130 is included in the dosing period, the number of days elapsed is 0. When the number of days elapsed is zero or less than or equal to a predetermined threshold, the processor 32 determines that the target patient is a recommended patient. That is, the fewer the number of days elapsed, the more recommended it is to propose the demand for face prescriptions.

[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 refers to the patient database (Figure 5) to identify the residence information associated with the target patient identification information. The processor 32 refers to the pharmacy database (Figure 4) to identify the location information associated with the target pharmacy identification information. The processor 32 calculates the distance between the residence of the target patient and the location of the target pharmacy from the residence information and the location information. The processor 32 determines whether the distance is less than or equal to a predetermined distance (that is, the residence of the target patient is in the vicinity of the target pharmacy).

[0075] After step S131, the server 30 executes a face prescription response (S132). Specifically, the processor 32 transmits face prescription response data to the client device 10. The face prescription response data includes, for example, the following information. · Patient identification information of the target patient · Patient name information of the target patient · Patient attribute information of the target patient (gender information and age information) · Residence information of the target patient · Pharmacy usage history information of the target patient (for example, information regarding the 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 the distance determination obtained in step S131

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

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

[0078] In the display object A111, the patient identification information, patient name information, patient attribute information, and residence information of the target patient are displayed.

[0079] In the display object A112, a message according to the determination result is displayed.

[0080] The operation object B111 is an object that receives a user instruction for presenting detailed information useful for the on-demand proposal of 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 the screen P12 (FIG. 8) on the display.

[0083] On the screen P12, detailed information of the target patient is displayed. The detailed information includes, for example, the following information. · Name of the prescribing medical institution that issued the prescription for the drug dispensed at another institution · Name of the doctor who issued the prescription · Name of the other institution · Dispensing date of the drug · Prescription days of the drug · Name of the drug · Dosage of the drug

[0084] Based on the information displayed on the screen P12, the user proposes the on-site prescription demand to the target patient.

[0085] (5) Parentheses in this embodiment According to this embodiment, a recommended patient for whom an on-site prescription demand should be proposed is determined based on the patient information of the target patient. As a result, the user can propose the on-site prescription demand to an appropriate patient among the target patients. As a result, the target pharmacy can increase the opportunity to handle prescriptions.

[0086] According to this embodiment, a patient with a target pharmacy utilization rate lower than a predetermined threshold may be determined as a recommended patient. As a result, the user can be made to recognize a patient with a relatively low target pharmacy utilization rate (that is, a large margin for using the target pharmacy) as a recommended patient. As a result, the target pharmacy can increase the opportunity to handle prescriptions.

[0087] According to this embodiment, a patient with a total utilization count of the target pharmacy equal to or more than a predetermined threshold may be determined as a recommended patient. As a result, the user can be made to recognize a patient with a relatively high total utilization count (that is, a large opportunity to use the pharmacy) as a recommended patient. As a result, the target pharmacy can increase the opportunity to handle prescriptions.

[0088] According to this embodiment, a patient whose total drug price for the target patient is equal to or higher than a predetermined threshold value may be determined as a recommended patient. Thereby, the user can be made to recognize a patient with a relatively high total drug price (that is, a large amount of money paid 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 whose number of days elapsed from the administration period of the target patient is zero or equal to or less than a predetermined threshold value may be determined as a recommended patient. Thereby, the user can be made to recognize a patient with a small number of days elapsed (that is, a high possibility of the next administration opportunity) as a recommended patient. As a result, the target pharmacy can increase the opportunity to handle prescriptions.

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

[0091] (6-1) Modification 1 Modification 1 will be described. Modification 1 is an example of determining whether or not the patient is a recommended patient based on the patient information of the family of the target patient. The same description as above will be omitted.

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

[0093] Similar to FIG. 7, the client device 10 executes reception of a user instruction (S110) to a face prescription request (S111).

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

[0095] After step S310, the server 30 executes distance determination (S131) to face prescription response (S312) as shown in Figure 7.

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

[0097] On the screen P13, the detailed information of the family of the target patient is displayed. The detailed information includes, for example, the following information. · The name of the prescribing medical institution that issued the prescription form for the drug dispensed at another pharmacy · The name of the doctor who issued the prescription form · The name of the other pharmacy · The dispensing date of the drug · The number of days of the prescription for the drug · The name of the drug · The dosage of the drug

[0098] The user can view the information displayed on the screen P13 and propose the need for a face-to-face prescription for the target patient to the appropriate patient among the target patients.

[0099] (6-1-2) Parentheses According to Modification Example 1, based on the patient information of the family of the target patient, a recommended patient for whom the need for a face-to-face prescription should be proposed is determined. As a result, the user can propose the need for a face-to-face prescription to the appropriate patient among the target patients. As a result, the target pharmacy can increase the opportunity to handle prescription forms.

[0100] (6-2) Modification Example 2 Describe Modification Example 2. Modification Example 2 is an example of calculating a facial prescription score. The facial prescription score is an index indicating the degree of room for demand expansion by obtaining the demand of the facial prescription for the target patient. The same explanation as above is omitted.

[0101] (6-2-1) Patient Database Describe the patient database of Modification Example 2. FIG. 9 is a diagram showing the data structure of the patient database of Modification Example 2.

[0102] Patient information is stored in the patient database of FIG. 9. 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 "Facial Prescription Score" field. Each field is associated with each other. The patient database is associated with pharmacy identification information.

[0103] The "Patient ID" field, "Patient Name" field, "Patient Attribute" field, "Residence" field, and "Family ID" field are the same as those in FIG. 5.

[0104] The "Facial Prescription Score" field stores the facial prescription score. The facial prescription score is an index indicating the room for expansion of the demand for the patient's facial prescription.

[0105] (6-2-2) Information Processing Describe the information processing of Modification Example 2. FIG. 10 is a sequence diagram of the information processing of Modification Example 2. FIG. 11 is a diagram showing an example of a screen displayed in the information processing of FIG. 10.

[0106] In the example of FIG. 10, the user of the target pharmacy is a pharmacist who provides medication guidance to the target patient who has come to the target pharmacy. The trigger for the process in FIG. 10 is, for example, that the client device 10 logs in to the service provided by the server 30 using the pharmacy identification information of the target pharmacy.

[0107] Similar to FIG. 7, the client device 10 executes reception of user instructions (S110) to a face prescription request (S111).

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

[0109] Describe the first example of step S230. Similar to the first example of step S130, the processor 32 calculates the utilization rate of the target pharmacy for the target patient. The processor 32 calculates a face prescription score corresponding to the utilization rate of the target pharmacy by providing the utilization rate of the target pharmacy to the face prescription model. The face prescription model is designed such that the lower the utilization rate of the target pharmacy, the higher the face prescription score. That is, the lower the utilization rate of the target pharmacy, the higher the room for expanding the demand for face prescriptions.

[0110] Describe the second example of step S230. The second example of step S230 is an example combined with the first example of step S230. Similar to the second example of step S130, the processor 32 calculates the total number of times the pharmacy of the target patient is used. The processor 32 calculates a face prescription score corresponding to the combination of the utilization rate of the target pharmacy and the total number of times of use by providing the utilization rate of the target pharmacy and the total number of times of use to the face prescription model. The face prescription model is designed such that the lower the utilization rate of the target pharmacy and the higher the total number of times of use, the higher the face prescription score. That is, the lower the utilization rate of the target pharmacy and the higher the total number of times of use, the higher the room for expanding the face prescription.

[0111] Describe the third example of step S230. Similar to the third example of step S130, the processor 32 identifies the total drug price information of the target patient. The processor 32 calculates a face prescription score according to the total drug price information by providing the total drug price information to the face prescription model. The face prescription model is designed such that the higher the total drug price, the higher the face prescription score. That is, the higher the total drug price, the higher the room for expansion of the face prescription.

[0112] A fourth example of step S230 will be described. The processor 32 calculates the number of days elapsed from the dosing period in the same manner as in the fourth example of step S130. The processor 32 calculates a face prescription score according to the number of days elapsed by providing the number of days elapsed to the face prescription model. The face prescription model is designed such that the fewer the number of days elapsed, the higher the face prescription score. That is, the fewer the number of days elapsed, the higher the room for expansion of the on-demand face prescription.

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

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

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

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

[0117] After step S131, the server 30 executes a face prescription response (S233). Specifically, the processor 32 transmits the face prescription response data to the client device 10. The face prescription response data includes, for example, the following information. · Patient identification information of the target patient · Patient name information of the target patient · Patient attribute information of the target patient (gender information and age information) · Residence information of the target patient · Pharmacy utilization history information of the target patient (for example, information regarding the utilization history of pharmacies other than the target pharmacy (hereinafter referred to as "other pharmacies")) · The face prescription score obtained in step S230 · A message according to the face prescription score · The result of the distance determination obtained in step S131

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

[0119] On the screen P20, the detailed information of the target patient is displayed. The detailed information includes, for example, the following information. · The name of the prescribing medical institution that issued the prescription form for the drug dispensed at other pharmacies · The name of the doctor who issued the prescription form · The name of the other pharmacy · The dispensing date of the drug · The face prescription score · A message according to the face prescription score · The name of the drug · The dosage of the drug

[0120] (6-2-3) Parentheses According to Modification Example 2, a face prescription score based on the patient information of the target patient is presented to the user. As a result, the user can be made aware of the room for expansion of the demand for the face prescription of the target patient. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0121] In addition, in Modification Example 2, not only the target patient but also, in the same manner as in Modification Example 1, the face prescription score of the family of the target patient may be calculated based on the patient information of the family of the target patient.

[0122] (6-3) Modification Example 3 Modification Example 3 will be described. Modification Example 3 is an example in which the calculation (S230) of the face prescription score is executed based on the number of family members' patient information. The same explanation as above will be omitted.

[0123] (6-3-1) Information Processing The information processing of Modification Example 3 will be described.

[0124] In step S230 (FIG. 10), the processor 32 refers to the patient database (FIG. 5) and specifies the number of family member identification information associated with the target patient identification information included in the face prescription request data (that is, the number of family members of the target patient). The processor 32 calculates a face prescription score corresponding to the number of family members by giving the number of family members to the face prescription model. The face prescription model is designed such that the face prescription score becomes higher as the number of family members increases. That is, it means that the proposal of the demand for the face prescription is recommended more as the number of family members of the patient increases.

[0125] (6-3-2) Parentheses According to Modification Example 3, a face prescription score based on the number of family members may be presented to the user. As a result, the user can be made to recognize a patient with a large number of family members (that is, a large number of families who may use the target pharmacy) as a patient for whom the face prescription is recommended. As a result, the target pharmacy can increase the opportunities to handle prescriptions.

[0126] (6-4) Modification Example 4 Describe Modification Example 4. Modification Example 4 is an example of executing the calculation of the face prescription score (S230) based on family information. The same description as above is omitted.

[0127] (6-4-1) Information Processing Describe the information processing of Modification Example 4.

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

[0129] The first example of the face prescription model in Modification Example 4 is designed such that the higher the target pharmacy utilization rate of the family, the higher the face prescription score. That is, the higher the target pharmacy utilization rate of the family, the higher the room for expansion of the demand for the face prescription of the target patient.

[0130] The second example of the face prescription model in Modification Example 4 is designed such that the lower the target pharmacy utilization rate of the family, the higher the face prescription score. That is, the lower the target pharmacy utilization rate of the family, the higher the room for expansion of the demand for the face prescription of the target patient including the family.

[0131] (6-4-2) Parentheses According to Modification Example 4, the face prescription score based on the target pharmacy utilization rate of the family may be presented to the user.

[0132] In the first example of the face prescription model of Modification Example 4, it is possible to make the user recognize the room for expansion of the demand for face prescriptions of patients who have a family with a high utilization rate of the target pharmacy (that is, a family that uses the target pharmacy as a regular pharmacy). As a result, the target pharmacy can increase the opportunity to handle prescriptions.

[0133] In the second example of the face prescription model of Modification Example 4, it is possible to make the user recognize the room for expansion of the demand for face prescriptions of patients who have a family with a low utilization rate of the target pharmacy (that is, a family with a high room for using the target pharmacy). As a result, the target pharmacy can increase the opportunity to handle prescriptions.

[0134] (6-5) Modification Example 5 Modification Example 5 will be described. Modification Example 5 is an example presenting the room for expansion of the demand for multiple pharmacy face prescriptions. The same explanation as above will be omitted.

[0135] (6-5-1) Outline of Modification Example 5 The outline of Modification Example 5 will be described. FIG. 12 is an explanatory diagram of the outline of Modification Example 5.

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

[0137] From the client devices 10 of each pharmacy PH1 to PH2, face prescription scores of a plurality of patients are transmitted to the server 30. As a result, face prescription scores for each pharmacy are accumulated in the server 30.

[0138] The server 30 transmits the face 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 face prescription score for each pharmacy transmitted from the server 30 to the administrator user.

[0140] The manager user can recognize the potential for expanding the demand for face prescriptions for each pharmacy by looking at the face prescription scores presented by the client device 10.

[0141] (6-5-2) Pharmacy Database The pharmacy database of Modification 5 will be described. FIG. 13 is a diagram showing the data structure of the pharmacy database of Modification 5.

[0142] The pharmacy database in FIG. 13 stores pharmacy information. The pharmacy database includes a "Pharmacy ID" field, a "Pharmacy Name" field, a "Corporate ID" field, a "Corporate Name" field, a "Location" field, and a "Pharmacy Face Prescription Score" field. Each field is associated with each other.

[0143] The "Pharmacy ID" field, "Pharmacy Name" field, "Corporate ID" field, "Corporate Name" field, and "Location" field are the same as in FIG. 4.

[0144] The "Pharmacy Face Prescription Score" field stores the pharmacy face prescription score. The pharmacy face prescription score is the face prescription score for each pharmacy (that is, an indicator showing the potential for expanding the demand for face prescriptions at the pharmacy level). The pharmacy face prescription score is, for example, any of the following. · The total value of the pharmacy face prescription scores stored in the "Face Prescription Score" field of the patient database (FIG. 9) associated with the pharmacy identification information · The average value of the said pharmacy face prescription score

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

[0146] In the example of FIG. 14, the user of the client device 10 is the manager user. The trigger for the process in FIG. 14 is, for example, that the client device 10 logs in to the service provided by the server 30 using the corporate identification information.

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

[0148] The screen P15 includes the 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 pharmacy management request data to the server 30. The pharmacy management request data includes, for example, the following information. · Corporate identification information used for login (hereinafter referred to as "target corporate identification information")

[0150] After step S311, the server 30 executes identification of a pharmacy prescription score (S330). Specifically, the processor 32 refers to the pharmacy database (FIG. 13) and identifies 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 pharmacy management response data to the client device 10. The pharmacy management response data includes, for example, the following information. · 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 the screen P31 (FIG. 15) on the display.

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

[0154] (6-5-4) Parentheses According to Modification 5, the face prescription score for each pharmacy is presented to the administrator user. As a result, the administrator user can be made aware of the room for expansion of the demand for face prescriptions for each pharmacy. As a result, the administrator user can make a plan to expand the demand for face prescriptions according to the room for expansion of the demand for face prescriptions for each pharmacy.

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

[0156] The storage device 11 may be connected to the client device 10 via the 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, when the client device 10 can execute all the steps of the above information processing, the client device 10 functions as a stand-alone information processing device without transmitting a request to the server 30.

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

Explanation of reference numerals

[0159] 1: Information Processing System 10: Client Device 11: Memory Device 12: Processor 13: Input / Output Interface 14: Communication Interface 30: Server 31: Memory Device 32: Processor 33: Input / Output Interface 34: Communication Interface

Claims

1. 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; 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 recited in any one of claims 1 to 9.

Images