<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v14i1e94813</article-id>
      <article-id pub-id-type="pmid">42013455</article-id>
      <article-id pub-id-type="doi">10.2196/94813</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>Clinical Model Autophagy: The Risk of Interpretative Drift in Recursive Medical AI</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Benis</surname>
            <given-names>Arriel</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lin</surname>
            <given-names>Kuan-Hsun</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hu</surname>
            <given-names>Bosen</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Shih</surname>
            <given-names>Pei Fan</given-names>
          </name>
          <degrees>MD</degrees>
          <address>
            <addr-line>No. 23, Ln. 110, Guanglong St.</addr-line>
            <addr-line>Bade Dist., Taoyuan City</addr-line>
            <addr-line>Taoyuan, 334</addr-line>
            <country>Taiwan</country>
            <phone>886 966285905</phone>
            <email>petershih5@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0005-3689-5568</ext-link>
        </contrib>
      </contrib-group>
      <author-notes>
        <corresp>Corresponding Author: Pei Fan Shih <email>petershih5@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>21</day>
        <month>4</month>
        <year>2026</year>
      </pub-date>
      <volume>14</volume>
      <elocation-id>e94813</elocation-id>
      <history>
        <date date-type="received">
          <day>6</day>
          <month>3</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>22</day>
          <month>3</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>24</day>
          <month>3</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>31</day>
          <month>3</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Pei Fan Shih. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 21.04.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 JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2026/1/e94813" xlink:type="simple"/>
      <abstract>
        <p>The rapid integration of large language models into electronic medical record systems introduces a critical theoretical vulnerability. Drawing on foundational computer science proofs of “model collapse,” this viewpoint introduces the concept of “Clinical Model Autophagy”—a systemic degradation of diagnostic integrity that occurs when clinical artificial intelligence (AI) models are recursively trained on unverified, AI-generated synthetic data. As these recursive models may progressively regress toward statistical means, they undergo “Interpretative Drift,” a clinically concerning phenomenon where rare pathological variances are systematically erased and complex diseases are homogenized into benign averages. To prevent the irreversible contamination of health care data ecosystems, the author urgently proposes the Data Purity Standard (DPS). The DPS mandates the cryptographic watermarking of all AI-assisted clinical entries for provenance tracking, alongside the establishment of “Human Vaults.” These physically segregated repositories of physician-verified heritage data will serve as immutable biological anchors to safely guide future AI training, ensuring the long-term reliability of digital health infrastructure.</p>
      </abstract>
      <kwd-group>
        <kwd>large language models</kwd>
        <kwd>electronic health records</kwd>
        <kwd>model collapse</kwd>
        <kwd>data governance</kwd>
        <kwd>diagnostic errors</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec>
      <title>The Impending Threat of Recursive Artificial Intelligence Training</title>
      <p>The integration of large language models (LLMs) into health care systems to draft clinical notes, summarize patient encounters, and synthesize documentation is accelerating at an unprecedented pace. While these tools offer undeniable administrative efficiencies, their unchecked deployment introduces a profound theoretical vulnerability to the medical data ecosystem [<xref ref-type="bibr" rid="ref1">1</xref>]. In computer science, recent foundational proofs have definitively established that training generative artificial intelligence (AI) on synthetic, AI-generated data inevitably leads to an irreversible statistical degradation known as “model collapse” [<xref ref-type="bibr" rid="ref2">2</xref>]. As recursive loops of generated content re-enter the training pipeline, models progressively forget the true underlying data distribution. Extrapolating this machine learning phenomenon to closed-loop electronic medical record (EMR) systems, the author posits that such a self-referential cycle poses a severe theoretical risk of triggering a phenomenon defined here as Clinical Model Autophagy—a systemic, self-consuming degradation of diagnostic integrity [<xref ref-type="bibr" rid="ref1">1</xref>]. In this viewpoint, Clinical Model Autophagy is introduced as a theoretical risk framework intended to describe how recursive synthetic exposure could degrade medical AI systems under plausible closed-loop deployment conditions.</p>
    </sec>
    <sec>
      <title>Defining the Terminology: Endogenous vs Exogenous Risks</title>
      <p>To ensure conceptual clarity, it is necessary to formally define these newly proposed terms and distinguish them from established terminology. In computer science, model collapse refers to the general statistical degradation observed when any generative AI trains on synthetic data. The author proposes the term Clinical Model Autophagy to describe the application-specific manifestation of this phenomenon within closed-loop EMR systems, highlighting the self-consuming erosion of clinical diagnostic integrity. Furthermore, Clinical Model Autophagy drives Interpretative Drift. This novel concept must be sharply distinguished from traditional concept drift or dataset shift, which occurs when the external, real-world data distribution changes over time (eg, emerging epidemiological trends). In contrast, Interpretative Drift is an endogenous, self-inflicted smoothing of data variance where the model actively erases rare pathologies despite the external real-world prevalence remaining constant. Finally, while automation bias describes a clinician's well-documented psychological tendency to over-rely on automated systems, Interpretative Drift describes the specific machine-side pathogenic mechanism that dangerously exploits this human vulnerability by generating highly fluent, yet clinically homogenized outputs.</p>
    </sec>
    <sec>
      <title>The Statistical Mechanics of Interpretative Drift</title>
      <p>The mechanism driving this impending collapse is fundamentally rooted in the statistical architecture of LLMs, which operate by optimizing for linguistic fluency and probabilistic likelihood [<xref ref-type="bibr" rid="ref3">3</xref>]. In human populations, diagnostic value is inherently concentrated at the long tails of clinical distributions, encompassing rare diseases, atypical presentations, and complex, multi-system pathophysiologies [<xref ref-type="bibr" rid="ref1">1</xref>]. However, as AI-generated EMR data permeate hospital databases and are subsequently harvested to train future iterations of clinical models, a mathematical regression to the mean is triggered. The recursive ingestion of synthetic clinical text systematically erodes these pathological tail-end variances [<xref ref-type="bibr" rid="ref4">4</xref>]. Because such models favor the most frequent and statistically expected tokens, recursive synthetic exposure may increasingly overwrite nuanced or severe clinical phenomena with homogenized language [<xref ref-type="bibr" rid="ref1">1</xref>]. Ultimately, this homogenization forces the system's representation of human physiology to regress toward generic statistical averages, actively erasing the diversity of disease and defaulting to “healthy” or “normal” archetypes [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref4">4</xref>].</p>
    </sec>
    <sec>
      <title>The Clinical Cascade: Interpretative Drift in Action</title>
      <p>The clinical consequence of this regression is a highly insidious threat this article terms as Interpretative Drift. Unlike early-generation AI failures that manifested as obvious syntactic gibberish or easily detectable language breakdown, Interpretative Drift produces outputs that maintain perfect structural and grammatical fidelity. To explain this conceptual framework, consider an illustrative thought experiment involving an oncology positron emission tomography/computed tomography report. While this specific clinical cascade remains speculative and has not yet been empirically observed at scale, it highlights the potential trajectory of interpretation errors. A future LLM, suffering from Clinical Model Autophagy, processes the imaging data and successfully extracts the correct numerical values, accurately documenting a focal lesion with an SUVmax of 12.4. However, due to Interpretative Drift, the model confidently hallucinates a benign clinical context, describing this hypermetabolic activity as normal “physiological uptake” rather than correctly identifying it as “progressive malignancy.” This subtle failure represents an insidious shift in diagnostic error paradigms. By coupling accurate numerical extraction with a hallucinatory but statistically smoothed interpretation, the model may superficially mimic professional competence, thereby attenuating the cognitive cues that would normally alert clinicians to diagnostic discrepancies [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. In time-pressured clinical environments, such false reassurance may bypass casual human review, effectively transforming high-risk pathologies into benign administrative records and creating substantial patient-safety risk that may not be readily detected during routine review.</p>
    </sec>
    <sec>
      <title>A Precautionary Governance Framework: The Data Purity Standard</title>
      <p>To prevent the irreversible contamination of our digital health infrastructure, the medical informatics community must transition immediately from passive monitoring to structural regulation. Historically, data governance in health care has been guided by established paradigms such as the FAIR (Findable, Accessible, Interoperable, and Reusable) principles, which have successfully standardized data lifecycle management for human-driven research [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. However, in the era of generative AI, these frameworks exhibit a critical blind spot: they primarily optimize for accessibility and formatting rather than cryptographic provenance. To safely train recursive clinical models, the “reusability” of EMR data must now be conditionally linked to its synthetic purity. Current regulatory frameworks for Software as a Medical Device, which primarily evaluate static algorithmic performance, are similarly ill-equipped to handle the recursive, dynamic degradation of training data [<xref ref-type="bibr" rid="ref9">9</xref>]. However, before proposing a new regulatory architecture, it is crucial to explicitly acknowledge the speculative nature of these clinical projections. While model collapse is an empirically demonstrated phenomenon in computer science, its exact timeline and manifestation in highly complex, human-in-the-loop clinical environments remain theoretical extrapolations. Nonetheless, although empirical validation of this clinical cascade remains an important next step, the mathematical plausibility and asymmetry of potential harm justify precautionary governance measures now. Accordingly, building upon established data governance foundations, the author proposes the Data Purity Standard (DPS). As a newly introduced conceptual framework, the DPS extends beyond conventional data security or privacy protocols. Rather than an immediate, rigid mandate, the author presents DPS as an exploratory governance proposal that conditionally links the future reusability of clinical data to its cryptographic provenance and human-verified origins, governing the safe deployment of generative AI in closed-loop EMR systems. The DPS asserts that the long-term safety of medical AI depends on preserving the cryptographic and biological integrity of training data [<xref ref-type="bibr" rid="ref10">10</xref>]. Consequently, DPS mandates two foundational pillars of data governance.</p>
      <p>First, DPS must require the cryptographic watermarking of all AI-assisted EMR entries [<xref ref-type="bibr" rid="ref11">11</xref>]. Drawing on emerging data provenance standards, every piece of synthetic or semisynthetic clinical text must carry an interoperable, tamper-evident digital signature [<xref ref-type="bibr" rid="ref5">5</xref>]. This cryptographic provenance ensures that future data harvesting pipelines can definitively identify and filter out AI-generated content, preventing it from being blindly reingested into subsequent model training cycles. Without mandatory, interoperable watermarking, the boundaries between human observation and machine synthesis will permanently dissolve, severely compromising the reliability of future datasets. Provenance marking alone does not establish factual correctness, but it provides the minimum traceability required to prevent synthetic content from being naively reingested as human ground truth.</p>
      <p>Second, hospitals and health care networks should establish logically segregated and access-controlled “Human Vaults” to serve as repositories of heritage data [<xref ref-type="bibr" rid="ref1">1</xref>]. To operationalize this concept, “physician-verified” ground truth must be strictly defined as finalized, legally binding clinical documentation—such as multidisciplinary tumor board summaries, finalized pathology reports, and digitally signed discharge summaries—that have explicitly bypassed generative AI assistance. These highly curated databases must be strictly isolated from all synthetic generation pipelines. Additionally, Human Vaults are not static archives; they require a dynamic curation lifecycle subject to periodic, version-controlled audits by institutional AI Data Oversight Committees. Crucially, because human-authored data are inherently susceptible to historical and cognitive biases, Vault curation must integrate rigorous demographic and clinical diversity audits. By employing statistical monitoring to identify and mitigate representation gaps [<xref ref-type="bibr" rid="ref4">4</xref>], institutions can ensure that the ground-truth data remain both cryptographically pure and clinically equitable. Ultimately, these Vaults provide a uniquely important source of high-fidelity ground-truth data for future model reset, calibration, and human-feedback alignment [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. By tethering the training of clinical LLMs exclusively to these verified Human Vaults, developers can continuously realign AI reasoning with genuine human expertise, systematically penalizing the overconfident errors characteristic of Interpretative Drift.</p>
    </sec>
    <sec>
      <title>Operationalizing DPS in Clinical Settings</title>
      <p>To ensure the translational value of DPS, its implementation must prioritize seamless integration into existing EMR workflows without exacerbating physician burnout. Operationally, the cryptographic watermarking of AI-assisted entries requires backend application programming interface-level integration rather than active clinician intervention. When an LLM generates a clinical draft, the system automatically embeds an algorithmic watermark (eg, controlled shifts in token distribution) or attaches a cryptographic metadata hash reflecting its synthetic provenance. The physician routinely reviews, edits, and signs the document; the EMR system then automatically logs the provenance metadata invisibly. Such backend API-level integration of cryptographic provenance metadata (eg, via W3C PROV standards and blockchain) has been demonstrated to enable seamless, automatic logging within existing EMR workflows with minimal clinician burden and no disruption to routine operations [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>].</p>
      <p>Furthermore, enforcing the DPS requires robust institutional governance. The author recommends the establishment of AI Data Oversight Committees within health care systems, ideally led by the Chief Medical Information Officer or Chief Data Officer. This committee would be tasked with auditing the logical segregation of the “Human Vaults.” By enforcing strict access controls, the committee ensures that only cryptographically pure, legacy human-authored data—or EMRs explicitly cleared of synthetic contamination—are used for future closed-loop model fine-tuning or local Reinforcement Learning from Human Feedback processes [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. This governance structure effectively shifts the burden of data purity from the individual frontline clinician to the institutional infrastructure.</p>
    </sec>
    <sec>
      <title>Implementation Challenges, Unintended Consequences, and Alternative Approaches</title>
      <p>While the theoretical necessity of the DPS and Human Vaults is compelling, framing them as exploratory proposals requires acknowledging significant implementation hurdles and clinical trade-offs. First, retrofitting legacy EMR systems to support cryptographic watermarking and automated provenance tracking requires substantial upfront financial and technical investment. Achieving this across fragmented, heterogeneous health care IT ecosystems pose severe interoperability challenges [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Second, there is an inherent trade-off between data volume and data purity; strictly filtering out AI-assisted entries to populate the Human Vaults will inevitably restrict the sheer volume of data available for future algorithm training. Furthermore, curating these Vaults carries the risk of unintended consequences. Because legacy human-authored data are inherently susceptible to historical prejudices, strictly isolating these data could inadvertently institutionalize and amplify existing health disparities. To mitigate this risk, rigorous demographic auditing must be mandatory. Additionally, maintaining the integrity of these Vaults requires continuous vigilance to ensure that “physician verification” does not devolve into a superficial rubber-stamping exercise driven by time-pressured clinical workflows. Finally, the DPS should not be viewed as a monolithic solution. It must be contextualized alongside alternative or complementary governance approaches such as federated learning across verified institutional nodes or continuous human-in-the-loop semantic auditing. Ultimately, transitioning toward provenance-aware medical AI will require a multifaceted ecosystem of policies, of which the DPS represents a foundational, yet evolving, conceptual cornerstone.</p>
    </sec>
    <sec>
      <title>Ethical Considerations</title>
      <p>This is a theoretical paper and does not involve human participants, animal subjects, or identifiable patient data. Consequently, under standard regulatory guidelines (Taiwan’s Human Subjects Research Act [<xref ref-type="bibr" rid="ref19">19</xref>]), this study is exempt from institutional review board approval and informed consent requirements.</p>
    </sec>
    <sec>
      <title>Conclusion</title>
      <p>The unchecked deployment of generative AI in health care is not merely a technological upgrade—it represents an epistemological intervention that threatens to reshape the informational basis of the medical record. If left unaddressed, this shift could compromise not only downstream model training but also the evidentiary integrity of routine clinical documentation, quality assurance systems, and retrospective research databases. Without structural firewalls, recursive loops of clinical model autophagy may progressively erode diagnostic reliability, replacing clinical nuance with an increasingly homogenized synthetic record (<xref rid="figure1" ref-type="fig">Figure 1</xref>). </p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>Mechanistic framework of clinical model autophagy and the data purity standard. (A) The vicious cycle of Clinical Model Autophagy. When artificial intelligence (AI)-generated electronic medical records (synthetic EMRs) are recursively fed back into subsequent training pipelines without provenance controls, the system may regress toward statistical means. This process can silently erode rare pathological variance, driving “Interpretative Drift,” in which complex diseases are progressively homogenized into benign averages. (B) The regulatory firewall via the Data Purity Standard (DPS). To interrupt this cycle, cryptographic watermarking functions as a provenance filter that allows AI-assisted entries to be identified and excluded from future training pools. Concurrently, logically segregated and access-controlled “Human Vaults”—containing exclusively physician-authored and verified clinical records—serve as immutable reference anchors for safe Reinforcement Learning from Human Feedback and help reduce the risk of model collapse. LLM: large language model.</p>
        </caption>
        <graphic xlink:href="medinform_v14i1e94813_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
  </body>
  <back>
    <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">DPS</term>
          <def>
            <p>Data Purity Standard</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FAIR</term>
          <def>
            <p>Findable, Accessible, Interoperable, and Reusable</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>In accordance with journal guidelines, generative artificial intelligence tools were used solely for language polishing, stylistic editing, and figure generation (ChatGPT DALL-E 3, OpenAI). The author assumes full responsibility for the content and originality of the manuscript.</p>
    </ack>
    <notes>
      <title>Funding</title>
      <p>This research received no external grant from any funding agency in the public, commercial, or not-for-profit sectors. The author conducted this work independently.</p>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>PFS is the sole author of this manuscript. PFS conceptualized the theoretical framework, coined the terms “Clinical Model Autophagy” and “Interpretative Drift,” designed the proposed Data Purity Standard (DPS) and Human Vault regulatory concepts, and drafted the manuscript.</p>
        <p>The author PFS is currently not affiliated with any institution, but is an Independent Researcher.</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>He</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xiang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>AI-generated data contamination erodes pathological variability and diagnostic reliability</article-title>
          <source>medRxiv. Preprint posted online on February 2, 2026</source>
          <pub-id pub-id-type="doi">10.64898/2026.01.19.26344383</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>Shumailov</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Shumaylov</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Papernot</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gal</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>AI models collapse when trained on recursively generated data</article-title>
          <source>Nature</source>
          <year>2024</year>
          <month>07</month>
          <volume>631</volume>
          <issue>8022</issue>
          <fpage>755</fpage>
          <lpage>759</lpage>
          <pub-id pub-id-type="doi">10.1038/s41586-024-07566-y</pub-id>
          <pub-id pub-id-type="medline">39048682</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-024-07566-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC11269175</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Generative AI in writing research papers: a new type of algorithmic bias and uncertainty in scholarly work</article-title>
          <source>Intelligent Systems and Applications</source>
          <year>2024</year>
          <month>07</month>
          <day>31</day>
          <publisher-loc>Switzerland</publisher-loc>
          <publisher-name>Springer Nature</publisher-name>
          <fpage>656</fpage>
          <lpage>669</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>Y</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>A survey of recent methods for addressing AI fairness and bias in biomedicine</article-title>
          <source>J Biomed Inform</source>
          <year>2024</year>
          <month>06</month>
          <volume>154</volume>
          <fpage>104646</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(24)00064-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2024.104646</pub-id>
          <pub-id pub-id-type="medline">38677633</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(24)00064-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC11129918</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mahajan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Improving authenticity and provenance in digital biomarkers: the case for digital watermarking</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <month>01</month>
          <day>15</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-024-01374-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-024-01374-4</pub-id>
          <pub-id pub-id-type="medline">39814830</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-024-01374-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC11736138</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Dumontier</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aalbersberg</surname>
              <given-names>IJ</given-names>
            </name>
            <name name-style="western">
              <surname>Appleton</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Axton</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baak</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Blomberg</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Boiten</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva Santos</surname>
              <given-names>LB</given-names>
            </name>
            <name name-style="western">
              <surname>Bourne</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Brookes</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Crosas</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dillo</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Dumon</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Edmunds</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Evelo</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Finkers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez-Beltran</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Groth</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Grethe</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Heringa</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>'t Hoen</surname>
              <given-names>Peter A C</given-names>
            </name>
            <name name-style="western">
              <surname>Hooft</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lusher</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Martone</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Packer</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Persson</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Rocca-Serra</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Roos</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van Schaik</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sansone</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schultes</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sengstag</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Slater</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Strawn</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Swertz</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>van der Lei</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>van Mulligen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Velterop</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Waagmeester</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wittenburg</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wolstencroft</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The FAIR Guiding Principles for scientific data management and stewardship</article-title>
          <source>Sci Data</source>
          <year>2016</year>
          <month>03</month>
          <day>15</day>
          <volume>3</volume>
          <fpage>160018</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/sdata.2016.18"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/sdata.2016.18</pub-id>
          <pub-id pub-id-type="medline">26978244</pub-id>
          <pub-id pub-id-type="pii">sdata201618</pub-id>
          <pub-id pub-id-type="pmcid">PMC4792175</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Inau</surname>
              <given-names>ET</given-names>
            </name>
            <name name-style="western">
              <surname>Sack</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Waltemath</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zeleke</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>Initiatives, concepts, and implementation practices of the findable, accessible, interoperable, and reusable data principles in health data stewardship: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <month>08</month>
          <day>28</day>
          <volume>25</volume>
          <fpage>e45013</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e45013/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/45013</pub-id>
          <pub-id pub-id-type="medline">37639292</pub-id>
          <pub-id pub-id-type="pii">v25i1e45013</pub-id>
          <pub-id pub-id-type="pmcid">PMC10495848</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Martínez-García</surname>
              <given-names>Alicia</given-names>
            </name>
            <name name-style="western">
              <surname>Alvarez-Romero</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Román-Villarán</surname>
              <given-names>Esther</given-names>
            </name>
            <name name-style="western">
              <surname>Bernabeu-Wittel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Luis Parra-Calderón</surname>
              <given-names>Carlos</given-names>
            </name>
          </person-group>
          <article-title>FAIR principles to improve the impact on health research management outcomes</article-title>
          <source>Heliyon</source>
          <year>2023</year>
          <month>05</month>
          <volume>9</volume>
          <issue>5</issue>
          <fpage>e15733</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2405-8440(23)02940-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.heliyon.2023.e15733</pub-id>
          <pub-id pub-id-type="medline">37205991</pub-id>
          <pub-id pub-id-type="pii">S2405-8440(23)02940-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC10189186</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gilbert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fenech</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hirsch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Upadhyay</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Biasiucci</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Starlinger</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Algorithm change protocols in the regulation of adaptive machine learning-based medical devices</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>10</month>
          <day>26</day>
          <volume>23</volume>
          <issue>10</issue>
          <fpage>e30545</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/10/e30545/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/30545</pub-id>
          <pub-id pub-id-type="medline">34697010</pub-id>
          <pub-id pub-id-type="pii">v23i10e30545</pub-id>
          <pub-id pub-id-type="pmcid">PMC8579211</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guillen-Aguinaga</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aguinaga-Ontoso</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Guillen-Aguinaga</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Guillen-Grima</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Aguinaga-Ontoso</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Data quality in the age of AI: a review of governance, ethics, and the FAIR principles</article-title>
          <source>Data</source>
          <year>2025</year>
          <month>12</month>
          <day>04</day>
          <volume>10</volume>
          <issue>12</issue>
          <fpage>201</fpage>
          <pub-id pub-id-type="doi">10.3390/data10120201</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kirchenbauer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Geiping</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Katz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Miers</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Goldstein</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>A watermark for large language models</article-title>
          <source>ArXiv. Preprint posted online on May 1, 2024</source>
          <pub-id pub-id-type="doi">10.48550/ARXIV.2301.10226</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kita</surname>
              <given-names>FJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rao</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Kirigiti</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <article-title>Innovative synthetic EHR data generation: diffusion models for enhanced privacy and clinical utility in multimorbidity clustering</article-title>
          <source>Connection Science</source>
          <year>2025</year>
          <month>10</month>
          <day>06</day>
          <volume>37</volume>
          <issue>1</issue>
          <fpage>2565163</fpage>
          <pub-id pub-id-type="doi">10.1080/09540091.2025.2565163</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Margheri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Masi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Miladi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sassone</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenzweig</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Decentralised provenance for healthcare data</article-title>
          <source>Int J Med Inform</source>
          <year>2020</year>
          <month>09</month>
          <volume>141</volume>
          <fpage>104197</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2020.104197</pub-id>
          <pub-id pub-id-type="medline">32540775</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(19)31203-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dar</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Helfert</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Data provenance in healthcare: approaches, challenges, and future directions</article-title>
          <source>Sensors (Basel)</source>
          <year>2023</year>
          <month>07</month>
          <day>18</day>
          <volume>23</volume>
          <issue>14</issue>
          <fpage>6495</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s23146495"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s23146495</pub-id>
          <pub-id pub-id-type="medline">37514788</pub-id>
          <pub-id pub-id-type="pii">s23146495</pub-id>
          <pub-id pub-id-type="pmcid">PMC10384601</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Freeman</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Magrabi</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Governance for safe and responsible AI in healthcare organisations: a scoping review of frameworks</article-title>
          <source>Research Square. Preprint posted online on September 10, 2025</source>
          <pub-id pub-id-type="doi">10.21203/rs.3.rs-7209096/v1</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>Kim</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Hasan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kueper</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hayes</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fine</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Balu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sendak</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Establishing organizational AI governance in healthcare: a case study in Canada</article-title>
          <source>NPJ Digit Med</source>
          <year>2025</year>
          <month>08</month>
          <day>15</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>522</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-025-01909-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-025-01909-3</pub-id>
          <pub-id pub-id-type="medline">40817280</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41746-025-01909-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC12356831</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Twenty-five years of evolution and hurdles in electronic health records and interoperability in medical research: comprehensive review</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <month>01</month>
          <day>09</day>
          <volume>27</volume>
          <fpage>e59024</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e59024/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/59024</pub-id>
          <pub-id pub-id-type="medline">39787599</pub-id>
          <pub-id pub-id-type="pii">v27i1e59024</pub-id>
          <pub-id pub-id-type="pmcid">PMC11757985</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holmes</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Beinlich</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Boland</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Bowles</surname>
              <given-names>KH</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>TS</given-names>
            </name>
            <name name-style="western">
              <surname>Demiris</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Draugelis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fluharty</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gabriel</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Grundmeier</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Herman</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Himes</surname>
              <given-names>BE</given-names>
            </name>
            <name name-style="western">
              <surname>Hubbard</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Kahn</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Koppel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Long</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Mirkovic</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Mowery</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Ritchie</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Urbanowicz</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Why is the electronic health record so challenging for research and clinical care?</article-title>
          <source>Methods Inf Med</source>
          <year>2021</year>
          <month>05</month>
          <volume>60</volume>
          <issue>1-02</issue>
          <fpage>32</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34282602"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0041-1731784</pub-id>
          <pub-id pub-id-type="medline">34282602</pub-id>
          <pub-id pub-id-type="pmcid">PMC9295893</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <source>Taiwan’s Human Subjects Research Act</source>
          <access-date>2026-04-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://law.moj.gov.tw/ENG/LawClass/LawAll.aspx?pcode=L0020176">https://law.moj.gov.tw/ENG/LawClass/LawAll.aspx?pcode=L0020176</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
