<?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">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</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">v10i11e40039</article-id>
      <article-id pub-id-type="pmid">36394938</article-id>
      <article-id pub-id-type="doi">10.2196/40039</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>Perspective Toward Machine Learning Implementation in Pediatric Medicine: Mixed Methods Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Ramgopal</surname>
            <given-names>Sriram</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hochheiser</surname>
            <given-names>Harry</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Alexander</surname>
            <given-names>Natasha</given-names>
          </name>
          <degrees>MBBS, MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0151-7277</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Aftandilian</surname>
            <given-names>Catherine</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9775-2839</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Guo</surname>
            <given-names>Lin Lawrence</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2965-8442</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Plenert</surname>
            <given-names>Erin</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0675-882X</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Posada</surname>
            <given-names>Jose</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3864-0241</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Fries</surname>
            <given-names>Jason</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9316-5768</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Fleming</surname>
            <given-names>Scott</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6047-7877</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Johnson</surname>
            <given-names>Alistair</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8735-3014</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Shah</surname>
            <given-names>Nigam</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9385-7158</ext-link>
        </contrib>
        <contrib id="contrib10" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Sung</surname>
            <given-names>Lillian</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Division of Haematology/Oncology</institution>
            <institution>The Hospital for Sick Children</institution>
            <addr-line>555 University Avenue</addr-line>
            <addr-line>Toronto, ON, M5G1X8</addr-line>
            <country>Canada</country>
            <phone>1 416 813 5287</phone>
            <fax>1 416 813 5979</fax>
            <email>lillian.sung@sickkids.ca</email>
          </address>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0951-3091</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Division of Haematology/Oncology</institution>
        <institution>The Hospital for Sick Children</institution>
        <addr-line>Toronto, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Division of Hematology/Oncology</institution>
        <institution>Department of Pediatrics</institution>
        <institution>Stanford University</institution>
        <addr-line>Palo Alto, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Program in Child Health Evaluative Sciences</institution>
        <institution>Peter Gilgan Centre for Research and Learning</institution>
        <addr-line>Toronto, ON</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Systems Engineering and Computing</institution>
        <institution>Universidad del Norte</institution>
        <addr-line>Barranquilla</addr-line>
        <country>Colombia</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Stanford Center for Biomedical Informatics Research</institution>
        <institution>Department of Biomedical Data Science</institution>
        <institution>Stanford University</institution>
        <addr-line>Palo Alto, CA</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Lillian Sung <email>lillian.sung@sickkids.ca</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>11</month>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>17</day>
        <month>11</month>
        <year>2022</year>
      </pub-date>
      <volume>10</volume>
      <issue>11</issue>
      <elocation-id>e40039</elocation-id>
      <history>
        <date date-type="received">
          <day>2</day>
          <month>6</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>7</day>
          <month>9</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>15</day>
          <month>9</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>10</day>
          <month>10</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Natasha Alexander, Catherine Aftandilian, Lin Lawrence Guo, Erin Plenert, Jose Posada, Jason Fries, Scott Fleming, Alistair Johnson, Nigam Shah, Lillian Sung. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 17.11.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2022/11/e40039" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Given the costs of machine learning implementation, a systematic approach to prioritizing which models to implement into clinical practice may be valuable.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The primary objective was to determine the health care attributes respondents at 2 pediatric institutions rate as important when prioritizing machine learning model implementation. The secondary objective was to describe their perspectives on implementation using a qualitative approach.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>In this mixed methods study, we distributed a survey to health system leaders, physicians, and data scientists at 2 pediatric institutions. We asked respondents to rank the following 5 attributes in terms of implementation usefulness: the clinical problem was common, the clinical problem caused substantial morbidity and mortality, risk stratification led to different actions that could reasonably improve patient outcomes, reducing physician workload, and saving money. Important attributes were those ranked as first or second most important. Individual qualitative interviews were conducted with a subsample of respondents.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Among 613 eligible respondents, 275 (44.9%) responded. Qualitative interviews were conducted with 17 respondents. The most common important attributes were risk stratification leading to different actions (205/275, 74.5%) and clinical problem causing substantial morbidity or mortality (177/275, 64.4%). The attributes considered least important were reducing physician workload and saving money. Qualitative interviews consistently prioritized implementations that improved patient outcomes.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Respondents prioritized machine learning model implementation where risk stratification would lead to different actions and clinical problems that caused substantial morbidity and mortality. Implementations that improved patient outcomes were prioritized. These results can help provide a framework for machine learning model implementation.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>machine learning</kwd>
        <kwd>clinical utilization</kwd>
        <kwd>preferences</kwd>
        <kwd>qualitative interviews</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Machine learning has had growing popularity in clinical settings related to the widespread adoption of electronic health records [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>], combined with increasing data storage and computational ability [<xref ref-type="bibr" rid="ref4">4</xref>]. In this setting, machine learning can be useful for multiple purposes including (1) to facilitate diagnoses, as in pathology [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>] and radiology [<xref ref-type="bibr" rid="ref7">7</xref>]; (2) to make predictions about outcomes for risk stratification; and (3) to improve resource utilization by anticipating volumes of patients or services [<xref ref-type="bibr" rid="ref8">8</xref>]. However, despite the initial enthusiasm around machine learning in health care, domain experts have expressed caution [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Similar information technology solutions have commonly failed to be implemented or provide utility [<xref ref-type="bibr" rid="ref11">11</xref>].</p>
      <p>An important consideration impacting utility is choosing the clinical setting and problem in which a machine learning model is to be implemented [<xref ref-type="bibr" rid="ref11">11</xref>]. A machine learning model’s predictions need to augment current approaches in a way that is meaningful and actionable without introducing excessive burden. It is important to carefully plan a machine learning model’s implementation because the costs of model deployment are considerable. Such costs may include resources required to develop and maintain the machine learning model, training of the intended model users regarding how to access and interpret the model’s predictions, and support to help users implement the results into practice [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>].</p>
      <p>Given these costs, a systematic approach for determining which machine learning models should be prioritized for implementation into clinical practice may be valuable. In determining priorities, it would be important to involve key stakeholders at the institution in which deployment is planned. We chose to survey 2 pediatric centers, 1 in the United States with a more established biomedical informatics program, and 1 in Canada with a less established biomedical informatics program, to gain insight into whether experience and expertise affected preferences for machine learning model prioritization. Consequently, the primary objective was to determine the health care attributes respondents at 2 pediatric institutions rate as important when prioritizing machine learning model implementation. The secondary objective was to describe their perspectives on machine learning model implementation using a qualitative approach.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design and Setting</title>
        <p>This was a mixed methods study that included a quantitative and a qualitative component. The institutions were The Hospital for Sick Children (SickKids) in Toronto, Ontario, Canada, and Lucile Packard Children’s Hospital in Palo Alto, California, United States.</p>
      </sec>
      <sec>
        <title>Participants</title>
        <p>We included health system leaders, physicians, and data scientists at SickKids and Lucile Packard Children’s Hospital at the time of survey distribution. We excluded trainees.</p>
      </sec>
      <sec>
        <title>Procedures</title>
        <p>The survey was developed by the study team based on their impression of health care attributes respondents might consider to be important; the machine learning–focused questions are presented as <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. Potential participants were identified through organizational emailing lists. The quantitative survey was distributed by email and participants completed the survey in REDCap [<xref ref-type="bibr" rid="ref14">14</xref>]. The survey asked respondents to indicate whether they were health system leaders, physicians, or data scientists; respondents could indicate multiple categories. Demographic variables included clinical specialty (if applicable), years employed following completion of training, and gender.</p>
        <p>We then asked about their knowledge of artificial intelligence on a 5-point Likert scale ranging from 1 (no knowledge at all) to 5 (a lot of knowledge). We asked them to rate their understanding of how machine learning models are built and interpreted, and how statistics are conducted and interpreted, using 5-point Likert scales ranging from 1 (no understanding) to 5 (fully understand). We asked if they had decision-making ability to implement artificial intelligence initiatives within their work environment, and how many machine learning models had been deployed at their institutions in the last 5 years.</p>
        <p>The next section asked respondents to rank the following 5 clinical problem and implementation consequence attributes in terms of whether machine learning implementation would be useful: “the clinical problem being solved is common,” “the clinical problem causes substantial morbidity or mortality,” “risk stratification would lead to different clinical actions that could reasonably improve patient outcomes,” “implementing the model could reduce physician workload,” and “implementing the model could save money.” Important attributes were defined as those ranked as most important or second most important (rank of 1 or 2) by respondents. The survey then asked 2 open-ended questions focused on clinical areas where being able to accurately predict an outcome might be useful, and clinical areas in which prioritization or reorganization of waitlists might be useful. Finally, the survey asked whether they would be willing to participate in a qualitative interview.</p>
        <p>For the qualitative aspect, we purposively sampled respondents to maximize variation by institution and self-rated understanding of machine learning. Semistructured interviews were conducted using Zoom (Zoom Video Communications, Inc.) or Microsoft Teams by a member of the SickKids team (EP) with expertise in the conduct of qualitative interviews. Respondents were asked to list 3 scenarios in which a machine learning model for risk stratification could be useful and then to state which scenario was the most important to implement first and the rationale for the choice. They were then asked how they would feel about using a machine learning model for risk stratification as opposed to their current approach, and to describe concerns they had about using a machine learning model to guide patient care. The interviews were recorded and transcribed verbatim.</p>
      </sec>
      <sec>
        <title>Analysis</title>
        <p>The data from the quantitative survey from SickKids and Lucile Packard Children’s Hospital were compared using the Fisher exact test. Analyses were performed in R (R Core Team) using RStudio version 3.6.1 [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>].</p>
        <p>The analysis of qualitative data was performed according to the principles of grounded theory methodology; data collection and analysis occurred concurrently. Qualitative transcripts were analyzed by 2 independent reviewers (NA and EP) using the constant comparative method to develop a theoretical framework for respondents’ perspectives of machine learning that are grounded in their individual experiences and understandings. Sampling was continued until saturation was reached, which was defined as the point in which no new themes emerged from the data.</p>
      </sec>
      <sec>
        <title>Ethics Approval</title>
        <p>The study was approved by the Research Ethics Board at SickKids. The need for Institutional Review Board approval was waived by Lucile Packard Children’s Hospital as the data collection was performed by SickKids personnel. For the quantitative survey, completion of the survey was considered implied consent to study participation. For the qualitative component, respondents provided verbal consent to participate.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>The quantitative survey was distributed at SickKids between November 1, 2021, and January 6, 2022 and at Lucile Packard Children’s Hospital between March 15, 2022, and April 12, 2022. Among 613 eligible respondents, 275 (44.9%) responded. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the participant identification and selection flowchart, including the number participating in the qualitative interviews when saturation was reached.</p>
      <p><xref ref-type="table" rid="table1">Table 1</xref> presents the demographic characteristics of respondents; physician specialty (<italic>P</italic>&#60;.001) and years from completion of training (<italic>P</italic>=.006) were significantly different between the 2 institutions. The majority of respondents were physicians (165/195, 84.6%, at SickKids and 73/80, 91.3%, at Lucile Packard Children’s Hospital). The number of respondents who had decision-making ability to implement artificial intelligence initiatives was 99/195 (50.8%) at SickKids and 41/80 (51.3%) at Lucile Packard Children’s Hospital. Most respondents did not know the number of machine learning models deployed at their institution over the last 5 years (137/195, 70.3%, at SickKids and 53/80, 66.3%, at Lucile Packard Children’s Hospital).</p>
      <p><xref ref-type="table" rid="table2">Table 2</xref> illustrates respondents’ self-perceived knowledge of artificial intelligence and understanding of machine learning and statistics. There were no statistically significant differences in these ratings by institution (artificial intelligence knowledge, <italic>P</italic>=.93; machine learning development and interpretation, <italic>P</italic>=.72; statistics conduct and interpretation, <italic>P</italic>=.19). The percentage of respondents who stated they had “moderate” or “a lot” of artificial intelligence knowledge was 17.9% (35/195) at SickKids and 17.5% (14/80) at Lucile Packard Children’s Hospital. <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> compares respondent characteristics by those who self-rated their artificial intelligence knowledge as high (score of 4 or 5 on the 5-point Likert scale) versus not high across institutions. Those who self-rated their knowledge as high were significantly more likely to be males (<italic>P</italic>=.02) and nonphysicians (<italic>P</italic>=.006). The percentage of respondents who stated they understood machine learning development and interpretation at a “moderate” level or “fully” was 15.9% (31/195) at SickKids and 11.3% (9/80) at Lucile Packard Children’s Hospital. Across both institutions, the percentage who stated their understanding of machine learning was “none” or “very little” was 146/275 (53.1%). Conversely, the percentage of respondents who stated they understood statistics conduct and interpretation at a “moderate” level or “fully” was 54.4% (106/195) at SickKids and 42.5% (34/80) at Lucile Packard Children’s Hospital. Across both institutions, the percentage who stated their understanding of statistics was “none” or “very little” was 30/275 (10.9%).</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>CONSORT (Consolidated Standards of Reporting Trials) diagram of participant identification, selection, and participation.</p>
        </caption>
        <graphic xlink:href="medinform_v10i11e40039_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Demographic characteristics of participants at 2 pediatric institutions (N=275).</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="370"/>
          <col width="0"/>
          <col width="190"/>
          <col width="0"/>
          <col width="340"/>
          <col width="0"/>
          <col width="70"/>
          <thead>
            <tr valign="top">
              <td colspan="3">Characteristic</td>
              <td colspan="2">SickKids (n=195), n (%)</td>
              <td colspan="2">Lucile Packard Children’s Hospital (n=80), n (%)</td>
              <td><italic>P</italic> value</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="3">Male gender</td>
              <td colspan="2">93 (47.7)</td>
              <td colspan="2">35 (43.8)</td>
              <td>.64</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Professional role<sup>a</sup></bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Physician</td>
              <td colspan="2">165 (84.6)</td>
              <td colspan="2">73 (91.3)</td>
              <td colspan="2">.20</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Health system leader</td>
              <td colspan="2">22 (11.3)</td>
              <td colspan="2">17 (21.3)</td>
              <td colspan="2">.05</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Data scientist</td>
              <td colspan="2">15 (7.7)</td>
              <td colspan="2">2 (2.5)</td>
              <td colspan="2">.18</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Physician specialty</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td>&#60;.001</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Hematology oncology</td>
              <td colspan="2">33 (16.9)</td>
              <td colspan="2">14 (17.5)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>General medicine</td>
              <td colspan="2">21 (10.8)</td>
              <td colspan="2">7 (8.8)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Critical care medicine</td>
              <td colspan="2">11 (5.6)</td>
              <td colspan="2">12 (15.0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Emergency medicine</td>
              <td colspan="2">14 (7.2)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Cardiology</td>
              <td colspan="2">9 (4.6)</td>
              <td colspan="2">7 (8.8)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Neurology</td>
              <td colspan="2">11 (5.6)</td>
              <td colspan="2">3 (3.8)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Endocrinology and metabolism</td>
              <td colspan="2">10 (5.1)</td>
              <td colspan="2">6 (7.5)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Gastroenterology</td>
              <td colspan="2">9 (4.6)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Respirology</td>
              <td colspan="2">4 (2.1)</td>
              <td colspan="2">4 (5.0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Infectious disease</td>
              <td colspan="2">2 (1.0)</td>
              <td colspan="2">5 (6.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Surgery</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">6 (7.5)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Adolescent medicine</td>
              <td colspan="2">6 (3.1)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Other</td>
              <td colspan="2">20 (10.3)</td>
              <td colspan="2">7 (8.8)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Not known</td>
              <td colspan="2">45 (23.1)</td>
              <td colspan="2">9 (11.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Years from completion of training</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td>.006</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>&#60;1</td>
              <td colspan="2">6 (3.1)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>1-4</td>
              <td colspan="2">38 (19.5)</td>
              <td colspan="2">5 (6.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>5-10</td>
              <td colspan="2">38 (19.5)</td>
              <td colspan="2">25 (31.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>11+</td>
              <td colspan="2">113 (57.9)</td>
              <td colspan="2">50 (62.5)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="3">Decision-making ability to implement artificial intelligence initiatives</td>
              <td colspan="2">99 (50.8)</td>
              <td colspan="2">41 (51.3)</td>
              <td>&#62;.99</td>
            </tr>
            <tr valign="top">
              <td colspan="5">
                <bold>Number of machine learning models deployed at institution in last 5 years</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td>.43</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>None</td>
              <td colspan="2">31 (15.9)</td>
              <td colspan="2">11 (13.8)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>1</td>
              <td colspan="2">7 (3.6)</td>
              <td colspan="2">6 (7.5)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>2-4</td>
              <td colspan="2">14 (7.2)</td>
              <td colspan="2">9 (11.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>5-10</td>
              <td colspan="2">2 (1.0)</td>
              <td colspan="2">1 (1.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>11+</td>
              <td colspan="2">4 (2.1)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Do not know</td>
              <td colspan="2">137 (70.3)</td>
              <td colspan="2">53 (66.3)</td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>Respondent may choose more than 1 option and thus, numbers do not add to 100%.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <table-wrap position="float" id="table2">
        <label>Table 2</label>
        <caption>
          <p>Self-rating of knowledge of artificial intelligence and understanding of machine learning and statistics.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="340"/>
          <col width="190"/>
          <col width="350"/>
          <col width="90"/>
          <thead>
            <tr valign="top">
              <td colspan="2">Areas</td>
              <td>SickKids (n=195), n (%)</td>
              <td>Lucile Packard Children’s Hospital (n=80), n (%)</td>
              <td><italic>P</italic>-value</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="2">
                <bold>Artificial intelligence knowledge</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>.93</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>None</td>
              <td>10 (5.1)</td>
              <td>5 (6.3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Very little</td>
              <td>67 (34.4)</td>
              <td>30 (37.5)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Some</td>
              <td>83 (42.6)</td>
              <td>31 (38.8)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Moderate</td>
              <td>30 (15.4)</td>
              <td>11 (13.8)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>A lot</td>
              <td>5 (2.6)</td>
              <td>3 (3.8)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Machine learning development and interpretation</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>.72</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>None</td>
              <td>44 (22.6)</td>
              <td>18 (22.5)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Very little</td>
              <td>56 (28.7)</td>
              <td>28 (35.0)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Somewhat</td>
              <td>64 (32.8)</td>
              <td>25 (31.3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Moderate</td>
              <td>24 (12.3)</td>
              <td>8 (10.0)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Fully</td>
              <td>7 (3.6)</td>
              <td>1 (1.3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Statistics conduct and interpretation</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>.19</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>None</td>
              <td>4 (2.1)</td>
              <td>1 (1.3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Very little</td>
              <td>18 (9.2)</td>
              <td>7 (8.8)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Somewhat</td>
              <td>67 (34.4)</td>
              <td>38 (47.5)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Moderate</td>
              <td>78 (40.0)</td>
              <td>29 (36.3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Fully</td>
              <td>28 (14.4)</td>
              <td>5 (6.3)</td>
              <td>
                <break/>
              </td>
            </tr>
          </tbody>
        </table>
      </table-wrap>
      <p><xref ref-type="table" rid="table3">Table 3</xref> reveals the proportion of respondents who ranked each attribute as important (ranked first or second among the 5 attributes) for prioritization of machine learning models. There were no significant differences in these proportions by institution for any of the 5 attributes (<xref ref-type="table" rid="table3">Table 3</xref>). Across both sites, the most common important attributes were risk stratification leading to different actions (205/275, 74.5%) and clinical problem causes substantial morbidity or mortality (177/275, 64.4%). The attributes considered least important were “implementing the model could reduce physician workload” (40/275, 14.5%) and “implementing the model could save money” (13/275, 4.7%). The median importance scores for both institutions combined are also shown in <xref ref-type="table" rid="table3">Table 3</xref> (where lower is more important).</p>
      <table-wrap position="float" id="table3">
        <label>Table 3</label>
        <caption>
          <p>Ranked as important<sup>a</sup> by respondents for prioritization of machine learning.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="430"/>
          <col width="140"/>
          <col width="210"/>
          <col width="70"/>
          <col width="150"/>
          <thead>
            <tr valign="top">
              <td>Attributes considered important</td>
              <td>SickKids (n=195), n (%)</td>
              <td>Lucile Packard Children’s Hospital (n=80), n (%)</td>
              <td><italic>P</italic>-value</td>
              <td>Median importance score (IQR)<sup>b</sup></td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>The clinical problem being solved is common</td>
              <td>66 (33.8)</td>
              <td>35 (43.8)</td>
              <td>.16</td>
              <td>3 (2-3)</td>
            </tr>
            <tr valign="top">
              <td>The clinical problem causes substantial morbidity or mortality</td>
              <td>133 (68.2)</td>
              <td>44 (55.0)</td>
              <td>.05</td>
              <td>2 (2-3)</td>
            </tr>
            <tr valign="top">
              <td>Risk stratification would lead to different clinical actions that could reasonably improve patient outcomes</td>
              <td>145 (74.4)</td>
              <td>60 (75.0)</td>
              <td>&#62;.99</td>
              <td>1 (1-2)</td>
            </tr>
            <tr valign="top">
              <td>Implementing the model could reduce physician workload</td>
              <td>29 (14.9)</td>
              <td>11 (13.8)</td>
              <td>.96</td>
              <td>4 (3-4)</td>
            </tr>
            <tr valign="top">
              <td>Implementing the model could save money</td>
              <td>11 (5.6)</td>
              <td>2 (2.5)</td>
              <td>.42</td>
              <td>5 (4-5)</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table3fn1">
            <p><sup>a</sup>Important defined as attributes ranked as most important or second most important (rank of 1 or 2) in terms of whether a machine learning model would be useful.</p>
          </fn>
          <fn id="table3fn2">
            <p><sup>b</sup>Across both institutions.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p><xref ref-type="table" rid="table4">Table 4</xref> shows the themes and subthemes from the qualitative interviews. Perceived benefits of machine learning model implementation included facilitating decision making in complex scenarios, supporting less experienced clinicians, reducing cognitive load, and reducing cognitive bias. It was also expressed that machine learning models can potentially improve the quality of care through standardization, more effective triage, and facilitating precision medicine. Finally, machine learning models had the potential to reduce physician workload. However, perceived challenges of machine learning model implementation included the potential for algorithmic bias, lack of transparency and trust, and failure to incorporate clinical expertise. Machine learning model implementation might also adversely affect quality of care and respondents spoke about the need to evaluate the impact of machine learning model implementation. Practical concerns raised about machine learning model implementation included challenges incorporating the model into the clinical workflow and questions about accountability in the event of poor outcomes arising from machine learning model–directed actions. Finally, uncertainty about the physician’s role was identified. When asked to prioritize 1 clinical scenario for machine learning model implementation, the rationale for choosing which scenario to implement consistently related to impact on patient outcomes: “most benefit to kids,” “leading cause of death,” and “implications can be extremely serious.”</p>
      <p><xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> illustrates examples of clinical areas that could be prioritized for machine learning initiatives identified from the quantitative survey.</p>
      <table-wrap position="float" id="table4">
        <label>Table 4</label>
        <caption>
          <p>Perspectives of machine learning implementation in pediatric medicine from qualitative interviews.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="30"/>
          <col width="180"/>
          <col width="0"/>
          <col width="0"/>
          <col width="760"/>
          <thead>
            <tr valign="top">
              <td colspan="5">Themes and subthemes</td>
              <td>Example quotations</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="6">Benefits of machine learning implementation</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Facilitates decision making</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Complex scenario</td>
              <td colspan="3">
                <italic>To me was very disturbing scenario where a very complex child with a number of issues, [...] Having some kind of system which alerts physicians who are directly involved as to not any in their own domains, but in other domains’ risk would be helpful</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Support less experienced clinicians</td>
              <td colspan="3">
                <italic>Well, you know where I see potential strength is not so much for the highly experienced physician, but more for the person who’s starting out [...] and just doesn't have that experience base yet.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Reduce cognitive load</td>
              <td colspan="3">
                <italic>It can offload some of the cognitive load. So yeah, absolutely. I mean there's many times you find yourself in the middle of the night very tired, half groggy and trying to make a decision and kind of going back and forth in your brain. You know, for like half an hour - should I do this or that?</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Reduce cognitive bias</td>
              <td colspan="3">
                <italic>[...]</italic>
                <italic> it's not that it replaces your judgment, it supplements another sense.</italic>
                <italic>...</italic>
                <italic>your decisions informed no matter by your experience but it's informed by thousands of experiences, computed even more times to see all the possibilities and then come up with a best sort of path forward. The most likely scenario. And understanding that it is not a perfect prediction but it's a much more</italic>
                <italic>...</italic>
                <italic>It's where that big data come in, right? It's really powered by real knowledge. It's not personal perceptions or personal experience, which is very biased and skewed.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Improve quality of care</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Standardize care</td>
              <td colspan="3">
                <italic>There probably is some significant interpersonal variability in terms of interpreting the guidelines and then decision making around management, and so if we could use machine learning so that there’s less of that, all the while providing I guess more accurate or better care. I think that would be very helpful.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>More effective triage</td>
              <td colspan="3">
                <italic>I feel like if we were able to use machine learning to risk stratify so that kids who are at higher risk could get more timely access to a referral. Recognizing that in this particular situation, certainly early diagnosis and management can really impact the trajectory of a child’s outcome. I think that would be helpful.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Facilitate precision medicine</td>
              <td colspan="3">
                <italic>And what I mean by that if you look at it, look at a population of babies who were all born, say at 25 weeks. There will be individual differences that should [...] be detectable by machine learning or artificial intelligence. So instead of treating every baby as simply a member of the population, I can sort of drill down onto specific physiological and clinical factors for that baby, [...] get closer to the idea of personalized medicine.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Reduce physician workload</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Freeing up time for physicians</td>
              <td colspan="3">
                <italic>If it was really useful, then maybe it would free me up to do things that only I can do.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="6">
                <bold>Challenges with</bold>
                <bold>machine</bold>
                <bold>learning implementation</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Hinders decision making</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Algorithmic bias</td>
              <td colspan="3">
                <italic>It's all about the biases like built into the system and how it's learned the data that you're putting in, and then how you get that out and how it would either pick up on our own biases, or like pre-existing, whether those are like systemic like sort of racial, ethnic or gendered biases [...] And so then that's not really helping us.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Lack of transparency and trust</td>
              <td colspan="3">
                <italic>Understanding what it is doing: like if it's doing things that I can't follow or don't understand, I'm going to be less to trust its opinion [...] I want to understand how it came to that decision so I can ask myself if I agree.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Not incorporating clinical expertise into decisions</td>
              <td colspan="3">
                <italic>I think it's like all the tools we have in medicine that if you use it appropriately, it can be incredibly powerful. But if it's used as a, you know, let me abandon all my other skills and I'll just follow this kind of direction, it potentially could be harmful, so I think a lot of thought will be needed.</italic>
                <break/>
                <italic>I mean in some ways it helps to predict, but I think I've always been a little skeptical about machine learning because biology and people do not follow an algorithm, they don’t follow a formula.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="5">
                <bold>Negative impact on quality of care</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Need for outcome evaluation</td>
              <td colspan="3">
                <italic>[...] looking at what the outcomes are and that we're actually improving patient care. So if we're admitting more but the outcomes are the same and the return visits are the same, then did it really matter and are we improving patient care or we just increasing cost to the system? And so, I think it needs constant evaluation, just like anything else that we do...</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Data quality</td>
              <td colspan="3">
                <italic>Of course, you know your outcome or the recommendation, or how machine learning is used is always only as good as the input, right?</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Practical concerns</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Challenges in workflow implementation</td>
              <td colspan="3">
                <italic>I guess there’s going to be some learning curve. How do we use it? Is it feasible? Is it on my iPhone? Do I have to go into certain area, how fast will it take me to get the response and along with the interface, how friendly is the interface? You know things that are related to stuff that we have not seen yet.</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Accountability</td>
              <td colspan="3">
                <italic>The challenge with machine learning over clinical decision rules is right now with the accountability piece and it's just getting to what that's going to be like. We don't blame, you know, the lab test or the lab. You know, if we don't pick it up. But right now, I think people feeling if they go against it, what does that mean and do we have to add like admit everybody or treat everybody based on that, knowing that like you alluded on the first question that it is a probability [...] So what does that mean for the provider thing choose to ignore it versus if they choose to follow it in harm happens</italic>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="3">
                <bold>Physician role</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>Uncertainty in physician role</td>
              <td colspan="3">
                <italic>On the other hand, you know, maybe it also kind of takes away a little bit from like, I guess there's a fear of what exactly is the doctor's role. If the computer can do a better job at diagnosing then I can</italic>
              </td>
            </tr>
          </tbody>
        </table>
      </table-wrap>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>In this mixed methods study, we found that the attributes most commonly listed as important for machine learning model implementation were risk stratification leading to different actions that could reasonably improve patient outcomes and a clinical problem that causes substantial morbidity or mortality. Few respondents considered reducing physician workload and saving money as important. We also found that important attributes were similar at the 2 institutions despite different levels of biomedical informatic program establishment and different health care systems.</p>
      <p>The wide range of recommended areas for machine learning model implementation highlights the need for prioritization given the likely limited capacity to develop, deploy, and monitor machine learning models, even at large institutions with mature bioinformatics programs. This study is important as it provides a framework by which institutional leaders could make decisions about which machine learning models to prioritize for implementation. While we found that risk stratification that improves patient outcomes was the most common important attribute, additional considerations include actions that would arise from high- and low-risk labels, evidence that differential actions will improve outcomes, and identifying ideal thresholds for risk categorization. Even once a model is deployed, ongoing monitoring of model performance and the impact of model deployment on patient care and clinical workflows are additional postimplementation considerations.</p>
      <p>While we evaluated attribute importance across respondent types, Wears and Berg [<xref ref-type="bibr" rid="ref11">11</xref>] previously discussed the complex relationship between decision makers, beneficiaries of a machine learning solution, and those who shoulder the burden of implementation. They noted that a mismatch between these individuals can lead to failure. More specifically, it is often the administrator who is the decision maker and recipient of benefits, while it is the clinician who often shoulders the burden of implementation [<xref ref-type="bibr" rid="ref11">11</xref>]. Anticipation and acknowledgement of conflicting perspectives will be required during the prioritization process among stakeholder types.</p>
      <p>We also found that across both institutions, respondents had greater confidence in their understanding of statistics and relatively lower confidence in their understanding of machine learning. These perspectives did not differ between the 2 institutions despite different levels of establishment of their biomedical informatic programs. Our results suggest that across pediatric medicine in general, more education focused on machine learning is required during training and continuing education.</p>
      <p>Our results complement the work of others who have highlighted the requirements of clinical decision support including those based on machine learning. Items important to consider include the need to avoid black boxes, excessive time requirement, and complexity in addition to ensuring relevance, respect, and scientific validity [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. It also accompanies work demonstrating that barriers to adoption of artificial intelligence are not restricted to clinicians but also include parents [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. It may also be useful to compare our findings with studies conducted outside of pediatric medicine. We found that the main anticipated benefits of machine learning implementation were facilitation of decision making, improvement in quality of care, and reduction in physician workload. Compared with our findings, benefits and challenges associated with artificial intelligence were similar in ophthalmology, dermatology, radiology, optometry, and surgery [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. However, our study is unique because of the consideration of how to prioritize problems for implementation, a pragmatic consideration in developing a clinical program. In addition, the focus on pediatrics may be important as the nature of clinical problems, perspectives, and stakeholders can differ between pediatric and adult patient populations.</p>
      <p>The strengths of this study include its mixed methods design and inclusion of 2 different pediatric institutions by country and establishment of their biomedical informatic programs. However, our results should be interpreted in light of their limitations. We had a relatively low response rate; respondents were likely biased in favor of interest in machine learning. Thus, nonrespondents likely would have had lower familiarity with machine learning and likely would have had less strong opinions about attributes considered important for machine learning prioritization. We also had a greater proportion of physicians than system leaders or data scientists; these groups may have different priorities or implementation concerns.</p>
      <p>In conclusion, respondents prioritized machine learning model implementation where risk stratification would lead to different actions and clinical problems that caused substantial morbidity and mortality. Implementations that improved patient outcomes were prioritized. These results can help provide a framework for prioritizing machine learning model implementation.</p>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Quantitative survey administered.</p>
        <media xlink:href="medinform_v10i11e40039_app1.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Comparison of participants with artificial intelligence knowledge high versus not high (N=275).</p>
        <media xlink:href="medinform_v10i11e40039_app2.docx" xlink:title="DOCX File , 17 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Examples of recommendations of areas in pediatric care that should be prioritized for machine learning from quantitative survey.</p>
        <media xlink:href="medinform_v10i11e40039_app3.docx" xlink:title="DOCX File , 18 KB"/>
      </supplementary-material>
    </app-group>
    <ack>
      <p>LS is supported by the Canada Research Chair in Pediatric Oncology</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnan</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Big data and clinicians: a review on the state of the science</article-title>
          <source>JMIR Med Inform</source>
          <year>2014</year>
          <month>01</month>
          <day>17</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2014/1/e1/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.2913</pub-id>
          <pub-id pub-id-type="medline">25600256</pub-id>
          <pub-id pub-id-type="pii">v2i1e1</pub-id>
          <pub-id pub-id-type="pmcid">PMC4288113</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>Hansen</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Miron-Shatz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>AYS</given-names>
            </name>
            <name name-style="western">
              <surname>Paton</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Big Data in Science and Healthcare: A Review of Recent Literature and Perspectives</article-title>
          <source>Yearb Med Inform</source>
          <year>2018</year>
          <month>03</month>
          <day>05</day>
          <volume>23</volume>
          <issue>01</issue>
          <fpage>21</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.15265/iy-2014-0004</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>El Aboudi</surname>
              <given-names>Naoual</given-names>
            </name>
            <name name-style="western">
              <surname>Benhlima</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Big Data Management for Healthcare Systems: Architecture, Requirements, and Implementation</article-title>
          <source>Adv Bioinformatics</source>
          <year>2018</year>
          <month>06</month>
          <day>21</day>
          <volume>2018</volume>
          <fpage>4059018</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2018/4059018"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2018/4059018</pub-id>
          <pub-id pub-id-type="medline">30034468</pub-id>
          <pub-id pub-id-type="pmcid">PMC6032968</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>Rajkomar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dean</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kohane</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Machine Learning in Medicine</article-title>
          <source>N Engl J Med</source>
          <year>2019</year>
          <month>04</month>
          <day>04</day>
          <volume>380</volume>
          <issue>14</issue>
          <fpage>1347</fpage>
          <lpage>1358</lpage>
          <pub-id pub-id-type="doi">10.1056/nejmra1814259</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>Nanaa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Akkus</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>WY</given-names>
            </name>
            <name name-style="western">
              <surname>Pantanowitz</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Salama</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>Machine learning and augmented human intelligence use in histomorphology for haematolymphoid disorders</article-title>
          <source>Pathology</source>
          <year>2021</year>
          <month>04</month>
          <volume>53</volume>
          <issue>3</issue>
          <fpage>400</fpage>
          <lpage>407</lpage>
          <pub-id pub-id-type="doi">10.1016/j.pathol.2020.12.004</pub-id>
          <pub-id pub-id-type="medline">33642096</pub-id>
          <pub-id pub-id-type="pii">S0031-3025(21)00045-3</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>Stenzinger</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alber</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Allgäuer</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Jurmeister</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bockmayr</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Budczies</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lennerz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Eschrich</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kazdal</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Schirmacher</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Tacke</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Capper</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Klaus-Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Klauschen</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and pathology: From principles to practice and future applications in histomorphology and molecular profiling</article-title>
          <source>Semin Cancer Biol</source>
          <year>2022</year>
          <month>09</month>
          <volume>84</volume>
          <fpage>129</fpage>
          <lpage>143</lpage>
          <pub-id pub-id-type="doi">10.1016/j.semcancer.2021.02.011</pub-id>
          <pub-id pub-id-type="medline">33631297</pub-id>
          <pub-id pub-id-type="pii">S1044-579X(21)00034-1</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>Richardson</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Auffermann</surname>
              <given-names>WF</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharya</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Consul</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Fotos</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Kelahan</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lo</surname>
              <given-names>HS</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>XV</given-names>
            </name>
            <name name-style="western">
              <surname>Salkowski</surname>
              <given-names>LR</given-names>
            </name>
            <name name-style="western">
              <surname>Sin</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Wassef</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ikuta</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Review of Artificial Intelligence Training Tools and Courses for Radiologists</article-title>
          <source>Acad Radiol</source>
          <year>2021</year>
          <month>09</month>
          <volume>28</volume>
          <issue>9</issue>
          <fpage>1238</fpage>
          <lpage>1252</lpage>
          <pub-id pub-id-type="doi">10.1016/j.acra.2020.12.026</pub-id>
          <pub-id pub-id-type="medline">33714667</pub-id>
          <pub-id pub-id-type="pii">S1076-6332(21)00061-1</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>Drysdale</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Goldenberg</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Forecasting emergency department capacity constraints for COVID isolation beds</article-title>
          <source>arXiv. Preprint posted online on November 9, 2020</source>
          <year>2020</year>
          <volume>1</volume>
          <fpage>1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/pdf/2011.06058.pdf"/>
          </comment>
        </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>Maddox</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Rumsfeld</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>PRO</given-names>
            </name>
          </person-group>
          <article-title>Questions for Artificial Intelligence in Health Care</article-title>
          <source>JAMA</source>
          <year>2019</year>
          <month>01</month>
          <day>01</day>
          <volume>321</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2018.18932</pub-id>
          <pub-id pub-id-type="medline">30535130</pub-id>
          <pub-id pub-id-type="pii">2718456</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>Verghese</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>NH</given-names>
            </name>
            <name name-style="western">
              <surname>Harrington</surname>
              <given-names>RA</given-names>
            </name>
          </person-group>
          <article-title>What This Computer Needs Is a Physician: Humanism and Artificial Intelligence</article-title>
          <source>JAMA</source>
          <year>2018</year>
          <month>01</month>
          <day>02</day>
          <volume>319</volume>
          <issue>1</issue>
          <fpage>19</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2017.19198</pub-id>
          <pub-id pub-id-type="medline">29261830</pub-id>
          <pub-id pub-id-type="pii">2666717</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>Wears</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Berg</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Computer technology and clinical work: still waiting for Godot</article-title>
          <source>JAMA</source>
          <year>2005</year>
          <month>03</month>
          <day>09</day>
          <volume>293</volume>
          <issue>10</issue>
          <fpage>1261</fpage>
          <lpage>3</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.293.10.1261</pub-id>
          <pub-id pub-id-type="medline">15755949</pub-id>
          <pub-id pub-id-type="pii">293/10/1261</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>Morse</surname>
              <given-names>KE</given-names>
            </name>
            <name name-style="western">
              <surname>Bagley</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>NH</given-names>
            </name>
          </person-group>
          <article-title>Estimate the hidden deployment cost of predictive models to improve patient care</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>01</month>
          <day>13</day>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>18</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-019-0651-8</pub-id>
          <pub-id pub-id-type="medline">31932778</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-019-0651-8</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>Sendak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Balu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schulman</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Barriers to Achieving Economies of Scale in Analysis of EHR Data</article-title>
          <source>Appl Clin Inform</source>
          <year>2017</year>
          <month>12</month>
          <day>20</day>
          <volume>08</volume>
          <issue>03</issue>
          <fpage>826</fpage>
          <lpage>831</lpage>
          <pub-id pub-id-type="doi">10.4338/aci-2017-03-cr-0046</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>Harris</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Thielke</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Conde</surname>
              <given-names>JG</given-names>
            </name>
          </person-group>
          <article-title>Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support</article-title>
          <source>J Biomed Inform</source>
          <year>2009</year>
          <month>04</month>
          <volume>42</volume>
          <issue>2</issue>
          <fpage>377</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(08)00122-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2008.08.010</pub-id>
          <pub-id pub-id-type="medline">18929686</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(08)00122-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC2700030</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>R Core Team</collab>
          </person-group>
          <source>R: A language and environment for statistical computing</source>
          <year>2021</year>
          <publisher-loc>Vienna, Austria</publisher-loc>
          <publisher-name>R Foundation for Statistical Computing</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.R-project.org/">https://www.R-project.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>RStudio Team</collab>
          </person-group>
          <source>RStudio: Integrated Development for R</source>
          <year>2020</year>
          <publisher-loc>Boston, MA</publisher-loc>
          <publisher-name>RStudio, PBC</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.rstudio.com/">http://www.rstudio.com/</ext-link>
          </comment>
        </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>Rousseau</surname>
              <given-names>Nikki</given-names>
            </name>
            <name name-style="western">
              <surname>McColl</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Newton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Grimshaw</surname>
              <given-names>Jeremy</given-names>
            </name>
            <name name-style="western">
              <surname>Eccles</surname>
              <given-names>Martin</given-names>
            </name>
          </person-group>
          <article-title>Practice based, longitudinal, qualitative interview study of computerised evidence based guidelines in primary care</article-title>
          <source>BMJ</source>
          <year>2003</year>
          <month>02</month>
          <day>08</day>
          <volume>326</volume>
          <issue>7384</issue>
          <fpage>314</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/12574046"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.326.7384.314</pub-id>
          <pub-id pub-id-type="medline">12574046</pub-id>
          <pub-id pub-id-type="pmcid">PMC143528</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>Zheng</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Padman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Diamond</surname>
              <given-names>HS</given-names>
            </name>
          </person-group>
          <article-title>Understanding technology adoption in clinical care: clinician adoption behavior of a point-of-care reminder system</article-title>
          <source>Int J Med Inform</source>
          <year>2005</year>
          <month>08</month>
          <volume>74</volume>
          <issue>7-8</issue>
          <fpage>535</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2005.03.007</pub-id>
          <pub-id pub-id-type="medline">16043083</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(05)00028-6</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>Patterson</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Doebbeling</surname>
              <given-names>BN</given-names>
            </name>
            <name name-style="western">
              <surname>Fung</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Militello</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Anders</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Asch</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Identifying barriers to the effective use of clinical reminders: bootstrapping multiple methods</article-title>
          <source>J Biomed Inform</source>
          <year>2005</year>
          <month>06</month>
          <volume>38</volume>
          <issue>3</issue>
          <fpage>189</fpage>
          <lpage>99</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(04)00164-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2004.11.015</pub-id>
          <pub-id pub-id-type="medline">15896692</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(04)00164-9</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>Sisk</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Antes</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Burrous</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>DuBois</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Parental Attitudes toward Artificial Intelligence-Driven Precision Medicine Technologies in Pediatric Healthcare</article-title>
          <source>Children (Basel)</source>
          <year>2020</year>
          <month>09</month>
          <day>20</day>
          <volume>7</volume>
          <issue>9</issue>
          <fpage>145</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=children7090145"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/children7090145</pub-id>
          <pub-id pub-id-type="medline">32962204</pub-id>
          <pub-id pub-id-type="pii">children7090145</pub-id>
          <pub-id pub-id-type="pmcid">PMC7552627</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>Jutzi</surname>
              <given-names>TB</given-names>
            </name>
            <name name-style="western">
              <surname>Krieghoff-Henning</surname>
              <given-names>EI</given-names>
            </name>
            <name name-style="western">
              <surname>Holland-Letz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Utikal</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Hauschild</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schadendorf</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sondermann</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Fröhling</surname>
              <given-names>Stefan</given-names>
            </name>
            <name name-style="western">
              <surname>Hekler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schmitt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Maron</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Brinker</surname>
              <given-names>TJ</given-names>
            </name>
          </person-group>
          <article-title>Artificial Intelligence in Skin Cancer Diagnostics: The Patients' Perspective</article-title>
          <source>Front Med (Lausanne)</source>
          <year>2020</year>
          <month>6</month>
          <day>2</day>
          <volume>7</volume>
          <fpage>233</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fmed.2020.00233"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fmed.2020.00233</pub-id>
          <pub-id pub-id-type="medline">32671078</pub-id>
          <pub-id pub-id-type="pmcid">PMC7326111</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>Scheetz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rothschild</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McGuinness</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hadoux</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Soyer</surname>
              <given-names>HP</given-names>
            </name>
            <name name-style="western">
              <surname>Janda</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Condon</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Oakden-Rayner</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Palmer</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Keel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>van Wijngaarden</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A survey of clinicians on the use of artificial intelligence in ophthalmology, dermatology, radiology and radiation oncology</article-title>
          <source>Sci Rep</source>
          <year>2021</year>
          <month>03</month>
          <day>04</day>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>5193</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-021-84698-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-021-84698-5</pub-id>
          <pub-id pub-id-type="medline">33664367</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-021-84698-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7933437</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>Eschert</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Schwendicke</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Krois</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bohner</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Vinayahalingam</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hanisch</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A Survey on the Use of Artificial Intelligence by Clinicians in Dentistry and Oral and Maxillofacial Surgery</article-title>
          <source>Medicina (Kaunas)</source>
          <year>2022</year>
          <month>08</month>
          <day>05</day>
          <volume>58</volume>
          <issue>8</issue>
          <fpage>1059</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=medicina58081059"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/medicina58081059</pub-id>
          <pub-id pub-id-type="medline">36013526</pub-id>
          <pub-id pub-id-type="pii">medicina58081059</pub-id>
          <pub-id pub-id-type="pmcid">PMC9412897</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
