In an EAEU medicinal-product dossier, the Summary of Product Characteristics (SmPC), patient leaflet and labeling are not final-stage translation deliverables. They are the public expression of the approved regulatory position.
The SmPC defines the official information used by healthcare professionals. The patient leaflet is derived from that approved medical position for the patient. The labeling and pack text must remain consistent with the authorized product, dosage form, strength, storage conditions and other approved information.
For an international manufacturer, the difficult task is rarely writing one Russian text from zero. It is reconciling several sources: global core safety/product information, source-country labeling, the EAEU reference product, the current dossier, pharmacovigilance conclusions, local language versions and the post-approval variation history.
The practical question is:
How do we create one scientifically defensible EAEU product-information baseline and keep every member-state version synchronized as the product changes?
Decision No. 88 defines the EAEU product-information architecture
EEC Council Decision No. 88 establishes the requirements for the SmPC and patient leaflet.
The Rules were substantially revised by Decision No. 18 of 21 February 2025, which entered into force in 2025 and now forms the current product-information framework.
The revised rules confirm a fundamental hierarchy:
approved scientific evidence → SmPC → patient leaflet → labeling/pack implementation.
The patient leaflet should not become an independent version of the medicinal product. It is prepared in accordance with the SmPC and should communicate the same approved benefit-risk position in a patient-appropriate form.
The 2025 revision is more than a formatting update
The EEC stated that the 2025 changes simplified the patient-leaflet format by removing sections that were not useful in practice.
The revision also removed the requirement to perform user testing for previously registered medicinal products, reducing the burden during transition to the EAEU framework.
At the same time, the revised Decision No. 88 strengthened lifecycle traceability and the relationship between reference-product information and generic/hybrid/biosimilar product information.
For a mature portfolio, the current task is therefore not merely to convert an old national instruction into a new template. It is to establish a controlled product-information baseline under the revised rules.
The SmPC is the regulatory master for medical use
The current Decision No. 88 describes the SmPC as the official source of information intended for healthcare professionals for correct prescribing and control of medicinal-product use.
Its content is approved through registration, renewal/confirmation and variation procedures.
A manufacturer therefore should not treat SmPC wording as purely editorial. A sentence can reflect a regulatory conclusion about indication, population, dose, contraindications, precautions, adverse reactions, pregnancy/lactation, pharmacology or use conditions.
Changes to those sections can require scientific justification and, depending on their origin, a formal variation under Decision No. 78.
Product information should be authored from evidence—not translated blindly
A global source text is an important starting point, but it may not match the EAEU regulatory basis exactly.
Differences can arise because:
- the EAEU indication is narrower or broader;
- different strengths or dosage forms are registered;
- the EAEU reference product has different wording;
- a safety change has been implemented at different times across markets;
- the source-country label contains local legal language;
- the EAEU dossier does not include evidence supporting a foreign-market claim;
- shelf life, storage or excipient information differs from the EAEU CMC dossier.
Pharegis therefore uses regulatory authoring, not literal translation.
Every material difference should have a source and rationale.
Generic, hybrid and biosimilar products have a reference-text discipline
The revised Decision No. 88 contains specific rules for generic, hybrid and biosimilar medicinal products.
The applicant is expected to compare the proposed SmPC and patient leaflet with the current information for the original/reference medicinal product and identify and justify relevant differences.
Typical legitimate differences can arise from manufacturer, excipients, shelf life, certain pharmacokinetic/bioavailability differences, product-specific limitations, intellectual-property restrictions or other scientifically justified reasons.
The current rules require a line-by-line comparison in the relevant procedures and a declaration/rationale for differences.
This is materially stronger than saying “our leaflet is based on the reference product”.
The 120-working-day reference-product update rule needs an owner
One of the most important lifecycle provisions introduced in the revised Decision No. 88 concerns generic, hybrid and biosimilar products.
Where relevant changes are made to the SmPC and/or patient leaflet of the original/reference product, the holder of the generic, hybrid or biosimilar authorization is required, in the applicable scenario, to introduce corresponding changes within 120 working days from publication of the updated reference product information in the EAEU register.
This creates a permanent monitoring obligation:
monitor → assess relevance → compare → prepare change → file variation → implement text/pack changes.
For an international portfolio, Pharegis can operate this as a controlled lifecycle process rather than leaving it to ad-hoc local monitoring.
Safety updates connect pharmacovigilance directly to product information
Decision No. 87 requires the pharmacovigilance system to keep product safety information aligned with current scientific knowledge.
A new signal, PSUR/PBRER conclusion, RMP change or regulatory safety action can therefore lead directly to an SmPC/PIL variation.
The regulatory workflow should connect:
safety conclusion → affected SmPC/PIL sections → variation classification → member-state implementation → packaging/labeling impact.
A pharmacovigilance vendor can identify a signal, but regulatory affairs must ensure the approved product information actually changes when required.
SmPC and patient leaflet are controlled full documents—not isolated changed paragraphs
Decision No. 88 requires traceability of changes during expert review and approval of the agreed complete texts.
A strong product-information process therefore maintains:
- approved clean version;
- tracked-change version;
- source/rationale table;
- regulatory sequence/variation reference;
- language versions;
- implementation status by market;
- packaging-artwork impact.
Editing one paragraph in an uncontrolled Word file and emailing it among affiliates is not a lifecycle system.
For products registered in several recognition states, version control becomes particularly important when variations, recognition-state additions and safety changes overlap.
One EAEU scientific core can still require several language implementations
The purpose of the EAEU framework is a harmonized regulatory product position across member states.
That does not remove national-language implementation requirements.
The manufacturer may need a Russian scientific master text, state-language versions for relevant recognition states, country-specific administrative elements and locally compliant packaging layouts.
The correct architecture is therefore:
one controlled scientific core → controlled translations/localizations → controlled pack implementation.
The scientific content should not be independently rewritten by each distributor or local vendor.
Translation quality is a regulatory control issue
Product information contains terminology where small translation differences can materially change meaning.
Dose frequency, contraindication versus precaution, pregnancy wording, adverse-reaction frequency, renal/hepatic dosing and storage instructions are examples where linguistic accuracy alone is not enough.
Pharegis separates translation from regulatory review.
A professional translator can produce linguistically correct text. A regulatory reviewer must verify that the text still expresses the approved scientific and legal meaning.
For multi-state portfolios, terminology should also be standardized across products so that the same regulatory concept is not translated differently from dossier to dossier.
Labeling is a separate regulated layer that must follow the dossier
EEC Council Decision No. 76 establishes the EAEU labeling requirements for medicinal products. Those requirements were further amended in 2025 by Decision No. 32, effective from 12 November 2025.
The labeling workstream should therefore be checked against the current rules rather than a legacy national pack template.
From a lifecycle-management perspective, the key requirement is consistency. The pack should not contradict the approved product name, strength, dosage form, use conditions, storage, shelf life, manufacturer/authorization-holder information, SmPC or patient leaflet.
A scientific variation can therefore create an artwork project even when the variation itself was initiated by pharmacovigilance or CMC.
Packaging should be designed as a supply-chain system
For a multi-country EAEU launch, packaging strategy should be decided before artwork finalization.
Commercial options can include one multilingual pack, country-specific packs, a common primary pack with market-specific secondary packaging, or controlled overlabeling where the applicable rules permit it.
The correct option depends on portfolio volume, language requirements, supply network and expected variation frequency.
A single multilingual pack may reduce SKU complexity but can make every safety change more operationally expensive. Country-specific packs increase artwork/SKU burden but can provide more implementation flexibility.
Pharegis can map those regulatory tradeoffs before the supply chain locks the pack design.
Product-information changes should be classified together with their trigger
The text change itself is not always the primary regulatory event.
Examples:
- new clinical indication → clinical variation + SmPC/PIL/labeling changes;
- new safety signal → safety variation + product-information update;
- new dosage form → registration/lifecycle change + new product information;
- storage change → CMC variation + SmPC/PIL/pack update;
- reference-product safety update → corresponding generic/hybrid/biosimilar change.
This matters for grouping and timing.
The product-information package should be built as a consequence of the underlying regulatory change, not as an unrelated later submission.
User testing should not be commissioned automatically
The 2025 revision removed the requirement for user testing of the patient leaflet for previously registered medicinal products in the relevant context.
That is a direct cost-saving opportunity.
For a new or otherwise applicable product, readability and the current Decision No. 88 requirements still need to be addressed properly.
The practical rule is:
do not commission user testing because an old internal checklist says it is always required. First determine whether the current EAEU rule requires it for this product and procedure.
Where product-information projects most often fail
Common problems include:
- translating a global label without reconciling it to the EAEU dossier;
- allowing SmPC, PIL and pack text to evolve independently;
- failing to monitor the EAEU reference product for generic/hybrid/biosimilar updates;
- missing the 120-working-day lifecycle obligation;
- treating a safety update as a PV document only and not filing the required regulatory change;
- using old national instructions as the master after an EAEU authorization becomes the baseline;
- losing track of clean/tracked versions during recognition-state procedures;
- permitting local distributors to make uncontrolled wording changes;
- finalizing artwork before variation text is stable;
- performing unnecessary user testing for a previously registered product;
- failing to reconcile storage, shelf-life or product configuration with the CMC dossier.
What Pharegis manages in an EAEU product-information project
Typical deliverables include:
- SmPC/PIL/labeling gap assessment against current Decisions No. 88 and No. 76;
- scientific-source and master-text map;
- generic/hybrid/biosimilar reference-product comparison;
- line-by-line difference table and justification;
- regulatory authoring of SmPC and patient leaflet;
- controlled Russian translation/review;
- recognition-state language-version coordination;
- reference-product update monitoring process;
- pharmacovigilance-to-product-information change workflow;
- variation classification/filing coordination;
- labeling/artwork regulatory review;
- multi-country pack strategy input;
- implementation/version tracker across EAEU states.
For international manufacturers, the objective is to maintain one EAEU scientific product identity while allowing the necessary language and packaging execution in each market.
Discuss an SmPC / patient leaflet harmonization project
For an initial assessment, prepare the current EAEU authorization/reference state, approved SmPC/PIL by state, source-country/core product information, reference-product SmPC/PIL where applicable, current Module 2/5 baseline, RMP and recent safety changes, packaging files, recognition states/languages and pending variations.
Pharegis can then identify the authoritative scientific baseline, isolate inconsistencies, determine which changes require regulatory action and create a controlled implementation plan across the relevant EAEU states.
The objective is not to translate product information. It is to keep the approved medical, safety and commercial product identity synchronized across the EAEU lifecycle.
Regulatory basis
- EEC Council Decision No. 88 of 3 November 2016 — Requirements to the SmPC and patient information leaflet.
- EEC Council Decision No. 18 of 21 February 2025 — current major revision of the SmPC/PIL requirements.
- EEC Council Decision No. 76 of 3 November 2016 — EAEU medicinal-product labeling requirements.
- EEC Council Decision No. 32 of 15 May 2025 — 2025 amendments to the labeling requirements, effective 12 November 2025.
- EEC Council Decision No. 78 of 3 November 2016 — registration and variation procedures through which product-information changes are approved.
- EEC Council Decision No. 87 of 3 November 2016 — GVP requirements relevant to safety-driven product-information updates.
Regulatory status reviewed: August 2026.