Can EU Medical Device Registration Test Reports Be Reused?

Quick Answer

Test reports and technical documentation prepared for an earlier EU MDD registration cannot simply be carried over into an EU MDR submission. Reuse is possible only when the existing evidence is re-evaluated against the MDR requirements — 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 — and then reorganised into a consistent MDR evidence chain. For a Chinese medical device manufacturer, the more reliable approach is to complete product classification and a documentation gap assessment first, and only then decide whether NMPA, CE, FDA, ISO 13485 or other market materials can be reused.

Article Information and Content Structure

Published: 15 July 2026, 21:03. Updated: 15 July 2026, 21:03.

The article addresses questions that companies need to resolve early in international medical device registration, documentation preparation, compliance pathways and post-market maintenance.

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documents and Evidence
• Common Mistakes
• Company Preparation Checklist
• AIMEILI's View
• Frequently Asked Follow-up Questions
• Further Reading
• Applicability Boundaries

Key Summary

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 rely solely on legacy MDD documentation; the technical file must be reorganised according to the MDR evidence chain.

For Chinese medical device manufacturers, the more prudent judgement path is to carry out product classification and a documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market materials can be reused. Registration in a target market usually affects the technical file, authorised representative arrangements, importer cooperation, label language, quality system evidence and subsequent change maintenance. If a project is driven purely by the question of which documents to submit, deficiencies and rework are likely to arise in model coverage, evidence chain consistency, label claims and certificate control.

AIMEILI recommends placing this question within a unified GHWP member state and multi-country market access strategy, using one reusable core technical file to support localisation across markets, rather than rebuilding documentation from scratch for each country.

Companies should also make project-specific judgements based on the latest requirements of the target country regulator, the existing technical file base, the product risk class and the launch plan, instead of mechanically preparing documents against a checklist.

Applicable Scenarios and Core Questions

Companies searching for this question are usually not looking for a conceptual explanation. They want to know whether their existing documentation can support a submission in a target market, whether a local agent or authorised representative is required, why timelines are being extended, and which issues could affect the launch plan. Behind this question there are usually several interrelated factors: product classification, registration route, evidence chain, label localisation and post-market maintenance responsibilities.

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

Registration Decision Logic

Companies should first confirm the intended purpose, mechanism of action, use scenario, mode of body contact, duration of use, whether the device is sterile or active, and whether it contains software or has IVD attributes. Only then can the risk class and submission route be determined. If the route is wrong, the subsequent translation, notarisation, authorisation, testing and supplementary documentation will all be misdirected.

For a target market project, the applicant entity and local responsibility boundaries must also be confirmed: who holds the certificate, who is responsible for regulatory communication, who handles importation and post-market events, who triggers changes, and who maintains renewal documentation. If these points are left vague in the commercial contract, market control can easily be compromised 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 documentation, clinical evaluation or clinical evidence, labelling and instructions for use, authorisation documents, existing registration certificates, manufacturer declarations and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. Claims in the instructions for use, the models covered by test reports, the scope of clinical evidence, risk management conclusions, label warnings and the information in the registration application form must mutually support each other. Regulators focus on whether the device is safe, effective and traceable for its intended purpose, not on how many documents have been uploaded.

Common Mistakes

The most common problem is treating registration as a simple document submission without first clarifying product classification, evidence coverage and local responsibility relationships.

• Submitting translated NMPA documentation directly without reorganising the evidence according to the target market route.
• Too many model specifications, with insufficient coverage in test reports, clinical evidence or labelling.
• Selecting a local agent purely on the basis of sales cooperation, without clarifying regulatory responsibility, certificate control and post-market maintenance obligations.
• Inconsistency between labels, instructions for use, promotional material and registration documentation, leading to deficiency letters or post-market compliance risk.
• Failure to plan multi-country documentation reuse in advance, resulting in duplicated preparation for each country and inflated cost and timelines.

Company Preparation Checklist

Before starting a project, companies are advised to confirm the documentation base using an internal checklist, 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 documentation, clinical evaluation and English instructions for use.
• Confirm the responsibilities, fees, certificate control and exit mechanisms of the local agent or authorised representative.
• Establish a target country gap assessment table identifying what must be retested, translated, notarised or supported by additional declarations.

AIMEILI's View

AIMEILI recommends that companies treat target market registration not as a one-off document submission but as an overseas market access programme. For companies entering multiple countries, establishing a clear core technical file and evidence matrix first and then converting it to national requirements is usually faster and more stable than filling documentation gaps country by country, and it also supports later changes and certificate renewals.

From a project management perspective, three items should be controlled early: first, product classification and route 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 experience repeated deficiency responses, agent communication problems and post-market maintenance difficulties, however extensive the documentation appears to be.

Frequently Asked Follow-up Questions

Can domestic documentation be used directly for target market registration?

Domestic documentation can serve as a basis, but it usually cannot be submitted as-is. Companies need to adjust the documentation structure, language, labelling, authorisation documents and evidence chain in accordance with local regulatory requirements.

When is the best time to start a gap assessment?

Start immediately after confirming the target markets and product list. The earlier the gap assessment is completed, the easier it is to schedule retesting, translation, label adaptation and agent selection in advance.

Why does the choice of local agent affect registration quality?

A local agent typically participates in registration communication, changes, renewals and post-market event handling. If responsibilities are unclear, certificate control and subsequent market stability may be affected.

Project Execution Recommendations

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

Companies that already hold registrations in several countries should also build an evidence reuse matrix, defining which documents can serve as core evidence and which must be reissued or supplemented in line with national requirements. Labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must be kept at consistent versions.

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

Quality System and Evidence Consistency

From a registration review perspective, quality system documentation is not an isolated certificate. Regulators normally check whether the manufacturer name, manufacturing site, product scope, certificate validity period, applicable standards and technical file are consistent. If the scope of the ISO 13485 certificate does not match the products being submitted, or if the manufacturing site, model specifications or instructions for use version do not match the test reports, additional clarification may be requested even if a large volume of documentation has been prepared.

Companies should establish an evidence consistency checklist before submission, mapping product name, model 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. Although this appears basic, it can significantly reduce the probability of deficiency letters, and it is especially valuable for projects involving multiple GHWP member states or several product families submitted at the same time.

Localisation and Agent Responsibilities

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

Labelling, instructions for use and authorisation documents cannot be handled by simple translation either. Companies should verify local language requirements, the boundaries of product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorised representative details and after-sales contact information. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localisation conversion is to translate reusable evidence into a submission structure acceptable to the target country, rather than writing an isolated set of documents from scratch.

Post-Market Maintenance and Long-Term Planning

Registration is not the end of compliance work. Companies must also maintain certificate validity, change records, distributor authorisations, 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; when a manufacturing site change, model extension, instructions for use update or agent replacement occurs, the certificate can become disconnected from actual market distribution.

AIMEILI recommends managing this question within an annual international registration plan: set target market priorities first, then build a reusable documentation package and a country gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value is not only improved efficiency for a single country registration, but also the development of a repeatable overseas compliance capability, reducing the cost of rebuilding documentation from zero each time a new market is entered.

Further Reading

• Previous: How should clinical evaluation documentation be prepared for EU medical device registration?
• Next: How should an ISO 13485 certificate be used for EU medical device registration?
• Recommended: How should a local agent be selected for medical device registration in Brazil?
• Recommended: How should the responsibilities of an authorised representative be divided for medical device registration in Brazil?
• Recommended: Why do medical device registration timelines in Brazil become extended?
• Recommended: What are the common reasons for deficiency responses in medical device registration in Brazil?
• Recommended: How should post-market surveillance be conducted for medical device registration in Brazil?
• Recommended: When must a registration change be filed for medical device registration in Brazil?
• Back to the FAQ Centre
• 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 principles: official regulatory authorities, international organisations, standards organisations and public regulatory materials are prioritised; industry media and project experience are used only as supporting judgement.

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 regulator, testing conclusions or legal opinions.

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 documentation base for the product concerned.