<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v9i4e22797</article-id>
      <article-id pub-id-type="pmid">33885370</article-id>
      <article-id pub-id-type="doi">10.2196/22797</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Hybrid Model for Family History Information Identification and Relation Extraction: Development and Evaluation of an End-to-End Information Extraction System</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Wang</surname>
            <given-names>Yanshan</given-names>
          </name>
        </contrib>
        <contrib contrib-type="editor">
          <name>
            <surname>Shen</surname>
            <given-names>Feichen</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Zheng</surname>
            <given-names>Jiaping</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Abeysinghe</surname>
            <given-names>Rashmie</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Torii</surname>
            <given-names>Manabu</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>Youngjun</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Biomedical Informatics Center</institution>
            <institution>Medical University of South Carolina</institution>
            <addr-line>22 WestEdge Street Suite 200/Room WG213</addr-line>
            <addr-line>Charleston, SC, 29403</addr-line>
            <country>United States</country>
            <phone>1 843 792 4268</phone>
            <email>youngjun.kim.res@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9085-6686</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Heider</surname>
            <given-names>Paul M</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1589-4567</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Lally</surname>
            <given-names>Isabel RH</given-names>
          </name>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7699-7837</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Meystre</surname>
            <given-names>Stéphane M</given-names>
          </name>
          <degrees>PhD, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7632-9625</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Biomedical Informatics Center</institution>
        <institution>Medical University of South Carolina</institution>
        <addr-line>Charleston, SC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Computer Science</institution>
        <institution>College of Charleston</institution>
        <addr-line>Charleston, SC</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Youngjun Kim <email>youngjun.kim.res@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>4</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>22</day>
        <month>4</month>
        <year>2021</year>
      </pub-date>
      <volume>9</volume>
      <issue>4</issue>
      <elocation-id>e22797</elocation-id>
      <history>
        <date date-type="received">
          <day>30</day>
          <month>8</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>21</day>
          <month>10</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>15</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>19</day>
          <month>2</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Youngjun Kim, Paul M Heider, Isabel RH Lally, Stéphane M Meystre. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 22.04.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2021/4/e22797" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Family history information is important to assess the risk of inherited medical conditions. Natural language processing has the potential to extract this information from unstructured free-text notes to improve patient care and decision making. We describe the end-to-end information extraction system the Medical University of South Carolina team developed when participating in the 2019 National Natural Language Processing Clinical Challenge (n2c2)/Open Health Natural Language Processing (OHNLP) shared task.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This task involves identifying mentions of family members and observations in electronic health record text notes and recognizing the 2 types of relations (family member-living status relations and family member-observation relations). Our system aims to achieve a high level of performance by integrating heuristics and advanced information extraction methods. Our efforts also include improving the performance of 2 subtasks by exploiting additional labeled data and clinical text-based embedding models.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We present a hybrid method that combines machine learning and rule-based approaches. We implemented an end-to-end system with multiple information extraction and attribute classification components. For entity identification, we trained bidirectional long short-term memory deep learning models. These models incorporated static word embeddings and context-dependent embeddings. We created a voting ensemble that combined the predictions of all individual models. For relation extraction, we trained 2 relation extraction models. The first model determined the living status of each family member. The second model identified observations associated with each family member. We implemented online gradient descent models to extract related entity pairs. As part of postchallenge efforts, we used the BioCreative/OHNLP 2018 corpus and trained new models with the union of these 2 datasets. We also pretrained language models using clinical notes from the Medical Information Mart for Intensive Care (MIMIC-III) clinical database.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The voting ensemble achieved better performance than individual classifiers. In the entity identification task, our top-performing system reached a precision of 78.90% and a recall of 83.84%. Our natural language processing system for entity identification took 3rd place out of 17 teams in the challenge. We ranked 4th out of 9 teams in the relation extraction task. Our system substantially benefited from the combination of the 2 datasets. Compared to our official submission with F<sub>1</sub> scores of 81.30% and 64.94% for entity identification and relation extraction, respectively, the revised system yielded significantly better performance (<italic>P</italic>&#60;.05) with F<sub>1</sub> scores of 86.02% and 72.48%, respectively.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>We demonstrated that a hybrid model could be used to successfully extract family history information recorded in unstructured free-text notes. In this study, our approach to entity identification as a sequence labeling problem produced satisfactory results. Our postchallenge efforts significantly improved performance by leveraging additional labeled data and using word vector representations learned from large collections of clinical notes.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>natural language processing</kwd>
        <kwd>machine learning</kwd>
        <kwd>deep learning</kwd>
        <kwd>named entity recognition</kwd>
        <kwd>clinical entity identification</kwd>
        <kwd>relation extraction</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Family history (FH) information included in the electronic health record (EHR) is important to assess the risk of inherited medical conditions. For certain diseases such as breast cancer [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>] and colorectal cancer [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>], FH is an important risk factor. FH information has been recorded in both structured and narrative free text, but often documented only in the latter. Polubriaginof et al [<xref ref-type="bibr" rid="ref5">5</xref>] reported that free-text notes contained more comprehensive information than structured data. Natural language processing (NLP) has the potential to extract this information from unstructured free-text notes to improve patient care and decision making.</p>
      <p>This manuscript describes the end-to-end information extraction (IE) system the Medical University of South Carolina (MUSC) team developed when participating in the 2019 National Natural Language Processing Clinical Challenge (n2c2)/Open Health Natural Language Processing (OHNLP) track on FH extraction [<xref ref-type="bibr" rid="ref6">6</xref>]. This shared task is built on the BioCreative/OHNLP 2018 FH extraction task [<xref ref-type="bibr" rid="ref7">7</xref>]. It involves (1) identifying mentions of family members and observations in EHR text notes and (2) recognizing the relations between family members, observations, and living status.</p>
      <p>Entity identification and relation extraction are often considered subtasks of IE. The semantic types of concepts of interest have been defined for different target tasks. Named entity recognition (NER) was introduced in the sixth of a series of Message Understanding Conferences [<xref ref-type="bibr" rid="ref8">8</xref>] and Automatic Content Extraction programs [<xref ref-type="bibr" rid="ref9">9</xref>]. The goal of NER is to extract and classify proper named or specialized entities into predefined categories [<xref ref-type="bibr" rid="ref8">8</xref>]. Relation extraction deals with a pair of concepts [<xref ref-type="bibr" rid="ref10">10</xref>] (ie, binary relations) or higher-order relations, which are <italic>n</italic>-ary relations among <italic>n</italic> typed entities [<xref ref-type="bibr" rid="ref11">11</xref>]. It aims to determine whether entities are in a relation and how they are semantically related. Medical concept extraction is closely related to our target task and has advanced from the general text NER by sharing the algorithms and features. It has aimed to extract medical information such as disease diagnoses, medications, laboratory data, and appliances from EHR text notes [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref16">16</xref>].</p>
      <p>Several studies focusing on FH information have been reported. Goryachev et al [<xref ref-type="bibr" rid="ref17">17</xref>] created a rule-based system for identifying family members and their related diagnoses. They observed that FH was often mentioned intermixed with the patient's own medical history, making this task challenging. Bill et al [<xref ref-type="bibr" rid="ref18">18</xref>] developed an NLP system for extracting FH information from History and Physical notes. Their NLP pipeline identified family member and observation entities, relations between them, and attributes such as vital status and age. FH information extraction was the focus of the BioCreative/OHNLP 2018 task [<xref ref-type="bibr" rid="ref7">7</xref>]. The best performance on this shared task was achieved by Shi et al [<xref ref-type="bibr" rid="ref19">19</xref>] with F<sub>1</sub> scores of 89.01% on subtask 1 and 63.59% on subtask 2. They proposed joint modeling of entities and relations by 2 stacked neural networks with shared parameters.</p>
      <p>The goal of this study was to extract the health information of patients and their relatives from unstructured EHR notes. Our system aims to achieve a high level of performance in this task by integrating heuristics and advanced information extraction methods. We approach entity identification as a sequence labeling problem. We applied a bidirectional long short-term memory (Bi-LSTM) [<xref ref-type="bibr" rid="ref20">20</xref>] algorithm, a widely used structured prediction algorithm. The input of the LSTM network included vector representations generated by Embeddings from Language Models (ELMo) [<xref ref-type="bibr" rid="ref21">21</xref>] contextual embeddings. We hypothesized that applying the LSTM to this problem can yield accurate FH information extraction. Our voting ensemble is created based on the fact that the LSTM algorithm is not deterministic; that is, every time the model is trained, the results vary. The proposed ensemble can provide efficient and convenient integration of individual LSTM models. For relation extraction, we implemented online gradient descent (OGD) [<xref ref-type="bibr" rid="ref22">22</xref>] models with lexical features.</p>
      <p>This study's contribution also includes improved performance on both subtasks by exploiting additional labeled data and clinical text–based embedding models. We added other labeled data used in the previous shared task to the training set. We retrained the classifier using a larger set of training data. We also used word embeddings pretrained with large quantities of clinical text. Our experimental results show that these efforts significantly improve the performance of both subtasks, especially relation extraction.</p>
      <p>The following sections describe the details of the 2 subtasks and discuss IE models developed to recognize the entities and their relations from EHRs. We then present the experimental results and investigate the performance improvements resulting from our postchallenge efforts.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <p>Our research focuses on the extraction of mentions of family members and related information recorded in EHR text notes. The first subtask, entity identification, involves detecting 2 types of entities: family members and observations. Only relatives in the first degree (eg, ‘<italic>Mother</italic>’ and ‘<italic>Son</italic>’) and second degree (eg, ‘<italic>Grandparent</italic>’ and ‘<italic>Cousin</italic>’) are annotated [<xref ref-type="bibr" rid="ref7">7</xref>]. Other relatives such as ‘<italic>Spouse</italic>’ and ‘<italic>Nephew</italic>’ are excluded. The normalized name and the side of family are annotated as attributes of each family member. Observation (disease) entities in the family history are also annotated. The second subtask, relation extraction, is to determine the existence of relations between family members and other information (ie, living status or observation). Two types of relations were therefore annotated: family member-living status and family member-observation. For relations between a family member and living status, the score representing the health status of the family member is annotated. Negation information is annotated to indicate whether the observation is negated in the relation between a family member and the associated observation.</p>
      <sec>
        <title>Data Description</title>
        <p>Clinical text notes representing patient FH information were selected from the Mayo Employee and Community Health cohort [<xref ref-type="bibr" rid="ref7">7</xref>]. <xref ref-type="table" rid="table1">Table 1</xref> shows the number of annotated entities and relations in the training set. The training set includes 99 clinical notes with 801 family member and 978 observation entities. Living status entities are less common and account for about half of the number of family members. For the observation category, the number of relations is less than the number of entities. This means that some observations are not related to any family member.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Number of annotated entities and relations in the training set.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="320"/>
            <col width="340"/>
            <col width="340"/>
            <thead>
              <tr valign="top">
                <td>Variable</td>
                <td>Entities</td>
                <td>Relations</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Family member</td>
                <td>801</td>
                <td>N/A<sup>a</sup></td>
              </tr>
              <tr valign="top">
                <td>Living status</td>
                <td>415</td>
                <td>425</td>
              </tr>
              <tr valign="top">
                <td>Observation</td>
                <td>978</td>
                <td>753</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>N/A: not applicable because relations between family members were not annotated.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Entity Identification Methods</title>
        <p>We addressed entity identification with rule-based and machine learning–based approaches. We describe each approach and present a voting ensemble–based method.</p>
        <sec>
          <title>Rule-Based System for Family Member Entities</title>
          <p>Our rule-based system for family member entity recognition uses a sliding window with simple term matching and part-of-speech filtering. We used NLTK [<xref ref-type="bibr" rid="ref23">23</xref>] (a Python Natural Language Toolkit) to split each note into sentences and then each sentence into tokens annotated with part-of-speech tags. Each token matching a relevant family member term (eg, “<italic>daughter</italic>”, “<italic>son</italic>”, or “<italic>child</italic>”) that was also tagged as a noun (ie, NN, NNP, or NNS) was flagged as a valid mention.</p>
        </sec>
        <sec>
          <title>Machine Learning–Based Models</title>
          <p>We trained sequence labeling models using Bi-LSTM [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref24">24</xref>] to assign a semantic category label to each word in a sequence. Bi-LSTM can combine both forward and backward information of each word.</p>
          <p>For this sequence labelling problem, we tokenized the input text. The training data were annotated with BIO token tags (B: beginning, I: inside, or O: outside of an entity; eg, “B-observation” for a token at the beginning of an observation mention). We also included the outputs of the 2 external resources (the 2010 Informatics for Integrating Biology and the Bedside [i2b2] [<xref ref-type="bibr" rid="ref25">25</xref>] and MetaMapLite [<xref ref-type="bibr" rid="ref26">26</xref>]) described in the following paragraphs as inputs to the LSTM network. Similar to the word token, the prediction from each external resource was also encoded with BIO tags.</p>
          <p>First, we used the medical concept extraction model trained with the 2010 i2b2 challenge data [<xref ref-type="bibr" rid="ref25">25</xref>]. The training set containing 349 text documents was used to create a Bi-LSTM model that identified medical <italic>problem</italic>, <italic>treatment</italic>, and <italic>test</italic> concepts from the FH extraction task corpus. We also used MetaMapLite [<xref ref-type="bibr" rid="ref26">26</xref>] (2019 AA version) to identify Unified Medical Language System (UMLS) Metathesaurus concept mentions along with their semantic type. We aligned MetaMap outputs with the entity types of subtask 1 to choose the relevant semantic types. <xref ref-type="table" rid="table2">Table 2</xref> lists the 10 most frequently aligned UMLS semantic types used by MetaMap for observation entity extraction. The first and second columns display semantic type names and abbreviations. The third column shows the number of observation entities from the training corpus aligned with each semantic type. The last column shows the mapping probability for each semantic type and observation category. For instance, “Disease or Syndrome” was mapped to the observation category with a probability of 79.89%. We used the training data to automatically create these heuristics. We used all (21) semantic types with a mapping probability of over 70%. The output semantic type was converted to a family member or observation entity, such as B-family_member or I‑observation.</p>
          <p>Our Bi-LSTM model incorporated 2 embedding layers for pretrained word embeddings. We used dependency-based embeddings by Komninos and Manandhar [<xref ref-type="bibr" rid="ref27">27</xref>] as static word embeddings. These embeddings were trained using the structure of dependency graphs. They were built with the English Wikipedia Dump of August 2015. As context-dependent embeddings, we used the ELMo [<xref ref-type="bibr" rid="ref21">21</xref>] model trained on a dataset of 5.5 billion tokens from Wikipedia and the news crawl corpus. The output of each external resource (the 2010 i2b2 and MetaMapLite) was represented as a one-hot vector and mapped to a 10-dimensional embedding. The concatenation of these embeddings (2 pretrained embeddings and 2 one-hot vectors) was fed to the LSTM layer.</p>
          <p>To fine-tune the parameters of LSTM models, we randomly selected 10 documents from the training set (about 10% of the training set) as held-out data. We tuned the hyperparameters to maximize the F<sub>1</sub> score with the held-out data. After experimenting with different dropout [<xref ref-type="bibr" rid="ref28">28</xref>] rates of 10%, 20%, 30%, 40%, and 50%, the models were trained using the Nadam [<xref ref-type="bibr" rid="ref29">29</xref>] optimizer for 30 epochs with a dropout rate of 50%.</p>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>The 10 most frequent Unified Medical Language System (UMLS) semantic types aligned with labeled observations in the training set.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="400"/>
              <col width="200"/>
              <col width="200"/>
              <col width="200"/>
              <thead>
                <tr valign="top">
                  <td>Semantic type name</td>
                  <td>Abbreviation</td>
                  <td>Count</td>
                  <td>Probability, %</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Disease or syndrome</td>
                  <td>dsyn</td>
                  <td>433</td>
                  <td>79.89</td>
                </tr>
                <tr valign="top">
                  <td>Neoplastic process</td>
                  <td>neop</td>
                  <td>165</td>
                  <td>78.20</td>
                </tr>
                <tr valign="top">
                  <td>Mental or behavioral dysfunction</td>
                  <td>mobd</td>
                  <td>59</td>
                  <td>74.68</td>
                </tr>
                <tr valign="top">
                  <td>Sign or symptom</td>
                  <td>sosy</td>
                  <td>28</td>
                  <td>70.00</td>
                </tr>
                <tr valign="top">
                  <td>Congenital abnormality</td>
                  <td>cgab</td>
                  <td>27</td>
                  <td>90.00</td>
                </tr>
                <tr valign="top">
                  <td>Anatomical abnormality</td>
                  <td>anab</td>
                  <td>10</td>
                  <td>83.33</td>
                </tr>
                <tr valign="top">
                  <td>Body system</td>
                  <td>bdsy</td>
                  <td>8</td>
                  <td>72.73</td>
                </tr>
                <tr valign="top">
                  <td>Tissue</td>
                  <td>tisu</td>
                  <td>7</td>
                  <td>100.00</td>
                </tr>
                <tr valign="top">
                  <td>Cell</td>
                  <td>cell</td>
                  <td>5</td>
                  <td>83.33</td>
                </tr>
                <tr valign="top">
                  <td>Physiologic function</td>
                  <td>phsf</td>
                  <td>4</td>
                  <td>80.00</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <p>We trained 10 different Bi-LSTM models that use the same hyperparameters but differ in random weight initialization and shuffling of training data. Then, we created a voting ensemble method that combined the predictions of all Bi-LSTM trials. Although these LSTM models were trained with the same hyperparameters, we hypothesized that they can be contributory to the voting ensemble in terms of diversity. Reimers and Gurevych [<xref ref-type="bibr" rid="ref30">30</xref>] showed that nondeterministic LSTMs can even lead to statistically significant differences between multiple runs.</p>
          <p>The voting ensemble collected candidate entities that received more votes than the voting threshold. When there were overlapping text spans on 2 different entities, the entity with more votes was selected. For overlapping entities with the same vote count, the one produced by the higher-ranking model was selected. To determine the ranking of 10 individual models, we measured how each model agreed with the other 9 models. Rankings were based on F<sub>1</sub> scores measured with other models. The higher the average F<sub>1</sub> score, the higher the model ranking.</p>
        </sec>
        <sec>
          <title>Heuristic Rules for Family Member Attributes</title>
          <p>We assigned each family member entity a normalized form using a simple dictionary-based mapping. For example, a family member with the text “<italic>his dad</italic>” was assigned ‘<italic>Father.</italic>’ We changed the text to lower case and removed the numeric values (eg, <italic>“three uncles</italic>” becomes '<italic>Uncle</italic>'). We also looked at the preceding words to search for another family member term that modified the target entity. When such a term was found, normalization was performed taking it into account. For example, in the phrase “<italic>mother has sister,</italic>” the family member ‘<italic>sister</italic>’ was normalized to ‘<italic>Aunt.</italic>’</p>
          <p>Our rule-based system looked at words in sentences near the family member and considered the degree of relatives to determine the family side. For each family member who was not a first-degree relative, the side of family (ie, ‘<italic>Paternal</italic>’ or ‘<italic>Maternal</italic>’) was assigned. For each label, we compiled the list of cue words indicating the side of family. For example, the cues for <italic>Paternal</italic> included ‘<italic>paternal,</italic>’ ‘<italic>patient's father,</italic>’ ‘<italic>father had,</italic>’ and ‘<italic>paternal family history.</italic>’ First, we searched for cue words within the entity term itself. If no cue word was found, the search was expanded to sentence boundaries.</p>
        </sec>
      </sec>
      <sec>
        <title>Relation Extraction Methods</title>
        <p>Subtask 2 aimed to identify related pairs of 3 entity types: family members, observations, and living status. Two types of relation exist between the 2 entities: family member-living status relations and family member-observation relations. We trained 2 relation extraction models. The first model determined the living status of each family member. The second model identified observations associated with each family member.</p>
        <p>For 2 binary-class models, we defined lexical features: words contained in each concept, 7 preceding and 7 following words for each concept, and the words between the 2 concepts. We also created 1 feature to measure the number of family member entities appearing between the pair. We created 2 binary-class OGD (also called stochastic gradient descent) [<xref ref-type="bibr" rid="ref22">22</xref>] classifiers using the Vowpal Wabbit [<xref ref-type="bibr" rid="ref31">31</xref>] online learning library. This online learning algorithm is getting more attention recently in large-scale machine learning problems. Using the default hyperparameters, each model was trained for 100 iterations.</p>
        <p>Training examples included positive examples (participating in a relation) and negative examples (pairs of entities that are not related to each other). Pairs of reference standard entities were used to train the classifiers. Entity pairs identified by the aforementioned voting ensemble were used as test examples. We filtered out the negative examples when there was a carriage return character (‘\n’) between the pair.</p>
        <p>For living status relations, once we extracted phrases that represent the living status of each family member, we assigned scores for the <italic>alive</italic> and <italic>healthy</italic> attributes. We compiled <italic>not alive</italic> (ie, dead) and <italic>healthy</italic> cues from the training data and calculated the score using the text phrase of each living status entity. If our algorithm detected any trigger phrase of <italic>not alive</italic> (eg, “<italic>deceased,”</italic> “<italic>passed away</italic>,” and “<italic>no longer living</italic>”), the algorithm assigned a score of 0. Otherwise, if the family member was in good health (eg, “<italic>good general health</italic>,” “<italic>healthy</italic>,” and “<italic>alive and well</italic>”), the algorithm assigned a score of 4. If no cues of <italic>not alive</italic> or <italic>healthy</italic> were found, a score of 2 was assigned.</p>
        <p>For each observation entity in the relation, we needed to determine whether it was negated or not. We used FastContext [<xref ref-type="bibr" rid="ref32">32</xref>], an efficient and scalable Java implementation of the ConText algorithm [<xref ref-type="bibr" rid="ref33">33</xref>] with customized trigger terms. After manually analyzing the examples from the training data, we added new trigger terms such as “<italic>not aware of,</italic>” “<italic>not significant</italic>,” and “<italic>no family history of</italic>.” For this binary classification, the algorithm detected the negated contextual attribute in the sentence for the observation entity and assigned 1 of 2 values: <italic>Negated</italic> or <italic>Non_Negated</italic>.</p>
        <p>In summary, we built an end-to-end system with multiple IE and attribute classification components, as shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>. The architecture includes a voting ensemble with Bi-LSTM models that accept the outputs of the MetaMap and 2010 concept models, an OGD model that extracts relations between entities, and postprocessing modules for family side, name normalization, living status, and negation classification.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>End-to-end system architecture. Bi-LSTM: bidirectional long short-term memory; EHR: electronic health record; i2b2: Informatics for Integrating Biology and the Bedside; OGD: online gradient descent.</p>
          </caption>
          <graphic xlink:href="medinform_v9i4e22797_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Improvements to Both Subtasks After the Shared Task Challenge</title>
        <p>This subsection describes further improvements to both entity identification and relation extraction as postchallenge efforts. We made 2 major changes in the pipeline system. The first revision was the addition of labeled examples to the training data. We used another text collection created for the 2018 BioCreative/OHNLP shared task [<xref ref-type="bibr" rid="ref7">7</xref>] to build new Bi-LSTM and OGD models. The combined dataset included the original 99 clinical notes and 50 text files used in the 2018 BioCreative/OHNLP test set. Extending from the previous models used for submission to the shared task, we investigated how well the new model trained with the union of 2 datasets performed. We trained the new models by reusing the classifier configuration optimized with the 2019 training data.</p>
        <p>Next, we used word embeddings trained with clinical text to construct vector representations of words. We pretrained 2 language models. One was trained using fastText [<xref ref-type="bibr" rid="ref34">34</xref>] as static word embeddings, and the other was trained using ELMo [<xref ref-type="bibr" rid="ref21">21</xref>] contextual embeddings. We used all clinical notes from the Medical Information Mart for Intensive Care (MIMIC-III) clinical database (version 1.4) [<xref ref-type="bibr" rid="ref35">35</xref>]. We pretrained ELMo embeddings by following the default hyperparameter setting used for other publicly available ELMo models [<xref ref-type="bibr" rid="ref21">21</xref>]. Pretraining lasted about 3 months, and it was manually stopped after 1,073,750 iterations. This process was performed on a NVIDIA Tesla P4 GPU.</p>
        <p>From these pretrained language models, we generated word vectors as input features. Then, we created new Bi-LSTM models for entity identification. As with the previous models, these models were trained for 30 epochs with 50% dropout to the recurrent units. Naturally, the predictions of these new Bi-LSTM models were used to create test instances that paired the 2 entities for relation extraction. In the next section, we present the experimental results from our official submission and revised systems.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>The input for subtask 1 (entity identification) was clinical text notes. The entity annotation file for subtask 1 contains family member and observation entities, one entity per line. The family side is provided for each family member entity. For subtask 2 (relation extraction), entity annotations were additionally used as input. The relation annotation file for task 2 contains 2 entities with their relation, 1 relation per line. Each living status relation has a score to represent living status. In each observation relation, the negation of the observation entity was identified.</p>
      <sec>
        <title>Evaluation Metrics</title>
        <p>We measured recall, precision, and F<sub>1</sub> score (harmonic mean of recall and precision with equal weight). We used the 2019 n2c2/OHNLP shared task [<xref ref-type="bibr" rid="ref6">6</xref>] evaluation script to calculate performance measures. To be considered a true positive, the entity attributes must also match. For observation entities, a match was counted if the reference annotation contained 1 or more words in common with the system-detected concept.</p>
      </sec>
      <sec>
        <title>Results for the 2019 n2c2/OHNLP Shared Task</title>
        <p>The 2019 n2c2/OHNLP shared task corpus consisting of a test set of 117 clinical notes was used for the evaluation. First, we present the results generated by systems implemented for the 2019 n2c2/OHNLP shared task submission.</p>
        <p><xref ref-type="table" rid="table3">Table 3</xref> shows the microaveraged overall precision, recall, and F<sub>1</sub> score for each of our submissions. The following 3 systems were submitted for subtask 1: System 1.1 was a rule-based system for collecting family member entities and a voting ensemble with a voting threshold of 5 for extracting observation entities, system 1.2 was a voting ensemble consisting of 10 trials with a voting threshold of 5 for extracting family member and observation entities, and system 1.3 was a voting ensemble with a voting threshold of 6. Among them, system 1.2 achieved the highest F<sub>1</sub> score, 81.30%, in subtask 1.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Results produced for the 2019 National Natural Language Processing Clinical Challenge (n2c2)/Open Health Natural Language Processing (OHNLP) shared task.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="520"/>
            <col width="150"/>
            <col width="150"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="2">System</td>
                <td>Precision score</td>
                <td>Recall score</td>
                <td>F<sub>1</sub> score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 1 (entity)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System 1.1</td>
                <td>72.61</td>
                <td>86.01</td>
                <td>78.74</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System 1.2</td>
                <td>78.90</td>
                <td>83.84</td>
                <td>81.30</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System 1.3</td>
                <td>80.29</td>
                <td>81.98</td>
                <td>81.13</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 2 (relation)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System 2.1</td>
                <td>65.48</td>
                <td>64.41</td>
                <td>64.94</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System 2.2</td>
                <td>66.37</td>
                <td>62.78</td>
                <td>64.53</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>System 2.3</td>
                <td>68.23</td>
                <td>59.79</td>
                <td>63.73</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>Similarly, we submitted 3 systems for subtask 2: System 2.1 was an OGD model with input pairs generated from predictions of the voting ensemble with a voting threshold of 4, system 2.2 was an OGD model with outputs from system 1.2, and system 2.3 was an OGD model with outputs from system 1.3. System 2.1 achieved a higher F<sub>1</sub> score than the others. The range of vote thresholds for task submission was selected after experimenting with values from 1 to 10 on the validation set. The highest F<sub>1</sub> score was obtained in subtask 2 with a voting threshold of 5 on the validation set.</p>
      </sec>
      <sec>
        <title>Improved Results After the Shared Task</title>
        <p>We report the results of further improvements for both subtasks as described earlier. The contributions of features or data are shown in <xref ref-type="table" rid="table4">Table 4</xref>. Systems from rows 1 to 3 were developed for the 2019 n2c2/OHNLP challenge, and rows 4 and 5 were postchallenge efforts.</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Improved performance by feature or data accumulation.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="520"/>
            <col width="150"/>
            <col width="150"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="2">System</td>
                <td>Precision score</td>
                <td>Recall score</td>
                <td>F<sub>1</sub> score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 1 (entity)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(1) word</td>
                <td>78.50</td>
                <td>84.28</td>
                <td>81.26</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(2) + MetaMap, i2b2<sup>a</sup> 2010</td>
                <td>78.87</td>
                <td>84.34</td>
                <td>81.48</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(3) + voting</td>
                <td>78.90</td>
                <td>83.84</td>
                <td>81.30</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(4) + 2018 data (postchallenge)</td>
                <td>83.63</td>
                <td>86.69</td>
                <td>85.13</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(5) + MIMIC<sup>b</sup> embeddings (postchallenge, [2018 + 2019]<sub>mim</sub>)</td>
                <td>84.83</td>
                <td>87.24</td>
                <td>86.02</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 2 (relation)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(1) word</td>
                <td>65.35</td>
                <td>61.14</td>
                <td>63.14</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(2) + MetaMap, i2b2 2010</td>
                <td>66.34</td>
                <td>61.24</td>
                <td>63.66</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(3) + voting</td>
                <td>66.37</td>
                <td>62.78</td>
                <td>64.53</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(4) + 2018 data (postchallenge)</td>
                <td>72.15</td>
                <td>70.79</td>
                <td>71.46</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>(5) + MIMIC embeddings (postchallenge, [2018 + 2019]<sub>mim</sub>)</td>
                <td>73.27</td>
                <td>71.70</td>
                <td>72.48</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table4fn1">
              <p><sup>a</sup>i2b2: Informatics for Integrating Biology and the Bedside.</p>
            </fn>
            <fn id="table4fn2">
              <p><sup>b</sup>MIMIC: Medical Information Mart for Intensive Care.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>As a baseline, only sequences of word tokens were used as input to train the Bi-LSTM models (row 1). The system was enhanced with the output of MetaMapLite [<xref ref-type="bibr" rid="ref26">26</xref>] and the 2010 i2b2 [<xref ref-type="bibr" rid="ref25">25</xref>] concept model as inputs (row 2). For rows 1 and 2, we report the average value between the 10 trials of each Bi-LSTM model. From row 3, the results of applying the voting ensemble are displayed. For comparison, we report results with a voting threshold of 5. Row 4 shows a further performance improvement when the 2018 BioCreative/OHNLP shared task [<xref ref-type="bibr" rid="ref7">7</xref>] data were added. This additional training example achieved substantial performance improvements in both subtasks. Compared to the submission for the challenge (row 3), the recall increased by 8.01% (70.79%-62.78%) in subtask 2. MIMIC embeddings (row 5) allowed for an improvement over general text embeddings. They led to F<sub>1</sub> scores of 86.02% and 72.48% for subtask 1 and subtask 2, respectively. We used a chi‑squared test to measure statistical significance. The significance level was set to .05. The performance of the full-featured system, called <italic>(2018 + 2019)<sub>mim</sub></italic>, (row 5) was significantly better than other systems with <italic>P</italic> values &#60;.001 except the system with the 2018 BioCreative/OHNLP shared task data (row 4).</p>
        <p><xref ref-type="table" rid="table5">Table 5</xref> displays the precision, recall, and F<sub>1</sub> scores of relation categories produced by the (2018 + 2019)<sub>mim</sub> system. F<sub>1</sub> scores for living status relations were 84.62% and 74.72% for subtask 1 and subtask 2, respectively. It was more challenging to determine whether the pair of family member and observation was related. For observation relations, the F<sub>1</sub> score was 71.79%, which was lower than for living status relations. A manual analysis of labeled examples from the training set revealed that distant pairs of family member and observation appeared more often than living status entities. In addition, there were more unrelated entity pairs (ie, negative examples) because many observation entities were not involved in the relation.</p>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Results of full-featured system for each relation category.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="520"/>
            <col width="150"/>
            <col width="150"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="2">System</td>
                <td>Precision score</td>
                <td>Recall score</td>
                <td>F<sub>1</sub> score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 1 (entity)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Living status</td>
                <td>83.08</td>
                <td>86.21</td>
                <td>84.62</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Observation</td>
                <td>85.99</td>
                <td>87.92</td>
                <td>86.94</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Overall</td>
                <td>84.83</td>
                <td>87.24</td>
                <td>86.02</td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 2 (relation)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Living status</td>
                <td>73.28</td>
                <td>76.22</td>
                <td>74.72</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Observation</td>
                <td>73.27</td>
                <td>70.37</td>
                <td>71.79</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Overall</td>
                <td>73.27</td>
                <td>71.70</td>
                <td>72.48</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>The experimental results show that our end-to-end pipeline system substantially benefited from the combination of the 2 datasets. Another finding is that a voting ensemble could achieve better performance than individual classifiers. This section analyzes the improvements resulting from the voting ensemble method. We also describe the detailed results of attribute classification.</p>
      <sec>
        <title>Voting Ensemble Analysis</title>
        <p>We analyzed the performance of the voting ensemble at each voting threshold. <xref rid="figure2" ref-type="fig">Figure 2</xref> shows the results of the voting ensembles with 5 trials of the (2018 + 2019)<sub>mim</sub> system. The graphs on the left and right represent the results of subtask 1 and subtask 2, respectively. The y-axis scale of each graph does not start at zero to focus on the value ranges of interest. The results with voting thresholds ranging from 1 to 10 are presented. The curves show that as the threshold gets higher, precision increases but recall simultaneously decreases. When the threshold was set to 3, the ensemble achieved the highest F<sub>1</sub> score (86.07%) in subtask 1. For subtask 2, the ensemble obtained an F<sub>1</sub> score of 72.48% at the voting threshold of 5.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Results of the voting ensemble for (A) subtask 1: entity identification and (B) subtask 2: relation extraction.</p>
          </caption>
          <graphic xlink:href="medinform_v9i4e22797_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Attribute Classification Analysis</title>
        <p>We applied heuristics to determine the attributes of entities. As the entity-level reference standard in the test set was being withheld, we evaluated the performance of these rule-based methods on the training set. <xref ref-type="table" rid="table6">Table 6</xref> shows the accuracy of the 4 classification tasks with the given reference standard concepts. Accuracy was computed as the percentage of correct predictions among total instances. The accuracy of family member normalization was 94.01%. Our classifier rarely failed to assign normalized terms to some entities. For example, our dictionary did not contain normalized terms for “<italic>twin</italic>” and “<italic>paternal relatives.</italic>” Most errors occurred when the normalized term did not match the actual relationship with the patient. For example, although it said “<italic>brother</italic>” in the text, it sometimes referred to the relationship with the patient’s parents, not the patient himself. The classifier often could not determine the family member as the patient's “<italic>Uncle.</italic>” This type of error was propagated in family-side decisions because the family-side information should only be provided to first-class relatives.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Accuracy of attribute classification of given reference standard concepts.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="500"/>
            <col width="500"/>
            <thead>
              <tr valign="top">
                <td>Task</td>
                <td>Accuracy (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Normalization of family members</td>
                <td>94.01</td>
              </tr>
              <tr valign="top">
                <td>Determination of the side of family</td>
                <td>95.38</td>
              </tr>
              <tr valign="top">
                <td>Assessment of family member’s living status</td>
                <td>92.53</td>
              </tr>
              <tr valign="top">
                <td>Detection of negation information for observations</td>
                <td>98.06</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In addition to the entity-level assessment described in the previous paragraph, we conducted another document-level evaluation of the entity attributes against the test set. To measure the performance impact of each attribute classification, the system was tested by ignoring one attribute of the entity. <xref ref-type="table" rid="table7">Table 7</xref> shows the results of the 2 subtasks on the test set by the (2018 + 2019)<sub>mim</sub> system. We report results for living status and negative information only for subtask 2 because they are not considered in subtask 1. A match is made if the system correctly detects an entity while the attribute is ignored. Compared to the default evaluation, which considered all attributes, it led to higher values for all metrics. Ignoring living status scores had the biggest impact. If the living status of every family member was correctly determined, the F<sub>1</sub> score could be increased by about 2%. Negative information had the least impact because it only applied to observations and might have been determined more accurately than other attributes.</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>Performance impact of attribute classification.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="520"/>
            <col width="150"/>
            <col width="150"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="2">System</td>
                <td>Precision score</td>
                <td>Recall score</td>
                <td>F<sub>1</sub> score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 1 (entity)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Default evaluation</td>
                <td>84.83</td>
                <td>87.24</td>
                <td>86.02</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ignoring the side of the family</td>
                <td>85.92</td>
                <td>89.11</td>
                <td>87.49</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ignoring the living status</td>
                <td>N/A<sup>a</sup></td>
                <td>N/A<sup>a</sup></td>
                <td>N/A<sup>a</sup></td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ignoring negation</td>
                <td>N/A<sup>b</sup></td>
                <td>N/A<sup>b</sup></td>
                <td>N/A<sup>b</sup></td>
              </tr>
              <tr valign="top">
                <td colspan="2">
                  <bold>Subtask 2 (relation)</bold>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Default evaluation</td>
                <td>73.27</td>
                <td>71.70</td>
                <td>72.48</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ignoring the side of the family</td>
                <td>75.33</td>
                <td>73.64</td>
                <td>74.48</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ignoring the living status</td>
                <td>75.40</td>
                <td>73.78</td>
                <td>74.58</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ignoring negation</td>
                <td>73.85</td>
                <td>72.90</td>
                <td>73.37</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table7fn1">
              <p><sup>a</sup>N/A: not applicable as the living status information was removed from evaluation for subtask 1.</p>
            </fn>
            <fn id="table7fn2">
              <p><sup>b</sup>N/A: not applicable as the negation information was removed from evaluation for subtask 1.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>We observed in this study that determining the voting threshold can be challenging for both subtasks. Our results showed that the best performing voting ensemble for one task did not achieve the highest accuracy for the other task. More efficient ensemble approaches will be desired to provide more diversity between individual models and reduce the error rate through optimal control of agreements among them. In the relation extraction task, the negative examples were filtered out when there was a carriage return character between the pairs, because they rarely appeared in the training data (about 2.6%). This instance pruning would make it impossible to find pairs of entities that existed in different sentences but were related. When training new models by combining 2 corpora, we reused the classifier configuration optimized for the 2019 n2c2 model. New development data randomly selected from both corpora would be needed for hyperparameter tuning.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>We presented a hybrid method that combined machine learning and rule-based approaches developed as part of the 2019 n2c2/OHNLP track on FH extraction [<xref ref-type="bibr" rid="ref6">6</xref>]. The MUSC team ranked 3rd and 4th among the participating teams in subtask 1 and subtask 2, respectively. This study demonstrated that our end-to-end pipeline system could successfully extract FH information recorded in unstructured narrative free text. Our experimental results confirmed that the voting ensemble of multiple trials outperformed the individual classifiers that produced nondeterministic results. Our postchallenge efforts significantly improved performance by leveraging additional labeled data and using word vector representations learned from large collections of clinical notes.</p>
        <p>Further research includes creating machine learning–based classifiers that will replace rule-based systems that determine the attributes of entities. They could lead to more accurate results on attribute classification as reported in several studies carried out for similar clinical NLP tasks [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref39">39</xref>]. Another direction for future work is to exploit unlabeled data to collect texts from the family history section. For efficient extension of the amount of training data, semisupervised learning can be employed with an instance selection method that uses text similarity measures to consider representativeness and diversity [<xref ref-type="bibr" rid="ref40">40</xref>].</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">Bi-LSTM</term>
          <def>
            <p>bidirectional long short-term memory</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ELMo</term>
          <def>
            <p>embeddings from language models</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FH</term>
          <def>
            <p>family history</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">i2b2</term>
          <def>
            <p>Informatics for Integrating Biology and the Bedside</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">IE</term>
          <def>
            <p>information extraction</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">LSTM</term>
          <def>
            <p>long short-term memory</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">MIMIC</term>
          <def>
            <p>Medical Information Mart for Intensive Care</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">MUSC</term>
          <def>
            <p>Medical University of South Carolina</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">n2c2</term>
          <def>
            <p>National Natural Language Processing Clinical Challenges</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">NER</term>
          <def>
            <p>named entity recognition</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">OGD</term>
          <def>
            <p>online gradient descent</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">OHNLP</term>
          <def>
            <p>Open Health Natural Language Processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">UMLS</term>
          <def>
            <p>unified medical language system</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This research was supported in part by the National Cancer Institute (R42CA180190) and the SmartState endowment. We gratefully acknowledge the efforts and support of the 2019 n2c2 shared task organizers.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>YK and PH made substantial contributions to the design and implementation of the research and to the analysis of the experimental results. All authors drafted the work or revised it critically. YK drafted the initial manuscript. PH and SM provided critical revision of the manuscript. All authors gave final approval of the version to be published. All authors agree to be accountable for all aspects of the work in ensuring that questions related to the accuracy or integrity of any part of the work are appropriately investigated and resolved.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Colditz</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Rosner</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Speizer</surname>
              <given-names>FE</given-names>
            </name>
          </person-group>
          <article-title>Risk factors for breast cancer according to family history of breast cancer. For the Nurses' Health Study Research Group</article-title>
          <source>J Natl Cancer Inst</source>
          <year>1996</year>
          <month>03</month>
          <day>20</day>
          <volume>88</volume>
          <issue>6</issue>
          <fpage>365</fpage>
          <lpage>71</lpage>
          <pub-id pub-id-type="doi">10.1093/jnci/88.6.365</pub-id>
          <pub-id pub-id-type="medline">8609646</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guttmacher</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>FS</given-names>
            </name>
            <name name-style="western">
              <surname>Carmona</surname>
              <given-names>RH</given-names>
            </name>
          </person-group>
          <article-title>The family history--more important than ever</article-title>
          <source>N Engl J Med</source>
          <year>2004</year>
          <month>11</month>
          <day>25</day>
          <volume>351</volume>
          <issue>22</issue>
          <fpage>2333</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMsb042979</pub-id>
          <pub-id pub-id-type="medline">15564550</pub-id>
          <pub-id pub-id-type="pii">351/22/2333</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fuchs</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Giovannucci</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Colditz</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Hunter</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Speizer</surname>
              <given-names>FE</given-names>
            </name>
            <name name-style="western">
              <surname>Willett</surname>
              <given-names>WC</given-names>
            </name>
          </person-group>
          <article-title>A prospective study of family history and the risk of colorectal cancer</article-title>
          <source>N Engl J Med</source>
          <year>1994</year>
          <month>12</month>
          <day>22</day>
          <volume>331</volume>
          <issue>25</issue>
          <fpage>1669</fpage>
          <lpage>74</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJM199412223312501</pub-id>
          <pub-id pub-id-type="medline">7969357</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Askling</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dickman</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Karlén</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Broström</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Lapidus</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Löfberg</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ekbom</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Family history as a risk factor for colorectal cancer in inflammatory bowel disease</article-title>
          <source>Gastroenterology</source>
          <year>2001</year>
          <month>05</month>
          <volume>120</volume>
          <issue>6</issue>
          <fpage>1356</fpage>
          <lpage>62</lpage>
          <pub-id pub-id-type="doi">10.1053/gast.2001.24052</pub-id>
          <pub-id pub-id-type="medline">11313305</pub-id>
          <pub-id pub-id-type="pii">S0016508501665193</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Polubriaginof</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Tatonetti</surname>
              <given-names>NP</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>An Assessment of Family History Information Captured in an Electronic Health Record</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2015</year>
          <volume>2015</volume>
          <fpage>2035</fpage>
          <lpage>42</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26958303"/>
          </comment>
          <pub-id pub-id-type="medline">26958303</pub-id>
          <pub-id pub-id-type="pmcid">PMC4765557</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Henry</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Uzuner</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Family History Extraction From Synthetic Clinical Narratives Using Natural Language Processing: Overview and Evaluation of a Challenge Data Set and Solutions for the 2019 National NLP Clinical Challenges (n2c2)/Open Health Natural Language Processing (OHNLP) Competition</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>01</month>
          <day>27</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e24008</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/1/e24008/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24008</pub-id>
          <pub-id pub-id-type="medline">33502329</pub-id>
          <pub-id pub-id-type="pii">v9i1e24008</pub-id>
          <pub-id pub-id-type="pmcid">PMC7875692</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rastegar-Mojarad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Overview of the BioCreative/OHNLP 2018 Family History Extraction Task</article-title>
          <year>2018</year>
          <conf-name>ACM International Conference on Bioinformatics, Computational Biology, and Health Informatics</conf-name>
          <conf-date>August 29-September 1, 2018</conf-date>
          <conf-loc>Washington DC</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3233547.3233672</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grishman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sundheim</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Message Understanding Conference-6: A Brief History</article-title>
          <source>Proceedings of the 16th Conference on Computational Linguistics - Volume 1</source>
          <year>1996</year>
          <conf-name>16th Conference on Computational Linguistics</conf-name>
          <conf-date>August 1996</conf-date>
          <conf-loc>Stroudsburg, PA</conf-loc>
          <fpage>466</fpage>
          <lpage>471</lpage>
          <pub-id pub-id-type="doi">10.3115/992628.992709</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Doddington</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Przybocki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ramshaw</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Strassel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Weischedel</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The Automatic Content Extraction (ACE) Program Tasks, Data, and Evaluation</article-title>
          <year>2004</year>
          <conf-name>Fourth International Conference on Language Resources and Evaluation (LREC-)</conf-name>
          <conf-date>May 2004</conf-date>
          <conf-loc>Lisbon, Portugal</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chinchor</surname>
              <given-names>NA</given-names>
            </name>
          </person-group>
          <article-title>Overview of MUC-7/MET-2</article-title>
          <year>1998</year>
          <conf-name>Seventh Message Understanding Conference (MUC-7)</conf-name>
          <conf-date>April 29-May 1, 1998</conf-date>
          <conf-loc>Fairfax, VA</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kulick</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Winters</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Simple algorithms for complex relation extraction with applications to biomedical IE</article-title>
          <year>2005</year>
          <conf-name>Proceedings of the 43rd Annual Meeting on Association for Computational Linguistics</conf-name>
          <conf-date>June 2005</conf-date>
          <conf-loc>Ann Arbor, MI</conf-loc>
          <fpage>491</fpage>
          <lpage>498</lpage>
          <pub-id pub-id-type="doi">10.3115/1219840.1219901</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Friedman</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Alderson</surname>
              <given-names>PO</given-names>
            </name>
            <name name-style="western">
              <surname>Austin</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Cimino</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>SB</given-names>
            </name>
          </person-group>
          <article-title>A general natural-language text processor for clinical radiology</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>1994</year>
          <volume>1</volume>
          <issue>2</issue>
          <fpage>161</fpage>
          <lpage>74</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/7719797"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.1994.95236146</pub-id>
          <pub-id pub-id-type="medline">7719797</pub-id>
          <pub-id pub-id-type="pmcid">PMC116194</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Christensen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Haug</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Fiszman</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>MPLUS: A Probabilistic Medical Language Understanding System</article-title>
          <year>2002</year>
          <conf-name>ACL-02 Workshop on Natural Language Processing in the Biomedical Domain</conf-name>
          <conf-date>July 2002</conf-date>
          <conf-loc>Philadelphia, PA</conf-loc>
          <fpage>29</fpage>
          <lpage>36</lpage>
          <pub-id pub-id-type="doi">10.3115/1118149.1118154</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Heinze</surname>
              <given-names>DT</given-names>
            </name>
            <name name-style="western">
              <surname>Morsch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sheffer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jimmink</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jennings</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Morsch</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>LifeCode: A deployed application for automated medical coding</article-title>
          <source>AI Magazine</source>
          <year>2001</year>
          <volume>22</volume>
          <issue>2</issue>
          <fpage>76</fpage>
          <pub-id pub-id-type="doi">10.1609/aimag.v22i2.1562</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>QT</given-names>
            </name>
            <name name-style="western">
              <surname>Goryachev</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Weiss</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sordo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Lazarus</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Extracting principal diagnosis, co-morbidity and smoking status for asthma research: evaluation of a natural language processing system</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2006</year>
          <month>07</month>
          <day>26</day>
          <volume>6</volume>
          <fpage>30</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-6-30"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-6-30</pub-id>
          <pub-id pub-id-type="medline">16872495</pub-id>
          <pub-id pub-id-type="pii">1472-6947-6-30</pub-id>
          <pub-id pub-id-type="pmcid">PMC1553439</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Savova</surname>
              <given-names>GK</given-names>
            </name>
            <name name-style="western">
              <surname>Masanz</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ogren</surname>
              <given-names>PV</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sohn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kipper-Schuler</surname>
              <given-names>KC</given-names>
            </name>
            <name name-style="western">
              <surname>Chute</surname>
              <given-names>CG</given-names>
            </name>
          </person-group>
          <article-title>Mayo clinical Text Analysis and Knowledge Extraction System (cTAKES): architecture, component evaluation and applications</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2010</year>
          <volume>17</volume>
          <issue>5</issue>
          <fpage>507</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20819853"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.2009.001560</pub-id>
          <pub-id pub-id-type="medline">20819853</pub-id>
          <pub-id pub-id-type="pii">17/5/507</pub-id>
          <pub-id pub-id-type="pmcid">PMC2995668</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goryachev</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng-Treitler</surname>
              <given-names>Q</given-names>
            </name>
          </person-group>
          <article-title>Identification and extraction of family history information from clinical reports</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2008</year>
          <month>11</month>
          <day>06</day>
          <fpage>247</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/18999129"/>
          </comment>
          <pub-id pub-id-type="medline">18999129</pub-id>
          <pub-id pub-id-type="pmcid">PMC2656021</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bill</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pakhomov</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Winden</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Carter</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Melton</surname>
              <given-names>GB</given-names>
            </name>
          </person-group>
          <article-title>Automated extraction of family history information from clinical notes</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2014</year>
          <volume>2014</volume>
          <fpage>1709</fpage>
          <lpage>17</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25954443"/>
          </comment>
          <pub-id pub-id-type="medline">25954443</pub-id>
          <pub-id pub-id-type="pmcid">PMC4419952</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Family history information extraction via deep joint learning</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <month>12</month>
          <day>27</day>
          <volume>19</volume>
          <issue>Suppl 10</issue>
          <fpage>277</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-019-0995-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-019-0995-5</pub-id>
          <pub-id pub-id-type="medline">31881967</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-019-0995-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC6933634</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hochreiter</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidhuber</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Long short-term memory</article-title>
          <source>Neural Comput</source>
          <year>1997</year>
          <month>11</month>
          <day>15</day>
          <volume>9</volume>
          <issue>8</issue>
          <fpage>1735</fpage>
          <lpage>80</lpage>
          <pub-id pub-id-type="doi">10.1162/neco.1997.9.8.1735</pub-id>
          <pub-id pub-id-type="medline">9377276</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Neumann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Iyyer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gardner</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zettlemoyer</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>Deep contextualized word representations. Association for Computational Linguistics; New Orleans, Louisiana</source>
          <year>2018</year>
          <access-date>2021-04-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1802.05365">https://arxiv.org/abs/1802.05365</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bottou</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Saad</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Online learning and stochastic approximations</article-title>
          <source>On-line learning in neural networks</source>
          <year>1999</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>Cambridge University Press</publisher-name>
          <fpage>9</fpage>
          <lpage>42</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bird</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Loper</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>NLTK: the Natural Language Toolkit</article-title>
          <year>2004</year>
          <conf-name>ACL-02 Workshop on Effective tools and methodologies for teaching natural language processing and computational linguistics</conf-name>
          <conf-date>July 2004</conf-date>
          <conf-loc>Barcelona, Spain</conf-loc>
          <fpage>214</fpage>
          <lpage>217</lpage>
          <pub-id pub-id-type="doi">10.3115/1118108.1118117</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schuster</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Paliwal</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Bidirectional recurrent neural networks</article-title>
          <source>IEEE Trans. Signal Process</source>
          <year>1997</year>
          <volume>45</volume>
          <issue>11</issue>
          <fpage>2673</fpage>
          <lpage>2681</lpage>
          <pub-id pub-id-type="doi">10.1109/78.650093</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Uzuner</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>South</surname>
              <given-names>BR</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>DuVall</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>2010 i2b2/VA challenge on concepts, assertions, and relations in clinical text</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2011</year>
          <volume>18</volume>
          <issue>5</issue>
          <fpage>552</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21685143"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2011-000203</pub-id>
          <pub-id pub-id-type="medline">21685143</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2011-000203</pub-id>
          <pub-id pub-id-type="pmcid">PMC3168320</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aronson</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Lang</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>An overview of MetaMap: historical perspective and recent advances</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2010</year>
          <volume>17</volume>
          <issue>3</issue>
          <fpage>229</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20442139"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.2009.002733</pub-id>
          <pub-id pub-id-type="medline">20442139</pub-id>
          <pub-id pub-id-type="pii">17/3/229</pub-id>
          <pub-id pub-id-type="pmcid">PMC2995713</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Komninos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Manandhar</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Dependency based embeddings for sentence classification tasks</article-title>
          <year>2016</year>
          <conf-name>2016 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</conf-name>
          <conf-date>June 2016</conf-date>
          <conf-loc>San Diego, CA</conf-loc>
          <fpage>1490</fpage>
          <lpage>1500</lpage>
          <pub-id pub-id-type="doi">10.18653/v1/n16-1175</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Hinton</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Krizhevsky</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sutskever</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Salakhutdinov</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Dropout: a simple way to prevent neural networks from overfitting</article-title>
          <source>The Journal of Machine Learning Research</source>
          <year>2014</year>
          <volume>15</volume>
          <issue>1</issue>
          <fpage>58</fpage>
          <pub-id pub-id-type="doi">10.5555/2627435.2670313</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dozat</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Incorporating nesterov momentum into adam</article-title>
          <year>2016</year>
          <conf-name>International Conference on Learning Representations (ICLR) 2016</conf-name>
          <conf-date>May 2-4, 2016</conf-date>
          <conf-loc>San Juan, Puerto Rico</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reimers</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gurevych</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Reporting Score Distributions Makes a Difference: Performance Study of LSTM-networks for Sequence Tagging</article-title>
          <year>2017</year>
          <conf-name>Conference on Empirical Methods in Natural Language Processing</conf-name>
          <conf-date>September 7–11, 2017</conf-date>
          <conf-loc>Copenhagen, Denmark</conf-loc>
          <pub-id pub-id-type="doi">10.18653/v1/d17-1035</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Langford</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Strehl</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Vowpal wabbit online learning project: Technical report</article-title>
          <source>Machine learning and learning theory research</source>
          <year>2007</year>
          <month>12</month>
          <day>21</day>
          <access-date>2019-12-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://hunch.net/?p=309">https://hunch.net/?p=309</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hurdle</surname>
              <given-names>JF</given-names>
            </name>
          </person-group>
          <article-title>Trie-based rule processing for clinical NLP: A use-case study of n-trie, making the ConText algorithm more efficient and scalable</article-title>
          <source>J Biomed Inform</source>
          <year>2018</year>
          <month>09</month>
          <volume>85</volume>
          <fpage>106</fpage>
          <lpage>113</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(18)30157-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2018.08.002</pub-id>
          <pub-id pub-id-type="medline">30092358</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(18)30157-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC6171746</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chapman</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Chu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dowling</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>ConText: An algorithm for identifying contextual features from clinical text</article-title>
          <year>2007</year>
          <conf-name>Workshop on BioNLP: Biological, Translational, and Clinical Language Processing</conf-name>
          <conf-date>June 2007</conf-date>
          <conf-loc>Prague, Czech Republic</conf-loc>
          <fpage>81</fpage>
          <lpage>88</lpage>
          <pub-id pub-id-type="doi">10.3115/1572392.1572408</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bojanowski</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Grave</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Joulin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mikolov</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Enriching Word Vectors with Subword Information</article-title>
          <source>TACL</source>
          <year>2017</year>
          <month>12</month>
          <volume>5</volume>
          <fpage>135</fpage>
          <lpage>146</lpage>
          <pub-id pub-id-type="doi">10.1162/tacl_a_00051</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>AEW</given-names>
            </name>
            <name name-style="western">
              <surname>Pollard</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lehman</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ghassemi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Moody</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Szolovits</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Mark</surname>
              <given-names>RG</given-names>
            </name>
          </person-group>
          <article-title>MIMIC-III, a freely accessible critical care database</article-title>
          <source>Sci Data</source>
          <year>2016</year>
          <month>05</month>
          <day>24</day>
          <volume>3</volume>
          <fpage>160035</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/sdata.2016.35"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/sdata.2016.35</pub-id>
          <pub-id pub-id-type="medline">27219127</pub-id>
          <pub-id pub-id-type="pii">sdata201635</pub-id>
          <pub-id pub-id-type="pmcid">PMC4878278</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aberdeen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bayer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yeniterzi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wellner</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hanauer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Malin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hirschman</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The MITRE Identification Scrubber Toolkit: design, training, and assessment</article-title>
          <source>Int J Med Inform</source>
          <year>2010</year>
          <month>12</month>
          <volume>79</volume>
          <issue>12</issue>
          <fpage>849</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2010.09.007</pub-id>
          <pub-id pub-id-type="medline">20951082</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(10)00168-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>de Bruijn</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Cherry</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kiritchenko</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Machine-learned solutions for three stages of clinical information extraction: the state of the art at i2b2 2010</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2011</year>
          <volume>18</volume>
          <issue>5</issue>
          <fpage>557</fpage>
          <lpage>62</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21565856"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2011-000150</pub-id>
          <pub-id pub-id-type="medline">21565856</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2011-000150</pub-id>
          <pub-id pub-id-type="pmcid">PMC3168309</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Riloff</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Meystre</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Improving classification of medical assertions in clinical notes</article-title>
          <year>2011</year>
          <conf-name>49th Annual Meeting of the Association for Computational Linguistics: Human Language Technologies</conf-name>
          <conf-date>June 2011</conf-date>
          <conf-loc>Portland, OR</conf-loc>
          <fpage>311</fpage>
          <lpage>316</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bejan</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Vanderwende</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Xia</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Yetisgen-Yildiz</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Assertion modeling and its role in clinical phenotype identification</article-title>
          <source>J Biomed Inform</source>
          <year>2013</year>
          <month>02</month>
          <volume>46</volume>
          <issue>1</issue>
          <fpage>68</fpage>
          <lpage>74</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(12)00148-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2012.09.001</pub-id>
          <pub-id pub-id-type="medline">23000479</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(12)00148-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Riloff</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Meystre</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Exploiting Unlabeled Texts with Clustering-based Instance Selection for Medical Relation Classification</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2017</year>
          <conf-name>AMIA Annual Symposium Proceedings</conf-name>
          <conf-date>Nov 4-Nov 8</conf-date>
          <conf-loc>Washington, DC</conf-loc>
          <fpage>1060</fpage>
          <lpage>1069</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29854174"/>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
