<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v28i1e96152</article-id>
      <article-id pub-id-type="pmid">42372265</article-id>
      <article-id pub-id-type="doi">10.2196/96152</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>A Futures Framework for Clinical AI Governance: Anticipating Emerging Risks, Shifting Roles, and Regulatory Challenges</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kristóf</surname>
            <given-names>Tamás</given-names>
          </name>
        </contrib>
        <contrib contrib-type="editor">
          <name>
            <surname>Mesko</surname>
            <given-names>Bertalan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Asadollahi</surname>
            <given-names>Ali</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Izadi</surname>
            <given-names>Reyhane</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Yang</surname>
            <given-names>Yi</given-names>
          </name>
          <degrees>MBA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0005-2923-5510</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Jialin</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Information Center</institution>
            <institution>West China Hospital of Sichuan University</institution>
            <addr-line>No 37 Guo Xue Xiang Street</addr-line>
            <addr-line>Chengdu, Sichuan, 610041</addr-line>
            <country>China</country>
            <phone>86 2885422416</phone>
            <email>dljl8@163.com</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-1369-4625</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Siru</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5003-5354</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Information Center</institution>
        <institution>West China Hospital of Sichuan University</institution>
        <addr-line>Chengdu, Sichuan</addr-line>
        <country>China</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Otolaryngology-Head and Neck Surgery</institution>
        <institution>West China Hospital of Sichuan University</institution>
        <addr-line>Chengdu, Sichuan</addr-line>
        <country>China</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Department  of Medical Informatics</institution>
        <institution>West China Medical School of Sichuan University</institution>
        <addr-line>Chengdu, Sichuan</addr-line>
        <country>China</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Biomedical Informatics</institution>
        <institution>Vanderbilt University Medical Center</institution>
        <addr-line>Nashville, TN</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Jialin Liu <email>dljl8@163.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>29</day>
        <month>6</month>
        <year>2026</year>
      </pub-date>
      <volume>28</volume>
      <elocation-id>e96152</elocation-id>
      <history>
        <date date-type="received">
          <day>26</day>
          <month>3</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>20</day>
          <month>5</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>25</day>
          <month>5</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>29</day>
          <month>5</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Yi Yang, Jialin Liu, Siru Liu. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 29.06.2026.</copyright-statement>
      <copyright-year>2026</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2026/1/e96152" xlink:type="simple"/>
      <abstract>
        <p>This viewpoint develops the futures framework for clinical artificial intelligence governance (FF-CAIG), a conceptual and anticipatory framework for organizing emerging governance challenges in clinical artificial intelligence (AI). Although life cycle–oriented oversight is increasingly reflected in clinical AI regulation and institutional governance, existing approaches remain more developed for near-term validation, current-state assurance, and retrospective risk detection than for longer-horizon sociotechnical change. This gap is increasingly relevant, as AI systems become more complex, adaptive, and autonomous, and as they become more deeply embedded in care relationships and accountability structures. FF-CAIG is grounded in 3 futures methodologies: the 3 horizons model, scenario planning, and causal layered analysis. It is operationalized through an emerging clinical AI risk taxonomy that links these methods to governance domains. Its practical outputs include horizon classification, risk-domain mapping, scenario stress-testing findings, accountability-chain mapping, and horizon-scaled minimum governance actions for deployment or continued use. Applied across near-term, transitional, and longer-term horizons, the framework proposes cross-horizon priorities, including stronger predeployment equity evaluation, clearer life cycle accountability, clinician AI oversight competencies, and safeguards for increasingly autonomous or AI-mediated care systems. We illustrate FF-CAIG through 3 representative clinical AI deployment patterns and discuss its limitations, including differential compliance burdens, risks of overdocumentation, variable feasibility across jurisdictions, and the need for empirical validation. FF-CAIG is intended not as a prescriptive policy instrument or validated assessment tool, but as a structured analytic approach for regulators, health system leaders, developers, and researchers seeking prospective and systems-oriented approaches to clinical AI governance.</p>
      </abstract>
      <kwd-group>
        <kwd>clinical AI</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>clinical AI governance</kwd>
        <kwd>futures studies</kwd>
        <kwd>strategic foresight</kwd>
        <kwd>health regulation</kwd>
        <kwd>clinical workforce</kwd>
        <kwd>emerging risks</kwd>
        <kwd>digital health policy</kwd>
        <kwd>artificial intelligence governance</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Clinical artificial intelligence (AI) has moved beyond controlled validation settings into routine deployment, supporting risk stratification, documentation, patient communication, and emerging decision support across care settings [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. Regulatory oversight of imaging algorithms, predictive models, and other AI-enabled medical products has also expanded through evolving US Food and Drug Administration (FDA) and European Union frameworks [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Although clinical AI governance increasingly incorporates life cycle–oriented elements, including postmarket monitoring and change-management expectations, much oversight remains more mature for near-term assurance and recognized risk signals than for longer-horizon sociotechnical change. Existing approaches, including institutional ethics oversight, regulatory approval pathways, and industry guidance, still focus primarily on risks such as bias, privacy breaches, performance degradation, and safety events that can be specified, monitored, or retrospectively detected [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>This orientation is increasingly challenged by the iterative, updateable, and cross-functional nature of advanced clinical AI [<xref ref-type="bibr" rid="ref8">8</xref>]. Recent regulatory developments, including the FDA’s life cycle–focused guidance for AI-enabled device software functions and the EU AI Act’s postmarket obligations for high-risk systems, indicate that clinical AI governance is no longer limited to static premarket approval [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. The remaining gap is more specific: current life cycle–oriented approaches are better developed for planned or bounded change, defined postmarket obligations, and measurable performance signals than for evolving clinical functions, foundation model–based tools, distributed accountability, and relational effects that may shift across contexts and over time. In health care, this challenge is especially consequential because safety, accountability, and trust depend not only on model performance but also on role clarity, implementation quality, and institutional capacity to detect and respond to change [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>The governance challenge posed by clinical AI is therefore not only technical but also temporal. Although regulators and health systems increasingly recognize the need for life cycle oversight, existing mechanisms still depend substantially on foreseeable changes, measurable postdeployment signals, and recognized failure modes. Clinical AI is evolving in ways that may generate governance problems before they are fully captured by conventional postdeployment oversight [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Some risks may emerge gradually, including clinician overreliance, rising verification burden, workflow dependence, and fragmentation of governance across institutions and jurisdictions [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Generative AI systems used for longitudinal communication, coordination, or triage may also reshape patient-clinician relationships in ways that existing frameworks for consent, accountability, and duty of care do not fully anticipate [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. This concern is increasingly recognized in international guidance, including recent World Health Organization work on large multimodal models in health [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
      <p>Futures studies provide a systematic but underused set of approaches for anticipating long-term change and emerging uncertainty [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. Although organizations such as the Organisation for Economic Co-operation and Development and World Health Organization have identified horizon scanning and scenario analysis as valuable governance tools under conditions of rapid change [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>], these methods have not been systematically integrated into clinical AI governance. As a result, longer-horizon concerns, including systemic dependency, workforce disruption, and regulatory obsolescence, often remain secondary to current-state compliance and near-term risk mitigation [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Existing frameworks provide important foundations, but they offer limited operational guidance for anticipating risks that may emerge beyond conventional life cycle monitoring, compliance assessment, or management-system processes. The futures framework for clinical artificial intelligence governance (FF-CAIG) addresses this gap by integrating futures methods with clinical AI governance.</p>
      <p>In this viewpoint, we introduce FF-CAIG, grounded in core futures methodologies [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>] and centered on patient safety and health equity as foundational principles [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. The framework addresses 3 interconnected domains: emerging systemic and clinical risks, evolving stakeholder roles across the care ecosystem, and regulatory responses that can better keep pace with technological change. FF-CAIG is designed to be prospective, adaptive, and applicable across organizational governance, regulatory policy, and clinical practice. FF-CAIG is intended for clinical AI systems whose deployment may create clinically, organizationally, ethically, or relationally consequential governance challenges. Its scope includes high-risk clinical decision-support systems, foundation model–based clinical tools, patient-facing communication or triage systems, and administrative or documentation tools that meet this threshold. It is not intended for low-impact administrative automation with no plausible effect on clinical decisions, patient-facing communication, safety, equity, or professional accountability; governance intensity should scale with autonomy, clinical consequences, deployment context, and horizon classification. We argue that it offers both a conceptual contribution to health informatics scholarship and a practical tool for regulators, health system leaders, professional bodies, and clinical AI developers seeking more anticipatory clinical AI governance under technological uncertainty.</p>
      <p>FF-CAIG is not intended as a simple aggregation of established foresight methods. Rather, it is designed as an integrated governance framework in which each component addresses a distinct limitation of oversight models that primarily emphasize current-state performance, compliance, and post hoc risk management in clinical AI [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. These 3 methods were selected because they address complementary needs in anticipatory clinical AI governance. The three horizons (3H) model supports temporal classification of risks across near-term, transitional, and longer-term phases; scenario planning stress-tests governance priorities under regulatory and institutional uncertainty; and causal layered analysis (CLA) examines the structural assumptions, professional role expectations, institutional incentives, and cultural narratives that shape which risks are recognized and how they are governed [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. Other approaches remain useful for adjacent governance functions: horizon scanning can support evidence gathering, Delphi consensus can support expert agreement, technology road mapping can support implementation planning, risk matrices can support risk scoring, and safety-case methods can support assurance documentation. However, no single method by itself connects temporal transition, policy robustness, and deeper sociotechnical analysis in a way that directly supports clinical AI governance. FF-CAIG integrates these functions into a single analytic framework (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>FF-CAIG: integrated analytical cycle for clinical AI governance. AI: artificial intelligence; FF-CAIG: futures framework for clinical artificial intelligence governance.</p>
        </caption>
        <graphic xlink:href="jmir_v28i1e96152_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec>
      <title>The Limitations of Present-Oriented Clinical AI Governance</title>
      <sec>
        <title>Overview</title>
        <p>Current approaches to clinical AI governance are increasingly incorporating life cycle–oriented elements, including postmarket monitoring, change-control planning, and ongoing obligations for high-risk AI systems [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. These developments are important and should not be characterized as purely static or reactive. However, most frameworks remain more developed for current-state evaluation, foreseeable updates, and retrospective risk detection than for anticipating longer-horizon changes in clinical roles, institutional accountability, patient relationships, and regulatory adaptation [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. This creates a growing mismatch with the dynamic, distributed, and sociotechnical character of clinical AI in practice.</p>
      </sec>
      <sec>
        <title>Static Approval Models for Dynamic Systems</title>
        <p>A central limitation of existing governance frameworks is their reliance on approval models developed for relatively stable technologies, structured around defined intended use, bounded functionality, and evaluation at discrete time points [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Although this remains useful for narrow and well-characterized applications, it is increasingly strained when applied to updateable, adaptive, or implementation-sensitive AI systems [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. The FDA’s predetermined change control plan framework is an important advance because it recognizes that AI-enabled device software may change after authorization [<xref ref-type="bibr" rid="ref9">9</xref>]. However, it remains primarily oriented toward planned and bounded change, making it less well suited to emergent behavioral shifts in foundation model–based systems or layered AI ecosystems shaped by model revision and local implementation [<xref ref-type="bibr" rid="ref24">24</xref>]. In parallel, the European Union’s AI governance architecture introduces conformity assessment and postmarket obligations for high-risk systems [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>], but practical questions remain about defining material change, monitoring continuously updated systems, and allocating ongoing oversight responsibility.</p>
      </sec>
      <sec>
        <title>Postmarket Surveillance Gaps</title>
        <p>A further limitation concerns how postdeployment harms are detected. Conventional postmarket surveillance was designed around discrete, reportable adverse events; yet, the performance of clinical AI may erode gradually as data, populations, and workflows shift after deployment [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Episodic, incident-triggered reporting is therefore poorly suited to detecting progressive deterioration, which may persist for an extended period before surfacing as an identifiable safety signal [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. As clinical AI becomes more embedded in routine care, governance will need to move beyond incident reporting toward continuous, context-sensitive, and performance-aware monitoring [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      </sec>
      <sec>
        <title>Accountability Fragmentation</title>
        <p>Clinical AI systems are increasingly developed, adapted, integrated, and configured by multiple actors across the system life cycle [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. This distributed architecture can make accountability difficult to locate within conventional governance and liability models, particularly when harm arises from interactions among model design, local implementation, workflow integration, and clinical use [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. This limitation creates the need for more explicit accountability allocation, which is addressed later as a core risk domain within FF-CAIG.</p>
      </sec>
      <sec>
        <title>Equity as a Core Governance Requirement</title>
        <p>Algorithmic bias is among the most widely recognized risks in clinical AI [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]; yet, equity is still often treated as secondary rather than as a core governance requirement [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. Existing frameworks rarely provide operational standards for subgroup performance reporting, proxy variable auditing, or postdeployment equity surveillance [<xref ref-type="bibr" rid="ref31">31</xref>]. The mechanisms and life cycle requirements of equity-oriented governance are examined later as a core risk domain within FF-CAIG; at this stage, the key point is that the absence of such standards leaves a structural gap that conventional oversight is poorly positioned to close. Taken together, these limitations expose a deeper mismatch between conventional oversight and the temporal, relational, and system-level nature of contemporary clinical AI.</p>
      </sec>
    </sec>
    <sec>
      <title>A Futures Methodology for Clinical AI Governance: The 3H Model</title>
      <sec>
        <title>Overview</title>
        <p>Among futures methods, the 3H model offers a useful way to analyze governance during system transition [<xref ref-type="bibr" rid="ref23">23</xref>]. Instead of treating change as a simple linear progression, it frames transformation as unfolding across 3 overlapping horizons. Horizon 1 (H1) is the currently dominant system, still operationally effective but increasingly marked by structural limitations. Horizon 2 (H2) is the transitional space in which emerging innovations, hybrid arrangements, and competing institutional logics begin to challenge H1 assumptions. Horizon 3 (H3) refers to longer-term system configurations whose values, structures, and practices may initially appear peripheral but can ultimately redefine the dominant order.</p>
      </sec>
      <sec>
        <title>Relevance to Clinical AI Governance</title>
        <p>Applied to clinical AI governance, the 3H model offers several advantages over linear forecasting. It recognizes that current governance structures will remain important even as their limitations become more visible, creates analytical space for examining transitional and longer-horizon challenges before they are fully realized [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>], and links technological change to shifts in professional roles, accountability structures, and care relationships [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. In this sense, the 3H model is not simply a way of organizing time but a framework for understanding how governance logics evolve during sociotechnical transition. This perspective is especially relevant in clinical AI. Recent developments, including the FDA’s predetermined change control plan guidance [<xref ref-type="bibr" rid="ref9">9</xref>] and the EU AI Act’s postmarket obligations [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>], represent important advances, but they do not eliminate the need for anticipatory governance [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. As clinical AI moves from relatively bounded tools toward more complex, layered, and adaptive ecosystems, governance assumptions may be challenged differently across successive horizons [<xref ref-type="bibr" rid="ref32">32</xref>]. <xref ref-type="table" rid="table1">Table 1</xref> applies the 3H model to clinical AI governance by organizing plausible conditions across near-term, transitional, and longer-term horizons.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Three horizons model applied to clinical artificial intelligence (AI) governance.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="150"/>
            <col width="250"/>
            <col width="280"/>
            <col width="320"/>
            <thead>
              <tr valign="top">
                <td>Domain</td>
                <td>Horizon 1: present system</td>
                <td>Horizon 2: transitional emergence</td>
                <td>Horizon 3: longer-term reconfiguration</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Temporal orientation</td>
                <td>Near term</td>
                <td>Transitional period</td>
                <td>Longer term</td>
              </tr>
              <tr valign="top">
                <td>Dominant paradigm</td>
                <td>Point-of-care AI tools, human-in-the-loop support, device-centered regulation</td>
                <td>Increasing task delegation, workflow-embedded foundation-model capabilities, and iterative system updates</td>
                <td>More autonomous, AI-mediated care infrastructures and cross-pathway coordination</td>
              </tr>
              <tr valign="top">
                <td>Primary governance challenge</td>
                <td>Premarket validation, transparency, bias and performance assessment, and fit within existing regulatory pathways</td>
                <td>Oversight of iteratively updated systems, layered accountability, workflow dependence, and role transition</td>
                <td>Responsibility, consent, disclosure, and professional accountability in low-human-intervention or AI-mediated care</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Governance Implications of the 3H Model</title>
        <p>Governance investments focused only on H1 realities, such as device classification, one-time approval logic, and narrow predeployment evaluation, may be insufficient for H2 conditions characterized by iterative updating, layered accountability, and partial delegation [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. They are even less suited to H3 settings in which clinical AI functions less as a bounded tool and more as a persistent mediating infrastructure across episodes of care [<xref ref-type="bibr" rid="ref32">32</xref>]. Governance should therefore be designed across all 3 horizons simultaneously, even when later horizons remain only partially formed [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. The 3H model thus reframes clinical AI governance as a problem of system transition rather than isolated product oversight. It helps regulators, health systems, and professional bodies identify where current mechanisms remain adequate, where hybrid approaches are needed, and where new forms of oversight may become necessary [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. The goal is not speculative prediction but anticipatory preparedness.</p>
      </sec>
    </sec>
    <sec>
      <title>An Emerging Risk Taxonomy for Clinical AI Governance</title>
      <sec>
        <title>Overview</title>
        <p>Drawing on a targeted narrative review and literature-informed conceptual synthesis of clinical AI governance literature, regulatory and policy documents, and analogous high-stakes AI domains, we identify 6 risk domains that warrant anticipatory attention in clinical AI governance (<xref ref-type="table" rid="table2">Table 2</xref>) [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. Because this paper is a viewpoint, FF-CAIG was developed through a structured synthesis rather than a preregistered protocol, formal expert consensus process, or empirical coding study. The synthesis involved targeted source review, identification of recurring governance concerns, iterative grouping into risk domains, mapping to futures methods, and assessment of links to practical governance outputs. Sources were prioritized when they addressed risks relevant to clinical decision-making, patient safety, institutional accountability, professional responsibility, equity, trust, or governance design, not technical performance alone. Recurring concerns were iteratively compared and grouped according to their dominant governance gap: technical reliability, structural accountability, or relational quality. Domains were retained when they were recurrent across sources, relevant to multiple stakeholders, applicable across different clinical AI deployment patterns, and linked to actionable governance responses. The taxonomy is intended to support anticipatory governance by distinguishing risks that are already visible, emerging, or likely to become more consequential over time. It is therefore presented as a viewpoint-based analytic framework, not as a systematic review–derived, empirically coded, or exhaustive classification.</p>
        <p>In this taxonomy, H1 denotes risks already observable in current clinical AI deployments; H2 denotes risks that become more consequential, as systems become iteratively updated, workflow-embedded, foundation model–based, or partially delegated; and H3 denotes longer-term risks associated with more autonomous, persistent, or AI-mediated care infrastructures.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Emerging risk taxonomy and horizon placement for clinical artificial intelligence (AI) governance.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="240"/>
            <col width="110"/>
            <col width="190"/>
            <col width="260"/>
            <thead>
              <tr valign="top">
                <td>Risk domain</td>
                <td>Illustrative manifestation</td>
                <td>Horizon (H)</td>
                <td>Governance gap</td>
                <td>Rationale for horizon placement</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Model drift and silent failure</td>
                <td>Model performance declines as populations, data pipelines, or workflows change</td>
                <td>H1-H2</td>
                <td>Inconsistent postmarket surveillance and drift response</td>
                <td>Already observable in current systems (H1); harder to detect, as systems become iterative and workflow-embedded (H2)</td>
              </tr>
              <tr valign="top">
                <td>Algorithmic equity amplification</td>
                <td>Nonrepresentative data lead to poorer performance for underserved groups</td>
                <td>H1-H3</td>
                <td>Limited equity auditing and subgroup performance standards</td>
                <td>Documented in current systems (H1); may scale with foundation models (H2); may become structurally embedded without life cycle equity governance (H3)</td>
              </tr>
              <tr valign="top">
                <td>Opacity and explainability</td>
                <td>Clinicians cannot explain AI recommendations or justify reliance on or overrides of AI outputs</td>
                <td>H1-H3</td>
                <td>Weak explainability, disclosure, and consent expectations</td>
                <td>Present in current tools (H1); intensified by foundation models (H2); more consequential, as AI mediates longitudinal care (H3)</td>
              </tr>
              <tr valign="top">
                <td>Agentic autonomy</td>
                <td>AI performs multistep tasks, such as triage or protocol execution, with limited real-time human review</td>
                <td>H2-H3</td>
                <td>Unclear oversight standards, autonomy thresholds, and escalation rules</td>
                <td>Primarily an emerging risk beyond most current human-supervised deployments; becomes more salient as delegation increases (H2-H3)</td>
              </tr>
              <tr valign="top">
                <td>Distributed liability</td>
                <td>Harm arises across developers, integrators, deployers, and clinicians without clear responsibility</td>
                <td>H1-H3</td>
                <td>Poor accountability allocation across sociotechnical systems</td>
                <td>Relatively clearer for bounded tools (H1); harder to assign, as multiactor and longitudinal workflows expand (H2-H3)</td>
              </tr>
              <tr valign="top">
                <td>AI-mediated care relationships</td>
                <td>Longitudinal AI tools reshape communication, trust, and continuity of care</td>
                <td>H2-H3</td>
                <td>Limited standards for relational quality, continuity, and access to human review</td>
                <td>Early forms are emerging in patient-facing tools (H2); consequences increase when AI persistently mediates care (H3)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Model Drift and Silent Failure</title>
        <p>As noted earlier, clinical AI may become less reliable after deployment, and this deterioration often develops gradually rather than as a discrete failure event. The result is the risk of silent failure: a system continues to operate within its nominal range while its clinical usefulness declines and the problem remains undetected [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Existing governance frameworks remain inconsistent in how they define drift, monitor performance change, or trigger remedial action [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. A prospective governance approach should therefore specify minimum standards for drift detection, reporting cadence, cohort-disaggregated monitoring, and response protocols that activate when clinically meaningful deterioration is detected [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      </sec>
      <sec>
        <title>Algorithmic Equity Amplification</title>
        <p>The risk that clinical AI may amplify existing inequities is well established [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. These inequities may arise through underrepresentation of historically marginalized groups in training data, proxy variables that encode racial or socioeconomic disadvantage [<xref ref-type="bibr" rid="ref30">30</xref>], and optimization targets that are misaligned with equity goals. They may also be reinforced by deployment contexts that concentrate advanced tools in already well-resourced institutions [<xref ref-type="bibr" rid="ref31">31</xref>]. As more general-purpose and foundation model–based systems are deployed across heterogeneous populations, these mechanisms may operate at greater scale and become harder to attribute [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. A futures-oriented governance approach should therefore move beyond documenting disparities after deployment and instead define minimum equity-governance requirements across the system life cycle.</p>
        <p>At minimum, high-impact clinical AI systems should undergo subgroup-disaggregated evaluation before deployment, periodic postdeployment reassessment after major updates or material workflow changes, and formal review and remediation planning when subgroup performance falls below prespecified, context-specific clinical acceptability thresholds [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. These thresholds should be defined prospectively according to the system’s intended clinical function, risk level, and potential consequences of error and may include minimum subgroup performance levels, calibration requirements, maximum allowable subgroup performance differences, and minimum sample-size or confidence requirements for reliable subgroup estimates. Governance should also specify which clinically relevant and equity-relevant subgroup variables are monitored, who is responsible for reviewing disparity signals, and what remedial actions are triggered when inequitable performance is detected. Remediation pathways should be proportionate to the severity and persistence of the disparity and may include governance review, root-cause analysis, enhanced human review, temporary restriction of use, recalibration, retraining, workflow redesign, revalidation, or suspension when safety or equity criteria are breached. In this framework, equity is not only an ethical principle but also an auditable governance function [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
      </sec>
      <sec>
        <title>Opacity and Explainability</title>
        <p>Foundation model–based and other complex clinical AI systems pose governance challenges that differ from those of more narrowly bounded tools because they often have broader capabilities, more variable downstream uses, and behaviors that are harder to characterize before deployment [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Under these conditions, clinicians may be unable to explain AI recommendations to patients, justify overrides in the medical record, or determine whether a model’s output reflects clinically relevant reasoning or spurious correlations [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. This creates governance pressure not only around technical explainability but also around disclosure, informed consent, documentation expectations, and professional accountability. Governance frameworks should therefore define minimum expectations for explainability proportional to clinical risk, including requirements for user-facing disclosure, justification of override or reliance in high-impact settings, and documentation standards for AI-supported decision-making [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>].</p>
      </sec>
      <sec>
        <title>Agentic Autonomy</title>
        <p>Increasingly, agentic clinical AI presents a major governance challenge on the medium- to longer-term horizon. These systems may support multistep activities such as triage, care coordination, chronic disease management, or protocolized follow-up [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. Although current deployments remain substantially human-supervised, ongoing development trajectories suggest that broader action spaces and more consequential forms of delegated decision support are likely to become more salient over the medium- to longer-term horizon [<xref ref-type="bibr" rid="ref32">32</xref>]. Existing governance frameworks do not clearly define how human oversight should scale with autonomy, what level of review remains meaningful, or how accountability should be allocated when AI-supported action contributes to patient harm [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Governance should therefore move beyond a simple human-in-the-loop requirement toward clearer standards for autonomy thresholds, escalation rules, and minimum conditions for meaningful human control [<xref ref-type="bibr" rid="ref36">36</xref>].</p>
      </sec>
      <sec>
        <title>Distributed Liability in Multicomponent Systems</title>
        <p>Accountability in clinical AI is difficult not only because some systems are opaque but also because responsibility is distributed across the development, integration, deployment, and use pathway [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Patient harm associated with AI-supported care may arise from model development, platform integration, local implementation, and downstream clinical oversight, without any single actor bearing sole responsibility [<xref ref-type="bibr" rid="ref17">17</xref>]. Conventional medical liability frameworks are poorly suited to this layered architecture. Accountability should therefore be addressed prospectively, with responsibilities specified before deployment and not only after harm occurs [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. One practical approach is to require accountability-chain documentation as a condition of deployment authorization [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. This documentation should identify the responsible actor for model development, integration, local validation, routine monitoring, incident review, user training, and authority to suspend use, together with handoff points between actors, reporting obligations, and escalation routes when clinically meaningful deterioration or harm is detected. In this way, accountability is translated from an abstract governance principle into a deployable institutional requirement.</p>
      </sec>
      <sec>
        <title>AI-Mediated Care Relationships</title>
        <p>Clinical AI may increasingly mediate communication, guidance, and continuity across patient journeys, particularly in navigation, triage, symptom support, and longitudinal follow-up [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. In these settings, governance concerns extend beyond safety and performance to the quality of AI-mediated relationships, including trust, continuity, dependence, and the conditions under which patients can access meaningful human interaction. Existing governance frameworks remain limited in how they address relational quality, continuity safeguards, or the risk that AI-mediated support may alter help-seeking, disclosure, or perceptions of professional care. Governance should therefore address not only what these systems do but also how they reshape communication and care relationships over time. Minimum safeguards may include clear disclosure of AI mediation, defined routes to human escalation, continuity protections for higher-risk or vulnerable patients, and review of relational impacts in longitudinal deployments.</p>
      </sec>
    </sec>
    <sec>
      <title>Shifting Roles Across the Clinical AI Governance Landscape</title>
      <sec>
        <title>Overview</title>
        <p>Futures methodology attends not only to technological change but also to the shifting human and institutional roles that accompany system transition. As clinical AI evolves across horizons, the roles of clinicians, patients, developers, operators, and regulators will also change, with direct governance consequences. Frameworks that fail to anticipate these shifts risk creating accountability gaps, competency mismatches, and consent structures that no longer reflect the actual distribution of agency in AI-enabled care.</p>
      </sec>
      <sec>
        <title>Clinicians: From Practitioners to AI Supervisors</title>
        <p>In H1 settings, the clinician’s role remains broadly recognizable: AI provides a recommendation, and the clinician accepts, modifies, or overrides it using independent professional judgment [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. As AI outputs become more numerous, complex, and time-sensitive, however, the conditions for meaningful oversight may erode, as earlier work on alert fatigue in clinical decision support suggests [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref38">38</xref>]. In H2 and beyond, the clinician’s role may shift from direct execution of care toward supervision of AI-enabled processes, requiring competencies not central to traditional clinical practice, including interpretation of outputs in light of known limitations, detection of behavioral drift, and communication of uncertainty to patients [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Current professional education and credentialing structures are not yet aligned with this shift [<xref ref-type="bibr" rid="ref40">40</xref>]. Governance should therefore recognize AI oversight competency as a core component of professional preparation, clinical privileging, and continuing education.</p>
      </sec>
      <sec>
        <title>Patients: From Recipients to Conavigators</title>
        <p>Patients have received less attention than clinicians or regulators in clinical AI governance, and in many current deployments, they remain passive recipients of AI-mediated recommendations, often without clear disclosure of AI involvement [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Informed consent frameworks also remain underdeveloped, with no settled standard for what patients should be told about AI’s role, limitations, or variable performance across populations [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. In longer-horizon settings, patients may interact directly and longitudinally with AI-enabled navigation, triage, or communication tools, raising governance questions about continuity, therapeutic alliance, the right to meaningful human contact, and the boundary between delegation and substitution [<xref ref-type="bibr" rid="ref43">43</xref>]. Patient rights in AI-mediated care should therefore be treated as a core governance domain rather than a narrow extension of disclosure requirements [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
      </sec>
      <sec>
        <title>Developers and Operators: From Innovators to Governors</title>
        <p>Clinical AI governance increasingly depends on the actions of developers and deployers well beyond model creation [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. The EU AI Act’s distinction between providers and deployers reflects this shift by assigning obligations to both those who place AI systems on the market and those who implement them in operational settings [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. In health care, governance must therefore extend across the deployment life cycle and not stop at technical development alone [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Developers should disclose key features of training data provenance, known performance limitations, and relevant subgroup performance where feasible [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. Deployers and operating institutions should document deployment context, local validation, monitoring procedures, and escalation mechanisms for clinically meaningful deterioration or adverse events [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. The governance principle is clear: stewardship responsibilities should follow the system through its life cycle rather than end at market entry [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      </sec>
      <sec>
        <title>Regulators: From Gatekeepers to Adaptive Stewards</title>
        <p>The traditional regulatory model, in which regulators primarily act as gatekeepers evaluating products against predefined standards [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>], is increasingly insufficient for systems whose behavior, use context, and organizational effects may change after deployment [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. A futures-oriented approach suggests that regulators will also need adaptive stewardship capacities, including monitoring population-level performance, updating expectations in response to postdeployment evidence, and convening multistakeholder processes when new governance issues emerge [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. International coordination will be especially important for systems operating across jurisdictions [<xref ref-type="bibr" rid="ref5">5</xref>], and bodies such as the International Medical Device Regulators Forum may provide useful mechanisms for convergence in classification, postmarket monitoring, and life cycle oversight of AI-enabled medical technologies [<xref ref-type="bibr" rid="ref44">44</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>Scenario Planning for Clinical AI Regulatory Design</title>
      <p>Scenario planning offers a useful method for exploring divergent futures without requiring deterministic prediction [<xref ref-type="bibr" rid="ref45">45</xref>]. It enables governance designers to examine how technological, institutional, and regulatory conditions may interact and to stress-test policies against a small number of coherent but meaningfully distinct scenarios without assuming a single expected trajectory [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      <sec>
        <title>Scenario Structure and Governance Logic</title>
        <p>In clinical AI governance, scenario planning is especially valuable because uncertainty arises not only from the pace of technological development but also from the coherence and adaptability of regulatory response [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. FF-CAIG uses 2 dimensions: the pace of clinical AI capability development, from incremental to rapid and broadly integrated, and the coherence of regulatory response, from fragmented and reactive to coordinated and anticipatory [<xref ref-type="bibr" rid="ref45">45</xref>]. On this basis, we focus on 3 analytically salient futures: governed acceleration, fragmented proliferation, and regulatory retrenchment (<xref ref-type="table" rid="table3">Table 3</xref>). The purpose is not to predict which future will occur, but to identify governance choices that remain robust across plausible trajectories [<xref ref-type="bibr" rid="ref45">45</xref>].</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Scenario matrix for clinical artificial intelligence (AI) regulatory futures.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="170"/>
            <col width="320"/>
            <col width="250"/>
            <col width="260"/>
            <thead>
              <tr valign="top">
                <td>Domain</td>
                <td>Scenario A: governed acceleration</td>
                <td>Scenario B: fragmented proliferation</td>
                <td>Scenario C: regulatory retrenchment</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Regulatory environment</td>
                <td>Adaptive and increasingly harmonized frameworks; stronger life cycle oversight and cross-jurisdictional alignment</td>
                <td>Patchwork regulation; inconsistent enforcement; uneven institutional governance capacity</td>
                <td>Postincident restriction, higher approval thresholds, and defensive compliance culture</td>
              </tr>
              <tr valign="top">
                <td>Clinician role</td>
                <td>AI oversight embedded in training, credentialing, and practice standards</td>
                <td>Variable expectations across specialties, settings, and resource levels</td>
                <td>Greater risk aversion; reduced willingness to rely on AI; increased documentation and liability burden</td>
              </tr>
              <tr valign="top">
                <td>Equity outcomes</td>
                <td>Equity integrated into validation, procurement, and postdeployment monitoring; routine subgroup reporting</td>
                <td>Benefits and monitoring concentrated in well-resourced institutions; disparities widen</td>
                <td>Formal equity attention may increase, but access gaps and structural inequities persist</td>
              </tr>
              <tr valign="top">
                <td>Innovation trajectory</td>
                <td>Trust-supported growth under clearer rules and accountability</td>
                <td>Rapid but uneven expansion outpaces governance and standardization</td>
                <td>Slower innovation; resources shift toward compliance, legal defense, and risk containment</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Scenario-Based Stress Testing for Governance Design</title>
        <sec>
          <title>Scenario A: Governed Acceleration</title>
          <p>In this pathway, innovation is matched by adaptive regulatory frameworks, stronger postdeployment monitoring, and greater alignment across institutions and jurisdictions [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Public trust is reinforced through transparency, accountability, and meaningful inclusion of clinician and patient perspectives [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. Equity is treated as a core implementation requirement rather than a secondary concern [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        </sec>
        <sec>
          <title>Scenario B: Fragmented Proliferation</title>
          <p>In this pathway, clinical AI capabilities expand while governance remains uneven across jurisdictions, organizations, and specialties [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Adoption proceeds rapidly but inconsistently, with safety protections, clinician support, and postmarket oversight varying by institutional resources and vendor practices [<xref ref-type="bibr" rid="ref8">8</xref>]. The likely result is a widening disparity in who benefits from clinical AI and under what conditions [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref33">33</xref>].</p>
        </sec>
        <sec>
          <title>Scenario C: Regulatory Retrenchment</title>
          <p>In this pathway, high-profile AI-related patient safety failures trigger more restrictive control and intensify approval burdens [<xref ref-type="bibr" rid="ref3">3</xref>]. Although politically understandable, this response may inhibit beneficial innovation without correcting the structural weaknesses that contributed to the precipitating harm [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref24">24</xref>].</p>
          <p>Within FF-CAIG, scenario planning functions as a structured stress-testing tool for regulatory proposals, institutional strategies, and professional standards. Life cycle monitoring, clearer accountability allocation, clinician oversight competencies, and routine equity surveillance are likely to remain valuable across all 3 scenarios [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. By contrast, governance strategies that assume stable technological trajectories or uniformly responsible deployment are more fragile under fragmented or crisis-driven futures [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
        </sec>
      </sec>
    </sec>
    <sec>
      <title>CLA and the Deep Structures of Clinical AI Governance</title>
      <sec>
        <title>Overview</title>
        <p>CLA offers a useful framework for examining how visible governance problems are sustained by deeper structural, cultural, and narrative conditions [<xref ref-type="bibr" rid="ref46">46</xref>]. It distinguishes 4 layers of analysis: visible problems, systemic drivers, worldview assumptions, and underlying myths and metaphors [<xref ref-type="bibr" rid="ref46">46</xref>]. In clinical AI governance, issues such as algorithmic bias, accountability gaps, and opaque decision-making may therefore reflect not only technical failures but also deeper assumptions about clinical knowledge, epistemic authority, and the relationship between algorithmic efficiency and human care [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref42">42</xref>].</p>
      </sec>
      <sec>
        <title>Applying CLA to Clinical AI Governance</title>
        <p>At the litany level, the visible concern is an AI system that produces biased recommendations, underperforms in certain patient groups, or fails silently after deployment [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. At the systemic level, these failures may be reinforced by incentive structures that privilege aggregate performance over subgroup equity [<xref ref-type="bibr" rid="ref31">31</xref>], regulatory processes that rely heavily on developer-provided evidence [<xref ref-type="bibr" rid="ref10">10</xref>], and procurement practices that prioritize efficiency over long-term oversight capacity [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. At the worldview level, governance may be shaped by techno-optimism that equates AI adoption with progress and frames skepticism as resistance to innovation [<xref ref-type="bibr" rid="ref39">39</xref>]. At the myth and metaphor level, the image of AI as a precision instrument may obscure the extent to which algorithmic outputs are shaped by assumptions embedded in design and deployment [<xref ref-type="bibr" rid="ref42">42</xref>].</p>
        <p>To illustrate how these 4 layers operate together in practice, consider an AI-enabled triage tool that underescalates symptoms reported by a particular subgroup of patients [<xref ref-type="bibr" rid="ref29">29</xref>]. CLA would examine not only this visible failure but also the systemic factors that produced it, such as underrepresentation in training data, limited subgroup testing, procurement criteria emphasizing throughput, or weak postdeployment monitoring. The analysis would also surface worldview assumptions that AI-enabled triage is inherently efficient and objective, as well as deeper metaphors of AI as a neutral gatekeeper. The resulting governance response would extend beyond model correction to include procurement standards, subgroup surveillance, escalation pathways, access to human review, and examination of the institutional assumptions that allowed the risk to remain underrecognized.</p>
      </sec>
      <sec>
        <title>From Causal Layers to Governance Interventions</title>
        <p>The governance value of CLA lies in changing the object of intervention [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]. If the problem is framed only at the litany level, the likely response is to add bias audits, incident reporting, or postdeployment monitoring [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. If CLA reveals that the problem is also systemic, governance must extend to procurement criteria, local validation requirements, committee composition, and allocation of monitoring responsibility [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. If the problem is partly rooted in worldview assumptions, such as equating AI adoption with modernization or treating skepticism as resistance to innovation, decision-makers may need to revise the criteria by which clinical AI is approved, funded, or scaled [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]. If deeper myths and metaphors frame AI as a neutral precision instrument instead of a sociotechnical actor, governance may need to include explicit review of relational effects, epistemic dependency, and institutional power asymmetries [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>]. Within FF-CAIG, CLA therefore helps regulators and health systems decide not only how to govern AI but also which level of governance intervention is required and why [<xref ref-type="bibr" rid="ref46">46</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>Applying FF-CAIG: An Operational Workflow</title>
      <p>FF-CAIG’s analytic components yield governance value only when they inform concrete deployment decisions. We therefore propose a 5-step workflow, summarized in <xref ref-type="table" rid="table4">Table 4</xref>, to translate the framework into a structured review process for AI procurement, deployment authorization, postdeployment reassessment, and regulatory policy design.</p>
      <p>In step 1, reviewers characterize the system under review, including its clinical function, data sources, update mechanism, autonomy level, deployment setting, patient-facing role, anticipated clinical consequences, and responsible actors. In step 2, the system is assigned to 1 or more horizons using 4 operational criteria: prevalence in routine care, level of real-time human oversight, fit with existing governance instruments, and observability of associated risks. This classification clarifies which risks are already governable, which require transitional adaptation, and which may fall outside current oversight instruments. In step 3, reviewers apply FF-CAIG’s analytic components by identifying implicated risk domains, stress-testing governance responses across plausible scenarios, examining deeper structural and cultural assumptions through CLA, and mapping accountability across actors. In step 4, reviewers consolidate the preceding analyses into a governance review record that specifies monitoring obligations, accountability allocation, disclosure and oversight requirements, equity surveillance expectations, and conditions for modification or suspension. In step 5, reviewers specify minimum actions scaled by horizon: a baseline for H1 systems centered on validation, monitoring, escalation, human fallback, and suspension authority, with additional H2 and H3 safeguards for life cycle monitoring, autonomy limits, patient-facing disclosure, access to human review, and reassessment after material change.</p>
      <table-wrap position="float" id="table4">
        <label>Table 4</label>
        <caption>
          <p>Operational workflow for applying the futures framework for clinical artificial intelligence governance.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="180"/>
          <col width="260"/>
          <col width="300"/>
          <col width="260"/>
          <thead>
            <tr valign="top">
              <td>Workflow step</td>
              <td>Core focus</td>
              <td>Governance output</td>
              <td>Minimum action</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>1. Characterize the system</td>
              <td>Clinical function, data sources, update mechanism, autonomy level, deployment context, patient-facing role, and responsible actors</td>
              <td>System profile and deployment context</td>
              <td>Document technical, organizational, and relational system characteristics</td>
            </tr>
            <tr valign="top">
              <td>2. Assign horizon classification</td>
              <td>Prevalence in routine care, real-time human oversight, fit with existing governance instruments, and risk observability</td>
              <td>H1<sup>a</sup>, H2, H3, or multihorizon classification</td>
              <td>Assign horizons and record the rationale for horizon placement</td>
            </tr>
            <tr valign="top">
              <td>3. Apply analytic components</td>
              <td>Risk domains, scenario stress-testing, causal layered analysis, and accountability across actors and handoffs</td>
              <td>Risk-domain map, scenario findings, causal layered analysis findings, and accountability-chain map</td>
              <td>Assess the deployment across risk domains, scenarios, causal layers, and accountability chains</td>
            </tr>
            <tr valign="top">
              <td>4. Define governance outputs</td>
              <td>Monitoring, accountability, disclosure, equity surveillance, and conditions for modification or suspension</td>
              <td>Consolidated governance review record</td>
              <td>Specify monitoring indicators, responsibility allocation, disclosure requirements, equity surveillance, and pause or suspension criteria</td>
            </tr>
            <tr valign="top">
              <td>5. Set minimum actions</td>
              <td>Horizon-scaled governance floor for deployment or continued use</td>
              <td>Deployment authorization, conditional approval, modification requirement, or nondeployment decision</td>
              <td>Require H1 baseline safeguards; add life cycle monitoring, autonomy limits, disclosure, human review access, and reassessment for H2-H3 systems</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table4fn1">
            <p><sup>a</sup>H: horizon.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
    </sec>
    <sec>
      <title>Applying FF-CAIG to Representative Clinical AI Deployments</title>
      <sec>
        <title>Overview</title>
        <p>The following 3 representative deployment patterns illustrate how this workflow can be applied across the horizon continuum. These examples are literature-grounded analytic exemplars that also reflect emerging institutional practice; they are not empirical validation exercises or single-site implementation studies. They demonstrate how FF-CAIG can be applied across different governance horizons, risk constellations, and deployment architectures.</p>
      </sec>
      <sec>
        <title>Electronic Health Record–Embedded Foundation Model Documentation Assistant (H1)</title>
        <p>A large academic medical center deploys a vendor-supplied ambient documentation assistant integrated into the electronic health record. FF-CAIG places this use case primarily in H1, while recognizing emerging H2 risks, as deployment expands across specialties and patient populations. The main governance concerns are model drift and distributed liability across the vendor, electronic health record integrator, deploying institution, and end users [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. The governance response is therefore focused on regular disaggregated performance reporting, a named institutional lead for monitoring and escalation, and clinician onboarding on system limitations and override conditions. Scenario stress-testing identifies a key vulnerability: vendor-initiated model updates may alter subgroup performance without timely local detection [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. The resulting H1 governance requirement is a deployment authorization standard that ties continued use to defined monitoring, reporting, and accountability obligations.</p>
      </sec>
      <sec>
        <title>Patient-Facing Longitudinal Triage and Communication Tool (H2)</title>
        <p>A regional health system introduces an AI-enabled patient navigation tool for longitudinal symptom monitoring, triage, and follow-up messaging between clinic visits. FF-CAIG places this deployment in H2 because the system interacts directly with patients over time while exercising increasing communicative and triage autonomy without routine clinician review. The key risk domains are agentic autonomy, AI-mediated care relationships, and opacity about AI involvement [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]. Governance priorities, therefore, include defined escalation thresholds, plain-language disclosure of AI use, access to human review on request, and exclusion criteria for patient groups requiring additional safeguards [<xref ref-type="bibr" rid="ref16">16</xref>]. Stress-testing of expansion into outpatient follow-up and longitudinal care further highlights the need for explicit rules governing use in patients with impaired decision-making capacity.</p>
      </sec>
      <sec>
        <title>Autonomous AI-Based Screening Agent (H3)</title>
        <p>A health system considers deploying an AI agent that autonomously reviews flagged imaging studies, generates preliminary reports, and triages cases for expedited review before radiologist assessment. FF-CAIG classifies this as H3 because clinically consequential action occurs with limited real-time human oversight [<xref ref-type="bibr" rid="ref36">36</xref>]. The main governance concerns are agentic autonomy, distributed liability, and equity risk arising from uneven performance across subpopulations [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. The governance response, therefore, requires predefined limits on autonomous action, thresholds for suspension or human fallback, and clear institutional responsibility for monitoring and intervention [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Stress-testing across affiliated community hospitals shows that validation in an academic center alone is insufficient. Deployment should therefore require site-specific validation, subgroup-based suspension thresholds, and clearly assigned authority to halt use when safety or equity criteria are breached [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref36">36</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>Cross-Horizon Governance Priorities</title>
      <sec>
        <title>Overview</title>
        <p>Drawing on the 3H model, the emerging risk taxonomy, scenario planning, and CLA, FF-CAIG identifies horizon-scaled governance priorities for near-term, transitional, and longer-term clinical AI environments. These priorities do not constitute separate risk categories; rather, they translate the preceding analysis into governance emphases that vary according to system maturity, autonomy, clinical consequences, institutional capacity, and regulatory uncertainty.</p>
      </sec>
      <sec>
        <title>Short-Term Priorities (H1)</title>
        <p>Near-term priorities should strengthen the governance foundations for currently deployed high-risk clinical AI systems by making them more auditable, locally accountable, and equity-aware. For high-impact systems, the core requirements include predeployment validation proportionate to clinical risk, subgroup-disaggregated performance evaluation, documentation of intended use and known limitations, and clear assignment of responsibility for monitoring, escalation, and suspension [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. In parallel, clinician education, continuing professional development, and, where appropriate, credentialing expectations should begin to align with emerging AI oversight roles [<xref ref-type="bibr" rid="ref40">40</xref>]. These measures address risks already visible in current clinical AI deployments while creating the baseline infrastructure needed for later life cycle oversight.</p>
      </sec>
      <sec>
        <title>Medium-Term Priorities (H2)</title>
        <p>Transitional priorities should focus on systems that are iteratively updated, workflow-embedded, foundation model–based, or partially delegated [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. In this horizon, governance should move from one-time validation toward life cycle review, with explicit thresholds for clinically meaningful performance change, reassessment after material updates, and standards for meaningful human oversight [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref39">39</xref>]. Patient-facing and workflow-integrated systems also require proportionate safeguards when AI materially shapes triage, communication, or care coordination, including disclosure, escalation pathways, and review mechanisms appropriate to clinical risk [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref42">42</xref>].</p>
      </sec>
      <sec>
        <title>Long-Term Priorities (H3)</title>
        <p>Longer-term priorities should address clinical AI systems that function as persistent, autonomous, or AI-mediated care infrastructures. Governance in this horizon should define the conditions under which autonomous or low-human-intervention clinical actions are permissible, how accountability is allocated across distributed systems, and how patients are protected when AI mediates access, communication, or continuity of care [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]. These priorities require stronger institutional and cross-jurisdictional coordination because the relevant risks may exceed the capacity of individual organizations or conventional product-centered oversight [<xref ref-type="bibr" rid="ref44">44</xref>]. Across horizons, the central governance task is not simply to regulate more AI, but to align governance intensity, accountability structures, and relational safeguards with changing forms of clinical AI capability and deployment.</p>
        <p>These priorities are largely convergent, with recommendations already present in the clinical AI governance literature, including life cycle oversight, equity auditing, distributed accountability, and human oversight standards. They should also be interpreted alongside evolving cross-sector and international AI governance instruments, including the EU AI Act [<xref ref-type="bibr" rid="ref49">49</xref>], the National Institute of Standards and Technology AI Risk Management Framework and its generative AI profile [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>], and International Organization for Standardization/International Electrotechnical Commission standards on AI management systems and AI risk management [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. FF-CAIG’s contribution is therefore not to introduce these priorities as isolated new requirements, but to show how their relative importance shifts across temporal horizons and divergent regulatory futures. By linking governance priorities to emerging risks, shifting roles, regulatory uncertainty, and deeper sociotechnical assumptions, FF-CAIG situates established governance commitments within a single anticipatory framework and clarifies when existing safeguards may remain sufficient, when they require adaptation, and when new forms of governance may become necessary.</p>
      </sec>
    </sec>
    <sec>
      <title>Limitations</title>
      <p>Several limitations and tensions in anticipatory governance warrant acknowledgment. First, front-loading governance requirements may increase compliance burden, especially for smaller developers, community hospitals, and health systems with limited governance infrastructure. Measures such as site-specific validation, disaggregated performance reporting, and accountability-chain documentation are more easily absorbed by large academic centers and well-resourced technology firms than by safety-net institutions or early-stage developers [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. If these requirements become de facto barriers to entry, anticipatory governance may contribute to regulatory consolidation without producing broader safety improvement. FF-CAIG does not resolve this tension and therefore requires jurisdictional and institutional adaptation to avoid becoming an instrument of exclusion.</p>
      <p>Second, anticipatory governance carries a risk of overdocumentation and procedural burden. Governance mechanisms designed for H2 and H3 conditions may be premature or disproportionate when applied to current H1 deployments, and prospective planning requirements may divert institutional capacity from direct patient care or quality improvement. A tiered approach that scales governance intensity to the autonomy, scope, and clinical consequences of the AI system may reduce this risk, although operationalizing such proportionality remains an open challenge.</p>
      <p>Third, the feasibility of FF-CAIG will vary across health systems and regulatory contexts. The framework draws primarily on regulatory developments in the United States and European Union [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Consequently, some recommendations may be difficult to implement in jurisdictions with less developed AI governance infrastructure, limited health informatics capacity, or different legal frameworks for medical device oversight. Equity in access to anticipatory governance tools is, therefore, itself a governance challenge that the framework does not fully resolve.</p>
      <p>Fourth, the deployment patterns used to illustrate FF-CAIG are representative analytic constructs, not empirical case studies. They are intended to demonstrate the framework’s interpretive and anticipatory logic across horizons, not to validate its real-world effectiveness. Relatedly, the cross-horizon priorities are derived analytically from the convergence of the framework’s temporal and scenario analyses; they have not been formally validated or systematically compared against alternative governance approaches. Future work should validate and refine FF-CAIG and its proposed cross-horizon priorities through modified Delphi consensus, retrospective mapping of documented clinical AI incidents or governance reviews, and prospective pilot-testing within institutional AI governance committees to assess horizon classification agreement, risk identification completeness, accountability clarity, decision documentation, and reviewer-reported usefulness.</p>
      <p>Fifth, FF-CAIG was not developed through primary expert consultation, Delphi elicitation, or structured stakeholder interviews, and therefore does not claim direct empirical grounding in the views of regulators, clinicians, patients, developers, or health-system leaders. Stakeholder perspectives informed the framework indirectly through the peer-reviewed studies, regulatory and policy documents, position statements, and international guidance included in the targeted narrative review. However, documentary representation is not a substitute for direct multistakeholder input, particularly for patient perspectives, which remain underrepresented in the clinical AI governance literature. Future Delphi-based validation should therefore examine whether FF-CAIG captures concerns that documentary sources may underweight or omit.</p>
    </sec>
    <sec>
      <title>Conclusions</title>
      <p>Clinical AI governance is entering a consequential period of transition. Decisions made over the next several years will shape whether clinical AI mitigates or amplifies existing inequities; whether patients retain meaningful rights to disclosure, explanation, and access to human review in AI-mediated care; and whether health systems develop the oversight capacity needed for adaptive and increasingly complex AI systems. FF-CAIG offers a structured approach for moving governance from a predominantly reactive model toward a more anticipatory one. It can help regulators, health system leaders, developers, and researchers identify cross-horizon governance gaps, stress-test governance strategies against divergent futures, and align oversight with the changing capabilities and consequences of clinical AI. Clinical AI governance should therefore be understood not simply as a technical regulatory task, but as a sociotechnical and institutional challenge requiring prospective, systems-oriented, and stakeholder-engaged approaches. Futures methodologies cannot eliminate uncertainty, but they can support more disciplined preparedness before emerging risks fully crystallize.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">3H</term>
          <def>
            <p>three horizons</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CLA</term>
          <def>
            <p>causal layered analysis</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FDA</term>
          <def>
            <p>US Food and Drug Administration</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">FF-CAIG</term>
          <def>
            <p>futures framework for clinical artificial intelligence governance</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>After drafting the manuscript, the authors used ChatGPT (OpenAI) to improve language clarity. All artificial intelligence–suggested edits were carefully reviewed and revised as necessary. The authors take full responsibility for the final content and integrity of the work.</p>
    </ack>
    <notes>
      <sec>
        <title>Funding</title>
        <p>This research received no specific grant from any funding agency in the public, commercial, or not-for-profit sectors.</p>
      </sec>
    </notes>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Data sharing is not applicable to this paper because no datasets were generated or analyzed during this study.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>JL and SL contributed to the conception and design of the viewpoint. YY, JL, and SL conducted the literature analysis and drafted the original manuscript. All authors critically revised the manuscript for important intellectual content, approved the final version, and agreed to be accountable for all aspects of the work.</p>
      </fn>
      <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>Novak</surname>
              <given-names>LL</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Garvey</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas Craig</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Snowdon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Clinical use of artificial intelligence requires AI-capable organizations</article-title>
          <source>JAMIA Open</source>
          <year>2023</year>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>ooad028</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37152469"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooad028</pub-id>
          <pub-id pub-id-type="medline">37152469</pub-id>
          <pub-id pub-id-type="pii">ooad028</pub-id>
          <pub-id pub-id-type="pmcid">PMC10155810</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>Labkoff</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Oladimeji</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kannry</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Solomonides</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Leftwich</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Koski</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Joseph</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez-Gonzalez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fleisher</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Nolen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Dutta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Levy</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Price</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Barr</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hron</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Pastor</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Luque</surname>
              <given-names>US</given-names>
            </name>
            <name name-style="western">
              <surname>Bui</surname>
              <given-names>TTT</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Weiner</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Naumann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Sittig</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>GP</given-names>
            </name>
            <name name-style="western">
              <surname>Quintana</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Toward a responsible future: recommendations for AI-enabled clinical decision support</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2024</year>
          <volume>31</volume>
          <issue>11</issue>
          <fpage>2730</fpage>
          <lpage>2739</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae209</pub-id>
          <pub-id pub-id-type="medline">39325508</pub-id>
          <pub-id pub-id-type="pii">7776823</pub-id>
          <pub-id pub-id-type="pmcid">PMC11491642</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>Poon</surname>
              <given-names>EG</given-names>
            </name>
            <name name-style="western">
              <surname>Lemak</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Rojas</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Guptill</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Classen</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Adoption of artificial intelligence in healthcare: survey of health system priorities, successes, and challenges</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2025</year>
          <month>07</month>
          <day>01</day>
          <volume>32</volume>
          <issue>7</issue>
          <fpage>1093</fpage>
          <lpage>1100</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/jamia/article-lookup/doi/10.1093/jamia/ocaf065"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaf065</pub-id>
          <pub-id pub-id-type="medline">40323320</pub-id>
          <pub-id pub-id-type="pii">8125015</pub-id>
          <pub-id pub-id-type="pmcid">PMC12202002</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>Warraich</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tazbaz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Califf</surname>
              <given-names>RM</given-names>
            </name>
          </person-group>
          <article-title>FDA perspective on the regulation of artificial intelligence in health care and biomedicine</article-title>
          <source>JAMA</source>
          <year>2025</year>
          <volume>333</volume>
          <issue>3</issue>
          <fpage>241</fpage>
          <lpage>247</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2024.21451</pub-id>
          <pub-id pub-id-type="medline">39405330</pub-id>
          <pub-id pub-id-type="pii">2825146</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>Busch</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kather</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Johner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Moser</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Truhn</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Bressem</surname>
              <given-names>KK</given-names>
            </name>
          </person-group>
          <article-title>Navigating the European Union Artificial Intelligence Act for healthcare</article-title>
          <source>NPJ Digit Med</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>210</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-024-01213-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-024-01213-6</pub-id>
          <pub-id pub-id-type="medline">39134637</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-024-01213-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC11319791</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>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Ethical considerations of using ChatGPT in health care</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <volume>25</volume>
          <fpage>e48009</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e48009/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/48009</pub-id>
          <pub-id pub-id-type="medline">37566454</pub-id>
          <pub-id pub-id-type="pii">v25i1e48009</pub-id>
          <pub-id pub-id-type="pmcid">PMC10457697</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>Aboy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Minssen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vayena</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Navigating the EU AI Act: implications for regulated digital medical products</article-title>
          <source>NPJ Digit Med</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>237</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-024-01232-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-024-01232-3</pub-id>
          <pub-id pub-id-type="medline">39242831</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-024-01232-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC11379845</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>Sendak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Beecy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vidal</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lifson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tobey</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Valladares</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Loufek</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mogri</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Balu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Strengthening the use of artificial intelligence within healthcare delivery organizations: balancing regulatory compliance and patient safety</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2024</year>
          <volume>31</volume>
          <issue>7</issue>
          <fpage>1622</fpage>
          <lpage>1627</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae119</pub-id>
          <pub-id pub-id-type="medline">38767890</pub-id>
          <pub-id pub-id-type="pii">7676585</pub-id>
          <pub-id pub-id-type="pmcid">PMC11187419</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <article-title>Marketing submission recommendations for a predetermined change control plan for artificial intelligence-enabled device software functions</article-title>
          <source>US Food and Drug Administration</source>
          <year>2024</year>
          <access-date>2026-02-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/regulatory-information/search-fda-guidance-documents/marketing-submission-recommendations-predetermined-change-control-plan-artificial-intelligence">https://www.fda.gov/regulatory-information/search-fda -guidance-documents/marketing-submission-recommendations-predetermined-change-control-plan-artificial-intelligence</ext-link>
          </comment>
        </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>Muehlematter</surname>
              <given-names>UJ</given-names>
            </name>
            <name name-style="western">
              <surname>Daniore</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Vokinger</surname>
              <given-names>KN</given-names>
            </name>
          </person-group>
          <article-title>Approval of artificial intelligence and machine learning-based medical devices in the USA and Europe (2015-20): a comparative analysis</article-title>
          <source>Lancet Digit Health</source>
          <year>2021</year>
          <volume>3</volume>
          <issue>3</issue>
          <fpage>e195</fpage>
          <lpage>e203</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(20)30292-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(20)30292-2</pub-id>
          <pub-id pub-id-type="medline">33478929</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(20)30292-2</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>Solaiman</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mekki</surname>
              <given-names>YM</given-names>
            </name>
            <name name-style="western">
              <surname>Qadir</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ghaly</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abdelkareem</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Ansari</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A "True Lifecycle Approach" towards governing healthcare AI with the GCC as a global governance model</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>337</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01614-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01614-1</pub-id>
          <pub-id pub-id-type="medline">40473925</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01614-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC12141507</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>Khera</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Simon</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Ross</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>Automation bias and assistive AI: risk of harm from AI-driven clinical decision support</article-title>
          <source>JAMA</source>
          <year>2023</year>
          <volume>330</volume>
          <issue>23</issue>
          <fpage>2255</fpage>
          <lpage>2257</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2023.22557</pub-id>
          <pub-id pub-id-type="medline">38112824</pub-id>
          <pub-id pub-id-type="pii">2812931</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>Salwei</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Carayon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hoonakker</surname>
              <given-names>PLT</given-names>
            </name>
            <name name-style="western">
              <surname>Hundt</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Wiegmann</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pulia</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Patterson</surname>
              <given-names>BW</given-names>
            </name>
          </person-group>
          <article-title>Workflow integration analysis of a human factors-based clinical decision support in the emergency department</article-title>
          <source>Appl Ergon</source>
          <year>2021</year>
          <volume>97</volume>
          <fpage>103498</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34182430"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2021.103498</pub-id>
          <pub-id pub-id-type="medline">34182430</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(21)00145-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC8474147</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>Lyell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Automation bias and verification complexity: a systematic review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>423</fpage>
          <lpage>431</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27516495"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw105</pub-id>
          <pub-id pub-id-type="medline">27516495</pub-id>
          <pub-id pub-id-type="pii">ocw105</pub-id>
          <pub-id pub-id-type="pmcid">PMC7651899</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Allan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Coghlan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cooper</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A governance model for the application of AI in health care</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <volume>27</volume>
          <issue>3</issue>
          <fpage>491</fpage>
          <lpage>497</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31682262"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz192</pub-id>
          <pub-id pub-id-type="medline">31682262</pub-id>
          <pub-id pub-id-type="pii">5612169</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647243</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Char</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>NH</given-names>
            </name>
            <name name-style="western">
              <surname>Magnus</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Implementing machine learning in health care—addressing ethical challenges</article-title>
          <source>N Engl J Med</source>
          <year>2018</year>
          <volume>378</volume>
          <issue>11</issue>
          <fpage>981</fpage>
          <lpage>983</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29539284"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/NEJMp1714229</pub-id>
          <pub-id pub-id-type="medline">29539284</pub-id>
          <pub-id pub-id-type="pmcid">PMC5962261</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Price</surname>
              <given-names>WN</given-names>
            </name>
            <name name-style="western">
              <surname>Gerke</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>IG</given-names>
            </name>
          </person-group>
          <article-title>Potential liability for physicians using artificial intelligence</article-title>
          <source>JAMA</source>
          <year>2019</year>
          <volume>322</volume>
          <issue>18</issue>
          <fpage>1765</fpage>
          <lpage>1766</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2019.15064</pub-id>
          <pub-id pub-id-type="medline">31584609</pub-id>
          <pub-id pub-id-type="pii">2752750</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Ethics and governance of artificial intelligence for health: guidance on large multi-modal models</article-title>
          <source>World Health Organization</source>
          <year>2025</year>
          <month>03</month>
          <day>25</day>
          <access-date>2026-02-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/9789240084759">https://www.who.int/publications/i/item/9789240084759</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cordova-Pozo</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rouwette</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>Types of scenario planning and their effectiveness: a review of reviews</article-title>
          <source>Futures</source>
          <year>2023</year>
          <volume>149</volume>
          <fpage>103153</fpage>
          <pub-id pub-id-type="doi">10.1016/j.futures.2023.103153</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>Coombs</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hislop</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Taneva</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Barnard</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The strategic impacts of intelligent automation for knowledge and service work: an interdisciplinary review</article-title>
          <source>J Strateg Inf Syst</source>
          <year>2020</year>
          <volume>29</volume>
          <issue>4</issue>
          <fpage>101600</fpage>
          <pub-id pub-id-type="doi">10.1016/j.jsis.2020.101600</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tõnurist</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Anticipatory innovation governance: shaping the future through proactive policy making</article-title>
          <source>OECD Working Papers on Public Governance</source>
          <year>2020</year>
          <access-date>2026-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2020/12/anticipatory-innovation-governance_d1aded4e/cce14d80-en.pdf">https://www.oecd.org/content/dam/oecd/en/publications/reports/2020/12/anticipatory-innovation-governance_d1aded4e/cce14d80-en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Foresight approaches in global public health: a practical guide for WHO staff</article-title>
          <source>World Health Organization</source>
          <year>2022</year>
          <access-date>2026-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/9789240048393">https://www.who.int/publications/i/item/9789240048393</ext-link>
          </comment>
        </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>Sharpe</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hodgson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Leicester</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lyon</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fazey</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Three horizons: a pathways practice for transformation</article-title>
          <source>Ecol Soc</source>
          <year>2016</year>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>47</fpage>
          <pub-id pub-id-type="doi">10.5751/es-08388-210247</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Meskó</surname>
              <given-names>Bertalan</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>The imperative for regulatory oversight of large language models (or generative AI) in healthcare</article-title>
          <source>NPJ Digit Med</source>
          <year>2023</year>
          <month>07</month>
          <day>06</day>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>120</fpage>
          <pub-id pub-id-type="doi">10.1038/s41746-023-00873-0</pub-id>
          <pub-id pub-id-type="medline">37414860</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-023-00873-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC10326069</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ning</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Teixayavong</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Savulescu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nagaraj</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Miao</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mertens</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DSW</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>JCL</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dunn</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vaughan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>MEH</given-names>
            </name>
            <name name-style="western">
              <surname>Sung</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Generative artificial intelligence and ethical considerations in health care: a scoping review and ethics checklist</article-title>
          <source>Lancet Digit Health</source>
          <year>2024</year>
          <volume>6</volume>
          <issue>11</issue>
          <fpage>e848</fpage>
          <lpage>e856</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(24)00143-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(24)00143-2</pub-id>
          <pub-id pub-id-type="medline">39294061</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(24)00143-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC11542614</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nestor</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>McDermott</surname>
              <given-names>MBA</given-names>
            </name>
            <name name-style="western">
              <surname>Boag</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Berner</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Naumann</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Goldenberg</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ghassemi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Feature robustness in non-stationary health records: caveats to deployable model performance in common clinical machine learning tasks</article-title>
          <source>Proc Mach Learn Res</source>
          <year>2019</year>
          <volume>106</volume>
          <fpage>381</fpage>
          <lpage>405</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.michaelchughes.com/papers/NestorEtAl_MLHC_2019.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Finlayson</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Subbaswamy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bowers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kupke</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zittrain</surname>
              <given-names>J</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>
          </person-group>
          <article-title>The clinician and dataset shift in artificial intelligence</article-title>
          <source>N Engl J Med</source>
          <year>2021</year>
          <volume>385</volume>
          <issue>3</issue>
          <fpage>283</fpage>
          <lpage>286</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34260843"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/NEJMc2104626</pub-id>
          <pub-id pub-id-type="medline">34260843</pub-id>
          <pub-id pub-id-type="pmcid">PMC8665481</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Crowe</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Teng</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>DeCamp</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenberg</surname>
              <given-names>EI</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>BX</given-names>
            </name>
            <name name-style="western">
              <surname>Huber</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Karches</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zucker</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rotenstein</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rodman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Richman</surname>
              <given-names>IB</given-names>
            </name>
            <name name-style="western">
              <surname>Henry</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>Somlo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pitts</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Mishuris</surname>
              <given-names>RG</given-names>
            </name>
          </person-group>
          <article-title>Recommendations for clinicians, technologists, and healthcare organizations on the use of generative artificial intelligence in medicine: a position statement from the Society of General Internal Medicine</article-title>
          <source>J Gen Intern Med</source>
          <year>2025</year>
          <volume>40</volume>
          <issue>3</issue>
          <fpage>694</fpage>
          <lpage>702</lpage>
          <pub-id pub-id-type="doi">10.1007/s11606-024-09102-0</pub-id>
          <pub-id pub-id-type="medline">39531100</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11606-024-09102-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC11861482</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Powers</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Vogeli</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mullainathan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Dissecting racial bias in an algorithm used to manage the health of populations</article-title>
          <source>Science</source>
          <year>2019</year>
          <volume>366</volume>
          <issue>6464</issue>
          <fpage>447</fpage>
          <lpage>453</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://escholarship.org/uc/item/6h92v832"/>
          </comment>
          <pub-id pub-id-type="doi">10.1126/science.aax2342</pub-id>
          <pub-id pub-id-type="medline">31649194</pub-id>
          <pub-id pub-id-type="pii">366/6464/447</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vyas</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Eisenstein</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Hidden in plain sight—reconsidering the use of race correction in clinical algorithms</article-title>
          <source>N Engl J Med</source>
          <year>2020</year>
          <volume>383</volume>
          <issue>9</issue>
          <fpage>874</fpage>
          <lpage>882</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMms2004740</pub-id>
          <pub-id pub-id-type="medline">32853499</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Cellini</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Charpignon</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Dee</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Dernoncourt</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Eber</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>WG</given-names>
            </name>
            <name name-style="western">
              <surname>Moukheiber</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schirmer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Situ</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Paguio</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wawira</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Sources of bias in artificial intelligence that perpetuate healthcare disparities—a global review</article-title>
          <source>PLoS Digit Health</source>
          <year>2022</year>
          <volume>1</volume>
          <issue>3</issue>
          <fpage>e0000022</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pdig.0000022"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pdig.0000022</pub-id>
          <pub-id pub-id-type="medline">36812532</pub-id>
          <pub-id pub-id-type="pii">PDIG-D-21-00034</pub-id>
          <pub-id pub-id-type="pmcid">PMC9931338</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Acosta</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Falcone</surname>
              <given-names>GJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rajpurkar</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>Multimodal biomedical AI</article-title>
          <source>Nat Med</source>
          <year>2022</year>
          <volume>28</volume>
          <issue>9</issue>
          <fpage>1773</fpage>
          <lpage>1784</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-022-01981-2</pub-id>
          <pub-id pub-id-type="medline">36109635</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-022-01981-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rajpurkar</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Banerjee</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>AI in health and medicine</article-title>
          <source>Nat Med</source>
          <year>2022</year>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-021-01614-0</pub-id>
          <pub-id pub-id-type="medline">35058619</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-021-01614-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moor</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Banerjee</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Abad</surname>
              <given-names>ZSH</given-names>
            </name>
            <name name-style="western">
              <surname>Krumholz</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Leskovec</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Topol</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rajpurkar</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Foundation models for generalist medical artificial intelligence</article-title>
          <source>Nature</source>
          <year>2023</year>
          <volume>616</volume>
          <issue>7956</issue>
          <fpage>259</fpage>
          <lpage>265</lpage>
          <pub-id pub-id-type="doi">10.1038/s41586-023-05881-4</pub-id>
          <pub-id pub-id-type="medline">37045921</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-023-05881-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wornow</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Thapa</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Steinberg</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fleming</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeffer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Fries</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>NH</given-names>
            </name>
          </person-group>
          <article-title>The shaky foundations of large language models and foundation models for electronic health records</article-title>
          <source>NPJ Digit Med</source>
          <year>2023</year>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>135</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-023-00879-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-023-00879-8</pub-id>
          <pub-id pub-id-type="medline">37516790</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-023-00879-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC10387101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Olawade</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Plabon</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Ojo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ogunbona</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Makanjuola</surname>
              <given-names>BD</given-names>
            </name>
            <name name-style="western">
              <surname>Olasilola</surname>
              <given-names>OR</given-names>
            </name>
          </person-group>
          <article-title>Human in the loop artificial intelligence in healthcare: applications, outcomes, and implementation challenges</article-title>
          <source>Int J Med Inform</source>
          <year>2026</year>
          <volume>213</volume>
          <fpage>106362</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(26)00102-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2026.106362</pub-id>
          <pub-id pub-id-type="medline">41740273</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(26)00102-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Hasan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kueper</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hayes</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fine</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Balu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sendak</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Establishing organizational AI governance in healthcare: a case study in Canada</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>522</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01909-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01909-3</pub-id>
          <pub-id pub-id-type="medline">40817280</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01909-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC12356831</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ancker</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nosal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hauser</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mauer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kaushal</surname>
              <given-names>R</given-names>
            </name>
            <collab>with the HITEC Investigators</collab>
          </person-group>
          <article-title>Effects of workload, work complexity, and repeated alerts on alert fatigue in a clinical decision support system</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2017</year>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>36</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-017-0430-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-017-0430-8</pub-id>
          <pub-id pub-id-type="medline">28395667</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-017-0430-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC5387195</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Emanuel</surname>
              <given-names>EJ</given-names>
            </name>
          </person-group>
          <article-title>Predicting the future—big data, machine learning, and clinical medicine</article-title>
          <source>N Engl J Med</source>
          <year>2016</year>
          <volume>375</volume>
          <issue>13</issue>
          <fpage>1216</fpage>
          <lpage>1219</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27682033"/>
          </comment>
          <pub-id pub-id-type="doi">10.1056/NEJMp1606181</pub-id>
          <pub-id pub-id-type="medline">27682033</pub-id>
          <pub-id pub-id-type="pmcid">PMC5070532</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>From agents to governance: essential AI skills for clinicians in the large language model era</article-title>
          <source>J Med Internet Res</source>
          <year>2026</year>
          <volume>28</volume>
          <fpage>e86550</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2026//e86550/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/86550</pub-id>
          <pub-id pub-id-type="medline">41534067</pub-id>
          <pub-id pub-id-type="pii">v28i1e86550</pub-id>
          <pub-id pub-id-type="pmcid">PMC12853083</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abràmoff</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Lavin</surname>
              <given-names>PT</given-names>
            </name>
            <name name-style="western">
              <surname>Birch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Folk</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Pivotal trial of an autonomous AI-based diagnostic system for detection of diabetic retinopathy in primary care offices</article-title>
          <source>NPJ Digit Med</source>
          <year>2018</year>
          <volume>1</volume>
          <fpage>39</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-018-0040-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-018-0040-6</pub-id>
          <pub-id pub-id-type="medline">31304320</pub-id>
          <pub-id pub-id-type="pii">40</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550188</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mittelstadt</surname>
              <given-names>BD</given-names>
            </name>
            <name name-style="western">
              <surname>Allo</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Taddeo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wachter</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Floridi</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The ethics of algorithms: mapping the debate</article-title>
          <source>Big Data Soc</source>
          <year>2016</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>205395171667967</fpage>
          <pub-id pub-id-type="doi">10.1177/2053951716679679</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Campos</surname>
              <given-names>HDO</given-names>
            </name>
            <name name-style="western">
              <surname>Wolfe</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Luan</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sim</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Generative AI as third agent: large language models and the transformation of the clinician-patient relationship</article-title>
          <source>J Particip Med</source>
          <year>2025</year>
          <volume>17</volume>
          <fpage>e68146</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jopm.jmir.org/2025//e68146/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/68146</pub-id>
          <pub-id pub-id-type="medline">40826831</pub-id>
          <pub-id pub-id-type="pii">v17i1e68146</pub-id>
          <pub-id pub-id-type="pmcid">PMC12361538</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Artificial Intelligence/Machine Learning-enabled Working Group</collab>
          </person-group>
          <article-title>Good machine learning practice for medical device development: guiding principles</article-title>
          <source>International Medical Device Regulators Forum</source>
          <year>2025</year>
          <access-date>2026-02-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.imdrf.org/documents/good-machine-learning-practice-medical-device-development-guiding-principles">https://www.imdrf.org/documents/good-machine-learning-practice-medical-device-development-guiding-principles</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Healey</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Hodgkinson</surname>
              <given-names>GP</given-names>
            </name>
          </person-group>
          <article-title>Overcoming strategic persistence: effects of multiple scenario analysis on strategic reorientation</article-title>
          <source>Strateg Manage J</source>
          <year>2024</year>
          <volume>45</volume>
          <issue>8</issue>
          <fpage>1423</fpage>
          <lpage>1445</lpage>
          <pub-id pub-id-type="doi">10.1002/smj.3589</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Inayatullah</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Causal layered analysis: poststructuralism as method</article-title>
          <source>Futures</source>
          <year>1998</year>
          <volume>30</volume>
          <issue>8</issue>
          <fpage>815</fpage>
          <lpage>829</lpage>
          <pub-id pub-id-type="doi">10.1016/s0016-3287(98)00086-x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McCradden</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>London</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>A normative framework for artificial intelligence as a sociotechnical system in healthcare</article-title>
          <source>Patterns (N Y)</source>
          <year>2023</year>
          <volume>4</volume>
          <issue>11</issue>
          <fpage>100864</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2666-3899(23)00248-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.patter.2023.100864</pub-id>
          <pub-id pub-id-type="medline">38035190</pub-id>
          <pub-id pub-id-type="pii">S2666-3899(23)00248-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC10682751</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carayon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wooldridge</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hoonakker</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hundt</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>MM</given-names>
            </name>
          </person-group>
          <article-title>SEIPS 3.0: human-centered design of the patient journey for patient safety</article-title>
          <source>Appl Ergon</source>
          <year>2020</year>
          <volume>84</volume>
          <fpage>103033</fpage>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2019.103033</pub-id>
          <pub-id pub-id-type="medline">31987516</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(19)30239-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC7152782</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence</article-title>
          <source>European Parliament and Council of the European Union</source>
          <year>2024</year>
          <access-date>2026-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng">https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tabassi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <source>Artificial Intelligence Risk Management Framework (AI RMF 1.0). NIST AI 100-1</source>
          <year>2023</year>
          <publisher-loc>Gaithersburg, MD</publisher-loc>
          <publisher-name>National Institute of Standards and Technology</publisher-name>
          <pub-id pub-id-type="doi">10.6028/NIST.AI.100-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Autio</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Schwartz</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dunietz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stanley</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tabassi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <source>Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile. NIST AI 600-1</source>
          <year>2024</year>
          <publisher-loc>Gaithersburg, MD</publisher-loc>
          <publisher-name>National Institute of Standards and Technology</publisher-name>
          <pub-id pub-id-type="doi">10.6028/NIST.AI.600-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="web">
          <article-title>ISO/IEC 42001:2023 information technology—artificial intelligence—management system</article-title>
          <source>International Organization for Standardization, International Electrotechnical Commission</source>
          <year>2023</year>
          <access-date>2026-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/42001">https://www.iso.org/standard/42001</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>ISO/IEC 23894:2023 information technology—artificial intelligence—guidance on risk management</article-title>
          <source>International Organization for Standardization, International Electrotechnical Commission</source>
          <year>2023</year>
          <access-date>2026-05-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/77304.html">https://www.iso.org/standard/77304.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
