0
We're unable to sign you in at this time. Please try again in a few minutes.
Retry
We were able to sign you in, but your subscription(s) could not be found. Please try again in a few minutes.
Retry
There may be a problem with your account. Please contact the AMA Service Center to resolve this issue.
Contact the AMA Service Center:
Telephone: 1 (800) 262-2350 or 1 (312) 670-7827  *   Email: subscriptions@jamanetwork.com
Error Message ......
Letters |

Nomenclature in Translational Research

Ian D. Graham, PhD; Jacqueline Tetroe, MA
JAMA. 2008;299(18):2148-2150. doi:10.1001/jama.299.18.2149-a.
Text Size: A A A
Published online

Extract

To the Editor: In his Commentary, Dr Woolf1 commented on the confusion arising from using the term translational research to describe both T1 (moving research findings from “bench to bedside”) and T2 (the translation of results from clinical studies into everyday clinical practice and health decision making) and the need for greater emphasis on T2. We agree with both points.

A unique aspect of the parliamentary mandate for the Canadian Institutes of Health Research is the direction to focus on promoting what is termed knowledge translation. Although this is essentially T2, the definition is more inclusive: “Knowledge translation is a dynamic and iterative process that includes synthesis, dissemination, exchange and ethically sound application of knowledge to improve the health of Canadians, provide more effective health services and products and strengthen the health care system.”1 In this view, translational research ends with the development and testing of the clinical application and does not include its widespread promotion, whereas the knowledge translation process is about identifying solutions to clinical, health services, and population health problems and facilitating their widespread application.

Topics

Sign in

Create a free personal account to sign up for alerts, share articles, and more.

Purchase Options

• Buy this article
• Subscribe to the journal

First Page Preview

View Large
First page PDF preview

Figures

Tables

References

Letters

May 14, 2008
Steven H. Woolf, MD, MPH
JAMA. 2008;299(18):2148-2150. doi:10.1001/jama.299.18.2149-b.
May 14, 2008
Kevin Fiscella, MD, MPH; Nancy M. Bennett, MD, MS; Peter G. Szilagyi, MD, MPH
JAMA. 2008;299(18):2148-2150. doi:10.1001/jama.299.18.2148-b.
CME
Meets CME requirements for:
Browse CME for all U.S. States
Accreditation Information
The American Medical Association is accredited by the Accreditation Council for Continuing Medical Education to provide continuing medical education for physicians. The AMA designates this journal-based CME activity for a maximum of 1 AMA PRA Category 1 CreditTM per course. Physicians should claim only the credit commensurate with the extent of their participation in the activity. Physicians who complete the CME course and score at least 80% correct on the quiz are eligible for AMA PRA Category 1 CreditTM.
Note: You must get at least of the answers correct to pass this quiz.
You have not filled in all the answers to complete this quiz
The following questions were not answered:
Sorry, you have unsuccessfully completed this CME quiz with a score of
The following questions were not answered correctly:
Commitment to Change (optional):
Indicate what change(s) you will implement in your practice, if any, based on this CME course.
Your quiz results:
The filled radio buttons indicate your responses. The preferred responses are highlighted
For CME Course: A Proposed Model for Initial Assessment and Management of Acute Heart Failure Syndromes
Indicate what changes(s) you will implement in your practice, if any, based on this CME course.

Multimedia

Some tools below are only available to our subscribers or users with an online account.

Web of Science® Times Cited: 6

Sign in

Create a free personal account to sign up for alerts, share articles, and more.

Purchase Options

• Buy this article
• Subscribe to the journal

Related Content

Customize your page view by dragging & repositioning the boxes below.

Jobs
brightcove.createExperiences();