WO2015189958A1 - Analysis system and analysis method - Google Patents

Analysis system and analysis method Download PDF

Info

Publication number
WO2015189958A1
WO2015189958A1 PCT/JP2014/065619 JP2014065619W WO2015189958A1 WO 2015189958 A1 WO2015189958 A1 WO 2015189958A1 JP 2014065619 W JP2014065619 W JP 2014065619W WO 2015189958 A1 WO2015189958 A1 WO 2015189958A1
Authority
WO
WIPO (PCT)
Prior art keywords
side effect
drug
prescription
patient
index
Prior art date
Application number
PCT/JP2014/065619
Other languages
French (fr)
Japanese (ja)
Inventor
島田 和之
淳平 佐藤
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2014/065619 priority Critical patent/WO2015189958A1/en
Publication of WO2015189958A1 publication Critical patent/WO2015189958A1/en

Links

Images

Classifications

    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H70/00ICT specially adapted for the handling or processing of medical references
    • G16H70/40ICT specially adapted for the handling or processing of medical references relating to drugs, e.g. their side effects or intended usage

Definitions

  • the present invention relates to an information system that supports analysis of side effects of prescription drugs in hospitals and the like.
  • Patent Document 1 states that “the present invention includes a system for predicting possible drug side effects by using a search engine that compares integrated data from laboratory and pharmacy information systems.
  • Patent Document 1 Japanese Patent Application Laid-Open No. 2002-342484
  • An object of the present invention is to provide an information system that visualizes the position (drug position) of effects, side effects, medical expenses, etc. of individual drugs in a wide variety of medications and supports appropriate medications. .
  • the present invention is an analysis system comprising a processor and a storage device connected to the processor, wherein the storage device indicates case information indicating the disease and hospitalization period of each patient. And prescription information indicating the prescription period of each drug to each patient, test information indicating the test result of each patient, and knowledge information indicating determination conditions for side effects based on the test results,
  • the processor causes a side effect based on the relationship between the time when the test result of each patient satisfies the determination condition for the side effect and the prescription period of each drug for each patient.
  • the medicine is estimated and the result of the estimation is output.
  • when a user selects the disease made into analysis and visualization it is explanatory drawing of the example of the disease selection screen which an input / output terminal displays.
  • FIG. 1 is a block diagram showing a configuration of a drug positioning visualization system according to an embodiment of the present invention.
  • the drug positioning visualization system of the present embodiment is a computer system that analyzes the position (drug position) of the effect, side effect, medical cost, etc. of each drug, visualizes the result, and outputs the result.
  • the network 140 and the input / output terminal 120 used by the user are configured.
  • the input / output terminal 120 includes an input unit (not shown) such as a keyboard, mouse, or touch panel, an output unit (not shown) such as a display, and a communication unit (not shown) that communicates with the data server 100 and the like. ) And one or more personal computers.
  • a portable terminal such as a PDA, PHS, mobile phone, smartphone, or tablet terminal having an input unit such as a button or a touch panel, an output unit such as a display, and a communication unit that communicates with the data server 100 or the like is an input / output terminal. 120 can also be used.
  • the input / output terminal 120 is installed and used in an insurer such as a medical institution (health care provider) such as a hospital or clinic, a country, a health insurance association, or a private insurance company.
  • the data server 100 is installed in the data center.
  • the user's personal information and privacy information such as the data collected from the user can be centrally managed, so that security management such as information leakage prevention can be simplified.
  • a doctor, manager or manager of a medical institution or insurer is assumed.
  • the user operates the input / output terminal 120 and uses the information system shown in this embodiment to analyze and visualize the effects, side effects, and medical costs of prescription drugs.
  • the data server 100 includes a control unit 101, a memory 102, a communication unit 103, a medical data acquisition unit 104, a medical cost data acquisition unit 105, an output unit 107, a disease information selection unit 108, a case data extraction unit 109,
  • the prescription data extraction unit 111, the examination data extraction unit 112, the effect determination unit 113, the side effect determination unit 114, the medical cost calculation unit 115, the screen generation unit 116, the case database 117, and the knowledge database 119 are configured.
  • the control unit 101 is a processor that executes a program stored in the memory 102, for example, and controls each unit of the data server 100.
  • the memory 102 is a storage device such as a DRAM (Dynamic Random Access Memory), for example, and stores data (for example, a program executed by the control unit 101) referred to by each unit of the data server 100.
  • DRAM Dynamic Random Access Memory
  • the case database 117 and the knowledge database 119 may be stored in the memory 102 or may be stored in another storage device (not shown) in the data server 100 such as an HDD (Hard Disk Drive).
  • HDD Hard Disk Drive
  • the communication unit 103 is connected to the network 140 and communicates with the input / output terminal 120.
  • the output unit 107 is a device that outputs a result of processing by the data server 100, and may be a display device, for example.
  • the unit 115 and the screen generation unit 116 are processing units that execute processing for realizing the functions of the data server 100, and each may be realized by dedicated hardware or may be realized by software. In the latter case, the processing executed by each processing unit in the following description is actually executed by the control unit 101 in accordance with an instruction described in a program stored in the memory 102. Details of the processing executed by each processing unit will be described later.
  • the data server 100 and the input / output terminal 120 are connected to the network 140.
  • the data server 100 communicates with the input / output terminal 120 via the network 140.
  • the network 140 uses wired communication using a LAN (Local Area Network) cable or wireless communication using a wireless LAN.
  • LAN Local Area Network
  • the network 140 can also use other wide area networks such as the Internet, VPN, mobile phone communication network, and PHS communication network.
  • FIG. 2 is an explanatory diagram of an example 200 of the case database 117 according to the embodiment of this invention.
  • the case database example 200 includes a case information table 210 for managing basic information for each case, a prescription information table 220 for storing prescription information for each case, a clinical test information table 230 for storing clinical test information for each case, , Image examination information table 240 for storing image examination information for each case, and cost information such as insurance claim costs and costs for each medical practice for medical practice such as prescription, clinical examination, image examination, and surgery. And a cost information table 250 to be stored.
  • the case information table 210 includes a field 211 for storing a patient ID for identifying a patient, a field 212 for storing a hospitalization date of a medical institution, a field 213 for storing a discharge date, a field 214 for storing a disease name, and discharge. And a field 215 for storing time outcome information.
  • Information on one case is stored in each record (case information record) of the case information table 210.
  • One hospitalization of one patient corresponds to one case.
  • the case identified by the patient ID “Pt-0001” is the hospitalization date “December 12, 2012” and the discharge date “2012”.
  • the prescription information table 220 includes a field 221 for storing a patient ID, a field 222 for storing information for identifying a prescription drug, a field 223 for storing a prescription date, and a field 224 for storing the length of a prescribed period. And a field 225 for storing a usage / dose.
  • the medicine A and the medicine B are each 5 days from December 12, 2012 (that is, from December 12 to 16). This shows that medication C was prescribed for 3 days from December 15, 2012 (ie, during the period from December 15 to 17).
  • the clinical test information table 230 includes a field 231 for storing a patient ID, a field 232 for storing information for identifying a test item, a field 233 for storing a test date, and a field 234 for storing a test result.
  • a field 231 for storing a patient ID
  • a field 232 for storing information for identifying a test item
  • a field 233 for storing a test date
  • a field 234 for storing a test result.
  • the image examination information table 240 includes a field 241 for storing a patient ID, a field 242 for storing information for identifying an examination item, a field 243 for storing an examination date, and a field for storing observation information as a result of image diagnosis. 244.
  • a field 241 for storing a patient ID for storing information for identifying an examination item
  • a field 243 for storing an examination date for storing observation information as a result of image diagnosis.
  • FIG. 2 in the case of the patient ID “Pt-0001”, 2012 regarding the examination findings of lung CT (Computed Tomography), which is an examination item for diagnosing the lung state. It is shown that “Tumor A was 10.2 mm” on December 12, and “Tumor A was 9.1 mm” on December 15, 2012.
  • the above-described clinical examination information table 230 and image examination information table 240 are examples of information indicating the results of examinations actually performed on each patient.
  • a clinical test information table 230 mainly including blood test results and an image test information table 240 including test results based on images such as CT are independent. May be included.
  • the case database 117 may include information indicating the results of other types of examinations performed on each patient, and further information related to the patient's subjective symptoms such as “nausea” or “vomiting” May be included.
  • the cost information table 250 includes a field 251 for storing a medical practice ID for identifying a medical practice, a field 252 for storing the name of the medical practice, and the number of insurance points that can be claimed when the medical practice is performed, that is, cost information that can be claimed. And a field 254 for storing the cost of the medical practice, that is, the cost when the medical practice is performed.
  • Information on one medical practice is stored in each record (medical practice record) of the cost information table 250.
  • the medical practice “drug A” identified by the medical practice ID “P0010001” has an insurance score “a” and a cost “x” yen.
  • the cost “x” yen is the insurance claim cost when the insurance score is “a”, that is, “a ⁇ 10” yen.
  • the cost assumes the purchase cost of prescription drugs (drugs) necessary for medical practice, reagents used for testing, and medical materials used for surgery or treatment in medical institutions that use this system. It can also include personnel costs of medical staff such as doctors when performing medical practice, and depreciation costs of medical equipment such as diagnostic imaging devices.
  • FIG. 3 is an explanatory diagram of an example 300 of the knowledge database 119 according to the embodiment of this invention.
  • the knowledge base example 300 includes a prescription drug knowledge table 310 and a side effect knowledge table 320.
  • the prescription drug knowledge table 310 specifies a field 311 for storing information for identifying a prescription drug, a field 312 for storing information for identifying a disease to which the prescription drug can be applied, and a test result or finding showing the effect of the prescription drug.
  • Information about one prescription drug is stored in each record (prescription drug knowledge record) of the prescription drug knowledge table 310.
  • the prescription drug “drug A” can be applied to the treatment of “lung cancer” (field 312), the effect is the improvement of “tumor size” (field 313), and the side effect is “liver function”.
  • the inspection item “ALT (GPT)” is deteriorated (field 314).
  • the side effect knowledge table 320 includes information indicating a side effect determination condition based on a test result or the like. Specifically, the side effect knowledge table 320 stores a field 321 for storing information for identifying an item indicating a side effect such as a test or a subjective symptom, and a side effect. The field 322 stores knowledge for determining an abnormal state for each item, and the field 323 stores knowledge for determining a dangerous state for each item indicating a side effect.
  • Information related to one examination item is stored in each record (side effect knowledge record) of the side effect knowledge table 320.
  • the side effect knowledge record 320A when the inspection item “ALT (GPT)” is 45 or more, it indicates an abnormal value indicating “abnormal condition”, and when it is 100 or more, it indicates a dangerous value indicating “dangerous condition”. Yes.
  • test item “digestive symptom” is “abnormal state” when “nausea”, and “dangerous state” when “vomiting”.
  • the abnormal state and the dangerous state are both states in which abnormalities in test results suspected to be caused by the side effects of prescription drugs have occurred, but the dangerous state is a state in which an abnormality greater than the abnormal state has occurred. It is.
  • the side effect determination condition based on the test result of one test item is stored in one side effect knowledge record. Specifically, a criterion for determining an abnormal state is stored in the field 322, and a criterion for determining a dangerous state is stored in the field 323, respectively.
  • the prescription of the medicine can be continued as it is, or the test result showing a side effect is displayed. It can assist the judgment of the prescription medical process, such as whether to continue the prescription while monitoring, or to stop the prescription. For example, if a doctor prescribes a drug and the patient does not become abnormal, the prescription is continued as it is, and if the patient becomes abnormal, the prescription is continued while monitoring test results that show side effects. A determination may be made that the prescription is interrupted immediately when the condition is reached.
  • FIG. 4 is a flowchart showing the operation of the data server 100 according to the embodiment of this invention.
  • the control unit 101 executes step 401 in which case data is read from the case database 117 and stored in the memory 102.
  • case data data related to cases, for example, information for identifying cases, information on prescription drugs corresponding to cases, information on test results corresponding to cases, and the like are collectively referred to as case data.
  • the control unit 101 may read all data included in the case database 117 and store it in the memory 102 in step 401.
  • control unit 101 reads out the knowledge data from the knowledge database 119 and executes step 402 for storing it in the memory 102.
  • control unit 101 may read all data included in the knowledge database 119 and store it in the memory 102 in step 402.
  • the control unit 101 activates the disease information selection unit 108.
  • the disease information selection unit 108 executes step 403 that allows the user to select a disease to be analyzed and visualized.
  • the disease selected in step 403 may be described as a target disease.
  • a disease selection screen is displayed on the input / output terminal 120.
  • FIG. 6 is an explanatory diagram of an example 600 of a disease selection screen displayed by the input / output terminal 120 when the user selects a disease to be analyzed and visualized in the embodiment of the present invention.
  • the screen example 600 includes a disease selection box 611, an execution button 613, and a prescription drug display area 620.
  • the user operates a drop-down button 612 attached to the disease selection box 611, and selects a disease to be analyzed and visualized from a plurality of diseases displayed in a drop-down list (not shown).
  • the user can directly input a disease name in the disease selection box 611.
  • the control unit 101 activates the case data extraction unit 109.
  • the case data extraction unit 109 executes Step 404 for extracting a case corresponding to the disease selected in Step 403 from the case database 117 stored in the memory 102.
  • the case data extraction unit 109 refers to the case information table 210, and the case described in the case information record in which the disease name selected in step 403 is stored in the field 214 (that is, a combination of the patient and the hospitalization period) Are all extracted.
  • the prescription data extraction unit 111 executes step 405 for extracting prescription data corresponding to the case extracted in step 404.
  • the prescription data extraction unit 111 identifies the patient ID and hospitalization period of each case from each case information record extracted in step 404, and stores the same patient ID as the identified patient ID in the field 221.
  • the record (prescription information record) of the prescription information table 220 in which the prescription date within the hospitalization period that has been stored in the field 223 may be extracted.
  • the prescription data extraction unit 111 may extract prescription data by a method different from the above method.
  • the prescription data extraction unit 111 uses the prescription drug knowledge table 310 of the knowledge database 300 stored in the memory 102 in step 402, and sets the applicable disease field 312 based on the disease (target disease) selected in step 403.
  • One or more prescription drugs stored in the prescription drug field 311 of one or more prescription drug knowledge records having a value in the applicable disease field 312 that matches the target disease can be extracted as prescription data.
  • control unit 101 determines whether or not the analysis processing from step 407 to step 409, which will be described later, is completed for all prescription drugs for each prescription drug described in the prescription data extracted in step 405, If there are one or more unprocessed prescription drugs, step 406 is performed to select one of them as an analysis target.
  • step 406 When it is determined in step 406 that there is a prescription drug whose analysis processing has not been completed, the control unit 101 determines one of unprocessed prescription drugs (hereinafter also referred to as a target prescription drug). The analysis processing from step 407 to step 409 is executed. In step 407, the control unit 101 activates the inspection data extraction unit 112. The test data extraction unit 112 uses the prescription drug knowledge table 310 to extract test data showing effects or side effects related to the prescription drug based on the cases extracted in step 404.
  • the test data extraction unit 112 stores the prescription drug knowledge record 310A.
  • the examination data extraction unit 112 extracts a record storing the tumor size of the lung CT from the image examination information table 240 and a record storing ALT (GPT) from the clinical examination information table.
  • step 408 the control unit 101 activates the effect determination unit 113.
  • the effect determination unit 113 calculates the effect index of the target prescription drug.
  • the target prescription drug is “medicine A”.
  • the effect determination unit 113 calculates the effect index DEI using Equation (1).
  • the effect determination unit 113 determines the number of improved cases based on the difference between the time of hospitalization and the time of discharge, such as a test result that shows the effect. For example, the effect determination unit 113 identifies a case corresponding to each record based on the patient ID and the examination date of each record related to the tumor size extracted in step 407, and the tumor size at the time of hospitalization and discharge at each case. Compare For example, when the “tumor size” of a case is “10.2 mm” at the time of hospitalization and “2.0 mm” at the time of discharge, there is a difference in tumor size before and after the prescription. Since this difference coincides with the decrease in tumor size, which is the effect stored in the field 313 of the prescription drug knowledge record 310A of the drug “A”, the effect determination unit 113 counts the case as an improved case.
  • the difference in the test results that show the effect may be calculated between the pre-prescription time and the post-prescription time point, and the above "on hospitalization” and “discharge time” are examples of those time points. is there.
  • the latest test result may be used instead of the test result at the time of discharge.
  • the number of cases APN prescribed for the target disease is the number of cases prescribed the target prescription drug “drug A” among the cases extracted in step 404.
  • the effect index DEI calculated by this is the probability that the effect of the prescription drug will appear by prescribing the prescription drug to the patient with the target disease.
  • a large effect index DEI of a prescription drug indicates a high rate of occurrence of cases where it is estimated that the effect of the prescription drug has appeared.
  • the effect determination unit 113 calculates the effect index by comparing the difference such as the test result with the effect stored in the prescription drug knowledge table 310, but this method has a high effect of the prescription drug.
  • This is an example of a method for calculating an effect index, which is an index indicating the degree, and the effect determination unit 113 may calculate the effect index by another method.
  • the effect determination unit 113 can also calculate the effect index using the “hospitalization period” from the hospitalization date to the discharge date of each patient for whom the prescription drug is prescribed.
  • the effect determination unit 113 may calculate the effect index DEI_A using the mathematical formula (1A).
  • step 409 the control unit 101 activates the medical cost calculation unit 115.
  • the medical cost calculation unit 115 calculates the medical cost of the target prescription drug.
  • the medical cost calculation unit 115 calculates the medical cost PRC using Equation (2).
  • the medical cost PRC calculated in this way is an expected value of the total medical cost of the prescription drug prescribed during the hospitalization period of the patient with the target disease.
  • the medical cost PRC calculated in this way is an expected value of the total medical cost of the prescription drug prescribed during the hospitalization period of the patient with the target disease.
  • the cost described in the cost information table 250 can be used as the unit price PUP of the prescription drug. Thereby, since the medical cost can be calculated using the cost for each medical institution, the comparison with other prescription drugs in the medical institution can be accurately analyzed.
  • the insurance score or insurance claim cost described in the cost information table 250 can be used. This makes it easy to analyze the comparison with other prescription drugs even if the cost is unclear. In addition, since insurance scores and insurance claim costs are standardized in each country including Japan, it is possible to analyze comparisons with other medical institutions using these.
  • control unit 101 then activates the side effect determination unit 114.
  • the side effect determination unit 114 executes step 410 for calculating a side effect index.
  • FIG. 5 is a flowchart showing an operation when the side effect determination unit 114 according to the embodiment of the present invention executes an analysis process for calculating a side effect index in Step 410.
  • FIG. 8 is an explanatory diagram of a screen example 800 on which the input / output terminal 120 according to the embodiment of the present invention displays case data.
  • the screen example 800 is an example of a screen that the input / output terminal 120 displays on an output unit (not shown) such as a display.
  • the screen 810 displays an area 810 that displays clinical indicators, an area 820 that displays prescription information, and medical cost information. Display area 830.
  • the screen generation unit 116 generates data of the screen example 800
  • the communication unit 103 transmits the data via the network 140
  • An example of display in (omitted) will be described.
  • this is an example of the output form of the processing result by the data server 100.
  • the output unit 107 may display the screen example 800, or the data server 100 sends the processing result of FIG.
  • the input / output terminal 120 may receive the processing result via the network 140, generate the screen example 800 based on the result, and display the screen example on an output unit (not shown).
  • the horizontal axis represents the number of days elapsed from the date of hospitalization to the date of discharge, and the vertical axis represents the size of the clinical index. Plots of test results that show effects and test results that show side effects are plotted. Will be displayed. Further, on this graph, the abnormal value stored in the abnormal condition knowledge field 322 of the side effect knowledge table 320 and the dangerous value stored in the dangerous condition knowledge field 323 are respectively shown as an abnormal value determination line 811 and a dangerous value determination line 812. Is displayed.
  • the prescription continuation days of prescription drugs prescribed from the hospitalization date to the discharge date of the target case are displayed.
  • the prescription period of each prescription drug is displayed on a graph in which the elapsed time from the hospitalization date to the discharge date is assigned to the horizontal axis.
  • a value obtained by adding the unit prices of prescription drugs for each day for the prescription drugs prescribed from the hospitalization date to the discharge date of the target case is displayed.
  • the above three graphs are displayed side by side on the same screen, and by making the scales of the horizontal axes the same, the prescription period of each prescription drug, the time of occurrence of an effect or a side effect, and , It becomes possible to easily grasp the relationship with the cost.
  • the side effect determination unit 114 determines whether or not the side effect analysis processing from step 502 to step 508, which will be described later, has been completed for all cases extracted in step 404, and there are one or more unprocessed cases In step S501, one of unprocessed cases is selected as a target for the side effect analysis process.
  • the side effect determination unit 114 executes step 502 for extracting a side effect occurrence period. For example, as shown in the screen example 800, the side effect determination unit 114 indicates that the test data corresponding to the side effect has changed from less than the abnormal value to more than the abnormal value as the “side effect occurrence start date”, and the abnormal value after the side effect occurrence start date. From the above, when it returns to less than the abnormal value, it is determined as the “side effect occurrence end date”, and from the side effect occurrence start date to the side effect occurrence end date is determined as the “side effect occurrence period”.
  • the period from when the inspection data changes from less than the abnormal value to more than the abnormal value until when it returns from the abnormal value to less than the abnormal value is described as the “abnormal value occurrence period”
  • the period from when the inspection data changes from less than the dangerous value to more than the dangerous value until when the inspection data returns from more than the dangerous value to less than the dangerous value is referred to as the “dangerous value occurrence period”.
  • the side effect determination unit 114 executes step 503 for extracting a prescription drug prescribed during the side effect occurrence period as a side effect causative drug candidate. Specifically, the side effect determination unit 114 extracts prescription drugs whose prescription period overlaps with the side effect occurrence period among prescription drugs prescribed during the hospitalization period of one case as a side effect cause drug candidate. In the case data of screen example 800, “drug A”, “drug B”, and “drug D” are extracted from the prescription drugs as drug candidates that cause side effects, excluding “drug C” that is not prescribed during the side effect occurrence period.
  • the side effect determination unit 114 executes step 503 for extracting a prescription drug prescribed during the side effect occurrence period as a side effect causative drug candidate. Specifically, the side effect determination unit 114 extracts prescription drugs whose prescription period overlaps with the side effect occurrence period among prescription drugs prescribed during the hospitalization period of one case as a side effect cause drug candidate. In the case data of screen example 800, “drug A”, “drug B”, and “d
  • the side effect determination unit 114 analyzes the variation of the test data and executes Step 504 for determining the date of occurrence of the dangerous value.
  • the side effect determination unit 114 determines the risk value occurrence date 813 when the test data corresponding to the side effect changes from less than the risk value to more than the risk value.
  • the side effect determination unit 114 determines whether or not the prescription information has changed before and after the risk value occurrence date, and prescription information that has not changed, that is, prescription drugs that are continuously prescribed before and after the risk value occurrence date.
  • Step 505 of excluding from the side effect cause drug candidate is executed. This is because, in general, when a risk value is generated by prescribing a certain medicine, it is considered that the doctor stops prescribing the medicine at that time. In other words, a drug that has been prescribed before the date of occurrence of the risk value and has been prescribed continuously after the date of occurrence of the risk value is not the cause of the occurrence of the risk value by the doctor who prescribes the drug. It is estimated that it was determined. For this reason, for example, the side effect determination unit 114 may exclude a drug prescribed for a predetermined period after the risk value occurrence date from the side effect causative drug candidate.
  • step 506 is executed to exclude prescription drugs prescribed after the risk value occurrence date from the side effect cause drug candidates. This is because prescription medicines that are not prescribed before the risk value occurrence date and that are prescribed after the risk value occurrence date cannot cause the risk value.
  • drug D that is not prescribed before the risk value occurrence date 813 and is prescribed after the risk value occurrence date 813 is excluded from the side effect cause drug candidates. .
  • the side effect determination unit 114 executes step 507 of extracting prescription drugs that are not excluded in either step 505 or step 506 among the side effect cause drug candidates extracted in step 503 as side effect cause drugs.
  • “drug B” is extracted as a side effect-causing drug.
  • the side effect determination unit 114 stores test values in the side effect knowledge table 320 for each case corresponding to the disease selected in step 403 (ie, each patient hospitalized for the disease selected in step 403). Based on the relationship between the time when the determined determination condition is satisfied and the prescription period of the drug to the patient, the drug estimated to be the cause of the side effect is extracted. Specifically, the side effect determination unit 114 is prescribed during the side effect occurrence period (step 503) and is not prescribed for a predetermined period after the test value changes from a value lower than the dangerous value to a higher value (step 505). And the medicine prescribed before the test value changes from a lower value to a higher value than the dangerous value (step 506) is extracted as a side effect-causing drug (step 507).
  • each determination condition stored in each record of the side effect knowledge table 320 is used to determine a first criterion for determining an abnormal value (that is, a criterion stored in the field 322) and a dangerous value.
  • the second criterion (that is, the criterion stored in the field 323) is included, but each determination condition may include only one criterion.
  • each determination condition may include only the second reference for determining the dangerous value.
  • the side effect occurrence period is a predetermined period including a period in which the determination condition is satisfied.
  • the side effect occurrence period is the same period as the abnormal value occurrence period (that is, including the abnormal value occurrence period), It is also a period including the dangerous value occurrence period.
  • the side effect occurrence period may be a predetermined period longer than the danger value occurrence period, including the danger value occurrence period.
  • the change in test data corresponding to the side effect is determined, and by using the continuity of prescription before and after the change (for example, the occurrence of a dangerous value), the cause of the side effect is determined. Can be narrowed down efficiently.
  • Step 508 for setting the side effect flag “1” to the prescription drug extracted as the side effect cause drug.
  • step 507 when a plurality of prescription drugs are extracted as side effect causative agents based on the side effect determination condition related to one inspection item (that is, stored in one side effect knowledge record), the side effect determination unit 114 Using equation (3), side effect flags are allocated and set according to the number of extracted prescription drugs.
  • the side effect determination unit 114 may perform slope distribution according to a predetermined criterion instead of using the above formula (3). For example, the side effect determination unit 114 is based on the estimation that the prescription drug having a longer number of days from the prescription end date to the subsequent risk value occurrence date is more likely to be unrelated to the occurrence of the risk value. In order to increase the value of the side effect flag allocated to the prescription drug with a shorter number of days from the risk value occurrence date to the prescription end date, the side effect flag is inclined and distributed for each prescription drug using Equation (4). You can also set it.
  • the side effect flag can be weighted so that the closer the two are, the closer the two are closer to the risk value occurrence date. It is possible to set a side effect flag according to the condition.
  • the prescription continuation state before and after the time when the inspection data shows an abnormal state or a dangerous state that is, the prescription process (prescription continuity) and the variability of the inspection data cause side effects.
  • Drugs can be narrowed down more efficiently. This makes it possible to conduct a more accurate side effect analysis for individual drugs in a wide variety of medications.
  • step 501 If it is determined in step 501 that the side effect analysis processing has been completed for all cases, the side effect determination unit 114 counts the side effect flags set in step 508 for all cases for each prescription drug, thereby determining the side effect index. Step 509 is calculated.
  • the side effect determination unit 114 calculates the side effect index DAI of the prescription drug m using Equation (5).
  • the side effect index DAI calculated by this is the probability that a side effect will appear when a prescription drug m is prescribed to a patient with the target disease.
  • a large side effect index DAI of the prescription drug m indicates a high rate of occurrence of cases suspected of causing side effects due to the prescription drug m. In this way, it is possible to analyze the comparison with other prescription drugs by using the side effect index that quantifies the degree of influence of side effects using hospitalization periods and examination information on multiple cases, etc. it can.
  • control unit 101 activates the screen generation unit 116.
  • the screen generator 116 outputs the results of all the analysis processes based on the effect index generated in step 408, the medical expenses generated in step 409, and the side effect index generated in step 410. Step 411 is generated.
  • control unit 101 executes Step 412 for outputting the screen generated in Step 411 to the input / output terminal 120.
  • FIG. 7 is an explanatory diagram of an example screen 700 on which the input / output terminal 120 according to the embodiment of the present invention displays the result of the analysis process after step 412 of FIG. 4 is executed.
  • a screen example 700 has a prescription drug display area 620 similar to that shown in FIG. 6, an effect index on the vertical axis, a side effect index on the horizontal axis, and the size of a circle (bubble) as medical expenses, and drugs A and B Drug C is displayed in a bubble chart on the same axis.
  • the therapeutic effects, side effects, and medical cost indicators of multiple prescription drugs prescribed for one disease are presented on the same axis of the same graph. It is possible to grasp the therapeutic effect, side effects, and the position of medical expenses (drag position) from a bird's-eye view. Thereby, since the user can easily grasp whether or not an appropriate drug is selected, it is possible to support optimization of a medical treatment process such as an appropriate medication treatment.
  • the horizontal axis indicates side effects (for example, 3%) similar to those in the attached document, and the average value of all side effect indexes calculated from data collected from other medical institutions (for example, the national average of 5%).
  • the average value of all effect indexes calculated from data collected from other medical institutions (for example, the national average of 80%) is displayed on the vertical axis.
  • the average value of all the side effect indexes and the average value of all the effect indexes calculated from the collected data in the medical institution are displayed by dotted lines as in-hospital averages 710 and 720, respectively.
  • the screen generation unit 116 generates data for displaying the screen example 700
  • the data server 100 transmits the data to the input / output terminal 120 via the network 140
  • the input / output terminal 120 converts the data into the data.
  • the output unit 107 may display the screen example 700.
  • FIG. 7 shows an example in which the effect index, the side effect index, and the medical cost of a plurality of prescription drugs are displayed in association with the vertical axis, the horizontal axis, and the size of the displayed circle, respectively.
  • a display method is an example, and these indicators may be displayed by other methods.
  • any one of the effect index, the side effect index, and the medical cost, or any combination of the two may be displayed, or a number indicating the value may be displayed.
  • the drug positioning visualization system provides an information system for visualizing the effects of individual drugs, side effects, and positioning of medical expenses (drug positions) in various types of medications and supporting appropriate medications. It becomes possible to do.
  • each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor.
  • Information such as programs, tables, and files that realize each function is a memory, hard disk drive, storage device such as SSD (Solid State Drive), or computer-readable non-transitory data such as an IC card, SD card, or DVD. It can be stored in a storage medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Toxicology (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Medicinal Chemistry (AREA)
  • Pharmacology & Pharmacy (AREA)
  • Chemical & Material Sciences (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

Provided is an analysis system comprising a processor and a storage device that is connected to the processor. The storage device stores case information which indicates the disease and length of hospital stay of each patient, prescription information which indicates the prescription period of each medicine for each patient, test information which indicates the test results for each patient, and knowledge information which indicates side-effect determination conditions based on the test results. The processor extrapolates, for each patient, the medicine that is the cause of a side effect, and does so on the basis of the relationship between a period in which the test results for each patient satisfy the side-effect determination conditions, and the prescription period of each medicine for each patient, and the processor outputs the results of the extrapolation.

Description

分析システムおよび分析方法Analysis system and analysis method
 本発明は、病院等の処方薬の副作用等の分析を支援する情報システムに関する。 The present invention relates to an information system that supports analysis of side effects of prescription drugs in hospitals and the like.
 本技術分野の背景技術として、特開2002-342484号公報(特許文献1)がある。特許文献1には、「本発明は検査室および調剤部の情報システムからの統合されたデータを比較する探索エンジンを使用することで可能な薬物副作用を予想するためのシステムを含んでおり、それを特定の検査テストに対する正常範囲を定義している予め決められたADEと比較する。異常なテスト値が受信され、患者の薬物養生における薬がADEルール内に含まれる薬を満足させると、警告プロシージャが引き起こされ、患者の検査および調剤データが適切な修正アクションが取られているか、その期間に何ら修正アクションが取られていないか、不適切な修正アクションが取られているかを決定するために患者の検査データおよび調剤データがモニターされ、健康管理プロバイダに潜在的なADEが警告される。」と記載されている(要約参照)。 As a background art in this technical field, there is JP-A-2002-342484 (Patent Document 1). Patent Document 1 states that “the present invention includes a system for predicting possible drug side effects by using a search engine that compares integrated data from laboratory and pharmacy information systems. Is compared to a predetermined ADE that defines the normal range for a particular laboratory test, and if an abnormal test value is received and a drug in the patient's drug regimen satisfies a drug included in the ADE rules, To determine if the procedure has been triggered and the patient's examination and dispensing data are taking appropriate corrective action, no corrective action being taken during that period, or improper corrective action being taken Patient test data and dispensing data are monitored and health care providers are alerted of potential ADEs. " About reference).
 特許文献1:特開2002-342484号公報 Patent Document 1: Japanese Patent Application Laid-Open No. 2002-342484
 近年、高齢化、長寿命化に伴い、医療費の拡大が世界的な社会問題となっている。このような背景のもと、政府機関、保険者、及び病院では、医療の質を維持しつつ、医療費を抑制する診療プロセスの最適化が強く求められている。このような診療プロセスの分析支援について、診療データを用いて、医薬品等の効果又は副作用を分析する情報システムが検討されている。上記の特許文献1はその一例である。 In recent years, the expansion of medical expenses has become a global social problem as the population ages and the life span increases. Against this background, government agencies, insurers, and hospitals are strongly required to optimize medical processes that maintain medical quality while reducing medical costs. With regard to support for analysis of such a medical process, an information system that analyzes effects or side effects of pharmaceuticals using medical data is being studied. Said patent document 1 is the example.
 しかし、上記のような従来の技術では、病名の診断から治療に至る診療プロセスを網羅的に把握することは、困難である。特に、多種多様な投薬治療において、治療効果及び副作用を網羅的に把握し、適切な薬剤が選択されているか、副作用等で入院期間が増えていないか等、がわからない、という課題があった。 However, with the conventional techniques as described above, it is difficult to comprehensively grasp the medical treatment process from diagnosis of disease name to treatment. In particular, in a wide variety of medications, there is a problem that the therapeutic effect and side effects are comprehensively grasped and it is not known whether an appropriate drug is selected or whether the hospitalization period has increased due to side effects or the like.
 本発明の目的は、多種多様な投薬治療において、個々の薬剤の効果、副作用、及び医療費等の位置づけ(ドラッグポジション)を可視化し、適切な投薬治療を支援する情報システムを提供することである。 An object of the present invention is to provide an information system that visualizes the position (drug position) of effects, side effects, medical expenses, etc. of individual drugs in a wide variety of medications and supports appropriate medications. .
 上記の課題を解決するために、本発明は、プロセッサと、前記プロセッサに接続される記憶装置と、を備える分析システムであって、前記記憶装置は、各患者の疾患及び入院期間を示す症例情報と、前記各患者への各薬の処方期間を示す処方情報と、前記各患者の検査結果を示す検査情報と、前記検査結果に基づく副作用の判定条件を示す知識情報と、を保持し、前記プロセッサは、前記疾患ごとに、前記各患者の検査結果が前記副作用の判定条件を満たした時期と、前記各患者への前記各薬の処方期間と、の関係に基づいて、副作用の原因となった薬を推定し、前記推定の結果を出力することを特徴とする。 In order to solve the above problems, the present invention is an analysis system comprising a processor and a storage device connected to the processor, wherein the storage device indicates case information indicating the disease and hospitalization period of each patient. And prescription information indicating the prescription period of each drug to each patient, test information indicating the test result of each patient, and knowledge information indicating determination conditions for side effects based on the test results, For each disease, the processor causes a side effect based on the relationship between the time when the test result of each patient satisfies the determination condition for the side effect and the prescription period of each drug for each patient. The medicine is estimated and the result of the estimation is output.
 本発明の一形態によれば、薬剤毎の副作用等が提示されるため、適切な薬剤が選択されているか否かを簡単に把握でき、適切な投薬治療等、診療プロセスの最適化を支援できる。 According to one aspect of the present invention, since side effects for each drug are presented, it is possible to easily grasp whether or not an appropriate drug has been selected, and to support optimization of a medical process such as appropriate medication. .
 上記以外の課題、構成及び効果は、以下の実施形態の説明によって明らかにされる。 Issues, configurations, and effects other than those described above will be clarified by the following description of the embodiments.
本発明の実施例のドラッグポジショニング可視化システムの構成を示すブロック図である。It is a block diagram which shows the structure of the drug positioning visualization system of the Example of this invention. 本発明の実施例の症例データベースの例の説明図である。It is explanatory drawing of the example of the case database of the Example of this invention. 本発明の実施例の知識データベースの例の説明図である。It is explanatory drawing of the example of the knowledge database of the Example of this invention. 本発明の実施例のデータサーバの動作を示すフローチャートである。It is a flowchart which shows operation | movement of the data server of the Example of this invention. 本発明の実施例の副作用判定部が副作用インデックスを算出する分析処理を実行するときの動作を示すフローチャートである。It is a flowchart which shows operation | movement when the side effect determination part of the Example of this invention performs the analysis process which calculates a side effect index. 本発明の実施例において、ユーザが分析および可視化の対象とする疾患を選択するときに入出力端末が表示する疾患選択画面の例の説明図である。In the Example of this invention, when a user selects the disease made into analysis and visualization, it is explanatory drawing of the example of the disease selection screen which an input / output terminal displays. 本発明の実施例の入出力端末が分析処理の結果を表示する画面例の説明図である。It is explanatory drawing of the example of a screen which the input / output terminal of the Example of this invention displays the result of an analysis process. 本発明の実施例の入出力端末が症例データを表示する画面例の説明図である。It is explanatory drawing of the example of a screen which the input / output terminal of the Example of this invention displays case data.
 図1は、本発明の実施例のドラッグポジショニング可視化システムの構成を示すブロック図である。 FIG. 1 is a block diagram showing a configuration of a drug positioning visualization system according to an embodiment of the present invention.
 本実施例のドラッグポジショニング可視化システムは、個々の薬剤の効果、副作用、及び医療費等の位置づけ(ドラッグポジション)を分析し、その結果を可視化して出力する計算機システムであり、データサーバ100と、ネットワーク140と、ユーザが利用する入出力端末120と、によって構成される。 The drug positioning visualization system of the present embodiment is a computer system that analyzes the position (drug position) of the effect, side effect, medical cost, etc. of each drug, visualizes the result, and outputs the result. The network 140 and the input / output terminal 120 used by the user are configured.
 本実施例では、入出力端末120は、キーボード、マウス、又はタッチパネルなどの入力部(図示省略)と、ディスプレイなどの出力部(図示省略)と、データサーバ100などと通信する通信部(図示省略)と、を有する1つまたは複数のパーソナルコンピュータである。また、ボタンまたはタッチパネルなどの入力部とディスプレイなどの出力部と、データサーバ100などと通信する通信部とを有するPDA、PHS、携帯電話、スマートフォン、またはタブレット端末などの可搬型端末を入出力端末120として利用することもできる。 In this embodiment, the input / output terminal 120 includes an input unit (not shown) such as a keyboard, mouse, or touch panel, an output unit (not shown) such as a display, and a communication unit (not shown) that communicates with the data server 100 and the like. ) And one or more personal computers. In addition, a portable terminal such as a PDA, PHS, mobile phone, smartphone, or tablet terminal having an input unit such as a button or a touch panel, an output unit such as a display, and a communication unit that communicates with the data server 100 or the like is an input / output terminal. 120 can also be used.
 本システムでは、入出力端末120を、病院もしくは診療所などの医療機関(ヘルスケアプロバイダ)、国、健康保険組合、または民間保険会社などの保険者に設置して利用する。一方、データサーバ100がデータセンターに設置される。 In this system, the input / output terminal 120 is installed and used in an insurer such as a medical institution (health care provider) such as a hospital or clinic, a country, a health insurance association, or a private insurance company. On the other hand, the data server 100 is installed in the data center.
 このように、データサーバ100をデータセンターに設置することで、ユーザの個人情報およびユーザから収集されるデータなどのプライバシー情報を一元管理できるので、情報漏洩防止等のセキュリティ管理を簡易化できる。 As described above, by installing the data server 100 in the data center, the user's personal information and privacy information such as the data collected from the user can be centrally managed, so that security management such as information leakage prevention can be simplified.
 入出力端末120の利用者(以下ユーザと記載する)としては、医療機関又は保険者の医師、管理者又は経営責任者を想定している。 As a user (hereinafter referred to as a user) of the input / output terminal 120, a doctor, manager or manager of a medical institution or insurer is assumed.
 ユーザは、入出力端末120を操作し、本実施例で示される情報システムを用いて、処方薬の効果、副作用、および医療費の分析および可視化を実施する。 The user operates the input / output terminal 120 and uses the information system shown in this embodiment to analyze and visualize the effects, side effects, and medical costs of prescription drugs.
 データサーバ100は、相互に接続された制御部101、メモリ102、通信部103、診療データ取得部104、医療費データ取得部105、出力部107、疾患情報選択部108、症例データ抽出部109、処方データ抽出部111、検査データ抽出部112、効果判定部113、副作用判定部114、医療費算出部115、画面生成部116、症例データベース117および知識データベース119によって構成される。 The data server 100 includes a control unit 101, a memory 102, a communication unit 103, a medical data acquisition unit 104, a medical cost data acquisition unit 105, an output unit 107, a disease information selection unit 108, a case data extraction unit 109, The prescription data extraction unit 111, the examination data extraction unit 112, the effect determination unit 113, the side effect determination unit 114, the medical cost calculation unit 115, the screen generation unit 116, the case database 117, and the knowledge database 119 are configured.
 制御部101は、例えばメモリ102に格納されたプログラムを実行するプロセッサであり、データサーバ100の各部を制御する。メモリ102は、例えばDRAM(Dynamic Random Access Memory)のような記憶装置であり、データサーバ100の各部によって参照されるデータ(例えば制御部101によって実行されるプログラム等)を格納する。 The control unit 101 is a processor that executes a program stored in the memory 102, for example, and controls each unit of the data server 100. The memory 102 is a storage device such as a DRAM (Dynamic Random Access Memory), for example, and stores data (for example, a program executed by the control unit 101) referred to by each unit of the data server 100.
 症例データベース117および知識データベース119は、メモリ102に格納されてもよいし、例えばHDD(Hard Disk Drive)のような、データサーバ100内の別の記憶装置(図示省略)に格納されてもよい。 The case database 117 and the knowledge database 119 may be stored in the memory 102 or may be stored in another storage device (not shown) in the data server 100 such as an HDD (Hard Disk Drive).
 通信部103は、ネットワーク140に接続され、入出力端末120との通信を行う。 The communication unit 103 is connected to the network 140 and communicates with the input / output terminal 120.
 出力部107は、データサーバ100による処理の結果を出力する装置であり、例えばディスプレイ装置であってもよい。 The output unit 107 is a device that outputs a result of processing by the data server 100, and may be a display device, for example.
 診療データ取得部104、医療費データ取得部105、疾患情報選択部108、症例データ抽出部109、処方データ抽出部111、検査データ抽出部112、効果判定部113、副作用判定部114、医療費算出部115および画面生成部116は、データサーバ100の機能を実現するための処理を実行する処理部であり、それぞれが専用のハードウェアによって実現されてもよいし、ソフトウェアによって実現されてもよい。後者の場合、以下の説明において上記の各処理部が実行する処理は、実際には、制御部101がメモリ102に格納されたプログラムに記述された命令に従って実行する。上記の各処理部によって実行される処理の詳細については後述する。 Medical data acquisition unit 104, medical cost data acquisition unit 105, disease information selection unit 108, case data extraction unit 109, prescription data extraction unit 111, examination data extraction unit 112, effect determination unit 113, side effect determination unit 114, medical cost calculation The unit 115 and the screen generation unit 116 are processing units that execute processing for realizing the functions of the data server 100, and each may be realized by dedicated hardware or may be realized by software. In the latter case, the processing executed by each processing unit in the following description is actually executed by the control unit 101 in accordance with an instruction described in a program stored in the memory 102. Details of the processing executed by each processing unit will be described later.
 ネットワーク140には、データサーバ100および入出力端末120が接続されている。データサーバ100は、ネットワーク140を介して入出力端末120と通信する。 The data server 100 and the input / output terminal 120 are connected to the network 140. The data server 100 communicates with the input / output terminal 120 via the network 140.
 ネットワーク140は、LAN(Local Area Network)ケーブルによる有線通信、または無線LANによる無線通信を利用する。 The network 140 uses wired communication using a LAN (Local Area Network) cable or wireless communication using a wireless LAN.
 また、ネットワーク140は、インターネット、VPN、携帯電話通信網、PHS通信網など、他の広域ネットワークを利用することもできる。 The network 140 can also use other wide area networks such as the Internet, VPN, mobile phone communication network, and PHS communication network.
 図2は、本発明の実施例の症例データベース117の例200の説明図である。 FIG. 2 is an explanatory diagram of an example 200 of the case database 117 according to the embodiment of this invention.
 症例データベース例200は、症例毎の基本情報等を管理する症例情報テーブル210と、症例毎の処方情報を格納する処方情報テーブル220と、症例毎の臨床検査情報を格納する臨床検査情報テーブル230と、症例毎の画像検査情報を格納する画像検査情報テーブル240と、処方、臨床検査、画像検査、および手術等の処置などの診療行為について、診療行為毎の保険請求費用および原価などのコスト情報を格納するコスト情報テーブル250と、で構成される。 The case database example 200 includes a case information table 210 for managing basic information for each case, a prescription information table 220 for storing prescription information for each case, a clinical test information table 230 for storing clinical test information for each case, , Image examination information table 240 for storing image examination information for each case, and cost information such as insurance claim costs and costs for each medical practice for medical practice such as prescription, clinical examination, image examination, and surgery. And a cost information table 250 to be stored.
 症例情報テーブル210は、患者を識別する患者IDを格納するフィールド211と、医療機関の入院日を格納するフィールド212と、退院日を格納するフィールド213と、疾患名を格納するフィールド214と、退院時の転帰情報を格納するフィールド215と、で構成される。症例情報テーブル210の各レコード(症例情報レコード)に、一つの症例に関する情報が格納される。一人の患者の1回の入院が一つの症例に対応する。例えば、図2に示した症例情報テーブル210の症例情報レコードの例210Aは、患者ID「Pt-0001」で識別される症例は、入院日「2012年12月12日」、退院日「2012年12月20日」であり、疾患名「肺がん」、転帰「治癒」であること(すなわち、患者ID「Pt-0001」で識別される患者が、肺がんの治療のために2012年12月12日から2012年12月20日まで入院し、その結果、肺がんが治癒したこと)を示している。 The case information table 210 includes a field 211 for storing a patient ID for identifying a patient, a field 212 for storing a hospitalization date of a medical institution, a field 213 for storing a discharge date, a field 214 for storing a disease name, and discharge. And a field 215 for storing time outcome information. Information on one case is stored in each record (case information record) of the case information table 210. One hospitalization of one patient corresponds to one case. For example, in the case information record example 210A of the case information table 210 shown in FIG. 2, the case identified by the patient ID “Pt-0001” is the hospitalization date “December 12, 2012” and the discharge date “2012”. December 20, 2012, with a disease name of “lung cancer” and an outcome of “cure” (ie, a patient identified with patient ID “Pt-0001” is treated on December 12, 2012 for treatment of lung cancer. To December 20, 2012, and as a result, lung cancer was cured.
 処方情報テーブル220は、患者IDを格納するフィールド221と、処方薬を識別する情報を格納するフィールド222と、処方日を格納するフィールド223と、処方された期間の長さを格納するフィールド224と、用法・用量を格納するフィールド225と、で構成される。例えば、図2に示した処方情報テーブル220の例は、患者ID「Pt-0001」の症例において、薬Aと薬Bが2012年12月12日からそれぞれ5日間(すなわち12月12日から16日までの期間に)処方され、薬Cが2012年12月15日から3日間(すなわち12月15日から17日までの期間に)処方されたことを示している。 The prescription information table 220 includes a field 221 for storing a patient ID, a field 222 for storing information for identifying a prescription drug, a field 223 for storing a prescription date, and a field 224 for storing the length of a prescribed period. And a field 225 for storing a usage / dose. For example, in the example of the prescription information table 220 shown in FIG. 2, in the case of the patient ID “Pt-0001”, the medicine A and the medicine B are each 5 days from December 12, 2012 (that is, from December 12 to 16). This shows that medication C was prescribed for 3 days from December 15, 2012 (ie, during the period from December 15 to 17).
 臨床検査情報テーブル230は、患者IDを格納するフィールド231と、検査項目を識別する情報を格納するフィールド232と、検査日を格納するフィールド233と、検査結果を格納するフィールド234と、で構成される。例えば、図2に示す臨床検査情報テーブル230の例は、患者ID「Pt-0001」の症例において、肝機能の状態を示す検査項目である、AST(GOT)およびALT(GPT)の値が、2012年12月12日に、それぞれ「28」および「29」であり、2012年12月15日に、それぞれ「49」および「71」であったことを示している。 The clinical test information table 230 includes a field 231 for storing a patient ID, a field 232 for storing information for identifying a test item, a field 233 for storing a test date, and a field 234 for storing a test result. The For example, in the example of the clinical test information table 230 shown in FIG. 2, in the case of the patient ID “Pt-0001”, the values of AST (GOT) and ALT (GPT), which are test items indicating the liver function state, On December 12, 2012, they are “28” and “29”, respectively, and on December 15, 2012, they are “49” and “71”, respectively.
 画像検査情報テーブル240は、患者IDを格納するフィールド241と、検査項目を識別する情報を格納するフィールド242と、検査日を格納するフィールド243と、画像診断の結果である所見情報を格納するフィールド244と、で構成される。例えば、図2に示す画像検査情報テーブル240の例は、患者ID「Pt-0001」の症例において、肺の状態を診断する検査項目である、肺CT(Computed Tomography)の検査所見に関して、2012年12月12日に、「腫瘍Aが10.2mm」であり、2012年12月15日に、「腫瘍Aが9.1mm」であったことを示している。 The image examination information table 240 includes a field 241 for storing a patient ID, a field 242 for storing information for identifying an examination item, a field 243 for storing an examination date, and a field for storing observation information as a result of image diagnosis. 244. For example, in the example of the image inspection information table 240 shown in FIG. 2, in the case of the patient ID “Pt-0001”, 2012 regarding the examination findings of lung CT (Computed Tomography), which is an examination item for diagnosing the lung state. It is shown that “Tumor A was 10.2 mm” on December 12, and “Tumor A was 9.1 mm” on December 15, 2012.
 上記の臨床検査情報テーブル230および画像検査情報テーブル240は、各患者に対して実際に行われた検査の結果を示す情報の例である。この例では、主に血液検査の結果を含む臨床検査情報テーブル230と、CT等の画像に基づく検査の結果を含む画像検査情報テーブル240とが独立しているが、これらの情報が一つのテーブルに含まれてもよい。また、症例データベース117には、各患者に対して行われた上記以外の種類の検査の結果を示す情報が含まれてもよく、さらに、「吐き気」または「嘔吐」といった患者の自覚症状に関する情報が含まれてもよい。 The above-described clinical examination information table 230 and image examination information table 240 are examples of information indicating the results of examinations actually performed on each patient. In this example, a clinical test information table 230 mainly including blood test results and an image test information table 240 including test results based on images such as CT are independent. May be included. In addition, the case database 117 may include information indicating the results of other types of examinations performed on each patient, and further information related to the patient's subjective symptoms such as “nausea” or “vomiting” May be included.
 コスト情報テーブル250は、診療行為を識別する診療行為IDを格納するフィールド251と、診療行為の名称を格納するフィールド252と、診療行為を実施した時に保険請求できる保険点数、すなわち保険請求できる費用情報を格納するフィールド253と、診療行為の原価、すなわち診療行為を実施した時の原価を格納するフィールド254と、で構成される。コスト情報テーブル250の各レコード(診療行為レコード)に、一つの診療行為に関する情報が格納される。例えば、図2に示す診療行為レコード250Aの場合、診療行為ID「P0010001」で識別される診療行為「薬A」は、保険点数「a」点、原価「x」円となる。なお、日本国内の場合、保険請求費用は保険点数1点あたり10円で換算される。このため、原価「x」円は、保険点数「a」点の場合の保険請求費用、すなわち「a×10」円となる。 The cost information table 250 includes a field 251 for storing a medical practice ID for identifying a medical practice, a field 252 for storing the name of the medical practice, and the number of insurance points that can be claimed when the medical practice is performed, that is, cost information that can be claimed. And a field 254 for storing the cost of the medical practice, that is, the cost when the medical practice is performed. Information on one medical practice is stored in each record (medical practice record) of the cost information table 250. For example, in the case of the medical practice record 250A shown in FIG. 2, the medical practice “drug A” identified by the medical practice ID “P0010001” has an insurance score “a” and a cost “x” yen. In Japan, insurance claim costs are converted at 10 yen per insurance point. Therefore, the cost “x” yen is the insurance claim cost when the insurance score is “a”, that is, “a × 10” yen.
 原価は、本システムを利用する医療機関における、診療行為に必要な処方薬(薬剤)、検査に用いられる試薬、および、手術または処置に用いられる医療部材等の購入費を想定しているが、診療行為を実施する場合の医師等の医療スタッフの人件費、および、画像診断装置等の医療機器の減価償却費などを含むこともできる。 The cost assumes the purchase cost of prescription drugs (drugs) necessary for medical practice, reagents used for testing, and medical materials used for surgery or treatment in medical institutions that use this system. It can also include personnel costs of medical staff such as doctors when performing medical practice, and depreciation costs of medical equipment such as diagnostic imaging devices.
 図3は、本発明の実施例の知識データベース119の例300の説明図である。 FIG. 3 is an explanatory diagram of an example 300 of the knowledge database 119 according to the embodiment of this invention.
 知識ベースの例300は、処方薬知識テーブル310と、副作用知識テーブル320と、で構成される。 The knowledge base example 300 includes a prescription drug knowledge table 310 and a side effect knowledge table 320.
 処方薬知識テーブル310は、処方薬を識別する情報を格納するフィールド311と、処方薬が適用できる疾患を識別する情報を格納するフィールド312と、処方薬の効果が表れる検査結果または所見等を特定する情報を格納するフィールド313と、処方薬の副作用の検査結果または所見等を特定する情報を格納するフィールド314と、で構成される。 The prescription drug knowledge table 310 specifies a field 311 for storing information for identifying a prescription drug, a field 312 for storing information for identifying a disease to which the prescription drug can be applied, and a test result or finding showing the effect of the prescription drug. A field 313 for storing information to be stored, and a field 314 for storing information for specifying test results or findings of side effects of prescription drugs.
 処方薬知識テーブル310の各レコード(処方薬知識レコード)に、一つの処方薬に関する情報が格納される。例えば、処方薬知識レコード310Aの場合、処方薬「薬A」は、「肺がん」治療に適用でき(フィールド312)、効果は「腫瘍サイズ」の改善(フィールド313)、副作用は「肝機能」のうち検査項目「ALT(GPT)」の悪化である(フィールド314)ことを示している。 Information about one prescription drug is stored in each record (prescription drug knowledge record) of the prescription drug knowledge table 310. For example, in the case of the prescription drug knowledge record 310A, the prescription drug “drug A” can be applied to the treatment of “lung cancer” (field 312), the effect is the improvement of “tumor size” (field 313), and the side effect is “liver function”. Of these, the inspection item “ALT (GPT)” is deteriorated (field 314).
 副作用知識テーブル320は、検査結果等に基づく副作用の判定条件を示す情報を含み、具体的には、検査または自覚症状などの副作用を示す項目を識別する情報を格納するフィールド321と、副作用を示す項目のそれぞれについて異常状態を判定するための知識を格納するフィールド322と、副作用を示す項目のそれぞれについて危険状態を判定するための知識を格納するフィールド323と、で構成される。 The side effect knowledge table 320 includes information indicating a side effect determination condition based on a test result or the like. Specifically, the side effect knowledge table 320 stores a field 321 for storing information for identifying an item indicating a side effect such as a test or a subjective symptom, and a side effect. The field 322 stores knowledge for determining an abnormal state for each item, and the field 323 stores knowledge for determining a dangerous state for each item indicating a side effect.
 副作用知識テーブル320の各レコード(副作用知識レコード)に、一つの検査項目に関する情報が格納される。例えば、副作用知識レコード320Aの場合、検査項目「ALT(GPT)」が、45以上のとき「異常状態」を示す異常値、100以上のとき「危険状態」を示す危険値であることを示している。 Information related to one examination item is stored in each record (side effect knowledge record) of the side effect knowledge table 320. For example, in the case of the side effect knowledge record 320A, when the inspection item “ALT (GPT)” is 45 or more, it indicates an abnormal value indicating “abnormal condition”, and when it is 100 or more, it indicates a dangerous value indicating “dangerous condition”. Yes.
 また、例えば、副作用知識レコード320Bの場合、検査項目「消化器症状」が、「吐き気」のとき「異常状態」、「嘔吐」のとき「危険状態」であることを示している。 Also, for example, in the case of the side effect knowledge record 320B, it indicates that the test item “digestive symptom” is “abnormal state” when “nausea”, and “dangerous state” when “vomiting”.
 なお、異常状態および危険状態は、いずれも、処方薬の副作用に起因することが疑われる検査結果の異常が発生した状態であるが、危険状態は、異常状態より程度の大きい異常が発生した状態である。上記の例では、一つの副作用知識レコードに一つの検査項目の検査結果に基づく副作用の判定条件が格納される。具体的には、フィールド322に異常状態を判定するための基準が、フィールド323に危険状態を判定するための基準が、それぞれ格納される。 The abnormal state and the dangerous state are both states in which abnormalities in test results suspected to be caused by the side effects of prescription drugs have occurred, but the dangerous state is a state in which an abnormality greater than the abnormal state has occurred. It is. In the above example, the side effect determination condition based on the test result of one test item is stored in one side effect knowledge record. Specifically, a criterion for determining an abnormal state is stored in the field 322, and a criterion for determining a dangerous state is stored in the field 323, respectively.
 このように、検査結果の項目ごとに、異常状態および危険状態を判定するための2つの知識(基準)を有することで、薬の処方をそのまま継続してよいか、副作用が表れる検査結果等をモニタリングしながら処方を継続するか、または処方を中断すべきか、など処方に関する診療プロセスの判断を支援することができる。例えば、医師は、ある薬を処方した結果、患者が異常状態にならなければ処方をそのまま継続し、異常状態となった場合には副作用が表れる検査結果等をモニタリングしながら処方を継続し、危険状態となった場合にはただちに処方を中断する、といった判断を行ってもよい。 In this way, for each item of the test result, having two knowledge (standards) for determining the abnormal state and the dangerous state, the prescription of the medicine can be continued as it is, or the test result showing a side effect is displayed. It can assist the judgment of the prescription medical process, such as whether to continue the prescription while monitoring, or to stop the prescription. For example, if a doctor prescribes a drug and the patient does not become abnormal, the prescription is continued as it is, and if the patient becomes abnormal, the prescription is continued while monitoring test results that show side effects. A determination may be made that the prescription is interrupted immediately when the condition is reached.
 次に、本システムの動作を、フローチャートを用いて説明する。 Next, the operation of this system will be described using a flowchart.
 図4は、本発明の実施例のデータサーバ100の動作を示すフローチャートである。 FIG. 4 is a flowchart showing the operation of the data server 100 according to the embodiment of this invention.
 まず、制御部101は、症例データベース117から症例データを読み出し、メモリ102に記憶するステップ401を実行する。ここでは、症例に関するデータ、例えば症例を識別する情報、症例に対応する処方薬の情報、症例に対応する検査結果の情報等を総称して症例データと記載する。例えば、制御部101は、ステップ401において、症例データベース117に含まれる全データを読み出し、メモリ102に記憶してもよい。 First, the control unit 101 executes step 401 in which case data is read from the case database 117 and stored in the memory 102. Here, data related to cases, for example, information for identifying cases, information on prescription drugs corresponding to cases, information on test results corresponding to cases, and the like are collectively referred to as case data. For example, the control unit 101 may read all data included in the case database 117 and store it in the memory 102 in step 401.
 次に、制御部101は、知識データベース119から知識データを読み出し、メモリ102に記憶するステップ402を実行する。例えば、制御部101は、ステップ402において、知識データベース119に含まれる全データを読み出し、メモリ102に記憶してもよい。 Next, the control unit 101 reads out the knowledge data from the knowledge database 119 and executes step 402 for storing it in the memory 102. For example, the control unit 101 may read all data included in the knowledge database 119 and store it in the memory 102 in step 402.
 次に、制御部101は、疾患情報選択部108を起動する。疾患情報選択部108は、ユーザに分析および可視化の対象とする疾患を選択させるステップ403を実行する。以下、ステップ403で選択された疾患を、対象疾患と記載する場合がある。疾患情報選択部108がステップ403を実行すると、疾患選択画面が入出力端末120に表示される。 Next, the control unit 101 activates the disease information selection unit 108. The disease information selection unit 108 executes step 403 that allows the user to select a disease to be analyzed and visualized. Hereinafter, the disease selected in step 403 may be described as a target disease. When the disease information selection unit 108 executes step 403, a disease selection screen is displayed on the input / output terminal 120.
 図6は、本発明の実施例において、ユーザが分析および可視化の対象とする疾患を選択するときに入出力端末120が表示する疾患選択画面の例600の説明図である。 FIG. 6 is an explanatory diagram of an example 600 of a disease selection screen displayed by the input / output terminal 120 when the user selects a disease to be analyzed and visualized in the embodiment of the present invention.
 画面例600は、疾患選択ボックス611と、実行ボタン613と、処方薬表示エリア620と、で構成される。 The screen example 600 includes a disease selection box 611, an execution button 613, and a prescription drug display area 620.
 ユーザは疾患選択ボックス611に付属するドロップダウンボタン612を操作し、ドロップダウンリスト(図示省略)に表示される複数の疾患から分析および可視化をする疾患を選択する。あるいは、ユーザは、疾患選択ボックス611に、直接疾患名を入力することもできる。 The user operates a drop-down button 612 attached to the disease selection box 611, and selects a disease to be analyzed and visualized from a plurality of diseases displayed in a drop-down list (not shown). Alternatively, the user can directly input a disease name in the disease selection box 611.
 ここで、ユーザが実行ボタン613を選択すると、制御部101は、症例データ抽出部109を起動する。症例データ抽出部109は、メモリ102に記憶された症例データベース117から、ステップ403で選択された疾患に対応する症例を抽出するステップ404を実行する。例えば、症例データ抽出部109は、症例情報テーブル210を参照し、ステップ403で選択された疾患名がフィールド214に格納されている症例情報レコードに記載された症例(すなわち患者と入院期間の組)を全て抽出する。 Here, when the user selects the execute button 613, the control unit 101 activates the case data extraction unit 109. The case data extraction unit 109 executes Step 404 for extracting a case corresponding to the disease selected in Step 403 from the case database 117 stored in the memory 102. For example, the case data extraction unit 109 refers to the case information table 210, and the case described in the case information record in which the disease name selected in step 403 is stored in the field 214 (that is, a combination of the patient and the hospitalization period) Are all extracted.
 次に、制御部101は、処方データ抽出部111を起動する。処方データ抽出部111は、ステップ404で抽出された症例に対応する処方データを抽出するステップ405を実行する。例えば、処方データ抽出部111は、ステップ404で抽出した各症例情報レコードから各症例の患者IDおよび入院期間を特定し、特定した患者IDと同一の患者IDがフィールド221に格納され、かつ、特定した入院期間内の処方日がフィールド223に格納されている処方情報テーブル220のレコード(処方情報レコード)を抽出してもよい。 Next, the control unit 101 activates the prescription data extraction unit 111. The prescription data extraction unit 111 executes step 405 for extracting prescription data corresponding to the case extracted in step 404. For example, the prescription data extraction unit 111 identifies the patient ID and hospitalization period of each case from each case information record extracted in step 404, and stores the same patient ID as the identified patient ID in the field 221. The record (prescription information record) of the prescription information table 220 in which the prescription date within the hospitalization period that has been stored in the field 223 may be extracted.
 これによって、対象疾患に対して処方された全ての処方薬を抽出することができ、分析および可視化を簡易かつ網羅的に実施することができる。 This makes it possible to extract all prescription drugs prescribed for the target disease, and to perform analysis and visualization easily and comprehensively.
 ステップ405において、処方データ抽出部111は、上記の方法とは別の方法によって処方データを抽出してもよい。例えば、処方データ抽出部111は、ステップ402でメモリ102に記憶された知識データベース300の処方薬知識テーブル310を用い、ステップ403で選択された疾患(対象疾患)をもとに適用疾患フィールド312を検索し、対象疾患と一致する適用疾患フィールド312の値を有する一つ以上の処方薬知識レコードの処方薬フィールド311に格納された一つ以上の処方薬を、処方データとして抽出することもできる。 In step 405, the prescription data extraction unit 111 may extract prescription data by a method different from the above method. For example, the prescription data extraction unit 111 uses the prescription drug knowledge table 310 of the knowledge database 300 stored in the memory 102 in step 402, and sets the applicable disease field 312 based on the disease (target disease) selected in step 403. One or more prescription drugs stored in the prescription drug field 311 of one or more prescription drug knowledge records having a value in the applicable disease field 312 that matches the target disease can be extracted as prescription data.
 これによって、予め設定された処方薬のみを抽出することができ、分析および可視化を効率的に実施することができる。 This makes it possible to extract only prescription drugs set in advance, and to efficiently perform analysis and visualization.
 次に、制御部101は、ステップ405で抽出された処方データに記載された処方薬毎に、全ての処方薬について後述するステップ407からステップ409の分析処理が終了したか否かを判定し、一つ以上の未処理の処方薬がある場合にはそれらの一つを分析処理の対象として選択するステップ406を実行する。 Next, the control unit 101 determines whether or not the analysis processing from step 407 to step 409, which will be described later, is completed for all prescription drugs for each prescription drug described in the prescription data extracted in step 405, If there are one or more unprocessed prescription drugs, step 406 is performed to select one of them as an analysis target.
 ステップ406で、分析処理が終了していない処方薬があると判定された場合、制御部101は、未処理の処方薬の一つ(以下、これを、対象とする処方薬とも記載する)についてステップ407からステップ409の分析処理を実行する。ステップ407において、制御部101は、検査データ抽出部112を起動する。検査データ抽出部112は、処方薬知識テーブル310を用い、処方薬と関連した効果または副作用が表れる検査データを、ステップ404で抽出された症例に基づいて抽出する。 When it is determined in step 406 that there is a prescription drug whose analysis processing has not been completed, the control unit 101 determines one of unprocessed prescription drugs (hereinafter also referred to as a target prescription drug). The analysis processing from step 407 to step 409 is executed. In step 407, the control unit 101 activates the inspection data extraction unit 112. The test data extraction unit 112 uses the prescription drug knowledge table 310 to extract test data showing effects or side effects related to the prescription drug based on the cases extracted in step 404.
 例えば、ステップ403で疾患として「肺がん」が選択され、ステップ406で処方薬「薬A」の分析処理が終了していないと判定された場合、検査データ抽出部112は、処方薬知識レコード310Aを参照して、薬Aの効果が「腫瘍サイズ」に表れ、副作用が「ALT(GPT)」に表れることを特定する。そして、検査データ抽出部112は、画像検査情報テーブル240から、肺CTの腫瘍サイズが格納されたレコードを、臨床検査情報テーブルからALT(GPT)が格納されたレコードを、それぞれ抽出する。 For example, if “lung cancer” is selected as the disease in step 403 and it is determined in step 406 that the analysis process for the prescription drug “drug A” has not been completed, the test data extraction unit 112 stores the prescription drug knowledge record 310A. By reference, it is specified that the effect of drug A appears in “tumor size” and the side effect appears in “ALT (GPT)”. Then, the examination data extraction unit 112 extracts a record storing the tumor size of the lung CT from the image examination information table 240 and a record storing ALT (GPT) from the clinical examination information table.
 次に、ステップ408において、制御部101は、効果判定部113を起動する。効果判定部113は、対象とする処方薬の効果インデックスを算出する。ここでは、例として、対象とする処方薬を「薬A」とする。 Next, in step 408, the control unit 101 activates the effect determination unit 113. The effect determination unit 113 calculates the effect index of the target prescription drug. Here, as an example, the target prescription drug is “medicine A”.
 例えば、効果判定部113は、数式(1)を用いて効果インデックスDEIを算出する。 For example, the effect determination unit 113 calculates the effect index DEI using Equation (1).
Figure JPOXMLDOC01-appb-M000001
Figure JPOXMLDOC01-appb-M000001
 ここで、効果判定部113は、効果が表れる検査結果等の入院時と退院時の差分に基づいて、改善した症例数を判定する。例えば、効果判定部113は、ステップ407で抽出された腫瘍サイズに関する各レコードの患者IDおよび検査日に基づいて各レコードに対応する症例を特定し、症例ごとに、入院時と退院時の腫瘍サイズを比較する。例えば、ある症例の「腫瘍サイズ」が入院時に「10.2mm」であり、退院時に「2.0mm」であった場合、処方の前後において腫瘍サイズの差分がある。この差分は、薬「A」の処方薬知識レコード310Aのフィールド313に格納されている効果である腫瘍サイズの減少と一致するため、効果判定部113は、当該症例を改善した症例としてカウントする。 Here, the effect determination unit 113 determines the number of improved cases based on the difference between the time of hospitalization and the time of discharge, such as a test result that shows the effect. For example, the effect determination unit 113 identifies a case corresponding to each record based on the patient ID and the examination date of each record related to the tumor size extracted in step 407, and the tumor size at the time of hospitalization and discharge at each case. Compare For example, when the “tumor size” of a case is “10.2 mm” at the time of hospitalization and “2.0 mm” at the time of discharge, there is a difference in tumor size before and after the prescription. Since this difference coincides with the decrease in tumor size, which is the effect stored in the field 313 of the prescription drug knowledge record 310A of the drug “A”, the effect determination unit 113 counts the case as an improved case.
 なお、効果が表れる検査結果等の差分は、薬の処方前の時点と処方後の時点との間で計算すればよく、上記の「入院時」および「退院時」はそれらの時点の一例である。例えば、患者がまだ退院していない症例においては、退院時の検査結果の代わりに最新の検査結果を用いてもよい。 In addition, the difference in the test results that show the effect may be calculated between the pre-prescription time and the post-prescription time point, and the above "on hospitalization" and "discharge time" are examples of those time points. is there. For example, in a case where the patient has not been discharged, the latest test result may be used instead of the test result at the time of discharge.
 また、対象疾患に処方された症例数APNとは、ステップ404で抽出された症例のうち、対象とする処方薬「薬A」を処方された症例の数である。 In addition, the number of cases APN prescribed for the target disease is the number of cases prescribed the target prescription drug “drug A” among the cases extracted in step 404.
 これによって計算される効果インデックスDEIは、対象疾患の患者に処方薬を処方したことによってその処方薬の効果が表れる確率である。ある処方薬の効果インデックスDEIが大きいことは、その処方薬の効果が表れたと推定される事例が発生する率が高いことを示している。このように、処方薬の効果について、複数の症例における処方情報および検査情報等を用いて効果を定量化した効果インデックスを用いることで、他の処方薬との比較を分析することができる。 The effect index DEI calculated by this is the probability that the effect of the prescription drug will appear by prescribing the prescription drug to the patient with the target disease. A large effect index DEI of a prescription drug indicates a high rate of occurrence of cases where it is estimated that the effect of the prescription drug has appeared. As described above, by using the effect index obtained by quantifying the effect using the prescription information and the test information in a plurality of cases, the comparison with other prescription drugs can be analyzed.
 上記の例では、効果判定部113は、検査結果等の差分を処方薬知識テーブル310に格納された効果と比較することによって効果インデックスを計算しているが、この方法は処方薬の効果の高さを示す指標である効果インデックスの計算方法の一例であり、効果判定部113は別の方法によって効果インデックスを計算してもよい。例えば、効果判定部113は、処方薬が処方された各患者の入院日から退院日までの「入院期間」を用いて効果インデックスを計算することもできる。具体的には、例えば、効果判定部113は、数式(1A)を用いて効果インデックスDEI_Aを算出してもよい。 In the above example, the effect determination unit 113 calculates the effect index by comparing the difference such as the test result with the effect stored in the prescription drug knowledge table 310, but this method has a high effect of the prescription drug. This is an example of a method for calculating an effect index, which is an index indicating the degree, and the effect determination unit 113 may calculate the effect index by another method. For example, the effect determination unit 113 can also calculate the effect index using the “hospitalization period” from the hospitalization date to the discharge date of each patient for whom the prescription drug is prescribed. Specifically, for example, the effect determination unit 113 may calculate the effect index DEI_A using the mathematical formula (1A).
Figure JPOXMLDOC01-appb-M000002
Figure JPOXMLDOC01-appb-M000002
 ある疾患とある処方薬の組に関して計算された効果インデックスDEI_Aの値が小さいほど、当該疾患に当該処方薬を処方した場合の患者の入院期間の平均値が小さい、すなわち当該処方薬の効果が大きかったと推定される。これは、処方薬の効果が大きいほど、患者の症状が早く改善され、その結果入院期間も短くなるとの推定に基づく。このように、治療効果の影響によって入院期間が変わる場合を考慮しつつ、処方薬の効果について他の処方薬との比較を分析することができる。 The smaller the value of the effect index DEI_A calculated for a given disease / prescription drug pair, the smaller the average value of the patient's hospital stay when prescribing the prescription drug for the disease, that is, the greater the effect of the prescription drug. It is estimated that This is based on the assumption that the greater the effect of the prescription drug, the faster the patient's symptoms will improve and the shorter the hospital stay will result. In this way, it is possible to analyze the comparison of prescription drugs with other prescription drugs while considering the case where the hospitalization period changes due to the effect of treatment effects.
 次に、ステップ409において、制御部101は、医療費算出部115を起動する。医療費算出部115は、対象とする処方薬の医療費を算出する。 Next, in step 409, the control unit 101 activates the medical cost calculation unit 115. The medical cost calculation unit 115 calculates the medical cost of the target prescription drug.
 例えば、医療費算出部115は、数式(2)を用いて医療費PRCを算出する。 For example, the medical cost calculation unit 115 calculates the medical cost PRC using Equation (2).
Figure JPOXMLDOC01-appb-M000003
Figure JPOXMLDOC01-appb-M000003
 このように計算される医療費PRCは、対象疾患の患者の入院期間中に処方される処方薬の医療費の総額の期待値である。このように、複数の症例における処方情報等を用いて処方薬の医療費を算出することで、他の処方薬との比較を分析することができる。 The medical cost PRC calculated in this way is an expected value of the total medical cost of the prescription drug prescribed during the hospitalization period of the patient with the target disease. Thus, by calculating the medical cost of a prescription drug using prescription information or the like in a plurality of cases, it is possible to analyze a comparison with other prescription drugs.
 処方薬の単価PUPとして、コスト情報テーブル250に記載された原価を用いることができる。これによって、医療機関毎の原価を用いた医療費の算出ができるので、その医療機関での他の処方薬との比較を正確に分析することができる。 The cost described in the cost information table 250 can be used as the unit price PUP of the prescription drug. Thereby, since the medical cost can be calculated using the cost for each medical institution, the comparison with other prescription drugs in the medical institution can be accurately analyzed.
 また、処方薬の単価PUPとして、コスト情報テーブル250に記載された保険点数または保険請求費用を用いることができる。これによって、原価が不明確な場合でも、他の処方薬との比較を簡単に分析することができる。また、保険点数および保険請求費用は日本を含む各国内で統一されているため、これらを用いて他の医療機関との比較を分析することも可能である。 Also, as the unit price PUP of the prescription drug, the insurance score or insurance claim cost described in the cost information table 250 can be used. This makes it easy to analyze the comparison with other prescription drugs even if the cost is unclear. In addition, since insurance scores and insurance claim costs are standardized in each country including Japan, it is possible to analyze comparisons with other medical institutions using these.
 処方薬の医療費については、数式(2)を用いない場合は、処方薬の単価のみを用いることもできる。 For the medical costs of prescription drugs, if the formula (2) is not used, only the unit price of prescription drugs can be used.
 ステップ406で、全ての処方薬について分析処理を終了したと判定されると、次に、制御部101は、副作用判定部114を起動する。副作用判定部114は、副作用インデックスを算出するステップ410を実行する。 If it is determined in step 406 that the analysis process has been completed for all prescription drugs, the control unit 101 then activates the side effect determination unit 114. The side effect determination unit 114 executes step 410 for calculating a side effect index.
 図5は、ステップ410において、本発明の実施例の副作用判定部114が副作用インデックスを算出する分析処理を実行するときの動作を示すフローチャートである。 FIG. 5 is a flowchart showing an operation when the side effect determination unit 114 according to the embodiment of the present invention executes an analysis process for calculating a side effect index in Step 410.
 図8は、本発明の実施例の入出力端末120が症例データを表示する画面例800の説明図である。 FIG. 8 is an explanatory diagram of a screen example 800 on which the input / output terminal 120 according to the embodiment of the present invention displays case data.
 画面例800は、入出力端末120がディスプレイなどの出力部(図示省略)に表示する画面の一例であり、臨床指標を表示するエリア810と、処方情報を表示するエリア820と、医療費情報を表示するエリア830と、で構成される。ここでは、画面生成部116が画面例800のデータを生成して、そのデータを通信部103がネットワーク140経由で送信し、そのデータを受信した入出力端末120が画面例800を出力部(図示省略)に表示する例を説明する。しかし、これはデータサーバ100による処理結果の出力の形態の一例であり、例えば出力部107が画面例800を表示してもよいし、データサーバ100が図4の処理の結果を通信部103から送信し、入出力端末120がその処理の結果をネットワーク140経由で受信し、それに基づいて画面例800を生成し、出力部(図示省略)に表示してもよい。 The screen example 800 is an example of a screen that the input / output terminal 120 displays on an output unit (not shown) such as a display. The screen 810 displays an area 810 that displays clinical indicators, an area 820 that displays prescription information, and medical cost information. Display area 830. Here, the screen generation unit 116 generates data of the screen example 800, the communication unit 103 transmits the data via the network 140, and the input / output terminal 120 receiving the data outputs the screen example 800 to the output unit (illustrated). An example of display in (omitted) will be described. However, this is an example of the output form of the processing result by the data server 100. For example, the output unit 107 may display the screen example 800, or the data server 100 sends the processing result of FIG. The input / output terminal 120 may receive the processing result via the network 140, generate the screen example 800 based on the result, and display the screen example on an output unit (not shown).
 臨床指標表示エリア810には、横軸に入院日から退院日までの経過日数を、縦軸に臨床指標の大きさを、それぞれ割り当て、効果が表れる検査結果等および副作用が表れる検査結果等をプロットしたグラフが表示される。さらに、このグラフ上に、副作用知識テーブル320の異常状態知識フィールド322に格納された異常値および危険状態知識フィールド323に格納された危険値が、それぞれ異常値判定ライン811および危険値判定ライン812として表示される。 In the clinical index display area 810, the horizontal axis represents the number of days elapsed from the date of hospitalization to the date of discharge, and the vertical axis represents the size of the clinical index. Plots of test results that show effects and test results that show side effects are plotted. Will be displayed. Further, on this graph, the abnormal value stored in the abnormal condition knowledge field 322 of the side effect knowledge table 320 and the dangerous value stored in the dangerous condition knowledge field 323 are respectively shown as an abnormal value determination line 811 and a dangerous value determination line 812. Is displayed.
 処方情報表示エリア820には、対象とする症例の入院日から退院日までに処方された処方薬の処方継続日数が表示される。図8の例では、横軸に入院日から退院日までの経過日数を割り当てたグラフ上に、それぞれの処方薬の処方期間が表示される。 In the prescription information display area 820, the prescription continuation days of prescription drugs prescribed from the hospitalization date to the discharge date of the target case are displayed. In the example of FIG. 8, the prescription period of each prescription drug is displayed on a graph in which the elapsed time from the hospitalization date to the discharge date is assigned to the horizontal axis.
 医療費情報表示エリア830には、対象とする症例の入院日から退院日までに処方された処方薬について、一日毎の処方薬の単価を合算した値が表示される。図8の例では、横軸に入院日から退院日までの経過日数を割り当て、縦軸に一日毎の処方薬の単価を合算した値を割り当てたグラフが表示される。 In the medical cost information display area 830, a value obtained by adding the unit prices of prescription drugs for each day for the prescription drugs prescribed from the hospitalization date to the discharge date of the target case is displayed. In the example of FIG. 8, a graph in which the elapsed time from the hospitalization date to the discharge date is assigned to the horizontal axis and the value obtained by adding the unit prices of prescription drugs for each day is assigned to the vertical axis.
 図8に示すように、上記の三つのグラフを同一画面上に並べて表示し、それらの横軸のスケールを同一にすることによって、それぞれの処方薬の処方期間と、効果又は副作用の発生時期と、費用との関係を容易に把握することが可能になる。 As shown in FIG. 8, the above three graphs are displayed side by side on the same screen, and by making the scales of the horizontal axes the same, the prescription period of each prescription drug, the time of occurrence of an effect or a side effect, and , It becomes possible to easily grasp the relationship with the cost.
 まず、副作用判定部114は、ステップ404で抽出された全ての症例について、後述するステップ502からステップ508の副作用分析処理が終了したか否かを判定し、未処理の症例が一つ以上ある場合には、未処理の症例の一つを副作用分析処理の対象として選択するステップ501を実行する。 First, the side effect determination unit 114 determines whether or not the side effect analysis processing from step 502 to step 508, which will be described later, has been completed for all cases extracted in step 404, and there are one or more unprocessed cases In step S501, one of unprocessed cases is selected as a target for the side effect analysis process.
 ステップ501において、いずれかの症例について副作用分析処理を実行すると判定されると、副作用判定部114は、副作用発生期間の抽出を行うステップ502を実行する。例えば、副作用判定部114は、画面例800に示すように、副作用に対応する検査データが異常値未満から異常値以上に変化したときを「副作用発生開始日」、副作用発生開始日以降で異常値以上から異常値未満に戻ったときを「副作用発生終了日」と判定し、副作用発生開始日から副作用発生終了日までを「副作用発生期間」と判定する。 If it is determined in step 501 that the side effect analysis processing is to be executed for any case, the side effect determination unit 114 executes step 502 for extracting a side effect occurrence period. For example, as shown in the screen example 800, the side effect determination unit 114 indicates that the test data corresponding to the side effect has changed from less than the abnormal value to more than the abnormal value as the “side effect occurrence start date”, and the abnormal value after the side effect occurrence start date. From the above, when it returns to less than the abnormal value, it is determined as the “side effect occurrence end date”, and from the side effect occurrence start date to the side effect occurrence end date is determined as the “side effect occurrence period”.
 なお、以下の説明において、検査データが異常値未満から異常値以上に変化したときから、その後、異常値以上から異常値未満に戻ったときまでの期間を「異常値発生期間」と記載する場合があり、検査データが危険値未満から危険値以上に変化したときから、その後、危険値以上から危険値未満に戻ったときまでの期間を「危険値発生期間」と記載する場合がある。 In the following explanation, the period from when the inspection data changes from less than the abnormal value to more than the abnormal value until when it returns from the abnormal value to less than the abnormal value is described as the “abnormal value occurrence period” In some cases, the period from when the inspection data changes from less than the dangerous value to more than the dangerous value until when the inspection data returns from more than the dangerous value to less than the dangerous value is referred to as the “dangerous value occurrence period”.
 次に、副作用判定部114は、副作用発生期間中に処方された処方薬を副作用原因薬剤候補として抽出するステップ503を実行する。具体的には、副作用判定部114は、一つの症例の入院期間中に処方された処方薬のうち、処方された期間が副作用発生期間と重複する処方薬を副作用原因薬剤候補として抽出する。画面例800の症例データの場合、処方薬から、副作用発生期間中に処方されていない「薬C」を除く、「薬A」「薬B」および「薬D」が副作用原因薬剤候補として抽出される。 Next, the side effect determination unit 114 executes step 503 for extracting a prescription drug prescribed during the side effect occurrence period as a side effect causative drug candidate. Specifically, the side effect determination unit 114 extracts prescription drugs whose prescription period overlaps with the side effect occurrence period among prescription drugs prescribed during the hospitalization period of one case as a side effect cause drug candidate. In the case data of screen example 800, “drug A”, “drug B”, and “drug D” are extracted from the prescription drugs as drug candidates that cause side effects, excluding “drug C” that is not prescribed during the side effect occurrence period. The
 次に、副作用判定部114は、検査データの変動を分析し、危険値発生日を判定するステップ504を実行する。画面例800の症例データの場合、副作用判定部114は、副作用に対応する検査データが危険値未満から危険値以上に変化したときを危険値発生日813として判定する。 Next, the side effect determination unit 114 analyzes the variation of the test data and executes Step 504 for determining the date of occurrence of the dangerous value. In the case data of the screen example 800, the side effect determination unit 114 determines the risk value occurrence date 813 when the test data corresponding to the side effect changes from less than the risk value to more than the risk value.
 次に、副作用判定部114は、危険値発生日前後での処方情報の変化の有無を判定し、処方情報に変化がない、即ち危険値発生日前後で継続的に処方されている処方薬を副作用原因薬剤候補から除外するステップ505を実行する。これは、一般に、ある薬を処方したことによって危険値が発生した場合、その時点で、医師がその薬の処方を中止すると考えられるためである。言い換えると、危険値発生日の前から処方されており、かつ、危険値発生日の後も継続的に処方された薬は、その薬を処方した医師によって、当該危険値の発生の原因ではないと判定された、と推定される。このため、副作用判定部114は、例えば、危険値発生日以後の所定の期間にわたって処方された薬を副作用原因薬剤候補から除外してもよい。 Next, the side effect determination unit 114 determines whether or not the prescription information has changed before and after the risk value occurrence date, and prescription information that has not changed, that is, prescription drugs that are continuously prescribed before and after the risk value occurrence date. Step 505 of excluding from the side effect cause drug candidate is executed. This is because, in general, when a risk value is generated by prescribing a certain medicine, it is considered that the doctor stops prescribing the medicine at that time. In other words, a drug that has been prescribed before the date of occurrence of the risk value and has been prescribed continuously after the date of occurrence of the risk value is not the cause of the occurrence of the risk value by the doctor who prescribes the drug. It is estimated that it was determined. For this reason, for example, the side effect determination unit 114 may exclude a drug prescribed for a predetermined period after the risk value occurrence date from the side effect causative drug candidate.
 画面例800の症例データの場合、副作用原因薬剤候補から、危険値発生日813の前後にわたって継続して処方されている「薬A」が除外される。 In the case data of the screen example 800, “drug A” prescribed continuously before and after the risk value occurrence date 813 is excluded from the side effect cause drug candidates.
 次に、副作用判定部114は、危険値発生日前後で、処方情報の変化の有無を判定し、処方情報に変化があり、危険値発生日前に処方情報がなく、危険値発生日後に処方情報がある、即ち危険値発生日前は処方されておらず、危険値発生日後に処方された処方薬を副作用原因薬剤候補から除外するステップ506を実行する。これは、危険値発生日前に処方されておらず、危険値発生日後に処方された処方薬は、当該危険値の原因になり得ないためである。画面例800の症例データの場合、副作用原因薬剤候補から、危険値発生日813の前には処方されておらず、危険値発生日813の翌日以降に処方された「薬D」が除外される。 Next, the side effect determination unit 114 determines whether or not the prescription information has changed before and after the risk value occurrence date, there is a change in the prescription information, there is no prescription information before the risk value occurrence date, and prescription information after the risk value occurrence date. In other words, step 506 is executed to exclude prescription drugs prescribed after the risk value occurrence date from the side effect cause drug candidates. This is because prescription medicines that are not prescribed before the risk value occurrence date and that are prescribed after the risk value occurrence date cannot cause the risk value. In the case data of the screen example 800, “drug D” that is not prescribed before the risk value occurrence date 813 and is prescribed after the risk value occurrence date 813 is excluded from the side effect cause drug candidates. .
 次に、副作用判定部114は、ステップ503で抽出された副作用原因薬剤候補のうち、ステップ505およびステップ506のいずれでも除外されなかった処方薬を副作用原因薬剤として抽出するステップ507を実行する。画面例800の症例データの場合、副作用原因薬剤として、「薬B」が抽出される。 Next, the side effect determination unit 114 executes step 507 of extracting prescription drugs that are not excluded in either step 505 or step 506 among the side effect cause drug candidates extracted in step 503 as side effect cause drugs. In the case data of the screen example 800, “drug B” is extracted as a side effect-causing drug.
 結局、副作用判定部114は、ステップ403で選択された疾患に対応する症例の各々(すなわちステップ403で選択された疾患のために入院した患者の各々)について、検査値が副作用知識テーブル320に格納された判定条件を満たした時期と、患者への薬剤の処方期間と、の関係に基づいて、副作用の原因と推定される薬剤を抽出する。具体的には、副作用判定部114は、副作用発生期間中に処方され(ステップ503)、検査値が危険値より低い値から高い値に変化した後の所定の期間に処方されず(ステップ505)、かつ、検査値が危険値より低い値から高い値に変化する前に処方された(ステップ506)薬を、副作用原因薬剤として抽出する(ステップ507)。 Eventually, the side effect determination unit 114 stores test values in the side effect knowledge table 320 for each case corresponding to the disease selected in step 403 (ie, each patient hospitalized for the disease selected in step 403). Based on the relationship between the time when the determined determination condition is satisfied and the prescription period of the drug to the patient, the drug estimated to be the cause of the side effect is extracted. Specifically, the side effect determination unit 114 is prescribed during the side effect occurrence period (step 503) and is not prescribed for a predetermined period after the test value changes from a value lower than the dangerous value to a higher value (step 505). And the medicine prescribed before the test value changes from a lower value to a higher value than the dangerous value (step 506) is extracted as a side effect-causing drug (step 507).
 上記の例では、副作用知識テーブル320の各レコードに格納された各判定条件が、異常値を判定するための第1の基準(すなわちフィールド322に格納された基準)と、危険値を判定するための第2の基準(すなわちフィールド323に格納された基準)を含んでいるが、各判定条件が一つの基準のみを含んでいてもよい。例えば、各判定条件が危険値を判定するための第2の基準のみを含んでもよい。いずれの場合も、副作用発生期間は、判定条件が満たされる期間を含む所定の期間である。具体的には、各判定条件が第1の基準および第2の基準を含む上記の例では、副作用発生期間は、異常値発生期間と同一の(すなわち異常値発生期間を含む)期間であり、危険値発生期間を含む期間でもある。一方、例えば、各判定条件が第2の基準のみを含む場合、副作用発生期間は、危険値発生期間を含む、危険値発生期間より長い所定の期間であってもよい。 In the above example, each determination condition stored in each record of the side effect knowledge table 320 is used to determine a first criterion for determining an abnormal value (that is, a criterion stored in the field 322) and a dangerous value. The second criterion (that is, the criterion stored in the field 323) is included, but each determination condition may include only one criterion. For example, each determination condition may include only the second reference for determining the dangerous value. In any case, the side effect occurrence period is a predetermined period including a period in which the determination condition is satisfied. Specifically, in the above example in which each determination condition includes the first criterion and the second criterion, the side effect occurrence period is the same period as the abnormal value occurrence period (that is, including the abnormal value occurrence period), It is also a period including the dangerous value occurrence period. On the other hand, for example, when each determination condition includes only the second criterion, the side effect occurrence period may be a predetermined period longer than the danger value occurrence period, including the danger value occurrence period.
 このように、副作用原因薬剤の判定するときに、副作用に対応する検査データの変化を判定し、その変化(例えば危険値の発生)の前後における処方の継続性を用いることで、副作用の原因となる薬剤を効率的に絞り込むことができる。 In this way, when determining a side effect-causing drug, the change in test data corresponding to the side effect is determined, and by using the continuity of prescription before and after the change (for example, the occurrence of a dangerous value), the cause of the side effect is determined. Can be narrowed down efficiently.
 次に、副作用判定部114は、副作用原因薬剤として抽出された処方薬に副作用フラグ「1」を設定するステップ508を実行する。 Next, the side effect determination unit 114 executes Step 508 for setting the side effect flag “1” to the prescription drug extracted as the side effect cause drug.
 ステップ507で、一つの検査項目に関する(すなわち一つの副作用知識レコードに格納された)副作用の判定条件に基づいて、複数の処方薬が副作用原因薬剤として抽出された場合は、副作用判定部114は、数式(3)を用いて、抽出された処方薬の数に応じて副作用フラグを配分して設定する。 In step 507, when a plurality of prescription drugs are extracted as side effect causative agents based on the side effect determination condition related to one inspection item (that is, stored in one side effect knowledge record), the side effect determination unit 114 Using equation (3), side effect flags are allocated and set according to the number of extracted prescription drugs.
Figure JPOXMLDOC01-appb-M000004
Figure JPOXMLDOC01-appb-M000004
 これによって、副作用の原因薬剤が複数抽出された場合でも、副作用の可能性を複数の原因薬剤に均等に配分した副作用フラグを設定することが可能となる。 This makes it possible to set a side effect flag that evenly distributes the possibility of a side effect to a plurality of causative agents even when a plurality of side effect causative agents are extracted.
 副作用判定部114は、ステップ508で複数の副作用原因薬剤に副作用フラグを設定する場合、上記の数式(3)を用いて均等に配分する代わりに、所定の基準に従って傾斜配分してもよい。例えば、副作用判定部114は、処方終了日から、その後の危険値発生日までの日数が長い処方薬ほど、その処方薬が危険値の発生と無関係である可能性が高い、との推定に基づいて、危険値発生日から処方終了日までの日数がより短い処方薬に配分される副作用フラグの値がより大きくなるように、数式(4)を用いて、副作用フラグを処方薬毎に傾斜配分して設定することもできる。 When the side effect determination unit 114 sets a side effect flag for a plurality of side effect causative agents in step 508, the side effect determination unit 114 may perform slope distribution according to a predetermined criterion instead of using the above formula (3). For example, the side effect determination unit 114 is based on the estimation that the prescription drug having a longer number of days from the prescription end date to the subsequent risk value occurrence date is more likely to be unrelated to the occurrence of the risk value. In order to increase the value of the side effect flag allocated to the prescription drug with a shorter number of days from the risk value occurrence date to the prescription end date, the side effect flag is inclined and distributed for each prescription drug using Equation (4). You can also set it.
Figure JPOXMLDOC01-appb-M000005
Figure JPOXMLDOC01-appb-M000005
 これによって、処方終了日から危険値発生日までの近さに応じて、両者が近いほど重くなるように副作用フラグを重み付けできるので、それぞれの処方薬について推定される副作用への影響度の大きさに応じた副作用フラグを設定することが可能となる。 As a result, the side effect flag can be weighted so that the closer the two are, the closer the two are closer to the risk value occurrence date. It is possible to set a side effect flag according to the condition.
 このように、検査データが異常状態または危険状態を示す時期の前後における処方の継続状態、即ち、処方プロセス(処方の継続性)と、検査データの変動性を用いることで、副作用の原因となる薬剤をより効率的に絞り込むことができる。これによって、多種多様な投薬治療において、個々の薬剤についてより正確な副作用の分析を実施することが可能となる。 In this way, the prescription continuation state before and after the time when the inspection data shows an abnormal state or a dangerous state, that is, the prescription process (prescription continuity) and the variability of the inspection data cause side effects. Drugs can be narrowed down more efficiently. This makes it possible to conduct a more accurate side effect analysis for individual drugs in a wide variety of medications.
 ステップ501で、全ての症例について副作用分析処理が終了したと判定されると、副作用判定部114は、処方薬ごとに、全ての症例についてステップ508で設定した副作用フラグを集計することによって、副作用インデックスを算出するステップ509を実行する。 If it is determined in step 501 that the side effect analysis processing has been completed for all cases, the side effect determination unit 114 counts the side effect flags set in step 508 for all cases for each prescription drug, thereby determining the side effect index. Step 509 is calculated.
 例えば、副作用判定部114は、数式(5)を用いて処方薬mの副作用インデックスDAIを算出する。 For example, the side effect determination unit 114 calculates the side effect index DAI of the prescription drug m using Equation (5).
Figure JPOXMLDOC01-appb-M000006
Figure JPOXMLDOC01-appb-M000006
 これによって計算される副作用インデックスDAIは、対象疾患の患者に処方薬mを処方した場合に副作用が表れる確率である。処方薬mの副作用インデックスDAIが大きいことは、処方薬mに起因して副作用が発生したと疑われる事例が発生する率が高いことを示している。このように、処方薬の副作用について、複数の症例に関する入院期間および検査情報等を用い、副作用の影響度合いを定量化した副作用インデックスを用いることで、他の処方薬との比較を分析することができる。 The side effect index DAI calculated by this is the probability that a side effect will appear when a prescription drug m is prescribed to a patient with the target disease. A large side effect index DAI of the prescription drug m indicates a high rate of occurrence of cases suspected of causing side effects due to the prescription drug m. In this way, it is possible to analyze the comparison with other prescription drugs by using the side effect index that quantifies the degree of influence of side effects using hospitalization periods and examination information on multiple cases, etc. it can.
 次に、制御部101は、画面生成部116を起動する。画面生成部116は、ステップ408で生成された効果インデックスと、ステップ409で生成された医療費と、ステップ410で生成された副作用インデックスと、に基づいて、全ての分析処理の結果を出力する画面を生成するステップ411を実行する。 Next, the control unit 101 activates the screen generation unit 116. The screen generator 116 outputs the results of all the analysis processes based on the effect index generated in step 408, the medical expenses generated in step 409, and the side effect index generated in step 410. Step 411 is generated.
 次に、制御部101は、ステップ411で生成された画面を入出力端末120に出力するステップ412を実行する。 Next, the control unit 101 executes Step 412 for outputting the screen generated in Step 411 to the input / output terminal 120.
 図7は、図4のステップ412が実行された後に、本発明の実施例の入出力端末120が分析処理の結果を表示する画面例700の説明図である。 FIG. 7 is an explanatory diagram of an example screen 700 on which the input / output terminal 120 according to the embodiment of the present invention displays the result of the analysis process after step 412 of FIG. 4 is executed.
 画面例700は、図6に示したものと同様の処方薬表示エリア620に、縦軸に効果インデックス、横軸に副作用インデックス、円(バブル)の大きさを医療費として、薬A、薬B、薬Cがそれぞれ同一軸上にバブルチャートで表示されている。 A screen example 700 has a prescription drug display area 620 similar to that shown in FIG. 6, an effect index on the vertical axis, a side effect index on the horizontal axis, and the size of a circle (bubble) as medical expenses, and drugs A and B Drug C is displayed in a bubble chart on the same axis.
 図7の例からは、薬Aは、治療効果が高く、副作用が少ないが、医療費は高い、ということがわかる。また、薬Bは、医療費は中程度であるが、副作用が多い、ということがわかる。また、薬Cは、医療費が低いものの、効果も低い、ということがわかる。 From the example of FIG. 7, it can be seen that drug A has a high therapeutic effect and few side effects, but has a high medical cost. It can also be seen that medicine B has moderate side effects, but has many side effects. It can also be seen that medicine C has a low medical cost, but has a low effect.
 このように、一つの疾患に処方される複数の処方薬の治療効果、副作用および医療費の指標が、それぞれ、同一のグラフの同一軸上に提示されるため、同じ疾患に対する様々な処方薬について、その治療効果、副作用および医療費の位置づけ(ドラッグポジション)が俯瞰的に把握できる。これによって、ユーザは適切な薬剤が選択されているか否かを簡単に把握できるため、適切な投薬治療等、診療プロセスの最適化を支援することができる。 In this way, the therapeutic effects, side effects, and medical cost indicators of multiple prescription drugs prescribed for one disease are presented on the same axis of the same graph. It is possible to grasp the therapeutic effect, side effects, and the position of medical expenses (drag position) from a bird's-eye view. Thereby, since the user can easily grasp whether or not an appropriate drug is selected, it is possible to support optimization of a medical treatment process such as an appropriate medication treatment.
 また、画面例700では、横軸に、添付文書と同程度の副作用(例えば3%)、他の医療機関から収集されたデータから算出した全ての副作用インデックスの平均値(例えば、全国平均5%など)、縦軸に他の医療機関から収集されたデータから算出した全ての効果インデックスの平均値(例えば、全国平均80%など)が表示される。また、医療機関内の収集されたデータから算出した全ての副作用インデックスの平均値及び全ての効果インデックスの平均値が、それぞれ院内平均710および720のように点線で表示される。 In the screen example 700, the horizontal axis indicates side effects (for example, 3%) similar to those in the attached document, and the average value of all side effect indexes calculated from data collected from other medical institutions (for example, the national average of 5%). The average value of all effect indexes calculated from data collected from other medical institutions (for example, the national average of 80%) is displayed on the vertical axis. In addition, the average value of all the side effect indexes and the average value of all the effect indexes calculated from the collected data in the medical institution are displayed by dotted lines as in- hospital averages 710 and 720, respectively.
 これによって、本システムを利用する医療機関において、治療効果および副作用の位置づけ(ドラッグポジション)が他の医療機関と比較して客観的に把握できるため、より適切な薬剤選択を支援しつつ、投薬治療に関する診療プロセスの最適化を支援することができる。 As a result, in medical institutions that use this system, the positioning of therapeutic effects and side effects (drug positions) can be objectively grasped compared to other medical institutions, so that medication treatment is supported while supporting more appropriate drug selection. Can help optimize the medical process.
 また、本システムを医師が診療時に利用する場合、例えば、患者への治療方針を説明するとき、すなわちインフォームドコンセントに用いることによって、処方薬毎の治療効果、副作用、および医療費を比較しながら説明できるため、治療方針の患者への説明および同意取得を効果的に実施することが可能となる。 In addition, when doctors use this system at the time of medical care, for example, when explaining the treatment policy to patients, that is, by using it for informed consent, while comparing the treatment effect, side effect, and medical cost for each prescription drug Since it can explain, it becomes possible to effectively explain the treatment policy to the patient and obtain consent.
 上記の例では、画面生成部116が画面例700を表示するためのデータを生成し、データサーバ100がそのデータをネットワーク140経由で入出力端末120に送信し、入出力端末120がそのデータに基づいて画面例700をディスプレイ装置等の出力装置(図示省略)に表示する例を示したが、出力部107が画面例700を表示してもよい。 In the above example, the screen generation unit 116 generates data for displaying the screen example 700, the data server 100 transmits the data to the input / output terminal 120 via the network 140, and the input / output terminal 120 converts the data into the data. Although an example in which the screen example 700 is displayed on an output device (not shown) such as a display device based on the above is shown, the output unit 107 may display the screen example 700.
 また、図7には、複数の処方薬の効果インデックス、副作用インデックスおよび医療費を、それぞれ、同一グラフの縦軸、横軸および表示される円の大きさに対応付けて表示する例を示したが、このような表示方法は一例であり、他の方法によってこれらの指標が表示されてもよい。例えば、効果インデックス、副作用インデックスおよび医療費のいずれか一つ、または任意の二つの組み合わせが表示されてもよいし、それらの値を示す数字が表示されてもよい。 FIG. 7 shows an example in which the effect index, the side effect index, and the medical cost of a plurality of prescription drugs are displayed in association with the vertical axis, the horizontal axis, and the size of the displayed circle, respectively. However, such a display method is an example, and these indicators may be displayed by other methods. For example, any one of the effect index, the side effect index, and the medical cost, or any combination of the two may be displayed, or a number indicating the value may be displayed.
 以上、本発明であるドラッグポジショニング可視化システムによって、多種多様な投薬治療において、個々の薬剤の効果、副作用および医療費の位置づけ(ドラッグポジション)を可視化し、適切な投薬治療を支援する情報システムを提供することが可能となる。 As described above, the drug positioning visualization system according to the present invention provides an information system for visualizing the effects of individual drugs, side effects, and positioning of medical expenses (drug positions) in various types of medications and supporting appropriate medications. It becomes possible to do.
 なお、本発明は上述した実施例に限定されるものではなく、様々な変形例が含まれる。例えば、上記した実施例は本発明を分かりやすく説明するために詳細に説明したものであり、必ずしも説明した全ての構成を備えるものに限定されるものではない。また、各実施例の構成の一部について、他の構成の追加・削除・置換をすることが可能である。 In addition, this invention is not limited to the Example mentioned above, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.
 上記の各構成、機能、処理部、処理手段等は、それらの一部または全部を、例えば集積回路で設計する等によってハードウェアで実現してもよい。また、上記の各構成、機能等は、プロセッサがそれぞれの機能を実現するプログラムを解釈し、実行することによってソフトウェアで実現してもよい。各機能を実現するプログラム、テーブル、ファイル等の情報は、メモリ、ハードディスクドライブ、SSD(Solid State Drive)等の記憶装置、または、ICカード、SDカード、DVD等の計算機読み取り可能な非一時的データ記憶媒体に格納することができる。 The above-described configurations, functions, processing units, processing means, etc. may be realized in hardware by designing a part or all of them, for example, with an integrated circuit. Further, each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files that realize each function is a memory, hard disk drive, storage device such as SSD (Solid State Drive), or computer-readable non-transitory data such as an IC card, SD card, or DVD. It can be stored in a storage medium.
 また、図面には、実施例を説明するために必要と考えられる制御線及び情報線を示しており、必ずしも、本発明が適用された実際の製品に含まれる全ての制御線及び情報線を示しているとは限らない。実際にはほとんど全ての構成が相互に接続されていると考えてもよい。 Further, the drawings show control lines and information lines that are considered necessary for explaining the embodiments, and not necessarily all control lines and information lines included in an actual product to which the present invention is applied. Not necessarily. Actually, it may be considered that almost all the components are connected to each other.

Claims (15)

  1.  プロセッサと、前記プロセッサに接続される記憶装置と、を備える分析システムであって、
     前記記憶装置は、
     各患者の疾患及び入院期間を示す症例情報と、
     前記各患者への各薬の処方期間を示す処方情報と、
     前記各患者の検査結果を示す検査情報と、
     前記検査結果に基づく副作用の判定条件を示す知識情報と、を保持し、
     前記プロセッサは、
     前記疾患ごとに、前記各患者の検査結果が前記副作用の判定条件を満たした時期と、前記各患者への前記各薬の処方期間と、の関係に基づいて、副作用の原因となった薬を推定し、
     前記推定の結果を出力することを特徴とする分析システム。
    An analysis system comprising a processor and a storage device connected to the processor,
    The storage device
    Case information showing the disease and hospitalization period of each patient,
    Prescription information indicating the prescription period of each drug for each patient;
    Test information indicating the test results of each patient,
    Holding knowledge information indicating conditions for determining side effects based on the test results,
    The processor is
    For each disease, the drug that caused the side effect is determined based on the relationship between the time when the test result of each patient satisfies the determination condition for the side effect and the prescription period of each drug for each patient. Estimate
    An analysis system that outputs the result of the estimation.
  2.  請求項1に記載の分析システムであって、
     前記プロセッサは、前記患者ごとに、前記検査結果が前記副作用の判定条件を満たした期間を含む所定の期間内に処方され、前記検査結果が前記副作用の判定条件を満たさない状態から満たす状態に変化した後の所定の期間に継続して処方されず、かつ、前記検査結果が前記副作用の判定条件を満たさない状態から満たす状態に変化する前に処方された薬を、前記副作用の原因と推定することを特徴とする分析システム。
    The analysis system according to claim 1,
    The processor is prescribed for each patient within a predetermined period including a period in which the test result satisfies the determination condition for the side effect, and the test result is changed from a state in which the test result does not satisfy the determination condition for the side effect to a state in which the test result is satisfied. Presumed as a cause of the side effect is a prescription that is not prescribed continuously for a predetermined period of time after the test, and the test result is changed from a state that does not satisfy the determination condition of the side effect to a state that satisfies the condition. An analysis system characterized by that.
  3.  請求項2に記載の分析システムであって、
     前記プロセッサは、
     前記患者ごとに、前記副作用の原因と推定された薬に所定のフラグ値を付与し、
     前記薬ごとに、複数の前記患者について付与された前記フラグ値を集計することによって、前記各薬の副作用の指標を計算し、
     前記各薬の副作用の指標を前記推定の結果として出力することを特徴とする分析システム。
    The analysis system according to claim 2,
    The processor is
    For each patient, a predetermined flag value is given to the presumed cause of the side effect,
    For each drug, by calculating the flag values given for a plurality of the patients, calculating an index of side effects of each drug,
    An analysis system, wherein an index of a side effect of each drug is output as the estimation result.
  4.  請求項3に記載の分析システムであって、
     前記プロセッサは、前記患者ごとに、一つの検査項目に関する前記副作用の判定条件に基づいて、複数の薬が前記副作用の原因と推定された場合、前記所定のフラグ値を前記複数の薬に配分して付与することを特徴とする分析システム。
    The analysis system according to claim 3,
    The processor, for each patient, allocates the predetermined flag value to the plurality of medicines when a plurality of medicines are estimated to be the cause of the side effects based on the determination condition of the side effects concerning one examination item. The analysis system characterized by giving.
  5.  請求項4に記載の分析システムであって、
     前記プロセッサは、前記患者ごとに、一つの検査項目に関する前記副作用の判定条件に基づいて、前記複数の薬が前記副作用の原因と推定された場合、前記複数の薬の各々の処方が終了してから、前記検査結果が前記副作用の判定条件を満たさない状態から満たす状態に変化するまでの期間の長さに基づいて、前記所定のフラグ値を前記複数の薬の各々に傾斜配分して付与することを特徴とする分析システム。
    The analysis system according to claim 4,
    The processor, for each of the patients, when the plurality of drugs are estimated to be the cause of the side effect based on the determination condition of the side effect for one test item, the prescription of each of the plurality of drugs is completed. The predetermined flag value is given to each of the plurality of medicines in an inclined manner based on the length of the period until the test result changes from a state not satisfying the determination condition for the side effect to a state satisfying An analysis system characterized by that.
  6.  請求項2に記載の分析システムであって、
     前記副作用の判定条件は、検査結果の異常を判定するための第1基準と、前記第1基準によって判定されるものより程度の大きい異常を判定するための第2基準と、を含み、
     前記プロセッサは、前記患者ごとに、前記検査結果が前記第1基準を満たした期間内に処方され、前記検査結果が前記第2基準を満たさない状態から満たす状態に変化した後の所定の期間に継続して処方されず、かつ、前記検査結果が前記第2基準を満たさない状態から満たす状態に変化する前に処方された薬を、前記副作用の原因と推定することを特徴とする分析システム。
    The analysis system according to claim 2,
    The determination condition of the side effect includes a first criterion for determining an abnormality of a test result and a second criterion for determining an abnormality that is greater than that determined by the first criterion,
    The processor is prescribed for each patient within a period in which the test result satisfies the first criterion and the test result changes from a state not satisfying the second criterion to a state satisfying the second criterion. An analysis system characterized in that a prescription that is not continuously prescribed and that is prescribed before the test result changes from a state that does not satisfy the second standard to a state that satisfies the second criterion is estimated as the cause of the side effect.
  7.  請求項3に記載の分析システムであって、
     前記記憶装置は、前記各薬の費用情報をさらに保持し、
     前記プロセッサは、
     少なくとも前記症例情報および前記処方情報に基づいて、前記疾患ごとの前記各薬の効果の指標を計算し、
     前記費用情報、前記症例情報および前記処方情報に基づいて、前記疾患ごとの前記各薬の費用の指標を計算し、
     前記疾患ごとの前記各薬の効果の指標、前記費用の指標および前記副作用の指標を出力することを特徴とする分析システム。
    The analysis system according to claim 3,
    The storage device further holds cost information of each medicine,
    The processor is
    Based on at least the case information and the prescription information, calculate an index of the effect of each drug for each disease,
    Based on the cost information, the case information and the prescription information, calculate an index of the cost of each drug for each disease,
    An analysis system that outputs an index of an effect of each drug for each disease, an index of the cost, and an index of the side effect.
  8.  請求項7に記載の分析システムであって、
     前記知識情報は、前記各薬と、前記各薬が適用できる疾患と、前記各薬を処方したことによる効果と、を対応付ける情報をさらに含み、
     前記プロセッサは、前記疾患ごとに、前記各患者への前記各薬の処方の前後の前記検査結果の変化と、前記知識情報に含まれる前記各薬に対応付けられた効果と、を比較することによって、前記各薬の効果の指標を計算することを特徴とする分析システム。
    The analysis system according to claim 7,
    The knowledge information further includes information associating each medicine, a disease to which each medicine can be applied, and an effect obtained by prescribing each medicine,
    The processor compares, for each disease, a change in the test result before and after the prescription of each drug to each patient and an effect associated with each drug included in the knowledge information. An analysis system characterized in that an index of the effect of each drug is calculated.
  9.  請求項7に記載の分析システムであって、
     前記プロセッサは、前記疾患ごとに、前記各薬が処方された前記各患者の入院期間の長さに基づいて、前記各薬の効果の指標を計算することを特徴とする分析システム。
    The analysis system according to claim 7,
    The analysis system characterized in that the processor calculates an index of the effect of each medicine based on the length of hospital stay of each patient prescribed for each medicine for each disease.
  10.  請求項7に記載の分析システムであって、
     ディスプレイ装置をさらに有し、
     前記プロセッサは、前記疾患ごとの前記複数の薬の効果の指標、費用の指標および副作用の指標を同一のグラフにプロットした画面を前記ディスプレイ装置に表示させることを特徴とする分析システム。
    The analysis system according to claim 7,
    A display device;
    The analysis system, wherein the processor causes the display device to display a screen in which an index of effect of the plurality of drugs, an index of cost, and an index of side effects are plotted on the same graph for each disease.
  11.  プロセッサと、前記プロセッサに接続される記憶装置と、を備える計算機システムが実行する分析方法であって、
     前記記憶装置は、
     各患者の疾患及び入院期間を示す症例情報と、
     前記各患者への各薬の処方期間を示す処方情報と、
     前記各患者の検査結果を示す検査情報と、
     前記検査結果に基づく副作用の判定条件を示す知識情報と、を保持し、
     前記分析方法は、
     前記疾患ごとに、前記各患者の検査結果が前記副作用の判定条件を満たした時期と、前記各患者への前記各薬の処方期間と、の関係に基づいて、副作用の原因となった薬を推定する第1手順と、
     前記推定の結果を出力する第2手順と、を含むことを特徴とする分析方法。
    An analysis method executed by a computer system comprising a processor and a storage device connected to the processor,
    The storage device
    Case information showing the disease and hospitalization period of each patient,
    Prescription information indicating the prescription period of each drug for each patient;
    Test information indicating the test results of each patient,
    Holding knowledge information indicating conditions for determining side effects based on the test results,
    The analysis method is:
    For each disease, the drug that caused the side effect is determined based on the relationship between the time when the test result of each patient satisfies the determination condition for the side effect and the prescription period of each drug for each patient. A first step to estimate;
    And a second procedure for outputting the result of the estimation.
  12.  請求項11に記載の分析方法であって、
     前記第1手順は、前記患者ごとに、前記検査結果が前記副作用の判定条件を満たした期間を含む所定の期間内に処方され、前記検査結果が前記副作用の判定条件を満たさない状態から満たす状態に変化した後の所定の期間に継続して処方されず、かつ、前記検査結果が前記副作用の判定条件を満たさない状態から満たす状態に変化する前に処方された薬を、前記副作用の原因と推定する手順を含むことを特徴とする分析方法。
    The analysis method according to claim 11, comprising:
    In the first procedure, for each patient, the test result is prescribed within a predetermined period including a period in which the side effect determination condition is satisfied, and the test result is satisfied from a state in which the side effect determination condition is not satisfied. A drug prescribed before the change from a state where the test result does not satisfy the determination condition for the side effect to a state where the test result does not satisfy the condition for determining the side effect An analysis method comprising an estimation procedure.
  13.  請求項12に記載の分析方法であって、
     前記第1手順は、
     前記患者ごとに、前記副作用の原因と推定された薬に所定のフラグ値を付与する手順と、
     前記薬ごとに、複数の前記患者について付与された前記フラグ値を集計することによって、前記各薬の副作用の指標を計算する手順と、を含み、
     前記第2手順は、前記各薬の副作用の指標を前記推定の結果として出力する手順を含むことを特徴とする分析方法。
    The analysis method according to claim 12, comprising:
    The first procedure includes:
    A procedure for giving a predetermined flag value to the medicine presumed to be the cause of the side effect for each patient,
    Calculating a side effect index for each drug by counting the flag values given for a plurality of patients for each drug, and
    The analysis method characterized in that the second procedure includes a procedure for outputting an index of a side effect of each drug as a result of the estimation.
  14.  請求項13に記載の分析方法であって、
     前記記憶装置は、前記各薬の費用情報をさらに保持し、
     前記分析方法は、さらに、
     少なくとも前記症例情報および前記処方情報に基づいて、前記疾患ごとの前記各薬の効果の指標を計算する第3手順と、
     前記費用情報、前記症例情報および前記処方情報に基づいて、前記疾患ごとの前記各薬の費用の指標を計算する第4手順と、を含み、
     前記第2手順は、前記疾患ごとの前記各薬の効果の指標、前記費用の指標および前記副作用の指標を出力する手順を含むことを特徴とする分析方法。
    The analysis method according to claim 13, comprising:
    The storage device further holds cost information of each medicine,
    The analysis method further includes:
    A third procedure for calculating an index of the effect of each drug for each disease based on at least the case information and the prescription information;
    A fourth step of calculating an index of the cost of each drug for each disease based on the cost information, the case information, and the prescription information,
    The analysis method characterized in that the second procedure includes a procedure for outputting an index of the effect of each drug for each disease, an index of the cost, and an index of the side effect.
  15.  請求項14に記載の分析方法であって、
     前記計算機システムはディスプレイ装置をさらに有し、
     前記第2手順は、前記疾患ごとの前記複数の薬の効果の指標、費用の指標および副作用の指標を同一のグラフにプロットした画面を前記ディスプレイ装置に表示させる手順を含むことを特徴とする分析方法。
    The analysis method according to claim 14, comprising:
    The computer system further includes a display device,
    The second procedure includes a procedure for causing the display device to display a screen in which the effect index, the cost index, and the side effect index of the plurality of drugs for each disease are plotted in the same graph. Method.
PCT/JP2014/065619 2014-06-12 2014-06-12 Analysis system and analysis method WO2015189958A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/065619 WO2015189958A1 (en) 2014-06-12 2014-06-12 Analysis system and analysis method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/065619 WO2015189958A1 (en) 2014-06-12 2014-06-12 Analysis system and analysis method

Publications (1)

Publication Number Publication Date
WO2015189958A1 true WO2015189958A1 (en) 2015-12-17

Family

ID=54833086

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/065619 WO2015189958A1 (en) 2014-06-12 2014-06-12 Analysis system and analysis method

Country Status (1)

Country Link
WO (1) WO2015189958A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017211772A (en) * 2016-05-24 2017-11-30 株式会社日立製作所 Adverse effect analysis system, and adverse effect analysis method
JP2019121051A (en) * 2017-12-28 2019-07-22 株式会社湯山製作所 Medical information management system and medical information management program
JP2019121050A (en) * 2017-12-28 2019-07-22 株式会社湯山製作所 Medical information management system and medical information management program
CN111933246A (en) * 2020-08-31 2020-11-13 平安国际智慧城市科技股份有限公司 Medical prescription analysis method, system, electronic device and storage medium
US20220051795A1 (en) * 2018-09-12 2022-02-17 Hitachi, Ltd. Analysis system and analysis method

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003288415A (en) * 2002-03-27 2003-10-10 Ntt Data Corp Drug evaluation system
JP2006178729A (en) * 2004-12-22 2006-07-06 Hitachi Ltd Method for supporting confirmation of safety of medicine, safety confirmation support system and program
JP2008310574A (en) * 2007-06-14 2008-12-25 Nec Corp Side effect information management system, side effect information management method, side effect information management program

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003288415A (en) * 2002-03-27 2003-10-10 Ntt Data Corp Drug evaluation system
JP2006178729A (en) * 2004-12-22 2006-07-06 Hitachi Ltd Method for supporting confirmation of safety of medicine, safety confirmation support system and program
JP2008310574A (en) * 2007-06-14 2008-12-25 Nec Corp Side effect information management system, side effect information management method, side effect information management program

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017211772A (en) * 2016-05-24 2017-11-30 株式会社日立製作所 Adverse effect analysis system, and adverse effect analysis method
JP2019121051A (en) * 2017-12-28 2019-07-22 株式会社湯山製作所 Medical information management system and medical information management program
JP2019121050A (en) * 2017-12-28 2019-07-22 株式会社湯山製作所 Medical information management system and medical information management program
JP7013866B2 (en) 2017-12-28 2022-02-01 株式会社湯山製作所 Medical information management system and medical information management program
US20220051795A1 (en) * 2018-09-12 2022-02-17 Hitachi, Ltd. Analysis system and analysis method
CN111933246A (en) * 2020-08-31 2020-11-13 平安国际智慧城市科技股份有限公司 Medical prescription analysis method, system, electronic device and storage medium

Similar Documents

Publication Publication Date Title
JP2020023573A (en) Systems and methods of managing treatment of chronic condition by symptom tracking
Birnbaum et al. Clinical features and diagnostic evaluation of biopsy-proven ocular sarcoidosis
JP6568851B2 (en) System and method for facilitating provision of patient care
US10593428B2 (en) Diagnosis support apparatus and method, and non-transitory computer readable medium
US20150339447A1 (en) Medical assistance device, operation method of medical assistance device, non-transitory computer-readable recording medium, and medical assistance system
EP3070628A1 (en) Methods and devices for tracking patient data
Gillies et al. Ethnic disparities in asthma treatment and outcomes in children aged under 15 years in New Zealand: analysis of national databases
JP6408436B2 (en) Medical support device, its operating method and operating program, and medical support system
WO2015189958A1 (en) Analysis system and analysis method
JP7212630B2 (en) Decision-making system and method for determining initiation and type of treatment for patients with progressive disease
US20170199965A1 (en) Medical system and method for predicting future outcomes of patient care
US11751821B2 (en) Systems and methods of advanced warning for clinical deterioration in patients
De Lott et al. Diplopia-related ambulatory and emergency department visits in the United States, 2003-2012
US20190392955A1 (en) System and method for drug interaction prediction
Hackam et al. Influence of noninvasive cardiovascular imaging in primary prevention: systematic review and meta-analysis of randomized trials
JP2014106776A (en) Inspection method proposing device
JP2014067344A (en) Graph creation device, graph creation method, and graph creation program
Adams et al. Clinician use and payments by medical specialty for audiometric and vestibular testing among US Medicare beneficiaries
JP2013536963A (en) Clinical status timeline
Rudmik et al. Routine magnetic resonance imaging for idiopathic olfactory loss: a modeling-based economic evaluation
US20170364646A1 (en) Method and system for analyzing and displaying optimization of medical resource utilization
JP7044113B2 (en) Presentation method, presentation system, and program
US11728034B2 (en) Medical examination assistance apparatus
JP5846925B2 (en) Medical image display device
Gawkrodger Risk management in dermatology: an analysis of data available from several British‐based reporting systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14894513

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14894513

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP