<?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 article-type="article-commentary" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIRxMed</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIRx Med</journal-id>
      <journal-title>JMIRx Med</journal-title>
      <issn pub-type="epub">2563-6316</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">v2i3e31568</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/31568</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Authors’ Response to Peer Reviews</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Authors’ Response to Peer Reviews</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Authors’ Response to Peer Reviews of “Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method”</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Meinert</surname>
            <given-names>Edward</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Bright</surname>
            <given-names>Roselie A</given-names>
          </name>
          <degrees>MS, ScD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7565-1284</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Rankin</surname>
            <given-names>Summer K</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <address>
            <institution>Booz Allen Hamilton</institution>
            <addr-line>8283 Greensboro Dr</addr-line>
            <addr-line>McLean, VA, 22102</addr-line>
            <country>United States</country>
            <phone>1 808 594 5975</phone>
            <email>rankin_summer@bah.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6886-3983</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Dowdy</surname>
            <given-names>Katherine</given-names>
          </name>
          <degrees>BA</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5187-5160</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Blok</surname>
            <given-names>Sergey V</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0286-7612</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Bright</surname>
            <given-names>Susan J</given-names>
          </name>
          <degrees>MPH, DVM</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1696-239X</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Palmer</surname>
            <given-names>Lee Anne M</given-names>
          </name>
          <degrees>MPH, VMD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4198-845X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>US Food and Drug Administration</institution>
        <addr-line>Silver Spring, MD</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Booz Allen Hamilton</institution>
        <addr-line>McLean, VA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>US Food and Drug Administration</institution>
        <addr-line>Rockville, MD</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Summer K Rankin 
        <email>rankin_summer@bah.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Jul-Sep</season>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>11</day>
        <month>8</month>
        <year>2021</year>
      </pub-date>
      <volume>2</volume>
      <issue>3</issue>
      <elocation-id>e31568</elocation-id>
      <history>
        <date date-type="received">
          <day>25</day>
          <month>6</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>25</day>
          <month>6</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Roselie A Bright, Summer K Rankin, Katherine Dowdy, Sergey V Blok, Susan J Bright, Lee Anne M Palmer. Originally published in JMIRx Med (https://med.jmirx.org), 11.08.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIRx Med, is properly cited. The complete bibliographic information, a link to the original publication on https://med.jmirx.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://med.jmirx.org/2021/3/e31568" xlink:type="simple"/>
      <related-article related-article-type="companion" id="preprint21249239" ext-link-type="doi" xlink:href="ttps://doi.org/10.1101/2021.01.05.21249239" vol="2" page="21249239" xlink:title="Preprint (medRxiv):" xlink:type="simple">https://www.medrxiv.org/content/10.1101/2021.01.05.21249239v1</related-article>
      <related-article related-article-type="companion" id="preprint27017" ext-link-type="doi" xlink:href="https://doi.org/10.2196/preprints.27017" vol="2" page="e27017" xlink:title="Preprint (JMIR Preprints):" xlink:type="simple">https://preprints.jmir.org/preprint/27017</related-article>
      <related-article related-article-type="companion" id="v2i3e27017" ext-link-type="doi" xlink:href="10.2196/27017" vol="2" page="e27017" xlink:title="Published Article:" xlink:type="simple">https://med.jmirx.org/2021/3/e27017/</related-article>
      <related-article related-article-type="companion" id="v2i3e31547" ext-link-type="doi" xlink:href="10.2196/31547" vol="2" page="e31547" xlink:title="Peer-Review Report by Anonymous:" xlink:type="simple">https://med.jmirx.org/2021/3/e31547/</related-article>
      <related-article related-article-type="companion" id="v2i3e31548" ext-link-type="doi" xlink:href="10.2196/31548" vol="2" page="e31548" xlink:title="Peer-Review Report by Anonymous:" xlink:type="simple">https://med.jmirx.org/2021/3/e31548/</related-article>
      <related-article related-article-type="companion" id="v2i3e31550" ext-link-type="doi" xlink:href="10.2196/31550" vol="2" page="e31550" xlink:title="Peer-Review Report by Mark Antoniou:" xlink:type="simple">https://med.jmirx.org/2021/3/e31550/</related-article>
      <related-article related-article-type="companion" id="v2i3e31551" ext-link-type="doi" xlink:href="10.2196/31551" vol="2" page="e31551" xlink:title="Peer-Review Report by Haiyan Yu:" xlink:type="simple">https://med.jmirx.org/2021/3/e31551/</related-article>
    </article-meta>
  </front>
  <body>
    <p>
      <italic>This is the author’s response to peer-review reports for the paper “Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method”</italic>
    </p>
    <p>This paper [<xref ref-type="bibr" rid="ref1">1</xref>] first underwent review as two separate manuscripts: one on transfusion adverse events and the other on time-based adverse events.</p>
    <p>In addition to responding to the reviewers’ comments [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref5">5</xref>], we made the following changes:</p>
    <sec>
      <title>Round 1 Review: Transfusion Adverse Events</title>
      <sec>
        <title>Anonymous [<xref ref-type="bibr" rid="ref2">2</xref>]</title>
        <sec>
          <title>General Comments</title>
          <list list-type="order">
            <list-item>
              <p>We believe our title matches the study contents. We do not understand how the results of using a new method, applied in a new area (blood transfusion adverse events [AEs]), are “self-evident.” We prefer to keep the title unchanged.</p>
            </list-item>
            <list-item>
              <p>Please see the new subsection “Comparison of the Shakespeare Method to Other Applications of LDA Topic Modeling” at the end of the <italic>Discussion</italic> section:</p>
              <p>“We were unable to find published instances of LDA topic modeling applications for adverse event detection. Furthermore, we found none that apply LDA topic modeling to words or phrases in documents in the group of interest that are filtered to terms that most significantly distinguished a patient group of interest from a comparison group. This filtering process was essential for identifying topics describing the unique qualities of transfused vs nontransfused groups. Also, to our knowledge, we are the first to check the interpretation of documents with large numbers of topics with nontrivial scores.”</p>
            </list-item>
            <list-item>
              <p>Please see the new subsection “Comparison of the Shakespeare Method to Other Applications of LDA Topic Modeling” at the end of the <italic>Discussion</italic> section for a summary of the use of latent Dirichlet allocation (LDA) topic modeling in electronic health record (EHR) data and how the Shakespeare method compares.</p>
              <p>We agree that natural language processing (NLP) is indispensable to finding potential AEs in unstructured text. Please see the new subsection “Comparison of the Shakespeare Method to Other Applications of LDA Topic Modeling” at the end of the <italic>Discussion</italic> section for the new text:</p>
              <p>“LDA topic modeling has been used for a variety of NLP tasks [6,7] (although it can also be used on other high-dimension data) such as text classification and filtering [8].”</p>
              <p>We state in the <italic>Conclusions</italic> section that the final step, manual interpretation of selected original notes, could benefit from adaptation of more sophisticated NLP methods.</p>
            </list-item>
            <list-item>
              <p>As described, LDA topic modeling is one step in the Shakespeare method.</p>
              <p>In the <italic>Discussion</italic> section, “Comparison of the Shakespeare Method to Other Applications of LDA Topic Modeling subsection, we now say:</p>
              <p>“We were unable to find published instances of LDA topic modeling applications for adverse event detection. Furthermore, we found none that apply LDA topic modeling to words or phrases in documents in the group of interest that are filtered to terms that most significantly distinguished a patient group of interest from a comparison group. This filtering process was essential for identifying topics describing the unique qualities of transfused vs nontransfused groups. Also, to our knowledge, we are the first to check the interpretation of documents with large numbers of topics with nontrivial scores.”</p>
            </list-item>
            <list-item>
              <p>Thank you for pointing out this error. We have made the correction to five steps.</p>
            </list-item>
            <list-item>
              <p>We have clarified this sentence in the <italic>Introduction</italic> section, “EHRs for Postmarketing Surveillance” subsection, and made a similar change to the <italic>Background</italic> section in the abstract. The new paragraph is:</p>
              <p>“Many methods for finding AEs in text [9-34] rely on predefining possible AEs before searching for prespecified words and phrases or manual labeling (standardization) by investigators. Crucially, events described in text may not necessarily be attributed to AEs [19,35,36]. We wanted to develop a method to identify possible AEs, even if unknown or unattributed, without any prespecifications or standardization of notes.”</p>
            </list-item>
          </list>
        </sec>
      </sec>
      <sec>
        <title>Anonymous [<xref ref-type="bibr" rid="ref3">3</xref>]</title>
        <sec>
          <title>General Comments</title>
          <p>We have clarified our statements in the <italic>Introduction</italic> section, “Selection of Case of Blood Transfusion” subsection, to indicate that some transfusion AEs were established in the literature by 2002 while others were gaining recognition over the time of the data set (2001-2012).</p>
        </sec>
        <sec>
          <title>Specific Comments</title>
          <sec>
            <title>Major Comments</title>
            <list list-type="order">
              <list-item>
                <p>We are in the process of publishing the code and expect to have a permanent citation in a few weeks. We now cite it as reference 54 in the <italic>Methods</italic> section, “The Shakespeare method” subsection.</p>
              </list-item>
              <list-item>
                <p>The details are in another paper we cited (reference 57).</p>
              </list-item>
              <list-item>
                <p>We added some explanation to the <italic>Methods</italic> section, “Step 4. Model Topics” subsection:</p>
                <list list-type="order">
                  <list-item>
                    <p>“An important consideration for LDA is that the number of topics must be selected a priori. The results of topic modeling change depending on the number of topics assigned to a corpus—this is an iterative (hyperparameter tuning) process that requires human judgment to interpret the topics (based on the top terms in each topic) and determine which number of topics best fits the corpus. With too few topics assigned, topics are not cohesive and do not add any clarity or information to an analysis. With too many topics assigned, “incoherent” topics that do not capture terms common to the member documents proliferate; also, useful topics are likely split among smaller, more specific topics, although that does not limit the ability to analyze true clusters in the corpus.</p>
                    <p>To tune the hyperparameters of the LDA model, we calculated models with the following numbers of topics: 25, 35, 45, 55, 65, 75, 85. We observed (data not shown):</p>
                    <p>In the <italic>Discussion</italic> section, “Comparison of the Shakespeare Method to Other Applications of LDA Topic Modeling” subsection, we added:</p>
                    <p>“The chosen number of topics was effective for identifying a range of PTAEs. Evaluation of the overlap of topics and contents of documents identified for varying numbers of topics has not been reported in the literature. Our iterative approach to evaluating different hyperparameters demonstrated to our satisfaction the relative stability of PTAEs indicated by topics.</p>
                    <p>We determined the number of topics based on our experience of tuning the hyperparameters, the number of TAEs reported in the literature, and the complexities of critical care patients. We were satisfied with the number because there was both overlap of topics that simultaneously had high word and document scores and some incoherent topics with low scores. As the number of topics gets too large, additional topics are uninterpretable, and that as data set size increases, more robust topics are generated [37].”</p>
                  </list-item>
                  <list-item>
                    <p>In the <italic>Discussion</italic> section, “Comparison of the Shakespeare Method to Other Applications of LDA Topic Modeling” subsection, we added:</p>
                    <p>“Systematic evaluation of the number of topics and other hyperparameters is always necessary for LDA topic modeling in a new setting.”</p>
                  </list-item>
                  <list-item>
                    <p>In the <italic>Methods</italic> section, “Step 4. Model Topics” subsection, we added:</p>
                    <p>“Topic modeling is an unsupervised method commonly used in NLP to extract the most relevant terms for each topic (cluster) of similar documents [6,7]. We chose latent Dirichlet allocation (LDA) [8] to accomplish topic modeling of the T documents. LDA is a generative probabilistic model that results in interpretable dimensionality reduction, which means that we reduced 41,664 terms to 45 topics for our data. A topic is a multimodal distribution of terms over an entire vocabulary (in our case, all the filtered terms). A topic consists of co-occurring terms in this corpus of T documents. Each document can have a mixture of these topics. Each topic contribution in a document is a probability (we refer to this as a document topic score); thus, the scores of all topics for a document sum to 1 (see Figure 3D).”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>In the new <italic>Discussion</italic> section, “Use of Classification to Filter Document Vectors” subsection, we added:</p>
                <p>“As noted before, we were initially surprised that primarily unigrams (and not the longer sequences) appeared to play a significant role in distinguishing transfusion from control texts. We believe it is possible that enough unigrams that were part of meaningful phrases were also in other phrases or were significant on their own to result in relatively higher scores. For example, although “mechanical ventilation” conveys more meaning than just “mechanical” or “ventilation,” each word occurs singly or in phrases other than “mechanical ventilation.” Because bigrams and phrases were important in other LDA studies [38,39], we do not conclude that our unigram finding is necessarily applicable to other study settings. In this data set and blood transfusion situation, including only unigrams would not be expected to have changed the particular unigrams selected during the ensemble classification step. In other studies, it might be important to include n-grams where n&gt;1.”</p>
                <p>In the new <italic>Discussion</italic> section, “Use of Classification to Trim Document Vectors” subsection, we added:</p>
                <p>“In this data set and blood transfusion situation, including only unigrams would not be expected to have changed the particular unigrams selected during the ensemble classification step. In other studies, it might be important to include n-grams where n&gt;1.”</p>
                <p>In the new <italic>Discussion</italic> section, “Use of Classification to Trim Document Vectors” subsection, we added:</p>
                <p>“Because bigrams and phrases were important in other LDA studies [38,39], we do not conclude that our unigram finding is necessarily applicable to other study settings.”</p>
              </list-item>
              <list-item>
                <p>We agree. In the <italic>Conclusion</italic> section, we added:</p>
                <p>“We present our use of the Shakespeare method for a different surveillance question elsewhere [40].”</p>
              </list-item>
              <list-item>
                <p>The renamed <italic>Methods</italic> subsection “Step 3. Extract Significant Terms” now explains the filtering (trimming) method in more detail.</p>
                <p>In the new <italic>Discussion</italic> section, “Use of Classification to Filter Document Vectors” subsection, we added:</p>
                <p>“Filtering the vectors to only terms that were important for focusing the topics on clinical conditions specific to transfusion, including reasons for and consequences of transfusion, was important for identifying PTAEs.”</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Minor Comments</title>
            <list list-type="order">
              <list-item>
                <p>We simplified the statement to:</p>
                <p>“We chose the case of transfusion adverse events (TAEs) and potential TAEs (PTAEs) because new TAE types were becoming recognized during the study data period, so we anticipated an opportunity to find unattributed TAEs in the notes.”</p>
              </list-item>
              <list-item>
                <p>Thank you for finding this mistake, which we corrected to “five steps.”</p>
              </list-item>
              <list-item>
                <p>Thank you for finding this typo in the <italic>Conclusion</italic> section. “Her” should have been “EHRs” and has been corrected.</p>
              </list-item>
            </list>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec>
      <title>Round 2 Review: Transfusion Adverse Events</title>
      <p>We finalized the citation for the Shakespeare method software in reference 54, and submitted manuscripts with and without tracked changes that show our changes.</p>
      <p>We believe we addressed the reviewer’s [<xref ref-type="bibr" rid="ref2">2</xref>] concerns. We apparently did not because some of the prior concerns remain in this review round. We are puzzled by the newly restated comments and would like more clarity on his/her points so that we can be sure to address the concerns. We provide more details about our questions as individual responses below.</p>
      <sec>
        <title>Anonymous [<xref ref-type="bibr" rid="ref2">2</xref>]</title>
        <sec>
          <title>General Comments</title>
          <p>We disagree that the Shakespeare method is an alternative to NLP, because we leverage NLP, which includes many methods. As part of the Shakespeare method, we used the following NLP methods: n-gram formation, count vectorization, supervised learning, and LDA topic modeling. We mentioned another NLP method, word/phrase searches, in the <italic>Introduction</italic> section, thus demonstrating our understanding of that method; we also discussed why we did not choose to use it. To form the transfused and nontransfused groups, we created and used a dictionary of transfusion terms. Outside of our paper, we are, indeed, familiar with many other NLP methods (stemming, sentence boundary recognition, part-of-speech tagging, parsing, semantics, sentiment analysis, word sense disambiguation, language models, language translation, and neural network–based machine learning) that are a menu of methods that may or may not be useful for a particular application. We do not understand why the reviewer thinks we do not understand NLP, why the reviewer thinks NLP is the preferred alternative to the Shakespeare method, and why that means we might be making mistaken conclusions.</p>
        </sec>
        <sec>
          <title>Specific Comments</title>
          <sec>
            <title>Major Comments</title>
            <list list-type="order">
              <list-item>
                <p>The reviewer seems to agree that the dictionary method relies on predefined possible AEs, which could rely on, for example, the Unified Medical Language System vocabulary list and could miss important terms. We are proposing an alternative method to find both expected and unexpected possible AEs, as we state in the <italic>Introduction</italic> section. We do not understand what the criticism is.</p>
              </list-item>
              <list-item>
                <p>We agree and state in the <italic>Discussion</italic> section that in addition to possibly causal TAEs, the Shakespeare method identified reasons for transfusion, consequences of reasons for transfusion, and possibly noncausal PTAEs. We agree and state that the PTAEs need manual review to distinguish among these groups. As we state, the difference from the NLP dictionary method is that the Shakespeare method found PTAEs that were not described as related to transfusion in the notes or billing codes. The dictionary method cannot find potentially important terms and phrases that are not in the dictionary.</p>
              </list-item>
              <list-item>
                <p>The application of the Shakespeare method to blood transfusion is a use scenario, so we do not understand why the reviewer thinks a potential use scenario needs to be included; however, we did include reference 107 as an additional scenario. We do not understand why or how manual review is an example of a potential use scenario. We reported our manual review of the results, so we do not understand what the reviewer means by asking “will more manual reviews be needed for the results.”</p>
              </list-item>
            </list>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec>
      <title>Round 1 Review: Time-Based Adverse Events</title>
      <sec>
        <title>Reviewer CD</title>
        <sec>
          <title>General Comments</title>
          <list list-type="order">
            <list-item>
              <p>We changed the beginning of the sentence to “We examined whether.”</p>
            </list-item>
            <list-item>
              <p>Thank you!</p>
            </list-item>
            <list-item>
              <p>We already stated some limitations. In the subsection “Discussion of Time Periods Case,” we pointed out that removing numerals from alphanumeric words had resulted in the creation of a “junk” topic that we would not recommend doing again. Additionally, in the <italic>Conclusions</italic> section, we mentioned that further development of tools for evaluating the reports would be very helpful. Furthermore, in the subsection “Use of Classification to Filter Document Vectors,” we added our observation that only unigrams survived the classification process in both the transfusion and time periods cases, and declined to recommend only using unigrams in other settings.</p>
            </list-item>
          </list>
        </sec>
      </sec>
      <sec>
        <title>Reviewer CI</title>
        <sec>
          <title>General Comments</title>
          <p>We appreciate the reviewer’s praise and hope we have satisfied the concerns.</p>
        </sec>
        <sec>
          <title>Specific Comments</title>
          <sec>
            <title>Major Comments</title>
            <list list-type="order">
              <list-item>
                <p>We agree that it would be great to know the accuracy of the Shakespeare method. Please see “Top-Scoring Documents for Each Transfusion Topic,” where we reviewed a random selection of transfusion admissions and compared them to the transfusion documents with high topic scores.</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Minor Comments</title>
            <list list-type="order">
              <list-item>
                <p>We trimmed the list of keywords.</p>
              </list-item>
              <list-item>
                <p>We are satisfied with the current state of the <italic>Conclusions</italic> section.</p>
              </list-item>
            </list>
          </sec>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AE</term>
          <def>
            <p>adverse event</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">LDA</term>
          <def>
            <p>latent Dirichlet allocation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">NLP</term>
          <def>
            <p>natural language processing</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>Bright</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Dowdy</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rankin</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Blok</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Palmer</surname>
              <given-names>LAM</given-names>
            </name>
            <name name-style="western">
              <surname>Bright</surname>
              <given-names>SJ</given-names>
            </name>
          </person-group>
          <article-title>Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method</article-title>
          <source>JMIRx Med</source>
          <year>2021</year>
          <month>8</month>
          <day>11</day>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>e27017</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://med.jmirx.org/2021/3/e27017/">https://med.jmirx.org/2021/3/e27017/</ext-link>
          </comment>
          <pub-id pub-id-type="doi">10.2196/27017</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Anonymous</collab>
          </person-group>
          <article-title>Peer Review of "Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method"</article-title>
          <source>JMIRx Med</source>
          <year>2021</year>
          <month>8</month>
          <day>11</day>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>e31547</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://med.jmirx.org/2021/3/e31547/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/31547</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Anonymous</collab>
          </person-group>
          <article-title>Peer Review of "Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method"</article-title>
          <source>JMIRx Med</source>
          <year>2021</year>
          <month>8</month>
          <day>11</day>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>e31548</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://med.jmirx.org/2021/3/e31548/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/31548</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Antoniou</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Peer Review of "Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method"</article-title>
          <source>JMIRx Med</source>
          <year>2021</year>
          <month>8</month>
          <day>11</day>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>e31550</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://med.jmirx.org/2021/3/e31550/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/31550</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>Yu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Peer Review of "Finding Potential Adverse Events in the Unstructured Text of Electronic Health Care Records: Development of the Shakespeare Method"</article-title>
          <source>JMIRx Med</source>
          <year>2021</year>
          <month>8</month>
          <day>11</day>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>e31551</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://med.jmirx.org/2021/3/e31551/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/31551</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
