Structure of the Registration Dossier in Belarus

1. Key takeaways

The registration dossier in Belarus — in the Russian original, регистрационное досье — is not a matter of bundling existing documents; it is prepared item by item against the list prescribed in the annex to Ministry of Health Resolution No. 55. The annex is a two-layer instrument: it enumerates the documents that make up the dossier and states the requirements each of those documents must satisfy. Both layers bind. A missing item is returned; an item that exists but does not meet the stated requirements is returned as well. Two structural facts frame the planning work. First, the national dossier is not the same construct as the Union dossier — the Union pathway organises its file under EEC Council Decision No. 46, so a dual-track company maintains two index systems, not one. Second, the dossier is a living object: later changes to names, production sites and labelling are made by amending the same dossier, because Resolution No. 55 expressly covers amendments to the dossiers of registered products. Designing the file for maintainability from the first filing is therefore not optional bookkeeping — it is what keeps every later change cheap.

2. Legal basis

3. Expert insights

Insight 1: The annex to Resolution No. 55 is a two-layer structure — list plus requirements. Public sources show that the annex to Resolution No. 55 does more than enumerate the documents of the registration dossier: it also prescribes requirements for those documents. This changes the standard of preparation. The question is never merely whether a document exists in the file; it is whether that document satisfies whatever the annex says it must contain — its form, its issuing authority, its language, its currency, its scope. A certificate that exists but is expired, or a description that exists but omits a mandated section, fails even though the checklist of file names looks complete. Self-checking must therefore walk through the requirements line by line, verifying each document against its stated criteria, rather than ticking file names off a list. Companies that adopt this discipline at the first filing find that later filings and amendments reuse the same checklists with almost no modification.

Insight 2: The national dossier and the Union dossier are not one and the same. The Union pathway organises its file under the format established by Decision No. 46; the national pathway organises it under the annex to Resolution No. 55. The two differ in structure, in language expectations and in the emphasis placed on particular supporting documents. Assuming that a single dossier can serve both tracks is a recurring and expensive mistake: the file built for one review gets returned or patched repeatedly when presented to the other. Dual-track companies should maintain two index systems from the outset — one per pathway — and explicitly map which underlying documents are shared between the two and which are pathway-specific. The shared core (quality system certificates, test reports, clinical evaluation) can be prepared once with care; the divergent wrappers must be built separately. The indexing itself should record, for each item, which pathway demands it and in which version.

Insight 3: The maintainability of the dossier must be designed in advance. A registration dossier is not a one-time artefact. Subsequent changes to the product name, the production site, labelling and the instructions for use are all made by amending the same dossier — Resolution No. 55 expressly governs amendments to the dossiers of registered products. If the original file is assembled as an unversioned pile of PDFs with ad hoc naming, every later amendment starts with an archaeology exercise: reconstructing what the current registered state actually is. The fix is cheap at the start and impossible to retrofit cheaply later. Number documents, version them, and keep an index that reflects the currently registered state of the dossier, so that an amendment is a delta against a known baseline. Companies that did this from day one process amendments in weeks; those that did not spend the first weeks of every change project merely reconstructing their own file.

Insight 4: Language is a hard acceptance threshold for the dossier. Application documents must be submitted in Russian or Belarusian (see the dedicated article on document and labelling language in this series). Language is not a translation-quality nicety that can be fixed during review; it is a question of whether the dossier is accepted at all. A technically excellent file submitted in the wrong language never reaches substantive review. The practical corollary is that translation and terminology work belong inside the document preparation phase — started while the source documents are being drafted, with a terminology table fixed before translation begins — not bolted on after the dossier is finalised. Rushed post-hoc translation produces inconsistent terms across documents, and inconsistent terms trigger corrections that consume review time the company cannot afford under the 90-calendar-day limit.

4. Practical recommendations

1. Self-check against the requirements, not against file names. Break the requirements for each document in the annex to Resolution No. 55 into discrete check items and verify each one, rather than ticking documents off a name list.
2. Establish dossier indexing and versioning rules. Design numbering and version management at first registration so that every later amendment operates against a known, indexed baseline.
3. Prepare two index systems for dual-track projects. Build separate indexes for the national and Union pathways, and record explicitly which underlying documents are shared and which are pathway-specific.
4. Move language compliance upstream. Schedule translation and terminology unification inside the document preparation phase, not after the dossier is finalised.

5. Verification checklist

• □ Self-check performed against the requirements in the annex to Resolution No. 55 (not merely against file names)
• □ Dossier numbering and version management rules established
• □ For dual-track projects, separate national and Union indexes built
• □ Language compliance completed during the document preparation phase
• □ Dossier structure designed for change (amendable)

Regulatory information verified as of 2026-10-30.

On the Eurasian Economic Union market, GRZAN’s core capabilities concentrate on three points. First, distinguishing the applicable conditions and remaining time windows of the two pathways — Union-wide registration versus national registration in each member state: the national registration procedure for medical devices in Belarus has been switched wholesale by Council of Ministers Resolution No. 211 of 2026-04-28 (state register No. 6-1/55925, effective 2026-05-01), which compressed the total time limit for preliminary technical works to 90 calendar days, closed the list of such works and prohibited the organising body from expanding it, while the window for filing applications under the national procedure treats 2027-12-31 as the critical cut-off — pathway selection must therefore be decided in step with the time window. Second, authorised representative services: GRZAN can act as the manufacturer’s statutory representative in Belarus, undertaking registration filings, responses to technical queries, registration dossier amendments and post-market reporting obligations, and has synchronised its coordination mechanisms after Council of Ministers Resolution No. 378 of 2026-07-27 (effective 2026-07-30) transferred adverse-event functions to the state organisation for pharmaceutical supervision. Third, quality system and testing support: assistance in establishing a quality management system conforming to ISO 13485, and in organising technical documentation according to the target pathway — the national pathway follows the annex to Ministry of Health Resolution No. 55, while the Union pathway follows EEC Council Decision No. 46.

For business inquiries: info@grzanglobal.com