<?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="review-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v24i3e33046</article-id>
      <article-id pub-id-type="pmid">35289752</article-id>
      <article-id pub-id-type="doi">10.2196/33046</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Workarounds in Electronic Health Record Systems and the Revised Sociotechnical Electronic Health Record Workaround Analysis Framework: Scoping Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kukafka</surname>
            <given-names>Rita</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Petersson</surname>
            <given-names>Goran</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Marshall</surname>
            <given-names>Robert</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Blijleven</surname>
            <given-names>Vincent</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Center for Marketing &#38; Supply Chain Management</institution>
            <institution>Nyenrode Business Universiteit</institution>
            <addr-line>Straatweg 25</addr-line>
            <addr-line>Breukelen, 3621 BG</addr-line>
            <country>Netherlands</country>
            <phone>31 630023248</phone>
            <email>vincentblijleven@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0925-6355</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Hoxha</surname>
            <given-names>Florian</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6357-3015</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Jaspers</surname>
            <given-names>Monique</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8040-9153</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Center for Marketing &#38; Supply Chain Management</institution>
        <institution>Nyenrode Business Universiteit</institution>
        <addr-line>Breukelen</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Center for Human Factors Engineering of Health Information Technology</institution>
        <institution>Amsterdam Public Health Research Institute</institution>
        <institution>Amsterdam UMC</institution>
        <addr-line>Amsterdam</addr-line>
        <country>Netherlands</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Vincent Blijleven <email>vincentblijleven@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>3</month>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>15</day>
        <month>3</month>
        <year>2022</year>
      </pub-date>
      <volume>24</volume>
      <issue>3</issue>
      <elocation-id>e33046</elocation-id>
      <history>
        <date date-type="received">
          <day>22</day>
          <month>8</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>10</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>13</day>
          <month>12</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>16</day>
          <month>12</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Vincent Blijleven, Florian Hoxha, Monique Jaspers. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 15.03.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2022/3/e33046" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Electronic health record (EHR) system users devise workarounds to cope with mismatches between workflows designed in the EHR and preferred workflows in practice. Although workarounds appear beneficial at first sight, they frequently jeopardize patient safety, the quality of care, and the efficiency of care.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This review aims to aid in identifying, analyzing, and resolving EHR workarounds; the Sociotechnical EHR Workaround Analysis (SEWA) framework was published in 2019. Although the framework was based on a large case study, the framework still required theoretical validation, refinement, and enrichment.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A scoping literature review was performed on studies related to EHR workarounds published between 2010 and 2021 in the MEDLINE, Embase, CINAHL, Cochrane, or IEEE databases. A total of 737 studies were retrieved, of which 62 (8.4%) were included in the final analysis. Using an analytic framework, the included studies were investigated to uncover the rationales that EHR users have for workarounds, attributes characterizing workarounds, possible scopes, and types of perceived impacts of workarounds.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The SEWA framework was theoretically validated and extended based on the scoping review. Extensive support for the pre-existing rationales, attributes, possible scopes, and types of impact was found in the included studies. Moreover, 7 new rationales, 4 new attributes, and 3 new types of impact were incorporated. Similarly, the descriptions of multiple pre-existing rationales for workarounds were refined to describe each rationale more accurately.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>SEWA is now grounded in the existing body of peer-reviewed empirical evidence on EHR workarounds and, as such, provides a theoretically validated and more complete synthesis of EHR workaround rationales, attributes, possible scopes, and types of impact. The revised SEWA framework can aid researchers and practitioners in a wider range of health care settings to identify, analyze, and resolve workarounds. This will improve user-centered EHR design and redesign, ultimately leading to improved patient safety, quality of care, and efficiency of care.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>electronic health records</kwd>
        <kwd>electronic medical records</kwd>
        <kwd>framework</kwd>
        <kwd>patient safety</kwd>
        <kwd>unintended consequences</kwd>
        <kwd>usability</kwd>
        <kwd>workarounds</kwd>
        <kwd>workflow</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Electronic health record (EHR) systems are the backbone of modern health care organizations. This is in pursuit of promising gains in patient safety, quality of care, efficiency, and control of spiraling costs by enabling value-based reimbursements. However, realizing these expected benefits is far from a given value. Over the years, an overwhelming number of studies have reported that EHRs have led to a multitude of unintended consequences. Examples include potential patient harm resulting from bad EHR usability [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]; increased odds of burnout of health care professionals [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]; physicians experiencing stress [<xref ref-type="bibr" rid="ref5">5</xref>]; users spending an equal amount of time on <italic>desktop medicine</italic> as they spend on having face-to-face interaction with patients [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]; extensive <italic>copy and paste</italic> practices of patient notes leading to note bloating, internal inconsistencies, and errors [<xref ref-type="bibr" rid="ref8">8</xref>]; and the unavailability of complete clinical information at the point of care [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      <p>Many causes of unintended consequences of EHR use can be traced back to discrepancies between the behavior, intentions, and expectations of EHR users and the workflows dictated by EHRs [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. When EHR users experience workflow mismatches, they often create workarounds [<xref ref-type="bibr" rid="ref16">16</xref>]. Workarounds are practices that handle exceptions to normal workflow [<xref ref-type="bibr" rid="ref17">17</xref>] and do not follow the rules, assumptions, workflow regulations, or intentions of systems designers [<xref ref-type="bibr" rid="ref18">18</xref>]. Although workarounds allow EHR users to proceed in accomplishing tasks in their preferred way (with or without the EHR), research shows that workarounds frequently jeopardize the safety, quality, and efficiency of care [<xref ref-type="bibr" rid="ref19">19</xref>]. Given their common adverse effects, workarounds are valuable points of departure for improving the EHR design and redesign.</p>
      <p>Blijleven et al [<xref ref-type="bibr" rid="ref20">20</xref>] developed the Sociotechnical EHR Workaround Analysis (SEWA) framework for identifying, analyzing, and subsequently resolving EHR workarounds. The framework was inspired by the Systems Engineering Initiative for Patient Safety (SEIPS) framework [<xref ref-type="bibr" rid="ref21">21</xref>]. The SEWA framework incorporates four angles: the different rationales EHR users have for creating workarounds (eg, memory aid and required data entry option missing), the stakeholders affected by a workaround (eg, patient and health care professional), the impact of a workaround (eg, on safety and efficiency), and inherent attributes of workarounds (eg, unavoidable, repetitive, and cascading).</p>
      <p>The SEWA framework [<xref ref-type="bibr" rid="ref20">20</xref>] was based on approximately 200 hours of audiovisual material of user–EHR interaction and semistructured follow-up interviews in a single large case study in an academic hospital setting [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. However, the authors argued that the applicability of the framework in other contexts might be limited, such as in nonacademic hospitals or in hospitals where paper-based workarounds (eg, for ordering drugs) are still allowed. Therefore, they recommended validation, refinement, and enrichment of the framework by incorporating workarounds and related rationales, attributes, possible scopes, and types of consequences identified in other EHR workaround–related research and clinical contexts.</p>
      <p>To address these shortcomings, a scoping literature review was performed to identify and map the available evidence on EHR workarounds [<xref ref-type="bibr" rid="ref23">23</xref>]. This paper presents a revised version of the SEWA framework, with rationales, attributes, possible scopes, and types of impact described in workaround-related studies in the EHR, electronic medical record, and computerized physician order entry domains in primary, secondary, and tertiary care contexts published between 2010 and 2021.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Search Strategy</title>
        <p>The MEDLINE, Embase, CINAHL, Cochrane, and IEEE databases were searched for relevant studies. We included original, full papers of research with empirical data and conference papers if there were no full papers published in the same study. <italic>Gray literature</italic>, such as books, was not considered. The search queries included the keywords <italic>EHR</italic>, <italic>electronic health record</italic>, and <italic>workaround(s)</italic> and their synonyms. As the aim was to identify new rationales, attributes, consequences, and scopes of EHR workarounds for the enrichment of the SEWA framework, we defined the searches as broad as possible. Pilot literature searches were conducted to check the appropriateness of the queries. During the pilot searches, the term <italic>workflow</italic> was used as a possible synonym for workarounds. The inclusion of this term led to a much larger pool of possible studies. However, most of these studies were focused on care processes that have no relation with EHR use and were thus, out of scope. Therefore, this term was excluded from search queries. Furthermore, to include the complete spectrum of possible EHRs, a combination of the terms <italic>health/medical/patient/health care/clinical record</italic> and <italic>electronic/digital/online</italic> was used. The results of this pilot evaluation were used to adjust the queries. The used queries are shown in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Search queries used for the scoping review.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="90"/>
            <col width="130"/>
            <col width="780"/>
            <thead>
              <tr valign="top">
                <td>Date of search</td>
                <td>Database</td>
                <td>Query</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>April 9, 2021</td>
                <td>MEDLINE</td>
                <td>
                  <italic>([([([(((((health record*) OR medical record*) OR patient record*) OR health care record*) OR clinical record*) AND electronic] OR digital) OR digitized] OR online) OR online] OR [([Electronic Health Records (MeSH Terms)] OR electronic health record*) OR EHR] OR [([Medical Records Systems, Computerized (MeSH Terms)] OR computerized patient record) OR computerised patient record]) AND ([(workaround*) OR work around*] OR workaround*)</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>April 9, 2021</td>
                <td>Embase</td>
                <td>
                  <italic>(workaround OR workaround* OR workaround OR workaround*) AND</italic>
                  <break/>
                  <italic>([(health record* OR medical record* OR patient record* OR health care record* OR clinical record*) AND (electronic OR digital OR online OR online OR digitized OR digitised)] OR [electronic health record* OR ehr OR electronic medical record* OR emr] OR [computerized patient record OR computerised patient record])</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>April 9, 2021</td>
                <td>CINAHL</td>
                <td>
                  <italic>(workaround OR work around OR workarounds) AND ([(health record OR medical record OR patient record OR health care record OR clinical record) AND (electronic OR digital OR [online OR online] OR [digitized OR digitised])] OR [electronic health record* OR EHR OR electronic medical record* OR EMR] OR [computerized patient record OR computerised patient record])</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>April 9, 2021</td>
                <td>IEEE</td>
                <td>
                  <italic>([([([(workaround*) OR work around*] OR workaround*)])] AND [([health record OR medical record OR patient record OR health care record OR clinical record] AND [electronic OR digital OR (online OR online) OR (digitized OR digitised)]) OR (electronic health record* OR EHR OR electronic medical record* OR EMR) OR (computerized patient record OR computerised patient record)])</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>April 9, 2021</td>
                <td>Cochrane</td>
                <td>
                  <italic>(workaround*): ti, ab,kw OR (work-around*): ti, ab, kw OR (work around*): ti, ab, kw AND ([(electronic health record*): ti, ab, kw OR (health record*): ti, ab, kw OR (medical record*): ti, ab, kw OR (patient record*): ti, ab, kw OR (health care record): ti, ab, kw OR (EHR): ti, ab, kw OR (EMR):ti, ab, kw OR (clinical record):ti, ab, kw OR ([computerized patient record]: ti, ab, kw OR [computerized patient record]: ti, ab, kw)] AND [electronic]: ti, ab, kw OR [digital]: ti, ab, kw OR [online]: ti, ab, kw OR [online]: ti, ab, kw OR [digitized]: ti, ab, kw OR [digitised]: ti, ab, kw)</italic>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Selection Criteria</title>
        <p>The inclusion and exclusion criteria were chosen through discussions among the reviewers (FH, VB, and MJ). As the focus of this scoping review was on workarounds in EHR use, it was decided to exclude studies focused on barcode medication administration systems as these systems serve only 1 purpose and cover only a small part of the medication process. Furthermore, the choice was made to exclude research focused on EHR functionalities other than those aimed at supporting the clinical process. To ensure data quality, a study was excluded if the research methods were not reported or in case the study had not been peer reviewed. Furthermore, research published before 2010 was excluded as EHRs have undergone significant changes and improvements over the years. Finally, the inclusion and exclusion criteria were chosen.</p>
        <p>The study inclusion criteria were as follows:</p>
        <list list-type="order">
          <list-item>
            <p>The health care setting of the study must be either ≥1 of primary, secondary, or tertiary care.</p>
          </list-item>
          <list-item>
            <p>Workarounds were studied or reported in the context of EHR use.</p>
          </list-item>
          <list-item>
            <p>The article was published between 2010 and 2021.</p>
          </list-item>
        </list>
        <p>Studies were excluded if they met any of the following criteria:</p>
        <list list-type="order">
          <list-item>
            <p>The research focused on EHR functionalities other than those aimed at supporting within the clinical process.</p>
          </list-item>
          <list-item>
            <p>The research focused on a barcode administration functionality.</p>
          </list-item>
          <list-item>
            <p>The article was not written in English.</p>
          </list-item>
          <list-item>
            <p>There was no access to the full-text article.</p>
          </list-item>
          <list-item>
            <p>The article was not peer reviewed.</p>
          </list-item>
          <list-item>
            <p>The research methods were not reported.</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Article Selection</title>
        <p>A literature search was conducted in April 2021. A total of 737 potentially relevant studies were retrieved from our initial search of electronic databases, more specifically MEDLINE (263/737, 35.7%), Embase (121/737, 16.4%), CINAHL (89/737, 12.1%), IEEE (58/737, 7.9%), and Cochrane (206/737, 27.9%). The results of the study selection process are shown in the PRISMA (Preferred Reporting Item for Systematic Reviews and Meta-Analyses) flowchart in <xref rid="figure1" ref-type="fig">Figure 1</xref>.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>PRISMA (Preferred Reporting Item for Systematic Reviews and Meta-Analyses) flowchart of the study selection process. CPOE: computerized physician order entry; EHR: electronic health record.</p>
          </caption>
          <graphic xlink:href="jmir_v24i3e33046_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The retrieved 737 studies were uploaded to EndNoteX9 (Clarivate), in which duplicates were first removed by both using EndNoteX9 and by performing a manual check (<xref rid="figure1" ref-type="fig">Figure 1</xref>). This led to 79.6% (587/737) of unique studies. These studies were reviewed by two independent reviewers (FH and VB). The 2 reviewers first independently screened the titles and abstracts of the eligible papers to evaluate whether they met the inclusion criteria. Of the 587 studies, 116 (19.8%) studies met the inclusion criteria, and 471 (60.2%) studies were excluded (because of, for example, workarounds not being focused on the EHR, not being a scientific research article, and no workarounds mentioned). Afterward, the reviewers independently screened the full texts of these 116 studies, leading to 62 (53.4%) included studies and 54 (46.6%) excluded studies (eg, no full-text available and methods inappropriately described). After each screening phase, the two reviewers (FH and VB) discussed their findings. The next screening phase was conducted only if a consensus was reached between the 2 independent reviewers. If a disagreement between the 2 reviewers could not be resolved by discussion, a third independent reviewer (MJ) was involved. After consensus was reached, interrater reliability was reported by calculating the Cohen κ. The interrater agreement was also calculated to show the extent to which the reviewers were able to reconcile through discussion [<xref ref-type="bibr" rid="ref24">24</xref>]. For the first round (title and abstract screening), the Cohen κ value was 0.958, and the interrater agreement value was 0.985. For the second round (full-text screening), the Cohen κ value was 0.930, and the interrater agreement value was 0.966.</p>
      </sec>
      <sec>
        <title>Data Analysis of Included Articles</title>
        <p>Descriptive data from the included articles, such as title, authors, year of publication, study setting, functionalities of EHR studied, and research methods used, were captured in a generic overview per study (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Workaround-related data from the included articles, such as workaround rationales, attributes, consequences, and scope, were captured in an analytic frame per study (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p>
        <p>The data extracted from the included articles were compared with the SEWA framework on a study-by-study basis. In doing so, SEWA was supplemented with new rationales, attributes, possible scopes, and types of impact of EHR workarounds that were not previously included. After the analysis was completed, an updated (graphical) version of the SEWA framework was created.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>General Characteristics</title>
        <p>The general characteristics of the 62 studies are shown in <xref ref-type="table" rid="table2">Table 2</xref>. There was an approximately even split in studies published between 2010 and 2015 and between 2016 and 2021. The study settings were almost equally distributed, with most (23/62, 37%) being set in tertiary care, such as academic hospitals and special care units. The largest group of studies (28/62, 45%) focused their research on the EHR overall. Of the 62 studies, 17 (27%) studied medication-related functionalities or EHR-integrated systems, such as computerized physician order entries. Approximately half (28/62, 45%) used or included a combination of physicians, nurses, and other staff such as pharmacists and administrative personnel as participants. Of the 62 studies, 26 (42%) used a combination of methods such as observations, interviews, and questionnaires, 15 (24%) used interviews as the sole method, 5 (8%) solely used questionnaires, 7 (11%) solely used observational methods, and 9 (15%) used other methods such as think-aloud protocols and documentation analysis.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>General characteristics of the included studies (N=62).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="700"/>
            <col width="270"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Study characteristics</td>
                <td>Values, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>Year of publication</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2010-2015</td>
                <td>30 (48)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>2016-2021</td>
                <td>32 (52)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Study setting</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Primary care</td>
                <td>18 (29)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Secondary care</td>
                <td>21 (34)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Tertiary care</td>
                <td>23 (37)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Functionalities of EHR<sup>a</sup> studied</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Medication-related (eg, prescribing and CPOE<sup>b</sup>)</td>
                <td>17 (27)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Documentation</td>
                <td>8 (13)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Overall EHR</td>
                <td>28 (45)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Others (eg, alert systems and authentication process)</td>
                <td>9 (15)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Type of population</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Physicians</td>
                <td>9 (15)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Nurses</td>
                <td>13 (21)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Others (eg, pharmacists or administrative staff such as managers, <break/>assistants, secretary, or not mentioned)</td>
                <td>12 (19)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Combination of users</td>
                <td>28 (45)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Methods</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Observations</td>
                <td>7 (11)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Interviews</td>
                <td>15 (24)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Questionnaires</td>
                <td>5 (8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Others (eg, think-aloud and documentation analysis)</td>
                <td>9 (15)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Combination of ≥1 observation, interview, questionnaire, or other</td>
                <td>26 (42)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>EHR: electronic health record.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>CPOE: computerized physician order entry.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Validation, Refinement, and Enrichment of the SEWA Framework</title>
        <sec>
          <title>Overview</title>
          <p>Evidence for the work system components, rationales, attributes, type of impact, and possible scopes contained in the original SEWA framework was found in the included studies. Moreover, we refined and enriched the original framework with 7 rationales, 4 attributes, and 3 types of impact. The following subsections elaborate on the work system components, rationales, attributes, possible scopes, and types of impact.</p>
        </sec>
        <sec>
          <title>Work System Components</title>
          <p>Support for all 5 work system components was found in the included studies, as shown in <xref ref-type="table" rid="table3">Table 3</xref>. No new work system components were identified. However, we made 1 change to the work system component <italic>EHR system</italic>, which we renamed to <italic>EHR system and related technology</italic>. The latter was incorporated to also cover workarounds stemming from the use of technology other than the EHR but used in parallel with the EHR, such as scanners [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Overview of work system components and related included studies.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="250"/>
              <col width="610"/>
              <col width="140"/>
              <thead>
                <tr valign="top">
                  <td>Work components</td>
                  <td>Description</td>
                  <td>Studies</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Person(s)</td>
                  <td>Health care professionals developing and using EHR<sup>a</sup> workarounds</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>EHR system and related technology</td>
                  <td>The EHR and related information technology used by health care professionals</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Organization</td>
                  <td>Organizational conditions (eg, care directives and hospital policies) under which clinical tasks and EHR use are performed</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Physical environment</td>
                  <td>The environment (eg, outpatient examination room and inpatient ward) and its conditions (eg, lighting and noise) in which clinical tasks are conducted by health care professionals</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Task(s)</td>
                  <td>Clinical tasks performed by health care professionals</td>
                  <td> [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref32">32</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Rationales</title>
          <p>The rationales for workarounds contained in the original SEWA framework were confirmed in many studies. In addition, 7 new rationales were identified.</p>
          <p>Under the work system component <italic>person(s)</italic>, one rationale was added: <italic>trust</italic> (<xref ref-type="table" rid="table4">Table 4</xref>). Multiple studies reported that users created workarounds because of insufficient trust in the (new) system or its capabilities while frequently maintaining trust in older systems (replaced by the EHR). The related causes of a lack of trust are a lack of perceived usefulness of the (new) system and insufficient confidence in (completeness) of the data available in the EHR [<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref39">39</xref>]. The description of the rationale <italic>awareness</italic> has been refined to also cover awareness of the information needs of patients and not just of colleagues [<xref ref-type="bibr" rid="ref40">40</xref>]. Likewise, the description of the rationale <italic>social norms</italic> has been refined to make cultural [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>] and collaborative [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref42">42</xref>] aspects more explicit.</p>
          <p>Although extensive support in the included studies was found for all rationales under the work system component <italic>EHR system and related technology</italic>, except <italic>patient data specificity,</italic> four additional rationales were identified: <italic>data integration</italic>, <italic>enforced actions</italic>, <italic>data quality</italic>, and <italic>interoperability</italic> (<xref ref-type="table" rid="table5">Table 5</xref>). The description of the pre-existing rationale <italic>technical issues</italic> has been refined to cover technical issues related to ancillary technology used in conjunction with the EHR.</p>
          <p>Multiple studies provide support for all rationales under the work system component <italic>organization</italic> except for the rationale <italic>data migration policy</italic> (<xref ref-type="table" rid="table6">Table 6</xref>). No new rationales were identified.</p>
          <p>Although support was found for the pre-existing rationales under <italic>task(s)</italic>, one rationale was added: <italic>task complexity</italic> (<xref ref-type="table" rid="table7">Table 7</xref>). Approximately 3% (2/62) of studies described that the EHR does not always sufficiently support the execution of a complex task at hand [<xref ref-type="bibr" rid="ref34">34</xref>-<xref ref-type="bibr" rid="ref39">39</xref>]. Therefore, health care professionals resort to workarounds to make their workflow more digestible.</p>
          <p>Finally, the SEIPS work system component <italic>physical environment</italic> was incorporated into the original SEWA framework without any rationale. However, Dudding et al [<xref ref-type="bibr" rid="ref25">25</xref>] mentioned that a busy, fast-paced environment where interruptions are constant, such as the neonatal intensive care unit, gives rise to EHR workarounds. The rationale here is “fast-paced environment” and is described as “devising workarounds to cope with the inability to, for example, update the documentation in fast-paced care environments where interruptions are constant” [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Overview of rationales for the work system component person(s) and related included studies.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="190"/>
              <col width="670"/>
              <col width="140"/>
              <thead>
                <tr valign="top">
                  <td>Rationales</td>
                  <td>Description</td>
                  <td>Studies</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Declarative knowledge</td>
                  <td>Not knowing how to use (a part of) the EHR<sup>a</sup> to accomplish a task</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Procedural knowledge</td>
                  <td>Knowing how but not being proficient enough to use a part of the EHR to accomplish a task</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Memory aid</td>
                  <td>Writing patient data down on paper (eg, keywords) or adding visual elements to parts of text in a progress note (eg, boldfacing, italicizing, or underlining) to remind oneself</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref45">45</xref>-<xref ref-type="bibr" rid="ref47">47</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Awareness</td>
                  <td>Storing patient data that are perceived important by the EHR user for other colleagues or patients to be noticed (frequently in a data field other than the intended field in the EHR)</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref48">48</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Social norms</td>
                  <td>Formal or informal, collaborative, and cultural understandings among health care professionals leading to the creation and dissemination of workarounds (eg, mimicking workarounds devised by colleagues to accomplish a task or working around the system upon as friendly requested or enforced by a fellow clinician)</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Trust (new)</td>
                  <td>Having insufficient trust in the (new) EHR system or its capabilities, lack of perceived usefulness, or insufficient confidence in the (completeness) of data</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Overview of rationales for the work system component EHR<sup>a</sup> system and related technology and related included studies.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="190"/>
              <col width="550"/>
              <col width="260"/>
              <thead>
                <tr valign="top">
                  <td>Rationales</td>
                  <td>Description</td>
                  <td>Studies</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Usability</td>
                  <td>High behavioral user cost in accomplishing a task</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref50">50</xref>-<xref ref-type="bibr" rid="ref56">56</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Technical issues</td>
                  <td>(A part of the) EHR or ancillary technology halting, crashing, or slowing down, hampering the EHR user in accomplishing a task</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref61">61</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Data presentation</td>
                  <td>Preferring a different data view (eg, visualization by means of charts or graphs rather than plain text)</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Patient data specificity</td>
                  <td>Needing to enter or request patient data with greater or lesser specificity than offered or enforced by the EHR</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Data integration (new)</td>
                  <td>EHR not providing or supporting the integration of patient data necessary for care delivery</td>
                  <td>[<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Enforced actions (new)</td>
                  <td>Avoiding or overriding actions enforced by the EHR (eg, bypassing the approval process of prescribing medication or using a different user account)</td>
                  <td>[<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Data quality (new)</td>
                  <td>Unavailability of data, disparity in data formats (eg, the same data being stored in multiple different formats in the EHR), lack of standardization, and information gaps in the EHR</td>
                  <td>[<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref34">34</xref>-<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref64">64</xref>-<xref ref-type="bibr" rid="ref67">67</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Interoperability (new)</td>
                  <td>Data not able to be exchanged between health care systems or institutions (eg, causing data to be unavailable at the right moment and time)</td>
                  <td>[<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table6">
            <label>Table 6</label>
            <caption>
              <p>Overview of rationales for the work system component organization and related included studies.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="190"/>
              <col width="540"/>
              <col width="270"/>
              <thead>
                <tr valign="top">
                  <td>Rationales</td>
                  <td>Description</td>
                  <td>Studies</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Efficiency</td>
                  <td>Using an alternative way of accomplishing a task that improves actual efficiency</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref68">68</xref>-<xref ref-type="bibr" rid="ref70">70</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Data migration policy</td>
                  <td>Not having (direct) access to required historical data because of data not having been imported from previously used systems to the current EHR<sup>a</sup></td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Enforced data entry</td>
                  <td>EHR enforcing user to enter patient data of which neither the user nor the patient has knowledge of</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref72">72</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Required data entry option missing</td>
                  <td>EHR not offering the required data entry option (eg, 3.75 mg rather than the available options 2.5 mg or 5 mg)</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table6fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table7">
            <label>Table 7</label>
            <caption>
              <p>Overview of rationales for the work system component task(s) and related included studies.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="210"/>
              <col width="580"/>
              <col width="210"/>
              <thead>
                <tr valign="top">
                  <td>Rationales</td>
                  <td>Description</td>
                  <td>Studies</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Task interference</td>
                  <td>Inability to perform multiple tasks at once (eg, simultaneously treating a patient on the treatment table as well as entering patient data into the EHR<sup>a</sup>)</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref61">61</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Commitment to patient interaction</td>
                  <td>Valuing patient interaction over computer interaction (ie, writing things down on paper and afterward entering this into the EHR)</td>
                  <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref73">73</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Task complexity (new)</td>
                  <td>The high complexity of the tasks needing to be conducted</td>
                  <td>[<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table7fn1">
                <p><sup>a</sup>EHR: electronic health record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <sec>
            <title>Attributes</title>
            <p>Although several studies confirmed the previously defined attributes in SEWA, several included studies also mentioned a total of 4 new attributes (<xref ref-type="table" rid="table8">Table 8</xref>). These are concerned with whether the user is aware of using a workaround [<xref ref-type="bibr" rid="ref49">49</xref>] (<italic>awareness</italic>), whether the workaround is an individual or shared practice across users [<xref ref-type="bibr" rid="ref49">49</xref>] (<italic>shared</italic>), on what medium the workaround is conducted (eg, paper or computer) [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref41">41</xref>] (<italic>medium</italic>), and whether the workaround is a formal or informal practice (eg, part of a defined process or approved or promoted by management or not) [<xref ref-type="bibr" rid="ref56">56</xref>] (<italic>formality</italic>).</p>
            <table-wrap position="float" id="table8">
              <label>Table 8</label>
              <caption>
                <p>Overview of workaround attributes and related included studies.</p>
              </caption>
              <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="150"/>
                <col width="740"/>
                <col width="110"/>
                <thead>
                  <tr valign="top">
                    <td>Attributes</td>
                    <td>Description</td>
                    <td>Source</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td>Cascadedness</td>
                    <td>Whether the workaround initiates the creation of 1 or multiple additional workarounds or is an isolated occurrence</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Avoidability</td>
                    <td>Whether the workaround is required to proceed with one’s workflow or optional</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref74">74</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Anticipatedness</td>
                    <td>Whether the workaround is used at known moments in time (ie, the situation in which the workaround is used is known beforehand) or used unexpectedly</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref74">74</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Repetitiveness</td>
                    <td>Whether the workaround is ingrained into the workflow (ie, becomes part of daily routines) or used temporarily to overcome workflow constraints</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref74">74</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Awareness (new)</td>
                    <td>Whether the user is aware of using the workaround</td>
                    <td>[<xref ref-type="bibr" rid="ref49">49</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Shared (new)</td>
                    <td>Whether the workaround is a shared practice across multiple other users of the EHR<sup>a</sup> or limited to 1 user</td>
                    <td>[<xref ref-type="bibr" rid="ref49">49</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Medium (new)</td>
                    <td>On what medium the workaround is conducted (eg, paper, computer, verbal, or a combination)</td>
                    <td>[<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Formality (new)</td>
                    <td>Whether the use of the workaround is approved by management and part of a defined process</td>
                    <td>[<xref ref-type="bibr" rid="ref56">56</xref>]</td>
                  </tr>
                </tbody>
              </table>
              <table-wrap-foot>
                <fn id="table8fn1">
                  <p><sup>a</sup>EHR: electronic health record.</p>
                </fn>
              </table-wrap-foot>
            </table-wrap>
          </sec>
          <sec>
            <title>Types of Impact</title>
            <p>The previously defined types of impact in the SEWA framework were confirmed by many included studies. Multiple additional types of impact were also identified: <italic>privacy/security</italic>, <italic>data quality</italic>, <italic>employee perception of EHR</italic>, <italic>financial</italic>, <italic>law/regulations</italic>, and <italic>workload</italic> (<xref ref-type="table" rid="table9">Table 9</xref>). <italic>Privacy/security</italic> relates not only to the impact a workaround has on the security and privacy of the data but also to the patient and organization itself. Data quality concerns the impact on, for example, loss of data, or a lower data quality because of spelling or formatting mistakes in the data. Moreover, workarounds can have a positive or negative financial impact [<xref ref-type="bibr" rid="ref58">58</xref>], may jeopardize laws and regulations [<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref75">75</xref>], and have a positive or negative impact on the workload of the user [<xref ref-type="bibr" rid="ref43">43</xref>].</p>
            <table-wrap position="float" id="table9">
              <label>Table 9</label>
              <caption>
                <p>Overview of types of impact and related included studies.</p>
              </caption>
              <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="190"/>
                <col width="480"/>
                <col width="330"/>
                <thead>
                  <tr valign="top">
                    <td>Impact</td>
                    <td>Description</td>
                    <td>Source</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td>Patient safety</td>
                    <td>The impact on the safety (physical and mental) of the patient</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref75">75</xref>-<xref ref-type="bibr" rid="ref77">77</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Effectiveness of care</td>
                    <td>The effectiveness and quality of the care process performed</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Efficiency of care</td>
                    <td>The impact on the efficiency of the care process in terms of time and resources expended</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref76">76</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Privacy and security (new)</td>
                    <td>Impact on the security and privacy of data related to the patient or organization</td>
                    <td>[<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref75">75</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Data quality (new)</td>
                    <td>Impact of workarounds on data quality (eg, loss of data or decreased data quality)</td>
                    <td>[<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref76">76</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Financial (new)</td>
                    <td>Financial implications because of the workaround</td>
                    <td>[<xref ref-type="bibr" rid="ref58">58</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Laws and regulations (new)</td>
                    <td>Legal conflicts resulting from the use of a workaround</td>
                    <td>[<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref75">75</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Workload (new)</td>
                    <td>An increase or decrease in workload of the EHR<sup>a</sup> user resulting from the use of a workaround</td>
                    <td>[<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  </tr>
                </tbody>
              </table>
              <table-wrap-foot>
                <fn id="table9fn1">
                  <p><sup>a</sup>EHR: electronic health record.</p>
                </fn>
              </table-wrap-foot>
            </table-wrap>
          </sec>
          <sec>
            <title>Possible Scopes</title>
            <p>Only a few studies explicitly discussed possible scopes (ie, entities impacted) of workarounds and resonated with those in the SEWA framework [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref77">77</xref>] (<xref ref-type="table" rid="table1">Table 10</xref>). No new possible scopes were identified.</p>
            <table-wrap position="float" id="table10">
              <label>Table 10</label>
              <caption>
                <p>Overview of possible scopes and related included studies.</p>
              </caption>
              <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="190"/>
                <col width="690"/>
                <col width="120"/>
                <thead>
                  <tr valign="top">
                    <td>Scope</td>
                    <td>Description</td>
                    <td>Source</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td>Patient</td>
                    <td>The workaround affects the patients in the care process</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref77">77</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Health care professional</td>
                    <td>The workaround affects the health care professionals such as physicians, nurses, and pharmacists</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Organization</td>
                    <td>The workaround affects the whole organization, including the supporting departments such as finance or legal</td>
                    <td>[<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]</td>
                  </tr>
                </tbody>
              </table>
            </table-wrap>
          </sec>
          <sec>
            <title>Revised Version of the SEWA Framework</title>
            <p>On the basis on the foregoing results, the original SEWA framework [<xref ref-type="bibr" rid="ref20">20</xref>] was revised to incorporate new rationales, attributes, types of impact, and possible scopes identified in the included studies (<xref rid="figure2" ref-type="fig">Figure 2</xref>). The revised SEWA framework still comprises 2 major parts. The first part concerns the work system and its components (inspired by the SEIPS framework), [<xref ref-type="bibr" rid="ref21">21</xref>] constituting the context in which EHR workarounds are created. The work system components now include 22 rationales (previously 15) for workaround creation, and EHR workarounds are now defined by 8 attributes (previously 4). The second part concerns the possible scope of workarounds in terms of types and number of entities affected (still 3), as well as their impact on patient safety, the effectiveness of care, the efficiency of care, and 5 newly introduced types of impact. All new items in the framework are marked with asterisks.</p>
            <fig id="figure2" position="float">
              <label>Figure 2</label>
              <caption>
                <p>Revised SEWA framework with incorporated rationales, attributes, types of impact, and possible scopes identified in included studies. EHR: electronic health record; SEWA: Sociotechnical Electronic Health Record Workaround Analysis.</p>
              </caption>
              <graphic xlink:href="jmir_v24i3e33046_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
            <p>The recommendations [<xref ref-type="bibr" rid="ref20">20</xref>] for using a scoring mechanism to indicate whether the impact per workaround is favorable, unfavorable, or neutral, as well as to indicate whether the impact is immediate or only observable after a certain period (<italic>direct/time lag</italic>) remain. However, we also recommend the inclusion of a scoring mechanism to indicate the number of patients and health care professionals and organizational units affected per applicable scope. This is in line with Carayon et al [<xref ref-type="bibr" rid="ref53">53</xref>], who distinguished between workarounds having an impact at an individual or <italic>team level</italic> (eg, an entire team of nurses in a certain hospital ward). Applying a scoring mechanism allows for a more substantiated view when analyzing and prioritizing various identified workarounds for resolution.</p>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>A scoping review was performed to theoretically validate the SEWA framework [<xref ref-type="bibr" rid="ref20">20</xref>] and refine and enrich it with newly identified rationales, attributes, types of impact, and possible scopes of EHR workarounds. The scoping review retrieved 737 studies, of which 62 (8.4%) were included. The included studies provided extensive support for nearly all the items included in the original SEWA framework. SEWA was revised and enriched with 7 new rationales, 4 attributes, and 5 types of impact of EHR workarounds mentioned in the included studies. The definitions of several existing rationales were also refined. As a result, SEWA is now grounded in the existing body of peer-reviewed empirical evidence on EHR workarounds published between 2010 and 2021. In addition, this revised version is likely also applicable in a wider range of health care settings as input for the original SEWA framework that came from a single comprehensive case study on EHR workarounds in an academic hospital.</p>
      </sec>
      <sec>
        <title>Comparison With the Literature</title>
        <p>The results of this scoping review are in line with prior research and reviews of EHR workarounds. In an integrative review, Fraczkowski et al [<xref ref-type="bibr" rid="ref78">78</xref>] examined nurse workarounds in EHR use. The categories defined in the review by Fraczkowski et al [<xref ref-type="bibr" rid="ref78">78</xref>] are similar to the work system components defined in SEWA, with the exception of <italic>usability</italic> being a separate rationale in the SEWA framework under the work system component <italic>EHR system and related technology</italic> [<xref ref-type="bibr" rid="ref20">20</xref>]. The <italic>patient</italic> category in the review by Fraczkowski et al [<xref ref-type="bibr" rid="ref78">78</xref>] is defined as an impact and scope category in SEWA [<xref ref-type="bibr" rid="ref20">20</xref>]. Finally, Fraczkowski et al [<xref ref-type="bibr" rid="ref78">78</xref>], similar to Koppel et al [<xref ref-type="bibr" rid="ref18">18</xref>], did not include a work system component for <italic>person(s)</italic> (the users of the EHR) as a category. Our scoping review is one of the few studies that investigated the entire spectrum of EHR users. On the one hand, we included studies of all types of health care professionals in primary, secondary, and tertiary care who make use of an EHR in their clinical practice, whereas other reviews merely focused on a specific population such as physicians, nurses, or secretary personnel [<xref ref-type="bibr" rid="ref78">78</xref>]. On the other hand, we excluded studies researching workarounds in the use of barcode medication administration systems, whereas other reviews did not [<xref ref-type="bibr" rid="ref78">78</xref>].</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>To maximize the capture of relevant information on EHR workarounds, comprehensive and structured searches were conducted in MEDLINE, Embase, CINAHL, Cochrane, and IEEE databases. Data charting templates and analytic frames were used to extract relevant information from the reviewed studies and compare with pre-existing items in the SEWA framework.</p>
        <p>A total of 2 research team members participated in the review process for both the title and abstract and full-text review phases, with a Cohen κ value of &#62;0.9. This indicates an adequate interrater agreement. Despite this, our scoping review is at risk for selection bias, as we did not identify all available data, such as gray literature on EHR workarounds. There is a chance that relevant but nonincluded studies may use terminology other than the terms included in the search queries.</p>
        <p>The broad scope of the retrieved information on EHR workarounds and the different types of studies reporting a particular issue made using a formal meta-analytic method to quantitatively assess the quality of the studies and evidence of retrieved information difficult. However, given the purpose of the scoping review to theoretically validate and refine the SEWA framework, we do not consider this limitation.</p>
      </sec>
      <sec>
        <title>Implications for Practice and Future Research</title>
        <p>Multidisciplinary teams (comprising, for example, physicians, nurses, management, and EHR developers) can use the revised SEWA framework to identify, analyze, prioritize, and resolve workarounds related to EHR use more accurately. Similarly, the consequences of current and future configurations of the work system (health care professionals’ work processes and activities in relation to their EHR use) can be assessed and discussed in greater detail to determine how a design and redesign of the work system would positively or negatively affect the interaction between work system components. Finally, as workarounds are subject to gradual change (eg, personal changes in experience with the EHR, system updates to the EHR, and hospital policies), more detailed snapshots of the work system using SEWA can be taken over time and compared so as to gain valuable insights into how EHR workarounds evolve over time.</p>
        <p>Concerning future research, EHR systems are continuously subject to technological evolution by developments in, for example, artificial intelligence, machine learning, and telemedicine. This may lead to the creation of hitherto unidentified rationales, attributes, possible scopes, and types of impact of workarounds on users, patients, and health care organizations. Similarly, more studies on EHR workarounds will continue to emerge that may report novel insights not incorporated into the revised SEWA framework. Therefore, we expect that SEWA needs a continuous process of refinement over time. This could be done by repeating the scoping review using the described search strategy, search queries, and inclusion and exclusion criteria.</p>
        <p>In addition, although the revised SEWA framework is now theoretically validated, refined, and enriched, practical validation is still required. The same holds true when investigating its practicality. The firsthand experience from the application of SEWA in practice could yield suggestions for further improvement. A related suggestion is that although the framework helps in identifying and analyzing workarounds, a prioritization method for handling these issues is likely required, as workarounds are generally abundant in any organization, and resources to resolve them are finite. Therefore, the framework could benefit from being extended with prioritization mechanisms and weighting factors for deciding which workarounds require priority. Similarly, the framework could be translated into a practical tool such as a scoring matrix to facilitate use by practitioners.</p>
        <p>Finally, the applicability of the SEWA framework could be explored for systems other than EHRs (eg, enterprise resource planning, customer relationship management, and content management) and in other settings (eg, nonacademic hospitals and general practitioner practices) and even in other industries (eg, financial services and manufacturing) after appropriate validation. Although SEWA has an explicit focus on EHRs used in health care, we expect many of the described workaround rationales and attributes to be applicable to other systems, settings, and industries.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Descriptive data template that was captured per included study.</p>
        <media xlink:href="jmir_v24i3e33046_app1.docx" xlink:title="DOCX File , 13 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Analytic frame with workaround-related data captured per study.</p>
        <media xlink:href="jmir_v24i3e33046_app2.docx" xlink:title="DOCX File , 13 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">PRISMA</term>
          <def>
            <p>Preferred Reporting Item for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">SEIPS</term>
          <def>
            <p>Systems Engineering Initiative for Patient Safety</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">SEWA</term>
          <def>
            <p>Sociotechnical Electronic Health Record Workaround Analysis</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="con">
        <p>VB, FH, and MJ conceived and designed the study. FH collected the data. VB and FH analyzed the data and wrote the manuscript. VB and MJ edited the manuscript. All authors read and approved the final manuscript.</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>Howe</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Hettinger</surname>
              <given-names>AZ</given-names>
            </name>
            <name name-style="western">
              <surname>Ratwani</surname>
              <given-names>RM</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record usability issues and potential contribution to patient harm</article-title>
          <source>J Am Med Assoc</source>
          <year>2018</year>
          <month>03</month>
          <day>27</day>
          <volume>319</volume>
          <issue>12</issue>
          <fpage>1276</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29584833"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jama.2018.1171</pub-id>
          <pub-id pub-id-type="medline">29584833</pub-id>
          <pub-id pub-id-type="pii">2676098</pub-id>
          <pub-id pub-id-type="pmcid">PMC5885839</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ratwani</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Savage</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Will</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fong</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Karavite</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Muthu</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rivera</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gibson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Asmonga</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Moscovitch</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Grundmeier</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rising</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Identifying electronic health record usability and safety challenges in pediatric settings</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2018</year>
          <month>11</month>
          <volume>37</volume>
          <issue>11</issue>
          <fpage>1752</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2018.0699</pub-id>
          <pub-id pub-id-type="medline">30395517</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>Melnick</surname>
              <given-names>ER</given-names>
            </name>
            <name name-style="western">
              <surname>Dyrbye</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>Sinsky</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Trockel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Nedelec</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tutty</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Shanafelt</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>The association between perceived electronic health record usability and professional burnout among US physicians</article-title>
          <source>Mayo Clin Proc</source>
          <year>2020</year>
          <month>03</month>
          <volume>95</volume>
          <issue>3</issue>
          <fpage>476</fpage>
          <lpage>87</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0025-6196(19)30836-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.mayocp.2019.09.024</pub-id>
          <pub-id pub-id-type="medline">31735343</pub-id>
          <pub-id pub-id-type="pii">S0025-6196(19)30836-5</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>Shanafelt</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Dyrbye</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>CP</given-names>
            </name>
          </person-group>
          <article-title>Addressing physician burnout: the way forward</article-title>
          <source>J Am Med Assoc</source>
          <year>2017</year>
          <month>03</month>
          <day>07</day>
          <volume>317</volume>
          <issue>9</issue>
          <fpage>901</fpage>
          <lpage>2</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2017.0076</pub-id>
          <pub-id pub-id-type="medline">28196201</pub-id>
          <pub-id pub-id-type="pii">2603408</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Akbar</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Mark</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Prausnitz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Warton</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>East</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Moeller</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Reed</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Lieu</surname>
              <given-names>TA</given-names>
            </name>
          </person-group>
          <article-title>Physician stress during electronic health record inbox work: in situ measurement with wearable sensors</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>04</month>
          <day>28</day>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>e24014</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/4/e24014/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24014</pub-id>
          <pub-id pub-id-type="medline">33908888</pub-id>
          <pub-id pub-id-type="pii">v9i4e24014</pub-id>
          <pub-id pub-id-type="pmcid">PMC8116996</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tai-Seale</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Olson</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Morikawa</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Durbin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Luft</surname>
              <given-names>HS</given-names>
            </name>
          </person-group>
          <article-title>Electronic health record logs indicate that physicians split time evenly between seeing patients and desktop medicine</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2017</year>
          <month>04</month>
          <day>01</day>
          <volume>36</volume>
          <issue>4</issue>
          <fpage>655</fpage>
          <lpage>62</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28373331"/>
          </comment>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2016.0811</pub-id>
          <pub-id pub-id-type="medline">28373331</pub-id>
          <pub-id pub-id-type="pii">36/4/655</pub-id>
          <pub-id pub-id-type="pmcid">PMC5546411</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>Sinsky</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Colligan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Prgomet</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reynolds</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goeders</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tutty</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Blike</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Allocation of physician time in ambulatory practice: a time and motion study in 4 specialties</article-title>
          <source>Ann Intern Med</source>
          <year>2016</year>
          <month>09</month>
          <day>06</day>
          <volume>165</volume>
          <issue>11</issue>
          <fpage>753</fpage>
          <pub-id pub-id-type="doi">10.7326/m16-0961</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>Tsou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lehmann</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Michel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Solomon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Possanza</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gandhi</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Safe practices for copy and paste in the EHR: systematic review, recommendations, and novel model for health IT collaboration</article-title>
          <source>Appl Clin Inform</source>
          <year>2017</year>
          <month>12</month>
          <day>20</day>
          <volume>26</volume>
          <issue>01</issue>
          <fpage>12</fpage>
          <lpage>34</lpage>
          <pub-id pub-id-type="doi">10.4338/aci-2016-09-r-0150</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>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>New unintended adverse consequences of electronic health records</article-title>
          <source>Yearb Med Inform</source>
          <year>2018</year>
          <month>03</month>
          <day>06</day>
          <volume>25</volume>
          <issue>01</issue>
          <fpage>7</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.15265/iy-2016-023</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Guappone</surname>
              <given-names>KP</given-names>
            </name>
            <name name-style="western">
              <surname>Dykstra</surname>
              <given-names>RH</given-names>
            </name>
          </person-group>
          <article-title>Types of unintended consequences related to computerized provider order entry</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2006</year>
          <month>09</month>
          <day>01</day>
          <volume>13</volume>
          <issue>5</issue>
          <fpage>547</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="doi">10.1197/jamia.m2042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Dykstra</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Guappone</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Carpenter</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Seshadri</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Categorizing the unintended sociotechnical consequences of computerized provider order entry</article-title>
          <source>Int J Med Inform</source>
          <year>2007</year>
          <month>06</month>
          <volume>76 Suppl 1</volume>
          <fpage>21</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2006.05.017</pub-id>
          <pub-id pub-id-type="medline">16793330</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(06)00138-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Poon</surname>
              <given-names>EG</given-names>
            </name>
            <name name-style="western">
              <surname>Guappone</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Dykstra</surname>
              <given-names>RH</given-names>
            </name>
          </person-group>
          <article-title>The extent and importance of unintended consequences related to computerized provider order entry</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2007</year>
          <month>07</month>
          <day>01</day>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>415</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.1197/jamia.m2373</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Guappone</surname>
              <given-names>KP</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Dykstra</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Ash</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>Computerized provider order entry adoption: implications for clinical workflow</article-title>
          <source>J Gen Intern Med</source>
          <year>2009</year>
          <month>01</month>
          <day>20</day>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>21</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/19020942"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-008-0857-9</pub-id>
          <pub-id pub-id-type="medline">19020942</pub-id>
          <pub-id pub-id-type="pmcid">PMC2607519</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>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Potts</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bark</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Swinglehurst</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Tensions and paradoxes in electronic patient record research: a systematic literature review using the meta-narrative method</article-title>
          <source>Milbank Q</source>
          <year>2009</year>
          <month>12</month>
          <volume>87</volume>
          <issue>4</issue>
          <fpage>729</fpage>
          <lpage>88</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20021585"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/j.1468-0009.2009.00578.x</pub-id>
          <pub-id pub-id-type="medline">20021585</pub-id>
          <pub-id pub-id-type="pii">MILQ578</pub-id>
          <pub-id pub-id-type="pmcid">PMC2888022</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>Blijleven</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Koelemeijer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Identifying and eliminating inefficiencies in information system usage: a lean perspective</article-title>
          <source>Int J Med Inform</source>
          <year>2017</year>
          <month>11</month>
          <volume>107</volume>
          <fpage>40</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2017.08.005</pub-id>
          <pub-id pub-id-type="medline">29029690</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(17)30204-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Halbesleben</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wakefield</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wakefield</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Work-arounds in health care settings: literature review and research agenda</article-title>
          <source>Health Care Manage Rev</source>
          <year>2008</year>
          <volume>33</volume>
          <issue>1</issue>
          <fpage>2</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1097/01.HMR.0000304495.95522.ca</pub-id>
          <pub-id pub-id-type="medline">18091439</pub-id>
          <pub-id pub-id-type="pii">00004010-200801000-00002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kobayashi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fussell</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Seagull</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Work coordination, workflow, and workarounds in a medical context</article-title>
          <source>Proceedings of the  CHI '05 Extended Abstracts on Human Factors in Computing Systems</source>
          <year>2005</year>
          <conf-name>CHI05: CHI 2005 Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>April 2 - 7, 2005</conf-date>
          <conf-loc>Portland OR USA</conf-loc>
          <fpage>1561</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="doi">10.1145/1056808.1056966</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>Koppel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wetterneck</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Telles</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Karsh</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Workarounds to barcode medication administration systems: their occurrences, causes, and threats to patient safety</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2008</year>
          <month>07</month>
          <day>01</day>
          <volume>15</volume>
          <issue>4</issue>
          <fpage>408</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.1197/jamia.m2616</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>Blijleven</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Koelemeijer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wetzels</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Workarounds emerging from electronic health record system usage: consequences for patient safety, effectiveness of care, and efficiency of care</article-title>
          <source>JMIR Hum Factors</source>
          <year>2017</year>
          <month>10</month>
          <day>05</day>
          <volume>4</volume>
          <issue>4</issue>
          <fpage>e27</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2017/4/e27/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/humanfactors.7978</pub-id>
          <pub-id pub-id-type="medline">28982645</pub-id>
          <pub-id pub-id-type="pii">v4i4e27</pub-id>
          <pub-id pub-id-type="pmcid">PMC5649044</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>Blijleven</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Koelemeijer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>SEWA: a framework for sociotechnical analysis of electronic health record system workarounds</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>05</month>
          <volume>125</volume>
          <fpage>71</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.02.012</pub-id>
          <pub-id pub-id-type="medline">30914183</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)30460-X</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>Holden</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Carayon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gurses</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Hoonakker</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hundt</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Ozok</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Rivera-Rodriguez</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>SEIPS 2.0: a human factors framework for studying and improving the work of healthcare professionals and patients</article-title>
          <source>Ergonomics</source>
          <year>2013</year>
          <month>11</month>
          <volume>56</volume>
          <issue>11</issue>
          <fpage>1669</fpage>
          <lpage>86</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24088063"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/00140139.2013.838643</pub-id>
          <pub-id pub-id-type="medline">24088063</pub-id>
          <pub-id pub-id-type="pmcid">PMC3835697</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>Blijleven</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Koelemeijer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jaspers</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Exploring workarounds related to electronic health record system usage: a study protocol</article-title>
          <source>JMIR Res Protoc</source>
          <year>2017</year>
          <month>04</month>
          <day>28</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e72</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchprotocols.org/2017/4/e72/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/resprot.6766</pub-id>
          <pub-id pub-id-type="medline">28455273</pub-id>
          <pub-id pub-id-type="pii">v6i4e72</pub-id>
          <pub-id pub-id-type="pmcid">PMC5429437</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>Munn</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>MDJ</given-names>
            </name>
            <name name-style="western">
              <surname>Stern</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Tufanaru</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McArthur</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Aromataris</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Systematic review or scoping review? Guidance for authors when choosing between a systematic or scoping review approach</article-title>
          <source>BMC Med Res Methodol</source>
          <year>2018</year>
          <month>11</month>
          <day>19</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>143</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/s12874-018-0611-x"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12874-018-0611-x</pub-id>
          <pub-id pub-id-type="medline">30453902</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12874-018-0611-x</pub-id>
          <pub-id pub-id-type="pmcid">PMC6245623</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>Campbell</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Quincy</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Osserman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>OK</given-names>
            </name>
          </person-group>
          <article-title>Coding in-depth semistructured interviews: problems of unitization and intercoder reliability and agreement</article-title>
          <source>Sociolog Methods Res</source>
          <year>2013</year>
          <month>08</month>
          <day>21</day>
          <volume>42</volume>
          <issue>3</issue>
          <fpage>294</fpage>
          <lpage>320</lpage>
          <pub-id pub-id-type="doi">10.1177/0049124113500475</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>Dudding</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gephart</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Carrington</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Neonatal nurses experience unintended consequences and risks to patient safety with electronic health records</article-title>
          <source>Comput Inform Nurs</source>
          <year>2018</year>
          <month>04</month>
          <volume>36</volume>
          <issue>4</issue>
          <fpage>167</fpage>
          <lpage>76</lpage>
          <pub-id pub-id-type="doi">10.1097/CIN.0000000000000406</pub-id>
          <pub-id pub-id-type="medline">29194056</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>Niazkhani</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Pirnejad</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>van der Sijs</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Aarts</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the medication process in the context of CPOE use: the significance of working around the system</article-title>
          <source>Int J Med Inform</source>
          <year>2011</year>
          <month>07</month>
          <volume>80</volume>
          <issue>7</issue>
          <fpage>490</fpage>
          <lpage>506</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2011.03.009</pub-id>
          <pub-id pub-id-type="medline">21555237</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(11)00075-X</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>Holden</surname>
              <given-names>RJ</given-names>
            </name>
          </person-group>
          <article-title>What stands in the way of technology-mediated patient safety improvements?: a study of facilitators and barriers to physicians' use of electronic health records</article-title>
          <source>J Patient Saf</source>
          <year>2011</year>
          <month>12</month>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>193</fpage>
          <lpage>203</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22064624"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/PTS.0b013e3182388cfa</pub-id>
          <pub-id pub-id-type="medline">22064624</pub-id>
          <pub-id pub-id-type="pmcid">PMC3220192</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>Salahuddin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ismail</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Abd Ghani</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Aboobaider</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Hasan Basari</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Exploring the contributing factors to workarounds to the hospital information system in Malaysian hospitals</article-title>
          <source>J Eval Clin Pract</source>
          <year>2020</year>
          <month>10</month>
          <day>20</day>
          <volume>26</volume>
          <issue>5</issue>
          <fpage>1416</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1111/jep.13326</pub-id>
          <pub-id pub-id-type="medline">31863517</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>Baysari</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gigante</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Moran</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sandaradura</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Richardson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sandhu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lehnbom</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Redesign of computerized decision support to improve antimicrobial prescribing</article-title>
          <source>Appl Clin Inform</source>
          <year>2017</year>
          <month>12</month>
          <day>20</day>
          <volume>08</volume>
          <issue>03</issue>
          <fpage>949</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.4338/aci2017040069</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ser</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Robertson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A qualitative exploration of workarounds related to the implementation of national electronic health records in early adopter mental health hospitals</article-title>
          <source>PLoS One</source>
          <year>2014</year>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e77669</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0077669"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0077669</pub-id>
          <pub-id pub-id-type="medline">24454678</pub-id>
          <pub-id pub-id-type="pii">PONE-D-12-12587</pub-id>
          <pub-id pub-id-type="pmcid">PMC3894172</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stevenson</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Israelsson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Petersson</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bath</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Factors influencing the quality of vital sign data in electronic health records: a qualitative study</article-title>
          <source>J Clin Nurs</source>
          <year>2018</year>
          <month>03</month>
          <day>08</day>
          <volume>27</volume>
          <issue>5-6</issue>
          <fpage>1276</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1111/jocn.14174</pub-id>
          <pub-id pub-id-type="medline">29149483</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>Ali</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cornford</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Klecun</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Exploring control in health information systems implementation</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2010</year>
          <volume>160</volume>
          <issue>Pt 1</issue>
          <fpage>681</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="medline">20841773</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>Crosson</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Etz</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Straus</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Eisenman</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Meaningful use of electronic prescribing in 5 exemplar primary care practices</article-title>
          <source>Ann Fam Med</source>
          <year>2011</year>
          <month>09</month>
          <day>12</day>
          <volume>9</volume>
          <issue>5</issue>
          <fpage>392</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=21911757"/>
          </comment>
          <pub-id pub-id-type="doi">10.1370/afm.1261</pub-id>
          <pub-id pub-id-type="medline">21911757</pub-id>
          <pub-id pub-id-type="pii">9/5/392</pub-id>
          <pub-id pub-id-type="pmcid">PMC3185481</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>Flanagan</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Saleem</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Millitello</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Russ</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Doebbeling</surname>
              <given-names>BN</given-names>
            </name>
          </person-group>
          <article-title>Paper- and computer-based workarounds to electronic health record use at three benchmark institutions</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2013</year>
          <month>06</month>
          <day>01</day>
          <volume>20</volume>
          <issue>e1</issue>
          <fpage>59</fpage>
          <lpage>66</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23492593"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2012-000982</pub-id>
          <pub-id pub-id-type="medline">23492593</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2012-000982</pub-id>
          <pub-id pub-id-type="pmcid">PMC3715348</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Horsky</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Drucker</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Ramelson</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Higher accuracy of complex medication reconciliation through improved design of electronic tools</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>05</month>
          <day>01</day>
          <volume>25</volume>
          <issue>5</issue>
          <fpage>465</fpage>
          <lpage>75</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29121197"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocx127</pub-id>
          <pub-id pub-id-type="medline">29121197</pub-id>
          <pub-id pub-id-type="pii">4601882</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647001</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>Djalali</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ursprung</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rosemann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Senn</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Tandjung</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Undirected health IT implementation in ambulatory care favors paper-based workarounds and limits health data exchange</article-title>
          <source>Int J Med Inform</source>
          <year>2015</year>
          <month>11</month>
          <volume>84</volume>
          <issue>11</issue>
          <fpage>920</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2015.08.001</pub-id>
          <pub-id pub-id-type="medline">26296433</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(15)30025-3</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>Watson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Skipper</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Steury</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Walsh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Levin</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Inpatient nursing care and early warning scores: a workflow mismatch</article-title>
          <source>J Nurs Care Qual</source>
          <year>2014</year>
          <volume>29</volume>
          <issue>3</issue>
          <fpage>215</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1097/NCQ.0000000000000058</pub-id>
          <pub-id pub-id-type="medline">24569518</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>Hysong</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sawhney</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Espadas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Provider management strategies of abnormal test result alerts: a cognitive task analysis</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2010</year>
          <month>01</month>
          <day>01</day>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>71</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1197/jamia.m3200</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saleem</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Russ</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Neddo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Blades</surname>
              <given-names>PT</given-names>
            </name>
            <name name-style="western">
              <surname>Doebbeling</surname>
              <given-names>BN</given-names>
            </name>
            <name name-style="western">
              <surname>Foresman</surname>
              <given-names>BH</given-names>
            </name>
          </person-group>
          <article-title>Paper persistence, workarounds, and communication breakdowns in computerized consultation management</article-title>
          <source>Int J Med Inform</source>
          <year>2011</year>
          <month>07</month>
          <volume>80</volume>
          <issue>7</issue>
          <fpage>466</fpage>
          <lpage>79</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2011.03.016</pub-id>
          <pub-id pub-id-type="medline">21530383</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(11)00092-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ihlebæk</surname>
              <given-names>HM</given-names>
            </name>
          </person-group>
          <article-title>Lost in translation - Silent reporting and electronic patient records in nursing handovers: an ethnographic study</article-title>
          <source>Int J Nurs Stud</source>
          <year>2020</year>
          <month>09</month>
          <volume>109</volume>
          <fpage>103636</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0020-7489(20)30120-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijnurstu.2020.103636</pub-id>
          <pub-id pub-id-type="medline">32593879</pub-id>
          <pub-id pub-id-type="pii">S0020-7489(20)30120-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stevenson</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Israelsson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nilsson</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Petersson</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bath</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Vital sign documentation in electronic records: the development of workarounds</article-title>
          <source>Health Informatics J</source>
          <year>2016</year>
          <month>08</month>
          <day>19</day>
          <fpage>206</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1177/1460458216663024</pub-id>
          <pub-id pub-id-type="medline">27542887</pub-id>
          <pub-id pub-id-type="pii">1460458216663024</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>Carrington</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Effken</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Strengths and limitations of the electronic health record for documenting clinical events</article-title>
          <source>Comput Inform Nurs</source>
          <year>2011</year>
          <month>06</month>
          <volume>29</volume>
          <issue>6</issue>
          <fpage>360</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1097/NCN.0b013e3181fc4139</pub-id>
          <pub-id pub-id-type="medline">21107239</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Nurses' electronic medical record workarounds in a tertiary teaching hospital</article-title>
          <source>Comput Inform Nurs</source>
          <year>2021</year>
          <month>03</month>
          <day>08</day>
          <volume>39</volume>
          <issue>7</issue>
          <fpage>367</fpage>
          <lpage>74</lpage>
          <pub-id pub-id-type="doi">10.1097/CIN.0000000000000692</pub-id>
          <pub-id pub-id-type="medline">33675300</pub-id>
          <pub-id pub-id-type="pii">00024665-202107000-00006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rathert</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Porter</surname>
              <given-names>TH</given-names>
            </name>
            <name name-style="western">
              <surname>Mittler</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Fleig-Palmer</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Seven years after meaningful use: physicians’ and nurses’ experiences with electronic health records</article-title>
          <source>Health Care Manage Rev</source>
          <year>2019</year>
          <volume>44</volume>
          <issue>1</issue>
          <fpage>30</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.1097/hmr.0000000000000168</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Assis-Hassid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Grosz</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Zimlichman</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Rozenblum</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Assessing EHR use during hospital morning rounds: a multi-faceted study</article-title>
          <source>PLoS One</source>
          <year>2019</year>
          <month>2</month>
          <day>25</day>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>e0212816</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0212816"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0212816</pub-id>
          <pub-id pub-id-type="medline">30802267</pub-id>
          <pub-id pub-id-type="pii">PONE-D-18-33695</pub-id>
          <pub-id pub-id-type="pmcid">PMC6388927</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cresswell</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Worth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Integration of a nationally procured electronic health record system into user work practices</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2012</year>
          <month>03</month>
          <day>08</day>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>15</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-12-15"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-12-15</pub-id>
          <pub-id pub-id-type="medline">22400978</pub-id>
          <pub-id pub-id-type="pii">1472-6947-12-15</pub-id>
          <pub-id pub-id-type="pmcid">PMC3313868</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Menon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Workarounds and test results follow-up in electronic health record-based primary care</article-title>
          <source>Appl Clin Inform</source>
          <year>2017</year>
          <month>12</month>
          <day>16</day>
          <volume>07</volume>
          <issue>02</issue>
          <fpage>543</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.4338/aci-2015-10-ra-0135</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Van Der Sijs</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Rootjes</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Aarts</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The shift in workarounds upon implementation of computerized physician order entry</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2011</year>
          <volume>169</volume>
          <fpage>290</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="medline">21893759</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barrett</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Stephens</surname>
              <given-names>KK</given-names>
            </name>
          </person-group>
          <article-title>Making Electronic Health Records (EHRs) work: informal talk and workarounds in healthcare organizations</article-title>
          <source>Health Commun</source>
          <year>2017</year>
          <month>08</month>
          <day>27</day>
          <volume>32</volume>
          <issue>8</issue>
          <fpage>1004</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1080/10410236.2016.1196422</pub-id>
          <pub-id pub-id-type="medline">27463257</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>O'Malley</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Grossman</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>GR</given-names>
            </name>
            <name name-style="western">
              <surname>Kemper</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Pham</surname>
              <given-names>HH</given-names>
            </name>
          </person-group>
          <article-title>Are electronic medical records helpful for care coordination? Experiences of physician practices</article-title>
          <source>J Gen Intern Med</source>
          <year>2010</year>
          <month>03</month>
          <day>22</day>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>177</fpage>
          <lpage>85</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20033621"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11606-009-1195-2</pub-id>
          <pub-id pub-id-type="medline">20033621</pub-id>
          <pub-id pub-id-type="pmcid">PMC2839331</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bowen</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>BC</given-names>
            </name>
            <name name-style="western">
              <surname>Ilgen</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Irby</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Cate</surname>
              <given-names>OT</given-names>
            </name>
          </person-group>
          <article-title>Chart stalking, list making, and physicians' efforts to track patients' outcomes after transitioning responsibility</article-title>
          <source>Med Educ</source>
          <year>2018</year>
          <month>04</month>
          <day>30</day>
          <volume>52</volume>
          <issue>4</issue>
          <fpage>404</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1111/medu.13509</pub-id>
          <pub-id pub-id-type="medline">29383741</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bristol</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nibbelink</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gephart</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Carrington</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Nurses' use of positive deviance when encountering electronic health records-related unintended consequences</article-title>
          <source>Nurs Adm Q</source>
          <year>2018</year>
          <volume>42</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.1097/NAQ.0000000000000264</pub-id>
          <pub-id pub-id-type="medline">29194338</pub-id>
          <pub-id pub-id-type="pii">00006216-201801000-00014</pub-id>
        </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>Carayon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hundt</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Hoonakker</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Technology barriers and strategies in coordinating care for chronically ill patients</article-title>
          <source>Appl Ergon</source>
          <year>2019</year>
          <month>07</month>
          <volume>78</volume>
          <fpage>240</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31046955"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2019.03.009</pub-id>
          <pub-id pub-id-type="medline">31046955</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(19)30061-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC6529186</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>Schiff</surname>
              <given-names>GD</given-names>
            </name>
            <name name-style="western">
              <surname>Amato</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Eguale</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Boehne</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Koppel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rashidee</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Elson</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>Whitney</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Thach</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Seger</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>Computerised physician order entry-related medication errors: analysis of reported errors and vulnerability testing of current systems</article-title>
          <source>BMJ Qual Saf</source>
          <year>2015</year>
          <month>04</month>
          <day>16</day>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>264</fpage>
          <lpage>71</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://qualitysafety.bmj.com/lookup/pmidlookup?view=long&#38;pmid=25595599"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2014-003555</pub-id>
          <pub-id pub-id-type="medline">25595599</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2014-003555</pub-id>
          <pub-id pub-id-type="pmcid">PMC4392214</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>Staggers</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jennings</surname>
              <given-names>BM</given-names>
            </name>
            <name name-style="western">
              <surname>Lasome</surname>
              <given-names>CE</given-names>
            </name>
          </person-group>
          <article-title>A usability assessment of AHLTA in ambulatory clinics at a military medical center</article-title>
          <source>Mil Med</source>
          <year>2010</year>
          <month>07</month>
          <volume>175</volume>
          <issue>7</issue>
          <fpage>518</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.7205/milmed-d-09-00285</pub-id>
          <pub-id pub-id-type="medline">20684457</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>Cresswell</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Mozaffar</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Workarounds to hospital electronic prescribing systems: a qualitative study in English hospitals</article-title>
          <source>BMJ Qual Saf</source>
          <year>2017</year>
          <month>07</month>
          <volume>26</volume>
          <issue>7</issue>
          <fpage>542</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2015-005149</pub-id>
          <pub-id pub-id-type="medline">27129493</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2015-005149</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>Bhattacharjee</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Murcko</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Fair</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Warholak</surname>
              <given-names>TL</given-names>
            </name>
          </person-group>
          <article-title>Medication prior authorization from the providers perspective: a prospective observational study</article-title>
          <source>Res Social Adm Pharm</source>
          <year>2019</year>
          <month>09</month>
          <volume>15</volume>
          <issue>9</issue>
          <fpage>1138</fpage>
          <lpage>44</lpage>
          <pub-id pub-id-type="doi">10.1016/j.sapharm.2018.09.019</pub-id>
          <pub-id pub-id-type="medline">30279130</pub-id>
          <pub-id pub-id-type="pii">S1551-7411(18)30154-2</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>Samaras</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Real</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Meunier</surname>
              <given-names>TS</given-names>
            </name>
          </person-group>
          <article-title>Recognizing nurse stakeholder dissonance as a critical determinant of patient safety in new healthcare information technologies</article-title>
          <source>Work</source>
          <year>2012</year>
          <volume>41 Suppl 1</volume>
          <fpage>1904</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.3233/WOR-2012-0406-1904</pub-id>
          <pub-id pub-id-type="medline">22316994</pub-id>
          <pub-id pub-id-type="pii">2271K3M825770883</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>Yeung</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lapinsky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Granton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Doran</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Cafazzo</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Examining nursing vital signs documentation workflow: barriers and opportunities in general internal medicine units</article-title>
          <source>J Clin Nurs</source>
          <year>2012</year>
          <month>04</month>
          <volume>21</volume>
          <issue>7-8</issue>
          <fpage>975</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1365-2702.2011.03937.x</pub-id>
          <pub-id pub-id-type="medline">22243491</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>Naughton</surname>
              <given-names>BD</given-names>
            </name>
          </person-group>
          <article-title>Medicine authentication technology: a quantitative study of incorrect quarantine, average response times and offline issues in a hospital setting</article-title>
          <source>BMJ Open</source>
          <year>2019</year>
          <month>02</month>
          <day>19</day>
          <volume>9</volume>
          <issue>2</issue>
          <fpage>e026619</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=30782947"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2018-026619</pub-id>
          <pub-id pub-id-type="medline">30782947</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2018-026619</pub-id>
          <pub-id pub-id-type="pmcid">PMC6367986</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>Sockolow</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bass</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Eberle</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Bowles</surname>
              <given-names>KH</given-names>
            </name>
          </person-group>
          <article-title>Homecare nurses' decision-making during admission care planning</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2016</year>
          <volume>225</volume>
          <fpage>28</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="medline">27332156</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>Slight</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Eguale</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Amato</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Seger</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Whitney</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Schiff</surname>
              <given-names>GD</given-names>
            </name>
          </person-group>
          <article-title>The vulnerabilities of computerized physician order entry systems: a qualitative study</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>03</month>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>311</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv135</pub-id>
          <pub-id pub-id-type="medline">26568606</pub-id>
          <pub-id pub-id-type="pii">ocv135</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>Balka</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Tolar</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Everyday ethical dilemmas arising with electronic record use in primary care</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2011</year>
          <volume>169</volume>
          <fpage>285</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="medline">21893758</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>Vest</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Issel</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Experience of using information systems in public health practice: findings from a qualitative study</article-title>
          <source>Online J Public Health Inform</source>
          <year>2014</year>
          <month>02</month>
          <day>05</day>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>227</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24678380"/>
          </comment>
          <pub-id pub-id-type="doi">10.5210/ojphi.v5i3.4847</pub-id>
          <pub-id pub-id-type="medline">24678380</pub-id>
          <pub-id pub-id-type="pii">ojphi-05-e227</pub-id>
          <pub-id pub-id-type="pmcid">PMC3959909</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Steele Gray</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Barnsley</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gagnon</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Belzile</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kenealy</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sheridan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wodchis</surname>
              <given-names>WP</given-names>
            </name>
          </person-group>
          <article-title>Using information communication technology in models of integrated community-based primary health care: exploring ICT in the iCOACH study</article-title>
          <source>Int J Integr Care</source>
          <year>2017</year>
          <month>10</month>
          <day>17</day>
          <volume>17</volume>
          <issue>5</issue>
          <fpage>144</fpage>
          <pub-id pub-id-type="doi">10.5334/ijic.3452</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Østensen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bragstad</surname>
              <given-names>LK</given-names>
            </name>
            <name name-style="western">
              <surname>Hardiker</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Hellesø</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Nurses' information practice in municipal health care-A web-like landscape</article-title>
          <source>J Clin Nurs</source>
          <year>2019</year>
          <month>07</month>
          <day>23</day>
          <volume>28</volume>
          <issue>13-14</issue>
          <fpage>2706</fpage>
          <lpage>16</lpage>
          <pub-id pub-id-type="doi">10.1111/jocn.14873</pub-id>
          <pub-id pub-id-type="medline">30938870</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>Remen</surname>
              <given-names>VM</given-names>
            </name>
            <name name-style="western">
              <surname>Grimsmo</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Closing information gaps with shared electronic patient summaries: how much will it matter?</article-title>
          <source>Int J Med Inform</source>
          <year>2011</year>
          <month>11</month>
          <volume>80</volume>
          <issue>11</issue>
          <fpage>775</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2011.08.008</pub-id>
          <pub-id pub-id-type="medline">21956001</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(11)00172-9</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>Eikey</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Designing for privacy management in hospitals: understanding the gap between user activities and IT staff's understandings</article-title>
          <source>Int J Med Inform</source>
          <year>2015</year>
          <month>12</month>
          <volume>84</volume>
          <issue>12</issue>
          <fpage>1065</fpage>
          <lpage>75</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2015.09.006</pub-id>
          <pub-id pub-id-type="medline">26467571</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(15)30041-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shemilt</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Morecroft</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Ford</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Mackridge</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Inpatient prescribing systems used in NHS Acute Trusts across England: a managerial perspective</article-title>
          <source>Eur J Hosp Pharm</source>
          <year>2017</year>
          <month>07</month>
          <day>30</day>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>213</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ejhp.bmj.com/lookup/pmidlookup?view=long&#38;pmid=31156943"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/ejhpharm-2016-000905</pub-id>
          <pub-id pub-id-type="medline">31156943</pub-id>
          <pub-id pub-id-type="pii">ejhpharm-2016-000905</pub-id>
          <pub-id pub-id-type="pmcid">PMC6451506</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</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="http://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="ref71">
        <label>71</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Fred</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Vawdrey</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>Workarounds used by nurses to overcome design constraints of electronic health records</article-title>
          <source>Proceedings of the 11th International Congress on Nursing Informatics</source>
          <year>2012</year>
          <conf-name>International Congress in Nursing Informatics</conf-name>
          <conf-date>June 23-27, 2012</conf-date>
          <conf-loc>Montreal, Canada</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24199061"/>
          </comment>
        </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>Stanhope</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Matthews</surname>
              <given-names>EB</given-names>
            </name>
          </person-group>
          <article-title>Delivering person-centered care with an electronic health record</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <month>08</month>
          <day>22</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>168</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-019-0897-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-019-0897-6</pub-id>
          <pub-id pub-id-type="medline">31438960</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-019-0897-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC6704707</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>Swinglehurst</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Caring for the patient, caring for the record: an ethnographic study of 'back office' work in upholding quality of care in general practice</article-title>
          <source>BMC Health Serv Res</source>
          <year>2015</year>
          <month>04</month>
          <day>23</day>
          <volume>15</volume>
          <issue>1</issue>
          <fpage>177</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-015-0774-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-015-0774-7</pub-id>
          <pub-id pub-id-type="medline">25907436</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-015-0774-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC4408578</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>Friedman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Crosson</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Howard</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Pellerano</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Karsh</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Crabtree</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jaén</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>DJ</given-names>
            </name>
          </person-group>
          <article-title>A typology of electronic health record workarounds in small-to-medium size primary care practices</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2014</year>
          <month>02</month>
          <day>01</day>
          <volume>21</volume>
          <issue>e1</issue>
          <fpage>78</fpage>
          <lpage>83</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23904322"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2013-001686</pub-id>
          <pub-id pub-id-type="medline">23904322</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2013-001686</pub-id>
          <pub-id pub-id-type="pmcid">PMC3957384</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>Campbell</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>McCarty</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rieckmann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>McNeely</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rotrosen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bart</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Interpretation and integration of the federal substance use privacy protection rule in integrated health systems: a qualitative analysis</article-title>
          <source>J Subst Abuse Treat</source>
          <year>2019</year>
          <month>02</month>
          <volume>97</volume>
          <fpage>41</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30577898"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jsat.2018.11.005</pub-id>
          <pub-id pub-id-type="medline">30577898</pub-id>
          <pub-id pub-id-type="pii">S0740-5472(18)30216-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC6310476</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>Bramble</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Abbott</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Fuji</surname>
              <given-names>KT</given-names>
            </name>
            <name name-style="western">
              <surname>Paschal</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Siracuse</surname>
              <given-names>MV</given-names>
            </name>
            <name name-style="western">
              <surname>Galt</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Patient safety perspectives of providers and nurses: the experience of a rural ambulatory care practice using an EHR with E-prescribing</article-title>
          <source>J Rural Health</source>
          <year>2013</year>
          <month>03</month>
          <day>12</day>
          <volume>29</volume>
          <issue>4</issue>
          <fpage>383</fpage>
          <lpage>91</lpage>
          <pub-id pub-id-type="doi">10.1111/jrh.12015</pub-id>
          <pub-id pub-id-type="medline">24088212</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>Kandaswamy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hettinger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffman</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ratwani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Marquard</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Communication through the electronic health record: frequency and implications of free text orders</article-title>
          <source>JAMIA Open</source>
          <year>2020</year>
          <month>07</month>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>154</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32734153"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooaa020</pub-id>
          <pub-id pub-id-type="medline">32734153</pub-id>
          <pub-id pub-id-type="pii">ooaa020</pub-id>
          <pub-id pub-id-type="pmcid">PMC7382628</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>Fraczkowski</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Matson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez</surname>
              <given-names>KD</given-names>
            </name>
          </person-group>
          <article-title>Nurse workarounds in the electronic health record: an integrative review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>07</month>
          <day>01</day>
          <volume>27</volume>
          <issue>7</issue>
          <fpage>1149</fpage>
          <lpage>65</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32651588"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa050</pub-id>
          <pub-id pub-id-type="medline">32651588</pub-id>
          <pub-id pub-id-type="pii">5870050</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647365</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
