<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Meta and Res Int</journal-id>
      <journal-title>JMIR Metascience and Research Integrity</journal-title>
      <issn pub-type="epub">XXXX-XXXX</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">v1i1e106068</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/106068</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>From AI Disclosure to Judgment Traceability: Addressing Research Waste in AI-Assisted Health Sciences Publishing</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Brini</surname>
            <given-names>Stefano</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Barrett</surname>
            <given-names>D</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Omar</surname>
            <given-names>Usama</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Hsieh</surname>
            <given-names>Tino</given-names>
          </name>
          <degrees>MSN</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>School of Nursing</institution>
            <institution>National Yang Ming Chiao Tung University</institution>
            <addr-line>No 155, Section 2, Linong Street</addr-line>
            <addr-line>Taipei, 112</addr-line>
            <country>Taiwan</country>
            <phone>886 966 737 862</phone>
            <email>t22671884@gmail.com</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0008-8590-4231</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>Ya-Ting</given-names>
          </name>
          <degrees>BSN</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-3371-4066</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>School of Nursing</institution>
        <institution>National Yang Ming Chiao Tung University</institution>
        <addr-line>Taipei</addr-line>
        <country>Taiwan</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Emergency Medicine</institution>
        <institution>National Taiwan University Hospital</institution>
        <addr-line>Taipei</addr-line>
        <country>Taiwan</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Tino Hsieh <email>t22671884@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>19</day>
        <month>10</month>
        <year>2026</year>
      </pub-date>
      <volume>1</volume>
      <elocation-id>e106068</elocation-id>
      <history>
        <date date-type="received">
          <day>2</day>
          <month>7</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>22</day>
          <month>7</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>26</day>
          <month>9</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>2</day>
          <month>10</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Tino Hsieh, Ya-Ting Chen. Originally published in the JMIR Metascience and Research Integrity (https://metascience.jmir.org), 19.10.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 Metascience and Research Integrity, is properly cited. The complete bibliographic information, a link to the original publication on https://metascience.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://metascience.jmir.org/2026/1/e106068" xlink:type="simple"/>
      <abstract>
        <p>Generative artificial intelligence (GAI) is changing how health sciences manuscripts are produced, revised, and evaluated. Publication guidance emphasizes necessary safeguards, such as disclosure, authorship, confidentiality, transparency, verification, and human responsibility, for AI-assisted content. However, disclosure alone does not establish whether consequential claims in a manuscript are grounded in accountable authorial and domain judgment. This viewpoint addresses this governance gap. We define expression-rich but judgment-thin scholarship as AI-amplified scholarly output in which linguistic fluency, structural coherence, and surface plausibility exceed the traceability of the reasoning, evidence interpretation, uncertainty, contextual limits, and responsibility behind major claims. We frame AI-induced research waste as a conceptual extension of the established research waste literature rather than as a measured prevalence claim. The concern is not that AI-assisted writing is inherently low quality; rather, GAI can make it easier to produce large volumes of polished text whose underlying judgments may be weakly supported, insufficiently limited, or difficult to defend. Building on emerging work on claim accountability, provenance, responsible AI-assisted writing, and publication ethics, we propose domain judgment traceability as a claim-centered governance approach for health sciences publishing. The framework asks whether major clinical, methodological, statistical, ethical, policy, and implementation claims can be traced to an appropriate evidence base, an identifiable interpretive step, explicit uncertainty, population and setting limits, equity and harm considerations, proportionate recommendation strength, and accountable human authorship. This approach shifts the unit of governance from the AI tool or prompt to the major scholarly claim. It also distinguishes disclosure from defensibility: disclosure describes whether and how AI contributed to manuscript development, whereas judgment traceability examines whether the resulting claim can be reconstructed, challenged, and defended by responsible authors. We propose practical implications for authors, reviewers, editors, and journals, including claim-level verification, proportionate requests for clarification, and selective piloting of traceability prompts rather than routine AI detection or exhaustive prompt surveillance. We also identify safeguards against gatekeeping, including attention to language equity, reviewer subjectivity, and the risk of conflating linguistic polish with scholarly competence. Domain judgment traceability is presented as a provisional conceptual governance aid, not a validated scoring instrument or reporting guideline. Its purpose is to complement—not replace—existing disclosure policies and reporting standards by making accountable judgment more visible where claims may influence clinical care, research interpretation, policy, implementation, or public trust. The framework creates an empirical agenda: future studies can test whether claim-centered prompts improve reviewer agreement, citation accuracy, proportionality between evidence and recommendations, author experience, and editorial usefulness without imposing an excessive documentation burden. The goal is not to reject AI-assisted scholarship or require disclosure of every prompt but to ensure that increasingly scalable scholarly expression is proportionate, defensible, context sensitive, and answerable to human judgment in health sciences publishing.</p>
      </abstract>
      <kwd-group>
        <kwd>generative artificial intelligence</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>AI</kwd>
        <kwd>health sciences publishing</kwd>
        <kwd>research integrity</kwd>
        <kwd>metascience</kwd>
        <kwd>scientific publishing</kwd>
        <kwd>research waste</kwd>
        <kwd>domain judgment</kwd>
        <kwd>publication ethics</kwd>
        <kwd>AI disclosure</kwd>
        <kwd>scholarly communication</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec>
      <title>Background</title>
      <p>Generative AI (GAI) has rapidly entered scholarly writing, with large-scale lexical analysis suggesting detectable traces of large language model (LLM)–assisted writing in biomedical abstracts [<xref ref-type="bibr" rid="ref1">1</xref>]. In health sciences publishing, AI-assisted tools may be used to organize manuscripts, improve clarity, support literature navigation, identify possible omissions, and reduce language-related barriers for authors who work in an English-dominant publication environment [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. These uses are not inherently problematic; peer-reviewed commentary has emphasized both potential productivity and accessibility benefits of GAI and the need for transparent, verifiable human oversight [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. The research integrity concern is therefore more specific than AI use itself: fluent and well-structured AI-assisted prose may make a manuscript appear complete without showing whether its major claims are accurate, proportionate to the evidence, contextually limited, and defensible by responsible authors [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      <p>Current publishing guidance has therefore focused on disclosure, authorship, confidentiality, transparency, verification, and human responsibility. Peer-reviewed guidance and policy analyses consistently state that AI systems cannot assume authorship responsibility and that human authors remain accountable for the accuracy, integrity, and transparency of the final work [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Policy analyses also show substantial heterogeneity across journals and publishers in allowable uses, disclosure expectations, and required descriptions of human oversight [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. This heterogeneity matters because a disclosure statement may document the presence of AI without revealing whether an author has verified the evidence, reconstructed the reasoning behind a consequential claim, or calibrated the strength of a recommendation. The emerging literature therefore increasingly distinguishes procedural transparency from substantive accountability [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      <p>Building on emerging arguments that responsible AI governance should move beyond tool disclosure toward accountability for scholarly claims [<xref ref-type="bibr" rid="ref7">7</xref>], this viewpoint asks what claim accountability requires in health sciences publishing. It defines expression-rich but judgment-thin scholarship, distinguishes it from adjacent research integrity problems, and proposes domain judgment traceability as a claim-centered governance approach for AI-assisted health sciences manuscripts. The intended audience includes journal editors and reviewers, health sciences authors, publication ethics committees, research integrity officers, and institutions developing AI use policies. Although the argument is especially relevant to clinically oriented manuscripts, it applies more broadly to public health, health informatics, health services research, implementation science, epidemiology, policy research, qualitative inquiry, and biomedical scholarship. Clinical judgment traceability is therefore treated as one important subtype within the broader concept of domain judgment traceability. This formulation is consistent with recent peer-reviewed arguments that responsible governance should preserve provenance, verification, and identifiable human responsibility rather than treating disclosure or prohibition as sufficient ends in themselves [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      <p>This viewpoint does not claim that AI-assisted writing is inherently defective or that disclosure policies are unimportant. Instead, it identifies a narrower governance gap. Disclosure documents whether and how a tool contributed to manuscript preparation; judgment traceability asks whether the resulting claims are sufficiently supported, limited, and accountable. This distinction allows the manuscript to engage AI-related risks while preserving a balanced position toward legitimate AI-assisted language, organization, and revision support [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Its primary contribution is to operationalize emerging claim accountability arguments for health sciences publishing through domain judgment traceability: a way of asking whether major scholarly claims remain connected to evidence, interpretation, uncertainty, context, and accountable authorship [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. The framing deliberately avoids the stronger assertion that judgment traceability has already been empirically shown to reduce research waste. Instead, it treats judgment traceability as a provisional governance aid whose usefulness, burden, fairness, and effects on editorial decision-making require empirical evaluation [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
    </sec>
    <sec>
      <title>Ethics Approval and Informed Consent</title>
      <p>Ethics approval and informed consent were not applicable because this viewpoint did not involve human participants, personal data, or identifiable clinical information.</p>
    </sec>
    <sec>
      <title>Why Disclosure Is Necessary but Insufficient</title>
      <p>Disclosure is a necessary part of responsible AI-assisted publishing because it informs editors, reviewers, and readers that a nonhuman system contributed to manuscript development. Peer-reviewed guidance increasingly recommends disclosures that specify not only the tool but also the task, extent of assistance, verification process, and location of AI-supported work [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Frameworks such as GAIDeT (Generative Artificial Intelligence Delegation Taxonomy) further provide structured language for documenting which research or writing tasks were delegated to GAI while preserving human oversight [<xref ref-type="bibr" rid="ref16">16</xref>]. These approaches strengthen transparency because “AI was used” can otherwise conceal materially different practices, ranging from grammar correction to literature summarization, conceptual brainstorming, data analysis, or recommendation drafting. However, disclosure is a description of process rather than a direct test of claim quality. A manuscript may transparently disclose AI use and still contain overextended interpretations, unsupported clinical implications, fabricated or erroneous citations, or recommendations whose strength exceeds the underlying evidence [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. Conversely, AI may be used for language editing, organization, or perspective checking, while authors preserve rigorous source interpretation, contextual limits, and responsibility for every substantive claim [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>This focus on claim quality addresses a practical weakness of tool-centered governance. A disclosure statement can be accurate yet uninformative about whether a recommendation is justified by the cited evidence. For example, an author may disclose AI-assisted drafting or summarization but still fail to show why a limited observational finding warrants a broad clinical implication; conversely, an author may use AI to improve readability while maintaining rigorous source interpretation and cautious recommendations [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. A citation should therefore not merely appear relevant: the cited source should directly support the claim attributed to it, and authors should be able to explain how the evidence justifies the level of inference or recommendation being made. This distinction is particularly important because disclosure practices remain heterogeneous across journals, disciplines, and publishers [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Some policies request only the name of a tool, whereas others ask authors to describe the task, location of use, or degree of human verification [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Disclosure can support transparency, but it remains procedural unless connected to the claims the manuscript asks readers to accept. A claim-centered standard therefore complements rather than competes with disclosure by asking whether consequential interpretations and recommendations remain attributable to responsible human judgment [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
    </sec>
    <sec>
      <title>Expression-Rich but Judgment-Thin Scholarship</title>
      <p>Expression-rich but judgment-thin scholarship is defined as scholarly work in which the language, structure, and apparent completeness of a manuscript exceed the traceability of the judgment supporting its major claims. The concept does not refer simply to poor writing, weak scholarship, or the use of GAI. Rather, it identifies a mismatch between scholarly expression and accountable reasoning: a manuscript may read as fluent, balanced, clinically relevant, and well organized while leaving unclear how its central claims were framed, interpreted, limited, and made defensible by responsible authors. This concern is compatible with broader warnings that GAI can create persuasive or seemingly authoritative outputs without reliable epistemic grounding and that apparent fluency should not be mistaken for understanding [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. It also aligns with recent claim accountability and provenance arguments that the central governance question is whether a human can reconstruct and defend the reasoning, evidence, and verification behind what enters the scholarly record [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
      <p>Judgment thinness is best understood as a property of the relationship among text, authorial process, and claims. A manuscript can be judgment thin without AI because conventional academic writing can also be formulaic, overgeneralized, densely cited but poorly interpreted, or disconnected from clinical and methodological realities. A manuscript can also be AI assisted and judgment rich if authors use AI to improve expression, identify missing perspectives, challenge assumptions, or organize reasoning while retaining responsibility for the final claims [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. AI may amplify judgment thinness, not because it uniquely causes weak reasoning, but because it can increase the speed and scale at which plausible scholarly text is produced and can make weakly examined reasoning appear polished enough to pass superficial review. The risk is therefore not the presence of machine-generated language itself; it is the possibility that fluency masks unresolved evidentiary, methodological, or contextual problems that responsible authors have not adequately examined [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref19">19</xref>].</p>
      <p>This concept overlaps with, but is not reducible to, several existing concerns. Hallucination concerns fabricated or inaccurate content, paper mill production concerns fraudulent or industrialized paper generation, automation bias concerns overreliance on machine output [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>], and epistemic opacity concerns difficulty understanding how algorithmic systems produce outputs [<xref ref-type="bibr" rid="ref23">23</xref>]. Paper mills represent a documented threat to research integrity [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>], and work on AI in science has warned that AI systems may produce illusions of understanding [<xref ref-type="bibr" rid="ref6">6</xref>]. Concerns about fluent but ungrounded language model output, including the “stochastic parrots” critique, are relevant background but do not by themselves define the claim-level failure mode addressed here [<xref ref-type="bibr" rid="ref20">20</xref>]. Judgment thinness specifically concerns whether the reasoning behind major claims is visible, proportionate, and defensible.</p>
      <p>We propose several observable warning signs that may prompt closer review: broad clinical or policy implications that exceed the evidence cited; generic recommendations that do not specify population, setting, resource, or equity limits; literature summaries that list findings without interpreting their strength or relevance; conclusions that convert limited evidence into action-oriented recommendations without explaining inferential steps; citations that exist but do not support the sentence in which they are placed; and statements that appear authoritative but cannot be defended by a responsible author when challenged [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. These features should prompt clarification of claim-to-evidence reasoning, not accusations of AI use. They are intentionally framed as review prompts rather than diagnostic criteria because AI detection tools have documented limitations and may produce inequitable misclassification, including for nonnative English writers [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Nor should the prompts penalize concise writing. Their purpose is to identify where a manuscript may require clearer explanation of evidence strength, inferential steps, contextual limits, or authorial responsibility. In this sense, judgment traceability functions as a quality and accountability standard rather than an AI detection strategy [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
    </sec>
    <sec>
      <title>From Research Waste to AI-Induced Research Waste</title>
      <p>Research waste is commonly discussed in relation to the production, conduct, reporting, dissemination, and usability of empirical research [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. In health sciences, this framing has ethical as well as economic significance because low-value research can consume participant contributions, public funding, institutional resources, reviewer labor, editorial attention, and reader trust. Contemporary research integrity literature also documents how fraudulent publication systems and paper mills can introduce large volumes of unreliable work into the scholarly record and create downstream burdens for journals and evidence synthesis [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. This literature provides the conceptual foundation for asking whether AI-assisted scholarly production may create an additional pathway to low-value output while also requiring caution: AI-induced research waste is proposed here as a conceptual extension, not as a measured prevalence claim.</p>
      <p>Empirical evidence supports the plausibility of this concern without proving its prevalence. Large-scale lexical analysis suggests detectable traces of LLM-assisted writing in biomedical abstracts [<xref ref-type="bibr" rid="ref1">1</xref>]. Separate studies demonstrate risks, including fraudulent-looking AI-generated medical manuscripts, fabricated or erroneous AI-generated citations, and citation errors that can appear bibliographically plausible [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. These findings do not show that AI-assisted manuscripts are inherently lower quality or judgment thin. They do show why authors, reviewers, and editors cannot rely on surface fluency, citation density, or procedural disclosure alone when evaluating whether a manuscript’s claims add proportionate knowledge value. The problem is compounded when unreliable material enters later scholarship: empirical work on paper mill contamination has shown that retracted fraudulent papers can be incorporated into systematic reviews and continue to be cited even after retraction [<xref ref-type="bibr" rid="ref30">30</xref>]. Although paper mills and AI-assisted writing are distinct phenomena, both illustrate why scholarly systems need safeguards that evaluate the integrity of the claim-source relationship rather than only the appearance of a completed manuscript [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p>
      <p>On this basis, AI-induced research waste should be understood as a possible pathway by which AI-assisted scholarly outputs consume attention without adding proportionate epistemic, clinical, methodological, or social value. The concern includes obvious problems, such as fabricated references and unreliable summaries, but it also includes a subtler failure: manuscripts that are fluent and rhetorically complete yet leave reviewers and readers to reconstruct missing judgment behind their major claims [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. This formulation is intended to prevent overclaiming. The available empirical evidence supports component risks (detectable AI-assisted writing, fabricated or erroneous citations, fraudulent-looking text, detector bias, automation-related overreliance, and broader threats to provenance), but it does not measure the prevalence of judgment-thin scholarship as an empirical category [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. The proposed contribution is therefore conceptual and governance-oriented: it names a failure mode that may become more scalable under AI-assisted writing conditions and specifies what would need to be visible for major claims to remain accountable. This emphasis also avoids equating productivity with value; the ethical concern is not that AI makes writing faster but that increased output can become wasteful when the additional text does not carry commensurate evidentiary or interpretive value [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>].</p>
    </sec>
    <sec>
      <title>From Clinical Judgment to Domain Judgment Traceability</title>
      <p>Because health sciences publishing includes diverse forms of inquiry, clinical judgment traceability should not be treated as the only relevant standard. Evidence-based practice has long emphasized that clinical decisions require integration of the best-available evidence, professional expertise, and patient values [<xref ref-type="bibr" rid="ref32">32</xref>]. Yet, manuscripts in public health, epidemiology, implementation science, health informatics, qualitative inquiry, health services research, policy research, and biomedical science may not make direct clinical recommendations while still depending on domain-specific judgment. Recent discussions of claim accountability and provenance similarly emphasize that the defensibility of scholarly claims depends on identifiable human responsibility for evidence selection, interpretation, and verification regardless of discipline [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. For this reason, this viewpoint uses domain judgment traceability as the broader governance concept.</p>
      <p>Domain judgment traceability refers to the ability of readers, reviewers, and editors to identify how responsible authors interpreted evidence, handled uncertainty, considered context, and justified the level of claim being made. Clinical judgment traceability is one subtype that becomes especially important when a manuscript makes claims about patient care, professional practice, clinical workflow, health system operations, or policy decisions with foreseeable implications for care. Other forms include methodological, statistical, ethical, policy, and implementation judgment. Judgment types describe the substantive domains in which authors exercise judgment, whereas the traceability domains in <xref ref-type="table" rid="table1">Table 1</xref> describe what must be made visible for a major claim to remain accountable. Where prior claim accountability work establishes that a named human must be able to reconstruct and defend each scholarly claim [<xref ref-type="bibr" rid="ref7">7</xref>], domain judgment traceability specifies what should be visible for that defense in health sciences manuscripts: the evidence base, author interpretation, uncertainty, population and setting context, equity and harms, recommendation strength, and accountable authorship. Its additional contribution is to connect those elements to health sciences–specific concerns about research waste; transferability; patient or population consequences; and the proportionality of clinical, policy, and implementation recommendations. This approach extends rather than replaces existing publication ethics expectations and reporting standards [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. The CONSORT-AI (Consolidated Standards of Reporting Trials–Artificial Intelligence) extension and DECIDE-AI (Developmental and Exploratory Clinical Investigation of Decision Support Systems Driven by Artificial Intelligence), for example, emphasize intended use, clinical setting, human-AI interaction, input and output handling, implementation context, and safety evaluation [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. Judgment traceability is not proposed as a replacement reporting guideline; rather, these reporting concerns illustrate why claims about AI-supported care, workflow, risk prediction, or implementation should make the evidence base, setting, uncertainty, harms, and level of action justified visible.</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Proposed claim-centered framework for domain judgment traceability in AI-assisted health sciences manuscripts.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="200"/>
          <col width="270"/>
          <col width="260"/>
          <col width="270"/>
          <thead>
            <tr valign="top">
              <td>Traceability domain</td>
              <td>What authors should make visible</td>
              <td>Potential failure mode</td>
              <td>Example of adequate traceability</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>Evidence base</td>
              <td>Studies, guidance, data, or conceptual sources supporting the claim</td>
              <td>Sources are cited but not interpreted; weak evidence supports strong claims.</td>
              <td>The recommendation is based on two observational studies and should be interpreted cautiously.</td>
            </tr>
            <tr valign="top">
              <td>Author interpretation</td>
              <td>How responsible authors moved from evidence to meaning and why the claim follows</td>
              <td>Findings are listed or paraphrased without an identifiable inferential step.</td>
              <td>We interpret these findings as relevant to workflow redesign because the observed effect concerns response timing while recognizing that alternative explanations remain possible.</td>
            </tr>
            <tr valign="top">
              <td>Uncertainty</td>
              <td>What remains uncertain, including limitations, competing explanations, and confidence in the inference</td>
              <td>The manuscript presents a qualified finding as settled or omits material uncertainty.</td>
              <td>The direction of effect is consistent, but uncertainty remains because evidence is heterogeneous and external validation is limited.</td>
            </tr>
            <tr valign="top">
              <td>Population, setting, and context</td>
              <td>Who the claim applies to, where it applies, and under what resource or workflow conditions</td>
              <td>A narrow finding is generalized to all patients, settings, or systems.</td>
              <td>These implications apply primarily to adult EDs<sup>a</sup> with integrated electronic health record alert systems and defined response protocols.</td>
            </tr>
            <tr valign="top">
              <td>Equity and harms</td>
              <td>Potential differential effects, exclusions, burdens, or unintended consequences</td>
              <td>The manuscript assumes equal benefit across groups or ignores possible harms.</td>
              <td>Performance should be assessed across relevant demographic, clinical, language, and access-related subgroups, when appropriate.</td>
            </tr>
            <tr valign="top">
              <td>Recommendation strength</td>
              <td>Whether the recommended action is proportionate to the strength, consistency, and applicability of the evidence</td>
              <td>A tentative implication is written as a universal implementation mandate.</td>
              <td>Current evidence supports further evaluation in appropriately resourced settings, not immediate universal adoption.</td>
            </tr>
            <tr valign="top">
              <td>Accountable authorship and AI assistance</td>
              <td>Which authors are responsible for interpretation and recommendation; whether AI materially supported major claims; and how relevant outputs were checked</td>
              <td>Responsibility is diffused into passive wording or AI-generated generality.</td>
              <td>AI assisted drafting of this section; the authors checked the cited sources, revised the inference, and accept responsibility for the final recommendation.</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>ED: emergency department.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>Different forms of domain judgment require different forms of traceability. Clinical judgment concerns whether claims about care, risk, diagnosis, treatment, triage, monitoring, or professional action are appropriate for the relevant population and setting. Methodological judgment concerns whether the study design, sampling, measurement, comparison, and interpretation are aligned with the question being asked. Statistical judgment concerns whether analytic choices, uncertainty, effect estimates, assumptions, and limitations are interpreted proportionately. Ethical judgment concerns whether benefits, burdens, risks, consent, privacy, equity, and potential harms are adequately considered. For the purposes of the framework proposed here, policy and implementation claims should additionally make feasibility, stakeholders, resources, workflows, workforce capacity, and unintended consequences visible rather than presenting these considerations as if they were automatically established by a generic AI reporting standard. The framework is therefore not restricted to bedside clinical decisions: A statistical claim may require traceability of analytic assumptions and uncertainty; an implementation claim may require traceability of staffing, infrastructure, and local feasibility; and a policy claim may require traceability of stakeholders, unintended consequences, and the level of action justified. These distinctions matter because health sciences manuscripts often combine empirical evidence, interpretation, and recommendations within the same paper, and the strength of each layer should remain visible rather than being compressed into a single authoritative sentence [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
    </sec>
    <sec>
      <title>What Should Be Traceable?</title>
      <p>Judgment traceability should be claim centered. It should apply primarily to major interpretive, clinical, methodological, ethical, policy, and implementation claims rather than to every sentence. A major claim is one that asks readers to accept an interpretation, change a practice, adopt a policy, cite a conclusion, prioritize an intervention, or treat a proposed implication, as warranted. Stronger claims require stronger traceability. <xref rid="figure1" ref-type="fig">Figure 1</xref> therefore places the major scholarly claim, rather than the AI tool or prompt, at the center of governance. AI assistance may influence multiple stages of scholarly work, but the unit of governance is the claim and whether it remains traceable to an evidence base, author interpretation, uncertainty, population and setting context, equity and harms, recommendation strength, and accountable authorship [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. This claim-centered orientation is also consistent with peer-reviewed calls to prioritize provenance and verification over attempts to govern GAI through prohibition alone [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
      <fig id="figure1" position="float">
        <label>Figure 1</label>
        <caption>
          <p>Claim-centered judgment traceability in AI-assisted health sciences publishing. The figure presents a conceptual framework, not an empirically validated model. AI: artificial intelligence.</p>
        </caption>
        <graphic xlink:href="metascience_v1i1e106068_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <p>The practical value of a claim-centered approach is proportionality. A minor wording edit does not require extensive documentation, whereas a claim that implies a change in clinical practice, health policy, professional responsibility, or implementation priority should make its evidentiary basis and inferential pathway visible [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Before applying the traceability domains, authors and reviewers should first classify the claim as an evidence summary, inference, implication, recommendation, or speculation because the required level of support depends on what the statement asks readers to accept. <xref ref-type="table" rid="table1">Table 1</xref> then translates judgment traceability into seven domains that correspond to <xref rid="figure1" ref-type="fig">Figure 1</xref>: evidence base, author interpretation, uncertainty, population and setting context, equity and harms, recommendation strength, and accountable authorship. These domains are not intended to create a scoring instrument; they provide a vocabulary for asking what must be visible for a major claim to be defensible. Existing reporting guidelines, such as CONSORT-AI and DECIDE-AI, demonstrate the broader value of making the intended use, setting, human-AI interaction, safety, and implementation context explicit, even though judgment traceability is not proposed as a replacement reporting guideline [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p>
      <p>The framework also clarifies the difference between empirical support and conceptual contribution. Empirical studies can support component concerns, such as fabricated citations, detector bias, language barriers, publication policy heterogeneity, paper mill contamination, and automation bias [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. They cannot, by themselves, prove the full construct of expression-rich but judgment-thin scholarship, because that construct is proposed here as an analytic lens. Accordingly, this viewpoint uses empirical evidence to support the plausibility and relevance of the problem while using explicit proposal language when advancing judgment traceability as a governance response [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. This separation is important for metascience: a useful conceptual framework should generate testable questions without presenting its proposed constructs as though their prevalence, reliability, or effectiveness had already been established.</p>
      <p><xref ref-type="table" rid="table1">Table 1</xref> summarizes the seven traceability domains shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>. It is not a validated assessment instrument. Rather, it is a conceptual governance aid intended to help authors, reviewers, and editors identify what should be made visible for consequential scholarly claims to remain defensible.</p>
    </sec>
    <sec>
      <title>When AI Contributes an Idea: a Worked Example</title>
      <p>A further question is whether a recommendation initially suggested by an AI tool can count as being supported by human judgment if the authors had not independently conceived it before the AI output was produced. The answer depends not on the origin of the idea but on the authorial work that follows. Accountability rests on whether responsible authors can reconstruct the reasoning, evaluate the evidence, consider alternative interpretations, identify limits, and defend the final claim as their own scholarly judgment [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. This position is consistent with publication ethics arguments that AI systems cannot bear authorship responsibility and with peer-reviewed guidance that verification and human responsibility remain necessary even when GAI materially assists writing or idea development [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. The practical distinction is between assistance that stimulates accountable scholarly work and delegation that leaves no responsible human able to defend the resulting claim.</p>
      <p>This issue is also relevant to honest AI disclosure. If authors believe that acknowledging AI use will automatically trigger disproportionate procedural burdens, they may be less willing to disclose assistance; conversely, generic disclosures may become performative if they are treated as sufficient evidence of responsible use [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. A claim-centered approach reduces that risk by focusing scrutiny on the consequences of the claim rather than the mere presence of AI support. The same standard can therefore be applied to AI-assisted and non-AI-assisted manuscripts: are the major claims proportionate, source grounded, context sensitive, and attributable to accountable authors? This preserves the transparency value of disclosure while avoiding a governance model in which every prompt or stylistic edit receives the same scrutiny as a recommendation that could influence care, policy, or research priorities [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
      <p>The worked example here illustrates this distinction in a clinical context, but the same logic can be adapted to other health sciences claims. We propose that a qualitative manuscript should make visible how interpretations were derived from data and context; an informatics manuscript should clarify intended users, workflow assumptions, model limitations, and potential harms; and a policy viewpoint should distinguish evidence supporting a proposed action from normative or speculative elements. These are applications of the proposed traceability framework rather than claims that one existing reporting guideline already covers all paper types [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Consider a hypothetical AI-assisted manuscript discussing an emergency department (ED) sepsis alert intervention. A judgment-thin implication might state, “AI-enabled sepsis alerts should be implemented across EDs to improve early recognition, accelerate treatment, and enhance patient safety.” This sentence is fluent and clinically plausible, but it does not show whether the supporting evidence came from adult or pediatric populations, academic or community hospitals, high-resource or underresourced settings, or prospective trials or early-stage evaluations or whether the alert system’s positive predictive value, false-positive burden, workflow effects, and performance across patient subgroups were adequately assessed. Empirical sepsis alert literature illustrates why these details matter: ED alert systems vary substantially across studies, and recent evidence shows both potential clinical benefits and persistent concerns about the alert burden, generalizability, and sociodemographic performance [<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref37">37</xref>].</p>
      <p>A judgment-traceable version would make the claim more proportionate: “Available evidence may support further evaluation of AI-enabled sepsis alerts in EDs with sufficient informatics infrastructure; clinician response protocols; and monitoring for false positives, alert burdens, workflow effects, and subgroup performance. The current evidence should not be interpreted as a universal implementation mandate. Before adoption, journals, institutions, and clinical leaders should examine whether the evaluated population, setting, workflow, AI system version, input data, output interpretation, and outcome measures correspond to the intended local use case.” The difference is not merely tone. The judgment-traceable version distinguishes evidence from inference and recommendation, identifies contextual limits, makes uncertainty visible, and preserves accountability for the level of action being proposed [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref37">37</xref>]. It also demonstrates why judgment traceability is not reducible to adding more citations: the same evidence base can support very different claims, depending on how authors interpret scope, uncertainty, harms, and transferability.</p>
    </sec>
    <sec>
      <title>Implications for Authors, Reviewers, Editors, and Journals</title>
      <p>For authors, judgment traceability means identifying major claims and ensuring that each is supported by an appropriate evidence base, an explicit interpretive step, and a proportionate level of recommendation. Authors should distinguish evidence summaries from inferences, implications, recommendations, and speculation and should verify that cited sources actually support the statements attributed to them [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Transparent AI-assisted writing can support this process when authors document human intellectual contribution and verification without turning governance into indiscriminate prompt-level surveillance [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref16">16</xref>]. The goal is not to record every prompt but to ensure that claims likely to influence interpretation, practice, policy, or implementation can be reconstructed and defended by responsible authors. A useful author-facing question is therefore not “Did AI write this sentence?” but “If challenged, can we show why this claim follows from the cited evidence, why its limits are appropriate, and who accepts responsibility for it?” [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>].</p>
      <p>For reviewers and editors, judgment traceability should function as an interpretive aid rather than a punitive label. Reviewers should not be asked to determine whether text is AI generated, particularly because detection tools may be unreliable and may disadvantage nonnative English writers [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Instead, they can examine whether cited evidence directly supports major claims, whether population and setting limits are specified, whether competing interpretations are acknowledged, and whether recommendation strength is proportionate to the evidence [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Editors can use this approach selectively when claims appear clinically, methodologically, ethically, or policy relevant but insufficiently supported. Journals could pilot structured traceability prompts before treating them as settled standards and evaluate outcomes, such as author burden, reviewer agreement, editorial usefulness, citation accuracy, correction requests, and perceived fairness. The staged approach also clarifies what journals should not routinely require: complete prompt histories, private drafting records, or speculative reconstructions of every AI interaction may be burdensome, difficult to standardize, and poorly aligned with the integrity risk [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. A more feasible approach is to request clarification when a consequential claim lacks adequate evidence, context, uncertainty, or accountability, preserving the integrity function of peer review while avoiding a governance model that rewards paperwork over reasoning.</p>
      <p>For journals and publishers, a practical starting point is not to require a new universal form but to identify where current editorial workflows already ask for evidence, limitation, and accountability. Traceability prompts could be integrated selectively into reviewer forms, revision letters, or editorial checks for manuscripts containing high-consequence clinical, policy, or implementation claims. For example, reviewers could be asked whether a major recommendation is directly supported by the cited evidence, whether the target population and setting are explicit, and whether uncertainty or foreseeable harms have been acknowledged. Such prompts would operationalize claim accountability without requiring editors to infer how much text was generated by AI or to police every stage of drafting [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Existing disclosure taxonomies and peer-reviewed guidance can continue to document the role of AI in manuscript production, while judgment traceability addresses the separate question of whether the resulting claims are defensible [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Importantly, implementation should be evaluated rather than assumed beneficial. Journals would need to monitor whether additional prompts improve citation accuracy, reviewer consistency, and recommendation proportionality and whether they create new burdens, delays, or inequities for authors and reviewers. A governance intervention that increases paperwork without improving claim quality would itself risk becoming a form of editorial waste. The proposed framework therefore favors targeted clarification of consequential claims over blanket expansion of submission requirements, and it treats feasibility, fairness, and workload as empirical outcomes for future testing.</p>
    </sec>
    <sec>
      <title>Equity, Subjectivity, and Gatekeeping</title>
      <p>Any framework that asks reviewers to evaluate judgment carries risks of subjectivity. Reviewers may mistake familiar disciplinary language, institutional prestige, seniority, native English fluency, or agreement with their own clinical preferences for stronger judgment. Evidence from peer-reviewed research suggests that author and affiliation information can influence reviewer behavior in some settings [<xref ref-type="bibr" rid="ref31">31</xref>]. Research on AI text detection raises a separate equity concern: GPT detectors have misclassified nonnative English writing as AI generated in some evaluation settings [<xref ref-type="bibr" rid="ref26">26</xref>], while nonnative English-speaking researchers face measurable burdens in reading, writing, publishing, and presenting science [<xref ref-type="bibr" rid="ref2">2</xref>]. Domain judgment traceability should therefore be applied through observable claim features rather than impressions of author competence. A judgment-rich manuscript does not need ornate prose or extensive rhetorical display; it needs alignment among claim, evidence, inference, uncertainty, context, and accountability [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Authors should have opportunities to clarify allegedly insufficiently traceable claims, and reviewer concerns should be framed as requests for claim evidence clarification rather than accusations about AI use or author capability. These safeguards are essential if claim-centered governance is to improve accountability without reproducing linguistic or institutional gatekeeping [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref31">31</xref>].</p>
    </sec>
    <sec>
      <title>Boundaries of Judgment Traceability and Future Research Priorities</title>
      <p>Judgment traceability should be understood as a proposed conceptual governance aid rather than a validated assessment instrument. Its domains and examples require refinement through stakeholder consultation, piloting, and empirical evaluation. Future work should examine whether claim-centered traceability improves reviewer agreement, author experience, editorial usefulness, citation accuracy, correction rates, and proportionality between evidence and recommendations while also measuring burden and unintended consequences [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Validation should proceed in stages: Qualitative work can first examine how authors, reviewers, and editors understand traceability; consensus methods can then refine candidate domains; pilot studies can assess interreviewer agreement and feasibility; and comparative evaluations can test whether traceability prompts improve claim-source alignment or recommendation proportionality without creating inequitable barriers. The emerging literature on claim accountability, provenance, and responsible AI-assisted writing is developing rapidly, so the contribution of judgment traceability should be interpreted within this evolving conversation rather than as a claim of conceptual exclusivity [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      <p>The concept should also be applied proportionately across paper types. A clinical guideline, empirical study, qualitative analysis, policy commentary, laboratory report, implementation report, and philosophical essay make different kinds of claims and require different levels of traceability. Judgment traceability should not become a universal checklist applied mechanically to all scholarly writing, nor should it be used as a proxy for seniority, institutional prestige, English fluency, or disciplinary conformity [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. Its purpose is to make consequential scholarly claims more accountable while preserving equitable access to legitimate AI-assisted language and writing support [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. A boundary-focused implementation should also distinguish private reasoning from accountable scholarly justification. Judgment traceability does not require authors to reveal private chain-of-thought, informal notes, or every intermediate draft; it requires that consequential scholarly judgments—such as why evidence was interpreted in a particular way, why a recommendation is limited to a certain population or setting, and who accepts responsibility for the final claim—be sufficiently visible for review, revision, and accountability [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. This boundary is important because responsible publishing needs verifiable justification, not surveillance of cognition.</p>
    </sec>
    <sec>
      <title>Conclusion</title>
      <p>GAI does not make scholarship irresponsible by default; it may improve clarity, accessibility, organization, and language equity when used with transparent human verification [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. The integrity problem begins when fluent scholarly expression becomes disconnected from accountable judgment. In health sciences publishing, where claims may influence care, policy, education, research priorities, and public trust, the crucial question is not only whether AI was used but also whether major claims remain traceable to evidence, interpretation, uncertainty, context, and responsible authorship [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. This viewpoint proposes expression-rich but judgment-thin scholarship as a conceptual lens for recognizing that mismatch and domain judgment traceability as a claim-centered governance response. Detection asks whether text can be identified as machine generated; disclosure asks whether AI use has been reported; and judgment traceability asks whether the claims carried by the text can be reconstructed and defended by responsible authors. The framework does not replace disclosure, reporting guidelines, peer review, or research integrity standards. It adds a proportional question at the point where those mechanisms converge: does the strength of a consequential claim remain matched to its evidence, interpretation, limits, and accountable human judgment? In an era when scholarly expression can be generated at scale, responsible publishing will increasingly depend not only on knowing how text was produced but also on whether the claims it carries are proportionate, defensible, and traceable to accountable human judgment [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
    </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">CONSORT-AI</term>
          <def>
            <p>Consolidated Standards of Reporting Trials–Artificial Intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DECIDE-AI</term>
          <def>
            <p>Developmental and Exploratory Clinical Investigation of Decision Support Systems Driven by Artificial Intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">ED</term>
          <def>
            <p>emergency department</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">GAI</term>
          <def>
            <p>generative AI</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">GAIDeT</term>
          <def>
            <p>Generative Artificial Intelligence Delegation Taxonomy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors thank the editors and reviewers for their constructive comments, which strengthened the conceptual precision, evidentiary grounding, and practical orientation of this manuscript.</p>
      <p>Using the GAIDeT (Generative Artificial Intelligence Delegation Taxonomy) declaration framework [<xref ref-type="bibr" rid="ref16">16</xref>], the authors report that generative AI (GAI) tools, including ChatGPT by OpenAI, were used during manuscript development and revision in 2026 to support conceptual discussion, structural editing, manuscript revision, literature search support, summarization support, reference-checking support, language refinement, proofreading, and language polishing. These delegated tasks correspond to GAIDeT categories related to conceptualization, literature review support, writing and editing, and publication support. The authors did not use GAI to replace scholarly, methodological, clinical, or editorial judgment and did not treat GAI output as authoritative evidence.</p>
    </ack>
    <notes>
      <sec>
        <title>Funding</title>
        <p>No financial support was received for this work.</p>
      </sec>
    </notes>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Data sharing is not applicable to this viewpoint because no empirical datasets were generated or analyzed.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>TH conceptualized the manuscript, developed the central argument and proposed framework, drafted the manuscript, revised the intellectual content, verified references and claim-to-source correspondence, and approved the final version for submission. YTC contributed to conceptual refinement, interpretation of the literature, critical revision of the manuscript for important intellectual content, reference verification, and approval of the final version for submission. All substantive claims, interpretations, recommendations, source selection, and final decisions were reviewed and revised by the authors. Final verification of bibliographic details, publication status, DOI information, author names, and claim-to-source correspondence was performed by the authors using publisher pages, indexing records, PubMed records, arXiv or SSRN records, or full-text sources, when available. No confidential patient information, unpublished data, or identifiable personal data were entered into GAI tools. Both authors reviewed the final manuscript, can take responsibility for the central claims and cited sources relevant to their contributions, and accept full responsibility for the final manuscript, including all claims, interpretations, references, and conclusions.</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>Kobak</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>González-Márquez</surname>
              <given-names>Rita</given-names>
            </name>
            <name name-style="western">
              <surname>Horvát</surname>
              <given-names>Emőke-Ágnes</given-names>
            </name>
            <name name-style="western">
              <surname>Lause</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Delving into LLM-assisted writing in biomedical publications through excess vocabulary</article-title>
          <source>Sci Adv</source>
          <year>2025</year>
          <month>07</month>
          <day>04</day>
          <volume>11</volume>
          <issue>27</issue>
          <fpage>eadt3813</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https:///www.science.org/doi/10.1126/sciadv.adt3813?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1126/sciadv.adt3813</pub-id>
          <pub-id pub-id-type="medline">40601754</pub-id>
          <pub-id pub-id-type="pmcid">PMC12219543</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>Amano</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ramírez-Castañeda</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Berdejo-Espinola</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Borokini</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Chowdhury</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Golivets</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>González-Trujillo</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Montaño-Centellas</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Paudel</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Veríssimo</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The manifold costs of being a non-native English speaker in science</article-title>
          <source>PLoS Biol</source>
          <year>2023</year>
          <month>07</month>
          <day>18</day>
          <volume>21</volume>
          <issue>7</issue>
          <fpage>e3002184</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pbio.3002184"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pbio.3002184</pub-id>
          <pub-id pub-id-type="medline">37463136</pub-id>
          <pub-id pub-id-type="pii">PBIOLOGY-D-22-02711</pub-id>
          <pub-id pub-id-type="pmcid">PMC10353817</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>Tang</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kwok</surname>
              <given-names>KO</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Luong</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tam</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>The importance of transparency: declaring the use of generative artificial intelligence (AI) in academic writing</article-title>
          <source>J Nurs Scholarsh</source>
          <year>2024</year>
          <month>03</month>
          <volume>56</volume>
          <issue>2</issue>
          <fpage>314</fpage>
          <lpage>318</lpage>
          <pub-id pub-id-type="doi">10.1111/jnu.12938</pub-id>
          <pub-id pub-id-type="medline">37904646</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Generative artificial intelligence and academic writing: friend or foe?</article-title>
          <source>J Clin Epidemiol</source>
          <year>2025</year>
          <month>03</month>
          <volume>179</volume>
          <fpage>111646</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0895-4356(24)00402-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jclinepi.2024.111646</pub-id>
          <pub-id pub-id-type="medline">39706536</pub-id>
          <pub-id pub-id-type="pii">S0895-4356(24)00402-5</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>Bagenal</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Biamis</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Boillot</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Brierley</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Chew</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dehnel</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Frankish</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Grainger</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Pope</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prowse</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Samuel</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Slogrove</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Stacey</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thapaliya</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Trethewey</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>HH</given-names>
            </name>
            <name name-style="western">
              <surname>Varley-Reeves</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kleinert</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Generative AI: ensuring transparency and emphasising human intelligence and accountability</article-title>
          <source>Lancet</source>
          <year>2024</year>
          <month>11</month>
          <day>30</day>
          <volume>404</volume>
          <issue>10468</issue>
          <fpage>2142</fpage>
          <lpage>2143</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.proquest.com/docview/3133957186/fulltextPDF?pq-origsite=primo&amp;sourcetype=Scholarly%20Journals"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(24)02615-1</pub-id>
          <pub-id pub-id-type="medline">39615987</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(24)02615-1</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>Messeri</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Crockett</surname>
              <given-names>MJ</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence and illusions of understanding in scientific research</article-title>
          <source>Nature</source>
          <year>2024</year>
          <month>03</month>
          <day>06</day>
          <volume>627</volume>
          <issue>8002</issue>
          <fpage>49</fpage>
          <lpage>58</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nature.com/articles/s41586-024-07146-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41586-024-07146-0</pub-id>
          <pub-id pub-id-type="medline">38448693</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-024-07146-0</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>van Zoonen</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Morgan-Thomas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tursunbayeva</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Beyond AI disclosure: claim accountability and responsible research in scholarly publishing</article-title>
          <source>Eur Manag J</source>
          <year>2026</year>
          <month>08</month>
          <volume>44</volume>
          <issue>4</issue>
          <fpage>550</fpage>
          <lpage>556</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S0263237326000721"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.emj.2026.06.001</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>Johnson</surname>
              <given-names>RF</given-names>
            </name>
          </person-group>
          <article-title>Provenance, not prohibition: a framework for AI in scholarly publishing</article-title>
          <source>Laryngoscope Investig Otolaryngol</source>
          <year>2026</year>
          <month>08</month>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>e70487</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/10.1002/lio2.70487"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/lio2.70487</pub-id>
          <pub-id pub-id-type="medline">42382923</pub-id>
          <pub-id pub-id-type="pii">LIO270487</pub-id>
          <pub-id pub-id-type="pmcid">PMC13314381</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>Moffatt</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Is AI my co-author? The ethics of using artificial intelligence in scientific publishing</article-title>
          <source>Account Res</source>
          <year>2025</year>
          <month>11</month>
          <volume>32</volume>
          <issue>8</issue>
          <fpage>1313</fpage>
          <lpage>1329</lpage>
          <pub-id pub-id-type="doi">10.1080/08989621.2024.2386285</pub-id>
          <pub-id pub-id-type="medline">39109816</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>Cleland</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Driessen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Masters</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lingard</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Maggio</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>When and how to disclose AI use in academic publishing: AMEE guide no.192</article-title>
          <source>Med Teach</source>
          <year>2025</year>
          <month>12</month>
          <day>30</day>
          <volume>48</volume>
          <issue>4</issue>
          <fpage>542</fpage>
          <lpage>553</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cris.maastrichtuniversity.nl/en/publications/when-and-how-to-disclose-ai-use-in-academic-publishing-amee-guide/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/0142159x.2025.2607513</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>Zielinski</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Winker</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Aggarwal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ferris</surname>
              <given-names>LE</given-names>
            </name>
            <name name-style="western">
              <surname>Heinemann</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lapeña</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Pai</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Ing</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Citrome</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Alam</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Voight</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Habibzadeh</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Chatbots, generative AI, and scholarly manuscripts: WAME recommendations on chatbots and generative artificial intelligence in relation to scholarly publications</article-title>
          <source>Colomb Med (Cali)</source>
          <year>2023</year>
          <month>12</month>
          <day>01</day>
          <volume>54</volume>
          <issue>3</issue>
          <fpage>e1015868</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38089825"/>
          </comment>
          <pub-id pub-id-type="doi">10.25100/cm.v54i3.5868</pub-id>
          <pub-id pub-id-type="medline">38089825</pub-id>
          <pub-id pub-id-type="pmcid">PMC10712422</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>Flanagin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pirracchio</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Khera</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Berkwits</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hswen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Bibbins-Domingo</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Reporting use of AI in research and scholarly publication—JAMA Network guidance</article-title>
          <source>JAMA</source>
          <year>2024</year>
          <month>04</month>
          <day>02</day>
          <volume>331</volume>
          <issue>13</issue>
          <fpage>1096</fpage>
          <lpage>1098</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jama/fullarticle/2816213"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jama.2024.3471</pub-id>
          <pub-id pub-id-type="medline">38451540</pub-id>
          <pub-id pub-id-type="pii">2816213</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>Ganjavi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Eppler</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Pekcan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Biedermann</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Abreu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>GS</given-names>
            </name>
            <name name-style="western">
              <surname>Gill</surname>
              <given-names>IS</given-names>
            </name>
            <name name-style="western">
              <surname>Cacciamani</surname>
              <given-names>GE</given-names>
            </name>
          </person-group>
          <article-title>Publishers' and journals' instructions to authors on use of generative artificial intelligence in academic and scientific publishing: bibliometric analysis</article-title>
          <source>BMJ</source>
          <year>2024</year>
          <month>01</month>
          <day>31</day>
          <volume>384</volume>
          <fpage>e077192</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=38296328"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2023-077192</pub-id>
          <pub-id pub-id-type="medline">38296328</pub-id>
          <pub-id pub-id-type="pmcid">PMC10828852</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>Yoo</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Defining the boundaries of AI use in scientific writing: a comparative review of editorial policies</article-title>
          <source>J Korean Med Sci</source>
          <year>2025</year>
          <month>06</month>
          <day>16</day>
          <volume>40</volume>
          <issue>23</issue>
          <fpage>e187</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jkms.org/DOIx.php?id=10.3346/jkms.2025.40.e187"/>
          </comment>
          <pub-id pub-id-type="doi">10.3346/jkms.2025.40.e187</pub-id>
          <pub-id pub-id-type="medline">40524628</pub-id>
          <pub-id pub-id-type="pii">40.e187</pub-id>
          <pub-id pub-id-type="pmcid">PMC12170296</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>Park</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Towards a transparent and reproducible AI-assisted research paper writing</article-title>
          <source>Genomics Inform</source>
          <year>2025</year>
          <month>12</month>
          <day>02</day>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>26</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://genomicsinform.biomedcentral.com/articles/10.1186/s44342-025-00057-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s44342-025-00057-0</pub-id>
          <pub-id pub-id-type="medline">41331701</pub-id>
          <pub-id pub-id-type="pii">10.1186/s44342-025-00057-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC12670809</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>Suchikova</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Tsybuliak</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Teixeira da Silva</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Nazarovets</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>GAIDeT (Generative AI Delegation Taxonomy): a taxonomy for humans to delegate tasks to generative artificial intelligence in scientific research and publishing</article-title>
          <source>Account Res</source>
          <year>2026</year>
          <month>04</month>
          <volume>33</volume>
          <issue>3</issue>
          <fpage>2544331</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/40781729/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/08989621.2025.2544331</pub-id>
          <pub-id pub-id-type="medline">40781729</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>Májovský</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Černý</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kasal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Komarc</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Netuka</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence can generate fraudulent but authentic-looking scientific medical articles: Pandora's box has been opened</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <month>05</month>
          <day>31</day>
          <volume>25</volume>
          <fpage>e46924</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e46924/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/46924</pub-id>
          <pub-id pub-id-type="medline">37256685</pub-id>
          <pub-id pub-id-type="pii">v25i1e46924</pub-id>
          <pub-id pub-id-type="pmcid">PMC10267787</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>Walters</surname>
              <given-names>WH</given-names>
            </name>
            <name name-style="western">
              <surname>Wilder</surname>
              <given-names>EI</given-names>
            </name>
          </person-group>
          <article-title>Fabrication and errors in the bibliographic citations generated by ChatGPT</article-title>
          <source>Sci Rep</source>
          <year>2023</year>
          <month>09</month>
          <day>07</day>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>14045</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-023-41032-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-023-41032-5</pub-id>
          <pub-id pub-id-type="medline">37679503</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-023-41032-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC10484980</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Resnik</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Hosseini</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Hallucinated citations produced by generative artificial intelligence may constitute research misconduct when citations function as data in scholarly papers</article-title>
          <source>Account Res</source>
          <year>2026</year>
          <month>10</month>
          <day>15</day>
          <volume>33</volume>
          <issue>7</issue>
          <fpage>2645390</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.1080/08989621.2026.2645390?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/08989621.2026.2645390</pub-id>
          <pub-id pub-id-type="medline">41833014</pub-id>
          <pub-id pub-id-type="pmcid">PMC13051339</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bender</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Gebru</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>McMillan-Major</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shmitchell</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>On the dangers of stochastic parrots: can language models be too big?</article-title>
          <year>2021</year>
          <conf-name>2021 ACM Conference on Fairness, Accountability, and Transparency (FAccT ’21)</conf-name>
          <conf-date>March 3-10, 2021</conf-date>
          <conf-loc>Canada</conf-loc>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Association for Computing Machinery</publisher-name>
          <fpage>610</fpage>
          <lpage>623</lpage>
          <pub-id pub-id-type="doi">10.1145/3442188.3445922</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>Goddard</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Roudsari</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Automation bias: a systematic review of frequency, effect mediators, and mitigators</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2012</year>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>121</fpage>
          <lpage>127</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/21685142"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2011-000089</pub-id>
          <pub-id pub-id-type="medline">21685142</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2011-000089</pub-id>
          <pub-id pub-id-type="pmcid">PMC3240751</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>Lyell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Automation bias and verification complexity: a systematic review</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2017</year>
          <month>03</month>
          <day>01</day>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>423</fpage>
          <lpage>431</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27516495"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocw105</pub-id>
          <pub-id pub-id-type="medline">27516495</pub-id>
          <pub-id pub-id-type="pii">ocw105</pub-id>
          <pub-id pub-id-type="pmcid">PMC7651899</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Burrell</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>How the machine ‘thinks’: understanding opacity in machine learning algorithms</article-title>
          <source>Big Data Soc</source>
          <year>2016</year>
          <month>01</month>
          <day>06</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/2053951715622512"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/2053951715622512</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>Parker</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Boughton</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bero</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Byrne</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Paper mill challenges: past, present, and future</article-title>
          <source>J Clin Epidemiol</source>
          <year>2024</year>
          <month>12</month>
          <volume>176</volume>
          <fpage>111549</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0895-4356(24)00305-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jclinepi.2024.111549</pub-id>
          <pub-id pub-id-type="medline">39389277</pub-id>
          <pub-id pub-id-type="pii">S0895-4356(24)00305-6</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>Candal-Pedreira</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ross</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Ruano-Ravina</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Egilman</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Fernández</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Pérez-Ríos</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Retracted papers originating from paper mills: cross sectional study</article-title>
          <source>BMJ</source>
          <year>2022</year>
          <month>11</month>
          <day>28</day>
          <volume>379</volume>
          <fpage>e071517</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bmj.com/lookup/pmidlookup?view=long&amp;pmid=36442874"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj-2022-071517</pub-id>
          <pub-id pub-id-type="medline">36442874</pub-id>
          <pub-id pub-id-type="pmcid">PMC9703783</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>Liang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Yuksekgonul</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Zou</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>GPT detectors are biased against non-native English writers</article-title>
          <source>Patterns (N Y)</source>
          <year>2023</year>
          <month>07</month>
          <day>14</day>
          <volume>4</volume>
          <issue>7</issue>
          <fpage>100779</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2666-3899(23)00130-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.patter.2023.100779</pub-id>
          <pub-id pub-id-type="medline">37521038</pub-id>
          <pub-id pub-id-type="pii">S2666-3899(23)00130-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC10382961</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>Chalmers</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Avoidable waste in the production and reporting of research evidence</article-title>
          <source>Lancet</source>
          <year>2009</year>
          <month>07</month>
          <day>04</day>
          <volume>374</volume>
          <issue>9683</issue>
          <fpage>86</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(09)60329-9</pub-id>
          <pub-id pub-id-type="medline">19525005</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(09)60329-9</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>Macleod</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Michie</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Dirnagl</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Chalmers</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ioannidis</surname>
              <given-names>JPA</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Shahi Salman</surname>
              <given-names>Rustam</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Biomedical research: increasing value, reducing waste</article-title>
          <source>Lancet</source>
          <year>2014</year>
          <month>01</month>
          <day>11</day>
          <volume>383</volume>
          <issue>9912</issue>
          <fpage>101</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(13)62329-6</pub-id>
          <pub-id pub-id-type="medline">24411643</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(13)62329-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chalmers</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Nasser</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bossuyt</surname>
              <given-names>PMM</given-names>
            </name>
            <name name-style="western">
              <surname>Korevaar</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Graham</surname>
              <given-names>ID</given-names>
            </name>
            <name name-style="western">
              <surname>Ravaud</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Boutron</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Increasing value and reducing waste in biomedical research: who's listening?</article-title>
          <source>Lancet</source>
          <year>2016</year>
          <month>04</month>
          <day>09</day>
          <volume>387</volume>
          <issue>10027</issue>
          <fpage>1573</fpage>
          <lpage>1586</lpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(15)00307-4</pub-id>
          <pub-id pub-id-type="medline">26423180</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(15)00307-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Citation contamination by paper mill articles in systematic reviews of the life sciences</article-title>
          <source>JAMA Netw Open</source>
          <year>2025</year>
          <month>06</month>
          <day>02</day>
          <volume>8</volume>
          <issue>6</issue>
          <fpage>e2515160</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2025.15160"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2025.15160</pub-id>
          <pub-id pub-id-type="medline">40504528</pub-id>
          <pub-id pub-id-type="pii">2835228</pub-id>
          <pub-id pub-id-type="pmcid">PMC12163679</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>Tomkins</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Heavlin</surname>
              <given-names>WD</given-names>
            </name>
          </person-group>
          <article-title>Reviewer bias in single- versus double-blind peer review</article-title>
          <source>Proc Natl Acad Sci U S A</source>
          <year>2017</year>
          <month>11</month>
          <day>28</day>
          <volume>114</volume>
          <issue>48</issue>
          <fpage>12708</fpage>
          <lpage>12713</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pnas.org/doi/10.1073/pnas.1707323114?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1073/pnas.1707323114</pub-id>
          <pub-id pub-id-type="medline">29138317</pub-id>
          <pub-id pub-id-type="pii">1707323114</pub-id>
          <pub-id pub-id-type="pmcid">PMC5715744</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>Sackett</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenberg</surname>
              <given-names>WMC</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>JAM</given-names>
            </name>
            <name name-style="western">
              <surname>Haynes</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>Richardson</surname>
              <given-names>WS</given-names>
            </name>
          </person-group>
          <article-title>Evidence based medicine: what it is and what it isn't</article-title>
          <source>BMJ</source>
          <year>1996</year>
          <month>01</month>
          <day>13</day>
          <volume>312</volume>
          <issue>7023</issue>
          <fpage>71</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/8555924"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.312.7023.71</pub-id>
          <pub-id pub-id-type="medline">8555924</pub-id>
          <pub-id pub-id-type="pmcid">PMC2349778</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>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cruz Rivera</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Calvert</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Denniston</surname>
              <given-names>AK</given-names>
            </name>
            <collab>SPIRIT-AI and CONSORT-AI Working Group</collab>
          </person-group>
          <article-title>Reporting guidelines for clinical trial reports for interventions involving artificial intelligence: the CONSORT-AI extension</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>09</month>
          <day>09</day>
          <volume>26</volume>
          <issue>9</issue>
          <fpage>1364</fpage>
          <lpage>1374</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32908283"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-020-1034-x</pub-id>
          <pub-id pub-id-type="medline">32908283</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-020-1034-x</pub-id>
          <pub-id pub-id-type="pmcid">PMC7598943</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</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>Nat Med</source>
          <year>2022</year>
          <month>05</month>
          <day>18</day>
          <volume>28</volume>
          <issue>5</issue>
          <fpage>924</fpage>
          <lpage>933</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/35585198/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-022-01772-9</pub-id>
          <pub-id pub-id-type="medline">35585198</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-022-01772-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ko</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Suh</surname>
              <given-names>GY</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>YJ</given-names>
            </name>
          </person-group>
          <article-title>Sepsis alert systems, mortality, and adherence in emergency departments: a systematic review and meta-analysis</article-title>
          <source>JAMA Netw Open</source>
          <year>2024</year>
          <month>07</month>
          <day>01</day>
          <volume>7</volume>
          <issue>7</issue>
          <fpage>e2422823</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/10.1001/jamanetworkopen.2024.22823"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.22823</pub-id>
          <pub-id pub-id-type="medline">39037814</pub-id>
          <pub-id pub-id-type="pii">2821277</pub-id>
          <pub-id pub-id-type="pmcid">PMC11265133</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>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Naidech</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Comparison between machine learning methods for mortality prediction for sepsis patients with different social determinants</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2022</year>
          <month>06</month>
          <day>16</day>
          <volume>22</volume>
          <issue>Suppl 2</issue>
          <fpage>156</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-022-01871-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-022-01871-0</pub-id>
          <pub-id pub-id-type="medline">35710407</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-022-01871-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC9204861</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>Hwang</surname>
              <given-names>MI</given-names>
            </name>
            <name name-style="western">
              <surname>Bond</surname>
              <given-names>WF</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>ES</given-names>
            </name>
          </person-group>
          <article-title>Sepsis alerts in emergency departments: a systematic review of accuracy and quality measure impact</article-title>
          <source>West J Emerg Med</source>
          <year>2020</year>
          <month>08</month>
          <day>24</day>
          <volume>21</volume>
          <issue>5</issue>
          <fpage>1201</fpage>
          <lpage>1210</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32970576"/>
          </comment>
          <pub-id pub-id-type="doi">10.5811/westjem.2020.5.46010</pub-id>
          <pub-id pub-id-type="medline">32970576</pub-id>
          <pub-id pub-id-type="pii">westjem.2020.5.46010</pub-id>
          <pub-id pub-id-type="pmcid">PMC7514413</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
