EU IVDR Vigilance Reporting under Article 82: Deadlines, FSCA and Summary Reports

1. Key takeaways

Under Article 82(3), serious incidents must be reported to the competent authorities no later than 15 days after the manufacturer becomes aware of them. Under Article 82(4), serious incidents that constitute a serious public health threat must be reported immediately, and no later than 2 days. Under Article 82(5), where the death of a patient, user or other person, or an unanticipated serious deterioration in their state of health, is involved, the report must be made immediately after the manufacturer has established or suspected a causal relationship, and no later than 10 days. All reports must be submitted via the electronic system referred to in Article 87 (Article 82(1)). Around these deadlines sit complementary obligations: incomplete reports may be filed first and completed later under Article 82(6), doubt about reportability never suspends the deadline under Article 82(7), field safety corrective actions must be reported before implementation under Article 82(8), and periodic summary reporting is available for recurring incidents under Article 82(9).

2. Legal basis

3. Expert insights

Insight 1: The three deadlines have different start dates and cannot be interchanged.

The 15-day period of Article 82(3) runs from the moment the manufacturer becomes aware of the serious incident. The 2-day period of Article 82(4) runs from awareness of the serious public health threat. The 10-day period of Article 82(5) runs from the date the manufacturer becomes aware of the incident, but the reporting action itself must be taken immediately after a causal relationship is established or suspected. Article 82(2) adds that the time limits should generally take account of the severity of the serious incident. In operational terms, each deadline therefore needs its own internal clock, its own definition of the awareness trigger event, and its own accountable owner, because a process that treats all vigilance as one 15-day queue will mis-time both the 2-day and the 10-day lanes.

Insight 2: Expected erroneous results go to trend reporting, not to serious incident reporting.

The exclusion in Article 82(1)(a) covers incidents involving expected erroneous results that are explicitly documented and quantified in the product information and technical documentation and are subject to trend reporting under Article 83. This allocation decides which route the large volume of IVD-specific performance deviations must take: serious incident reporting under Article 82, or trend reporting under Article 83. Mis-classification produces either over-reporting, which floods authorities and distracts from genuine signals, or under-reporting, which is itself a compliance breach. The decision tree must therefore be anchored in the quantified expectations held in the technical documentation.

Insight 3: The reporting moment for an FSCA is before implementation.

Article 82(8) requires that, except in urgent cases where a field safety corrective action (FSCA) must be taken immediately, the manufacturer reports the FSCA without delay before it is implemented. Article 82(1)(b) further extends the scope to FSCA taken in a third country in relation to a device which is also legally supplied to the EU market, where the reason for the action is not specific to the third country. Together these rules mean that a global recall decision must enter the vigilance workflow at the moment the decision is made, not after execution, and that overseas recalls of EU-marketed IVDs also trigger the obligation.

Insight 4: Report even when uncertain, and use periodic summary reporting where allowed.

Article 82(7) provides that where the manufacturer is uncertain whether an incident is reportable, the report must nonetheless be submitted within the time limits set out in paragraphs 2 to 5. Article 82(9) allows the manufacturer, with the agreement of the coordinating competent authority (Article 84(9)) on the format, content and frequency, to submit periodic summary reports instead of individual reports for similar serious incidents, where the root cause has been identified or an FSCA has been implemented, or where the incidents are common and well documented. Both provisions reward manufacturers who keep the authority dialogue structured and documented.

4. Practical recommendations

1. Build an incident triage decision tree that first allocates each event to one of three lanes: serious incident, expected erroneous result, or trend, before any clock is started.
2. Set separate internal clocks and accountable owners for the 15-day, 2-day and 10-day lanes, and write the awareness trigger that starts each clock directly into the procedure.
3. Place the FSCA reporting node before implementation in the recall workflow, and prepare the periodic summary reporting mechanism of Article 82(9) in parallel.
4. Include a UDI field in the report template (Article 24(5)) and share the underlying data source with Article 83 trend reporting so the two channels stay consistent.
5. Have the PRRC take responsibility for the reporting obligations under Articles 82 to 86 under Article 15(3)(d), with sign-off records retained as evidence of compliance.

5. Verification checklist

• □ An incident triage decision tree is in place (serious incident / expected erroneous result / trend)
• □ Internal clocks are set for 15 days (Article 82(3)), 2 days (Article 82(4)) and 10 days (Article 82(5))
• □ The FSCA reporting node is placed before implementation (Article 82(8))
• □ The report template includes a UDI field (Article 24(5))
• □ The periodic summary reporting mechanism has been discussed with the coordinating competent authority (Article 82(9))
• □ The PRRC is formally responsible for the Articles 82–86 reporting obligations under Article 15(3)(d)

Legal information verified as of 29 October 2026.

GRZAN helps IVD manufacturers operating under the IVDR to run vigilance with confidence: triage decision trees for serious incidents and expected erroneous results, deadline management across the 15-day, 2-day and 10-day lanes, FSCA recall coordination and authority communication, and periodic summary reporting agreements. For support with IVDR vigilance and recalls, contact info@grzanglobal.com.