Techical Document
Last Updated: 30 June 2026
Under EU MDR, medical device manufacturers must have a Post Market Surveillance (PMS) system and a well-trained team in place to stay compliant. Our Medical devices Post Market Surveillance (PMS) Services support this work by helping teams collect, review, and act on real world device data. An effective PMS system gives you continuous follow-up data on how your device performs. By focusing on this, you keep your products safe and effective once they are on the market. We help you identify product issues early, making safety reporting easier for your team.
Medical devices Post Market Surveillance (PMS) Services and Medical Device Quality Management System Integration
When you sell a device, you cannot simply wait for complaints. Under the Medical Devices Regulation (EU) 2017/745, Medical devices Post Market Surveillance (PMS) Services must be built into a Medical device Quality Management System. The effort you put into this system must match the risk class of your device. Monitoring starts when the first unit goes on sale and continues until the final model completes its intended lifetime. You also need to keep top management informed through regular updates during formal reviews.
Technical Documentation for Medical Devices Post Market Surveillance (PMS) Services
Your entire strategy must be driven by a structured PMS plan. For standard products, this plan forms part of your technical documentation. The plan should also connect with the Medical device Quality Management System so that surveillance findings lead to controlled actions. You can cover a single device or a device family that shares the same design and manufacturing characteristics. Keep the documentation clear, organized, and easy to search. Your plan must show how you collect information from serious incidents, field safety corrective actions (FSCAs), technical literature, competitor data, and feedback from distributors or users. Where internal resources are limited, medical device regulatory consulting can help review the plan and identify documentation gaps.
Process, Methodological, and Protocol Mandates
Your data collection process needs to show how your device compares with similar products and remains State of the Art (SOTA). Set up a process to filter unverified social media comments so your data remains reliable. You need clear metrics and action limits based on sales numbers, batch quantities, and actual clinical exposure. Your plan also needs complaint investigation tools, communication rules for authorities, and a formal Post-Market Clinical Follow-up (PMCF) plan, or a clear written reason why your product does not need one.
QMS Interfacing and Systemic Updates
Field data should not simply be stored in a file. It needs to update relevant parts of the Medical device Quality Management System. If a risk classification changes, you must update the Risk Management File and adjust your benefit risk calculations. If people misuse the product or experience unexpected side effects, you may need to change the design or update the user manual. Under European rules for medical devices and in vitro diagnostic devices, real-world feedback must be used to update official safety and performance reports. Focused medical device regulatory consulting can also help teams connect these findings with CAPA, design controls, and management review. This real world data keeps public safety summaries accurate, helps address manufacturing flaws, and warns you if other products may share the same risks.
Post Market Surveillance report Workflows by Device Class
Your reporting duties depend on your device's risk class. If you make lower-risk products, such as MDR Class I or IVDR Class A and B devices, you will prepare a Post Market Surveillance report (PMSR). This report summarizes your conclusions and any CAPAs taken. Keep the records in your technical files so they are ready for inspection. For higher-risk products, you also need a regular, standalone periodic safety update report. This document tracks changes in the benefit risk profile against historical data, includes clear cover-page metadata, and provides an executive conclusion on device safety. Medical device regulatory consulting can support the review and preparation of these class-specific deliverables.
Periodic Safety Update Report Frequencies, Timelines, And Submission Channels
How often you update and where you send your PSUR depends on your classification:
MDR Class III and Implantables: Update every year and submit through the EUDAMED electronic interface for notified body review.
MDR Class IIb (Non-Implantable) and Legacy Class III or IIb: Update every year, keep in your technical files, and share upon request.
MDR Class Executive IIa (Implantable): Update every two years and upload via EUDAMED.
MDR Class IIa (Non-Implantable) and Legacy Class IIa: Update at least every two years and keep in your technical documentation.
Data collection windows must be continuous and start on the certification date. Even if production stops, reporting duties do not end. You must maintain a reactive PSUR for complaints and serious incidents throughout the remaining device lifetime or legal retention period, which may extend to 10 years for non-implantable devices and 15 years for implantable devices.
PSUR Multi-Device Grouping Guidelines
You can merge multiple device families into one PSUR only when you provide a clear technical justification. The Leading Device Rule requires the model with the highest risk classification to anchor the schedule. This leading device determines the timelines and data collection windows for lower-tier products in the group, overriding their individual certification dates. The same leading device logic must be explained in the periodic safety update report. You can add or remove individual devices during revisions, but changing the leading device starts a new PSUR series. All grouped devices must also be managed by the same Notified Body.
Quantitative, Vigilance, and Incident Metrics in Reporting
Compare data from year to year so you can distinguish short term changes from long-term trends. Keep sales volume and configuration data mathematically consistent throughout. For serious incidents, separate technical device faults, clinical root causes, and health effects. Map these to Level 2 IMDRF Adverse Event Terminology codes across Annexes A, C, D, and F. Split metrics between Union and global figures, showing absolute numbers alongside incident rates. All deaths must be disclosed individually. The Post Market Surveillance report must also include an FSCA registry, CAPA logs, statements on data limitations, and verification against risk thresholds
Vigilance and Statutory Timeframes for Serious Incidents
Manufacturers are legally required to report serious incidents and FSCAs through the centralized electronic system. Expected side effects do not need individual reporting when they are clearly quantified in the technical file and tracked through trend reports. FSCAs performed in overseas markets must still be reported when the device is available in the Union, unless the root cause is limited to that foreign territory. Reporting deadlines are strict:
Serious Public Health Threats: Report immediately, and no later than 2 days after awareness.
Death or Unanticipated Serious Health Deterioration: Report immediately once a causal link is suspected or established, and no later than 10 days after awareness.
Standard Serious Incidents: Report immediately once a causal link is reasonably possible, and no later than 15 days after awareness.
You can submit an initial incomplete report to meet these deadlines, and you must report within the required window even when some details remain uncertain.
Periodic Summary Reporting and Investigation Protocols
Instead of filing individual incident reports, you may use Periodic Summary Reporting (PSR) for similar, well-documented incidents when the root cause is known and an FSCA is already in place. The format and frequency must be agreed with the coordinating competent authority. When authorities forward complaints from healthcare professionals or users, you must file a standard report within the 2, 10, or 15 day window if you agree with the issue, or provide a formal explanation if you do not. The authority may still overrule the explanation and require a report. Once an incident is filed, you must begin the investigation and risk assessment without delay. You must not alter a device sample in a way that compromises root cause evaluation before informing the competent authorities.
Trend Reporting and Custom-Made Devices (CMDs)
You must maintain a trend reporting process to identify a statistically significant increase in the frequency or severity of non-serious incidents or expected side effects that could affect the benefit risk profile. This is measured against baseline levels established in the technical file. For Custom-Made Devices (CMDs), the structured PMS plan and reports are exempt from the standard technical documentation structure, but they must remain within the CMD-specific documentation under Annex XIII of the MDR. CMD manufacturers must still prepare a Post Market Surveillance report for Class I devices or a PSUR for Class IIa, IIb, and III devices. They must maintain a PMCF plan, group data by shared designs or materials, and establish active communication channels with healthcare providers.
Requirements for Other Clinical Investigations
Clinical investigations conducted in the Union that do not fall under standard regulatory purposes must still follow core safety, ethical, and procedural rules. Individual Member States may add local requirements to protect human subjects within their borders. Implementing acts may also introduce uniform application metrics, harmonized electronic forms, and timelines for reporting serious adverse events across the market.
Medical Device Regulatory Consulting For Pms Compliance
To build an effective PMS strategy, manufacturers must first understand the applicable requirements. Regulatory authorities worldwide set rules for how medical devices are monitored after market entry. Morulaa provides Medical devices Post Market Surveillance (PMS) Services that support surveillance planning, data review, vigilance workflows, and corrective actions. Our medical device regulatory consulting also connects PMS outputs with the Medical device Quality Management System, including CAPA, risk management, and management review. We can help prepare a Post Market Surveillance report, review higher risk reporting, and address documentation gaps before submission or notified body review. Clear long-term surveillance and reporting practices support compliance and help protect confidence among healthcare professionals and patients.
Frequently Asked Questions
Are there different compliance pipelines for overseas manufacturers and European manufacturers?
No. Medical devices Post Market Surveillance (PMS) Services apply the same post-market compliance, vigilance, and surveillance principles to European and overseas manufacturers placing or maintaining devices on the Union market. The required evidence must be maintained within the technical documentation and relevant quality processes.
What are the statutory timelines for reporting serious incidents?
The reporting window depends on the severity of the incident. Serious public health threats must be reported no later than 2 days after awareness. Incidents involving death or unanticipated serious deterioration of health must be reported no later than 10 days after awareness or when a causal link is suspected. Other serious incidents must be reported no later than 15 days after a confirmed or reasonably possible causal relationship is identified.
Is a Post-Market Clinical Follow-up (PMCF) plan mandatory for all devices, including customized units?
For standard devices, you must include a formal PMCF plan or provide a clear, documented justification explaining why it is not applicable. For Custom-Made Devices, post-market review remains linked to expected clinical performance, and a dedicated PMCF plan is required.
How frequently must a periodic safety update report be updated and submitted for higher-risk devices?
The periodic safety update report frequency and submission route depend on the device classification and design. MDR Class III and implantable devices must be updated at least annually and submitted through EUDAMED. MDR Class IIb non-implantable and legacy Class III or IIb devices must be updated at least annually, maintained in the technical file, and shared upon request. Class IIa implantable devices require an update every two years through EUDAMED, while Class IIa non-implantable and legacy Class IIa devices are updated at least every two years and kept in the technical documentation.
Can an overseas manufacturer alter an affected device sample during a serious incident investigation?
No. You must not alter the device or a sample from the affected batch in a way that could compromise the evaluation of root causes before informing the competent authorities.