How Should Registration Dossiers Be Prepared for EU Medical Device Registration?

Published: 15 July 2026, 20:21   Updated: 15 July 2026, 20:21

Preparing registration dossiers for EU medical device registration under the MDR requires rebuilding the technical documentation around the MDR evidence chain, not simply carrying over legacy MDD files. The technical file must cover the product description, design and manufacturing information, GSPR conformity, risk management, performance verification, clinical evaluation, labelling and instructions for use, PMS/PMCF and the EU Declaration of Conformity. For Chinese medical device manufacturers, the most reliable starting point is to confirm product classification and complete a documentation gap assessment, and only then decide whether existing NMPA, CE, FDA, ISO 13485 or other market materials can be reused.

Registration in a target market typically affects the technical file, authorized representative arrangements, importer cooperation, label language, quality system evidence and subsequent change maintenance. If a project is driven only by the question of "which documents must be submitted," deficiency letters or rework are likely in areas such as model coverage, evidence-chain consistency, labelling claims and certificate control.

This article addresses medical device international registration, documentation preparation, compliance pathways and post-market maintenance, and outlines the questions companies should prioritize in real projects.

Key points

EU MDR technical documentation for medical devices must cover the product description, design and manufacturing information, GSPR conformity, risk management, performance verification, clinical evaluation, labelling and instructions for use, PMS/PMCF and the EU Declaration of Conformity. Companies cannot simply reuse their legacy MDD dossiers; the technical documentation must be reorganized around the MDR evidence chain.

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

Target market registration usually affects the technical file, the authorized representative, importer cooperation, label language, quality system evidence and subsequent change maintenance. If a project is driven only by the document submission checklist, deficiency letters or rework are likely in model coverage, evidence-chain consistency, labelling claims and certificate control.

AIMEILI recommends that companies plan this question within a broader GHWP member state and multi-country market access strategy, using one reusable core technical file to support localization in different markets instead of redoing documentation on a country-by-country basis.

Companies should also make project-based judgments by combining the latest requirements of the target country's regulatory authority, the existing technical file basis, the product risk class and the launch plan, rather than mechanically preparing documents against a checklist.

Compiled from AIMEILI's regulatory practice resources, the medical device international registration knowledge base and public regulatory information. Specific projects should be based on the latest requirements of the target country's regulatory authority and the product's documentation basis.

Scope and core questions

Companies searching for "how to prepare EU medical device registration dossiers" usually want to determine whether their existing documentation can support a target market submission, whether a local agent or authorized representative is required, why timelines are extended, and which issues could affect the launch plan, rather than seeking a conceptual explanation.

Behind this question are usually several interconnected topics: product classification, registration pathway, evidence chain, label localization and post-market maintenance responsibilities.

If a company plans to enter several GHWP member states or markets in Southeast Asia, the Middle East and Latin America at the same time, answering the process for one country alone is not enough. A more valuable approach is to first develop reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labelling/instructions for use, and then adapt them to each country's regulatory requirements.

Regulatory pathway assessment logic

Companies should first confirm the intended purpose, mechanism of action, use scenario, method and duration of body contact, whether the device is sterile, whether it is active, and whether it contains software or has IVD attributes, and then determine the risk class and submission pathway. Once the pathway is wrongly determined, the subsequent translation, notarization, authorization, testing and supplementary documentation will all deviate from the correct direction.

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

Documents and evidence

Typical documentation includes the product description, model and specification matrix, intended purpose, risk classification rationale, ISO 13485 or applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labelling and instructions for use, authorization documents, existing registration certificates, manufacturer's declarations and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. Instructions-for-use claims, the models covered by test reports, the scope of application of clinical evidence, risk management conclusions, label warnings and the information in the registration application form must support one another. Regulatory authorities focus on whether the device is safe, effective and traceable for its intended purpose, not on how many documents a company has uploaded.

Common errors

The most common problem is that companies treat a registration project 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 models and specifications while test reports, clinical evidence or labelling coverage are insufficient.
• Selecting a local agent solely on the basis of sales cooperation, without clarifying regulatory responsibilities, certificate control and post-market maintenance obligations.
• Inconsistencies between labels, instructions for use, promotional materials and registration dossier claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country document reuse in advance, resulting in repeated preparation in each country and inflated costs and timelines.

Company preparation checklist

Before starting a project, companies should use an internal checklist to confirm the documentation basis, so that critical evidence gaps are not discovered only after submission.

• Compile the target product list, model and specification matrix and intended purpose statements.
• Verify whether existing NMPA, CE, FDA or other market registration documents can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management file, clinical evaluation and English instructions for use.
• Confirm the responsibilities, fees, certificate control and exit mechanism of the local agent or authorized representative.
• Establish a target country gap assessment table identifying what must be re-tested, translated, notarized or supported by additional declarations.

AIMEILI's perspective

AIMEILI recommends that companies not view target market registration as a one-off 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 to national requirements is usually faster, more stable and more conducive to subsequent changes and certificate renewals than supplementing documents country by country on an ad hoc basis.

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

Frequently asked 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 they are. Companies need to adjust the document structure, language, labelling, authorization documents and evidence chain in accordance with local regulatory requirements. The extent of adjustment depends on the target country's submission format, language requirements, local representative arrangements and the gap between the existing evidence and the intended purpose in that market.

When is the best time to start a gap assessment?

A gap assessment should be started as soon as the target markets and product list are confirmed. The earlier the gap assessment is completed, the earlier companies can arrange additional testing, translation, label adjustments and agent selection. Starting the assessment after the submission plan is fixed often compresses the testing and translation schedule and increases the risk of deficiency letters or launch delays.

Why does the choice of local agent affect registration quality?

The local agent usually participates in registration communication, changes, certificate renewal and the handling of post-market events. Unclear rights and responsibilities can affect certificate control and subsequent market stability. Companies should therefore define in writing who holds the certificate, who communicates with the regulator, who submits changes and renewals, and who is responsible for vigilance and post-market reporting.

Project execution recommendations

When executing this type of registration project, companies should establish a project ledger that manages the product list, models and specifications, registration pathway, document owners, translation status, testing status, local agent communication records and expected submission dates in a single table. This makes documentation gaps visible in time and helps management judge whether the project will affect the launch plan.

For companies that already have registrations in several 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 with explanations in accordance with national requirements. Labels and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates must in particular be kept version-consistent.

• Confirm the target markets and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify the 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 documentation is not an isolated certificate. Regulatory authorities usually examine whether the manufacturer name, manufacturing site, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope covered by the ISO 13485 certificate does not match the device being registered, or if the manufacturing site, models and specifications or instructions-for-use version are inconsistent with the test reports, the authority may request supplementary explanations even if the company has prepared a large number of documents.

Before submission, companies should establish an evidence consistency checklist that maps the product name, models and specifications, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and instructions-for-use version, and quality system certificate item by item. This step appears 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 and authorized representative 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 handles regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and subsequent market stability.

Labels, instructions for use and authorization documents also cannot simply be translated. Companies should verify local language requirements, boundaries for product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative information and after-sales contact details. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localization is to convert reusable evidence into a submission structure acceptable to the target country, not to write a separate set of isolated documents.

Post-market maintenance and long-term planning

Registration is not the end of compliance work. Companies also need to maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall procedures, label versions and regulatory update records. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance; subsequently, once a manufacturing site change, model expansion, instructions-for-use update or agent replacement occurs, the certificate and market sales can become disconnected.

AIMEILI recommends that companies manage this question within an annual international registration plan: first set target market priorities, then establish a reusable documentation package and a country gap list, and finally schedule submission, deficiency response, post-market maintenance and certificate renewal milestones. The value of this approach is not only higher registration efficiency in a single country; more importantly, it enables companies to build a replicable overseas compliance capability and reduce the cost of starting from scratch every time they enter a new market.

Further reading

• Previous: How to Handle Inconsistent Quality System Evidence for Medical Device Registration in Japan?
• Next: How to Determine Product Classification for EU Medical Device Registration?
• Brazil Medical Device Registration: How Should a Local Agent Be Selected?
• Brazil Medical Device Registration: How Should Authorized Representative Responsibilities Be Divided?
• Brazil Medical Device Registration: Why Are Registration Timelines Extended?
• Brazil Medical Device Registration: What Are the Common Reasons for Deficiency Letters?
• Brazil Medical Device Registration: How Should Post-Market Surveillance Be Conducted?
• Brazil Medical Device Registration: When Must Registration Changes Be Filed?

Content review and applicability boundaries

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team.

Source principles: Priority is given to official regulatory authorities, international organizations, standards organizations and public regulatory materials; industry media and project experience are used only as supporting references.

Applicability boundaries: This article is intended for preliminary understanding, documentation preparation and project planning. It does not replace the formal requirements of the target country's regulatory authority, testing conclusions or legal opinions.