EU MDR FSCA under Articles 87(1)(b) and 89: Report Before Implementation

1. Key takeaways

Under Article 87(1)(b) of the MDR, manufacturers must report field safety corrective actions (FSCA) concerning devices supplied on the Union market; under Article 87(8), an FSCA must be reported before it is implemented, except in urgent situations. Under Article 89, manufacturers must investigate serious incidents and FSCA, cooperate with the competent authorities, and submit a final report stating the conclusions of the investigation through the Article 92 electronic system; when an FSCA is taken, the manufacturer must issue a field safety notice (FSN) to device users in accordance with Article 89(8).

The practical message of these provisions is sequencing: report first, implement second, investigate in parallel, and close with a final report and user notice. Companies that invert the sequence, or that merge the FSCA track with the serious incident track, create avoidable non-compliance findings.

For multinational portfolios the FSCA provisions interact directly with global quality decisions. A recall decision taken anywhere in the world can become an EU reportable FSCA on the same day, which means the EU evaluation must be a standing item on the global decision agenda, not a follow-up task. Companies that integrate this step avoid the two classic failures: late reporting because the EU review started after implementation, and inconsistent decisions because regional teams applied different criteria to the same defect.

2. Legal basis

The FSCA reporting and investigation duties arise from Articles 87 and 89 of Regulation (EU) 2017/745, read with the guidance below.

3. Expert insights

Insight 1: Article 87(1) contains two independent obligations that are often wrongly merged into one.

Point (a) of Article 87(1) is the reporting of serious incidents, using the manufacturer incident report (MIR) form; point (b) is the reporting of field safety corrective actions, using a separate FSCA form. The two report types use different forms, and the rules for determining the competent authority differ as well: serious incidents are assessed by the competent authority of the Member State in which the event occurred, while an FSCA is assessed by the competent authority of the Member State in which the measure is taken, that is, the Member State where the affected devices were supplied. Running both through a single form or a single queue misfiles reports and delays assessments.

Insight 2: Reporting before implementation is the rule; urgency is the exception.

Article 87(8) requires FSCA to be reported before they are implemented, except in urgent situations where immediate action is necessary. This means that the habitual practice of issuing the field safety notice first and filing the report afterwards inverts the legal sequence. The correct order is report first, implement second; only genuinely urgent situations justify acting immediately, and the reasons must be documented. Building the report step into the FSCA decision workflow, rather than treating it as an administrative afterthought, is what keeps the sequence intact under time pressure. To make the sequence workable, the FSCA report should be drafted alongside the field safety notice rather than after it, since both documents share their factual core: the affected devices, the problem, the action and the advice to users.

Insight 3: The investigation duty under Article 89 runs on a separate timeline from the report.

Under Article 89, the manufacturer must investigate serious incidents and FSCA without undue delay, cooperate with the competent authorities, and submit a final report stating the conclusions of the investigation and, where appropriate, the corrective actions taken, through the Article 92 electronic system. The initial report under Article 87 and the final report under Article 89 are two distinct documents: the former is bound by the 15, 10 or 2-day deadlines, while the latter follows the progress of the investigation. Companies should keep two ledgers so that neither timeline is measured against the wrong clock. The final report should also close the loop with users: where the investigation changes the advice given in the field safety notice, an updated notice is usually the cleanest way to communicate it.

Insight 4: FSCA taken in third countries may also have to be reported.

The reporting duty covers actions taken in respect of devices supplied on the Union market. If an FSCA is implemented in a third country but concerns devices that are also lawfully supplied in the European Union, the measure falls within the reporting scope (a practical estimate, following the example logic of the MDCG guidance). This requires the global FSCA decision process of the company to be connected to the EU reporting process, so that a recall decided in another region triggers an evaluation of EU reporting duties at the same meeting, not weeks later.

4. Practical recommendations

The measures below focus on sequencing and templates, which are the two levers that make the report-before-implement rule operable under time pressure.

1. Establish an FSCA determination flow that distinguishes ordinary corrective actions from field safety corrective actions, and record the rationale for each determination.
2. Set the process order as report, then implement, with a separate urgent channel that keeps the justification on file.
3. Prepare the field safety notice (FSN) template in advance, covering user reachability and confirmation of product return (Article 89(8)).
4. Invite EU compliance staff to global FSCA decision meetings to evaluate whether EU reporting is triggered.
5. Maintain separate ledgers for initial reports and final reports, tracking deadlines and completion status for each.

5. Verification checklist

Use the checklist below to confirm that both reporting tracks and the investigation duty are covered by documented processes.

• □ Serious incident reporting under Article 87(1)(a) is distinguished from FSCA reporting under Article 87(1)(b)
• □ FSCA flow is set to report before implementation (Article 87(8)), with an urgent channel in place
• □ Field safety notice template has been prepared (Article 89(8))
• □ Investigation process for serious incidents and FSCA is established under Article 89
• □ Final report submitted through the Article 92 electronic system
• □ Global FSCA decisions include an EU reporting evaluation step

Regulatory information verified as of 29 October 2026.

GRZAN regulatory support. GRZAN assists medical device manufacturers with post-market compliance in the European Union market under Regulation (EU) 2017/745, covering field safety corrective action (FSCA) recalls and field safety notices, vigilance reporting, and responses to competent authority inspections. If you need support with your EU MDR post-market obligations, contact info@grzanglobal.com.