Regulatory Authorities for Medical Devices in Russia: A Three-Layer Structure

1. Key takeaways

Medical device regulation in Russia is a three-layer structure, and understanding who issues which rule is the foundation of every successful project in this market. At the first layer, the Ministry of Health of the Russian Federation (Minzdrav Rossii, MZ RF) develops technical rules and issues ministerial orders that govern testing, classification, and the substance of conformity assessment. At the second layer, the Federal Service for Surveillance in Healthcare (Roszdravnadzor, RZN) executes state registration, supervises devices in circulation, and handles adverse event management. At the third layer, the Eurasian Economic Commission (EEC) adopts registration and circulation rules at the union level that apply across all EAEU member states simultaneously.

In practice, the overwhelming majority of a company’s interactions with the authorities occur with RZN and its subordinate expert institutions, because these bodies receive applications, commission testing, and issue decisions. However, the power to interpret the rules themselves largely rests with the Ministry of Health. A manufacturer who addresses every question to RZN may therefore receive slower or less definitive answers than one who first identifies which layer issued the requirement in dispute. Mapping each obligation to its issuing authority is a discipline worth building from day one of any Russian registration project.

2. Legal basis

3. Expert insights

Insight 1: The issuing authority of a rule determines the appeal path. The state registration procedure is regulated by a government resolution (Resolution No. 1684), while technical matters are regulated by ministerial orders (No. 4n, No. 421n, No. 540n, and others). When a dispute arises over how a provision applies, the efficient first step is to determine which layer of documentation the requirement comes from, and then address the authority empowered to interpret that layer. Writing directly to RZN about a testing methodology question that belongs to a Ministry order, or raising a procedural timing issue with an expert institution, wastes rounds of correspondence. GRZAN routinely builds this mapping into project files so that every query is routed correctly the first time.

Insight 2: Assessment and decision-making are separated. RZN accepts applications and issues decisions, but the technical review itself is carried out by its subordinate expert institutions, such as VNIIIMT. Requests for supplementary documentation typically originate from the expert institution, while the authority to continue, suspend, or withdraw a procedure rests with RZN. Keeping these two lines of communication separate and tracking them in parallel shortens projects noticeably, because technical questions are answered with technical evidence while procedural questions are answered with procedural arguments, and neither blocks the other.

Insight 3: Union-level rules are not decided by Moscow alone. EEC decisions (No. 46, No. 27, No. 173, No. 174, and others) are amended through consensus among the member states, and the amendment process is linked to the domestic approval procedures of each country. Companies planning a single pathway after 2028 should therefore track rule-making at the EEC level, not only initiatives within Russia. A change negotiated in one capital can reshape the timeline for everyone, and early visibility into EEC working documents gives manufacturers time to adjust dossiers before new requirements take effect.

4. Practical recommendations

1. Build a three-layer regulatory tracking list: the government resolution layer (No. 1684, No. 2214, and others), the ministerial order layer (No. 4n, No. 421n, No. 540n, No. 541n, and others), and the EEC decision layer (No. 46, No. 173, No. 174, and others), each with its own review frequency and named owner.
2. Before any external communication, confirm the competence boundaries of the authority you are addressing: queries about testing methods go first to the expert institution performing the review, while interpretations of dates and procedures should rest on the text of the regulation itself.
3. Keep current versions of all three layers in the project document library at all times, so that responses to queries never cite a provision that has been repealed or superseded.
4. Record, for each active project, which layer issued each requirement in the dossier, so that future amendments can be traced to their source without re-research.

5. Verification checklist

• □ It has been confirmed whether the project follows national rules or union rules, and the tracking list is set accordingly
• □ Every cited document is within its validity period (for example, Order No. 885n is replaced by Order No. 421n from September 1, 2026)
• □ Responses to queries distinguish technical questions from the expert institution from procedural questions from RZN
• □ The tracking list also includes the GOST standards layer (Russian adaptations of ISO 13485, ISO 14971, IEC 62304)

GRZAN supports manufacturers in navigating the three-layer Russian regulatory structure, from government resolutions and Ministry of Health orders to EEC decisions at the union level. Our team maintains living regulatory tracking lists for clients, routes correspondence to the correct authority, and coordinates technical and procedural workstreams in parallel so that registration projects move without avoidable delays. For structured support with RZN and EAEU registration and compliance in Russia, contact GRZAN at info@grzanglobal.com.

Regulatory information verified as of October 29, 2026.