<?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">ResProt</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Res Protoc</journal-id>
      <journal-title>JMIR Research Protocols</journal-title>
      <issn pub-type="epub">1929-0748</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">v12i1e47717</article-id>
      <article-id pub-id-type="pmid">37651166</article-id>
      <article-id pub-id-type="doi">10.2196/47717</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Protocol</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Protocol</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Graphical User Interface Development for a Hospital-Based Predictive Risk Tool: Protocol for a Co-Design Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Cao</surname>
            <given-names>Caroline</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Zhuang</surname>
            <given-names>Yan</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Wilson</surname>
            <given-names>Ian</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>Marlow</surname>
            <given-names>Nicholas</given-names>
          </name>
          <degrees>MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>University of South Australia</institution>
            <addr-line>GPO Box 2471</addr-line>
            <addr-line>Adelaide, 5001</addr-line>
            <country>Australia</country>
            <phone>61 001183022129</phone>
            <email>Nicholas.marlow@mymail.unisa.edu.au</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4210-0520</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Eckert</surname>
            <given-names>Marion</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7232-6208</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Sharplin</surname>
            <given-names>Greg</given-names>
          </name>
          <degrees>MPsych</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6294-1146</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Gwilt</surname>
            <given-names>Ian</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3759-3423</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Carson-Chahhoud</surname>
            <given-names>Kristin</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9966-9289</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>University of South Australia</institution>
        <addr-line>Adelaide</addr-line>
        <country>Australia</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Nicholas Marlow <email>Nicholas.marlow@mymail.unisa.edu.au</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>31</day>
        <month>8</month>
        <year>2023</year>
      </pub-date>
      <volume>12</volume>
      <elocation-id>e47717</elocation-id>
      <history>
        <date date-type="received">
          <day>29</day>
          <month>3</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>8</day>
          <month>6</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>6</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>27</day>
          <month>6</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Nicholas Marlow, Marion Eckert, Greg Sharplin, Ian Gwilt, Kristin Carson-Chahhoud. Originally published in JMIR Research Protocols (https://www.researchprotocols.org), 31.08.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Research Protocols, is properly cited. The complete bibliographic information, a link to the original publication on https://www.researchprotocols.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.researchprotocols.org/2023/1/e47717" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>This co-design research method details the iterative process developed to identify health professional recommendations for the graphical user interface (GUI) of an artificial intelligence (AI)–enabled risk prediction tool. Driving the decision to include a co-design process is the belief that choices regarding the aesthetic and functionality of an intervention are best made by its intended users and that engaging these users in its design will promote the tool’s adoption and use.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The aim of this research is to identify health professional design and uptake recommendations for the GUI of an AI-enabled predictive risk tool.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We will hold 3 research phases, each consisting of 2 workshops with health professionals, between mid-2023 and mid-2024. A total of 6 health professionals will be sought per workshop, resulting in a total enrollment of 36 health professionals at the conclusion of the research. A total of 7 workshop activities have been scheduled across the 3 workshops; these include context of use, notifiers, format, AI survey–Likert, prototype, AI survey–written, and testing. The first 6 of these activities will be repeated in each workshop to enable the iterative development and refinement of GUI. The last activity (testing) will be performed in the final workshop to examine health professionals’ thoughts on the final GUI iteration. Qualitative and quantitative results data will be produced from tasks in each research activity. Qualitative data will be examined through inductive thematic analysis or deductive thematic analysis in accordance with the Nonadoption, Abandonment, and Challenges to the Scale-up, Spread, and Sustainability (NASSS) framework; visual data will be examined in accordance with “framework of interactivity;” and quantitative data will be examined using descriptive statistics.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Project registration with the Australia and New Zealand Clinical Trial Registry has been requested (#384098). Finalized design recommendations are expected in early to mid-2024, with a results manuscript to be submitted in mid-2024. This research method has human research ethics approval from the South Australian Department of Health and Wellbeing (#2022/HRE00131) as well as from the Human Research Ethics Committee of the University of South Australia (application ID#204143).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Understanding whether an intervention is needed in a particular situation is just the start; designing an intervention so that it is used within that situation is paramount. This co-design process engages end users to create a GUI that includes the aesthetic and functional details they need in a manner that aligns with their existing work practices. Indeed, interventions that fail to do this may be disliked, and at worst, they may be dangerous.</p>
        </sec>
        <sec sec-type="registered-report">
          <title>International Registered Report Identifier (IRRID)</title>
          <p>PRR1-10.2196/47717</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>co-design</kwd>
        <kwd>health information technology</kwd>
        <kwd>health professional</kwd>
        <kwd>user-centered design</kwd>
        <kwd>user interface</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Dashboards summarize information in a meaningful manner to ensure users can make informed decisions in accordance with organizational objectives [<xref ref-type="bibr" rid="ref1">1</xref>]. They can take many forms, such as electronic medical records (EMRs) or electronic health records (EHRs), as well as computerized provider order entry (CPOE), to name but a few. Each is advocated as a tool that increases productivity and efficiency, improves patient health care outcomes [<xref ref-type="bibr" rid="ref2">2</xref>], and assists health professionals to avoid errors and drive down health care costs [<xref ref-type="bibr" rid="ref3">3</xref>]. Yet despite their advocated benefits, health professionals encounter barriers to their use and sustainability [<xref ref-type="bibr" rid="ref4">4</xref>].</p>
      <p>In many instances, barriers result from dashboards’ imposition on the way health professionals deliver care or the way in which they are required to interact with the platform in their professional practice. A thematic analysis of physician interviews identified that using the platform not only disrupted their patient consultation but also resulted in an additional time burden due to the need to record diagnostic codes [<xref ref-type="bibr" rid="ref5">5</xref>]. Confidence in the quality of information within these records is of concern for health professionals, with “prescriber” views reporting that patient files included “untrustworthy” information and produced “irrelevant” alerts [<xref ref-type="bibr" rid="ref6">6</xref>]. Distrust as to the true intent of health information technology (HIT) has also been identified, with some health professionals reporting feeling that their CPOE systems are a mechanism for oversight and performance monitoring [<xref ref-type="bibr" rid="ref7">7</xref>]. How health professionals interact with dashboards can also create issues, with research identifying pharmacist views that CPOE use can be time consuming [<xref ref-type="bibr" rid="ref8">8</xref>] and a struggle due to functional and navigational issues [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      <p>Workplace practice and navigational issues, among others, can accumulate and result in a negative experience for health professionals. Of the interviewed physicians, 64.2% reported “agreeing” or “strongly agreeing” that EMRs added to the “frustration of their day.” Furthermore, these physicians also had significantly higher odds of burnout [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      <p>The introduction of artificial intelligence (AI)–enabled technologies in health care has been reported to raise several concerns for health professionals, specifically ethicality, data management, and its influence on health care delivery [<xref ref-type="bibr" rid="ref11">11</xref>]. Alternatively, research on AI adoption reports that as health professionals’ exposure to AI increases, their positive feelings toward it also increase, as do their satisfaction and use intentions [<xref ref-type="bibr" rid="ref12">12</xref>]. It is critical, therefore, that health professionals’ engagement with AI occurs in a positive manner to encourage adoption and repeated use.</p>
      <p>Positive interaction with AI can be achieved through end-user engagement in graphical user interface (GUI) design. Indeed, the GUI is the most prominent, and perhaps the only, element of AI-enabled software with which the user will interact. Its appropriate design is therefore paramount. Co-design as a participatory process enables meaningful engagement with relevant users [<xref ref-type="bibr" rid="ref13">13</xref>]. It is a process where the contributions of different users are synthesized [<xref ref-type="bibr" rid="ref14">14</xref>], and it collaboratively integrates design thinking, stakeholder knowledge, scientific evidence, and the bottom-up approach of participatory action research to produce solutions to identify and address what is important within the local context [<xref ref-type="bibr" rid="ref4">4</xref>]. Co-design will be used by this research to develop the notifiers (eg, graphs, dials, and icons) and layouts required because it places the user at the center of the research and development process with the goal of creating the version of the GUI that best represents their design needs.</p>
      <p>The research method detailed herein will be performed as part of a PhD project and forms part of the larger Predictive Harm Response Management (PreHaRM) Algorithmic Tool to Reduce Adverse Events in Health Care Settings project. The purpose of the larger project is to develop and test an AI-enabled predictive risk algorithm and interface for use within the hospital setting (the PreHaRM tool). The PreHaRM tool will focus on the prediction of 3 adverse events: patient falls, medication errors, and occupational violence (patient or caregiver toward staff). The larger project, including this co-design project, is supported by Digital Health Cooperative Research Centre (DHCRC) Limited. DHCRC Limited is funded under the Australian Commonwealth Government’s Cooperative Research Centers Program (Project #DHCRC-0156). The co-design workshops will develop health professionals informed recommendations for the visualization of the DHCRC PreHaRM tool.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Objective</title>
        <p>The aim of this research is to identify health professional design and uptake recommendations for the GUI of an AI-enabled predictive risk tool. The primary and secondary objectives are described in the following sections.</p>
        <sec>
          <title>Primary Objective</title>
          <p>Objective 1: Identify health professionals design preferences for GUI aesthetics and function.</p>
        </sec>
        <sec>
          <title>Secondary Objectives</title>
          <p>Objective 2: Identify health professional usability levels for professional practice and PreHaRM GUIs.</p>
          <p>Objective 3: Identify health professional acceptability levels for professional practice and PreHaRM GUIs.</p>
          <p>Objective 4: Identify health professionals’ perceptions of AI in health care in relation to its implementation and adoption.</p>
        </sec>
        <sec>
          <title>Outcome Measures</title>
          <p>Outcome measures developed in accordance with objective 1 are as follows:</p>
          <list list-type="bullet">
            <list-item>
              <p>Participant for GUI aesthetic and function preferences tabulated and narratively synthesized according to the framework of interactivity.</p>
            </list-item>
            <list-item>
              <p>Participant visual design preferences tabulated and narratively synthesized according to the elements and principles of visual design.</p>
            </list-item>
          </list>
          <p>Outcome measures developed in accordance with objective 2 are as follows:</p>
          <list list-type="bullet">
            <list-item>
              <p>Participant System Usability Scale (SUS) scores for professional and PreHaRM GUIs.</p>
            </list-item>
          </list>
          <p>Outcome measures developed in accordance with objective 3 are as follows:</p>
          <list list-type="bullet">
            <list-item>
              <p>Barriers and enablers for professional and PreHaRM GUIs tabulated and narratively synthesized according to the theoretical framework of acceptability.</p>
            </list-item>
          </list>
          <p>Outcome measures developed in accordance with objective 4 are as follows:</p>
          <list list-type="bullet">
            <list-item>
              <p>Participant “AI potential impact” scores measured by the 10-question Shinners Artificial Intelligence Perception tool.</p>
            </list-item>
            <list-item>
              <p>Participant “AI readiness” scores measured using the 10-question Shinners Artificial Intelligence Perception tool.</p>
            </list-item>
            <list-item>
              <p>Barriers and enablers to AI adoption in health care tabulated and narratively synthesized according to the Nonadoption, Abandonment, and Challenges to the Scale-up, Spread, and Sustainability (NASSS) framework.</p>
            </list-item>
          </list>
        </sec>
      </sec>
      <sec>
        <title>Study Design</title>
        <p>A total of three 2-month research phases have been scheduled from mid-2023 to mid-2024, with 2 co-design workshops scheduled per phase, one in Adelaide (University of South Australia city west campus), the other in Tonsley (Tonsley Innovation District) for Central Adelaide and Southern Adelaide Local Health Network staff, respectively. If required, participants may attend using teleconferencing software (eg, Zoom) and collaborative software (eg, Miro). Each workshop will be led by an experienced facilitator and run for approximately 2 and a half hours. A total of 2 support staff will also be in attendance: one will observe and note proceedings while a second will provide operational support to the facilitator (eg, information technology troubleshooting, handing out and collecting activity sheets).</p>
        <p>Members of the PreHaRM clinical implementation team (CIT) will be asked to promote each workshop by circulating an invitation to colleagues within their peer network. Individuals who confirm their interest in the workshop will be emailed workshop details (ie, session date, time, and location). A total of 6 participants will be enrolled in each workshop, resulting in a total of 12 participants per research phase, for a maximum total of 36 participants (<xref ref-type="table" rid="table1">Table 1</xref>). The total number of individuals may be less than 36, as participants will be allowed to attend more than one workshop should they choose to; however, this repeat attendance is not a requirement and will be made at their discretion.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Research phase and co-design workshop schedule.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="470"/>
            <col width="0"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="bottom">
                <td colspan="3">Phase and location</td>
                <td>Participants, n</td>
                <td>Date<sup>a</sup></td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Research phase 1</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>CALHN<sup>b</sup> workshop 1</td>
                <td colspan="2">6</td>
                <td>September</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SALHN<sup>c</sup> workshop 1</td>
                <td colspan="2">6</td>
                <td>September</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Research phase 2</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>CALHN workshop 2</td>
                <td colspan="2">6</td>
                <td>November or December</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SALHN workshop 2</td>
                <td colspan="2">6</td>
                <td>November or December</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Research phase 3</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>CALHN workshop 3</td>
                <td colspan="2">6</td>
                <td>January or February</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SALHN workshop 3</td>
                <td colspan="2">6</td>
                <td>January or February</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Proposed 2023 time period.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>CALHN: Central Adelaide Local Health Network.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>SALHN: Southern Adelaide Local Health Network.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Inclusion and Exclusion Criteria</title>
        <p>Nurses have been identified as the target user of the GUI, and as such, the inclusion and exclusion criteria below reflect the need to attract a diverse range of participants from this professional group; for example, nurses of all levels (including enrolled, registered, and nursing unit managers) will be sought so the diversity of their experience can benefit the design. Criteria for enrollment are listed in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> below.</p>
        <boxed-text id="box1" position="float">
          <title>Inclusion and exclusion criteria.</title>
          <p>
            <bold>Inclusion criteria</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Enrolled nurses</p>
            </list-item>
            <list-item>
              <p>Registered nurses</p>
            </list-item>
            <list-item>
              <p>Nursing unit managers</p>
            </list-item>
            <list-item>
              <p>Nurses in noncare roles</p>
            </list-item>
            <list-item>
              <p>Use health information technology in professional role</p>
            </list-item>
            <list-item>
              <p>Able to provide informed consent</p>
            </list-item>
          </list>
          <p>
            <bold>Exclusion criteria</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Not employed by SA Health</p>
            </list-item>
            <list-item>
              <p>Unable to provide informed consent</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Iterative Workshops</title>
        <p>An iterative co-design process will run across each of the workshops. Each workshop includes predesign and generative activities, noting that these activities will culminate in the testing activity held in the third workshop. <xref rid="figure1" ref-type="fig">Figure 1</xref> illustrates the focus and relationship of each workshop, as well as the overall iterative co-design process.</p>
        <p>A description of each workshop activity is provided in <xref ref-type="table" rid="table2">Table 2</xref> below.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Iterative co-design process. AI: artificial intelligence; GUI: graphical user interface.</p>
          </caption>
          <graphic xlink:href="resprot_v12i1e47717_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Workshop activity matrix.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="500"/>
            <col width="300"/>
            <thead>
              <tr valign="top">
                <td>Activity</td>
                <td>Description</td>
                <td>Tools</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Context of use</td>
                <td>Participants will be asked about their use of GUIs<sup>a</sup> at work.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Web-based survey</p>
                    </list-item>
                    <list-item>
                      <p>Moderator guide</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Notifiers</td>
                <td>Participants will be asked to design notifiers (eg, graphs, dials, or icons) that they would like to see on the PreHaRM<sup>b</sup> GUI.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Generative toolkits</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Format</td>
                <td>Participants will be asked to arrange their chosen visualizations on a mock GUI.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Generative toolkits</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>AI survey–Likert</td>
                <td>Likert scale questions will investigate participant feelings toward AI<sup>c</sup> enabled software in health care.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Web-based survey</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Prototype</td>
                <td>Participants will be asked to provide feedback in relation to the potential usability of the PreHaRM prototype 1.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Web-based survey</p>
                    </list-item>
                    <list-item>
                      <p>Moderator guide</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>AI survey–written</td>
                <td>Participants will be given results from previously completed surveys and asked to contextualize the results from their point of view.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Web-based survey</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Testing</td>
                <td>Participants will be asked provide feedback on their use of prototype 2 in relation to a mock workplace scenario.</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Scenario testing</p>
                    </list-item>
                    <list-item>
                      <p>Web-based survey</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>GUI: graphical user interface.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>PreHaRM: Predictive Harm Response Management.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>AI: artificial intelligence.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Workshop Tools</title>
        <p>Workshop tools and the method for analyzing their respective results data are described in the follows sections.</p>
        <sec>
          <title>Surveys</title>
          <p>A background survey will be used to obtain basic participant demographic information (workshops 1-3). The SUS will be used to examine participants views on the usability and acceptability of GUIs currently used in their professional practice (“context” activity, workshops 1-3) [<xref ref-type="bibr" rid="ref15">15</xref>]; a sample survey has been included for reference (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). The SUS activity survey will also be used to understand participant views on the PreHaRM prototypes 1 and 2 (“prototype” activity, workshop 2, and “testing” activity, workshop 3). The Shinners Artificial Intelligence Perception (SHAIP) framework will be used to identify health professionals’ perceptions of AI in health [<xref ref-type="bibr" rid="ref11">11</xref>] (AI survey–Likert, workshops 1-3). The third survey will present results from the AI survey–Likert alongside written questions asking participants to interpret and report what these results mean (AI survey–written, workshops 2-3). All surveys will be delivered using a web-based platform (eg, Microsoft Forms). All data will be downloaded from the web-based survey platform for analysis. Quantitative data collected from the background, SUS, and SHAIP surveys will be examined using descriptive statistics calculated in R (version 4.2.0; R Core Team). Qualitative data collected from the AI Survey–written will be coded against the 22 themes within the NASSS framework in NVivo (version 14; QSR International) [<xref ref-type="bibr" rid="ref16">16</xref>]. Coding will be performed by NM with checking by a second researcher; any disagreements will be reviewed by KCC.</p>
        </sec>
        <sec>
          <title>Moderator Guide</title>
          <p>Health professionals’ acceptance of professional practice GUIs as well as the PreHaRM prototype GUI will be examined through questions contained in a semistructured moderator guide. Their responses will be audio recorded and transcribed, and the coding of responses will then be performed against the 8 domains of the theoretical framework of analysis (TFA) [<xref ref-type="bibr" rid="ref17">17</xref>]. Coding will be performed by NM and checked by a second researcher, with any disagreements reviewed by KCC.</p>
        </sec>
        <sec>
          <title>Generative Toolkits</title>
          <p>For notifier development, participants will be given example cut-outs and asked to amend them to represent how they’d prefer it to look. Blank paper, colored markers, and other materials will be provided for participants should they prefer to draw their own notifiers. For layout development, participants will be given GUI screen templates (and blank pieces of paper) onto which they can arrange their chosen notifiers to design their preferred GUI (“notifiers” and “format” activities, workshops 1-3).</p>
          <p>Notifiers and layouts will be produced using generative toolkits. Both artifact types will be assessed to identify their aesthetic and functional characteristics. Aesthetic characteristics will be examined in relation to the visual elements that comprise each artifact (ie, line, shape, color palette, texture, typography, and form) as well as the use of visual design principles (ie, unity, gestalt, space, hierarchy, balance, contrast, scale, dominance, and similarity) [<xref ref-type="bibr" rid="ref18">18</xref>]. Functional (or interactive) characteristics will be examined using the framework of interactivity [<xref ref-type="bibr" rid="ref19">19</xref>]; this will be used to categorize each artifact in regard to its ideational, interpersonal, and textual intent. All artifacts will be examined by NM, with results recorded on an Excel spreadsheet developed a priori. These will be checked by a second researcher, with KCC adjudicating any disagreements. Review of the content and frequency of these results will inform the PreHaRM design recommendations.</p>
        </sec>
        <sec>
          <title>Scenario Testing</title>
          <p>A mock scenario to test PreHaRM prototype 2 will be developed using CIT, the technical advisory group (TAG), and research staff input. Participants in workshop 3 will be offered 1 opportunity to attempt the tasks within the scenario (“testing” activity, workshop 3). All attempts will be video recorded, either through screen capture software or a separate video camera. Participant attempts will be examined using “navigation testing,” where participants’ time taken as well as navigation hits and misses will be recorded. Exploration results will be examined using descriptive statistics calculated in R. Following their completion of the scenario, they will be asked to complete the SUS questionnaire, and the resultant data will be examined as per the process described above.</p>
        </sec>
      </sec>
      <sec>
        <title>Unstructured Interviews</title>
        <p>Following the completion of each workshop, attendees will be offered the opportunity to participate in voluntary, one-on-one, unstructured interviews with NM. The purpose of the interview is to enable participants to provide further information about their workshop feedback or to provide new feedback if they feel uncomfortable raising it in a group context. Interviews will be offered through teleconferences only (Zoom; version 5.12.8; Zoom Video Communications Inc). These interviews will be offered as an opt-in opportunity, and it will be explained that participation in any workshop is not contingent on their participation in the interviews.</p>
        <p>In unstructured interviews, it is unclear what participants may choose to discuss; consequently, inductive thematic analysis will be used to examine participant interview transcripts. This will be performed using NVivo. Participant perspectives will be coded by NM and examined by KCC.</p>
      </sec>
      <sec>
        <title>Data Management</title>
        <p>All workshops and follow-up interviews will be audio recorded using a digital recording device; scenario testing activities will be recorded using video cameras; hardcopy artifacts (ie, visualizations and dashboards) will be collected by PreHaRM researchers; and participant surveys will be collated using web-based software. Audio recordings will be transcribed using voice recognition Rev (Rev.com, Inc); video recordings will be reviewed using Adobe Premiere Pro (version 23.0.0; Adobe Inc); Microsoft Forms will host each survey and automatically collate responses. Once the survey period has ended, collated responses will be downloaded. All electronic data will be stored in password-protected folders at the University of South Australia, Australia. All artifacts will be stored in facilities at the University of South Australia, Australia. All data will be retained for a minimum of five years after project completion in accordance with Australian State and Commonwealth guidelines.</p>
        <p>Peer-reviewed manuscripts, posters, and oral presentations detailing the co-design process and results will be produced; information used in these research outputs will be deidentified. If video recordings are used, then participant likenesses (audio and visual) will be obscured. Data sets generated and analyzed during this research are not publicly available due to dissemination restrictions resulting from the ethics approval process.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>A participant information sheet and consent form will be emailed to all participants before each workshop. Hardcopies will be available at the start of each session, and all individuals must read the information sheet and sign the consent form before participating. This research method has human research ethics approval from the South Australian Department of Health and Wellbeing (#2022/HRE00131) as well as from the Human Research Ethics Committee of the University of South Australia (application ID#204143). No research activity will commence until approvals from both committees have been received. All research data will be deidentified by researchers. Participants will be offered an AU $50 (US $32.82) gift card for their attendance.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>Recruitment for this project will commence in mid-2023, with data collection scheduled to commence in mid- to late 2023 and end in mid-2024. Co-design and review will occur throughout the data collection period.</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Strengths</title>
        <p>The key strength of this research and the broader PreHaRM project is the purposeful engagement of end users in each research activity; this is research with health professionals for health professionals. Preliminary engagement with the state government and local health networks has been achieved through engagement with the CIT. Comprised of senior hospital staff and government health care data professionals (managers and stewards), this group provides strategic information on data collection and use within the local health care system. This insight provides PreHaRM researchers with a deeper understanding of the administrative and technical context in which health professionals work. Similarly, the PreHaRM TAG includes leaders in AI software development and interface design. This group guides researchers’ thinking on the capacity of the PreHaRM algorithm. Both the CIT and the TAG have already been central to the predesign phase [<xref ref-type="bibr" rid="ref20">20</xref>] and will continue to remain involved in the upcoming stages of the design process. Health professionals drive the generative phase of the PreHaRM tool primarily through their efforts in the “notifiers” and “format” activities, but also through their descriptions of software use and their feelings toward AI within health care. The evaluative activities of researchers and the presentation of these results back to health professionals further involve them in the iterative and generative process at the crux of this research. The broad contextualization of the health care system and guidance of AI development from the CIT and TAG, respectively, are operationalized through the generative activities of health professionals at the “coal face.”</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>As primary end users, nurses are the target cohort for each workshop, and their input in these sessions will inform the PreHaRM GUI. Within the hospital context, however, it is possible that other health professionals may also use the PreHaRM GUI. Callen et al [<xref ref-type="bibr" rid="ref21">21</xref>] identified that differences in organizational culture along professional lines represent differences in attitudes toward HITs. Therefore, the focused recruitment of one health professional group is a potential limitation; future research should broaden recruitment to capture the design requirements of additional health professional cultures. Additional in situ research should be conducted with health professionals to confirm the issues they noted in the sessions are as consequential as they are real and to seek further refinements that improve the adoption of the PreHaRM tool.</p>
      </sec>
      <sec>
        <title>Practical Significance</title>
        <p>This project will engage health professionals in an iterative co-design process across 3 workshops. This process of repeat engagement will enable researchers to refine recommendations for the aesthetics and functionalities of the PreHaRM GUI. It is anticipated that by adopting their recommendations, health professionals will be more likely to accept and use this tool and to prevent forecast events from occurring. The target audience of this protocol is other health researchers, health professionals interested in research, and user interface and user experience design researchers.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The PreHaRM tool will combine an AI-enabled predictive risk algorithm with a co-designed GUI. The purpose of this algorithm is to identify the potential occurrence of adverse events, whereas the purpose of the GUI is to convey these potential events to health professionals in a meaningful manner. Indeed, the presentation of the algorithm results is paramount if the warning it displays is to be acknowledged and actioned. Co-design will be used in this research to identify end user aesthetic and functionality design recommendations to help ensure the appropriateness of the final product and its incorporation with existing work practices. This research takes as a basic assumption that the PreHaRM GUI, designed with input from health professionals, will be used by professionals to the benefit of patients and their families.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Professional practice dashboard use web-based survey.</p>
        <media xlink:href="resprot_v12i1e47717_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 30 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CALHN</term>
          <def>
            <p>Central Adelaide Local Health Network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CIT</term>
          <def>
            <p>clinical implementation team</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">CPOE</term>
          <def>
            <p>computerized provider order entry</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">DHCRC</term>
          <def>
            <p>Digital Health Cooperative Research Centre</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">GUI</term>
          <def>
            <p>graphical user interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">HIT</term>
          <def>
            <p>health information technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">NASSS</term>
          <def>
            <p>Nonadoption, Abandonment and Challenges to the Scale-up, Spread and Sustainability</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">PreHaRM</term>
          <def>
            <p>Predictive Harm Response Management</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">SALHN</term>
          <def>
            <p>Southern Adelaide Local Health Network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">SHAIP</term>
          <def>
            <p>Shinners Artificial Intelligence Perception</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">TAG</term>
          <def>
            <p>technical advisory group</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">TFA</term>
          <def>
            <p>theoretical framework of analysis</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This research was supported by Digital Health Cooperative Research Centre (DHCRC) Limited. DHCRC Limited is funded under the Australian Commonwealth Government’s Cooperative Research Centers Program (Project #DHCRC-0156).</p>
    </ack>
    <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>Buttigieg</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Pace</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rathert</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Hospital performance dashboards: a literature review</article-title>
          <source>J Health Organ Manag</source>
          <year>2017</year>
          <volume>31</volume>
          <issue>3</issue>
          <fpage>385</fpage>
          <lpage>406</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1108/JHOM-04-2017-0088"/>
          </comment>
          <pub-id pub-id-type="doi">10.1108/JHOM-04-2017-0088</pub-id>
          <pub-id pub-id-type="medline">28686130</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>Kruse</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Stein</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kaur</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>The use of electronic health records to support population health: a systematic review of the literature</article-title>
          <source>J Med Syst</source>
          <year>2018</year>
          <volume>42</volume>
          <issue>11</issue>
          <fpage>214</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/article/10.1007/s10916-018-1075-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-018-1075-6</pub-id>
          <pub-id pub-id-type="medline">30269237</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-018-1075-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC6182727</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>Almoaber</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Amyot</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Key factors of clinicians' acceptance of CPOE system and their link to change management</article-title>
          <source>Inform Health Soc Care</source>
          <year>2022</year>
          <volume>47</volume>
          <issue>3</issue>
          <fpage>326</fpage>
          <lpage>345</lpage>
          <pub-id pub-id-type="doi">10.1080/17538157.2021.1993858</pub-id>
          <pub-id pub-id-type="medline">34723747</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>Tay</surname>
              <given-names>BSJ</given-names>
            </name>
            <name name-style="western">
              <surname>Edney</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Brinkworth</surname>
              <given-names>GD</given-names>
            </name>
            <name name-style="western">
              <surname>Cox</surname>
              <given-names>DN</given-names>
            </name>
            <name name-style="western">
              <surname>Wiggins</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gwilt</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Haveman-Nies</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Co-design of a digital dietary intervention for adults at risk of type 2 diabetes</article-title>
          <source>BMC Public Health</source>
          <year>2021</year>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>2071</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpublichealth.biomedcentral.com/articles/10.1186/s12889-021-12102-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12889-021-12102-y</pub-id>
          <pub-id pub-id-type="medline">34763701</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12889-021-12102-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC8582335</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>Porat</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Delaney</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kostopoulou</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>The impact of a diagnostic decision support system on the consultation: perceptions of GPs and patients</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2017</year>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>79</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-017-0477-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-017-0477-6</pub-id>
          <pub-id pub-id-type="medline">28576145</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-017-0477-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC5457602</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>Van Dort</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>WY</given-names>
            </name>
            <name name-style="western">
              <surname>Sundar</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Baysari</surname>
              <given-names>MT</given-names>
            </name>
          </person-group>
          <article-title>Optimizing clinical decision support alerts in electronic medical records: a systematic review of reported strategies adopted by hospitals</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2021</year>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>177</fpage>
          <lpage>183</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33186438"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa279</pub-id>
          <pub-id pub-id-type="medline">33186438</pub-id>
          <pub-id pub-id-type="pii">5981524</pub-id>
          <pub-id pub-id-type="pmcid">PMC7810441</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>Farre</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Heath</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bem</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Cummins</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>How do stakeholders experience the adoption of electronic prescribing systems in hospitals? A systematic review and thematic synthesis of qualitative studies</article-title>
          <source>BMJ Qual Saf</source>
          <year>2019</year>
          <volume>28</volume>
          <issue>12</issue>
          <fpage>1021</fpage>
          <lpage>1031</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://qualitysafety.bmj.com/content/28/12/1021"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2018-009082</pub-id>
          <pub-id pub-id-type="medline">31358686</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2018-009082</pub-id>
          <pub-id pub-id-type="pmcid">PMC6934241</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>McLeod</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Karampatakis</surname>
              <given-names>GD</given-names>
            </name>
            <name name-style="western">
              <surname>Heyligen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>McGinley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Franklin</surname>
              <given-names>BD</given-names>
            </name>
          </person-group>
          <article-title>The impact of implementing a hospital electronic prescribing and administration system on clinical pharmacists' activities—a mixed methods study</article-title>
          <source>BMC Health Serv Res</source>
          <year>2019</year>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>156</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-019-3986-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-019-3986-4</pub-id>
          <pub-id pub-id-type="medline">30866925</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-019-3986-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC6417214</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>Mogharbel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dowding</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ainsworth</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Physicians' use of the computerized physician order entry system for medication prescribing: systematic review</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>3</issue>
          <fpage>e22923</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/3/e22923"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22923</pub-id>
          <pub-id pub-id-type="medline">33661126</pub-id>
          <pub-id pub-id-type="pii">v9i3e22923</pub-id>
          <pub-id pub-id-type="pmcid">PMC7974763</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>Gardner</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Cooper</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Haskell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Poplau</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kroth</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Linzer</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Physician stress and burnout: the impact of health information technology</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <volume>26</volume>
          <issue>2</issue>
          <fpage>106</fpage>
          <lpage>114</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/jamia/article/26/2/106/5230918?login=false"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy145</pub-id>
          <pub-id pub-id-type="medline">30517663</pub-id>
          <pub-id pub-id-type="pii">5230918</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647171</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>Shinners</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Grace</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stephens</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Aggar</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Exploring healthcare professionals' perceptions of artificial intelligence: piloting the shinners artificial intelligence perception tool</article-title>
          <source>Digit Health</source>
          <year>2022</year>
          <volume>8</volume>
          <fpage>20552076221078110</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/20552076221078110"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/20552076221078110</pub-id>
          <pub-id pub-id-type="medline">35154807</pub-id>
          <pub-id pub-id-type="pii">10.1177_20552076221078110</pub-id>
          <pub-id pub-id-type="pmcid">PMC8832586</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>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Xiong</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Accelerating AI adoption with responsible AI signals and employee engagement mechanisms in health care</article-title>
          <source>Inf Syst Front</source>
          <year>2021</year>
          <fpage>1</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/article/10.1007/s10796-021-10154-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10796-021-10154-4</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>Slattery</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Saeri</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Bragge</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Research co-design in health: a rapid overview of reviews</article-title>
          <source>Health Res Policy Syst</source>
          <year>2020</year>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>17</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health-policy-systems.biomedcentral.com/articles/10.1186/s12961-020-0528-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12961-020-0528-9</pub-id>
          <pub-id pub-id-type="medline">32046728</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12961-020-0528-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC7014755</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>Sanz</surname>
              <given-names>MF</given-names>
            </name>
            <name name-style="western">
              <surname>Acha</surname>
              <given-names>BV</given-names>
            </name>
            <name name-style="western">
              <surname>García</surname>
              <given-names>MF</given-names>
            </name>
          </person-group>
          <article-title>Co-design for people-centred care digital solutions: a literature review</article-title>
          <source>Int J Integr Care</source>
          <year>2021</year>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>16</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ijic.org/articles/10.5334/ijic.5573"/>
          </comment>
          <pub-id pub-id-type="doi">10.5334/ijic.5573</pub-id>
          <pub-id pub-id-type="medline">33981193</pub-id>
          <pub-id pub-id-type="pmcid">PMC8086727</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brooke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>SUS: a quick and dirty usability scale</article-title>
          <source>Usability Evaluation In Industry</source>
          <year>1996</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
          <fpage>189</fpage>
        </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>Greenhalgh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wherton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Papoutsi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>A'Court</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hinder</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fahy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Beyond adoption: a new framework for theorizing and evaluating nonadoption, abandonment, and challenges to the scale-up, spread, and sustainability of health and care technologies</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>e367</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/11/e367/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8775</pub-id>
          <pub-id pub-id-type="medline">29092808</pub-id>
          <pub-id pub-id-type="pii">v19i11e367</pub-id>
          <pub-id pub-id-type="pmcid">PMC5688245</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sekhon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cartwright</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Francis</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>Acceptability of healthcare interventions: an overview of reviews and development of a theoretical framework</article-title>
          <source>BMC Health Serv Res</source>
          <year>2017</year>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>88</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-017-2031-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-017-2031-8</pub-id>
          <pub-id pub-id-type="medline">28126032</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-017-2031-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC5267473</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Visual design basics</article-title>
          <source>U.S. General Services Administration</source>
          <access-date>2023-07-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.usability.gov/what-and-why/visual-design.html">https://www.usability.gov/what-and-why/visual-design.html</ext-link>
          </comment>
        </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>Adami</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>What’s in a click? A social semiotic framework for the multimodal analysis of website interactivity</article-title>
          <source>Vis Commun</source>
          <year>2015</year>
          <volume>14</volume>
          <issue>2</issue>
          <fpage>133</fpage>
          <lpage>153</lpage>
          <pub-id pub-id-type="doi">10.1177/1470357214565583</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>Sanders</surname>
              <given-names>EBN</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <article-title>Probes, toolkits and prototypes: three approaches to making in codesigning</article-title>
          <source>CoDesign</source>
          <year>2014</year>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1080/15710882.2014.888183</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>Callen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Braithwaite</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Westbrook</surname>
              <given-names>JI</given-names>
            </name>
          </person-group>
          <article-title>The importance of medical and nursing sub-cultures in the implementation of clinical information systems</article-title>
          <source>Methods Inf Med</source>
          <year>2009</year>
          <volume>48</volume>
          <issue>2</issue>
          <fpage>196</fpage>
          <lpage>202</lpage>
          <pub-id pub-id-type="doi">10.3414/ME9212</pub-id>
          <pub-id pub-id-type="medline">19283319</pub-id>
          <pub-id pub-id-type="pii">09020196</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
