<?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">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</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">v19i12e417</article-id>
    <article-id pub-id-type="pmid">29254915</article-id>
    <article-id pub-id-type="doi">10.2196/jmir.8536</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>Text Simplification Using Consumer Health Vocabulary to Generate Patient-Centered Radiology Reporting: Translation and Evaluation</article-title>
    </title-group>
    <contrib-group>
      <contrib contrib-type="editor">
        <name>
          <surname>Parra-Calderón</surname>
          <given-names>Carlos Luis</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Cruz-Díaz</surname>
          <given-names>Noa Patricia</given-names>
        </name>
      </contrib>
      <contrib contrib-type="reviewer">
        <name>
          <surname>Irizarry</surname>
          <given-names>Taya</given-names>
        </name>
      </contrib>
    </contrib-group>
    <contrib-group>
      <contrib contrib-type="author" id="contrib1" corresp="yes">
      <name name-style="western">
        <surname>Qenam</surname>
        <given-names>Basel</given-names>
      </name>
      <degrees>MSc</degrees>
      <xref rid="aff1" ref-type="aff">1</xref>
      <address>
        <institution>Department of Radiological Sciences</institution>
        <institution>College of Applied Medical Sciences</institution>
        <institution>King Saud University</institution>
        <addr-line>P.O. Box 10219</addr-line>
        <addr-line>Riyadh, 11432</addr-line>
        <country>Saudi Arabia</country>
        <phone>966 114693567</phone>
        <email>bqenam@ksu.edu.sa</email>
      </address>  
      <xref rid="aff2" ref-type="aff">2</xref>
      <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-4891-6723</ext-link></contrib>
      <contrib contrib-type="author" id="contrib2">
        <name name-style="western">
          <surname>Kim</surname>
          <given-names>Tae Youn</given-names>
        </name>
        <degrees>RN, PhD</degrees>
        <xref rid="aff3" ref-type="aff">3</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-2896-5424</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib3">
        <name name-style="western">
          <surname>Carroll</surname>
          <given-names>Mark J</given-names>
        </name>
        <degrees>MPH</degrees>
        <xref rid="aff4" ref-type="aff">4</xref>
        <xref rid="aff5" ref-type="aff">5</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0003-3055-7240</ext-link>
      </contrib>
      <contrib contrib-type="author" id="contrib4">
        <name name-style="western">
          <surname>Hogarth</surname>
          <given-names>Michael</given-names>
        </name>
        <degrees>MD</degrees>
        <xref rid="aff6" ref-type="aff">6</xref>
        <ext-link ext-link-type="orcid">http://orcid.org/0000-0002-4264-1258</ext-link>
      </contrib>
    </contrib-group>
    <aff id="aff1">
    <sup>1</sup>
    <institution>Department of Radiological Sciences</institution>
    <institution>College of Applied Medical Sciences</institution>  
    <institution>King Saud University</institution>  
    <addr-line>Riyadh</addr-line>
    <country>Saudi Arabia</country></aff>
    <aff id="aff2">
    <sup>2</sup>
    <institution>Health Informatics program</institution>
    <institution>School of Medicine</institution>  
    <institution>University of California, Davis</institution>  
    <addr-line>Sacramento, CA</addr-line>
    <country>United States</country></aff>
    <aff id="aff3">
    <sup>3</sup>
    <institution>Betty Irene Moore School of Nursing</institution>
    <institution>University of California, Davis</institution>  
    <addr-line>Sacramento, CA</addr-line>
    <country>United States</country></aff>
    <aff id="aff4">
    <sup>4</sup>
    <institution>Division of Health Informatics</institution>
    <institution>Department of Public Health Sciences</institution>  
    <institution>University of California, Davis</institution>  
    <addr-line>Sacramento, CA</addr-line>
    <country>United States</country></aff>
    <aff id="aff5">
    <sup>5</sup>
    <institution>Division of Pathology Informatics</institution>
    <institution>Department of Pathology and Laboratory Medicine</institution>  
    <institution>University of California, Davis</institution>  
    <addr-line>Sacramento, CA</addr-line>
    <country>United States</country></aff>
    <aff id="aff6">
    <sup>6</sup>
    <institution>UC San Diego Health</institution>
    <institution>University of California</institution>  
    <addr-line>San Diego, CA</addr-line>
    <country>United States</country></aff>
    <author-notes>
      <corresp>Corresponding Author: Basel Qenam 
      <email>bqenam@ksu.edu.sa</email></corresp>
    </author-notes>
    <pub-date pub-type="collection"><month>12</month><year>2017</year></pub-date>
    <pub-date pub-type="epub">
      <day>18</day>
      <month>12</month>
      <year>2017</year>
    </pub-date>
    <volume>19</volume>
    <issue>12</issue>
    <elocation-id>e417</elocation-id>
    <!--history from ojs - api-xml-->
    <history>
      <date date-type="received">
        <day>25</day>
        <month>7</month>
        <year>2017</year>
      </date>
      <date date-type="rev-request">
        <day>21</day>
        <month>8</month>
        <year>2017</year>
      </date>
      <date date-type="rev-recd">
        <day>16</day>
        <month>10</month>
        <year>2017</year>
      </date>
      <date date-type="accepted">
        <day>7</day>
        <month>11</month>
        <year>2017</year>
      </date>
    </history>
    <!--(c) the authors - correct author names and publication date here if necessary. Date in form ', dd.mm.yyyy' after jmir.org-->
    <copyright-statement>©Basel Qenam, Tae Youn Kim, Mark J Carroll, Michael Hogarth. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 18.12.2017.</copyright-statement>
    <copyright-year>2017</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 the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
    </license>  
    <self-uri xlink:href="http://www.jmir.org/2017/12/e417/" xlink:type="simple"/>
    <abstract>
      <sec sec-type="background">
        <title>Background</title>
        <p>Radiology reporting is a clinically oriented form of documentation that reflects critical information for patients about their health care processes. Realizing its importance, many medical institutions have started providing radiology reports in patient portals. The gain, however, can be limited because of medical language barriers, which require a way for customizing these reports for patients. The open-access, collaborative consumer health vocabulary (CHV) is a terminology system created for such purposes and can be the basis of lexical simplification processes for clinical notes.</p>
      </sec>
      <sec sec-type="objective">
        <title>Objective</title>
        <p>The aim of this study was to examine the comprehensibility and suitability of CHV in simplifying radiology reports for consumers. This was done by characterizing the content coverage and the lexical similarity between the terms in the reports and the CHV-preferred terms.</p>
      </sec>
      <sec sec-type="methods">
        <title>Methods</title>
        <p>The overall procedure was divided into the following two main stages: (1) translation and (2) evaluation. The translation process involved using MetaMap to link terms in the reports to CHV concepts. This is followed by replacing the terms with CHV-preferred terms using the concept names and sources table (MRCONSO) in the Unified Medical Language System (UMLS) Metathesaurus. In the second stage, medical terms in the reports and general terms that are used to describe medical phenomena were selected and evaluated by comparing the words in the original reports with the translated ones. The evaluation includes measuring the content coverage, investigating lexical similarity, and finding trends in missing concepts.</p>
      </sec>
      <sec sec-type="results">
        <title>Results</title>
        <p>Of the 792 terms selected from the radiology reports, 695 of them could be mapped directly to CHV concepts, indicating a content coverage of 88.5%. A total of 51 of the concepts (53%, 51/97) that could not be mapped are names of human anatomical structures and regions, followed by 28 anatomical descriptions and pathological variations (29%, 28/97). In addition, 12 radiology techniques and projections represented 12% of the unmapped concepts, whereas the remaining six concepts (6%, 12/97) were physiological descriptions. The rate of lexical similarity between the CHV-preferred terms and the terms in the radiology reports was approximately 72.6%.</p>
      </sec>
      <sec sec-type="conclusions">
        <title>Conclusions</title>
        <p>The CHV covered a high percentage of concepts found in the radiology reports, but unmapped concepts are associated with areas that are commonly found in radiology reporting. CHV terms also showed a high percentage of lexical similarity with terms in the reports, which contain a myriad of medical jargon. This suggests that many CHV terms might not be suitable for lay consumers who would not be facile with radiology-specific vocabulary. Therefore, further patient-centered content changes are needed of the CHV to increase its usefulness and facilitate its integration into consumer-oriented applications.</p>
      </sec>
    </abstract>
    <kwd-group>
      <kwd>consumer health information</kwd>
      <kwd>vocabulary</kwd>
      <kwd>radiology</kwd>
      <kwd>electronic health records</kwd>
      <kwd>natural language processing</kwd>
    </kwd-group></article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Engaging Patients in Health Care Processes</title>
        <p>The modern view of medicine endorses engaging patients in their health care [<xref ref-type="bibr" rid="ref1">1</xref>]. These efforts have been facilitated by the accelerating adoption of health information technology in the United States [<xref ref-type="bibr" rid="ref2">2</xref>] after the Health Information Technology for Economic and Clinical Health (HITECH) Act [<xref ref-type="bibr" rid="ref3">3</xref>]. In 2008, the American Medical Informatics Association’s Consumer Health Informatics Working Group identified the need for consumer-oriented tools to improve consumers’ understanding of health information [<xref ref-type="bibr" rid="ref4">4</xref>]. A Web-based patient portal, for example, is an important communication form between the patient and the provider that can increase the transparency of health care processes [<xref ref-type="bibr" rid="ref5">5</xref>]. A multicentral experimental study conducted in 2012 suggests that a majority of people who accessed their clinical notes through the Web sensed more control over their health care processes and showed an improved adherence in taking medications [<xref ref-type="bibr" rid="ref6">6</xref>]. Therefore, a number of large health care delivery organizations in the United States have adopted initiatives such as Open Notes, which grant patients a secure access to their medical records though Web portals [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      </sec>
      <sec>
        <title>Radiology Reports</title>
        <p>Radiology reports are one of the documents that have become unprecedentedly open to patients in multiple medical institutions nationwide [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. However, these reports use clinical and radiology terms that are unfamiliar to the lay public, which creates an opportunity for significant misinterpretation by patients.</p>
        <p>In the traditional health care process, radiology reports are where radiologists professionally express their knowledge and expertise to other physicians. The reports serve the purpose of describing diagnostic images to look for abnormalities, leading radiology reports to include a myriad of anatomical structures and pathological concepts. This makes it difficult to interpret such texts for someone without knowledge in the field.</p>
        <p>Generally, clinical documentation requires average reading skills higher than those of adults in the United States [<xref ref-type="bibr" rid="ref9">9</xref>]. Understanding many forms of clinical notes requires formal training in medical terminology. The level of complexity, nonetheless, differs from one type of documentation to another. In comparison with visit summaries, for instance, radiology reports are considered one of the most difficult clinical documentation forms for the lay public to understand [<xref ref-type="bibr" rid="ref10">10</xref>]. Therefore, providing such clinically oriented reports to patients through Web portals without considering their medical literacy level can be irrelevant and problematic. Reports should continue, nevertheless, to provide the clinical value and accuracy, and adhere to the needed time efficiency of the clinical workflow. Although the heterogeneity in the audience may cause contradictions in the requirements of a radiology report, it is costly and time-consuming to manually create an additional consumer-friendly version of the report. As a result, an automated maneuver to create a simplified version of the radiology report would be desirable.</p>
      </sec>
      <sec>
        <title>Lexical Simplification</title>
        <p>Text simplification is a division of natural language processing (NLP) that can refer to several syntactic, semantic, and lexical methods with the goal of simplifying text [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Early work in the field of text simplification focused on simplifying Web and newspaper articles for language learners and people with disorders that negatively affect reading abilities [<xref ref-type="bibr" rid="ref13">13</xref>]. The focus of text simplification is to produce a more readable and understandable text for the reader, without considering if it is shorter or longer. This distinguishes it from text summarization, where the major goal is text shortening. Lexical simplification, for example, is one realm of text simplification that focuses on replacing terms in a context with simpler synonyms [<xref ref-type="bibr" rid="ref14">14</xref>]. This can be useful when a main reason behind text difficulty is that it includes terms unfamiliar to the readers, which is the case in radiology reports [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>One important part of lexical simplification is to identify difficult terms and represent those with what are considered simpler terms. Such determination, nevertheless, tends to be subjective and ambiguous, which makes it hard to conduct by a computer. Usually, automated methods used to assign difficulty levels for words include measuring words length, the number of syllables, and usage frequency [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. In different realms of medicine, however, there are ontologies that can predefine medical terms, which might require simplification for the public. For example, RxNorm includes medications’ names for every drug in the US market [<xref ref-type="bibr" rid="ref17">17</xref>], and the Logical Observation Identifiers Names and Codes (LOINC) is a collection of terms used in laboratory observations [<xref ref-type="bibr" rid="ref18">18</xref>]. Furthermore, to harmonize these efforts, the National Library of Medicine built the Unified Medical Language System (UMLS), integrating similar terms from different ontologies into unified entities, each represented by a concept unique identifier (CUI). These data are constructed in relational tables that form the UMLS Metathesaurus [<xref ref-type="bibr" rid="ref19">19</xref>]. MRCONSO is one of the tables in the database, and it includes preferred terms and their synonyms linked to CUIs and other identifiers from the original sources of the terms (ie, LOINC).</p>
      </sec>
      <sec>
        <title>The Open-access, Collaborative Consumer Health Vocabulary (CHV)</title>
        <p>The UMLS Metathesaurus also includes the open-access, collaborative consumer health vocabulary (CHV) [<xref ref-type="bibr" rid="ref20">20</xref>] developed by the Biomedical Informatics Department at the University of Utah as an open-source set of biomedical terms that are suitable for laypersons. Research that uses the term <italic>consumer health vocabulary</italic> started in 2003 [<xref ref-type="bibr" rid="ref21">21</xref>], with the purpose of helping the lay public to understand health information [<xref ref-type="bibr" rid="ref20">20</xref>]. CHV is a collection of terms found to best represent the medical concepts for consumers; they are chosen because they are more comprehensible by patients when compared with their synonyms [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
        <p>The CHV has been implemented in the literature as the back end of medical lexical simplification techniques for consumers. This has been, especially, possible because the CHV concepts are linked to the medical concepts in the UMLS. In 2007, Zeng-Treitler et al tested the use of CHV as the basis of a translator prototype that attempted to simplify the content of electronic medical records and biomedical literature [<xref ref-type="bibr" rid="ref23">23</xref>]. Zeng-Treitler’s model changes terms to CHV-preferred terms when available and, if not, provides “explanations” based on the UMLS hierarchal and semantic relations [<xref ref-type="bibr" rid="ref23">23</xref>]. The correct translations reported in the latter model were considered promising, yet the percentage of incorrect translations was 8.2%. Most of the inaccuracy, as explained, was because of incorrect hierarchical relations in the UMLS such as “tobacco abuse” as “a type of psychiatric problem.” The semantic relationships among concepts included in the UMLS Metathesaurus are suboptimal because of the UMLS content being derived from external terminological systems that use a variety of heuristics for conceptual relationships.</p>
        <p>Hypothetically, the CHV can help in creating a more consumer-oriented version of radiology reports. Yet, there is a lack of evidence on whether CHV is an appropriate source of lay terms that can simply replace medical terms used in the field of radiology, which has unique contexts and jargon. Any implementation of CHV should take lexical differences into consideration to make sure CHV is a good fit for the required purpose. Text simplification is by nature more sensitive to errors than other NLP techniques. Incorrect translations can make clinical reports more difficult to comprehend and might provide incorrect information to patients, such as defining a “cyst” as “a type of tumor” [<xref ref-type="bibr" rid="ref23">23</xref>]. Higher comprehension of radiology concepts would lead to relying on less hierarchal relations, which was shown to introduce more errors.</p>
        <p>We believe that automated simplification of radiology reports using lay terms would be beneficial to patients as such simple transformation of medical terms could enhance patients’ understanding of the content. The first step in this endeavor is to determine the relevance and comprehension of CHV as a backbone of a lexical simplification tool for radiology reports. The objectives of this study can be conceived by answering the following set of questions:</p>
        <list list-type="bullet">
          <list-item>
            <p>What is the content coverage of CHV for concepts included in radiology reports?</p>
          </list-item>
          <list-item>
            <p>What is the percentage of lexical similarity between CHV-preferred terms and medical terms used in the radiology reports?</p>
          </list-item>
          <list-item>
            <p>What are the main observations and obstacles in implementing CHV in a lexical simplification tool for radiology reports?</p>
          </list-item>
        </list>
        <p>Although content coverage shows the level of comprehension on covering radiology concepts, lexical similarity can indicate how the CHV distinctively describes concepts in a consumer-oriented manner.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>The overall procedure can be divided into the following two main stages: (1) translation and (2) evaluation. The translation process involving the following two components is outlined in <xref ref-type="fig" rid="figure1">Figure 1</xref>: mapping medical terms to CHV concepts, which corresponds to the objects 1 to 3 in the diagram, and replacing medical terms in the reports with CHV-preferred terms (objects 4-8 in <xref ref-type="fig" rid="figure1">Figure 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>A sequence diagram of the translation process. UMLS: unified medical language system; MMI: MetaMap indexing.</p>
          </caption>
          <graphic xlink:href="jmir_v19i12e417_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>The Translation Process</title>
        <sec>
          <title>Mapping Terms in Radiology Reports to Their Relevant Concepts in the Consumer Health Vocabulary</title>
          <p>A set of 31 radiology reports were parsed and mapped to the CHV concepts using MetaMap 2016 [<xref ref-type="bibr" rid="ref24">24</xref>], an NLP tool created by the National Library of Medicine based on the UMLS Metathesaurus. The reports were anonymous Web-published samples from multiple institutions in the United States [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. The sample comprised 10 magnetic resonance imaging (MRI) reports, 6 ultrasound reports, 5 computed tomography reports, 5 nuclear medicine reports, and 5 x-ray reports. The anatomical structures covered in these imaging acquisitions included the abdomen, the chest, the neck, the head, the shoulders, and the ankles. In addition, there were organ-specific acquisitions for the brain, the spine, the kidneys, the liver, and testicles. This was besides two physiology-oriented cases, a Doppler carotid scan and a carotid stress test.</p>
          <p>In the mapping process, all the semantic types in the UMLS were included [<xref ref-type="bibr" rid="ref29">29</xref>], and a low MetaMap evaluation score threshold of 500 out of 1000 was set [<xref ref-type="bibr" rid="ref30">30</xref>]. Both decisions had been made to ensure that the system is as inclusive as possible in linking report terms to CHV concepts. Restricting semantic types reduces mapping errors caused by linking terms to concepts in irreverent categories (ie, geographical area). It can, nevertheless, affect the comprehension of the tool in detecting some applicable concepts if their semantic types were excluded. Similarly, a low evaluation score threshold would spread the net for the purpose of measuring the content coverage. Although this would increase the risk of mapping words or terms to irrelevant concepts, these incidents were excluded through manual investigation.</p>
        </sec>
        <sec>
          <title>Replacing Every Mapped Term in the Reports With the Consumer Health Vocabulary–Preferred Term of its Representative Concept</title>
          <p>In the previous process, the output of MetaMap was created in the form of fielded MetaMap indexing (MMI), a pipe-separated structured text document that could be processed with programming scripts. One program using Python programming language [<xref ref-type="bibr" rid="ref31">31</xref>] was created to extract the CUIs of the detected concepts and the terms that provoked each CUI. This program can detect up to 4 terms for each CUI and load all extracted pieces of data into a MySQL [<xref ref-type="bibr" rid="ref32">32</xref>] database. In addition, it adds the CHV-preferred terms to a table by matching the detected CUIs in MRCONSO. Another script replaces the list of terms in the table with their CHV-preferred terms counterparts. To facilitate pinpointing during evaluation, the replaced words were marked with square brackets, such as [CHV Preferred Term], to be recognizable for evaluation.</p>
        </sec>
      </sec>
      <sec>
        <title>The Evaluation Process</title>
        <p>After completing the term replacement process, we counted medical terms in the reports, such as anatomical structures and abnormalities. Additionally, we included general terms that have been used to describe clinical phenomena and might need clarification, such as “irregular” to describe the margins of a mass. Words, however, that are considered simple English, for instance “patient” or “right side,” were not counted despite being mapped to CHV concepts. When a medical term was not mapped to a CHV concept, it was investigated in the CHV Web portal to eliminate the chances of false negatives in the coverage because of limitations in the mapping process. Similarly, words that had been mapped to incorrect concepts were excluded if they did not have matching concepts in the CHV after a manual investigation. Each term is counted once unless it was written once in full and used again as an abbreviation.</p>
        <p>To measure the content coverage of CHV and lexical similarity of terms between the radiology reports and CHV-preferred terms, included terms were classified in two ways. First, to measure the content coverage, terms that are represented by CHV concepts were compared with terms that did not match any CHV concept, following the equation:</p>
        <disp-formula>Content coverage = (Covered terms × 100) / (Total terms)</disp-formula>
        <p>Second, terms mapped to CHV concepts were categorized based on their lexical similarity with the original terms used in radiology reports. Lexical similarity refers to different statistical calculations that are commonly used to measure how close two different languages or two pieces of text are to each other [<xref ref-type="bibr" rid="ref33">33</xref>]. In this context, it is calculated using the following equation:</p>
        <disp-formula>Lexical similarity = (Similar terms × 100) / (Covered terms)</disp-formula>
        <p>A word is considered lexically similar if its CHV-preferred term is the same word or a variant that is based on the same stem. Additionally, phrases are considered similar if the same words are paraphrased differently (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <p>Terms are considered lexically different if their CHV-preferred terms include words derived from distinct stems. This includes preferred terms with added words such as replacing the term “ventricles” with “heart ventricles,” as well as any terms that were totally altered, such as replacing “necrosis” with “tissue death.” The importance of lexical similarity is based on the premise that consumer-oriented terms are supposed to be expressed differently in comparison with clinically oriented reports that are characterized by being difficult for consumers to grasp.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Examples of lexical similarity classification.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="435"/>
            <col width="415"/>
            <col width="140"/>
            <thead>
              <tr valign="top">
                <td>Report term</td>
                <td>Preferred term</td>
                <td>Lexical similarity</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Lateral</td>
                <td>Lateral</td>
                <td>Similar</td>
              </tr>
              <tr valign="top">
                <td>Thickening</td>
                <td>Thickened</td>
                <td>Similar</td>
              </tr>
              <tr valign="top">
                <td>Abdominal wall</td>
                <td>Wall of abdomen</td>
                <td>Similar</td>
              </tr>
              <tr valign="top">
                <td>Ventricle</td>
                <td>Heart ventricle</td>
                <td>Different</td>
              </tr>
              <tr valign="top">
                <td>Necrosis</td>
                <td>Tissue death</td>
                <td>Different</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Content Coverage</title>
        <p>Out of 792 terms extracted from the sample of 31 reports, 695 terms (88.5%) were covered by CHV concepts (<xref ref-type="table" rid="table2">Table 2</xref>). Coverage per report ranges from 61% to 100% (<xref ref-type="fig" rid="figure2">Figure 2</xref>), with an average of 88.5% and a median of 88.9%.</p>
        <p>When categorizing the reports based on imaging modalities (<xref ref-type="table" rid="table3">Table 3</xref>), content coverage ranges approximately between 84% and 94%, with ultrasound being the lowest and nuclear medicine being the highest. For the results of individual reports’ analyses please see <xref ref-type="app" rid="app1">Multimedia Appendix 1</xref>.</p>
      </sec>
      <sec>
        <title>Missing Concepts</title>
        <p>The analysis shows that 97 terms of the 792 terms (12.2%) were not linked to CHV concepts. To illustrate the coverage gaps found in radiology reports, uncovered terms can be divided into the following four categories:</p>
        <list list-type="order">
          <list-item>
            <p><italic>Human anatomical structures and regions:</italic> 51 terms (53%) are in this category. Examples include “disc space” and “midthoracic.”</p>
          </list-item>
          <list-item>
            <p><italic>Anatomical descriptions:</italic> For example, “heterogeneity” and normal and pathologic variations such as “tracheomegaly” represented 28 of the unmapped terms (29%).</p>
          </list-item>
          <list-item>
            <p><italic>Radiology-related techniques and projections:</italic> For example, “post-contrast” and “anteroposterior” accounted for 12 missing terms (12%).</p>
          </list-item>
          <list-item>
            <p><italic>Physiology-related terms:</italic> Six uncovered terms (6%) are considered in this category. Examples are “metabolically active” and “basic” as used in “basic rhythm of atrial fibrillation.”</p>
          </list-item>
        </list>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>A summary of terms classification, content coverage, and percentage of similar terms in 31 sample reports.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="210"/>
            <col width="170"/>
            <col width="170"/>
            <col width="170"/>
            <col width="170"/>
            <col width="110"/>
            <thead>
              <tr valign="top">
                <td>Category of terms</td>
                <td>Similar</td>
                <td>Different</td>
                <td>Missing</td>
                <td>Total covered</td>
                <td>Total</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Sum</td>
                <td>505</td>
                <td>190</td>
                <td>97</td>
                <td>695</td>
                <td>792</td>
              </tr>
              <tr valign="top">
                <td>Percentage (%)</td>
                <td>63.8</td>
                <td>24</td>
                <td>12.2</td>
                <td>88.5</td>
                <td>100</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>A scatter plot of sample reports percentages of content coverage. CT: computed tomography; MRI: magnetic resonance imaging; NM: nuclear medicine; US: ultrasound.</p>
          </caption>
          <graphic xlink:href="jmir_v19i12e417_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Sample reports classified per modality, showing the content coverage and lexical similarity for each set, and the average coverage and similarity for the different modalities.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="240"/>
            <col width="90"/>
            <col width="90"/>
            <col width="90"/>
            <col width="90"/>
            <col width="80"/>
            <col width="90"/>
            <col width="120"/>
            <col width="110"/>
            <thead>
              <tr valign="top">
                <td>Modality</td>
                <td>Reports’ quantity</td>
                <td>Similar terms</td>
                <td>Different terms</td>
                <td>Missing terms</td>
                <td>Total terms</td>
                <td>Covered terms</td>
                <td>Coverage (%)</td>
                <td>Similarity (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Magnetic resonance imaging</td>
                <td>10</td>
                <td>229</td>
                <td>91</td>
                <td>58</td>
                <td>378</td>
                <td>320</td>
                <td>84.66</td>
                <td>71.56</td>
              </tr>
              <tr valign="top">
                <td>Ultrasound</td>
                <td>6</td>
                <td>52</td>
                <td>16</td>
                <td>13</td>
                <td>81</td>
                <td>68</td>
                <td>83.95</td>
                <td>76.47</td>
              </tr>
              <tr valign="top">
                <td>Computed tomography</td>
                <td>5</td>
                <td>90</td>
                <td>39</td>
                <td>11</td>
                <td>140</td>
                <td>129</td>
                <td>92.14</td>
                <td>69.77</td>
              </tr>
              <tr valign="top">
                <td>Nuclear medicine<sup>a</sup></td>
                <td>5</td>
                <td>81</td>
                <td>22</td>
                <td>7</td>
                <td>110</td>
                <td>103</td>
                <td>93.64</td>
                <td>78.64</td>
              </tr>
              <tr valign="top">
                <td>X-ray<sup>b</sup></td>
                <td>5</td>
                <td>53</td>
                <td>22</td>
                <td>8</td>
                <td>83</td>
                <td>75</td>
                <td>90.36</td>
                <td>70.67</td>
              </tr>
              <tr valign="top">
                <td>Average</td>
                <td><break/></td>
                <td><break/></td>
                <td><break/></td>
                <td><break/></td>
                <td><break/></td>
                <td><break/></td>
                <td>88.95</td>
                <td>73.42</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>Includes 1 report of a positron emission tomography-computed tomography procedure.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>Includes 1 report of a mammography procedure.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>A summary of terms’ classification based on lexical similarity. This classification only includes terms that are covered by the consumer health vocabulary.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="330"/>
            <col width="270"/>
            <col width="290"/>
            <col width="110"/>
            <thead>
              <tr valign="top">
                <td>Terms</td>
                <td>Similar</td>
                <td>Different</td>
                <td>Total</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Sum</td>
                <td>505</td>
                <td>190</td>
                <td>695</td>
              </tr>
              <tr valign="top">
                <td>Percentage (%)</td>
                <td>72.6</td>
                <td>27.3</td>
                <td>100</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In a linguistic manner, there are areas where the CHV fails to cover concepts more than others. Two main areas are compound words and words with affixes such as “extraaxial” and “paracentral.” Another challenge is abbreviations. In many cases, the original terms were present in CHV, but not their acronyms. An example of this is the phrase “left ventricle,” which is present in CHV, but not the abbreviation “LV.” <xref ref-type="fig" rid="figure2">Figure 2</xref> illustrates 2 reports that are noticeably lower in coverage than others, a lumber MRI report being the lowest, followed by a report of a carotid Doppler ultrasound procedure. Although the MRI case mostly contains uncovered anatomical structures, the Doppler ultrasound missed abbreviations to express names of arteries.</p>
      </sec>
      <sec>
        <title>Lexical Similarity</title>
        <p>Looking at the terms covered by CHV concepts, the average lexical similarity between the CHV-preferred terms and the terms in the radiology reports was approximately 72.6% (<xref ref-type="table" rid="table4">Table 4</xref>).</p>
        <p>Approximately 27.3% of the covered terms were replaced with terms or phrases that are lexically different from what was written in the reports. In some cases, words were replaced with more familiar descriptions, such as replacing the word “necrosis” with “tissue death” or replacing “cortex” with the phrase “outer layer of an organ.” Other terms were replaced with phrases that include the original terms but with a brief illustration, such as “heart ventricles” in place of “ventricles.” In addition, few terms were replaced with others that can be less familiar. For example, the CHV-preferred term “effusion” replaced the phrase “free fluid,” which was used in the reports.</p>
      </sec>
      <sec>
        <title>Other Observations</title>
        <sec>
          <title>Idiosyncrasies With Semantic Types</title>
          <p>When only semantic types of interest were chosen, a concept was found for the word “anterior,” but not the word “posterior.” As they have an antonymous relationship, one might expect they are in the same semantic category, yet “anterior” is classified in the UMLS as a “functional concept,” whereas “posterior” is a “spatial concept,” a type that was excluded in this experiment. When semantic types were not specified, there were more mappings to irrelevant concepts. For example, the word “no” was mapped to the concept “nitric oxide,” when the semantic types “Biologically Active Substance” or “Pharmacologic Substance” were not excluded. In addition, there were more mappings to words with the wrong sense, word sense disambiguation errors. For example, the word “ultrasound” was mapped to the concept “therapeutic shock waves,” although the meaning of the word in the report refers to “diagnostic ultrasound.”</p>
        </sec>
        <sec>
          <title>Syntactic Errors</title>
          <p>In some cases, when replacing terms with others, part of speech of the words is altered, such as when the noun “opacity” replaces the adjective “opaque.” Furthermore, articles, “a” and “an” needed an adjustment after replacing a word that begins with a consonant with another word that starts with a vowel.</p>
        </sec>
        <sec>
          <title>Spelling Errors</title>
          <p>The term “homogenous” was written in one report to describe what is usually referred to as “homogeneous.” This has led to mapping the term to a different concept “homozygote,” which is not the meaning in the report. Another case is the term “metastatic,” which is misspelled in one report to be “metastic.” In that case, the term was not mapped to a concept.</p>
        </sec>
        <sec>
          <title>Representation of Consumer Health Vocabulary in the Unified Medical Language System</title>
          <p>In the MRCONSO table, it is possible to find 2 CHV terms marked as preferred term with the same UMLS CUI, although only one is expected. As the mapping results from MetaMap are CUI-oriented, there has been an ambiguity in defining the right CHV-preferred terms in these cases from the MRCONSO table. The situation was different, nonetheless, when searching for a CUI directly in the CHV Web portal. For example, the word “change” has 2 CHV-preferred terms in the MRCONSO table, “change” and “modified,” yet only one preferred term, “change,” was found in the CHV Web portal. This is true for all other concepts in the Web portal, but there has not been a pattern to define that single term in the MRCONSO table.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Of the 31 radiology reports examined, the CHV shows an overall high percentage of content coverage (88.5%) for terms found in sample reports. However, unmapped terms were associated with areas that can be uniquely common in radiology reporting. Likewise, there was a high percentage of lexical similarity between the terms used in the reports and the CHV-preferred terms. This has resulted in merely 27.3% of the sample terms to be considered lexically different after replacing them with their CHV counterparts.</p>
      </sec>
      <sec>
        <title>Content Coverage</title>
        <p>A substantial amount of the effort that has been invested in the CHV involved broadening content coverage. The findings of this study suggest that the content coverage is perhaps not the highest priority improvement needed at this juncture. Nevertheless, the association between uncovered concepts and terms uniquely used in radiology reporting is notable. This is not surprising as the CHV concepts were created by finding terms that are frequently used in MedlinePlus [<xref ref-type="bibr" rid="ref22">22</xref>], and many of the missing terms are less frequent and can even be absent in other medical texts. That, nevertheless, does not eradicate the importance of explaining such terms when they appear in patients’ radiology reports.</p>
        <p>Another gap in coverage is abbreviations. Acronyms have a high risk of being ambiguous, which makes covering them difficult as their meanings can differ from one field to another. For example, PET and CAT in common terms can refer to types of animals. In contrast, it refers, in radiology, to positron emission tomography and computed axial tomography, respectively. This obstacle, however, can be solved in the implementation. MetaMap, for instance, can circumvent acronyms’ ambiguity by allowing users to predefine them before the mapping process.</p>
      </sec>
      <sec>
        <title>Lexical Similarity</title>
        <p>Although a decent percentage of similarity had been expected, the result surpassed our expectations. It shows that about one of every 4 terms of interest is expressed differently in the CHV in comparison with radiology reports. This high level of similarity can be due to many reasons. It is either because some words in the reports are easy to grasp, a simpler explanation does not exist, or they are not explained to the consumer level in the CHV. All these factors are most likely relevant, but this matter requires more research to identify which one is dominant.</p>
        <p>The usefulness of the CHV implementation, however, is illustrated when looking at terms that are lexically different. Explanations, for example, are expected to be easier in many contexts for people without background knowledge in pathology or anatomy. It is worth noting that adding explanations can possibly be problematic depending on the way it is used and the context. We can see that if we replace the term “cortex” with its given definition in the phrase “renal cortex,” without adjusting the sentence. Such a change would affect the readability and the coherence of the text. Another type of replacement that can increase understandability is terms that were modified by adding an extra word (ie, “heart” in “heart fibrillation”). It is, however, important to watch for redundancy, such as when a similar word is adjacent to the replaced term in the original report.</p>
        <p>As there is a large percentage of similarity, introducing changes in these terms can lead to little benefit while introducing a risk of avoidable syntactic errors. Therefore, a simplification tool should include a grammatical layer to maintain the parts of speech after terms’ replacements. In fact, such a component is vital for all replaced terms, not only the similar ones. Another straightforward method to reduce syntactic errors is excluding terms from replacement if their CHV-preferred terms are lexically similar. This can be done by stemming the terms and by removing morphological affixes using an NLP algorithm. As a result, a tool would be prohibited from replacing words with others that have the same stem.</p>
      </sec>
      <sec>
        <title>Other Observations</title>
        <p>When restricting semantic types, the inclusiveness of CHV concepts was negatively affected, missing potential mappings between terms in the radiology reports and concepts in the CHV. Not specifying them, in contrast, increased mapping errors that were related to the senses of the words. These errors made the text more difficult to read. Moreover, syntactic errors can also affect readability in a negative way. Some of them appeared in the text because of missing a ripple effect of change in the sentence after a one-to-one lexical replacement. Although this might be an inherent characteristic of lexical simplification, applying simple grammatical changes as part of the process would help to mitigate the problem.</p>
        <p>Spelling errors are always a possibility in free narrative writing, which makes them an intrinsic challenge in NLP. In this study, misspelling appeared to be affecting lexical simplification more than grammatical errors as MetaMap does not recognize misspelled terms. One way to overcome this dilemma is by using noisy channel algorithms, which are able to predict intended words within a margin of error [<xref ref-type="bibr" rid="ref34">34</xref>]. Furthermore, any type of premapping spell checking that corrects or excludes misspelled words is helpful.</p>
        <p>Overall, the settings of this study were oriented toward its research objectives, mainly finding the content coverage and the lexical similarity. There are, however, possible optimizations to build a result-oriented translator, ranging from available MetaMap options, such as excluding unwanted semantic types and prespecifying acronyms, to postprocessing measures. All these optimizations would be intended mainly to help in simplifying terms without affecting the coherence of the text, which can be the major principle to create a successful lexical simplification process.</p>
        <p>The CHV representation in the UMLS, specifically in the MRCONSO table, is an essential part of the translation methodology implemented in this work. It, however, has undermined finding the intended preferred terms for some of the concepts as two preferred terms can exist for one CUI, which does not happen when searching the CHV Web portal for the same CUIs. This may be because when CHV concepts were added to the UMLS, in some cases, two CHV concepts were found to fit one concept in the UMLS. Therefore, a change in the methodology applied in this work can be essential to create a successful lexical simplification tool based on the CHV.</p>
        <p>Oh et al discuss a prototype project called “PORTER” that aimed to create patient-oriented reports by first establishing a “lay-language glossary” for MRI knee exams [<xref ref-type="bibr" rid="ref35">35</xref>]. The CHV can be a good resource to start broadening such a project. Doing so would require a method for extracting preferred terms that can be useful for consumers in the specific matter. It is also possible that focusing the simplification process on the action items of the report would facilitate covering more types of medical imaging procedures while maintaining most of the benefit for the consumers. An actionable representation for patients in radiology can be restricted to the impressions section. Nevertheless, providing the rest of the report is still important for the purpose of transparency.</p>
        <p>Generally, research in translation is an ongoing and a promising process. Google, for example, has announced in 2016 a new approach in machine translation for Google Translator using neural networks models for creating a better human-like translation between English and Chinese [<xref ref-type="bibr" rid="ref36">36</xref>]. This emphasizes the importance of improving the CHV to support the advancements in translations when creating consumer-focused biomedical applications. In that process, automated methods to improve ontologies, known as Ontology Learning, can be advantageous to better encompass CHV [<xref ref-type="bibr" rid="ref37">37</xref>]. A study investigating the “folksonomy” of terms published by patients in the platform “PatientsLikeMe” elucidates that about half of the terms did not have a match or a synonym in the UMLS [<xref ref-type="bibr" rid="ref38">38</xref>]. Some of these terms might not have a direct concept that corresponds to them in the UMLS, but there might be a parent concept in the hierarchy where semantically broader concepts can be found. Keselman et al provides a framework of initiating “lay” tagged concepts that can be used for only consumer-based projects and still be linked to the UMLS hierarchy [<xref ref-type="bibr" rid="ref39">39</xref>]. Doing so will help ontologies to cover more of CHV, which can help to bridge the gap between the two different ways consumers and clinicians describe medical phenomena.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The results of the study are based on a sample of 31 reports from a variety of radiology specialties. Although the reports include hundreds of terms used in the field, the results cannot be generalized to cover the vast realm of medical imaging. It, however, provides an overview that can pave the way for more targeted studies.</p>
        <p>Although medical terms could be easy to define, general terms that describe medical phenomena are often vague. In some cases, choosing general terms to be included in the study might have depended on personal judgment despite following the inclusion criteria. Included words, nevertheless, had been defined before investigating what categorization they belong to (ie, missing) to eliminate the risk of bias.</p>
        <p>This work measures the lexical but not the semantic similarity. Semantic similarity, also referred to as conceptual similarity, compares the conceptual meanings of words without considering their lexical similarity [<xref ref-type="bibr" rid="ref40">40</xref>]. It is measured by mapping terms to an ontology and measuring their distance apart in a hierarchy. Semantic similarity can be investigated for many purposes. One main usage is to find similar documents despite different wording, which is very useful in information retrieval. Semantic similarity can be applied in the context of this study to investigate the accuracy of the translation in maintaining the conceptual meanings in the original reports. This measure does not only rely on the CHV word choices, but also on the mapping process, which serves a different but important purpose that complements what is intended in this study.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The CHV provided an overall high content coverage of 88.5% for the terms found in the sample radiology reports. Yet, uncovered concepts are associated with areas that are uniquely common and important in radiology reporting, such as anatomical descriptions and radiation projections. The study also shows a high level of lexical similarity between CHV-preferred terms and original terms in the sample radiology reports, which have a plethora of medical jargon. This indicates that some CHV-preferred terms can be above the level of consumers’ comprehension. Such terms would require further simplification before successfully integrating the CHV into radiology-related applications that target consumers. Overall, our implementation shows that lexical simplification is not sufficient to simplify the reports for consumers, yet it can play an important role if used to complement other methods of simplification and explanation.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <app id="app1">
        <title>Multimedia Appendix 1</title>
        <p>The full data of the terms' evaluation process.</p>
        <media xlink:href="jmir_v19i12e417_app1.xlsx" xlink:title="XLSX File (Microsoft Excel File), 67KB"/>
      </app>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CAT</term>
          <def>
            <p>computed axial tomography</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CHV</term>
          <def>
            <p>consumer health vocabulary</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CUI</term>
          <def>
            <p>concept unique identifier</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HITECH</term>
          <def>
            <p>Health Information Technology for Economic and Clinical Health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">LOINC</term>
          <def>
            <p>logical observation identifiers names and codes</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">MMI</term>
          <def>
            <p>MetaMap indexing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">MRCONSO</term>
          <def>
            <p>concept names and sources table</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">MRI</term>
          <def>
            <p>magnetic resonance imaging</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">NLP</term>
          <def>
            <p>natural language processing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">PET</term>
          <def>
            <p>positron emission tomography</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">UMLS</term>
          <def>
            <p>unified medical language system</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <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>Koh</surname>
            <given-names>HK</given-names>
          </name>
          <name name-style="western">
            <surname>Brach</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Harris</surname>
            <given-names>LM</given-names>
          </name>
          <name name-style="western">
            <surname>Parchman</surname>
            <given-names>ML</given-names>
          </name>
        </person-group>
        <article-title>A proposed 'health literate care model' would constitute a systems approach to improving patients' engagement in care</article-title>
        <source>Health Aff (Millwood)</source>  
        <year>2013</year>  
        <month>02</month>  
        <volume>32</volume>  
        <issue>2</issue>  
        <fpage>357</fpage>  
        <lpage>67</lpage>  
        <pub-id pub-id-type="doi">10.1377/hlthaff.2012.1205</pub-id>
        <pub-id pub-id-type="medline">23381529</pub-id>
        <pub-id pub-id-type="pii">32/2/357</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>Xierali</surname>
            <given-names>IM</given-names>
          </name>
          <name name-style="western">
            <surname>Hsiao</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Puffer</surname>
            <given-names>JC</given-names>
          </name>
          <name name-style="western">
            <surname>Green</surname>
            <given-names>LA</given-names>
          </name>
          <name name-style="western">
            <surname>Rinaldo</surname>
            <given-names>JCB</given-names>
          </name>
          <name name-style="western">
            <surname>Bazemore</surname>
            <given-names>AW</given-names>
          </name>
          <name name-style="western">
            <surname>Burke</surname>
            <given-names>MT</given-names>
          </name>
          <name name-style="western">
            <surname>Phillips</surname>
            <given-names>RL</given-names>
          </name>
        </person-group>
        <article-title>The rise of electronic health record adoption among family physicians</article-title>
        <source>Ann Fam Med</source>  
        <year>2013</year>  
        <volume>11</volume>  
        <issue>1</issue>  
        <fpage>14</fpage>  
        <lpage>9</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.annfammed.org/cgi/pmidlookup?view=long&#38;pmid=23319501"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1370/afm.1461</pub-id>
        <pub-id pub-id-type="medline">23319501</pub-id>
        <pub-id pub-id-type="pii">11/1/14</pub-id>
        <pub-id pub-id-type="pmcid">PMC3596022</pub-id></nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
        <source>Congress</source>  
        <year>2009</year>  
        <access-date>2017-07-22</access-date>
        <comment>H.R.1 - American recovery and reinvestment act of 2009 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.congress.gov/bill/111th-congress/house-bill/1/text">https://www.congress.gov/bill/111th-congress/house-bill/1/text</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6s9K679vP"/></comment> </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>Keselman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Logan</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>CA</given-names>
          </name>
          <name name-style="western">
            <surname>Leroy</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Zeng-Treitler</surname>
            <given-names>Q</given-names>
          </name>
        </person-group>
        <article-title>Developing informatics tools and strategies for consumer-centered health communication</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2008</year>  
        <volume>15</volume>  
        <issue>4</issue>  
        <fpage>473</fpage>  
        <lpage>83</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/cgi/pmidlookup?view=long&#38;pmid=18436895"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1197/jamia.M2744</pub-id>
        <pub-id pub-id-type="medline">18436895</pub-id>
        <pub-id pub-id-type="pii">M2744</pub-id>
        <pub-id pub-id-type="pmcid">PMC2442255</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>Bruno</surname>
            <given-names>MA</given-names>
          </name>
          <name name-style="western">
            <surname>Petscavage-Thomas</surname>
            <given-names>JM</given-names>
          </name>
          <name name-style="western">
            <surname>Mohr</surname>
            <given-names>MJ</given-names>
          </name>
          <name name-style="western">
            <surname>Bell</surname>
            <given-names>SK</given-names>
          </name>
          <name name-style="western">
            <surname>Brown</surname>
            <given-names>SD</given-names>
          </name>
        </person-group>
        <article-title>The “open letter”: radiologists' reports in the era of patient web portals</article-title>
        <source>J Am Coll Radiol</source>  
        <year>2014</year>  
        <month>09</month>  
        <volume>11</volume>  
        <issue>9</issue>  
        <fpage>863</fpage>  
        <lpage>7</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jacr.2014.03.014</pub-id>
        <pub-id pub-id-type="medline">24836272</pub-id>
        <pub-id pub-id-type="pii">S1546-1440(14)00153-7</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>Delbanco</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Walker</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Bell</surname>
            <given-names>SK</given-names>
          </name>
          <name name-style="western">
            <surname>Darer</surname>
            <given-names>JD</given-names>
          </name>
          <name name-style="western">
            <surname>Elmore</surname>
            <given-names>JG</given-names>
          </name>
          <name name-style="western">
            <surname>Farag</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Feldman</surname>
            <given-names>HJ</given-names>
          </name>
          <name name-style="western">
            <surname>Mejilla</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Ngo</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Ralston</surname>
            <given-names>JD</given-names>
          </name>
          <name name-style="western">
            <surname>Ross</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Trivedi</surname>
            <given-names>N</given-names>
          </name>
          <name name-style="western">
            <surname>Vodicka</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Leveille</surname>
            <given-names>SG</given-names>
          </name>
        </person-group>
        <article-title>Inviting patients to read their doctors' notes: a quasi-experimental study and a look ahead</article-title>
        <source>Ann Intern Med</source>  
        <year>2012</year>  
        <month>10</month>  
        <day>2</day>  
        <volume>157</volume>  
        <issue>7</issue>  
        <fpage>461</fpage>  
        <lpage>70</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23027317"/>
        </comment>  
        <pub-id pub-id-type="doi">10.7326/0003-4819-157-7-201210020-00002</pub-id>
        <pub-id pub-id-type="medline">23027317</pub-id>
        <pub-id pub-id-type="pii">1363511</pub-id>
        <pub-id pub-id-type="pmcid">PMC3908866</pub-id></nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Delbanco</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Walker</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Darer</surname>
            <given-names>JD</given-names>
          </name>
          <name name-style="western">
            <surname>Elmore</surname>
            <given-names>JG</given-names>
          </name>
          <name name-style="western">
            <surname>Feldman</surname>
            <given-names>HJ</given-names>
          </name>
          <name name-style="western">
            <surname>Leveille</surname>
            <given-names>SG</given-names>
          </name>
          <name name-style="western">
            <surname>Ralston</surname>
            <given-names>JD</given-names>
          </name>
          <name name-style="western">
            <surname>Ross</surname>
            <given-names>SE</given-names>
          </name>
          <name name-style="western">
            <surname>Vodicka</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Weber</surname>
            <given-names>VD</given-names>
          </name>
        </person-group>
        <article-title>Open notes: doctors and patients signing on</article-title>
        <source>Ann Intern Med</source>  
        <year>2010</year>  
        <month>07</month>  
        <day>20</day>  
        <volume>153</volume>  
        <issue>2</issue>  
        <fpage>121</fpage>  
        <lpage>5</lpage>  
        <pub-id pub-id-type="doi">10.7326/0003-4819-153-2-201007200-00008</pub-id>
        <pub-id pub-id-type="medline">20643992</pub-id>
        <pub-id pub-id-type="pii">153/2/121</pub-id></nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Henshaw</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Okawa</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Ching</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>Garrido</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Qian</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Tsai</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Access to radiology reports via an online patient portal: experiences of referring physicians and patients</article-title>
        <source>J Am Coll Radiol</source>  
        <year>2015</year>  
        <month>06</month>  
        <volume>12</volume>  
        <issue>6</issue>  
        <fpage>582</fpage>  
        <lpage>6.e1</lpage>  
        <pub-id pub-id-type="doi">10.1016/j.jacr.2015.01.015</pub-id>
        <pub-id pub-id-type="medline">26047399</pub-id>
        <pub-id pub-id-type="pii">S1546-1440(15)00030-7</pub-id></nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Nielsen-Bohlman</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Panzer</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Kindig</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Executive Summary</article-title>
        <source>Health literacy: a prescription to end confusion</source>  
        <year>2004</year>  
        <publisher-loc>Washington, DC</publisher-loc>
        <publisher-name>National Academies Press</publisher-name></nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Keselman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Slaughter</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>CA</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Divita</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Browne</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Tsai</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Zeng-Treitler</surname>
            <given-names>Q</given-names>
          </name>
        </person-group>
        <article-title>Towards consumer-friendly PHRs: patients' experience with reviewing their health records</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2007</year>  
        <month>10</month>  
        <day>11</day>  
        <fpage>399</fpage>  
        <lpage>403</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/18693866"/>
        </comment>  
        <pub-id pub-id-type="medline">18693866</pub-id>
        <pub-id pub-id-type="pmcid">PMC2655877</pub-id></nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Siddharthan</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>Syntactic simplification and text cohesion</article-title>
        <source>Res Lang Comput</source>  
        <year>2006</year>  
        <month>3</month>  
        <day>28</day>  
        <volume>4</volume>  
        <issue>1</issue>  
        <fpage>77</fpage>  
        <lpage>109</lpage>  
        <pub-id pub-id-type="doi">10.1007/s11168-006-9011-1</pub-id></nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Kandula</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Curtis</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Zeng-Treitler</surname>
            <given-names>Q</given-names>
          </name>
        </person-group>
        <article-title>A semantic and syntactic text simplification tool for health content</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2010</year>  
        <month>11</month>  
        <day>13</day>  
        <conf-name>AMIA Annual Symposium</conf-name>
        <conf-date>2010</conf-date>
        <conf-loc>Washington,DC</conf-loc>
        <fpage>366</fpage>  
        <lpage>70</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21347002"/>
        </comment> </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>Carroll</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Minnen</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Canning</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Devlin</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Tait</surname>
            <given-names>J</given-names>
          </name>
        </person-group>
        <article-title>Practical simplification of English newspaper text to assist aphasic readers</article-title>
        <source>Proceedings of the AAAI-98 Workshop on Integrating Artificial Intelligence and Assistive Technology</source>  
        <year>1998</year>  
        <conf-name>AAAI-98</conf-name>
        <conf-date>July 26–30, 1998</conf-date>
        <conf-loc>Madison, WI</conf-loc>
        <publisher-name>Association for the Advancement of Artificial Intelligence</publisher-name></nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Specia</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Jauhar</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Mihalcea</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>SemEval-2012 task 1: English lexical simplification</article-title>
        <year>2012</year>  
        <conf-name>First Joint Conference on Lexical and Computational Semantics</conf-name>
        <conf-date>2012</conf-date>
        <conf-loc>Montréal, Canada</conf-loc>
        <publisher-name>Association for Computational Linguistics</publisher-name></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>Crossley</surname>
            <given-names>SA</given-names>
          </name>
          <name name-style="western">
            <surname>Louwerse</surname>
            <given-names>MM</given-names>
          </name>
          <name name-style="western">
            <surname>McCarthy</surname>
            <given-names>PM</given-names>
          </name>
          <name name-style="western">
            <surname>McNamara</surname>
            <given-names>DS</given-names>
          </name>
        </person-group>
        <article-title>A linguistic analysis of simplified and authentic texts</article-title>
        <source>Modern Language J</source>  
        <year>2007</year>  
        <month>03</month>  
        <volume>91</volume>  
        <issue>1</issue>  
        <fpage>15</fpage>  
        <lpage>30</lpage>  
        <pub-id pub-id-type="doi">10.1111/j.1540-4781.2007.00507.x</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>McLaughlin</surname>
            <given-names>GH</given-names>
          </name>
        </person-group>
        <article-title>SMOG grading-a new readability formula</article-title>
        <source>J Read</source>  
        <year>1969</year>  
        <volume>12</volume>  
        <issue>8</issue>  
        <fpage>639</fpage>  
        <lpage>46</lpage> </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>Liu</surname>
            <given-names>S</given-names>
          </name>
          <collab>Wei Ma</collab>
          <name name-style="western">
            <surname>Moore</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Ganesan</surname>
            <given-names>V</given-names>
          </name>
          <name name-style="western">
            <surname>Nelson</surname>
            <given-names>S</given-names>
          </name>
        </person-group>
        <article-title>RxNorm: prescription for electronic drug information exchange</article-title>
        <source>IT Prof</source>  
        <year>2005</year>  
        <month>09</month>  
        <volume>7</volume>  
        <issue>5</issue>  
        <fpage>17</fpage>  
        <lpage>23</lpage>  
        <pub-id pub-id-type="doi">10.1109/MITP.2005.122</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>McDonald</surname>
            <given-names>CJ</given-names>
          </name>
          <name name-style="western">
            <surname>Huff</surname>
            <given-names>SM</given-names>
          </name>
          <name name-style="western">
            <surname>Suico</surname>
            <given-names>JG</given-names>
          </name>
          <name name-style="western">
            <surname>Hill</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Leavelle</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Aller</surname>
            <given-names>R</given-names>
          </name>
          <name name-style="western">
            <surname>Forrey</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Mercer</surname>
            <given-names>K</given-names>
          </name>
          <name name-style="western">
            <surname>DeMoor</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Hook</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Williams</surname>
            <given-names>W</given-names>
          </name>
          <name name-style="western">
            <surname>Case</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Maloney</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>LOINC, a universal standard for identifying laboratory observations: a 5-year update</article-title>
        <source>Clin Chem</source>  
        <year>2003</year>  
        <month>04</month>  
        <volume>49</volume>  
        <issue>4</issue>  
        <fpage>624</fpage>  
        <lpage>33</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.clinchem.org/cgi/pmidlookup?view=long&#38;pmid=12651816"/>
        </comment>  
        <pub-id pub-id-type="medline">12651816</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>Aronson</surname>
            <given-names>AR</given-names>
          </name>
        </person-group>
        <article-title>Effective mapping of biomedical text to the UMLS Metathesaurus: the MetaMap program</article-title>
        <source>Proc AMIA Symp</source>  
        <year>2001</year>  
        <fpage>17</fpage>  
        <lpage>21</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/11825149"/>
        </comment>  
        <pub-id pub-id-type="medline">11825149</pub-id>
        <pub-id pub-id-type="pii">D010001275</pub-id>
        <pub-id pub-id-type="pmcid">PMC2243666</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>Zeng</surname>
            <given-names>QT</given-names>
          </name>
          <name name-style="western">
            <surname>Tse</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Divita</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Keselman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Crowell</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Browne</surname>
            <given-names>AC</given-names>
          </name>
          <name name-style="western">
            <surname>Goryachev</surname>
            <given-names>S</given-names>
          </name>
          <name name-style="western">
            <surname>Ngo</surname>
            <given-names>L</given-names>
          </name>
        </person-group>
        <article-title>Term identification methods for consumer health vocabulary development</article-title>
        <source>J Med Internet Res</source>  
        <year>2007</year>  
        <month>02</month>  
        <day>28</day>  
        <volume>9</volume>  
        <issue>1</issue>  
        <fpage>e4</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.jmir.org/2007/1/e4/"/>
        </comment>  
        <pub-id pub-id-type="doi">10.2196/jmir.9.1.e4</pub-id>
        <pub-id pub-id-type="medline">17478413</pub-id>
        <pub-id pub-id-type="pii">v9i1e4</pub-id>
        <pub-id pub-id-type="pmcid">PMC1874512</pub-id></nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zielstorff</surname>
            <given-names>RD</given-names>
          </name>
        </person-group>
        <article-title>Controlled vocabularies for consumer health</article-title>
        <source>J Biomed Inform</source>  
        <year>2003</year>  
        <volume>36</volume>  
        <issue>4-5</issue>  
        <fpage>326</fpage>  
        <lpage>33</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://linkinghub.elsevier.com/retrieve/pii/S1532046403000960"/>
        </comment>  
        <pub-id pub-id-type="medline">14643728</pub-id>
        <pub-id pub-id-type="pii">S1532046403000960</pub-id></nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</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>Tse</surname>
            <given-names>T</given-names>
          </name>
          <name name-style="western">
            <surname>Crowell</surname>
            <given-names>J</given-names>
          </name>
          <name name-style="western">
            <surname>Divita</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Roth</surname>
            <given-names>L</given-names>
          </name>
          <name name-style="western">
            <surname>Browne</surname>
            <given-names>AC</given-names>
          </name>
        </person-group>
        <article-title>Identifying consumer-friendly display (CFD) names for health concepts</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2005</year>  
        <fpage>859</fpage>  
        <lpage>63</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/16779162"/>
        </comment>  
        <pub-id pub-id-type="medline">16779162</pub-id>
        <pub-id pub-id-type="pii">58480</pub-id>
        <pub-id pub-id-type="pmcid">PMC1560732</pub-id></nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Zeng-Treitler</surname>
            <given-names>Q</given-names>
          </name>
          <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>Keselman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Rosendale</surname>
            <given-names>D</given-names>
          </name>
        </person-group>
        <article-title>Making texts in electronic health records comprehensible to consumers: a prototype translator</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2007</year>  
        <fpage>846</fpage>  
        <lpage>50</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/18693956"/>
        </comment>  
        <pub-id pub-id-type="medline">18693956</pub-id>
        <pub-id pub-id-type="pmcid">PMC2655860</pub-id></nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
        <source>Interactive MetaMap</source>  
        <access-date>2017-03-27</access-date>
        <comment>MetaMap - a tool for recognizing UMLS concepts in text 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://metamap.nlm.nih.gov/">https://metamap.nlm.nih.gov/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6pHkKljnu"/></comment> </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
        <source>SEER training</source>  
        <access-date>2017-07-03</access-date>
        <comment>Clinical examinations 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://training.seer.cancer.gov/abstracting/procedures/clinical/">https://training.seer.cancer.gov/abstracting/procedures/clinical/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6pI3kzxgV"/></comment> </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
        <source>NationalRad</source>  
        <access-date>2017-03-28</access-date>
        <comment>Diagnostic radiology reports 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://nationalrad.com/radiology/reports/">http://nationalrad.com/radiology/reports/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6pI44pMN6"/></comment> </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="web">
        <source>mtsamples</source>  
        <access-date>2017-03-28</access-date>
        <comment>Transcribed medical transcription sample reports and examples 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://mtsamples.com/">http://mtsamples.com/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6pI4VrzLw"/></comment> </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
        <source>Radisphereradiology</source>  
        <access-date>2017-03-28</access-date>
        <comment>Radiology reports 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://www.radisphereradiology.com/resources/radiology-reports/">http://www.radisphereradiology.com/resources/radiology-reports/</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6pI4dukaM"/></comment> </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
        <source>NLM</source>  
        <year>2016</year>  
        <access-date>2017-03-12</access-date>
        <publisher-loc>Bethesda, MD</publisher-loc>
        <publisher-name>National Library of Medicine</publisher-name>
        <comment>Current semantic types 
        <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.nlm.nih.gov/research/umls/META3_current_semantic_types.html">https://www.nlm.nih.gov/research/umls/META3_current_semantic_types.html</ext-link>
        <ext-link ext-link-type="webcite" xlink:href="6psCpB4Hf"/></comment> </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Aronson</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <article-title>MetaMap evaluation</article-title>
        <source>NLM</source>  
        <year>2001</year>  
        <fpage>1</fpage>  
        <lpage>12</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://skr.nlm.nih.gov/papers/references/mm.evaluation.pdf"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Van Rossum</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Python programming language</article-title>
        <source>Proceedings of the USENIX Annual Technical Conference</source>  
        <year>2007</year>  
        <conf-name>USENIX Annual Technical Conference</conf-name>
        <conf-date>June 17-22, 2007</conf-date>
        <conf-loc>Santa Clara, CA</conf-loc></nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
        <source>MySQL</source>  
        <year>2010</year>  
        <access-date>2017-12-04</access-date>
        <publisher-name>Oracle</publisher-name>
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://www.mysql.com">https://www.mysql.com</ext-link>
          <ext-link ext-link-type="webcite" xlink:href="6vTBGCUl5"/>
        </comment> </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Agrawal</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Elhanan</surname>
            <given-names>G</given-names>
          </name>
        </person-group>
        <article-title>Contrasting lexical similarity and formal definitions in SNOMED CT: consistency and implications</article-title>
        <source>J Biomed Inform</source>  
        <year>2014</year>  
        <month>02</month>  
        <volume>47</volume>  
        <fpage>192</fpage>  
        <lpage>8</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(13)00180-9"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1016/j.jbi.2013.11.003</pub-id>
        <pub-id pub-id-type="medline">24239752</pub-id>
        <pub-id pub-id-type="pii">S1532-0464(13)00180-9</pub-id></nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="confproc">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Brill</surname>
            <given-names>E</given-names>
          </name>
          <name name-style="western">
            <surname>Moore</surname>
            <given-names>R</given-names>
          </name>
        </person-group>
        <article-title>An improved error model for noisy channel spelling correction</article-title>
        <year>2000</year>  
        <conf-name>Proceedings of the 38th Annual Meeting on Association for Computational Linguistics</conf-name>
        <conf-date>October 03-06, 2000</conf-date>
        <conf-loc>Hong Kong</conf-loc>
        <publisher-loc>Stroudsburg, PA, USA</publisher-loc>
        <publisher-name>Association for Computational Linguistics</publisher-name>
        <fpage>286</fpage>  
        <lpage>93</lpage>  
        <pub-id pub-id-type="doi">10.3115/1075218.1075255</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>Oh</surname>
            <given-names>SC</given-names>
          </name>
          <name name-style="western">
            <surname>Cook</surname>
            <given-names>TS</given-names>
          </name>
          <name name-style="western">
            <surname>Kahn</surname>
            <given-names>CE</given-names>
          </name>
        </person-group>
        <article-title>PORTER: a prototype system for patient-oriented radiology reporting</article-title>
        <source>J Digit Imaging</source>  
        <year>2016</year>  
        <month>08</month>  
        <volume>29</volume>  
        <issue>4</issue>  
        <fpage>450</fpage>  
        <lpage>4</lpage>  
        <pub-id pub-id-type="doi">10.1007/s10278-016-9864-2</pub-id>
        <pub-id pub-id-type="medline">26856348</pub-id>
        <pub-id pub-id-type="pii">10.1007/s10278-016-9864-2</pub-id>
        <pub-id pub-id-type="pmcid">PMC4942390</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>Wu</surname>
            <given-names>Y</given-names>
          </name>
          <name name-style="western">
            <surname>Schuster</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>Z</given-names>
          </name>
          <name name-style="western">
            <surname>Le</surname>
            <given-names>Q</given-names>
          </name>
          <name name-style="western">
            <surname>Norouzi</surname>
            <given-names>M</given-names>
          </name>
          <name name-style="western">
            <surname>Macherey</surname>
            <given-names>W</given-names>
          </name>
        </person-group>
        <article-title>Google's neural machine translation system: bridging the gap between human and machine translation</article-title>
        <source>arXiv</source>  
        <year>2016</year>  
        <fpage>1</fpage>  
        <lpage>23</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="https://arxiv.org/abs/1609.08144"/>
        </comment>  
        <pub-id pub-id-type="pii">arXiv:1609.08144v2</pub-id></nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="book">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Maedche</surname>
            <given-names>A</given-names>
          </name>
        </person-group>
        <source>Ontology Learning for the Semantic Web</source>  
        <year>2002</year>  
        <publisher-loc>New York, NY</publisher-loc>
        <publisher-name>Springer US</publisher-name></nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Wicks</surname>
            <given-names>P</given-names>
          </name>
        </person-group>
        <article-title>PatientsLikeMe: consumer health vocabulary as a folksonomy</article-title>
        <source>AMIA Annu Symp Proc</source>  
        <year>2008</year>  
        <month>11</month>  
        <day>06</day>  
        <fpage>682</fpage>  
        <lpage>6</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/18999004"/>
        </comment>  
        <pub-id pub-id-type="medline">18999004</pub-id>
        <pub-id pub-id-type="pmcid">PMC2656083</pub-id></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>Keselman</surname>
            <given-names>A</given-names>
          </name>
          <name name-style="western">
            <surname>Smith</surname>
            <given-names>CA</given-names>
          </name>
          <name name-style="western">
            <surname>Divita</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>H</given-names>
          </name>
          <name name-style="western">
            <surname>Browne</surname>
            <given-names>AC</given-names>
          </name>
          <name name-style="western">
            <surname>Leroy</surname>
            <given-names>G</given-names>
          </name>
          <name name-style="western">
            <surname>Zeng-Treitler</surname>
            <given-names>Q</given-names>
          </name>
        </person-group>
        <article-title>Consumer health concepts that do not map to the UMLS: where do they fit?</article-title>
        <source>J Am Med Inform Assoc</source>  
        <year>2008</year>  
        <volume>15</volume>  
        <issue>4</issue>  
        <fpage>496</fpage>  
        <lpage>505</lpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/lookup/pmidlookup?view=long&#38;pmid=18436906"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1197/jamia.M2599</pub-id>
        <pub-id pub-id-type="medline">18436906</pub-id>
        <pub-id pub-id-type="pii">M2599</pub-id>
        <pub-id pub-id-type="pmcid">PMC2442253</pub-id></nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
        <person-group person-group-type="author">
          <name name-style="western">
            <surname>Pesquita</surname>
            <given-names>C</given-names>
          </name>
          <name name-style="western">
            <surname>Faria</surname>
            <given-names>D</given-names>
          </name>
          <name name-style="western">
            <surname>Falcão</surname>
            <given-names>AO</given-names>
          </name>
          <name name-style="western">
            <surname>Lord</surname>
            <given-names>P</given-names>
          </name>
          <name name-style="western">
            <surname>Couto</surname>
            <given-names>FM</given-names>
          </name>
        </person-group>
        <article-title>Semantic similarity in biomedical ontologies</article-title>
        <source>PLoS Comput Biol</source>  
        <year>2009</year>  
        <month>07</month>  
        <volume>5</volume>  
        <issue>7</issue>  
        <fpage>e1000443</fpage>  
        <comment>
          <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pcbi.1000443"/>
        </comment>  
        <pub-id pub-id-type="doi">10.1371/journal.pcbi.1000443</pub-id>
        <pub-id pub-id-type="medline">19649320</pub-id>
        <pub-id pub-id-type="pmcid">PMC2712090</pub-id></nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
