Post-Market Surveillance Under EU MDR: A Complete Guide to PMS, PMCF, and PSUR

Post-market surveillance (PMS) is one of the most consequential pillars of the EU Medical Device Regulation (MDR 2017/745), and its requirements represent a fundamental departure from what manufacturers were accustomed to under the legacy Medical Device Directives (MDD 93/42/EEC and AIMDD 90/385/EEC). Under the MDR, PMS is not an afterthought or a checkbox exercise performed once a device reaches the market. It is a continuous, systematic, and documented process that runs throughout the entire lifecycle of a medical device, from initial market placement through to decommissioning. The legal foundation for PMS is established primarily in MDR Articles 83 through 86, with additional requirements detailed in Annex III. Article 83 sets out the overarching obligation for manufacturers to plan, establish, document, implement, maintain, and update a PMS system for each device. Article 84 specifies the content of the PMS plan. Article 85 defines the PMS report required for Class I devices, while Article 86 establishes the periodic safety update report (PSUR) required for Class IIa, IIb, and III devices. Beyond these core articles, PMS obligations are interwoven throughout the regulation, appearing in the context of clinical evaluation (Article 61), vigilance (Articles 87-92), and the General Safety and Performance Requirements (Annex I). The Medical Device Coordination Group (MDCG) has further elaborated on PMS expectations through guidance documents such as MDCG 2020-7 on PMCF plan and PMCF evaluation report templates, and MDCG 2020-8 on PMCF evaluation report templates for legacy devices. Manufacturers should treat these MDCG guidance documents as de facto requirements, since Notified Bodies and competent authorities use them as benchmarks during assessments.

The PMS plan is the foundational document of the entire PMS system and must be established before a device is placed on the market. Article 84 of the MDR specifies that the PMS plan shall address the collection and utilisation of available information, with particular attention to the aspects enumerated in the regulation. Specifically, the PMS plan must include a proactive and systematic process for collecting any information referenced in Annex III Section 1.1, including data from users, distributors, importers, and healthcare professionals. It must describe the effective and appropriate methods and processes for assessing collected data, including adequate statistical methods and data quality criteria. The plan must define suitable indicators and threshold values for triggering corrective or preventive actions, including a re-assessment of the benefit-risk determination and the risk management output. It must specify methods and protocols to manage the events described in Articles 87 to 92, covering vigilance reporting, field safety corrective actions, and trend reporting. The plan must also address the communication mechanisms between the manufacturer and competent authorities, Notified Bodies, economic operators, and users regarding PMS findings. Furthermore, the PMS plan must reference the procedures and methods for monitoring the state of the art for the particular device category, including any equivalent or similar devices already on the market. It must cover the process for identifying and implementing any necessary corrective or preventive actions, confirm the effectiveness of those actions, and describe how the PMS findings feed back into the clinical evaluation, risk management, and design and manufacturing processes. A common deficiency observed during Notified Body audits is a PMS plan that is generic rather than device-specific. Each device or device group must have its own PMS plan tailored to the particular risks, intended use, and clinical context of that specific product. A PMS plan that merely restates the regulatory requirements without articulating how they will be implemented for the specific device in question will not satisfy auditors.

The MDR distinguishes between two post-market surveillance reporting documents based on device classification: the PMS report for Class I devices and the periodic safety update report (PSUR) for Class IIa, IIb, and III devices. While both documents serve the purpose of summarizing PMS findings, the PSUR carries significantly more detailed requirements and must be submitted at defined intervals. For Class I devices, Article 85 requires manufacturers to compile a PMS report that summarizes the results and conclusions of the analyses of PMS data, together with a rationale and description of any preventive or corrective actions taken. This report must be updated when necessary and be available to the competent authority upon request. While the PMS report for Class I devices does not have a mandated submission frequency, it must be kept current and reflect ongoing surveillance activities. For Class IIa devices, Article 86 requires a PSUR to be updated at least every two years. For Class IIb and Class III devices, the PSUR must be updated at least annually. The PSUR is a substantially more comprehensive document than the Class I PMS report. It must include the conclusions of the benefit-risk determination, the main findings of the PMCF evaluation report, the volume of sales of the device and an estimation of the size and other characteristics of the population using the device, as well as the usage frequency of the device where practicable. A critical distinction is the submission and review pathway: PSURs for Class III devices and Class IIb implantable devices must be submitted to the Notified Body as part of the ongoing conformity assessment. The Notified Body evaluates the PSUR and records its assessment in a report that is shared with the competent authority. PSURs for Class IIa and non-implantable Class IIb devices must be made available to the Notified Body upon request and to the competent authority upon request. Once EUDAMED becomes fully functional, PSURs for Class IIa, IIb, and III devices must be uploaded to the electronic system. Manufacturers should plan for this requirement now rather than waiting for the mandatory date.

Post-market clinical follow-up (PMCF) is a specific and proactive subset of PMS that focuses on the clinical performance and safety of a device after it has been placed on the market. The legal basis for PMCF is found in Article 61(11) of the MDR, which states that PMCF shall be understood to be a continuous process that updates the clinical evaluation, and in Annex XIV Part B, which details the specific requirements for PMCF. The fundamental purpose of PMCF is to proactively collect and evaluate clinical data from the use of an already CE-marked device in order to confirm the clinical safety and performance throughout the expected lifetime of the device, to identify previously unknown side-effects and monitor the identified side-effects and contraindications, to identify and analyse emergent risks on the basis of factual evidence, to ensure the continued acceptability of the benefit-risk ratio, and to identify possible systematic misuse or off-label use. PMCF is not optional. MDCG guidance 2020-7 makes clear that a justification for not conducting PMCF activities is only acceptable in exceptional circumstances, and even then, the justification must be detailed and scientifically sound. The guidance states that merely claiming that the device is well-established or has been on the market for many years is not sufficient justification for omitting PMCF. Notified Bodies have increasingly scrutinised this area, and rejections of PMCF justifications that amount to "the device has a long history of safe use" without substantive supporting analysis have become common. The scope of PMCF activities can include PMCF studies (clinical investigations conducted post-market), PMCF surveys (structured feedback from healthcare professionals or patients), analysis of published clinical literature, analysis of data from registries, and real-world evidence analysis. The choice of PMCF methods must be justified in the PMCF plan and must be proportionate to the risk class of the device, the nature of the device, and any residual risks or unanswered clinical questions identified in the clinical evaluation.

The PMCF plan is a required component of the clinical evaluation plan and, by extension, of the technical documentation. Annex XIV Part B of the MDR specifies the minimum content for the PMCF plan. The plan must specify the general methods and procedures of PMCF activities to be undertaken, including PMCF studies, PMCF surveys, or other systematic activities. It must describe the specific objectives to be addressed by the PMCF, with reference to the general safety and performance requirements that need ongoing confirmation and any residual risks or unanswered clinical questions from the pre-market clinical evaluation. It must provide a rationale for the chosen methodology, describe the reference to the relevant parts of the clinical evaluation report and risk management documentation, and specify the timelines, milestones, and deliverables associated with each PMCF activity. The PMCF plan must also address how the PMCF will evaluate interactions of the device with other devices, medications, or substances, where relevant. It should reference the methods for capturing and analysing data from complaints, feedback from users, and published literature as part of the PMCF process. MDCG 2020-7 provides a template that many manufacturers and Notified Bodies use as a reference structure for the PMCF plan. While the template is not mandatory, deviating from it without justification may raise questions during audit. The PMCF evaluation report documents the results and analysis of all PMCF activities. It must be updated regularly as new data become available and must be part of the clinical evaluation report and the technical documentation. The PMCF evaluation report should present the data collected, the analysis performed, the conclusions drawn regarding the clinical safety and performance of the device, and any actions taken or recommended as a result of the findings. For manufacturers of Class III and implantable devices, the PMCF evaluation report receives particularly close scrutiny from Notified Bodies. The report must demonstrate that PMCF activities were actually conducted as specified in the plan, that data were collected and analysed using appropriate methods, and that the conclusions are supported by the evidence. A PMCF evaluation report that merely restates the plan without presenting actual data and analysis will be rejected.

A robust PMS system draws on multiple data sources to build a comprehensive picture of device performance in the field. The MDR and associated MDCG guidance documents identify several categories of data that manufacturers must systematically collect and evaluate. Complaint data from customers, users, and patients represents the most direct source of information about device performance issues. Manufacturers must have processes in place to receive, log, investigate, and trend complaints, distinguishing between those that constitute reportable incidents and those that reflect performance issues not meeting the incident reporting threshold. Vigilance data, both the manufacturer's own incident reports and those reported by other manufacturers of equivalent or similar devices, provides critical safety intelligence. Under the MDR, manufacturers are required to monitor publicly available databases for vigilance information, including national competent authority databases and, once fully functional, EUDAMED. Published scientific literature must be reviewed systematically and regularly. This is not a one-time literature search conducted during the initial clinical evaluation; rather, it is an ongoing process that must be documented in the PMS plan and executed according to a defined protocol with specified search terms, databases, inclusion and exclusion criteria, and review intervals. Clinical data from registries, both disease-specific and device-specific, represent an increasingly important data source. The MDR encourages the use of registry data, and several Notified Bodies have begun asking manufacturers whether relevant registries exist and, if so, why data from those registries are not being used. Real-world evidence (RWE) from electronic health records, insurance claims databases, and other sources can supplement traditional clinical data, although the quality and applicability of such data must be critically assessed. User feedback that does not constitute a formal complaint, such as reports from sales representatives, installation technicians, and clinical application specialists, can provide early signals of emerging issues. Manufacturers should ensure that mechanisms exist to capture this information systematically rather than allowing it to remain in informal channels. Data from servicing, maintenance, and calibration activities can reveal trends in device degradation, component failure, or performance drift that may not be apparent from complaint data alone.

One of the most significant shifts from the MDD to the MDR is the explicit expectation that PMS be proactive rather than merely reactive. Under the legacy directives, many manufacturers operated PMS systems that were essentially complaint-handling mechanisms: they waited for problems to be reported, investigated those reports, and took corrective action when warranted. The MDR demands a fundamentally different approach. Proactive surveillance means that the manufacturer actively seeks out information about device performance rather than waiting for adverse events to be reported. This includes conducting regular literature reviews, monitoring registries and databases, surveying users about their experience with the device, analysing trends in complaint data before they reach statistical significance, and engaging with clinical experts to understand the evolving state of the art. Regulators and Notified Bodies assess whether a manufacturer's PMS system is genuinely proactive or merely reactive in several ways. They examine whether the PMS plan specifies proactive data collection activities with defined timelines and responsible persons. They review whether literature searches have been conducted at the specified intervals and whether the search results have been meaningfully analysed. They look for evidence that complaint data have been trended and that trending analysis has been used to identify emerging risks or performance issues. They assess whether the manufacturer has engaged with relevant registries and, if not, whether the omission has been justified. They also evaluate whether the manufacturer monitors the regulatory landscape for changes in applicable standards, guidance documents, or regulatory requirements that could affect the device's benefit-risk profile. A PMS system that is exclusively reactive, that waits for incidents to occur and then responds, will be viewed as non-compliant with MDR Article 83, which explicitly requires systematic processes for proactively collecting and utilising information. Manufacturers transitioning from MDD to MDR should conduct a gap analysis of their existing PMS processes against the proactive surveillance expectations of the MDR, and should implement the necessary enhancements well before their MDR conformity assessment.

Article 88 of the MDR introduces a specific obligation for trend reporting that had no direct equivalent under the MDD. Manufacturers must report to competent authorities any statistically significant increase in the frequency or severity of incidents or expected undesirable side-effects that are not serious, and that have a significant impact on the benefit-risk analysis. This obligation requires manufacturers to define appropriate statistical methods and threshold values in their PMS plan, as required by Article 84, and to apply those methods systematically to their surveillance data. The choice of statistical method must be appropriate to the data characteristics and the device context. Common approaches include control charts (such as CUSUM or EWMA charts) for monitoring event rates over time, chi-squared tests or Fisher's exact tests for comparing observed versus expected event frequencies, time-series analysis for detecting shifts in trend, and Bayesian methods for incorporating prior knowledge into trend assessments. The threshold values that trigger investigation or reporting must be defined prospectively in the PMS plan. These thresholds should be clinically meaningful and statistically justified. Setting thresholds too high risks missing genuine safety signals; setting them too low generates excessive noise and diverts resources from genuine issues. The MDCG has not prescribed specific statistical methods, recognising that the appropriate approach depends on the device, the risk profile, the volume of data, and the nature of the events being monitored. However, the expectation is that manufacturers can demonstrate that their chosen methods are scientifically sound and appropriate for the data they are analysing. Notified Bodies will ask to see not only the results of trend analyses but also the rationale for the methods and thresholds chosen, the raw data underlying the analyses, and the conclusions drawn. A common audit finding is that manufacturers have defined statistical methods in their PMS plan but have not actually implemented them, or that the methods defined are inappropriate for the data volumes involved. For manufacturers with small complaint volumes, traditional frequentist statistical methods may lack sufficient power to detect meaningful trends. In such cases, alternative approaches such as Bayesian analysis, qualitative trend assessment with expert review, or pooling data across product families may be appropriate, provided the rationale is documented.

PMS does not operate in isolation. The MDR explicitly requires that PMS findings feed back into the manufacturer's risk management process, clinical evaluation, and quality management system. This integration is one of the hallmarks of a mature PMS system and is an area where many manufacturers fall short. The connection between PMS and risk management is perhaps the most critical integration point. ISO 14971:2019, the harmonised standard for risk management of medical devices, requires manufacturers to collect and review information about the medical device in the production and post-production phases. PMS data should systematically inform updates to the risk management file, including the identification of new hazards or hazardous situations not anticipated during pre-market risk analysis, revised probability estimates for known risks based on field data, assessment of whether the residual risks identified in the risk management report remain acceptable in light of post-market evidence, and evaluation of the effectiveness of risk control measures based on their real-world performance. When PMS data indicate that the benefit-risk ratio may have shifted, manufacturers must re-evaluate the benefit-risk determination documented in the clinical evaluation report and, if necessary, implement corrective actions. The corrective and preventive action (CAPA) system serves as the primary mechanism for translating PMS findings into tangible improvements. When PMS data reveal a systematic issue such as a recurring complaint pattern, a trend in a specific failure mode, or a newly identified risk, the manufacturer should initiate a CAPA investigation. The CAPA process should trace back to the specific PMS data that triggered the investigation, document the root cause analysis, define corrective and preventive actions with assigned responsibilities and timelines, and verify and validate the effectiveness of those actions. The results of CAPA activities, in turn, should be reflected in updated PMS reporting (the PMS report or PSUR), in updates to the risk management file, and in updates to the clinical evaluation report where the CAPA relates to clinical performance or safety. This circular flow of information, from market data through PMS into risk management and CAPA and back into design, manufacturing, and documentation, is what the MDR envisions as a lifecycle approach to device safety. Manufacturers who treat PMS, CAPA, risk management, and clinical evaluation as separate, disconnected activities will struggle to demonstrate compliance.

Drawing on our extensive experience supporting manufacturers through MDR conformity assessments, we observe recurring patterns in the PMS-related findings raised by Notified Bodies. Understanding these common deficiencies can help manufacturers prepare more effectively and avoid delays in certification. The most frequently cited deficiency is a PMS plan that is generic and not device-specific. Manufacturers who develop a single PMS plan template and apply it across their entire product portfolio without tailoring it to the specific risks, clinical context, and data sources relevant to each device or device group will receive non-conformities. Each PMS plan must demonstrate that the manufacturer has considered the particular characteristics and risk profile of the specific device. A second common finding is insufficient PMCF justification. As noted earlier, claiming that a device is well-established and has a long market history is not sufficient to justify the absence of proactive PMCF activities. Notified Bodies expect to see either a substantive PMCF plan with defined activities, timelines, and deliverables, or, in exceptional cases, a detailed scientific justification for why PMCF is not necessary. Third, inadequate complaint trending is a frequent finding. Many manufacturers log and investigate individual complaints but fail to analyse complaint data in aggregate to identify trends, patterns, or emerging risks. The MDR requires systematic trending with defined statistical methods and threshold values. Fourth, failure to monitor the state of the art is cited when manufacturers cannot demonstrate that they have systematically reviewed scientific literature, regulatory guidance, and applicable standards to determine whether the device's benefit-risk profile remains acceptable in light of the current state of clinical knowledge. Fifth, missing or incomplete feedback loops between PMS and risk management are flagged when PMS data are collected and analysed but the results are not reflected in updates to the risk management file, clinical evaluation report, or design documentation. Sixth, inadequate PMS reporting is found when PMS reports or PSURs lack substantive analysis and present only raw data without interpretation, conclusions, or evidence of action taken. Seventh, some manufacturers fail to include data from all relevant sources, relying solely on complaint data while neglecting literature, registries, vigilance databases, and user feedback. Each of these deficiencies can result in a major non-conformity that delays certification until the issue is resolved to the Notified Body's satisfaction.

While the MDR does not prescribe a specific template for the PSUR, the content requirements set out in Article 86 and the expectations articulated in MDCG guidance provide a clear framework for what must be included. A well-structured PSUR should begin with a summary of the device description, its intended purpose, the target population, and the classification rationale. This context-setting section allows the reader to understand the device and its regulatory status without needing to cross-reference the full technical documentation. The PSUR should then present a summary of the PMS plan, highlighting the data collection methods, data sources, review intervals, and statistical methods employed during the reporting period. The next section should present the PMS data collected during the reporting period, organised by data source. This includes a quantitative summary of complaints received, categorised by type (e.g., device malfunction, user error, adverse event), with comparison to previous reporting periods. It should include a summary of reportable incidents and any field safety corrective actions taken. It should present the results of literature reviews conducted during the period, highlighting any publications with implications for the device's safety or performance profile. Data from registries, surveys, or other proactive surveillance activities should be included. The PSUR must present the conclusions of the PMCF evaluation, summarising the findings of any PMCF studies or other PMCF activities conducted during the period. The benefit-risk determination must be re-evaluated in light of the new data collected, with an explicit conclusion as to whether the benefit-risk ratio remains acceptable. If any changes to the benefit-risk assessment have occurred, the actions taken or planned must be described. The PSUR should include the volume of sales or units distributed during the reporting period and, where practicable, an estimation of the size and characteristics of the user and patient populations. This information is essential for calculating event rates and putting complaint and incident data into context. Finally, the PSUR should include a summary of corrective and preventive actions initiated, ongoing, or completed during the reporting period, with an assessment of their effectiveness. The document should conclude with an overall assessment of whether the device continues to meet the general safety and performance requirements and any actions planned for the next reporting period. For Class III and implantable devices, the PSUR is submitted to the Notified Body, and manufacturers should anticipate detailed review and potential requests for additional information or clarification.

EUDAMED, the European Database on Medical Devices, is designed to serve as a central hub for regulatory information exchange, and its vigilance reporting module will fundamentally change how PMS data flows between manufacturers, competent authorities, and Notified Bodies. While EUDAMED has experienced repeated delays in its full deployment, manufacturers must prepare for the system's eventual mandatory use, as several modules are already operational and the vigilance module is expected to become mandatory in the near term. Under the MDR, manufacturers are required to report serious incidents and field safety corrective actions (FSCAs) through EUDAMED once the system is fully functional. Until then, reporting continues through the existing national competent authority reporting mechanisms, primarily using MedDev 2.12/1 forms or their national equivalents. However, the MDR introduces several enhancements to vigilance reporting that manufacturers should already be implementing. The reporting timelines under the MDR are more granular than under the MDD. Serious incidents involving a serious public health threat must be reported immediately but no later than 2 days after awareness. Incidents involving death or an unanticipated serious deterioration in health must be reported within 10 days. All other serious incidents must be reported within 15 days. These timelines apply from the date the manufacturer becomes aware of the event and the causal relationship with the device, or where such relationship is reasonably possible. The trend reporting obligation under Article 88 is entirely new and requires manufacturers to report statistically significant increases in non-serious incidents or expected side-effects to competent authorities through EUDAMED. This obligation reinforces the need for robust statistical trending capabilities in the PMS system. Manufacturers should prepare for EUDAMED by ensuring that their internal incident management processes align with the data fields and reporting formats expected by the system, by training relevant personnel on EUDAMED functionality, and by conducting dry-run exercises with test data. The vigilance module will also provide manufacturers with access to information about incidents reported with similar devices, which can inform their own PMS activities. Proactive monitoring of this information, once available, should be incorporated into the PMS plan.

For manufacturers who are building or enhancing their PMS system to meet MDR requirements, a structured implementation timeline helps ensure that all elements are addressed systematically and that the system is operational before the Notified Body audit. In the first phase, spanning approximately months one through three, manufacturers should conduct a gap analysis of their existing PMS processes against MDR requirements, MDCG guidance, and Notified Body expectations. This gap analysis should cover the PMS plan, complaint handling, vigilance reporting, literature monitoring, PMCF planning, trend analysis capabilities, reporting processes, and feedback mechanisms to risk management and clinical evaluation. The output is a prioritised action plan with defined responsibilities and timelines. In the second phase, covering months three through six, manufacturers should develop or revise the PMS plan for each device or device group. This includes defining data sources, collection methods, review frequencies, statistical methods, threshold values, and responsible roles. In parallel, the PMCF plan should be developed or updated, with clearly defined PMCF objectives, methods, timelines, and deliverables. Literature search protocols should be established, with defined search terms, databases, inclusion and exclusion criteria, and review intervals. During the third phase, from months six through nine, manufacturers should implement the operational processes: setting up or enhancing complaint trending and analysis tools, establishing literature monitoring schedules, configuring vigilance reporting workflows aligned with MDR timelines, and building the data collection and analysis infrastructure for PMCF activities. Personnel should be trained on their PMS responsibilities and on the specific procedures and tools being deployed. In the fourth phase, covering months nine through twelve, manufacturers should conduct a full cycle of PMS activities, producing the first PMS report or PSUR under the MDR framework. This includes executing the first comprehensive literature review, running the first trend analyses, initiating PMCF activities as defined in the plan, and compiling the results into a PMS report or PSUR that meets the content requirements outlined earlier. This first full cycle serves as both a validation of the system and a source of documentation for the Notified Body audit. Manufacturers should anticipate that Notified Bodies will want to see evidence that the PMS system has been operationally tested and has produced meaningful outputs, not merely that procedures have been written.

A PMS system is not a static set of documents and procedures. The MDR envisions PMS as a dynamic, continuously improving process that adapts to new data, new risks, and evolving regulatory expectations. Manufacturers should build review mechanisms into their PMS system that ensure regular reassessment and enhancement. The PMS plan itself should be reviewed at least annually, or more frequently if triggered by significant new data, a change in the regulatory landscape, or a corrective action affecting the device. The review should assess whether the data sources identified in the plan remain relevant and complete, whether the statistical methods and thresholds remain appropriate, whether the PMCF activities are progressing according to plan and generating useful data, and whether the feedback mechanisms to risk management and clinical evaluation are functioning effectively. Each PMS report or PSUR cycle provides an opportunity to evaluate the effectiveness of the overall PMS system. Manufacturers should track key performance indicators such as complaint response times, literature review timeliness, CAPA closure rates, and the time from signal detection to investigation initiation. These metrics help identify process bottlenecks and areas for improvement. It is also critical to monitor external developments that may affect PMS requirements. Changes to harmonised standards, new MDCG guidance documents, updated Notified Body expectations communicated through audit findings or published position papers, and developments in clinical practice or the state of the art should all be tracked and assessed for their impact on the PMS system. Manufacturers who approach PMS as a living, evolving system rather than a fixed set of deliverables will be better positioned for ongoing regulatory compliance and will derive genuine business value from their surveillance activities through improved product quality, reduced field failures, and enhanced customer satisfaction.

Manufacturers transitioning legacy devices from MDD certification to MDR face specific PMS challenges that deserve careful attention. Under the MDD, PMS obligations were significantly less prescriptive, and many manufacturers operated with minimal post-market surveillance infrastructure. The MDR requires a step-change in PMS capability, and this gap is often underestimated in transition planning. For legacy devices, the PMS plan must address the full history of the device on the market, not just the period from the MDR application date. This means that manufacturers must retrospectively gather and analyse complaint data, incident reports, literature, and any other relevant information from the device's entire market history to establish a baseline for ongoing surveillance. The clinical evaluation for a legacy device must incorporate all available post-market clinical data, and the PMCF plan must address any clinical questions that remain open after this retrospective analysis. MDCG 2020-8 provides specific guidance on the PMCF evaluation report template for legacy devices, acknowledging that the evidentiary landscape for a device with years or decades of market history is different from that of a newly developed device. Notified Bodies assessing MDR applications for legacy devices pay close attention to whether the manufacturer can demonstrate continuous and adequate post-market surveillance throughout the device's market history, even if the formal PMS system was less structured under the MDD. Gaps in surveillance history are viewed critically, and manufacturers may need to conduct retrospective analyses or enhanced PMCF activities to compensate for periods of limited data collection. The transition period is an opportunity to establish a robust, MDR-compliant PMS system that serves the manufacturer well for the long term, rather than viewing it as a regulatory hurdle to be cleared with minimum effort.

The relationship between PMS and clinical evaluation is bidirectional and continuous. Article 61(11) of the MDR states that the clinical evaluation and its documentation shall be updated throughout the lifecycle of the device with clinical data obtained from PMCF and through PMS. This means that the clinical evaluation report (CER) is a living document that must be revised whenever new PMS data affect the conclusions regarding clinical safety, performance, or the benefit-risk ratio. In practice, this requires manufacturers to establish clear triggers for CER updates. These triggers should include significant changes in the complaint profile, new or updated literature that affects the evidence base, results from PMCF studies or surveys, changes in the state of the art, new or revised applicable standards, field safety corrective actions, and changes to the device or its intended purpose. The frequency of CER updates should be defined in the clinical evaluation plan and should be proportionate to the device classification and risk profile. For Class III and implantable devices, annual CER updates are generally expected. For lower-risk devices, the update frequency may be less frequent but must be justified. Each CER update should clearly document the new data considered, the analysis performed, and the impact on the overall clinical evaluation conclusions. The PMS system must be designed to flag data that may trigger a CER update and to route that information to the person or team responsible for the clinical evaluation. This requires clear roles, responsibilities, and escalation procedures within the organisation. Manufacturers who maintain a clear, documented link between their PMS outputs and their clinical evaluation process will find that Notified Body audits proceed more smoothly, as auditors can readily verify that the lifecycle approach required by the MDR is being implemented in practice rather than merely described in procedures.

The volume and complexity of PMS data under the MDR, spanning complaints, incidents, literature, registry data, PMCF results, and trend analyses, increasingly necessitate dedicated software tools and digital infrastructure to manage effectively. While spreadsheet-based approaches may be adequate for manufacturers with a small number of simple, low-risk devices, they become unwieldy and error-prone as device portfolios grow and data volumes increase. Modern PMS software solutions typically provide integrated modules for complaint management with automated classification and trending, incident reporting with configurable workflow and regulatory timeline tracking, literature monitoring with search automation and relevance scoring, PMCF data capture and analysis, statistical trending with configurable control charts and alerting thresholds, and integrated reporting that pulls data from all sources into PMS report and PSUR templates. When selecting PMS software, manufacturers should evaluate whether the system supports the full range of data sources required by the MDR, whether it can be configured to match the specific PMS plan requirements for each device, whether it provides audit trail functionality consistent with the quality management system requirements, whether it integrates with existing systems such as the complaint management system, CAPA system, and document management system, and whether it supports EUDAMED data formats and reporting requirements. Regardless of the tooling chosen, the underlying principle is that PMS data must be traceable, auditable, and accessible. Notified Bodies expect to be able to trace any conclusion in a PMS report or PSUR back to the underlying data, and to verify that the data were collected, analysed, and reported according to the processes defined in the PMS plan. Manufacturers should also consider the human resources required to operate the PMS system effectively. PMS is not solely a quality assurance function; it requires input from clinical, regulatory, engineering, and commercial teams. Clear role definitions and adequate training are essential to ensure that PMS activities are performed consistently and competently.

Post-market surveillance under the MDR is a demanding, multifaceted obligation that requires regulatory expertise, clinical knowledge, statistical capability, and operational discipline. At Swiss MPC, we work with medical device manufacturers across Europe and globally to build PMS systems that are not only compliant with MDR requirements but also operationally efficient and genuinely informative. Our PMS consulting services cover the full scope of post-market surveillance, from initial gap analysis and PMS plan development through PMCF planning and execution, trend analysis methodology design, PSUR compilation, and preparation for Notified Body audits. We bring hands-on experience from supporting manufacturers through MDR conformity assessments with leading European Notified Bodies, and we understand the specific expectations and common findings that arise during PMS-related audit activities. Our approach is practical and device-specific. We do not deliver generic templates; instead, we work with your team to develop PMS documentation and processes that reflect the particular risks, clinical context, and data landscape of your specific devices. Whether you are transitioning a legacy device portfolio from MDD to MDR, launching a new device under the MDR framework, or seeking to enhance an existing PMS system that has been found deficient during audit, our senior regulatory consultants provide the expertise and structured methodology to achieve and maintain compliance. We also support manufacturers with PMCF study design and management, literature search protocol development, statistical trending methodology selection and implementation, and EUDAMED preparation. Our goal is to help you establish a PMS system that satisfies regulatory requirements while also delivering actionable insights that improve product quality and patient safety. For a confidential discussion of your post-market surveillance requirements, contact Swiss MPC at info@swissmpc.com or call +41 44 586 72 67. Our regulatory team responds within one business day with an initial assessment and recommended next steps.