Clinical Trial Translation: Documents, Rules and Process
Clinical trial translation is the translation and cultural adaptation of study materials, from the protocol to the informed-consent form to patient diaries, so that every participant and site can understand them. In the U.S., the core test is set by the FDA: consent information must be in a language the participant can comprehend. For a trial that includes Hungarian-speaking sites or participants, that means qualified medical translators, a controlled process and a clear record of what was done. This guide explains what to translate, which rules apply, how the process works and how to brief a translator.
TL;DR
FDA expects informed-consent information, oral or written, to be in a language and at a level the participant or their legally authorized representative can comprehend.
Protocols, investigator brochures, consent materials, CRFs, diaries, clinical outcome assessments (COAs) and recruitment ads are the documents that most often need translation.
Patient-facing questionnaires usually need more than translation: forward translation, independent back-translation, reconciliation and testing with the target population.
Give the translator a glossary, the source files, the approved prior versions and the regulatory context before work starts, and ask who reviews the final text.
We translate Hungarian-English, German-Hungarian and French-Hungarian medical content. Per-word rates start at €0.05 for translation into Hungarian.
Table of Contents
What clinical trial translation covers
It is the translation of study-related materials for use in multilingual research. The word “clinical” matters. These texts are not marketing copy. A mistranslated dosing instruction, an eligibility criterion that shifts in meaning or a consent sentence that a lay reader cannot follow can harm a participant or compromise the data.
Two audiences read these texts, and they need different things:
Participants need plain, accurate language at a comprehensible level. FDA’s informed consent guidance says information given to a subject or legally authorized representative must be in a language they can comprehend, including an explanation of scientific and medical terms.
Research teams, ethics committees and regulators need terminology that is consistent across every document, so that the protocol, the consent form and the case report forms all describe the same procedure in the same words.
The scope is wider than recruitment and consent. A 2026 commentary in the journal Trials argues that language support must be considered across the whole trial lifecycle, not only at the point of enrollment, to protect equity and participant safety. That includes safety letters, follow-up questionnaires and results summaries.
Which documents need translation
The ICH GCP list of essential records, effective 23 July 2025, names the documents a trial must keep. Several of them are the ones most often translated:
Document | Who reads it | Typical translation concern |
Protocol and amendments | Investigators, site staff, ethics committee | Exact procedural and eligibility wording; consistent terminology across versions |
Investigator’s brochure | Investigators | Dense pharmacology and safety data; units and numbers |
Informed-consent form and information sheet | Participants, ethics committee | Reading level, plain language, explained medical terms |
Short-form consent | Participants with limited English | Must be written in a language the participant understands |
Case report forms (CRFs) | Site staff | Field labels that match the database |
Patient diaries and COAs | Participants | Linguistic validation, not just translation |
Recruitment advertisements | Public | Cultural fit, no promises the protocol does not make |
Instructions for the investigational product or device | Participants, pharmacists | Unambiguous steps; safety warnings |
Not every document needs a full translation in every trial. Which ones do depends on the sponsor, the ethics committee and the funder. A 2013 study of 60 U.S. institutional review boards found that committees often struggle to decide when to require translation of consent forms and study materials, weighing participant autonomy and justice against practical costs. The practical lesson: ask your IRB early, and put the answer in writing.
What U.S. rules say about translated consent materials
FDA: comprehension is the standard
FDA regulations do not name a specific translation method. They set an outcome: the participant must understand. The agency’s guidance for IRBs and investigators says oral and written consent information must be comprehensible, and it is explicit that scientific and medical terms need explaining.
There is also a route for participants who do not read English. When a short form is used under 21 CFR 50.27(b)(2) and 45 CFR 46.117(b)(2), the same guidance states that the short form must be written in a language the subject understands, and an impartial witness, such as an independent interpreter, must be present for the oral presentation.
NIH: respect for persons
The NIH IRB treats this as an ethical point as well as a regulatory one. Its guidance on non-English-speaking participants says that giving research information in a language the participant cannot understand violates both the ethical obligation of respect for persons and the requirement for understandable language.
NIAID DMID: certified translations
Funders can be stricter than the baseline. Under a policy effective 23 May 2024, NIAID’s DMID requires that, for research it supports, non-English subject-facing documents and documents communicating safety or protocol procedures have an accurate certified English translation. A translation equivalence form that summarizes a document may be accepted instead, but only with approval from DMID staff.
This matters for Hungarian work in both directions. Source documents written in Hungarian at a site may need certified English versions for a U.S. sponsor, and U.S. consent forms need Hungarian versions for participants.
University policies on bilingual staff
Some teams are tempted to use a bilingual coordinator instead of a translation provider. Institutional policies treat this as an exception with conditions. Duke University’s IRB policy, dated 31 May 2024, says that when bilingual staff are used, forward and back-translations are required, along with an attestation by the Principal Investigator of the staff members’ bilingual abilities. Check your own institution’s policy, because it may differ.
Translation versus linguistic validation
These are two different jobs, and mixing them up is a common source of delay.
Translation moves a document from one language to another, accurately and in the right register. A protocol, an investigator’s brochure and a consent form are translated and then proofread or reviewed.
Linguistic validation applies to instruments that measure something, such as patient-reported outcome (PRO) questionnaires. The PRO Consortium defines it as assessing and confirming the conceptual equivalence and content validity of translations, which protects data integrity when a measure is used globally.
FDA’s patient-focused drug development materials describe the typical sequence as forward translation, back-translation by an independent linguist, reconciliation by a third party, and testing with the target population, known as cognitive debriefing. Psychometric validation often follows to confirm the translated instrument keeps its reliability and validity. The same document points sponsors to the ISPOR principles for translating and culturally validating COAs.
Two published examples show what testing looks like in practice:
A 2020 study of the PRO-CTCAE in Simplified Chinese translated the items, ran cognitive interviews, and revised items that troubled 20% or more of participants.
A 2008 study of the Reflux Disease Questionnaire translated it into Norwegian and Swedish, tested it with patients and back-translated it into English to check that content and clarity were preserved.
For electronic instruments, there is another layer. The ISOQOL TCA-SIG’s 2025 recommendations say translation, cultural adaptation and electronic implementation of eCOAs should not be treated as unrelated processes, and they include an electronic language feasibility assessment. In plain terms: a Hungarian string that fits on paper may not fit on a phone screen, so check this before you lock the build.
What goes wrong: an inspection example
An FDA review document describes a September 2021 inspection of a foreign site. The inspectors cited the site for not conducting studies under good clinical practice. The consent documents were not at a comprehensible level, one translation was not direct, and another added explanations and terminology that differed from the English.
The case is useful because it shows both failure modes. A translation can be too literal for a lay reader, or it can drift from the approved source by adding its own explanations. A good translator avoids both: the text stays faithful to the approved English, and where a term needs explaining, the explanation is agreed in advance and goes into the source document first.
A workable process for a Hungarian project
Agree the scope. List every document, its version and its audience. Decide with the IRB or sponsor which items need full translation, which need certified translation and which need linguistic validation.
Freeze the source. Translate approved, final text. Changes after translation start create rework and version mismatches.
Build a glossary. Include the study drug, procedures, endpoints, abbreviations and any terms the sponsor already uses. Add approved Hungarian terms from earlier studies if they exist.
Translate with a translation memory. CAT tools keep terminology consistent across the protocol, consent form and CRFs, and they make amendments cheaper because unchanged sentences are reused.
Review independently. A second qualified person checks the Hungarian against the source, and for patient-facing material a lay reader checks comprehension.
Back-translate or validate where required. Use the forward, back-translation, reconciliation and debriefing sequence for COAs and any document your ethics committee flags.
Document everything. Keep the translator’s details, version numbers and review records for the trial master file.
Plan for amendments. Protocol changes will come. Send tracked changes, not a new file, so only the altered text is retranslated.
Reading level matters as much as vocabulary
A consent form can be correct and still fail. FDA’s comprehension standard applies to the participant, not to the investigator. A Hungarian consent form should use everyday words, short sentences and an explanation for terms such as randomization or placebo. If the English source is too dense, raise that with the sponsor before translating, because the translation will inherit the problem.
Interpretation is not translation
Written translation alone only partly closes the language gap. The 2026 Trials commentary argues for a broader strategy that includes multilingual staff, appropriate interpretation and early planning to build trust and support truly informed consent. It also notes that multilingual research teams help with culturally sensitive engagement and with recruiting and retaining underserved groups. Budget for interpreters at consent visits and for translated materials, not one or the other.
Clinical documents punish approximation. When I translate a protocol or a consent form, I am not looking for a Hungarian sentence that merely sounds right. I am checking that the same term means the same thing on page 3 of the protocol, in the CRF and in the diary a participant fills in at home. That is why we work the way we do. One experienced translator handles the project from start to finish, with subject-matter knowledge of medical and legal terminology and current CAT tools. A single person owning the terminology means fewer inconsistencies between documents, and no hand-offs where meaning gets lost. Trials also run on schedules that do not respect office hours. Amendments arrive late, a site needs a corrected consent form before a visit, and a sponsor asks for something overnight. We are available beyond regular business hours for urgent needs, and we set realistic deadlines we then keep. Confidentiality is part of the job from the first file: study documents are sensitive, and we handle them that way. Our advice to sponsors and CROs is simple. Send the glossary and the approved source early, tell us who reviews the final text, and let us flag unclear source sentences before they become unclear Hungarian. Bernadett
Our perspective
Choosing a translation provider
Whatever route you take, ask these questions. Providers come in several types: large multi-language agencies, specialist life-science agencies, in-house CRO language teams and independent medical translators. Judge each on the same points.
Subject expertise. Has the translator worked on medical and regulatory texts? Can they explain the terms in your protocol?
Process. Is there a documented review step, and is a translation memory used? Is linguistic validation offered separately where you need it?
Terminology control. Will they build and maintain a glossary across documents?
Confidentiality. How are files stored and shared? Our guide to protecting sensitive documents in translation covers the questions to ask.
Availability. Who answers when an amendment lands at 6 p.m.?
Records. Can they supply the documentation your trial master file needs?
For documents that include chemical or product safety information, such as investigational product handling, see how we approach safety data sheet translation. For patient education modules and training for site staff, our notes on e-learning translation apply.
What it costs
Most translation is priced per source or target word. Our published starting rates are €0.05 per word for translation into Hungarian and €0.07 per word for translation into English, German or French. Machine translation post-editing starts at €0.04 per word for full post-editing and €0.03 per word for light post-editing. Localization is quoted per project.
These are starting rates. The final quote depends on the document type, its complexity, the deadline and the volume. Extra steps such as back-translation, independent review or linguistic validation add to the scope, so list them in your request.
A word on machine translation. Post-editing can speed up high-volume, repetitive material such as site-level logistics documents or large sets of similar forms. For participant-facing consent materials and COAs, ask your IRB or sponsor what level of human review they require, and choose full post-editing or standard translation accordingly.
Work with us on your Hungarian trial documents
If your study involves Hungarian sites or participants, we translate between Hungarian and English, and between Hungarian and German or French, with medical terminology and CAT-tool consistency built into the workflow. Send us the source files, the deadline and any glossary or previous versions, and we will scope the work and quote it.
See our translation and post-editing services and starting rates to request a quote.
FAQ
What translation services are available for clinical trials?
The main services are document translation (protocols, consent forms, brochures, CRFs), certified translation where a funder or committee requires it, linguistic validation of questionnaires and COAs, interpretation at visits, and post-editing for large volumes. Which ones you need depends on the document and on what your IRB or sponsor requires.
Does the FDA require certified translations of consent forms?
The FDA guidance sets a comprehension standard: information must be in a language the subject or representative can understand. It does not prescribe one method in the sources we reviewed. Some funders go further: NIAID’s DMID policy requires certified English translations of certain non-English documents. Confirm with your IRB and funder.
Can a bilingual staff member translate the consent form?
Some institutions allow it as an exception. Duke’s policy, for example, requires forward and back-translations plus a PI attestation of the staff members’ bilingual abilities. Your own IRB’s policy governs, so ask before you rely on this route.
What is the difference between translation and linguistic validation?
Translation converts a text into another language. Linguistic validation confirms that a translated questionnaire measures the same concept as the original. It uses independent back-translation, reconciliation and testing with people from the target population, and it applies to PRO and other COA instruments.
Which documents should I translate first?
Start with what participants see and what the ethics committee reviews: the consent form and recruitment materials. Then handle the protocol, CRFs and diaries. Freeze the source text first, so you translate once.
Sources
FDA: Informed Consent guidance for IRBs, clinical investigators and sponsors
Trials (2026): Translation and interpreting services across the clinical trial lifecycle
ICH GCP: Essential records for the conduct of a clinical trial
How US institutional review boards decide when researchers must translate study documents
ISOQOL TCA-SIG: Principles of good practice for translation of electronic COAs
Recommended
Comments