Which Pharmacovigilance Documents Need Certified EU Translation
- 3 days ago
- 6 min read
Five pharmacovigilance documents routinely need certified or validated EU translation: individual case safety reports, periodic safety update reports, risk-management-plan summaries, direct healthcare professional communications, and patient-facing safety material. Each carries its own language rule, and drift in any of them turns into a reporting error, a national authority query, or a delayed safety message.
The language obligations sit in Directive 2001/83/EC and Regulation (EC) No 726/2004, with the operational detail in the EMA Good Pharmacovigilance Practices (GVP) modules and the format rules in Commission Implementing Regulation (EU) No 520/2012. Some documents move in English only. Others must reach patients and prescribers in the official language of every member state where the medicine is authorised. Knowing which is which keeps a safety file consistent across 24 languages. AD VERBUM runs this work under ISO 17100 and ISO 27001 with GDPR- and HIPAA-compliant processes, and we handle the same pharmacovigilance flow behind EMA pharma regulatory translation.
1. Individual case safety reports (ICSRs)
An ICSR records a single suspected adverse reaction. Under Directive 2001/83/EC Article 107, a marketing authorisation holder must report serious cases to EudraVigilance within 15 days and non-serious EU cases within 90 days, submitted electronically in the ICH E2B(R3) format. The coded fields are structured, but the case narrative is free text and often reaches you in the reporter's language. That narrative has to be rendered into English without losing dose, timing, outcome, or the causality assessment. Get the narrative wrong and you can misclassify seriousness, which feeds a bad signal into pharmacovigilance analysis. ICSRs also carry patient health data, so they are special-category data under GDPR Article 9, which shapes how the text can be handled and stored.
2. Periodic safety update reports (PSURs)
A PSUR is the periodic benefit-risk review for an authorised medicine, structured under GVP Module VII and Commission Implementing Regulation (EU) No 520/2012. The report itself is submitted in English to the EU PSUR repository and assessed once through the PSUR single assessment (PSUSA) procedure. The translation exposure is downstream. A PSUSA outcome can require changes to the summary of product characteristics and the package leaflet, and those changes then have to appear in every national language where the product is on the market. When the source wording is imprecise, or the downstream updates drift between languages, you end up with safety text that says slightly different things in different countries. Coordinating that parallel production against a fixed deadline is a discipline in its own right, which is why we treat PSUR translation as a scheduled, term-locked workflow.
3. Risk-management-plan summaries
The full risk management plan is a technical document, but its public summary is what most patients ever see. GVP Module V sets the RMP structure, and Directive 2001/83/EC Article 106 requires the summary to be published on the national medicines web portals run by each competent authority. Written in plain language for patients and healthcare professionals, that summary is published per member state, so it needs translation into the official language of each portal. A summary that reads differently in one language misstates the risk-minimisation measures to the public, and because it sits on a regulator's website, the mismatch is easy to spot.
4. Direct healthcare professional communications (DHPCs)
A DHPC is the urgent safety letter that tells prescribers to change what they do. Under GVP Module XV, the text is agreed in English with the competent authority, then translated into the official language of each member state where it will be distributed. National authorities review those translations, often inside about 48 hours, before the letter goes out. Speed and accuracy pull against each other here. A slow translation delays a warning that clinicians need now, and a wording error in an action instruction can change prescribing behaviour in the wrong direction. This is the document type where a single mistranslated dose threshold does real harm.
5. Patient-facing safety material
When a safety review lands, the package leaflet, patient alert cards, and risk-minimisation educational material all have to follow. The package leaflet and labelling must appear in the official language or languages of each member state under Directive 2001/83/EC Article 63, and the text must be legible and understandable under the readability expectation carried by the QRD template. An error in dosing, a contraindication, or a warning is a safety and readability non-compliance at once, and it can escalate to a variation or a corrective action. The same care that protects a package leaflet from triggering an EMA variation or recall applies to every patient-facing safety document.
How AD VERBUM handles pharmacovigilance translation
Pharmacovigilance translation fails in two places, the source text and the audit trail, so we build against both. AD VERBUM keeps a certified process around every one of these document types, so the narrative that reaches EudraVigilance and the leaflet that reaches a patient carry the same meaning as the source. What we bring to a PV file:
ISO 17100 certified translation with independent second-linguist revision, so no adverse-event narrative or warning ships on a single pair of eyes.
ISO 27001 certified, EU-hosted infrastructure for GDPR Article 9 patient data, with no reliance on public cloud tooling for core processing.
Pharmacovigilance and regulatory subject-matter linguists who know EudraVigilance, PSUSA, and QRD conventions, not generalist translators.
Term-base governance across the summary of product characteristics, package leaflet, and RMP summary, so a change in one document stays consistent across every language version.
Our pharmacovigilance translation services
Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as GVP pharmacovigilance reporting and Commission Implementing Regulation (EU) No 520/2012 applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.
FAQ
Do ICSRs need translation?
Yes where the case narrative arrives in a language other than English. A marketing authorisation holder reports to EudraVigilance in the ICH E2B(R3) format under Directive 2001/83/EC Article 107, and the narrative must be rendered into English without losing dose, timing, or causality. Because an ICSR carries patient health data, it is special-category data under GDPR Article 9.
In which language is a PSUR submitted?
The PSUR is submitted in English to the EU PSUR repository and assessed through the PSUR single assessment (PSUSA) under GVP Module VII. The translation work comes after, when a PSUSA outcome changes the summary of product characteristics or the package leaflet and those changes need every national language.
Does the RMP summary have to be translated?
Yes. GVP Module V sets the plan structure, and Directive 2001/83/EC Article 106 requires the public summary to appear on national medicines web portals. Each portal publishes in its own official language, so the plain-language summary needs translation per member state.
How fast must a DHPC translation be ready?
Very fast. Under GVP Module XV the text is agreed in English, then translated into each member state's official language, and national authorities often review the translation within about 48 hours before distribution. A delay holds up a safety message that prescribers need immediately.
What language rule applies to the package leaflet?
Directive 2001/83/EC Article 63 requires the package leaflet and labelling in the official language or languages of each member state where the medicine is placed on the market, and the text must be legible and understandable under the readability expectation carried by the QRD template.
What does certified translation mean for pharmacovigilance documents?
It means a documented, auditable process with qualified linguists and independent revision. AD VERBUM works to ISO 17100 for the translation process and ISO 27001 for data security, with GDPR- and HIPAA-compliant handling of the patient data that ICSRs and safety reports contain.
