Does One SmPC Change Force Retranslation Across 24 EU Languages
- 19 hours ago
- 5 min read
Yes. For a centrally authorised medicine, a single change to the Summary of Product Characteristics (SmPC) pulls the labelling and the package leaflet with it, and every one of the 24 official EU languages has to be updated in step. The edit doesn't stay in the language you touched. It reopens the whole language set, because the SmPC, the labelling, and the leaflet are one linked set of annexes that the European Medicines Agency reviews together.
What a single SmPC edit actually touches
The product information for a centrally authorised product is three documents that move as one: the SmPC (Annex I), the labelling (Annex IIIA), and the package leaflet, or PIL (Annex IIIB). Directive 2001/83/EC sets what each must contain, the SmPC content in Article 11 and the leaflet content in Article 59, and Article 63 requires each national version to be in the official language or languages of the member state where the medicine is sold. Change a contraindication or a dosing line in the SmPC and the leaflet has to reflect it, because the leaflet is derived from the SmPC. So a one-line safety edit in English is never one line of work. It's the same edit, re-expressed, checked, and approved in 24 languages, plus Icelandic and Norwegian for the EEA.
Why the change reopens every language at once
Timing is where the pressure shows. In the centralised procedure, within 5 calendar days of a positive CHMP opinion the marketing authorisation holder submits the final English product information together with translations into the other EU and EEA languages, and each member state then checks its own version during the EMA linguistic review. A variation under Regulation (EC) No 1234/2008 runs through that same review. The EMA's QRD template fixes the format and the standard wording every version has to follow, so a phrase you rendered loosely in one market reads as a divergence the moment a reviewer sets it against the template and the approved English. Miss the window in one language and the whole variation waits.
Where divergence creeps in
The usual failure isn't a clumsy translation. It's 24 versions that were each correct on their own day and no longer agree. Divergence tends to come from four places:
A previous safety update reached some language versions but not others, so the base text you're editing already differs by market.
A national affiliate corrects a leaflet locally to satisfy one authority, and that wording never travels back to the central source.
The same clinical term, hypersensitivity or renal impairment, was rendered two ways across languages because no shared term base held the approved equivalents.
The English source changed after translation had started, and only some languages picked up the revision.
Each of these surfaces at variation review as an inconsistency finding, and the reviewer's remedy is to send it back.
What keeps 24 versions in step
Controlling this is a governance problem before it's a language problem. Four things do most of the work:
A single approved term base, so excipient, posology, and every warning phrase carry one signed-off equivalent per language that a translator cannot quietly override.
Version-locked source control, so all 24 languages branch from the same English revision and no market edits a stale base.
Translation memory tied to the approved product information, so the unchanged bulk of the document is reused word for word and only the delta is retranslated and reviewed.
One central owner of the language set rather than 24 affiliates fixing their own copies, so every correction flows back to source.
This is also the machinery behind the certifications that are non-negotiable for regulated translation, and the reason we treat the term base as the master asset rather than the individual files.
How AD VERBUM handles it
AD VERBUM runs SmPC, labelling, and leaflet updates as one controlled event, not 24 parallel jobs. We hold the approved term base and translation memory for the product, branch every language from one locked English revision, and route each version through independent revision under ISO 17100 before it reaches the QRD comparison. Our infrastructure is EU-hosted and ISO 27001 certified, which matters while the source still carries pre-approval safety data. It's the same discipline we bring to MDR and IVDR device documentation, and it rests on the full certification stack that defines a regulated-industry translation company, tuned here to the EMA variation clock.
Our pharmaceutical 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 the QRD product-information template and Regulation (EC) No 1234/2008 variation handling 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
Does one SmPC change really require all 24 EU language versions to be updated?
Yes. For a centrally authorised product the SmPC, labelling, and package leaflet are linked annexes reviewed together, and Directive 2001/83/EC Article 63 requires each national version to be in the official language or languages of its member state. A change in one cascades to all.
How long do you have to translate a product information variation?
In the centralised procedure the final English product information plus translations reach the EMA within 5 calendar days of a positive CHMP opinion. A variation under Regulation (EC) No 1234/2008 follows the same linguistic review, so the translation window is short and fixed.
What is the QRD template and why does it matter for translation?
The QRD (Quality Review of Documents) template is the EMA's standard structure and wording for the SmPC, labelling, and leaflet. Translations are checked against it, so wording that drifts off the template reads as a divergence and can trigger a review finding.
What is the difference between the SmPC and the package leaflet?
The SmPC (Directive 2001/83/EC Article 11) is the prescriber's reference document. The package leaflet (Article 59) is the patient-facing version derived from it, which is why any SmPC change has to be reflected in the leaflet across every language.
Can a national affiliate just fix its own leaflet?
No. Isolated per-country fixes are the main source of divergence between language versions. Corrections have to return to the central source so all versions stay aligned against the approved English and the QRD template.
How does a term base prevent inconsistent language versions?
A single approved term base holds one signed-off equivalent per language for each clinical term, so hypersensitivity or renal impairment cannot be rendered two ways. Independent revision under ISO 17100 then checks each version before submission.
