- What makes SmPC translation different from other pharmaceutical documents
- Regulatory requirements by approval pathway
- Common problems in SmPC translations and how to avoid them
- Managing multi-language SmPC submissions at scale
- SmPC translation with M21Global
- Related Services
- Frequently Asked Questions
The Summary of Product Characteristics is one of the most tightly regulated documents in pharmaceutical submission. A terminology error, a divergence from the approved reference text, or a formatting inconsistency in a single language version can trigger a review cycle that delays the entire dossier. For regulatory affairs teams managing multi-country submissions, SmPC translation is a process risk, not an administrative task.
What makes SmPC translation different from other pharmaceutical documents
The SmPC follows a fixed structure defined by the QRD (Quality Review of Documents) template published by the EMA. Each section, from Section 1 (name of the medicinal product) through Section 10 (date of revision), has a prescribed format and content type. The translator does not have latitude to paraphrase, reorganise, or substitute terms with clinical synonyms, however natural the alternative might seem.
Terminology must align with the current version of MedDRA (Medical Dictionary for Regulatory Activities) for adverse reactions, the ATC classification for therapeutic indications, and the dosage conventions recognised by the competent authority in each target market. Any deviation from these references is flagged during assessment.
The approved SmPC in the reference language (typically English for centrally authorised products) is the source against which all translated versions are evaluated. If a translated version uses a term that does not correspond to the preferred MedDRA term in the target language, or if a dosing instruction has been rendered with a different clinical meaning, that version will require correction before the submission proceeds.
Regulatory requirements by approval pathway
The approval pathway determines which language versions are required and who validates them.
Centralised procedure (EMA): the marketing authorisation is granted in English, French, and German. The marketing authorisation holder (MAH) is responsible for providing translations into the official languages of all Member States where the product will be marketed, prior to commercialisation in each country.
Mutual recognition procedure (MRP) and decentralised procedure (DCP): each participating Member State requires the SmPC in its official language. The reference member state (RMS) and concerned member states (CMS) may have specific requirements regarding file format and submission method for linguistic versions.
National procedure: submission goes directly to the national competent authority. In Germany, that is the BfArM or PEI depending on product type. In France, the ANSM. Requirements for translation format and delivery may differ from centralised procedure standards.
Across all pathways, translated SmPCs must be delivered in an editable format compatible with the current QRD template. M21Global's pharmaceutical translation services cover all major European approval pathways, including ongoing QRD template updates and multi-country simultaneous delivery.
Common problems in SmPC translations and how to avoid them
Most deficiencies identified during regulatory review fall into three categories.
Incorrect MedDRA terminology. Adverse reactions must use preferred MedDRA terms in the version current at the time of submission. Using common clinical terms, even when they are medically accurate, constitutes a non-conformity. Translators must have access to the current MedDRA browser in the target language and understand how to apply it.
Divergence from the reference SmPC. When a translation is produced from an outdated version of the source text, or when the translator is not informed of changes made after the previous revision, the translated version falls out of alignment. This is particularly critical for Type II variations, which involve significant changes to the safety profile.
Unintended adaptation of dosing instructions. Doses, administration intervals, and special population data must be translated literally. The SmPC is written for healthcare professionals. Simplifying language for general readability, even with good intention, introduces discrepancies that reviewers will identify.
The Package Leaflet (PL), which is written for patients and subject to readability testing, follows different linguistic rules. When both documents need to be translated as part of the same submission, it is important to establish separate workflows with separate reviewers. Conflating the two risks importing the SmPC's technical register into the PL, or, conversely, softening SmPC language in ways that are not permitted. This applies equally to drug labelling translation, where the target audience and regulatory requirements differ from those of the SmPC.
Managing multi-language SmPC submissions at scale
A European submission frequently requires translations into 10, 15, or more languages simultaneously. Without a controlled process, this creates terminology inconsistencies across language versions that are difficult to trace and expensive to correct.
The foundation is a product-specific translation memory built from the approved reference SmPC. Each new or modified segment is translated by a specialist with documented experience in pharmaceutical regulation, then reviewed by a second specialist before a terminology consistency check against integrated MedDRA glossaries in the CAT environment.
For variations and renewals, the process applies only to modified sections. This reduces both time and cost while maintaining full version traceability. The same version control logic applies to other regulatory documents within the same submission, including clinical trial protocol translations, where audit trails and change documentation are equally critical.
Deadlines in a regulatory submission are fixed. A delay in delivering translated SmPCs delays the complete dossier. Working with a translation provider that understands DCP and MRP timelines, and that has the capacity to mobilise specialist teams across multiple language pairs simultaneously, is a functional requirement for any MAH managing European market access.
SmPC translation with M21Global
M21Global has over 20 years of experience in pharmaceutical and regulatory translation, with ISO 17100:2015 certification from Bureau Veritas. The team includes translators with backgrounds in pharmaceutical sciences or medicine and direct project experience across EMA centralised procedures and national submissions in Portugal, Spain, France, Germany, and other European markets. Terminology assets are maintained by product and client, with full audit trails.
For submissions with defined regulatory deadlines, a quote request should include the number of target languages, the approval pathway, and the submission deadline. Request a quote for SmPC translation today and receive a detailed proposal with timelines and methodology.
Related Services
Request a free medical translation quote
- Request a free medical translation quote
- Medical Device Documentation Translation Mdr Compliance
- Translating Clinical Trial Protocols Regulatory Submission
- Drug Labeling Translation
Frequently Asked Questions
Does an SmPC translator need a pharmaceutical qualification?
There is no explicit legal requirement for a formal pharmaceutical degree, but regulatory authorities expect translations that use correct MedDRA terminology and align precisely with the approved reference SmPC. In practice, this level of accuracy requires translators with documented experience in pharmaceutical regulation, not general medical translation.
Which languages are mandatory for an SmPC submitted under the centralised procedure?
The EMA issues the marketing authorisation in English, French, and German. The MAH is responsible for providing translations into all official EU languages for any Member State where the product will be marketed, prior to commercialisation in that country.
What is the difference between an SmPC and a Package Leaflet for translation purposes?
The SmPC is addressed to healthcare professionals and uses strict technical terminology regulated by MedDRA and QRD template requirements. The Package Leaflet is addressed to patients, must pass readability testing, and uses plain language. They are separate documents with different linguistic requirements and should be managed as separate translation projects.
Can previous SmPC translations be reused for variations or renewals?
Yes, through product-specific translation memories. Sections that have not changed can be applied directly from the existing translation memory, and only modified sections require new translation. This reduces cost and turnaround time, but requires that original files are documented and version-controlled.
What file format is required for SmPC submission to European regulatory authorities?
Translated SmPCs must be delivered in an editable format compatible with the current EMA QRD template, typically a structured Word document. The specific format requirements may vary between the centralised procedure and national procedures, so the MAH should confirm the accepted format with the relevant competent authority before submission.
