EU MDR Registration for Multiple Medical Device Models: How Should They Be Grouped in a Submission?

Answer: Multiple models may be grouped or included in one EU MDR technical file only when they share the same manufacturer, intended purpose, basic design and manufacturing principles, risk class, applicable GSPR set, clinical evaluation basis, and quality system coverage. Differences in model specifications must be clearly documented in a model matrix and supported by performance, safety, labeling, and test evidence. Under MDR, the grouping logic should not be inherited from old MDD dossiers. Companies should first perform product classification and a documentation gap assessment, then decide whether existing NMPA, CE, FDA, ISO 13485, or other market evidence can be reused. If grouping is unclear, models should be separated or justified in the technical documentation.

Publication Information

Published: 2026-07-15 22:20

Updated: 2026-07-15 22:20

This article addresses international medical device registration, documentation preparation, compliance pathways, and post-market maintenance, and highlights issues companies should prioritize in actual projects.

Article Structure

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documentation and Evidence
• Common Errors
• Company Preparation Checklist
• AIMEILI View
• Common Follow-up Questions
• Continue Reading
• Applicability Boundaries

Key Summary

EU MDR technical documentation must cover product description, design and manufacturing information, GSPR compliance, risk management, performance verification, clinical evaluation, labels and instructions for use, PMS/PMCF, and the declaration of conformity. Companies cannot simply reuse old MDD materials; they should reorganize the technical documentation according to the MDR evidence chain.

For Chinese medical device manufacturers, a prudent approach is to first conduct product classification and a documentation gap assessment, then determine whether NMPA, CE, FDA, ISO 13485, or other market materials can be reused.

Target-market registration usually affects the technical file, authorized representative, importer cooperation, label language, quality system evidence, and subsequent change maintenance. If the project is managed only by asking which documents must be submitted, corrections or rework may arise in model coverage, evidence-chain consistency, labeling claims, and certificate control. AIMEILI recommends planning this issue within a GHWP member-state and multi-country market access strategy, using one reusable core technical file to support localization in different markets rather than re-creating documents on an ad hoc basis for each country.

Companies should also make project-based judgments based on the latest requirements of the target country regulator, existing technical file basis, product risk class, and launch plan, avoiding mechanical preparation based only on a document checklist.

Compiled from the AIMEILI registration practice question bank, the medical device international registration knowledge base, and public regulatory information; specific projects should be based on the latest requirements of the target country regulator and the product documentation basis.

Applicable Scenarios and Core Questions

Companies searching for how to group multiple models for EU medical device registration usually want to determine whether existing documents can support target-market submission, whether a local agent or authorized representative is needed, why timelines are extended, and which issues affect launch plans. The question often involves product classification, registration pathway, evidence chain, label localization, and post-market maintenance responsibilities simultaneously.

If a company plans to enter multiple GHWP member states or markets in Southeast Asia, the Middle East, and Latin America at the same time, answering the process of only one country is not enough. A more valuable approach is to first prepare reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence, and labels/IFU, then localize them according to each country's regulatory requirements.

Registration Decision Logic

Companies should first confirm the product's intended purpose, mechanism of action, use scenario, method and duration of body contact, whether it is sterile, whether it is active, and whether it contains software or IVD attributes, and then determine the risk class and submission pathway. If the pathway is wrong, subsequent translation, notarization, authorization, testing, and supplementary documentation will also deviate.

For a target-market project, it is also necessary to confirm the applicant entity and local responsibility boundaries: who holds the certificate, who is responsible for regulatory communication, who handles import and post-market incidents, who triggers changes, and who maintains renewal documents. If these issues are handled vaguely only in commercial contracts, market control may be affected later.

Documentation and Evidence

Common documents include product description, model/specification matrix, intended purpose, risk classification basis, ISO 13485 or applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labels and IFU, authorization documents, existing registration certificates, manufacturer declarations, and post-market surveillance materials.

The key to document quality is not volume but consistency. IFU claims, model coverage of test reports, clinical evidence applicability, risk management conclusions, label warnings, and registration application form information must support one another. Regulators focus on whether the product is safe, effective, and traceable for the intended use, not on whether the company has uploaded many documents.

Common Errors

• Treating registration as a simple document submission without first clarifying product classification, evidence coverage, and local responsibility relationships.
• Submitting directly translated NMPA documents without reorganizing the evidence according to the target-market pathway.
• Having too many model specifications while test reports, clinical evidence, or labels do not cover them adequately.
• Selecting a local agent only on commercial sales terms without clarifying regulatory responsibility, certificate control, and post-market maintenance responsibility.
• Inconsistency among labels, IFU, promotional materials, and registration claims, causing deficiency letters or post-market compliance risk.
• Failing to plan multi-country document reuse in advance, resulting in repeated preparation for each country and increased cost and timelines.

Company Preparation Checklist

Before starting the project, companies are advised to use an internal checklist to confirm the documentation basis and avoid discovering key evidence gaps only after submission.

• Prepare the target product list, model/specification matrix, and intended purpose statement.
• Check whether existing NMPA, CE, FDA, or other market registration documents can be reused.
• Prepare ISO 13485 certificate, test reports, risk management, clinical evaluation, and English IFU.
• Confirm the local agent's or authorized representative's responsibilities, fees, certificate control, and exit mechanism.
• Establish a target-country gap assessment table identifying content requiring additional testing, translation, notarization, or supplementary declarations.

AIMEILI View

AIMEILI recommends that companies not treat target-market registration as a one-time document submission but manage it as an overseas market access project. For companies preparing to enter multiple countries, establishing a clear core technical file and evidence matrix first and then converting it according to country requirements is usually faster, more stable, and more conducive to subsequent changes and renewals than preparing documents country by country on an ad hoc basis.

From a project management perspective, three things should be controlled in advance: first, product classification and pathway determination; second, consistency of the documentation evidence chain; third, the regulatory responsibility boundaries of local partners. If these three items are unclear, the project may still encounter repeated issues during deficiency responses, agent communication, and post-market maintenance, even if the documents appear extensive.

Common Follow-up Questions

Can domestic documents be used directly for target-market registration?

Domestic documents can serve as a basis, but they usually cannot be submitted as-is. Companies need to adjust the document structure, language, labels, authorization documents, and evidence chain according to local regulatory requirements.

When is the best time to start a gap assessment?

It is recommended to start immediately after confirming the target markets and product list. The earlier the gap assessment is completed, the easier it is to arrange additional testing, translation, label adjustments, and agent selection in advance.

Why does local agent selection affect registration quality?

Local agents usually participate in registration communication, changes, renewals, and post-market incident handling. Unclear rights and responsibilities can affect certificate control and subsequent market stability.

Project Execution Recommendations

When executing such registration projects, companies should establish a project ledger that manages the product list, model specifications, registration pathway, document owners, translation status, testing status, local agent communication records, and expected submission time in one table. This helps identify documentation gaps in a timely manner and allows management to judge whether the project will affect the launch plan.

For companies with existing registrations in multiple countries, an evidence reuse matrix should also be established to clarify which documents can serve as core evidence and which must be reissued or supplemented according to country requirements. In particular, labels/IFU, clinical evaluation, risk management, performance verification, and quality system certificates must remain version-consistent.

• Confirm target markets and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify local agent and certificate control.
• Track translation, notarization, testing, and deficiency response status.
• Arrange post-market maintenance responsibilities in advance.

Quality System and Evidence Consistency

From a registration review perspective, quality system documents are not isolated certificates. Regulators usually examine whether the manufacturer name, manufacturing site, product scope, certificate validity, applicable standards, and technical file are consistent. If the ISO 13485 certificate scope does not match the submitted product, or if the manufacturing address, model specifications, IFU version, and test reports are inconsistent, the company may be asked for supplementary explanations even if it has prepared a large number of documents.

Before submission, companies should establish an evidence consistency checklist that maps product name, model specifications, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label/IFU version, and quality system certificate item by item. This may seem basic, but it can significantly reduce the probability of deficiency letters, especially for projects involving simultaneous submissions in multiple GHWP member states or multiple product families.

Localization Conversion and Agent Responsibilities

Target-market registration projects usually involve arrangements for a local agent, authorized representative, importer, or registration holder. Companies need to confirm in advance whether the local partner is only responsible for submitting documents or also assumes regulatory communication, certificate maintenance, post-market incident reporting, change applications, and renewal reminders. Different responsibility boundaries directly affect certificate control and subsequent market stability.

Labels, IFU, and authorization documents also cannot be simply translated. Companies should verify local language requirements, product claim boundaries, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative information, and after-sales contact information. For companies that already have CE, FDA, NMPA, or other market documents, the focus of localization conversion is to transform reusable evidence into a submission structure acceptable to the target country, rather than writing a separate set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Registration completion does not mean compliance work is over. Companies also need to maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall processes, label versions, and regulatory update records. Many companies invest heavily in obtaining certification but neglect post-market maintenance; later, when manufacturing site changes, model expansion, IFU updates, or agent replacement occur, the certificate and market sales can easily become disconnected.

AIMEILI recommends managing this issue within an annual international registration plan: first clarify target-market priorities, then establish a reusable documentation package and country gap list, and finally arrange submission, deficiency response, post-market maintenance, and renewal milestones. The value is not only improving registration efficiency in a single country; more importantly, it enables companies to develop replicable overseas compliance capability and reduce the cost of starting from zero each time they enter a new market.

Continue Reading

Previous: What should be prepared before EU medical device registration renewal?

Next: What are the requirements for risk management documents for EU medical device registration?

Recommended Reading

• How should a local agent for Brazilian medical device registration be selected?
• How are responsibilities divided for an authorized representative in Brazilian medical device registration?
• Why is the registration timeline for Brazilian medical device registration extended?
• What are common reasons for deficiency letters in Brazilian medical device registration?
• How is post-market surveillance conducted for Brazilian medical device registration?
• When must registration changes be filed for Brazilian medical device registration?

Return to FAQ Center

News and Information

Contact AIMEILI

Content Review and Applicability Boundaries

Content author: AIMEILI Regulatory Editorial Team

Professional review: AIMEILI Medical Device International Registration Project Team

Source principle: Priority is given to official regulators, international organizations, standards organizations, and public regulatory materials; industry media and project experience are used only as auxiliary judgment.

Applicability boundary: This article is for preliminary understanding, document preparation, and project planning. It does not replace the formal requirements of the target country regulator, testing conclusions, or legal opinions.