Prescription support system, method for supporting prescription, and program

Abstract

To present a highly reliable prescription set.SOLUTION: A prescription support system includes: a diagnosis information acquisition unit for acquiring the attribute, the symptom, and the disease name of a patient; and a prescribed medicine presentation unit for presenting a prescribed medicine which corresponds to the attribute, the symptom, and the disease name of a patient to a doctor with reference to a prescribed medicine database in which the attribute of the patient, the symptom and the disease name of the patient, and the prescribed medicine of the patient prescribed in the past with reference to the symptom and the disease name, and the attribute of receipt data are accumulated in relation to one another on the basis of the receipt data.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a prescription support system, a prescription support method, and a program. [Background technology]

[0002] In the above technical field, Patent Document 1 discloses a technology in which an electronic medical record server stores electronic medical record information from multiple medical institutions and statistical information associating symptoms with prescription drugs, and when symptoms are input from the electronic medical record input screen, associated prescription drugs are searched for and displayed as prescription drug reference information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-081528 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the technology described in the above document associates symptoms with prescribed drugs based on electronic medical record information, and since the quality of the electronic medical record information varies depending on the doctor and dispensing is not inspected, it is not possible to provide reliable reference information for prescription drugs.

[0005] An object of the present invention is to provide a technique for solving the above-mentioned problems. [Means for solving the problem]

[0006] In order to achieve the above object, the prescription support system according to the present invention comprises: a receipt data acquisition unit that acquires receipt data including medical receipts and prescription receipts; A database that links and accumulates a patient's attributes, the patient's symptoms or disease names, and the patient's prescription drug sets that have been prescribed according to the symptoms or disease names based on the receipt data; a medical examination information acquisition unit that acquires attributes of a patient and symptoms or disease names input by a doctor; a prescription drug set presentation unit that refers to the database and presents to the doctor at least one prescription drug set corresponding to the attributes and symptoms or disease name of the patient acquired by the examination information acquisition unit; Equipped with.

[0007] In order to achieve the above object, a prescription support method according to the present invention comprises: a medical examination information acquisition step in which a medical examination information acquisition unit acquires attributes and symptoms or disease names of a patient; a prescription drug presentation step in which a prescription drug presentation unit refers to a prescription drug database that links and accumulates a patient's attributes, the patient's symptoms or disease name, prescription drugs prescribed for the patient in the past according to the symptoms or disease name, and attributes of the receipt data based on the receipt data, and presents to a doctor prescription drugs corresponding to the patient's attributes and symptoms or disease name; A prescription support method including:

[0008] In order to achieve the above object, an application program according to the present invention comprises: A medical examination information acquisition step of acquiring attributes and symptoms or disease names of patients; a prescription drug presentation step of referring to a prescription drug database that links and accumulates a patient's attributes, the patient's symptoms or disease name, prescription drugs prescribed to the patient in the past according to the symptoms or disease name, and attributes of the receipt data based on the receipt data, and presenting to a doctor prescription drugs corresponding to the patient's attributes and symptoms or disease name; to be executed by the computer. Effect of the Invention

[0009] According to the present invention, a highly reliable set of prescription drugs can be presented. [Brief description of the drawings]

[0010] [Figure 1] 1 is a block diagram showing the configuration of a prescription support system according to a first embodiment. FIG. [Figure 2A] FIG. 11 is a diagram showing a display screen of a communication terminal in the prescription support system according to the second embodiment. [Figure 2B] FIG. 11 is a diagram showing a display screen of a communication terminal in the prescription support system according to the second embodiment. [Figure 2C] FIG. 11 is a diagram showing a display screen of a communication terminal in the prescription support system according to the second embodiment. [Figure 3A] FIG. 1 is a diagram showing the configuration of a prescription support system according to a second embodiment. [Figure 3B] FIG. 11 is a block diagram showing the functional configuration of a prescription support system according to a second embodiment. [Figure 4] FIG. 11 is a sequence diagram showing an operation procedure of the prescription support system according to the second embodiment. [Diagram 5] FIG. 11 is a block diagram showing a functional configuration of an information processing device serving as a prescription medicine set extraction unit according to the second embodiment. [Figure 6A] FIG. 11 is a diagram showing data processed in a prescription medicine set extraction unit according to the second embodiment. [Figure 6B] FIG. 11 is a diagram showing the configuration of medical receipt data according to the second embodiment. [Figure 6C] FIG. 11 is a diagram showing the configuration of a search database according to the second embodiment. [Figure 6D] FIG. 11 is a diagram showing major classifications / minor classifications for adults according to the second embodiment. [Figure 6E] FIG. 11 is a diagram showing major classifications / minor classifications for adults according to the second embodiment. [Figure 6F] FIG. 11 is a diagram showing major classifications / minor classifications for adults according to the second embodiment. [Figure 6G] FIG. 11 is a diagram showing major classifications / minor classifications for adults according to the second embodiment. [Figure 6H] FIG. 11 is a diagram showing major / minor classifications for infants and children according to the second embodiment. [Figure 6I] FIG. 11 is a diagram showing major / minor classifications for infants and children according to the second embodiment. [Figure 6J]FIG. 11 is a diagram showing major / minor classifications for infants and children according to the second embodiment. [Figure 6K] FIG. 11 is a diagram showing major / minor classifications for infants and children according to the second embodiment. [Figure 6L] FIG. 11 is a diagram showing major / minor classifications in gynecology according to the second embodiment. [Figure 6M] FIG. 11 is a diagram showing major / minor classifications in gynecology according to the second embodiment. [Figure 6N] FIG. 11 is a diagram showing major / minor classifications in gynecology according to the second embodiment. [Figure 6O] FIG. 11 is a diagram showing major / minor classifications in gynecology according to the second embodiment. [Figure 7] 13 is a flowchart showing a processing procedure of a prescription medicine set extraction unit according to the second embodiment. [Figure 8] FIG. 11 is a block diagram showing a functional configuration of an information processing device serving as a dispensing information search server according to the second embodiment. [Figure 9] FIG. 11 is a diagram showing the configuration of a search result acquisition table according to the second embodiment. [Figure 10] 13 is a flowchart showing a processing procedure of a dispensing information search server according to the second embodiment. [Figure 11] FIG. 11 is a block diagram showing a functional configuration of an information processing device serving as a prescription information providing server according to a second embodiment. [Figure 12] FIG. 11 is a diagram showing a configuration of a prescription information screen generating table according to the second embodiment. [Figure 13] 10 is a flowchart showing a processing procedure of a prescription information providing server according to the second embodiment. [Figure 14] FIG. 11 is a block diagram showing a functional configuration of a communication terminal according to a second embodiment. [Figure 15] 10 is a flowchart showing a processing procedure of a communication terminal according to the second embodiment. [Figure 16] FIG. 13 is a diagram showing a search input screen of a communication terminal in the prescription support system according to the third embodiment. [Figure 17]FIG. 11 is a diagram showing the configuration of a search database according to the third embodiment. [Figure 18] FIG. 13 is a block diagram showing a functional configuration of a prescription medicine set extraction unit according to the fourth embodiment. [Figure 19] FIG. 13 is a diagram showing the configuration of a receipt issuer weighting table according to the fourth embodiment. [Figure 20] FIG. 13 is a diagram showing a search result display screen of a communication terminal in the prescription support system according to the fifth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. However, the components described in the following embodiment are merely examples, and are not intended to limit the technical scope of the present invention. In this specification, a drug set dispensed at a pharmacy based on receipt data is referred to as a dispensed drug set, and a drug set presented to support a doctor is referred to as a prescribed drug set.

[0012] [First embodiment] A prescription support system 100 according to a first embodiment of the present invention will be described with reference to Fig. 1. The prescription support system 100 is a system that supports doctors in issuing prescriptions.

[0013] As shown in FIG. 1, the prescription support system 100 includes a medical receipt data acquisition unit 101, a database 102, a medical examination information acquisition unit 103, and a prescription drug set presentation unit 104. The medical receipt data acquisition unit 101 acquires medical receipt data including medical receipts and prescription drug sets. The database 102 links and accumulates a patient's attributes 121, a patient's symptoms or disease name 122, and a patient's prescription drug set 123 that is dispensed according to the symptoms or disease name 122 based on the medical receipt data. The medical examination information acquisition unit 103 acquires a patient's attributes and symptoms or disease name input by a doctor 110. The prescription drug set presentation unit 104 refers to the database 102 and presents to the doctor 110 at least one prescription drug set 143 that corresponds to the patient's attributes 141 and symptoms or disease name 142 acquired by the medical examination information acquisition unit 103.

[0014] According to this embodiment, since prescription data including medical prescriptions and prescriptions for prescriptions are used, there is no variation in the quality of the information, and the prescriptions have been checked, making it possible to present a highly reliable set of prescription drugs.

[0015] [Second embodiment] Next, a prescription support system according to a second embodiment of the present invention will be described. In the prescription support system according to this embodiment, when a patient's attributes, disease, or symptoms are input as search conditions based on receipt data including medical receipts and dispensing receipts, examples of prescription drug sets that serve as references for prescriptions issued by doctors are displayed. When there are multiple prescription drug sets, examples are displayed in order of frequency of appearance. In addition, when a doctor specifies drugs to be included or excluded in the search results, a prescription drug set corresponding to the specification is presented.

[0016] <Prescription support system> The configuration and operation of the prescription support system of this embodiment will be described below with reference to FIGS. 2A to 4.

[0017] (Example of a communication device display screen) FIG. 2A is a diagram showing a display screen of the communication terminal 210 in the prescription support system according to this embodiment.

[0018] FIG. 2A shows a prescription search screen 211 on which a doctor requests a search for a prescription drug set based on the attributes of a patient or the patient's symptoms or disease name, and a search result screen 212 on which the prescription drug sets of the search results are displayed.

[0019] In the prescription search screen 211, for example, "patient generation" is input as a patient attribute. In addition, in the prescription search screen 211, for example, hierarchical "major categories of diseases and symptoms" and "minor categories" are input as the patient's symptoms or disease names. Here, the "major categories" and "minor categories" are classifications according to a classification table newly generated in this embodiment shown in the following Figs. 6D to 6O. With such classification, it is possible to input the symptoms of the patient that are not biased by the doctor as a search condition. Furthermore, in the prescription search screen 211 of Fig. 2A, the doctor can specify the medicine to be included in the search result. In addition, it is also possible to specify the medicine that should not be included in the search result based on the patient's allergies, medical history, etc. It is noted that the input conditions in the prescription search screen 211 are not limited to Fig. 2A.

[0020] A summary of the search criteria, the search results, and the prescription drug sets are displayed on the search result screen 212. The search result screen 212 of FIG. 2A shows that there were 32 search results, and displays an overview of each searched prescription drug set in order of frequency.

[0021] 2B is a diagram showing a display screen 213 of detailed contents of each prescription drug set, which is a search result of the communication terminal 210 in the prescription support system according to this embodiment. The display screen 213 presents combinations of the same prescription drug set, but with different dosages and prescription dates.

[0022] Clicking on each prescription drug on the display screen 213 displays more detailed pharmaceutical information for that prescription drug. In addition, in the prescription drug set by prescription time shown in the third embodiment (FIG. 16), the usage and dosage of the prescription drug and the number of prescription days in FIG. 2B are taken into consideration. Furthermore, as a search result, information such as an indication master linked to an external master (such as a medical information center) can also be displayed.

[0023] 2C is a diagram showing display screens 214 and 215 of the communication terminal 210 which feed back the doctor's evaluation of each prescription drug set that is the search result. Display screen 214 is a screen on which the doctor has selected "Dood!" to provide feedback of a good evaluation. On the other hand, display screen 215 is a screen on which the doctor has selected "Bad!" to provide feedback of a bad evaluation. This fed back doctor's evaluation result is reflected in subsequent searches for prescription drug sets by changing the weighting.

[0024] (System Configuration) FIG. 3A is a diagram showing the configuration of a prescription support system 300 according to this embodiment.

[0025] The prescription support system 300 includes a general-purpose communication terminal 210 used by doctors 381 to 38n, and a prescription information providing server 330, which are connected to the network 390. The prescription support system 300 also includes a prescription information search server 320 and a payment processing server 370, which are connected to the prescription information providing server 330. Any of the prescription information providing server 330, the prescription information search server 320, and the payment processing server 370 may be realized as an integrated server. The prescription support system 300 also includes a prescription drug set extraction unit 340, a DWH (data warehouse) 350, and an external master 360, which are connected to the network 390 or are connected without the network 390. The DWH 350 includes the Ministry of Health, Labor and Welfare, medical institutions, pharmacies, and the like. The external master 360 includes a medical information center, and the like.

[0026] The prescription information providing server 330 presents to the communication terminal 210, as a reference, prescription drug sets by other doctors that have been searched for by the prescription information search server 320 in the past, according to the search conditions input from the communication terminal 210. The prescription information search server 320 searches for prescription drug sets from the search database generated by the prescription drug set extraction unit 340, using the patient's attributes, symptoms, or disease name as search keys, based on the data from the DWH 350 and the external master 360. The payment processing server 370 also settles the service fee to the communication terminal 210.

[0027] (Functional configuration) Fig. 3B is a block diagram showing the functional configuration of prescription support system 300 according to this embodiment. In Fig. 3B, the same components as those in Fig. 3A are denoted by the same reference numerals. In Fig. 3B, doctors 381 to 38n in Fig. 3A are represented as doctor 380.

[0028] A prescription support application (prescription support app in the figure) 310 is installed in the communication terminal 210. The prescription information providing server 330 has a member database for registering doctors 380, an application record for storing search applications for prescription drug sets from the communication terminal 210, a search result for holding search results, and a notice list for holding notices to the doctor 380. The prescription information providing server 330 has an inquiry function for inquiring about search applications to the dispensing information search server 320.

[0029] In addition, the dispensing information search server 320 has a search database 321 and is equipped with a response function for responding to a search request inquiry from the prescription information providing server 330, and a search engine for sending a search code according to search conditions to the search database 321, obtaining the search results, and sending a response to the prescription information providing server 330.

[0030] The contents of the search database 321 are extracted and generated by a generation- and disease-specific prescription drug set extraction unit 340 based on a medical product master 351 acquired from a DWH 350, prescription data 352 including medical prescriptions and prescription prescriptions, and an indication master 361 acquired from an external master 360.

[0031] (Operation sequence) FIG. 4 is a sequence diagram showing the operation procedure of the prescription support system 300 according to this embodiment.

[0032] In step S401, the prescription drug set extraction unit 340 receives the prescription data and the drug master from the DWH 350. In step S403, the prescription drug set extraction unit 340 receives the indication master from the external master 360. In step S405, the prescription drug set extraction unit 340 accumulates these medical care data. In step S407, the prescription drug set extraction unit 340 extracts prescription drug sets based on the accumulated data. Note that although FIG. 4 describes extraction of prescription drug sets, in reality, the prescription drug sets are arranged in order of frequency by comparing the occurrence counts of similar prescription drug sets based on the data serving as a search code (key), in this embodiment, the attributes of the patient, symptoms, or disease name. The extraction results of the prescription drug sets are stored in the search database 321. The extracted prescription drug set is sent to the prescription information search server 320, and in step S409, a standardized search code (key) is generated for searching prescription drug sets stored in the search database 321. The generated search code is then stored in the search database 321 so that the prescription drug set can be searched. In step S411, the prescription information providing server 330 generates a prescription search screen for inputting search conditions corresponding to the generated search code.

[0033] Note that Fig. 4 only shows the initial collection of receipt data, drug master data, and indication master data. However, the collection of receipt data, drug master data, and indication master data, especially receipt data, is continuously performed, the search database 321 is updated, and as the amount of referenced receipt data increases, learning is performed to search for more appropriate prescription drug sets.

[0034] In step S421, a prescription support application is started in the communication terminal 210, the prescription information providing server 330, and the dispensing information search server 320. The prescription support application may be configured to be downloaded to the communication terminal 210 and started, or may be configured to be connected via a browser. In step S423, the doctor 380 performs registration for receiving prescription support from the communication terminal 210.

[0035] In step S425, the prescription information providing server 330 outputs the prescription search screen generated in step S411 to the communication terminal 210. In step S427, the prescription search screen is displayed on the communication terminal 210. In step S429, the doctor 380 inputs search conditions to the prescription search screen from the communication terminal 210. The search conditions are sent to the dispensing information search server 320 via the prescription information providing server 330.

[0036] In step S431, the dispensing information search server 320 converts the acquired search conditions into a search code for searching the search database 321 and sets it. Then, in step S433, the dispensing information search server 320 instructs the search database 321 to perform a search process. The search database 321 performs a search using the search code and outputs the search results to the dispensing information search server 320. In this embodiment, the search code corresponds to the patient's attributes and the patient's symptoms or disease name, and the search results are at least one dispensing drug set linked to the patient's attributes and the patient's symptoms or disease name, and if there are multiple search results, they are output with a frequency ranking. The search results are directly fed back to the search database 321, or are fed back from the dispensing drug set extraction unit 340 to the search database 321 as in step S441, and the contents of the search database 321 are updated.

[0037] In step S435, the dispensing information search server 320 returns the dispensing drug set of the search result to the prescription information providing server 330. In step S437, the prescription information providing server 330 generates a screen displaying the prescription drug set of the search result and transmits it to the communication terminal 210. The communication terminal 210 displays the prescription drug set of the received search result. Although not shown, the prescription information providing server 330 selects prescription drug sets including drugs instructed by the doctor 380 to be included from the prescription drug sets of the search result, while omitting prescription drug sets including drugs instructed by the doctor 380 not to be included, and displays them on the communication terminal 210.

[0038] Furthermore, in step S443, when the doctor inputs an evaluation of each prescription drug set in the search results from the communication terminal 210, this is fed back from the prescription drug set extraction unit 340 to the search database 321 as in step S445, and the contents of the search database 321 are updated (see FIG. 2C).

[0039] <Prescription drug set extraction section> Hereinafter, the configuration and operation of an information processing device serving as a prescription drug set extraction unit 340 that generates a search database 321 based on prescription data including medical receptors and prescription drug receptors will be described with reference to Figs. 5 to 7.

[0040] (Functional configuration) FIG. 5 is a block diagram showing the functional configuration of the prescription medicine set extraction unit 340 according to this embodiment.

[0041] The prescription medicine set extraction unit 340 includes an input interface and communication control unit 501, a medical data collection unit 502, and a medical database 503. The prescription medicine set extraction unit 340 also includes an extraction condition storage unit 504, a prescription medicine set reading unit 505, a statistical processing unit 506, and a search data storage instruction unit 507.

[0042] The input interface and communication control unit 501 controls connections for collecting data from the DWH 350 and the external master 360. The medical data collection unit 502 collects drug master data and prescription data from the DWH 350, and indication master data (drug and corresponding disease name data) from the external master 360, via the input interface and communication control unit 501. The medical database 503 accumulates the data collected by the medical data collection unit 502.

[0043] The extraction condition storage unit 504 stores extraction conditions corresponding to the search conditions at the time of search. The prescription drug set reading unit 505 extracts prescription drug sets from the medical care database 503 according to the extraction conditions stored in the extraction condition storage unit 504. The statistical processing unit 506 performs statistical processing on the extracted prescription drug sets. In this embodiment, for example, the occurrence frequency is calculated from the number of occurrences of the same prescription drug sets extracted under similar extraction conditions, and the order is set in descending order of occurrence frequency. The search data storage instruction unit 507 instructs storage in the search database 321 so that prescription drug sets searched for under the search conditions are presented in descending order of occurrence frequency. For example, the extraction condition storage unit 504 stores a classification table of major classifications and minor classifications according to this embodiment, and is added as a search key in the search database 321 by subsequent processing.

[0044] (Data Composition) FIG. 6A is a diagram showing data processed in the prescription medication set extraction unit 340 according to this embodiment.

[0045] The data collected and stored in the medical care database 503 includes receipt data 352 including medical receipts 353 and prescription receipts 354, a medical product master 351, and an indications master 361. The medical receipts 353 include the patient's date of birth, diagnosed illness, prescription information, etc. The prescription receipts 354 include prescription information, dispensed medical products, prescription quantity (corresponding to prescription days), dosage and administration, etc. The medical product master 351 includes the specifications and drug prices for each medical product. The indications master 361 stores the correspondence between existing medical products and indications.

[0046] The prescription drug set search table 622 accumulated in the search database 321 includes patient attributes such as generation, symptoms, prescription drug set information, prescription drug set frequency ranking, dosage and administration, and prescription period.

[0047] 6B is a diagram showing the configuration of the medical receipt data according to this embodiment. The medical receipt data includes a medical receipt 353 and a prescription receipt 354.

[0048] The upper diagram of FIG. 6B shows an example of the format of the medical receipt 353 and an example of data items that can be extracted from the medical receipt 353. For example, the "date of medical treatment" is obtained from the medical treatment date column of the medical receipt 353, the "name (patient ID)", "gender", and "age" are read from the patient column, and the "name of medical institution (facility ID)", "location", "number of hospital beds", and "department" are obtained from the medical institution column. In addition, the "name of injury or illness", "name of suspected illness", "start date of treatment", "actual number of days of treatment", and "outcome" are obtained from the injury or illness column of the medical receipt 353, and the "name of medical product", "dosage", "number of days of administration", "number of administrations", "test items and number of times", "treatment and operation contents", "name and quantity of health care materials", and "treatment category" of the prescription are obtained from the summary column. In this embodiment, "gender" is optional.

[0049] The lower diagram of FIG. 6B shows an example of the format of the dispensing receipt 354 and an example of data items that can be extracted from the dispensing receipt 354. For example, the "dispensing date" can be obtained from the dispensing date column of the dispensing receipt 354, the "name (patient ID)", "gender", and "age" can be obtained from the patient column, the "pharmacy name (facility ID)" and "location" can be obtained from the pharmacy column, and the "medical institution name (facility ID)", "location", and "doctor name" can be obtained from the medical institution column. In addition, the "prescribing doctor number", "prescription date", dispensed "medical product name", "standard", "dosage", "number of administration days / number of prescriptions", and "dosage form / method of use" can be obtained from the prescription column of the dispensing receipt 354. In this embodiment, "gender" is optional.

[0050] The data obtained from the medical receipt 353 and the data obtained from the prescription 354 are collated to link the patient's attributes, the patient's symptoms or disease name, and the prescription drug set.

[0051] (Search Database) 6C is a diagram showing the configuration of the search database 321 according to this embodiment. The search database 321 is a database that accumulates prescription drug sets so that a patient's attributes and the patient's symptoms or disease name are used as search keys, and prescription drug sets sorted by frequency are output as search results.

[0052] The search database 321 stores at least one prescription drug set information 603 in association with a patient's attribute 601 and a patient's symptom or disease name 602. The patient's attribute 601 includes gender and generation, but in this embodiment, "gender" is optional. The generation is, for example, infant / child or adult. Furthermore, gynecology (pregnant woman) is another independent attribute. In addition, by using the major and minor classifications proposed in this embodiment as the patient's symptom or disease name 602, an unbiased database is created by absorbing individual differences due to the doctor in charge of treatment. Note that the attributes are not limited to this example, and the method of dividing the generations is also not limited to this example.

[0053] When multiple pieces of prescription drug set information 603 are included, the order of frequency of appearance 604 is stored. Multiple prescription drugs 605 are stored corresponding to each prescription drug set information 603, and each prescription drug 605 stores usage and dosage 606, number of prescription days 607, and medical product information 608 obtained from the medical product master.

[0054] (Major and minor categories) Figures 6D to 6O are diagrams showing the major and minor categories by generation and gynecology used in this embodiment. Figures 6D to 6G show a table 621 of major and minor categories for adults, Figures 6H to 6K show a table 622 of major and minor categories for infants and children, and Figures 6L to 6O show a table 623 of major and minor categories for gynecology.

[0055] In this embodiment, the major and minor categories are designed to allow searches by symptoms, and the ease of use of searches is improved by allowing searches for the same symptoms (minor categories) within different major categories. In other words, in existing disease classification tables (e.g., ICD10), depending on the symptoms to be searched, some symptoms are better classified in terms of medication, while others are better classified in terms of medication. Therefore, in this embodiment, by having doctors organize the symptoms from their perspective, it is possible to produce a more appropriate prescription drug set.

[0056] (Processing Procedure) 7 is a flowchart showing the processing procedure of the prescription medicine set extraction unit 340 according to this embodiment. This flowchart is executed by the CPU that controls the prescription medicine set extraction unit 340 using the RAM, and realizes the components of the prescription medicine set extraction unit 340 in FIG.

[0057] In step S701, the prescription drug set extraction unit 340 acquires an existing indication master from the external master 360. In step S703, the prescription drug set extraction unit 340 acquires a drug master from the DWH 350. In step S707, the prescription drug set extraction unit 340 initializes search conditions and prescribed drug sets in the search database 321 configured as shown in Fig. 6C from the existing indication master and medical product master.

[0058] The prescription drug set extraction unit 340 acquires the medical receptor from the DWH 350 in step S709, and acquires the prescription drug receptor in step S711. If the medical receptor and prescription drug receptor have already been combined, both receipts are acquired in step S710. In step S713, the prescription drug set extraction unit 340 links the patient's attributes, symptoms or disease names, and prescription drug sets based on the medical receptor and prescription drug receptor. At this time, the major classification and minor classification of this embodiment are used as the symptoms or disease names to improve the search results.

[0059] In step S715, the prescription drug set extraction unit 340 determines whether or not there is a new drug in the prescription drug set extracted from the receipt. If there is a new drug in the prescription drug set, in step S717, the prescription drug set extraction unit 340 acquires information on the new drug from the drug master of the DWH 350. It is also useful to separately collect the prescription history of the new drug and present it to the doctor.

[0060] In step S719, the prescription drug set extraction unit 340 executes statistical processing such as setting a rank based on the frequency of appearance of prescription drug sets under the conditions of similar patient attributes and symptoms or disease names. Then, in step S721, the prescription drug set extraction unit 340 adds prescription drug set information based on newly acquired prescription data to the search database 321 to update it. If there is little prescription data, the reliability of the search database 321 is low, so in step S723, the prescription drug set extraction unit 340 determines whether the prescription data is sufficient. If the accumulation of prescription data is not sufficient, the prescription drug set extraction unit 340 returns to step S709 (S710) and repeats addition and update to the search database 321 until the accumulated prescription data is sufficient and the reliability of the search database 321 becomes high.

[0061] If the accumulation of prescription data is sufficient, in step S725, the prescription set extraction unit 340 enables the search use of the search database 321. In step S727, the prescription drug set extraction unit 340 determines whether to suspend or stop the prescription drug set extraction process, and repeats the processes of steps S709 (S710) to S727 to proceed with learning in the search database 321 unless an instruction to suspend or stop the prescription drug set extraction process is given.

[0062] <Pharmacy information search server> Hereinafter, with reference to Figs. 8 to 10, a configuration and operation of an information processing device serving as a prescription information search server 320 that searches for prescription drug sets based on the attributes of a patient or the symptoms or disease name of a patient will be described.

[0063] (Functional configuration) FIG. 8 is a block diagram showing the functional configuration of the dispensing information search server 320 according to the second embodiment.

[0064] The dispensing information search server 320 includes an application interface (API) 801 , a search condition acquisition unit 802 , a search code (formula) generation unit 803 , a search result acquisition unit 804 , and a search result response unit 805 .

[0065] An application interface (API) 801 controls data exchange with the prescription information providing server 330, which connects to the communication terminal 210 and presents a prescription drug set. A search condition acquiring unit 802 acquires search conditions input from the communication terminal 210 via the prescription information providing server 330. A search code (formula) generating unit 803 generates a search code (formula) capable of searching the search database 321 from the search conditions acquired by the search condition acquiring unit 802.

[0066] The search result acquisition unit 804 has a search result acquisition table 841, acquires the search result from the search database 321 by the search code (expression), and generates a search result to be returned to the prescription information providing server 330. The search result response unit 805 replies to the prescription information providing server 330 with the search result acquired and generated by the search result acquisition unit 804.

[0067] (Search result table) 9 is a diagram showing the configuration of a search result acquisition table 841 according to this embodiment. The search result acquisition table 841 is used by the search result acquisition unit 804 to organize search results acquired from the search database 321 by the search code (formula) into an answer format.

[0068] The search result acquisition table 841 stores prescription drug set information 903, which is associated with the patient's attributes 901 and the patient's symptoms or disease name 902 as search conditions, and which is ranked by frequency rank 904 in the case of multiple search results. Multiple prescription drugs 905 are stored corresponding to each prescription drug set information 903, and each prescription drug 905 stores usage and dosage 906, number of prescription days 907, and medical product information 908 acquired from the medical product master. Note that gender in the patient's attributes 901 is optional.

[0069] (Processing Procedure) 10 is a flowchart showing the processing procedure of the dispensing information search server 320 according to this embodiment. This flowchart is executed by the CPU that controls the dispensing information search server 320 using the RAM, and realizes the components of the dispensing information search server 320 in FIG.

[0070] In step S1001, the dispensing information search server 320 waits for a search request from the prescription information providing server 330. If there is a search request, in step S1003, the dispensing information search server 320 acquires search conditions from the prescription information providing server 330. Then, in step S1005, the dispensing information search server 320 converts the acquired search conditions into a search code (formula) for searching the search database 321.

[0071] In step S1007, the dispensing information search server 320 searches the search database 321 by the search code (formula). In step S1009, the dispensing information search server 320 acquires the search results from the search database 321. In step S1011, the dispensing information search server 320 returns the search results to the prescription information providing server 330. In step S1013, the dispensing information search server 320 determines whether to stop the search process, and if not, repeats the search process of steps S1001 to S1013.

[0072] <Prescription information server> Hereinafter, with reference to Figures 11 to 13, the configuration and operation of an information processing device serving as a prescription information providing server 330 that receives a search request for a prescription drug set from the communication terminal 210, requests a search to the prescription information search server 320, and presents the search results to the communication terminal 210 will be described.

[0073] (Functional configuration) FIG. 11 is a block diagram showing the functional configuration of the prescription information providing server 330 according to this embodiment.

[0074] The prescription information providing server 330 includes a communication control unit 1101, a doctor information acquiring unit 1102, a member database 1103, a doctor authentication unit 1104, and an application interface 1105. The prescription information providing server 330 also includes a search condition acquiring unit 1106, a prescription search screen generating unit 1107, and a prescription search screen transmitting unit 1108. The prescription information providing server 330 also includes a prescription search screen receiving unit 1109, a search condition transmitting unit 1110, a search result acquiring unit 1111, a prescription drug set selection instruction unit 1112, a prescription information screen generating unit 1113, and a prescription information screen transmitting unit 1114.

[0075] The communication control unit 1101 controls communication with the communication terminal 210. The doctor information acquisition unit 1102 acquires information on the doctor who requests the presentation of a prescription drug set from the communication terminal 210 using the communication terminal 210. The member database 1103 registers the acquired doctor information. When a doctor requests the presentation of a prescription drug set, the doctor authentication unit 1104 authenticates the requesting doctor using the member registration information in the member database 1103. The application interface 1105 controls connection with the dispensing information search server 320.

[0076] The search condition acquisition unit 1106 acquires search conditions of the search database 321 from the dispensing information search server 320. The prescription search screen generation unit 1107 generates a prescription search screen for inputting search conditions to be displayed on the communication terminal 210 according to the acquired search conditions. The prescription search screen transmission unit 1108 transmits the prescription search screen to the communication terminal 210 that has started the prescription assistance app. The prescription search screen reception unit 1109 receives the prescription search screen on which the doctor has set search conditions such as the attributes of the patient, the symptoms or disease name of the patient, from the communication terminal 210. The search condition transmission unit 1110 extracts search conditions such as the attributes, symptoms or disease name of the patient from the prescription search screen, and transmits them to the dispensing information search server 320 to request a search for a dispensing drug set.

[0077] The search result acquisition unit 1111 acquires the search result corresponding to the search condition transmitted by the search condition transmission unit 1110 from the dispensing information search server 320. If the prescription search screen received by the prescription search screen receiving unit 1109 contains instruction information to select a prescription drug set to be presented to a doctor from the dispensing drug sets of the search result, the prescription drug set selection instruction unit 1112 instructs the prescription information screen generation unit 1113 to select a prescription drug set. For example, if drugs to be included in the search and drugs not to be included in the results are set on the prescription search screen, the prescription drug set selection instruction unit 1112 deletes prescription drug sets without drugs to be included in the search and prescription drug sets with drugs not to be included in the search from the prescription information screen.

[0078] The prescription information screen generating unit 1113 has a prescription information screen generating table 1131, and generates a prescription information screen from the acquired search results, taking into consideration the instruction of the prescription drug set selection instruction unit 1112. The prescription information screen transmitting unit 1114 transmits the generated prescription information screen to the communication terminal 210 that originated the search.

[0079] (Prescription information screen generation table) Fig. 12 is a diagram showing the configuration of a prescription information screen generation table 1131 according to this embodiment. The prescription information screen generation table 1131 is used by the prescription information screen generation unit 1113 to generate a prescription information screen from the acquired search results. In Fig. 12, the same components as those in Fig. 9 are given the same reference numbers, and duplicated explanations are omitted.

[0080] Prescription information screen generation table 1131 includes table 1210 for generating a screen displaying search conditions, table 1220 for generating a screen displaying a prescription drug set as a search result, and table 1230 for generating a screen displaying detailed information of prescription drugs.

[0081] Table 1210 stores a search condition display image 1211 in association with the search conditions. Table 1220 stores a prescription drug display image 1221 in association with the prescription drug sets of the search results, and stores display availability (o: display, x: non-display) 1222 for each prescription drug set by specifying "drugs to include" as an instruction from the prescription drug set selection instruction unit 1112, and display availability (o: display, x: non-display) 1223 for specifying "drugs not to include" as an instruction from the prescription drug set selection instruction unit 1112. Table 1230 stores a medical product detail display image 1231 based on the medical product information of the prescription drug.

[0082] (Processing Procedure) 13 is a flowchart showing the processing procedure of the prescription information providing server 330 according to this embodiment. This flowchart is executed by the CPU that controls the prescription information providing server 330 using the RAM, and realizes the components of the prescription information providing server 330 in FIG.

[0083] In step S1311, the prescription information providing server 330 determines whether or not a doctor is to be registered. If a doctor is to be registered, in step S1313, the prescription information providing server 330 acquires doctor information from the communication terminal 210. Then, in step S1315, the prescription information providing server 330 registers the doctor information in the member database 1103.

[0084] If the doctor is not registered, the prescription information providing server 330 determines whether or not a prescription support request has been made from the communication terminal 210 in step S1321. If a prescription support request has been made from the communication terminal 210, the prescription information providing server 330 transmits a prescription search screen for inputting search conditions to the communication terminal 210 in step S1323. Then, the prescription information providing server 330 waits for reception of the search conditions from the communication terminal 210 in step S1325. Upon receiving the search conditions, the prescription information providing server 330 transmits the search conditions to the dispensing information search server 320 in step S1327. Then, the prescription information providing server 330 waits for a response of the search results from the dispensing information search server 320 in step S1329.

[0085] If there is a search result response, the prescription information providing server 330 acquires the search result response in step S1331. In step S1333, the prescription information providing server 330 determines whether or not to select a prescription drug set to be displayed for the search result. In the case of selecting a prescription drug set to be displayed, the prescription information providing server 330 selects a prescription drug set to be presented based on included / excluded drugs in step S1335. In step S1337, the prescription information providing server 330 generates a display screen of the prescription drug set, and in step S1339, transmits the display screen of the prescription drug set to the communication terminal 210 that sent the search request.

[0086] <Communication terminal> Hereinafter, with reference to Figs. 14 and 15, a configuration and operation of the communication terminal 210 that displays the search results when a doctor instructs a search for a prescription drug set as prescription support will be described.

[0087] (Functional configuration) FIG. 14 is a block diagram showing the functional configuration of a communication terminal 210 according to this embodiment.

[0088] The communication terminal 210 includes a communication control unit 1401 , a prescription support application acquisition unit 1402 , a prescription support application execution unit 1403 , and an input / output interface 1404 .

[0089] The communication control unit 1401 controls communication with the prescription information providing server 330. The prescription support application acquisition unit 1402 acquires a prescription support application to be executed in the communication terminal 210. The prescription support application execution unit 1403 executes the acquired prescription support application. The input / output interface 1404 connects to input / output devices such as a display unit 1441 and an operation unit 1442.

[0090] The prescription support app execution unit 1403 includes a doctor information acquisition unit 1431, a doctor information registration instruction unit 1432, a search condition input screen acquisition unit 1433, and a search condition input screen display control unit 1434. The prescription support app execution unit 1403 also includes a search condition acquisition unit 1435, a search condition transmission unit 1436, a prescription drug set display screen receiving unit 1437, and a prescription drug set display screen display control unit 1438.

[0091] The doctor information acquisition unit 1431 acquires doctor information input from the operation unit 1442 for doctor registration. The doctor information registration instruction unit 1432 transmits the acquired doctor information to the prescription information providing server 330 and instructs doctor registration. The search condition input screen acquisition unit 1433 acquires a prescription search screen as a screen for inputting search conditions from the prescription information providing server 330. The search condition input screen display control unit 1434 displays the acquired prescription search screen on the display unit 1441. The search condition acquisition unit 1435 acquires search conditions input from the operation unit 1442 for the prescription search screen. The search condition transmission unit 1436 transmits the acquired search conditions to the prescription information providing server 330 as a search request for a prescription drug set. The prescription drug set display screen receiving unit 1437 receives a display screen of the prescription drug set of the search result from the prescription information providing server 330 as a response to the search request. The prescription drug set display screen display control unit 1438 displays the display screen of the prescription drug set of the received search result on the display unit 1441.

[0092] (Processing Procedure) 15 is a flowchart showing the processing procedure of the communication terminal 210 according to this embodiment. This flowchart is executed by the CPU that controls the communication terminal 210 using the RAM, and realizes the components of the communication terminal 210 in FIG.

[0093] The communication terminal 210 determines whether or not the prescription support app is to be started in step S1511. If the prescription support app is to be started, the communication terminal 210 acquires the prescription support app in step S1513, and starts the prescription support app in step S1515.

[0094] In step S1517, the communication terminal 210 determines whether or not a doctor needs to be registered (is not registered). If a doctor needs to be registered, the communication terminal 210 acquires doctor information in step S1519, and transmits the acquired doctor information to the prescription information providing server 330 in step S1521.

[0095] If the prescription support app is running, the communication terminal 210 determines whether or not the request is a search request for a prescription drug set in step S1531. If the request is a search request for a prescription drug set, the communication terminal 210 acquires a prescription search screen, which is an input screen for search conditions, from the prescription information providing server 330 in step S1533. Then, the communication terminal 210 displays the prescription search screen in step S1535.

[0096] In step S1537, the communication terminal 210 waits for input of search conditions from the operation unit 1442. If the search conditions are input, in step S1539, the communication terminal 210 transmits the search conditions to the prescription information providing server 330. Then, in step S1541, the communication terminal 210 waits for a response of search results from the prescription information providing server 330. If a response of search results is received, in step S1543, the communication terminal 210 displays the prescription drug set that is the search result.

[0097] According to this embodiment, since the receipt data including medical receipts and dispensing receipts is used, the quality of the information is consistent, the dispensing has been checked, and a highly reliable prescription drug set can be presented. In addition, since the doctor can specify the drugs he / she wants to include in the prescription drug set, for example, it is possible to know prescription examples of new drugs. In addition, since the doctor can specify the drugs he / she does not want to include in the prescription drug set, for example, it is possible to know appropriate prescription examples corresponding to the patient.

[0098] That is, since receipt data is used, the names of diseases that can be written on receipts are fixed (based on standard disease names set by the Ministry of Health, Labor and Welfare), so it is expected that there will be less variation due to doctors' and pharmacists' inconsistencies in notation (standardization is achieved because the medical affairs department checks the form to be submitted as a receipt). In addition, by using the major and minor categories of this embodiment, it is possible to search by symptoms, so the ease of use of searches is improved by searching for the same symptoms (minor categories) within different major categories, making it possible to produce a more appropriate prescription drug set.

[0099] [Third embodiment] Next, a prescription support system according to a third embodiment of the present invention will be described. The prescription support system according to this embodiment differs from the second embodiment in that it presents a prescription drug set that takes into account the timing of issuing a prescription. The timing of issuing a prescription includes, for example, the first consultation, the continuation of medical treatment, and the change of the prescription drug set. Since the other configurations and operations are the same as those of the second embodiment, the same reference numerals are used for the same configurations and operations, and detailed explanations thereof will be omitted.

[0100] (Search input screen of communication device) Fig. 16 is a diagram showing a search input screen 1611 of the communication terminal 210 in the prescription support system according to this embodiment. Note that in Fig. 16, explanations of components similar to those in the prescription search screen 211 in Fig. 2A will be omitted.

[0101] The search input screen 1611 has a field 1612 for setting whether the prescription is to be issued at the "first visit", "during continued treatment", or "when the prescription is changed" during the medical treatment period, and a field 1613 for inputting the medical history. In this embodiment, different prescription drug sets, particularly the usage and dosage, or the number of prescription days, can be optimized depending on the time when the prescription is issued.

[0102] (Search Database) Fig. 17 is a diagram showing the configuration of a search database 1721 according to this embodiment. In Fig. 17, the same components as those in Fig. 6C are given the same reference numerals, and duplicated explanations will be omitted.

[0103] In the search database 1721, the prescription drug sets are further subdivided according to the prescription time 1701, and prescription drug sets suitable for the prescription time are stored.

[0104] According to this embodiment, in addition to the effects of the other embodiments, assistance can be provided that takes into account the timing of issuing a prescription, thereby enabling prescriptions to be issued more accurately.

[0105] [Fourth embodiment] Next, a prescription support system according to a third embodiment of the present invention will be described. The prescription support system according to this embodiment is different from the second and third embodiments in that it supports prescription issuance by considering the issuer of the receipt data. Since the other configurations and operations are the same as those of the second and third embodiments, the same configurations and operations are assigned the same reference numerals and detailed descriptions thereof are omitted.

[0106] <Prescription drug set extraction section> Fig. 18 is a block diagram showing the functional configuration of an information processing device as a prescription medicine set extraction unit 1840 according to this embodiment. In Fig. 18, the same components as those in Fig. 5 are given the same reference numbers, and duplicated explanations will be omitted.

[0107] The dispensed drug set extraction unit 1840 includes a statistical processing unit 1806 having a prescription issuer weighting table 1861. For example, in the setting of frequency ranking in the statistical processing unit 1806, by calculating the appearance frequency by weighting prescriptions depending on whether the prescription issuer is a general hospital or a clinic, it is possible to search for dispensed drug sets that are not biased toward individual doctors.

[0108] (Receipt issuer weighting table) 19 is a diagram showing the configuration of a prescription issuer weighting table 1861 according to this embodiment. The prescription issuer weighting table 1861 is used by the statistical processing unit 1806 of the prescription drug set extraction unit 1840 to generate a search database 321 that enables a search for prescription drug sets that are not biased toward individual doctors.

[0109] The prescription issuer weighting table 1861 stores prescription issuer 1902 and ranking weighting 1903 in addition to data 1901 of a prescription set corresponding to a patient's attributes and the patient's symptoms or disease name. Note that gender in the patient attributes is optional.

[0110] According to this embodiment, in addition to the effects of the other embodiments, it is possible to assist in issuing prescriptions based on more reliable receipt data.

[0111] [Fifth embodiment] Next, a prescription support system according to a third embodiment of the present invention will be described. The prescription support system according to this embodiment is different from the second to fourth embodiments in that it supports prescription issuance taking into account medical history. Since the other configurations and operations are the same as those of the second to fourth embodiments, the same reference numerals are used for the same configurations and operations, and detailed descriptions thereof will be omitted.

[0112] (Search result display screen on communication device) FIG. 20 is a diagram showing a search result display screen 2011 of a communication terminal 2010 in the prescription support system according to this embodiment.

[0113] The search result display screen 2011 of the communication terminal 2010 displays the search conditions and the prescription dosage history for each prescription drug A, B, and B in the prescription drug set of the search result in the form of a graph. By referring to such a graph, the doctor can refer to the current appropriate dosage. Note that, although the present embodiment focuses on the progress of only the dosage, this is not limiting. For example, even when a prescription drug is changed, the progress and dosage can be referred to at a glance.

[0114] According to this embodiment, in addition to the effects of the other embodiments, it is possible to assist in issuing a prescription that matches the history of medication for a patient.

[0115] [Other embodiments] Although not described in detail in the above embodiment, it is possible to support the issuance of a more appropriate prescription for the patient by taking into consideration, for example, the side effects of the drug, the patient's medical history, contraindications for use with other drugs, and contraindications for use with foods. These additions and modifications to the above embodiment are self-evident from the above embodiment.

[0116] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the technical scope of the present invention. In addition, systems or devices that combine the separate features included in each embodiment in any way are also included in the technical scope of the present invention.

[0117] The present invention may be applied to a system consisting of multiple devices, or to a single device. Furthermore, the present invention is also applicable to a case where an information processing program for implementing the functions of the embodiments is supplied to a system or device and executed by a built-in processor. In order to implement the functions of the present invention on a computer, an application program installed on a computer, a medium storing the program, a server for downloading the program, and a processor for executing the program are also included in the technical scope of the present invention. In particular, at least a non-transitory computer readable medium storing a program for causing a computer to execute the processing steps included in the above-mentioned embodiments is included in the technical scope of the present invention.

Claims

1. A medical examination information acquisition unit that acquires attributes and symptoms or disease names of patients; a prescription drug presentation unit that refers to a prescription drug database that links and accumulates a patient's attributes, the patient's symptoms or disease name, prescription drugs prescribed to the patient in the past according to the symptoms or disease name, and attributes of the receipt data based on the receipt data, and presents to a doctor prescription drugs corresponding to the patient's attributes and symptoms or disease name; A prescription support system equipped with

2. The medical examination information acquisition unit further acquires information on drugs that should be included in the prescription or drugs that should not be included in the prescription, The prescription support system according to claim 1 , wherein the prescription presentation unit presents to the doctor prescription drugs that include the drug to be included or prescription drugs that do not include the drug that should not be included.

3. The medical examination information acquisition unit further acquires the issuance time of a prescription during the medical examination period of the patient, 3. The prescription support system according to claim 1, wherein the prescription presentation unit presents the prescription drugs selected in accordance with the issuance time to the doctor.

4. The prescription support system according to claim 3 , wherein the issuing time includes a time of a first consultation, a medical treatment period excluding the first consultation, and a time of a change in a prescribed drug.

5. The prescription support system according to any one of claims 1 to 4, wherein the prescription drug presentation unit extracts at least one of information on contraindications for combinations including drug interactions and food interactions, information on drug side effects, allergy information, and medical history from the prescription data, and selects the prescription drug to be presented.

6. a medical examination information acquisition step in which a medical examination information acquisition unit acquires attributes and symptoms or disease names of a patient; a prescription drug presentation step in which a prescription drug presentation unit refers to a prescription drug database that links and accumulates a patient's attributes, the patient's symptoms or disease name, prescription drugs prescribed for the patient in the past according to the symptoms or disease name, and attributes of the receipt data based on the receipt data, and presents to a doctor prescription drugs corresponding to the patient's attributes and symptoms or disease name; A prescription support method including:

7. A medical examination information acquisition step of acquiring attributes and symptoms or disease names of patients; a prescription drug presentation step of referring to a prescription drug database that links and accumulates a patient's attributes, the patient's symptoms or disease name, prescription drugs prescribed to the patient in the past according to the symptoms or disease name, and attributes of the receipt data based on the receipt data, and presenting to a doctor prescription drugs corresponding to the patient's attributes and symptoms or disease name; An application program that causes a computer to execute the following:

Images