What Are the Most Common Reasons for Deficiency Notices in EU Medical Device Registration Dossiers?

Short answer: Deficiency notices in EU medical device registration most often arise because the technical documentation was carried over from the MDD instead of being rebuilt as an MDR evidence chain. The recurring root causes are incomplete GSPR (General Safety and Performance Requirements) compliance justification, a weak link between intended purpose, model/specification matrix, test reports, clinical evaluation and labelling claims, insufficient PMS/PMCF planning, unclear responsibilities of the EU authorised representative or importer, and a quality management system certificate whose scope, addresses or product range do not match the device being filed. The most reliable way to reduce deficiency findings is to confirm the product classification and complete a documentation gap assessment before submission.

Published: 15 July 2026 · Updated: 15 July 2026

This FAQ addresses the questions manufacturers most need to resolve first when planning international medical device registration, preparing documentation, selecting a compliance pathway and maintaining compliance after market entry.

Key Takeaways

Under the EU MDR, the technical file 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 declaration of conformity. Manufacturers cannot simply reuse legacy MDD documentation; the technical documentation must be reorganised 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 only then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.

Target-market registration usually affects the technical file, authorised representative, importer cooperation, labelling language, quality system evidence and ongoing change maintenance at the same time. If the project is driven only by a list of “which documents to submit”, deficiency notices and rework are likely to appear in model coverage, evidence chain consistency, labelling claims and certificate control.

AIMEILI recommends treating this question within a GHWP member-state and multi-country market access strategy — using one reusable core technical file to support localisation in different markets, rather than rebuilding documentation country by country on an ad hoc basis.

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

Applicable Scenarios and Core Questions

Manufacturers searching for “what are the most common reasons for deficiency notices in EU medical device registration” usually are not looking for a conceptual explanation. They need to judge whether their existing documentation can support a filing in the target market, whether a local agent or authorised representative is required, why the timeline is being extended, and which issues could affect the launch plan. Behind this question there are typically several intertwined issues: product classification, registration pathway, evidence chain, labelling localisation and post-market maintenance responsibilities.

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

Registration Decision Logic

Manufacturers should first confirm the intended purpose, mechanism of action, conditions of use, mode of body contact, duration of use, sterility, whether the device is active, and whether it incorporates software or has IVD characteristics. Only then should the risk class and registration pathway be determined. If the pathway is wrong, everything downstream — translation, notarisation, authorisation, testing and supplementary documentation — will move in the wrong direction.

For a target-market project, the applicant entity and the boundaries of local responsibility must also be confirmed: who holds the certificate, who handles regulatory communication, who manages importation and post-market incidents, who triggers changes, and who maintains renewal documentation. If these points are left ambiguous in a commercial contract, market control can easily be compromised later.

Documentation and Evidence

Typical documentation includes the device description, model and specification matrix, intended purpose, basis for risk classification, ISO 13485 or applicable quality system evidence, the 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. Instructions-for-use claims, the models covered by test reports, the applicable scope of clinical evidence, risk management conclusions, label warnings and the information on the registration application form must support one another. Regulators focus on whether the device is safe, effective and traceable for its intended purpose — not on how many files have been uploaded.

Common Errors

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

• Submitting translated NMPA documentation directly, without reorganising the evidence for the target market pathway.
• Listing too many models and specifications while test reports, clinical evidence or labelling do not cover them adequately.
• Selecting a local agent purely on the basis of commercial sales cooperation, without defining regulatory responsibility, certificate control and post-market maintenance duties.
• Mismatched claims across labels, instructions for use, promotional materials and registration documents, leading to deficiency notices or post-market compliance risk.
• Failing to plan multi-country document reuse in advance, resulting in duplicated preparation for every country and inflated cost and timelines.

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 target product list, model/specification matrix and intended purpose statements.
• Verify 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 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 manufacturers 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 each national requirement, is usually faster and more stable than patching documentation country by country — and it also supports later changes and renewals more effectively.

From a project management perspective, three things should be controlled at the earliest stage: first, product classification and pathway determination; second, consistency of the documentation evidence chain; third, the regulatory responsibility boundaries of local partners. If these three points are unclear, a project can still stall repeatedly at the deficiency response, agent communication and post-market maintenance stages, no matter how many documents appear to have been prepared.

Common Follow-Up Questions

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

Domestic documentation can serve as a starting point, but it usually cannot be submitted as is. Manufacturers must adjust the documentation structure, language, labelling, authorisation documents and evidence chain to meet local regulatory requirements.

When is the best time to start a gap assessment?

A gap assessment should ideally begin as soon as the target markets and product list are confirmed. The earlier it is completed, the easier it is to arrange retesting, translation, labelling adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

The local agent typically participates in registration communication, changes, renewals and post-market incident handling. If roles and responsibilities are unclear, certificate control and subsequent market stability can be affected.

Project Execution Recommendations

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

Manufacturers 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 with country-specific statements. 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 product list.
• Complete risk classification and pathway determination.
• Build the documentation gap assessment table.
• Define the local agent and certificate control arrangements.
• Track translation, notarisation, testing and deficiency response status.
• Assign 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 typically examine whether the manufacturer name, manufacturing sites, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope of the ISO 13485 certificate does not match the device being filed, or if manufacturing addresses, model specifications or instructions-for-use versions are inconsistent with the test reports, additional clarification may be requested even when a large volume of documentation has been prepared.

Before filing, manufacturers should build an evidence consistency checklist that maps product name, model and specifications, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling version and quality system certificate item by item. This step appears basic, but it significantly reduces the probability of deficiency findings — particularly for projects filing simultaneously in several GHWP member states or with multiple product families.

Localisation and Representative Responsibilities

Target-market registration projects usually involve a local agent, authorised representative, importer or registration holder arrangement. Manufacturers must confirm in advance whether the local partner only submits 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 authorisation 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, authorised representative details and after-sales contact information. For manufacturers that already hold CE, FDA, NMPA or other market documentation, the focus of localisation is converting reusable evidence into a filing structure acceptable in the target country — not writing a separate, isolated set of documents.

Post-Market Maintenance and Long-Term Planning

Registration approval does not mean the compliance work is finished. Manufacturers 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, and then find that the certificate and commercial distribution become disconnected when a manufacturing site changes, models are expanded, instructions are updated or the agent is replaced.

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 greater efficiency in a single country — it is building a repeatable overseas compliance capability and reducing the cost of starting from scratch every time a new market is entered.

Further Reading

• Why do EU medical device registration timelines become extended?
• How should post-market surveillance be conducted for EU medical device registration?
• How should a local agent be selected for medical device registration in Brazil?
• How should authorised representative responsibilities be divided for medical device registration in Brazil?
• Why do medical device registration timelines become extended in Brazil?
• What are the most common reasons for deficiency notices in Brazilian medical device registration dossiers?
• How should post-market surveillance be conducted for medical device registration in Brazil?
• When must a registration change be filed for medical device registration in Brazil?

Content Review and Scope of Application

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

Sourcing principle: official regulatory authorities, international organisations, standards bodies and publicly available regulatory materials are prioritised; industry media and project experience are used only as supporting judgement.

Scope of application: this article is intended for preliminary understanding, document preparation and project planning. It does not replace the formal requirements of the target-country regulator, testing conclusions or legal advice.