Post-Market Surveillance & Vigilance

30 minCore

Learning Objectives

By the end of this module you will be able to:

  • 1Explain the post-market surveillance (PMS) framework under MDR/IVDR and its purpose
  • 2Describe vigilance reporting obligations, timelines, and the HPRA notification process
  • 3Identify the components of a PMS plan, PSUR, and periodic safety update report
  • 4Understand the healthcare professionalโ€™s role in supporting manufacturer PMS and PMCF activities
Content reviewed: March 2026

Post-Market Surveillance & Vigilance

Post-market surveillance (PMS) and vigilance are critical regulatory obligations under both MDR (EU) 2017/745 and IVDR (EU) 2017/746. They ensure medical devices remain safe and perform as intended throughout their entire lifecycle โ€” not just at market entry.

Art. 83โ€“92

MDR PMS & Vigilance articles

2/10/15

Day reporting timelines

Lifecycle

Continuous monitoring obligation

๐Ÿฅ What This Means for Your Hospital

  • You are often the first to observe a device incident โ€” your reports trigger the entire vigilance chain
  • Ireland's HPRA relies on healthcare professionals to flag safety concerns early
  • Acting on Field Safety Notices protects patients โ€” check for affected devices in your inventory
  • Recording UDI numbers enables effective traceability during recalls

1. PMS vs Vigilance โ€” What's the Difference?

Post-market surveillance is a proactive and systematic process through which manufacturers collect, record, and analyse relevant data on the quality, performance, and safety of a medical device throughout its entire lifetime (MDR Article 83, IVDR Article 78).

๐Ÿ”

PMS (Post-Market Surveillance)

Proactive

The manufacturer actively gathers data about their device from user feedback, literature, registries, and complaints. Governed by MDR Articles 83โ€“85 & Annex III.

๐Ÿšจ

Vigilance

Reactive

Triggered when a serious incident occurs or a field safety corrective action is needed. Governed by MDR Articles 87โ€“92 & IVDR Articles 82โ€“87.

๐Ÿ’ก Key Change from Old Directives: Under the previous MDD (93/42/EEC) and IVDD (98/79/EC), PMS was less structured. The MDR/IVDR now require a documented PMS plan for every device, with specific outputs (PMS reports or PSURs) depending on device class. This represents a fundamental shift from a primarily reactive system to a proactive lifecycle approach.

Knowledge Check

What is the key difference between PMS and Vigilance under the MDR?

2. Serious Incidents & Reporting Timelines

Vigilance centres on serious incidents. Under MDR Article 87, manufacturers must report these to the competent authority of the Member State where the incident occurred.

โš ๏ธ What is a Serious Incident? (MDR Article 2(65))

Any incident that directly or indirectly led to, might have led to, or might lead to:

๐Ÿ’€

Death

of a patient, user, or other person

๐Ÿฅ

Serious Deterioration

in health of a patient, user, or other person

๐ŸŒ

Public Health Threat

serious threat to public health

Reporting Timelines (MDR Article 87(2)โ€“(5))

2

DAYS

Serious public health threat

Imminent risk requiring urgent field safety corrective action

Example: Batch contamination of IV sets across multiple hospitals

10

DAYS

Death or unanticipated serious deterioration

Incidents resulting in death or unexpected serious health deterioration

Example: Patient death potentially linked to pacemaker software malfunction

15

DAYS

All other serious incidents

Standard timeline for serious incidents not falling under 2 or 10 day categories

Example: Surgical instrument fracture during a procedure โ€” patient recovered

Note: These timelines apply to the manufacturer. Healthcare facilities should report internally as quickly as possible so the manufacturer can meet these deadlines.

Knowledge Check

A manufacturer learns that a batch of surgical staplers has caused three patient injuries requiring reoperation. No deaths occurred. What is the reporting deadline?

3. How to Report โ€” HPRA Incident Reporting Flow

In Ireland, medical device incidents should be reported to the HPRA (Health Products Regulatory Authority). Here is the step-by-step process for healthcare professionals:

๐Ÿ”” When Should You Report?

๐Ÿ”ดDevice malfunction during a procedure (even if patient wasn't harmed)
๐Ÿ”ดUnexpected device behaviour that could have caused injury
๐Ÿ”ดPatient injury or death potentially related to a device
๐ŸŸกLabelling errors that could lead to incorrect use
๐ŸŸกRepeated device failures or quality issues
๐ŸŸกUse-error patterns you observe across your team

4. PMS Plans & Reports

Every manufacturer must establish, document, implement, and maintain a PMS plan for each device. This plan is part of the technical documentation described in MDR Annex II & III.

Data collection

A proactive and systematic process to collect data from users, patients, distributors, importers, literature, databases, and registries (Annex III, Section 1.1)

Complaint handling

Procedures for recording/reporting non-conformities, including methods to distinguish device-related issues from other causes

Trend analysis

Effective methods and statistical processes for trend detection and threshold definitions

Indicators & thresholds

Suitable indicators and threshold values to trigger re-assessment of the benefit-risk ratio

Investigation protocols

Methods to investigate complaints and protocols for communicating with competent authorities

Corrective action linkage

Procedures for taking corrective actions, field safety corrective actions, or communicating findings

PMCF/PMPF integration

How post-market clinical/performance follow-up findings feed back into the PMS system

PMS Outputs: Report vs PSUR

๐Ÿ“„
PMS Report (Art. 85)
Class I devices
  • Summary of PMS data and findings
  • Conclusions and any actions taken
  • Updated when necessary
  • Part of technical documentation
  • Available to competent authority on request
๐Ÿ“Š
PSUR โ€” Periodic Safety Update Report (Art. 86)
Class IIa, IIb, III
  • Comprehensive benefit-risk analysis
  • Volume of sales and usage estimates
  • Updated at least annually (IIa) or as needed
  • Must be uploaded to EUDAMED
  • Notified Body reviews for Class III
๐Ÿ“Œ IVDR Equivalent: IVDR Article 80 requires a PMS report for Class A and B IVDs. IVDR Article 81 requires a PSUR for Class C and D IVDs. For Class D and companion diagnostics, the PSUR must be submitted to the Notified Body at least annually.

Knowledge Check

A manufacturer of a Class IIb surgical mesh must produce which PMS output?

5. Field Safety Corrective Actions (FSCAs)

An FSCA is any corrective action taken by a manufacturer for technical or medical reasons to prevent or reduce a risk of a serious incident (MDR Article 2(68)). Every FSCA must be accompanied by a Field Safety Notice (FSN) sent to customers and users.

๐Ÿ”ด
Recall

Return of the device to the manufacturer or disposal

๐Ÿ”ง
Modification

Device modification, exchange, or retrofit in the field

๐Ÿ“ข
Advisory

Additional information on device use, warnings, or contraindications

๐Ÿ’ป
Software Update

Software update to address safety concerns

1
Read the FSN carefully โ€” identify the affected device model(s), serial numbers, and lot/batch numbers
2
Check your inventory โ€” determine if your facility has any affected devices in stock or active clinical use
3
Follow the manufacturer's instructions โ€” this may include quarantining devices, applying software updates, or returning products
4
Inform affected clinical departments โ€” ensure all relevant staff are aware and understand any interim measures
5
Document and confirm โ€” complete the response form (if provided) and return it to the manufacturer
6
Consider patient impact โ€” for implantable devices, review whether any patients may need to be contacted or monitored

๐Ÿ“‹ Case Study: Infusion Pump Recall in an Irish Hospital

A large teaching hospital in Dublin received an FSN from a manufacturer regarding a software defect in their infusion pumps that could, in rare circumstances, cause an over-infusion of medication. Here's how they responded:

โš ๏ธ The Problem

  • โ€ข Software bug in firmware v2.3.1
  • โ€ข Could cause 10% over-delivery in specific modes
  • โ€ข Affected 340 pumps across the hospital group

โœ… The Response

  • โ€ข Clinical Engineering identified all affected units within 24 hours
  • โ€ข Interim guidance issued to nursing staff on safe mode settings
  • โ€ข Firmware update rolled out over 2 weeks
  • โ€ข No patient harm occurred โ€” early action prevented incidents
๐Ÿฅ Key Lesson: A robust inventory management system with UDI tracking enabled rapid identification of affected devices. Hospitals without such systems took significantly longer to respond.

6. Trend Reporting (MDR Article 88)

Beyond individual incident reports, the regulations require monitoring for trends. If there is a statistically significant increase in the frequency or severity of incidents, this must be reported to competent authorities.

๐Ÿ“ˆ

Increasing complaint rates

Rising complaints for a specific device model over time

๐Ÿ“‰

Higher failure rates

Failure rates exceeding expectations during specific procedures

๐Ÿ”—

Event clustering

Similar adverse events across different healthcare facilities

โšก

Emerging use-errors

New use-error patterns not identified pre-market

๐Ÿฆ 

Infection patterns

Rise in infections or complications post-implantation

๐Ÿงฉ

Component failures

Specific component failures appearing across a product line

๐Ÿฅ Hospital Role: Even if individual incidents seem minor, document them consistently. Your internal data can reveal trends invisible at the manufacturer level. Regular communication between clinical departments and your biomedical/risk management team is essential for detecting patterns early.

Knowledge Check

Under MDR Article 88, what triggers a trend report to the competent authority?

7. PMCF & PMPF Studies

Post-market clinical/performance follow-up is a continuous process to proactively collect and evaluate clinical data from CE-marked devices, updating the clinical evaluation throughout the device lifecycle.

๐Ÿ”ฌ
PMCF
MDR Annex XIV, Part B

Post-Market Clinical Follow-up for medical devices under MDR.

Methods: clinical investigations, registries, surveys, literature reviews

๐Ÿงช
PMPF
IVDR Annex XIII, Part B

Post-Market Performance Follow-up for IVDs under IVDR.

Particularly important for Class C/D IVDs and companion diagnostics

๐Ÿฅ What This Means for You: Manufacturers may contact your hospital to participate in PMCF or PMPF studies. This could involve contributing anonymised clinical data, participating in device registries, or facilitating surveys. Your cooperation supports the ongoing safety evaluation of devices you use daily.

8. SSCP โ€” Summary of Safety & Clinical Performance

For implantable devices and Class III devices, manufacturers must draw up an SSCP โ€” a public-facing document uploaded to EUDAMED.

Device identification (including UDI)
Intended purpose and indications
Description of the device
Suggested user profile and training
Clinical evaluation and PMCF results
Possible therapeutic alternatives
Suggested patient profile
Harmonised standards applied

SSCPs must be validated by the Notified Body (Art. 32(3)) and updated annually. The IVDR equivalent โ€” the SSP (Summary of Safety and Performance) โ€” is required for Class C and D IVDs.

9. EUDAMED & UDI System

EUDAMED is the European database established under MDR Article 33 that centralises information about medical devices across the EU, serving as the primary electronic system for PMS and vigilance.

๐Ÿ‘ฅ

Actor Registration

Registration of manufacturers, ARs, importers, NBs

Live
๐Ÿ“ฑ

UDI/Device Registration

Device UDI-DI data and Basic UDI-DI

Live
๐Ÿ›๏ธ

NB & Certificates

Notified Body designations and certificates

Live
๐Ÿ”ฌ

Clinical Investigations

Clinical investigations and performance studies

Live
๐Ÿšจ

Vigilance & PMS

Incident reports, FSCAs, FSNs, PSURs

Phased rollout
๐Ÿ‘๏ธ

Market Surveillance

CA market surveillance activities

Phased rollout
๐Ÿฅ Why This Matters for Your Hospital: While hospitals don't register directly in EUDAMED, you benefit from public access to safety information, UDI lookup for verifying device identification, and NB certificate checks. Recording UDIs for implantable devices is strongly recommended and may be required by national legislation (MDR Art. 27(9)).

Knowledge Check

What is the purpose of the UDI-PI (Production Identifier) component of the UDI?

10. National Competent Authorities

CountryCompetent Authority
๐Ÿ‡ฎ๐Ÿ‡ช IrelandHPRA โ€” Health Products Regulatory Authority
๐Ÿ‡ฉ๐Ÿ‡ช GermanyBfArM โ€” Federal Institute for Drugs and Medical Devices
๐Ÿ‡ซ๐Ÿ‡ท FranceANSM โ€” Agence nationale de sรฉcuritรฉ du mรฉdicament
๐Ÿ‡ณ๐Ÿ‡ฑ NetherlandsIGJ โ€” Health and Youth Care Inspectorate
๐Ÿ‡ฎ๐Ÿ‡น ItalyMinistry of Health โ€” DG Medical Devices
๐Ÿ‡ช๐Ÿ‡ธ SpainAEMPS โ€” Spanish Agency of Medicines
๐Ÿ‡ง๐Ÿ‡ช BelgiumFAMHP โ€” Federal Agency for Medicines and Health Products
๐Ÿ‡ธ๐Ÿ‡ช SwedenLรคkemedelsverket โ€” Medical Products Agency

11. Irish & HSE Context

๐Ÿ‡ฎ๐Ÿ‡ช HPRA & Vigilance

The HPRA uses a risk-based approach to market surveillance โ€” devices with higher inherent risk (Class III, Class D IVDs) receive more scrutiny. When you report an incident, the HPRA evaluates it and may trigger FSCAs at national or EU level.

The HPRA's vigilance system feeds directly into the manufacturer's post-market risk management process, potentially triggering corrective actions across all EU markets.

๐Ÿฅ HSE Medical Device Governance

The HSE Medical Device Governance Policy requires each healthcare facility to maintain:

  • Device inventories with UDI information where available
  • Documented procedures for receiving and acting on FSCAs
  • Incident reporting aligned with national vigilance requirements
  • Cooperation with manufacturers in PMS and PMCF activities

๐ŸŽฏ Key Takeaways

PMS is proactive & continuous โ€” Vigilance is reactive to incidents
Manufacturers must report serious incidents within 2, 10, or 15 days
Your incident reports trigger the entire vigilance chain โ€” every report matters
Record UDI numbers for traceability during FSCAs and recalls
Act promptly on Field Safety Notices โ€” check inventory for affected devices
Trend reporting catches patterns that individual reports may miss
PSURs are required for Class IIa/IIb/III devices and uploaded to EUDAMED
In Ireland, report device incidents to the HPRA directly

Irish Context โ€” Vigilance & the HPRA

In Ireland, all serious incidents must be reported to the HPRA. Manufacturers report directly; hospitals should also notify the HPRA if they become aware of a serious incident.

The HPRA publishes Field Safety Notices (FSNs) from manufacturers and coordinates with EU authorities via the EUDAMED vigilance module.

HSE hospitals should have a process to receive and action HPRA safety notices โ€” typically managed through the clinical engineering or risk management department.

Trend reporting: if you notice recurring near-misses or minor incidents with the same device, report this to the HPRA even if individual incidents do not meet the serious incident threshold.

Useful HPRA Links:

This is educational content only and is not an accredited or externally verified course. Always refer to official HPRA publications and your facility's own policies.

Knowledge Check

4 questions ยท 80% required to pass

Q1.What is the primary purpose of Post-Market Surveillance (PMS) under MDR?

Q2.What is a PSUR (Periodic Safety Update Report)?

Q3.What is a Field Safety Corrective Action (FSCA)?

Q4.Within what timeframe must a manufacturer report a serious incident to the competent authority?

0/4 answered

Print-Friendly Summary

One-page PDF for ward reference & quick revision

Was this module useful?