Medical Device Vigilance System Under EU MDR and IVDR
A medical device vigilance system is the process a manufacturer uses to record, assess and report serious incidents and Field Safety Corrective Actions (FSCA) to the competent authorities. Under EU MDR 2017/745 (Articles 87 to 92) and IVDR 2017/746 (Articles 82 to 87), serious incidents must be reported within 2, 10 or 15 days, depending on how serious they are.
What Is a Medical Device Vigilance System?
A medical device vigilance system collects information about incidents with devices already on the market, checks whether they are serious, and reports them to the authorities. The aim is to stop the same incident from happening again, through corrective actions and safety notices that reach every user of the device.
Vigilance is part of post-market surveillance (PMS). Article 10(13) of the MDR requires every manufacturer to have a system for recording and reporting incidents and FSCAs, as described in Articles 87 and 88. ISO 13485:2016 clause 8.2.3 adds the same duty inside the quality management system.
| Question | Short answer |
|---|---|
| Legal basis | EU MDR 2017/745, Chapter VII, Section 2 (Articles 87–92); EU IVDR 2017/746, Articles 82–87 |
| Who reports | The manufacturer. A non-EU manufacturer usually works through its EU Authorised Representative. |
| Who receives reports | The competent authority of the Member State where the incident happened |
| What is reported | Serious incidents, FSCAs, trend reports and periodic summary reports |
| Main guidance | MDCG 2023-3 Rev.2, Questions and Answers on vigilance terms and concepts |
| Applies to | All CE-marked devices, including legacy devices under the old directives (Article 120(3) MDR) |
Which Vigilance Terms Do You Need to Know?
Article 2 of the MDR defines the terms used in a medical device vigilance system. Using them correctly decides whether an event must be reported and how fast.
Incident
Any malfunction or deterioration in the performance of a device on the market, a use error caused by ergonomic features, inadequate information from the manufacturer, or an undesirable side-effect (Article 2(64)).
Serious incident
An incident that directly or indirectly led, might have led or might lead to death, a temporary or permanent serious deterioration in health, or a serious public health threat (Article 2(65)).
Serious public health threat
An event that could cause imminent risk of death, serious deterioration in health or serious illness, and may need prompt remedial action (Article 2(66)).
Field Safety Corrective Action (FSCA)
Action a manufacturer takes for technical or medical reasons to prevent or reduce the risk of a serious incident, such as a recall, modification or software update (Article 2(68)).
Field Safety Notice (FSN)
The communication the manufacturer sends to users or customers about an FSCA (Article 2(69)).
Manufacturer Incident Report (MIR)
The European Commission form used to report a serious incident to the competent authority. Version 7.3.1 is mandatory from 1 May 2026.
What Are the Serious Incident Reporting Timelines?
Deadlines are the core of any medical device vigilance system. The clock starts on the day the manufacturer becomes aware of the event. You report immediately once you have established a causal link with the device, or that a link is reasonably possible, and no later than the deadlines below.
| Event | Deadline | Legal reference |
|---|---|---|
| Serious public health threat | 2 days after awareness | MDR Art. 87(4) · IVDR Art. 82(4) |
| Death or unanticipated serious deterioration in health | 10 days after awareness | MDR Art. 87(5) · IVDR Art. 82(5) |
| Any other serious incident | 15 days after awareness | MDR Art. 87(3) · IVDR Art. 82(3) |
| Field Safety Corrective Action | Before the FSCA starts, unless it is urgent | MDR Art. 87(8) · IVDR Art. 82(8) |
| Trend report | When a statistically significant increase is found | MDR Art. 88 · IVDR Art. 83 |
Not sure if it is reportable? Report anyway within the deadline (Article 87(7)). You can send an initial report first and complete it later (Article 87(6)).
How Does Vigilance Reporting Work in 7 Steps?
A working medical device vigilance system follows the same path for every event. Each step should be described in your vigilance procedure and recorded for the Notified Body.
- Receive and log the informationComplaints from users, distributors, healthcare professionals, literature or the competent authority are logged with the date of awareness.
- Assess reportabilityDecide whether it is an incident or a serious incident, and whether the device could have caused or contributed to it.
- Submit the MIRSend an initial Manufacturer Incident Report to the competent authority within 2, 10 or 15 days.
- InvestigateCarry out root cause analysis and risk assessment without delay (Article 89). Do not alter the device in a way that affects the analysis before informing the authority.
- Decide on FSCAIf the risk needs action, report the FSCA and prepare a Field Safety Notice for users.
- Send the final reportSubmit the final MIR with the findings, root cause and corrective actions. If you take no action, explain why.
- Feed back into PMSUpdate the risk management file, trend analysis, PMS report or PSUR, and the technical documentation.
What Must Be Reported, and What Is Not Reportable?
In a medical device vigilance system, Article 87(1) MDR sets two main reporting duties: serious incidents and FSCAs for devices made available on the EU market.
- Serious incidents involving devices on the EU market
- FSCAs on EU devices, including FSCAs taken outside the EU if the reason also affects EU devices
- Use errors that caused, or could cause, death or serious harm
- A statistically significant increase in non-serious incidents or expected side-effects (trend report)
- Expected side-effects clearly documented in the product information, quantified in the technical documentation and covered by trend reporting
- Incidents that are not serious; record them and include them in trend analysis
- Similar serious incidents covered by an agreed periodic summary report
Remember: non-serious incidents are not reported one by one, but you must record them and include them in your trend analysis and your PMS report or PSUR.
How Do You Manage an FSCA and a Field Safety Notice?
FSCA management is where a medical device vigilance system is tested most. An FSCA can be a device return, modification, exchange, destruction, software update, or new advice on how to use the device. The Field Safety Notice tells users what has happened and what they must do.
- Report the FSCA to the competent authorities of every Member State affected, before you start, unless the action is urgent.
- Send the draft FSN to the evaluating competent authority for comments, except in urgent cases (Article 89(8)).
- Write the FSN in the official languages required by each Member State, using the Commission FSN template.
- Make sure the FSN identifies the device, including its UDI, explains the risk and states the actions users must take.
- Track that customers received and acted on the FSN, then close the FSCA with a final report.
Correct UDI data makes it easier to find the affected devices. See our guide to Unique Device Identification.
What Are Trend Reports and Periodic Summary Reports?
Trend report (Article 88)
You must report a statistically significant increase in the frequency or severity of non-serious incidents or expected side-effects that could change the benefit-risk balance. Your PMS plan must explain how you detect trends, the statistical method and the observation period.
Periodic summary report (Article 87(9))
For similar serious incidents with the same device, where the root cause is known or an FSCA is in place, you can send one periodic summary report instead of individual reports. The format, content and frequency must first be agreed with the competent authority.
Which Forms Are Used, and Is EUDAMED Required for Vigilance?
Every medical device vigilance system in the EU uses the same reporting forms. The European Commission publishes the official vigilance reporting forms.
| Form | Used for | Status |
|---|---|---|
| MIR 7.3.1 | Initial, follow-up and final serious incident reports, with IMDRF adverse event codes | Mandatory in the EU from 1 May 2026 |
| Manufacturer’s FSCA report | Reporting an FSCA to competent authorities | Current Commission form |
| Field Safety Notice template | Informing users about an FSCA | Current Commission template |
| Manufacturer’s Trend Report | Article 88 trend reports | Current Commission form |
| Periodic Summary Report | Agreed periodic summary reporting | Current Commission form |
EUDAMED registration for actors, UDI/devices, Notified Bodies and certificates, and market surveillance has been mandatory since 28 May 2026 (Commission Decision (EU) 2025/2371). The vigilance and post-market surveillance module is not yet live. In October 2026, the Commission announced that its mandatory use will not start before 2028. Until then, send vigilance reports to the national competent authorities.
Who Does What in a Medical Device Vigilance System?
| Party | Vigilance role |
|---|---|
| Manufacturer | Owns the vigilance system, reports serious incidents and FSCAs, investigates and issues FSNs |
| EU Authorised Representative | Forwards complaints and suspected incident reports to the manufacturer and cooperates with competent authorities |
| Importers and distributors | Pass complaints and suspected incidents to the manufacturer, and support FSCAs in their supply chain |
| PRRC | Makes sure vigilance reporting obligations are met (Article 15). See PRRC requirements. |
| Healthcare professionals and patients | Encouraged to report suspected incidents to the national authority (Article 87(10)) |
| Competent authority | Evaluates the risk, monitors the investigation and FSCA, and coordinates with other Member States |
| Notified Body | Reviews the vigilance procedure during audits and is informed of relevant vigilance data |
How Do You Set Up a Medical Device Vigilance System in Your QMS?
Notified Bodies expect a medical device vigilance system to be described in a written procedure linked to complaint handling, risk management and PMS. A good procedure covers:
- Complaint intake and a clear “date of awareness” rule
- A reportability decision tree based on MDCG 2023-3
- Responsibilities, including the PRRC and the EU Authorised Representative
- Competent authority contacts and the MIR, FSCA and FSN forms
- Root cause investigation and links to ISO 14971 risk management and CAPA
- Trend reporting method and thresholds, as set in the PMS plan
- Records, training and regular checks that the system works
Ready-made vigilance procedure templates and ISO 13485 procedures can shorten setup. Also check any MDCG device-specific vigilance guidance that applies to your product.
How Does EU Vigilance Compare With US FDA and UK Reporting?
If you sell in several markets, your medical device vigilance system needs one complaint process with separate reporting rules for each regulator.
| Topic | EU (MDR / IVDR) | US FDA | UK (Great Britain) |
|---|---|---|---|
| Legal basis | MDR Art. 87–92, IVDR Art. 82–87 | 21 CFR Part 803 (Medical Device Reporting) | UK MDR 2002, with the post-market surveillance rules in force since 16 June 2025 |
| Main deadlines | 2, 10 or 15 days | 30 calendar days; 5 work days when remedial action is needed or FDA asks | 2, 10 or 15 days |
| Report sent to | National competent authority | FDA (eMDR) | MHRA |
| Recalls / FSCA | FSCA report and FSN | Corrections and removals (21 CFR Part 806) | FSCA report and FSN to MHRA |
| Local contact for foreign makers | EU Authorised Representative | US Agent (registration contact) | UK Responsible Person |
Northern Ireland continues to follow the EU MDR and IVDR.
Build a Vigilance System That Works From Day One
I3CGLOBAL is a regulatory consultancy with offices in India, Europe and the USA, and has supported more than 300 CE certifications. We help manufacturers set up and run their medical device vigilance system.
- Vigilance, complaint handling and FSCA procedures
- MIR, FSCA report and Field Safety Notice preparation
- EU Authorised Representative and UK Responsible Person services
Request vigilance support
Tell us about your device and markets. We will review your current process and explain what is needed.
Medical Device Vigilance System: Frequently Asked Questions
What is a medical device vigilance system?
It is the manufacturer’s process for recording, assessing and reporting serious incidents and Field Safety Corrective Actions to competent authorities. EU MDR Articles 87 to 92 and IVDR Articles 82 to 87 set the requirements.
How many days do I have to report a serious incident under the MDR?
Report within 2 days for a serious public health threat, within 10 days for a death or unanticipated serious deterioration in health, and within 15 days for any other serious incident. The days count from when you become aware of the event.
What is the difference between an incident and a serious incident?
An incident is any malfunction, deterioration, use error, information problem or undesirable side-effect. It becomes a serious incident when it led, might have led or might lead to death, serious deterioration in health or a serious public health threat. Only serious incidents are reported one by one.
Which MIR form version must I use?
The Manufacturer Incident Report form version 7.3.1 is mandatory in the EU from 1 May 2026. Download the current version from the European Commission’s reporting forms page.
Do I report vigilance cases through EUDAMED?
Not yet. The EUDAMED vigilance module is not live, and the Commission has said its mandatory use will not start before 2028. Send reports to the national competent authority where the incident happened.
Does vigilance apply to legacy devices certified under the directives?
Yes. Article 120(3) of the MDR applies the MDR vigilance requirements to legacy devices, replacing the reporting rules of the old directives and MEDDEV 2.12-1.
Who reports for a manufacturer outside the EU?
The manufacturer is still responsible for reporting. The EU Authorised Representative forwards complaints and suspected incident reports to the manufacturer and cooperates with the competent authorities.
Which guidance explains vigilance terms?
MDCG 2023-3 Rev.2 gives questions and answers on vigilance terms and concepts for both the MDR and the IVDR. Device-specific vigilance guidance from the MDCG also exists for some device types.
Medical Device Vigilance System Guides and Related Services
Updated | Author: Sobha Augustine, Founder, I3CGLOBAL | Reviewed by: Asha Johnson, Manager, I3CGLOBAL
