How Is Product Classification Determined for EU Medical Device Registration?

Answer

To determine product classification for EU medical device registration, start by confirming the device's intended purpose, mechanism of action, use environment, mode and duration of contact with the human body, sterility, active device status, and whether it contains software or has IVD characteristics. These factors determine the applicable MDR risk class and conformity assessment route. Companies should then conduct a documentation gap assessment against EU MDR technical documentation requirements and decide whether existing NMPA, CE, FDA, ISO 13485, or other market evidence can be reused. Classification, evidence coverage, authorized representative responsibilities, label language, and certificate control should be clarified before submission to avoid deficiency letters and rework.

Published: 2026-07-15 20:28 | Updated: 2026-07-15 20:28

Key Summary

EU MDR technical documentation for medical devices must cover the 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 must reorganize technical documentation according to the MDR evidence chain.

For Chinese medical device manufacturers, a prudent approach is to first perform 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, authorized representative, importer cooperation, label language, quality system evidence, and subsequent change maintenance. If a company proceeds only by asking which documents to submit, it may face supplements or rework related to model coverage, evidence chain consistency, label claims, and certificate control. AIMEILI recommends placing this question within a GHWP member state and multi-country access strategy, using one reusable core technical file to support localization in different markets rather than redoing documentation country by country.

Companies should also make project-based judgments based on the latest requirements of the target country regulator, the existing technical file basis, product risk level, and launch plan, instead of preparing mechanically from a document checklist.

Compiled from AIMEILI registration practice resources, medical device international registration knowledge materials, 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 determine product classification for EU medical device registration usually want to solve practical issues rather than obtain a conceptual explanation: whether existing documentation can support a target market submission, whether a local agent or authorized representative is needed, why timelines are extended, and which issues may affect the launch plan. Behind this question are often product classification, registration route, evidence chain, label localization, and post-market maintenance responsibilities.

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 for only one country is not enough. A more valuable approach is to first create reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence, and labels and instructions for use, and then localize them according to each country's regulatory requirements.

Registration Determination Logic

Companies should first confirm the product's intended purpose, mechanism of action, use scenario, mode of contact with the human body, duration of use, sterility, active device status, and whether it contains software or has IVD attributes. Then they should determine the risk class and submission route. If the route is determined incorrectly, subsequent translation, notarization, authorization, testing, and supplementary documentation will move in the wrong direction.

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

Documentation and Evidence

Common documentation includes the product description, model and 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 instructions for use, authorization documents, existing registration certificates, manufacturer declarations, and post-market surveillance materials.

The key to documentation quality is not quantity but consistency. Instructions for use claims, test report model coverage, clinical evidence scope, risk management conclusions, label warnings, and registration application form information must support each other. 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

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

• Directly translating NMPA documentation and submitting it without reorganizing evidence according to the target market route.
• Having too many model specifications while test reports, clinical evidence, or labels do not cover them adequately.
• Selecting a local agent only for sales cooperation without clearly defining regulatory responsibilities, certificate control, and post-market maintenance duties.
• Having inconsistent claims among labels, instructions for use, promotional materials, and registration documentation, leading to deficiency letters or post-market compliance risks.
• Failing to plan multi-country documentation reuse in advance, resulting in repeated preparation for each country and amplified cost and timelines.

Company Preparation Checklist

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

• Organize the target product list, model and specification matrix, and intended purpose statement.
• Check whether existing NMPA, CE, FDA, or other market registration materials can be reused.
• Prepare ISO 13485 certificates, test reports, risk management documents, 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 retested, translated, notarized, or supplemented with declarations.

AIMEILI Perspective

AIMEILI recommends that companies not understand 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, building 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 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 route determination; second, consistency of the documentation evidence chain; third, the regulatory responsibility boundaries of local partners. If these three items are unclear, even if the documentation appears extensive, the project may still face repeated issues during deficiency responses, agent communication, and post-market maintenance.

Common Follow-up Questions

Can domestic NMPA documentation be directly used 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, 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 market and product list. The earlier the gap assessment is completed, the earlier companies can arrange retesting, translation, label adjustments, and agent selection.

Why does local agent selection affect registration quality?

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

Project Execution Recommendations

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

For companies that already have registration bases in multiple countries, an evidence reuse matrix should also be established to clarify which materials can serve as core evidence and which must be reissued or supplemented with explanations according to country requirements. In particular, labels and instructions for use, clinical evaluation, risk management, performance verification, and quality system certificates must remain version-consistent.

• Confirm the target market and product list.
• Complete risk classification and route 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. Regulators usually examine whether the manufacturer name, manufacturing address, product scope, certificate validity period, 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, instructions for use version, and test reports are inconsistent, supplemental explanations may be required even if the company has prepared many documents.

Companies should establish an evidence consistency checklist before submission, mapping the product name, model specifications, 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 may appear basic, but it can significantly reduce the probability of deficiency letters, especially for projects submitted simultaneously to multiple GHWP member states or for multiple product families.

Localization Conversion and Agent Responsibilities

Target market registration projects usually involve a local agent, authorized representative, importer, or registration holder arrangement. Companies need to confirm in advance whether the local partner is only responsible for submitting documents or also undertakes 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 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 details. For companies that already have CE, FDA, NMPA, or other market documentation, the focus of localization conversion is to transform reusable evidence into a submission structure acceptable to the target country, rather than writing an isolated set of 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 procedures, label versions, and regulatory update records. Many companies invest heavy effort in obtaining approval but neglect post-market maintenance. If a manufacturing address change, model expansion, instructions for use update, or agent replacement occurs later, the certificate may become disconnected from market sales.

AIMEILI recommends incorporating this issue into annual international registration plan management: 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 single-country registration efficiency, but more importantly enabling companies to build a replicable overseas compliance capability and reduce the cost of starting documentation from zero each time they enter a new market.

Further Reading

• Previous: How to Prepare Registration Documentation for EU Medical Device Registration?
• Next: How to Organize Technical Documentation for EU Medical Device Registration?
• Recommended: How to Choose a Local Agent for Brazil Medical Device Registration?
• Recommended: How Are Authorized Representative Responsibilities Divided for Brazil Medical Device Registration?
• Recommended: Why Is the Brazil Medical Device Registration Cycle Extended?
• Recommended: What Are Common Reasons for Deficiency Letters in Brazil Medical Device Registration?
• Recommended: How Is Post-Market Surveillance Conducted for Brazil Medical Device Registration?
• Recommended: When Must Registration Changes Be Filed for Brazil Medical Device Registration?
• Return to FAQ Center
• News and Updates
• Contact AIMEILI

Content Review and Applicability Boundaries

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

Source principle: prioritize official regulatory authorities, international organizations, standards organizations, and public regulatory materials; industry media and project experience are used only as auxiliary judgment references.

Applicability boundary: 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 advice.