EU Medical Device Registration: When Must Changes Be Notified?

Under Regulation (EU) 2017/745 (MDR), a change must be notified to the Notified Body that issued the relevant certificate, and where it affects conformity it must be assessed and approved before implementation, whenever it could affect the device's compliance with the General Safety and Performance Requirements (GSPR), the validity of the EU technical documentation assessment or type-examination certificate, the scope of the certified quality management system, or the conclusions of the clinical evaluation and risk management. Typical triggers include changes to intended purpose or indications, design, materials, software, sterilization, manufacturing process or manufacturing site, packaging, labelling and claims, device classification, and the PMS/PMCF plan. Changes that are not notifiable still have to be handled through the manufacturer's documented change control procedure, and the justification for not notifying must be recorded. Under MDR Annex IX, manufacturers must inform the Notified Body of planned changes to the approved technical documentation, and any change affecting conformity must be assessed before it is implemented.

Published: 2026-07-15 22:04 · Last updated: 2026-07-15 22:04

Key Summary

The EU MDR technical documentation for a medical device must cover the device description, design and manufacturing information, GSPR compliance, risk management, performance verification, clinical evaluation, labelling and instructions for use, PMS/PMCF and the EU Declaration of Conformity. Manufacturers cannot simply carry over legacy MDD documentation; the technical file has to be reorganized around the MDR evidence chain.

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

Target-market registration usually affects the technical file, the authorized representative, importer cooperation, label language, quality system evidence and ongoing change maintenance at the same time. If a project is driven only by the question of which documents are to be submitted, deficiencies and rework are likely to appear in model coverage, evidence-chain consistency, label claims and certificate control.

AIMEILI recommends that manufacturers plan this question 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 rebuilding documentation country by country on an ad hoc basis.

Manufacturers should also make project-based judgments that combine the latest requirements of the target-country regulator, the existing technical file, the device risk class and the launch plan, instead of preparing mechanically against a document checklist.

Prepared from the AIMEILI regulatory practical question bank, the medical device international registration knowledge base and publicly available regulatory information; individual projects should be based on the latest requirements of the target-country regulator and the device's documentation base.

Scope and Core Question

Manufacturers searching for when changes to an EU medical device registration need to be notified are usually not looking for a conceptual explanation. They want to know whether their existing documentation can support a filing in the target market, whether a local agent or authorized representative is required, why timelines keep extending, and which issues could affect the launch plan. Behind this question there are usually several linked topics: device classification, the registration pathway, the evidence chain, label localization and post-market maintenance responsibilities.

If a manufacturer plans to enter several GHWP member states at the same time, or markets in Southeast Asia, the Middle East and Latin America, answering the procedure for one country alone is not enough. A more valuable approach is to first turn the core technical file, quality system evidence, performance verification, clinical evidence and labelling into a reusable version, and then localize them according to each country's regulatory requirements.

Registration Decision Logic

Manufacturers should first confirm the intended purpose, mechanism of action, use scenario, mode and duration of body contact, whether the device is sterile, whether it is active, and whether it contains software or has IVD characteristics, and then determine the risk class and the filing pathway. Once the pathway decision is wrong, the subsequent translation, notarization, authorization, testing and supplementary documentation will all move in the wrong direction.

For a target-market project, the applicant entity and the boundaries of local responsibility also have to be confirmed: who holds the certificate, who handles regulatory communication, who manages import and post-market incidents, who triggers a change, and who maintains the documentation for certificate renewal. If these points are left vague in a commercial contract, market control can easily be affected later.

Documentation and Evidence

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

The key to documentation quality is not volume but consistency. Claims in the instructions for use, the model coverage of test reports, the applicable scope of clinical evidence, the conclusions of risk management, label warnings and the information in the registration application form must support one another. Regulators focus on whether the device is safe, effective and traceable for its intended use, not on how many documents a manufacturer has uploaded.

Common Errors

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

• Submitting translated NMPA documentation directly without reorganizing the evidence according to the target-market pathway.
• Listing too many models and specifications while test reports, clinical evidence or labels do not cover them adequately.
• Choosing a local agent purely on the basis of sales cooperation, without defining regulatory responsibility, certificate control and post-market maintenance duties.
• Inconsistency between labels, instructions for use, promotional material and registration claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country documentation reuse in advance, so that each country is prepared separately and both cost and timelines are inflated.

Manufacturer Preparation Checklist

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

• Compile the list of target devices, the model and specification matrix and the intended purpose statement.
• Check whether existing NMPA, CE, FDA or other market registration documentation can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management documentation, clinical evaluation and English instructions for use.
• Confirm the duties, fees, certificate control and exit mechanism of the local agent or authorized representative.
• Build a target-country gap assessment table identifying what requires additional testing, translation, notarization or supplementary declarations.

AIMEILI Perspective

AIMEILI recommends that manufacturers not treat target-market registration as a one-off document submission, but manage it as an overseas market access project. For companies preparing to enter several countries, building a clear core technical file and evidence matrix first and then converting it country by country is usually faster, more stable, and more conducive to subsequent changes and certificate renewal than filling gaps on an ad hoc basis.

From a project management perspective, three things should be controlled in advance: first, device classification and pathway determination; second, evidence-chain consistency; third, the boundaries of regulatory responsibility of local partners. If these three are unclear, the project may still run into repeated issues during deficiency responses, agent communication and post-market maintenance, no matter how extensive the documentation appears.

Frequently Asked Questions

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

Domestic documentation can serve as a basis, but it generally cannot be submitted as it stands. Manufacturers need to adjust the documentation structure, language, labels, authorization documents and evidence chain according to local regulatory requirements.

When is the best time to start a gap assessment?

Immediately after the target markets and device list have been confirmed. 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 the choice of local agent affect registration quality?

The local agent usually takes part in registration communication, changes, certificate renewal and post-market incident handling. Unclear duties and rights can affect certificate control and subsequent market stability.

Project Execution Recommendations

When executing this type of registration project, manufacturers should maintain a project register that tracks the device list, model and specification matrix, 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 early and helps management judge whether the project will affect the launch plan.

Companies that already have registrations in several countries should also build an evidence reuse matrix that identifies which documents can serve as core evidence and which must be reissued or supplemented according to national requirements. Labels and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must remain version-consistent.

• Confirm the target markets and device list.
• Complete risk classification and pathway determination.
• Build the documentation gap assessment table.
• Define the local agent and certificate control.
• Track translation, notarization, testing and deficiency 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. Regulators usually check whether the manufacturer's name, manufacturing address, device scope, certificate validity period, applicable standards and technical file are consistent. If the scope of the ISO 13485 certificate does not match the device being registered, or if the manufacturing address, model and specification, or instructions for use version do not match the test reports, supplementary explanations may be requested even when a large volume of documentation has been prepared.

Before filing, manufacturers should build an evidence consistency checklist that maps the device name, model and specification, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and instructions for use version and quality system certificate item by item. This step appears basic, but it can clearly reduce the probability of deficiency letters, especially for projects filing in several GHWP member states or for several product families at the same time.

Localization Conversion and Authorized Representative Responsibilities

Target-market registration projects usually involve arrangements for a local agent, authorized representative, importer or registration holder. Manufacturers need to confirm in advance whether the local partner is only responsible for submitting documents or also handles 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, instructions for use and authorization documents also cannot simply be translated. Manufacturers should verify local language requirements, the boundaries of 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 conversion is to transform reusable evidence into a filing structure acceptable to the target country, rather than writing a separate, isolated set of documents.

Post-Market Maintenance and Long-Term Planning

Registration is not the end of compliance work. Manufacturers 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 certification but neglect post-market maintenance; when a manufacturing address change, model extension, instructions for use update or agent replacement occurs later, the certificate and market sales can easily become disconnected.

AIMEILI recommends managing this question within an annual international registration plan: define 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 higher efficiency for a single country, but a replicable overseas compliance capability that reduces the cost of starting from scratch each time a new market is entered.

Further Reading

• Previous: How is post-market surveillance handled for EU medical device registration?
• Next: What needs to be prepared before renewing an EU medical device registration certificate?
• Recommended: How should a local agent be selected for Brazilian medical device registration?
• Recommended: How are the responsibilities of an authorized representative divided in Brazilian medical device registration?
• Recommended: Why does the registration timeline for Brazilian medical device registration get extended?
• Recommended: What are the common reasons for deficiency letters in Brazilian medical device registration?
• Recommended: How is post-market surveillance handled for Brazilian medical device registration?
• Recommended: When do changes to a Brazilian medical device registration need to be notified?

Return to the FAQ Centre · News · Contact AIMEILI

Content Review and Scope of Application

Content author: AIMEILI Regulatory Editorial Team

Professional review: AIMEILI Medical Device International Registration Project Team

Sourcing principle: Priority is given to official regulatory authorities, international organizations, standards bodies and publicly available regulatory documents; industry media and project experience are used only as supporting judgment.

Scope of application: This article is intended for preliminary understanding, documentation preparation and project planning. It does not replace the formal requirements of the target-country regulator, test conclusions or legal opinions.