<?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 Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</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">v8i4e26964</article-id>
      <article-id pub-id-type="pmid">34842528</article-id>
      <article-id pub-id-type="doi">10.2196/26964</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>Clinician Preimplementation Perspectives of a Decision-Support Tool for the Prediction of Cardiac Arrhythmia Based on Machine Learning: Near-Live Feasibility and Qualitative Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Canares</surname>
            <given-names>Therese</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Montmirail</surname>
            <given-names>Valentin</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Matthiesen</surname>
            <given-names>Stina</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Computer Science</institution>
            <institution>Faculty of Science</institution>
            <institution>University of Copenhagen</institution>
            <addr-line>Universitetsparken 5</addr-line>
            <addr-line>Copenhagen, 2100</addr-line>
            <country>Denmark</country>
            <phone>45 21231008</phone>
            <email>matthiesen@di.ku.dk</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7143-7467</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Diederichsen</surname>
            <given-names>Søren Zöga</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9687-0857</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Hansen</surname>
            <given-names>Mikkel Klitzing Hartmann</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5609-2723</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Villumsen</surname>
            <given-names>Christina</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7425-4714</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Lassen</surname>
            <given-names>Mats Christian Højbjerg</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2255-582X</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Jacobsen</surname>
            <given-names>Peter Karl</given-names>
          </name>
          <degrees>DMSc, MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1520-8774</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Risum</surname>
            <given-names>Niels</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0357-9164</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Winkel</surname>
            <given-names>Bo Gregers</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3063-4712</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Philbert</surname>
            <given-names>Berit T</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9479-7601</ext-link>
        </contrib>
        <contrib id="contrib10" contrib-type="author">
          <name name-style="western">
            <surname>Svendsen</surname>
            <given-names>Jesper Hastrup</given-names>
          </name>
          <degrees>DMSc, MD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8466-8515</ext-link>
        </contrib>
        <contrib id="contrib11" contrib-type="author">
          <name name-style="western">
            <surname>Andersen</surname>
            <given-names>Tariq Osman</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-9342-5520</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Computer Science</institution>
        <institution>Faculty of Science</institution>
        <institution>University of Copenhagen</institution>
        <addr-line>Copenhagen</addr-line>
        <country>Denmark</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Vital Beats</institution>
        <addr-line>Copenhagen</addr-line>
        <country>Denmark</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Department of Cardiology</institution>
        <institution>Rigshospitalet</institution>
        <institution>Copenhagen University Hospital</institution>
        <addr-line>Copenhagen</addr-line>
        <country>Denmark</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Clinical Medicine</institution>
        <institution>Faculty of Health and Medical Sciences</institution>
        <institution>University of Copenhagen</institution>
        <addr-line>Copenhagen</addr-line>
        <country>Denmark</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Stina Matthiesen <email>matthiesen@di.ku.dk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Oct-Dec</season>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>26</day>
        <month>11</month>
        <year>2021</year>
      </pub-date>
      <volume>8</volume>
      <issue>4</issue>
      <elocation-id>e26964</elocation-id>
      <history>
        <date date-type="received">
          <day>5</day>
          <month>1</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>2</day>
          <month>3</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>23</day>
          <month>3</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>11</day>
          <month>10</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Stina Matthiesen, Søren Zöga Diederichsen, Mikkel Klitzing Hartmann Hansen, Christina Villumsen, Mats Christian Højbjerg Lassen, Peter Karl Jacobsen, Niels Risum, Bo Gregers Winkel, Berit T Philbert, Jesper Hastrup Svendsen, Tariq Osman Andersen. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 26.11.2021.</copyright-statement>
      <copyright-year>2021</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 Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2021/4/e26964" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Artificial intelligence (AI), such as machine learning (ML), shows great promise for improving clinical decision-making in cardiac diseases by outperforming statistical-based models. However, few AI-based tools have been implemented in cardiology clinics because of the sociotechnical challenges during transitioning from algorithm development to real-world implementation.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study explored how an ML-based tool for predicting ventricular tachycardia and ventricular fibrillation (VT/VF) could support clinical decision-making in the remote monitoring of patients with an implantable cardioverter defibrillator (ICD).</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Seven experienced electrophysiologists participated in a near-live feasibility and qualitative study, which included walkthroughs of 5 blinded retrospective patient cases, use of the prediction tool, and questionnaires and interview questions. All sessions were video recorded, and sessions evaluating the prediction tool were transcribed verbatim. Data were analyzed through an inductive qualitative approach based on grounded theory.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The prediction tool was found to have potential for supporting decision-making in ICD remote monitoring by providing reassurance, increasing confidence, acting as a second opinion, reducing information search time, and enabling delegation of decisions to nurses and technicians. However, the prediction tool did not lead to changes in clinical action and was found less useful in cases where the quality of data was poor or when VT/VF predictions were found to be irrelevant for evaluating the patient.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>When transitioning from AI development to testing its feasibility for clinical implementation, we need to consider the following: expectations must be aligned with the intended use of AI; trust in the prediction tool is likely to emerge from real-world use; and AI accuracy is relational and dependent on available information and local workflows. Addressing the sociotechnical gap between the development and implementation of clinical decision-support tools based on ML in cardiac care is essential for succeeding with adoption. It is suggested to include clinical end-users, clinical contexts, and workflows throughout the overall iterative approach to design, development, and implementation.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>cardiac arrhythmia</kwd>
        <kwd>short-term prediction</kwd>
        <kwd>clinical decision support systems</kwd>
        <kwd>machine learning</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>preimplementation</kwd>
        <kwd>qualitative study</kwd>
        <kwd>implantable cardioverter defibrillator</kwd>
        <kwd>remote follow-up</kwd>
        <kwd>sociotechnical</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Ventricular tachycardia and ventricular fibrillation (VT/VF) are potentially lethal cardiac arrhythmias, which constitute a growing challenge to health care systems worldwide [<xref ref-type="bibr" rid="ref1">1</xref>]. The development of implantable cardioverter defibrillators (ICDs) has led to major advances in the prevention of death from VT/VF [<xref ref-type="bibr" rid="ref2">2</xref>]. ICDs are implantable devices used in patients at increased risk of sudden cardiac death. ICDs monitor the heart rhythm continuously to detect and treat VT/VF. In recent years, remote monitoring has become the standard of care for ICD patients [<xref ref-type="bibr" rid="ref3">3</xref>], and follow-ups are based on transmission of data from the implanted device through the patient’s home monitoring box. This has reduced the number of in-office follow-ups [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>] and increased survival rates [<xref ref-type="bibr" rid="ref6">6</xref>] due to improved early detection of arrhythmias [<xref ref-type="bibr" rid="ref7">7</xref>]. However, the numbers of ICD implants are increasing worldwide, posing a workload challenge for electrophysiologists and technicians when assessing data from incoming transmissions in remote monitoring centers [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. There is a growing need for decision-making tools that can support and reduce data-intensive remote follow-ups, and while current systems can detect and treat VT/VF arrhythmias as they occur, tools for predicting arrhythmias before their onset are lacking [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
      <p>Artificial intelligence (AI), such as machine learning (ML), shows great promise for improving clinical decision-making in cardiac diseases by outperforming statistical-based models [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>], and recent examples include promising models for the prediction of heart disease and heart failure [<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref18">18</xref>], as well as cardiac arrhythmias, such as ventricular arrhythmia [<xref ref-type="bibr" rid="ref19">19</xref>], atrial fibrillation [<xref ref-type="bibr" rid="ref20">20</xref>], and electrical storm [<xref ref-type="bibr" rid="ref21">21</xref>]. There are positive attitudes and high expectations among physicians that AI will improve future patient care in fields where data are collected continuously, such as cardiology [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      <p>However, few prediction outcome algorithms based on ML have been implemented in cardiology clinics because of the challenges during transitioning from algorithm development to real-world implementation. While studies of medical AI-based tools that undergo prospective clinical validation are emerging [<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref27">27</xref>], there is a general lack of understanding of how AI may support achieving clinical effectiveness and improve patient care in real-life settings [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. Scholars have argued that ML-based patient outcome prediction models are yet to prove their worth to human clinicians [<xref ref-type="bibr" rid="ref30">30</xref>]. Prediction accuracy by itself can be impressive in the lab; however, this does not always translate to better treatment, and it is being stressed to look for ways to make human and AI prediction algorithms complement each other, ensuring actionability in clinical practice [<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. Going from research and development environments to hospital or clinical contexts is considered a challenging task that has been named “the last mile” of implementing medical AI-based tools [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>], and there is a call for research on how end-users find AI-based user interfaces useful in practice [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref39">39</xref>], as well as studies that report on the sociotechnical challenges of deploying AI-based tools in complex clinical environments [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref54">54</xref>].</p>
      <p>This study addresses the sociotechnical gap between the development and implementation of a clinical decision-support tool based on ML for the prediction of VT/VF in remote monitoring of ICD patients. The aim of this study was to explore the feasibility and clinician preimplementation perspectives of using a prediction tool for improved workflows. Therefore, this study does not provide algorithmic validation per se but instead answers questions about the clinical feasibility and workflow integration of a decision-support tool based on ML.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Understanding Needs and Co-design of the Prediction Tool</title>
        <p>This study was conducted at the remote monitoring center at Rigshospitalet, Copenhagen University Hospital, Denmark, which is a large tertiary hospital covering all aspects of treatments in cardiology and is among the largest centers in Europe having more than 4000 patients with cardiac implanted electronic devices in remote follow-up. The study was organized in 3 stages (<xref rid="figure1" ref-type="fig">Figure 1</xref>). In the first stage, field work observations in the remote monitoring clinic were conducted to understand both the clinical workflow and workload [<xref ref-type="bibr" rid="ref10">10</xref>]. This was followed by 3 co-design workshops with an electrophysiologist (PKJ) and 5 co-design workshops with a cardiologist consultant (SZD) focusing on feature engineering and sketching the user interface. In stage 2, the AI algorithm was developed, and in stage 3, a near-live feasibility and qualitative interview study was conducted. The study was reviewed by the Danish National Board of Health and the Danish National Committee on Health Research Ethics, and authorized by The Capital Region of Denmark.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Overall study design. ML: machine learning.</p>
          </caption>
          <graphic xlink:href="humanfactors_v8i4e26964_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Development of the AI Algorithm</title>
        <p>A prediction tool was developed for improving the support for clinical decision-making in ICD remote monitoring based on the random forest ML method, and it consisted of a risk prediction algorithm of VT/VF within 30 days. The prediction tool was designed to show alarm status (yes/no), risk probability (%), and ranking of the 5 most and least important parameters for the prediction, using the LIME technique [<xref ref-type="bibr" rid="ref55">55</xref>] (<xref rid="figure2" ref-type="fig">Figure 2</xref>). The design and development of the tool were informed by previous fieldwork studies of current practices [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref56">56</xref>], as well as early results from using ML to predict electrical storm, a severe form of cardiac arrhythmia [<xref ref-type="bibr" rid="ref21">21</xref>]. The data set used for developing the algorithm consisted of 11,921 transmissions from 1251 patients with an ICD or a cardiac resynchronization therapy defibrillator (CRT-D), followed over a 4-year period from 2015 to 2019 at Rigshospitalet. The data set contained 74,149 arrhythmia episodes, each characterized by 7 variables, such as the type of arrhythmia (VT, VF, supraventricular tachycardia, atrial fibrillation, etc), ICD treatment of the arrhythmia, duration of the episode, and maximum heart rate reached during the episode.</p>
        <p>The random forest ML method [<xref ref-type="bibr" rid="ref44">44</xref>] was selected for algorithm development because it provided optimal results when considering the tradeoffs between model performance and explainability. Several other classifier methods (supervised, unsupervised, and deep learning methods) were evaluated through development and testing, including KNeighborsClassifier [<xref ref-type="bibr" rid="ref57">57</xref>], GradientBoostingClassifier [<xref ref-type="bibr" rid="ref58">58</xref>], AdaBoostClassifier [<xref ref-type="bibr" rid="ref59">59</xref>], support vector classifier [<xref ref-type="bibr" rid="ref60">60</xref>], and long short-term memory (LSTM) [<xref ref-type="bibr" rid="ref61">61</xref>]. The deep learning method, LSTM, provided poorer performance and poorer explainability, possibly due to the nature of the data (ie, time series data with considerable time between events, making time series modeling difficult). The other methods provided similar performance. KNeighborsClassifier and support vector machine had the worst performance, while the decision tree methods had the best performance. GradientBoostingClassifier produced an optimal F1 score and recall score; however, random forest provided the highest accuracy and precision scores, which led to the choice of using the random forest method for developing the first version of the algorithm to be evaluated with end-users in this study. The algorithm was tested on 2342 of the 11,921 transmissions. The transmission data were stratified and grouped into training and test sets. This means that the prevalence of the positive condition was the same in both the training and test sets (stratified) and that no patient had data in both data sets (grouped). The algorithm achieved an accuracy of 0.96, with a positive predictive value of 0.67 and a negative predictive value of 0.97. The probability threshold for raising an alarm was set to 0.28, indicating the value with an optimal tradeoff between negative and positive predictive outcomes.</p>
        <p>Feature engineering was carried out in collaboration between 2 data scientists (MKHH and CV) and a cardiologist consultant (SZD) during 5 co-design workshops. A total of 48 features (referred to as parameters when discussed with the study participants) were developed, and the following 2 main principles were adopted: aggregating episodes by day and building a historic snapshot for days leading up to the arrhythmic event. To provide the clinical end-user with algorithm explainability, the LIME technique [<xref ref-type="bibr" rid="ref55">55</xref>] was used to show the top 5 features that increase or decrease the likelihood of a VT/VF arrhythmic event occurring within the coming 30 days.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>The prediction tool on a paper printout as shown to study participants (Case 3, see Table 2). The output shows the alarm (yes/no), risk probability (%), and up to 5 most important parameters for increasing and decreasing the likelihood of ventricular tachycardia and ventricular fibrillation within 30 days. To the right: example pictures of electrophysiologists conducting near-live case walkthroughs.</p>
          </caption>
          <graphic xlink:href="humanfactors_v8i4e26964_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Study Participants and Case Selection</title>
        <p>Seven medical doctors specialized in electrophysiology (ie, cardiologists treating patients with cardiac arrhythmia) were selected for participation from a convenience sample (<xref ref-type="table" rid="table1">Table 1</xref>). Participants included 6 males and 1 female (average age, 52 years; average work experience as an electrophysiologist, 13 years).</p>
        <p>A selection of 5 retrospective patient cases (<xref ref-type="table" rid="table2">Table 2</xref>) was used to evaluate the feasibility of the prediction tool’s ability to support clinical decision-making. The cases included high and low risk probability, true positives, and true negatives, and 2 cases with AF as the primary episode type. Patient cases were retrieved 19 to 27 months back in time, blinded, and presented as paper printouts with a summary of each patient’s clinical history along with reports from the electronic health record (list of diagnoses, progress notes from the cardiology department, latest blood tests, and list of medications) and screenshots of relevant ICD transmission data, including device type, battery status, device programming and settings, time of implantation, latest diagnostic information about the transmission, frequency of arrhythmias, heart rate, device therapy, and assessment of physical activity.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Participating electrophysiologists.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="90"/>
            <col width="90"/>
            <col width="100"/>
            <col width="320"/>
            <col width="400"/>
            <thead>
              <tr valign="top">
                <td>Participant</td>
                <td>Sex</td>
                <td>Age (years)</td>
                <td>Title</td>
                <td>Years since obtaining specialist certification in cardiology</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Female</td>
                <td>52</td>
                <td>Consultant cardiologist, MD, PhD</td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Male</td>
                <td>61</td>
                <td>Professor, consultant cardiologist, MD, DMSc</td>
                <td>23</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Male</td>
                <td>55</td>
                <td>Consultant cardiologist, MD, PhD</td>
                <td>14</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Male</td>
                <td>43</td>
                <td>Cardiologist, MD, PhD</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Male</td>
                <td>62</td>
                <td>Consultant cardiologist, MD, DMSc</td>
                <td>28</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>Male</td>
                <td>44</td>
                <td>Cardiologist, MD, PhD</td>
                <td>2</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>Male</td>
                <td>47</td>
                <td>Consultant cardiologist, MD, DMSc</td>
                <td>9</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Case overview with patient summary, current implantable cardioverter defibrillator transmission information, and prediction tool information.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="70"/>
            <col width="220"/>
            <col width="120"/>
            <col width="70"/>
            <col width="80"/>
            <col width="180"/>
            <col width="0"/>
            <col width="110"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td>Case number</td>
                <td>Patient summary</td>
                <td colspan="5">Current ICD<sup>a</sup> transmission</td>
                <td colspan="2">Prediction tool</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Transmission type</td>
                <td>Primary episode type</td>
                <td>ICD treatment</td>
                <td>Transmission summary</td>
                <td colspan="2">30-day VT<sup>b</sup>/VF<sup>c</sup> risk probability</td>
                <td>Alarm raised (prediction outcome)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Male, age 63 years, ischemic heart failure, left ventricular assist device</td>
                <td>Automated</td>
                <td>VT/VF</td>
                <td>ATP<sup>d</sup></td>
                <td>3 VT/VF; 36 sensing episodes; 217 VT-NS<sup>e</sup></td>
                <td colspan="2">58.6</td>
                <td>Yes (true positive)</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Female, age 67 years, dilated cardiomyopathy</td>
                <td>Automated</td>
                <td>VT/VF</td>
                <td>Shock</td>
                <td>1 VT/VF; 1 VT-NS; 20 min of AF<sup>f</sup> since the last transmission</td>
                <td colspan="2">14.4</td>
                <td>No (true negative)</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Female, age 40 years, dilated cardiomyopathy</td>
                <td>Automated</td>
                <td>VT/VF</td>
                <td>Shock</td>
                <td>2 VT/VF; 4 VT-NS</td>
                <td colspan="2">35.4</td>
                <td>Yes (true positive)</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Male, age 61 years, ischemic heart failure</td>
                <td>Patient initiated</td>
                <td>AF</td>
                <td>None</td>
                <td>12 hours of AF since the last transmission</td>
                <td colspan="2">1.2</td>
                <td>No (true negative)</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Male, age 73 years, ischemic heart failure</td>
                <td>Automated</td>
                <td>AF</td>
                <td>None</td>
                <td>14 hours of AF since the last session; 26 VT-NS</td>
                <td colspan="2">7.8</td>
                <td>No (true negative)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>ICD: implantable cardioverter defibrillator.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>VT: ventricular tachycardia.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>VF: ventricular fibrillation.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>ATP: antitachycardia pacing.</p>
            </fn>
            <fn id="table2fn5">
              <p><sup>e</sup>VT-NS: nonsustained ventricular tachycardia.</p>
            </fn>
            <fn id="table2fn6">
              <p><sup>f</sup>AF: atrial fibrillation.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Data Collection</title>
        <p>A combined feasibility and qualitative interview study was undertaken based on a retrospective case study design. The primary aim of the study was to address the following 4 main questions about the feasibility of the prediction tool using quantitative measures: Does use of the tool lead to change in clinical action? Does it support decision-making? Are visualizing parameters useful? Can it reduce time spent? The secondary aims were to understand the electrophysiologist’s immediate reactions to using the prediction tool, including qualifying the quantitative feasibility measures against qualitative dimensions based on interviews. Electrophysiologists were invited to conduct a “near-live” clinical simulation of decision-making based on walkthroughs of the 5 patient cases (<xref ref-type="table" rid="table2">Table 2</xref>) with and without the prediction tool. Two structured questionnaires based on a 5-point Likert scale were designed to capture electrophysiologists’ decisions on action without the prediction tool (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) and their experiences of the feasibility of the prediction tool (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). A semistructured interview guide was designed based on the framework of Bowen et al for feasibility studies [<xref ref-type="bibr" rid="ref62">62</xref>] to cover open-ended questions about the electrophysiologists’ overall experiences of using the prediction tool. Ten questions in the following 4 areas of inquiry were posed: acceptability, demand, adoption, and implementation (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>).</p>
        <p>“Near-live” case walkthroughs were performed with inspiration from Li et al [<xref ref-type="bibr" rid="ref63">63</xref>] (<xref rid="figure1" ref-type="fig">Figure 1</xref>), and they were facilitated by the authors SM, MKHH, and TOA. First, the electrophysiologist was on-boarded with a presentation of the study objectives, the intended use of the prediction tool, the algorithm development (data set and ML model, as well as results), and the outline of the feasibility and qualitative study processes, and time was provided to resolve open questions. Second, the electrophysiologist was provided with a patient case and asked to do a walkthrough of the case material to reach a decision on clinical action, similar to normal clinical practice, and was asked to answer the first questionnaire and explain the reasoning behind the decision on clinical action. Third, the electrophysiologist received the prediction tool on paper and was asked to answer the second questionnaire for evaluation of the effects of the prediction tool and to share his/her immediate reactions. Fourth, after ending all patient case walkthroughs, the electrophysiologist was interviewed about his/her experience of the feasibility of the prediction tool. The total time for observations and interviews was 12.5 hours, with an average of 1 hour 47 minutes per electrophysiologist. Case walkthroughs and interviews were audio and video recorded, and sections with electrophysiologists’ responses to the questionnaires and the open-ended interview were transcribed verbatim.</p>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>Data from electrophysiologists’ reactions to the interview study were analyzed using an inductive qualitative approach based on grounded theory [<xref ref-type="bibr" rid="ref64">64</xref>]. A 2-step iterative coding process was applied beginning with line-by-line coding to support initial analytic decisions about the data. Action codes were developed by using gerunds (a noun form of a verb) to make explicit what electrophysiologists were doing during case walkthroughs and what meaning they derived (eg, “being confirmed,” “building trust,” and “using to prioritize”). This was done to preserve focus on action and situated processes of electrophysiologists’ decision-making, and to turn thematic descriptions into analytical insights in later stages of the analysis. Focused coding was carried out by iteratively sorting and synthesizing line-by-line codes into themes and subthemes related to the research questions and by constructing key insights. This process allowed for comparing and turning frequently reappearing initial codes across large amounts of data, and obtaining more general and analytically incisive findings (eg, “predictions can serve as a second opinion” and “decision-making workload is reduced when trust in the prediction tool is established”). The entire process was carried out iteratively in collaboration between SM and TOA using the qualitative data analysis software NVivo 12 (QSR International).</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Feasibility of the Prediction Tool in Clinical Practice</title>
        <sec>
          <title>Does the Prediction Tool Change Clinical Decisions?</title>
          <p>Overall, the electrophysiologists did not change their decisions on clinical action when presented with the 30-day VT/VF arrhythmia prediction (<xref ref-type="table" rid="table3">Table 3</xref>). However, several electrophysiologists found that the prediction tool was helpful (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 1) and increased their confidence in their choice of clinical action, and that the predictions could help prioritize patients (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 2) and determine what action to take in relation to the local circumstances at the clinic (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 3).</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Effect of the prediction tool on electrophysiologists’ decision-making.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="360"/>
              <col width="110"/>
              <col width="100"/>
              <col width="100"/>
              <col width="100"/>
              <col width="100"/>
              <col width="100"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Question and answer</td>
                  <td>Total (N=35), n (%)</td>
                  <td>Case 1 (N=7), n (%)</td>
                  <td>Case 2 (N=7), n (%)</td>
                  <td>Case 3 (N=7), n (%)</td>
                  <td>Case 4 (N=7), n (%)</td>
                  <td>Case 5 (N=7), n (%)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q1: The prediction tool made me change my decision on clinical action</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Yes</td>
                  <td>1 (3)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>No</td>
                  <td>34 (97)</td>
                  <td>6 (86)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q1a: I will contact the patient</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Strongly disagree/disagree</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Neither agree nor disagree</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Agree/strongly agree</td>
                  <td>35 (100)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                  <td>7 (100)</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q1b: I will book a procedure or reschedule an existing procedure</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Strongly disagree/disagree</td>
                  <td>3 (9)</td>
                  <td>0 (0)</td>
                  <td>1 (14)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>1 (14)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Neither agree nor disagree</td>
                  <td>6 (17)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>4 (57)</td>
                  <td>1 (14)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Agree/strongly agree</td>
                  <td>26 (74)</td>
                  <td>6 (86)</td>
                  <td>6 (86)</td>
                  <td>6 (86)</td>
                  <td>3 (43)</td>
                  <td>5 (71)</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q1c: I will do something else</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Strongly disagree/disagree</td>
                  <td>19 (54)</td>
                  <td>5 (71)</td>
                  <td>3 (43)</td>
                  <td>5 (71)</td>
                  <td>2 (29)</td>
                  <td>4 (57)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Neither agree nor disagree</td>
                  <td>5 (14)</td>
                  <td>1 (14)</td>
                  <td>1 (14)</td>
                  <td>1 (14)</td>
                  <td>2 (29)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Agree/strongly agree</td>
                  <td>11 (31)</td>
                  <td>1 (14)</td>
                  <td>3 (43)</td>
                  <td>1 (14)</td>
                  <td>3 (43)</td>
                  <td>3 (43)</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q2: The prediction tool supported my decision-making</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Strongly disagree/disagree</td>
                  <td>8 (23)</td>
                  <td>2 (29)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>3 (43)</td>
                  <td>2 (29)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Neither agree nor disagree</td>
                  <td>4 (11)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>1 (14)</td>
                  <td>1 (14)</td>
                  <td>1 (14)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Agree/strongly agree</td>
                  <td>23 (66)</td>
                  <td>4 (57)</td>
                  <td>6 (86)</td>
                  <td>6 (86)</td>
                  <td>3 (43)</td>
                  <td>4 (57)</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q3: The prediction tool’s visualization of parameters supported my decision making</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Strongly disagree/disagree</td>
                  <td>11 (31)</td>
                  <td>3 (43)</td>
                  <td>1 (14)</td>
                  <td>2 (29)</td>
                  <td>3 (43)</td>
                  <td>2 (29)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Neither agree nor disagree</td>
                  <td>3 (9)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>1 (14)</td>
                  <td>1 (14)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Agree/strongly agree</td>
                  <td>21 (60)</td>
                  <td>3 (43)</td>
                  <td>6 (86)</td>
                  <td>5 (71)</td>
                  <td>3 (43)</td>
                  <td>4 (57)</td>
                </tr>
                <tr valign="top">
                  <td colspan="2">
                    <bold>Q4: The prediction tool can help me reach a decision faster</bold>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Strongly disagree/disagree</td>
                  <td>13 (37)</td>
                  <td>4 (57)</td>
                  <td>2 (29)</td>
                  <td>2 (29)</td>
                  <td>2 (29)</td>
                  <td>3 (43)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Neither agree nor disagree</td>
                  <td>4 (11)</td>
                  <td>1 (14)</td>
                  <td>0 (0)</td>
                  <td>0 (0)</td>
                  <td>3 (43)</td>
                  <td>0 (0)</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Agree/strongly agree</td>
                  <td>18 (51)</td>
                  <td>2 (29)</td>
                  <td>5 (71)</td>
                  <td>5 (71)</td>
                  <td>2 (29)</td>
                  <td>4 (57)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <boxed-text id="box1" position="float">
            <title>Themes, insights, and illustrative quotes describing the feasibility of the prediction tool.</title>
            <p>
              <bold>Taking Action</bold>
            </p>
            <p><bold>Insights:</bold> The prediction tool led to no change in clinical action; the prediction tool can increase confidence in clinical action; the prediction tool can help prioritize clinical action and patients; and being confirmed supports decision-making.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 1:</bold><italic> Well, it hasn’t changed my current decision, but the basis is much better, and I can easily see that it has helped me.</italic> [Case 3, Electrophysiologist #7]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 2:</bold><italic> If you are in a busy situation where many transmissions have arrived and the technician and I have to maneuver and prioritize, there is no doubt that we will concentrate on those with high-risk predictions.</italic> [Electrophysiologist #5]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 3:</bold><italic> This [tool prediction] is something that might make me react a little more aggressively. […] Now I've been told that he's actually more likely to get an episode within the next month than he's not getting an episode […] if our program is fully booked, both today and tomorrow, and the day after tomorrow, but on Friday we have a time. Then I kind of have to make a trade off if I really want to spare him a shock. Which may turn into a lot of shocks.</italic> [Case 1, Electrophysiologist #2]</p>
              </list-item>
            </list>
            <p>
              <bold>Decision-Making</bold>
            </p>
            <p><bold>Insights:</bold> The prediction tool predictions served as a second opinion; the prediction tool supported gathering of thoughts; the overall presentation of the prediction tool needs to be easily translatable to clinical relevance; and being confirmed supports decision-making.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 4:</bold><italic> So, I agree with the conclusion, it was also my feeling that I would be a little worried about this patient.</italic> [Case 3, Electrophysiologist #6]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 5:</bold><italic> But then if it is you now have to convince some [other electrophysiologists] that they should ablate her, then instead of saying that I think so, you can argue that the algorithm thinks so too. So, in that way you can say that you can get an extra view of it.</italic> [Case 3, Electrophysiologist #3]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 6:</bold><italic> In that way, the algorithm can be a support because it helps to gather thoughts about things that play a role in whether a person gets a new arrhythmia.</italic> [Case 3, Electrophysiologist #5]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 7:</bold><italic> Yes, I think again that if you present 58.6% then it expresses an accuracy that you may have difficulty navigating with. I know it from other areas in the medical world, the thing about expressing something with a decimal number, it expresses an accuracy for which there may be no evidence at all […] I have a hard time relating to the number […] it’s problematic to translate that into something clinically relevant.</italic> [Case 1, Electrophysiologist #5]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 8:</bold><italic> I agree with what the alarm tells me, but I don’t think it has helped me very much right here.</italic> [Case 5, Electrophysiologist #5]</p>
              </list-item>
            </list>
            <p>
              <bold>Visualization</bold>
            </p>
            <p><bold>Insights:</bold> The prediction tool should provide actionable parameters; showing parameters enables confirmation and agreement; showing parameters enables in-situ validation of algorithmic inputs and the prediction tool result; the prediction tool performs only as good as the data it bases its predictions on; transparency about the algorithmic data input helped raise confidence and trust; and showing important parameters is more important than showing the output probability.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 9:</bold><italic> To list what counts for and what counts against, makes really good sense. That’s also how it works in my head.</italic> [Case 3, Electrophysiologist #7]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 10:</bold><italic> I think it's super good, I actually think it's really pedagogical, I like it. Because, in reality this is how it confirms the result. It’s basically the same empirical data that you have in your mind: You say “okay, is this a case where we have to do something?” It sums up some assumptions that you have made yourself, and in that way, I actually think you are confirmed more than if you have a green or red light.</italic> [Electrophysiologist #4]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 11:</bold><italic> It's very nice to see that the algorithm reacts on the same parameters that I've discovered myself ... So it's nice to see that I agree with it. You could say that it’s supporting and it's safe to know, that it also says there was something here.</italic> [Case 3, Electrophysiologist #1]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 12:</bold><italic> What's happening here is that the ICD detects that the patient has VT, and then the prediction tool bases it’s predictions on that. But it’s not entirely correct, because the device has recently been re-programmed to sense everything.</italic> [Case 1, Electrophysiologist #6]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 13:</bold><italic> This case has nothing to do with risk of VT/VF [...] it's the second thing I look at. No, here I won’t use it [the prediction tool].</italic> [Case 4, Electrophysiologist #1]</p>
              </list-item>
            </list>
            <p> </p>
            <p>
              <bold>Time Saving</bold>
            </p>
            <p><bold>Insights:</bold> The prediction tool can speed up decision-making when trust is established; the prediction tool can reduce workload when trust is established; the prediction tool can reduce information search time when no or low risk is predicted; the prediction tool can substitute patient input; and showing important parameters enables work redelegation to technicians and nurses.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 14:</bold><italic> It will give me a much better basis for decision making and I actually think it will save me a lot of time. Just like with all other new technology based on machine learning: the first 2 months I sit and read through to see what I have, but in month 3, I will look at the output alone. Because then I trust that it has pulled out what is appropriate, and then it starts saving me all the work I did in the beginning. But for everyone, it is that there is a phase for you personally to find out if this brings you further. […] I really think I would have come to the decision faster if I had seen this first.</italic> [Case 3, Electrophysiologist #7]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 15:</bold><italic> I might reach a decision faster with this system if I can’t get a hold of the patient i.e., if the patient does not pick up the phone. Then it could well be that I look at the alarm and say “well, yes okay there is low risk.”</italic> [Case 2, Electrophysiologist #6]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 16:</bold><italic> You could make a scenario where the technician first looks at it [the prediction tool] and says ... okay there are those parameters and there is electrical storm, so we call in the patient and the doctor does not have to look at the transmission. That would support our workflow.</italic> [Case 1, Electrophysiologist #4]</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>In Which Cases Does the Prediction Tool Support Clinical Decision-Making?</title>
          <p>In 23 (66%) of the case walkthroughs, the electrophysiologists agreed that the prediction tool supported their decision-making, whereas in 8 (23%) of the walkthroughs they disagreed. Finding the prediction tool supporting was particularly pertinent in both patient cases 2 and 3, where 6 (86%) of the electrophysiologists agreed, and the prediction tool was found to assist decision-making by confirming the electrophysiologists’ clinical evaluations and expectations of an increasing risk of VF/VT (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 4). On the contrary, when the electrophysiologists were focused on predicting arrhythmias other than VT/VF, the prediction tool was deemed less useful, and answers were more heterogenous (Case 4 and Case 5). Some electrophysiologists said that the predictions served as a second opinion (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 5) and that the prediction tool was helpful for collecting arguments that supported the electrophysiologists when trying to “gather thoughts” about potential VT/VF occurrences (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 6). Nevertheless, some electrophysiologists found that showing the probability score as a percentage with decimals created uncertainty, and the naming of parameters was sometimes found difficult to interpret (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 7).</p>
        </sec>
        <sec>
          <title>Is Visualization of Important Parameters Useful?</title>
          <p>The prediction tool’s visualization of the most important parameters in the prediction of increased or decreased probability of VT/VF arrhythmia was found useful when the electrophysiologists agreed with the parameters presented. In patient cases 2 and 3, 6 (86%) and 5 (71%) of the electrophysiologists agreed that showing important parameters supported their decision-making. However, when the parameters represented poor data quality (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 12), agreement was lower, for example, in patient Case 1 (43% agreed, 43% disagreed), or when the electrophysiologists were focused on predicting arrhythmias (Case 4 and Case 5) other than what the prediction tool was designed for (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 13).</p>
          <p>In general, presentation of important parameters provided explainability and supported decision-making by resembling the clinical interpretation process of what counts for or against the occurrence of VT/VF (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 9). Several electrophysiologists found that visualization of important parameters created more confidence in the prediction tool than the probability score alone as the tool summed up many of the same assumptions that the electrophysiologists already had (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 10). Listing the algorithm’s important parameters also enabled electrophysiologists to do in-situ validations of the prediction tool’s predictions by interpreting the data against the patient case (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 11). However, in some cases, the electrophysiologists found that the parameters were based on wrong data from the ICD transmission. In those cases, it enabled electrophysiologists to check if the prediction tool based its predictions on wrong or poor data quality and to decide whether to trust the predictions or not (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 12).</p>
        </sec>
        <sec>
          <title>Does the Prediction Tool Reduce Time for Decision-Making?</title>
          <p>The electrophysiologists found that the prediction tool could enable a reduction in time for decision-making in cases where they trusted the predictions. Moreover, 5 (71%) of the electrophysiologists agreed that the prediction tool can help reach a decision faster (Case 2 and Case 3). However, agreement was lower (29% in Case 1 and 57% in Case 5) when predictions were found to be uncertain or less useful for handling patients.</p>
          <p>Several of the electrophysiologists expressed that once they become familiar with the system, they expect the AI tool will speed up decision-making and reduce the diagnostic workload. This indicates that establishing trust in AI predictions is essential. One of the electrophysiologists explained how time can be saved when personal trust in the prediction tool is developed (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 14).</p>
          <p>Across all cases, several electrophysiologists found that the probability score and the presentation of important parameters can reduce information search time. Typically, electrophysiologists must retrieve valuable information by clicking through multiple webpages in the ICD manufacturer’s web-based system, which the prediction tool summarizes in a table. Some electrophysiologists also speculated that the tool could support decision-making when patient input is inaccessible, such as when a patient does not answer the phone (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 15). Other electrophysiologists considered that the tool can support workflow and reduce unnecessary time consumption for electrophysiologists by delegating decision-making to the technician (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>, Quote 16).</p>
        </sec>
      </sec>
      <sec>
        <title>Clinician Preimplementation Perspectives of the Prediction Tool: Acceptability, Adoption, Demand, and Implementation</title>
        <sec>
          <title>Acceptability</title>
          <p>Acceptability of the prediction tool was high when patient cases concerned VT/VF, as the risk predictions were found to be relevant. However, several electrophysiologists had expectations that the prediction tool would bring new and groundbreaking insights (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 1) to support or challenge their decisions on which action to take. In cases where the task-technology fit was lower (Case 1, Case 4, and Case 5), acceptability was also lower (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 2). For some of the electrophysiologists, the prediction tool was therefore considered “nice to have” rather than “need to have” (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 3), while most of the electrophysiologists recognized the potential of the prediction tool. Some of the electrophysiologists considered the tool useful for standardizing decision-making across the electrophysiologist team by avoiding individual influences from recent experiences and thus achieving harmonization of individual treatment (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 4).</p>
        </sec>
        <sec>
          <title>Adoption</title>
          <p>There was consensus that high precision is important for prediction tool adoption to happen. Several of the electrophysiologists emphasized that the positive or negative predictive value should be as unambiguous as possible, showing either low or high risk when the alarm is raised (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 5). Other electrophysiologists emphasized that false positives or negatives hinder adoption, which they explained to be the case for the adoption of OptiVol (an early warning alarm for fluid-related decompensation). Here, the electrophysiologist team decided not to use it due to too many false positives (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 6). Several electrophysiologists explained that acceptance and clinical adoption are collectively decided based on team experiences from real-world use (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 7) and from experiencing that the prediction tool actually confirms decisions in everyday clinical practice (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 8). Adoption can also be achieved through building trust in the tool by means of validation studies. Participants explained that trust is a precondition for adoption, which can be achieved by documenting effects in a randomized clinical trial and through algorithm validation in peer-reviewed journals (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 9).</p>
        </sec>
        <sec>
          <title>Demand</title>
          <p>Several of the electrophysiologists emphasized that there is a high demand for workflow support in remote monitoring of cardiac device patients. They found the prediction tool useful for supporting more efficient prioritization and identification of important patient cases (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 10). Others described the demand for screening support among the increasing number of nonspecialized hospitals where fewer electrophysiologists are at work. For example, the prediction tool could support technicians doing the initial prioritization work more effectively and efficiently; the prediction tool could decrease electrophysiologists’ patient information search time when handed over from technicians; and the prediction tool could function as “data help” by enabling junior doctors to get a form of senior help by consulting the tool (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 11).</p>
        </sec>
        <sec>
          <title>Implementation</title>
          <p>To ensure successful implementation, some electrophysiologists described how remote monitoring clinics may want to be able to adjust the threshold of the prediction tool to fit local workflows and prioritization rules. For example, technicians and electrophysiologists should be able to configure the prediction tool and decide on related actions, such as “no need to take action” or “need to contact the patient.” Relatedly, several electrophysiologists explained that indications of low-risk patients are especially useful in supporting clinicians in handling low-risk transmissions (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 12). Moreover, the electrophysiologists explained that the intention of using the prediction tool is dependent on easy access, as well as how well it presents data and alleviates the need for clicking through several web pages in remote monitoring systems (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 13). Some electrophysiologists added that it is practical that the algorithm uses data already available in remote monitoring systems, which are used daily for decision-making in the clinic. Knowing the data creates transparency and enables in-situ validation of the correctness of the probability score, thereby increasing the likelihood for success with implementation of the prediction tool (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>, Quote 14).</p>
          <boxed-text id="box2" position="float">
            <title>Themes, insights, and illustrative quotes describing clinicians’ preimplementation perspectives of the prediction tool.</title>
            <p>
              <bold>Acceptability</bold>
            </p>
            <p><bold>Insights:</bold> Expectations that the prediction tool would bring new and more groundbreaking insights; overall usefulness of the prediction tool is “nice to have;” clear purpose is decisive for acceptability; intension of use is tied to the prediction tool’s task-technology fit; harmonizing individual treatment; and avoiding being influenced by recent experiences and reducing individual bias.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 1:</bold><italic> […] it confirms the assessment you make, and that's fine, but it's not something groundbreaking, and that's okay too.</italic> [Interview, Electrophysiologist #5]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 2:</bold><italic> […] I'm a little disappointed with the alarm, because for the cases I have looked at, the alarm has not given me much. […] if you had some cases with some ‘meat’ on such as a couple of treatment requiring VTs, I actually do think that getting a number, a risk score, will enable to better estimating the problem. I think that can be valuable […] I just think the cases were wrong. If you want to show that this algorithm gives value and then bring 2 cases with AF problems, which the algorithm does not handle, then that’s not optimal.</italic> [Interview, Electrophysiologist #2]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 3:</bold><italic> It's always nice when something is supportive, I would say, but isn't it a “nice to have” and not a “need to have”?</italic> [Interview, Electrophysiologist #4]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 4:</bold><italic> 20 years of experience or not. Perhaps, the advantage of the algorithm is that it is not influenced by what the individual clinician has experienced within the last month, and in this way helping to make more uniform conclusions.</italic> [Interview, Electrophysiologist #5]</p>
              </list-item>
            </list>
            <p>
              <bold>Adoption</bold>
            </p>
            <p><bold>Insights:</bold> High precision is important; false positives hinder adoption; using the prediction tool and getting confirmation in real life creates trust and enables adoption; the clinical team needs to decide on use; a randomized clinical trial is a precondition for acceptability; and algorithm validation supports trust.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 5:</bold><italic> If you want to come out with this, it must be something with a positive predictive value that is really good, so that you don’t get a lot of nonsense that you can’t use. The alarm should only be raised when there really is something.</italic> [Interview, Electrophysiologist #3]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 6:</bold><italic> It needs to be easily accessible and we [team of electrophysiologists] have to agree that we trust it [the prediction tool]. We just have to say that yes it looks right. For example, the Optivol alarm had too many false positives, which gave a lot of extra work and everything, and we actually chose not to use it because there were too many sources of error, and you only really discover that when you work with it [new algorithms].</italic> [Interview, Electrophysiologist #1]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 7:</bold><italic> I would say that it [prediction tool] would be an instrument that would have to be accepted in our group and then you would find it valuable when we all agree to take the red alarms first, and in that way use it to prioritize a bit.</italic> [Interview, Electrophysiologist #5]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 8:</bold><italic> I just think I should see that it confirms our decisions in enough cases - then I would feel comfortable about colleagues leaning on it […] There is something about trying it out, you know how it is.</italic> [Interview, Electrophysiologist #4]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 9:</bold><italic> Published studies of the algorithm would increase confidence yes, because then you know that someone with an understanding of making these models have said that it looks okay; someone externally who have validated it.</italic> [Electrophysiologist #1]</p>
              </list-item>
            </list>
            <p>
              <bold>Demand</bold>
            </p>
            <p><bold>Insights:</bold> Supporting better workflows; demand for prioritization and identification of important patient cases; increasing demand for screening tools in nonspecialist hospitals; demand for decreasing electrophysiologist’s information search time; supporting nurses and technicians to do prioritization work; and “data help” that enables junior doctors to get senior help.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 10:</bold><italic> When transmissions come in, it’s almost an unsorted list of transmissions […] The list is unprocessed, so with the algorithm it takes it a step further by nuancing what comes into CareLink [Medtronic’s remote monitoring dashboard] with some semi-quantitative markings. And, if it is reliable, then it would be valuable. Partly because you don’t overlook anything, and partly because you are confirmed that we must take these patients first, because we have experience that there can be trouble here.</italic> [Interview, Electrophysiologist #5]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 11:</bold><italic> You could say that in this way, the young doctor can do without getting senior help by actually getting data help.</italic> [Interview, Electrophysiologist #2]</p>
              </list-item>
            </list>
            <p> </p>
            <p>
              <bold>Implementation</bold>
            </p>
            <p><bold>Insights:</bold> Demand for adjusting the threshold to local prioritization rules; clinics need to be able to configure the cutoff and threshold; making the prediction tool easily accessible and integrated in the list of transmissions supports the workflow; intention of use is dependent on easy access; and it is practical that the algorithm uses data that are already familiar to the clinicians.</p>
            <list list-type="bullet">
              <list-item>
                <p><bold>Quote 12:</bold><italic> Electrophysiologists don’t bother to hear about it if it is below a certain percentage […]. We have adopted some rules, e.g. if you have a patient and she has got a shock, and gets rare therapies and it goes over, then we don’t need to hear about it because we think there is not a big risk. You might well imagine that introducing this alarm will support handling low-risk transmissions.</italic> [Interview, Electrophysiologist #3]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 13:</bold><italic> If it’s easily presented and you don’t have to go in and look through 4 pages and such and if it was on the front page and brought up “number of episodes” and information like that - if you could easily retrieve the information [from the prediction tool] or if it was printed on the list of transmissions we are working on, then it would also be a great help.</italic> [Interview, Electrophysiologist #1]</p>
              </list-item>
              <list-item>
                <p><bold>Quote 14:</bold><italic> What one would emphasize, is that the algorithm uses the same data that the clinician uses i.e. it’s the same data, just integrated according to a formula that clinicians do not currently have available.</italic> [Interview, Electrophysiologist #5]</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Tackling the Sociotechnical Challenges of ML-Based Tools in Health Care</title>
        <p>In bridging the sociotechnical gap between the development of ML-based tools and clinical implementation, this study explored the feasibility and clinical perspectives of using a prediction tool for improved workflows in ICD remote monitoring. We found that the feasibility of the ML-based tool is promising when the intended use of the tool is aligned with expectations, that is, by providing support for decision-making, visualizing useful information, and reducing time spent. The results also show that an actionable prediction tool is one that presents the reason for why the algorithm deemed as it did, such as in this study, by highlighting important data to be used for clinical evaluation and enabling clinicians to assess the algorithm’s outcome against their own evaluation [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref33">33</xref>].</p>
        <p>However, the current prediction tool did not lead to change in clinical action, suggesting that ML and explainability techniques do not outperform specialized and experienced electrophysiologist evaluations, but at best confirm and support the interpretation of complex ICD device information along with a promise for a less time-consuming clinical workflow.</p>
        <p>The contribution of this paper lies in the implications of the qualitative results suggesting that clinical end-users, clinical contexts, and workflows must be included throughout an overall iterative approach to design, development, and implementation. In the following sections, we will discuss the qualitative results concerning the sociotechnical challenges and implementation of ML-based tools for clinical decision support.</p>
      </sec>
      <sec>
        <title>Expectations Need to Align With the Intended Use of AI</title>
        <p>In cases where misalignment emerged between the electrophysiologists’ expectations and intended use, the prediction tool was considered less useful and at best “nice to have” for clinical decision-making. For example, in cases where the ICD transmissions revolved around other types of arrhythmias than what the prediction tool was designed for and in cases where the electrophysiologists expected that the prediction tool should be capable of outperforming their own evaluation, disappointment was raised about the performance of the underlying AI algorithm. This aligns with recent studies that reported on physicians’ high expectations and attitudes toward medical AI [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]. The challenge of managing expectations has been addressed by a growing number of studies aimed at providing an explanation of algorithmic decisions at the time of inference [<xref ref-type="bibr" rid="ref36">36</xref>] and by developing user interfaces with expectation adjustment techniques [<xref ref-type="bibr" rid="ref66">66</xref>]. Recently, researchers focused on the early human-AI onboarding process of pathologists and found that presenting a global view of a prediction tool and its capabilities, limitations, and biases is key to the formation of initial impressions and appropriate mental models [<xref ref-type="bibr" rid="ref67">67</xref>]. This suggests that the development of so-called explainability in the user interface is important, but communicating the intended use of the prediction tool is imperative for acceptance in the clinic. To achieve alignment of expectations, training programs for clinicians are critical when implementing medical AI tools.</p>
      </sec>
      <sec>
        <title>Trust Emerges From Real-World Use</title>
        <p>Trust is another key factor for user acceptance and adoption of AI technologies. Trust is typically considered an issue in creating transparent and understandable algorithmic behavior, as opposed to seeing the prediction tool as a black box [<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. Extensive research on explainable AI and various approaches to achieve transparency have been suggested [<xref ref-type="bibr" rid="ref11">11</xref>], yet experimental studies on whether these approaches achieve their intended effects in the real world are only just starting to emerge [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref70">70</xref>]. In this study, the electrophysiologists requested large-scale algorithm validation and prospective evaluations from clinical trials. However, an important observation was that trust in the prediction tool may only emerge from continuous use of the tool and from experiencing confirmation on individual evaluations in collaboration with the tool. There was general agreement among the electrophysiologists that visualization of the most important predictive parameters helped raise confidence and trust over time, and that adoption of the prediction tool would hinge on the collective decision among the team of electrophysiologists. Recent experimental studies have reported similar findings [<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref71">71</xref>] and have demonstrated that adding an AI prediction tool to the clinical evaluation can increase clinician confidence [<xref ref-type="bibr" rid="ref24">24</xref>]. The implication of understanding trust as emerging from real-world use is that when deploying medical AI in clinical settings, trust needs to be built bottom-up through weeks or months of trialing the new tool for clinicians to experience convincing reassurance. Therefore, initial implementation processes may benefit from simultaneous calibration and adaption of the tool to establish a human-AI partnership, and allowing the local team of clinicians to decide collectively how they choose to trust and use the tool in the clinic.</p>
      </sec>
      <sec>
        <title>Accuracy is Dependent on Workflow and Context</title>
        <p>While AI algorithms have been validated and have been shown to have similar or higher accuracy than humans, recent studies of AI deployment in clinical settings report that professional autonomy, workflow, and local sociotechnical factors have impacts on how accuracy is perceived and used in clinical practice [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref45">45</xref>-<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref50">50</xref>-<xref ref-type="bibr" rid="ref54">54</xref>]. Bruun et al [<xref ref-type="bibr" rid="ref24">24</xref>] found that overall performance was positively impacted among clinicians using an AI-prediction tool for assessing progression in early stage dementia and that clinicians’ professional autonomy impacts the use of medical AI in situated clinical practice. Additionally, the study by Beede et al [<xref ref-type="bibr" rid="ref29">29</xref>] of a ML-based (deep learning) system used in clinics for the detection of diabetic eye disease indicated that several socioenvironmental factors, such as busy screening procedures, poor lighting conditions, and consideration of patient burden, have impacts on how AI accuracy is perceived in clinical screening practices. Similarly, we found that high accuracy becomes relative to the electrophysiologist’s evaluation of available information, the local circumstances, and the consequences that AI predictions have for taking action. For example, several electrophysiologists argued that AI prediction needs to be considered against patient-reported symptoms and that a full patient schedule may affect how the AI prediction is acted upon in practice. Moreover, in several cases, the electrophysiologists found the visualization of important parameters more useful than the prediction score itself. This indicates that AI accuracy needs to be understood as relational and dependent on available information and local workflows, which supports the vision of establishing a human-AI symbiosis that combines the predictive abilities of both the clinician and the AI prediction algorithm [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. Finally, the wish for better visualization of data parameters over prediction accuracy indicates that the development of medical AI assistants needs to be carried out as close as possible to implementation in clinical practice with clinical end-users through iterative approaches [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref72">72</xref>] that can bridge the “AI chasm” [<xref ref-type="bibr" rid="ref41">41</xref>] of scientifically sound algorithms and their use in meaningful real-world clinical applications.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The findings in this study are limited to the small number of study participants and patient cases. One electrophysiologist (PKJ) participated in co-design workshops, resulting in potential positive bias. Patient cases were selected to represent diversity in prediction capabilities, rather than the distribution in clinical practice, which may weaken the generalizability of the results. Only cases where the prediction tool provided true-positive and true-negative prediction outcomes were used, which means that the clinical feasibility of ML in cases with false-positive and false-negative outcomes [<xref ref-type="bibr" rid="ref73">73</xref>] have not been explored. Future studies are needed to assess the implications of false prediction outcomes, as well as conduct algorithmic validation similar to recent related studies [<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref21">21</xref>]. Limitations also involve data availability, that is, the data set used may entail algorithmic bias [<xref ref-type="bibr" rid="ref13">13</xref>] and the study participants may have been more positive toward innovative AI technology since all of the study participants were from a tertiary university hospital and constituted a rather homogenous group of highly specialized physicians. The AI studied has limitations, because only the random forest ML-based algorithm was evaluated with electrophysiologists. These types of methods are commonly used in medical applications [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref75">75</xref>] because of their high classification accuracy and capabilities for handling data with imbalanced classes [<xref ref-type="bibr" rid="ref50">50</xref>] while providing easily accessible, if limited, global intelligibility through the visualization and ranking of parameter importance [<xref ref-type="bibr" rid="ref55">55</xref>]. This work will benefit from being validated in a large-scale multicenter study with higher diversity in participating electrophysiologists and workflows. It will be imperative to conduct prospective clinical trials evaluating the algorithm against standard care with regard to workload, cost-effectiveness, and hard clinical endpoints.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study shows that a tool based on ML for the prediction of VT/VF in remote monitoring of ICD patients has the potential to support electrophysiologists’ decision-making. While the prediction tool was regarded as “nice to have” rather than “need to have” in its current form, the tool demonstrated potential for supporting clinical decision-making, as it provided reassurance, increased confidence, and indicated the potential for reducing information search time, as well as enabled delegation of decisions to nurses and technicians. The findings also indicate that trust in the prediction tool, acceptable data quality, and clearly defined intended use are decisive for end-user acceptance and that adoption hinges on successful clinical implementation. This suggests that clinical end-users’ sociotechnical contexts and workflows need to be taken into consideration early on and continuously throughout a participatory design process to address the sociotechnical gap between the development and implementation of medical AI in cardiac care.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Questionnaire used before the electrophysiologists are presented with the prediction tool results.</p>
        <media xlink:href="humanfactors_v8i4e26964_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 79 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Questionnaire after the electrophysiologists have received the prediction tool results.</p>
        <media xlink:href="humanfactors_v8i4e26964_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 103 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>The semistructured interview guide.</p>
        <media xlink:href="humanfactors_v8i4e26964_app3.pdf" xlink:title="PDF File  (Adobe PDF File), 53 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">ICD</term>
          <def>
            <p>implantable cardioverter defibrillator</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">LSTM</term>
          <def>
            <p>long short-term memory</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">ML</term>
          <def>
            <p>machine learning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">VF</term>
          <def>
            <p>ventricular fibrillation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">VT</term>
          <def>
            <p>ventricular tachycardia</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>We wish to thank the participating electrophysiologists at the Department of Cardiology, Rigshospitalet, Copenhagen University Hospital, Copenhagen, Denmark. The research and technology developed (working title: SafeHeart) were supported by the European Data Pitch Innovation Program H2020–732506 and led by TOA.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>TOA is a co-founder of Vital Beats, which has commercial interests in the technology under investigation. MKHH and CV were full-time employees of Vital Beats. JHS, SZD, MCHL, and SM are affiliated with Vital Beats as advisors or independent researchers. The authors have no other conflicts of interest to disclose.</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>Al-Khatib</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Stevenson</surname>
              <given-names>WG</given-names>
            </name>
            <name name-style="western">
              <surname>Ackerman</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bryant</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Callans</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Deal</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Dickfeld</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Field</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Fonarow</surname>
              <given-names>GC</given-names>
            </name>
            <name name-style="western">
              <surname>Gillis</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Granger</surname>
              <given-names>CB</given-names>
            </name>
            <name name-style="western">
              <surname>Hammill</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Hlatky</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Joglar</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Kay</surname>
              <given-names>GN</given-names>
            </name>
            <name name-style="western">
              <surname>Matlock</surname>
              <given-names>DD</given-names>
            </name>
            <name name-style="western">
              <surname>Myerburg</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Page</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>2017 AHA/ACC/HRS Guideline for Management of Patients With Ventricular Arrhythmias and the Prevention of Sudden Cardiac Death: A Report of the American College of Cardiology/American Heart Association Task Force on Clinical Practice Guidelines and the Heart Rhythm Society</article-title>
          <source>J Am Coll Cardiol</source>
          <year>2018</year>
          <month>10</month>
          <day>02</day>
          <volume>72</volume>
          <issue>14</issue>
          <fpage>e91</fpage>
          <lpage>e220</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0735-1097(17)41306-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jacc.2017.10.054</pub-id>
          <pub-id pub-id-type="medline">29097296</pub-id>
          <pub-id pub-id-type="pii">S0735-1097(17)41306-4</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>Nanthakumar</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Kay</surname>
              <given-names>GN</given-names>
            </name>
            <name name-style="western">
              <surname>Plumb</surname>
              <given-names>VJ</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Prophylactic implantable cardioverter-defibrillator therapy in patients with left ventricular systolic dysfunction: a pooled analysis of 10 primary prevention trials</article-title>
          <source>J Am Coll Cardiol</source>
          <year>2004</year>
          <month>12</month>
          <day>07</day>
          <volume>44</volume>
          <issue>11</issue>
          <fpage>2166</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0735-1097(04)01744-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jacc.2004.08.054</pub-id>
          <pub-id pub-id-type="medline">15582314</pub-id>
          <pub-id pub-id-type="pii">S0735-1097(04)01744-9</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>Varma</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ricci</surname>
              <given-names>RP</given-names>
            </name>
          </person-group>
          <article-title>Telemedicine and cardiac implants: what is the benefit?</article-title>
          <source>Eur Heart J</source>
          <year>2013</year>
          <month>07</month>
          <day>04</day>
          <volume>34</volume>
          <issue>25</issue>
          <fpage>1885</fpage>
          <lpage>95</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23211231"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/eurheartj/ehs388</pub-id>
          <pub-id pub-id-type="medline">23211231</pub-id>
          <pub-id pub-id-type="pii">ehs388</pub-id>
          <pub-id pub-id-type="pmcid">PMC4051258</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>Mabo</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Victor</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bazin</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ahres</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Babuty</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Da Costa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Binet</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Daubert</surname>
              <given-names>J</given-names>
            </name>
            <collab>COMPAS Trial Investigators</collab>
          </person-group>
          <article-title>A randomized trial of long-term remote monitoring of pacemaker recipients (the COMPAS trial)</article-title>
          <source>Eur Heart J</source>
          <year>2012</year>
          <month>05</month>
          <volume>33</volume>
          <issue>9</issue>
          <fpage>1105</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22127418"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/eurheartj/ehr419</pub-id>
          <pub-id pub-id-type="medline">22127418</pub-id>
          <pub-id pub-id-type="pii">ehr419</pub-id>
          <pub-id pub-id-type="pmcid">PMC3341630</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>Landolina</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Perego</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Lunati</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Curnis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Guenzati</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Vicentini</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Parati</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Borghi</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Zanaboni</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Valsecchi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marzegalli</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Remote monitoring reduces healthcare use and improves quality of care in heart failure patients with implantable defibrillators: the evolution of management strategies of heart failure patients with implantable defibrillators (EVOLVO) study</article-title>
          <source>Circulation</source>
          <year>2012</year>
          <month>06</month>
          <day>19</day>
          <volume>125</volume>
          <issue>24</issue>
          <fpage>2985</fpage>
          <lpage>92</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ahajournals.org/doi/full/10.1161/circulationaha.111.088971"/>
          </comment>
          <pub-id pub-id-type="doi">10.1161/CIRCULATIONAHA.111.088971</pub-id>
          <pub-id pub-id-type="medline">22626743</pub-id>
          <pub-id pub-id-type="pii">CIRCULATIONAHA.111.088971</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>Saxon</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Hayes</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Gilliam</surname>
              <given-names>FR</given-names>
            </name>
            <name name-style="western">
              <surname>Heidenreich</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Seth</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>TE</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Boehmer</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <article-title>Long-term outcome after ICD and CRT implantation and influence of remote device follow-up: the ALTITUDE survival study</article-title>
          <source>Circulation</source>
          <year>2010</year>
          <month>12</month>
          <day>07</day>
          <volume>122</volume>
          <issue>23</issue>
          <fpage>2359</fpage>
          <lpage>67</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ahajournals.org/doi/10.1161/circulationaha.110.960633"/>
          </comment>
          <pub-id pub-id-type="doi">10.1161/CIRCULATIONAHA.110.960633</pub-id>
          <pub-id pub-id-type="medline">21098452</pub-id>
          <pub-id pub-id-type="pii">CIRCULATIONAHA.110.960633</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>Crossley</surname>
              <given-names>GH</given-names>
            </name>
            <name name-style="western">
              <surname>Boyle</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vitense</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mead</surname>
              <given-names>RH</given-names>
            </name>
            <collab>CONNECT Investigators</collab>
          </person-group>
          <article-title>The CONNECT (Clinical Evaluation of Remote Notification to Reduce Time to Clinical Decision) trial: the value of wireless remote monitoring with automatic clinician alerts</article-title>
          <source>J Am Coll Cardiol</source>
          <year>2011</year>
          <month>03</month>
          <day>08</day>
          <volume>57</volume>
          <issue>10</issue>
          <fpage>1181</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0735-1097(10)05068-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jacc.2010.12.012</pub-id>
          <pub-id pub-id-type="medline">21255955</pub-id>
          <pub-id pub-id-type="pii">S0735-1097(10)05068-0</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>Cronin</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Ching</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Varma</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>DO</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkoff</surname>
              <given-names>BL</given-names>
            </name>
            <name name-style="western">
              <surname>Lindsay</surname>
              <given-names>BD</given-names>
            </name>
          </person-group>
          <article-title>Remote monitoring of cardiovascular devices: a time and activity analysis</article-title>
          <source>Heart Rhythm</source>
          <year>2012</year>
          <month>12</month>
          <volume>9</volume>
          <issue>12</issue>
          <fpage>1947</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S1547527112008600"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.hrthm.2012.08.002</pub-id>
          <pub-id pub-id-type="medline">22864266</pub-id>
          <pub-id pub-id-type="pii">S1547-5271(12)00860-0</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>Ricci</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Morichelli</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>D'Onofrio</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Calò</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Vaccari</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zanotto</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Curnis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Buja</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rovai</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gargaro</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Manpower and outpatient clinic workload for remote monitoring of patients with cardiac implantable electronic devices: data from the HomeGuide Registry</article-title>
          <source>J Cardiovasc Electrophysiol</source>
          <year>2014</year>
          <month>11</month>
          <day>28</day>
          <volume>25</volume>
          <issue>11</issue>
          <fpage>1216</fpage>
          <lpage>23</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1111/jce.12482"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/jce.12482</pub-id>
          <pub-id pub-id-type="medline">24964380</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>Andersen</surname>
              <given-names>TO</given-names>
            </name>
            <name name-style="western">
              <surname>Nielsen</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Moll</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Svendsen</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Unpacking telemonitoring work: Workload and telephone calls to patients in implanted cardiac device care</article-title>
          <source>Int J Med Inform</source>
          <year>2019</year>
          <month>09</month>
          <volume>129</volume>
          <fpage>381</fpage>
          <lpage>387</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(18)31415-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.06.021</pub-id>
          <pub-id pub-id-type="medline">31445281</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(18)31415-1</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>Gustafson,</surname>
              <given-names>PE</given-names>
            </name>
          </person-group>
          <article-title>Implementing Remote Monitoring of Cardiac Implantable Electronic Devices: The Clinical Experience from One Center in Sweden</article-title>
          <source>The Journal of Innovations in Cardiac Rhythm Management</source>
          <year>2014</year>
          <volume>5</volume>
          <fpage>1733</fpage>
          <lpage>1739</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.innovationsincrm.com/images/pdf/crm-05-08-1733.pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.19102/icrm.2014.050808</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>Patel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sengupta</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Machine learning for predicting cardiac events: what does the future hold?</article-title>
          <source>Expert Rev Cardiovasc Ther</source>
          <year>2020</year>
          <month>02</month>
          <day>23</day>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>84</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32066289"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/14779072.2020.1732208</pub-id>
          <pub-id pub-id-type="medline">32066289</pub-id>
          <pub-id pub-id-type="pmcid">PMC7962010</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>Crowley</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>YJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ioannidis</surname>
              <given-names>JPA</given-names>
            </name>
          </person-group>
          <article-title>Empirical assessment of bias in machine learning diagnostic test accuracy studies</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>07</month>
          <day>01</day>
          <volume>27</volume>
          <issue>7</issue>
          <fpage>1092</fpage>
          <lpage>1101</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32548642"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa075</pub-id>
          <pub-id pub-id-type="medline">32548642</pub-id>
          <pub-id pub-id-type="pii">5858298</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647361</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>Lagu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Pekow</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Shieh</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stefan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pack</surname>
              <given-names>QR</given-names>
            </name>
            <name name-style="western">
              <surname>Kashef</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Atreya</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Valania</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Slawsky</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Lindenauer</surname>
              <given-names>PK</given-names>
            </name>
          </person-group>
          <article-title>Validation and Comparison of Seven Mortality Prediction Models for Hospitalized Patients With Acute Decompensated Heart Failure</article-title>
          <source>Circ: Heart Failure</source>
          <year>2016</year>
          <month>08</month>
          <volume>9</volume>
          <issue>8</issue>
          <fpage>e002912</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ahajournals.org/doi/full/10.1161/CIRCHEARTFAILURE.115.002912"/>
          </comment>
          <pub-id pub-id-type="doi">10.1161/circheartfailure.115.002912</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>Pan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Tao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Enhanced Deep Learning Assisted Convolutional Neural Network for Heart Disease Prediction on the Internet of Medical Things Platform</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <volume>8</volume>
          <fpage>189503</fpage>
          <lpage>189512</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9204704"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/access.2020.3026214</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>Eltrass</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Tayel</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Ammar</surname>
              <given-names>AI</given-names>
            </name>
          </person-group>
          <article-title>A new automated CNN deep learning approach for identification of ECG congestive heart failure and arrhythmia using constant-Q non-stationary Gabor transform</article-title>
          <source>Biomedical Signal Processing and Control</source>
          <year>2021</year>
          <month>03</month>
          <volume>65</volume>
          <fpage>102326</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S1746809420304420?via%3Dihub"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.bspc.2020.102326</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>Hammad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Iliyasu</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Subasi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ho</surname>
              <given-names>ESL</given-names>
            </name>
            <name name-style="western">
              <surname>El-Latif</surname>
              <given-names>AAA</given-names>
            </name>
          </person-group>
          <article-title>A Multitier Deep Learning Model for Arrhythmia Detection</article-title>
          <source>IEEE Trans. Instrum. Meas</source>
          <year>2021</year>
          <volume>70</volume>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/9239355"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/tim.2020.3033072</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shouval</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hadanny</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shlomo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Iakobishvili</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Unger</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zahger</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Alcalai</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Atar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gottlieb</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Matetzky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Goldenberg</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Beigel</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Machine learning for prediction of 30-day mortality after ST elevation myocardial infraction: An Acute Coronary Syndrome Israeli Survey data mining study</article-title>
          <source>Int J Cardiol</source>
          <year>2017</year>
          <month>11</month>
          <day>01</day>
          <volume>246</volume>
          <fpage>7</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S0167527316328698?casa_token=m8QlIvJJYBUAAAAA:_dUvlS1ONCrNpfItg8xGBld9C7qcsOViDJnmtiEqYXVwG5ueTcY3-ycMZW-R-ubbd-43-Bxu-TUC"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijcard.2017.05.067</pub-id>
          <pub-id pub-id-type="medline">28867023</pub-id>
          <pub-id pub-id-type="pii">S0167-5273(16)32869-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karnan</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Natarajan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Manivel</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Human machine interfacing technique for diagnosis of ventricular arrhythmia using supervisory machine learning algorithms</article-title>
          <source>Concurrency Computat Pract Exper</source>
          <year>2018</year>
          <month>10</month>
          <day>19</day>
          <volume>33</volume>
          <issue>4</issue>
          <fpage>e5001</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/abs/10.1002/cpe.5001"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/cpe.5001</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>Attia</surname>
              <given-names>ZI</given-names>
            </name>
            <name name-style="western">
              <surname>Noseworthy</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez-Jimenez</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Asirvatham</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Deshmukh</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gersh</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Carter</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Rabinstein</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Erickson</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kapa</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Friedman</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>An artificial intelligence-enabled ECG algorithm for the identification of patients with atrial fibrillation during sinus rhythm: a retrospective analysis of outcome prediction</article-title>
          <source>The Lancet</source>
          <year>2019</year>
          <month>09</month>
          <day>07</day>
          <volume>394</volume>
          <issue>10201</issue>
          <fpage>861</fpage>
          <lpage>867</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(19)31721-0/fulltext"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(19)31721-0</pub-id>
          <pub-id pub-id-type="medline">31378392</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(19)31721-0</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>Shakibfar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Krause</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Lund-Andersen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Aranda</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Moll</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>TO</given-names>
            </name>
            <name name-style="western">
              <surname>Svendsen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>HH</given-names>
            </name>
            <name name-style="western">
              <surname>Igel</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Predicting electrical storms by remote monitoring of implantable cardioverter-defibrillator patients using machine learning</article-title>
          <source>Europace</source>
          <year>2019</year>
          <month>02</month>
          <day>01</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>268</fpage>
          <lpage>274</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/europace/article/21/2/268/5224771"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/europace/euy257</pub-id>
          <pub-id pub-id-type="medline">30508072</pub-id>
          <pub-id pub-id-type="pii">5224771</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kwon</surname>
              <given-names>SH</given-names>
            </name>
          </person-group>
          <article-title>Physician Confidence in Artificial Intelligence: An Online Mobile Survey</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>03</month>
          <day>25</day>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>e12422</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/3/e12422/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12422</pub-id>
          <pub-id pub-id-type="medline">30907742</pub-id>
          <pub-id pub-id-type="pii">v21i3e12422</pub-id>
          <pub-id pub-id-type="pmcid">PMC6452288</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maassen</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Fritsch</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Palm</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Deffge</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kunze</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Marx</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Riedel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schuppert</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bickenbach</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Future Medical Artificial Intelligence Application Requirements and Expectations of Physicians in German University Hospitals: Web-Based Survey</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>03</month>
          <day>05</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>e26646</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/3/e26646/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/26646</pub-id>
          <pub-id pub-id-type="medline">33666563</pub-id>
          <pub-id pub-id-type="pii">v23i3e26646</pub-id>
          <pub-id pub-id-type="pmcid">PMC7980122</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bruun</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Frederiksen</surname>
              <given-names>KS</given-names>
            </name>
            <name name-style="western">
              <surname>Rhodius-Meester</surname>
              <given-names>HFM</given-names>
            </name>
            <name name-style="western">
              <surname>Baroni</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gjerum</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Koikkalainen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Urhemaa</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tolonen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>van Gils</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rueckert</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dyremose</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>BB</given-names>
            </name>
            <name name-style="western">
              <surname>Lemstra</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Hallikainen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kurl</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Herukka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Remes</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Waldemar</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Soininen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mecocci</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>van der Flier</surname>
              <given-names>WM</given-names>
            </name>
            <name name-style="western">
              <surname>Lötjönen</surname>
              <given-names>Jyrki</given-names>
            </name>
            <name name-style="western">
              <surname>Hasselbalch</surname>
              <given-names>SG</given-names>
            </name>
          </person-group>
          <article-title>Impact of a clinical decision support tool on prediction of progression in early-stage dementia: a prospective validation study</article-title>
          <source>Alzheimers Res Ther</source>
          <year>2019</year>
          <month>03</month>
          <day>20</day>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>25</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://alzres.biomedcentral.com/articles/10.1186/s13195-019-0482-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13195-019-0482-3</pub-id>
          <pub-id pub-id-type="medline">30894218</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13195-019-0482-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC6425602</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Manz</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chivers</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Regli</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Changolkar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>CN</given-names>
            </name>
            <name name-style="western">
              <surname>Rareshide</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Draugelis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Navathe</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bekelman</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>O'Connor</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schuchter</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Shulman</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>Parikh</surname>
              <given-names>RB</given-names>
            </name>
          </person-group>
          <article-title>Prospective validation of a machine learning algorithm to predict short-term mortality among outpatients with cancer</article-title>
          <source>JCO</source>
          <year>2020</year>
          <month>05</month>
          <day>20</day>
          <volume>38</volume>
          <issue>15_suppl</issue>
          <fpage>2009</fpage>
          <lpage>2009</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ascopubs.org/doi/abs/10.1200/JCO.2020.38.15_suppl.2009"/>
          </comment>
          <pub-id pub-id-type="doi">10.1200/jco.2020.38.15_suppl.2009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abràmoff</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Lavin</surname>
              <given-names>PT</given-names>
            </name>
            <name name-style="western">
              <surname>Birch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Folk</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Pivotal trial of an autonomous AI-based diagnostic system for detection of diabetic retinopathy in primary care offices</article-title>
          <source>NPJ Digit Med</source>
          <year>2018</year>
          <volume>1</volume>
          <fpage>39</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-018-0040-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-018-0040-6</pub-id>
          <pub-id pub-id-type="medline">31304320</pub-id>
          <pub-id pub-id-type="pii">40</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550188</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gulshan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Coram</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stumpe</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Narayanaswamy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Venugopalan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Widner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Madams</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Cuadros</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Raman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Mega</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Webster</surname>
              <given-names>DR</given-names>
            </name>
          </person-group>
          <article-title>Development and Validation of a Deep Learning Algorithm for Detection of Diabetic Retinopathy in Retinal Fundus Photographs</article-title>
          <source>JAMA</source>
          <year>2016</year>
          <month>12</month>
          <day>13</day>
          <volume>316</volume>
          <issue>22</issue>
          <fpage>2402</fpage>
          <lpage>2410</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jama/fullarticle/2588763"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jama.2016.17216</pub-id>
          <pub-id pub-id-type="medline">27898976</pub-id>
          <pub-id pub-id-type="pii">2588763</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Morin</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Closing the Gap Between Machine Learning and Clinical Cancer Care-First Steps Into a Larger World</article-title>
          <source>JAMA Oncol</source>
          <year>2020</year>
          <month>11</month>
          <day>01</day>
          <volume>6</volume>
          <issue>11</issue>
          <fpage>1731</fpage>
          <lpage>1732</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamaoncology/article-abstract/2770694"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamaoncol.2020.4314</pub-id>
          <pub-id pub-id-type="medline">32970129</pub-id>
          <pub-id pub-id-type="pii">2770694</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beede</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Baylor</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Hersch</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Iurchenko</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ruamviboonsuk</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Vardoulakis</surname>
              <given-names>LM</given-names>
            </name>
          </person-group>
          <article-title>A Human-Centered Evaluation of a Deep Learning System Deployed in Clinics for the Detection of Diabetic Retinopathy</article-title>
          <source>CHI '20: Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems</source>
          <year>2020</year>
          <conf-name>2020 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>April 25-30, 2020</conf-date>
          <conf-loc>Honolulu, HI</conf-loc>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1145/3313831.3376718</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Asch</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Machine Learning and Prediction in Medicine - Beyond the Peak of Inflated Expectations</article-title>
          <source>N Engl J Med</source>
          <year>2017</year>
          <month>06</month>
          <day>29</day>
          <volume>376</volume>
          <issue>26</issue>
          <fpage>2507</fpage>
          <lpage>2509</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28657867"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/NEJMp1702071</pub-id>
          <pub-id pub-id-type="medline">28657867</pub-id>
          <pub-id pub-id-type="pmcid">PMC5953825</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lindsell</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Stead</surname>
              <given-names>WW</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>KB</given-names>
            </name>
          </person-group>
          <article-title>Action-Informed Artificial Intelligence-Matching the Algorithm to the Problem</article-title>
          <source>JAMA</source>
          <year>2020</year>
          <month>06</month>
          <day>02</day>
          <volume>323</volume>
          <issue>21</issue>
          <fpage>2141</fpage>
          <lpage>2142</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2020.5035</pub-id>
          <pub-id pub-id-type="medline">32356878</pub-id>
          <pub-id pub-id-type="pii">2765667</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>High-performance medicine: the convergence of human and artificial intelligence</article-title>
          <source>Nat Med</source>
          <year>2019</year>
          <month>01</month>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>44</fpage>
          <lpage>56</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nature.com/articles/s41591-018-0300-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-018-0300-7</pub-id>
          <pub-id pub-id-type="medline">30617339</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-018-0300-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Is Artificial Intelligence Better Than Human Clinicians in Predicting Patient Outcomes?</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>08</month>
          <day>26</day>
          <volume>22</volume>
          <issue>8</issue>
          <fpage>e19918</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/8/e19918/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19918</pub-id>
          <pub-id pub-id-type="medline">32845249</pub-id>
          <pub-id pub-id-type="pii">v22i8e19918</pub-id>
          <pub-id pub-id-type="pmcid">PMC7481865</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cabitza</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Campagner</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Balsano</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Bridging the "last mile" gap between AI implementation and operation: "data awareness" that matters</article-title>
          <source>Ann Transl Med</source>
          <year>2020</year>
          <month>04</month>
          <volume>8</volume>
          <issue>7</issue>
          <fpage>501</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.21037/atm.2020.03.63"/>
          </comment>
          <pub-id pub-id-type="doi">10.21037/atm.2020.03.63</pub-id>
          <pub-id pub-id-type="medline">32395545</pub-id>
          <pub-id pub-id-type="pii">atm-08-07-501</pub-id>
          <pub-id pub-id-type="pmcid">PMC7210125</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The Last Mile: Where Artificial Intelligence Meets Reality</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>11</month>
          <day>08</day>
          <volume>21</volume>
          <issue>11</issue>
          <fpage>e16323</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/11/e16323/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/16323</pub-id>
          <pub-id pub-id-type="medline">31702559</pub-id>
          <pub-id pub-id-type="pii">v21i11e16323</pub-id>
          <pub-id pub-id-type="pmcid">PMC7351266</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdul</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vermeulen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>BY</given-names>
            </name>
            <name name-style="western">
              <surname>Kankanhalli</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Trends and Trajectories for Explainable, Accountable and Intelligible Systems: An HCI Research Agenda</article-title>
          <source>CHI '18: Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems</source>
          <year>2018</year>
          <conf-name>2018 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>April 21-26, 2018</conf-date>
          <conf-loc>Montreal, QC, Canada</conf-loc>
          <fpage>1</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1145/3173574.3174156</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wolf</surname>
              <given-names>CT</given-names>
            </name>
          </person-group>
          <article-title>Explainability scenarios: towards scenario-based XAI design</article-title>
          <source>IUI '19: Proceedings of the 24th International Conference on Intelligent User Interfaces</source>
          <year>2019</year>
          <conf-name>24th International Conference on Intelligent User Interfaces</conf-name>
          <conf-date>March 17-20, 2019</conf-date>
          <conf-loc>Marina del Ray, CA</conf-loc>
          <fpage>252</fpage>
          <lpage>257</lpage>
          <pub-id pub-id-type="doi">10.1145/3301275.3302317</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Explanation in artificial intelligence: Insights from the social sciences</article-title>
          <source>Artificial Intelligence</source>
          <year>2019</year>
          <month>02</month>
          <volume>267</volume>
          <fpage>1</fpage>
          <lpage>38</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S0004370218305988"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.artint.2018.07.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Poursabzi-Sangdeh</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Goldstein</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Hofman</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Vaughan</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Wallach</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Manipulating and Measuring Model Interpretability</article-title>
          <source>CHI '21: Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems</source>
          <year>2021</year>
          <conf-name>2021 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 8-13, 2021</conf-date>
          <conf-loc>Yokohama Japan</conf-loc>
          <fpage>1</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1145/3411764.3445315</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>EW</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in medicine: the challenges ahead</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>1996</year>
          <volume>3</volume>
          <issue>6</issue>
          <fpage>363</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/8930853"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.1996.97084510</pub-id>
          <pub-id pub-id-type="medline">8930853</pub-id>
          <pub-id pub-id-type="pmcid">PMC116321</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Keane</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>With an eye to AI and autonomous diagnosis</article-title>
          <source>NPJ Digit Med</source>
          <year>2018</year>
          <volume>1</volume>
          <fpage>40</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-018-0048-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-018-0048-y</pub-id>
          <pub-id pub-id-type="medline">31304321</pub-id>
          <pub-id pub-id-type="pii">48</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550235</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Quiroz</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Laranjo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kocaballi</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Berkovsky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rezazadegan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Challenges of developing a digital scribe to reduce clinical documentation burden</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <month>11</month>
          <day>22</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>114</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0190-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0190-1</pub-id>
          <pub-id pub-id-type="medline">31799422</pub-id>
          <pub-id pub-id-type="pii">190</pub-id>
          <pub-id pub-id-type="pmcid">PMC6874666</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kocaballi</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Ijaz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Laranjo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Quiroz</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Rezazadegan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Tong</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Willcock</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Berkovsky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Envisioning an artificial intelligence documentation assistant for future primary care consultations: A co-design study with general practitioners</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>11</month>
          <day>01</day>
          <volume>27</volume>
          <issue>11</issue>
          <fpage>1695</fpage>
          <lpage>1704</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32845984"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa131</pub-id>
          <pub-id pub-id-type="medline">32845984</pub-id>
          <pub-id pub-id-type="pii">5897463</pub-id>
          <pub-id pub-id-type="pmcid">PMC7671614</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petkovic</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vigil</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Improving the explainability of Random Forest classifier - user centered approach</article-title>
          <source>Pac Symp Biocomput</source>
          <year>2018</year>
          <volume>23</volume>
          <fpage>204</fpage>
          <lpage>215</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://psb.stanford.edu/psb-online/proceedings/psb18/abstracts/2018_p204.html"/>
          </comment>
          <pub-id pub-id-type="medline">29218882</pub-id>
          <pub-id pub-id-type="pii">9789813235533_0019</pub-id>
          <pub-id pub-id-type="pmcid">PMC5728671</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Benda</surname>
              <given-names>NC</given-names>
            </name>
            <name name-style="western">
              <surname>Das</surname>
              <given-names>LT</given-names>
            </name>
            <name name-style="western">
              <surname>Abramson</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Blackburn</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Thoman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kaushal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ancker</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>"How did you get to this number?" Stakeholder needs for implementing predictive analytics: a pre-implementation qualitative study</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <volume>27</volume>
          <issue>5</issue>
          <fpage>709</fpage>
          <lpage>716</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32159774"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa021</pub-id>
          <pub-id pub-id-type="medline">32159774</pub-id>
          <pub-id pub-id-type="pii">5803107</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647269</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sendak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Elish</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Futoma</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ratliff</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Nichols</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bedoya</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Balu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>"The human body is a black box": supporting clinical decision-making with deep learning</article-title>
          <source>FAT '20: Proceedings of the 2020 Conference on Fairness, Accountability, and Transparency</source>
          <year>2020</year>
          <conf-name>2020 Conference on Fairness, Accountability, and Transparency</conf-name>
          <conf-date>January 27-30, 2020</conf-date>
          <conf-loc>Barcelona, Spain</conf-loc>
          <fpage>99</fpage>
          <lpage>109</lpage>
          <pub-id pub-id-type="doi">10.1145/3351095.3372827</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Elish</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Watkins</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>Repairing Innovation: A Study of Integrating AI in Clinical Care</article-title>
          <source>Data Society</source>
          <year>2020</year>
          <access-date>2021-11-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://datasociety.net/wp-content/uploads/2020/09/Repairing-Innovation-DataSociety-20200930-1.pdf">https://datasociety.net/wp-content/uploads/2020/09/Repairing-Innovation-DataSociety-20200930-1.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>TO</given-names>
            </name>
            <name name-style="western">
              <surname>Nunes</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kaziunas</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Matthiesen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Magrabi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Realizing AI in Healthcare: Challenges Appearing in the Wild</article-title>
          <source>CHI EA '21: Extended Abstracts of the 2021 CHI Conference on Human Factors in Computing Systems</source>
          <year>2021</year>
          <conf-name>2021 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 8-13, 2021</conf-date>
          <conf-loc>Yokohama, Japan</conf-loc>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1145/3411763.3441347</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ginestra</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Giannini</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Schweickert</surname>
              <given-names>WD</given-names>
            </name>
            <name name-style="western">
              <surname>Meadows</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Pavan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chivers</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Draugelis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Donnelly</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Fuchs</surname>
              <given-names>BD</given-names>
            </name>
            <name name-style="western">
              <surname>Umscheid</surname>
              <given-names>CA</given-names>
            </name>
          </person-group>
          <article-title>Clinician Perception of a Machine Learning–Based Early Warning System Designed to Predict Severe Sepsis and Septic Shock*</article-title>
          <source>Critical Care Medicine</source>
          <year>2019</year>
          <volume>47</volume>
          <issue>11</issue>
          <fpage>1477</fpage>
          <lpage>1484</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1097/ccm.0000000000003803"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/ccm.0000000000003803</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Barda</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Horvat</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Hochheiser</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A qualitative research framework for the design of user-centered displays of explanations for machine learning model predictions in healthcare</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2020</year>
          <month>10</month>
          <day>08</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>257</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-020-01276-x"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-020-01276-x</pub-id>
          <pub-id pub-id-type="medline">33032582</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-020-01276-x</pub-id>
          <pub-id pub-id-type="pmcid">PMC7545557</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Romero-Brufau</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>Boyum</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mickelson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cognetta-Rieke</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A lesson in implementation: A pre-post study of providers' experience with artificial intelligence-based clinical decision support</article-title>
          <source>Int J Med Inform</source>
          <year>2020</year>
          <month>05</month>
          <volume>137</volume>
          <fpage>104072</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S1386505619310123"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2019.104072</pub-id>
          <pub-id pub-id-type="medline">32200295</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(19)31012-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sandhu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Brajer</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sperling</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ratliff</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Bedoya</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Balu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sendak</surname>
              <given-names>MP</given-names>
            </name>
          </person-group>
          <article-title>Integrating a Machine Learning System Into Clinical Workflows: Qualitative Study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>11</month>
          <day>19</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>e22421</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/11/e22421/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22421</pub-id>
          <pub-id pub-id-type="medline">33211015</pub-id>
          <pub-id pub-id-type="pii">v22i11e22421</pub-id>
          <pub-id pub-id-type="pmcid">PMC7714645</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Tian</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>“Brilliant AI Doctor” in Rural Clinics: Challenges in AI-Powered Clinical Decision Support System Deployment</article-title>
          <source>CHI '21: Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems</source>
          <year>2021</year>
          <conf-name>2021 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 8-13, 2021</conf-date>
          <conf-loc>Yokohama, Japan</conf-loc>
          <fpage>1</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1145/3411764.3445432</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Steinfeld</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zimmerman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Unremarkable AI: Fitting Intelligent Decision Support into Critical, Clinical Decision-Making Processes</article-title>
          <source>CHI '19: Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems</source>
          <year>2019</year>
          <conf-name>2019 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 4-9, 2019</conf-date>
          <conf-loc>Glasgow, Scotland</conf-loc>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.1145/3290605.3300468</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ribeiro</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Guestrin</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>"Why Should I Trust You?": Explaining the Predictions of Any Classifier</article-title>
          <source>KDD '16: Proceedings of the 22nd ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</source>
          <year>2016</year>
          <conf-name>22nd ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</conf-name>
          <conf-date>August 13-17, 2016</conf-date>
          <conf-loc>San Francisco, CA</conf-loc>
          <fpage>1135</fpage>
          <lpage>1144</lpage>
          <pub-id pub-id-type="doi">10.1145/2939672.2939778</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bjørn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kensing</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Moll</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Designing for collaborative interpretation in telemonitoring: re-introducing patients as diagnostic agents</article-title>
          <source>Int J Med Inform</source>
          <year>2011</year>
          <month>08</month>
          <volume>80</volume>
          <issue>8</issue>
          <fpage>e112</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S1386505610001711"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2010.09.010</pub-id>
          <pub-id pub-id-type="medline">21067968</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(10)00171-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>NS</given-names>
            </name>
          </person-group>
          <article-title>An Introduction to Kernel and Nearest-Neighbor Nonparametric Regression</article-title>
          <source>The American Statistician</source>
          <year>1992</year>
          <month>08</month>
          <volume>46</volume>
          <issue>3</issue>
          <fpage>175</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.2307/2685209"/>
          </comment>
          <pub-id pub-id-type="doi">10.2307/2685209</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Friedman</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Greedy function approximation: A gradient boosting machine</article-title>
          <source>Ann. Statist</source>
          <year>2001</year>
          <month>10</month>
          <day>1</day>
          <volume>29</volume>
          <issue>5</issue>
          <fpage>1189</fpage>
          <lpage>232</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.jstor.org/stable/2699986"/>
          </comment>
          <pub-id pub-id-type="doi">10.1214/aos/1013203451</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Freund</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Schapire</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A short introduction to boosting</article-title>
          <source>Journal of Japanese Society for Artificial Intelligence</source>
          <year>1999</year>
          <month>9</month>
          <volume>14</volume>
          <issue>5</issue>
          <fpage>771</fpage>
          <lpage>780</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.yorku.ca/gisweb/eats4400/boost.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>CJ</given-names>
            </name>
          </person-group>
          <article-title>LIBSVM</article-title>
          <source>ACM Trans. Intell. Syst. Technol</source>
          <year>2011</year>
          <month>04</month>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>27</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1145/1961189.1961199"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/1961189.1961199</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karim</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Majumdar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Darabi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>LSTM Fully Convolutional Networks for Time Series Classification</article-title>
          <source>IEEE Access</source>
          <year>2018</year>
          <volume>6</volume>
          <fpage>1662</fpage>
          <lpage>1669</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/abstract/document/8141873"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/access.2017.2779939</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bowen</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kreuter</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Spring</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Cofta-Woerpel</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Linnan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Weiner</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bakken</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kaplan</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Squiers</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Fabrizio</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fernandez</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>How we design feasibility studies</article-title>
          <source>Am J Prev Med</source>
          <year>2009</year>
          <month>05</month>
          <volume>36</volume>
          <issue>5</issue>
          <fpage>452</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/19362699"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.amepre.2009.02.002</pub-id>
          <pub-id pub-id-type="medline">19362699</pub-id>
          <pub-id pub-id-type="pii">S0749-3797(09)00096-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC2859314</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Kannry</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chrimes</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>McGinn</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>Edonyabo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mann</surname>
              <given-names>DM</given-names>
            </name>
          </person-group>
          <article-title>Integrating usability testing and think-aloud protocol analysis with "near-live" clinical simulations in evaluating clinical decision support</article-title>
          <source>Int J Med Inform</source>
          <year>2012</year>
          <month>11</month>
          <volume>81</volume>
          <issue>11</issue>
          <fpage>761</fpage>
          <lpage>72</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2012.02.009</pub-id>
          <pub-id pub-id-type="medline">22456088</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(12)00041-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Charmaz</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <source>Constructing Grounded Theory: A Practical Guide through Qualitative Analysis</source>
          <year>2006</year>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Sage Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdullah</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Fakieh</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Health Care Employees' Perceptions of the Use of Artificial Intelligence Applications: Survey Study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>05</month>
          <day>14</day>
          <volume>22</volume>
          <issue>5</issue>
          <fpage>e17620</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/5/e17620/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17620</pub-id>
          <pub-id pub-id-type="medline">32406857</pub-id>
          <pub-id pub-id-type="pii">v22i5e17620</pub-id>
          <pub-id pub-id-type="pmcid">PMC7256754</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kocielnik</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Amershi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>PN</given-names>
            </name>
          </person-group>
          <article-title>Will You Accept an Imperfect AI? Exploring Designs for Adjusting End-user Expectations of AI Systems</article-title>
          <source>CHI '19: Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems</source>
          <year>2019</year>
          <conf-name>2019 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 4-9, 2019</conf-date>
          <conf-loc>Glasgow, Scotland</conf-loc>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1145/3290605.3300641</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Winter</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Steiner</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wilcox</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Terry</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>"Hello AI": Uncovering the Onboarding Needs of Medical Practitioners for Human-AI Collaborative Decision-Making</article-title>
          <source>Proc. ACM Hum.-Comput. Interact</source>
          <year>2019</year>
          <month>11</month>
          <day>07</day>
          <volume>3</volume>
          <issue>CSCW</issue>
          <fpage>1</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1145/3359206</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>LaRosa</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Danks</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Impacts on Trust of Healthcare AI</article-title>
          <source>AIES '18: Proceedings of the 2018 AAAI/ACM Conference on AI, Ethics, and Society</source>
          <year>2018</year>
          <conf-name>2018 AAAI/ACM Conference on AI, Ethics, and Society</conf-name>
          <conf-date>February 2-3, 2018</conf-date>
          <conf-loc>New Orleans, LA</conf-loc>
          <fpage>210</fpage>
          <lpage>215</lpage>
          <pub-id pub-id-type="doi">10.1145/3278721.3278771</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wortman Vaughan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wallach</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Understanding the Effect of Accuracy on Trust in Machine Learning Models</article-title>
          <source>CHI '19: Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems</source>
          <year>2019</year>
          <conf-name>2019 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 4-9, 2019</conf-date>
          <conf-loc>Glasgow, Scotland</conf-loc>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1145/3290605.3300509</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amann</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Blasimme</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vayena</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Frey</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Madai</surname>
              <given-names>VI</given-names>
            </name>
            <collab>Precise4Q consortium</collab>
          </person-group>
          <article-title>Explainability for artificial intelligence in healthcare: a multidisciplinary perspective</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2020</year>
          <month>11</month>
          <day>30</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>310</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-020-01332-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-020-01332-6</pub-id>
          <pub-id pub-id-type="medline">33256715</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-020-01332-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7706019</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maniatopoulos</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Llewellyn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Boyd</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Moving beyond local practice: reconfiguring the adoption of a breast cancer diagnostic technology</article-title>
          <source>Soc Sci Med</source>
          <year>2015</year>
          <month>04</month>
          <volume>131</volume>
          <fpage>98</fpage>
          <lpage>106</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0277953615001288"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.socscimed.2015.02.036</pub-id>
          <pub-id pub-id-type="medline">25769108</pub-id>
          <pub-id pub-id-type="pii">S0277-9536(15)00128-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Abdul</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>BY</given-names>
            </name>
          </person-group>
          <article-title>Designing Theory-Driven User-Centric Explainable AI</article-title>
          <source>CHI '19: Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems</source>
          <year>2019</year>
          <conf-name>2019 CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 4-9, 2019</conf-date>
          <conf-loc>Glasgow, Scotland</conf-loc>
          <fpage>1</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1145/3290605.3300831</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gajowniczek</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Grzegorczyk</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ząbkowski</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Reducing False Arrhythmia Alarms Using Different Methods of Probability and Class Assignment in Random Forest Learning Methods</article-title>
          <source>Sensors (Basel)</source>
          <year>2019</year>
          <month>04</month>
          <day>02</day>
          <volume>19</volume>
          <issue>7</issue>
          <fpage>1588</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s19071588"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s19071588</pub-id>
          <pub-id pub-id-type="medline">30986930</pub-id>
          <pub-id pub-id-type="pii">s19071588</pub-id>
          <pub-id pub-id-type="pmcid">PMC6479538</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Azar</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Elshazly</surname>
              <given-names>HI</given-names>
            </name>
            <name name-style="western">
              <surname>Hassanien</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Elkorany</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>A random forest classifier for lymph diseases</article-title>
          <source>Comput Methods Programs Biomed</source>
          <year>2014</year>
          <month>02</month>
          <volume>113</volume>
          <issue>2</issue>
          <fpage>465</fpage>
          <lpage>73</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.cmpb.2013.11.004"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cmpb.2013.11.004</pub-id>
          <pub-id pub-id-type="medline">24290902</pub-id>
          <pub-id pub-id-type="pii">S0169-2607(13)00375-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khalilia</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chakraborty</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Popescu</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Predicting disease risks from highly imbalanced data using random forest</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2011</year>
          <month>07</month>
          <day>29</day>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>51</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-11-51"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-11-51</pub-id>
          <pub-id pub-id-type="medline">21801360</pub-id>
          <pub-id pub-id-type="pii">1472-6947-11-51</pub-id>
          <pub-id pub-id-type="pmcid">PMC3163175</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
