Key takeaways
- Under EU GVP Module VI, individual case safety reports should be completed and submitted in English unless otherwise requested.
- Where a reporter describes a reaction in another official EU language, the marketing authorisation holder must provide the original verbatim text and an English summary.
- Serious valid ICSRs must be submitted within 15 days and non-serious ones within 90 days of receipt, under Articles 107(3) and 107a(4) of Directive 2001/83/EC.
- The reporting clock starts when any company staff or contractor receives the minimum information, so translation time counts against the deadline.
- On request, the marketing authorisation holder must supply a full English translation of a literature article that triggered a case report.
This article is for drug safety officers, qualified persons for pharmacovigilance and the vendors who support them. It explains where translation sits in adverse event reporting, what EU guidance says about language, and how to build a translation workflow that keeps up with regulatory deadlines.
Pharmacovigilance is the science and activities relating to detecting, assessing and preventing adverse effects of medicines. Safety information arrives from patients, doctors, pharmacists and published papers in many languages, and most of it has to be read, coded and reported in English.
What is pharmacovigilance translation?
Pharmacovigilance translation is the translation of safety information so that it can be assessed, coded and reported to regulators. The core unit is the individual case safety report (ICSR), the structured report of one or more suspected adverse reactions in one patient.
Typical source material includes call-centre notes, emails and letters from patients, healthcare professional reports, follow-up questionnaires, hospital discharge letters, and articles in local medical journals. Each needs a translation that keeps the reporter's meaning exactly, including uncertainty: "I think the rash started after the second tablet" must not become "the rash started after the second tablet".
What does GVP Module VI say about languages?
The EU Guideline on good pharmacovigilance practices (GVP) Module VI, Rev 2, which EMA lists with a legal effective date of 22 November 2017 on its GVP page, sets out how languages are handled in ICSRs. Its section on handling of languages states:
"Where suspected adverse reactions are reported by the primary source in narrative and textual descriptions in an official language of the Union other than English, the original verbatim text and the summary thereof in English shall be provided by the marketing authorisation holder." (EMA, GVP Module VI, section VI.C.6.2.2.11)
The guideline adds that the ICSR "should be completed and submitted in English if not otherwise requested", and that for suspected adverse reactions originating outside the EU, "English shall be used in the ICSR". Additional documents held only in a local language "should only be translated if requested by the receiver".
In the ICH E2B(R3) electronic format, the guideline points to separate data elements for the reporter's words in their native language, the language used, and the English translation, as well as the case summary. Translators therefore often deliver two outputs: a faithful translation of the reporter's text and an English narrative.
How do reporting deadlines affect translation?
Reporting deadlines make pharmacovigilance one of the most time-critical areas of medical translation. GVP Module VI, citing Articles 107(3) and 107a(4) of Directive 2001/83/EC, requires serious valid ICSRs to be submitted "within 15 days from the date of receipt" and non-serious valid ICSRs within 90 days.
The clock starts at day zero, when the minimum information reaches any personnel of the marketing authorisation holder, "including medical representatives and contractors". The guideline also notes that the timelines "are based on calendar days". A translation that takes a week because it arrived on a Friday uses half of the time allowed for a serious case.
Which safety documents need translating?
Different safety documents carry different translation requirements and urgency. The table summarises common cases under GVP Module VI.
| Source material | Typical requirement | Translation focus |
|---|---|---|
| Spontaneous report from an EU patient or professional in another EU language | Original verbatim text plus English summary; ICSR in English | Faithful rendering of the reporter's words, with no interpretation |
| Report originating outside the EU | English used in the ICSR | Complete English translation of the relevant content |
| Article in non-English medical literature | Comprehensive English summary in the case narrative; full English translation on request of EMA | Accurate medical terminology and study details |
| Supporting documents in a local language | Translated only if the receiver requests it | Fast turnaround once requested |
| Follow-up information | Same rules as the initial report | Consistency with earlier translations of the case |
Medical devices follow a separate vigilance system. Under Article 89(8) of the EU Medical Device Regulation, field safety notices must be issued in the official language or languages determined by the Member State where the corrective action is taken. Our article on EU MDR language requirements covers this in more detail.
How does translation interact with MedDRA coding?
Adverse events are coded with MedDRA, the Medical Dictionary for Regulatory Activities, a standard medical terminology used in regulatory reporting. GVP Module VI says reports "should include the verbatim text as used by the primary source or an accurate translation of it", and recommends using "the translation of the terminology in the local language to code the verbatim text" where applicable.
For translators, this means precision over style. If a reporter writes "palpitations", the translation must not become "tachycardia", which is a different MedDRA concept. If the reporter's wording is vague, the translation should stay vague and add a translator's note, rather than guess.
How to set up a pharmacovigilance translation workflow
- Agree service levels by seriousness. Define faster turnaround for potentially serious cases, including weekend cover.
- Pre-approve translators with medical backgrounds and a confidentiality agreement, for every language your products generate reports in.
- Use a secure transfer route. Case documents contain special category health data and must not travel by unsecured email.
- Provide a glossary of product names, indications and company-specific terms.
- Define the output format: verbatim translation, English summary, or both, with translator notes for ambiguities.
- Record timestamps for receipt and delivery, so translation time is visible in audits of day-zero compliance.
Common mistakes in pharmacovigilance translation
- Interpreting instead of translating. Adding a diagnosis the reporter did not make distorts causality assessment.
- Dropping hedges and negations. "No fever" and "possibly linked" carry clinical weight.
- Using unchecked machine translation. See our article on machine translation in healthcare for why safety-critical text needs a human check.
- Losing the original. Keep the source-language text with the case, because a Member State or EMA may request it.
- Inconsistent follow-up translations. Different translators rendering the same symptom differently can create apparent new events.
Pharmacovigilance is one of several regulated medical translation areas covered in our medical and pharmaceutical translation guide. For the skills safety translators need, see why medical translation needs subject-matter experts.
How TranslationWorks can help with pharmacovigilance translation
TranslationWorks is a UK-based translation agency that translates adverse event reports, follow-up correspondence and safety literature through native-speaking professional linguists in more than 150 languages. Our medical and pharmaceutical translation service uses human translators with medical knowledge and works remotely with safety teams and service providers.
Because case documents contain health data, our ISO 27001 registration and Cyber Essentials certification are relevant, alongside ISO 17100 translation services and ISO 9001 quality management. Tell us your languages, expected volumes and turnaround needs, and request a free quote for safety translation; we reply within 24 hours.
