<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="letter"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR AI</journal-id><journal-id journal-id-type="publisher-id">ai</journal-id><journal-id journal-id-type="index">41</journal-id><journal-title>JMIR AI</journal-title><abbrev-journal-title>JMIR AI</abbrev-journal-title><issn pub-type="epub">2817-1705</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">v5i1e104210</article-id><article-id pub-id-type="doi">10.2196/104210</article-id><article-categories><subj-group subj-group-type="heading"><subject>Letter to the Editor</subject></subj-group></article-categories><title-group><article-title>PRISMA-trAIce: A Name Without Endorsement</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Moher</surname><given-names>David</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Page</surname><given-names>Matthew</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>McKenzie</surname><given-names>Joanne</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Takwoingi</surname><given-names>Yemisi</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Mayo-Wilson</surname><given-names>Evan</given-names></name><degrees>DPhil, MPA</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib></contrib-group><aff id="aff1"><institution>Centre for Journalology, Methodological and Implementation Research Program, Ottawa Hospital Research Institute</institution><addr-line>501 Smyth Road, L1255, Box/C.P. 711</addr-line><addr-line>Ottawa</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff2"><institution>Methods in Evidence Synthesis Unit, School of Public Health and Preventive Medicine, Monash University</institution><addr-line>Melbourne</addr-line><addr-line>Victoria</addr-line><country>Australia</country></aff><aff id="aff3"><institution>Department of Applied Health Sciences, College of Medicine and Health, University of Birmingham</institution><addr-line>Birmingham</addr-line><addr-line>England</addr-line><country>United Kingdom</country></aff><aff id="aff4"><institution>Department of Epidemiology, UNC Gillings School of Global Public Health, University of North Carolina at Chapel Hill</institution><addr-line>Chapel Hill</addr-line><addr-line>NC</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Coristine</surname><given-names>Andrew</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to David Moher, PhD, Centre for Journalology, Methodological and Implementation Research Program, Ottawa Hospital Research Institute, 501 Smyth Road, L1255, Box/C.P. 711, Ottawa, ON, K1H 8L6, Canada, 1 613-737-8899 ext 73812; <email>dmoher@ohri.ca</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>18</day><month>8</month><year>2026</year></pub-date><volume>5</volume><elocation-id>e104210</elocation-id><history><date date-type="received"><day>20</day><month>06</month><year>2026</year></date><date date-type="accepted"><day>05</day><month>08</month><year>2026</year></date></history><copyright-statement>&#x00A9; David Moher, Matthew Page, Joanne McKenzie, Yemisi Takwoingi, Evan Mayo-Wilson. Originally published in JMIR AI (<ext-link ext-link-type="uri" xlink:href="https://ai.jmir.org">https://ai.jmir.org</ext-link>), 18.8.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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR AI, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.ai.jmir.org/">https://www.ai.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://ai.jmir.org/2026/1/e104210"/><kwd-group><kwd>systematic literature review</kwd><kwd>reporting guideline</kwd><kwd>artificial intelligence</kwd><kwd>large language models</kwd><kwd>LLMs</kwd><kwd>PRISMA</kwd><kwd>transparency</kwd><kwd>evidence synthesis</kwd></kwd-group></article-meta></front><body><p>We recently read the article titled &#x201C;Transparent Reporting of AI in Systematic Literature Reviews: Development of the PRISMA-trAIce Checklist&#x201D; by Holst and colleagues [<xref ref-type="bibr" rid="ref1">1</xref>] in <italic>JMIR AI</italic>. We are writing in our capacity as members of the PRISMA Executive, which oversees and supports the development of the main PRISMA (Preferred Reporting Items for Systematic reviews and Meta-Analyses) statement (PRISMA 2020) and its extensions, to raise our concerns about this checklist.</p><p>The PRISMA Executive has established processes to guide decisions about the need for new extensions, ensure that the reporting guidelines are developed using rigorous consensus-based methods, and determine whether they ultimately should be endorsed. This is important because use of the PRISMA name not only signals that a checklist is relevant to systematic reviews but also conveys to users that the guideline has been developed using appropriate and rigorous methods. As the developers of the PRISMA-trAIce checklist did not follow our processes, we do not endorse it as a PRISMA checklist.</p><p>We would also like to take this opportunity to highlight the process for developing PRISMA extensions for the benefit of those interested in developing future extensions. This process, outlined on the PRISMA website [<xref ref-type="bibr" rid="ref2">2</xref>], aims to ensure that PRIMSA extensions are complementary with one another and the main statement, not redundant, and are developed using consensus-based methods. Applicants are expected to complete a form providing details of their proposed PRISMA extension, which the PRISMA Executive assesses against the criteria for approving new extensions [<xref ref-type="bibr" rid="ref3">3</xref>].</p><p>The importance of these processes is illustrated by several concerns regarding the development and positioning of PRISMA-trAIce. There is very limited information describing how the checklist items were selected for inclusion. More broadly, the reporting guideline development process does not follow established guidance for developing reporting guidelines, including extensions [<xref ref-type="bibr" rid="ref4">4</xref>]. The authors of PRISMA-trAIce acknowledge this, stating that their work is &#x201C;the result of a systematic adaptation, not a formal, large-scale consensus-building exercise.&#x201D; They also describe the checklist as a foundational tool &#x201C;paving the way for a formal, community-endorsed standard.&#x201D; This raises the question of why the PRISMA name is being used at this stage. Inappropriately badging the checklist as a PRISMA extension could be confusing for authors, who may be unsure how to use PRISMA-trAIce alongside PRISMA 2020 and other extensions.</p><p>We agree with Holt and colleagues [<xref ref-type="bibr" rid="ref1">1</xref>] that PRISMA 2020 should be updated to incorporate guidance on the use of AI tools in the systematic review process. To meet this need, members of the PRISMA Executive and its global collaborators are spearheading the development of such consensus-based guidance. This guidance will soon serve as an official resource, hosted on the PRISMA website to ensure findability and drive uptake across the evidence synthesis community.</p></body><back><notes><sec><title>Funding</title><p>The authors declared no financial support was received for this work.</p></sec></notes><fn-group><fn fn-type="conflict"><p>All authors are members of the PRISMA Executive.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">PRISMA</term><def><p>Preferred Reporting Items for Systematic reviews and Meta-Analyses</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Holst</surname><given-names>D</given-names> </name><name name-style="western"><surname>Moenck</surname><given-names>K</given-names> </name><name name-style="western"><surname>Koch</surname><given-names>J</given-names> </name><name name-style="western"><surname>Schmedemann</surname><given-names>O</given-names> </name><name name-style="western"><surname>Sch&#x00FC;ppstuhl</surname><given-names>T</given-names> </name></person-group><article-title>Transparent reporting of AI in systematic literature reviews: development of the PRISMA-trAIce checklist</article-title><source>JMIR AI</source><year>2025</year><month>12</month><day>10</day><volume>4</volume><fpage>e80247</fpage><pub-id pub-id-type="doi">10.2196/80247</pub-id><pub-id pub-id-type="medline">41370833</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="web"><article-title>PRISMA extensions</article-title><source>PRISMA</source><access-date>2026-08-13</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.prisma-statement.org/extensions">https://www.prisma-statement.org/extensions</ext-link></comment></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="web"><article-title>Criteria for approving new PRISMA extensions</article-title><source>PRISMA</source><access-date>2026-08-13</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.prisma-statement.org/criteria-new-extension">https://www.prisma-statement.org/criteria-new-extension</ext-link></comment></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Moher</surname><given-names>D</given-names> </name><name name-style="western"><surname>Schulz</surname><given-names>KF</given-names> </name><name name-style="western"><surname>Simera</surname><given-names>I</given-names> </name><name name-style="western"><surname>Altman</surname><given-names>DG</given-names> </name></person-group><article-title>Guidance for developers of health research reporting guidelines</article-title><source>PLoS Med</source><year>2010</year><month>02</month><day>16</day><volume>7</volume><issue>2</issue><fpage>e1000217</fpage><pub-id pub-id-type="doi">10.1371/journal.pmed.1000217</pub-id><pub-id pub-id-type="medline">20169112</pub-id></nlm-citation></ref></ref-list></back></article>