<?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">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</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">v9i1e63902</article-id>
      <article-id pub-id-type="pmid">40117572</article-id>
      <article-id pub-id-type="doi">10.2196/63902</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>Exploring Physicians’ Dual Perspectives on the Transition From Free Text to Structured and Standardized Documentation Practices: Interview and Participant Observational Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chartash</surname>
            <given-names>David</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Golburean</surname>
            <given-names>Olga</given-names>
          </name>
          <degrees>MPhil</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Neuromedicine and Movement Science</institution>
            <institution>Faculty of Medicine and Health Sciences</institution>
            <institution>NTNU-Norwegian University of Science and Technology</institution>
            <addr-line>Elgeseter Gate 28</addr-line>
            <addr-line>Trondheim, 7030</addr-line>
            <country>Norway</country>
            <phone>47 91787389</phone>
            <email>olga.golburean@ntnu.no</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-0129-1740</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Pedersen</surname>
            <given-names>Rune</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9032-4153</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Melby</surname>
            <given-names>Line</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4507-0198</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Faxvaag</surname>
            <given-names>Arild</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6510-7306</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Neuromedicine and Movement Science</institution>
        <institution>Faculty of Medicine and Health Sciences</institution>
        <institution>NTNU-Norwegian University of Science and Technology</institution>
        <addr-line>Trondheim</addr-line>
        <country>Norway</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Norwegian Centre for E-Health Research</institution>
        <institution>University Hospital of North Norway</institution>
        <addr-line>Tromsø</addr-line>
        <country>Norway</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Department of Health Research</institution>
        <institution>SINTEF Digital</institution>
        <addr-line>Trondheim</addr-line>
        <country>Norway</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Olga Golburean <email>olga.golburean@ntnu.no</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>21</day>
        <month>3</month>
        <year>2025</year>
      </pub-date>
      <volume>9</volume>
      <elocation-id>e63902</elocation-id>
      <history>
        <date date-type="received">
          <day>4</day>
          <month>7</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>9</day>
          <month>1</month>
          <year>2025</year>
        </date>
        <date date-type="rev-recd">
          <day>17</day>
          <month>1</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>19</day>
          <month>1</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Olga Golburean, Rune Pedersen, Line Melby, Arild Faxvaag. Originally published in JMIR Formative Research (https://formative.jmir.org), 21.03.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 Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2025/1/e63902" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Clinical documentation plays a crucial role in providing and coordinating care. Despite the widespread adoption of electronic health record (EHR) systems, many end users still document clinical data in a manner similar to traditional paper-based records. To fully leverage the benefits of EHR systems, it is necessary to adopt new documentation approaches that facilitate easy access to information at the point of care and seamless exchange of information across health care facilities.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>We aimed to evaluate how the transition from an older EHR system to a cross-institutional EHR system impacts physicians’ documentation practices and gain a deeper understanding of the factors influencing their choice between free text and structured and standardized documentation methods.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A qualitative study was conducted between September 2023 and January 2024. It involved participant observations and individual semistructured interviews with physicians at a university hospital in Norway. Data were analyzed using reflexive thematic analysis.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The analysis revealed 3 main themes. First, physicians encountered challenges during the implementation phase of the new EHR system due to its complexity and their unfamiliarity with its use. However, with time, physicians gradually adopted new documentation processes. This integration or adoption primarily occurred by learning through practical experience and collaborative knowledge exchange with their peers. Second, although the implementation of the new EHR system had increased structured and standardized clinical documentation, free text remained the preferred method, with some exceptions. In addition, the fact that many physicians still relied on free-text documentation created a sense of distrust among them toward some of the standardized clinical data. Finally, the informants had mixed perceptions of Systematized Nomenclature of Medicine–Clinical Terms. Some viewed it as a more nuanced terminology system, while others found it more complex. Most informants found using templates for routine procedures beneficial as it saved time in the documentation process and ensured that all necessary parameters and documentation requirements were met.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The study findings revealed that physicians’ acceptance of new documentation processes is influenced by various social and technological factors. These factors include previous documentation experiences, perceived benefits, familiarity with the EHR system, time constraints, and user-friendliness of the system. While physicians generally have a positive attitude toward using templates for routine procedures, they often create their own templates, and data within these templates are documented in a free-text format. To address this, health care organizations should consider implementing common standardized or semistandardized templates to reduce disparities in documentation, enhance data recording, and ensure adherence to guidelines. Furthermore, to facilitate the transition to the new documentation processes, we recommend providing physicians with customized training programs and platforms for tacit knowledge exchange.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>documentation</kwd>
        <kwd>documentation practice</kwd>
        <kwd>standardized documentation</kwd>
        <kwd>structured documentation</kwd>
        <kwd>secondary use of data</kwd>
        <kwd>interoperability</kwd>
        <kwd>electronic health record</kwd>
        <kwd>EHR</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Electronic health record (EHR) systems have been advocated as means to enhance the efficiency of health care services, facilitating improved coordination and delivery of safe and evidence-based care [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. Data from an EHR system can also provide health professionals with the information they need to make informed decisions at the point of care and the opportunity to reflect on their clinical work and learn from past experiences [<xref ref-type="bibr" rid="ref3">3</xref>]. In addition, an EHR system facilitates access to data collected during clinical care, which may be used for secondary purposes (eg, research and augmenting the capabilities of clinical decision support systems) [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. Nevertheless, clinical data need to be captured in a fixed structure in order to facilitate their use [<xref ref-type="bibr" rid="ref4">4</xref>]. Health professionals play a crucial role in the documentation process, facilitating the accumulation of data in the EHR system. However, the implementation of the EHR system often results in end users still recording clinical data in a manner reminiscent of traditional paper-based records, although in a digital format, using computers and keyboards [<xref ref-type="bibr" rid="ref7">7</xref>]. Entering structured and standardized data into an EHR system can be time-consuming, and the level of acceptance among different end users can vary greatly. Health professionals, frequently constrained by time limitations, might be reluctant to assume the data entry task unless they see significant benefits [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      </sec>
      <sec>
        <title>Clinical Documentation in EHR Systems</title>
        <p>Health care systems are bound by stringent laws and regulations. In Norway, the use of electronic health data for the provision of health care services (ie, the primary use of health data) is regulated by the Patient Record Act [<xref ref-type="bibr" rid="ref10">10</xref>]. This act aims to ensure that patients receive high-quality health care by making health data available for health professionals in a quick, effective, and secure manner. Health professionals, on their side, have a duty to meet documentation requirements as outlined in the Health Personnel Act [<xref ref-type="bibr" rid="ref11">11</xref>]. This act specifically mandates that patient journals must be maintained in accordance with high professional standards, ensuring that they include pertinent and essential information about the patient and the health care services rendered. Furthermore, the journals must be easily comprehensible for other qualified health care personnel. The use of electronic health data for purposes such as statistics, public health, health surveillance, research and product development, education, or teaching (ie, the secondary use of health data) is also strictly regulated [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>The adoption of the EHR system has significantly expanded the volume of clinical data available. However, a considerable portion of these data remains underused, largely due to the dominance of unstructured documentation, such as free-text notes and narrative reports [<xref ref-type="bibr" rid="ref7">7</xref>]. It is estimated that 80% of the EHR data exist in unstructured documents [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Consequently, there is increasing pressure on health professionals to adopt structured and standardized documentation methods [<xref ref-type="bibr" rid="ref6">6</xref>]. This involves the use of standardized coding systems for data entry, the incorporation of models and terminologies such as Systematized Nomenclature of Medicine–Clinical Terms (SNOMED CT), and the use of structured forms [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Structured and standardized data encompass various patient details, including demographics, laboratory tests, height, weight, blood pressure, medications, allergies, and more [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Since structured and standardized data types are organized within a fixed structure, they can be easily analyzed using statistical or machine learning methods [<xref ref-type="bibr" rid="ref16">16</xref>]. Furthermore, data from EHR systems also play a crucial role in the realization of learning health systems, where data are captured as a by-product of care. These data are subsequently analyzed to generate new knowledge, which, in turn, informs continuous improvement and innovation in health care service delivery [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. While on the one hand, structured and standardized documentation practices are associated with enhanced quality of clinical notes [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>], on the other hand, research highlights that the adoption of the EHR system has led to increased documentation time and reduced attention to patient care [<xref ref-type="bibr" rid="ref6">6</xref>]. Moreover, structured and standardized documentation can impede expressivity in notes. Free-text documentation is crucial in health care delivery as it allows health professionals to record detailed and nuanced patient narratives. Thus, Rosenbloom et al [<xref ref-type="bibr" rid="ref22">22</xref>] advocated that health professionals should have the flexibility to decide their documentation style according to workflow needs and content specifics. Their study highlighted that structured documentation is ideal for scenarios requiring data reuse, whereas narrative documentation is suitable when data reuse is not a priority. Furthermore, Levy et al [<xref ref-type="bibr" rid="ref23">23</xref>] emphasized that health professionals encounter an excessive documentation burden when the usability of the documentation systems fails to adequately support patient care delivery. This highlights the crucial role of systems’ usability and the need to assess their impact on documentation practices.</p>
        <p>The aim of this study is to evaluate how the transition from an older EHR system to a newer cross-institutional EHR system, which enables structured and standardized documentation, impacts physicians’ documentation practices. It seeks to gain insights into the factors that impact physicians’ choice of documentation methods, such as free text or structured and standardized documentation.</p>
      </sec>
      <sec>
        <title>Theory</title>
        <p>Standardizing work processes in health care, such as implementing standardized guidelines for procedures and treatments, is regarded as a useful approach to improving the quality of health care due to its ability to improve outcomes, reduce the likelihood of errors, and eliminate unnecessary variations [<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. The increased adoption of EHR systems has led to increased interest in integrating standardized clinical tools within these systems. This includes, among others, standards pertaining to clinical documentation, encompassing what, where, and how information should be documented (eg, structured text, use of templates, and narrative text) [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref30">30</xref>]. Standardizing the use of the EHR system contributes to achieving interoperable EHR system, enabling the seamless exchange of clinical data among various health care organizations [<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. Nevertheless, the pursuit of standardization in health care, particularly in the realm of EHR systems, has proven to be challenging [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. This is due to the highly heterogeneous nature of health care, marked by the constant occurrence of unforeseen circumstances. A significant portion of health care professionals’ responsibilities cannot be strictly defined by standardized procedures alone, as a substantial amount of their work is tailored to address the unique requirements of individual patients [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. Thus, it has been suggested that providing flexibility is essential in health care work, as it enables health care professionals to customize their work to factors such as patient needs, good judgment, workflow, and prevailing circumstances [<xref ref-type="bibr" rid="ref24">24</xref>]. Cherns [<xref ref-type="bibr" rid="ref37">37</xref>] further emphasized the importance of incorporating sufficient flexibility within technical systems. This entails the ability to tailor the system according to specific local needs and adapt to evolving requirements [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. This is justifiable, as Orlikowski [<xref ref-type="bibr" rid="ref38">38</xref>] highlighted the dynamic nature of technologies, which are continually shaped by human responses to a multitude of influences, such as environmental, political, and cultural factors. Nevertheless, it is important to note that people have their own distinct viewpoints, “practice lenses” that impact how they use the systems [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref38">38</xref>], and may also rely on their own meanings and interpretations of the technology’s functions, known as “interpretative flexibility,” which may deviate from the designer’s original intentions [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Considering the aforementioned information, it is notable that the implementation of EHR systems and the standardized processes they encompass (eg, clinical documentation) extend beyond being mere technological tools. Instead, EHR systems are integral components of a sociotechnical system, which encompasses a dynamic interaction between technology, health professionals, organizational structures, and the social environment in which they are embedded [<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref43">43</xref>]. Thus, literature has previously emphasized the significance of using the sociotechnical system theory [<xref ref-type="bibr" rid="ref44">44</xref>] in the design, development, implementation, use, and evaluation of health information technology [<xref ref-type="bibr" rid="ref45">45</xref>] and applied it to examine its impact on documentation practices [<xref ref-type="bibr" rid="ref46">46</xref>].</p>
      </sec>
      <sec>
        <title>The Context</title>
        <p>Although all health care organizations in Norway use an EHR system, many of these systems are not adequately designed for structured and standardized documentation [<xref ref-type="bibr" rid="ref47">47</xref>]. The daily documentation primarily comprises unstructured notes written in free text, which makes it difficult to use for secondary purposes, such as quality improvements. Moreover, in many cases, medications are manually recorded and signed on paper-based charts before being scanned as images into the EHR system [<xref ref-type="bibr" rid="ref47">47</xref>]. According to Norwegian health authorities, health professionals lack proper access to patient health information when needed at the point of care [<xref ref-type="bibr" rid="ref48">48</xref>]. This challenge is primarily attributed to the fragmented nature of the health care systems, coupled with the insufficient integration of various information and communication technology systems [<xref ref-type="bibr" rid="ref48">48</xref>]. Thus, in 2012, the Norwegian government launched the “One citizen—one health record” initiative. Its goal is to facilitate the seamless integration and accessibility of essential health information at every stage of patient care, regardless of when or where it is required [<xref ref-type="bibr" rid="ref48">48</xref>]. As part of this initiative, the Health Platform (Helseplattformen) project was established [<xref ref-type="bibr" rid="ref49">49</xref>], with the aim to replace the existing fragmented EHR systems with an integrated solution for both primary and specialist health professionals in the entire central Norway region [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. The project selected Epic Systems Corporation as the vendor for the EHR system [<xref ref-type="bibr" rid="ref49">49</xref>].</p>
        <p>Health Platform aimed to shift toward more structured and standardized documentation of clinical data in order to achieve optimal system functionality and make data machine readable. A pivotal change within the Health Platform project is the transition from the <italic>International Classification of Diseases, 10th Revision</italic> (<italic>ICD-10</italic>) to the more comprehensive and nuanced terminology system, SNOMED CT [<xref ref-type="bibr" rid="ref52">52</xref>]. The complexity of SNOMED CT arises from a dense hierarchical structure and “is-a” relationships that link broader and more specific concepts, as explored by Abeysinghe et al [<xref ref-type="bibr" rid="ref53">53</xref>]. This allows SNOMED CT to capture nuances that provide better clinical coverage, making it more suitable for the EHR system and supporting patient care, compared to <italic>ICD</italic>, which is mainly used for diagnoses and billing [<xref ref-type="bibr" rid="ref54">54</xref>]. The lack of detail in <italic>ICD</italic> codes can lead to a loss of specificity in a clinical context, which means that rare conditions can be grouped under a single code, thus impacting the EHR system’s ability to provide accurate clinical decision support [<xref ref-type="bibr" rid="ref54">54</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design and Settings</title>
        <p>We used a descriptive qualitative research method to conduct this case study based on participant observations and individual semistructured interviews with physicians. Qualitative research methods enable researchers to delve deeply into the subject matter, providing comprehensive insights and detailed descriptions from the participants’ perspectives. Unlike quantitative methods, qualitative approaches, such as interviews and observations, excel at offering detailed explanations, particularly when investigating questions pertaining to <italic>why</italic> and <italic>how</italic> [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref55">55</xref>].</p>
        <p>We conducted this study in 1 surgical department at a large university hospital in the central Norway region, which transitioned from a facility-centered EHR system to Health Platform, the new cross-institutional EHR system (Epic Systems Corporation), in November 2022. The university hospital houses approximately 1000 beds and employs around 11,000 staff members. The surgical department includes an outpatient clinic, inpatient ward, surgical unit, and emergency room, complemented by a specialized division for pediatrics.</p>
      </sec>
      <sec>
        <title>Recruitment of Participants</title>
        <p>Participants for this study were recruited through verbal and written approaches. First, an email was sent to all physicians working within the surgical department, requesting their participation in an observational study. Second, recognizing the challenges of recruiting busy physicians, particularly during the transition to the new EHR system, the first author (OG) attended the physicians’ morning meeting to provide additional information about the project and give them the opportunity to ask direct questions about the study. The study aimed to recruit participants with varying levels of professional experience, including experienced physicians and interns, to ensure a diverse range of perspectives. After completing the observational study phase, a subsequent email invitation was sent to the same group of individuals (ie, physicians in the surgical department), inviting them to participate in individual interviews. The first author (OG) reached out to physicians interested in participating in the study to schedule a convenient time and location for their meeting. In total, 14 physicians participated in the study, and the characteristics of the participants are summarized in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Demographic characteristics of the study participants (N=14).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="300"/>
            <col width="0"/>
            <col width="670"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Characteristics</td>
                <td>Participants, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Age group (y)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>25-39</td>
                <td colspan="2">9 (64)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>≥40</td>
                <td colspan="2">5 (36)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Sex</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Female</td>
                <td colspan="2">6 (43)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Male</td>
                <td colspan="2">8 (57)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Practice (y)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>&#60;5</td>
                <td colspan="2">3 (21)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>5-15</td>
                <td colspan="2">7 (50)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>&#62;15</td>
                <td colspan="2">4 (29)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Data Collection</title>
        <sec>
          <title>Observations</title>
          <p>Participant observations occurred from September 2023 to November 2023. In total, 12 physicians were observed for a combined duration of approximately 44 hours. <xref rid="figure1" ref-type="fig">Figure 1</xref> depicts the information regarding data collection activities. The observation sessions ranged from 1 to 3 times, with each session varying in duration from 1 hour to 3 hours. The observation was conducted at the surgical department at several health care facilities where the physicians were working, including an outpatient clinic, an inpatient ward, and an emergency room. Before these observations, a taxonomy was developed to guide the observational process. It was developed based on the research question, a review of existing literature [<xref ref-type="bibr" rid="ref56">56</xref>-<xref ref-type="bibr" rid="ref58">58</xref>], and collaborative inputs from field experts (AF, LM, and RP). The primary focus during observations was on physicians’ interactions with the new EHR system, with particular attention given to their documentation practices. Throughout each observational session, the observer (OG) recorded notes, capturing both the physicians’ activities and, when feasible, engaging them in dialogue about their EHR use. Following observations, the observer supplemented these notes with additional remarks and personal reflections.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Data collection activities. EHR: electronic health record.</p>
            </caption>
            <graphic xlink:href="formative_v9i1e63902_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Interviews</title>
          <p>After the completion of the observations, individual, semistructured interviews were conducted face-to-face with the participants by the first author (OG). In total, 10 physicians were interviewed, 8 (80%) of whom had also been part of previous observations. The interviews were conducted between November 2023 and January 2024 (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The interviews lasted between 34 and 60 minutes, with an average duration of 44 (SD 9.6) minutes. The interview guide, developed based on the existing literature [<xref ref-type="bibr" rid="ref58">58</xref>-<xref ref-type="bibr" rid="ref60">60</xref>] and expert collaboration in the field, was initially outlined before the observational phase. However, following the observations, which provided in-depth insights into the physicians’ work practices with the new EHR system, the interview guide was revised to incorporate emerging, relevant questions. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> provides the interview guide. Each interview was audio recorded and transcribed verbatim by the first author (OG). The process of transcription began immediately after the first interview and was integral to the preliminary data analysis phase, which involved a thorough familiarization with the collected data. The interview phase concluded once data saturation was achieved. This happened when further interviews no longer provided any new insights or themes.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>Data were organized using NVivo (Lumivero) software [<xref ref-type="bibr" rid="ref61">61</xref>] and analyzed through a reflexive thematic analysis approach [<xref ref-type="bibr" rid="ref62">62</xref>]<italic>.</italic> The transcripts of the interviews and field notes from the observation sessions were thoroughly examined to familiarize them with the data. Then, specific codes were developed using an inductive approach, meaning that the codes were derived from the data. The initial codes were created using a semantic coding approach. These initial codes were reviewed, leading to the formation of initial themes. Throughout this process, we continuously reviewed and revised the raw data, codes, and initial themes to ensure consistency and coherence. Moreover, we conducted a 2-day workshop where authors collaboratively reviewed the preliminary themes and their associated codes. During this workshop, we used latent analyses to gain a deeper understanding of the data within the themes. Specifically, we delved into the factors that influenced physicians’ documentation practices in the new EHR system using the sociotechnical system theory [<xref ref-type="bibr" rid="ref44">44</xref>]. These factors encompassed various aspects, such as implications of learning and training in the use of EHR system, physicians’ perspectives and previous experiences with clinical documentation, familiarity with the new EHR system, and the influence of technology (new EHR system) and its user-friendliness on physicians’ documentation practices (<xref rid="figure2" ref-type="fig">Figure 2</xref>). The research team involved in the data analysis possessed diverse backgrounds that enriched the interpretation of the data. The researchers included experts in health informatics, medicine, qualitative research, and implementation science. This multidisciplinary perspective facilitated a comprehensive understanding of the complexities inherent in the data collected. Using the workshop notes, the first author (OG) further refined the themes. This phase served as the basis for drafting the initial report. The authors adhered to the SRQR (Standards for Reporting Qualitative Research) checklist [<xref ref-type="bibr" rid="ref63">63</xref>]. <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> provides the complete SRQR checklist.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Sociotechnical factors impacting physicians’ documentation practices. EHR: electronic health record.</p>
          </caption>
          <graphic xlink:href="formative_v9i1e63902_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study was registered and approved by Sikt, Norwegian Agency for Shared Services in Education and Research (project number 540255). Before conducting observations and interviews, all participants were provided with written and verbal information about the study. Written consent was individually obtained from each participant. No personally identifiable data were collected, and in cases where indirectly identifiable information was mentioned during interviews, such details were omitted from all reports, papers, and presentations. Participants in this study did not receive any form of compensation.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>Through observations and interviews, 3 main themes, with corresponding subthemes related to documentation practices, were identified (<xref rid="figure3" ref-type="fig">Figure 3</xref>). The first theme shed light on the initial challenges faced by physicians during the implementation phase, specifically their uncertainty in navigating the new EHR system and its complexity. It also showed the gradual integration of physicians into the new processes of the EHR system, primarily by learning through practical experience and collaborative knowledge exchange with their peers (peer-based learning). The second theme contemplated the influence of the new EHR system on physicians’ documentation practices. It delved into the preferred method of documentation and provided insights into the challenges and benefits associated with the implementation of the new documentation processes. In addition, it highlighted the issue of nonstandardized documentation, which in some cases leads to a sense of distrust among physicians toward standardized clinical data. The third theme delved into the perspectives of physicians regarding the adoption of the new terminology system, SNOMED CT, and their opinions on using templates for clinical data documentation.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Themes and subthemes regarding clinical documentation practices emerged from the interviews and observations. EHR: electronic health record; SNOMED CT: Systematized Nomenclature of Medicine–Clinical Terms.</p>
          </caption>
          <graphic xlink:href="formative_v9i1e63902_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>New Documentation Processes</title>
        <sec>
          <title>Uncertainty in Navigating the New EHR System and Incorporating New Documentation Processe; Complexity of the System and Insufficient Postimplementation Training</title>
          <p>Physicians encountered a learning curve while transitioning to the new EHR system, necessitating adjustments to specific documentation practices. The complexity of certain processes and the additional administrative responsibilities linked to the new system left physicians feeling unsure about how to efficiently navigate the system and, in certain cases, how to accurately document clinical data:</p>
          <disp-quote>
            <p>... you spend more time searching for the right function that you need to document correctly, and to search for information, and then maybe you are a little bit unsure about some things, you wonder if you have included everything...there is a lot of clicking to move forward; it wasn’t like that before; it used to be more like create note, write note, done, so there are quite a lot of steps to move forward [in the new EHR]; the system controls you a bit, sort of.</p>
            <attrib>Informant 10</attrib>
          </disp-quote>
          <p>Initially, many physicians were unfamiliar with the specific functionalities of the new EHR system and attempted to use and document clinical data in a similar manner as they did in the previous system. Consequently, certain informants encountered difficulties when using the new system due to its complexity and lack of familiarity with effective navigation:</p>
          <disp-quote>
            <p>I think that what we need now is to go through each workflow and make sure that everyone does it in the same way so that we can coordinate more, also that you can improve the shortcuts that exist and the ways of working efficiently so that everyone learns it because there are some who use the system very cumbersomely.</p>
            <attrib>Informant 9</attrib>
          </disp-quote>
          <p>Furthermore, informants highlighted that the training they received before the implementation of the new EHR system was not sufficient. This was mainly due to substantial modifications made to the EHR system since the training and because the training did not address their specific role. In addition, some informants mentioned that differentiating between essential and less significant aspects addressed in the training became difficult if they had not yet used the system. Most informants also believed that there was insufficient personalized training provided after the implementation, and they felt that more specific and customized training was necessary to effectively use the system’s advanced features, particularly once physicians had acquired a basic understanding of the system:</p>
          <disp-quote>
            <p>We received a lot of tips and tricks in the beginning, but then it was more about doing, surviving, staying afloat, and stabilizing ourselves a bit...having new training now would have been a much bigger help at this time than it was before...</p>
            <attrib>Informant 1</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Moving Toward the Adoption of New Documentation Processes and Learning Through Practical Experience and Peer-Based Learning</title>
          <p>On the basis of the observation sessions and interview data, it was evident that physicians were gradually adapting to new processes in the new EHR system and making changes to specific documentation practices:</p>
          <disp-quote>
            <p>When I used to admit patients, I used to write a continuous text with previous illnesses, family, and social, such as whether they lived at home or in a nursing home. I used to just list all previous illnesses, which were often taken from a previous admission journal. I have partly done it that way now as well, but there is more and more emphasis on not doing it and instead entering the information in problem lists of medical and surgical history. So, it’s a transition for me...</p>
            <attrib>Informant 10</attrib>
          </disp-quote>
          <p>This adaptation and learning occurred both through practice (actual use of the system) and knowledge sharing among colleagues (peer-based learning). The informants found it valuable to learn from experienced colleagues. Occasionally, they also organized small group meetings where these colleagues provided guidance on navigating the system effectively. However, most physicians expressed concerns about the complexity of the newly implemented EHR system, which hindered their learning process and effective use. It was emphasized that simplifying the system and eliminating unnecessary features would greatly enhance its usability.</p>
        </sec>
      </sec>
      <sec>
        <title>The Impact of the New EHR System on Clinical Documentation</title>
        <sec>
          <title>Structured and Standardized Clinical Documentation Is Increasing, and Free Text Remains the Preferred Documentation Method</title>
          <p>Compared to the previous EHR system, a greater proportion of patient information was being entered in a structured and standardized format. In certain cases, the system enforced a hard stop, making it mandatory for users to input the required standardized information. For instance, in the old EHR system, the findings and diagnosis code were described in a free-text format along with codes such as <italic>ICD-10</italic>, whereas in the new EHR system, these aspects were documented in a standardized format using SNOMED CT. Another example was the transition from paper-based to digital documentation for ordering surgical procedures. As a result, numerous tasks were performed electronically, eliminating the reliance on paper, and more patient health information was documented in a structured and standardized format:</p>
          <disp-quote>
            <p>Well, then [previous EHR] there was nothing standardized, so...no, no, then I manually entered the procedure code and diagnosis code, and the medications were mostly just copied from one note to the next, and then you hoped that what you had copied over was correct.</p>
            <attrib>Informant 6</attrib>
          </disp-quote>
          <p>Although structured and standardized documentation has become more prevalent, many physicians still preferred using free text whenever possible. This preference was primarily due to the flexibility and time-saving nature of free-text documentation. It was also easier for physicians to provide a comprehensive overview of a patient’s medical condition through free-text notes. Furthermore, some informants highlighted their preference for reading high-quality free-text notes as they provided a better understanding of the patient’s condition compared to information presented in templates or diagnosis codes:</p>
          <disp-quote>
            <p>The only way I manage to get an overview of the medical history of a patient is basically if someone has written something reasonable in a journal note.</p>
            <attrib>Informant 4</attrib>
          </disp-quote>
          <p>Moreover, physicians were accustomed to free-text documentation, and transitioning to structured and standardized formats required additional time and training to ensure accuracy.</p>
          <p>Structured and standardized documentation, on the other hand, was often perceived as time-consuming, more challenging, and sometimes misaligned with physicians’ workflows. In addition, one physician added that he did not see the benefits of adopting a more intricate approach, such as standardized documentation:</p>
          <disp-quote>
            <p>Yes, no, I need to see the benefit of doing it in a more complicated way, then I might have chosen a different way of documentation than free text. So far, I haven’t been able to see the major benefit, so that’s why I document in free text...</p>
            <attrib>Informant 2</attrib>
          </disp-quote>
          <p>Nonetheless, some informants acknowledged that reading and finding free-text documentation could be challenging in certain situations, particularly when there were numerous notes present. In such cases, important information might become obscured or go unnoticed, whereas standardized information automatically appeared when reviewing the patient journal.</p>
        </sec>
        <sec>
          <title>Lack of Standardized Documentation and Distrust Toward Standardized Data</title>
          <p>On the basis of our findings, the preference for free-text documentation method was often accompanied by a culture of distrust among physicians toward standardized data available in the EHR system. For instance, the new EHR system integrated several processes related to clinical documentation that were not present in the previous EHR system. These included processes such as the documentation of the “problem list,” which is an overview of medical conditions that might impact the health care given to the patient, and “medical history,” which lists the conditions that have been resolved and no longer impact patients’ health or treatment. These conditions, if documented, were automatically displayed when reviewing patient journals without the need to access journal notes. However, physicians were uncertain about the accuracy of these standardized data and sometimes could not rely on it, as they were aware that many of their colleagues did not adhere to standardized documentation:</p>
          <disp-quote>
            <p>It depends on how many people enter standardized data, so I feel that I can’t rely on what is stated there. One can enter previous illnesses and medical history, but it is rarely done. So, then, the patient looks healthy on paper, but there are many illnesses, as you can find in the old journal system.</p>
            <attrib>Informant 4</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Reduced Need for Double Documentation</title>
          <p>In certain situations, physicians favored structured and standardized documentation; for instance, in the new EHR system, they transitioned from paper-based to digital documentation when ordering surgical procedures. By adhering to structured and standardized documentation during the preoperative phase, they could save time in the postoperative phase, as some of the information was automatically filled in the postoperative template, eliminating redundant documentation. As a result, physicians recognized the benefits of using structured and standardized documentation for frequently performed routine procedures:</p>
          <disp-quote>
            <p>It is to some extent a bit easier [postoperative documentation] because all the information I enter beforehand also appears in the postoperative description afterwards, so before, I used to manually write in codes and bleeding amount, for example, but all of this is now automatically included in the postoperative description, so actually, writing the postoperative description afterwards is easier.</p>
            <attrib>Informant 8</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Medication Reconciliation and Medication Ordering Being Complex and Time-Consuming</title>
          <p>With the implementation of the new EHR system, physicians transitioned from manually recording medications on paper-based charts to electronically documenting them in a standardized format. The informants expressed their frustration and difficulties with the current medication reconciliation process, ordering and administering medicines, and inaccuracies in the medication list. This frustration was particularly evident during patient admission and discharge, as there were numerous medications to reconcile. However, while some informants acknowledged the challenges of entering and managing medication reconciliation in the new EHR system compared to the previous system, they also emphasized the potential for mitigating patient risk. Moreover, some informants expressed contentment with the shift from paper charts to electronic charts for medication lists. Conversely, certain individuals contended that this process was demanding and could potentially increase patient risk:</p>
          <disp-quote>
            <p>I find the medication lists to be a bit tangled and unclear, especially when you have to discharge the patient and know what they are actually on, I always feel like there is something that gets overlooked, some medications that are missing or others that have been included but shouldn’t have been, so, the medication lists are challenging.</p>
            <attrib>Informant 1</attrib>
          </disp-quote>
          <p>Furthermore, it was observed that, in some cases, physicians who encountered difficulties with medication ordering or the medication reconciliation process sought assistance from colleagues who were more proficient in using the system.</p>
        </sec>
      </sec>
      <sec>
        <title>Structured and Standardized Clinical Documentation: SNOMED CT and the Use of Templates</title>
        <sec>
          <title>SNOMED CT: More Nuanced or More Complex Terminology System?</title>
          <p>The transition from <italic>ICD-10</italic> to SNOMED CT for documenting patient health conditions was perceived by some informants as challenging and by others as a more nuanced diagnostic system. Challenges usually arose due to difficulties associated with finding the correct diagnosis, as physicians were presented with multiple alternatives when starting to write the name of the diagnosis. In addition, sometimes physicians could not find the diagnosis they needed. When diagnosing with SNOMED CT, physicians could specify the location of a medical condition using the SNOMED CT code:</p>
          <disp-quote>
            <p>...in ICD, there is no difference between right and left, or bilaterally, whereas in SNOMED it is easier to...there, the diagnosis code can already indicate differences between right and left, and bilaterally, so it is potentially that I write right and left in the diagnosis code, which I did not do before...</p>
            <attrib>Informant 7</attrib>
          </disp-quote>
          <p>However, in some cases, it was not possible to do this for certain conditions. For instance, during one of the observations, it was noted that when the physician was documenting the diagnosis of deep subfascial lipoma, the physician could not specify the location of the lipoma in SNOMED CT. As a solution, the physician noted the location in the daily notes. The physician pointed out that this information could be essential, especially for surgeons. In addition, the physician mentioned that they could specify the location for a “general” lipoma but not for a subfascial lipoma.</p>
          <p>Nonetheless, some informants perceived SNOMED CT as a more nuanced terminology system. Furthermore, SNOMED CT eliminated the need for physicians to commit to memorizing the precise code linked to a specific diagnosis. Instead, they could search for a broader term related to the diagnosis they intended to document. Subsequently, they were presented with multiple alternative options, allowing them to choose the most fitting one.</p>
          <p>It is important to note that, in numerous cases, most physicians relied on <italic>ICD-10</italic> codes to identify the corresponding SNOMED CT diagnosis.</p>
        </sec>
        <sec>
          <title>Use of Templates: Both Limitation and Means of Maintaining Continuity and Quality Assurance</title>
          <p>Most informants emphasized the benefits of using templates to document routine procedures, such as the most frequently performed surgeries. They believed that this approach saved time, and, for some informants, it helped them remember all the necessary parameters and documentation requirements:</p>
          <disp-quote>
            <p>It goes faster because there is already a lot of text that is already there, and then you just need to fill in the right and left, how long are the screws, what type of plate was used, what kind of things...and the rehabilitation afterward, is it six weeks, or eight weeks...</p>
            <attrib>Informant 7</attrib>
          </disp-quote>
          <p>In addition, it could serve as a checklist for each step involved in a procedure. Many informants had created their own templates, with some developing up to 20 templates for frequently executed operations. However, some of the informants also mentioned that it took time to create these templates properly, so they relied on templates designed by their colleagues. It was also noted that, despite being in a template, these data were not searchable because they were written in free-text format.</p>
          <p>Conversely, the informants highlighted that the use of structured and standardized templates for nonstandardized procedures was viewed as both time-consuming and ineffective. It was mentioned that by using a standardized template, physicians might end up documenting unnecessary information, thereby complicating the clinical workflow, particularly during hectic days.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study provides insights into physicians’ documentation practices after they transitioned from an older EHR system to a cross-institutional EHR system, which enables standardized and structured documentation. This transition necessitated physicians to change their documentation habits to some extent, resulting in more clinical data being recorded in a structured and standardized format. However, the degree of acceptance toward new documentation processes is influenced by a range of social and technological factors.</p>
        <p>First, according to the study participants, training in system use and ongoing technical support were of utmost importance, particularly after implementing the EHR:</p>
        <disp-quote>
          <p>We received a lot of tips and tricks in the beginning, but then it was more about doing, surviving, staying afloat, and stabilizing ourselves a bit...having new training now would have been a much bigger help at this time than it was before...</p>
          <attrib>Informant 1</attrib>
        </disp-quote>
        <p>The importance of training has been well-documented in previous research [<xref ref-type="bibr" rid="ref64">64</xref>-<xref ref-type="bibr" rid="ref67">67</xref>]. However, most of the attention and resources allocated for training tend to be centered on the pre–go-live phase and the initial implementation stage of the EHR system, with limited support available for an extended period after the go-live phase and for system updates [<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. In addition, it has been noted that users may feel overwhelmed during initial training and prioritize familiarizing themselves with the fundamental aspects of the system rather than striving to use it efficiently [<xref ref-type="bibr" rid="ref68">68</xref>]. This concern was also emphasized by the informants in our study. Moreover, peer-based learning, where physicians are taught by their expert peers in the use of the EHR system, was deemed beneficial. This suggests that acquiring knowledge from fellow experts could prove more advantageous, as these peers possess a deep understanding of the physicians’ workflows and the specific challenges they face when using the system. Peer-based learning has also been observed when physicians use the templates created by their colleagues. Hence, it can be advantageous to create platforms where physicians can share tacit knowledge, enabling them to mutually benefit from their expertise in effectively using the system and implementing best practices for documentation. Providing additional training in documentation practices should be considered, particularly during the transition to the new EHR system, which necessitates changes in physicians’ documentation practices. This training becomes even more significant considering the alarming statistics from a study conducted in Norway. The study, which encompassed 14 hospitals, revealed that in 2003, an incorrect main diagnosis code was assigned in 37.8% of hospital stays, and in 2008, in 36.2% of hospital stays [<xref ref-type="bibr" rid="ref47">47</xref>]. According to physicians working in these hospitals, the main factors contributing to this issue were challenging code systems (59%) and inadequate training (50%) [<xref ref-type="bibr" rid="ref70">70</xref>]. The significance of education and ongoing training in good documentation practices as well as its contribution to achieving a learning health system, has been emphasized in numerous research studies [<xref ref-type="bibr" rid="ref71">71</xref>-<xref ref-type="bibr" rid="ref75">75</xref>].</p>
        <p>Second, in conjunction with the aforementioned first factor, physicians found the transition to the new EHR system to be challenging. The challenge stems from the complex navigation needed to find and execute specific tasks, the overwhelming amount of information in the EHR system, and the inefficient user interface. Furthermore, physicians’ past recording habits in older EHR systems can impact their documentation practices in the new EHR system. As pointed out by Orlikowski [<xref ref-type="bibr" rid="ref38">38</xref>], when people use technology, “people also draw on their skills, power, knowledge, assumptions, and expectations about the technology and its use, influenced typically by training, communication, and previous experiences” [<xref ref-type="bibr" rid="ref76">76</xref>]. Given that physicians have established workflows in the previous system, adjusting to new processes in the new EHR system might hinder their adaptability and work efficiency. This finding aligns with previous research conducted by Joukes et al [<xref ref-type="bibr" rid="ref77">77</xref>], who identified that the preimplementation circumstances played a significant role in shaping the perceived advantages of implementing a new EHR system with structured and standardized clinical data recording. Specifically, the authors emphasized that the perceived impact of the implementation varied depending on whether users were transitioning from older EHR systems or paper-based records. In a paper-based record center, the implementation yielded positive perceived effects on EHR use, data quality, and data reuse. However, in a center that had previously used an EHR system, the perceived effects were predominantly negative or neutral. The authors further highlighted that individuals with previous exposure to EHR systems tended to draw comparisons between the new system and their old one, thereby potentially recognizing that certain tasks were accomplished more efficiently in the former system [<xref ref-type="bibr" rid="ref77">77</xref>].</p>
        <p>While the adoption of the new EHR system has led to an increase in structured and standardized data recording, it is often not a decision made by physicians but rather an imposition by the new system and health organization. In certain cases, the structured and standardized documentation does not align with physicians’ traditional workflow; therefore, it takes more time compared to free-text documentation. Moreover, physicians occasionally experience uncertainty and difficulties regarding the correct way to document structured and standardized data or question their necessity. This may potentially lead to inconsistencies in data recording. Data that could be standardized may instead be documented in a free-text format, and when faced with time constraints, physicians may use work-arounds, such as quickly clicking through to proceed further. This practice might also explain physicians’ distrust toward some of the standardized clinical data available in the EHR system, such as problem lists and medical history. One advantage of the problem list and medical history is that these remain visible to physicians whenever they access patient records, without the need to open journal notes. While this provides better information at the point of care, the problem lists and medical history lose their advantage if physicians fail to document or update it or if they lack trust in the accuracy and reliability of this information. Moreover, the prevalent reliance of physicians on the <italic>ICD-10</italic> codes to identify the corresponding SNOMED CT codes may undermine the advantages of using a more comprehensive terminology system, SNOMED CT. This reliance can lead to loss of clinical detail and mapping inaccuracies. This practice indicates a discrepancy between the physicians’ mental models (understanding and reasoning about systems) and the designer’s conceptual model (how the system is intended to be used) [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref79">79</xref>]. Mental models, derived from a range of factors, including experiences, knowledge, and perception, have been widely applied in the field of human-computer interaction research [<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref80">80</xref>]. Gaining an understanding of physicians’ mental models can be important for effectively optimizing the system and tailoring training in documentation practices in the new EHR system. The greater the disparity between the designer’s conceptual model and the user’s mental model, the more challenging it becomes for individuals to effectively use the system [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref79">79</xref>]. Furthermore, this emphasizes the need to distinguish between technologies as artifacts and technologies in practice (how technology is actually used rather than solely focusing on the technology itself), as it is only through effective use that technology can impact productivity [<xref ref-type="bibr" rid="ref38">38</xref>]. Consequently, when enhancing technology, it becomes vital to consider sociotechnical factors, which, in turn, necessitates the technology to possess sufficient flexibility in order to be customized according to specific local needs and evolving requirements [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. Moreover, Rosenbloom et al [<xref ref-type="bibr" rid="ref22">22</xref>] have underscored the significance of offering flexibility in the documentation processes, as they are highly valued and essential for health care professionals. By using free-text documentation, health care professionals can document intricate and nuanced details about a patient, which can also prove to be more valuable for subsequent health care professionals taking over the patient’s care [<xref ref-type="bibr" rid="ref22">22</xref>]. Some of our study participants have also emphasized that reading high-quality free-text journal notes can provide them with more crucial information compared to solely reviewing standardized or structured data:</p>
        <disp-quote>
          <p>The only way I manage to get an overview of the medical history of a patient is basically if someone has written something reasonable in a journal note.</p>
          <attrib>Informant 4</attrib>
        </disp-quote>
        <p>Having the right balance between standardization and flexibility in documentation processes is crucial, particularly in situations where unforeseen clinical findings or unexpected circumstances arise [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
        <p>According to the study participants, most physicians have a positive attitude toward using templates for documenting routine procedures:</p>
        <disp-quote>
          <p>It goes faster [using templates] because there is already a lot of text that is already there, and then you just need to fill in the right and left, how long are the screws, what type of plate was used, what kind of things...and the rehabilitation afterward, is it six weeks, or eight weeks...</p>
          <attrib>Informant 7</attrib>
        </disp-quote>
        <p>While certain physicians have created their own templates for frequently conducted surgeries, others depend on templates designed by their peers. However, the information contained within these templates is recorded in a free-text format. As a result, these data are not conducive to analysis using statistical or machine learning techniques. Moreover, when physicians develop their own templates for commonly performed surgeries, it can result in inconsistencies in documentation and potential omissions of critical data that need to be documented. On the other hand, this behavior might be elucidated through the analysis of physician-patient dialogues in Norwegian general practice by Nessa [<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref82">82</xref>]. His research emphasized that these conversations were a fundamental aspect of a physician’s work, encompassing rich narratives and certain elements such as context and emotional tone [<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref82">82</xref>]. Such complexities may be challenging to capture within a standardized template and encoded data. Thus, adhering strictly to encoded data and standardized templates implied by the organization may impose a semiotic burden on physicians, requiring them to exert considerable mental effort to fit complex narratives into standardized templates. The attitudes of health care professionals toward structured and standardized documentation may also depend on their perception of the benefits it provides [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref83">83</xref>]. Our study participants also highlighted this aspect (eg, saving time in postoperative documentation), suggesting that physicians may view the implementation of standardized or semistandardized templates for commonly performed procedures, developed in collaboration with physicians and following established guidelines, as a positive step. Moreover, this approach could potentially minimize variations in clinical documentation. This approach might also enable more data to be consistently recorded in a standardized format and enhance guideline compliance. Several studies have shown that the use of templates improves the accuracy of documentation [<xref ref-type="bibr" rid="ref84">84</xref>-<xref ref-type="bibr" rid="ref86">86</xref>]. For instance, Thomson et al [<xref ref-type="bibr" rid="ref85">85</xref>] demonstrated the advantages of using a standardized operative note template adhering to established guidelines. This implementation led to enhanced documentation quality and a decrease in the missing data.</p>
      </sec>
      <sec>
        <title>Limitations and Future Research</title>
        <p>One limitation of our study is that it involved a limited number of physicians, and data were collected from only 1 hospital. Therefore, the findings of this study may only reflect physicians’ perspectives working within this specific context. Nonetheless, we have made an effort to gather information on documentation practices that can be applied more broadly. Specifically, our focus was on understanding documentation practices when physicians transition from an older EHR system to a new EHR system that facilitates structured and standardized documentation. In addition, we aimed to identify the factors influencing physicians’ choice of documentation methods, such as free text and standardized documentation, regardless of the EHR system they use. Thus, our findings may have relevance beyond the specific organization and the EHR system used in this study, providing insights that can be applied to a wider context.</p>
        <p>Moreover, although it is evident that the implementation of the new EHR system has increased the amount of clinical data recorded in a standardized format, our study did not objectively evaluate either the quality of these data (eg, accuracy and completeness) or their effectiveness for secondary uses. Consequently, future research should aim to objectively assess the quality of the data. Furthermore, additional investigations could delve into the perceived data quality from the perspectives of individuals using the data from the new EHR system for secondary purposes, such as quality assurance. This would help determine whether the transition to a more standardized EHR system has positively impacted the use of these data for secondary purposes.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The findings of this study identified that physicians’ acceptance of new documentation processes is influenced by a range of social and technological factors. These factors include physicians’ past experiences with documentation, perceived benefits, familiarity with the EHR system, and time constraints, all of which can impact their choice of documentation methods. Furthermore, it is important to consider the user-friendliness of the EHR system and how well the documentation processes align with physicians’ workflows. To facilitate the transition to a new EHR system, health care organizations should provide tailored training programs on documentation practices. This is particularly crucial after the implementation of the new system. In addition, it would be advantageous to establish platforms that allow physicians to exchange tacit knowledge and expertise on effectively using the system. Moreover, physicians highly value flexibility in clinical documentation. Therefore, health care organizations should consider implementing standardized documentation processes that also align with physicians’ preferences and allow them some flexibility in the documentation process. For instance, introducing common standardized or semistandardized templates for routine procedures, developed in collaboration with physicians, could potentially minimize disparities in clinical documentation, ensure the consistent recording of data, and improve adherence to guidelines.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Semistructured interview guide.</p>
        <media xlink:href="formative_v9i1e63902_app1.docx" xlink:title="DOCX File , 19 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>SRQR (Standards for Reporting Qualitative Research) checklist.</p>
        <media xlink:href="formative_v9i1e63902_app2.docx" xlink:title="DOCX File , 27 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">ICD-10</term>
          <def>
            <p>International Classification of Diseases, 10th Revision</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">SNOMED CT</term>
          <def>
            <p>Systematized Nomenclature of Medicine–Clinical Terms</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">SRQR</term>
          <def>
            <p>Standards for Reporting Qualitative Research</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to extend their gratitude to the physicians for their time commitment in sharing their experiences and providing insightful perspectives on the use of the new electronic health record system and documentation practices. This study was funded by the Liaison Committee between the Central Norway Regional Health Authority and the Norwegian University of Science and Technology.</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The datasets generated or analyzed during this study are not publicly available to protect participant privacy but are available from the corresponding author on reasonable request.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>OG, AF, LM, and RP conceptualized and designed the study. OG conducted data collection and performed the initial data analyses. AF, LM, and RP contributed to the analyses and interpretation of the data. OG wrote the initial draft of the manuscript. All authors performed critical revisions of the paper and contributed to the final version of the manuscript. All authors have reviewed and approved the submission of the paper in its current form.</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>Gatiti</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ndirangu</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mwangi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mwanzu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ramadhani</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Enhancing healthcare quality in hospitals through electronic health records: a systematic review</article-title>
          <source>J Health Inform Dev Ctries</source>
          <year>2021</year>
          <month>11</month>
          <day>02</day>
          <volume>15</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>25</lpage>
        </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>Kruse</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Mileski</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vijaykumar</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Viswanathan</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Suskandla</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Chidambaram</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Impact of electronic health records on long-term care facilities: systematic review</article-title>
          <source>JMIR Med Inform</source>
          <year>2017</year>
          <month>09</month>
          <day>29</day>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>e35</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2017/3/e35/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.7958</pub-id>
          <pub-id pub-id-type="medline">28963091</pub-id>
          <pub-id pub-id-type="pii">v5i3e35</pub-id>
          <pub-id pub-id-type="pmcid">PMC5640822</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>Janssen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kay</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Talic</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pusic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Birnbaum</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cavalcanti</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gasevic</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Electronic health records that support health professional reflective practice: a missed opportunity in digital health</article-title>
          <source>J Healthc Inform Res</source>
          <year>2023</year>
          <month>01</month>
          <day>20</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>375</fpage>
          <lpage>84</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36744083"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s41666-022-00123-0</pub-id>
          <pub-id pub-id-type="medline">36744083</pub-id>
          <pub-id pub-id-type="pii">123</pub-id>
          <pub-id pub-id-type="pmcid">PMC9892400</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>Capurro</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yetisgen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Eaton</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Black</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Tarczy-Hornoch</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Availability of structured and unstructured clinical data for comparative effectiveness research and quality improvement: a multisite assessment</article-title>
          <source>EGEMS (Wash DC)</source>
          <year>2014</year>
          <month>07</month>
          <day>11</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>1079</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25848594"/>
          </comment>
          <pub-id pub-id-type="doi">10.13063/2327-9214.1079</pub-id>
          <pub-id pub-id-type="medline">25848594</pub-id>
          <pub-id pub-id-type="pii">egems1079</pub-id>
          <pub-id pub-id-type="pmcid">PMC4371483</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Olsen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Aisner</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>McGinnis</surname>
              <given-names>J</given-names>
            </name>
            <collab>Institute of Medicine (US) Roundtable on Evidence-Based Medicine</collab>
          </person-group>
          <source>The Learning Healthcare System: Workshop Summary</source>
          <year>2007</year>
          <publisher-loc>Washington, DC</publisher-loc>
          <publisher-name>National Academies Press</publisher-name>
        </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>Joukes</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Abu-Hanna</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>de Keizer</surname>
              <given-names>NF</given-names>
            </name>
          </person-group>
          <article-title>Time spent on dedicated patient care and documentation tasks before and after the introduction of a structured and standardized electronic health record</article-title>
          <source>Appl Clin Inform</source>
          <year>2018</year>
          <month>01</month>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>46</fpage>
          <lpage>53</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29342479"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0037-1615747</pub-id>
          <pub-id pub-id-type="medline">29342479</pub-id>
          <pub-id pub-id-type="pmcid">PMC5801881</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>Ebbers</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Takes</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Smeele</surname>
              <given-names>LE</given-names>
            </name>
            <name name-style="western">
              <surname>Kool</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>van den Broek</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Dirven</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The implementation of a multidisciplinary, electronic health record embedded care pathway to improve structured data recording and decrease electronic health record burden</article-title>
          <source>Int J Med Inform</source>
          <year>2024</year>
          <month>04</month>
          <volume>184</volume>
          <fpage>105344</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(24)00007-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2024.105344</pub-id>
          <pub-id pub-id-type="medline">38310755</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(24)00007-8</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>Bush</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Kuelbs</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ryu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Chiang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Structured data entry in the electronic medical record: perspectives of pediatric specialty physicians and surgeons</article-title>
          <source>J Med Syst</source>
          <year>2017</year>
          <month>05</month>
          <volume>41</volume>
          <issue>5</issue>
          <fpage>75</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28324321"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-017-0716-5</pub-id>
          <pub-id pub-id-type="medline">28324321</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-017-0716-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC5510605</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>Gilbert</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Physician data entry: providing options is essential</article-title>
          <source>Health Data Manag</source>
          <year>1998</year>
          <month>09</month>
          <volume>6</volume>
          <issue>9</issue>
          <fpage>84</fpage>
          <lpage>6, 88, 90-2</lpage>
          <pub-id pub-id-type="medline">10185232</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>Lov om behandling av helseopplysninger ved ytelse av helsehjelp (pasientjournalloven)</article-title>
          <source>Lovdata</source>
          <year>2015</year>
          <access-date>2024-06-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://lovdata.no/dokument/NL/lov/2014-06-20-42">https://lovdata.no/dokument/NL/lov/2014-06-20-42</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <article-title>Lov om helsepersonell m.v. (helsepersonelloven)</article-title>
          <source>Lovdata</source>
          <access-date>2024-06-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://lovdata.no/dokument/NL/lov/1999-07-02-64/KAPITTEL_8#KAPITTEL_8">https://lovdata.no/dokument/NL/lov/1999-07-02-64/KAPITTEL_8#KAPITTEL_8</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <article-title>Lov om behandling av personopplysninger (personopplysningsloven)</article-title>
          <source>Lovdata</source>
          <year>2018</year>
          <access-date>2024-06-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://lovdata.no/dokument/NL/lov/2018-06-15-38">https://lovdata.no/dokument/NL/lov/2018-06-15-38</ext-link>
          </comment>
        </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>Post</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Burningham</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Halwani</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record data in cancer learning health systems: challenges and opportunities</article-title>
          <source>JCO Clin Cancer Inform</source>
          <year>2022</year>
          <month>03</month>
          <volume>6</volume>
          <fpage>e2100158</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35353547"/>
          </comment>
          <pub-id pub-id-type="doi">10.1200/CCI.21.00158</pub-id>
          <pub-id pub-id-type="medline">35353547</pub-id>
          <pub-id pub-id-type="pmcid">PMC9005105</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>Kong</surname>
              <given-names>HJ</given-names>
            </name>
          </person-group>
          <article-title>Managing unstructured big data in healthcare system</article-title>
          <source>Healthc Inform Res</source>
          <year>2019</year>
          <month>01</month>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>2</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30788175"/>
          </comment>
          <pub-id pub-id-type="doi">10.4258/hir.2019.25.1.1</pub-id>
          <pub-id pub-id-type="medline">30788175</pub-id>
          <pub-id pub-id-type="pmcid">PMC6372467</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>Joukes</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>de Bruijne</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>de Keizer</surname>
              <given-names>NF</given-names>
            </name>
            <name name-style="western">
              <surname>Abu-Hanna</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Development and validation of a model for the adoption of structured and standardised data recording among healthcare professionals</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2018</year>
          <month>06</month>
          <day>28</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>54</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-018-0640-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-018-0640-8</pub-id>
          <pub-id pub-id-type="medline">29954388</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-018-0640-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC6027789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>A survey of data mining technology on electronic medical records</article-title>
          <source>Proceedings of the IEEE 19th International Conference on e-Health Networking, Applications and Services</source>
          <year>2017</year>
          <conf-name>HealthCom 2017</conf-name>
          <conf-date>October 12-15, 2017</conf-date>
          <conf-loc>Dalian, China</conf-loc>
          <pub-id pub-id-type="doi">10.1109/HealthCom.2017.8210774</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>Tayefi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ngo</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chomutare</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Dalianis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Salvi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Budrionis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Godtliebsen</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Challenges and opportunities beyond structured data in analysis of electronic health records</article-title>
          <source>WIREs Comput Stat</source>
          <year>2021</year>
          <month>02</month>
          <day>14</day>
          <volume>13</volume>
          <issue>6</issue>
          <fpage>e1549</fpage>
          <pub-id pub-id-type="doi">10.1002/wics.1549</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>Seid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hartley</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Margolis</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>A science of collaborative learning health systems</article-title>
          <source>Learn Health Syst</source>
          <year>2021</year>
          <month>06</month>
          <day>01</day>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>e10278</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34277944"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/lrh2.10278</pub-id>
          <pub-id pub-id-type="medline">34277944</pub-id>
          <pub-id pub-id-type="pii">LRH210278</pub-id>
          <pub-id pub-id-type="pmcid">PMC8278442</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>Zafar</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Beck</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Chirumbolo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Haralson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rich</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Margolis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hartley</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A regional learning health system of congregate care facilities for COVID-19 response</article-title>
          <source>Learn Health Syst</source>
          <year>2024</year>
          <month>01</month>
          <day>24</day>
          <volume>8</volume>
          <issue>3</issue>
          <fpage>e10407</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1002/lrh2.10407"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/lrh2.10407</pub-id>
          <pub-id pub-id-type="medline">39036529</pub-id>
          <pub-id pub-id-type="pii">LRH210407</pub-id>
          <pub-id pub-id-type="pmcid">PMC11257048</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>Ebbers</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kool</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>Smeele</surname>
              <given-names>LE</given-names>
            </name>
            <name name-style="western">
              <surname>Dirven</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>den Besten</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Karssemakers</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Verhoeven</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Herruer</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>van den Broek</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Takes</surname>
              <given-names>RP</given-names>
            </name>
          </person-group>
          <article-title>The impact of structured and standardized documentation on documentation quality; a multicenter, retrospective study</article-title>
          <source>J Med Syst</source>
          <year>2022</year>
          <month>05</month>
          <day>27</day>
          <volume>46</volume>
          <issue>7</issue>
          <fpage>46</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35618978"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-022-01837-9</pub-id>
          <pub-id pub-id-type="medline">35618978</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-022-01837-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC9135789</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>Vuokko</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mäkelä-Bengs</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hyppönen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lindqvist</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Doupi</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Impacts of structuring the electronic health record: results of a systematic literature review from the perspective of secondary use of patient data</article-title>
          <source>Int J Med Inform</source>
          <year>2017</year>
          <month>01</month>
          <volume>97</volume>
          <fpage>293</fpage>
          <lpage>303</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2016.10.004</pub-id>
          <pub-id pub-id-type="medline">27919387</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(16)30219-2</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>Rosenbloom</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Denny</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lorenzi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Stead</surname>
              <given-names>WW</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>KB</given-names>
            </name>
          </person-group>
          <article-title>Data from clinical notes: a perspective on the tension between structure and flexible documentation</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2011</year>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>181</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/21233086"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.2010.007237</pub-id>
          <pub-id pub-id-type="medline">21233086</pub-id>
          <pub-id pub-id-type="pii">jamia.2010.007237</pub-id>
          <pub-id pub-id-type="pmcid">PMC3116264</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Levy</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Withall</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Mishuris</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Tiase</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Diamond</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Douthit</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Grabowska</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>RY</given-names>
            </name>
            <name name-style="western">
              <surname>Moy</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sengstack</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Adler-Milstein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Detmer</surname>
              <given-names>DE</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>KB</given-names>
            </name>
            <name name-style="western">
              <surname>Cimino</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Corley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenbloom</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Cato</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rossetti</surname>
              <given-names>SC</given-names>
            </name>
          </person-group>
          <article-title>Defining documentation burden (DocBurden) and excessive DocBurden for all health professionals: a scoping review</article-title>
          <source>Appl Clin Inform</source>
          <year>2024</year>
          <month>10</month>
          <volume>15</volume>
          <issue>5</issue>
          <fpage>898</fpage>
          <lpage>913</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/a-2385-1654"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/a-2385-1654</pub-id>
          <pub-id pub-id-type="medline">39137903</pub-id>
          <pub-id pub-id-type="pmcid">PMC11524753</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sinsky</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Bavafa</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Beasley</surname>
              <given-names>JW</given-names>
            </name>
          </person-group>
          <article-title>Standardization vs customization: finding the right balance</article-title>
          <source>Ann Fam Med</source>
          <year>2021</year>
          <volume>19</volume>
          <issue>2</issue>
          <fpage>171</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.annfammed.org/cgi/pmidlookup?view=long&#38;pmid=33685879"/>
          </comment>
          <pub-id pub-id-type="doi">10.1370/afm.2654</pub-id>
          <pub-id pub-id-type="medline">33685879</pub-id>
          <pub-id pub-id-type="pii">19/2/171</pub-id>
          <pub-id pub-id-type="pmcid">PMC7939702</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>Kriznik</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Lamé</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Dixon-Woods</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Challenges in making standardisation work in healthcare: lessons from a qualitative interview study of a line-labelling policy in a UK region</article-title>
          <source>BMJ Open</source>
          <year>2019</year>
          <month>11</month>
          <day>27</day>
          <volume>9</volume>
          <issue>11</issue>
          <fpage>e031771</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=31780591"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2019-031771</pub-id>
          <pub-id pub-id-type="medline">31780591</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2019-031771</pub-id>
          <pub-id pub-id-type="pmcid">PMC6887013</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>Wears</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Standardisation and its discontents</article-title>
          <source>Cogn Technol Work</source>
          <year>2015</year>
          <month>02</month>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>89</fpage>
          <lpage>94</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25667566"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10111-014-0299-6</pub-id>
          <pub-id pub-id-type="medline">25667566</pub-id>
          <pub-id pub-id-type="pmcid">PMC4319563</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>Brunner</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cannedy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McCoy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hamilton</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Shelton</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Software is policy: electronic health record governance and the implications of clinical standardization</article-title>
          <source>J Gen Intern Med</source>
          <year>2023</year>
          <month>10</month>
          <volume>38</volume>
          <issue>Suppl 4</issue>
          <fpage>949</fpage>
          <lpage>55</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37798574"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-023-08280-7</pub-id>
          <pub-id pub-id-type="medline">37798574</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11606-023-08280-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC10593671</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>Bansler</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <article-title>Challenges in user-driven optimization of EHR: a case study of a large epic implementation in Denmark</article-title>
          <source>Int J Med Inform</source>
          <year>2021</year>
          <month>04</month>
          <volume>148</volume>
          <fpage>104394</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2021.104394</pub-id>
          <pub-id pub-id-type="medline">33485217</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(21)00020-4</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>Koh</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Improving clinical documentation: introduction of electronic health records in paediatrics</article-title>
          <source>BMJ Open Qual</source>
          <year>2021</year>
          <month>02</month>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>e000918</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopenquality.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33589503"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjoq-2020-000918</pub-id>
          <pub-id pub-id-type="medline">33589503</pub-id>
          <pub-id pub-id-type="pii">bmjoq-2020-000918</pub-id>
          <pub-id pub-id-type="pmcid">PMC7887344</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>Electronic health records and the importance of how to document</article-title>
          <source>Pan American Health Organization</source>
          <year>2021</year>
          <access-date>2024-05-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://iris.paho.org/handle/10665.2/55410">https://iris.paho.org/handle/10665.2/55410</ext-link>
          </comment>
        </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>Ulriksen</surname>
              <given-names>GH</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ellingsen</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Infrastructuring in healthcare through the OpenEHR architecture</article-title>
          <source>Comput Supp Coop Work</source>
          <year>2017</year>
          <month>2</month>
          <day>13</day>
          <volume>26</volume>
          <fpage>33</fpage>
          <lpage>69</lpage>
          <pub-id pub-id-type="doi">10.1007/s10606-017-9269-x</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>Meum</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ellingsen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Monteiro</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wangensteen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Igesund</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>The interplay between global standards and local practice in nursing</article-title>
          <source>Int J Med Inform</source>
          <year>2013</year>
          <month>12</month>
          <volume>82</volume>
          <issue>12</issue>
          <fpage>e364</fpage>
          <lpage>74</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2013.02.005</pub-id>
          <pub-id pub-id-type="medline">23688846</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(13)00039-7</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>Eason</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Local sociotechnical system development in the NHS national programme for information technology</article-title>
          <source>J Inf Technol</source>
          <year>2007</year>
          <month>09</month>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>257</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.1057/palgrave.jit.2000101</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>Pedersen</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ellingsen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Monteiro</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Standardized nursing work: works in practice but not in theory?</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2010</year>
          <volume>157</volume>
          <fpage>91</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="medline">20543373</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Standardizing work in healthcare through architecture, routines and technologies</article-title>
          <source>Proceedings of the 10th International Conference on the Design of Cooperative Systems</source>
          <year>2012</year>
          <conf-name>COOP 2012</conf-name>
          <conf-date>May 30-June 1, 2012</conf-date>
          <conf-loc>Marseille, France</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-1-4471-4093-1_2</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>Schaper</surname>
              <given-names>LK</given-names>
            </name>
            <name name-style="western">
              <surname>Pervan</surname>
              <given-names>GP</given-names>
            </name>
          </person-group>
          <article-title>ICT and OTs: a model of information and communication technology acceptance and utilisation by occupational therapists</article-title>
          <source>Int J Med Inform</source>
          <year>2007</year>
          <month>06</month>
          <volume>76 Suppl 1</volume>
          <fpage>S212</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2006.05.028</pub-id>
          <pub-id pub-id-type="medline">16828335</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(06)00150-X</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>Cherns</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The principles of sociotechnical design</article-title>
          <source>Hum Relat</source>
          <year>1976</year>
          <month>08</month>
          <volume>29</volume>
          <issue>8</issue>
          <fpage>783</fpage>
          <lpage>92</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1177/001872677602900806"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/001872677602900806</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>Orlikowski</surname>
              <given-names>WJ</given-names>
            </name>
          </person-group>
          <article-title>Using technology and constituting structures: a practice lens for studying technology in organizations</article-title>
          <source>Organ Sci</source>
          <year>2000</year>
          <month>08</month>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>404</fpage>
          <lpage>28</lpage>
          <pub-id pub-id-type="doi">10.1287/orsc.11.4.404.14600</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Standardization strategies in healthcare practices?</article-title>
          <source>Proceedings of the Fifteenth International Symposium for Health Information Management Research</source>
          <year>2011</year>
          <conf-name>ISHIMR 2011</conf-name>
          <conf-date>September 8-9, 2011</conf-date>
          <conf-loc>Zurich, Switzerland</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Suchman</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <source>Plans and Situated Actions: The Problem of Human-Machine Communication</source>
          <year>1987</year>
          <publisher-loc>Cambridge, UK</publisher-loc>
          <publisher-name>Cambridge University Press</publisher-name>
        </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>Bostrom</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Heinen</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>MIS problems and failures: a socio-technical perspective. Part I: the causes</article-title>
          <source>MIS Q</source>
          <year>1977</year>
          <month>09</month>
          <volume>1</volume>
          <issue>3</issue>
          <fpage>17</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.2307/248710</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>Orlikowski</surname>
              <given-names>WJ</given-names>
            </name>
          </person-group>
          <article-title>The duality of technology: rethinking the concept of technology in organizations</article-title>
          <source>Organ Sci</source>
          <year>1992</year>
          <month>08</month>
          <day>01</day>
          <volume>3</volume>
          <issue>3</issue>
          <fpage>398</fpage>
          <lpage>427</lpage>
          <pub-id pub-id-type="doi">10.1287/orsc.3.3.398</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A sociotechnical approach to electronic health record related safety</article-title>
          <source>Key Advances in Clinical Informatics: Transforming Health Care Through Health Information Technology</source>
          <year>2017</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>Academic Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abbas</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Michael</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Papagiannidis</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Socio-Technical Theory: A Review</source>
          <year>2023</year>
          <publisher-loc>Newcastle upon Tyne, UK</publisher-loc>
          <publisher-name>TheoryHub Book</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Kaufman</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Kannampallil</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>VL</given-names>
            </name>
          </person-group>
          <article-title>A new socio-technical model for studying health information technology in complex adaptive healthcare systems</article-title>
          <source>Cognitive Informatics for Biomedicine: Human Computer Interaction in Healthcare</source>
          <year>2015</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer International Publishing</publisher-name>
        </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>Laukvik</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Lyngstad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rotegård</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Fossum</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Utilizing nursing standards in electronic health records: a descriptive qualitative study</article-title>
          <source>Int J Med Inform</source>
          <year>2024</year>
          <month>04</month>
          <volume>184</volume>
          <fpage>105350</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(24)00013-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2024.105350</pub-id>
          <pub-id pub-id-type="medline">38306850</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(24)00013-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <article-title>Utredning av «en innbygger – én journal»</article-title>
          <source>Helsedirektoratet</source>
          <year>2014</year>
          <month>9</month>
          <access-date>2024-04-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.regjeringen.no/contentassets/355890dd2872413b838066702dcdad88/ikt_utfordringsbilde_helse_omsorgssektoren.pdf">https://www.regjeringen.no/contentassets/355890dd2872413b838066702dcdad88/ikt_utfordringsbilde_helse_omsorgssektoren.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
          <article-title>Meld. St. 9 (2012–2013)</article-title>
          <source>Regjeringen.no</source>
          <year>2012</year>
          <access-date>2024-04-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.regjeringen.no/no/dokumenter/meld-st-9-20122013/id708609/">https://www.regjeringen.no/no/dokumenter/meld-st-9-20122013/id708609/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <article-title>Bakgrunn for Helseplattformen</article-title>
          <source>Helseplattformen</source>
          <access-date>2024-04-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.helseplattformen.no/bakgrunn-for-helseplattformen">https://www.helseplattformen.no/bakgrunn-for-helseplattformen</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="web">
          <article-title>Kartlegging av elektroniske pasientjournalsystemer og deres støtte for nasjonale e-helseløsninger</article-title>
          <source>Helsedirektoratet</source>
          <year>2023</year>
          <access-date>2025-03-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/y7mupvvv">https://tinyurl.com/y7mupvvv</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <article-title>Årlig melding 2017 for Helse Midt-Norge RHF til Helse- og omsorgsdepartementet</article-title>
          <source>Regjeringen.no</source>
          <year>2017</year>
          <access-date>2024-03-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.regjeringen.no/contentassets/18f93a5faa81417b8ac28f74a02cc0ee/arlig-melding-2017-fra-helse-midt-norge-rhf.pdf">https://www.regjeringen.no/contentassets/18f93a5faa81417b8ac28f74a02cc0ee/arlig-melding-2017-fra-helse-midt-norge-rhf.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stedenfeldt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wekre</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tørhaug</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gotaas</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Toch-Marquardt</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Fra fritekst til struktur og felles helsespråk</article-title>
          <source>Michael</source>
          <year>2023</year>
          <volume>20</volume>
          <issue>Supplement 31</issue>
          <fpage>106</fpage>
          <lpage>14</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.michaeljournal.no/article/2023/02/Fra%20fritekst%20til%20struktur%20og%20felles%20helsespr%C3%A5k"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abeysinghe</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bernstam</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bodenreider</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A deep learning approach to identify missing is-a relations in SNOMED CT</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2023</year>
          <month>02</month>
          <day>16</day>
          <volume>30</volume>
          <issue>3</issue>
          <fpage>475</fpage>
          <lpage>84</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36539234"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocac248</pub-id>
          <pub-id pub-id-type="medline">36539234</pub-id>
          <pub-id pub-id-type="pii">6947996</pub-id>
          <pub-id pub-id-type="pmcid">PMC9933066</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fung</surname>
              <given-names>KW</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>An exploration of the properties of the CORE problem list subset and how it facilitates the implementation of SNOMED CT</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2015</year>
          <month>05</month>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>649</fpage>
          <lpage>58</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25725003"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocu022</pub-id>
          <pub-id pub-id-type="medline">25725003</pub-id>
          <pub-id pub-id-type="pii">ocu022</pub-id>
          <pub-id pub-id-type="pmcid">PMC5566198</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Some unintended consequences of information technology in health care: the nature of patient care information system-related errors</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2004</year>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>104</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/14633936"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M1471</pub-id>
          <pub-id pub-id-type="medline">14633936</pub-id>
          <pub-id pub-id-type="pii">M1471</pub-id>
          <pub-id pub-id-type="pmcid">PMC353015</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mamykina</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Stetson</surname>
              <given-names>PD</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Clinical documentation: composition or synthesis?</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2012</year>
          <month>11</month>
          <day>01</day>
          <volume>19</volume>
          <issue>6</issue>
          <fpage>1025</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/22813762"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2012-000901</pub-id>
          <pub-id pub-id-type="medline">22813762</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2012-000901</pub-id>
          <pub-id pub-id-type="pmcid">PMC3534467</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pizziferri</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kittler</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Volk</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Honour</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lippincott</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Primary care physician time utilization before and after implementation of an electronic health record: a time-motion study</article-title>
          <source>J Biomed Inform</source>
          <year>2005</year>
          <month>06</month>
          <volume>38</volume>
          <issue>3</issue>
          <fpage>176</fpage>
          <lpage>88</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(04)00161-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2004.11.009</pub-id>
          <pub-id pub-id-type="medline">15896691</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(04)00161-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rowlands</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tariq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Coverdale</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wood</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A qualitative investigation into clinical documentation: why do clinicians document the way they do?</article-title>
          <source>Health Inf Manag</source>
          <year>2022</year>
          <month>09</month>
          <volume>51</volume>
          <issue>3</issue>
          <fpage>126</fpage>
          <lpage>34</lpage>
          <pub-id pub-id-type="doi">10.1177/1833358320929776</pub-id>
          <pub-id pub-id-type="medline">32643428</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ho</surname>
              <given-names>YX</given-names>
            </name>
            <name name-style="western">
              <surname>Gadd</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Kohorst</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenbloom</surname>
              <given-names>ST</given-names>
            </name>
          </person-group>
          <article-title>A qualitative analysis evaluating the purposes and practices of clinical documentation</article-title>
          <source>Appl Clin Inform</source>
          <year>2014</year>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>153</fpage>
          <lpage>68</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/24734130"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2013-10-RA-0081</pub-id>
          <pub-id pub-id-type="medline">24734130</pub-id>
          <pub-id pub-id-type="pmcid">PMC3974254</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pankhurst</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Evison</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Atia</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gallier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Coleman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ball</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McKee</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Black</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Introduction of systematized nomenclature of medicine-clinical terms coding into an electronic health record and evaluation of its impact: qualitative and quantitative study</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>11</month>
          <day>23</day>
          <volume>9</volume>
          <issue>11</issue>
          <fpage>e29532</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/11/e29532/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/29532</pub-id>
          <pub-id pub-id-type="medline">34817387</pub-id>
          <pub-id pub-id-type="pii">v9i11e29532</pub-id>
          <pub-id pub-id-type="pmcid">PMC8663536</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>AlYahmady</surname>
              <given-names>HH</given-names>
            </name>
            <name name-style="western">
              <surname>Al Abri</surname>
              <given-names>SS</given-names>
            </name>
          </person-group>
          <article-title>Using Nvivo for data analysis in qualitative research</article-title>
          <source>Int Interdiscip J Educ</source>
          <year>2013</year>
          <month>02</month>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>181</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.12816/0002914</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>One size fits all? What counts as quality practice in (reflexive) thematic analysis?</article-title>
          <source>Qual Res Psychol</source>
          <year>2020</year>
          <month>08</month>
          <day>12</day>
          <volume>18</volume>
          <issue>3</issue>
          <fpage>328</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1080/14780887.2020.1769238</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>O’Brien</surname>
              <given-names>BC</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>IB</given-names>
            </name>
            <name name-style="western">
              <surname>Beckman</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Reed</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <article-title>Standards for reporting qualitative research: a synthesis of recommendations</article-title>
          <source>Acad Med</source>
          <year>2014</year>
          <volume>89</volume>
          <issue>9</issue>
          <fpage>1245</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1097/acm.0000000000000388</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ratwani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Fairbanks</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Savage</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wittie</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Boone</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Hayden</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hettinger</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Gettinger</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Mind the gap. A systematic review to identify usability and safety challenges and practices during electronic health record implementation</article-title>
          <source>Appl Clin Inform</source>
          <year>2016</year>
          <month>11</month>
          <day>16</day>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>1069</fpage>
          <lpage>87</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27847961"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2016-06-R-0105</pub-id>
          <pub-id pub-id-type="medline">27847961</pub-id>
          <pub-id pub-id-type="pii">2016-06-R-0105</pub-id>
          <pub-id pub-id-type="pmcid">PMC5228144</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Blavin</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ramos</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Devers</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Lessons from the literature on electronic health record implementation: a study funded by the office of the national coordinator for health information technology of the U.S. Department of Health and Human Services</article-title>
          <source>The Urban Institute</source>
          <year>2013</year>
          <month>8</month>
          <day>1</day>
          <access-date>2024-05-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthit.gov/sites/default/files/hit_lessons_learned_lit_review_final_08-01-2013.pdf">https://www.healthit.gov/sites/default/files/hit_lessons_learned_lit_review_final_08-01-2013.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Samadbeik</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fatehi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Braunstein</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barry</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Saremian</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kalhor</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Edirippulige</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Education and training on electronic medical records (EMRs) for health care professionals and students: a scoping review</article-title>
          <source>Int J Med Inform</source>
          <year>2020</year>
          <month>10</month>
          <volume>142</volume>
          <fpage>104238</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2020.104238</pub-id>
          <pub-id pub-id-type="medline">32828034</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(20)30780-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Heponiemi</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gluschkoff</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Vehko</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kaihlanen</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Saranto</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Nissinen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nadav</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kujala</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record implementations and insufficient training endanger nurses' well-being: cross-sectional survey study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>12</month>
          <day>23</day>
          <volume>23</volume>
          <issue>12</issue>
          <fpage>e27096</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/12/e27096/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/27096</pub-id>
          <pub-id pub-id-type="medline">34941546</pub-id>
          <pub-id pub-id-type="pii">v23i12e27096</pub-id>
          <pub-id pub-id-type="pmcid">PMC8738988</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bredfeldt</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Awad</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Joseph</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Snyder</surname>
              <given-names>MH</given-names>
            </name>
          </person-group>
          <article-title>Training providers: beyond the basics of electronic health records</article-title>
          <source>BMC Health Serv Res</source>
          <year>2013</year>
          <month>12</month>
          <day>02</day>
          <volume>13</volume>
          <fpage>503</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/1472-6963-13-503"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6963-13-503</pub-id>
          <pub-id pub-id-type="medline">24295150</pub-id>
          <pub-id pub-id-type="pii">1472-6963-13-503</pub-id>
          <pub-id pub-id-type="pmcid">PMC4220630</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sachs</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yonek</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Mullins</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Hamilton</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rachman</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kaleba</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McAlearney</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Hasnain-Wynia</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Impact of health IT on lab order use in community health centers</article-title>
          <source>Agency for Healthcare Research and Quality</source>
          <year>2011</year>
          <month>11</month>
          <access-date>2024-05-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital.ahrq.gov/file/18903/download?token=9XtjSeyh">https://digital.ahrq.gov/file/18903/download?token=9XtjSeyh</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="web">
          <article-title>Riksrevisjonens undersøkelse av kodekvaliteten ved helseforetakene</article-title>
          <source>Riksrevisjonen</source>
          <year>2006</year>
          <access-date>2024-06-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.stortinget.no/globalassets/pdf/dokumentserien/2005-2006/dok_3_7_2005_2006.pdf">https://www.stortinget.no/globalassets/pdf/dokumentserien/2005-2006/dok_3_7_2005_2006.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Forrest</surname>
              <given-names>CB</given-names>
            </name>
            <name name-style="western">
              <surname>Crandall</surname>
              <given-names>WV</given-names>
            </name>
            <name name-style="western">
              <surname>Bailey</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Joffe</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Colletti</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>Adler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Baron</surname>
              <given-names>HI</given-names>
            </name>
            <name name-style="western">
              <surname>Berman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>del Rosario</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Grossman</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffenberg</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Israel</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Lightdale</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Margolis</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Marsolo</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>DI</given-names>
            </name>
            <name name-style="western">
              <surname>Milov</surname>
              <given-names>DE</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Tung</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kappelman</surname>
              <given-names>MD</given-names>
            </name>
          </person-group>
          <article-title>Effectiveness of anti-TNFα for Crohn disease: research in a pediatric learning health system</article-title>
          <source>Pediatrics</source>
          <year>2014</year>
          <month>07</month>
          <volume>134</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <lpage>44</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/24935993"/>
          </comment>
          <pub-id pub-id-type="doi">10.1542/peds.2013-4103</pub-id>
          <pub-id pub-id-type="medline">24935993</pub-id>
          <pub-id pub-id-type="pii">peds.2013-4103</pub-id>
          <pub-id pub-id-type="pmcid">PMC4531278</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rattray</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Damush</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Miech</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Homoya</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Myers</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Penney</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Ferguson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Giacherio</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bravata</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>Empowering implementation teams with a learning health system approach: leveraging data to improve quality of care for transient ischemic attack</article-title>
          <source>J Gen Intern Med</source>
          <year>2020</year>
          <month>11</month>
          <day>01</day>
          <volume>35</volume>
          <issue>Suppl 2</issue>
          <fpage>823</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32875510"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-020-06160-y</pub-id>
          <pub-id pub-id-type="medline">32875510</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11606-020-06160-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC7652965</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mungmode</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Noor</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Weinstock</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Izquierdo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Indyk</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>DeSalvo</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Corathers</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Demeterco-Berggen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hsieh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jacobsen</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Mekhoubad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Akturk</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Wirsch</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Miyazaki</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Malik</surname>
              <given-names>FS</given-names>
            </name>
            <name name-style="western">
              <surname>Ebekozien</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Clements</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Alonso</surname>
              <given-names>GT</given-names>
            </name>
          </person-group>
          <article-title>Making diabetes electronic medical record data actionable: promoting benchmarking and population health improvement using the T1D exchange quality improvement portal</article-title>
          <source>Clin Diabetes</source>
          <year>2022</year>
          <volume>41</volume>
          <issue>1</issue>
          <fpage>45</fpage>
          <lpage>55</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36714251"/>
          </comment>
          <pub-id pub-id-type="doi">10.2337/cd22-0072</pub-id>
          <pub-id pub-id-type="medline">36714251</pub-id>
          <pub-id pub-id-type="pii">CD220072</pub-id>
          <pub-id pub-id-type="pmcid">PMC9845086</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alonso</surname>
              <given-names>GT</given-names>
            </name>
            <name name-style="western">
              <surname>Corathers</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Clements</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kamboj</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sonabend</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>DeSalvo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cabrera</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rioles</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ohmer</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Establishment of the T1D exchange quality improvement collaborative (T1DX-QI)</article-title>
          <source>Clin Diabetes</source>
          <year>2020</year>
          <month>04</month>
          <volume>38</volume>
          <issue>2</issue>
          <fpage>141</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32327886"/>
          </comment>
          <pub-id pub-id-type="doi">10.2337/cd19-0032</pub-id>
          <pub-id pub-id-type="medline">32327886</pub-id>
          <pub-id pub-id-type="pii">cd190032</pub-id>
          <pub-id pub-id-type="pmcid">PMC7164986</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vandenberg</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Kegler</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hastings</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Stevens</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Clevenger</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Eucker</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Genes</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Ikpe-Ekpo</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Nassisi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Previll</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sanon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schlientz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Vigliotti</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Vaughan</surname>
              <given-names>CP</given-names>
            </name>
          </person-group>
          <article-title>Sequential implementation of the EQUIPPED geriatric medication safety program as a learning health system</article-title>
          <source>Int J Qual Health Care</source>
          <year>2020</year>
          <month>09</month>
          <day>23</day>
          <volume>32</volume>
          <issue>7</issue>
          <fpage>470</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1093/intqhc/mzaa077</pub-id>
          <pub-id pub-id-type="medline">32671390</pub-id>
          <pub-id pub-id-type="pii">5871954</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Orlikowski</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gash</surname>
              <given-names>DC</given-names>
            </name>
          </person-group>
          <article-title>Technological frames: making sense of information technology in organizations</article-title>
          <source>ACM Trans Inf Syst</source>
          <year>1994</year>
          <month>04</month>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>174</fpage>
          <lpage>207</lpage>
          <pub-id pub-id-type="doi">10.1145/196734.196745</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Joukes</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>de Keizer</surname>
              <given-names>NF</given-names>
            </name>
            <name name-style="western">
              <surname>de Bruijne</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Abu-Hanna</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cornet</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Impact of electronic versus paper-based recording before EHR implementation on health care professionals' perceptions of EHR use, data quality, and data reuse</article-title>
          <source>Appl Clin Inform</source>
          <year>2019</year>
          <month>03</month>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>199</fpage>
          <lpage>209</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30895574"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0039-1681054</pub-id>
          <pub-id pub-id-type="medline">30895574</pub-id>
          <pub-id pub-id-type="pmcid">PMC6426723</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Staggers</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Norcio</surname>
              <given-names>AF</given-names>
            </name>
          </person-group>
          <article-title>Mental models: concepts for human-computer interaction research</article-title>
          <source>Int J Man Mach Stud</source>
          <year>1993</year>
          <month>4</month>
          <volume>38</volume>
          <issue>4</issue>
          <fpage>587</fpage>
          <lpage>605</lpage>
          <pub-id pub-id-type="doi">10.1006/imms.1993.1028</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaufman</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Kannampallil</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>VL</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>VL</given-names>
            </name>
            <name name-style="western">
              <surname>Kannampallil</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>Kaufman</surname>
              <given-names>DR</given-names>
            </name>
          </person-group>
          <article-title>Cognition and human computer interaction in health and biomedicine</article-title>
          <source>Cognitive Informatics for Biomedicine</source>
          <year>2015</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holtrop</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Scherer</surname>
              <given-names>LD</given-names>
            </name>
            <name name-style="western">
              <surname>Matlock</surname>
              <given-names>DD</given-names>
            </name>
            <name name-style="western">
              <surname>Glasgow</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>The importance of mental models in implementation science</article-title>
          <source>Front Public Health</source>
          <year>2021</year>
          <month>7</month>
          <day>6</day>
          <volume>9</volume>
          <fpage>680316</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34295871"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpubh.2021.680316</pub-id>
          <pub-id pub-id-type="medline">34295871</pub-id>
          <pub-id pub-id-type="pmcid">PMC8290163</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nessa</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>From a medical consultation to a written text. 1. Transcribing the doctor-patient dialogue</article-title>
          <source>Scand J Prim Health Care</source>
          <year>1995</year>
          <month>06</month>
          <day>12</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>83</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.3109/02813439508996741?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.3109/02813439508996741</pub-id>
          <pub-id pub-id-type="medline">7569483</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nessa</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>From a medical consultation to a written text. 2. Pragmatics and textlinguistics applied to medicine</article-title>
          <source>Scand J Prim Health Care</source>
          <year>1995</year>
          <month>06</month>
          <day>12</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>89</fpage>
          <lpage>92</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.3109/02813439508996742?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.3109/02813439508996742</pub-id>
          <pub-id pub-id-type="medline">7569484</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ludwick</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Doucette</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Adopting electronic medical records in primary care: lessons learned from health information systems implementation experience in seven countries</article-title>
          <source>Int J Med Inform</source>
          <year>2009</year>
          <month>01</month>
          <volume>78</volume>
          <issue>1</issue>
          <fpage>22</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2008.06.005</pub-id>
          <pub-id pub-id-type="medline">18644745</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(08)00092-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mahapatra</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ieong</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Improving documentation and communication using operative note proformas</article-title>
          <source>BMJ Qual Improv Rep</source>
          <year>2016</year>
          <month>02</month>
          <day>08</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>u209122.w3712</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26893892"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjquality.u209122.w3712</pub-id>
          <pub-id pub-id-type="medline">26893892</pub-id>
          <pub-id pub-id-type="pii">bmjquality_uu209122.w3712</pub-id>
          <pub-id pub-id-type="pmcid">PMC4752707</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thomson</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Baldwin</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bellini</surname>
              <given-names>MI</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>Improving the quality of operative notes for laparoscopic cholecystectomy: assessing the impact of a standardized operation note proforma</article-title>
          <source>Int J Surg</source>
          <year>2016</year>
          <month>03</month>
          <volume>27</volume>
          <fpage>17</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1743-9191(16)00046-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijsu.2016.01.037</pub-id>
          <pub-id pub-id-type="medline">26804350</pub-id>
          <pub-id pub-id-type="pii">S1743-9191(16)00046-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kahn</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Simon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Friedman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mosher</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sharpe</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>El-Farra</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>A prescription for note bloat: an effective progress note template</article-title>
          <source>J Hosp Med</source>
          <year>2018</year>
          <month>06</month>
          <day>01</day>
          <volume>13</volume>
          <issue>6</issue>
          <fpage>378</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.12788/jhm.2898</pub-id>
          <pub-id pub-id-type="medline">29350222</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
