<?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 article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <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">v28i1e109467</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/109467</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>Institutional Approval Is Not Public Authorization: Legitimacy as a Governance Requirement for Clinical AI</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Steenstra</surname>
            <given-names>Ivan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Steiskal</surname>
            <given-names>Jost-Vincent</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Furusa</surname>
            <given-names>Samuel Simbarashe</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" 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>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1369-4625</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Siru</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <address>
            <institution>Department of Biomedical Informatics</institution>
            <institution>Vanderbilt University Medical Center</institution>
            <addr-line>2525 West End Ave, Suite 1475</addr-line>
            <addr-line>Nashville, TN, 37212</addr-line>
            <country>United States</country>
            <phone>1 615 875 5216</phone>
            <email>siru.liu@vumc.org</email>
          </address>
          <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 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: Siru Liu <email>siru.liu@vumc.org</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>2</day>
        <month>11</month>
        <year>2026</year>
      </pub-date>
      <volume>28</volume>
      <elocation-id>e109467</elocation-id>
      <history>
        <date date-type="received">
          <day>12</day>
          <month>8</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>8</day>
          <month>10</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>18</day>
          <month>10</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>20</day>
          <month>10</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Jialin Liu, Siru Liu. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 02.11.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/e109467" xlink:type="simple"/>
      <abstract>
        <p>Clinical AI governance has advanced rapidly in technical validation, regulatory compliance, risk management, human oversight, and postdeployment monitoring. Yet a more fundamental question often remains implicit: under what conditions are health institutions justified in exercising consequential authority through AI over patients, clinicians, and communities? In this Viewpoint, we argue that legitimacy should be recognized as an independent governance requirement, distinct from technical assurance, legal and ethical compliance, trust, acceptance, and institutional approval. Our aim is to distinguish institutional approval from public authorization and to propose a normative framework for authorizing consequential clinical AI deployments. We address health system leaders, clinical AI governance and procurement teams, frontline clinicians, and patient and community representatives. Drawing on theories of legitimacy and public value and published clinical AI governance research, we make the following contributions: (1) the concept of the unclaimed decision, defined as a consequential choice about purpose, threshold, population, or priority for which no actor clearly assumes responsibility for public justification; (2) a tripartite framework comprising procedural authorization, substantive justification, and relational renewal; and (3) practical governance tools to support public justification, contestation, and renewal. These tools include 3 minimum auditable conditions: visibility of deployment; affected-party input before governing conditions are fixed; and conditional reviewability, which requires a predefined trigger that can be invoked by a named actor outside the deploying team. A 5-question public authorization test examines purpose, distribution, exclusion, meaningful choice and contestability, and renewal. Governance intensity should increase with clinical consequence; distributive reach; difficulty of reversal; and the absence of genuine, informed choice. For smaller health care organizations, we propose ways to perform the same core governance functions through existing advisory bodies, targeted interviews, shared regional resources, and standardized documentation. We also outline a heuristic for identifying affected publics, procedures for specifying participation authority and resolving disagreement, and procurement provisions that preserve reviewability across vendor boundaries. These are normative proposals requiring evaluation. Public authorization requires continuing substantive justification; it cannot be inferred from compliance, popularity, or completion of an audit checklist.</p>
      </abstract>
      <kwd-group>
        <kwd>artificial intelligence</kwd>
        <kwd>AI</kwd>
        <kwd>clinical AI</kwd>
        <kwd>AI governance</kwd>
        <kwd>legitimacy</kwd>
        <kwd>public authorization</kwd>
        <kwd>public justification</kwd>
        <kwd>social license</kwd>
        <kwd>patient engagement</kwd>
        <kwd>contestability</kwd>
        <kwd>accountability</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Clinical AI governance increasingly emphasizes technical validation, regulatory compliance, risk management, and life cycle monitoring. However, published evaluations have identified important limitations in the evidence available to support oversight. A review of 1012 US Food and Drug Administration (FDA) device summaries through December 2024 reported a mean transparency score of 3.3 out of 17 [<xref ref-type="bibr" rid="ref1">1</xref>]. A separate examination of 903 devices listed through August 2024 found that 505 (55.9%) reported clinical performance studies, of which 41 (8.1%) were prospective and 12 (2.4%) were randomized [<xref ref-type="bibr" rid="ref2">2</xref>]. These findings concern publicly reported evidence rather than providing proof that unreported evaluations never occurred. The European Union AI Act and professional governance proposals provide additional legal, ethical, and organizational safeguards [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. Nevertheless, technical assurance and regulatory compliance do not by themselves establish public authorization.</p>
      <p>We use institutional approval to describe the regulatory, professional, and organizational warrants that permit an institution to deploy AI [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. Affected publics remain incompletely represented in these processes [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Public authorization concerns whether the resulting exercise of authority is publicly justifiable, meaningfully open to affected-party influence, and subject to continuing contestation and revision [<xref ref-type="bibr" rid="ref10">10</xref>]. A clinical AI system may therefore be safe, effective, legally permissible, and institutionally approved while still lacking public legitimacy if affected publics lack meaningful opportunities to shape its governing conditions or contest consequential uses. For example, AI referral triage may reorder access without directly diagnosing disease [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Its definition of urgency still requires justification beyond evidence of classification accuracy or organizational approval [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
      <p>Experience with health data initiatives illustrates this distinction. Analyses of England’s care data program identified deficiencies in public engagement, transparency, and safeguards despite an asserted public benefit rationale [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. The Royal Free–DeepMind collaboration raised concerns about data use, transparency, and accountability [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. These cases illustrate challenges of public justification; they do not establish the effectiveness of the framework proposed here. Social license emphasizes the continuing acceptability of institutional practices [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]; public authorization additionally asks whether the authority exercised can be justified to those subject to it, including dissenters [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>].</p>
      <p>Organizational and political theories offer distinct accounts of legitimacy [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Drawing on these accounts, we examine the public justification of deployment authority. Public value theory helps frame this inquiry: authorizing environment in health care combines regulatory mandates, institutional accountability, professional judgment, and affected-public participation [<xref ref-type="bibr" rid="ref22">22</xref>]. Deployment choices may fall between these sources of authority, creating what we call the unclaimed decision: a consequential choice about purpose, threshold, population, or priority for which no actor clearly assumes responsibility for public justification.</p>
      <p>This Viewpoint distinguishes institutional approval from public authorization and proposes a normative framework for governing consequential clinical AI deployments [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. We advance four key messages: (1) legitimacy is an independent governance requirement that cannot be inferred from technical assurance, legal or ethical compliance, trust, acceptance, or institutional approval; (2) the unclaimed decision identifies gaps in responsibility for publicly justifying deployment choices; (3) public authorization requires procedural authorization, substantive justification, and relational renewal, supported by 3 minimum auditable conditions (visibility, affected-party input before governing conditions are fixed, and conditional reviewability) and complemented by the 5-question public authorization test; and (4) governance intensity should reflect clinical consequence, distributive reach, difficulty of reversal, and the absence of genuine, informed choice. The practical recommendations address institutional decision-making, procurement, clinical oversight, and patient and community participation. We also propose candidate process indicators to support empirical evaluation of public authorization practices.</p>
    </sec>
    <sec>
      <title>The Legitimacy Concept: From Political Philosophy to Clinical AI</title>
      <sec>
        <title>Legitimacy as a Distinct Normative Requirement</title>
        <p>In political philosophy, legitimacy concerns the normative justification of authority: whether an institution has a defensible right to exercise power over those subject to its decisions [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. It is distinct from legality, effectiveness, ethical compliance, and sociological acceptance. Authority may be lawful and effective yet remain illegitimate if its exercise lacks a publicly defensible justification [<xref ref-type="bibr" rid="ref26">26</xref>]; conversely, public acceptance does not itself establish legitimacy [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
        <p>This distinction is particularly important in clinical AI because health institutions increasingly exercise authority through computational systems as well as through clinicians and formal policies. AI systems stratify risk, prioritize patients, recommend treatments, flag diagnoses, and allocate clinical attention [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. In doing so, they shape the distribution of treatment opportunities, risks, responsibilities, and other socially important goods [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. Institutions must therefore be able to justify to affected publics why they are entitled to exercise clinical authority through a particular system, for a particular purpose, and under particular conditions [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. Moreover, AI design and deployment embed value choices that technical validation cannot resolve: they concern how institutional power should be exercised and therefore require public justification [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
      </sec>
      <sec>
        <title>The Structural Legitimacy Deficit in Clinical AI</title>
        <p>Current clinical AI governance may treat legitimacy as a presumed consequence of institutional approval. A device may receive regulatory clearance [<xref ref-type="bibr" rid="ref32">32</xref>], its local deployment may be classified as nonresearch quality improvement or receive a favorable institutional determination [<xref ref-type="bibr" rid="ref33">33</xref>], and a health system committee may approve its integration [<xref ref-type="bibr" rid="ref34">34</xref>]. Together, these processes may establish technical, legal, and organizational permissibility [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>], but they do not by themselves establish public authorization to govern through the technology [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        <p>The deficit is not an absence of governance. Patients, communities, and frontline clinicians may nonetheless have limited, late-stage, or advisory-only influence over a system’s purposes, embedded trade-offs, target populations, or conditions for modification or withdrawal [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. Those most affected by AI-mediated authority may therefore have little meaningful opportunity to shape, contest, or reauthorize its exercise. Existing oversight mechanisms remain necessary, but they do not by themselves establish why an institution is entitled to make particular deployment-level choices on behalf of those subject to them [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
      </sec>
      <sec>
        <title>The Unclaimed Decision and the Limits of Existing Authorization</title>
        <p>This problem is best understood as a jurisdictional gap. Regulatory mandates, institutional accountability, professional judgment, and affected-public participation each provide a partial warrant for clinical AI deployment, yet responsibility for publicly justifying deployment-level decisions about purpose, threshold, population, priority, and acceptable trade-offs may remain unclear [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. The concept of the unclaimed decision introduced above captures this gap in responsibility. Accumulating existing forms of approval does not resolve the gap: regulatory, institutional, professional, and participatory processes answer different questions and provide complementary rather than substitutable warrants [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p>
        <p>Individual consent remains important but cannot authorize every systemic consequence of clinical AI. Organizational uses may reshape access, workload, and resource allocation beyond the consenting encounter [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref39">39</xref>], particularly when AI-mediated processes are embedded in routine care and difficult to avoid. We distinguish 3 complementary mechanisms: voice, meaning influence over governing purposes and conditions; contestability, meaning the ability to challenge a consequential decision and obtain meaningful reconsideration; and exit, meaning a practical opportunity to avoid the AI-mediated pathway. A patient may challenge an AI-mediated decision without being able to influence deployment policy or decline an encounter-level AI tool while remaining subject to an AI-managed referral queue.</p>
      </sec>
      <sec>
        <title>Why Legitimacy Becomes Unavoidable in Clinical AI</title>
        <p>The legitimacy deficit is not merely conceptual. Research identifies concerns about trust in institutional AI use and the inclusion of affected communities in governance [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Insufficient public justification may compound these concerns, although its effects on resistance and inequities require empirical evaluation. We propose that stronger public authorization could help identify value conflicts and distributional concerns before deployment arrangements become embedded in routine care [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Legitimacy does not guarantee acceptance or better outcomes; it provides a basis for institutions to assess whether a proposed exercise of deployment authority is justifiable despite disagreement [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        <p>The legitimacy question becomes more consequential as AI is embedded in clinical workflows [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. As validated tools become integrated into professional practice, clinicians may face expectations to use them, making nonuse as consequential as use [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref41">41</xref>], while AI-mediated care may become increasingly difficult for patients to avoid. The question is therefore not only whether AI is safe, effective, or trustworthy, but also on what grounds institutions subject patients to consequential algorithmic processes [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. Patients may not have chosen these processes and may have limited ability to contest them [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <p>Clinical AI governance must account for 2 constituencies simultaneously. Patients may be subject to AI-mediated prioritization, recommendations, communication, and access decisions, while frontline clinicians may experience changes in professional discretion, workload, accountability, and standards of care [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Public authorization therefore cannot be reduced to patient acceptance alone [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Legitimate governance must account for both those who receive AI-mediated care and those who remain professionally answerable for delivering it, particularly because clinical authority is embedded in fiduciary and relational obligations [<xref ref-type="bibr" rid="ref44">44</xref>]. When AI redistributes judgment, attention, and responsibility, the authority exercised through it must remain publicly justifiable, contestable, and renewable [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref44">44</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>A Tripartite Framework for Public Authorization</title>
      <sec>
        <title>Conceptual Basis</title>
        <p>Our framework connects political theories of legitimacy and public value theory [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>] with governance concerns discussed in the clinical AI literature. These include limited affected-party influence over deployment decisions [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>], insufficient public justification of purposes and distributive trade-offs [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>], and the need for mechanisms to support contestation and reauthorization as systems and uses change [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. We interpret these concerns as aspects of the unclaimed decision. This normative-conceptual synthesis is not a systematic review or a consensus exercise.</p>
        <p>On this basis, we propose 3 interdependent dimensions of public authorization: procedural authorization, substantive justification, and relational renewal (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Each addresses a distinct question: Who can meaningfully influence deployment decisions? Which purposes and distributions of benefit and burden can be publicly justified? How does authorization remain contestable and justified over time?</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Tripartite framework for public authorization of clinical AI. The unclaimed decision arises when no actor clearly assumes responsibility for publicly justifying deployment choices about purpose, threshold, population, or priority. Public authorization addresses this gap through 3 interdependent dimensions: procedural authorization, substantive justification, and relational renewal. These dimensions are jointly necessary but individually insufficient and must remain aligned as systems, uses, and conditions change.</p>
          </caption>
          <graphic xlink:href="jmir_v28i1e109467_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Procedural Authorization</title>
        <p>Procedural authorization concerns how AI deployment decisions are made and whether those affected have meaningful influence over them. Affected constituencies, including disproportionately affected groups, should be involved before the purposes, trade-offs, and conditions of use are established [<xref ref-type="bibr" rid="ref35">35</xref>]. Participation should involve deliberation or co-design where appropriate, with documented institutional responses showing how input influenced decisions [<xref ref-type="bibr" rid="ref35">35</xref>]. Input should address choices that remain open to influence; product-level constraints may require engagement with developers or vendors.</p>
        <p>In a national survey of US adults conducted in 2023, 62.7% rated as “very true” the statement that notification of AI use in their care is important [<xref ref-type="bibr" rid="ref47">47</xref>]. Two UK citizens’ juries, each involving 18 participants over 5 days, favored accuracy over explainability in the health care scenarios considered [<xref ref-type="bibr" rid="ref48">48</xref>]. These findings inform notification and deliberation but do not establish legitimacy or clinical benefits. Broader research identifies context-dependent expectations concerning public benefit, privacy, commercial involvement, and institutional trustworthiness [<xref ref-type="bibr" rid="ref49">49</xref>-<xref ref-type="bibr" rid="ref52">52</xref>]. Participation should therefore shape governing decisions rather than merely secure acceptance [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref51">51</xref>].</p>
      </sec>
      <sec>
        <title>Mapping the Affected Public</title>
        <p>We propose a 4-step process for mapping the affected public for each deployment. First, identify whose care, access, work, or responsibilities may change. Second, trace indirect effects, including queue displacement, caregiver burdens, consequences for data-contributing communities, and unequal exposure to error. Third, identify groups at risk of underrepresentation because of language, disability, digital access, geography, or social disadvantage. Fourth, publish the proposed boundary, the reasons for inclusion and exclusion, recruitment routes, and omissions; invite corrections; and revisit the map after material changes. This engagement-informed heuristic is not a validated sampling method [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref53">53</xref>].</p>
        <p>For a hospital-wide risk model, relevant groups may include patients whose care is intensified or deprioritized, staff receiving alerts, and subgroups with unequal error burdens. Referral triage also affects people displaced within the queue and referring services. Ambient documentation affects patients whose encounters are recorded and clinicians whose documentation changes; secondary data uses may warrant wider inclusion. The boundary should reflect distributive reach rather than current use or ease of recruitment.</p>
      </sec>
      <sec>
        <title>Participation Authority and Disagreement</title>
        <p>Institutions should specify participants’ influence before engagement. For low-impact, readily avoidable uses, input may be advisory but should be accompanied by a reasoned response. For consequential uses, affected representatives should help set conditions, monitoring priorities, and review triggers. For high-impact, rights-sensitive, or effectively unavoidable uses, we propose formally delegated powers to require reconsideration or to pause deployment, subject to applicable law and institutional authority. These collective powers are distinct from an individual veto over a shared service.</p>
        <p>A named accountable institutional body should resolve disagreement through documented deliberation, disclose conflicts of interest, publish reasons and dissent, and provide escalation to a body outside the deploying team. Delegated powers should be explicitly defined, while the deploying institution retains accountability. Majority support cannot waive safety obligations or protections against discrimination. Unresolved concerns about fundamental interests should prompt modification, restriction, or suspension pending review [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref45">45</xref>].</p>
      </sec>
      <sec>
        <title>Substantive Justification</title>
        <p>Substantive justification concerns whether the purposes and distributive consequences of AI deployment can be publicly defended. It requires explicit scrutiny of what a system is designed to optimize, which trade-offs it privileges, and whose interests it prioritizes [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. A legitimate deployment should pursue a clearly stated clinical or social purpose, generate benefits proportionate to its risks and burdens, and avoid creating or exacerbating inequities [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. Efficiency and cost reduction may be relevant benefits, but they do not by themselves justify adverse effects on autonomy, access, workforce burden, or relational care, nor do they justify commercial extraction of public health data without adequate safeguards [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref51">51</xref>].</p>
        <p>This dimension draws on the Belmont principles of respect for persons, beneficence, and justice [<xref ref-type="bibr" rid="ref54">54</xref>], adapting them to clinical AI deployment beyond research settings. It requires health systems to assess and publicly report how AI-related benefits, burdens, errors, and opportunity costs are distributed. Health AI assurance laboratories can provide essential evidence on validity, safety, fairness, and real-world performance [<xref ref-type="bibr" rid="ref7">7</xref>]. However, technical assurance cannot by itself establish the public justification of a deployment’s purpose or distributive trade-offs. Technical metrics can inform but cannot resolve normative choices about tolerable errors, the time available for relational care, or the allocation of scarce attention [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
        <p>For data-intensive or commercially developed systems, substantive justification should also address reciprocity: whether data-contributing communities receive proportionate benefits and whether commercial value extraction is consistent with the stated public purpose [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. Where technically reasonable options remain normatively contestable, value pluralism itself becomes part of the governance problem [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
      </sec>
      <sec>
        <title>Relational Renewal</title>
        <p>Relational renewal concerns the continuing answerability of institutions that exercise authority through AI. Legitimacy cannot be secured once at procurement or deployment because systems, workflows, institutional incentives, and public expectations change over time [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. Trust in clinical AI is relational rather than a fixed property of the system [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref55">55</xref>]. It should be treated as a possible consequence of legitimate governance, not as evidence of legitimacy itself [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        <p>Declining trust, rising complaints, repeated override patterns, or persistent subgroup concerns should therefore function as warning signals that prompt review, rather than as direct measures of legitimacy [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]. Relational renewal requires accessible mechanisms for patients and clinicians to identify AI involvement, challenge consequential outputs, and obtain human reconsideration, explanation, or remedy [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]. It also requires transparent communication, continued professional responsibility, and predefined review triggers when models, vendors, data sources, populations, purposes, workflows, or degrees of autonomy materially change [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. Authorization should remain capable of renewal, restriction, suspension, or withdrawal when its original conditions no longer hold [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>].</p>
        <p>The 3 dimensions are jointly necessary but individually insufficient. Participation without substantive safeguards can create an appearance of legitimacy while leaving harmful deployment choices inadequately justified; technical fairness without meaningful participation can preserve paternalistic authority; and initial authorization without relational renewal can become obsolete. Public authorization therefore depends on the continuing alignment of fair participation, publicly defensible purposes, and accountable relationships.</p>
      </sec>
    </sec>
    <sec>
      <title>The 5-Question Public Authorization Test</title>
      <sec>
        <title>Purpose and Scope of the Test</title>
        <p>The 5-question public authorization test (<xref ref-type="table" rid="table1">Table 1</xref>) translates the tripartite framework into 5 governance questions addressing purpose, distribution of benefits and burdens, exclusion, meaningful choice and contestability, and renewal. <xref ref-type="table" rid="table1">Table 1</xref> links each question to minimum evidence and warning signs. These domains reflect established health AI governance priorities concerning public benefit, equity, accountability, human oversight, contestation and remedy, monitoring, and change management [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>]. The test is a normative governance diagnostic, not a validated assessment instrument or a substitute for regulatory assessment.</p>
        <p>It complements existing technical, ethical, legal, regulatory, and risk management assessments by examining the public justification of a specified deployment [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. Its domains span procedural, substantive, and relational concerns. The test should be applied before deployment, at predefined review intervals, and after material changes in systems or deployment conditions [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref57">57</xref>]. Each answer should identify publicly defensible evidence, unresolved concerns, and any further justification, modification, or review needed.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>The 5-question public authorization test: questions, minimum evidence, and warning signs for clinical AI.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="140"/>
            <col width="250"/>
            <col width="330"/>
            <col width="280"/>
            <thead>
              <tr valign="top">
                <td>Question number</td>
                <td>Public authorization questions<sup>a</sup></td>
                <td>Minimum evidence</td>
                <td>Warning signs</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Does the AI system serve a publicly defensible clinical or social purpose?</td>
                <td>Meaningful clinical, patient-centered, safety, workflow, or population benefit compared with an appropriate alternative; justification for using AI; and public reason and value statement<sup>b</sup></td>
                <td>Benchmark performance or efficiency gains without evidence of meaningful benefit</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Who benefits, and who bears the burdens?</td>
                <td>Subgroup-specific benefits and harms and distribution of errors, costs, workload, risks, and opportunity costs</td>
                <td>Average performance only; burdens shifted to patients, clinicians, caregivers, or disadvantaged groups</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Does deployment create, reduce, or reproduce exclusion?</td>
                <td>Assessment across relevant dimensions of disadvantage, including language, disability, geography, digital access, and socioeconomic context</td>
                <td>Dependence on resources, literacy, language, or access that systematically excludes some groups</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Do affected people have meaningful choice and access to contestation?</td>
                <td>Proportionate disclosure; accessible non-AI option without undue cost, delay, or loss of quality or access; language and disability accommodations; reconsideration of choice; accessible explanation, appeal, meaningful human reconsideration, and remedy; and documented justification and safeguards where exit is infeasible</td>
                <td>Invisible or effectively unavoidable AI use without adequate justification or safeguards; nominal opt-out with unreasonable disadvantages; inaccessible explanations or appeals; and no meaningful human reconsideration</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Does authorization remain justified over time?</td>
                <td>Periodic reviews and reviews after material changes; complaint and incident trends; corrective actions; and criteria for renewal, restriction, suspension, or withdrawal</td>
                <td>Permanent approval; material changes without review; ignored complaints or incidents; and persistent subgroup concerns</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Procedural authorization is assessed primarily through the 3 minimum auditable conditions described separately. Question 4 examines meaningful choice, contestability, and human reconsideration; voice in deployment governance is addressed through affected-party input. Where a practical non-AI pathway is unavailable, its absence should be explicitly acknowledged and should inform the justification, safeguards, and intensity of review.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>A concise statement of the deployment’s purpose, major value trade-offs, rationale for using AI, and limits of authorized use.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Interpreting the Test</title>
        <p>The test addresses a distinct governance question: whether an institution is justified in exercising authority through a particular AI system, for a particular purpose and population, and under particular conditions [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. It is noncompensatory and should not be reduced to an additive score: strength in 1 domain cannot offset an unresolved failure in another. Technical performance cannot compensate for authority that affected people cannot meaningfully challenge, nor can participation justify substantively unacceptable distributions of benefit and burden. Prior authorization cannot substitute for renewed justification when the system or its conditions materially change. An answer that reveals an authorization gap or leaves a material concern unresolved should therefore trigger further justification, modification, or review.</p>
        <p>The test identifies where authorization remains insufficient and what evidence or governance response is needed before deployment proceeds or continues. The following recommendations translate these requirements into institutional governance mechanisms.</p>
      </sec>
    </sec>
    <sec>
      <title>Operationalizing Legitimacy: Practical Recommendations</title>
      <sec>
        <title>Overview</title>
        <p>The tripartite framework supports a recurring, risk-proportionate governance cycle of deliberation, legitimacy impact assessment, conditional authorization, disclosure and monitoring, and renewal, restriction, or withdrawal (<xref rid="figure2" ref-type="fig">Figure 2</xref>). The 5-question public authorization test applies across the cycle, while the 3 minimum auditable conditions provide a procedural foundation. The cycle specifies governance functions; it does not require a new committee or a separate assessment document at every stage.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Operational pathway for public authorization of clinical AI. Public authorization operates as a recurring governance cycle comprising deliberation; legitimacy impact assessment; conditional authorization; disclosure and monitoring; and renewal, restriction, or withdrawal. The 5-question public authorization test serves as a cross-cycle diagnostic. Visibility, affected-party input, and conditional reviewability constitute the 3 minimum auditable conditions. The dashed tags indicate the stages at which these conditions are most directly operationalized, although they may extend across the entire cycle.</p>
          </caption>
          <graphic xlink:href="jmir_v28i1e109467_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Minimum Auditable Conditions for Public Authorization</title>
        <p>Translating the tripartite framework into practice requires mechanisms that support, document, and renew public authorization. We propose 3 minimum auditable conditions for consequential clinical AI deployments: visibility, affected-party input, and conditional reviewability. Visibility means that a deployment is discoverable by those it affects. Affected-party input must be structured and provided before the purposes and governing conditions are established. Conditional reviewability requires at least 1 predefined review trigger that can prompt formal reconsideration and be invoked by a named actor outside the deploying team. In operational terms, deployments should be locatable, claimable, and revisable.</p>
        <p>These are minimum procedural conditions, not a comprehensive standard or proof of legitimacy. Together, they make AI-mediated authority identifiable, allow affected parties to influence choices before institutional embedding, and permit authorization to be reopened when circumstances change or its justification weakens. They are consistent with governance principles emphasizing transparency, stakeholder engagement, contestation, and redress [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref45">45</xref>].</p>
      </sec>
      <sec>
        <title>Risk-Proportionate Public Deliberation</title>
        <p>Deliberation should address the purposes and major trade-offs of proposed deployments [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. It should occur early enough to influence procurement, workflow design, conditions of use, and the scope of authorized uses [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref45">45</xref>], and should produce reasoned findings that receive documented institutional responses. Public deliberation should complement, not replace, technical, regulatory, ethical, and clinical review.</p>
        <p>We propose 4 determinants of governance intensity: clinical consequence; distributive reach across access, attention, opportunity, and burden; difficulty of reversal; and the absence of genuine, informed choice. Meaningful exit requires proportionate disclosure of AI involvement, an accessible non-AI pathway without unreasonable disadvantage in cost, waiting time, quality, or access, appropriate language and disability accommodations, and an opportunity to reconsider the choice. Where AI use is invisible or effectively unavoidable, stronger affected-party influence, accessible contestation, and more frequent review are warranted. Where a non-AI alternative is infeasible, institutions should explain why and justify continued AI use under clearly specified safeguards [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref45">45</xref>].</p>
      </sec>
      <sec>
        <title>Proportionate Implementation in Smaller Health Care Organizations</title>
        <p>Every health care organization using consequential AI should identify an accountable owner, make deployment visible, obtain timely affected-party input, publicly explain purposes and trade-offs, and maintain contestation and invocable review. These are minimum functions within the proposed framework; their organizational form can vary with risk and resources. They do not necessarily require dedicated panels, stand-alone assessments, bespoke registries, or in-house audit teams. Shared technical assessments can be reused, but local judgment is still needed to assess effects on workflows, identify excluded populations, and determine whether patients have a practical opportunity to opt out of AI-mediated care [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref45">45</xref>].</p>
        <p>A community clinic or smaller behavioral health care organization could use its patient advisory body, sampled interviews, including interviews with underrepresented patients, and a clinician working group; document decisions using standardized assessment and disclosure templates; publish information on an existing service page; and designate an existing safety lead to receive concerns. Where a patient body is absent, trusted community partners can support recruitment. Regional networks or professional associations could share assessment expertise, contract templates, and independent escalation mechanisms. The deploying health care organization retains responsibility for its local decision.</p>
        <p>Low-impact, readily reversible, and genuinely optional uses may receive abbreviated review. Consequential uses require documented affected-party input and conditional authorization; high-impact, broadly distributive, or effectively unavoidable uses warrant stronger representation and independent scrutiny, which can be obtained through shared services where necessary. To limit participation fatigue, institutions can reuse engagement where contexts are comparable and combine related reviews while preserving local input; participation should be accessible, compensated where feasible, and followed by an explanation of how input affected decisions. Periodic reassessment should continue, with additional review triggered by material changes, complaints, or emerging risks. Resource constraints should change the mechanism, not excuse failure to perform a necessary function [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref53">53</xref>].</p>
      </sec>
      <sec>
        <title>Legitimacy Impact Assessment and Public Reason</title>
        <p>Legitimacy impact assessment should ordinarily be integrated into, rather than duplicate, existing algorithmic, privacy, clinical safety, ethical, or fundamental rights impact assessments [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>]. Beyond bias, fairness, and technical performance, evaluation should consider the meaningful involvement of affected publics, the public defensibility of the deployment’s clinical or social purpose [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>], the distribution of benefits, burdens, and opportunity costs, and the availability of mechanisms for contestation and remedy [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>].</p>
        <p>A public summary should document major concerns, institutional responses, and how affected-party input influenced the final decision. It should include a concise public reason and value statement specifying what the system is intended to optimize, the principal value trade-offs accepted, why AI is preferred to feasible alternatives, and which uses fall outside the scope of authorization. Relevant trade-offs include whose outcomes are prioritized, which errors are considered acceptable, how efficiency is balanced against relational care, and how burdens are distributed across affected publics [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref57">57</xref>].</p>
      </sec>
      <sec>
        <title>Conditional Authorization and Periodic Renewal</title>
        <p>For consequential clinical AI deployments, we recommend conditional authorization with predefined review intervals rather than presumptively indefinite approval. Authorization should specify the approved purpose, population, workflow, degree of autonomy, human oversight requirements, accountable institutional owner, and conditions for continued use.</p>
        <p>Authorization should remain valid only while its specified conditions continue to hold. Formal reassessment should occur at predefined intervals and after material changes to the system, its intended use, population, vendor, or deployment context [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref57">57</xref>]. For AI-enabled devices regulated by the US FDA, relevant modification procedures should be aligned with any authorized predetermined change control plan [<xref ref-type="bibr" rid="ref58">58</xref>]. Review should permit continuation, modification, restriction, suspension, or withdrawal of authorization.</p>
        <p>At least 1 predefined review trigger should be invocable by a named actor outside the deploying team, such as a patient or community governance body, clinical safety office, ethics committee, or independent review body. Each authorization should specify the trigger, evidence required, and permissible actions. Review should not depend solely on self-initiation by the deploying team.</p>
      </sec>
      <sec>
        <title>Disclosure and Monitoring</title>
        <p>Publicly accessible deployment records should be maintained for consequential clinical AI through a registry or an existing service page, with the format adapted to the health care organization’s scale and resources. These records should identify the system, vendor, intended purpose, deployment context, and accountable institutional owner, and summarize local validation, population and equity analyses, affected-party input, key findings from the legitimacy impact assessment, contestation and remedy pathways, authorization conditions, and the date or trigger for subsequent review [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>].</p>
        <p>These records should also report material updates and aggregated or deidentified information on incidents, complaints, corrective actions, and significant subgroup concerns [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>], with proportionate safeguards for privacy, cybersecurity, and legitimate commercial confidentiality [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref57">57</xref>]. They should include the public reason and value statement, allowing affected publics to assess the stated purpose, accepted trade-offs, and institutional justification for deployment. Together, these records should support risk-proportionate public scrutiny, contestation, and review of AI-mediated institutional authority, without requiring a public referendum on every algorithm.</p>
      </sec>
    </sec>
    <sec>
      <title>Extending Accountability Beyond Institutional Boundaries</title>
      <sec>
        <title>Cross-Institutional Accountability and Remedy</title>
        <p>Health systems should provide accessible pathways for patients and clinicians to challenge consequential AI-mediated decisions, request meaningful human reconsideration, and obtain documented responses and corrective action [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. These pathways should include independent review beyond the deploying team for unresolved concerns or systemic problems.</p>
        <p>Accountability must also extend across organizational and contractual boundaries. Legal counsel and procurement teams, working with clinical and governance leads, should negotiate contractual provisions that make conditional reviewability operational. Contracts should specify notification requirements for material changes affecting performance or authorized use; access to version histories, audit logs, and relevant validation and subgroup evidence; investigation and remediation responsibilities and timelines; and audits by qualified independent reviewers.</p>
        <p>Health systems should secure contractual rights and operational means to pause, restrict, or disable use, revert to a prior version where feasible, and terminate the contract and transition to an alternative service when essential authorization conditions cannot be maintained. Access should be sufficient for oversight, with proportionate confidentiality safeguards, without necessarily requiring unrestricted source code disclosure. Urgent safety or security updates should follow an expedited notification and review process. These are proposed contractual safeguards, not universally available legal rights [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>].</p>
        <p>Deployment records should distinguish locally configurable choices from vendor-controlled constraints, including optimization targets, thresholds, updates, data dependencies, and modification limits. Outsourcing can deepen the problem of the unclaimed decision when an institution remains responsible for care but lacks the information, authority, or capacity to investigate and correct failures [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Shared contract templates and pooled procurement expertise may help smaller health care organizations secure these review conditions. Where essential review conditions cannot be secured, institutions should document the gap and restrict or decline the proposed use [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref57">57</xref>].</p>
      </sec>
      <sec>
        <title>Specified Human Oversight and Relational Answerability</title>
        <p>Human oversight should be specified rather than presumed. Requirements for human oversight are insufficient unless institutions define the conditions for meaningful review. These include the identity of the person responsible for reviewing AI-mediated decisions, when review occurs, what information and scope for independent judgment are available, what authority reviewers have to override recommendations or reverse decisions, and how review is documented [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref61">61</xref>]. A nominal human checkpoint may preserve procedural compliance while leaving algorithmic influence largely unchanged [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref45">45</xref>].</p>
        <p>Accountability must also be relational rather than merely documentary. Patients and clinicians should be able to identify who remains answerable for a consequential AI-assisted decision, request meaningful human reconsideration, understand the reasons for the resulting decision, and obtain correction or remedy when a decision produces avoidable harm or unjustified disadvantage [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>Limitations and Future Research</title>
      <sec>
        <title>Limitations</title>
        <p>The framework is normative and has not been empirically validated. Its dimensions, test, proposed governance arrangements, and process indicators require evaluation across applications, populations, and organizational settings. The examples illustrate proposals rather than demonstrated implementation effects.</p>
        <p>No participation procedure can guarantee that all affected interests are represented or eliminate disagreement. Cultural and legal contexts, resource disparities, and institutional power may distort participation [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. Mapping and publicly explaining representation decisions can expose these limitations but cannot resolve them mechanically. Advisory input should not be described as delegated decision authority.</p>
        <p>Governance requirements may delay beneficial deployment, create participation fatigue, favor large organizations or established vendors, duplicate existing oversight, and widen inequalities between health care organizations [<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]. The proportionate pathways proposed here are intended to mitigate those risks, but their costs and effectiveness remain uncertain.</p>
      </sec>
      <sec>
        <title>Future Research</title>
        <p>Measurement and construct validation. Studies should develop measures of perceived legitimacy distinct from trust, technology acceptance, satisfaction, perceived usefulness, and willingness to use AI [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]. Conventional acceptance frameworks address perceived usefulness, behavioral intention, and technology use [<xref ref-type="bibr" rid="ref64">64</xref>-<xref ref-type="bibr" rid="ref66">66</xref>]. Measures of perceived legitimacy should assess the perceived rightfulness of authority, the opportunity for procedural voice, the adequacy of public justification, distributive fairness, contestability, and access to remedy. Validation should examine reliability, construct validity, and measurement invariance across populations and jurisdictions. Perceived legitimacy cannot, by itself, establish normative legitimacy.</p>
        <p>Participatory governance and implementation. Comparative studies should examine whether participation changes deployment purposes, conditions, or safeguards; whether legitimacy assessments identify concerns missed by conventional review; and whether procurement provisions and review mechanisms enable corrective action [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]. Comparisons across health care organization sizes should assess abbreviated, integrated, and shared governance arrangements, including costs, staff time, participation burden, deployment delays, and opportunity costs [<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]. Evaluation should examine whether affected-public mapping and specified participation powers change whose concerns influence decisions and whether shared resources preserve local influence and institutional responsibility.</p>
        <p>Authorization processes and process indicators. Three candidate indicators warrant evaluation: authorization coverage, the proportion of consequential deployments with documented evidence for all 3 minimum auditable conditions; time to affected-party input, measured from formal initiation of deployment consideration to the first structured input from a materially affected group; and invocable review trigger rate, the proportion of consequential deployments with a predefined trigger invocable by a named actor outside the deploying team. The review trigger rate provides a component-specific measure that may identify weaknesses obscured by overall authorization coverage. These indicators should be assessed alongside evidence of whether decisions remained open to influence, meaningful choice, actual participation influence, and the timeliness and consequences of review. They should not be combined into a numerical legitimacy score.</p>
        <p>Comparative and jurisdictional governance. Research should examine how regulation, professional standards, ownership, commercial incentives, financing, and Indigenous and community governance shape public authorization [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]. Indigenous data governance frameworks foreground collective benefit, authority to control, responsibility, and ethics [<xref ref-type="bibr" rid="ref67">67</xref>]. Studies should include both patients and frontline clinicians.</p>
      </sec>
    </sec>
    <sec>
      <title>Conclusions</title>
      <p>Institutional approval and public authorization are not equivalent. The unclaimed decision identifies consequential deployment choices for which no actor clearly assumes responsibility for public justification. We propose a normative framework comprising procedural authorization, substantive justification, and relational renewal, supported by 3 minimum auditable conditions and the 5-question public authorization test. Governance intensity should reflect clinical consequence; distributive reach; difficulty of reversal; and the absence of genuine, informed choice. The proposed arrangements require empirical evaluation and do not constitute a certification standard or legitimacy score. Institutional approval permits deployment; public authorization requires continuing justification of the authority exercised through it.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">FDA</term>
          <def>
            <p>Food and Drug Administration</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <notes>
      <sec>
        <title>Funding</title>
        <p>The authors declare that no external financial support or grants were received from any public, commercial, or not-for-profit organization for the research, authorship, or publication of this article.</p>
      </sec>
    </notes>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Data sharing is not applicable to this article, as no new data were created or analyzed in this study.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>JL and SL conceived and designed the Viewpoint, performed the literature review, and drafted the manuscript. Both authors critically revised the manuscript for substantive intellectual content and approved the final version.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <notes>
      <sec>
        <title>Generative AI Use</title>
        <p>After the initial draft was completed, ChatGPT (version 6.1; OpenAI) was used to assist with language refinement. The authors independently evaluated all AI-generated revisions, made further modifications as needed, and take full responsibility for the content of the final manuscript.</p>
      </sec>
    </notes>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Komanduri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bhadouriya</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Shrestha</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Nikolov</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schulman</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Evaluating transparency in AI/ML model characteristics for FDA-reviewed medical devices</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <month>11</month>
          <day>17</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>673</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-02052-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-02052-9</pub-id>
          <pub-id pub-id-type="medline">41249460</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-02052-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC12624113</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>Windecker</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baj</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Shiri</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kazaj</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Kaesmacher</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gräni</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Siontis</surname>
              <given-names>GC</given-names>
            </name>
          </person-group>
          <article-title>Generalizability of FDA-approved AI-enabled medical devices for clinical use</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>04</month>
          <day>01</day>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>e258052</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://boris-portal.unibe.ch/handle/20.500.12422/210722"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.8052</pub-id>
          <pub-id pub-id-type="medline">40305017</pub-id>
          <pub-id pub-id-type="pii">2833324</pub-id>
          <pub-id pub-id-type="pmcid">PMC12044510</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</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 and amending Regulations (EC) No 300/2008, (EU) No 167/2013, (EU) No 168/2013, (EU) 2018/858, (EU) 2018/1139 and (EU) 2019/2144 and Directives 2014/90/EU, (EU) 2016/797 and (EU) 2020/1828 (Artificial Intelligence Act)</article-title>
          <source>European Union</source>
          <access-date>2026-06-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/eli/reg/2024/1689/oj">https://eur-lex.europa.eu/eli/reg/2024/1689/oj</ext-link>
          </comment>
        </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>Solomonides</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Koski</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Atabaki</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Weinberg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McGreevey</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Kannry</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lehmann</surname>
              <given-names>CU</given-names>
            </name>
          </person-group>
          <article-title>Defining AMIA's artificial intelligence principles</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2022</year>
          <month>03</month>
          <day>15</day>
          <volume>29</volume>
          <issue>4</issue>
          <fpage>585</fpage>
          <lpage>91</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35190824"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocac006</pub-id>
          <pub-id pub-id-type="medline">35190824</pub-id>
          <pub-id pub-id-type="pii">6534106</pub-id>
          <pub-id pub-id-type="pmcid">PMC8922174</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>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>
          <month>08</month>
          <day>11</day>
          <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="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Eaneff</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Butte</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>The case for algorithmic stewardship for artificial intelligence and machine learning technologies</article-title>
          <source>JAMA</source>
          <year>2020</year>
          <month>10</month>
          <day>13</day>
          <volume>324</volume>
          <issue>14</issue>
          <fpage>1397</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2020.9371</pub-id>
          <pub-id pub-id-type="medline">32926087</pub-id>
          <pub-id pub-id-type="pii">2770772</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>Shah</surname>
              <given-names>NH</given-names>
            </name>
            <name name-style="western">
              <surname>Halamka</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Saria</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pencina</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tazbaz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tripathi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Callahan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hildahl</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A nationwide network of health AI assurance laboratories</article-title>
          <source>JAMA</source>
          <year>2024</year>
          <month>01</month>
          <day>16</day>
          <volume>331</volume>
          <issue>3</issue>
          <fpage>245</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2023.26930</pub-id>
          <pub-id pub-id-type="medline">38117493</pub-id>
          <pub-id pub-id-type="pii">2813425</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>Mello</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Nag</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tuttle</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Char</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Engaging patients in AI governance</article-title>
          <source>BMJ Digit Health Ai</source>
          <year>2026</year>
          <month>04</month>
          <day>10</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e000099</fpage>
          <pub-id pub-id-type="doi">10.1136/bmjdh-2026-000099</pub-id>
          <pub-id pub-id-type="medline">42712282</pub-id>
          <pub-id pub-id-type="pii">bmjdh-2026-000099</pub-id>
          <pub-id pub-id-type="pmcid">PMC13492535</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McKay</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Prestwich</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Treanor</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hallowell</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Public governance of medical artificial intelligence research in the UK: an integrated multi-scale model</article-title>
          <source>Res Involv Engagem</source>
          <year>2022</year>
          <month>05</month>
          <day>21</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>21</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://researchinvolvement.biomedcentral.com/articles/10.1186/s40900-022-00357-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40900-022-00357-7</pub-id>
          <pub-id pub-id-type="medline">35598004</pub-id>
          <pub-id pub-id-type="pii">10.1186/s40900-022-00357-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC9123617</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beetham</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>The Legitimation of Power</source>
          <year>2013</year>
          <publisher-loc>Basingstoke, UK</publisher-loc>
          <publisher-name>Palgrave Macmillan</publisher-name>
        </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>Abdel-Hafez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ebrahimabadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Graham</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Slee</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Whitfield</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in medical referrals triage based on clinical prioritization criteria</article-title>
          <source>Front Digit Health</source>
          <year>2023</year>
          <month>10</month>
          <day>27</day>
          <volume>5</volume>
          <fpage>1192975</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37964894"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2023.1192975</pub-id>
          <pub-id pub-id-type="medline">37964894</pub-id>
          <pub-id pub-id-type="pmcid">PMC10642163</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>Vergara</surname>
              <given-names>PO</given-names>
            </name>
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Mattiello</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Montelongo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Roman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Katz</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wives</surname>
              <given-names>LK</given-names>
            </name>
            <name name-style="western">
              <surname>Rados</surname>
              <given-names>DV</given-names>
            </name>
          </person-group>
          <article-title>Accuracy of artificial intelligence for gatekeeping in referrals to specialized care</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>06</month>
          <day>02</day>
          <volume>8</volume>
          <issue>6</issue>
          <fpage>e2513285</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2025.13285"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.13285</pub-id>
          <pub-id pub-id-type="medline">40459894</pub-id>
          <pub-id pub-id-type="pii">2834850</pub-id>
          <pub-id pub-id-type="pmcid">PMC12134955</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>Habli</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Lawton</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Porter</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in health care: accountability and safety</article-title>
          <source>Bull World Health Organ</source>
          <year>2020</year>
          <month>04</month>
          <day>01</day>
          <volume>98</volume>
          <issue>4</issue>
          <fpage>251</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32284648"/>
          </comment>
          <pub-id pub-id-type="doi">10.2471/BLT.19.237487</pub-id>
          <pub-id pub-id-type="medline">32284648</pub-id>
          <pub-id pub-id-type="pii">BLT.19.237487</pub-id>
          <pub-id pub-id-type="pmcid">PMC7133468</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>Carter</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Laurie</surname>
              <given-names>GT</given-names>
            </name>
            <name name-style="western">
              <surname>Dixon-Woods</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The social licence for research: why care.data ran into trouble</article-title>
          <source>J Med Ethics</source>
          <year>2015</year>
          <month>05</month>
          <volume>41</volume>
          <issue>5</issue>
          <fpage>404</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jme.bmj.com/lookup/pmidlookup?view=long&amp;pmid=25617016"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/medethics-2014-102374</pub-id>
          <pub-id pub-id-type="medline">25617016</pub-id>
          <pub-id pub-id-type="pii">medethics-2014-102374</pub-id>
          <pub-id pub-id-type="pmcid">PMC4431337</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>Review of data security, consent and opt-outs</article-title>
          <source>United Kingdom Government</source>
          <year>2017</year>
          <access-date>2026-06-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/government/publications/review-of-data-security-consent-and-opt-outs">https://www.gov.uk/government/publications/review-of-data-security-consent-and-opt-outs</ext-link>
          </comment>
        </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>Powles</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hodson</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Google DeepMind and healthcare in an age of algorithms</article-title>
          <source>Health Technol (Berl)</source>
          <year>2017</year>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>351</fpage>
          <lpage>67</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29308344"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12553-017-0179-1</pub-id>
          <pub-id pub-id-type="medline">29308344</pub-id>
          <pub-id pub-id-type="pii">179</pub-id>
          <pub-id pub-id-type="pmcid">PMC5741783</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>Google DeepMind and class action lawsuit</article-title>
          <source>Information Commissioner's Office</source>
          <access-date>2026-06-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/for-the-public/ico-40/google-deepmind-and-class-action-lawsuit/">https://ico.org.uk/for-the-public/ico-40/google-deepmind-and-class-action-lawsuit/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bharti</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>O'Donovan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Smallman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Public trust, deliberative engagement and health data projects: beyond legal provisions</article-title>
          <source>Engag Sci Technol Soc</source>
          <year>2021</year>
          <month>10</month>
          <day>05</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>125</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.17351/ests2021.1197</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Daniels</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sabin</surname>
              <given-names>JE</given-names>
            </name>
          </person-group>
          <article-title>Accountability for reasonableness: an update</article-title>
          <source>BMJ</source>
          <year>2008</year>
          <month>10</month>
          <day>09</day>
          <volume>337</volume>
          <fpage>a1850</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.a1850</pub-id>
          <pub-id pub-id-type="medline">18845595</pub-id>
          <pub-id pub-id-type="pii">337/oct09_1/a1850</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>Suchman</surname>
              <given-names>MC</given-names>
            </name>
          </person-group>
          <article-title>Managing legitimacy: strategic and institutional approaches</article-title>
          <source>Acad Manag Rev</source>
          <year>1995</year>
          <month>07</month>
          <volume>20</volume>
          <issue>3</issue>
          <fpage>571</fpage>
          <lpage>610</lpage>
          <pub-id pub-id-type="doi">10.2307/258788</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Buchanan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Keohane</surname>
              <given-names>RO</given-names>
            </name>
          </person-group>
          <article-title>The legitimacy of global governance institutions</article-title>
          <source>Ethics Int Aff</source>
          <year>2011</year>
          <month>03</month>
          <day>25</day>
          <volume>20</volume>
          <issue>4</issue>
          <fpage>405</fpage>
          <lpage>37</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1747-7093.2006.00043.x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>MH</given-names>
            </name>
          </person-group>
          <source>Creating Public Value: Strategic Management in Government</source>
          <year>1995</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>Harvard University Press</publisher-name>
        </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>Schmidt</surname>
              <given-names>VA</given-names>
            </name>
          </person-group>
          <article-title>Democracy and legitimacy in the European Union revisited: input, output and ‘throughput’</article-title>
          <source>Polit Stud</source>
          <year>2012</year>
          <month>08</month>
          <day>06</day>
          <volume>61</volume>
          <issue>1</issue>
          <fpage>2</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1467-9248.2012.00962.x</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>Cohen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Suzor</surname>
              <given-names>NP</given-names>
            </name>
          </person-group>
          <article-title>Contesting the public interest in AI governance</article-title>
          <source>Internet Policy Rev</source>
          <year>2024</year>
          <month>09</month>
          <day>30</day>
          <volume>13</volume>
          <issue>3</issue>
          <pub-id pub-id-type="doi">10.14763/2024.3.1794</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peter</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Zalta</surname>
              <given-names>EN</given-names>
            </name>
            <name name-style="western">
              <surname>Nodelman</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Political legitimacy</article-title>
          <source>The Stanford Encyclopedia of Philosophy</source>
          <year>2023</year>
          <publisher-loc>Stanford, CA</publisher-loc>
          <publisher-name>Metaphysics Research Lab, Stanford University</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peter</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <source>The Grounds of Political Legitimacy</source>
          <year>2023</year>
          <publisher-loc>Oxford, UK</publisher-loc>
          <publisher-name>Oxford University Press</publisher-name>
        </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>Vayena</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Blasimme</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>IG</given-names>
            </name>
          </person-group>
          <article-title>Machine learning in medicine: addressing ethical challenges</article-title>
          <source>PLoS Med</source>
          <year>2018</year>
          <month>11</month>
          <day>6</day>
          <volume>15</volume>
          <issue>11</issue>
          <fpage>e1002689</fpage>
          <pub-id pub-id-type="doi">10.1371/journal.pmed.1002689</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>Ethics and governance of artificial intelligence for health: WHO guidance</article-title>
          <source>World Health Organization</source>
          <access-date>2026-06-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/9789240029200">https://www.who.int/publications/i/item/9789240029200</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lazar</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Sobel</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wall</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Legitimacy, authority, and democratic duties of explanation</article-title>
          <source>Oxford Studies in Political Philosophy</source>
          <year>2024</year>
          <publisher-loc>Oxford, UK</publisher-loc>
          <publisher-name>Oxford University Press</publisher-name>
        </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>Bartlett</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Towards accountable, legitimate and trustworthy AI in healthcare: enhancing AI ethics with effective data stewardship</article-title>
          <source>New Bioeth</source>
          <year>2024</year>
          <month>12</month>
          <volume>30</volume>
          <issue>4</issue>
          <fpage>285</fpage>
          <lpage>309</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.1080/20502877.2025.2482282?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/20502877.2025.2482282</pub-id>
          <pub-id pub-id-type="medline">40135972</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>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>
          <month>12</month>
          <day>01</day>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.1177/2053951716679679</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>List of artificial intelligence-enabled medical devices</article-title>
          <source>U.S. Food &amp; Drug Administration</source>
          <access-date>2026-06-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-enabled-medical-devices">https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-enabled-medical-devices</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
          <article-title>Quality improvement activities FAQs</article-title>
          <source>U.S. Department of Health and Human Services</source>
          <access-date>2026-06-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/ohrp/regulations-and-policy/guidance/faq/quality-improvement-activities/index.html">https://www.hhs.gov/ohrp/regulations-and-policy/guidance/faq/quality-improvement-activities/index.html</ext-link>
          </comment>
        </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>Liao</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Adelaine</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Afshar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Patterson</surname>
              <given-names>BW</given-names>
            </name>
          </person-group>
          <article-title>Governance of clinical AI applications to facilitate safe and equitable deployment in a large health system: key elements and early successes</article-title>
          <source>Front Digit Health</source>
          <year>2022</year>
          <month>8</month>
          <day>24</day>
          <volume>4</volume>
          <fpage>931439</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36093386"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2022.931439</pub-id>
          <pub-id pub-id-type="medline">36093386</pub-id>
          <pub-id pub-id-type="pmcid">PMC9448877</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>Abejirinde</surname>
              <given-names>IO</given-names>
            </name>
            <name name-style="western">
              <surname>Itanyi</surname>
              <given-names>IU</given-names>
            </name>
            <name name-style="western">
              <surname>Kornas</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zaim</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Guha</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chui</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Lipscombe</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rosella</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Principles and practices of community engagement in AI for population health: formative qualitative study of the AI for diabetes prediction and prevention project</article-title>
          <source>J Particip Med</source>
          <year>2025</year>
          <month>10</month>
          <day>02</day>
          <volume>17</volume>
          <fpage>e69497</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jopm.jmir.org/2025//e69497/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/69497</pub-id>
          <pub-id pub-id-type="medline">41037755</pub-id>
          <pub-id pub-id-type="pii">v17i1e69497</pub-id>
          <pub-id pub-id-type="pmcid">PMC12490773</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>Ulizio</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Dua</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mukul</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Areti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kostick-Quenet</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rahimzadeh</surname>
              <given-names>VN</given-names>
            </name>
          </person-group>
          <article-title>Exploring the ethical and practical considerations of artificial intelligence in real-world health care settings: stakeholder focus group study</article-title>
          <source>JMIR AI</source>
          <year>2026</year>
          <month>04</month>
          <day>02</day>
          <volume>5</volume>
          <fpage>e85163</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ai.jmir.org/2026//e85163/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/85163</pub-id>
          <pub-id pub-id-type="medline">41927044</pub-id>
          <pub-id pub-id-type="pii">v5i1e85163</pub-id>
          <pub-id pub-id-type="pmcid">PMC13087557</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>Lang</surname>
              <given-names>BH</given-names>
            </name>
            <name name-style="western">
              <surname>Nyholm</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Blumenthal-Barby</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Responsibility gaps and black box healthcare AI: shared responsibilization as a solution</article-title>
          <source>Digit Soc</source>
          <year>2023</year>
          <month>12</month>
          <volume>2</volume>
          <issue>3</issue>
          <fpage>52</fpage>
          <pub-id pub-id-type="doi">10.1007/s44206-023-00073-z</pub-id>
          <pub-id pub-id-type="medline">38596344</pub-id>
          <pub-id pub-id-type="pmcid">PMC11003475</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>Rose</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Shapiro</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>An ethically supported framework for determining patient notification and informed consent practices when using artificial intelligence in health care</article-title>
          <source>Chest</source>
          <year>2024</year>
          <month>09</month>
          <volume>166</volume>
          <issue>3</issue>
          <fpage>572</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0012-3692(24)00633-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.chest.2024.04.014</pub-id>
          <pub-id pub-id-type="medline">38788895</pub-id>
          <pub-id pub-id-type="pii">S0012-3692(24)00633-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC11443239</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>Sheehan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Fistein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Davies</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>Parker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Savulescu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Authority and the future of consent in population-level biomedical research</article-title>
          <source>Public Health Ethics</source>
          <year>2019</year>
          <month>10</month>
          <day>30</day>
          <volume>12</volume>
          <issue>3</issue>
          <fpage>225</fpage>
          <lpage>36</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32082417"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/phe/phz015</pub-id>
          <pub-id pub-id-type="medline">32082417</pub-id>
          <pub-id pub-id-type="pii">phz015</pub-id>
          <pub-id pub-id-type="pmcid">PMC7020771</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>Nong</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Platt</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Patients' trust in health systems to use artificial intelligence</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>02</month>
          <day>03</day>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>e2460628</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2024.60628"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.60628</pub-id>
          <pub-id pub-id-type="medline">39951270</pub-id>
          <pub-id pub-id-type="pii">2830240</pub-id>
          <pub-id pub-id-type="pmcid">PMC11829222</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Price</surname>
              <given-names>WN II</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>Liability for use of artificial intelligence in medicine</article-title>
          <source>Research Handbook on Health, AI and the Law</source>
          <year>2024</year>
          <month>07</month>
          <day>16</day>
          <publisher-loc>Cheltenham, UK</publisher-loc>
          <publisher-name>Edward Elgar Publishing</publisher-name>
        </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>Schuitmaker</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Drogt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Benders</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jongsma</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Physicians' required competencies in AI-assisted clinical settings: a systematic review</article-title>
          <source>Br Med Bull</source>
          <year>2025</year>
          <month>01</month>
          <day>16</day>
          <volume>153</volume>
          <issue>1</issue>
          <fpage>ldae025</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/bmb/article-lookup/doi/10.1093/bmb/ldae025"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/bmb/ldae025</pub-id>
          <pub-id pub-id-type="medline">39821209</pub-id>
          <pub-id pub-id-type="pii">7958568</pub-id>
          <pub-id pub-id-type="pmcid">PMC11738171</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>Vo</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Aquino</surname>
              <given-names>YS</given-names>
            </name>
            <name name-style="western">
              <surname>Carter</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Do</surname>
              <given-names>QN</given-names>
            </name>
            <name name-style="western">
              <surname>Woode</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>Multi-stakeholder preferences for the use of artificial intelligence in healthcare: a systematic review and thematic analysis</article-title>
          <source>Soc Sci Med</source>
          <year>2023</year>
          <month>12</month>
          <volume>338</volume>
          <fpage>116357</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0277-9536(23)00714-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.socscimed.2023.116357</pub-id>
          <pub-id pub-id-type="medline">37949020</pub-id>
          <pub-id pub-id-type="pii">S0277-9536(23)00714-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ludewigs</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Narchi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kiefer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Winkler</surname>
              <given-names>EC</given-names>
            </name>
          </person-group>
          <article-title>Ethics of the fiduciary relationship between patient and physician: the case of informed consent</article-title>
          <source>J Med Ethics</source>
          <year>2024</year>
          <month>12</month>
          <day>23</day>
          <volume>51</volume>
          <issue>1</issue>
          <fpage>59</fpage>
          <lpage>66</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jme.bmj.com/lookup/pmidlookup?view=long&amp;pmid=36564172"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jme-2022-108539</pub-id>
          <pub-id pub-id-type="medline">36564172</pub-id>
          <pub-id pub-id-type="pii">jme-2022-108539</pub-id>
          <pub-id pub-id-type="pmcid">PMC11877024</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lekadir</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Frangi</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Porras</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Glocker</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Cintas</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Langlotz</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Weicken</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Asselbergs</surname>
              <given-names>FW</given-names>
            </name>
            <name name-style="western">
              <surname>Prior</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Kaissis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Tsakou</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Buvat</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kalpathy-Cramer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mongan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schnabel</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Kushibar</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Riklund</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Marias</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Amugongo</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Fromont</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Maier-Hein</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cerdá-Alberich</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Martí-Bonmatí</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cardoso</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bobowicz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shabani</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tsiknakis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zuluaga</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Fritzsche</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Camacho</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Linguraru</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Wenzel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>De Bruijne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tolsgaard</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Goisauf</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cano Abadía</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Papanikolaou</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lazrak</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Pujol</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Osuala</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Napel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Colantonio</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aussó</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>WA</given-names>
            </name>
            <name name-style="western">
              <surname>Salahuddin</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Starmans</surname>
              <given-names>MP</given-names>
            </name>
          </person-group>
          <article-title>FUTURE-AI: international consensus guideline for trustworthy and deployable artificial intelligence in healthcare</article-title>
          <source>BMJ</source>
          <year>2025</year>
          <month>02</month>
          <day>05</day>
          <volume>388</volume>
          <fpage>e081554</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=39909534"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2024-081554</pub-id>
          <pub-id pub-id-type="medline">39909534</pub-id>
          <pub-id pub-id-type="pmcid">PMC11795397</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>Keyes</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Callahan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pandya</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Ambers</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Banda</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Fuentes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lugtu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Masariya</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Nallan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Alsentzer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Dash</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Eisenberg</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kotecha</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Revri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeffer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>NH</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>SS</given-names>
            </name>
          </person-group>
          <article-title>Why and how to monitor deployed AI systems in health care</article-title>
          <source>NEJM Catal Innov Care Deliv</source>
          <year>2026</year>
          <month>06</month>
          <volume>7</volume>
          <issue>6</issue>
          <fpage>CAT250372</fpage>
          <pub-id pub-id-type="doi">10.1056/CAT.25.0372</pub-id>
          <pub-id pub-id-type="medline">42418612</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>Platt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nong</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Carmona</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kardia</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Public attitudes toward notification of use of artificial intelligence in health care</article-title>
          <source>JAMA Netw Open</source>
          <year>2024</year>
          <month>12</month>
          <day>02</day>
          <volume>7</volume>
          <issue>12</issue>
          <fpage>e2450102</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2024.50102"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.50102</pub-id>
          <pub-id pub-id-type="medline">39661391</pub-id>
          <pub-id pub-id-type="pii">2827758</pub-id>
          <pub-id pub-id-type="pmcid">PMC11635529</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>van der Veer</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Riste</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cheraghi-Sohi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Phipps</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Tully</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Bozentko</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Atwood</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hubbard</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wiper</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Oswald</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Peek</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Trading off accuracy and explainability in AI decision-making: findings from 2 citizens' juries</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2021</year>
          <month>09</month>
          <day>18</day>
          <volume>28</volume>
          <issue>10</issue>
          <fpage>2128</fpage>
          <lpage>38</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34333646"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocab127</pub-id>
          <pub-id pub-id-type="medline">34333646</pub-id>
          <pub-id pub-id-type="pii">6333351</pub-id>
          <pub-id pub-id-type="pmcid">PMC8522832</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bracic</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Spector-Bagdady</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Towle</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>James</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Price</surname>
              <given-names>WN II</given-names>
            </name>
          </person-group>
          <article-title>Factors for patient trust and acceptance of medical artificial intelligence</article-title>
          <source>JAMA Netw Open</source>
          <year>2026</year>
          <month>03</month>
          <day>02</day>
          <volume>9</volume>
          <issue>3</issue>
          <fpage>e260815</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2026.0815"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2026.0815</pub-id>
          <pub-id pub-id-type="medline">41784960</pub-id>
          <pub-id pub-id-type="pii">2845955</pub-id>
          <pub-id pub-id-type="pmcid">PMC12964161</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beets</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Newman</surname>
              <given-names>TP</given-names>
            </name>
            <name name-style="western">
              <surname>Howell</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Bao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Surveying public perceptions of artificial intelligence in health care in the United States: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <month>04</month>
          <day>04</day>
          <volume>25</volume>
          <fpage>e40337</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e40337/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/40337</pub-id>
          <pub-id pub-id-type="medline">37014676</pub-id>
          <pub-id pub-id-type="pii">v25i1e40337</pub-id>
          <pub-id pub-id-type="pmcid">PMC10131909</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Muller</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Kalkman</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>van Thiel</surname>
              <given-names>GJ</given-names>
            </name>
            <name name-style="western">
              <surname>Mostert</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Delden</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>The social licence for data-intensive health research: towards co-creation, public value and trust</article-title>
          <source>BMC Med Ethics</source>
          <year>2021</year>
          <month>08</month>
          <day>10</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>110</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedethics.biomedcentral.com/articles/10.1186/s12910-021-00677-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12910-021-00677-5</pub-id>
          <pub-id pub-id-type="medline">34376204</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12910-021-00677-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC8353823</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Busch</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>García-Juárez</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Toapanta-Yanchapaxi</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>Gorelik</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gorelik</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez-Granillo</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Ferrarotti</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Cuong</surname>
              <given-names>NN</given-names>
            </name>
            <name name-style="western">
              <surname>Thi</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Tuncel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kaya</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Solis-Barquero</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Mendez Avila</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Ivanova</surname>
              <given-names>NG</given-names>
            </name>
            <name name-style="western">
              <surname>Kitamura</surname>
              <given-names>FC</given-names>
            </name>
            <name name-style="western">
              <surname>Hayama</surname>
              <given-names>KY</given-names>
            </name>
            <name name-style="western">
              <surname>Puntunet Bates</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Torres</surname>
              <given-names>PI</given-names>
            </name>
            <name name-style="western">
              <surname>Ortiz-Prado</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Izquierdo-Condoy</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Schwarz</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Hofstaetter</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Hide</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Takeda</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Peric</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Pilko</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Thulesius</surname>
              <given-names>HO</given-names>
            </name>
            <name name-style="western">
              <surname>Lindow</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kolawole</surname>
              <given-names>IK</given-names>
            </name>
            <name name-style="western">
              <surname>Olatoke</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Grzybowski</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Corlateanu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Iaconi</surname>
              <given-names>OS</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Domitrz</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kepczynska</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mihalcin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fašaneková</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zatonski</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Fulek</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Molnár</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Maihoub</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva Gama</surname>
              <given-names>ZA</given-names>
            </name>
            <name name-style="western">
              <surname>Saba</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sountoulides</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Makowski</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Aerts</surname>
              <given-names>HJ</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>
            <collab>COMFORT consortium</collab>
            <name name-style="western">
              <surname>Navarro</surname>
              <given-names>ÁA</given-names>
            </name>
            <name name-style="western">
              <surname>Águas</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Aineseder</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Alomar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Al Sliman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Anand</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Angkurawaranon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aoki</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Arkoh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ashraf</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Astri</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Bakhshi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bayramov</surname>
              <given-names>NY</given-names>
            </name>
            <name name-style="western">
              <surname>Billis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bitencourt</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Bolejko</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bollas Becerra</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bwambale</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Capela</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cau</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Chacon-Acevedo</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Chaunzwa</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>Chojniak</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Clements</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Cuocolo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dahlblom</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Sousa</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Villarrubia</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>VB</given-names>
            </name>
            <name name-style="western">
              <surname>Dhakal</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Dignum</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Andrade</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Ferraioli</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ganguly</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Garg</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Savevska</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Radovikj</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Gkartzoni</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gorospe</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Griffin</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Hadamitzky</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ndahiro</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Hering</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hochhegger</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Huseynova</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Ishida</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kader</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kavnoudias</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kolostoumpis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Koshy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kruger</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Löser</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lucijanic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mantziari</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Margue</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>McFadden</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Miyake</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morakote</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Ngabonziza</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Niehues</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Nortje</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Palaian</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pentara</surname>
              <given-names>NV</given-names>
            </name>
            <name name-style="western">
              <surname>de Almeida</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Poma</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Purwoko</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pyrgidis</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rafailidis</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Rainey</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ribeiro</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Agudelo</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Sado</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Saidman</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Saturno-Hernandez</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Suryadevara</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Schulz</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Soric</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Soto-Pérez-Olivares</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stanzione</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Struck</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Takaoka</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Tanioka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Huyen</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Truhn</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>van Dijk</surname>
              <given-names>EH</given-names>
            </name>
            <name name-style="western">
              <surname>van Wijngaarden</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>YC</given-names>
            </name>
            <name name-style="western">
              <surname>Weidlich</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Multinational attitudes toward AI in health care and diagnostics among hospital patients</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>06</month>
          <day>02</day>
          <volume>8</volume>
          <issue>6</issue>
          <fpage>e2514452</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2025.14452"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.14452</pub-id>
          <pub-id pub-id-type="medline">40493367</pub-id>
          <pub-id pub-id-type="pii">2835159</pub-id>
          <pub-id pub-id-type="pmcid">PMC12152705</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ocloo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Garfield</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Franklin</surname>
              <given-names>BD</given-names>
            </name>
            <name name-style="western">
              <surname>Dawson</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Exploring the theory, barriers and enablers for patient and public involvement across health, social care and patient safety: a systematic review of reviews</article-title>
          <source>Health Res Policy Syst</source>
          <year>2021</year>
          <month>01</month>
          <day>20</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>8</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health-policy-systems.biomedcentral.com/articles/10.1186/s12961-020-00644-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12961-020-00644-3</pub-id>
          <pub-id pub-id-type="medline">33472647</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12961-020-00644-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7816359</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Department of Health‚ Education‚ Welfare</collab>
            <collab>National Commission for the Protection of Human Subjects of Biomedical and Behavioral Research</collab>
          </person-group>
          <article-title>The Belmont Report. Ethical principles and guidelines for the protection of human subjects of research</article-title>
          <source>J Am Coll Dent</source>
          <year>2014</year>
          <volume>81</volume>
          <issue>3</issue>
          <fpage>4</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="medline">25951677</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goisauf</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cano Abadía</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Akyüz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bobowicz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Buyx</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Colussi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Fritzsche</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Lekadir</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Marttinen</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Mayrhofer</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Meszaros</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Trust, trustworthiness, and the future of medical AI: outcomes of an interdisciplinary expert workshop</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <month>06</month>
          <day>02</day>
          <volume>27</volume>
          <fpage>e71236</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e71236/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/71236</pub-id>
          <pub-id pub-id-type="medline">40455564</pub-id>
          <pub-id pub-id-type="pii">v27i1e71236</pub-id>
          <pub-id pub-id-type="pmcid">PMC12171647</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mathias</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Vasey</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Chalkidou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Riedemann</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Melvin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gilbert</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Safe AI-enabled digital health technologies need built-in open feedback</article-title>
          <source>Nat Med</source>
          <year>2025</year>
          <month>02</month>
          <volume>31</volume>
          <issue>2</issue>
          <fpage>370</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-024-03397-6</pub-id>
          <pub-id pub-id-type="medline">39905271</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-024-03397-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tabassi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Artificial Intelligence Risk Management Framework (AI RMF 1.0)</article-title>
          <source>NIST Trustworthy and Responsible AI, National Institute of Standards and Technology</source>
          <year>2023</year>
          <access-date>2026-10-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10">https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <article-title>Marketing submission recommendations for a predetermined change control plan for artificial intelligence-enabled device software functions: guidance for industry and Food and Drug Administration staff</article-title>
          <source>U.S. Food &amp; Drug Administration</source>
          <year>2025</year>
          <month>08</month>
          <access-date>2026-06-28</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="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <article-title>Health data, technology, and interoperability: certification program updates, algorithm transparency, and information sharing</article-title>
          <source>Federal Register</source>
          <year>2024</year>
          <access-date>2026-10-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.federalregister.gov/documents/2024/01/09/2023-28857/health-data-technology-and-interoperability-certification-program-updates-algorithm-transparency-and">https://www.federalregister.gov/documents/2024/01/09/2023-28857/health-data-technology-and-interoperability-certification-program-updates-algorithm-transparency-and</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>TT</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>
          <month>11</month>
          <day>01</day>
          <volume>31</volume>
          <issue>11</issue>
          <fpage>2730</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/jamia/article-lookup/doi/10.1093/jamia/ocae209"/>
          </comment>
          <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="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Toro-Tobon</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ponte</surname>
              <given-names>OP</given-names>
            </name>
            <name name-style="western">
              <surname>Montori</surname>
              <given-names>VM</given-names>
            </name>
            <name name-style="western">
              <surname>Brito</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <article-title>Clinician in the loop: a flawed solution for AI oversight</article-title>
          <source>BMJ</source>
          <year>2026</year>
          <month>05</month>
          <day>05</day>
          <volume>393</volume>
          <fpage>e089213</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=42086290"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2025-089213</pub-id>
          <pub-id pub-id-type="medline">42086290</pub-id>
          <pub-id pub-id-type="pmcid">PMC13140781</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bergholtz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wolf</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Crine</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Cleeve</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Santana</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Björkman</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Patient and public involvement in healthcare: a systematic mapping review of systematic reviews - identification of current research and possible directions for future research</article-title>
          <source>BMJ Open</source>
          <year>2024</year>
          <month>09</month>
          <day>19</day>
          <volume>14</volume>
          <issue>9</issue>
          <fpage>e083215</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&amp;pmid=39304210"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2023-083215</pub-id>
          <pub-id pub-id-type="medline">39304210</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2023-083215</pub-id>
          <pub-id pub-id-type="pmcid">PMC11418490</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Huber</surname>
              <given-names>GA</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schwartzberg</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The empirical study of legitimate authority: normative guidance for positive analysis</article-title>
          <source>Political Legitimacy: NOMOS LXI</source>
          <year>2019</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>New York University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>FD</given-names>
            </name>
          </person-group>
          <article-title>Perceived usefulness, perceived ease of use, and user acceptance of information technology</article-title>
          <source>MIS Q</source>
          <year>1989</year>
          <month>09</month>
          <volume>13</volume>
          <issue>3</issue>
          <fpage>319</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.2307/249008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Venkatesh</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>FD</given-names>
            </name>
          </person-group>
          <article-title>User acceptance of information technology: toward a unified view</article-title>
          <source>MIS Q</source>
          <year>2003</year>
          <volume>27</volume>
          <issue>3</issue>
          <fpage>425</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.2307/30036540</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dingel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kleine</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Cecil</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sigl</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Lermer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Gaube</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Predictors of health care practitioners' intention to use AI-enabled clinical decision support systems: meta-analysis based on the unified theory of acceptance and use of technology</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <month>08</month>
          <day>05</day>
          <volume>26</volume>
          <fpage>e57224</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e57224/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/57224</pub-id>
          <pub-id pub-id-type="medline">39102675</pub-id>
          <pub-id pub-id-type="pii">v26i1e57224</pub-id>
          <pub-id pub-id-type="pmcid">PMC11333871</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carroll</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Garba</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Figueroa-Rodríguez</surname>
              <given-names>OL</given-names>
            </name>
            <name name-style="western">
              <surname>Holbrook</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lovett</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Materechera</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Parsons</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Raseroka</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez-Lonebear</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rowe</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sara</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hudson</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The CARE principles for indigenous data governance</article-title>
          <source>Data Sci J</source>
          <year>2020</year>
          <volume>19</volume>
          <fpage>43</fpage>
          <pub-id pub-id-type="doi">10.5334/dsj-2020-043</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
