The Need for Demonstrated Clinical Translational Evidence in Submissions to the IEEE Journal of Translational Engineering in Health and Medicine
Date
Authors
Boyle, Gerard
Forner-Cordero, Arturo
Kalra, Anubha
Kremen, Vaclav
Ponsiglione, Alfonso Maria
Ranji, Mahsa
Sinha, Sharad
Tang, Xiangyang
Yang, Po
Reilly, Richard B
Supervisor
Item type
Journal Article
Degree name
Journal Title
Journal ISSN
Volume Title
Publisher
Institute of Electrical and Electronics Engineers (IEEE)
Abstract
The IEEE Journal of Translational Engineering in Health and Medicine (JTEHM) exists at the intersection of biomedical engineering and clinical practice. Published articles go beyond laboratory proof-of-concept to provide tangible, real-world evidence of translation into clinical settings. This editorial provides the rationale for manuscripts submitted to IEEE JTEHM to demonstrate evidence of clinical translation. It also provides examples of acceptable forms of evidence and offers guidance to authors on how to meet this expectation. Clinical and Impact—By requiring demonstrated clinical translational evidence IEEE JTEHM endeavours to publish high-quality research with scientific novelty and practical clinical impact. This expectation strengthens the journal’s aim to accelerate the adoption of innovative solutions into healthcare systems and ultimately deliver quantifiable benefits to patients.Description
Keywords
4003 Biomedical engineering, 4203 Health services and systems, Translational engineering, clinical translation, clinical validation, clinical endpoints, clinical impact
Source
IEEE Journal of Translational Engineering in Health and Medicine, ISSN: 2168-2372 (Online), Institute of Electrical and Electronics Engineers (IEEE), 14, vi-xi. doi: 10.1109/jtehm.2026.3680558
Publisher's version
Rights statement
Open Access. Under a Creative Commons Licence. CC-BY. IEEE is not the copyright holder of this material. Please follow the instructions via https://creativecommons.org/licenses/by/4.0/ to obtain full-text articles and stipulations in the API documentation.