<?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">v10i1e34038</article-id>
      <article-id pub-id-type="pmid">35084352</article-id>
      <article-id pub-id-type="doi">10.2196/34038</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Technology-Enabled, Evidence-Driven, and Patient-Centered: The Way Forward for Regulating Software as a Medical Device</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>Burns</surname>
            <given-names>Michael</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Tomar</surname>
            <given-names>Ayush</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Carolan</surname>
            <given-names>Jane Elizabeth</given-names>
          </name>
          <degrees>BMedSc, MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Institute of Health Informatics</institution>
            <institution>University College London</institution>
            <addr-line>Gower Street</addr-line>
            <addr-line>London, WC1E 6BT</addr-line>
            <country>United Kingdom</country>
            <phone>44 07464345635</phone>
            <email>j.carolan@ucl.ac.uk</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1270-1774</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>McGonigle</surname>
            <given-names>John</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6670-8181</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Dennis</surname>
            <given-names>Andrea</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-0152-6528</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Lorgelly</surname>
            <given-names>Paula</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8990-9514</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Banerjee</surname>
            <given-names>Amitava</given-names>
          </name>
          <degrees>MA, MPH, DPhil</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8741-3411</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Institute of Health Informatics</institution>
        <institution>University College London</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Institute of Epidemiology and Health Care</institution>
        <institution>University College London</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Perspectum Ltd</institution>
        <addr-line>Oxford</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>University College London Hospitals NHS Foundation Trust</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Barts Health NHS Trust</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Jane Elizabeth Carolan <email>j.carolan@ucl.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>1</month>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>27</day>
        <month>1</month>
        <year>2022</year>
      </pub-date>
      <volume>10</volume>
      <issue>1</issue>
      <elocation-id>e34038</elocation-id>
      <history>
        <date date-type="received">
          <day>4</day>
          <month>10</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>14</day>
          <month>11</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>4</day>
          <month>12</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Jane Elizabeth Carolan, John McGonigle, Andrea Dennis, Paula Lorgelly, Amitava Banerjee. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 27.01.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/1/e34038" xlink:type="simple"/>
      <abstract>
        <p>Artificial intelligence (AI) is a broad discipline that aims to understand and design systems that display properties of intelligence. Machine learning (ML) is a subset of AI that describes how algorithms and models can assist computer systems in progressively improving their performance. In health care, an increasingly common application of AI/ML is software as a medical device (SaMD), which has the intention to diagnose, treat, cure, mitigate, or prevent disease. AI/ML includes either “locked” or “continuous learning” algorithms. Locked algorithms consistently provide the same output for a particular input. Conversely, continuous learning algorithms, in their infancy in terms of SaMD, modify in real-time based on incoming real-world data, without controlled software version releases. This continuous learning has the potential to better handle local population characteristics, but with the risk of reinforcing existing structural biases. Continuous learning algorithms pose the greatest regulatory complexity, requiring seemingly continuous oversight in the form of special controls to ensure ongoing safety and effectiveness. We describe the challenges of continuous learning algorithms, then highlight the new evidence standards and frameworks under development, and discuss the need for stakeholder engagement. The paper concludes with 2 key steps that regulators need to address in order to optimize and realize the benefits of SaMD: first, international standards and guiding principles addressing the uniqueness of SaMD with a continuous learning algorithm are required and second, throughout the product life cycle and appropriate to the SaMD risk classification, there needs to be continuous communication between regulators, developers, and SaMD end users to ensure vigilance and an accurate understanding of the technology.</p>
      </abstract>
      <kwd-group>
        <kwd>Artificial intelligence</kwd>
        <kwd>machine learning</kwd>
        <kwd>algorithm</kwd>
        <kwd>software</kwd>
        <kwd>risk assessment</kwd>
        <kwd>informatics</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Artificial intelligence (AI) is a broad discipline that aims to understand and design systems that display properties of intelligence [<xref ref-type="bibr" rid="ref1">1</xref>]. Machine learning (ML) is a subset of AI that describes how algorithms and models can assist computer systems in progressively improving their performance [<xref ref-type="bibr" rid="ref2">2</xref>]. Based on publicly available information, in late September 2021, the US Food and Drug Administration (FDA) listed (noting “initial list” only) 343 AI/ML-enabled medical devices marketed in the United States. In health care, an increasingly common application of AI and ML is software as a medical device (SaMD), which has the intention to diagnose, treat, cure, mitigate, or prevent disease [<xref ref-type="bibr" rid="ref3">3</xref>]. Regulatory frameworks for SaMD need to be adaptive while prioritizing patient safety and effectiveness [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. Regulatory challenges of SaMD include processing submitted evidence to verify clinical effectiveness, generalizability, interoperability, data integrity, and data security. Constructing a fit-for-purpose regulatory framework for SaMD with a continuous learning algorithm is an added complexity. As regulatory agencies aim to advance health care delivery through SaMD adoption, with efforts to avoid unintended consequences, this commentary summarizes the current regulatory frameworks for SaMD. First, we describe the challenges of continuous learning algorithms, then highlight the new evidence standards and frameworks under development, and discuss the need for stakeholder engagement, concluding with 2 key steps that regulators need to address in order to optimize and realize the many benefits of SaMD.</p>
    </sec>
    <sec>
      <title>Technology-Enabled Algorithms</title>
      <p>ML techniques incorporate training, validation, and test data sets at different stages of model development. Algorithms are executed in a training data set and results compared with a target value. Parameters of the model are adjusted accordingly as part of this process. Identifying potential data biases (including age, ethnicity, vendor, disease prevalence) is critical, but not limited to this point. At the validation stage, the fitted model is used to predict responses for observations in the validation data set, a process of fine-tuning the model. In the test stage, the ML model is exposed to a test data set, independent of training or validation data sets, providing unbiased evaluation of the final model. AI/ML includes either “locked” or “continuous learning” algorithms. Locked algorithms consistently provide the same output for a particular input. Such algorithms may be modified to optimize performance, requiring “episodic” regulatory review if the algorithm requires additional inputs or changes in intended use or performance. Continuous learning algorithms, in their infancy in terms of SaMD, modify in real-time based on incoming real-world data, without controlled software version releases. Continuous learning algorithms pose the greatest regulatory complexity, requiring seemingly continuous oversight in the form of special controls to ensure ongoing safety and effectiveness.</p>
      <p>Although systems with continuous learning may appear conceptually similar to systems that self-calibrate to the local environment (eg, adapting to temperature), continuous learning algorithms using modern ML techniques are qualitatively different in that portions of their algorithms, in the form of their trained networks, are being modified autonomously. This continuous learning has the potential to better handle local population characteristics, but with the risk of reinforcing existing structural biases, potentially without adequate oversight. Thus, special regulations are needed to classify these risks and accordingly, ensure appropriate human oversight.</p>
    </sec>
    <sec>
      <title>Frameworks and Standards for the Future</title>
      <p>Medical device regulatory agencies such as the US FDA, EU Notified Bodies, and the UK Medicines and Healthcare products Regulatory Agency (MHRA) have responsibility for protecting public health by only enabling market access for safe and effective products. Further down the line, importantly, health care budget holders then need to assess cost-effectiveness and budget impact, a potential rate-limiting step for successful market access. Lessons on successful AI/ML adoption in other industries are limited in their value given the unique health risks and benefits that health care regulators must assess. To verify claims of safety and effectiveness in the form of submitted evidence, regulators must keep pace with the complexity of algorithm models, including validation and testing stages, selected use of software of unknown pedigree, and real-world performance [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>The FDA has outlined its proposed framework for SaMD in a total product life cycle approach [<xref ref-type="bibr" rid="ref4">4</xref>] and released an AI/ML-based SaMD action plan [<xref ref-type="bibr" rid="ref8">8</xref>] in response to stakeholder feedback. At the premarket submission stage, a predetermined change control plan would play a role in obtaining reasonable assurance of safety and effectiveness: developers would stipulate what anticipated algorithm modifications would occur, and how the algorithm would learn and change without compromising safety or performance. Postmarket access, periodic updates to the FDA on changes to the algorithm to enable ongoing oversight of real-world performance would be provided. Early next year, draft guidance on detailed requirements is anticipated; currently, it is not evident how much oversight should be performed by the end user(s) and manufacturer, nor how much robust data are needed to substantiate safety and effectiveness claims.</p>
      <p>To promote rigor and transparency in design and reporting of AI-based interventions (underpinning regulatory submission evidence claims), reporting guidelines and checklists include Consolidated Standards of Reporting Trials–Artificial Intelligence (CONSORT-AI), Standard Protocol Items: Recommendations for Interventional Trials–Artificial Intelligence (SPIRIT-AI), The Transparent Reporting of a multivariable prediction model of Individual Prognosis Or Diagnosis-Artificial Intelligence (TRIPOD-AI), and Minimum Information About Clinical Artificial Intelligence Modeling (MI-CLAIM) [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. In the UK, the National Institute for Health and Care Excellence (NICE) has also released revised evidence standards for digital health technologies [<xref ref-type="bibr" rid="ref11">11</xref>]. Currently, there is an absence of tailored frameworks for AI/ML-based SaMD with a continuous learning algorithm; guidelines including MI-CLAIM and NICE’s evidence standards framework, while valuable for locked algorithms, note that continuous learning algorithms are beyond their scope.</p>
      <p>Globally, the International Medical Device Regulators Federation (IMDRF) aims to accelerate medical device international regulatory harmonization and has drafted key SaMD policies to complement existing international standards, particularly in terms of risk classification, converging terminology, a risk-based framework, and quality management systems. The Institute of Electrical and Electronic Engineers (IEEE) has Artificial Intelligence Medical Device Working Groups on terminology and recommended practice for the quality management of data sets. United Nations agency collaboration between the World Health Organization and the International Telecommunication Union: Focus Group on Artificial Intelligence for Health (FG-AI4H) was established to use AI to advance health care for all, and to benchmark AI models using secure and confidential, globally representative data sets [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
    </sec>
    <sec>
      <title>The Need for Stakeholder Engagement</title>
      <p>It is recognized that patient-centered data and engagement play a fundamental role in regulatory assessment of SaMD. The “patient-centered” approach referred to by the FDA addresses usability, equity, trust, and accountability. Engagement with both developers and end users occurred at a February 2020 Public Workshop on the Evolving Role of Artificial Intelligence in Radiological Imaging. At the latter event, The American College of Radiology (ACR) and Radiological Society of North America (RSNA) questioned [<xref ref-type="bibr" rid="ref13">13</xref>] the ability of the FDA to ensure safety and effectiveness of continuous learning algorithms, without direct physician or expert oversight during each use. Familiar concerns relate to autonomous image interpretation independent of physician confirmation and oversight. If an algorithm ceases to function properly without radiologist oversight, a significant number of patients are at risk of incorrect screening before algorithm failure is recognized. It was noted that algorithm user manuals must have clear guidance regarding which equipment and protocols are supported, and deployment restricted to those settings studied during validation. Evaluation of real-world algorithm performance will reassure patients and health professionals of readiness for clinical use.</p>
    </sec>
    <sec>
      <title>Conclusion</title>
      <p>SaMD has great potential to improve health and health care at individual and system levels. To optimize on the benefits associated with SaMD, patient safety and effectiveness need to be aptly assessed for which 2 key steps are necessary. First, international standards and guiding principles addressing the uniqueness of SaMD with a continuous learning algorithm are required [<xref ref-type="bibr" rid="ref14">14</xref>], outlining best practice oversight and reporting requirements. Aligned regulatory requirements, tailor-made for SaMD with a continuous learning algorithm, are essential, particularly to verify maintenance measures to keep in check modifications throughout the life cycle of SaMD. A special registry dedicated to these technologies may also be appropriate. Depending on the degree of risk to patients from a particular application of AI/ML SaMD, a degree of expert clinical oversight coupled with technology industry/developer assurance is likely to be required. Second, throughout the product life cycle, appropriate to the risk classification of the SaMD product, there needs to be continuous communication between regulators, developers, and SaMD end users to ensure vigilance and an accurate understanding of the technology. The latter will facilitate the adoption of state-of-the-art automation, optimizing clinical effectiveness and ensuring patient safety.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">ACR</term>
          <def>
            <p>American College of Radiology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CONSORT-AI</term>
          <def>
            <p>Consolidated Standards of Reporting Trials–Artificial Intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FDA</term>
          <def>
            <p>the US Food and Drug Administration</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">FG-AI4H</term>
          <def>
            <p>Focus Group on Artificial Intelligence for Health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">IEEE</term>
          <def>
            <p>Institute of Electrical and Electronic Engineers</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">IMDRF</term>
          <def>
            <p>International Medical Device Regulators Federation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">MHRA</term>
          <def>
            <p>the UK Medicines and Healthcare products Regulatory Agency</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">MI-CLAIM</term>
          <def>
            <p>Minimum Information About Clinical Artificial Intelligence Modeling</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">ML</term>
          <def>
            <p>machine learning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">NICE</term>
          <def>
            <p>National Institute for Health and Care Excellence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">RSNA</term>
          <def>
            <p>Radiological Society of North America</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">SaMD</term>
          <def>
            <p>software as a medical device</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">SPIRIT-AI</term>
          <def>
            <p>Standard Protocol Items: Recommendations for Interventional Trials–Artificial Intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">TRIPOD-AI</term>
          <def>
            <p>The Transparent Reporting of a multivariable prediction model of Individual Prognosis Or Diagnosis- Artificial Intelligence</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="con">
        <p>JC was responsible for research concept, literature search, specialist engagement, initial draft, revisions, and final draft; JMG took care of specialist input, review, and editing; AD performed review and editing; PL performed review and editing; and AB was responsible for supervision, revisions, and final draft.</p>
      </fn>
      <fn fn-type="conflict">
        <p>JC is employed by University College London (UCL) based at Perspectum Ltd through an Innovate UK grant: Knowledge Transfer Partnership (KTP). AB and PL receive research funding from the Perspectum/Innovate UK grant. AD and JMG are employees of Perspectum Ltd.</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>Panch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Szolovits</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Atun</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence, machine learning and health systems</article-title>
          <source>J Glob Health</source>
          <year>2018</year>
          <month>12</month>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>020303</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.7189/jogh.08.020303"/>
          </comment>
          <pub-id pub-id-type="doi">10.7189/jogh.08.020303</pub-id>
          <pub-id pub-id-type="medline">30405904</pub-id>
          <pub-id pub-id-type="pii">jogh-08-020303</pub-id>
          <pub-id pub-id-type="pmcid">PMC6199467</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>Chen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Banerjee</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Machine learning: a long way from implementation in cardiovascular disease</article-title>
          <source>Heart</source>
          <year>2020</year>
          <month>03</month>
          <volume>106</volume>
          <issue>5</issue>
          <fpage>318</fpage>
          <lpage>320</lpage>
          <pub-id pub-id-type="doi">10.1136/heartjnl-2019-316030</pub-id>
          <pub-id pub-id-type="medline">31911505</pub-id>
          <pub-id pub-id-type="pii">heartjnl-2019-316030</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>IMDRF SaMD Working Group</collab>
          </person-group>
          <source>Software as a Medical Device (SaMD): Key Definitions</source>
          <year>2013</year>
          <access-date>2020-09-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.imdrf.org/docs/imdrf/final/technical/imdrf-tech-131209-samd-key-definitions.pdf">http://www.imdrf.org/docs/imdrf/final/technical/imdrf-tech-131209-samd-key-definitions.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>US Food and Drug Administration</collab>
          </person-group>
          <source>Artificial Intelligence and Machine Learning in Software as a Medical Device</source>
          <year>2019</year>
          <access-date>2022-01-18</access-date>
          <publisher-loc>White Oak, MD</publisher-loc>
          <publisher-name>US Food and Drug Administration</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-and-machine-learning-software-medical-device">https://tinyurl.com/49w63ey6</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Turpin</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hoefer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lewelling</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Baird</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>Machine Learning AI in Medical Devices: Adapting Regulatory Frameworks and Standards to Ensure Safety and Performance</source>
          <year>2020</year>
          <access-date>2022-01-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bsigroup.com/globalassets/meddev/localfiles/fr-fr/whitepapers/md---machine_learning_ai_in_medical_devices.pdf">https://tinyurl.com/49w63ey6</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>No authors listed</collab>
          </person-group>
          <article-title>Machine learning and artificial intelligence research for patient benefit: 20 critical questions on transparency, replicability, ethics, and effectiveness</article-title>
          <source>BMJ</source>
          <year>2020</year>
          <month>04</month>
          <day>01</day>
          <volume>369</volume>
          <fpage>m1312</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=32238345"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.m1312</pub-id>
          <pub-id pub-id-type="medline">32238345</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>US Food and Drug Administration</collab>
          </person-group>
          <source>Developing a Software Precertification Program: A Working Model</source>
          <year>2019</year>
          <access-date>2022-01-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/downloads/MedicalDevices/DigitalHealth/DigitalHealthPreCertProgram/UCM629276.pdf">https://www.fda.gov/downloads/MedicalDevices/DigitalHealth/DigitalHealthPreCertProgram/UCM629276.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Center for Devices and Radiological Health</collab>
          </person-group>
          <source>Artificial Intelligence/Machine Learning (AI/ML)- Based Software as a Medical Device (SaMD) Action Plan</source>
          <year>2021</year>
          <month>1</month>
          <access-date>2021-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-and-machine-learning-software-medical-device">https://tinyurl.com/49w63ey6</ext-link>
          </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>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cruz Rivera</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Calvert</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Denniston</surname>
              <given-names>AK</given-names>
            </name>
            <collab>SPIRIT-AICONSORT-AI Working Group</collab>
          </person-group>
          <article-title>Reporting guidelines for clinical trial reports for interventions involving artificial intelligence: the CONSORT-AI extension</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>09</month>
          <volume>26</volume>
          <issue>9</issue>
          <fpage>1364</fpage>
          <lpage>1374</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32908283"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-020-1034-x</pub-id>
          <pub-id pub-id-type="medline">32908283</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-020-1034-x</pub-id>
          <pub-id pub-id-type="pmcid">PMC7598943</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>Norgeot</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Quer</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Beaulieu-Jones</surname>
              <given-names>BK</given-names>
            </name>
            <name name-style="western">
              <surname>Torkamani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dias</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gianfrancesco</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Arnaout</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kohane</surname>
              <given-names>IS</given-names>
            </name>
            <name name-style="western">
              <surname>Saria</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Butte</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Minimum information about clinical artificial intelligence modeling: the MI-CLAIM checklist</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>09</month>
          <day>09</day>
          <volume>26</volume>
          <issue>9</issue>
          <fpage>1320</fpage>
          <lpage>1324</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32908275"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-020-1041-y</pub-id>
          <pub-id pub-id-type="medline">32908275</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-020-1041-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC7538196</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>Unsworth</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Dillon</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Collinson</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Salmon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Oladapo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ayiku</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Shield</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Holden</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Greaves</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tonnel</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The NICE Evidence Standards Framework for digital health and care technologies - Developing and maintaining an innovative evidence framework with global impact</article-title>
          <source>Digit Health</source>
          <year>2021</year>
          <month>06</month>
          <day>24</day>
          <volume>7</volume>
          <fpage>20552076211018617</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/20552076211018617?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub%3dpubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/20552076211018617</pub-id>
          <pub-id pub-id-type="medline">34249371</pub-id>
          <pub-id pub-id-type="pii">10.1177_20552076211018617</pub-id>
          <pub-id pub-id-type="pmcid">PMC8236783</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>Wiegand</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnamurthy</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuglitsch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Pujari</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Salathé</surname>
              <given-names>Marcel</given-names>
            </name>
            <name name-style="western">
              <surname>Wenzel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>WHO and ITU establish benchmarking process for artificial intelligence in health</article-title>
          <source>Lancet</source>
          <year>2019</year>
          <month>07</month>
          <day>06</day>
          <volume>394</volume>
          <issue>10192</issue>
          <fpage>9</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(19)30762-7</pub-id>
          <pub-id pub-id-type="medline">30935732</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(19)30762-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fleishon</surname>
              <given-names>HB</given-names>
            </name>
            <name name-style="western">
              <surname>Haffy</surname>
              <given-names>BG</given-names>
            </name>
          </person-group>
          <source>Public Workshop - Evolving Role of Artificial Intelligence in Radiological Imaging, Comments of the American College of Radiology</source>
          <year>2020</year>
          <month>6</month>
          <day>30</day>
          <access-date>2020-07-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acr.org/Advocacy-and-Economics/Advocacy-News/Advocacy-News-Issues/In-the-July-4-2020-Issue/ACR-and-RSNA-Highlight-Challenges-to-Future-FDA-Oversight-of-Autonomous-AI">https://tinyurl.com/2p8p76ym</ext-link>
          </comment>
        </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>Gilbert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fenech</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hirsch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Upadhyay</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Biasiucci</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Starlinger</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Algorithm Change Protocols in the Regulation of Adaptive Machine Learning-Based Medical Devices</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>10</month>
          <day>26</day>
          <volume>23</volume>
          <issue>10</issue>
          <fpage>e30545</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/10/e30545/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/30545</pub-id>
          <pub-id pub-id-type="medline">34697010</pub-id>
          <pub-id pub-id-type="pii">v23i10e30545</pub-id>
          <pub-id pub-id-type="pmcid">PMC8579211</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
