<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v28i1e92240</article-id>
      <article-id pub-id-type="pmid">42308509</article-id>
      <article-id pub-id-type="doi">10.2196/92240</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>Ethical Considerations in Personal Health Large Language Models</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Coristine</surname>
            <given-names>Andrew</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mauri</surname>
            <given-names>Lara</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lacroix</surname>
            <given-names>Paulette</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>El Ammari</surname>
            <given-names>Anis</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/>
            <institution>Department of Biomedical Informatics</institution>
            <institution>Vanderbilt University Medical Center</institution>
            <addr-line>2525 West End Ave #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>17</day>
        <month>6</month>
        <year>2026</year>
      </pub-date>
      <volume>28</volume>
      <elocation-id>e92240</elocation-id>
      <history>
        <date date-type="received">
          <day>27</day>
          <month>1</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>26</day>
          <month>2</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>27</day>
          <month>5</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>29</day>
          <month>5</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Jialin Liu, Siru Liu. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 17.06.2026.</copyright-statement>
      <copyright-year>2026</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2026/1/e92240" xlink:type="simple"/>
      <abstract>
        <p>Personal health large language models (PH-LLMs) have rapidly evolved from research prototypes into consumer-facing, data-linked systems that support symptom triage, medication questions, mental health check-ins, and longitudinal self-management. Their direct-to-consumer use without clinical oversight creates a distinct ethical risk profile that general artificial intelligence governance frameworks do not fully address. This viewpoint focuses on text-based, platform-mediated PH-LLMs and synthesizes PH-LLM–specific challenges across 6 domains: privacy, accuracy, equity, transparency, human-artificial intelligence interaction, and regulatory governance. These risks may be amplified by health literacy gaps, longitudinal data aggregation, persuasive conversational design, and fragmented oversight across the consumer-clinical boundary. Grounded in the 4 principles of biomedical ethics, we propose a governance framework that operationalizes beneficence, nonmaleficence, autonomy, and justice through design and deployment controls, including health literacy-aligned communication, crisis and pharmacological safeguards, hallucination mitigation, role disclosure, granular consent, fairness auditing, and accessible design. We further outline implementation mechanisms, including risk-tiered certification, tiered accountability, and postdeployment oversight through adverse-event reporting, transparency reporting, and independent safety evaluation. This framework is intended as an evidence-informed but partly anticipatory approach to governing PH-LLMs in personal health management.</p>
      </abstract>
      <kwd-group>
        <kwd>digital health</kwd>
        <kwd>ethics</kwd>
        <kwd>privacy</kwd>
        <kwd>generative artificial intelligence</kwd>
        <kwd>governance</kwd>
        <kwd>health AI</kwd>
        <kwd>health equity</kwd>
        <kwd>health literacy</kwd>
        <kwd>patient safety</kwd>
        <kwd>personal health large language model</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Personal health large language models (PH-LLMs) are consumer-facing generative systems designed to support individuals through natural language dialogue across health-related contexts such as symptom triage, chronic disease self-management, medication questions, and mental health check-ins [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. This viewpoint focuses on text-based, dialogue-driven PH-LLMs deployed directly to consumers. We distinguish these systems from general-purpose chatbots by their sustained health-oriented interaction, use of personal health disclosures, and potential to shape real-world health decisions. Some PH-LLM functions may fall within medical device software regulation when intended for diagnostic, therapeutic, or patient-specific clinical decision support, although thresholds vary across jurisdictions. PH-LLMs may offer scalable adjunctive support between clinical encounters, particularly where health or mental health services are limited or delayed [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. However, because they operate on sensitive personal information and may influence high-stakes decisions, their deployment raises questions that warrant systematic examination [<xref ref-type="bibr" rid="ref6">6</xref>].</p>
      <p>Between late 2025 and early 2026, PH-LLMs moved rapidly from prototypes to consumer-facing, data-linked products. Major technology companies introduced health-oriented conversational systems linked to medical records, wearable data, or health-system workflows, positioning large language models (LLMs) as increasingly common entry points for personal health support [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. For instance, OpenAI reports that over 230 million people ask health and wellness questions on ChatGPT each week [<xref ref-type="bibr" rid="ref7">7</xref>]. Moreover, open-source and open-weight deployments outside centralized platform controls raise additional governance challenges.</p>
      <p>The World Health Organization has emphasized that generative artificial intelligence (AI) in health care can deliver value only if risks are proactively identified, evaluated, and mitigated [<xref ref-type="bibr" rid="ref6">6</xref>]. Emerging evidence suggests that inadequately governed PH-LLMs may generate unsafe or misleading recommendations, compromise privacy through mishandling of sensitive data, amplify health inequities through biased outputs, and cause psychological harm through false reassurance, relational overreach, or poor management of emotional distress, particularly among vulnerable users [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. PH-LLM ethics, therefore, should move beyond general principles toward an actionable governance architecture for responsible, accountable, and equitable deployment.</p>
    </sec>
    <sec>
      <title>Core Ethical Challenges of PH-LLMs</title>
      <sec>
        <title>Overview</title>
        <p>PH-LLMs generate tailored guidance from personal health disclosures through longitudinal, dialogue-based interaction. Unlike institutionally governed clinical AI, direct-to-consumer PH-LLMs often lack professional mediation, allowing hallucinations, bias, and framing effects to shape health decisions without meaningful oversight. Drawing on the 4 principles of biomedical ethics, we identify 6 interconnected domains (<xref rid="figure1" ref-type="fig">Figure 1</xref>), which vary in severity, interact with one another, and may produce harms that accumulate across decisions. <xref ref-type="table" rid="table1">Table 1</xref> contrasts general AI ethics concerns with PH-LLM–specific manifestations.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Six ethical dimensions of personal health large language model (PH-LLM) deployment and their bidirectional relationships. AI: artificial intelligence.</p>
          </caption>
          <graphic xlink:href="jmir_v28i1e92240_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Core ethical challenges: general artificial intelligence (AI) concerns vs personal health large language model (PH-LLM)–specific manifestations.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="240"/>
            <col width="240"/>
            <col width="520"/>
            <thead>
              <tr valign="top">
                <td>Challenge domain</td>
                <td>General AI concern</td>
                <td>PH-LLM–specific manifestation</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Privacy and data security</td>
                <td>Data collection and retention</td>
                <td>Intangible vulnerability; longitudinal aggregation; health data broker exposure outside clinical protections</td>
              </tr>
              <tr valign="top">
                <td>Accuracy and reliability</td>
                <td>Hallucinations</td>
                <td>Verification gap; cascading clinical harm; crisis mismanagement</td>
              </tr>
              <tr valign="top">
                <td>Fairness and health equity</td>
                <td>Algorithmic bias</td>
                <td>Differential recommendations across groups; digital inverse care law; tiered-access barriers</td>
              </tr>
              <tr valign="top">
                <td>Transparency and accountability</td>
                <td>Black box decisions</td>
                <td>Explainability gap; accountability gap; relational expectations without duty</td>
              </tr>
              <tr valign="top">
                <td>Human-AI interaction</td>
                <td>Overreliance</td>
                <td>Parasocial attachment; distorted care-seeking; continuity-of-care displacement</td>
              </tr>
              <tr valign="top">
                <td>Regulatory and legal governance</td>
                <td>Regulatory lag</td>
                <td>Coverage gaps across jurisdictions; medical device classification ambiguity; cross-border accountability diffusion</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Privacy and Data Security</title>
        <p>Privacy is among the most salient ethical concerns in PH-LLM deployment [<xref ref-type="bibr" rid="ref1">1</xref>]. Compared with general-purpose AI, these risks are amplified by the convergence of highly sensitive disclosures, blurred regulatory boundaries, and system-level data integration [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Users may disclose highly sensitive information, including mental health concerns and genetic predispositions, yet undervalue the privacy significance of such disclosures relative to tangible assets [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. This intangible vulnerability may be intensified by the empathetic, low-barrier design of PH-LLM interactions, which encourages candid disclosure while obscuring downstream data uses [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. Outside regulated clinical settings, conversational data may be combined with behavioral, device, or consumer data and repurposed for advertising, analytics, profiling, or data-broker activities, creating ethical concerns that users may not fully anticipate. Users may also interpret conversational empathy as evidence of professional accountability or legal confidentiality. In the United States, however, the Health Insurance Portability and Accountability Act generally applies only to covered entities and their business associates, so many direct-to-consumer PH-LLM interactions fall outside its scope [<xref ref-type="bibr" rid="ref16">16</xref>]. Sensitive information may therefore be disclosed under assumptions of protection that do not apply in practice. In addition, conversation data may be retained for model improvement or other secondary uses [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>], and integration with ecosystem data streams can enable high-fidelity longitudinal profiling that raises reidentification risk and reduces the effectiveness of conventional deidentification approaches [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      </sec>
      <sec>
        <title>Accuracy and Reliability</title>
        <p>The central value proposition of PH-LLMs, namely, reliable health guidance, is challenged by hallucinations, clinically significant omissions, and users’ limited capacity to independently verify outputs. Medical hallucinations may appear clinically plausible and can compound across multiturn exchanges into downstream health decisions [<xref ref-type="bibr" rid="ref21">21</xref>]. A 2025 evaluation of LLM-generated clinical summaries identified hallucinations in 1.47% of outputs and clinically significant omissions in 3.45% [<xref ref-type="bibr" rid="ref21">21</xref>], although these estimates derive from structured summarization tasks and may not generalize to open-ended PH-LLM dialogue. Adversarial prompting and training-time vulnerabilities, such as data poisoning, pose further risks to model integrity over time [<xref ref-type="bibr" rid="ref22">22</xref>]. Unlike general information domains, where errors are often verifiable by informed users, PH-LLM outputs frequently cannot be independently scrutinized by individuals lacking clinical expertise [<xref ref-type="bibr" rid="ref23">23</xref>]. This verification gap is especially hazardous for the approximately 80 million Americans with limited health literacy [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>].</p>
        <p>Risks are particularly acute in psychological and medication contexts. “Deceptive empathy” describes therapeutic-sounding language that builds perceived alliance while obscuring the system’s lack of professional accountability [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Empirical evaluations show that some therapy-oriented conversational systems may provide information about lethal means without recognizing suicidal intent [<xref ref-type="bibr" rid="ref28">28</xref>]. Recent litigation involving chatbot interactions and adolescent self-harm has further raised questions about whether direct-to-consumer PH-LLMs can satisfy a duty of care [<xref ref-type="bibr" rid="ref29">29</xref>]. Repeated PH-LLM interactions may also exacerbate automation bias, defined as uncritical deference to algorithmic outputs over independent verification, because conversational fluency facilitates cognitive offloading and may lead users to mistake probabilistic suggestions for medical certainties [<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. Case reports document outputs encouraging users to abruptly taper psychiatric medications or discount professional counsel [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>], which may increase the risk of withdrawal or relapse [<xref ref-type="bibr" rid="ref36">36</xref>] and undermine trust in professional advice.</p>
      </sec>
      <sec>
        <title>Fairness and Health Equity</title>
        <p>PH-LLMs may reproduce and amplify structural disparities through both model behavior and access pathways, thereby undermining health equity, defined as a fair opportunity to attain one’s highest level of health [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. A 2025 systematic review of 24 studies found demographic bias in 22 (91.7%), including gender bias in 15/16 (93.8%) studies and racial or ethnic bias in 10/11 (90.9%) studies assessing these dimensions [<xref ref-type="bibr" rid="ref38">38</xref>]. Bias may vary by model architecture: discriminative models primarily show disparities in classification performance, whereas generative models may encode bias through tone, framing, and recommendation priority [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. For example, Yang et al [<xref ref-type="bibr" rid="ref41">41</xref>] reported cases in which GPT-3.5-turbo recommended surgery for White patients but conservative management for Black patients with otherwise identical clinical presentations. Equity concerns also extend beyond outputs to access pathways. Accessibility is stratified by digital determinants of health [<xref ref-type="bibr" rid="ref42">42</xref>], and tiered subscriptions may restrict advanced personalization and reasoning to paid access, favoring users with greater financial means and health literacy [<xref ref-type="bibr" rid="ref43">43</xref>]. This creates a digital inverse care law [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]: those with the greatest health needs may be confined to lower-capability services, while more advantaged groups gain priority access to advanced tools. Without equity-centered governance, PH-LLMs may deepen structural health disparities rather than alleviate them.</p>
      </sec>
      <sec>
        <title>Transparency and Accountability</title>
        <p>In conventional health care, clinical judgment is embedded in auditable institutional processes and clear lines of professional responsibility. PH-LLMs disrupt both: model reasoning is often opaque, and accountability is distributed across developers, deployers, and health care institutions. In high-stakes health contexts, users reasonably expect understandable explanations and supporting evidence for PH-LLM–generated recommendations [<xref ref-type="bibr" rid="ref11">11</xref>]. Yet interpretability, explainability, transparency, and auditability are not equivalent. For LLMs, direct interpretability of internal mechanisms remains limited [<xref ref-type="bibr" rid="ref46">46</xref>], and post hoc explanations may appear plausible without faithfully reflecting how outputs were generated [<xref ref-type="bibr" rid="ref47">47</xref>]. Without sufficient transparency and auditability, users and oversight bodies cannot reliably assess the evidentiary basis or clinical validity of recommendations. When PH-LLM advice contributes to harm, attributing responsibility among these actors becomes practically difficult [<xref ref-type="bibr" rid="ref48">48</xref>]. Direct-to-consumer deployment may also bypass institutional oversight and shift risk onto users despite well-documented health literacy gaps [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref49">49</xref>], weakening incentives for safety investment and limiting recourse [<xref ref-type="bibr" rid="ref50">50</xref>]. These concerns are intensified by relational design features: anthropomorphic or affective language may create expectations of care and accountability, even though no human or institutional actor is clearly positioned to fulfill them [<xref ref-type="bibr" rid="ref51">51</xref>-<xref ref-type="bibr" rid="ref53">53</xref>]. Together, these conditions may weaken meaningful informed consent and compromise patient autonomy.</p>
      </sec>
      <sec>
        <title>Human-AI Interaction</title>
        <p>PH-LLMs may foster emotional dependence and overreliance through anthropomorphic and affective language that creates a perceived sense of care without corresponding therapeutic responsibility [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref54">54</xref>]. Their empathic and nonjudgmental dialogue may encourage parasocial attachment and emotional reliance, particularly among adolescents and socially isolated users [<xref ref-type="bibr" rid="ref53">53</xref>-<xref ref-type="bibr" rid="ref55">55</xref>]. Greater perceived social presence is associated with increased self-disclosure and emotional reliance [<xref ref-type="bibr" rid="ref56">56</xref>-<xref ref-type="bibr" rid="ref59">59</xref>], raising concerns about sustained dependence and displacement of continuity-based care [<xref ref-type="bibr" rid="ref60">60</xref>-<xref ref-type="bibr" rid="ref63">63</xref>]. PH-LLM interactions may also distort care-seeking: reassuring responses may delay appropriate evaluation [<xref ref-type="bibr" rid="ref64">64</xref>-<xref ref-type="bibr" rid="ref66">66</xref>], while alarming responses may trigger unnecessary escalation [<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref68">68</xref>].</p>
      </sec>
      <sec>
        <title>Regulatory and Legal Governance</title>
        <p>A cross-cutting challenge is the mismatch between rapid PH-LLM deployment and slower regulatory evolution. In the United States, many direct-to-consumer health technologies are governed through Federal Trade Commission enforcement and a patchwork of state health data laws, particularly when services fall outside traditional clinical privacy regimes [<xref ref-type="bibr" rid="ref69">69</xref>-<xref ref-type="bibr" rid="ref73">73</xref>]. In the European Union, privacy and AI oversight are structured through the General Data Protection Regulation and the phased, risk-based AI Act [<xref ref-type="bibr" rid="ref74">74</xref>]. In Asia, governance approaches diverge, with China emphasizing provider accountability, security review, and content governance for generative AI services, while South Korea, Japan, and Singapore continue to develop different combinations of statutory oversight, sector-specific guidance, and risk-based governance [<xref ref-type="bibr" rid="ref75">75</xref>-<xref ref-type="bibr" rid="ref78">78</xref>]. Similar PH-LLM interactions may therefore receive different protections across jurisdictions, creating opportunities for regulatory arbitrage.</p>
        <p>PH-LLMs also expose a classification gap between general wellness products and regulated software as a medical device. When systems are marketed as nonclinical but functionally approximate symptom triage, diagnostic reasoning, treatment guidance, medication advice, or crisis response, developers may avoid premarket scrutiny [<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref80">80</xref>]. A capability-based governance approach would reduce this form of regulatory arbitrage by assigning oversight according to what the system enables users to do rather than how it is described in marketing materials. Because cross-border services can diffuse accountability across developers, deployers, platforms, and jurisdictions, PH-LLM governance requires risk-calibrated mechanisms that link ethical concerns to concrete oversight, certification, adverse-event reporting, and redress pathways [<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref82">82</xref>].</p>
      </sec>
    </sec>
    <sec>
      <title>Ethical Governance Framework for PH-LLMs</title>
      <sec>
        <title>Overview</title>
        <p>To address these challenges, we propose a principlism-based governance framework for consumer-facing PH-LLMs [<xref ref-type="bibr" rid="ref83">83</xref>]. The framework translates the 4 principles of biomedical ethics into life cycle controls across 5 stakeholder groups: developers, deployers or platforms, health care institutions, regulators, and users. Governance intensity should scale with 4 risk dimensions: clinical severity and time criticality, harm reversibility, user actionability, and deployment scale. Higher-risk systems, therefore, warrant stronger certification, auditability, postmarket surveillance, and clearer liability allocation. Because PH-LLM outputs are probabilistic and vulnerable to prompt injection and adversarial manipulation [<xref ref-type="bibr" rid="ref22">22</xref>], these safeguards should be understood as risk-reduction measures rather than guarantees. <xref ref-type="table" rid="table2">Table 2</xref> maps each challenge domain to its corresponding governance mechanism and implementation level. To avoid overstating the evidence, we distinguish 3 classes of proposals throughout the framework: evidence-informed proposals grounded in empirical findings from PH-LLM or closely analogous digital health evaluations; normative proposals articulating ethical commitments without relying primarily on empirical demonstration; and conceptual proposals describing architectural or procedural designs whose real-world effects have not yet been prospectively validated. Where relevant, these distinctions are integrated into the prose.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Governance framework overview: challenge domains, recommended mechanisms, and implementation levels.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="300"/>
            <col width="410"/>
            <col width="290"/>
            <thead>
              <tr valign="top">
                <td>Challenge domain</td>
                <td>Recommended governance mechanism</td>
                <td>Implementation level</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Sensitive data and privacy</td>
                <td>Tiered consent and data governance</td>
                <td>Input and session level</td>
              </tr>
              <tr valign="top">
                <td>Unsafe or misleading outputs</td>
                <td>Risk-tiered certification and guardrails</td>
                <td>System level</td>
              </tr>
              <tr valign="top">
                <td>Bias and inequity</td>
                <td>Subgroup validation and disparity monitoring</td>
                <td>System and population level</td>
              </tr>
              <tr valign="top">
                <td>Poor explainability and transparency</td>
                <td>Provenance disclosure and auditability requirements</td>
                <td>Interface and oversight level</td>
              </tr>
              <tr valign="top">
                <td>Crisis and mental health risk</td>
                <td>Escalation and handoff protocols</td>
                <td>Interaction level</td>
              </tr>
              <tr valign="top">
                <td>Fragmented responsibility</td>
                <td>Tiered accountability and liability allocation</td>
                <td>Institutional and regulatory level</td>
              </tr>
              <tr valign="top">
                <td>Drift after deployment</td>
                <td>Adverse-event reporting and periodic audits</td>
                <td>Life cycle level</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Guiding Principles</title>
        <p>Because PH-LLMs interact directly with users outside traditional settings, the 4 principles of biomedical ethics [<xref ref-type="bibr" rid="ref83">83</xref>] require specific operationalization.</p>
      </sec>
      <sec>
        <title>Beneficence (Outcome-Oriented Support)</title>
        <p>For PH-LLMs, beneficence can be operationalized as measurable support for safe decision-making and timely access to care, including health-literacy adaptation, risk-stratified care navigation, and longitudinal coherence across sessions.</p>
      </sec>
      <sec>
        <title>Nonmaleficence (Proactive Harm Prevention)</title>
        <p>Evidence from PH-LLM failures and adjacent digital health contexts supports active safety mechanisms beyond passive disclaimers, particularly for high-risk failures such as crisis mismanagement, contraindicated advice, and hallucinated medical claims. This principle is operationalized through 3 design imperatives: crisis-detection and response protocols, contraindication safeguards, and hallucination mitigation [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref85">85</xref>].</p>
      </sec>
      <sec>
        <title>Respect for Autonomy (Informed Agency)</title>
        <p>From a normative perspective, respect for autonomy requires countering safety illusions in which users misinterpret AI-mediated intimacy as clinical oversight or regulatory protection, while preserving meaningful choice. This principle is operationalized through clear role and scope disclosure, meaningful data-use consent, and practical user rights over interaction data [<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref87">87</xref>].</p>
      </sec>
      <sec>
        <title>Justice (Equity and Access)</title>
        <p>PH-LLMs should expand access without reproducing disparities in health information, communication quality, or safety outcomes. Equity, therefore, extends beyond model outputs to accessibility, language coverage, cultural appropriateness, and usability across differences in health literacy, disability, and digital access [<xref ref-type="bibr" rid="ref88">88</xref>-<xref ref-type="bibr" rid="ref90">90</xref>]. Fairness monitoring requires interaction-level and outcome-relevant measures, such as group-stratified rates of unsafe guidance and crisis escalation success [<xref ref-type="bibr" rid="ref91">91</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]. Predefined disparity triggers initiate audit and remediation (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
      </sec>
      <sec>
        <title>Stakeholder Responsibilities</title>
        <p>Operationalizing this framework requires coordinated action across 5 stakeholder groups.</p>
      </sec>
      <sec>
        <title>Developers (Ethical Design and Life Cycle Accountability)</title>
        <p>Developers bear primary responsibility for baseline protections across the life cycle: diverse training corpora, documented data provenance, and bias and crisis-focused safety evaluation before release [<xref ref-type="bibr" rid="ref90">90</xref>]; clear disclosure of nonhuman identity and nonclinical role, crisis-response functions, pharmacological safety guardrails, and granular data-use controls at deployment; and accessible grievance channels and adverse-event reporting after deployment (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p>
      </sec>
      <sec>
        <title>Deployers and Platforms (Interface and Operational Controls)</title>
        <p>Deployers and platforms adapt developer-level safeguards into interface design and escalation pathways required by their deployment context, and ensure sustained compliance with safety, transparency, and user-protection requirements.</p>
      </sec>
      <sec>
        <title>Health Care Institutions (Algorithmic Stewardship)</title>
        <p>Institutions that integrate or endorse PH-LLMs assume stewardship obligations proportional to their involvement, including contextual validation, escalation and handoff workflows, clinician training, and postdeployment monitoring [<xref ref-type="bibr" rid="ref93">93</xref>,<xref ref-type="bibr" rid="ref94">94</xref>].</p>
      </sec>
      <sec>
        <title>Regulators (Oversight and Harmonization)</title>
        <p>Regulators should address the governance gap through enforceable disclosure requirements, minimum crisis-response standards, adverse-event reporting infrastructure, risk-stratified premarket evaluation for sensitive domains, and cross-jurisdictional harmonization informed by the EU AI Act and the National Institute of Standards and Technology AI Risk Management Framework [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]. Engagement with insurers and payers can link reimbursement to minimum safety requirements.</p>
      </sec>
      <sec>
        <title>Users and Civil Society (Literacy and Advocacy)</title>
        <p>Users and civil society contribute through health-AI literacy, accessible harm-reporting channels, and advocacy for meaningful data rights, including access, correction, and deletion [<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref96">96</xref>].</p>
      </sec>
      <sec>
        <title>Implementation Mechanisms</title>
        <sec>
          <title>Overview</title>
          <p>In practice, our framework centers on 3 instruments: risk-tiered certification, tiered accountability, and postdeployment monitoring. The main text presents the rationale, whereas operational specifications, including certification-tier expectations, developer life cycle responsibilities, fairness-audit triggers, scope boundaries, stakeholder responsibilities, and adverse-event thresholds, are detailed in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendices 1</xref>-8.</p>
        </sec>
        <sec>
          <title>Risk-Tiered Certification</title>
          <p>Certification could be scaled according to functional risk and deployment reach, with baseline requirements spanning crisis handling, health-literacy alignment, nondiagnostic guardrails, equity auditing, disclosure integrity, and data governance [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref96">96</xref>-<xref ref-type="bibr" rid="ref99">99</xref>]. To reduce reliance on developer self-labeling, we propose that certification be triggered by demonstrated capabilities rather than marketing claims. Systems that provide or materially support symptom triage, diagnostic reasoning, treatment guidance, medication advice, crisis-response, or other health decision-support activities would be assigned to the corresponding risk tier even when marketed as wellness tools. Certification criteria could be developed through multistakeholder processes, with audits conducted by accredited third-party or regulator-authorized bodies [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref99">99</xref>-<xref ref-type="bibr" rid="ref103">103</xref>]. Because regulatory approaches differ across jurisdictions, certification frameworks could prioritize interoperable baseline standards while allowing local legal adaptation [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref82">82</xref>]. Possible enforcement pathways include capability-based classification, postmarket surveillance for functional drift, and market-access conditionality through app stores, platform hosts, insurers, payers, and institutional procurement channels. These remain conceptual proposals requiring further institutional validation. Detailed standards and institutional anchors are summarized in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p>
        </sec>
        <sec>
          <title>Tiered Accountability</title>
          <p>Tiered accountability would follow operational control and implementation capacity. Foundation-model developers would be responsible for baseline safety properties and documentation, whereas deployers and platforms would be responsible for context-specific safeguards, interface design, and user protection. In direct-to-consumer settings, we propose a default elevated duty of care as a normative position. Any safe harbor would be conditional, limited, and available only to operators demonstrating independently verified compliance with certification, auditability, postdeployment surveillance, and user-protection requirements. Such protection would mitigate, but not eliminate, liability and would be coupled with compensation pathways, such as insurance-based or no-fault mechanisms [<xref ref-type="bibr" rid="ref95">95</xref>,<xref ref-type="bibr" rid="ref104">104</xref>,<xref ref-type="bibr" rid="ref105">105</xref>]. Developers or deployers who decline certification are not exempt from this duty of care; rather, they remain subject to ordinary liability, consumer-protection enforcement, and regulatory scrutiny.</p>
        </sec>
        <sec>
          <title>Postdeployment Monitoring</title>
          <p>This layer complements predeployment testing by establishing standardized adverse-event reporting, targeted surveillance for population-level harms, and periodic audits for model drift, safety regressions, and equity-related performance changes [<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref106">106</xref>-<xref ref-type="bibr" rid="ref109">109</xref>]. These mechanisms draw on established approaches in medical-device safety, health-AI evaluation, and postmarket surveillance, but require adaptation to the probabilistic, continuously updated, and dialogue-dependent behavior of PH-LLMs. For higher-reach deployments, monitoring may be supplemented by independent safety oversight designed to preserve independence from the entities being reviewed.</p>
        </sec>
      </sec>
      <sec>
        <title>Illustrative Case: Youth Mental Health Check-In PH-LLM</title>
        <p>To show how the framework could be applied, we present an illustrative end-to-end case of YouthPH-LLM, a platform-mediated direct-to-consumer PH-LLM providing conversational mood tracking, coping-skills education, and sleep and activity coaching to users aged 13-25 years, with more than 1 million monthly active users. Under the 4 risk dimensions, YouthPH-LLM is classified as high risk across clinical severity, harm reversibility, user actionability, and deployment scale, placing it in the most demanding certification tier. Predeployment requirements include crisis-scenario testing, counterfactual fairness testing across age, gender, and linguistic subgroups, retrieval-augmented generation grounded in authoritative mental health guidelines, and a public model card. Postdeployment, a critical adverse event would trigger immediate crisis-response protocol, feature-level suspension of the implicated functionality within 24 hours where technically feasible, regulatory notification within 72 hours where required, and root-cause analysis by an independent safety advisory board. Suspension should preserve access to crisis resources or human support where available. Multi-intent prompts, such as a sleep log submitted with a request to interpret a clinical questionnaire score, are handled through partitioned response: the system may provide sleep-coaching guidance while redirecting questionnaire interpretation to qualified clinicians. Full specification of stakeholder responsibilities, certification criteria, and escalation thresholds is provided in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>.</p>
      </sec>
    </sec>
    <sec>
      <title>Practical Paths to Mitigate Ethical Risks of PH-LLMs</title>
      <sec>
        <title>Overview</title>
        <p>Building on the framework above, we outline practical implementation pathways with measurable targets across 5 operational domains: data governance, model design safeguards, equity and inclusive design, human-AI collaboration, and postdeployment oversight.</p>
      </sec>
      <sec>
        <title>Data Governance</title>
        <sec>
          <title>Overview</title>
          <p>The ethical analysis identified 2 privacy-related concerns: users may underestimate the sensitivity of emotional disclosures, and longitudinal aggregation may increase reidentification risk. To address these concerns, PH-LLMs should implement data-governance safeguards adapted to conversational health data.</p>
        </sec>
        <sec>
          <title>Tiered Consent Architecture With Retention Safeguards</title>
          <p>Rather than binary consent, PH-LLMs should apply 4 sensitivity tiers supported by a classify-then-govern workflow (<xref ref-type="table" rid="table3">Table 3</xref>) [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref81">81</xref>]. In this proposed design for platform-mediated direct-to-consumer PH-LLMs, retention defaults would vary by sensitivity tier: Tier 1 content would follow limited default retention periods with user-adjustable settings; Tier 2 content would use shorter default retention with immediate-deletion options; Tier 3 content would be temporarily retained only as needed for required safety audit, legally authorized safety review, or legal compliance and then deleted; and Tier 4 content would require explicit user authorization and periodic reconsent, with automatic deletion as the default absent active renewal. Deviations from tier-specific retention defaults require documented risk-benefit analysis that considers clinical use, reidentification risk, user-preference evidence, technical necessity, and applicable legal requirements, with rationale disclosed in transparency reports. Restrictions on third-party sharing, including transfers to data brokers, advertising networks, and profiling services, follow the same sensitivity hierarchy and cannot be overridden by blanket onboarding consent [<xref ref-type="bibr" rid="ref99">99</xref>,<xref ref-type="bibr" rid="ref110">110</xref>]. Illustrative retention windows and operational details are provided in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref> and should be recalibrated according to deployment context, user preferences, ethical risk assessment, technical feasibility, and jurisdictional requirements.</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Tiered consent architecture for PH-LLM data governancea.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="180"/>
              <col width="250"/>
              <col width="270"/>
              <col width="300"/>
              <thead>
                <tr valign="top">
                  <td>Data category</td>
                  <td>Consent requirement</td>
                  <td>Default retention</td>
                  <td>Third-party sharing</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Tier 1: general health queries</td>
                  <td>Baseline onboarding consent and standard terms of service</td>
                  <td>Limited default retention, user-adjustable</td>
                  <td>Deidentified or aggregated research only, where permitted, with opt-out; no default transfer to data brokers, advertising networks, or profiling services</td>
                </tr>
                <tr valign="top">
                  <td>Tier 2: noncrisis mental health disclosures</td>
                  <td>Low-friction enhanced consent for retention or secondary use; nonpersistent mode if declined or abandoned</td>
                  <td>No routine retention if consent is declined; brief, access-restricted safety buffer with automatic deletion unless a potential adverse event is reported</td>
                  <td>No commercial or unrelated secondary use; safety audits via privacy-preserving mechanisms where feasible</td>
                </tr>
                <tr valign="top">
                  <td>Tier 3: crisis-related content</td>
                  <td>No intervening consent prompt before safety support; immediate safety-oriented response and crisis-resource escalation</td>
                  <td>Temporary retention only as needed for safety audit, legally authorized review, or legal compliance; deleted thereafter</td>
                  <td>Limited to legally authorized or required emergency interventions</td>
                </tr>
                <tr valign="top">
                  <td>Tier 4: longitudinal narratives</td>
                  <td>Explicit authorization, periodic reconsent, and granular controls</td>
                  <td>Automatic deletion as the default absent active renewal</td>
                  <td>Default opt-out; explicit per-purpose authorization required</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>Specific retention parameters are provided in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>. These illustrative baselines reflect privacy risk management principles rather than universal requirements and warrant recalibration through documented risk-benefit analysis disclosed in transparency reports.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>User-requested deletion should be defined with technical precision. It applies to stored raw conversational logs, retained session records, stored user profiles used for retrieval, vector-store entries, and derived longitudinal summaries under the operator’s control. It should not be represented as a guarantee that information already incorporated into a foundation model’s trained weights can be fully and verifiably removed, because machine unlearning for large generative models remains an open technical problem with unresolved limitations in effectiveness and verification [<xref ref-type="bibr" rid="ref111">111</xref>]. Sensitive PH-LLM interactions should therefore be excluded from foundation-model training or fine-tuning by default unless explicit user authorization is obtained, and consent materials should transparently disclose the technical limits of deletion.</p>
        </sec>
        <sec>
          <title>Implementation of Classify-Then-Govern</title>
          <p>Because free-text sensitivity cannot be determined without initial processing, this architecture cannot operate as a simple “consent-then-ingest” model [<xref ref-type="bibr" rid="ref99">99</xref>]. Inputs first undergo transient routing and safety classification under baseline onboarding consent, limited to classification only and without default retention or secondary use [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref99">99</xref>]. Tier 1 content remains within baseline consent. Tier 2 content requires in-context consent before retention; if consent is declined or abandoned, the interaction continues in nonpersistent mode, with flagged content excluded from routine retention and secondary use by default. To balance privacy protection with safety auditing, nonpersistent mode may still permit a narrowly scoped, encrypted, access-restricted safety buffer that is automatically purged after a brief, predefined window unless a potential adverse event is reported, in which case only the minimum necessary information is retained for root-cause analysis and safety remediation. Tier 3 content triggers an immediate safety-oriented response, delivery of context-appropriate crisis resources, and handoff to human crisis support where available, without intervening consent prompts [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref112">112</xref>]. For Tier 4 longitudinal content, explicit retention authorization is triggered by predefined accumulation thresholds rather than being embedded repeatedly in active dialogue. This approach is most feasible in explicitly health-oriented PH-LLM deployments, where the health-related purpose of interaction is already established. Extending it to general-purpose LLMs would require separate governance analysis because detecting health-related content across heterogeneous conversations could require continuous or broad input scanning, thereby introducing secondary privacy and proportionality risks.</p>
        </sec>
        <sec>
          <title>Accessible, Nondisruptive Consent Design</title>
          <p>Enhanced consent should not shift cognitive burden onto vulnerable users. Because many users face limited health literacy, emotional distress, disability, or low digital fluency, accessibility should be treated as a core safety and equity requirement rather than a downstream usability concern. Consent escalation relies on brief, plain-language, just-in-time disclosures; a small set of standardized choices; and protective default pathways favoring nonpersistent session handling when users do not actively authorize retention or secondary use. For noncrisis mental health disclosures (Tier 2), enhanced consent should be low-friction and deferrable, allowing the conversation to continue in nonpersistent mode while authorization is requested separately. Crisis-related interactions are not delayed by consent procedures and default instead to immediate safety-oriented support and escalation pathways. Granular controls may remain available through a dashboard, but safe baseline use does not depend on navigating it. Interface designs require prospective testing with users who have limited health literacy, disability, low digital fluency, or heightened emotional vulnerability, and evaluation extending to comprehension, decision confidence, perceived burden, and abandonment rather than consent-completion rates alone [<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref113">113</xref>].</p>
        </sec>
        <sec>
          <title>Longitudinal Data and Reidentification Safeguards</title>
          <p>PH-LLMs integrated with wearables and health records may generate highly identifying longitudinal profiles from temporally dense, behaviorally specific data [<xref ref-type="bibr" rid="ref20">20</xref>]. Developers should implement privacy-preserving analytics (eg, differential privacy calibrated to sensitivity and use, with k-anonymity where appropriate) [<xref ref-type="bibr" rid="ref114">114</xref>,<xref ref-type="bibr" rid="ref115">115</xref>], conduct reidentification risk assessments at intervals proportional to data accumulation, and test vulnerability to inference attacks [<xref ref-type="bibr" rid="ref115">115</xref>]. User-facing aggregation dashboards enable users to inspect derived longitudinal patterns and selectively delete specific data categories.</p>
        </sec>
      </sec>
      <sec>
        <title>Model Design Safeguards: Hallucination Mitigation, Crisis Escalation, and Pharmacological Safety</title>
        <p>Three clinically significant safety risks warrant dedicated design-level controls: hallucinations, crisis-management failures, and unsafe pharmacological guidance.</p>
      </sec>
      <sec>
        <title>Hallucination Mitigation</title>
        <p>PH-LLMs should incorporate a sequential safety pipeline that combines input filtering, retrieval-augmented generation from curated authoritative sources, output checking against structured medical knowledge resources, and uncertainty signaling where technically feasible [<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref116">116</xref>-<xref ref-type="bibr" rid="ref118">118</xref>]. Prompts requesting individualized diagnosis or treatment recommendations trigger safety messaging and redirection to qualified professional care [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref97">97</xref>]. Because retrieved evidence may be outdated, incomplete, or misinterpreted by the model, these safeguards are best understood as risk-reduction mechanisms rather than guarantees of factual accuracy.</p>
      </sec>
      <sec>
        <title>Crisis Escalation</title>
        <p>Crisis management requires a distinct escalation protocol that includes detection of self-harm, suicide, or interpersonal violence signals; immediate, nonjudgmental acknowledgment; safety-oriented risk stratification; delivery of context-appropriate crisis resources; and handoff to human crisis support where available [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref119">119</xref>]. Because detection remains probabilistic, higher-risk deployments should favor conservative thresholds, clearly specified escalation criteria, and periodic review under qualified mental health oversight.</p>
      </sec>
      <sec>
        <title>Pharmacological Safety</title>
        <p>For medication-related queries, PH-LLMs should use a hybrid safety architecture combining external knowledge validation, rule-based guardrails, and escalation to human clinical support for complex or high-risk cases [<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref120">120</xref>-<xref ref-type="bibr" rid="ref123">123</xref>]. These controls block high-risk dosing instructions, contraindicated combinations, and unsupervised medication changes. Escalation triggers are prospectively specified in system logic rather than left to user discretion, because users may not recognize when a query exceeds safe self-management boundaries.</p>
      </sec>
      <sec>
        <title>Equity and Inclusive Design</title>
        <p>Fairness governance encompasses subgroup-based evaluation, representative testing, accessibility review, and periodic reassessment across updates and deployment settings [<xref ref-type="bibr" rid="ref91">91</xref>,<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref124">124</xref>-<xref ref-type="bibr" rid="ref130">130</xref>]. Before release, PH-LLMs undergo counterfactual fairness evaluation based on matched clinical vignettes [<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref124">124</xref>]: variation in race, ethnicity, gender, language, or socioeconomic indicators should not produce materially different recommendations in cases where these characteristics are not clinically relevant, and audits assess clinically salient error disparities such as false reassurance or inappropriate escalation while incorporating intersectional analysis [<xref ref-type="bibr" rid="ref126">126</xref>,<xref ref-type="bibr" rid="ref127">127</xref>]. Inclusive design extends beyond outcome auditing: PH-LLMs should support languages prevalent in target populations, incorporate cultural adaptation beyond direct translation, conform to Web Content Accessibility Guidelines 2.2 [<xref ref-type="bibr" rid="ref129">129</xref>], and provide health-literacy adaptation through adjustable response complexity and optional comprehension checks [<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref130">130</xref>].</p>
      </sec>
      <sec>
        <title>Human-AI Collaboration: Preventing Overreliance</title>
        <p>PH-LLMs require interface- and workflow-level safeguards that promote relational transparency, reduce automation bias, and preserve meaningful human oversight [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref131">131</xref>]. These controls include clear communication of the system’s nonhuman identity, calibrated disclosure of uncertainty and epistemic limits, and structured redirection when users request diagnosis, prognosis, prescribing, or other clinician-dependent judgments [<xref ref-type="bibr" rid="ref97">97</xref>,<xref ref-type="bibr" rid="ref132">132</xref>]. Systems should distinguish supportive self-management functions from clinician-dependent decisions and use adaptive boundary prompts rather than uniformly friction-based interruptions, so that higher-risk interactions trigger stronger warnings or referral cues without unnecessarily disrupting routine support [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref133">133</xref>].</p>
        <p>As a conceptual safeguard, PH-LLMs could use partitioned responses for multi-intent prompts that combine permitted and restricted functions. For example, when a user submits recent laboratory results together with a request for lifestyle coaching, the system may provide general lifestyle education while declining to interpret the laboratory findings or tailor clinical recommendations based on them, redirecting interpretation to a qualified clinician. However, partitioned responses are technically fragile if implemented only at the level of response wording. Because LLMs may condition on the broader prompt context, restricted contextual information, such as laboratory values, may implicitly influence the permitted portion of a response. Robust guardrail engineering is therefore needed to reduce context bleed and prevent implicit diagnostic integration [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Such safeguards may include intent classification, restricted-context masking or separation, output-level verification, and escalation rules when permitted coaching cannot be reliably separated from clinician-dependent interpretation. Safeguard effectiveness should be evaluated through postdeployment monitoring of both safety outcomes, such as appropriate escalation or referral, and engagement outcomes, such as abandonment following boundary prompts [<xref ref-type="bibr" rid="ref3">3</xref>]. Illustrative scope boundaries are provided in <xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref>.</p>
      </sec>
      <sec>
        <title>Postdeployment Oversight and Version Governance</title>
        <p>Predeployment evaluation is necessary but insufficient for PH-LLMs because system behavior, safety performance, and deployment context may change over time. Governance should therefore include structured postdeployment monitoring, low-friction adverse-event reporting, transparency mechanisms, and version-aware change control [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref134">134</xref>]. The system provides users, caregivers, and clinicians with standardized reporting pathways for clinically relevant events, including dangerous hallucinations, crisis mismanagement, and privacy breaches, adapted to AI-specific harms [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref89">89</xref>,<xref ref-type="bibr" rid="ref134">134</xref>,<xref ref-type="bibr" rid="ref135">135</xref>].</p>
        <p>As a conceptual response framework, critical adverse events trigger graduated action according to scope and severity, ranging from session-level termination of an affected thread to feature-level disabling of implicated functionality or, when risk is systemic, global suspension of the application. User lockout without alternative crisis resources must be avoided. Developers should publish periodic transparency reports covering adverse events by severity, crisis-protocol activation and outcomes, bias-audit findings and remediation, and model updates with associated safety evaluations [<xref ref-type="bibr" rid="ref93">93</xref>,<xref ref-type="bibr" rid="ref102">102</xref>].</p>
        <p>For higher-reach deployments, these mechanisms may be supplemented by independent safety oversight funded through structures designed to preserve independence from reviewed entities. As a normative governance proposal, potential models include pooled industry levies administered by neutral standards bodies, regulatory fees, public funding with statutory protections, or coalition-based subscription models with disclosed funding sources and recusal rules [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref82">82</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]. These oversight mechanisms differ in target audience and implementation pathway. Developers and deployers can directly implement technical guardrails, reporting channels, transparency reports, and internal safety audits. By contrast, pooled industry levies, regulatory fees, and publicly funded oversight structures are directed primarily to policymakers, regulators, and standards-setting bodies because they generally require statutory or regulatory authorization. Voluntary coalition-based models may be more immediately feasible, but still require conflict-of-interest safeguards, transparent funding disclosure, and recusal rules to preserve independence.</p>
        <p>Postdeployment governance should also be version-aware. Minor releases undergo documented internal validation, whereas major changes, including model updates, prompt-template revisions, plugin integration, interface redesign, or new data-linking functions, may warrant independent reassessment and, where appropriate, recertification [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref134">134</xref>]. Each release generates auditable change logs and predefined monitoring indicators to support rollback, incident investigation, and detection of behavioral drift after updates [<xref ref-type="bibr" rid="ref106">106</xref>,<xref ref-type="bibr" rid="ref108">108</xref>,<xref ref-type="bibr" rid="ref134">134</xref>]. Illustrative adverse-event severity categories and response pathways are provided in <xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref>.</p>
      </sec>
      <sec>
        <title>Scope and Feasibility</title>
        <p>This framework is grounded primarily in text-based, platform-mediated, direct-to-consumer PH-LLM deployment. Multimodal systems introduce additional governance challenges, including biometric-data protection, modality-specific failure modes, and cross-modal inference of sensitive attributes, and therefore require modality-specific validation and corresponding adjustments to consent, accountability, and monitoring structures [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref136">136</xref>]. Feasibility also varies across institutions, jurisdictions, and developer types because certification, audits, postdeployment surveillance, and incident reporting depend on unevenly distributed financial, technical, regulatory, and workforce capacity [<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref101">101</xref>].</p>
        <p>As the YouthPH-LLM case illustrates, youth-facing PH-LLMs expose an additional limitation of current digital privacy-law frameworks when applied to adolescent mental health support. Age-of-consent and parental authorization requirements, such as those under the General Data Protection Regulation [<xref ref-type="bibr" rid="ref87">87</xref>], may protect minors’ privacy and parental rights, but strict implementation can conflict with the ethical goal of providing confidential, low-friction access to adolescent mental health support. Routine parental disclosure or burdensome consent workflows may deter help-seeking, particularly among adolescents experiencing psychological distress, stigma, family conflict, or safety concerns [<xref ref-type="bibr" rid="ref137">137</xref>]. Future governance should therefore distinguish ordinary data-processing consent from immediate safety-oriented support, preserving rapid access to crisis resources while developing jurisdiction-specific mechanisms for age-appropriate privacy, parental involvement, and safeguarding obligations.</p>
        <p>The framework should balance underregulation, which may allow safety-critical failures to propagate at scale and shift risk onto vulnerable users, against overregulation, which may consolidate markets around large incumbents, reduce innovation for underrepresented groups, and divert resources from substantive safety work to compliance documentation. Because validated PH-LLM audit and certification cost data are not yet available, cost implications are described as qualitative categories: lower-cost safeguards include identity disclosure, scope labeling, basic adverse-event reporting, and crisis-resource signposting, whereas independent audits, red-team testing, certification preparation, continuous monitoring, and independent safety oversight are likely to impose moderate to high recurring costs. Large technology platforms may absorb these recurring costs, whereas startups, academic deployers, hospitals, and resource-constrained settings may face substantial barriers without proportionate pathways such as regulatory sandboxes, shared evaluation infrastructure, audit reciprocity, market-access incentives, and tiered certification with reduced fixed costs for smaller deployers [<xref ref-type="bibr" rid="ref138">138</xref>,<xref ref-type="bibr" rid="ref139">139</xref>].</p>
        <p>We distinguish near-term feasible actions, such as identity disclosure and scope labeling, Tier 3 crisis exclusion from training data, and standardized adverse-event reporting, from longer-term aspirational elements, such as harmonized certification reciprocity, sustainably funded independent safety advisory boards, and population-level longitudinal outcomes monitoring. Qualitative cost categories, institutional capacity profiles, and implementation trade-offs are detailed in <xref ref-type="supplementary-material" rid="app8">Multimedia Appendix 8</xref>.</p>
      </sec>
    </sec>
    <sec>
      <title>Current Evidence Base and Limitations</title>
      <p>The evidence base for ethical and governance concerns in PH-LLMs remains heterogeneous. Established empirical findings include hallucinations and clinically significant omissions in health-related LLM tasks, persistent demographic bias, privacy and confidentiality concerns in direct-to-consumer digital health settings, and failures of some conversational systems to manage crisis-related interactions safely [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref38">38</xref>]. Automation bias in PH-LLM contexts is supported mainly by adjacent-domain evidence from clinical decision-support systems, with limited direct PH-LLM evidence [<xref ref-type="bibr" rid="ref32">32</xref>]. Emerging signals include increasing user reliance on PH-LLMs for health-related guidance, emotionally dependent use patterns, early indicators of therapeutic displacement, and the influence of interface design and deployment context on safety, trust, and care-seeking behavior [<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref56">56</xref>-<xref ref-type="bibr" rid="ref59">59</xref>]. Forward-looking risks include population-level safety effects, large-scale longitudinal profiling, governance challenges in multimodal and open-source deployments, and health-related use of general-purpose LLMs, where evidence remains limited and many safeguards have not yet been prospectively validated. This framework should therefore be understood as evidence-informed but partly anticipatory, identifying plausible governance needs where empirical certainty remains uneven.</p>
    </sec>
    <sec>
      <title>Conclusion</title>
      <p>PH-LLMs are rapidly emerging as widely used interfaces for health sensemaking and self-management. Their direct-to-consumer deployment introduces a distinct ethical risk profile spanning 6 domains: privacy, accuracy, equity, transparency, human-AI interaction, and regulatory governance. Because failures across these domains may propagate harm at scale, governance for PH-LLMs should be not only principle-based but also operational and life cycle-oriented. We therefore propose a principlism-grounded framework that translates beneficence, nonmaleficence, autonomy, and justice into deployable safeguards across developers, deployers, health care institutions, regulators, and users. This framework is intended as an evidence-informed but partly anticipatory governance approach rather than an empirically validated solution set. Ongoing oversight will likely require continuous monitoring, adverse-event reporting, and, where appropriate, independent safety evaluation. Future work should prospectively examine the feasibility, effects, and implementation trade-offs of these mechanisms, including whether privacy-preserving forms of health-context activation could support limited adaptation of selected framework components to general-purpose LLMs used for health-related queries.</p>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Protected-attribute handling for fairness monitoring.</p>
        <media xlink:href="jmir_v28i1e92240_app1.docx" xlink:title="DOCX File , 21 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Developer lifecycle responsibilities and adverse-event reporting.</p>
        <media xlink:href="jmir_v28i1e92240_app2.docx" xlink:title="DOCX File , 18 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Standards and institutional anchors for risk-tiered certification.</p>
        <media xlink:href="jmir_v28i1e92240_app3.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>YouthPH-LLM case: full stakeholder specification.</p>
        <media xlink:href="jmir_v28i1e92240_app4.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Illustrative retention windows for tiered consent architecture.</p>
        <media xlink:href="jmir_v28i1e92240_app5.docx" xlink:title="DOCX File , 19 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Illustrative scope boundaries: permitted versus clinician-dependent functions.</p>
        <media xlink:href="jmir_v28i1e92240_app6.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app7">
        <label>Multimedia Appendix 7</label>
        <p>Adverse-event severity categories and response pathways.</p>
        <media xlink:href="jmir_v28i1e92240_app7.docx" xlink:title="DOCX File , 18 KB"/>
      </supplementary-material>
      <supplementary-material id="app8">
        <label>Multimedia Appendix 8</label>
        <p>Feasibility, cost categories, and implementation trade-offs.</p>
        <media xlink:href="jmir_v28i1e92240_app8.docx" xlink:title="DOCX File , 22 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">PH-LLM</term>
          <def>
            <p>personal health large language model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>Following initial drafting, the authors used ChatGPT (OpenAI) for language editing to improve clarity. All artificial intelligence–generated suggestions were critically reviewed and revised as needed. The authors assume full responsibility for the final content and integrity of the manuscript.</p>
    </ack>
    <notes>
      <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>
    </notes>
    <notes>
      <title>Funding</title>
      <p>No external financial support or grants were received from any public, commercial, or not-for-profit entities for the research, authorship, or publication of this article.</p>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>JL and SL contributed to the conceptualization and design of the viewpoint. JL and SL conducted the literature analysis and drafted the original manuscript. All authors critically revised the manuscript for important intellectual content, approved the final version, and agreed to be accountable for all aspects of the work.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khasentino</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Belyaeva</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Furlotte</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Schenck</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schneider</surname>
              <given-names>LD</given-names>
            </name>
            <name name-style="western">
              <surname>Bryant</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gomes</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Perez</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Speed</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Tailor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Althoff</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Heneghan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hernandez</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Malhotra</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stern</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Matias</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Corrado</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shetty</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prabhakara</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McDuff</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>McLean</surname>
              <given-names>CY</given-names>
            </name>
          </person-group>
          <article-title>A personal health large language model for sleep and fitness coaching</article-title>
          <source>Nat Med</source>
          <year>2025</year>
          <volume>31</volume>
          <issue>10</issue>
          <fpage>3394</fpage>
          <lpage>3403</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-025-03888-0</pub-id>
          <pub-id pub-id-type="medline">40813712</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-025-03888-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC12532688</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>Aydin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Karabacak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vlachos</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Margetis</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Large language models in patient education: a scoping review of applications in medicine</article-title>
          <source>Front Med (Lausanne)</source>
          <year>2024</year>
          <volume>11</volume>
          <fpage>1477898</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fmed.2024.1477898"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fmed.2024.1477898</pub-id>
          <pub-id pub-id-type="medline">39534227</pub-id>
          <pub-id pub-id-type="pmcid">PMC11554522</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huo</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Boyle</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marfo</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Tangamornsuksan</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Steen</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>McKechnie</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mayol</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Antoniou</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Thirunavukarasu</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Sanger</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ramji</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Guyatt</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Large language models for chatbot health advice studies: a systematic review</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>e2457879</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2024.57879"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.57879</pub-id>
          <pub-id pub-id-type="medline">39903463</pub-id>
          <pub-id pub-id-type="pii">2829839</pub-id>
          <pub-id pub-id-type="pmcid">PMC11795331</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>Improving service access and quality</article-title>
          <source>World Health Organization</source>
          <access-date>2026-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/activities/improving-service-access-and-quality">https://www.who.int/activities/improving-service-access-and-quality</ext-link>
          </comment>
        </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>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>DCF</given-names>
            </name>
            <name name-style="western">
              <surname>Mei</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Yorke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Chatbot-delivered interventions for improving mental health among young people: a systematic review and meta-analysis</article-title>
          <source>Worldviews Evid Based Nurs</source>
          <year>2025</year>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>e70059</fpage>
          <pub-id pub-id-type="doi">10.1111/wvn.70059</pub-id>
          <pub-id pub-id-type="medline">40662463</pub-id>
          <pub-id pub-id-type="pmcid">PMC12261465</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <article-title>WHO releases AI ethics and governance guidance for large multi-modal models</article-title>
          <source>World Health Organization</source>
          <year>2024</year>
          <access-date>2026-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/news/item/18-01-2024-who-releases-ai-ethics-and-governance-guidance-for-large-multi-modal-models">https://www.who.int/news/item/18-01-2024-who-releases-ai-ethics-and-governance-guidance-for-large-multi-modal-models</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>OpenAI</collab>
          </person-group>
          <article-title>Introducing ChatGPT Health</article-title>
          <source>OpenAI Blog</source>
          <year>2026</year>
          <access-date>2026-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openai.com/index/introducing-chatgpt-health">https://openai.com/index/introducing-chatgpt-health</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <article-title>What is ChatGPT Health? OpenAI help center</article-title>
          <source>OpenAI</source>
          <year>2026</year>
          <access-date>2026-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://help.openai.com/en/articles/20001036-what-is-chatgpt-health">https://help.openai.com/en/articles/20001036-what-is-chatgpt-health</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Anthropic</collab>
          </person-group>
          <article-title>Advancing Claude in healthcare and the life sciences</article-title>
          <source>Anthropic News</source>
          <year>2026</year>
          <access-date>2026-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.anthropic.com/news/healthcare-life-sciences">https://www.anthropic.com/news/healthcare-life-sciences</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abramson</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Fitbit’s personal health coach in public preview is here</article-title>
          <source>Google (The Keyword)</source>
          <year>2025</year>
          <access-date>2026-01-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://blog.google/products-and-platforms/devices/fitbit/personal-health-coach-public-preview/">https://blog.google/products-and-platforms/devices/fitbit/personal-health-coach-public-preview/</ext-link>
          </comment>
        </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>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Ethical considerations of using ChatGPT in health care</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <volume>25</volume>
          <fpage>e48009</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e48009/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/48009</pub-id>
          <pub-id pub-id-type="medline">37566454</pub-id>
          <pub-id pub-id-type="pii">v25i1e48009</pub-id>
          <pub-id pub-id-type="pmcid">PMC10457697</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <article-title>Ethics and governance of artificial intelligence for health: guidance on large multi-modal models</article-title>
          <source>World Health Organization</source>
          <year>2025</year>
          <access-date>2026-01-10</access-date>
          <publisher-loc>Geneva</publisher-loc>
          <publisher-name>WHO</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/9789240084759">https://www.who.int/publications/i/item/9789240084759</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <article-title>What is special category data? UK GDPR guidance</article-title>
          <source>Information Commissioner’s Office</source>
          <year>2024</year>
          <access-date>2026-01-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/special-category-data/what-is-special-category-data/">https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/special-category-data/what-is-special-category-data/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kwesi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Manchanda</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Emami-Naeini</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Exploring user security and privacy attitudes and concerns toward the use of general-purpose LLM chatbots for mental health</article-title>
          <year>2025</year>
          <conf-name>SEC '25: Proceedings of the 34th USENIX Conference on Security Symposium</conf-name>
          <conf-date>2025 August 13 - 15</conf-date>
          <conf-loc>Seattle WA USA</conf-loc>
          <fpage>6007</fpage>
          <lpage>6024</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Papneja</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yadav</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Self-disclosure to conversational AI: A literature review, emergent framework, and directions for future research</article-title>
          <source>Pers Ubiquit Comput</source>
          <year>2024</year>
          <volume>29</volume>
          <issue>2</issue>
          <fpage>119</fpage>
          <lpage>151</lpage>
          <pub-id pub-id-type="doi">10.1007/s00779-024-01823-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marks</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Haupt</surname>
              <given-names>CE</given-names>
            </name>
          </person-group>
          <article-title>AI chatbots, health privacy, and challenges to HIPAA compliance</article-title>
          <source>JAMA</source>
          <year>2023</year>
          <volume>330</volume>
          <issue>4</issue>
          <fpage>309</fpage>
          <lpage>310</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2023.9458</pub-id>
          <pub-id pub-id-type="medline">37410450</pub-id>
          <pub-id pub-id-type="pii">2807170</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>King</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Klyman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Capstick</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Saade</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hsieh</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>User privacy and large language models: an analysis of frontier developers’ privacy policies</article-title>
          <source>AIES</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>1465</fpage>
          <lpage>1477</lpage>
          <pub-id pub-id-type="doi">10.1609/aies.v8i2.36646</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>OWASP Top 10 for large language model applications 2025</article-title>
          <source>OWASP Foundation</source>
          <year>2024</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://owasp.org/www-project-top-10-for-large-language-model-applications/">https://owasp.org/www-project-top-10-for-large-language-model-applications/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Doherty</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Baldwin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lambe</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Altini</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Caulfield</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Privacy in consumer wearable technologies: a living systematic analysis of data policies across leading manufacturers</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>363</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01757-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01757-1</pub-id>
          <pub-id pub-id-type="medline">40517175</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01757-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC12167361</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>Chikwetu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Miao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Woldetensae</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Goldenholz</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Dunn</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Does deidentification of data from wearable devices give us a false sense of security? A systematic review</article-title>
          <source>Lancet Digit Health</source>
          <year>2023</year>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e239</fpage>
          <lpage>e247</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(22)00234-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(22)00234-5</pub-id>
          <pub-id pub-id-type="medline">36797124</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(22)00234-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC10040444</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>Asgari</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Montaña-Brown</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Dubois</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Khalil</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Balloch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yeung</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Pimenta</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A framework to assess clinical safety and hallucination rates of LLMs for medical text summarisation</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>274</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01670-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01670-7</pub-id>
          <pub-id pub-id-type="medline">40360677</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01670-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC12075489</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>Jun</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Suh</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Vulnerability of large language models to prompt injection when providing medical advice</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>12</issue>
          <fpage>e2549963</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2025.49963"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.49963</pub-id>
          <pub-id pub-id-type="medline">41632124</pub-id>
          <pub-id pub-id-type="pii">2842987</pub-id>
          <pub-id pub-id-type="pmcid">PMC12717619</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ouyang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Trust transfer from medical AI to doctors and hospitals: integrating digital, AI, and scientific literacy in a cross-sectional framework</article-title>
          <source>BMC Med Ethics</source>
          <year>2025</year>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>144</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedethics.biomedcentral.com/articles/10.1186/s12910-025-01300-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12910-025-01300-7</pub-id>
          <pub-id pub-id-type="medline">41107871</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12910-025-01300-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC12535035</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>Keene Woods</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Medina</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reyes</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chesser</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>Health literacy, health outcomes and equity: a trend analysis based on a population survey</article-title>
          <source>J Prim Care Community Health</source>
          <year>2023</year>
          <volume>14</volume>
          <fpage>21501319231156132</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/21501319231156132?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/21501319231156132</pub-id>
          <pub-id pub-id-type="medline">36852725</pub-id>
          <pub-id pub-id-type="pmcid">PMC10071098</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shenkman</surname>
              <given-names>LJ</given-names>
            </name>
          </person-group>
          <article-title>Health literacy and health outcomes of adults in the United States: implications for providers</article-title>
          <source>IJAHSP</source>
          <year>2018</year>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.46743/1540-580x/2018.1689</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iftikhar</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ransom</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Suresh</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>How LLM counselors violate ethical standards in mental health practice: a practitioner-informed framework</article-title>
          <source>AIES</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>1311</fpage>
          <lpage>1323</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1609/aies.v8i2.36632"/>
          </comment>
          <pub-id pub-id-type="doi">10.1609/aies.v8i2.36632</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>DiPaola</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sap</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>HW</given-names>
            </name>
            <name name-style="western">
              <surname>Breazeal</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Empathy toward artificial intelligence versus human experiences and the role of transparency in mental health and social support chatbot design: comparative study</article-title>
          <source>JMIR Ment Health</source>
          <year>2024</year>
          <volume>11</volume>
          <fpage>e62679</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mental.jmir.org/2024//e62679/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/62679</pub-id>
          <pub-id pub-id-type="medline">39321450</pub-id>
          <pub-id pub-id-type="pii">v11i1e62679</pub-id>
          <pub-id pub-id-type="pmcid">PMC11464935</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pichowicz</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kotas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Piotrowski</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Performance of mental health chatbot agents in detecting and managing suicidal ideation</article-title>
          <source>Sci Rep</source>
          <year>2025</year>
          <volume>15</volume>
          <issue>1</issue>
          <fpage>31652</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-025-17242-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-025-17242-4</pub-id>
          <pub-id pub-id-type="medline">40866537</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-025-17242-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC12391427</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duffy</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Character.AI and Google agree to settle lawsuits over teen mental health harms and suicides</article-title>
          <source>CNN Business</source>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cnn.com/2026/01/07/business/character-ai-google-settle-teen-suicide-lawsuit">https://www.cnn.com/2026/01/07/business/character-ai-google-settle-teen-suicide-lawsuit</ext-link>
          </comment>
        </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>Carnat</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Human, all too human: accounting for automation bias in generative large language models</article-title>
          <source>Int Data Priv Law</source>
          <year>2024</year>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>299</fpage>
          <lpage>314</lpage>
          <pub-id pub-id-type="doi">10.1093/idpl/ipae018</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>Shekar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pataranutaporn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sarabu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Cecchi</surname>
              <given-names>GA</given-names>
            </name>
            <name name-style="western">
              <surname>Maes</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>People overtrust AI-generated medical advice despite low accuracy</article-title>
          <source>NEJM AI</source>
          <year>2025</year>
          <volume>2</volume>
          <issue>6</issue>
          <fpage>AIoa2300015</fpage>
          <pub-id pub-id-type="doi">10.1056/aioa2300015</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khera</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Simon</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Ross</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>Automation bias and assistive AI: risk of harm from AI-driven clinical decision support</article-title>
          <source>JAMA</source>
          <year>2023</year>
          <volume>330</volume>
          <issue>23</issue>
          <fpage>2255</fpage>
          <lpage>2257</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2023.22557</pub-id>
          <pub-id pub-id-type="medline">38112824</pub-id>
          <pub-id pub-id-type="pii">2812931</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wingerter</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>Straub</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Schweitzer</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Mitigating automation bias in generative AI through nudges: a cognitive reflection test study</article-title>
          <source>Procedia Comput Sci</source>
          <year>2025</year>
          <volume>270</volume>
          <fpage>2106</fpage>
          <lpage>2114</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2025.09.331</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Al-Sibai</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT Is telling people with psychiatric problems to go off their meds</article-title>
          <source>Futurism</source>
          <year>2025</year>
          <access-date>2026-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://futurism.com/chatgpt-mental-illness-medications">https://futurism.com/chatgpt-mental-illness-medications</ext-link>
          </comment>
        </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>Hough</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Culley</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Erganian</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Alahdab</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Potential risks of GenAI on medical education</article-title>
          <source>BMJ Evid Based Med</source>
          <year>2025</year>
          <volume>30</volume>
          <issue>6</issue>
          <fpage>406</fpage>
          <lpage>408</lpage>
          <pub-id pub-id-type="doi">10.1136/bmjebm-2025-114339</pub-id>
          <pub-id pub-id-type="medline">41326281</pub-id>
          <pub-id pub-id-type="pii">bmjebm-2025-114339</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>Lewis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Marston</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Duffy</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Freemantle</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gilbody</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hunter</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kendrick</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kessler</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mangin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>King</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lanham</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Nazareth</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Wiles</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bacon</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bird</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Brabyn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Burns</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Hunt</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pervin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Maintenance or discontinuation of antidepressants in primary care</article-title>
          <source>N Engl J Med</source>
          <year>2021</year>
          <volume>385</volume>
          <issue>14</issue>
          <fpage>1257</fpage>
          <lpage>1267</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMoa2106356</pub-id>
          <pub-id pub-id-type="medline">34587384</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>Rodriguez</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Alsentzer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
          </person-group>
          <article-title>Leveraging large language models to foster equity in healthcare</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2024</year>
          <volume>31</volume>
          <issue>9</issue>
          <fpage>2147</fpage>
          <lpage>2150</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocae055</pub-id>
          <pub-id pub-id-type="medline">38511501</pub-id>
          <pub-id pub-id-type="pii">7632598</pub-id>
          <pub-id pub-id-type="pmcid">PMC11339521</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>Omar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sorin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Agbareia</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Apakama</surname>
              <given-names>DU</given-names>
            </name>
            <name name-style="western">
              <surname>Soroush</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sakhuja</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Freeman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Horowitz</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Richardson</surname>
              <given-names>LD</given-names>
            </name>
            <name name-style="western">
              <surname>Nadkarni</surname>
              <given-names>GN</given-names>
            </name>
            <name name-style="western">
              <surname>Klang</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Evaluating and addressing demographic disparities in medical large language models: a systematic review</article-title>
          <source>Int J Equity Health</source>
          <year>2025</year>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>57</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://equityhealthj.biomedcentral.com/articles/10.1186/s12939-025-02419-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12939-025-02419-0</pub-id>
          <pub-id pub-id-type="medline">40011901</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12939-025-02419-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC11866893</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>Pfohl</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Cole-Lewis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sayres</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Neal</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Asiedu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dieng</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tomasev</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rashid</surname>
              <given-names>QM</given-names>
            </name>
            <name name-style="western">
              <surname>Azizi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rostamzadeh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>McCoy</surname>
              <given-names>LG</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Schaekermann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Walton</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Parrish</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nagpal</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dewitt</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mansfield</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Prakash</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Heller</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Karthikesalingam</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Semturs</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Barral</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Corrado</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Matias</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Smith-Loud</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Horn</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Singhal</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A toolbox for surfacing health equity harms and biases in large language models</article-title>
          <source>Nat Med</source>
          <year>2024</year>
          <volume>30</volume>
          <issue>12</issue>
          <fpage>3590</fpage>
          <lpage>3600</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-024-03258-2</pub-id>
          <pub-id pub-id-type="medline">39313595</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-024-03258-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC11645264</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>Hanna</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wakene</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>AO</given-names>
            </name>
            <name name-style="western">
              <surname>Lehmann</surname>
              <given-names>CU</given-names>
            </name>
            <name name-style="western">
              <surname>Medford</surname>
              <given-names>RJ</given-names>
            </name>
          </person-group>
          <article-title>Assessing racial and ethnic bias in text generation by large language models for health care-related tasks: cross-sectional study</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <volume>27</volume>
          <fpage>e57257</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e57257/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/57257</pub-id>
          <pub-id pub-id-type="medline">40080818</pub-id>
          <pub-id pub-id-type="pii">v27i1e57257</pub-id>
          <pub-id pub-id-type="pmcid">PMC11950697</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Unmasking and quantifying racial bias of large language models in medical report generation</article-title>
          <source>Commun Med (Lond)</source>
          <year>2024</year>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>176</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s43856-024-00601-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s43856-024-00601-z</pub-id>
          <pub-id pub-id-type="medline">39256622</pub-id>
          <pub-id pub-id-type="pii">10.1038/s43856-024-00601-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC11387737</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Kessel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Seghers</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schutte</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Monti</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Haig</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wharton</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Roman-Urrestarazu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Larrain</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sapanel</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Stüwe</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bourbonneux</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Yoon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Paccoud</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Borga</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ndili</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sutherland</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Görgens</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Weicken</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Coder</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>de Fatima Marin</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Val</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Profili</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Kosinska</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Browne</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Marcelo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mrazek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Eskandar</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chestnov</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Smelyanskaya</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Källander</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Buttigieg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ramesh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Holly</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rys</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Azzopardi-Muscat</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>de Barros</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Quintana</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Spina</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hyder</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Labrique</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kamel Boulos</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Agrawal</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Klucken</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prainsack</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Balicer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kickbusch</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Novillo-Ortiz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mossialos</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>A scoping review and expert consensus on digital determinants of health</article-title>
          <source>Bull World Health Organ</source>
          <year>2025</year>
          <volume>103</volume>
          <issue>2</issue>
          <fpage>110</fpage>
          <lpage>125H</lpage>
          <pub-id pub-id-type="doi">10.2471/BLT.24.292057</pub-id>
          <pub-id pub-id-type="medline">39882497</pub-id>
          <pub-id pub-id-type="pii">BLT.24.292057</pub-id>
          <pub-id pub-id-type="pmcid">PMC11774227</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>Ong</surname>
              <given-names>JCL</given-names>
            </name>
            <name name-style="western">
              <surname>Seng</surname>
              <given-names>BJJ</given-names>
            </name>
            <name name-style="western">
              <surname>Law</surname>
              <given-names>JZF</given-names>
            </name>
            <name name-style="western">
              <surname>Low</surname>
              <given-names>LL</given-names>
            </name>
            <name name-style="western">
              <surname>Kwa</surname>
              <given-names>ALH</given-names>
            </name>
            <name name-style="western">
              <surname>Giacomini</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DSW</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence, ChatGPT, and other large language models for social determinants of health: current state and future directions</article-title>
          <source>Cell Rep Med</source>
          <year>2024</year>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>101356</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2666-3791(23)00573-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.xcrm.2023.101356</pub-id>
          <pub-id pub-id-type="medline">38232690</pub-id>
          <pub-id pub-id-type="pii">S2666-3791(23)00573-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC10829781</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>Davies</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Honeyman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gann</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Addressing the digital inverse care law in the time of COVID-19: potential for digital technology to exacerbate or mitigate health inequalities</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>e21726</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/4/e21726/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21726</pub-id>
          <pub-id pub-id-type="medline">33735096</pub-id>
          <pub-id pub-id-type="pii">v23i4e21726</pub-id>
          <pub-id pub-id-type="pmcid">PMC8030655</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>Hart</surname>
              <given-names>JT</given-names>
            </name>
          </person-group>
          <article-title>The inverse care law</article-title>
          <source>Lancet</source>
          <year>1971</year>
          <volume>1</volume>
          <issue>7696</issue>
          <fpage>405</fpage>
          <lpage>412</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0140-6736(71)92410-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/s0140-6736(71)92410-x</pub-id>
          <pub-id pub-id-type="medline">4100731</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(71)92410-X</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>Mesinovic</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Watkinson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Explainability in the age of large language models for healthcare</article-title>
          <source>Commun Eng</source>
          <year>2025</year>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>128</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s44172-025-00453-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s44172-025-00453-y</pub-id>
          <pub-id pub-id-type="medline">40676176</pub-id>
          <pub-id pub-id-type="pii">10.1038/s44172-025-00453-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC12271443</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>Savage</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Nayak</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gallo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rangan</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Diagnostic reasoning prompts reveal the potential for large language model interpretability in medicine</article-title>
          <source>NPJ Digit Med</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>20</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-024-01010-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-024-01010-1</pub-id>
          <pub-id pub-id-type="medline">38267608</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-024-01010-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC10808088</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>Shumway</surname>
              <given-names>DO</given-names>
            </name>
            <name name-style="western">
              <surname>Hartman</surname>
              <given-names>HJ</given-names>
            </name>
          </person-group>
          <article-title>Medical malpractice liability in large language model artificial intelligence: legal review and policy recommendations</article-title>
          <source>J Osteopath Med</source>
          <year>2024</year>
          <volume>124</volume>
          <issue>7</issue>
          <fpage>287</fpage>
          <lpage>290</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.degruyterbrill.com/document/doi/10.1515/jom-2023-0229"/>
          </comment>
          <pub-id pub-id-type="doi">10.1515/jom-2023-0229</pub-id>
          <pub-id pub-id-type="medline">38295300</pub-id>
          <pub-id pub-id-type="pii">jom-2023-0229</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>Mennella</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Maniscalco</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>De Pietro</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Esposito</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Ethical and regulatory challenges of AI technologies in healthcare: a narrative review</article-title>
          <source>Heliyon</source>
          <year>2024</year>
          <volume>10</volume>
          <issue>4</issue>
          <fpage>e26297</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2405-8440(24)02328-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.heliyon.2024.e26297</pub-id>
          <pub-id pub-id-type="medline">38384518</pub-id>
          <pub-id pub-id-type="pii">S2405-8440(24)02328-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC10879008</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>Noto</surname>
              <given-names>LDG</given-names>
            </name>
            <name name-style="western">
              <surname>Bezerra</surname>
              <given-names>LCT</given-names>
            </name>
          </person-group>
          <article-title>Can there be responsible AI without AI liability? Incentivizing generative AI safety through ex-post tort liability under the EU AI liability directive</article-title>
          <source>Int J Law Inf Technol</source>
          <year>2024</year>
          <volume>32</volume>
          <fpage>eaae021</fpage>
          <pub-id pub-id-type="doi">10.1093/ijlit/eaae021</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>Peter</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Riemer</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>JD</given-names>
            </name>
          </person-group>
          <article-title>The benefits and dangers of anthropomorphic conversational agents</article-title>
          <source>Proc Natl Acad Sci U S A</source>
          <year>2025</year>
          <volume>122</volume>
          <issue>22</issue>
          <fpage>e2415898122</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pnas.org/doi/10.1073/pnas.2415898122?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1073/pnas.2415898122</pub-id>
          <pub-id pub-id-type="medline">40378006</pub-id>
          <pub-id pub-id-type="pmcid">PMC12146756</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>Sobowale</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Humphrey</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>SY</given-names>
            </name>
          </person-group>
          <article-title>Evaluating generative AI psychotherapy chatbots used by youth: cross-sectional study</article-title>
          <source>JMIR Ment Health</source>
          <year>2025</year>
          <volume>12</volume>
          <fpage>e79838</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mental.jmir.org/2025//e79838/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/79838</pub-id>
          <pub-id pub-id-type="medline">41370787</pub-id>
          <pub-id pub-id-type="pii">v12i1e79838</pub-id>
          <pub-id pub-id-type="pmcid">PMC12694945</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>Laestadius</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bishop</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Illenčík</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Campos-Castillo</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Too human and not human enough: a grounded theory analysis of mental health harms from emotional dependence on the social chatbot Replika</article-title>
          <source>New Media Soc</source>
          <year>2022</year>
          <volume>26</volume>
          <issue>10</issue>
          <fpage>5923</fpage>
          <lpage>5941</lpage>
          <pub-id pub-id-type="doi">10.1177/14614448221142007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hua</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Siddals</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Galatzer-Levy</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Xia</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Hau</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Na</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Flathers</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Linardon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ayubcha</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Torous</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Charting the evolution of artificial intelligence mental health chatbots from rule-based systems to large language models: a systematic review</article-title>
          <source>World Psychiatry</source>
          <year>2025</year>
          <volume>24</volume>
          <issue>3</issue>
          <fpage>383</fpage>
          <lpage>394</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1002/wps.21352"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/wps.21352</pub-id>
          <pub-id pub-id-type="medline">40948070</pub-id>
          <pub-id pub-id-type="pmcid">PMC12434366</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>Zhang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ji</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Effects of attractions and social attributes on peoples' usage intention and media dependence towards chatbot: the mediating role of parasocial interaction and emotional support</article-title>
          <source>BMC Psychol</source>
          <year>2025</year>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>986</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpsychology.biomedcentral.com/articles/10.1186/s40359-025-03284-w"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40359-025-03284-w</pub-id>
          <pub-id pub-id-type="medline">40883845</pub-id>
          <pub-id pub-id-type="pii">10.1186/s40359-025-03284-w</pub-id>
          <pub-id pub-id-type="pmcid">PMC12398025</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="web">
          <article-title>Talk, trust, and trade-offs: how and why teens use AI companions</article-title>
          <source>Common Sense Media</source>
          <year>2025</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.commonsensemedia.org/sites/default/files/research/report/talk-trust-and-trade-offs_2025_web.pdf">https://www.commonsensemedia.org/sites/default/files/research/report/talk-trust-and-trade-offs_2025_web.pdf</ext-link>
          </comment>
        </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>Faverio</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sidoti</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Teens, social media and AI chatbots 2025</article-title>
          <source>Pew Research Center</source>
          <year>2025</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewresearch.org/internet/2025/12/09/teens-social-media-and-ai-chatbots-2025/">https://www.pewresearch.org/internet/2025/12/09/teens-social-media-and-ai-chatbots-2025/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ischen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Butler</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ohme</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Chatting about the unaccepted: self-disclosure of unaccepted news exposure behaviour to a chatbot</article-title>
          <source>Behav Inf Technol</source>
          <year>2023</year>
          <volume>43</volume>
          <issue>10</issue>
          <fpage>2044</fpage>
          <lpage>2056</lpage>
          <pub-id pub-id-type="doi">10.1080/0144929x.2023.2237605</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Skjuve</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Følstad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Brandtzæg</surname>
              <given-names>PB</given-names>
            </name>
          </person-group>
          <article-title>A longitudinal study of self-disclosure in human–chatbot relationships</article-title>
          <source>Interact Comput</source>
          <year>2023</year>
          <volume>35</volume>
          <issue>1</issue>
          <fpage>24</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.1093/iwc/iwad022</pub-id>
        </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>Catapan</surname>
              <given-names>SDC</given-names>
            </name>
            <name name-style="western">
              <surname>Sazon</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gallegos-Rejas</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Mendis</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Santiago</surname>
              <given-names>PHR</given-names>
            </name>
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>JT</given-names>
            </name>
          </person-group>
          <article-title>A systematic review of consumers' and healthcare professionals' trust in digital healthcare</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>115</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01510-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01510-8</pub-id>
          <pub-id pub-id-type="medline">39984678</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01510-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC11845731</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>Birkhäuer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gaab</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kossowsky</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hasler</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Krummenacher</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Werner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gerger</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Trust in the health care professional and health outcome: a meta-analysis</article-title>
          <source>PLoS One</source>
          <year>2017</year>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>e0170988</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0170988"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0170988</pub-id>
          <pub-id pub-id-type="medline">28170443</pub-id>
          <pub-id pub-id-type="pii">PONE-D-16-37935</pub-id>
          <pub-id pub-id-type="pmcid">PMC5295692</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>Beatty</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Malik</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Meheli</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sinha</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the therapeutic alliance with a free-text CBT conversational agent (Wysa): a mixed-methods study</article-title>
          <source>Front Digit Health</source>
          <year>2022</year>
          <volume>4</volume>
          <fpage>847991</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35480848"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2022.847991</pub-id>
          <pub-id pub-id-type="medline">35480848</pub-id>
          <pub-id pub-id-type="pmcid">PMC9035685</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Martinengo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Jabir</surname>
              <given-names>AI</given-names>
            </name>
            <name name-style="western">
              <surname>Kowatsch</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Atun</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tudor Car</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Conversational agents in health care: expert interviews to inform the definition, classification, and conceptual framework</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <volume>25</volume>
          <fpage>e50767</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e50767/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/50767</pub-id>
          <pub-id pub-id-type="medline">37910153</pub-id>
          <pub-id pub-id-type="pii">v25i1e50767</pub-id>
          <pub-id pub-id-type="pmcid">PMC10652195</pub-id>
        </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>Saenger</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Hunger</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Boss</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Richter</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Delayed diagnosis of a transient ischemic attack caused by ChatGPT</article-title>
          <source>Wien Klin Wochenschr</source>
          <year>2024</year>
          <volume>136</volume>
          <issue>7-8</issue>
          <fpage>236</fpage>
          <lpage>238</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38305909"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s00508-024-02329-1</pub-id>
          <pub-id pub-id-type="medline">38305909</pub-id>
          <pub-id pub-id-type="pii">10.1007/s00508-024-02329-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC11006786</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>Riboli-Sasco</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>El-Osta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alaa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Webber</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Karki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>El Asmar</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Purohit</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Painter</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hayhoe</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Triage and diagnostic accuracy of online symptom checkers: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <volume>25</volume>
          <fpage>e43803</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e43803/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/43803</pub-id>
          <pub-id pub-id-type="medline">37266983</pub-id>
          <pub-id pub-id-type="pii">v25i1e43803</pub-id>
          <pub-id pub-id-type="pmcid">PMC10276326</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>Woodcock</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mittelstadt</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Busbridge</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Blank</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>The impact of explanations on layperson trust in artificial intelligence-driven symptom checker apps: experimental study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>11</issue>
          <fpage>e29386</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/11/e29386/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/29386</pub-id>
          <pub-id pub-id-type="medline">34730544</pub-id>
          <pub-id pub-id-type="pii">v23i11e29386</pub-id>
          <pub-id pub-id-type="pmcid">PMC8600426</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>Wallace</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chidambaram</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hanna</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Iqbal</surname>
              <given-names>FM</given-names>
            </name>
            <name name-style="western">
              <surname>Acharya</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Normahani</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ashrafian</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Markar</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Sounderajah</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The diagnostic and triage accuracy of digital and online symptom checker tools: a systematic review</article-title>
          <source>NPJ Digit Med</source>
          <year>2022</year>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>118</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-022-00667-w"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-022-00667-w</pub-id>
          <pub-id pub-id-type="medline">35977992</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-022-00667-w</pub-id>
          <pub-id pub-id-type="pmcid">PMC9385087</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="web">
          <article-title>Tele-triage</article-title>
          <source>US Department of Health and Human Services</source>
          <year>2025</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://telehealth.hhs.gov/providers/best-practice-guides/telehealth-for-emergency-departments/tele-triage">https://telehealth.hhs.gov/providers/best-practice-guides/telehealth-for-emergency-departments/tele-triage</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="web">
          <article-title>Covered entities and business associates</article-title>
          <source>US Department of Health and Human Services</source>
          <year>2024</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html">https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tovino</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and the HIPAA privacy rule: a primer</article-title>
          <source>Hous J Health Law Policy</source>
          <year>2024</year>
          <volume>24</volume>
          <fpage>77</fpage>
          <lpage>140</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digitalcommons.law.ou.edu/cgi/viewcontent.cgi?params=/context/fac_articles/article/1648/&#38;path_info=Tovino_2025_Artificial_Intelligence_and_the_HIPAA_Privacy_Rule.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="web">
          <source>Office for Civil Rights, U.S. Department of Health and Human Services</source>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access-right-health-apps-apis/">https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access-right-health-apps-apis/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Savage</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Savage</surname>
              <given-names>LC</given-names>
            </name>
          </person-group>
          <article-title>Doctors routinely share health data electronically under HIPAA, and sharing with patients and patients' third-party health apps is consistent: interoperability and privacy analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <volume>22</volume>
          <issue>9</issue>
          <fpage>e19818</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/9/e19818/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19818</pub-id>
          <pub-id pub-id-type="medline">32876582</pub-id>
          <pub-id pub-id-type="pii">v22i9e19818</pub-id>
          <pub-id pub-id-type="pmcid">PMC7495255</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="web">
          <article-title>FTC to ban betterHelp from revealing consumers’ data, including sensitive mental health information, to Facebook and others for targeted advertising</article-title>
          <source>Federal Trade Commission</source>
          <year>2023</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ftc.gov/news-events/news/press-releases/2023/03/ftc-ban-betterhelp-revealing-consumers-data-including-sensitive-mental-health-information-facebook">https://www.ftc.gov/news-events/news/press-releases/2023/03/ftc-ban-betterhelp-revealing-consumers-data-including-sensitive-mental-health-information-facebook</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2024/1689 of the European parliament and of the council of 13 june 2024</article-title>
          <source>European Parliament and Council of the European Union</source>
          <access-date>2026-01-15</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="ref75">
        <label>75</label>
        <nlm-citation citation-type="web">
          <article-title>Interim measures for administration of generative artificial intelligence services</article-title>
          <source>State Council of the People’s Republic of China</source>
          <year>2023</year>
          <access-date>2026-01-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://english.www.gov.cn/archive/statecouncilgazette/202308/30/content_WS64ee8c0cc6d0868f4e8deeea.html">https://english.www.gov.cn/archive/statecouncilgazette/202308/30/content_WS64ee8c0cc6d0868f4e8deeea.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="web">
          <article-title>Framework act on the development of artificial intelligence and the creation of a foundation for trust</article-title>
          <source>Korea Legislation Research Institute / Ministry of Government Legislation</source>
          <year>2025</year>
          <access-date>2026-01-12</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://elaw.klri.re.kr/eng_service/lawView.do?hseq=71019&#38;lang=ENG">https://elaw.klri.re.kr/eng_service/lawView.do?hseq=71019&#38;lang=ENG</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Ministry of Internal Affairs and Communications</collab>
          </person-group>
          <article-title>AI guidelines for business ver1.0</article-title>
          <source>Ministry of Economy, Trade and Industry</source>
          <year>2024</year>
          <access-date>2026-02-26</access-date>
          <publisher-loc>Tokyo, Japan</publisher-loc>
          <publisher-name>Ministry of Economy, Trade and Industry</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.meti.go.jp/english/press/2024/0419_002.html">https://www.meti.go.jp/english/press/2024/0419_002.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="web">
          <article-title>Proposed model AI governance framework for generative AI</article-title>
          <source>Infocomm Media Development Authority</source>
          <year>2024</year>
          <access-date>2026-02-26</access-date>
          <publisher-loc>Singapore</publisher-loc>
          <publisher-name>Infocomm Media Development Authority</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.imda.gov.sg/resources/press-releases-factsheets-and-speeches/press-releases/2024/public-consult-model-ai-governance-framework-genai">https://www.imda.gov.sg/resources/press-releases-factsheets-and-speeches/press-releases/2024/public-consult-model-ai-governance-framework-genai</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Palaniappan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>EYT</given-names>
            </name>
            <name name-style="western">
              <surname>Vogel</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Global regulatory frameworks for the use of artificial intelligence (AI) in the healthcare services sector</article-title>
          <source>Healthcare (Basel)</source>
          <year>2024</year>
          <volume>12</volume>
          <issue>5</issue>
          <fpage>562</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare12050562"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare12050562</pub-id>
          <pub-id pub-id-type="medline">38470673</pub-id>
          <pub-id pub-id-type="pii">healthcare12050562</pub-id>
          <pub-id pub-id-type="pmcid">PMC10930608</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aboy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Minssen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vayena</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Navigating the EU AI Act: implications for regulated digital medical products</article-title>
          <source>NPJ Digit Med</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>237</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-024-01232-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-024-01232-3</pub-id>
          <pub-id pub-id-type="medline">39242831</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-024-01232-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC11379845</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</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>
          <year>2021</year>
          <access-date>2026-01-16</access-date>
          <publisher-loc>Geneva</publisher-loc>
          <publisher-name>World Health Organization</publisher-name>
          <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="ref82">
        <label>82</label>
        <nlm-citation citation-type="web">
          <article-title>Recommendation of the council on artificial intelligence</article-title>
          <source>Organization for Economic Co-operation and Development</source>
          <year>2019</year>
          <access-date>2026-01-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0449">https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0449</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beauchamp</surname>
              <given-names>TL</given-names>
            </name>
            <name name-style="western">
              <surname>Childress</surname>
              <given-names>JF</given-names>
            </name>
          </person-group>
          <source>Principles of Biomedical Ethics</source>
          <year>2019</year>
          <publisher-loc>New York</publisher-loc>
          <publisher-name>Oxford University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bakker</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Klopotowska</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Dongelmans</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Eslami</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vermeijden</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hendriks</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ten Cate</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Karakus</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Purmer</surname>
              <given-names>IM</given-names>
            </name>
            <name name-style="western">
              <surname>van Bree</surname>
              <given-names>SHW</given-names>
            </name>
            <name name-style="western">
              <surname>Spronk</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Hoeksema</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>de Jonge</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>de Keizer</surname>
              <given-names>NF</given-names>
            </name>
            <name name-style="western">
              <surname>Abu-Hanna</surname>
              <given-names>A</given-names>
            </name>
            <collab>SIMPLIFY study group</collab>
          </person-group>
          <article-title>The effect of computerised decision support alerts tailored to intensive care on the administration of high-risk drug combinations, and their monitoring: a cluster randomised stepped-wedge trial</article-title>
          <source>Lancet</source>
          <year>2024</year>
          <volume>403</volume>
          <issue>10425</issue>
          <fpage>439</fpage>
          <lpage>449</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(23)02465-0</pub-id>
          <pub-id pub-id-type="medline">38262430</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(23)02465-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amugongo</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Mascheroni</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Brooks</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Doering</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Seidel</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Retrieval augmented generation for large language models in healthcare: a systematic review</article-title>
          <source>PLOS Digit Health</source>
          <year>2025</year>
          <volume>4</volume>
          <issue>6</issue>
          <fpage>e0000877</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pdig.0000877"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pdig.0000877</pub-id>
          <pub-id pub-id-type="medline">40498738</pub-id>
          <pub-id pub-id-type="pii">PDIG-D-24-00337</pub-id>
          <pub-id pub-id-type="pmcid">PMC12157099</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brückner</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dridi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Deshmukh</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kirsten</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lauber-Rönsberg</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Riedel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hetmank</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Welzel</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gilbert</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A user-driven consent platform for health data sharing in digital health applications</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>699</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-02147-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-02147-3</pub-id>
          <pub-id pub-id-type="medline">41298895</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-02147-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC12657888</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2016/679 of the European parliament and of the council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation)</article-title>
          <source>European Parliament and Council of the European Union</source>
          <access-date>2026-04-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/eli/reg/2016/679/oj">https://eur-lex.europa.eu/eli/reg/2016/679/oj</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alderman</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Palmer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Laws</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McCradden</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Ordish</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ghassemi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pfohl</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Rostamzadeh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Cole-Lewis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Glocker</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Calvert</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pollard</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gill</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gath</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Adebajo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Beng</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>CH</given-names>
            </name>
            <name name-style="western">
              <surname>Kuku</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Farmer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Matin</surname>
              <given-names>RN</given-names>
            </name>
            <name name-style="western">
              <surname>Mateen</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>McKay</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Heller</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Karthikesalingam</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Treanor</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mackintosh</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Oakden-Rayner</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Pearson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Manrai</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Myles</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kumuthini</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kapacee</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Sebire</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Nazer</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Seah</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Akbari</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Berman</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gichoya</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Righetto</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Samuel</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wasswa</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Charalambides</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pujari</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Summers</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sapey</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Thakker</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Denniston</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Tackling algorithmic bias and promoting transparency in health datasets: the STANDING together consensus recommendations</article-title>
          <source>Lancet Digit Health</source>
          <year>2025</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>e64</fpage>
          <lpage>e88</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(24)00224-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(24)00224-3</pub-id>
          <pub-id pub-id-type="medline">39701919</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(24)00224-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC11668905</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hatef</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Hudson Scholle</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Buckley</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Weiner</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Austin</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Development of an evidence- and consensus-based digital healthcare equity framework</article-title>
          <source>JAMIA Open</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>4</issue>
          <fpage>ooae136</fpage>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooae136</pub-id>
          <pub-id pub-id-type="medline">39553827</pub-id>
          <pub-id pub-id-type="pii">ooae136</pub-id>
          <pub-id pub-id-type="pmcid">PMC11565864</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Babic</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Glenn Cohen</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Stern</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ouellet</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A general framework for governing marketed AI/ML medical devices</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>328</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01717-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01717-9</pub-id>
          <pub-id pub-id-type="medline">40450160</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01717-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC12126487</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ning</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Teixayavong</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Mertens</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Miao</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DSW</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>LT</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>JCL</given-names>
            </name>
            <name name-style="western">
              <surname>Teo</surname>
              <given-names>ZL</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>TF</given-names>
            </name>
            <name name-style="western">
              <surname>RaviChandran</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>MEH</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>A scoping review and evidence gap analysis of clinical AI fairness</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>360</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01667-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01667-2</pub-id>
          <pub-id pub-id-type="medline">40517148</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01667-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC12167363</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Templin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Fort</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Padmanabham</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Seshadri</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Rimal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Oliva</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hassmiller Lich</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sylvia</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sinnott-Armstrong</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Framework for bias evaluation in large language models in healthcare settings</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>414</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01786-w"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01786-w</pub-id>
          <pub-id pub-id-type="medline">40624264</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01786-w</pub-id>
          <pub-id pub-id-type="pmcid">PMC12234702</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vasey</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Nagendran</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Clifton</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Denaxas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Denniston</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Faes</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Geerts</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ibrahim</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Mateen</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Mathur</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McCradden</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ordish</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Saria</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DSW</given-names>
            </name>
            <name name-style="western">
              <surname>Watkinson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wheatstone</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>McCulloch</surname>
              <given-names>P</given-names>
            </name>
            <collab>DECIDE-AI expert group</collab>
          </person-group>
          <article-title>Reporting guideline for the early stage clinical evaluation of decision support systems driven by artificial intelligence: DECIDE-AI</article-title>
          <source>BMJ</source>
          <year>2022</year>
          <volume>377</volume>
          <fpage>e070904</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=35584845"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2022-070904</pub-id>
          <pub-id pub-id-type="medline">35584845</pub-id>
          <pub-id pub-id-type="pmcid">PMC9116198</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Health Canada</collab>
            <collab>Medicines and Healthcare products Regulatory Agency</collab>
          </person-group>
          <article-title>Good machine learning practice for medical device development: guiding principles</article-title>
          <source>U.S. Food and Drug Administration</source>
          <year>2021</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/media/153486/download">https://www.fda.gov/media/153486/download</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="web">
          <article-title>Artificial Intelligence Risk Management Framework (AI RMF 1.0)</article-title>
          <source>National Institute of Standards and Technology</source>
          <year>2023</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.6028/NIST.AI.100-1">https://doi.org/10.6028/NIST.AI.100-1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="web">
          <article-title>What is health literacy?</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <year>2024</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/health-literacy/php/about/index.html">https://www.cdc.gov/health-literacy/php/about/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="web">
          <article-title>Clinical decision support software: guidance for industry and food and drug administration staff</article-title>
          <source>US Food and Drug Administration</source>
          <year>2026</year>
          <access-date>2026-02-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/regulatory-information/search-fda-guidance-documents/clinical-decision-support-software">https://www.fda.gov/regulatory-information/search-fda-guidance-documents/clinical-decision-support-software</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bouguettaya</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stuart</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Aboujaoude</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Racial bias in AI-mediated psychiatric diagnosis and treatment: a qualitative comparison of four large language models</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>332</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01746-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01746-4</pub-id>
          <pub-id pub-id-type="medline">40467886</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01746-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC12137607</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref99">
        <label>99</label>
        <nlm-citation citation-type="web">
          <article-title>Use of online tracking technologies by HIPAA covered entities and business associates</article-title>
          <source>US Department of Health and Human Services</source>
          <year>2024</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/hipaa-online-tracking/index.html">https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/hipaa-online-tracking/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="web">
          <article-title>Regulatory considerations on artificial intelligence for health</article-title>
          <source>World Health Organization</source>
          <year>2023</year>
          <access-date>2026-03-10</access-date>
          <publisher-loc>Geneva, Switzerland</publisher-loc>
          <publisher-name>World Health Organization</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/9789240078871">https://www.who.int/publications/i/item/9789240078871</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rozenblit</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Price</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Solomonides</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Joseph</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Koski</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Labkoff</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bray</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez-Gonzalez</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>deBronkart</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Barr</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Szolovits</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dattani</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jaffe</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fridsma</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baris</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Leftwich</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Stolper</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Weiner</surname>
              <given-names>MG</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>Lin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Thuy Bui</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Oladimeji</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>GP</given-names>
            </name>
            <name name-style="western">
              <surname>Hsueh</surname>
              <given-names>PS</given-names>
            </name>
            <name name-style="western">
              <surname>Quintana</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Toward responsible AI governance: balancing multi-stakeholder perspectives on AI in healthcare</article-title>
          <source>Int J Med Inform</source>
          <year>2025</year>
          <volume>203</volume>
          <fpage>106015</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(25)00232-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2025.106015</pub-id>
          <pub-id pub-id-type="medline">40680319</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(25)00232-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="web">
          <article-title>AI system evaluations: independent evaluations. Developing AI accountability: inputs and a deeper dive (AI accountability policy report series)</article-title>
          <source>National Telecommunications and Information Administration</source>
          <year>2024</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ntia.gov/issues/artificial-intelligence/ai-accountability-policy-report/developing-accountability-inputs-a-deeper-dive/ai-system-evaluations/independent-evaluations">https://www.ntia.gov/issues/artificial-intelligence/ai-accountability-policy-report/developing-accountability-inputs-a-deeper-dive/ai-system-evaluations/independent-evaluations</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kiseleva</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kotzinos</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>De Hert</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Transparency of AI in healthcare as a multilayered system of accountabilities: between legal requirements and technical limitations</article-title>
          <source>Front Artif Intell</source>
          <year>2022</year>
          <volume>5</volume>
          <fpage>879603</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35707765"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/frai.2022.879603</pub-id>
          <pub-id pub-id-type="medline">35707765</pub-id>
          <pub-id pub-id-type="pmcid">PMC9189302</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Schweikart</surname>
              <given-names>SJ</given-names>
            </name>
          </person-group>
          <article-title>Are current tort liability doctrines adequate for addressing injury caused by AI?</article-title>
          <source>AMA J Ethics</source>
          <year>2019</year>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>E160</fpage>
          <lpage>E166</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journalofethics.ama-assn.org/article/are-current-tort-liability-doctrines-adequate-addressing-injury-caused-ai/2019-02"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/amajethics.2019.160</pub-id>
          <pub-id pub-id-type="medline">30794126</pub-id>
          <pub-id pub-id-type="pii">amajethics.2019.160</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Longpre</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kapoor</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Klyman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ramaswami</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bommasani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Blili-Hamelin</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A safe harbor for AI evaluation and red teaming</article-title>
          <source>arXiv. Preprint posted online on March 7, 2024</source>
          <pub-id pub-id-type="doi">10.48550/arXiv.2403.04893</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dorn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Matheny</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Emerging algorithmic bias: fairness drift as the next dimension of model maintenance and sustainability</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2025</year>
          <volume>32</volume>
          <issue>5</issue>
          <fpage>845</fpage>
          <lpage>854</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaf039</pub-id>
          <pub-id pub-id-type="medline">40079820</pub-id>
          <pub-id pub-id-type="pii">8074959</pub-id>
          <pub-id pub-id-type="pmcid">PMC12012346</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="web">
          <article-title>The importance of pharmacovigilance: safety monitoring of medicinal products</article-title>
          <source>World Health Organization</source>
          <year>2002</year>
          <access-date>2026-01-15</access-date>
          <publisher-loc>Geneva</publisher-loc>
          <publisher-name>WHO</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://iris.who.int/server/api/core/bitstreams/002b78d5-4dfc-433c-a518-f92ebdee8706/content">https://iris.who.int/server/api/core/bitstreams/002b78d5-4dfc-433c-a518-f92ebdee8706/content</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="web">
          <article-title>Marketing submission recommendations for a predetermined change control plan for artificial intelligence-enabled device software functions</article-title>
          <source>US Food and Drug Administration</source>
          <year>2024</year>
          <access-date>2026-03-10</access-date>
          <publisher-loc>Silver Spring, MD</publisher-loc>
          <publisher-name>US Food and Drug Administration</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/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="ref109">
        <label>109</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <collab>Council for International Organizations of Medical Sciences (CIOMS)</collab>
          </person-group>
          <source>Artificial Intelligence in Pharmacovigilance: CIOMS Working Group XIV Report</source>
          <year>2025</year>
          <publisher-loc>Geneva</publisher-loc>
          <publisher-name>CIOMS (Council for International Organizations of Medical Sciences)</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="web">
          <article-title>Protecting the privacy and security of your health information when using your personal cell phone or tablet</article-title>
          <source>US Department of Health and Human Services</source>
          <year>2022</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/cell-phone-hipaa/index.html">https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/cell-phone-hipaa/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Le-Khac</surname>
              <given-names>UN</given-names>
            </name>
            <name name-style="western">
              <surname>Truong</surname>
              <given-names>VNX</given-names>
            </name>
          </person-group>
          <article-title>A survey on large language models unlearning: taxonomy, evaluations, and future directions</article-title>
          <source>Artif Intell Rev</source>
          <year>2025</year>
          <volume>58</volume>
          <issue>12</issue>
          <fpage>399</fpage>
          <pub-id pub-id-type="doi">10.1007/s10462-025-11376-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref112">
        <label>112</label>
        <nlm-citation citation-type="web">
          <article-title>2025 national guidelines for a behavioral health coordinated system of crisis care</article-title>
          <source>SAMHSA</source>
          <year>2025</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.chcs.org/resource-center-item/2025-national-guidelines-for-a-behavioral-health-coordinated-system-of-crisis-care/">https://www.chcs.org/resource-center-item/2025-national-guidelines-for-a-behavioral-health-coordinated-system-of-crisis-care/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref113">
        <label>113</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nahum-Shani</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Spring</surname>
              <given-names>BJ</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Witkiewitz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tewari</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>Just-in-time adaptive interventions (JITAIs) in mobile health: key components and design principles for ongoing health behavior support</article-title>
          <source>Ann Behav Med</source>
          <year>2018</year>
          <volume>52</volume>
          <issue>6</issue>
          <fpage>446</fpage>
          <lpage>462</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27663578"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12160-016-9830-8</pub-id>
          <pub-id pub-id-type="medline">27663578</pub-id>
          <pub-id pub-id-type="pii">10.1007/s12160-016-9830-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC5364076</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref114">
        <label>114</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Differential privacy medical data publishing method based on attribute correlation</article-title>
          <source>Sci Rep</source>
          <year>2022</year>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>15725</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-022-19544-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-022-19544-3</pub-id>
          <pub-id pub-id-type="medline">36131115</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-022-19544-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC9492700</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref115">
        <label>115</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garfinkel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Guttman</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Near</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dajani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Singer</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>De-Identifying Government Datasets: Techniques and Governance</source>
          <year>2023</year>
          <publisher-loc>Gaithersburg, MD</publisher-loc>
          <publisher-name>National Institute of Standards and Technology</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref116">
        <label>116</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Farquhar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kossen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gal</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Detecting hallucinations in large language models using semantic entropy</article-title>
          <source>Nature</source>
          <year>2024</year>
          <volume>630</volume>
          <issue>8017</issue>
          <fpage>625</fpage>
          <lpage>630</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38898292"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41586-024-07421-0</pub-id>
          <pub-id pub-id-type="medline">38898292</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-024-07421-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC11186750</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Roustan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bastardot</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>The clinicians' guide to large language models: a general perspective with a focus on hallucinations</article-title>
          <source>Interact J Med Res</source>
          <year>2025</year>
          <volume>14</volume>
          <fpage>e59823</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.i-jmr.org/2025//e59823/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/59823</pub-id>
          <pub-id pub-id-type="medline">39874574</pub-id>
          <pub-id pub-id-type="pii">v14i1e59823</pub-id>
          <pub-id pub-id-type="pmcid">PMC11815294</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Perez</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Piktus</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Petroni</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Karpukhin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Goyal</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Retrieval-augmented generation for knowledge-intensive NLP tasks</article-title>
          <source>Adv Neural Inf Process Syst</source>
          <year>2020</year>
          <volume>33</volume>
          <fpage>9459</fpage>
          <lpage>9474</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arowosegbe</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Oyelade</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Application of natural language processing (NLP) in detecting and preventing suicide ideation: a systematic review</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2023</year>
          <volume>20</volume>
          <issue>2</issue>
          <fpage>1514</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph20021514"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph20021514</pub-id>
          <pub-id pub-id-type="medline">36674270</pub-id>
          <pub-id pub-id-type="pii">ijerph20021514</pub-id>
          <pub-id pub-id-type="pmcid">PMC9859480</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref120">
        <label>120</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pais</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Voigt</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Wade</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bayati</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Large language models for preventing medication direction errors in online pharmacies</article-title>
          <source>Nat Med</source>
          <year>2024</year>
          <volume>30</volume>
          <issue>6</issue>
          <fpage>1574</fpage>
          <lpage>1582</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38664535"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-024-02933-8</pub-id>
          <pub-id pub-id-type="medline">38664535</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-024-02933-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC11186789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>National Library of Medicine</collab>
          </person-group>
          <article-title>RxNorm</article-title>
          <source>National Institutes of Health</source>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nlm.nih.gov/research/umls/rxnorm/index.html">https://www.nlm.nih.gov/research/umls/rxnorm/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="web">
          <article-title>FDA adverse event reporting system (FAERS)</article-title>
          <source>U.S. Food and Drug Administration</source>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/drugs/drug-approvals-and-databases/fda-adverse-event-reporting-system-faers-database">https://www.fda.gov/drugs/drug-approvals-and-databases/fda-adverse-event-reporting-system-faers-database</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>JCL</given-names>
            </name>
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Elangovan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>GYS</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>DYZ</given-names>
            </name>
            <name name-style="western">
              <surname>Sng</surname>
              <given-names>GGR</given-names>
            </name>
            <name name-style="western">
              <surname>Ke</surname>
              <given-names>YH</given-names>
            </name>
            <name name-style="western">
              <surname>Tung</surname>
              <given-names>JYM</given-names>
            </name>
            <name name-style="western">
              <surname>Zhong</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Koh</surname>
              <given-names>CMY</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>KZH</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Ch'ng</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Than</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Goh</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>CP</given-names>
            </name>
            <name name-style="western">
              <surname>Ng</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DSW</given-names>
            </name>
          </person-group>
          <article-title>Large language model as clinical decision support system augments medication safety in 16 clinical specialties</article-title>
          <source>Cell Rep Med</source>
          <year>2025</year>
          <volume>6</volume>
          <issue>10</issue>
          <fpage>102323</fpage>
          <pub-id pub-id-type="doi">10.1016/j.xcrm.2025.102323</pub-id>
          <pub-id pub-id-type="medline">40997804</pub-id>
          <pub-id pub-id-type="pii">S2666-3791(25)00396-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC12629785</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref124">
        <label>124</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zack</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lehman</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Suzgun</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Gichoya</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jurafsky</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Szolovits</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>DW</given-names>
            </name>
            <name name-style="western">
              <surname>Abdulnour</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Butte</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Alsentzer</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Assessing the potential of GPT-4 to perpetuate racial and gender biases in health care: a model evaluation study</article-title>
          <source>Lancet Digit Health</source>
          <year>2024</year>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>e12</fpage>
          <lpage>e22</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(23)00225-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(23)00225-X</pub-id>
          <pub-id pub-id-type="medline">38123252</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(23)00225-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Powers</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Vogeli</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mullainathan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Dissecting racial bias in an algorithm used to manage the health of populations</article-title>
          <source>Science</source>
          <year>2019</year>
          <volume>366</volume>
          <issue>6464</issue>
          <fpage>447</fpage>
          <lpage>453</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://escholarship.org/uc/item/6h92v832"/>
          </comment>
          <pub-id pub-id-type="doi">10.1126/science.aax2342</pub-id>
          <pub-id pub-id-type="medline">31649194</pub-id>
          <pub-id pub-id-type="pii">366/6464/447</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>IY</given-names>
            </name>
            <name name-style="western">
              <surname>Szolovits</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ghassemi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Can AI help reduce disparities in general medical and mental health care?</article-title>
          <source>AMA J Ethics</source>
          <year>2019</year>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>E167</fpage>
          <lpage>E179</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journalofethics.ama-assn.org/article/can-ai-help-reduce-disparities-general-medical-and-mental-health-care/2019-02"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/amajethics.2019.167</pub-id>
          <pub-id pub-id-type="medline">30794127</pub-id>
          <pub-id pub-id-type="pii">amajethics.2019.167</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chin</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Afsar-Manesh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bierman</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Colón-Rodríguez</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Dullabh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Duran</surname>
              <given-names>DG</given-names>
            </name>
            <name name-style="western">
              <surname>Fair</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hernandez-Boussard</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hightower</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jordan</surname>
              <given-names>WB</given-names>
            </name>
            <name name-style="western">
              <surname>Konya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shaheen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Snyder</surname>
              <given-names>LP</given-names>
            </name>
            <name name-style="western">
              <surname>Srinivasan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Umscheid</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Ohno-Machado</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Guiding principles to address the impact of algorithm bias on racial and ethnic disparities in health and health care</article-title>
          <source>JAMA Netw Open</source>
          <year>2023</year>
          <volume>6</volume>
          <issue>12</issue>
          <fpage>e2345050</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38100101"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2023.45050</pub-id>
          <pub-id pub-id-type="medline">38100101</pub-id>
          <pub-id pub-id-type="pii">2812958</pub-id>
          <pub-id pub-id-type="pmcid">PMC11181958</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref128">
        <label>128</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Naderbagi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Loblay</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Zahed</surname>
              <given-names>IUM</given-names>
            </name>
            <name name-style="western">
              <surname>Ekambareshwar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Poulsen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>YJC</given-names>
            </name>
            <name name-style="western">
              <surname>Ospina-Pinillos</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Krausz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mamdouh Kamel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hickie</surname>
              <given-names>IB</given-names>
            </name>
            <name name-style="western">
              <surname>LaMonica</surname>
              <given-names>HM</given-names>
            </name>
          </person-group>
          <article-title>Cultural and contextual adaptation of digital health interventions: narrative review</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e55130</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e55130/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/55130</pub-id>
          <pub-id pub-id-type="medline">38980719</pub-id>
          <pub-id pub-id-type="pii">v26i1e55130</pub-id>
          <pub-id pub-id-type="pmcid">PMC11267096</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref129">
        <label>129</label>
        <nlm-citation citation-type="web">
          <article-title>Web Content Accessibility Guidelines (WCAG) 2.2</article-title>
          <source>World Wide Web Consortium (W3C)</source>
          <year>2023</year>
          <access-date>2026-01-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.w3.org/TR/WCAG22/">https://www.w3.org/TR/WCAG22/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref130">
        <label>130</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ayre</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bonner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Muscat</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Cvejic</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mac</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Mouwad</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shepherd</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Aslani</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dunn</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>McCaffery</surname>
              <given-names>KJ</given-names>
            </name>
          </person-group>
          <article-title>Online plain language tool and health information quality: a randomized clinical trial</article-title>
          <source>JAMA Netw Open</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>10</issue>
          <fpage>e2437955</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2024.37955"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.37955</pub-id>
          <pub-id pub-id-type="medline">39378036</pub-id>
          <pub-id pub-id-type="pii">2824548</pub-id>
          <pub-id pub-id-type="pmcid">PMC11581667</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref131">
        <label>131</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Petrakaki</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>User-AI intimacy in digital health</article-title>
          <source>Soc Sci Med</source>
          <year>2026</year>
          <volume>389</volume>
          <fpage>118853</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0277-9536(25)01184-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.socscimed.2025.118853</pub-id>
          <pub-id pub-id-type="medline">41453777</pub-id>
          <pub-id pub-id-type="pii">S0277-9536(25)01184-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref132">
        <label>132</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kompa</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Snoek</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Beam</surname>
              <given-names>AL</given-names>
            </name>
          </person-group>
          <article-title>Second opinion needed: communicating uncertainty in medical machine learning</article-title>
          <source>NPJ Digit Med</source>
          <year>2021</year>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>4</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-020-00367-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-020-00367-3</pub-id>
          <pub-id pub-id-type="medline">33402680</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-020-00367-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7785732</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref133">
        <label>133</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Boucher</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Harake</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Ward</surname>
              <given-names>HE</given-names>
            </name>
            <name name-style="western">
              <surname>Stoeckl</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Vargas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Minkel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Parks</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Zilca</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Artificially intelligent chatbots in digital mental health interventions: a review</article-title>
          <source>Expert Rev Med Devices</source>
          <year>2021</year>
          <volume>18</volume>
          <issue>sup1</issue>
          <fpage>37</fpage>
          <lpage>49</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.1080/17434440.2021.2013200?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/17434440.2021.2013200</pub-id>
          <pub-id pub-id-type="medline">34872429</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref134">
        <label>134</label>
        <nlm-citation citation-type="web">
          <article-title>Artificial intelligence and machine learning (AI/ML)-enabled medical devices</article-title>
          <source>U.S. Food and Drug Administration</source>
          <access-date>2026-01-20</access-date>
          <publisher-loc>Silver Spring, MD</publisher-loc>
          <publisher-name>FDA</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-and-machine-learning-aiml-enabled-medical-devices">https://www.fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-and-machine-learning-aiml-enabled-medical-devices</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref135">
        <label>135</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fossouo Tagne</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yakob</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Mcdonald</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wickramasinghe</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Linking activity theory within user-centered design: novel framework to inform design and evaluation of adverse drug reaction reporting systems in pharmacy</article-title>
          <source>JMIR Hum Factors</source>
          <year>2023</year>
          <volume>10</volume>
          <fpage>e43529</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2023//e43529/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/43529</pub-id>
          <pub-id pub-id-type="medline">36826985</pub-id>
          <pub-id pub-id-type="pii">v10i1e43529</pub-id>
          <pub-id pub-id-type="pmcid">PMC10007010</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref136">
        <label>136</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yeung-Levy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lungren</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Poon</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chaudhari</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>A systematic review and implementation guidelines of multimodal foundation models in medical imaging</article-title>
          <source>Res Sq Preprint</source>
          <year>2025</year>
          <pub-id pub-id-type="doi">10.21203/rs.3.rs-5537908/v1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref137">
        <label>137</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hackell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Alderman</surname>
              <given-names>EM</given-names>
            </name>
            <collab>COMMITTEE ON ADOLESCENCE</collab>
          </person-group>
          <article-title>Confidentiality in the care of adolescents: policy statement</article-title>
          <source>Pediatrics</source>
          <year>2024</year>
          <volume>153</volume>
          <issue>5</issue>
          <fpage>e2024066326</fpage>
          <pub-id pub-id-type="doi">10.1542/peds.2024-066326</pub-id>
          <pub-id pub-id-type="medline">38646690</pub-id>
          <pub-id pub-id-type="pii">197124</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref138">
        <label>138</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>OECD</collab>
          </person-group>
          <article-title>Artificial intelligence and competitive dynamics in downstream markets</article-title>
          <source>OECD Roundtables on Competition Policy Papers No. 331</source>
          <year>2025</year>
          <access-date>2026-03-10</access-date>
          <publisher-loc>Paris, France</publisher-loc>
          <publisher-name>OECD Publishing</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2025/11/artificial-intelligence-and-competitive-dynamics-in-downstream-markets_c6e81d0e/ccf0624a-en.pdf">https://www.oecd.org/content/dam/oecd/en/publications/reports/2025/11/artificial-intelligence-and-competitive-dynamics-in-downstream-markets_c6e81d0e/ccf0624a-en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref139">
        <label>139</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>OECD</collab>
          </person-group>
          <article-title>Regulatory sandboxes in artificial intelligence</article-title>
          <source>OECD Digital Economy Papers No. 356</source>
          <year>2023</year>
          <access-date>2026-03-10</access-date>
          <publisher-loc>Paris, France</publisher-loc>
          <publisher-name>OECD Publishing</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2023/07/regulatory-sandboxes-in-artificial-intelligence_a44aae4f/8f80a0e6-en.pdf">https://www.oecd.org/content/dam/oecd/en/publications/reports/2023/07/regulatory-sandboxes-in-artificial-intelligence_a44aae4f/8f80a0e6-en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
