JP2019159871A - Side effect diagnostic device and side effect diagnostic method - Google Patents

Abstract

To provide a side effect diagnostic device capable of diagnosing the presence or absence of the side effect caused by the medicine to be ingested.SOLUTION: A side effect diagnostic device 1 for diagnosing side effects to patients due to ingestion drug, medical records created for a patient, nursing records, or care records D1, and a symptom candidate database 16 for storing information according to a plurality of physical symptom candidates, based on occurring in the patient, a physical symptom identification unit 13 for identifying the physical symptoms, and information D2 according to the ingestion drug, and a side effect information database 17 for storing information according to the side effect candidate of a plurality of drugs, based on a side effect candidate extraction unit 14 for extracting the side effect candidates that may occur in the patient, by matching the side effect candidate, and physical symptoms which the physical symptoms identification unit and the side effect candidate which the side effect candidate extraction unit has identified are correlated, and a diagnostic unit 15 for diagnosing the presence or absence of the occurrence of the side effects caused by the ingestion agent.SELECTED DRAWING: Figure 2

Description

  The present disclosure relates to a side effect diagnosis device and a side effect diagnosis method.

  2. Description of the Related Art Conventionally, a side effect diagnostic device that diagnoses that a side effect caused by a drug does not occur is known.

  For example, Patent Document 1 describes a side effect diagnosis device that presents a side effect that may occur due to a drug using a database that associates the drug with a side effect as a system for a pharmacy. Yes. Patent Documents 2 and 3 describe a side effect diagnosis device that predicts a side effect of a drug in consideration of a patient's constitution as a system for a hospital.

JP 2004-185196 A JP-A-2005-090560 JP 2013-012025 A

  By the way, in general, the side effects of drugs vary greatly from patient to patient in terms of the type of physical symptoms that occur or the degree of physical symptoms that occur. Therefore, it is often difficult to predict the side effects of drugs in advance.

  Against this background, patients suffer from any side effects caused by drugs taken or administered by infusion (hereinafter collectively referred to as “medicines” or “ingested drugs”). The drug may continue to be prescribed. For example, if the doctor is not aware of the side effects of the drug, the doctor often does not come up with the side effects from the patient's chief complaint.

  In particular, the side effect diagnosis of drugs is different in the physical symptoms that occur in each patient, and it is difficult for patients themselves to clearly recognize physical symptoms (for example, even if there is an abnormality in organ function) May be aware only of allergic symptoms that occur as a result), and physical symptoms that the patient is aware of may be due to factors other than drugs (for example, mental factors) Etc. have difficulty.

  In this regard, the prior arts of Patent Documents 1 to 3 merely predict side effects of a drug before prescribing the drug to a patient. Therefore, in the prior arts of Patent Documents 1 to 3, even when the patient feels some discomfort as a physical symptom, the discomfort is due to the medication taken or due to other factors. There is a problem that it cannot be diagnosed.

  The present disclosure has been made in view of the above problems, and an object of the present disclosure is to provide a side effect diagnostic apparatus and a side effect diagnostic method capable of diagnosing the presence / absence of occurrence of a side effect caused by an ingested drug.

The main present disclosure for solving the above-described problems is as follows.
A side effect diagnostic device for diagnosing the occurrence of side effects on patients caused by ingested drugs,
A physical symptom identification unit that identifies physical symptoms occurring in the patient based on a diagnosis record, nursing record, or care record created for the patient, and a symptom candidate database stored for a plurality of physical symptom candidates When,
Based on the information on the ingested drug and the side effect information database storing the side effect candidates of a plurality of drugs, the side effect candidate extraction unit that extracts the side effect candidate that may occur in the patient,
Checking the physical symptoms identified by the physical symptom identification unit and the side effect candidates extracted by the side effect candidate extraction unit, and diagnosing the presence or absence of the occurrence of the side effects caused by the ingested drug,
It is a side effect diagnosis apparatus provided with.

In other aspects,
A side effect diagnosis method for diagnosing the occurrence of side effects on patients caused by ingested drugs,
Based on the examination record, nursing record, or care record created for the patient, and a symptom candidate database stored for a plurality of physical symptom candidates, the physical symptom occurring in the patient is identified,
Based on the information on the ingested drug and the side effect information database storing the side effect candidates of a plurality of drugs, the side effect candidates that may occur in the patient are extracted,
Collating the identified physical symptoms with the extracted candidate for side effects, and diagnosing the presence or absence of the side effects caused by the ingested drug,
It is a method for diagnosing side effects.

  According to the side effect diagnostic apparatus according to the present disclosure, it is possible to diagnose the presence or absence of the occurrence of a side effect caused by the medicine taken.

The figure which shows an example of a structure of the side effect diagnosis system which concerns on one Embodiment The block diagram which shows an example of a structure of the side effect diagnostic apparatus which concerns on one Embodiment The figure which shows an example of the hardware constitutions of the side effect diagnostic apparatus which concerns on one Embodiment Figure showing an example of a medical record Figure showing an example of a medication list The figure which shows an example of a structure of symptom candidate DB which concerns on one Embodiment. The flowchart which shows an example of the process which the physical symptom specific | specification part which concerns on one Embodiment performs The figure which shows an example of a structure of the side effect candidate DB which concerns on one Embodiment. The figure explaining the process of a diagnostic part

  Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the appended drawings. In the present specification and drawings, components having substantially the same function are denoted by the same reference numerals, and redundant description is omitted.

[Overall configuration of side effect diagnosis system]
In the present embodiment, a mode in which the side effect diagnosis apparatus according to the present invention is applied to a side effect diagnosis system in a hospital will be described. Hereinafter, the configuration of the side effect diagnosis system according to the present embodiment will be described with reference to FIGS.

  FIG. 1 is a diagram illustrating an example of a configuration of a side effect diagnosis system U according to the present embodiment. FIG. 1 shows a situation where a doctor H2 (corresponding to the “examiner” of the present invention) is examining a patient H1 in a hospital examination room.

  The side effect diagnosis system U according to the present embodiment includes a side effect diagnosis device 1, an electronic medical record terminal 2, and a patient terminal 3.

  The electronic medical chart terminal 2 is, for example, a general computer, and is used for inputting a medical record (also referred to as a medical chart) when the doctor H2 examines the patient H1. The electronic medical record terminal 2 is installed, for example, in an examination room where a doctor H2 performs an examination.

  During the examination, the doctor H2 makes an inquiry about the physical condition of the patient H1, or uses an examination device (for example, a blood pressure measurement device, a pulse measurement device, a stethoscope, or an ultrasonic diagnostic device). A physical examination of patient H1 is performed. Then, the doctor H2 inputs, for example, the contents of the statement made by the patient H1 during the examination, the examination result of the physical examination of the patient H1, or the evaluation contents of the doctor H2, etc. to the electronic medical record terminal 2 as the examination record. To do.

  The patient terminal 3 is, for example, a general computer, and is provided for the patient H1 to record medication records (ingestion records) and the like. The patient terminal 3 stores the type of medicine taken by the patient H1, the number of medicines taken, and the like.

  The side effect diagnosis device 1 is a computer that diagnoses the presence or absence of the occurrence of side effects due to the medications already taken by the patient H1 for the patient H1 who has visited the examination room.

  The side effect diagnosis apparatus 1 is connected to the electronic medical record terminal 2 and the patient terminal 3 through a communication network N such as a LAN (Local Area Network), a WAN (Wide Area Network), or an Internet line. 2 receives data related to the medical record of the patient H1, and receives data related to the medication taken from the patient terminal 3. And the side effect diagnosis apparatus 1 diagnoses the presence or absence of the occurrence of the side effect resulting from the medicine taken based on these data. In other words, the side effect diagnosis device 1 diagnoses whether the physical symptoms occurring in the patient H2 are caused by the side effects of the medicine taken.

  The drug to be diagnosed by the side effect diagnosis device 1 is not limited to a drug administered from the mouth of the patient H1, but also includes a drug administered into the body of the patient H1 using injection or infusion.

  FIG. 2 is a block diagram illustrating an example of the configuration of the side effect diagnosis apparatus 1 according to the present embodiment.

  The side effect diagnosis apparatus 1 according to this embodiment includes a diagnosis record acquisition unit 11, a medication list acquisition unit 12, a physical symptom specification unit 13, a side effect candidate extraction unit 14, a diagnosis unit 15, a symptom candidate database 16 (hereinafter referred to as “symptom candidate DB16”). And a side effect candidate database 17 (hereinafter referred to as “side effect candidate DB 17”).

  In addition, the arrow in FIG. 2 represents the flow of the process of each function, and the flow of data D1-D3.

  FIG. 3 is a diagram illustrating an example of a hardware configuration of the side effect diagnosis apparatus 1 according to the present embodiment.

  The side effect diagnosis apparatus 1 includes a CPU 101, a ROM 102, a RAM 103, an external storage device (for example, an HDD or a flash memory) 104, a communication interface 105 (for example, a communication controller for a LAN line), and the like as main components. It is.

  Each function described above of the side effect diagnosis apparatus 1 is realized by the CPU 101 referring to processing programs and various data stored in the ROM 102, the RAM 103, the external storage device 104, and the like, for example. However, some or all of the above-described functions may be realized by processing by a dedicated hardware circuit instead of, or together with, processing by software.

  Hereinafter, details of the configuration of the side effect diagnosis device 1 will be described.

[Diagnosis Record Acquisition Department]
The medical record acquisition unit 11 acquires data (hereinafter referred to as “medical record”) D1 related to the medical record of the doctor H2 who has examined the patient H1 from the electronic medical record terminal 2. The diagnosis record D1 typically includes information related to the content of the remarks of the patient H1, information related to the examination result of the physical examination of the patient H1, and information related to the evaluation of the doctor H2.

  FIG. 4 is a diagram illustrating an example of the diagnosis record D1.

  The medical examination record D1 shown in FIG. 4 is an example of what is created by the doctor H2 in accordance with a SOAP (Subject-Object-Assessment-Plan) system that is a general medical examination recording system. In the SOAP method, the doctor H2 has [Subject] (subject's subjective complaint), [Object] (objective observation), [Assessment] (evaluation / judgment), [Plan] (future treatment plan). Enter the results of the examination for each item.

  In the “[Subject] patient's subjective complaint” column, the content of the statement of the patient H1, that is, the main complaint of the patient H1 (a symptom that the patient H1 complains to the doctor H2) is entered. In the “[Object] Objective Observation” column, the examination result of the physical examination of the patient H1 (for example, examination data of the physical examination of the patient H1 performed by the doctor H2 during the examination) is entered. Further, in the “[Assessment] evaluation / judgment” column, for example, the evaluation of the doctor H2 regarding the patient H1 throughout the examination, such as exchange with the patient H1, is entered. In the “[Plan] future treatment plan” column, a future treatment plan to be examined by the doctor H2 is entered.

  As shown in FIG. 4, in the medical record D1, in general, in addition to objective data (for example, a test result obtained by examining the physical condition of the patient H1), although it is abstract, it is difficult to appear as a result of the physical test. Intrinsic data (for example, the specific content of the patient H1 and the diagnostic content diagnosed by the doctor H2 based on the experience) are included.

  The examination record D1 is typically text data of a sentence created by the doctor H2. However, the examination record D1 includes data stored in a format such as voice (for example, data obtained by recording a conversation at the time of examination) or an image (for example, a schema image created by the doctor H2) other than text format data. You may go out.

  In the present embodiment, a medical record D1 created by the doctor H2 is shown as a suitable example of information referred to by the physical symptom specifying unit 13 described later for specifying the physical symptom. However, as the information referred to by the physical symptom specifying unit 13 for specifying the physical symptom, the nursing record created by the nurse or the care record created by the caregiver is used instead of the diagnosis record D1. Also good.

[Medication List Acquisition Department]
The medication list acquisition unit 12 acquires data (hereinafter referred to as “medicine list”) D <b> 2 related to the medication (ingestion medication) of the patient H <b> 1 from the patient terminal 3. The medication list D2 includes, for example, record information of medications taken by the patient H1, such as the type or medication name of the medication taken by the patient H1.

  FIG. 5 is a diagram illustrating an example of the medication list D2. In the medication list D2 shown in FIG. 5, “Aspirin” and “Topsin” are shown as the types of medication taken by the patient H1. The medication list D2 includes the number of patients H1 who took the “aspirin” and “topsin”.

  The medication list acquisition unit 12 may automatically acquire the medication list D2 from the patient terminal 3 or may be configured to acquire it from another terminal in which a list of medications heard from the patient H1 is written. . In addition, the medication list acquisition unit 12 may acquire the medication list D2 from within the medical record D1 acquired by the medical record acquisition unit 11, or from the medical record D1 created in the past. May be obtained.

[Physical symptom identification part]
The physical symptom specifying unit 13 performs morphological analysis on the diagnosis record D1 acquired by the diagnosis record acquiring unit 11, and specifies the physical symptom occurring in the patient H1. The physical symptom specifying unit 13 specifies, for example, a physical symptom occurring in the patient H1 with reference to a symptom candidate DB 16 stored in advance. Then, the physical symptom specifying unit 13 sends the specified physical symptom data (hereinafter abbreviated as “physical symptom”) D1a to the diagnosis unit 15.

  FIG. 6 is a diagram illustrating an example of the configuration of the symptom candidate DB 16.

  The symptom candidate DB 16 stores various physical symptom candidates hierarchically and diversified for each body part, for example, in an ontology format. That is, the items of physical symptom candidates listed in the symptom candidate DB 16 are items that express physical symptoms more specifically or locally from abstract and rough items as they go from the upper layer items to the lower layer items.

  The ontology of the symptom candidate DB 16 shown in FIG. 6 has “chest feeling” and “chest pain” as the parallel lower-level items of “chest”, and “tightening” as the parallel lower-level items of the “chest pain”. "Pain like pain" and "radiated pain that spreads pain". In addition, the ontology of the symptom candidate DB 16 has “wheezing”, “cough / phlegm”, and “breathing difficulty” as parallel lower-level items of “respiratory organs”, , “Acute shortness of breath”, “intermittent shortness of breath”, and “shortness of breath during exercise”. Further, the ontology of the symptom candidate DB 16 includes “erythema”, “white spot”, “angioedema”, and “urticaria” as parallel subordinate items of “skin”, and the “erythema”, “angioedema” ”And“ redness of skin ”as a lower layer item common to“ urticaria ”.

  It should be noted that the physical symptom candidate data stored in the symptom candidate DB 16 relates to physical symptoms of a lower concept (that is, more specifically or locally expressed content) than the side effect candidate data stored in the side effect candidate DB 17 described later. Have items. This avoids duplication of items related to physical symptoms for each drug in the side effect candidate DB 17 and suppresses the maximization of the side effect ontology.

  Further, the data of the physical symptom candidates stored in the symptom candidate DB 16 are more preferably stored in association with the standard range of the examination numerical values of the physical examination. As a result, it is possible to identify physical symptoms from the examination results (for example, the contents entered in [Object]) of the physical examination of the patient H1 included in the examination record D1.

  Further, the physical symptom candidate data stored in the symptom candidate DB 16 may be stored as a word (that is, text information), or may be stored as a word vector. As the word vector, for example, a word vector generated using a known algorithm such as Word2Vec can be used.

  Note that each item and hierarchical structure of physical symptoms stored in the symptom candidate DB 16 is based on, for example, a medical terminology dictionary provided by the Japan Medical Association, or a plurality of examination records created for other patients in the past. Is set. The method for creating the symptom candidate DB 16 may be a manual input method or a clustering method using machine learning or the like.

  Thus, the symptom candidate DB 16 according to the present embodiment stores physical symptom candidates in an ontology format. Thereby, the physical symptom specifying unit 13 specifies the physical symptom hierarchically and multilaterally from the contents of the examination record D1 expressed variously (for example, the contents of the chief complaint of the patient H1 and the evaluation contents of the doctor H2). be able to. In other words, this allows the diagnosis unit 15 to execute the collation process with higher accuracy (details will be described later).

  FIG. 7 is a flowchart illustrating an example of processing performed by the physical symptom specifying unit 13.

  First, the physical symptom specifying unit 13 fills in the examination record D1 (here, [Subject], [Assessment], and [Object]) based on pre-stored grammar rules and data related to a dictionary (not shown). Morphological analysis of the text data) (step S1). The morphological analysis method may be a method using any known algorithm such as a hidden Markov model or a rule base. Thus, the physical symptom specifying unit 13 decomposes the sentence written in the examination record D1 into words, and extracts nouns from the words.

  Next, the physical symptom specifying unit 13 searches for nouns related to the physical symptom candidates stored in the symptom candidate DB 16 among the nouns extracted from the [Subject] field and the [Assessment] field of the examination record D1, for example. Thereby, a physical symptom occurring in the patient H1 is specified (step S2). At this time, the physical symptom specifying unit 13 specifies, for example, the body part where the physical symptom is generated in the patient H1 based on the noun related to the body part extracted from the diagnosis record D1. And the physical symptom specific | specification part 13 collates the noun concerning the physical symptom extracted from the medical examination record D1, for example with the content of each item of the physical symptom memorize | stored in symptom candidate DB16, and the body which has generate | occur | produced in the patient H1 Identify symptoms.

  In addition, the collation process in this step S2 may be a method of calculating the degree of coincidence between the noun related to the physical symptom candidate stored in the symptom candidate DB 16 and the noun related to the physical symptom extracted from the examination record D1, A technique for calculating the degree of coincidence between vectors defining these may be used.

  Next, the physical symptom specifying unit 13 specifies the physical symptom occurring in the patient H1 from the symptom candidate DB 16 based on the examination result in the [Object] column of the diagnosis record D1 (step S3). At this time, the physical symptom specifying unit 13 sets a standard range for each type of physical examination (for example, blood pressure, pulse rate, respiratory rate, etc.), and the examination result in the [Object] column of the examination record D1 It is determined whether or not any of the numerical values is out of the standard range. Then, when there is a target outside the standard range, the physical symptom specifying unit 13 specifies the physical symptom corresponding to the target out of the standard range from the symptom candidate DB 16.

  In FIG. 6, items surrounded by a dotted line are examples of physical symptoms specified by the physical symptom specifying unit 13. Here, the physical symptom specifying unit 13 performs “acute” based on the remarks of the patient H1 entered in the [Subject] field of the examination record D1 shown in FIG. In addition to specifying the physical symptoms of “suffocation”, the upper-level items of “dyspnea” and “respiratory symptoms” are specified. In addition, the physical symptom identification unit 13 determines whether or not “angioedema” is based on the content of the test result entered in the [Object] column (for example, vital sign (blood pressure: 126/84, pulse: 78 times / min)). In addition to specifying physical symptoms, the upper layer item “skin symptoms” and the lower layer item “skin redness” are specified.

  In this way, the physical symptom specifying unit 13 refers to the symptom candidate DB 16 and specifies physical symptoms in an ontology format (that is, hierarchically).

  In addition, the method in which the physical symptom specific | specification part 13 specifies a physical symptom can be variously changed. In the above description, the physical symptom specifying unit 13 is configured to specify which physical symptom corresponds to, for example, a plurality of physical symptom candidates. 1) may be calculated.

  The physical symptom specifying unit 13 may use a nursing record or a care record created for the patient H1 instead of the diagnosis record D1 when specifying the physical symptom. However, from the viewpoint of the accuracy of information, it is preferable to use the diagnosis record D1.

[Adverse drug candidate extraction unit]
The side effect candidate extraction unit 14 refers to the side effect candidate DB 17 and extracts side effect candidates that may occur in the patient H1 based on the medication list D2 acquired by the medication list acquisition unit 12. Then, the side effect candidate extraction unit 14 sends the extracted side effect candidate data (hereinafter, abbreviated as “side effect candidate”) D2a to the diagnosis unit 15.

  FIG. 8 is a diagram illustrating an example of the configuration of the side effect candidate DB 17.

  For example, the side effect candidate DB 17 stores various side effect candidates hierarchically and diversified in an ontology format for each type of medicine. Further, the side effect candidate items listed in the side effect candidate DB 17 are more specifically or locally expressed as the lower level items.

  For example, the ontology of the side effect candidate DB 17 has “shock”, “anaphylaxis”, and “intracranial hemorrhage” as parallel lower-level items of “aspirin”, and “difficulty breathing” as parallel lower-level items of “anaphylaxis”. ”,“ Urticaria ”, and“ angioedema ”.

  More preferably, the side effect candidate DB 17 stores, in association with each side effect candidate, the possibility that the side effect candidate generally occurs. For example, in the case of “aspirin”, it is generally known that the above-mentioned “shock”, “anaphylaxis”, and “intracranial hemorrhage” occur as side effects with a high possibility of about 20%. On the other hand, as other side effects caused by “aspirin”, “gastrointestinal disorders, vomiting, abdominal pain, heartburn, constipation, diarrhea, esophagitis, swelling of the lips, vomiting, or nausea” is about 5% to 10% in the digestive system. It is known that “nausea, loss of appetite, or stomach discomfort” may occur with a probability of 0.1% to 5% (not shown in FIG. 8). As described above, by storing the possibility of occurrence of a side effect candidate in association with each of the side effect candidates, the diagnosis accuracy by the diagnosis unit 15 described later can be enhanced.

  Also, the ontology of the side effect candidate DB 17 more preferably has side effects caused by the interaction between one drug and another drug. This makes it possible to diagnose side effects caused by the interaction between one drug and another drug.

  For example, the side effect candidate extraction unit 14 searches the side effect candidate DB 17 based on the type of medicine taken by the patient H1 (for example, drug name), and extracts a side effect candidate. And the side effect candidate extraction part 14 which concerns on this embodiment extracts the ontology of the side effect candidate corresponding to a taking medicine with reference to the side effect candidate DB17.

  In addition, when there are a plurality of types of medications to be taken, the side effect candidate extraction unit 14 selects a candidate for a side effect that may occur in the patient H1 or a candidate for interaction with other medications for each of the plurality of types of medications. Extract.

  Each item of the side effect candidate stored in the side effect candidate DB 17 is set based on, for example, a drug information database provided by the Japan Pharmaceutical Information Center (JAPIC). However, each item of the side effect candidate may be set based on other arbitrary information.

[Diagnostic Department]
The diagnosis unit 15 collates the physical symptom D1a identified by the physical symptom identification unit 13 with the side effect candidate D2a extracted by the side effect candidate extraction unit 14, and diagnoses the presence or absence of the occurrence of a side effect caused by the medicine taken. When the patient H1 is taking a plurality of medicines, the diagnosis unit 15 performs a diagnosis process for each of the plurality of medicines taken by the patient H1. Then, the diagnosis unit 15 sends the diagnosis result D3 to the electronic medical record terminal 2.

  For example, the diagnosis unit 15 collates the physical symptom D1a with the side effect candidate D2a, and each item of the physical symptom D1a (each item surrounded by a dotted line in FIG. 6) corresponds to each item of the side effect candidate D2a (FIG. 8). It is determined whether or not the physical symptom is caused by the medicine taken depending on whether or not each item matches.

  At this time, the diagnosis unit 15 additionally adds information such as a possibility that the side effect of the item generally associated with each item of the side effect candidate D2a and the history information related to the medicine taken by the patient H1. It may be used.

  The collation process by the diagnosis unit 15 may use an arbitrary method. For example, the physical symptom candidates in the symptom candidate DB 16 and the side effect candidates in the side effect candidate DB 17 may be associated in advance. Further, a technique for calculating the degree of coincidence between nouns between the physical symptom D1a and the side effect candidate D2a may be used, or a technique for calculating the degree of coincidence between vectors defining these may be used. In addition, a method of calculating the similarity between the group of physical symptoms D1a and the group of side effect candidates D2a may be used.

  As a reference when the diagnosis unit 15 determines the diagnosis result, for example, the proportion of each item of the physical symptom D1a matches each item of the side effect candidate D2a (for example, the number of matching items), and each item of the physical symptom D1a A criterion such as whether or not the item corresponds to a characteristic item among the items of the side effect candidate D2a is used.

  FIG. 9 is a diagram for explaining the processing of the diagnosis unit 15.

  FIG. 9 shows an example of the result of collation processing performed by the diagnosis unit 15 for the side effect candidates (see FIG. 8) extracted from the side effect candidate DB 17.

  In FIG. 9, the diagnosis unit 15 determines that the two side effects candidates “dyspnea” and “angioedema” match the physical symptoms (see FIG. 6) identified by the physical symptom identification unit 13. Yes. Accordingly, the diagnosis unit 15 diagnoses that the physical symptom is caused by “aspirin”.

  In addition, when there are a plurality of types of medicines to be taken, the diagnosis unit 15 determines whether or not side effects caused by the medicines taken or whether they interact with other medicines are taken. Diagnose.

  And the diagnostic part 15 transmits the said diagnostic result with respect to the electronic medical record terminal 2 via the communication network N, for example. The diagnosis result is displayed on, for example, the display of the electronic medical record terminal 2 and used as information for examining whether the doctor H2 or the like changes the prescription.

  However, the diagnosis unit 15 may calculate a possibility that a physical symptom that occurs in a patient is caused by a side effect of a medicine taken. In addition to the above configuration, the diagnosis unit 15 may further include a function of searching for alternative medicines and indicating candidates.

[effect]
As described above, the side effect diagnosis apparatus 1 according to the present embodiment is based on the diagnosis record, nursing record, or care record D1 created for the patient H1, and the symptom candidate DB 16 that stores a plurality of physical symptom candidates. Based on the physical symptom identification unit 13 that identifies the physical symptom D1a occurring in the patient H1, the information D2 related to the ingested drug, and the side effect information DB 17 that stores the side effect candidates of a plurality of drugs, the patient The side effect candidate extraction unit 14 for extracting the side effect candidate D2a that may occur in the patient, the physical symptom D1a specified by the physical symptom specification unit 13 and the side effect candidate D2a extracted by the side effect candidate extraction unit 14 are collated and taken And a diagnosis unit 15 for diagnosing whether or not a side effect caused by the drug has occurred.

  Therefore, according to the side effect diagnostic apparatus 1 according to the present embodiment, it is possible to diagnose whether or not the physical symptom occurring in the patient H1 is a side effect caused by the medicine taken with high accuracy. Furthermore, this makes it possible to identify a medication that causes a side effect on the patient H1 among a plurality of medications taken by the patient H1.

  In particular, in the medical record, nursing record, or care record D1, in addition to objective data (for example, a test result obtained by examining the physical condition of the patient H1), as a result of a physical test that is abstract, Essential data that is difficult to appear is included (for example, the specific remarks of the patient H1 and the diagnosis contents diagnosed by the doctor H2 or the like based on experience). Therefore, like the side effect diagnosis apparatus 1 according to the present embodiment, by identifying physical symptoms using a medical record, it is more comprehensive as compared to an aspect in which physical symptoms are identified only from physical examination results. Or, it is possible to identify physical symptoms from various viewpoints. In other words, this can improve the accuracy when collating with a side effect candidate.

  In particular, in the side effect diagnosis apparatus 1 according to the present embodiment, the symptom candidate DB 16 and the side effect candidate DB 17 both store data in an ontology format. As a result, the collation process between the physical symptom and the side effect candidate can be executed in a hierarchical and multifaceted manner, so that a more accurate side effect diagnosis can be performed. In addition, by having separate ontology for the symptom candidate DB 16 and the side effect candidate DB 17, it is possible to avoid duplication of items related to physical symptoms for each drug in the side effect candidate DB 17, thereby suppressing the maximization of the side effect ontology. Can do.

  As mentioned above, although the specific example of this invention was demonstrated in detail, these are only illustrations and do not limit a claim. The technology described in the claims includes various modifications and changes of the specific examples illustrated above.

  According to the side effect diagnostic apparatus according to the present disclosure, it is possible to diagnose the presence or absence of the occurrence of side effects caused by the medicine taken.

U side effect diagnosis system 1 side effect diagnosis device 11 examination record acquisition unit 12 medication list acquisition unit 13 physical symptom identification unit 14 side effect candidate extraction unit 15 diagnosis unit 16 symptom candidate database 17 side effect candidate database 2 electronic medical record terminal 3 patient terminal

Claims (10)

A side effect diagnostic device for diagnosing the occurrence of side effects on patients caused by ingested drugs,
A body that identifies physical symptoms occurring in the patient based on a diagnosis record, nursing record, or care record created for the patient, and a symptom candidate database that stores information on a plurality of physical symptom candidates The symptom identification part,
Based on the information on the ingested drug and the side effect information database storing information on the side effect candidates of a plurality of drugs, the side effect candidate extraction unit that extracts the side effect candidates that may occur in the patient,
Checking the physical symptoms identified by the physical symptom identification unit and the side effect candidates extracted by the side effect candidate extraction unit, and diagnosing the presence or absence of the occurrence of the side effects caused by the ingested drug,
A side effect diagnosis apparatus comprising: If there are multiple types of ingested drugs,
The side effect candidate extraction unit extracts, for each of a plurality of types of ingested drugs, the side effect candidates that may occur in the patient or interaction candidates with other ingested drugs,
2. The side effect according to claim 1, wherein the diagnosis unit diagnoses, for each of a plurality of types of the ingested drug, whether or not the side effect caused by the ingested drug occurs or whether or not an interaction with the other ingested drug occurs. Diagnostic device. The physical symptom identification unit identifies the physical symptom based on a morphological analysis of the examination record, the nursing record, or the care record, and an analysis result of the morphological analysis and the symptom candidate database. 3. The side effect diagnosis device according to 1 or 2. The symptom candidate database stores concepts related to the physical symptom candidates in an ontology format,
The side effect diagnosis apparatus according to any one of claims 1 to 3, wherein the side effect information database stores concepts related to the side effect candidates in an ontology format. The physical symptom specifying unit specifies the physical symptom in an ontology format,
The side effect diagnosis device according to claim 4, wherein the side effect candidate extraction unit extracts the side effect candidates in an ontology format. The side effect information database stores, for each of the plurality of side effect candidates, the possibility of occurrence of the side effect candidates in association with each other,
The side effect diagnosis apparatus according to any one of claims 1 to 5. The examination record, the nursing record, or the care record includes information relating to a test result of the patient's physical examination, information relating to the patient's remarks, and the examination record, the nursing record, or the care record. The side effect diagnosis apparatus according to any one of claims 1 to 6, including information related to evaluation contents evaluated by the creator on the physical symptoms of the patient. The side effect diagnosis apparatus according to any one of claims 1 to 7, wherein the information related to the ingested drug is specified based on an intake record of the ingested drug input to a terminal held by the patient. The side effect diagnosis apparatus according to any one of claims 1 to 8, wherein the diagnosis unit transmits the result of the diagnosis to a terminal in which the examination record, the nursing record, or the care record is created. A side effect diagnosis method for diagnosing the occurrence of side effects on patients caused by ingested drugs,
Based on the examination record, nursing record, or care record created for the patient, and a symptom candidate database that stores information related to a plurality of physical symptom candidates, the physical symptom occurring in the patient is identified,
Based on the information on the ingested drug and the side effect information database storing information on the side effect candidates of a plurality of drugs, the side effect candidates that may occur in the patient are extracted,
Collating the identified physical symptoms with the extracted candidate for side effects, and diagnosing the presence or absence of the side effects caused by the ingested drug,
Side effect diagnosis method.

Images