Under Regulation (EU) 2017/745, is not a complaint inbox. For each device, the manufacturer must run a documented PMS system that gathers, records, and analyses quality, performance, and safety data across the device lifetime.
This page helps structure PMS plans, PMS reports or PSURs, PMCF updates, vigilance decisions, trend reporting, EUDAMED submissions, and the records reviewers will ask to see.
EU MDR and vigilance should connect field data to technical documentation, clinical evaluation, risk management, corrective action, and authority reporting. Keep a traceable record of the signal received, its assessment, the MDR route applied, each report or update, and the evidence retained in the technical file.
1
Section 1
Build the PMS system around device-specific signals
Article 83 requires a system for each device that is proportionate to risk class and appropriate for the device type. The system belongs inside the manufacturer's quality management system, so support tickets, complaint handling, service records, distributor feedback, literature review, registry data, and clinical follow-up should feed the same controlled process.
MDR PMS data does more than populate a log. It is used to update benefit-risk determination, risk management, design and manufacturing information, instructions for use, labelling, clinical evaluation, the summary of safety and clinical performance where relevant, and needs for preventive, corrective, or .
MDCG 2025-10 describes PMS as a continuous cycle that begins when the first device is placed on the market or put into service and continues through the intended lifetime of the last device covered by the plan. One plan may cover a device group, but it must identify every device in scope and justify monitoring methods and frequencies against the risk profile.
Define PMS intake sources by device, version, intended purpose, risk class, market, and responsible owner.
Classify each signal as complaint, non-serious incident, serious incident candidate, expected side-effect, trend signal, PMCF input, CAPA input, or non-device issue.
Link each PMS conclusion to the records it may update: risk file, clinical evaluation report, PMCF plan or report, IFU, labelling, SSCP, technical documentation, PMS report, or .
When PMS identifies preventive or corrective action, document the measure, authority or notified-body communication if applicable, and post-action monitoring.
Articles 83 and 84 require a device-specific PMS system and PMS plan, and identify how PMS data updates risk management, clinical evaluation, labelling, technical documentation, and corrective action.
plan, establish, document, implement, maintain and update
Current non-binding MDCG guidance on PMS lifecycle, plan scope, grouping, proactive collection, method rationale, QMS interfaces, and management review.
PMS is a continuous process
2
Section 2
Keep the PMS plan, PMS report, and PSUR distinct
The PMS plan is the operating design for collecting and analysing post-market data. Article 84 points to Annex III and requires the plan to be part of technical documentation for devices other than custom-made devices.
The report type depends on class. Class I manufacturers prepare a PMS report summarising analysis results, conclusions, and the rationale and description for preventive and corrective actions. Class IIa, IIb, and III manufacturers prepare a for each device, or where relevant each category or group of devices, with conclusions from benefit-risk determination, main PMCF findings, sales volume, user population estimates, and usage frequency where practicable.
For class I, keep the PMS report current when necessary and available for competent-authority request.
For class IIa, update the when necessary and at least every two years.
For class IIb and class III, update the at least annually.
For class III and implantable devices, Article 86 requires submission through the Article 92 electronic system once the relevant EUDAMED workflow is operative. Until then, follow national provisions and the submission method agreed with the notified body; keep its evaluation with the record.
For other devices, keep the PSUR available to the notified body involved in conformity assessment and, upon request, to competent authorities.
Articles 84, 85, and 86 define the PMS plan, PMS report, PSUR content, update cadence, and submission or availability routes by device class.
Periodic safety update report
3
Section 3
Use PMCF to update clinical evaluation and risk management
PMCF is part of PMS, but it has a clinical evidence job. MDR Annex XIV treats PMCF as a continuous process that updates clinical evaluation and requires a documented PMCF plan. MDCG 2020-7 gives a practical structure for the plan: manufacturer and device details, PMCF activities, links to technical documentation, clinical evaluation and risk management references, equivalent or similar device data, standards or guidance, and the estimated date of the PMCF evaluation report.
A usable PMCF record explains why each activity is needed, what data quality is expected, which endpoints or questions are being answered, what limitations exist, when analysis and reporting will happen, and how findings flow back into the clinical evaluation report, technical documentation, and risk controls.
Include general methods such as clinical experience, user feedback, scientific literature, and other clinical data sources.
Use specific methods where justified, such as registries, PMCF studies, real-world evidence analyses, healthcare professional surveys, patient or user surveys, and case report review.
State the PMCF objective: confirming safety and performance, monitoring side-effects and contraindications, detecting emerging risks, confirming benefit-risk acceptability, or identifying systematic misuse or off-label use.
Document PMCF findings in a PMCF evaluation report and use the conclusions to update clinical evaluation and risk management; implement preventive or corrective measures when PMCF identifies the need.
Annex XIV Part B requires PMCF to update clinical evaluation, specifies minimum PMCF plan content, and requires PMCF findings to be documented and fed back into clinical evaluation and risk management.
PMCF shall be performed pursuant to a documented method
MDCG 2020-7 provides a non-binding PMCF plan template and examples of PMCF activities, objectives, rationale, limitations, timelines, and evaluation-report planning.
The PMCF plan shall be part of the post-market surveillance plan.
4
Section 4
Separate serious incident, FSCA, and trend decisions
Vigilance starts with triage. Article 87 requires manufacturers to report serious incidents involving devices made available on the Union market, except expected side-effects that are clearly documented, quantified in technical documentation, and subject to trend reporting. The same article covers field safety corrective actions, including third-country FSCAs for a device also legally made available on the Union market when the reason is not limited to the third-country device.
Trend reporting is a different route. Article 88 covers statistically significant increases in the frequency or severity of non-serious incidents or expected undesirable side-effects that could significantly affect benefit-risk analysis and may create unacceptable health or safety risks. The PMS plan should specify the methodology, observation period, and handling approach for those trend signals.
For each event, record awareness date, device identification, market, seriousness assessment, causality assessment, expected side-effect status, trend threshold check, and reporting route.
Report a serious incident immediately once the causal relationship is established or reasonably possible, and no later than 15 days after awareness. For death or unanticipated serious deterioration, report immediately once causality is established or suspected and no later than 10 days after awareness. Report a serious public health threat immediately and no later than 2 days after awareness.
For FSCAs, record the field safety notice, affected UDI or device identifiers, SRN if issued, user actions, competent-authority review where applicable, and evidence that users were informed without delay.
After a serious incident report, keep investigation records, risk assessment, final report, corrective action decision, and communications with competent authorities and the notified body where relevant.
Articles 87 to 89 define reportable serious incidents, FSCAs, expected side-effect exceptions, vigilance reporting clocks, trend reporting, investigations, final reports, and field safety notices.
any serious incident involving devices
5
Section 5
Use current reporting routes and prepare for EUDAMED
MDR Article 92 establishes the electronic system for vigilance and PMS information, including serious incident and FSCA reports, periodic summary reports, trend reports, PSURs, field safety notices, and competent-authority exchanges. The Actor, UDI/Device, Notified Bodies and Certificates, and Market Surveillance modules became mandatory on 28 May 2026, but the Commission still lists the Vigilance and module as in development. Manufacturers and authorised representatives must therefore continue using the applicable national processes for vigilance and PMS submissions.
MDCG 2024-11 says there is no voluntary-use period for the Vigilance and module. When it becomes mandatory, subsequent actions on still-open national reports move into EUDAMED, but the original report is not entered retrospectively. Commission Implementing Regulation (EU) 2021/2078 supplies malfunction rules once an operative EUDAMED submission is required.
Until the module becomes mandatory, keep national submission records, authority correspondence, notified-body delivery records where applicable, and the identifiers needed to continue open follow-up actions in EUDAMED later.
After the module becomes mandatory, keep EUDAMED receipts and submission identifiers with the related case. Maintain a fallback communication log if a malfunction affects a required submission: who was informed, what data was provided, which authority-prescribed channel was used, and when the EUDAMED entry was completed.
Do not rely on EUDAMED module status as a reason to skip internal MDR records; keep the PMS, PMCF, risk, clinical, and vigilance evidence controlled in the technical documentation and QMS.
Article 92 identifies the PMS and vigilance information handled by the electronic system, including serious incident reports, FSCAs, trend reports, PSURs, field safety notices, and competent-authority exchanges.
Electronic system on vigilance and on post-market surveillance
Confirms that four EUDAMED modules became mandatory on 28 May 2026 and that the Vigilance and Post-Market Surveillance module remains under development.
Current guidance for the unavailable VGL module, continued national processes, and the later handling of reports that remain open when the module becomes mandatory.
This does not imply retrospective registration
Recommended next step
Review MDR PMS and vigilance evidence
Check that the PMS plan, PMCF plan, PSUR or PMS report, vigilance triage, FSCA process, trend method, and EUDAMED records remain consistent for the same device and version.
A reviewer should be able to reconstruct the full chain from signal to decision. Keep records at device and version level, and preserve links between PMS analysis, clinical evaluation, risk management, PMCF, vigilance reports, field safety actions, CAPA, notified-body review, and EUDAMED submission evidence.
Record the MDR article route, device scope, data source, method, assessment, decision, report or update made, authority communication, and follow-up monitoring. Link each reporting deadline to the applicable legal trigger.
PMS plan, data-source map, statistical methods for trend detection, observation periods, and escalation criteria.
PMS report or with benefit-risk conclusions, PMCF findings, sales or use estimates where required, preventive and corrective actions, and update history.
Vigilance triage records, serious incident reports, FSCA decisions, field safety notices, final investigation reports, periodic summary reporting agreements if used, and competent-authority or notified-body correspondence.
National submission and notified-body delivery records while the VGL module is unavailable; after mandatory use begins, EUDAMED receipts, transition records for open cases, malfunction communications, and evidence that users received field safety notices when applicable.
Articles 83 to 92 and Annex XIV support the required record chain across PMS, PMCF, PSURs, vigilance, trend reporting, corrective actions, technical documentation, and EUDAMED submissions.
The technical documentation shall be updated accordingly.
Primary MDR source for PMS system and plan, PMS report, PSUR, serious incident and FSCA reporting, trend reporting, Article 92 electronic system, and Annex XIV PMCF requirements.
Articles 83 and 84 require a device-specific PMS system and PMS plan, and identify how PMS data updates risk management, clinical evaluation, labelling, technical documentation, and corrective action.
Articles 84, 85, and 86 define the PMS plan, PMS report, PSUR content, update cadence, and submission or availability routes by device class.
Show 4 more
Annex XIV Part B requires PMCF to update clinical evaluation, specifies minimum PMCF plan content, and requires PMCF findings to be documented and fed back into clinical evaluation and risk management.
Articles 87 to 89 define reportable serious incidents, FSCAs, expected side-effect exceptions, vigilance reporting clocks, trend reporting, investigations, final reports, and field safety notices.
Article 92 identifies the PMS and vigilance information handled by the electronic system, including serious incident reports, FSCAs, trend reports, PSURs, field safety notices, and competent-authority exchanges.
Articles 83 to 92 and Annex XIV support the required record chain across PMS, PMCF, PSURs, vigilance, trend reporting, corrective actions, technical documentation, and EUDAMED submissions.
"Post-market surveillance system of the manufacturer"
More quoted passages
"plan, establish, document, implement, maintain and update"
"Periodic safety update report"
"PMCF shall be performed pursuant to a documented method"
"any serious incident involving devices"
"Electronic system on vigilance and on post-market surveillance"
"The technical documentation shall be updated accordingly."
MDCG guidance source for PMCF plan structure, PMCF activity examples, objectives, rationale, timelines, and links to clinical evaluation, risk management, technical documentation, and PMCF evaluation reports.
MDCG 2020-7 provides a non-binding PMCF plan template and examples of PMCF activities, objectives, rationale, limitations, timelines, and evaluation-report planning.
Supports practical PMCF evidence fields, including activity source, description, objectives, methods, rationale, timelines, and PMCF evaluation-report planning.
"Post-market clinical follow-up (PMCF) Plan Template"
More quoted passages
"The PMCF plan shall be part of the post-market surveillance plan."
Binding EUDAMED operating source for access, user support, data exchange, and malfunction contingency records when technical unavailability affects submissions.
Sets rules for EUDAMED access, technical support, machine-to-machine services, and contingency handling when malfunctions hinder required submissions.
"laying down rules for the application"
More quoted passages
"technical and administrative assistance on Eudamed"
Current transition source for national vigilance processes and later continuation of open reports in EUDAMED.
Current guidance for the unavailable VGL module, continued national processes, and the later handling of reports that remain open when the module becomes mandatory.
"The VGL module is not available for voluntary use"
Current MDCG guidance for PMS system operation, continuous lifecycle coverage, PMS plan scope, proactive collection, and QMS feedback.
Current non-binding MDCG guidance on PMS lifecycle, plan scope, grouping, proactive collection, method rationale, QMS interfaces, and management review.
Confirms that four EUDAMED modules became mandatory on 28 May 2026 and that the Vigilance and Post-Market Surveillance module remains under development.