<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v13i1e78502</article-id>
      <article-id pub-id-type="pmid">41418294</article-id>
      <article-id pub-id-type="doi">10.2196/78502</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>Copy Tools in the Electronic Health Record: Perceptions, Implications, and Future Directions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Coristine</surname>
            <given-names>Andrew</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Adegoke</surname>
            <given-names>Kola</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Rungvivatjarus</surname>
            <given-names>Tiranun</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Tiase</surname>
            <given-names>Victoria</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Corby</surname>
            <given-names>Sky</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Division of Pulmonary, Allergy, and Critical Care Medicine</institution>
            <institution>Department of Medicine</institution>
            <institution>Oregon Health &#38; Science University</institution>
            <addr-line>3181 Southwest Sam Jackson Park Road</addr-line>
            <addr-line>Portland, OR, 97239</addr-line>
            <country>United States</country>
            <phone>1 5034948311</phone>
            <email>corby@ohsu.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6493-0774</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Ash</surname>
            <given-names>Joan S</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0017-3035</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Jungbauer</surname>
            <given-names>Rebecca M</given-names>
          </name>
          <degrees>DrPH</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2504-7054</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Scholl</surname>
            <given-names>Gretchen</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8063-6716</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Florig</surname>
            <given-names>Sarah</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6906-2689</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Mohan</surname>
            <given-names>Vishnu</given-names>
          </name>
          <degrees>MD, MBI</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3873-4969</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Gold</surname>
            <given-names>Jeffrey A</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6683-9907</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Division of Pulmonary, Allergy, and Critical Care Medicine</institution>
        <institution>Department of Medicine</institution>
        <institution>Oregon Health &#38; Science University</institution>
        <addr-line>Portland, OR</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Division of Informatics, Clinical Epidemiology, and Translational Data Science</institution>
        <institution>Department of Medicine</institution>
        <institution>Oregon Health &#38; Science University</institution>
        <addr-line>Portland, OR</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Division of Undergraduate Medical Education</institution>
        <institution>Department of Medicine</institution>
        <institution>Oregon Health &#38; Science University</institution>
        <addr-line>Portland, OR</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>College of Medicine</institution>
        <institution>Nebraska Medical Center</institution>
        <addr-line>Omaha, NE</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Division of General Internal Medicine and Geriatrics</institution>
        <institution>Department of Medicine</institution>
        <institution>Oregon Health &#38; Science University</institution>
        <addr-line>Portland, OR</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Sky Corby <email>corby@ohsu.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>19</day>
        <month>12</month>
        <year>2025</year>
      </pub-date>
      <volume>13</volume>
      <elocation-id>e78502</elocation-id>
      <history>
        <date date-type="received">
          <day>5</day>
          <month>6</month>
          <year>2025</year>
        </date>
        <date date-type="rev-request">
          <day>6</day>
          <month>10</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>25</day>
          <month>11</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Sky Corby, Joan S Ash, Rebecca M Jungbauer, Gretchen Scholl, Sarah Florig, Vishnu Mohan, Jeffrey A Gold. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 19.12.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/e78502" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Electronic health records (EHRs) can aid in provider efficiency, but may also lead to unintended consequences, such as documentation burden and increased length of notes. To combat issues related to documentation, copying and pasting (CP) and copying or carrying forward (CF) are tools that have been used to aid in documentation burden. Multiple studies have identified the benefits and challenges of using these tools; however, few studies have identified the unintended consequences of CP and CF, and how the adoption of these tools may affect users.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The objective was to describe providers’ perceptions and use of copying tools available in the EHR and describe their suggestions for improvement on these copying tools.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Research team members conducted semistructured interviews with faculty members, advanced practice providers, residents or fellow trainees, and medical students at a single academic health sciences center. The Diffusion of Innovations Theory of Unintended Consequences guided the analysis and interpretation of interview results.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 22 semistructured interviews were conducted in 2023 and analyzed during 2024. The findings showed that respondents use and value these tools for efficiency and communication purposes. The negative unintended consequences include inaccuracies and errors in documentation and increased patient safety risks. Some respondents experience inner angst or moral injury related to using CP/CF, but they feel that they must use them to satisfy organizational requirements surrounding documentation. The respondents suggested that artificial intelligence will likely help improve documentation tools, as would further training around these types of documentation tools.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Some respondents noted feeling both internal and external pressures that influenced when and how they use CP/CF. Respondents noted that they value EHR copying tools for efficiency purposes, but they also understand the risks involved. This tension may lead to moral angst or moral injury. They offered numerous suggestions for lowering the risk, especially by improving the documentation capabilities of the EHR through artificial intelligence. Future research should investigate both technical and educational solutions to relieve the documentation burden and moral angst they are experiencing.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>clinical communication</kwd>
        <kwd>electronic health records</kwd>
        <kwd>clinical documentation</kwd>
        <kwd>copy-paste</kwd>
        <kwd>carry-forward</kwd>
        <kwd>qualitative research</kwd>
        <kwd>attitude of health personnel</kwd>
        <kwd>electronic documentation</kwd>
        <kwd>human factors</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Electronic health records (EHRs) were first introduced as a more efficient mechanism than paper for collecting and storing patient information such as test results, diagnoses, and clinical notes [<xref ref-type="bibr" rid="ref1">1</xref>]. Although the EHR is effective in many aspects, the adoption of this technology has given rise to unintended consequences. One primary concern, documentation burden, includes increased length of notes (“note bloat”) [<xref ref-type="bibr" rid="ref2">2</xref>] and time spent documenting [<xref ref-type="bibr" rid="ref3">3</xref>]. These unintended consequences contribute to another widespread problem: provider burnout [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
      <p>To combat issues related to EHR documentation, vendors have developed and implemented documentation tools that facilitate copying and pasting (CP) text and copying or carrying forward (CF) entire notes [<xref ref-type="bibr" rid="ref5">5</xref>] into their products that clinical users in health care organizations have embraced. CP allows users to copy elements of a note (eg, free text, test results, and clinical narratives) and paste that information into a new note. CF, available in some EHR systems, is used to copy an entire note, including templates and formats, to bring forward into a new note.</p>
      <p>Prior studies suggest CP/CF is used to improve usability and efficiency in documentation [<xref ref-type="bibr" rid="ref6">6</xref>], to decrease provider burnout [<xref ref-type="bibr" rid="ref7">7</xref>], and to improve documentation quality, where quality was defined as the accuracy of the information, and timeliness of the information, and the overall readability of the information in the note [<xref ref-type="bibr" rid="ref8">8</xref>]. However, CP can be a significant contributor to note bloat and error [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Some researchers found that 90% or more of inpatient service notes were either copied or templated, increasing length and number of errors in the notes [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>], while others reported CP/CF-related diagnostic and process errors contributed to the potential for moderate to severe harm [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Please see <xref ref-type="table" rid="table1">Table 1</xref> for a summary comparing intended versus unintended consequences.</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Summary of intended and unintended consequences of using CP<sup>a</sup>/CF<sup>b</sup> in EHR documentation from previous literature.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="500"/>
          <col width="500"/>
          <thead>
            <tr valign="top">
              <td>Intended consequences of CP/CF</td>
              <td>Unintended consequences of CP/CF</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>Efficiency</td>
              <td>Note bloat</td>
            </tr>
            <tr valign="top">
              <td>Relieve burnout</td>
              <td>Increase in errors in documentation</td>
            </tr>
            <tr valign="top">
              <td>Improve documentation quality</td>
              <td>Increase in diagnostic errors</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>CP: copying and pasting.</p>
          </fn>
          <fn id="table1fn2">
            <p><sup>b</sup>CF: copying or carrying forward.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>Researchers have typically investigated CP/CF use via surveys [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>] and large retrospective analyses of notes [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. A mixed-methods study assessing the association of CP use and risk severity, as well as perspectives of CP/CF use in progress notes and reported a wide spectrum of the value of CP/CF and progress notes across note authors and consumers was carried out [<xref ref-type="bibr" rid="ref21">21</xref>]. Other research has found similar variance in perception of value and efficiency by specialty, seniority, and setting [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      <p>Numerous studies have described the benefits (eg, efficiency) and challenges (eg, note bloat) of these tools. However, evidence considering the context in which these tools are implemented, and the potential to limit or avoid unanticipated and undesirable consequences of implementation, is lacking. The Diffusion of Innovations model posits that adoption of innovations proceeds through stages and is affected by properties of the innovations, adopters, social systems, change agents (individuals pushing for process improvement), and communication relationships [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. While CP/CF may be considered successful innovations in terms of adoption, the unanticipated (and potentially contradictory) consequences of CP/CF use may have dramatic ramifications for users, consumers, and the health systems themselves [<xref ref-type="bibr" rid="ref22">22</xref>]. This Theory of Unintended Consequences, a corollary to the Diffusion of Innovations Theory, is depicted in <xref rid="figure1" ref-type="fig">Figure 1</xref>, showing a cycle in which an innovation (in this case, CP/CF) is introduced and adopted. Adoption creates the intended and unintended consequences described in prior research, followed by iterative updates based on interactions with the social system. Throughout the process, the outside environment (eg, policy or cultural values) exerts pressure against the innovation usage.</p>
      <p>However, the benefits and challenges of innovative tools, such as CP/CF, coupled with an understanding of how the unanticipated and unintended consequences of CP/CF adoption affect users, are poorly described in the current literature. We aimed to use qualitative methodologies, guided by the Diffusion of Innovation Theory of Unintended Consequences, to (1) investigate provider perceptions, thoughts, and attitudes about CP/CF in the EHR; (2) identify the consequences (both intended and unintended) of using CP/CF across different specialties, departments, provider roles, and training level in one academic health care system; and (3) better understand users’ experiences with intended and unanticipated consequences of CP/CF by focusing on the futures of CP/CF.</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>The figure below depicts the modified Diffusion of Innovations Theory of Unintended Consequences, which is a theory showing a circular pattern where an innovation is introduced and adopted. The adoption of innovation then creates the intended and unintended consequences, which are followed by iterative updates based on interactions from the social system and the outside environmental pressures. CF: copying or carrying forward; CP: copying and pasting.</p>
        </caption>
        <graphic xlink:href="medinform_v13i1e78502_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study was approved by the Institutional Review Board at Oregon Health &#38; Science University (IRB #10027). Informed consent was obtained from respondents invited via email to participate in this study, and verbal consent was given before being recorded during the interview. The data used for this paper were deidentified, and the manuscript does not contain any information that would allow for the identification of respondents. Respondents were informed that study findings would be published, and their quotations would be presented anonymously. Participants were not compensated for participating in the interview.</p>
      </sec>
      <sec>
        <title>Recruitment or Setting of This Study</title>
        <p>Respondents for this comprised providers who initially responded to a prior quantitative survey [<xref ref-type="bibr" rid="ref19">19</xref>] in 2022-2023 regarding use of CP/CF for documentation, and while completing the survey, self-identified to be interviewed for the present study. These providers included faculty, advanced practice providers (APPs), medical students, and residents or fellow trainees at a single academic health institution. For our study, we have defined APPs as health care professionals who have had special training to diagnose, treat, and manage common medical conditions, which include physician’s assistants, certified nurses, nurse practitioners, and licensed social workers. APPs, faculty, medical students, and residents or fellow trainees who all used Epic (Epic Systems); and medical students and residents or fellow trainees on rotation at the Veterans Affairs health care system who also used VistA (Veterans Health Information Systems and Technology Architecture; US Department of Veterans Affairs). Thus, while the initial survey was purposively sampled, the participants identified for this study represented a convenience subsampling of a prior purposively selected cohort. The research team reached out to individuals who volunteered to participate in interviews to schedule virtual meetings.</p>
      </sec>
      <sec>
        <title>Design</title>
        <p>In 2023, the research team, consisting of four individuals from diverse and multiple backgrounds (informatics, qualitative research, quantitative research, psychology, and medical education), developed an interview guide. The interview guide included questions regarding demographics (eg, professional background, department or specialty, and patient population), innovation of CP/CF, CP/CF use, factors influencing use such as environmental pressures, types of consequences, and the future of CP/CF (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Each interview was conducted by 2 team members virtually through Cisco Webex (one interviewer was the lead, who asked the questions on the interview guide, and the second interviewer asked follow-up questions as well as any questions that may have been missed by the lead interviewer). Interviews were recorded and professionally transcribed.</p>
      </sec>
      <sec>
        <title>Analysis</title>
        <p>In 2024, the research team used both a thematic deductive framework, deriving themes from existing theories, and a thematic inductive framework (where themes are derived organically from raw data) to analyze data. Two team members used 3 transcripts to develop the initial codebook. Five team members then analyzed all 22 transcripts, consisting of 322 pages of data, using a standard inductive grounded approach, iteratively developing a codebook, and generating patterns and themes. NVivo 12 (Lumivero) was used for the management and analysis of the data. The inductively generated themes naturally fell into categories described in the Diffusion of Innovations Theory of Unintended Consequences [<xref ref-type="bibr" rid="ref22">22</xref>], so this framework was applied to describe the results.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>Findings are organized using the Diffusion of Innovations Theory of Unintended Consequences framework in <xref rid="figure1" ref-type="fig">Figure 1</xref>, enhanced by inductively produced themes. Rich quotes from interviewees are available in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
      </sec>
      <sec>
        <title>Demographics</title>
        <p>In 2023, we conducted 22 interviews (mean duration 48 minutes, range 29 to 65 minutes). Half were faculty (11/22, 50%), and most treated adult or family populations (17/22, 77%; <xref ref-type="table" rid="table2">Table 2</xref>). Most respondents were specialists (14/22, 64%). Many of the respondents saw patients in both inpatient and ambulatory settings (10/22, 45%), with some respondents reporting seeing patients in ambulatory settings alone (8/22, 36%).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Demographics table: qualitative interview respondents’ characteristics, including role or training level, population, department, and setting.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="470"/>
            <col width="0"/>
            <col width="0"/>
            <col width="500"/>
            <col width="0"/>
            <col width="0"/>
            <col width="0"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Respondent characteristic</td>
                <td colspan="3">Value, n (%)</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="7">
                  <bold>Role or training level</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Faculty</td>
                <td colspan="3">11 (50)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>APP<sup>a</sup></td>
                <td colspan="3">7 (32)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Resident and fellow trainee</td>
                <td colspan="3">2 (9)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Medical student</td>
                <td colspan="3">2 (9)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Population</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Pediatrics</td>
                <td colspan="3">5 (23)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Adult and family</td>
                <td colspan="3">17 (77)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Department</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">Specialists<sup>b</sup></td>
                <td colspan="4">14 (64)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Primary care, family medicine, and internal medicine</td>
                <td colspan="3">6 (27)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">Students</td>
                <td colspan="4">2 (9)</td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Setting</bold>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inpatient</td>
                <td colspan="3">4 (18)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ambulatory</td>
                <td colspan="3">8 (36)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Both</td>
                <td colspan="3">10 (45)</td>
                <td colspan="3">
                  <break/>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>APP: advanced practice provider (physician’s assistant, nurse practitioners, certified nurse, and licensed social worker).</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>Specialists include 1 each of the following: emergency medicine, women’s health, pediatrics, urology, midwifery, dermatology, psychiatry, rheumatology, neuroradiology, infectious disease, sepsis, neonatology, clinical informatics, and hematology-oncology.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Innovation</title>
        <p>The model (<xref rid="figure1" ref-type="fig">Figure 1</xref>) starts on the left with the innovation. The innovation is a new idea: in this case, duplicative text tools in the EHR. Respondents believed that because the documentation burden was so high for providers, CP/CF were developed as innovative solutions. <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> depicts the themes and subthemes found in the results.</p>
        <boxed-text id="box1" position="float">
          <title>Diffusion of Innovations Theory of Unintended Consequences Framework components from <xref rid="figure1" ref-type="fig">Figure 1</xref> and the subthemes related to each of the framework components (subthemes are displayed as bullet points).</title>
          <p>Framework component (from <xref rid="figure1" ref-type="fig">Figure 1</xref>) and subthemes</p>
          <p>
            <bold>Innovation</bold>
          </p>
          <p>
            <bold>Diffusion of CP (copying and pasting)/CF (copying or carrying forward) use</bold>
          </p>
          <p>
            <bold>Communication (influences)</bold>
          </p>
          <p>
            <bold>Social system</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Overview</p>
            </list-item>
            <list-item>
              <p>Differences in types of patient visits</p>
            </list-item>
            <list-item>
              <p>Difference in the health care delivery system</p>
            </list-item>
            <list-item>
              <p>Difference in specialty</p>
            </list-item>
            <list-item>
              <p>Difference in electronic health record (EHR) products</p>
            </list-item>
          </list>
          <p>
            <bold>Intended consequences</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Overview</p>
            </list-item>
            <list-item>
              <p>Efficiency or decreased documentation time</p>
            </list-item>
            <list-item>
              <p>Organization and time management skills</p>
            </list-item>
            <list-item>
              <p>Increased communication</p>
            </list-item>
            <list-item>
              <p>Improved accuracy for objective data</p>
            </list-item>
          </list>
          <p>
            <bold>Unintended consequences</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Overview</p>
            </list-item>
            <list-item>
              <p>Inaccuracies and errors in the note</p>
            </list-item>
            <list-item>
              <p>Plagiarism</p>
            </list-item>
            <list-item>
              <p>Note bloat</p>
            </list-item>
            <list-item>
              <p>Critical thinking issues</p>
            </list-item>
            <list-item>
              <p>Ultimate unintended consequence: inner angst or moral injury</p>
            </list-item>
          </list>
          <p>
            <bold>Outside environment</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Overview</p>
            </list-item>
            <list-item>
              <p>EHR-related solutions</p>
            </list-item>
            <list-item>
              <p>Artificial intelligence–related solutions</p>
            </list-item>
            <list-item>
              <p>Innovation: people-focused solutions</p>
            </list-item>
            <list-item>
              <p>Cultural shifts in documentation</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Diffusion of CP/CF Use</title>
        <p>Moving to the center square (<xref rid="figure1" ref-type="fig">Figure 1</xref>), consideration of the diffusion of CP/CF includes (1) how people adopt tools, (2) why people use these tools, and (3) why some decide not to use these tools.</p>
        <p>In the case of CP/CF, some respondents noted that at times, documentation duties occasionally fell onto the residents/fellow trainees and APPs, so these tools are necessary for efficiency purposes. Residents/fellow trainees are, at times, active change agents in the diffusion of CP/CF because “it would be impossible for trainees to not copy and paste” (faculty). However, residents/fellow trainees are not the only ones who document and use CP/CF. When faculty are not supervising residents/fellow trainees, they are writing notes themselves and use these tools regularly, so they can achieve a better work/life balance.</p>
      </sec>
      <sec>
        <title>Communication Influences</title>
        <p>The superior aspect of the model (<xref rid="figure1" ref-type="fig">Figure 1</xref>) indicates that communication impacts the diffusion and spread of an innovation (ie, CP/CF). Information about CP/CF was commonly communicated through informal training and education from other colleagues rather than through formal training. Medical students noted that communication about the appropriate use of these tools was inconsistent. Some direct supervisors (ie, resident/fellow trainees) vocalized and encouraged medical students to use the tools and “start building [these skills now]” (medical student), while others (ie, faculty supervisors) did not want them to use the tools because, as students, they needed practice writing notes themselves and developing critical thinking skills.</p>
      </sec>
      <sec>
        <title>Influence of Social Systems</title>
        <sec>
          <title>Overview</title>
          <p>The inferior aspect of the model (<xref rid="figure1" ref-type="fig">Figure 1</xref>) indicates there are societal or systems pressures influencing how and when CP/CF are used. Use of CP/CF varied greatly by type of patient visits, setting, specialty, and attributes of the EHR product.</p>
        </sec>
        <sec>
          <title>Differences in Types of Patient Visits</title>
          <p>The use of CP/CF differed depending on the type of patient visit (eg, telephone, virtual, or in-person visit; returning, new, or old patient). With a new patient, providers reported using CP to gather the patient’s historical information, especially when the history was complex and involved many images. However, there were some notable differences in use among clinicians. For example, a surgical resident/fellow trainee noted that he was more likely to write down verbal history when meeting a patient for the first time versus gathering prior information and using CP. Other providers mentioned that they do not use CF because they view each visit as a new visit.</p>
        </sec>
        <sec>
          <title>Difference in Health Care Delivery Setting</title>
          <p>According to our respondents, CP/CF use is influenced by whether care is provided in an ambulatory or inpatient setting. For example, CF has been described as “the backbone of all (in-)patient charting” (APP) because it aids in the continuity of care between team members, which would not be applicable in ambulatory settings. Providers who work in both inpatient and outpatient settings mentioned using CP in both settings because they are used to doing so.</p>
        </sec>
        <sec>
          <title>Difference in Specialty</title>
          <p>Respondents described how different workflows and documentation requirements impact CP/CF use. When providers see long-term patients for chronic problems, they rely on CP/CF, but if they consistently see new patients, such as in emergency medicine, they tend not to use them.</p>
          <p>Specialties vary in how they structure their notes, impacting the value of CP/CF. Those with more structured and templated notes used CP/CF less frequently, whereas other specialties required documentation of detailed thought processes and thus were less structured and used CP/CF more frequently. Volume and duration of the patient visits differed by specialty, which impacted providers’ use of CP/CF, with one faculty member noting, “when I’m busier, I tend to copy/paste more and copy forward more” (faculty). The research team also noted that the value found in using CP/CF differed by specialty, so developing a single policy to guide CP/CF throughout a health system would be challenging.</p>
        </sec>
        <sec>
          <title>Difference in EHR Products</title>
          <p>EHRs vary based on product offerings and integration into a system, including access to and policies for use of duplicative text tools. One resident/fellow trainee compared one academic center’s commercial EHR to the Veterans Affairs’ EHR, noting that CP is not easy to do, and CF is not available at all.</p>
        </sec>
      </sec>
      <sec>
        <title>Intended Consequences of CP/CF</title>
        <sec>
          <title>Overview</title>
          <p>The right aspect of the model (<xref rid="figure1" ref-type="fig">Figure 1</xref>) features the intended and unintended consequences of implementing any new technology. Our analysis revealed intended benefits from the innovation of CP/CF tools.</p>
        </sec>
        <sec>
          <title>Efficiency or Decreased Documentation Time</title>
          <p>When asked about the benefits of CP/CF, many respondents highlighted that these tools were “a survival mechanism” (faculty) that streamlines work processes, decreases documentation time, and increases efficiency, which reduces provider stress and promotes work/life balance.</p>
        </sec>
        <sec>
          <title>Organization and Time Management Skills</title>
          <p>Part of the CP/CF’s efficiency is derived from organization and time management, allowing providers to update relevant data in a template rather than recreating an entire note from scratch. When used this way, CF can provide consistency, organization, and standardization of notes, helping providers find salient information quickly.</p>
        </sec>
        <sec>
          <title>Increased Communication</title>
          <p>Respondents discussed CP/CF’s enhancement of communication within and across teams and disciplines and settings, which “saves [them] a great deal of time” (faculty). CP/CF help providers stay organized in their notes, which allows them to solve problems together.</p>
        </sec>
        <sec>
          <title>Improved Accuracy for Objective Data</title>
          <p>CP/CF may decrease errors in translating complicated or nuanced data from note to note, especially from specialists or when dictating notes. One example noted was radiology, because the integrity and accuracy of the original report should stay intact, and providers “don’t have translational[/dictation-relations] errors” (faculty).</p>
        </sec>
      </sec>
      <sec>
        <title>Unintended Consequences of CP/CF</title>
        <sec>
          <title>Overview</title>
          <p>While innovations bring about intended and desirable consequences, unintended consequences can also affect the adoption of innovations (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Although the diffusion of CP/CF into EHR systems could be considered a success, respondents discussed the risks and challenges CP/CF use presented, which shaped their willingness to use CP/CF in their practice.</p>
        </sec>
        <sec>
          <title>Inaccuracies and Errors in the Note</title>
          <p>All respondents noted that CP/CF use can increase inaccuracies and errors in the notes, from the seemingly innocuous errors (spelling errors) to harmful errors (forgetting to update a note). Information can be outdated yet copied. Errors can be perpetuated. Respondents admitted to forgetting to update information they had previously copied, especially in hectic environments. Some respondents expect that inaccuracies and errors will occur due to the “amount of pressure they feel to get [notes] done” (faculty) and the pressure on providers to see higher volumes of patients.</p>
          <p>Whether inaccuracies are accepted as part of the cost of using efficiency tools, these errors can be harmful, in some cases leading to legal as well as patient safety risks. One risk is putting the copied text into the wrong chart, allowing patients to see other patients’ confidential information. Another risk is carrying forward a care management plan that may not be appropriate for patients. One faculty member noted, “whatever we are signing our name [to] should be our own work” (faculty), and that signing off on a note that they have not reviewed thoroughly is problematic.</p>
        </sec>
        <sec>
          <title>Plagiarism</title>
          <p>Respondents noted that plagiarism can be another unintended consequence of using these tools. Attribution was another issue, with respondents discussing how they, or others, copied from other people’s notes without citing where they obtained this information or verifying that the information they copied is correct.</p>
        </sec>
        <sec>
          <title>Note Bloat</title>
          <p>One of the most cited challenges with the CP/CF innovation was the increased length of notes or note bloat. Note bloat makes quickly finding relevant or updated information within a large volume of data more challenging. The length of notes also contributes to the perpetuation of errors. As described by respondents, CP/CF contribute directly to note bloat. Additionally, longer notes mean that providers may not be reviewing and editing notes as carefully as they should, allowing errors to slip through.</p>
        </sec>
        <sec>
          <title>Critical Thinking Issues</title>
          <p>Respondents described how the use of CP/CF affected critical thinking skills and led people to not review information thoroughly. Providers, especially medical students and residents/fellow trainees, must learn how to think critically. As one faculty member noted, providers must “separate the wheat from the chaff” (faculty) and determine what to include in a note; critical thinking is an important part of training, which may be impeded by shortcuts in documentation.</p>
        </sec>
        <sec>
          <title>Ultimate Unintended Consequence: Inner Angst or Moral Injury</title>
          <p>The constant friction between the internal and personal desires to practice caution, review information thoroughly, and create concise and accurate notes, and the external pressures of practicing medicine in today’s organizational environment, has led to the most important unanticipated and unintended consequence of the CP/CF innovation: a sense of inner angst, or moral injury, among respondents. The concept of medical moral injury (or distress) among providers has gained traction in the literature in recent years, and covered actions due to commission (providers acting against a belief) or omission (providers not able to act on their beliefs), whether due to a sense of being internally or externally constrained in their ability to provide what they believe is quality care in a high-stakes situation or betrayal from people, institutions, or systems in power [<xref ref-type="bibr" rid="ref24">24</xref>]. Whether conscious of these feelings of inner angst or moral injury, respondents discussed at length the impact on and of CP/CF use.</p>
          <p>Documentation burden, due to time constraints and increased pressure to see higher patient volumes, negatively affected providers’ sense of well-being and created pressure to use these tools, even if they did not want to do so. With a higher patient census, documentation requirements increase, as does the amount of time providers need to review other people’s notes. Due to these conflicting issues, the compromise between efficiency and accuracy is a challenge for providers. Respondents described a love/hate relationship with CP/CF, in that, despite the risks, the tools are necessary to function in the current environment.</p>
          <p>Despite the acknowledgement that CP/CF can create some efficiencies, many respondents called CP/CF a “necessary evil” (APP) due to the risks and challenges arising from use.</p>
          <p>Respondents experience this internal struggle with wanting to be thorough, efficient, and accurate with documentation, but they do not have enough time to document, so they use tools that they know have errors associated with them, with some calling CP/CF “sloppy and paste” (faculty). Respondents feel this inner angst or moral injury because they have no other choice when the institution is pushing them to see more patients without allocating more time or compensation to document.</p>
        </sec>
      </sec>
      <sec>
        <title>Influence From the Outside Environment</title>
        <sec>
          <title>Overview</title>
          <p>Further complicating and adding to the inner angst experienced by providers, the outside environment influences diffusion of an innovation and its consequences (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Not only are providers feeling internal pressures, but they are also experiencing outside influences, including legal, regulatory, and financial requirements regarding what content to include in the note. This pressure, and the possible consequences, directly impact how respondents use CP/CF. In one example, a faculty member noted that the Centers for Medicare and Medicaid Services require an enormous number of requirements for one note, with some calling the note the “patient Wiki[pedia]” (faculty) for how many purposes the note serves at one time.</p>
        </sec>
        <sec>
          <title>EHR-Related Solutions</title>
          <p>Respondents provided suggestions for improving the EHR infrastructure to increase efficiency, including smart phrases, as well as improving education on EHR use. Part of that education includes understanding what information is relevant to keep in the notes to increase the usefulness of currently available efficiency tools, whether through CP or smart tools (Epic Systems). Respondents also expressed a desire for dictionaries that autocorrect abbreviations or prepopulate problem-based notes.</p>
          <p>Another suggestion was for a tool that automatically identifies whether any information had been copied, with author attribution prominently displayed, such as a pop-up alert when using or reviewing text created with CP/CF and requiring users to review common errors from CP/CF, such as dates or values, before closing an encounter<italic>.</italic> Respondents also mentioned needing alternative tools to display and integrate notes, as well as more standardization and guidelines in note creation. Others suggested having some sections of the notes be collapsible, as well as being able to insert images and hyperlinks within a charting tool for easier access to other areas of the chart.</p>
        </sec>
        <sec>
          <title>Artificial Intelligence–Related Solutions</title>
          <p>Some respondents described recent advances in artificial intelligence (AI) and the potential for integration into documentation tools. They wished that the note could be automatically created “like Jarvis style from the Avengers” (faculty). One such advancement currently under investigation is the use of ambient scribes, which listen to the physician-patient encounter and write the notes on behalf of the providers.</p>
        </sec>
        <sec>
          <title>New Innovations: People-Focused Solutions</title>
          <p>As much of the training and communication in EHR use to this point has arisen from informal communication channels (eg, word of mouth) or piecemeal, based on workflows and department needs, respondents requested additional education and training on best practices for documentation. Respondents also suggested training should focus on what the “right tools are to do the work” (APP), which could minimize reliance on CP/CF as the primary documentation tools.</p>
          <p>Equally critical to providing training on best practices in documentation is giving providers the amount of time necessary to set up templates and smart phrases in the EHR, as well as an understanding of what is important to include in a note, ensuring documentation is more efficient in the future. Respondents proposed new or updated guidelines and standards with clear teaching and expectations of use for CP/CF to ensure efficient use of the tools. Departmental guidelines and expectations surrounding CP/CF use could help new learners and faculty use these tools appropriately.</p>
          <p>The creation of a super user role on teams to facilitate general knowledge-sharing could provide a point person to identify key workflow components and functionality within departments or systems, which could “eliminate the amount of overload that the Epic support team [gets]” (APP) and lessen prolonged waiting times for users.</p>
        </sec>
        <sec>
          <title>Cultural Shifts in Documentation</title>
          <p>One of the key barriers to reviewing and editing notes for conciseness and accuracy is time, where <italic>“</italic>[time spent on editing the notes] is seen as an extra burden” (resident/fellow trainee). This extra time often is uncompensated and means less time caring for patients. The time spent on editing notes has unanticipated consequences of external constraints (eg, reimbursement policies or patient volume targets) on inner angst. An APP noted she wished she could spend more time with patients and less time documenting in general. Another APP highlighted that, “there’s been such an increasing pressure to see more and more patients… and that’s just making it harder and harder to actually document” (APP). With the current documentation culture, one resident/fellow trainee noted that, “the only way to function really, is to be copy and pasting from yourself [and] from others” (resident/fellow trainee).</p>
          <p>Providers argued that there needs to be a cultural shift with regard to best practices for what gets documented and put into the note, as well as how notes are used. The reliance on notes as a patient “Wikipedia” has contributed to note bloat and the rise in errors and inaccuracies, as well as provider burnout, and therefore, reliance on CP/CF to document quickly. Providing the time needed for reviewing the work is critical.</p>
          <p>Some providers suggested that the use of these tools should be limited. One faculty member said attribution should be mandatory; others added that the copied portions should be cited in quotes and attributed to the original author as in peer-reviewed publications. It could also be helpful to use different fonts, italics, or bold typeface to indicate copied text. Others mentioned that CP/CF should only be used for what is necessary to contextualize or augment the note, with clear identification of the information’s source.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary</title>
        <p>In this study, we identified perceptions of and attitudes toward CP and CF, as well as consequences of the diffusion of this innovation in note writing, in an academic hospital (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Whereas prior studies have described provider perceptions and process improvement through the introduction of CP/CF, our research expands on this literature by qualitatively exploring the consequences of this innovation through the lens of unintended consequences in diffusion [<xref ref-type="bibr" rid="ref19">19</xref>] (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>).</p>
        <boxed-text id="box2" position="float">
          <title>Summary findings are split up by the components of the Diffusion of Innovations Theory of Unintended Consequences framework from <xref rid="figure1" ref-type="fig">Figure 1</xref>.</title>
          <p>
            <bold>Communication (diffusion)</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Documentation burden falls greatly on providers—but with pressures on their time, diffusion (via communication or training) is limited and inconsistent—users have created ad hoc workarounds to deal with the workload, versus intentional evidence-based practice and critical thinking skills development.</p>
            </list-item>
          </list>
          <p>
            <bold>Social system</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Note purpose and use vary by specialty, health care setting, patient visits, and EHR products, so a one-size-fits-all solution is not feasible.</p>
            </list-item>
          </list>
          <p>
            <bold>Intended consequences</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Respondents report a more streamlined workflow and increased efficiency, especially those with templates to help with organization and consistency, and can help with inter- and intrateam communication—when used appropriately.</p>
            </list-item>
          </list>
          <p>
            <bold>Unintended consequences</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Whether through limited training, anxiety around policies, or other challenges, inaccuracies in notes result in risks to the patient, author, and system, from simple to severe. Respondents experience the moral injury of spending more time documenting out of fear of liability, harm, and denial of reimbursement, versus spending time providing care to patients, changing the culture of care. Noat bloat increases, the culture changes, and consequently, users experience frustration and burnout.</p>
            </list-item>
          </list>
          <p>
            <bold>Outside environment</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Legal, regulatory, and financial pressures require documentation, but users are having to adjust their workflow to the requirements, rather than the system adjusting to the workflow. Respondents hope innovations will help with efficiency, but question where they will fit in the current external environment, which is perceived as broken, or whether they will arise from within. There is a need for guidance and policy, but it is hard to do so when use is so variable.</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Discussion of Framework Elements</title>
        <sec>
          <title>Communication</title>
          <p>Awareness of CP/CF tools spread by word of mouth (<xref rid="figure1" ref-type="fig">Figure 1</xref>). As reported by others, the diffusers (ie, the ones spreading the innovation) are sometimes residents/fellow trainees and APPs, rather than supervisory or more senior staff, a trend that has persisted over the years [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. However, simple awareness does not guarantee the quality of the information communicated in the medical note, so tailored formal training is recommended [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Another recommendation to promote high-quality training is to have an EHR champion available, especially in the inpatient setting where CP/CF are most used [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>].</p>
          <p>Communication and training about the use of CP/CF in documentation can provide teaching opportunities to enhance critical thinking of relevant information to capture [<xref ref-type="bibr" rid="ref29">29</xref>]. This may be less likely in high-pressure, dynamic systems, but some have had success in training through templated or team-based writing [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p>
        </sec>
        <sec>
          <title>Social System</title>
          <p>Innovations (<xref rid="figure1" ref-type="fig">Figure 1</xref>) such as CP/CF are highly complex and are integrated into similarly complex and evolving systems [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. Implementation and adoption rely not only on individuals and their personal characteristics, but the innovation itself, as well as the structure and characteristics, and culture of the organization in which the innovation is deployed. By certain metrics, innovations may be successfully diffused (technically adopted), but a lack of consideration for the interdependency of the actors in a system may inhibit realization of the optimal or true value to the system, and can lead to unintended consequences [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>].</p>
        </sec>
        <sec>
          <title>Intended Consequences</title>
          <p>Our results reflect those of other reports that CP/CF improve efficiency [<xref ref-type="bibr" rid="ref6">6</xref>], continuity of care for patients [<xref ref-type="bibr" rid="ref8">8</xref>], and communication with teammates [<xref ref-type="bibr" rid="ref33">33</xref>], as well as decreased documentation burden [<xref ref-type="bibr" rid="ref7">7</xref>]. Yet in the two decades of literature acknowledging the benefit of innovation in electronic records, these same reports highlight the double-edged sword of efficiency versus unintended consequences [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. Without trust in the system or other users, or without bulwarks against our own inherent flaws as human users of technology [<xref ref-type="bibr" rid="ref35">35</xref>], the optimal use and benefits of these innovations and the intended consequence of improving quality of care will not be realized [<xref ref-type="bibr" rid="ref31">31</xref>].</p>
          <p>Our respondents describe the need for short-term solutions, such as recurring formal training on how and when to use CP/CF. Others have similarly demonstrated that lack of knowledge of appropriate use results in increased length of notes [<xref ref-type="bibr" rid="ref36">36</xref>] and the importance of training and education for safe practice regarding these tools [<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        </sec>
        <sec>
          <title>Unintended Consequences</title>
          <p>Documentation burden, note bloat, inaccuracies, and more time spent documenting to the detriment of patient care, training, and interpersonal communication and trust—all have led to a perceived worsening of culture, the work environment, and workflows [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. These phenomena are not new; the same benefits and challenges have remained consistent over time and across systems [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref40">40</xref>]. This dichotomy of intended (often positive) consequences and unintended (often negative) consequences results in providers experiencing increased inner angst and moral injury [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Providers report angst from constraints against practicing what they consider “quality” care, and despite knowing the myriad risks, use tools such as CP/CF as the only workaround right now in a broken system, calling CP/CF a necessary evil. While providers acknowledge that CP/CF and other tools aid in the continuity of care and create a sense of efficiency when documenting, the lack of time to review notes thoroughly is a consistent and pervasive structural barrier. In such instances, errors slip through the cracks—the role of CP/CF in errors, inaccuracies, and outdated information is of particular concern [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], as they have contributed to note bloat [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>] and may play a role in patient safety [<xref ref-type="bibr" rid="ref16">16</xref>]. Inaccuracies may damage a patient’s trust in and experience with the clinician or system; contribute to diagnostic and safety errors (inaccurate or out-of-date records, difficulty in finding relevant data in bloated notes); and increase legal risks, including unintentional falsification of records or plagiarism and medical malpractice [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. All of these factors conspire to reduce providers’ overall perceived quality of care delivery. This, in turn, can further worsen provider dissatisfaction and burnout, with a study suggesting that clinician involvement in medical errors is an independent risk of burnout [<xref ref-type="bibr" rid="ref43">43</xref>].</p>
        </sec>
        <sec>
          <title>Outside Environment</title>
          <p>The outer system (<xref rid="figure1" ref-type="fig">Figure 1</xref>) is a key factor for optimal diffusion and implementation of an innovation [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Recommendations to address challenges in using CP/CF include developing policies, both institution-wide and specialty-specific, for CP/CF use. These larger structural factors—policies, standards, legislation, system resources, and engagement of leadership—filter down into organizational workflow and processes and then to individual knowledge of the innovation [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Although improvements at this larger scale are difficult to accomplish and are often more long-term solutions, a fundamental shift is needed at the outer system level in how these innovations are built for and integrated into dynamic, complex systems. Notes should serve clinical purposes and not focus as much on reimbursement regulations and national quality measures [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref44">44</xref>].</p>
        </sec>
        <sec>
          <title>New Innovations</title>
          <p>In the short term, most providers report the need for specific interventions, such as training to improve optimal EHR use, continued EHR optimization, and improved awareness of best practices for use of the functionality are necessary. Others recommended some degree of restrictions on use as well. While shown in other health systems to have direct impacts on hospital readmission [<xref ref-type="bibr" rid="ref45">45</xref>], the overall widespread reliance on its use, and the inability to remove this functionality (easily) from underlying operating systems, suggest this is a nonviable solution. As a result, one must look for more novel, sustainable solutions. With the growth of AI and tools such as ambient or digital scribes already in use in clinical care to reduce documentation burden, careful reflection on the appropriate use of innovative tools will be paramount in mitigating current and future unintended consequences [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref46">46</xref>-<xref ref-type="bibr" rid="ref48">48</xref>]. Another way to mitigate unintended consequences for ambient scribing would be to develop measures and metrics of success (eg, provider satisfaction scores, decrease in pajama time charting, decrease in documentation time, and increase in work/life balance). That way, organizations could evaluate whether the ambient scribes are aiding providers related to the intended metrics. However, while ambient scribes hold promise, to date, no studies have documented the impact of the ambient scribes on the amount of CP present in notes. This is likely, in part, because studies on ambient scribes are limited to ambulatory settings [<xref ref-type="bibr" rid="ref49">49</xref>]. This will need to be an area of future study as the technology becomes more widespread.</p>
        </sec>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>There were some strengths in our study. First, this paper addresses providers’ perspectives toward CP/CF in a way that adds depth and insight to the body of literature already present. Second, this is one of the first papers that attributes the concept of moral injury to the use of CP/CF, which has not been explored in the literature. Third, this manuscript offers recent perspectives and alternative solutions to aid in the documentation burden (eg, AI scribing). Fourth, this paper provides a true direct negative harm of CP/CF to the users, something which has not been previously described. In essence, while CP/CF use is continuing to grow over the years, it is associated with higher rates of documentation burden and job dissatisfaction. Thus, it is not working to solve the primary problem it was adopted to address: to make providers efficient and alleviate documentation burden. One reason for this may be the unintended consequence of its use, that whatever benefit the provider obtains from using these tools, moral injury and guilt compound and hinder providers.</p>
        <p>There were some limitations to our study. First, this research was conducted at one academic health care institution, which may limit the generalizability of the findings. However, we solicited a breadth of input from various departments, roles/training levels, and clinical settings. Further, reported results from previous research on CP/CF are consistent with our findings, suggesting that these phenomena go beyond our institution. We also engaged a diverse team of researchers from a variety of disciplinary and demographic backgrounds to analyze the data to ensure a multidisciplinary approach and perspective. Second, it should be noted that the respondents for interviews were recruited from a subset of respondents to a previously deployed anonymous survey [<xref ref-type="bibr" rid="ref19">19</xref>], specifically those who had self-identified and volunteered to participate in interviews. This approach does raise the likelihood of amplifying potential selection bias. Additionally, we used a convenience sampling method to select participants for interviews, and while the initial survey used a more robust purposive sampling strategy, the subset of self-identified interview participants was predominantly faculty and APPs, as opposed to medical students and residents/fellow trainees. As the use of CP is ubiquitous across levels of training and professional experience, we believe that our sampling strategy does reflect a broad and adequate spectrum of perspectives despite the relative underrepresentation of medical students and residents/fellow trainees. Third, at the time these interviews were conducted, there had been some discussion within the institution about whether curtailing or banning the use of CP/CF was appropriate as a policy measure. However, despite this potential barrier, it should be noted that respondents uniformly expressed both positive and negative perceptions of EHR documentation tools.</p>
      </sec>
      <sec>
        <title>Future Research Directions</title>
        <p>Research addressing the unintended consequences of CP/CF, such as the use of a note for multiple purposes (eg, legal and patient safety implications, billing, communication, and continuity of care), could lead to slimmer, more streamlined notes, a decrease in documentation burden, and less burnout.</p>
        <p>While CP/CF has limitations, there are innovations that could encourage appropriate use or reduce the need for CP/CF in documentation. Some potential innovations discussed by our participants were EHR technical solutions, including automatically identifying information that has been copied and having pop-up alerts when using or reviewing texts. Future research on the role these proposed features have in documentation could inform additional technical innovations and support cultural practices for proper attribution. AI solutions, such as digital or ambient scribes, may decrease the documentation burden and the need to use CP/CF; research is ongoing [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>], but future research is needed to understand use across systems with different EHR policies and capacities. People-focused solutions, including more robust orientation training on CP/CF and having staff EHR super users to facilitate general knowledge sharing, could support more efficient and appropriate use of EHR tools, which in turn could help address documentation burden. Future research of educational programs and inclusion of EHR super users pre- and postimplementation may provide justification to integrate these ideas into clinical practice workflows, supporting a culture valuing time for training. Furthermore, importantly, health care systems are complex environments, and implementing new tools can result in unintended consequences. Future work must consider the potential for these unintended consequences resulting from the implementation of a complex innovation in dynamic systems.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Our study aimed to use semistructured interviews with providers to investigate their perceptions and attitudes surrounding CP/CF in the EHR, using a modified Diffusion of Innovations Theory of Unintended Consequences framework to analyze the data. The intended consequence of the innovative CP/CF tool, efficiency, is valued by users. However, the unintended consequences, including note bloat, errors, and patient safety and legal risks, have given rise to moral injury, a finding consistent with the literature. The theory of unintended consequences framework addresses the complex system within which CP/CF exists. In the case of CP/CF, outside pressures on documentation requirements are one of the critical barriers to realizing the potential for innovative duplicative text tools. Fewer documentation requirements may lessen internal and external pressures, leading to inner angst or moral injury among providers.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Participant interview guide.</p>
        <media xlink:href="medinform_v13i1e78502_app1.docx" xlink:title="DOCX File , 24 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Table of quotes from participants in relation to the diffusion of innovation themes.</p>
        <media xlink:href="medinform_v13i1e78502_app2.docx" xlink:title="DOCX File , 37 KB"/>
      </supplementary-material>
    </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">APP</term>
          <def>
            <p>advanced practice provider</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CF</term>
          <def>
            <p>copying or carrying forward</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">CP</term>
          <def>
            <p>copying and pasting</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">VistA</term>
          <def>
            <p>Veterans Health Information Systems and Technology Architecture</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study would not have been possible without the support of Oregon Health and Science University. No generative artificial intelligence tools were used in the writing of this paper.</p>
    </ack>
    <notes>
      <sec>
        <title>Funding</title>
        <p>This research project was funded through a grant from the Agency for Healthcare Research and Quality (R18HS029345).</p>
      </sec>
    </notes>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The dataset generated or analyzed during this study is available from the corresponding author on reasonable request.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>Conceptualization: JAG (equal), VM (equal), JSA (equal), SC (equal)</p>
        <p>Data curation: SC (lead)</p>
        <p>Formal analysis: SC (equal), JSA (equal), RMJ (supporting), SF (supporting), GS (supporting)</p>
        <p>Funding acquisition: JAG (lead)</p>
        <p>Investigation: JSA (equal), SF (supporting), SC (equal)</p>
        <p>Methodology: JSA (equal), SC (equal), JAG (equal), VM (equal), SF (supporting), GS (supporting), RMJ (supporting)</p>
        <p>Project administration: SC (lead)</p>
        <p>Resources: SC (equal), VM (equal), JAG (lead), JSA (equal)</p>
        <p>Software: SC (lead)</p>
        <p>Supervision: JAG (equal), JSA (lead), VM (equal), SC (equal)</p>
        <p>Validation: SC (lead), JSA (lead), RMJ (equal), GS (equal), SF (equal), JAG (supporting), VM (supporting)</p>
        <p>Visualization: RMJ (lead)</p>
        <p>Writing – original draft: SC (lead)</p>
        <p>Writing – review &#38; editing: SC (lead), RMJ (lead), JSA (lead), VM (equal), JAG (equal), GS (equal), SF (supporting)</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>Blumenthal</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Launching HITECH</article-title>
          <source>N Engl J Med</source>
          <year>2010</year>
          <volume>362</volume>
          <issue>5</issue>
          <fpage>382</fpage>
          <lpage>385</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMp0912825</pub-id>
          <pub-id pub-id-type="medline">20042745</pub-id>
          <pub-id pub-id-type="pii">NEJMp0912825</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>Holmgren</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Downing</surname>
              <given-names>NL</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Milstein</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Cutler</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Huckman</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Schulman</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>Assessment of electronic health record use between US and non-us health systems</article-title>
          <source>JAMA Intern Med</source>
          <year>2021</year>
          <volume>181</volume>
          <issue>2</issue>
          <fpage>251</fpage>
          <lpage>259</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33315048"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamainternmed.2020.7071</pub-id>
          <pub-id pub-id-type="medline">33315048</pub-id>
          <pub-id pub-id-type="pii">2774129</pub-id>
          <pub-id pub-id-type="pmcid">PMC7737152</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>Rotenstein</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Apathy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Holmgren</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Physician note composition patterns and time on the EHR across specialty types: a national, cross-sectional study</article-title>
          <source>J Gen Intern Med</source>
          <year>2023</year>
          <volume>38</volume>
          <issue>5</issue>
          <fpage>1119</fpage>
          <lpage>1126</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36418647"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-022-07834-5</pub-id>
          <pub-id pub-id-type="medline">36418647</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11606-022-07834-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC10110827</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>West</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Dyrbye</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>TD</given-names>
            </name>
          </person-group>
          <article-title>Physician burnout: contributors, consequences and solutions</article-title>
          <source>J Intern Med</source>
          <year>2018</year>
          <volume>283</volume>
          <issue>6</issue>
          <fpage>516</fpage>
          <lpage>529</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1111/joim.12752"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/joim.12752</pub-id>
          <pub-id pub-id-type="medline">29505159</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Apathy</surname>
              <given-names>NC</given-names>
            </name>
            <name name-style="western">
              <surname>Rotenstein</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Holmgren</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Documentation dynamics: note composition, burden, and physician efficiency</article-title>
          <source>Health Serv Res</source>
          <year>2023</year>
          <volume>58</volume>
          <issue>3</issue>
          <fpage>674</fpage>
          <lpage>685</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36342001"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/1475-6773.14097</pub-id>
          <pub-id pub-id-type="medline">36342001</pub-id>
          <pub-id pub-id-type="pmcid">PMC10154172</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tsou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lehmann</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Michel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Solomon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Possanza</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gandhi</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Safe practices for copy and paste in the EHR</article-title>
          <source>Appl Clin Inform</source>
          <year>2017</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <lpage>34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28074211"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2016-09-R-0150</pub-id>
          <pub-id pub-id-type="medline">28074211</pub-id>
          <pub-id pub-id-type="pii">2016-09-R-0150</pub-id>
          <pub-id pub-id-type="pmcid">PMC5373750</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hilliard</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Haskell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gardner</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Are specific elements of electronic health record use associated with clinician burnout more than others?</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <volume>27</volume>
          <issue>9</issue>
          <fpage>1401</fpage>
          <lpage>1410</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32719859"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa092</pub-id>
          <pub-id pub-id-type="medline">32719859</pub-id>
          <pub-id pub-id-type="pii">5876976</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647296</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>O'Donnell</surname>
              <given-names>HC</given-names>
            </name>
            <name name-style="western">
              <surname>Kaushal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Barrón</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Callahan</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Adelman</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Siegler</surname>
              <given-names>EL</given-names>
            </name>
          </person-group>
          <article-title>Physicians' attitudes towards copy and pasting in electronic note writing</article-title>
          <source>J Gen Intern Med</source>
          <year>2009</year>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>63</fpage>
          <lpage>68</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/18998191"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-008-0843-2</pub-id>
          <pub-id pub-id-type="medline">18998191</pub-id>
          <pub-id pub-id-type="pmcid">PMC2607489</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>Digan</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wack</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Looten</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Neuraz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Burgun</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rance</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the impact of text duplications on a corpus of more than 600,000 clinical narratives in a French hospital</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <volume>264</volume>
          <fpage>103</fpage>
          <lpage>107</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI190192</pub-id>
          <pub-id pub-id-type="medline">31437894</pub-id>
          <pub-id pub-id-type="pii">SHTI190192</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>Roddy</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>VM</given-names>
            </name>
            <name name-style="western">
              <surname>Chaudhry</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Rein</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Banerjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Swenson</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Fletcher</surname>
              <given-names>KE</given-names>
            </name>
          </person-group>
          <article-title>The prevalence and implications of copy and paste: internal medicine program director perspectives</article-title>
          <source>J Gen Intern Med</source>
          <year>2018</year>
          <volume>33</volume>
          <issue>12</issue>
          <fpage>2032</fpage>
          <lpage>2033</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30066119"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-018-4575-7</pub-id>
          <pub-id pub-id-type="medline">30066119</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11606-018-4575-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6258631</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rule</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bedrick</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chiang</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Hribar</surname>
              <given-names>MR</given-names>
            </name>
          </person-group>
          <article-title>Length and redundancy of outpatient progress notes across a decade at an academic medical center</article-title>
          <source>JAMA Netw Open</source>
          <year>2021</year>
          <volume>4</volume>
          <issue>7</issue>
          <fpage>e2115334</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34279650"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2021.15334</pub-id>
          <pub-id pub-id-type="medline">34279650</pub-id>
          <pub-id pub-id-type="pii">2782054</pub-id>
          <pub-id pub-id-type="pmcid">PMC8290305</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>Steinkamp</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kantrowitz</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Airan-Javia</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Prevalence and sources of duplicate information in the electronic medical record</article-title>
          <source>JAMA Netw Open</source>
          <year>2022</year>
          <volume>5</volume>
          <issue>9</issue>
          <fpage>e2233348</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36156143"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2022.33348</pub-id>
          <pub-id pub-id-type="medline">36156143</pub-id>
          <pub-id pub-id-type="pii">2796664</pub-id>
          <pub-id pub-id-type="pmcid">PMC9513649</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>Wang</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Khanna</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Najafi</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Characterizing the source of text in electronic health record progress notes</article-title>
          <source>JAMA Intern Med</source>
          <year>2017</year>
          <volume>177</volume>
          <issue>8</issue>
          <fpage>1212</fpage>
          <lpage>1213</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28558106"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamainternmed.2017.1548</pub-id>
          <pub-id pub-id-type="medline">28558106</pub-id>
          <pub-id pub-id-type="pii">2629493</pub-id>
          <pub-id pub-id-type="pmcid">PMC5818790</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>Wang</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Carrington</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Hammarlund</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sanchez</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Revere</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>An evaluation of copy and paste events in electronic notes of patients with hospital acquired conditions</article-title>
          <source>Int J Med Inform</source>
          <year>2023</year>
          <volume>170</volume>
          <fpage>104934</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2022.104934</pub-id>
          <pub-id pub-id-type="medline">36508751</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(22)00248-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Al Hadidi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Upadhaya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shastri</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Alamarat</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Use of dictation as a tool to decrease documentation errors in electronic health records</article-title>
          <source>J Community Hosp Intern Med Perspect</source>
          <year>2017</year>
          <volume>7</volume>
          <issue>5</issue>
          <fpage>282</fpage>
          <lpage>286</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.1080/20009666.2017.1379852?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/20009666.2017.1379852</pub-id>
          <pub-id pub-id-type="medline">29147468</pub-id>
          <pub-id pub-id-type="pii">1379852</pub-id>
          <pub-id pub-id-type="pmcid">PMC5676967</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>Singh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Giardina</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>AND</given-names>
            </name>
            <name name-style="western">
              <surname>Forjuoh</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Reis</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>Types and origins of diagnostic errors in primary care settings</article-title>
          <source>JAMA Intern Med</source>
          <year>2013</year>
          <volume>173</volume>
          <issue>6</issue>
          <fpage>418</fpage>
          <lpage>425</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/23440149"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamainternmed.2013.2777</pub-id>
          <pub-id pub-id-type="medline">23440149</pub-id>
          <pub-id pub-id-type="pii">1656540</pub-id>
          <pub-id pub-id-type="pmcid">PMC3690001</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>Graber</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Siegal</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Riah</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Johnston</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kenyon</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record-related events in medical malpractice claims</article-title>
          <source>J Patient Saf</source>
          <year>2019</year>
          <volume>15</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>85</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26558652"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/PTS.0000000000000240</pub-id>
          <pub-id pub-id-type="medline">26558652</pub-id>
          <pub-id pub-id-type="pmcid">PMC6553982</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>Heiman</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Rasminsky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bierman</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Kinner</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Stamos</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Martinovich</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>McGaghie</surname>
              <given-names>WC</given-names>
            </name>
          </person-group>
          <article-title>Medical students' observations, practices, and attitudes regarding electronic health record documentation</article-title>
          <source>Teach Learn Med</source>
          <year>2014</year>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>49</fpage>
          <lpage>55</lpage>
          <pub-id pub-id-type="doi">10.1080/10401334.2013.857337</pub-id>
          <pub-id pub-id-type="medline">24405346</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hudkins</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gold</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Corby</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mohan</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Exploring provider perceptions and attitudes toward copy-paste and copy-forward in clinical documentation</article-title>
          <source>Appl Clin Inform</source>
          <year>2025</year>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>736</fpage>
          <lpage>746</lpage>
          <pub-id pub-id-type="doi">10.1055/a-2574-1348</pub-id>
          <pub-id pub-id-type="medline">40769172</pub-id>
          <pub-id pub-id-type="pmcid">PMC12328030</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>Thornton</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Schold</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Venkateshaiah</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lander</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Prevalence of copied information by attendings and residents in critical care progress notes</article-title>
          <source>Crit Care Med</source>
          <year>2013</year>
          <volume>41</volume>
          <issue>2</issue>
          <fpage>382</fpage>
          <lpage>388</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/23263617"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/CCM.0b013e3182711a1c</pub-id>
          <pub-id pub-id-type="medline">23263617</pub-id>
          <pub-id pub-id-type="pmcid">PMC3718042</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>Payne</surname>
              <given-names>TH</given-names>
            </name>
            <name name-style="western">
              <surname>Keller</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Brusati</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Levin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Salgaonkar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zech</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lees</surname>
              <given-names>AF</given-names>
            </name>
          </person-group>
          <article-title>Writing practices associated with electronic progress notes and the preferences of those who read them: descriptive study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>10</issue>
          <fpage>e30165</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/10/e30165/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/30165</pub-id>
          <pub-id pub-id-type="medline">34612825</pub-id>
          <pub-id pub-id-type="pii">v23i10e30165</pub-id>
          <pub-id pub-id-type="pmcid">PMC8529482</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>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Dykstra</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Guappone</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Carpenter</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Seshadri</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Categorizing the unintended sociotechnical consequences of computerized provider order entry</article-title>
          <source>Int J Med Inf</source>
          <year>2007</year>
          <volume>76 Suppl 1</volume>
          <fpage>S21</fpage>
          <lpage>S27</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2006.05.017</pub-id>
          <pub-id pub-id-type="medline">16793330</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(06)00138-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>EM</given-names>
            </name>
          </person-group>
          <source>Diffusion of Innovations</source>
          <year>2003</year>
          <publisher-loc>New York City</publisher-loc>
          <publisher-name>Free Press</publisher-name>
        </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>Griffin</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Purcell</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Burkman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Litz</surname>
              <given-names>BT</given-names>
            </name>
            <name name-style="western">
              <surname>Bryan</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Schmitz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Villierme</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Walsh</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Maguen</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Moral injury: an integrative review</article-title>
          <source>J Trauma Stress</source>
          <year>2019</year>
          <volume>32</volume>
          <issue>3</issue>
          <fpage>350</fpage>
          <lpage>362</lpage>
          <pub-id pub-id-type="doi">10.1002/jts.22362</pub-id>
          <pub-id pub-id-type="medline">30688367</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>Block</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Habicht</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>KN</given-names>
            </name>
            <name name-style="western">
              <surname>Niessen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Oliver</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Feldman</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>In the wake of the 2003 and 2011 duty hours regulations, how do internal medicine interns spend their time?</article-title>
          <source>J Gen Intern Med</source>
          <year>2013</year>
          <volume>28</volume>
          <issue>8</issue>
          <fpage>1042</fpage>
          <lpage>1047</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/23595927"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-013-2376-6</pub-id>
          <pub-id pub-id-type="medline">23595927</pub-id>
          <pub-id pub-id-type="pmcid">PMC3710392</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khairat</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chourasia</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kwong</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Seashore</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Effect of tailored coaching on physicians' electronic health record proficiency and user experience: a randomized crossover study</article-title>
          <source>Mayo Clin Proc Digit Health</source>
          <year>2023</year>
          <volume>1</volume>
          <issue>2</issue>
          <fpage>94</fpage>
          <lpage>104</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2949-7612(23)00011-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.mcpdig.2023.02.005</pub-id>
          <pub-id pub-id-type="medline">40206730</pub-id>
          <pub-id pub-id-type="pii">S2949-7612(23)00011-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC11975678</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gainforth</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Latimer-Cheung</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Athanasopoulos</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ginis</surname>
              <given-names>KAM</given-names>
            </name>
          </person-group>
          <article-title>The role of interpersonal communication in the process of knowledge mobilization within a community-based organization: a network analysis</article-title>
          <source>Implement Sci</source>
          <year>2014</year>
          <volume>9</volume>
          <fpage>59</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/1748-5908-9-59"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1748-5908-9-59</pub-id>
          <pub-id pub-id-type="medline">24886429</pub-id>
          <pub-id pub-id-type="pii">1748-5908-9-59</pub-id>
          <pub-id pub-id-type="pmcid">PMC4052292</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Cauthorn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Francis</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hackenberg</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Maloney</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hohmuth</surname>
              <given-names>BA</given-names>
            </name>
          </person-group>
          <article-title>A practical approach for monitoring the use of copy-paste in clinical notes</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2022</year>
          <volume>2021</volume>
          <fpage>1178</fpage>
          <lpage>1185</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35308931"/>
          </comment>
          <pub-id pub-id-type="medline">35308931</pub-id>
          <pub-id pub-id-type="pii">3577441</pub-id>
          <pub-id pub-id-type="pmcid">PMC8861699</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>Huang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Whitehead</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kuper</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Competing discourses, contested roles: electronic health records in medical education</article-title>
          <source>Med Educ</source>
          <year>2024</year>
          <volume>58</volume>
          <issue>12</issue>
          <fpage>1490</fpage>
          <lpage>1501</lpage>
          <pub-id pub-id-type="doi">10.1111/medu.15428</pub-id>
          <pub-id pub-id-type="medline">38764398</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rodríguez-Fernández</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Loeb</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Hier</surname>
              <given-names>DB</given-names>
            </name>
          </person-group>
          <article-title>It's time to change our documentation philosophy: writing better neurology notes without the burnout</article-title>
          <source>Front Digit Health</source>
          <year>2022</year>
          <volume>4</volume>
          <fpage>1063141</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36518562"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2022.1063141</pub-id>
          <pub-id pub-id-type="medline">36518562</pub-id>
          <pub-id pub-id-type="pmcid">PMC9742203</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>Humphrey-Murto</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Makus</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Watanabe Duffy</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Maniate</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Scowcroft</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Buba</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rangel</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Training physicians and residents for the use of electronic health records-a comparative case study between two hospitals</article-title>
          <source>Med Educ</source>
          <year>2023</year>
          <volume>57</volume>
          <issue>4</issue>
          <fpage>337</fpage>
          <lpage>348</lpage>
          <pub-id pub-id-type="doi">10.1111/medu.14944</pub-id>
          <pub-id pub-id-type="medline">36181382</pub-id>
        </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>Singh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
          </person-group>
          <article-title>A sociotechnical framework for safety-related electronic health record research reporting: the SAFER reporting framework</article-title>
          <source>Ann Intern Med</source>
          <year>2020</year>
          <volume>172</volume>
          <issue>11 Suppl</issue>
          <fpage>S92</fpage>
          <lpage>S100</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/10.7326/M19-0879?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M19-0879</pub-id>
          <pub-id pub-id-type="medline">32479184</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>Vos</surname>
              <given-names>JFJ</given-names>
            </name>
            <name name-style="western">
              <surname>Boonstra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kooistra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Seelen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Offenbeek</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The influence of electronic health record use on collaboration among medical specialties</article-title>
          <source>BMC Health Serv Res</source>
          <year>2020</year>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>676</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-020-05542-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-020-05542-6</pub-id>
          <pub-id pub-id-type="medline">32698807</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-020-05542-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7374868</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>Hirschtick</surname>
              <given-names>RE</given-names>
            </name>
          </person-group>
          <article-title>A piece of my mind. Copy-and-paste</article-title>
          <source>JAMA</source>
          <year>2006</year>
          <volume>295</volume>
          <issue>20</issue>
          <fpage>2335</fpage>
          <lpage>2336</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.295.20.2335</pub-id>
          <pub-id pub-id-type="medline">16720812</pub-id>
          <pub-id pub-id-type="pii">295/20/2335</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rahimi</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Timpka</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vimarlund</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Uppugunduri</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Svensson</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Organization-wide adoption of computerized provider order entry systems: a study based on diffusion of innovations theory</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2009</year>
          <volume>9</volume>
          <fpage>52</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-9-52"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-9-52</pub-id>
          <pub-id pub-id-type="medline">20043843</pub-id>
          <pub-id pub-id-type="pii">1472-6947-9-52</pub-id>
          <pub-id pub-id-type="pmcid">PMC2809050</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>Pennathur</surname>
              <given-names>PR</given-names>
            </name>
          </person-group>
          <article-title>A theoretical framework for understanding creator-consumer information interaction behaviors in healthcare documentation systems</article-title>
          <source>Appl Ergon</source>
          <year>2020</year>
          <volume>84</volume>
          <fpage>103034</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31987517"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2019.103034</pub-id>
          <pub-id pub-id-type="medline">31987517</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(19)30240-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7141766</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Embi</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Yackel</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Logan</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Bowen</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Cooney</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>Gorman</surname>
              <given-names>PN</given-names>
            </name>
          </person-group>
          <article-title>Impacts of computerized physician documentation in a teaching hospital: perceptions of faculty and resident physicians</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2004</year>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>300</fpage>
          <lpage>309</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/15064287"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M1525</pub-id>
          <pub-id pub-id-type="medline">15064287</pub-id>
          <pub-id pub-id-type="pii">M1525</pub-id>
          <pub-id pub-id-type="pmcid">PMC436079</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>Hoerbst</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schweitzer</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A systematic investigation on barriers and critical success factors for clinical information systems in integrated care settings</article-title>
          <source>Yearb Med Inf</source>
          <year>2015</year>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>79</fpage>
          <lpage>89</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.15265/IY-2015-018"/>
          </comment>
          <pub-id pub-id-type="doi">10.15265/IY-2015-018</pub-id>
          <pub-id pub-id-type="medline">26293853</pub-id>
          <pub-id pub-id-type="pii">me2015-018</pub-id>
          <pub-id pub-id-type="pmcid">PMC4587036</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Siegler</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Adelman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Copy and paste: a remediable hazard of electronic health records</article-title>
          <source>Am J Med</source>
          <year>2009</year>
          <volume>122</volume>
          <issue>6</issue>
          <fpage>495</fpage>
          <lpage>496</lpage>
          <pub-id pub-id-type="doi">10.1016/j.amjmed.2009.02.010</pub-id>
          <pub-id pub-id-type="medline">19486708</pub-id>
          <pub-id pub-id-type="pii">S0002-9343(09)00157-0</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>Ross</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stevenson</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Murray</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Factors that influence the implementation of e-health: a systematic review of systematic reviews (an update)</article-title>
          <source>Implement Sci</source>
          <year>2016</year>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>146</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/s13012-016-0510-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13012-016-0510-7</pub-id>
          <pub-id pub-id-type="medline">27782832</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13012-016-0510-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC5080780</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Day</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Lawson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mantri</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rabago</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lennon</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Physician moral injury in the context of moral, ethical and legal codes</article-title>
          <source>J Med Ethics</source>
          <year>2022</year>
          <volume>48</volume>
          <issue>10</issue>
          <fpage>746</fpage>
          <lpage>752</lpage>
          <pub-id pub-id-type="doi">10.1136/medethics-2021-107225</pub-id>
          <pub-id pub-id-type="medline">34290114</pub-id>
          <pub-id pub-id-type="pii">medethics-2021-107225</pub-id>
        </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>Dean</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Talbot</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dean</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Reframing clinician distress: moral injury not burnout</article-title>
          <source>Fed Pract</source>
          <year>2019</year>
          <volume>36</volume>
          <issue>9</issue>
          <fpage>400</fpage>
          <lpage>402</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31571807"/>
          </comment>
          <pub-id pub-id-type="medline">31571807</pub-id>
          <pub-id pub-id-type="pmcid">PMC6752815</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>Tawfik</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Profit</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Morgenthaler</surname>
              <given-names>TI</given-names>
            </name>
            <name name-style="western">
              <surname>Satele</surname>
              <given-names>DV</given-names>
            </name>
            <name name-style="western">
              <surname>Sinsky</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Dyrbye</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>Tutty</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>TD</given-names>
            </name>
          </person-group>
          <article-title>Physician burnout, well-being, and work unit safety grades in relationship to reported medical errors</article-title>
          <source>Mayo Clin Proc</source>
          <year>2018</year>
          <volume>93</volume>
          <issue>11</issue>
          <fpage>1571</fpage>
          <lpage>1580</lpage>
          <pub-id pub-id-type="doi">10.1016/j.mayocp.2018.05.014</pub-id>
          <pub-id pub-id-type="medline">30001832</pub-id>
          <pub-id pub-id-type="pii">S0025-6196(18)30372-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC6258067</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>Wosny</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Strasser</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Hastings</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The paradoxes of digital tools in hospitals: qualitative interview study</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e56095</fpage>
          <pub-id pub-id-type="doi">10.2196/56095</pub-id>
          <pub-id pub-id-type="medline">39008341</pub-id>
          <pub-id pub-id-type="pii">v26i1e56095</pub-id>
          <pub-id pub-id-type="pmcid">PMC11287097</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>C-P</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>H-L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>M-C</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>C-A</given-names>
            </name>
          </person-group>
          <article-title>Restricted use of copy and paste in electronic health records potentially improves healthcare quality</article-title>
          <source>Medicine (Baltimore)</source>
          <year>2022</year>
          <volume>101</volume>
          <issue>4</issue>
          <fpage>e28644</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35089204"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/MD.0000000000028644</pub-id>
          <pub-id pub-id-type="medline">35089204</pub-id>
          <pub-id pub-id-type="pii">00005792-202201280-00019</pub-id>
          <pub-id pub-id-type="pmcid">PMC8797538</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>Waisberg</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Masalkhi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kamran</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Zaman</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sarker</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Tavakkoli</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>GPT-4: a new era of artificial intelligence in medicine</article-title>
          <source>Ir J Med Sci</source>
          <year>2023</year>
          <volume>192</volume>
          <issue>6</issue>
          <fpage>3197</fpage>
          <lpage>3200</lpage>
          <pub-id pub-id-type="doi">10.1007/s11845-023-03377-8</pub-id>
          <pub-id pub-id-type="medline">37076707</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11845-023-03377-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Knitza</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hügle</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Rheumatology in the digital health era: status quo and quo vadis?</article-title>
          <source>Nat Rev Rheumatol</source>
          <year>2024</year>
          <volume>20</volume>
          <issue>12</issue>
          <fpage>747</fpage>
          <lpage>759</lpage>
          <pub-id pub-id-type="doi">10.1038/s41584-024-01177-7</pub-id>
          <pub-id pub-id-type="medline">39482466</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41584-024-01177-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sezgin</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sirrianni</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Kranz</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of a digital scribe: conversation summarization for emergency department consultation calls</article-title>
          <source>Appl Clin Inform</source>
          <year>2024</year>
          <volume>15</volume>
          <issue>3</issue>
          <fpage>600</fpage>
          <lpage>611</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/a-2327-4121"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/a-2327-4121</pub-id>
          <pub-id pub-id-type="medline">38749477</pub-id>
          <pub-id pub-id-type="pmcid">PMC11268986</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>Tierney</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Gayre</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hoberman</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mattern</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ballesca</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson Hannay</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Castilla</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Kipnis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Ambient artificial intelligence scribes: learnings after 1 year and over 2.5 million uses</article-title>
          <source>NEJM Catalyst</source>
          <year>2025</year>
          <volume>6</volume>
          <issue>5</issue>
          <pub-id pub-id-type="doi">10.1056/cat.25.0040</pub-id>
        </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>Shah</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Crowell</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Jeong</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Devon-Sand</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Delahaie</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hsia</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeffer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Physician perspectives on abient AI scribes</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>3</issue>
          <fpage>e251904</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2025.1904"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.1904</pub-id>
          <pub-id pub-id-type="medline">40126477</pub-id>
          <pub-id pub-id-type="pii">2831866</pub-id>
          <pub-id pub-id-type="pmcid">PMC11933996</pub-id>
        </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>Ma</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jeong</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Devon-Sand</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Crowell</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Delahaie</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hsia</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeffer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Ambient artificial intelligence scribes: utilization and impact on documentation time</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2025</year>
          <volume>32</volume>
          <issue>2</issue>
          <fpage>381</fpage>
          <lpage>385</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae304</pub-id>
          <pub-id pub-id-type="medline">39688515</pub-id>
          <pub-id pub-id-type="pii">7926614</pub-id>
          <pub-id pub-id-type="pmcid">PMC11756633</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
