How Is Post-Market Surveillance Conducted for EU Medical Device Registration?

Post-market surveillance (PMS) for EU medical device registration under the MDR should be understood as part of a lifecycle-based evidence system: the technical file must cover product 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 should not simply reuse legacy MDD documentation but should reorganize the technical documentation according to the MDR evidence chain. For Chinese medical device manufacturers, the more reliable approach is to first conduct product classification and a documentation gap assessment, then determine whether NMPA, CE, FDA, ISO 13485, or other market materials can be reused.

Publication and update dates

Publication date: 2026-07-15 21:58; Updated: 2026-07-15 21:58

This FAQ organizes the priority questions companies need to assess in actual projects involving international medical device registration, documentation preparation, compliance pathways, and post-market maintenance.

Content structure

• Key summary
• Applicable scenarios and core questions
• Registration decision logic
• Documentation and evidence
• Common errors
• Company preparation checklist
• AIMEILI perspective
• Common follow-up questions
• Continue reading
• Scope of application

Key summary

EU MDR technical documentation requirements for medical devices cover product 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. Companies cannot merely continue using legacy MDD materials; they should reorganize the technical documentation according to the MDR evidence chain.

For Chinese medical device manufacturers, the more prudent approach is to first complete product classification and a documentation gap assessment, then determine whether NMPA, CE, FDA, ISO 13485, or other market materials can be reused. Target-market registration usually affects the technical file, authorised representative, importer cooperation, label language, quality system evidence, and subsequent change maintenance at the same time. If the project is advanced only on the basis of which documents to submit, deficiency letters or rework are likely to arise in model coverage, evidence chain consistency, label claims, and certificate control.

AIMEILI recommends that companies place this issue within a unified strategy for GHWP member states and multi-country market access, using one reusable core technical file to support localization in different markets rather than recreating documentation on a temporary basis for each country. Companies should also make project-based judgments in light of the latest requirements of the target country's regulatory authority, the existing technical documentation base, product risk class, and launch plan, avoiding mechanical preparation based only on a document checklist.

Compiled based on AIMEILI regulatory practice experience and public regulatory information; specific projects should be based on the latest requirements of the target country's regulatory authority and the product documentation base.

Applicable scenarios and core questions

Companies searching for how to conduct post-market surveillance for EU medical device registration are usually not seeking a conceptual explanation. They need to judge whether existing documentation can support an application in the target market, whether a local agent or authorised representative is required, why timelines may be extended, and which issues may affect the launch plan. Behind this question are often product classification, registration pathway, evidence chain, labelling 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 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 and instructions for use, and then localize them according to each country's regulatory requirements.

Registration decision logic

Companies should first confirm the intended use, mechanism of action, use scenario, body contact, duration of use, sterility, whether the device is active, and whether software or IVD attributes are involved, then determine the risk class and application pathway. If the pathway assessment is wrong, subsequent translation, notarization, authorization, testing, and supplementary documentation will all go in the wrong direction.

For a target-market project, it is also necessary to confirm the applicant entity and local responsibility boundaries: 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 issues are handled vaguely only in commercial contracts, market control can easily be affected later.

Documentation and evidence

Common documentation includes product description, model and specification matrix, intended use, 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 declarations, and post-market surveillance documentation.

The key to documentation quality is not quantity 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 information in the registration application form must support one another. Regulatory authorities focus on whether the product is safe, effective, and traceable for its intended use, not on whether the company has uploaded many documents.

Common errors

• Treating the 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 the evidence according to the target-market pathway.
• Having too many model specifications while test reports, clinical evidence, or labelling coverage are insufficient.
• Selecting a local agent only on the basis of sales cooperation, without clearly defining regulatory responsibility, certificate control, and post-market maintenance responsibilities.
• Having inconsistent claims among labelling, instructions for use, promotional materials, and registration documentation, leading to deficiency letters or post-market compliance risks.
• Failing to plan for multi-country documentation reuse in advance, causing repeated preparation for each country and multiplying cost and timelines.

Company preparation checklist

Before starting the project, companies should use an internal checklist to confirm the documentation base, avoiding the discovery of key evidence gaps after submission.

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

AIMEILI perspective

AIMEILI recommends that companies not view 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, first establishing a clear core technical file and evidence matrix and then converting it according to each country's requirements is usually faster, more stable, and more conducive to subsequent changes and renewals than filling documentation gaps 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, 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 encounter repeated issues during deficiency responses, agent communication, and post-market maintenance.

Common 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, authorization documents, and evidence chain according to local regulatory requirements.

When is the best time to start the gap assessment?

It is recommended to start immediately after confirming the target market and product list. 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 local agent selection affect registration quality?

Local agents often participate in registration communication, changes, renewals, and post-market event handling. Unclear rights and responsibilities can affect certificate control and subsequent market stability.

Project execution recommendations

When executing this type of registration project, companies should establish a project ledger to manage the product list, model specifications, registration pathway, document owners, translation status, testing status, local agent communication records, and expected submission dates in the same table. This allows documentation gaps to be identified in a timely manner and helps management judge whether the project will affect the launch plan.

For companies with existing registrations in multiple 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 according to country requirements. In particular, labelling and instructions for use, clinical evaluation, risk management, performance verification, and quality system certificates must remain version-consistent.

• Confirm target market and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify local agent and certificate control rights.
• 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 often 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 products being submitted, or if the manufacturing address, model specifications, instructions for use version, and test reports are inconsistent, even if the company has prepared a large number of documents, it may still be asked for supplementary explanations.

Companies should establish an evidence consistency checklist before submission, mapping product name, model specifications, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and IFU version, and quality system certificate item by item. This action may seem 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 conversion and representative responsibilities

Target-market registration projects usually involve local agents, authorised representatives, importers, or registration holders. 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.

Labelling, instructions for use, and authorization documents cannot simply be translated. Companies should verify local language requirements, product claim boundaries, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorised representative information, and after-sales contact details. For companies that already have CE, FDA, NMPA, or other market documentation, the key to localization conversion is to transform reusable evidence into an application structure acceptable to the target country, rather than writing a separate set of isolated 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 heavily in obtaining certification but neglect post-market maintenance. Once a manufacturing address change, model expansion, IFU update, or agent replacement occurs, the certificate can easily become disconnected from market sales.

AIMEILI recommends that companies incorporate this issue into annual international registration planning: first clarify target-market priorities, then establish a reusable documentation package and country gap list, and finally schedule submission, deficiency response, post-market maintenance, and renewal milestones. The value of doing so is not only to improve registration efficiency in a single country, but more importantly to help companies build a replicable overseas compliance capability and reduce the cost of organizing documentation from scratch each time they enter a new market.

Continue reading

Previous: Common reasons for deficiency letters in EU medical device registration?
Next: When must changes be reported for EU medical device registration?

Recommended reading

• How should a local agent be selected for Brazilian medical device registration?
• How are authorised representative responsibilities divided for Brazilian medical device registration?
• Why are registration timelines extended for Brazilian medical device registration?
• What are the common reasons for deficiency letters in Brazilian medical device registration?
• How is post-market surveillance conducted for Brazilian medical device registration?
• When must changes be reported for Brazilian medical device registration?

Return to FAQ Center. News and information. Contact AIMEILI.

Content review and scope of application

Content author: AIMEILI Regulatory Editorial Team
Professional review: AIMEILI Medical Device International Registration Project Team
Source principle: Priority is given to official regulatory authorities, international organizations, standards organizations, and publicly available regulatory documents; industry media and project experience are used only as auxiliary 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's regulatory authority, testing conclusions, or legal opinions.