<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">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">v22i3e14855</article-id>
      <article-id pub-id-type="pmid">32167479</article-id>
      <article-id pub-id-type="doi">10.2196/14855</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Late Attempt to Involve End Users in the Design of Medication-Related Alerts: Survey Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hussain</surname>
            <given-names>Mustafa</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Alvarez</surname>
            <given-names>Celia</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Sabarguna</surname>
            <given-names>Subirosa</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Baysari</surname>
            <given-names>Melissa Therese</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Faculty of Health Sciences</institution>
            <institution>The University of Sydney</institution>
            <addr-line>Charles Perkins Centre D17</addr-line>
            <addr-line>Sydney, 2006</addr-line>
            <country>Australia</country>
            <phone>61 28627 9245</phone>
            <email>melissa.baysari@sydney.edu.au</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1645-9126</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Zheng</surname>
            <given-names>Wu Yi</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1159-4700</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Van Dort</surname>
            <given-names>Bethany</given-names>
          </name>
          <degrees>BMedSci</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0052-6400</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Reid-Anderson</surname>
            <given-names>Hannah</given-names>
          </name>
          <degrees>BNursing</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5287-4154</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Gronski</surname>
            <given-names>Mihaela</given-names>
          </name>
          <degrees>DEng</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4092-465X</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Kenny</surname>
            <given-names>Eliza</given-names>
          </name>
          <degrees>BNursing, MHSM</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7823-7740</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Faculty of Health Sciences</institution>
        <institution>The University of Sydney</institution>
        <addr-line>Sydney</addr-line>
        <country>Australia</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Centre for Health Systems &#38; Safety Research</institution>
        <institution>Australian Institute of Health Innovation</institution>
        <institution>Macquarie University</institution>
        <addr-line>Sydney</addr-line>
        <country>Australia</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Macquarie University Hospital</institution>
        <addr-line>Sydney</addr-line>
        <country>Australia</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Melissa Therese Baysari <email>melissa.baysari@sydney.edu.au</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>3</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>13</day>
        <month>3</month>
        <year>2020</year>
      </pub-date>
      <volume>22</volume>
      <issue>3</issue>
      <elocation-id>e14855</elocation-id>
      <history>
        <date date-type="received">
          <day>30</day>
          <month>5</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>14</day>
          <month>9</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>4</day>
          <month>12</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>16</day>
          <month>12</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Melissa Therese Baysari, Wu Yi Zheng, Bethany Van Dort, Hannah Reid-Anderson, Mihaela Gronski, Eliza Kenny. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 13.03.2020.</copyright-statement>
      <copyright-year>2020</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 http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2020/3/e14855" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>When users of electronic medical records (EMRs) are presented with large numbers of irrelevant computerized alerts, they experience alert fatigue, begin to ignore alert information, and override alerts without processing or heeding alert recommendations. Anecdotally, doctors at our study site were dissatisfied with the medication-related alerts being generated, both in terms of volume being experienced and clinical relevance.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to involve end users in the redesign of medication-related alerts in a hospital EMR, 4 years post implementation.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>This work was undertaken at a private not-for-profit teaching hospital in Sydney, Australia. Since EMR implementation in 2015, the organization elected to implement all medication-related alert types available in the system for prescribers: allergy and intolerance alerts, therapeutic duplication alerts, pregnancy alerts, and drug-drug interaction alerts. The EMR included no medication administration alerts for nurses. To obtain feedback on current alerts and suggestions for redesign, a Web-based survey was distributed to all doctors and nurses at the site via hospital mailing lists.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Despite a general dissatisfaction with alerts, very few end users completed the survey. In total, only 3.37% (36/1066) of doctors and 14.5% (60/411) of nurses took part. Approximately 90% (30/33) of doctors who responded held the view that too many alerts were triggered in the EMR. Doctors suggested that most alerts be removed and that alerts be more specific and less sensitive. In contrast, 97% (58/60) of the nurse respondents indicated that they would like to receive medication administration alerts in the EMR. Most nurses indicated that they would like to receive all the alert types available at all severity levels.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Attempting to engage with end users several years post implementation was challenging. Involving users so late in the implementation process may lead to clinicians viewing the provision of feedback to be futile. Seeking user feedback on usefulness, volume, and design of alerts is extremely valuable; however, we suggest this is undertaken early, preferably before system implementation.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>alert fatigue</kwd>
        <kwd>alerting</kwd>
        <kwd>medication alert systems</kwd>
        <kwd>clinical decision support</kwd>
        <kwd>hospital information systems</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Many studies have shown that medication-related computerized alerts embedded in hospital electronic medical records (EMRs) can result in significant changes to prescriber behavior [<xref ref-type="bibr" rid="ref1">1</xref>]. For example, introduction of dosing alerts for psychotropic medications in a US tertiary hospital led to an increase in the prescription of recommended daily doses from 19% to 29% and a reduction in the incidence of tenfold dosing errors from 5% to 3% [<xref ref-type="bibr" rid="ref2">2</xref>]. However, studies have also shown that computerized alerts can have no impact or a negative impact on prescribing [<xref ref-type="bibr" rid="ref1">1</xref>]. One of the main factors hampering alert effectiveness is alert overload. When users are presented with large numbers of irrelevant alerts, they experience alert fatigue [<xref ref-type="bibr" rid="ref3">3</xref>], begin to ignore alert information [<xref ref-type="bibr" rid="ref4">4</xref>], and override alerts (ie, click past the alert window) without processing or heeding alert recommendations [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>Despite international efforts to improve medication-related alerts, alert override rates remain as high as they were over a decade ago [<xref ref-type="bibr" rid="ref6">6</xref>]. Alert fatigue appears to be a widespread problem for users of EMRs, but there is limited evidence available on what constitutes a <italic>tolerable</italic> volume of irrelevant alerts for prescribers [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. How many is too many before alert fatigue sets in? With no answer to this question, many hospitals have chosen to enable the main decision support alerts available in their EMR, including drug-drug interaction, allergy, and dose range alerts, with some also implementing pregnancy and therapeutic duplication warnings [<xref ref-type="bibr" rid="ref9">9</xref>]. Our site was one such hospital, implementing all available medication-related alert types for prescribers.</p>
      <p>In this study, we describe an attempt that was made to involve end users in the redesign of medication-related alerts several years post implementation. Anecdotally, via informal discussions with doctors, we learned that doctors were dissatisfied with the alerts being generated, both in terms of volume being experienced and clinical relevance. We administered a Web-based survey to doctors and nurses to more systematically capture their views of medication-related alerts embedded in the hospital EMR and their suggestions for redesign.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Context</title>
        <p>This work was undertaken at a private not-for-profit teaching hospital, with approximately 150 beds, in Sydney, Australia. In 2015, the hospital implemented a single EMR in all wards and areas of the hospital. Before EMR implementation, a suite of fragmented clinical information systems was in place (an intensive care unit system, a general ward system, a medication management system, and a patient administration system). The single EMR was introduced to better support integration of care and to ensure efficient and effective delivery of health services. With respect to medication management, the system allowed prescribing, pharmacy review, and medication administration.</p>
      </sec>
      <sec>
        <title>Implementation of Medication-Related Alerts</title>
        <p>A core group of clinicians and administrative staff (information technology and billing) were consulted before EMR implementation, which included mainly heads of departments and units. Since EMR implementation, the organization elected to implement all medication-related alert types available in the system for prescribers: allergy and intolerance alerts, therapeutic duplication alerts, pregnancy alerts, and drug-drug interaction alerts. Not long after implementation, the alert configuration was changed so that only alerts classified as <italic>severe</italic> were displayed to doctors. All alerts were interruptive, appearing in an alert window that prevented prescribers from continuing with their orders until alerts were acknowledged. This could be done by selecting an override reason from a drop-down menu that appeared at the top of the alert screen (see <xref rid="figure1" ref-type="fig">Figure 1</xref>). The EMR included no medication administration alerts for nurses.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>An example showing two alerts that have been triggered simultaneously, an allergy alert and a drug-drug interaction alert.</p>
          </caption>
          <graphic xlink:href="jmir_v22i3e14855_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>User Engagement: Web-Based Survey</title>
        <p>A Web-based survey was distributed to all doctors (n=1066) and nurses (n=411) at the site via hospital mailing lists (see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Participation in the survey was voluntary, and no reimbursement was provided for participation. The survey was codeveloped with key stakeholders (researchers, doctors, nurses, pharmacists, and implementation staff) and comprised some basic demographic questions, questions on the current alerts in the system (for prescribers), and questions on preferences for changes to the system (for prescribers and nurses)—see <xref ref-type="supplementary-material" rid="app2">Multimedia Appendices 2</xref> and <xref ref-type="supplementary-material" rid="app3">3</xref>. Following distribution of the survey, a single reminder was sent out after 2 weeks. The survey was closed after 1 month.</p>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>Descriptive statistics were used for analysis of quantitative data. A general inductive approach was used for analysis of qualitative responses. Responses to free-text questions were reviewed independently by 2 researchers (WZ and BD) who came together to reach a consensus on key themes related to current alerts and redesign recommendations.</p>
        <p>Ethics approval was obtained from the hospital’s human research ethics committee (reference number 5201833414318).</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Survey Respondents and Response Rate</title>
        <p>In total, 36 doctors and 60 nurses responded to the survey, representing a response rate of 3.37% (36/1066) and 14.5% (60/411), respectively (see <xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Characteristics of 36 doctors and 60 nurses that responded to the survey. (Not all participants responded to all questions).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="30"/>
            <col width="590"/>
            <col width="350"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Respondents</td>
                <td>Respondents who responded to the question, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Prescribers</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Roles</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Accredited practitioner—anesthetics</td>
                <td>23 (64)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Accredited practitioner—medical</td>
                <td>4 (11)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Accredited practitioner—surgical</td>
                <td>6 (17)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Registrar</td>
                <td>1 (3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Intern</td>
                <td>1 (3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Days per week working at hospital</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Less than 2</td>
                <td>23 (64)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>2-3</td>
                <td>7 (19)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>4-5</td>
                <td>6 (17)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Setting of EMR<sup>a</sup> use</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Inpatient</td>
                <td>36 (100)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Outpatient</td>
                <td>2 (5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Frequency with which they prescribe in EMR</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Multiple times a day</td>
                <td>27 (75)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Once in the day</td>
                <td>2 (6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Only on some days</td>
                <td>2 (6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Rarely</td>
                <td>4 (11)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Never</td>
                <td>1 (3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Experience using other EMR systems</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Yes</td>
                <td>18 (55)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>No</td>
                <td>15 (45)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Nurses</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Roles</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Registered nurse</td>
                <td>57 (95)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Endorsed enrolled nurse</td>
                <td>3 (5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Days per week working at hospital</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>1-2</td>
                <td>5 (8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>3-4</td>
                <td>23 (38)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>5-6</td>
                <td>32 (53)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="3">
                  <bold>Experience using other EMR systems</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Yes</td>
                <td>24 (41)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>No</td>
                <td>35 (59)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>EMR: electronic medical record.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Some respondents indicated that they were pleased the evaluation was being done:</p>
        <disp-quote>
          <p>Thank you for doing something to fix this. Please involve clinicians.</p>
          <attrib>#02</attrib>
        </disp-quote>
        <p>However, on the whole, most doctors appeared highly dissatisfied with the EMR in general and made sarcastic or sweeping comments about the system in the free-text boxes of the survey. For example, a doctor said:</p>
        <disp-quote>
          <p>The whole system is user unfriendly, please do not give it another band-aid.</p>
          <attrib>#21</attrib>
        </disp-quote>
      </sec>
      <sec>
        <title>Findings Related to the Volume of Alerts Being Triggered in the Electronic Medical Record for Doctors</title>
        <p>As shown in <xref ref-type="table" rid="table2">Table 2</xref>, approximately 90% (30/33) of doctors who responded held the view that too many alerts were triggered in the EMR, and only 9% (3/33) doctors indicated that the number of alerts was <italic>right</italic>.</p>
        <p>When asked to indicate how frequently they read the alerts, responses were mixed, as shown in <xref ref-type="table" rid="table3">Table 3</xref>.</p>
        <p>The free-text responses received in response to the question “I only read the alerts in the EMR when...” reflected this variability. Examples from doctors included:</p>
        <disp-quote>
          <p>Severe alert fatigue—I now disregard all XX (EMR) alerts and check my own prescribing as I would have done when medication charts were on paper.</p>
          <attrib>#16</attrib>
        </disp-quote>
        <disp-quote>
          <p>I scan them very quickly, but don’t read them fully. It’s almost impossible to prescribe in XX (the EMR) without creating alerts—so they don’t really “alert” me.</p>
          <attrib>#13</attrib>
        </disp-quote>
        <disp-quote>
          <p>I always read them.</p>
          <attrib>#11</attrib>
        </disp-quote>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Doctors’ views on the current alert burden in the electronic medical record (N=33 responses).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="500"/>
            <col width="500"/>
            <thead>
              <tr valign="top">
                <td>Response option</td>
                <td>Frequency of doctors who responded to the question, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Far too many alerts, most need to be removed</td>
                <td>19 (58)</td>
              </tr>
              <tr valign="top">
                <td>Too many alerts, some need to be removed</td>
                <td>11 (33)</td>
              </tr>
              <tr valign="top">
                <td>About the right number of alerts</td>
                <td>3 (9)</td>
              </tr>
              <tr valign="top">
                <td>Too few alerts, some need to be added</td>
                <td>0 (0)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Frequency with which doctors reported that they read alerts in the electronic medical record.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="500"/>
            <col width="500"/>
            <thead>
              <tr valign="top">
                <td>Response option</td>
                <td>Frequency of doctors who responded to the question, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Never</td>
                <td>4 (12)</td>
              </tr>
              <tr valign="top">
                <td>Rarely</td>
                <td>6 (18)</td>
              </tr>
              <tr valign="top">
                <td>Sometimes</td>
                <td>10 (30)</td>
              </tr>
              <tr valign="top">
                <td>Often</td>
                <td>4 (12)</td>
              </tr>
              <tr valign="top">
                <td>Always</td>
                <td>9 (27)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Findings Related to the Usefulness of Each Alert Type for Doctors</title>
        <p>When asked to rate each alert type on a Likert scale of usefulness, allergy and intolerances alerts were rated most positively. As shown in <xref ref-type="table" rid="table4">Table 4</xref>, these alerts were viewed to be <italic>sometimes useful</italic> by approximately half of the doctors in the survey. The other alert types were rated as <italic>never</italic> or <italic>rarely useful</italic> by the majority of doctors. When asked to indicate which alert type was the most useful, 60% (20/33) doctors selected allergy and intolerances alerts, and 24% (8/33) indicated that none of the alerts were useful.</p>
        <p>Interestingly, when asked which of the alert types they would remove from the EMR (with more than one option possible), approximately half of the doctors (17/36, 47%) indicated that they would remove therapeutic duplication alerts, pregnancy alerts, and drug interaction alerts. In addition, 19% (7/36) also indicated that they would remove allergy and intolerance alerts.</p>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Doctors’ views on alert usefulness.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="150"/>
            <col width="240"/>
            <col width="230"/>
            <col width="140"/>
            <col width="240"/>
            <thead>
              <tr valign="top">
                <td>Response option</td>
                <td colspan="4">Frequency, n</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Allergy and intolerances alert</td>
                <td>Therapeutic duplication alert</td>
                <td>Pregnancy alert</td>
                <td>Generic drug interaction alert</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Never useful</td>
                <td>8</td>
                <td>11</td>
                <td>12</td>
                <td>12</td>
              </tr>
              <tr valign="top">
                <td>Rarely useful</td>
                <td>5</td>
                <td>13</td>
                <td>15</td>
                <td>12</td>
              </tr>
              <tr valign="top">
                <td>Sometimes useful</td>
                <td>17</td>
                <td>7</td>
                <td>6</td>
                <td>10</td>
              </tr>
              <tr valign="top">
                <td>Often useful</td>
                <td>6</td>
                <td>5</td>
                <td>3</td>
                <td>2</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Doctors’ and Nurses’ Preferences for Changes to the Alerting System</title>
        <p>Nurses did not receive medication administration alerts in the EMR; however, 97% (58/60) of the nurse respondents indicated that they should. When asked what types of alerts nurses should receive, most nurses selected all the alert types available to the doctors. Other suggested alert types included alerts for stat orders, overdue medications, blood thinning medications, dose alerts, and alerts warning when a nursing intervention was required (eg, digoxin).</p>
        <p>When asked to indicate what alert severity level or levels should be included in the EMR, nurses and doctors expressed very different views. As shown in <xref ref-type="table" rid="table5">Table 5</xref>, nurses were more open to receiving alerts of all severities.</p>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Doctors’ and nurses’ preferences for alert severity.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="230"/>
            <col width="390"/>
            <col width="380"/>
            <thead>
              <tr valign="top">
                <td>Response option</td>
                <td>Frequency of doctors who responded to the question, n (%)</td>
                <td>Frequency of nurses who responded to the question, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Only severe alerts</td>
                <td>12 (36)</td>
                <td>1 (2)</td>
              </tr>
              <tr valign="top">
                <td>Severe and moderate alerts</td>
                <td>20 (61)</td>
                <td>19 (33)</td>
              </tr>
              <tr valign="top">
                <td>All alerts, including minor alerts</td>
                <td>1 (3)</td>
                <td>38 (66)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p> In response to a request for suggested changes to the alerts in the EMR, the most frequent response from doctors was to reduce alert numbers primarily by making the alerts more relevant. For example, doctors said:</p>
        <disp-quote>
          <p>Too many for too many trivial issues.</p>
          <attrib>#41</attrib>
        </disp-quote>
        <disp-quote>
          <p>Real ones need to be more prominent. All the silly ones need to go.</p>
          <attrib>#02</attrib>
        </disp-quote>
        <disp-quote>
          <p>Many of the alerts are theoretical and are ignored in our everyday practice.</p>
          <attrib>#17</attrib>
        </disp-quote>
        <disp-quote>
          <p>Hard to tell which ones are useful and which ones are not...You are more likely to miss important alerts if you are bombarded with too many insignificant alerts.</p>
          <attrib>#24</attrib>
        </disp-quote>
        <p>Other common suggestions from doctor respondents were related to alert design. Current alerts were described as <italic>not user friendly,</italic> and doctors suggested using color coding to highlight the type or severity of alerts and suggested making alert content more concise:</p>
        <disp-quote>
          <p>Perhaps they could be color coded e.g. the severe ones and e.g. multiple opioid prescribing alert be large and red, moderate orange, minor orange and smaller. The blue color is very neutral.</p>
          <attrib>#20</attrib>
        </disp-quote>
        <p>This was consistent with what nurses viewed to be characteristic of a well-designed alert:</p>
        <disp-quote>
          <p>Brief but adequate information, highlighted (font and color).</p>
          <attrib>#11</attrib>
        </disp-quote>
        <disp-quote>
          <p>As simple as it can be.</p>
          <attrib>#28</attrib>
        </disp-quote>
        <p>Some nurses also described what they believed to be the ideal content to be included in an alert screen. For example:</p>
        <disp-quote>
          <p>Alert specifies the issue clearly. Specifies the action required. The alert can be dismissed easily where appropriate. Contains the problem: e.g. duplicate drug.</p>
          <attrib>#5</attrib>
        </disp-quote>
        <disp-quote>
          <p>An alert that states: “ALERT,” not wordy but precise description of alert. An alert that is easy to understand.</p>
          <attrib>#41</attrib>
        </disp-quote>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of Key Findings From the Survey</title>
        <p>With respect to the current alerts in the EMR, prescribers reported that too many alerts were being triggered and that most alerts were not clinically relevant. As a consequence, alerts were not always being read, and many doctors reported experiencing alert fatigue. These findings confirm what had been suspected by the organization and are in line with many studies exploring user views of alerts [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Allergy alerts were perceived to be the most useful among the alert types, a finding also consistent with previous research [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. With respect to recommended changes to the alerts, prescribers suggested that most alerts be removed and that alerts be more specific and less sensitive. Prescribers also recommended that alert interfaces be redesigned so that alert text is more concise, and color coding is used to signal alert type and severity of alerts. These suggestions were consistent with nurses’ preferences for alert content and display and reflect good <italic>human factors</italic> design [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>].</p>
      </sec>
      <sec>
        <title>Lessons Learned From Our Attempt to Engage Users</title>
        <p>Our survey highlighted some important lessons for the site and more broadly for other hospitals with plans to implement medication-related alerts in their EMR. Seeking user feedback on usefulness, volume, and design of alerts, even with this small-scale survey, proved to be extremely valuable; however, we suggest consulting users early and regularly. Our low response rate could in part reflect staff not checking emails or not having enough time to action emails. However, based on the free-text responses we received, it more likely reflected a workforce feeling disengaged and dissatisfied with the alerting system and associated implementation process. Early consultation would have allowed user views to be captured before negative mindsets were established and may have minimized any perception that the provision of feedback was futile. Continuous consultation with users is needed to ensure alert volume remains manageable and alert content remains relevant.</p>
        <p>We recommend that organizations involve end users in the decision-making processes surrounding alert selection before EMR rollout as well as in implementation and ongoing evaluation. Involving users in EMR implementation more broadly has been shown to facilitate a sense of ownership of the system among users and to result in an EMR that aligns well with the needs of end users rather than the needs of the information technology department or leadership staff [<xref ref-type="bibr" rid="ref15">15</xref>]. Consistent with previous research [<xref ref-type="bibr" rid="ref16">16</xref>], our findings confirm that user engagement is particularly important for medication-related alerts. Engaging end users in the selection and implementation processes for alerts will also increase user awareness of the challenges associated with alert optimization (eg, vendor restrictions and complexity associated with identifying a set of <italic>high priority</italic> alerts).</p>
        <p>One of the interesting findings that emerged from our survey was that in contrast to doctors, nurses showed a strong preference for enabling all alert types of all severities for nurses in the EMR. This could reflect their limited experience with alerts, as a common misconception held by clinicians who do not experience alerts themselves is <italic>the more alerts, the better</italic>. To allow end users to make informed decisions about alert selection, we recommend providing current users and prospective users with data on alert rates (eg, 50% of your orders/administrations/reviews will trigger an alert) to facilitate an understanding of the potential impact of alerts on their work and educating staff on the well-known risks associated with alert overload.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Our attempt to engage users in the redesign of medication-related alerts in an EMR was largely unsuccessful, with only a small number of doctors and nurses partaking in our survey. This likely reflects the delay between implementation and seeking feedback from end users. However, the feedback we received from survey respondents on usefulness, volume, and design of alerts proved to be extremely valuable. We recommend hospitals adopt a <italic>less-is-more</italic> approach and work closely with all end user groups before EMR implementation to determine the types, design, and content of alerts and implement these in their systems.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Recruitment emails.</p>
        <media xlink:href="jmir_v22i3e14855_app1.docx" xlink:title="DOCX File , 14 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Doctor survey.</p>
        <media xlink:href="jmir_v22i3e14855_app2.docx" xlink:title="DOCX File , 23 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Nurse survey.</p>
        <media xlink:href="jmir_v22i3e14855_app3.docx" xlink:title="DOCX File , 21 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Page</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Baysari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of the effectiveness of interruptive medication prescribing alerts in hospital CPOE systems to change prescriber behavior and improve patient safety</article-title>
          <source>Int J Med Inform</source>
          <year>2017</year>
          <month>09</month>
          <volume>105</volume>
          <fpage>22</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2017.05.011</pub-id>
          <pub-id pub-id-type="medline">28750908</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(17)30160-0</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>Peterson</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Kuperman</surname>
              <given-names>GJ</given-names>
            </name>
            <name name-style="western">
              <surname>Shek</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Avorn</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Guided prescription of psychotropic medications for geriatric inpatients</article-title>
          <source>Arch Intern Med</source>
          <year>2005</year>
          <month>04</month>
          <day>11</day>
          <volume>165</volume>
          <issue>7</issue>
          <fpage>802</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1001/archinte.165.7.802</pub-id>
          <pub-id pub-id-type="medline">15824302</pub-id>
          <pub-id pub-id-type="pii">165/7/802</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>Payne</surname>
              <given-names>TH</given-names>
            </name>
          </person-group>
          <article-title>EHR-related alert fatigue: minimal progress to date, but much more can be done</article-title>
          <source>BMJ Qual Saf</source>
          <year>2019</year>
          <month>01</month>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>2</lpage>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2017-007737</pub-id>
          <pub-id pub-id-type="medline">30297378</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2017-007737</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>Baysari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Richardson</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>RO</given-names>
            </name>
          </person-group>
          <article-title>The influence of computerized decision support on prescribing during ward-rounds: are the decision-makers targeted?</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2011</year>
          <volume>18</volume>
          <issue>6</issue>
          <fpage>754</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21676939"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2011-000135</pub-id>
          <pub-id pub-id-type="medline">21676939</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2011-000135</pub-id>
          <pub-id pub-id-type="pmcid">PMC3197993</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>van der Sijs</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Aarts</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Vulto</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Overriding of drug safety alerts in computerized physician order entry</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2006</year>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>138</fpage>
          <lpage>47</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/16357358"/>
          </comment>
          <pub-id pub-id-type="doi">10.1197/jamia.M1809</pub-id>
          <pub-id pub-id-type="medline">16357358</pub-id>
          <pub-id pub-id-type="pii">M1809</pub-id>
          <pub-id pub-id-type="pmcid">PMC1447540</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>Bryant</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fletcher</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Drug interaction alert override rates in the Meaningful Use era: no evidence of progress</article-title>
          <source>Appl Clin Inform</source>
          <year>2014</year>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>802</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25298818"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2013-12-RA-0103</pub-id>
          <pub-id pub-id-type="medline">25298818</pub-id>
          <pub-id pub-id-type="pmcid">PMC4187095</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>Baysari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Tariq</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>RO</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
          </person-group>
          <article-title>Alert override as a habitual behavior - a new perspective on a persistent problem</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>03</month>
          <day>1</day>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>409</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw072</pub-id>
          <pub-id pub-id-type="medline">27274015</pub-id>
          <pub-id pub-id-type="pii">ocw072</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>Rayo</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Moffatt-Bruce</surname>
              <given-names>SD</given-names>
            </name>
          </person-group>
          <article-title>Alarm system management: evidence-based guidance encouraging direct measurement of informativeness to improve alarm response</article-title>
          <source>BMJ Qual Saf</source>
          <year>2015</year>
          <month>04</month>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>282</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2014-003373</pub-id>
          <pub-id pub-id-type="medline">25734193</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2014-003373</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>Page</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Baysari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
          </person-group>
          <article-title>Selection and use of decision support alerts in electronic medication management systems in Australian hospitals: a survey of implementers</article-title>
          <source>J Pharm Pract Res</source>
          <year>2019</year>
          <volume>49</volume>
          <issue>2</issue>
          <fpage>142</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1002/jppr.1479</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>Liberati</surname>
              <given-names>EG</given-names>
            </name>
            <name name-style="western">
              <surname>Ruggiero</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Galuppo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gorli</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>González-Lorenzo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Maraldi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ruggieri</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Friz</surname>
              <given-names>HP</given-names>
            </name>
            <name name-style="western">
              <surname>Scaratti</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kwag</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Vespignani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Moja</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>What hinders the uptake of computerized decision support systems in hospitals? A qualitative study and framework for implementation</article-title>
          <source>Implement Sci</source>
          <year>2017</year>
          <month>09</month>
          <day>15</day>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>113</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://implementationscience.biomedcentral.com/articles/10.1186/s13012-017-0644-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13012-017-0644-2</pub-id>
          <pub-id pub-id-type="medline">28915822</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13012-017-0644-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC5602839</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>Fournier</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Stavri</surname>
              <given-names>PZ</given-names>
            </name>
            <name name-style="western">
              <surname>Dykstra</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Principles for a successful computerized physician order entry implementation</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2003</year>
          <volume>2003</volume>
          <fpage>36</fpage>
          <lpage>40</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/14728129"/>
          </comment>
          <pub-id pub-id-type="medline">14728129</pub-id>
          <pub-id pub-id-type="pii">D030002698</pub-id>
          <pub-id pub-id-type="pmcid">PMC1480169</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>Baysari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Egan</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>RO</given-names>
            </name>
          </person-group>
          <article-title>Identification of strategies to reduce computerized alerts in an electronic prescribing system using a Delphi approach</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2013</year>
          <volume>192</volume>
          <fpage>8</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="medline">23920505</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>Pelayo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marcilly</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bernonville</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Leroy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Beuscart-Zephir</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Human factors based recommendations for the design of medication related clinical decision support systems (CDSS)</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2011</year>
          <volume>169</volume>
          <fpage>412</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="medline">21893783</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>Phansalkar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Edworthy</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hellier</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Seger</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Schedlbauer</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Avery</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>A review of human factors principles for the design and implementation of medication safety alerts in clinical information systems</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2010</year>
          <volume>17</volume>
          <issue>5</issue>
          <fpage>493</fpage>
          <lpage>501</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20819851"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.2010.005264</pub-id>
          <pub-id pub-id-type="medline">20819851</pub-id>
          <pub-id pub-id-type="pii">17/5/493</pub-id>
          <pub-id pub-id-type="pmcid">PMC2995688</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>Simon</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Keohane</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Amato</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Coffey</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cadet</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Zimlichman</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Lessons learned from implementation of computerized provider order entry in 5 community hospitals: a qualitative study</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2013</year>
          <month>06</month>
          <day>24</day>
          <volume>13</volume>
          <fpage>67</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-13-67"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-13-67</pub-id>
          <pub-id pub-id-type="medline">23800211</pub-id>
          <pub-id pub-id-type="pii">1472-6947-13-67</pub-id>
          <pub-id pub-id-type="pmcid">PMC3695777</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>Baysari</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Richardson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>RO</given-names>
            </name>
          </person-group>
          <article-title>Optimising computerised alerts within electronic medication management systems: a synthesis of four years of research</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2014</year>
          <volume>204</volume>
          <fpage>1</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="medline">25087519</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
