Expertise · Medical Devices

Medical Device Registration in Russia and the EAEU: Pathway, Evidence, QMS and Clinical Strategy

Registration, evidence and certification guidance

This practice covers medical-device registration and the evidence, documentation, QMS and certification questions that arise across the regulatory pathway in Russia and the EAEU.

Current guidance is consolidated in the medical-device registration article.

Medical device registration pathways in Russia and the EAEU
Medical device registration pathways: classification, technical file, clinical evaluation and registration

For a medical-device manufacturer entering Russia in 2026, the first regulatory decision is no longer simply “prepare a Russian registration dossier.” The Eurasian Economic Union has a common registration system for medical devices, while a transition protocol signed by the EAEU states on 29 December 2025 temporarily preserved the possibility of filing new applications under either the EAEU rules or the national legislation of a member state through 31 December 2027.

That creates a genuine strategic choice.

A national Russian registration may still be appropriate for a manufacturer whose immediate commercial objective is Russia only and whose evidence package is better aligned with the national procedure. An EAEU registration may be more efficient for a manufacturer planning Russia together with Kazakhstan, Belarus, Armenia or Kyrgyzstan and willing to build one Union-level technical and clinical dossier around a selected reference state.

The choice should be made before expensive testing, clinical work, translations or QMS inspection are commissioned.

The central question is:

Which regulatory route gives the device the most maintainable market position for its intended geography, risk class, evidence base and lifecycle—not merely the fastest first filing?

For manufacturers from China, Korea, India, Europe, MENA, Latin America and other third-country markets, this pathway decision can materially change the testing strategy, clinical-evidence requirements, QMS workstream, authorized-representative model and future cost of maintaining the product.

In 2026 there are two possible entry routes into Russia

Route 1 — national registration in Russia

The December 2025 transition protocol allows applications for examination and registration of medical devices to continue under member-state national legislation through 31 December 2027.

For a manufacturer focused exclusively on the Russian market, the national pathway can therefore remain a legitimate commercial option during the transition period.

Its principal limitation is geographical: a Russian national registration authorizes circulation under the Russian system; it does not create an EAEU registration that can be recognized across the Union.

The decision to use the national pathway should therefore be made deliberately. A manufacturer that expects to enter Kazakhstan or Belarus shortly after Russia may save a first-stage regulatory effort but later face a second dossier, additional evidence review and a different lifecycle architecture.

Route 2 — EAEU registration under Decision No. 46

The EAEU procedure is governed by EEC Council Decision No. 46 of 12 February 2016, as amended.

The applicant selects a reference state, whose competent authority or expert organization performs the principal examination of safety, quality and performance, and one or more recognition states in which the manufacturer also seeks access.

The reference state evaluates the registration dossier and produces the expert conclusion. The recognition states review and agree—or, where justified, do not agree—with that conclusion. Following successful completion, the registration information enters the Union system and the device can be placed on the markets included in the procedure subject to local implementation requirements.

For a multi-country launch, the EAEU route is therefore not merely “Russia plus translations.” It is one coordinated regulatory programme with one scientific/technical dossier and several national implementation layers.

Do not choose the route only by comparing formal timelines

The EEC’s published registration scheme illustrates a formal procedure that includes initial completeness review, the main expert examination, coordination with recognition states and final registration. The main expert-review stage is structured around a 60-working-day period, while applicant deficiency-response periods, QMS production inspection where applicable and other excluded activities can materially extend the calendar timeline.

The real project starts earlier:

device qualification → risk classification → nomenclature code → market/pathway decision → testing strategy → QMS/inspection strategy → clinical evidence strategy → technical-file remediation → Russian-language dossier → filing → expert review → deficiency responses → recognition-state coordination → registration → post-market lifecycle.

A nominally fast filing can be slower overall if the device enters expert review with the wrong risk class, an incomplete technical file or clinical evidence that does not meet EAEU expectations.

The most effective timeline optimization is performed before the first test is ordered.

Step 1: confirm that the product is a medical device under the EAEU framework

Borderline products should be qualified before the registration strategy is built.

The EAEU uses a specific regulatory definition of a medical device and maintains criteria for distinguishing medical devices from other product categories. A product marketed globally as “health technology,” software, a laboratory product, wellness equipment or an accessory may not map automatically to the same regulatory category in the Union.

The intended purpose is critical.

A change in claims can change whether the product qualifies as a medical device and can also change its risk classification, clinical-evidence burden and type code.

Pharegis therefore starts with the manufacturer’s intended purpose, mode of action, target patient/user, clinical claims and product architecture rather than relying on the classification used in the EU, US, China or another jurisdiction.

Step 2: classify the device by potential risk

EAEU medical devices are classified according to potential risk of use. For non-IVD devices the principal classes are:

  • Class 1 — low risk;
  • Class 2a — moderate risk;
  • Class 2b — increased risk;
  • Class 3 — high risk.

Separate rules and criteria apply to in vitro diagnostic devices.

Classification is not a marketing label. It influences the depth of evidence expected during examination, the QMS workstream, the clinical strategy and the level of post-market oversight.

The current expert methodology explicitly applies a risk-based principle: the volume and degree of detail of the evidence should be proportionate to the device’s potential-risk class.

The classification rules were themselves amended in 2025. An international regulatory team should therefore not simply copy an old EAEU class from a distributor spreadsheet or assume direct equivalence with EU MDR Class I/IIa/IIb/III or another jurisdiction.

Pharegis documents the applicable EAEU classification rule and the rationale before the testing and dossier plan is finalized.

Step 3: determine the EAEU nomenclature type before filing

The Union maintains its own medical-device nomenclature.

The registration application must identify the corresponding EAEU device type/code. Several type codes for one registration can be used only in the specific circumstances allowed for models/brands within the registration structure.

This is not an administrative detail.

Under the amendments adopted by EEC Council Decision No. 50 of 8 July 2025 and effective from 24 February 2026, the registration rules expressly address what happens when the appropriate type is absent from the Global Medical Device Nomenclature and the EAEU nomenclature. The reference-state authority may initiate the process for creation/inclusion of a new type, and the time needed for that nomenclature process can sit outside the ordinary expert-review timeline.

For a novel device, filing without checking nomenclature can therefore create an avoidable procedural stop.

Pharegis verifies the intended EAEU type early and, where necessary, plans the nomenclature workstream before submission.

One registration can contain several models—but the family logic has to be defensible

Manufacturers often want to register an entire product family under one certificate.

The EAEU rules permit multiple models/brands within the registration structure where the regulatory criteria are met, but the models must remain sufficiently connected in intended purpose, risk profile, design and other relevant characteristics.

The expert question is not whether the marketing department calls them one product family.

The question is whether the models can be evaluated as one medical device without obscuring differences that affect safety or performance.

Before filing, Pharegis maps:

  • intended purpose;
  • risk class;
  • design architecture;
  • materials;
  • sterile/non-sterile status;
  • software version/functionality;
  • accessories and components;
  • manufacturing sites;
  • performance specifications;
  • clinical claims.

This determines which models belong together and which should be separated into another registration.

Foreign manufacturers need an authorized representative in the EAEU

A manufacturer established outside the EAEU must appoint an authorized representative of the manufacturer for the period in which the medical device circulates in the Union.

The authorized representative is not merely the address used in Module 1-style administrative paperwork. The representative has responsibilities connected with circulation of the medical device and compliance with Union requirements.

The registration dossier should contain the relevant contractual/authorization documents and current information about that representative.

For a manufacturer entering several EAEU markets, this role should be selected as part of the regulatory operating model. Changing the representative later is a lifecycle event and should not be treated as an afterthought after registration.

The dossier is a technical evidence system, not a translation package

The 2024 EEC Methodological Recommendations No. 27 substantially improved the practical description of what experts expect in a Union medical-device dossier.

The dossier should demonstrate compliance with the EAEU General Requirements for safety and performance and support the device’s intended purpose through a coherent technical file.

Depending on the device, the evidence architecture can include:

  • manufacturer and manufacturing-site information;
  • device description and intended purpose;
  • models, components and accessories;
  • manufacturing-process information;
  • risk-management documentation;
  • applicable standards and evidence of conformity;
  • technical testing;
  • biological evaluation where relevant;
  • electrical safety and electromagnetic compatibility where relevant;
  • software lifecycle and cybersecurity-related evidence where applicable;
  • sterilization, packaging and shelf-life evidence where relevant;
  • analytical and clinical performance for IVDs;
  • clinical evidence for non-IVD devices;
  • labeling and instructions for use;
  • QMS evidence and production-inspection reports where applicable;
  • post-market safety/performance data collection plan;
  • adverse-event, recall and corrective-action history for marketed devices.

The expert methodology is explicitly risk-based. The same document checklist should not be mechanically applied to a simple Class 1 non-sterile device and to an implantable Class 3 device.

Russian language is a regulatory requirement, not a convenience

The current EAEU dossier methodology states that dossier documents are submitted in Russian, or accompanied by a Russian translation certified according to the law of the reference state where the original is not in Russian.

The instructions for use, service documentation and labeling can additionally require the state language(s) of the relevant member state.

This is particularly important for Chinese, Korean and other Asian manufacturers whose technical files may exist in Chinese/English combinations.

A weak strategy is to translate the dossier only after every technical document is finalized.

A better strategy is to identify early which documents will need regulatory-quality Russian translation and which documents are likely to be revised during remediation. Otherwise a manufacturer can translate hundreds of pages twice.

Pharegis separates:

source-document remediation → controlled regulatory version → Russian translation → final dossier sequence.

Standards help only when the evidence actually matches the claimed standard

The EAEU maintains a list of standards whose voluntary use can fully or partly demonstrate compliance with the General Requirements for safety and performance.

In 2025 that standards list was updated to reflect newer editions, including standards relating to clinical investigations, symbols/labeling and usability engineering.

Using a listed standard is valuable because it creates a recognized conformity route. But simply citing ISO or IEC numbers in the technical file is not enough.

The expert methodology requires the evidence to show what methods were used, their validity, relevant test equipment and the results obtained. Where the manufacturer relies on standards outside the EAEU list, the expert review considers the validity and adequacy of those standards and the evidence generated under them.

For manufacturers with a mature EU or US technical file, this is often where the real gap analysis begins: the test report may be scientifically sound, but the dossier must still explain how it demonstrates compliance with the EAEU General Requirements.

The testing strategy should be decided before choosing laboratories

Medical-device registration can require several distinct evidence streams. Depending on product characteristics, these may include:

  • technical testing;
  • electrical safety and EMC;
  • biological evaluation;
  • sterility/packaging validation;
  • software validation;
  • metrological testing for devices falling within the relevant measuring-instrument framework;
  • clinical or clinical-laboratory studies;
  • other product-specific performance testing.

Not every device requires every test.

The 2024 EEC expert recommendations also recognize circumstances in which first-party evidence generated by the manufacturer can be accepted, subject to risk class, method validity and supporting rationale. This means the regulatory strategy should determine what evidence is needed and what evidence source is acceptable before assuming that every test must be repeated locally.

Pharegis therefore prepares an evidence matrix:

requirement → existing manufacturer evidence → applicable standard/rule → acceptability → gap → new test/study if needed.

This can avoid both under-testing and unnecessary duplication.

Clinical evidence is one of the most misunderstood parts of EAEU device registration

A CE-marked device or a device with extensive foreign market history does not automatically have an acceptable EAEU clinical package.

The current EAEU clinical rules and the 2024 expert recommendations distinguish among product types and risk classes.

For higher-risk non-IVD devices—particularly Classes 2b and 3 and implantable devices—clinical safety and performance are generally expected to be supported by clinical data, and multicenter clinical investigations can be required unless the applicant can specifically justify another route to demonstrate clinical performance and safety.

A key timing distinction applies to foreign clinical studies:

  • studies completed before 1 January 2022, or already ongoing with enrollment completed at that date, can be considered under the transition provisions when they meet the relevant requirements;
  • for clinical investigations initiated after 1 January 2022, the EAEU framework generally requires compliance with the Union clinical-investigation rules, and at least one clinical investigation is conducted in an EAEU member state for the applicable higher-risk device scenarios.

This is a major strategic issue for manufacturers whose global clinical programme was designed entirely around EU MDR, FDA or Chinese NMPA requirements.

The correct question is therefore not “Do we have a clinical report?”

It is:

Does our existing clinical evidence satisfy the EAEU clinical pathway for this risk class and intended purpose, or do we need an EAEU clinical investigation?

That question should be answered before submission, because a missing EAEU clinical component can change the project by months.

IVDs follow a different clinical-evidence logic

In vitro diagnostic devices should not be forced into the non-IVD clinical model.

The EAEU rules use clinical-laboratory performance evidence and risk-specific requirements. The 2024 recommendations state that multicenter clinical-laboratory studies are not universally mandatory for IVDs; for Class 2b and 3 IVDs, clinical-laboratory evidence from one medical organization can be sufficient in the applicable scenario.

The dossier should distinguish:

  • scientific validity/clinical association where relevant;
  • analytical performance;
  • clinical performance;
  • intended population and specimen type;
  • reference methods/comparators;
  • sensitivity/specificity and other relevant performance characteristics;
  • risk associated with false positive/false negative results;
  • post-market performance monitoring.

For an IVD manufacturer, this can make the difference between a rational evidence plan and an unnecessary hospital-study programme.

Software and AI medical devices need their own evidence architecture

The current EAEU clinical framework expressly addresses software as a medical device, including software using artificial-intelligence technologies.

The clinical evaluation must consider the credibility of the clinical association and the analytical and clinical validation of the software function. Patient data used for clinical evaluation must meet the applicable evidentiary requirements, including verification through medical organizations in the relevant scenarios.

This makes a conventional “hardware technical file plus software description” insufficient for many software products.

Pharegis separates the software dossier into:

  • intended medical purpose;
  • algorithm/function architecture;
  • input data and output claims;
  • analytical validation;
  • clinical validation;
  • data provenance;
  • risk management;
  • software lifecycle/control;
  • cybersecurity and update strategy where relevant;
  • post-market change-management logic.

A future software update can be a regulatory change. The registration strategy should therefore anticipate the manufacturer’s release cycle from the beginning.

QMS inspection is a regulatory workstream, not a certificate attachment

EEC Council Decision No. 106 establishes EAEU requirements for implementation, maintenance and assessment of the medical-device quality management system according to device risk.

The dossier can include ISO 13485 certification as supporting evidence, but ISO 13485 certification and the EAEU production-inspection requirement are not identical concepts.

Where an EAEU production-inspection report is required, experts assess whether:

  • the manufacturer has a positive QMS conformity conclusion;
  • the report covers the relevant group/subgroup of medical devices;
  • the manufacturing sites and addresses correspond to those stated in the registration dossier.

This linkage is critical.

A valid inspection report for another device family or another manufacturing-site configuration may not support the new registration automatically.

Pharegis therefore connects:

device classification → product group → manufacturing sites → QMS scope → inspection report → registration dossier.

For foreign manufacturers, the QMS workstream should be started early enough that it does not become the last unresolved dependency after the technical and clinical dossier is otherwise complete.

The manufacturing map must match the regulatory manufacturer model

The EAEU technical file requires transparent information on how and where the medical device is produced.

This can include the manufacturer, contract manufacturers, production sites, sterilization sites and other relevant stages.

A common international-company problem is that the legal manufacturer shown on global labeling is not the entity performing the critical manufacturing operations. The dossier must explain those relationships and the division of responsibilities.

For outsourced production, Pharegis reviews whether the contracts, QMS scope, labeling, technical file and inspection evidence describe the same operational model.

The objective is not to list every supplier. It is to identify the sites and activities that form part of the regulated manufacturing chain.

Labeling and instructions need to be designed for a multi-state launch

The EAEU registration dossier includes full-color packaging/labeling layouts and the Russian labeling text. Additional state-language requirements can apply in recognition states.

This means the commercial packaging strategy should be decided before final dossier assembly.

Questions include:

  • one multilingual pack or country-specific packs;
  • device/model identifiers;
  • manufacturer and authorized-representative information;
  • registration details;
  • symbols and language conventions;
  • warnings and contraindications;
  • storage/transport conditions;
  • electronic vs paper instructions where permitted;
  • service documentation.

A last-minute decision to add another recognition state can therefore create more than an administrative fee: it can change the labeling and instruction package.

Existing market history is evidence—but it can also expose risk

For devices already marketed outside the EAEU, the dossier includes regulatory and post-market history where applicable.

The 2024 recommendations call for information on adverse events/incidents, recalls and corrective actions, as well as marketing history for relevant higher-risk devices.

A strong global market history can support the benefit-risk position.

But unresolved recalls, inconsistent incident reporting or major field safety corrective actions can create expert questions.

Pharegis therefore reviews post-market evidence before filing rather than waiting for the expert organization to discover it during examination.

The objective is to provide a coherent narrative:

what happened → what risk was identified → what corrective action was taken → whether the issue affects the EAEU device configuration.

Post-market planning is part of registration

The EAEU expert methodology expects a manufacturer plan for collection and analysis of post-market safety and performance data for devices of all risk classes.

For higher-risk devices, additional post-registration clinical monitoring obligations can apply. For Class 3 devices and implantable Class 2b devices, the clinical evidence package can include a post-registration clinical monitoring plan.

Registration should therefore be designed with lifecycle resources in mind.

The manufacturer needs a process for:

  • complaints;
  • incidents;
  • corrective actions;
  • trend analysis;
  • recalls/field actions;
  • post-market clinical or performance follow-up;
  • regulatory changes;
  • coordination with the authorized representative.

A device registration is not finished when the certificate is issued.

National Russia vs EAEU: how to make the pathway decision

During the transition period through 31 December 2027, the choice should be commercial and evidence-based.

National Russia may be reasonable where:

  • Russia is the only intended EAEU market for the foreseeable future;
  • the manufacturer has a Russia-specific launch strategy;
  • the current evidence package is more efficiently deployable under the national procedure;
  • the organization accepts that future expansion into other EAEU states may require a separate Union-level project.

EAEU registration is usually more attractive where:

  • two or more EAEU markets are planned;
  • the manufacturer wants one Union regulatory baseline;
  • the technical and clinical dossier can be built to EAEU requirements;
  • the company wants future lifecycle work coordinated around a reference state rather than maintained as several unrelated national files.

The decision can also differ by product.

A manufacturer may rationally place a strategic multi-country platform device into the EAEU system while using the national Russian route for a lower-volume legacy model during the transition period.

The objective is not ideological “harmonization.” It is regulatory efficiency across the product portfolio.

Where medical-device registration projects most often lose time

The most expensive delays are usually created before formal examination:

  • selecting the national or EAEU route after testing has already begun;
  • using the wrong EAEU risk class;
  • discovering late that the required EAEU nomenclature type does not exist;
  • trying to place too many materially different models in one registration;
  • translating an unreconciled technical file;
  • assuming CE/FDA/NMPA evidence will be accepted without an EAEU evidence mapping;
  • commissioning unnecessary local tests instead of first assessing existing evidence;
  • discovering after filing that a post-2022 clinical programme lacks the EAEU component required for the product;
  • treating ISO 13485 as if it automatically resolves the EAEU QMS inspection workstream;
  • allowing manufacturing-site information in the dossier and QMS inspection report to diverge;
  • delaying Russian labeling/IFU localization until expert review is nearly complete;
  • failing to disclose or contextualize significant global post-market incidents;
  • planning approval without planning the authorized-representative and post-market operating model.

These are not documentation problems. They are pathway and evidence-strategy problems.

What Pharegis manages in a medical-device market-entry project

Pharegis can support one defined workstream or coordinate the complete Russia/EAEU registration programme. Typical deliverables include:

  • national Russia vs EAEU pathway memo;
  • device qualification and borderline-product assessment;
  • EAEU risk-classification rationale;
  • nomenclature code/type assessment and new-type strategy where required;
  • model/family registration-structure assessment;
  • reference-state and recognition-state strategy;
  • authorized-representative operating model;
  • technical-file gap matrix against current EAEU requirements;
  • evidence/standards matrix;
  • testing strategy and laboratory coordination;
  • biological-evaluation strategy where applicable;
  • clinical/clinical-laboratory evidence assessment;
  • determination of whether an EAEU clinical study is required;
  • QMS/production-inspection dependency assessment;
  • manufacturing-site and contractor mapping;
  • Russian regulatory translation and dossier assembly;
  • labeling, IFU and recognition-state language strategy;
  • expert-question response coordination;
  • post-market safety/performance plan;
  • lifecycle and variation strategy after registration.

For a manufacturer without an EAEU regulatory department, these workstreams can be managed as one remote-market-entry function. For a multinational organization, Pharegis can take responsibility for the difficult local interface—classification, evidence gap, EAEU clinical strategy, QMS inspection, recognition-state coordination or recovery of a stalled dossier—without duplicating the global regulatory team.

Discuss a medical-device registration project

For an initial assessment, prepare:

  • product description and intended purpose;
  • models/configurations to be registered;
  • current risk classification in major markets;
  • existing registrations/approvals;
  • intended EAEU countries and launch sequence;
  • technical file / design dossier;
  • ISO 13485/QMS status and manufacturing-site list;
  • available technical, EMC/electrical, biological and other testing;
  • clinical or performance evidence;
  • post-market history and significant incidents/recalls;
  • labeling and instructions for use;
  • target filing and launch date.

Pharegis can then determine whether the national Russian or EAEU route is more rational, identify evidence that can be reused, isolate the real testing/clinical/QMS gaps and place those workstreams on one registration critical path.

The objective is not simply to obtain a medical-device registration in Russia. It is to build a regulatory position that matches the manufacturer’s geography, evidence and product lifecycle—and does not have to be rebuilt when the next EAEU market is added.

Regulatory basis

Regulatory status reviewed: August 2026.