<?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="editorial"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v14i1e109008</article-id><article-id pub-id-type="doi">10.2196/109008</article-id><article-categories><subj-group subj-group-type="heading"><subject>Editorial</subject></subj-group></article-categories><title-group><article-title>Refining Our Focus by Bridging Theory and Practice for Real-World Impact: An Updated Scope for JMIR Medical Informatics</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Iannaccio</surname><given-names>Amanda</given-names></name><degrees>BA, GCBA</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Coristine</surname><given-names>Andrew J</given-names></name><degrees>MSc, PhD</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Leung</surname><given-names>Tiffany I</given-names></name><degrees>MPH, MD</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff5">5</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Biomedical Engineering, Duke University</institution><addr-line>Durham</addr-line><addr-line>NC</addr-line><country>United States</country></aff><aff id="aff2"><institution>Department of Biomedical Informatics, Jacobs School of Medicine and Biomedical Sciences, University at Buffalo</institution><addr-line>Buffalo</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff3"><institution>JMIR Publications, Inc</institution><addr-line>130 Queens Quay East, Unit 1100</addr-line><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff4"><institution>Division of Cardiology (affiliate), Department of Medicine, McGill University</institution><addr-line>Montreal</addr-line><addr-line>QC</addr-line><country>Canada</country></aff><aff id="aff5"><institution>Department of Internal Medicine (adjunct), Southern Illinois University School of Medicine</institution><addr-line>Springfield</addr-line><addr-line>IL</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Steenstra</surname><given-names>Ivan</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Arriel Benis, PhD, JMIR Publications, Inc, 130 Queens Quay East, Unit 1100, Toronto, ON, M5A 0P6, Canada, 1 416-583-2040; <email>ed-support@jmir.org</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>4</day><month>9</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e109008</elocation-id><history><date date-type="received"><day>07</day><month>08</month><year>2026</year></date><date date-type="rev-recd"><day>14</day><month>08</month><year>2026</year></date><date date-type="accepted"><day>14</day><month>08</month><year>2026</year></date></history><copyright-statement>&#x00A9; Arriel Benis, Amanda Iannaccio, Andrew J Coristine, Tiffany I Leung. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 4.9.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 Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.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://medinform.jmir.org/2026/1/e109008"/><abstract><p>To align with contemporary trends and place greater focus on persistent and novel challenges in the field, <italic>JMIR Medical Informatics</italic> has updated its focus and scope. Each submitted work will be evaluated against a stronger criterion for translational impact. Additionally, submissions on AI methods and applications are expected to meet standards of rigor and reporting transparency. In this editorial, we explain further what changed; why; and what this means for prospective authors, reviewers, and readers.</p></abstract><kwd-group><kwd>medical informatics</kwd><kwd>biomedical informatics</kwd><kwd>informatics applications</kwd><kwd>informatics</kwd><kwd>clinical applications</kwd><kwd>artificial intelligence</kwd><kwd>digital health applications</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>The pace of technological advancements and applications in medical informatics continues to accelerate. Scientific, peer-reviewed publishing is also evolving in parallel. To align with contemporary trends and bring greater focus to persistent and novel challenges in the field, <italic>JMIR Medical Informatics</italic> has updated its editorial scope and focus. In this editorial, we explain what changed; why; and what this means for prospective authors, reviewers, and readers. As biomedical and health informatics (BMHI) has evolved, so has the process and production of research and publications. To maintain priority and focus on high-quality research with translational impact and rigorously conducted and reported AI applications, we outline the editors&#x2019; vision for updating the journal&#x2019;s focus and scope.</p></sec><sec id="s2"><title>What Has Changed</title><p>The core identity of the journal is unchanged: <italic>JMIR Medical Informatics</italic> remains a home for high-quality research on BMHI and, specifically, medical informatics; clinical informatics applications; and the full pipeline of data on medicine, health, and well-being&#x2014;from acquisition and semantics through analytics, decision support, and evaluation. The journal&#x2019;s updated scope provides guidance for two specific groups of submissions to <italic>JMIR Medical Informatics</italic>.</p><p><italic>First, each submitted work will be evaluated against a stronger criterion for translational impact. JMIR Medical Informatics</italic> focuses on applied, translational research and implementation science. The revised scope explicitly prioritizes &#x201C;research that bridges theoretical frameworks with actionable insights, ensuring that informatics solutions demonstrate measurable clinical or population impact&#x201D; [<xref ref-type="bibr" rid="ref1">1</xref>]. Theoretical frameworks should be accompanied by actionable insights. To meet this updated expectation, authors must explicitly articulate the clinical and population health implications of their work and should not rely on technical novelty only. Manuscripts should clearly demonstrate how the proposed informatics solutions translate theoretical frameworks into tangible benefits for health systems, care delivery, and patient outcomes.</p><p><italic>Second, submissions on AI methods and applications must state their standards explicitly</italic>. Submitted work is expected to provide evidence of clinical applicability and maturity. This includes all submitted manuscripts that build on machine learning, deep learning, information retrieval, natural language processing, or image processing. The updated journal scope says AI-oriented submissions &#x201C;must demonstrate utility beyond algorithmic performance on static datasets. Studies should exhibit clinical applicability and maturity, such as integration into care workflows, deployment in routine practice, or robust external validation, with meaningful documented outcomes for patients or clinicians&#x201D; [<xref ref-type="bibr" rid="ref1">1</xref>]. Submissions must demonstrate utility beyond algorithmic development or performance on static datasets, including publicly available datasets. While a well-tuned model evaluated only on a held-out test set is valuable, it is no longer sufficient on its own for consideration in this journal. We recommend that authors adhere to the appropriate TRIPOD (Transparent Reporting of a Multivariable Prediction Model for Individual Prognosis or Diagnosis) guidelines, such as the TRIPOD+AI or TRIPOD-LLM (large language model) guidelines, for their study design and methodology, with particular attention to item 27c in TRIPOD+AI [<xref ref-type="bibr" rid="ref2">2</xref>] or item 19g in TRIPOD-LLM [<xref ref-type="bibr" rid="ref3">3</xref>]; these items underscore the &#x201C;applicability and generalizability&#x201D; of the predictive model or LLM [<xref ref-type="bibr" rid="ref4">4</xref>]. Furthermore, authors should explicitly detail the practice insights and outcomes gained from their deployment, illustrating how the presented tools affect clinical and administrative workflows, reduce cognitive load or burden for health care consumers and providers, and improve operational or health system efficiencies.</p><p><italic>Finally, a complete</italic> Data Availability <italic>statement is expected for all submissions</italic> [<xref ref-type="bibr" rid="ref5">5</xref>]. Additionally, where the methods involve writing code, authors should include a statement on code availability (eg, making the code available on GitHub).</p><p>We also welcome implementation reports [<xref ref-type="bibr" rid="ref6">6</xref>]&#x2014;a novel format that was introduced in 2023 as the first of its kind among medical informatics journals and was specifically intended for manuscripts that systematically describe how an informatics solution was translated into a routine clinical environment. Since their inception, implementation reports have followed a complete and standardized reporting guidance [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. Last year, an accompanying i-CHECK-DH&#x2013;related toolkit was published to further support researchers in carrying out and reporting their work on clinical informatics and digital health implementations [<xref ref-type="bibr" rid="ref9">9</xref>]. These have become a durable and growing part of our portfolio, and they are exactly the kind of scholarship the revised scope is designed to encourage.</p></sec><sec id="s3"><title>Why Update Journal Scope</title><p>The journal&#x2019;s scope has been updated to adapt to gradual shifts in submission and publication trends in <italic>JMIR Medical Informatics</italic>. Over the last 2 years, machine learning and deep learning approaches have made up the largest proportion of submissions. Among published articles, those that describe electronic health record infrastructure, interoperability work, and system-level data integration are markedly more common. Additionally, published articles are frequently framed around the implementation and real-world deployment of digital health and informatics. Conversely, submissions that are narrowly focused bibliometric analyses or simple literature reviews (those not applying a rigorous and standardized methodology), as well as submissions on stand-alone generative AI applications, tend not to advance to review or publication.</p><p>This pattern aligns with the revised scope: technical sophistication alone, whether in a predictive model or an LLM (or any other model) application, is not what will earn a place in this journal. The journal prioritizes evidence that a solution has been evaluated in real-world settings by patients, caregivers, clinicians, other health professionals, or decision-makers (eg, within a workflow, health system, or validated deployment). Additionally, we also value transparently reported negative results; rigorously conducted evaluations of implementations that failed to improve clinical or operational outcomes are vital for advancing implementation science and preventing repeated systemic failures, as long as the methodologies and lessons learned are comprehensively documented to prevent the submission of trivial nonresults.</p></sec><sec id="s4"><title>What This Means for Authors</title><p>If your research demonstrates a working BMHI solution or explains why it did not work, we welcome your submission for consideration in <italic>JMIR Medical Informatics</italic>: this is where it belongs. Moving forward, we strongly encourage authors to dedicate a specific portion of their discussion to clinical and informatics practice insights, ensuring that the broader impact on personalized medicine, individuals, populations, public health, and health systems is transparent and actionable. If you are refining a promising model that has not yet left the training environment, we would prefer to see it again once it has matured. We are grateful to the authors, reviewers, and editors who have shaped this journal&#x2019;s identity, and we look forward to continuing that work together, along with the BMHI communities, as we move forward with the refined focus and scope of <italic>JMIR Medical Informatics</italic>.</p></sec></body><back><ack><p>The following tasks were delegated to Claude Sonnet 5 (Anthropic) under full human supervision: text summarization, editing, and trend identification (TIL). Authors manually verified all claims and citations and are accountable for the content of this editorial.</p></ack><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="con"><p>Conceptualization: AB, TIL, AJC</p><p>Supervision: AB, TIL</p><p>Writing &#x2013; original draft: TIL</p><p>Writing &#x2013; review &#x0026; editing: AB, AI, TIL, AJC</p></fn><fn fn-type="conflict"><p>AB is the editor-in-chief of <italic>JMIR Medical Informatics</italic> at the time of this publication. AI is a managing editor at JMIR Publications at the time of this publication. TIL is the scientific editorial director at JMIR Publications at the time of this publication and a director on the Board of Directors, American Medical Informatics Association. AJC is a scientific editor at JMIR Publications at the time of this publication. All authors had no involvement in the editorial review and processing of this manuscript.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">BMHI</term><def><p>biomedical and health informatics</p></def></def-item><def-item><term id="abb2">LLM</term><def><p>large language model</p></def></def-item><def-item><term id="abb3">TRIPOD</term><def><p>Transparent Reporting of a Multivariable Prediction Model for Individual Prognosis or Diagnosis</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="web"><article-title>Focus and scope</article-title><source>JMIR Medical Informatics</source><access-date>2026-07-18</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/about-journal/focus-and-scope">https://medinform.jmir.org/about-journal/focus-and-scope</ext-link></comment></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>Collins</surname><given-names>GS</given-names> </name><name name-style="western"><surname>Moons</surname><given-names>KGM</given-names> </name><name name-style="western"><surname>Dhiman</surname><given-names>P</given-names> </name><etal/></person-group><article-title>TRIPOD+AI statement: updated guidance for reporting clinical prediction models that use regression or machine learning methods</article-title><source>BMJ</source><year>2024</year><month>04</month><day>16</day><volume>385</volume><fpage>e078378</fpage><pub-id pub-id-type="doi">10.1136/bmj-2023-078378</pub-id><pub-id pub-id-type="medline">38626948</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>Gallifant</surname><given-names>J</given-names> </name><name name-style="western"><surname>Afshar</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ameen</surname><given-names>S</given-names> </name><etal/></person-group><article-title>The TRIPOD-LLM reporting guideline for studies using large language models</article-title><source>Nat Med</source><year>2025</year><month>01</month><volume>31</volume><issue>1</issue><fpage>60</fpage><lpage>69</lpage><pub-id pub-id-type="doi">10.1038/s41591-024-03425-5</pub-id><pub-id pub-id-type="medline">39779929</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>Collins</surname><given-names>GS</given-names> </name><name name-style="western"><surname>Reitsma</surname><given-names>JB</given-names> </name><name name-style="western"><surname>Altman</surname><given-names>DG</given-names> </name><name name-style="western"><surname>Moons</surname><given-names>KGM</given-names> </name></person-group><article-title>Transparent Reporting of a Multivariable Prediction Model for Individual Prognosis or Diagnosis (TRIPOD): The TRIPOD statement</article-title><source>Ann Intern Med</source><year>2015</year><month>01</month><day>6</day><volume>162</volume><issue>1</issue><fpage>55</fpage><lpage>63</lpage><pub-id pub-id-type="doi">10.7326/M14-0697</pub-id><pub-id pub-id-type="medline">25560714</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="web"><article-title>What is the JMIR publications data sharing policy?</article-title><source>JMIR Publications - support - KB</source><access-date>2026-08-07</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://support.jmir.org/hc/en-us/articles/360030832631-What-is-the-JMIR-Publications-data-sharing-policy">https://support.jmir.org/hc/en-us/articles/360030832631-What-is-the-JMIR-Publications-data-sharing-policy</ext-link></comment></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="web"><article-title>Implementation report</article-title><source>JMIR Medical Informatics</source><access-date>2026-08-06</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/themes/145-implementation-report">https://medinform.jmir.org/themes/145-implementation-report</ext-link></comment></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>Perrin Franck</surname><given-names>C</given-names> </name><name name-style="western"><surname>Geissbuhler</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lovis</surname><given-names>C</given-names> </name></person-group><article-title>&#x201C;To err is evolution&#x201D;: we need the implementation report to learn</article-title><source>JMIR Med Inform</source><year>2023</year><month>04</month><day>4</day><volume>11</volume><fpage>e47695</fpage><pub-id pub-id-type="doi">10.2196/47695</pub-id><pub-id pub-id-type="medline">37014675</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>Perrin Franck</surname><given-names>C</given-names> </name><name name-style="western"><surname>Babington-Ashaye</surname><given-names>A</given-names> </name><name name-style="western"><surname>Dietrich</surname><given-names>D</given-names> </name><etal/></person-group><article-title>iCHECK-DH: Guidelines and Checklist for the Reporting on Digital Health Implementations</article-title><source>J Med Internet Res</source><year>2023</year><month>05</month><day>10</day><volume>25</volume><fpage>e46694</fpage><pub-id pub-id-type="doi">10.2196/46694</pub-id><pub-id pub-id-type="medline">37163336</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>Liyanage</surname><given-names>A</given-names> </name><name name-style="western"><surname>Irfaan</surname><given-names>S</given-names> </name><name name-style="western"><surname>Moonesinghe</surname><given-names>L</given-names> </name><name name-style="western"><surname>Kasturiaratchi</surname><given-names>K</given-names> </name><name name-style="western"><surname>Perrin Franck</surname><given-names>C</given-names> </name><name name-style="western"><surname>Hussein</surname><given-names>R</given-names> </name></person-group><article-title>Reporting digital health implementations based on the iCHECK-DH guidelines and checklist: development of an interactive toolkit</article-title><source>J Med Internet Res</source><year>2025</year><month>08</month><day>8</day><volume>27</volume><fpage>e74235</fpage><pub-id pub-id-type="doi">10.2196/74235</pub-id><pub-id pub-id-type="medline">40779756</pub-id></nlm-citation></ref></ref-list></back></article>