How Should a Post-Market Surveillance (PMS) Plan Be Prepared Under EU MDR?

How Should a Post-Market Surveillance (PMS) Plan Be Prepared Under EU MDR?

Answer: Under EU MDR, a PMS plan is not a post-certification formality; it is part of the technical documentation and must show how the manufacturer will continuously collect, analyze, and use post-market data throughout the product lifecycle. The plan should cover complaints, adverse events, serious incidents, trend reporting, literature, user feedback, certificate maintenance, PMCF necessity, risk management updates, clinical evaluation updates, labeling and IFU updates, and corrective and preventive actions (CAPA). It must be proportionate to the device risk class, intended purpose, clinical evidence, and market scale, and must define data sources, frequency, responsibilities, analytical methods, and trigger mechanisms. A template-based PMS plan that cannot connect to the CER, PMCF, PSUR, or PMS report is likely to be considered insufficient by a notified body.

Published: 2026-07-08 09:00

Updated: 2026-07-08 09:00

Content Overview

This FAQ addresses priority questions that companies need to judge in international medical device registration, document preparation, compliance pathways, and post-market maintenance.

• Key Summary
• Reference Basis
• Who Should Read This
• Step 1: Clarify the Regulatory Position of the PMS Plan
• Step 2: Design Data Sources and Analysis Frequency
• Step 3: Connect PMS Results to CER, PMCF, and Risk Management
• Common Errors
• AIMEILI Recommendations
• Internal Checklist
• Continue Reading
• Applicability Boundaries

Key Summary

Under EU MDR, a PMS plan is not a formality to be completed after certification; it is part of the technical documentation. It demonstrates how the manufacturer will continuously collect, analyze, and use post-market data throughout the product lifecycle. When preparing a PMS plan, companies should cover complaints, adverse events, serious incidents, trend reporting, literature, user feedback, certificate maintenance, PMCF necessity, risk management updates, clinical evaluation updates, labeling and IFU updates, and CAPA.

The PMS plan should match the product risk class, intended purpose, clinical evidence, and market scale, and should specify data sources, frequency, responsible persons, analytical methods, and trigger mechanisms. If the PMS plan is only a copied template and cannot connect to the CER, PMCF, PSUR, or PMS report, a notified body is likely to consider the system insufficient during review.

Reference Basis

Official source: European Commission / MDCG

Source link: https://health.ec.europa.eu/document/download/a9ad86b7-1b8e-4bae-beb4-48b2b3ed2f05_en?filename=mdcg_2025-10_en.pdf

MDCG 2025-10 states that Article 84 of the MDR and Article 79 of the IVDR require the PMS system to be based on a PMS plan, and that the PMS plan forms part of the technical documentation; the PMS plan requirements are set out in Annex III of the MDR/IVDR.

Who Should Read This

This article is intended for manufacturers preparing CE MDR technical documentation, manufacturers already under notified body review, or manufacturers that have obtained a CE certificate but need to maintain a PMS/PMCF system. It is particularly relevant to Class IIa, IIb, and III devices, implantable devices, active devices, medical device software, and products under continuous pressure to update clinical evidence.

Step 1: Clarify the Regulatory Position of the PMS Plan

The PMS plan belongs to the technical documentation system; it is not a complaints process kept separately by the after-sales department. It should connect risk management, clinical evaluation, PMCF, vigilance, trend reporting, CAPA, labeling updates, and product improvement. Under the MDR, manufacturers need to proactively and systematically collect post-market data and use real-world use information to continuously confirm product safety and performance.

Step 2: Design Data Sources and Analysis Frequency

The PMS plan should list data sources, such as complaints, user feedback, distributor feedback, service records, adverse events, recalls or field safety corrective actions, literature, information on similar products, registration databases, clinical follow-up, PMCF activities, and regulatory notifications. Different data sources should have defined collection frequency, responsible department, analytical method, escalation path, and record requirements. High-risk products should not rely only on passive complaint data.

Step 3: Connect PMS Results to CER, PMCF, and Risk Management

The value of the PMS plan lies in bringing post-market data into product decisions. If new risks, complaint trends, performance degradation, use errors, or vigilance signals from similar products are identified, this should trigger updates to the risk management file, clinical evaluation, PMCF plan, labeling and IFU, or CAPA. PMS, PSUR, PMS report, and CER should be mutually traceable.

Common Errors

• The PMS plan is only a copied template.
• Data sources are not designed according to the product risk class.
• The complaint process is disconnected from clinical evaluation.
• The PMCF necessity assessment is too simple.
• No trend analysis thresholds are set.
• PMS outputs do not feed into risk management and technical documentation updates.

Notified bodies usually do not merely check whether a PMS document exists; they examine whether the PMS system actually operates.

AIMEILI Recommendations

AIMEILI recommends that manufacturers treat the PMS plan as a product lifecycle monitoring program, rather than a document checklist. For each product family, the monitoring objectives, data sources, frequency, responsible persons, trigger conditions, and output documents should be clearly defined. For manufacturers planning to maintain CE MDR certificates long term, PMS system maturity directly affects annual surveillance, certificate maintenance, and subsequent change reviews.

Internal Checklist

• Is the PMS plan included in the technical documentation and aligned with Annex III?
• Do data sources cover complaints, vigilance, literature, user feedback, and PMCF?
• Are collection frequency, responsible persons, analytical methods, and escalation conditions defined?
• Can PMS outputs update risk management, CER, PMCF, and labeling and IFU?
• For Class IIb/III or implantable products, are PSUR and higher-frequency monitoring considered?
• Are trend analysis, CAPA, and regulatory reporting trigger mechanisms established?

Continue Reading

• Previous: What compliance obligations should be confirmed before TGA medical device registration in Australia?
• Next: What should be noted when selling medical device software apps on EU online platforms?

Recommended Reading

• How do EUDAMED and SSCP management requirements affect MDR certificate holders?
• What should companies prepare before TGA medical device registration in Australia?
• Can CE documentation be reused for Singapore HSA medical device registration?
• What core documents are required for UAE MOHAP medical device registration?
• Why is the Brazil ANVISA medical device registration cycle so long?
• What is the difference between a Vietnam medical device import license and registration certificate?

Content Review and Applicability Boundaries

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 materials; industry media and project experience are used only as supporting judgment.

Applicability boundary: This article is for preliminary understanding, document preparation, and project planning. It does not replace the formal requirements of the target country regulatory authority, testing conclusions, or legal advice.