<?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="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v13i1e66476</article-id>
      <article-id pub-id-type="pmid">40705416</article-id>
      <article-id pub-id-type="doi">10.2196/66476</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>Improving Large Language Models’ Summarization Accuracy by Adding Highlights to Discharge Notes: Comparative Evaluation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Benis</surname>
            <given-names>Arriel</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chrimes</surname>
            <given-names>Dillon</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chaturvedi</surname>
            <given-names>Akhil</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Koohi Habibi Dehkordi</surname>
            <given-names>Mahshad</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution/>
            <institution>Department of Computer Science</institution>
            <institution>New Jersey Institute of Technology</institution>
            <addr-line>Ying Wu College of Computing, NJIT, 323 Martin Luther King Jr. Blvd</addr-line>
            <addr-line>Apt 1</addr-line>
            <addr-line>Newark, NJ, 07102</addr-line>
            <country>United States</country>
            <phone>1 973 596 3000</phone>
            <email>mk985@njit.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3489-0892</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Perl</surname>
            <given-names>Yehoshua</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1940-9386</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Deek</surname>
            <given-names>Fadi P</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0001-1022-4118</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>He</surname>
            <given-names>Zhe</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3608-0244</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Keloth</surname>
            <given-names>Vipina K</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6919-1122</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Hao</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1975-1272</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Elhanan</surname>
            <given-names>Gai</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1518-5522</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Einstein</surname>
            <given-names>Andrew J</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff7" ref-type="aff">7</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2583-9278</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Computer Science</institution>
        <institution>New Jersey Institute of Technology</institution>
        <addr-line>Newark, NJ</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Informatics</institution>
        <institution>New Jersey Institute of Technology</institution>
        <addr-line>Newark, NJ</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>School of Information</institution>
        <institution>Florida State University</institution>
        <addr-line>Tallahassee, FL</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Medical Informatics</institution>
        <institution>Yale University</institution>
        <addr-line>New Haven, CT</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Department of Computer Science</institution>
        <institution>Montclair State University</institution>
        <addr-line>Montclair, NJ</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>School of Medicine</institution>
        <institution>University of Nevada</institution>
        <addr-line>Reno, NV</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff7">
        <label>7</label>
        <institution>Department of Medicine</institution>
        <institution>Columbia University Irving Medical Center</institution>
        <addr-line>New York, NY</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Mahshad Koohi Habibi Dehkordi <email>mk985@njit.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>24</day>
        <month>7</month>
        <year>2025</year>
      </pub-date>
      <volume>13</volume>
      <elocation-id>e66476</elocation-id>
      <history>
        <date date-type="received">
          <day>15</day>
          <month>9</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>29</day>
          <month>11</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>20</day>
          <month>12</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>16</day>
          <month>6</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Mahshad Koohi Habibi Dehkordi, Yehoshua Perl, Fadi P Deek, Zhe He, Vipina K Keloth, Hao Liu, Gai Elhanan, Andrew J Einstein. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 24.07.2025.</copyright-statement>
      <copyright-year>2025</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2025/1/e66476" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The American Medical Association recommends that electronic health record (EHR) notes, often dense and written in nuanced language, be made readable for patients and laypeople, a practice we refer to as the simplification of discharge notes. Our approach to achieving the simplification of discharge notes involves a process of incremental simplification steps to achieve the ideal note. In this paper, we present the first step of this process. Large language models (LLMs) have demonstrated considerable success in text summarization. Such LLM summaries represent the content of EHR notes in an easier-to-read language. However, LLM summaries can also introduce inaccuracies.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to test the hypothesis that summaries generated by LLMs from highlighted discharge notes will achieve increased accuracy compared to those generated from the original notes. For this purpose, we aim to prove a hypothesis that summaries generated by LLMs of discharge notes in which detailed information is highlighted are likely to be more accurate than summaries of the original notes.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>To test our hypothesis, we randomly sampled 15 discharge notes from the MIMIC III database and highlighted their detailed information using an interface terminology we previously developed with machine learning. This interface terminology was curated to encompass detailed information from the discharge notes. The highlighted discharge notes distinguished detailed information, specifically the concepts present in the aforementioned interface terminology, by applying a blue background. To calibrate the LLMs’ summaries for our simplification goal, we chose GPT-4o and used prompt engineering to ensure high-quality prompts and address issues of output inconsistency and prompt sensitivity. We provided both highlighted and unhighlighted versions of each EHR note along with their corresponding prompts to GPT-4o. Each generated summary was manually evaluated to assess its quality using the following evaluation metrics: completeness, correctness, and structural integrity.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>We used the study sample of 15 discharge notes. On average, summaries from highlighted notes (H-summaries) achieved 96% completeness, 8% higher than the summaries from unhighlighted notes (U-summaries). H-summaries had higher completeness in 13 notes, and U-summaries had higher or equal completeness in 2 notes, resulting in <italic>P</italic>=.01, which implied statistical significance. Moreover, H-summaries demonstrated better correctness than U-summaries, with fewer instances of erroneous information (2 vs 3 errors, respectively). The number of improper headers was smaller for H-summaries for 11 notes and U-summaries for 4 notes (<italic>P</italic>=.03; implying statistical significance). Moreover, we identified 8 instances of misplaced information in the U-summaries and only 2 in the H-summaries. We showed that our findings supported the hypothesis that summarizing highlighted discharge notes improves the accuracy of the summaries.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Feeding LLMs with highlighted discharge notes, combined with prompt engineering, results in higher-quality summaries in terms of correctness, completeness, and structural integrity compared to unhighlighted discharge notes.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>electronic health record</kwd>
        <kwd>EHR</kwd>
        <kwd>EHR summaries</kwd>
        <kwd>clinical notes summarization</kwd>
        <kwd>discharge notes summarization</kwd>
        <kwd>LLM summaries</kwd>
        <kwd>ChatGPT summaries</kwd>
        <kwd>highlighted EHR notes</kwd>
        <kwd>accuracy of summaries</kwd>
        <kwd>discharge notes</kwd>
        <kwd>large language model</kwd>
        <kwd>LLM</kwd>
        <kwd>ChatGPT</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>AI</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Electronic health records (EHRs) [<xref ref-type="bibr" rid="ref1">1</xref>] are digital versions of a patient’s medical records that were originally intended for communication among health care professionals, such as clinicians and nurses, to facilitate quick comprehension and efficient interoperability. These notes are typically written in highly technical language, filled with abbreviations, complex sentence structures, and medical jargon that may be unfamiliar to individuals without a medical background [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
        <p>According to the 21st Century Cures Act and the Open Notes Rule [<xref ref-type="bibr" rid="ref3">3</xref>], it is required to make these notes available to patients through patient portals, and because of this, a significant challenge has emerged. Patients with limited health literacy may struggle to understand written medical information, communicate health concerns with health care providers, and navigate EHR systems [<xref ref-type="bibr" rid="ref2">2</xref>]. Research shows that patients often use different vocabulary than clinicians when searching for health information [<xref ref-type="bibr" rid="ref4">4</xref>], indicating that the language clinicians use in discharge notes is potentially unfamiliar and difficult for patients to understand. To increase the comprehension of EHR notes, the American Medical Association recommends a grade 6 reading level, whereas the National Institutes of Health (NIH) recommends a grade 7 to 8 reading level for EHR notes [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. The National Cancer Institute recommends an grade 6 reading level, reflecting the average reading level for a US citizen [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>].</p>
        <p>Large language models (LLMs) [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref13">13</xref>] have demonstrated success in text summarization and simplification tasks [<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref16">16</xref>]. ChatGPT (OpenAI) [<xref ref-type="bibr" rid="ref17">17</xref>], in particular, has shown promise in generating summaries that are comparable to those created by human experts [<xref ref-type="bibr" rid="ref18">18</xref>]. Prompt engineering [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>] has gained significant popularity in recent years due to its potential to improve the performance of LLMs. By carefully crafting prompts, we can instruct LLMs on how to extract key information, maintain coherence, and structure summaries according to specific needs. Well-designed prompts help control the level of detail, tone, and style, thereby improving both accuracy and readability [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Because LLMs rely on input instructions [<xref ref-type="bibr" rid="ref22">22</xref>], prompt engineering is essential for aligning model behavior with the desired summarization outcome, reducing ambiguity and enhancing reliability.</p>
        <p>Despite the advantages, several concerns remain regarding the use of LLMs in the medical field, particularly for summarizing medical texts [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. These include issues of reliability, inconsistency in output quality, the potential for false information, and prompt sensitivity. Without addressing these concerns, LLMs might not realize their full potential for summarizing discharge notes. As mentioned earlier, the presence of inadequate sentence structure, a lack of punctuation, the presence of fragmented expressions, and an abundance of abbreviations within discharge notes make summarization relatively more difficult compared to general domain text summarization. Therefore, LLM-generated summaries may sometimes omit crucial information or lack proper structure.</p>
        <p>In this paper, we present the first step in the process of simplifying discharge notes by harnessing the summarization capabilities of LLMs. In this study, we aim to generate more accurate, structured summaries from discharge notes where headers provide clear orientation and make the content easier to understand [<xref ref-type="bibr" rid="ref25">25</xref>]. These summaries are then converted into accurate, simplified notes that are understandable for patients with a grade 6 reading level [<xref ref-type="bibr" rid="ref26">26</xref>].</p>
        <p>To address and evaluate the loss of crucial information in the summaries of discharge notes, our approach involves modifying the input by providing LLMs with highlighted discharge notes, where detailed information is emphasized. We then compare these summaries with those generated from unhighlighted notes. Our previous research [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>] developed an innovative method for automatically highlighting detailed information in discharge notes. In this study, we automatically highlighted discharge notes using that technique (which is described in the Methods section). Our technique also uses prompt engineering to enhance the structural integrity of the generated summaries and address prompt sensitivity. We hypothesize that feeding LLMs with the highlighted notes aids in summarizing them more accurately. The rationale for this prediction is that, with a prompt to focus on the highlighted detailed information in a text, the summary will be more accurate and better structured than one obtained without highlighting.</p>
        <p>We conducted this study to test the following hypothesis: Summaries generated by LLMs from highlighted discharge notes will achieve increased accuracy compared to those generated from the original notes. This is done by generating summaries from both unhighlighted and highlighted discharge notes using LLMs and then comparing both versions of the summaries for each discharge note to see which method yields better results. We evaluated different dimensions of the accuracy of summaries with proper metrics, including completeness, correctness, and structural integrity. Our findings support the hypothesis that summarizing highlighted discharge notes improves the accuracy of the summaries as measured by these metrics. Thus, it is advantageous to generate summaries of discharge notes after highlighting them. Structured summaries of highlighted discharge notes provide a valuable starting point for future efforts to enhance the simplification of these notes while maintaining their accuracy.</p>
      </sec>
      <sec>
        <title>Related Work</title>
        <p>The goal of text summarization is to condense text while keeping its key information and important content intact [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. Before the advent of LLMs, text summarization was primarily performed by automatic text summarization (ATS) [<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. ATS involves a trainable summarizer that considers various features, such as sentence position, keywords, sentence centrality, resemblance to the title, inclusion of named entities and numerical data, relative length, bushy path, and aggregated similarity to generate summaries [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
        <p>While traditional ATS methods are still in use, LLMs are increasingly adopted for summarization tasks as they have shown great performance in this area. Therefore, there has been a significant shift from ATS to LLMs, with methods evolving from pretraining and fine-tuning to prompt-based approaches [<xref ref-type="bibr" rid="ref31">31</xref>]. Besides, when summarizing discharge notes, mainly replete with medical abbreviations, LLMs typically spell out most of the abbreviations, yielding more readable clinical notes.</p>
        <p>In a recent study [<xref ref-type="bibr" rid="ref35">35</xref>], 8 LLMs (Flan-T5, Flan-UL2, Alpaca, MedAlpaca, Vicuna, Llama-2, GPT-3.5, and GPT-4) were evaluated for various clinical text summarization tasks. The study identified GPT-4 as the best-performing model, particularly when using in-context learning [<xref ref-type="bibr" rid="ref36">36</xref>] for adaptation. GPT-4 demonstrated superior completeness, correctness, and conciseness in summaries compared to other models and even human experts. Therefore, in this study, we have used the latest version of ChatGPT, GPT-4o, for summarization.</p>
        <p>In the study by Kanwal and Rizzo [<xref ref-type="bibr" rid="ref37">37</xref>], they developed an extractive summarization method tailored for discharge notes using a bidirectional encoder representations from transformers–based model fine-tuned on the MIMIC-III dataset. Their approach uses attention scores from the final transformer layer to identify clinically important sentences without relying on reference summaries. The model dynamically selects sentences with above-average attention scores, aiming to preserve essential clinical content. Their method outperformed 3 baseline approaches, namely frequency-based, graph-based, and K-means centroid-based extractive summarization, demonstrating better content preservation and semantic alignment with the original notes.</p>
        <p>In the study by Alsentzer and Kim [<xref ref-type="bibr" rid="ref38">38</xref>], they explored extractive summarization of discharge notes from the MIMIC-III database. They estimated an upper bound on extractive summarization by measuring how much of the information in a discharge summary can be found elsewhere in the patient’s EHR notes using concept unique identifiers. To support future summarization tasks, they also developed a long short-term memory model to label word-level topics in the “history of present illness” sections. This classifier achieved an <italic>F</italic><sub>1</sub>-score of 0.876 on a manually annotated test set, demonstrating its potential for generating topic-specific evaluation datasets for extractive summarization models.</p>
        <p>In the study by Ma et al [<xref ref-type="bibr" rid="ref39">39</xref>], the researchers developed a method called ImpressionGPT to summarize the “impression” section of radiology reports using ChatGPT. They used a dynamic prompt generation and iterative optimization approach to improve the performance of ChatGPT in this task. The results showed that ImpressionGPT achieved better performance in generating correct and concise summaries compared to existing methods, demonstrating its potential to enhance clinical workflows and reduce the workload of health care professionals.</p>
        <p>The challenges faced by clinicians with limited time to remain abreast of the rapidly expanding medical literature have been documented in the study by Hake et al [<xref ref-type="bibr" rid="ref40">40</xref>]. The authors evaluated the performance of ChatGPT in summarizing 140 peer-reviewed medical abstracts from 14 different journals. Their methodology involved prompting ChatGPT to create summaries and then having physicians assess the quality, accuracy, and bias of these summaries, where bias refers to the phenomenon where artificial intelligence (AI) systems are trained on data that lack sufficient reflection of the diversity within the population. The results showed that ChatGPT-produced summaries were 70% shorter than the original abstracts but maintained an accuracy of 92.5%. The study concluded that while ChatGPT can aid in summarizing medical literature, full-text evaluation remains crucial for critical medical decisions. Although they conducted the study on scientific paper abstracts, which are well structured and have much simpler language than discharge notes, they reported several occurrences of serious inaccuracies in ChatGPT summaries that could materially impact the major interpretation of the text.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>Existing research on summarization using ChatGPT [<xref ref-type="bibr" rid="ref35">35</xref>] has primarily focused on prompt engineering to achieve optimal results. These studies have not explored the potential benefits of modifying the input format and providing customized context tailored to the specific text. In contrast, our study goes beyond prompt engineering by incorporating important information directly into the input text. This approach ensures that ChatGPT pays attention to key details, enhancing the completeness, correctness, and structural integrity of the generated summaries.</p>
        <p>In the Methods section, we first explain the automatic EHR highlighting technique, followed by the summarization method used in this study.</p>
      </sec>
      <sec>
        <title>Automatic EHR Highlighting</title>
        <p>In our previous studies [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], we developed a cardiology interface terminology (CIT) to facilitate efficient highlighting of detailed content in cardiology-related discharge notes. The process is composed of 2 phases. In the first phase [<xref ref-type="bibr" rid="ref27">27</xref>], we created an initial version of CIT (ICIT), which contains the cardiology-related subhierarchies of Systematized Nomenclature of Medicine–Clinical Terms [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. However, ICIT did not capture all the important information from the discharge notes of cardiology patients. Therefore, we added concepts by extracting fine-granularity phrases from discharge notes that contained ICIT concepts. This was done using a semiautomatic iterative process, resulting in the formation of CIT. In each iteration, we highlighted the build dataset with the last version of the CIT and calculated the coverage and breadth of the highlighted dataset. Coverage is the percentage of the total number of words that are highlighted in one note, and breadth is the average length of each highlighted concept.</p>
        <p>We defined 2 operations for mining more complex, higher-granularity phrases from the build dataset: concatenation and anchoring. Concatenation combined adjacent highlighted concepts, potentially separated by stop words, to form a meaningful phrase. Anchoring expanded existing highlighted concepts by attaching surrounding words on the left, right, or both sides. We applied an iterative process in which the application of the concatenation operation was followed by the application of the anchoring operation.</p>
        <p>Because CIT is an interface terminology, its concepts should follow the requirements for being considered concepts of a terminology. According to the desiderata of Cimino et al [<xref ref-type="bibr" rid="ref43">43</xref>], a concept is an embodiment of a particular meaning. Concept orientation means that terms must correspond to at least one meaning (“nonvagueness”) and no more than one meaning (“nonambiguity”) and that meanings correspond to no more than one term (“nonredundancy”) [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>].</p>
        <p>After each application of either concatenation or anchoring, the newly mined phrases, as potential CIT concepts, were manually and automatically reviewed. Phrases that were deemed legitimate during the review, both structurally and semantically, such as “normal ejection fraction,” were accepted and added to the CIT. All illegitimate phrases, whether identified automatically or manually, were added to a rejection list. For example, “step down unit for further” was rejected because it is a truncated phrase with an incomplete meaning. After each application of either the concatenation or anchoring operation, we highlighted the build dataset with the updated version of the CIT. This iterative process continued until the increase in coverage became negligible (&lt;2% increase). The results of this phase served as training data for the second phase, where all the concepts in the resulting CIT were considered positive samples (labeled 1), and all the illegitimate phrases in the rejection list were considered negative samples (labeled 0). More detailed descriptions, including examples, are given in the study by Dehkordi et al [<xref ref-type="bibr" rid="ref27">27</xref>].</p>
        <p>In the second phase [<xref ref-type="bibr" rid="ref28">28</xref>], we first trained a feedforward neural network model using the training data obtained from the first phase. Next, we extracted more phrases from discharge notes and applied predefined rules to filter out structurally illegitimate ones. The remaining phrases were labeled using the neural network model. The accepted phrases were then added to the CIT, forming CIT<sub>ml</sub>. CIT<sub>ml</sub> significantly improved the evaluation metrics of highlighted discharge notes. More detailed descriptions, including examples, are given in the study by Dehkordi et al [<xref ref-type="bibr" rid="ref28">28</xref>]. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the diagram of constructing CIT<sub>ml</sub>.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Diagram of constructing CITml. Cardiology interface terminology (CIT) has versions with 2 indices. The first indicates the iteration number, and the second is binary, with 1 following concatenation and 2 following anchoring. CIT_V: updated version of the CIT; EHR: electronic health record; ICIT: initial version of the CIT; ML: machine learning; SNOMED CT: Systematized Nomenclature of Medicine–Clinical Terms.</p>
          </caption>
          <graphic xlink:href="medinform_v13i1e66476_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>In another study [<xref ref-type="bibr" rid="ref45">45</xref>], we created and assessed interface terminologies designed to extract pertinent details from the clinical records of patients with COVID-19, underscoring the generalizability of our methodologies.</p>
      </sec>
      <sec>
        <title>Data</title>
        <p>We randomly selected 15 discharge notes from the MIMIC-III database from 2 intensive care units related to cardiology patients: the coronary care unit and the cardiac surgery recovery unit. Only the “discharge summary” category was extracted from the discharge notes. We chose 15 notes to enable a careful manual comparison of 2 summaries per note, with and without highlighting, versus the original text.</p>
        <p>For each note, we created 2 HTML files: one containing the original discharge note without highlights and the other containing the highlighted discharge note, which is the output of the highlighting technique from our previous work.</p>
        <p>As described in the Methods section, our previous work involved curating an interface terminology leveraging machine learning techniques. This terminology encompasses fine-granular, detailed concepts found in discharge notes. In this study, we applied this curated interface terminology to highlight the 15 discharge notes, such that all concepts from the terminology that were present in these notes were highlighted. The highlighted information was marked using span tags with a blue background color with the color code of #ADD8E6. Moreover, we created plain text in HTML format to ensure both inputs have a uniform format to be provided to ChatGPT. The plain text HTML file was created by enclosing the entire text within a &lt;p&gt;&lt;/p&gt; tag.</p>
        <p>To provide insights into the 15 discharge notes we were summarizing, <xref ref-type="table" rid="table1">Table 1</xref> presents the text volume, overall themes, word frequency, and the repetition count of each word within a single document.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Text volume, overall themes, and word frequency of 15 discharge notes.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="390"/>
            <col width="90"/>
            <col width="80"/>
            <col width="110"/>
            <col width="110"/>
            <col width="80"/>
            <col width="70"/>
            <col width="70"/>
            <thead>
              <tr valign="bottom">
                <td>Theme</td>
                <td>TW<sup>a</sup></td>
                <td>SW<sup>b</sup></td>
                <td>TW_ESW<sup>c</sup></td>
                <td>DW_ESW<sup>d</sup></td>
                <td>N1<sup>e</sup></td>
                <td>N2<sup>f</sup></td>
                <td>N3<sup>g</sup></td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Management of shortness of breath and heart failure</td>
                <td>164</td>
                <td>71</td>
                <td>93</td>
                <td>83</td>
                <td>74</td>
                <td>8</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Aortic valve replacement</td>
                <td>366</td>
                <td>122</td>
                <td>244</td>
                <td>188</td>
                <td>152</td>
                <td>24</td>
                <td>12</td>
              </tr>
              <tr valign="top">
                <td>Bilateral renal artery stenosis</td>
                <td>160</td>
                <td>51</td>
                <td>109</td>
                <td>77</td>
                <td>58</td>
                <td>12</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>Three-vessel coronary artery bypass grafting</td>
                <td>266</td>
                <td>103</td>
                <td>163</td>
                <td>122</td>
                <td>96</td>
                <td>19</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>Aortic valve replacement and coronary artery bypass grafting</td>
                <td>377</td>
                <td>93</td>
                <td>284</td>
                <td>203</td>
                <td>169</td>
                <td>16</td>
                <td>18</td>
              </tr>
              <tr valign="top">
                <td>Peripheral vascular disease</td>
                <td>448</td>
                <td>153</td>
                <td>295</td>
                <td>206</td>
                <td>156</td>
                <td>31</td>
                <td>19</td>
              </tr>
              <tr valign="top">
                <td>Septic shock with respiratory failure</td>
                <td>386</td>
                <td>113</td>
                <td>273</td>
                <td>220</td>
                <td>187</td>
                <td>20</td>
                <td>13</td>
              </tr>
              <tr valign="top">
                <td>Coronary artery disease</td>
                <td>312</td>
                <td>101</td>
                <td>211</td>
                <td>144</td>
                <td>106</td>
                <td>27</td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>Diabetic ketoacidosis with a history of coronary artery disease</td>
                <td>180</td>
                <td>41</td>
                <td>139</td>
                <td>112</td>
                <td>97</td>
                <td>12</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Posterior mediastinal mass</td>
                <td>560</td>
                <td>199</td>
                <td>361</td>
                <td>255</td>
                <td>197</td>
                <td>36</td>
                <td>22</td>
              </tr>
              <tr valign="top">
                <td>Cardiac arrest</td>
                <td>520</td>
                <td>211</td>
                <td>309</td>
                <td>251</td>
                <td>205</td>
                <td>39</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>Hypercalcemia</td>
                <td>375</td>
                <td>133</td>
                <td>242</td>
                <td>198</td>
                <td>165</td>
                <td>26</td>
                <td>7</td>
              </tr>
              <tr valign="top">
                <td>Right coronary artery disease</td>
                <td>411</td>
                <td>160</td>
                <td>251</td>
                <td>168</td>
                <td>119</td>
                <td>33</td>
                <td>16</td>
              </tr>
              <tr valign="top">
                <td>Coronary artery bypass grafting</td>
                <td>155</td>
                <td>61</td>
                <td>94</td>
                <td>80</td>
                <td>70</td>
                <td>9</td>
                <td>1</td>
              </tr>
              <tr valign="top">
                <td>Aortic valve replacement</td>
                <td>128</td>
                <td>46</td>
                <td>82</td>
                <td>76</td>
                <td>70</td>
                <td>6</td>
                <td>0</td>
              </tr>
              <tr valign="top">
                <td>—<sup>h</sup></td>
                <td>320 (139)</td>
                <td>111 (53)</td>
                <td>209 (90)</td>
                <td>159 (64)</td>
                <td>128 (50)</td>
                <td>21 (11)</td>
                <td>10 (7)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>TW: total words.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>SW: stop words.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>TW_ESW: total words excluding stop words.</p>
            </fn>
            <fn id="table1fn4">
              <p><sup>d</sup>DW_ESW: distinct words excluding stop words.</p>
            </fn>
            <fn id="table1fn5">
              <p><sup>e</sup>N1: words repeated once, excluding stop words.</p>
            </fn>
            <fn id="table1fn6">
              <p><sup>f</sup>N2: words repeated twice, excluding stop words.</p>
            </fn>
            <fn id="table1fn7">
              <p><sup>g</sup>N3: words repeated more than 2 times, excluding stop words.</p>
            </fn>
            <fn id="table1fn8">
              <p><sup>h</sup>Not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Prompt Engineering</title>
        <p>Prompt engineering [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref46">46</xref>] is used to craft and refine input prompts to achieve the best possible results from LLMs, such as ChatGPT. However, it is a challenging task because even a minor change can significantly impact performance, leading to different results [<xref ref-type="bibr" rid="ref39">39</xref>].</p>
        <p>We proposed a protocol to incrementally generate effective prompts for both types of summaries from highlighted and unhighlighted notes.</p>
        <p>In prompt engineering, we need to use static input and simply refine the prompt to find an appropriate prompt, which leads us to the best possible result. Therefore, we chose a random note that was not used in the evaluations to develop and test the prompt engineering design. We needed 2 prompts because 2 summaries are required for each note, the summary from unhighlighted notes (U-summary) and the summary from highlighted notes (H-summary).</p>
        <p>We began the prompt engineering process with the unhighlighted text. To generate summaries, we initially used a simple prompt, “Give me a summary of this note.” We evaluated the completeness, correctness, word count, and structure of the generated summaries. If the summaries were too long, erroneous, or incomplete, we adjusted the prompt accordingly. For instance, the first prompt, “Give me a summary of this note,” resulted in a summary longer than the original text, so we revised it to “Give me a short summary of this note.” In another example, we determined that the output was not structured, so we added “structured” to the prompt, forming the prompt “Give me a short structured summary of this note,” so the summary would include headers and bullets for better orientation. This iterative process continued until the results were satisfactory to us after measuring the relevant metrics. Once we finalized the prompt for the unhighlighted text, we adapted it for the highlighted text by adding information about the format of the highlighted information.</p>
        <p>Finally, to ensure that the prompts were generalizable to other clinical notes, we applied the final prompts to 3 more randomly selected notes that were not used in the evaluation of this study. Because we obtained satisfactory summaries, after measuring the relevant metrics for both U-summaries and H-summaries, we concluded that the final prompts were suitable for our study.</p>
        <p>The final prompts were as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>The prompt for the unhighlighted note was “Give me a short structured summary of this EHR note”</p>
          </list-item>
          <list-item>
            <p>The prompt for the highlighted note was “Give me a short structured summary of this EHR note, focusing on the highlighted information [whose tags are “style=”‘background-color: #ADD8E6’]”</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Generating Summaries</title>
        <p>For each of the 15 randomly selected notes, we provided both the prompts to GPT-4o, along with the corresponding HTML files. To measure the evaluation metrics, we extracted all important information items from the original notes. Consequently, we manually inspected both summaries for each such item. For each summary, we counted the number of words, the number of important information items included by comparing them to the list of all important information items, and the number of possible erroneous statements generated by ChatGPT. We also counted the structural elements, misplaced information items, and false information items. We used this information to calculate the evaluation metrics.</p>
      </sec>
      <sec>
        <title>Evaluation Metrics</title>
        <sec>
          <title>Overview</title>
          <p>Assessing the quality of a summary is challenging, and currently, no automatic proxy exists for this task. Therefore, similar to related studies [<xref ref-type="bibr" rid="ref35">35</xref>], extensive manual effort is required to measure various aspects and compare which summary is more accurate. The evaluation was done by MKHD, a third-year PhD candidate in computer science with 3 years of research experience in processing EHR notes who has published studies [<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>] on this subject under the supervision of YP, who has more than 30 years of experience in medical informatics research. We used existing metrics and proposed new metrics for evaluating several aspects of the structured summaries generated. Our purpose was to test the following hypothesis: The H-summaries of discharge notes are likely to be more accurate than the U-summaries of those notes.</p>
          <p>To assess the plausibility of the hypothesis, we needed to consider several metrics. The following 4 aspects should be evaluated in a summary: completeness, correctness, succinctness, and structural integrity. First, the completeness and correctness of the summary must be assessed. We followed the study by Van Veen et al [<xref ref-type="bibr" rid="ref35">35</xref>] in using the metrics for completeness and correctness, which, respectively, measured the extent to which important information was covered and how accurate the covered information was. Second, the structure of the summary should be assessed by examining all the headers to identify proper and improper headers as well as bullets, which contribute to secondary structuring. In addition, because correct information might be placed under inappropriate headers within the text, we proposed a metric called the misplaced information to evaluate this aspect of each summary. Furthermore, the succinctness of the summary could be evaluated by the percentage reduction in size compared to the original text, which we referred to as the length reduction metric. This metric, although interesting, was not related to the quality of the summary.</p>
        </sec>
        <sec>
          <title>Completeness</title>
          <p>The completeness metric measures how well the summary has captured the important information from the original text. It is calculated as the percentage of the important information items included in the generated summary compared to all the important information items in the original text. This metric has also been used in other studies [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>] to evaluate summaries based on the original text. Completeness can be calculated using the following equation:</p>
          <graphic xlink:href="medinform_v13i1e66476_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          <p>Examples of important information items in <xref rid="figure2" ref-type="fig">Figure 2</xref>A are “known aortic stenosis,” “worsening DOE,” and “extubated without incident.”</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>(A) An original highlighted note with 128 words, (B) the summary from unhighlighted notes of the note with 91 words and 84% (31/37 items of information) completeness, (C) and the summary from highlighted notes of the same note with 111 words and 100% completeness. The pink highlight in (B) indicates misplaced information. The orange highlight in (B) indicates repetitive information, the first of which is redundant and misplaced. The yellow highlights in (C) indicate information items from the original text that do not appear in (B).</p>
            </caption>
            <graphic xlink:href="medinform_v13i1e66476_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>To calculate completeness, we first extracted and listed all information items from the original notes. We examined each summary, identifying how many of these items were present in the summary. We calculated the completeness of each note using equation 1. We calculated the average completeness scores for the 15 H-summaries and the 15 U-summaries separately.</p>
        </sec>
        <sec>
          <title>Correctness</title>
          <p>A summary is considered correct if it does not contain erroneous information. If it contains at least one instance of inaccurate information, it is then considered incorrect. The correctness of the summaries for a group of notes is the percentage of correct summaries. To evaluate correctness, we manually scanned the 15 U-summaries and the 15 H-summaries to identify all false information items based on the original text. This metric has also been used in similar studies [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>].</p>
        </sec>
        <sec>
          <title>Structural Elements Count</title>
          <sec>
            <title>Overview</title>
            <p>This metric quantifies the total number of structural elements, including the headers and bullet points, used to organize and structure the summaries. The structural elements count (SEC) is calculated by simply counting all the headers and bullet points in each summary.</p>
            <p>ChatGPT added headers and subheaders to both the H-summaries and U-summaries based on the given prompt. Upon manual review of the headers, we found that most of them accurately captured the information that followed, and we referred to these as “proper headers.” However, some headers were found to be redundant or misleading. Redundant headers are unnecessary and do not provide additional orientation for the reader, while misleading headers do not accurately represent the content that follows. Overall, having more proper headers and subheaders enhances the orientation of the note. In contrast, improper headers, whether redundant or misleading, may confuse the reader. Naturally, our goal was to maximize the number of proper headers to improve reader orientation and minimize the number of improper headers to avoid confusion and redundancy.</p>
          </sec>
          <sec>
            <title>Proper Headers</title>
            <p>Proper headers are those that correctly and effectively organize the text, accurately capturing the information that follows, leading to a clearer summary. The number of proper headers for each summary is determined by subtracting the improper headers from the total number of headers. For example, <xref rid="figure3" ref-type="fig">Figure 3</xref>A shows a portion of a summary where all the information is included in a single block of text, while <xref rid="figure3" ref-type="fig">Figure 3</xref>B shows the same portion of the summary with proper headers. In <xref rid="figure3" ref-type="fig">Figure 3</xref>B, information regarding status, medications, imaging, and physical examination is correctly categorized under separate sections with appropriate labels, thereby improving the orientation of the note.</p>
            <fig id="figure3" position="float">
              <label>Figure 3</label>
              <caption>
                <p>(A) A portion of a summary lacking proper headers and (B) the same portion of the summary with proper headers.</p>
              </caption>
              <graphic xlink:href="medinform_v13i1e66476_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
          </sec>
          <sec>
            <title>Improper Headers</title>
            <p><xref rid="figure4" ref-type="fig">Figure 4</xref> shows an example of improper headers. <xref rid="figure4" ref-type="fig">Figure 4</xref>A shows a portion of a U-summary, and <xref rid="figure4" ref-type="fig">Figure 4</xref>B is the corresponding H-summary. As shown, <xref rid="figure4" ref-type="fig">Figure 4</xref>A contains numerous redundant subtitles, which significantly interfere with the orientation because they may overwhelm and confuse the reader.</p>
            <fig id="figure4" position="float">
              <label>Figure 4</label>
              <caption>
                <p>(A) A portion of a summary having improper headers and (B) the same portion of the summary without improper headers.</p>
              </caption>
              <graphic xlink:href="medinform_v13i1e66476_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
            <p>To assess the improper headers metric, we manually reviewed all the summaries to identify the number of additional structural headers in each summary to compare the corresponding summaries with regard to their structural integrity.</p>
          </sec>
          <sec>
            <title>Misplaced Information</title>
            <p>Sometimes, a summary incorrectly categorizes information under the wrong section, resulting in misplaced information, confusing the reader. For example, in <xref rid="figure2" ref-type="fig">Figure 2</xref>B, “known aortic stenosis” is placed under the “patient information” category, whereas it should be under a header titled “medical history.” This structure is correctly applied in the highlighted summary shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>C. We counted the number of cases of misplaced information in both types of summaries to compare their structural information integrity.</p>
          </sec>
          <sec>
            <title>Length Reduction</title>
            <p>To evaluate the succinctness of the generated summaries, we used the length reduction metric, which is calculated using equation 2 with a Python (Python Software Foundation) program:</p>
            <graphic xlink:href="medinform_v13i1e66476_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            <p>We used the Fisher exact test [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>] twice; once to compare the completeness metric between the H-summaries and the U-summaries and the second time to compare the number of improper header metrics between the H-summaries and the U-summaries.</p>
          </sec>
        </sec>
      </sec>
      <sec>
        <title>Power Analysis</title>
        <p>In our methodology, power analysis [<xref ref-type="bibr" rid="ref54">54</xref>] was conducted using the Fisher exact test to determine the necessary sample size for detecting significant effects, particularly valuable when dealing with categorical data in scenarios of small sample sizes or sparse data. We started our analysis with the 2 metrics that were dominant for the accuracy of the discharge notes.</p>
        <sec>
          <title>Completeness Metric Analysis</title>
          <p>For assessing the completeness of summaries, we had 2 equal-sized groups, each comprising 15 paired discharge notes. In this evaluation, summaries generated by method 1 (H-summaries) were superior in 13 instances, while method 2 (U-summaries) led in 2 cases. Consequently, the probability of a favorable outcome in group 1 (H-summaries) was 86.7%, and in group 2 (U-summaries), it was 13.3%. Given the consistent performance advantage of H-summaries, a 1-sided Fisher exact test was appropriate, with a significance level (α) set at .025. The resulting power analysis yielded a high power of 0.98, indicating robust confidence in these findings.</p>
        </sec>
        <sec>
          <title>Improper Header Metric Analysis</title>
          <p>For the improper header metric, power analysis using the Fisher exact test was conducted, taking into account unequal sample sizes. The total count of structural elements (SECs), which include headers and bullet points, was 463 for H-summaries, of which 4 (0.9%) were improper, and 516 for U-summaries, of which 30 (5.8%) were improper This metric necessitated a 2-sided test with an α of .05, achieving a perfect power of 1, suggesting that the test reliably confirmed substantially more improper headers for method 2 when compared to method 1.</p>
        </sec>
        <sec>
          <title>Correctness Metric Analysis</title>
          <p>Regarding the correctness metric, all H-summaries contained 870 items of information, 2 (0.2%) of which were false, while the U-summaries contained 795 items, 3 (0.38) of which were false. This resulted in probabilities of 0.2% (2/870) for H-summaries and 0.3% (3/795) for U-summaries. Given the substantial total sample size exceeding 1000 items (1665 items of information in total), a Pearson chi-square test [<xref ref-type="bibr" rid="ref55">55</xref>] for unequal sample sizes was deemed suitable. However, the resulting power was low at 0.06. Further analysis revealed that to achieve a minimum power of 0.8 with a 2-sided test, the required sample sizes would need to increase to 41,146 items for H-summaries and 37,032 items for U-summaries, which is not practical for manual comparison.</p>
        </sec>
        <sec>
          <title>Misplaced Information Metric Analysis</title>
          <p>Finally, for the misplaced information metric, considering that there are 2 instances of misplaced information in 463 SECs for H-summaries and 8 in 516 SECs for U-summaries, the probabilities are 0.4% (2/463) and 1.6% (8/516), respectively. Conducting a 2-sided Fisher exact test power analysis with α of .05 and considering unequal sample sizes, we found that the resulting power was 0.41, which was low. To achieve a desired power of 0.8, recalculations suggested that sample sizes of 1272 for H-summaries (almost 3 times the current size) and 1145 for U-summaries (almost twice the current size) were needed.</p>
        </sec>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study used discharge notes from the MIMIC-III dataset [<xref ref-type="bibr" rid="ref56">56</xref>], a large, freely available database containing deidentified health-related data from &gt;40,000 patients who were admitted to the Beth Israel Deaconess Medical Center between 2001 and 2012. The database includes information, such as vital signs, laboratory test results, procedures, medications, etc. The MIMIC-III database was approved by the institutional review boards [<xref ref-type="bibr" rid="ref57">57</xref>] of the Beth Israel Deaconess Medical Center and the Massachusetts Institute of Technology. The requirement for individual patient consent was waived, as the dataset is fully deidentified and does not impact clinical care [<xref ref-type="bibr" rid="ref58">58</xref>]. Before inclusion in MIMIC-III, all data underwent a rigorous deidentification process in compliance with Health Insurance Portability and Accountability Act (HIPAA) [<xref ref-type="bibr" rid="ref59">59</xref>] standards [<xref ref-type="bibr" rid="ref58">58</xref>]. Structured data were deidentified by removing all 18 HIPAA-defined protected health information elements, such as names, addresses, phone numbers, and exact dates [<xref ref-type="bibr" rid="ref58">58</xref>]. To further ensure privacy, dates were randomly shifted while preserving relative intervals, and patients aged &gt;89 years had their ages masked. Free-text fields, including physician notes and diagnostic reports, were processed using an extensively evaluated deidentification system that used dictionary lookups and pattern-matching algorithms to remove protected health information [<xref ref-type="bibr" rid="ref58">58</xref>]. Because all data are deidentified and do not contain any identifiable patient information, the requirement for informed consent was waived by the overseeing institutional review boards [<xref ref-type="bibr" rid="ref58">58</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p><xref rid="figure2" ref-type="fig">Figure 2</xref>A shows an example of a discharge note (note 15) with 128 words, accompanied by its U-summary (<xref rid="figure2" ref-type="fig">Figure 2</xref>B) and H-summary (<xref rid="figure2" ref-type="fig">Figure 2</xref>C), containing 91 and 111 words, respectively. We noted that this discharge note was missing, describing the actual surgery that obviously happened during hospitalization of the patient. We assumed that this omission was based on the fact that the surgery was described in the surgical note section of the discharge note. We chose this note because it enabled us to demonstrate several efficiencies in 1 short note. As shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>C, 6 important information items from the original text, marked by yellow color, appeared in the H-summary but did not appear in the U-summary. In contrast, H-summary did not miss any items. Consequently, the calculated completeness for the H-summary was 100% (35/35), while the completeness of the U-summary was 84% (31/37 items of information), as shown also for note 15 in <xref ref-type="table" rid="table2">Table 2</xref>.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Values of 2 metrics for 15 notes.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="150"/>
            <col width="180"/>
            <col width="160"/>
            <col width="160"/>
            <col width="180"/>
            <col width="170"/>
            <thead>
              <tr valign="bottom">
                <td>Notes</td>
                <td>Word count of the original text<sup>a</sup></td>
                <td colspan="2">Length reduction</td>
                <td colspan="2">Completeness</td>
              </tr>
              <tr valign="bottom">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>H- summaries<sup>b</sup> (%)</td>
                <td>U-summaries<sup>c</sup> (%)</td>
                <td>H-summaries, n/N (%)</td>
                <td>U- summaries, n/N (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>164</td>
                <td>2</td>
                <td>–10</td>
                <td>35/35 (100)</td>
                <td>29/35 (83)</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>366</td>
                <td>23</td>
                <td>20</td>
                <td>31/32 (97)</td>
                <td>28/32 (88)</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>160</td>
                <td>1</td>
                <td>21</td>
                <td>40/40 (100)</td>
                <td>39/40 (98)</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>266</td>
                <td>23</td>
                <td>26</td>
                <td>41/42 (99)</td>
                <td>41/42 (99)</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>377</td>
                <td>5</td>
                <td>7</td>
                <td>24/26 (92)</td>
                <td>22/26 (85)</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>448</td>
                <td>39</td>
                <td>31</td>
                <td>32/33 (97)</td>
                <td>28/33 (85)</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>386</td>
                <td>25</td>
                <td>21</td>
                <td>43/46 (93)</td>
                <td>38/46 (83)</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>312</td>
                <td>24</td>
                <td>27</td>
                <td>21/22 (95)</td>
                <td>20/22 (91)</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>180</td>
                <td>–4</td>
                <td>–6</td>
                <td>22/23 (96)</td>
                <td>22/23 (96)</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>560</td>
                <td>33</td>
                <td>44</td>
                <td>33/35 (94)</td>
                <td>27/35 (77)</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>520</td>
                <td>36</td>
                <td>39</td>
                <td>24/27 (89)</td>
                <td>23/27 (85)</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>375</td>
                <td>38</td>
                <td>37</td>
                <td>38/42 (90)</td>
                <td>35/42 (83)</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>411</td>
                <td>40</td>
                <td>34</td>
                <td>42/43 (98)</td>
                <td>41/43 (95)</td>
              </tr>
              <tr valign="top">
                <td>14</td>
                <td>155</td>
                <td>33</td>
                <td>19</td>
                <td>29/30 (97)</td>
                <td>27/30 (90)</td>
              </tr>
              <tr valign="top">
                <td>15</td>
                <td>128</td>
                <td>13</td>
                <td>29</td>
                <td>37/37 (100)</td>
                <td>31/37 (84)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>Mean 320, SD 139 words.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>H-summary: summary from highlighted notes (length reduction: mean 22, SD 15; completeness: mean 96, SD 4).</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>U-summary: summary from unhighlighted notes (length reduction: mean 23, SD 15; completeness: mean 88, SD 6).</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Completeness</title>
        <p>As shown in <xref ref-type="table" rid="table2">Table 2</xref>, on average, the completeness of the U-summaries was 88% (SD 6%), while the completeness of the H-summaries was 96% (SD 4%), which was 8% higher. All percentages in <xref ref-type="table" rid="table2">Table 2</xref> are rounded to the nearest whole number. It is worth mentioning that for 13 notes, the completeness of the H-summary was higher than that of the U-summary, and for 2 notes, the completeness was equal. Using the Fisher exact test [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>], we compared the number of notes with higher completeness in the H-summary group (13 notes) versus the number of notes with higher or equal completeness in the U-summary group (2 notes). The Fisher exact test yielded <italic>P</italic>=.01, indicating a statistically significant difference.</p>
      </sec>
      <sec>
        <title>Length Reduction</title>
        <p>As shown in <xref ref-type="table" rid="table2">Table 2</xref>, the average word count of the original notes was 320 words, and the average length reduction of the H-summaries and U-summaries was 22% (SD 15%) and 23% (SD 15%) words, respectively. A negative number for length reduction in <xref ref-type="table" rid="table2">Table 2</xref> indicates that the summary generated had more words than the original text.</p>
      </sec>
      <sec>
        <title>Correctness</title>
        <p>In our analysis, we identified 3 instances of false information in U-summaries. In contrast, H-summaries contained only 2 false information items. However, this did not provide a statistically significant result, implying improvement. As an example of erroneous information, the original note contained the phrase “consistent either with aspiration pneumonia or increased apical interstitial edema,” whereas the U-summary incorrectly contained “consistent either with aspiration pneumonia and increased apical interstitial edema.” Replacing “or” with “and” changed the meaning of the phrase. Another example was a U-summary that mistakenly referred to Troponin T, a protein, as an enzyme.</p>
      </sec>
      <sec>
        <title>Structural Evaluation</title>
        <p>The total number of SECs, which were either headers or bullet points, for the U-summaries was 516, while for H-summaries, it was 463. In terms of improper headers, there were 30 instances in the U-summaries compared to only 4 in the H-summaries. <xref ref-type="table" rid="table3">Table 3</xref> presents the distribution of improper headers and misplaced information for the U-summaries and H-summaries for each of the 15 notes. For 11 (73%) of the notes, according to <xref ref-type="table" rid="table3">Table 3</xref>, the number of improper headers in the U-summaries was larger than the number for the H-summaries. For the other 4 (27%) notes, the numbers were equal. Hence, the number of improper headers in U-summaries was larger than those for H-summaries with statistical significance according to the Fisher exact test [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. We compared the number of notes with a higher number of improper headers in the U-summary group (11 notes) and the number of notes with a higher number of improper headers in the H-summary group (4 notes). The Fisher exact test yielded <italic>P</italic>=.03, indicating a statistically significant result.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Distribution of improper headers and misplaced information for the summaries from unhighlighted notes (U-summaries) and summaries from highlighted notes (H-summaries).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="140"/>
            <col width="220"/>
            <col width="230"/>
            <col width="210"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td>Notes</td>
                <td colspan="2">Improper headers</td>
                <td colspan="2">Misplaced information</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>U-summaries (n=30), n (%)</td>
                <td>H-summaries, (n=4), n (%)</td>
                <td>U-summaries, (n=8), n (%)</td>
                <td>H-summaries, (n=2), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>1 (50)</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>1 (12)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>1 (12)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>5 (17)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>4 (13)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>1 (3)</td>
                <td>1 (25)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>1 (12)</td>
                <td>1 (50)</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>1 (12)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>2 (7)</td>
                <td>1 (25)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>2 (7)</td>
                <td>2 (50)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>6 (20)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>14</td>
                <td>3 (10)</td>
                <td>0 (0)</td>
                <td>2 (25)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>15</td>
                <td>1 (3)</td>
                <td>0 (0)</td>
                <td>2 (25)</td>
                <td>0 (0)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>In other words, 5.8% (30/516) of the SECs in U-summaries were improper headers, whereas this percentage was only 0.1% (4/463) in the H-summaries. On the other hand, the number of proper SECs, after deducting the improper headers, was 94.2% (486/516) for the U-summaries and 99.1% (459/463) for the H-summaries. Hence, the structure of U-summaries was slightly more detailed than that of the H-summaries. However, the high percentage of improper headers rendered this advantage irrelevant because the structure was meaningfully less reliable. Moreover, we identified 8 instances of misplaced information in the U-summaries and only 2 in the H-summaries.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>In this study, we evaluated summaries generated by LLMs from 2 versions of discharge notes, H-summaries and U-summaries, to test the hypothesis that highlighting discharge notes improves the accuracy of the generated summaries. Our results show that feeding LLMs with H-summaries, combined with prompt engineering, results in higher-quality summaries in terms of correctness, completeness, and structural integrity compared to U-summaries.</p>
        <p>This study serves as the first step toward meeting the NIH challenge, which is facilitating the conversion of text in discharge notes into language that is comprehensible to a patient with a grade 6 reading level [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]. In a previous work [<xref ref-type="bibr" rid="ref26">26</xref>], we conducted a study to simplify discharge notes using 2 simplification approaches.</p>
        <p>In the first approach, we first summarized the discharge notes and then, in a second step, converted them into language understandable by a grade 6 reader. In the second approach, we directly generated, in a single step, a simplified summary understandable by a grade 6 reader from the discharge note. Our results showed that the first approach, simplifying notes in 2 steps, led to higher-quality and more understandable notes for grade 6 readers. Our interpretation is that, given discharge notes are inherently dense and complex, breaking the task into 2 steps reduces the cognitive load on the LLM, allowing it to generate more accurate and comprehensible results. Hence, cascading the findings of the previous study [<xref ref-type="bibr" rid="ref26">26</xref>] to the findings of this paper provides a pipeline responding to the NIH challenge of summarizing discharge notes into a language that is comprehensible to a patient with a grade 6 reading level with high accuracy. Because the findings of both studies satisfy statistical significance, their combined impact is reliable, although this study is based on a sample of only 15 discharge notes.</p>
        <p>Usually, summaries are shorter than the original text and thus enable the reader to review the content of a document faster. LLMs can actually generate summaries of various lengths according to the prompt provided to them. Because our final goal is the simplification of discharge notes, we are not necessarily interested in short summaries for the sake of brevity but in succinct summaries that capture all detailed information of a note in a simpler language.</p>
        <p>When evaluating the summary of a discharge note, if the summary lacks key information from the original note (ie, low completeness), it cannot be considered accurate. Similarly, if the summary contains erroneous information (lacking correctness), its accuracy is also compromised. Furthermore, if relevant information is placed under incorrect categories (referred to as “misplaced information”), the summary’s accuracy is further affected. Therefore, in this paper, when we state that H-summaries have higher accuracy than U-summaries, we mean that H-summaries exhibit greater completeness, correctness, and structural integrity compared to U-summaries.</p>
        <p>The scientific contribution of this research is the improvement in the accuracy of LLM summaries of discharge notes by feeding the LLMs with discharge notes in which the detailed information is highlighted. Automatic highlighting of discharge notes is provided by techniques from our previous research [<xref ref-type="bibr" rid="ref28">28</xref>]. A sample of a discharge note highlighted automatically by this technique is shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>A. Our hypothesis was that providing such highlighting would better direct the LLMs to capture the detailed information of the note and would better structure its summary. Our study has proven the plausibility of this hypothesis by the evaluation of several metrics.</p>
        <p>Although highlighting is used in this paper, it is not the primary focus of our study. However, we wish to clarify an observation regarding the highlighting in <xref rid="figure2" ref-type="fig">Figure 2</xref>A. This example is rich in information but with some stop words not highlighted. While there are other notes in our sample where several words and phrases are not highlighted, we note that “discharge notes” from MIMIC-III EHRs have contributed to this richness of information as they summarize the hospital course of the patient. Our highlighting method is based on mining phrases from clinical notes and determining which ones should be incorporated into the interface terminology. Only concepts present in the interface terminology are subsequently highlighted within the clinical note. Indeed, the density of the highlighting depends on the type of clinical notes and will be higher in discharge notes due to the richness of information they contain. Full details can be found in the studies by Dehkordi et al [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <p>Out of the 4 metrics we used to compare the H-summaries to the U-summaries, results from 2 metrics have shown statistical significance for better quality of the H-summaries. For the other 2 metrics, instances of erroneous information were low, but still, the results are better for H-summaries. The reason for having fewer improper headers in H-summaries compared to U-summaries may be attributed to the fact that by identifying the detailed information in the text, ChatGPT achieves better orientation in the note, allowing it to focus on the essential content and structure it more effectively. Despite the higher completeness in H-summaries compared to U-summaries, the inclusion of redundant information in U-summaries resulted in a similar length reduction for both H-summaries and U-summaries. For instance, the orange color in <xref rid="figure2" ref-type="fig">Figure 2</xref>B indicates that there is repetitive information in the U-summary, such as the phrase “one vessel coronary artery disease,” which appears twice.</p>
        <p>We define SEC as the total number of headers and bullets. In general, a larger number of proper headers and bullets is desirable, as such categorization of information enhances the clarity of the notes, making them more understandable for the reader. Because this study represents the first step toward simplifying the texts, having information categorized in different sections to increase clarity is preferable, unless the headers are improper. Our study demonstrated that the ratio of improper headers is substantially lower in H-summaries compared to U-summaries.</p>
        <p>Traditionally, for summarization, evaluation metrics such as recall-oriented understudy for gisting evaluation [<xref ref-type="bibr" rid="ref61">61</xref>] are used. We have not used these metrics since (1) our hypothesis is comparing highlighted versus nonhighlighted notes with a focus on completeness, correctness, and structural integrity; and (2) there is a lack of human-generated summaries used by these metrics for computing the respective scores. Similarly, simplification of text is measured using metrics, such as the Flesch-Kincaid Grade Level [<xref ref-type="bibr" rid="ref62">62</xref>], Simple Measure of Gobbledygook [<xref ref-type="bibr" rid="ref63">63</xref>], and Gunning-Fog Index [<xref ref-type="bibr" rid="ref64">64</xref>]. Because this study’s focus was not on the readability of the notes, these metrics were not applicable.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>In our study, we considered only the discharge note part of the clinical notes, which are the most relevant parts of the clinical notes for the patients. Due to their summarizing nature, discharge notes have aspects from all other parts of clinical notes. Thus, we have chosen to concentrate only on the discharge note, while we expect a similar result for a study that would summarize the complete clinical note.</p>
        <p>To minimize the amount of tedious manual review required for the evaluation of the various metrics, we have chosen a study of 15 notes, and this number was sufficient to yield the statistical significance for 2 dominant metrics of the 4 metrics for accuracy. For the other 2 metrics, the number of erroneous information items and misplaced information cases was infrequent, and a much larger sample would be needed to display statistical significance. Altogether, the results have proven our hypothesis that providing highlighted notes as input for ChatGPT will likely yield more accurate summaries.</p>
        <p>Moreover, the reliance on extensive manual review for evaluating the summaries may introduce subjectivity into the assessment process. Future studies could benefit from developing more automated methods to assess summary quality to reduce potential bias and labor intensity. In addition, although highlighting is used to enhance the input for LLMs, the technique itself may have limitations, such as the potential for overhighlighting or missing critical information not recognized by the underlying algorithm. This could affect the quality of the input and, consequently, the accuracy of the summaries produced. However, we are continuously working in parallel on different automated methods to improve the highlighting techniques and algorithms [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>]. Finally, this study’s results are based on the state of a specific LLM at a point in time. Continuous updates to LLMs could alter their performance characteristics, necessitating ongoing validation of the findings.</p>
      </sec>
      <sec>
        <title>Future Work</title>
        <p>In future work, we will use the LLM H-summaries as a starting point for further simplification of the notes to meet NIH’s readability target for patients with grade 6 reading skills using various techniques. Some patients may be interested in just the big picture without many details, while others, based on their health literacy, may require detailed information. As mentioned previously, in the future, we intend to explore the capabilities of LLMs alongside the vast wealth of curated knowledge embedded in biomedical ontologies and terminologies in catering to the varied requirements of patient populations by offering summaries and simplifications of clinical notes tailored to individual needs and comprehension levels. While this study demonstrated statistical significance in the completeness and improper headers metrics, the limited sample size of 15 discharge notes was insufficient for the other 2 metrics. In future studies, we plan to use a larger sample to test statistical significance for the correctness and misplaced information metrics as well.</p>
      </sec>
      <sec>
        <title>Ethical Concerns</title>
        <p>The integration of LLMs into clinical data summarization introduces several ethical considerations that warrant careful attention. A primary concern is the potential for these models to generate inaccurate or fabricated information, commonly referred to as hallucinations [<xref ref-type="bibr" rid="ref65">65</xref>], which could adversely affect patient care.</p>
        <p>Bias within training data presents another ethical challenge. If LLMs are trained on unrepresentative datasets, they may perpetuate existing health disparities by providing less accurate summaries for certain populations [<xref ref-type="bibr" rid="ref66">66</xref>]. Addressing these biases is critical to ensure equitable health care delivery.</p>
        <p>Moreover, the lack of transparency in how LLMs generate outputs [<xref ref-type="bibr" rid="ref67">67</xref>] can lead to challenges in clinical settings. Clinicians may find it difficult to trust or validate AI-generated summaries without a clear understanding of the underlying processes, potentially hindering the integration of these tools into health care practice.</p>
        <p>To mitigate these ethical concerns, it is imperative to implement robust validation processes, ensure compliance with privacy regulations, actively address biases in training data, and maintain transparency in AI operations.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this paper, we propose the use of highlighted discharge notes, emphasizing detailed information, to enhance the completeness and correctness of the summaries generated by LLMs. We have also developed and applied prompt engineering techniques to improve the structural integrity of these summaries, effectively addressing issues related to prompt sensitivity and reliability. Our study includes empirical validation with a random sample of 15 highlighted discharge notes from the MIMIC-III database, demonstrating that the input with the highlighted notes leads to more accurate LLM summaries of clinical notes. The final goal is to simplify discharge notes to be readable by a patient with grade 6 reading skills. To achieve this goal, we will use the summaries obtained in this research as input for the future simplification process.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">ATS</term>
          <def>
            <p>automatic text summarization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CIT</term>
          <def>
            <p>cardiology interface terminology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">H-summary</term>
          <def>
            <p>summary from highlighted notes</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">HIPAA</term>
          <def>
            <p>Health Insurance Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">ICIT</term>
          <def>
            <p>initial version of cardiology interface terminology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">NIH</term>
          <def>
            <p>National Institutes of Health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">SEC</term>
          <def>
            <p>structural elements count</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">U-summary</term>
          <def>
            <p>summary from unhighlighted notes</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This work was partially supported by a New Jersey Institute of Technology (seed grant 213443).</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>MKHD was responsible for conceptualization, methodology, software, validation, formal analysis, investigation, data curation, and writing the original draft. YP was responsible for conceptualization, methodology, validation, formal analysis, reviewing and editing the manuscript, supervision, and project administration. FPD was responsible for reviewing and editing the manuscript. ZH was responsible for reviewing and editing the manuscript. VKK was responsible for methodology. HL was responsible for reviewing and editing the manuscript. GE and AJE were responsible for supervision.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Seymour</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Frantsvog</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Graeber</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Electronic health records (EHR)</article-title>
          <source>Am J Health Sci</source>
          <year>2012</year>
          <month>07</month>
          <day>13</day>
          <volume>3</volume>
          <issue>3</issue>
          <fpage>201</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/267226700_Electronic_Health_Records_EHR"/>
          </comment>
          <pub-id pub-id-type="doi">10.19030/ajhs.v3i3.7139</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>Polepalli Ramesh</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Houston</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Brandt</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Improving patients' electronic health record comprehension with NoteAid</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2013</year>
          <volume>192</volume>
          <fpage>714</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">23920650</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Magid</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Katzovitz</surname>
              <given-names>LS</given-names>
            </name>
          </person-group>
          <article-title>21 Century Cures Act, an information technology-led organizational initiative</article-title>
          <source>HSS J</source>
          <year>2022</year>
          <month>03</month>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>42</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/15563316211041613?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/15563316211041613</pub-id>
          <pub-id pub-id-type="medline">35082558</pub-id>
          <pub-id pub-id-type="pii">10.1177_15563316211041613</pub-id>
          <pub-id pub-id-type="pmcid">PMC8753555</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>McCray</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Loane</surname>
              <given-names>RF</given-names>
            </name>
            <name name-style="western">
              <surname>Browne</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Bangalore</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>Terminology issues in user access to web-based medical information</article-title>
          <source>Proc AMIA Symp</source>
          <year>1999</year>
          <fpage>107</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/10566330"/>
          </comment>
          <pub-id pub-id-type="medline">10566330</pub-id>
          <pub-id pub-id-type="pii">D005626</pub-id>
          <pub-id pub-id-type="pmcid">PMC2232498</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weiss</surname>
              <given-names>BD</given-names>
            </name>
          </person-group>
          <article-title>Health literacy: a manual for clinicians</article-title>
          <source>American Medical Association</source>
          <access-date>2025-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://lib.ncfh.org/pdfs/6617.pdf">http://lib.ncfh.org/pdfs/6617.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>Health education materials assessment tool</article-title>
          <source>National Institutes of Health National Library of Medicine</source>
          <access-date>2025-07-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medlineplus.gov/pdf/health-education-materials-assessment-tool.pdf">https://medlineplus.gov/pdf/health-education-materials-assessment-tool.pdf</ext-link>
          </comment>
        </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>Grever</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Schepartz</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Chabner</surname>
              <given-names>BA</given-names>
            </name>
          </person-group>
          <article-title>The National Cancer Institute: cancer drug discovery and development program</article-title>
          <source>Semin Oncol</source>
          <year>1992</year>
          <month>12</month>
          <volume>19</volume>
          <issue>6</issue>
          <fpage>622</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="medline">1462164</pub-id>
          <pub-id pub-id-type="pii">0093-7754(92)90032-V</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>Davis</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Wolf</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <article-title>Health literacy: implications for family medicine</article-title>
          <source>Fam Med</source>
          <year>2004</year>
          <month>09</month>
          <volume>36</volume>
          <issue>8</issue>
          <fpage>595</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">15343422</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Perni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rooney</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Horowitz</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>Golden</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>McCall</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Einstein</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Jagsi</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Assessment of use, specificity, and readability of written clinical informed consent forms for patients with cancer undergoing radiotherapy</article-title>
          <source>JAMA Oncol</source>
          <year>2019</year>
          <month>08</month>
          <day>01</day>
          <volume>5</volume>
          <issue>8</issue>
          <fpage>e190260</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31046122"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamaoncol.2019.0260</pub-id>
          <pub-id pub-id-type="medline">31046122</pub-id>
          <pub-id pub-id-type="pii">2732507</pub-id>
          <pub-id pub-id-type="pmcid">PMC6499131</pub-id>
        </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>Zhao</surname>
              <given-names>WX</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Hou</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Min</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ren</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Nie</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>A survey of large language models</article-title>
          <source>ArXiv. Preprint posted online on March 31, 2023</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2303.18223"/>
          </comment>
        </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>Chang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yi</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>A survey on evaluation of large language models</article-title>
          <source>ACM Trans Intell Syst Technol</source>
          <year>2024</year>
          <month>03</month>
          <day>29</day>
          <volume>15</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1145/3641289</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thirunavukarasu</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Elangovan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gutierrez</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>TF</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Large language models in medicine</article-title>
          <source>Nat Med</source>
          <year>2023</year>
          <month>08</month>
          <day>17</day>
          <volume>29</volume>
          <issue>8</issue>
          <fpage>1930</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-023-02448-8</pub-id>
          <pub-id pub-id-type="medline">37460753</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-023-02448-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jahan</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Laskar</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>JX</given-names>
            </name>
          </person-group>
          <article-title>A comprehensive evaluation of large language models on benchmark biomedical text processing tasks</article-title>
          <source>Comput Biol Med</source>
          <year>2024</year>
          <month>03</month>
          <volume>171</volume>
          <fpage>108189</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0010-4825(24)00273-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2024.108189</pub-id>
          <pub-id pub-id-type="medline">38447502</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(24)00273-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Madzime</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Nyirenda</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Enhanced electronic health records text summarization using large language models</article-title>
          <source>ArXiv. Preprint posted online on October 12, 2024</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2410.09628"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chintagunta</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Katariya</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Amatriain</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Kannan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Medically aware GPT-3 as a data generator for medical dialogue summarization</article-title>
          <source>Proceedings of Machine Learning Research 2021</source>
          <year>2021</year>
          <conf-name>PMLR 2021</conf-name>
          <conf-date>December 13, 2021</conf-date>
          <conf-loc>Online</conf-loc>
          <pub-id pub-id-type="doi">10.18653/v1/2021.nlpmc-1.9</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>Jeblick</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Schachtner</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Dexl</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mittermeier</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stüber</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Topalis</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wesp</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sabel</surname>
              <given-names>BO</given-names>
            </name>
            <name name-style="western">
              <surname>Ricke</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ingrisch</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT makes medicine easy to swallow: an exploratory case study on simplified radiology reports</article-title>
          <source>Eur Radiol</source>
          <year>2024</year>
          <month>05</month>
          <day>05</day>
          <volume>34</volume>
          <issue>5</issue>
          <fpage>2817</fpage>
          <lpage>25</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37794249"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s00330-023-10213-1</pub-id>
          <pub-id pub-id-type="medline">37794249</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00330-023-10213-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC11126432</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dave</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Athaluri</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT in medicine: an overview of its applications, advantages, limitations, future prospects, and ethical considerations</article-title>
          <source>Front Artif Intell</source>
          <year>2023</year>
          <month>5</month>
          <day>4</day>
          <volume>6</volume>
          <fpage>1169595</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37215063"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/frai.2023.1169595</pub-id>
          <pub-id pub-id-type="medline">37215063</pub-id>
          <pub-id pub-id-type="pmcid">PMC10192861</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>Guo</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nie</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yue</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>How close is ChatGPT to human experts? Comparison corpus, evaluation, and detection</article-title>
          <source>ArXiv. Preprint posted online on January 18, 2023</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2301.07597"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marvin</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hellen</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jjingo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nakatumba-Nabende</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Prompt engineering in large language models</article-title>
          <source>Proceedings of the Data Intelligence and Cognitive Informatics</source>
          <year>2023</year>
          <conf-name>ICDICI 2023</conf-name>
          <conf-date>June 27-28, 2023</conf-date>
          <conf-loc>Tirunelveli, India</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-981-99-7962-2_30</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>Giray</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Prompt engineering with ChatGPT: a guide for academic writers</article-title>
          <source>Ann Biomed Eng</source>
          <year>2023</year>
          <month>12</month>
          <day>07</day>
          <volume>51</volume>
          <issue>12</issue>
          <fpage>2629</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1007/s10439-023-03272-4</pub-id>
          <pub-id pub-id-type="medline">37284994</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10439-023-03272-4</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>Patil</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Heston</surname>
              <given-names>TF</given-names>
            </name>
            <name name-style="western">
              <surname>Bhuse</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Prompt engineering in healthcare</article-title>
          <source>Electronics</source>
          <year>2024</year>
          <month>07</month>
          <day>26</day>
          <volume>13</volume>
          <issue>15</issue>
          <fpage>2961</fpage>
          <pub-id pub-id-type="doi">10.3390/electronics13152961</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>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Instruction tuning for large language models: a survey</article-title>
          <source>ArXiv. Preprint posted online on August 21, 2023</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2308.10792"/>
          </comment>
        </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>Hadi</surname>
              <given-names>MU</given-names>
            </name>
            <name name-style="western">
              <surname>Tashi</surname>
              <given-names>QA</given-names>
            </name>
            <name name-style="western">
              <surname>Qureshi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Muneer</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Irfan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zafar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shaikh</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Akhtar</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Hassan</surname>
              <given-names>SZ</given-names>
            </name>
            <name name-style="western">
              <surname>Shoman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mirjalili</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A survey on large language models: applications, challenges, limitations, and practical usage</article-title>
          <source>TechRxiv. Preprint posted online on July 10, 2023</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.techrxiv.org/doi/full/10.36227/techrxiv.23589741.v1"/>
          </comment>
          <pub-id pub-id-type="doi">10.36227/techrxiv.23589741.v1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karabacak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Margetis</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Embracing large language models for medical applications: opportunities and challenges</article-title>
          <source>Cureus</source>
          <year>2023</year>
          <month>05</month>
          <volume>15</volume>
          <issue>5</issue>
          <fpage>e39305</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37378099"/>
          </comment>
          <pub-id pub-id-type="doi">10.7759/cureus.39305</pub-id>
          <pub-id pub-id-type="medline">37378099</pub-id>
          <pub-id pub-id-type="pmcid">PMC10292051</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Syed-Abdul</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>CC</given-names>
            </name>
          </person-group>
          <article-title>Recognition and evaluation of clinical section headings in clinical documents using token-based formulation with conditional random fields</article-title>
          <source>Biomed Res Int</source>
          <year>2015</year>
          <volume>2015</volume>
          <fpage>873012</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2015/873012"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2015/873012</pub-id>
          <pub-id pub-id-type="medline">26380302</pub-id>
          <pub-id pub-id-type="pmcid">PMC4563061</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dehkordi</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Perl</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Deek</surname>
              <given-names>FP</given-names>
            </name>
            <name name-style="western">
              <surname>Einstein</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Elhanan</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Enhancing patient comprehension: an effective sequential prompting approach to simplifying EHRs using LLMs</article-title>
          <source>Proceedings of the IEEE International Conference on Bioinformatics and Biomedicine</source>
          <year>2024</year>
          <conf-name>BIBM 2024</conf-name>
          <conf-date>December 3-6, 2024</conf-date>
          <conf-loc>Lisbon, Portugal</conf-loc>
          <pub-id pub-id-type="doi">10.1109/bibm62325.2024.10822313</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dehkordi</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Perl</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Geller</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Einstein</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Elhanan</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Using annotation for computerized support for fast skimming of cardiology electronic health record notes</article-title>
          <source>Proceedings of the IEEE International Conference on Bioinformatics and Biomedicine</source>
          <year>2023</year>
          <conf-name>BIBM 2023</conf-name>
          <conf-date>December 5-8, 2023</conf-date>
          <conf-loc>Istanbul, Turkiye</conf-loc>
          <pub-id pub-id-type="doi">10.1109/bibm58861.2023.10385289</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dehkordi</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Kollapally</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Perl</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Geller</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Deek</surname>
              <given-names>FP</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Keloth</surname>
              <given-names>VK</given-names>
            </name>
            <name name-style="western">
              <surname>Elhanan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Einstein</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Skimming of electronic health records highlighted by an interface terminology curated with machine learning mining</article-title>
          <source>Proceedings of the 17th International Joint Conference on Biomedical Engineering Systems and Technologies</source>
          <year>2024</year>
          <conf-name>BIOSTEC 2024</conf-name>
          <conf-date>February 21-23, 2024</conf-date>
          <conf-loc>Rome, Italy</conf-loc>
          <pub-id pub-id-type="doi">10.5220/0012391600003657</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bian</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fiszman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Weir</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Jonnalagadda</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mostafa</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Del Fiol</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Text summarization in the biomedical domain: a systematic review of recent research</article-title>
          <source>J Biomed Inform</source>
          <year>2014</year>
          <month>12</month>
          <volume>52</volume>
          <fpage>457</fpage>
          <lpage>67</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(14)00147-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2014.06.009</pub-id>
          <pub-id pub-id-type="medline">25016293</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(14)00147-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC4261035</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gholamrezazadeh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Salehi</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Gholamzadeh</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A comprehensive survey on text summarization systems</article-title>
          <source>Proceedings of the 2nd International Conference on Computer Science and its Applications</source>
          <year>2009</year>
          <conf-name>CSA 2009</conf-name>
          <conf-date>December 10-12, 2009</conf-date>
          <conf-loc>Jeju, Korea (South)</conf-loc>
          <pub-id pub-id-type="doi">10.1109/csa.2009.5404226</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Meng</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A comprehensive survey on process-oriented automatic text summarization with exploration of LLM-based methods</article-title>
          <source>ArXiv. Preprint posted online on March 5, 2024</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2403.02901"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El-Kassas</surname>
              <given-names>WS</given-names>
            </name>
            <name name-style="western">
              <surname>Salama</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Rafea</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Mohamed</surname>
              <given-names>HK</given-names>
            </name>
          </person-group>
          <article-title>Automatic text summarization: a comprehensive survey</article-title>
          <source>Expert Syst Appl</source>
          <year>2021</year>
          <month>03</month>
          <volume>165</volume>
          <fpage>113679</fpage>
          <pub-id pub-id-type="doi">10.1016/j.eswa.2020.113679</pub-id>
        </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>Gambhir</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Recent automatic text summarization techniques: a survey</article-title>
          <source>Artif Intell Rev</source>
          <year>2016</year>
          <month>3</month>
          <day>29</day>
          <volume>47</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1007/s10462-016-9475-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fattah</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Ren</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Automatic text summarization</article-title>
          <source>Int J Electr Comput Eng</source>
          <year>2008</year>
          <volume>3</volume>
          <fpage>25</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://citeseerx.ist.psu.edu/document?repid=rep1&amp;type=pdf&amp;doi=dd7ef1aecb0c5f6a41c317bae62099e3cec2f0ea"/>
          </comment>
        </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>Van Veen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Van Uden</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Blankemeier</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Delbrouck</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Aali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bluethgen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Pareek</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Polacin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reis</surname>
              <given-names>EP</given-names>
            </name>
            <name name-style="western">
              <surname>Seehofnerová</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rohatgi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Hosamani</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Ahuja</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Langlotz</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Hom</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gatidis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pauly</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chaudhari</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Adapted large language models can outperform medical experts in clinical text summarization</article-title>
          <source>Nat Med</source>
          <year>2024</year>
          <month>04</month>
          <day>27</day>
          <volume>30</volume>
          <issue>4</issue>
          <fpage>1134</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-024-02855-5</pub-id>
          <pub-id pub-id-type="medline">38413730</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-024-02855-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC11479659</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>Dong</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Xia</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sui</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>A survey on in-context learning</article-title>
          <source>ArXiv. Preprint posted online on December 31, 2022</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2301.00234"/>
          </comment>
          <pub-id pub-id-type="doi">10.18653/v1/2024.emnlp-main.64</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kanwal</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rizzo</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Attention-based clinical note summarization</article-title>
          <source>Proceedings of the 37th ACM/SIGAPP Symposium on Applied Computing</source>
          <year>2022</year>
          <conf-name>SAC '22</conf-name>
          <conf-date>April 25-29, 2022</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3477314.3507256</pub-id>
        </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>Alsentzer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Extractive summarization of EHR discharge notes</article-title>
          <source>ArXiv. Preprint posted online on October 26, 2018</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1810.12085"/>
          </comment>
        </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>Ma</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>An iterative optimizing framework for radiology report summarization with ChatGPT</article-title>
          <source>IEEE Trans Artif Intell</source>
          <year>2024</year>
          <month>8</month>
          <volume>5</volume>
          <issue>8</issue>
          <fpage>4163</fpage>
          <lpage>75</lpage>
          <pub-id pub-id-type="doi">10.1109/tai.2024.3364586</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>Hake</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Crowley</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Coy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shanks</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Eoff</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kirmer-Voss</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Dhanda</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Parente</surname>
              <given-names>DJ</given-names>
            </name>
          </person-group>
          <article-title>Quality, accuracy, and bias in ChatGPT-based summarization of medical abstracts</article-title>
          <source>Ann Fam Med</source>
          <year>2024</year>
          <month>03</month>
          <day>25</day>
          <volume>22</volume>
          <issue>2</issue>
          <fpage>113</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.annfammed.org/cgi/pmidlookup?view=long&amp;pmid=38527823"/>
          </comment>
          <pub-id pub-id-type="doi">10.1370/afm.3075</pub-id>
          <pub-id pub-id-type="medline">38527823</pub-id>
          <pub-id pub-id-type="pii">22/2/113</pub-id>
          <pub-id pub-id-type="pmcid">PMC11237196</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <article-title>SNOMED International homepage</article-title>
          <source>SNOMED International</source>
          <access-date>2025-06-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.snomed.org/">https://www.snomed.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Donnelly</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>SNOMED-CT: the advanced terminology and coding system for eHealth</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2006</year>
          <volume>121</volume>
          <fpage>279</fpage>
          <lpage>90</lpage>
          <pub-id pub-id-type="medline">17095826</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cimino</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Clayton</surname>
              <given-names>PD</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>SB</given-names>
            </name>
          </person-group>
          <article-title>Knowledge-based approaches to the maintenance of a large controlled medical terminology</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>1994</year>
          <month>01</month>
          <day>01</day>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>35</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/7719786"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.1994.95236135</pub-id>
          <pub-id pub-id-type="medline">7719786</pub-id>
          <pub-id pub-id-type="pmcid">PMC116183</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cimino</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>Desiderata for controlled medical vocabularies in the twenty-first century</article-title>
          <source>Methods Inf Med</source>
          <year>2018</year>
          <month>02</month>
          <day>15</day>
          <volume>37</volume>
          <issue>04/05</issue>
          <fpage>394</fpage>
          <lpage>403</lpage>
          <pub-id pub-id-type="doi">10.1055/s-0038-1634558</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Keloth</surname>
              <given-names>VK</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Elhanan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Einstein</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Geller</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Mining concepts for a COVID interface terminology for annotation of EHRs</article-title>
          <source>Proceedings of the 2020 IEEE International Conference on Big Data</source>
          <year>2020</year>
          <conf-name>BigData 2020</conf-name>
          <conf-date>December 10-13, 2020</conf-date>
          <conf-loc>Atlanta, GA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/bigdata50022.2020.9377981</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yue</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Pan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Ge</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Prompt engineering for healthcare: methodologies and applications</article-title>
          <source>ArXiv. Preprint posted online on April 28, 2023</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2304.14670"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kollapally</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Dehkordi</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Perl</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Geller</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Deek</surname>
              <given-names>FP</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Keloth</surname>
              <given-names>VK</given-names>
            </name>
            <name name-style="western">
              <surname>Elhanan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Einstein</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Using clinical entity recognition for curating an interface terminology to aid fast skimming of EHRs</article-title>
          <source>Proceedings of the 2024 IEEE International Conference on Bioinformatics and Biomedicine</source>
          <year>2024</year>
          <conf-name>BIBM 2024</conf-name>
          <conf-date>December 03-06, 2024</conf-date>
          <conf-loc>Lisbon, Portugal</conf-loc>
          <pub-id pub-id-type="doi">10.1109/bibm62325.2024.10822845</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Perl</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Dehkordi</surname>
              <given-names>MK</given-names>
            </name>
          </person-group>
          <article-title>CFC annotator: a cluster-focused combination algorithm for annotating electronic health records by referencing interface terminology</article-title>
          <source>Proceedings of the 18th International Joint Conference on Biomedical Engineering Systems and Technologies</source>
          <year>2025</year>
          <conf-name>BIOSTEC 2025</conf-name>
          <conf-date>February 19-21, 2025</conf-date>
          <conf-loc>Porto, Portugal</conf-loc>
          <pub-id pub-id-type="doi">10.5220/0013244500003911</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Samarinas</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Krubner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Salemi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zamani</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Beyond factual accuracy: evaluating coverage of diverse factual information in long-form text generation</article-title>
          <source>ArXiv. Preprint posted online on January 7, 2025</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2501.03545"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Celikyilmaz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of text generation: a survey</article-title>
          <source>ArXiv. Preprint posted online on June 26, 2020</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2006.14799"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Merck</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Tsai</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Manning</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Langlotz</surname>
              <given-names>CP</given-names>
            </name>
          </person-group>
          <article-title>Optimizing the factual correctness of a summary: a study of summarizing radiology reports</article-title>
          <source>ArXiv. Preprint posted online on November 6, 2019</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1911.02541"/>
          </comment>
          <pub-id pub-id-type="doi">10.18653/v1/2020.acl-main.458</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Upton</surname>
              <given-names>GJ</given-names>
            </name>
          </person-group>
          <article-title>Fisher's exact test</article-title>
          <source>J R Stat Soc Ser A Stat Soc</source>
          <year>1992</year>
          <volume>155</volume>
          <issue>3</issue>
          <fpage>395</fpage>
          <lpage>402</lpage>
          <pub-id pub-id-type="doi">10.2307/2982890</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>Easy Fisher Exact Test calculator</article-title>
          <source>Social Science Statistics</source>
          <access-date>2025-06-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.socscistatistics.com/tests/fisher/default2.aspx">https://www.socscistatistics.com/tests/fisher/default2.aspx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Statistical power analysis</article-title>
          <source>Curr Dir Psychol Sci</source>
          <year>1992</year>
          <month>06</month>
          <day>01</day>
          <volume>1</volume>
          <issue>3</issue>
          <fpage>98</fpage>
          <lpage>101</lpage>
          <pub-id pub-id-type="doi">10.1111/1467-8721.ep10768783</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Plackett</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Karl Pearson and the Chi-Squared Test</article-title>
          <source>Int Stat Rev</source>
          <year>1983</year>
          <volume>51</volume>
          <issue>1</issue>
          <fpage>59</fpage>
          <lpage>72</lpage>
          <pub-id pub-id-type="doi">10.2307/1402731</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Pollard</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>LW</given-names>
            </name>
            <name name-style="western">
              <surname>Lehman</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ghassemi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Moody</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Szolovits</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Mark</surname>
              <given-names>RG</given-names>
            </name>
          </person-group>
          <article-title>MIMIC-III, a freely accessible critical care database</article-title>
          <source>Sci Data</source>
          <year>2016</year>
          <month>05</month>
          <day>24</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>160035</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/sdata.2016.35"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/sdata.2016.35</pub-id>
          <pub-id pub-id-type="medline">27219127</pub-id>
          <pub-id pub-id-type="pii">sdata201635</pub-id>
          <pub-id pub-id-type="pmcid">PMC4878278</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grady</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Institutional review boards: purpose and challenges</article-title>
          <source>Chest</source>
          <year>2015</year>
          <month>11</month>
          <volume>148</volume>
          <issue>5</issue>
          <fpage>1148</fpage>
          <lpage>55</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26042632"/>
          </comment>
          <pub-id pub-id-type="doi">10.1378/chest.15-0706</pub-id>
          <pub-id pub-id-type="medline">26042632</pub-id>
          <pub-id pub-id-type="pii">S0012-3692(15)50225-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC4631034</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pollard</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Mark</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>MIMIC-III clinical database</article-title>
          <source>PhysioNet</source>
          <year>2016</year>
          <month>9</month>
          <day>4</day>
          <access-date>2025-06-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://physionet.org/content/mimiciii/1.4/">https://physionet.org/content/mimiciii/1.4/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Frye</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Review of HIPAA, part 1: history, protected health information, and privacy and security rules</article-title>
          <source>J Nucl Med Technol</source>
          <year>2019</year>
          <month>12</month>
          <day>10</day>
          <volume>47</volume>
          <issue>4</issue>
          <fpage>269</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://tech.snmjournals.org/cgi/pmidlookup?view=long&amp;pmid=31182664"/>
          </comment>
          <pub-id pub-id-type="doi">10.2967/jnmt.119.227819</pub-id>
          <pub-id pub-id-type="medline">31182664</pub-id>
          <pub-id pub-id-type="pii">jnmt.119.227819</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weiss</surname>
              <given-names>BD</given-names>
            </name>
            <name name-style="western">
              <surname>Blanchard</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>McGee</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Hart</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Warren</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Burgoon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>KJ</given-names>
            </name>
          </person-group>
          <article-title>Illiteracy among Medicaid recipients and its relationship to health care costs</article-title>
          <source>J Health Care Poor Underserved</source>
          <year>1994</year>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>99</fpage>
          <lpage>111</lpage>
          <pub-id pub-id-type="doi">10.1353/hpu.2010.0272</pub-id>
          <pub-id pub-id-type="medline">8043732</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>CY</given-names>
            </name>
          </person-group>
          <article-title>ROUGE: a package for automatic evaluation of summaries</article-title>
          <source>Proceedings of the Workshop on Text Summarization Branches Out</source>
          <year>2004</year>
          <conf-name>ACL-04</conf-name>
          <conf-date>July 25-26, 2004</conf-date>
          <conf-loc>Barcelona, Spain</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="web">
          <article-title>Flesch-Kincaid readability test</article-title>
          <source>Rockstar-English.com</source>
          <access-date>2025-06-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://rockstar-english.com/lessons/advanced/12-Flesch_Kincaid_Readability_Test.pdf">https://rockstar-english.com/lessons/advanced/12-Flesch_Kincaid_Readability_Test.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bernstein</surname>
              <given-names>JD</given-names>
            </name>
          </person-group>
          <article-title>Gobbledygook: the proliferation of jargon in English language teaching</article-title>
          <source>TESOL J</source>
          <year>2021</year>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>e541</fpage>
          <pub-id pub-id-type="doi">10.1002/tesj.541</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rodríguez Timaná</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Saavedra Lozano</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Castillo García</surname>
              <given-names>JF</given-names>
            </name>
          </person-group>
          <article-title>Software to determine the readability of written documents by implementing a variation of the gunning fog index using the Google linguistic corpus</article-title>
          <source>Proceedings of the First International Conference on Applied Technologies</source>
          <year>2019</year>
          <conf-name>ICAT 2019</conf-name>
          <conf-date>December 3-5, 2019</conf-date>
          <conf-loc>Quito, Ecuador</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-3-030-42517-3_31</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Perković</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Drobnjak</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Botički</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Hallucinations in LLMs: understanding and addressing challenges</article-title>
          <source>Proceedings of the 47th MIPRO ICT and Electronics Convention</source>
          <year>2024</year>
          <conf-name>MIPRO 2024</conf-name>
          <conf-date>May 20-24, 2024</conf-date>
          <conf-loc>Opatija, Croatia</conf-loc>
          <pub-id pub-id-type="doi">10.1109/mipro60963.2024.10569238</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ranjan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A comprehensive survey of bias in LLMs: current landscape and future directions</article-title>
          <source>ArXiv. Preprint posted online on September 24, 2024</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2409.16430"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>QV</given-names>
            </name>
            <name name-style="western">
              <surname>Vaughan</surname>
              <given-names>JW</given-names>
            </name>
          </person-group>
          <article-title>AI transparency in the age of LLMs: a human-centered research roadmap</article-title>
          <source>ArXiv. Preprint posted online on June 2, 2023</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2306.01941"/>
          </comment>
          <pub-id pub-id-type="doi">10.1162/99608f92.8036d03b</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
