Field Safety Corrective Action (FSCA) is a corrective action a medical device manufacturer takes, for technical or medical reasons, to prevent or reduce the risk of a serious incident from a device already on the market. Defined in EU MDR Article 2(68), it covers recalls, software updates, labeling changes, and similar field-level interventions.
What is a Field Safety Corrective Action (FSCA)?
An FSCA is one of the two main outputs of the EU medical device vigilance system, sitting alongside serious incident reporting. The term is defined in Article 2(68) of the EU MDR 2017/745, with a parallel definition in Article 2(71) of the IVDR for in vitro diagnostics. It applies once a device has been made available on the market, so it belongs to the post-market phase of the device lifecycle rather than design or premarket review.
The action can take several forms: a recall, a device modification or retrofit, a software update, a labeling change, a device exchange, or advice to users on how to operate or inspect it. A recall is only one type of FSCA. Every recall is an FSCA, but many FSCAs never involve physically retrieving product. Whichever form it takes, the manufacturer communicates the action to users through a Field Safety Notice (FSN), defined in Article 2(69).
Why Field Safety Corrective Action (FSCA) matters in medical device development
A late or missing FSCA report is one of the most frequently cited findings in competent authority inspections and notified body audits. It signals a broken post-market surveillance system and carries direct patient-safety consequences.
The obligation is strict. Under Article 87(1)(b), the manufacturer, or its Authorized Representative for non-EU companies, must report every FSCA to the relevant competent authority. Reporting timelines run on calendar days from the awareness date, so weekends and holidays count against the clock. For manufacturers selling in both the EU and the US, an FSCA often maps to an FDA correction or removal under 21 CFR Part 806, and the two systems use different forms, thresholds, and deadlines that have to be managed in parallel.
A field action also pulls engineering, quality, regulatory, and customer-facing teams onto unplanned work, and a poorly scoped one can expand into a larger recall or compliance escalation.
How the Field Safety Corrective Action (FSCA) process works
An FSCA starts with a decision, not a product retrieval. The reportable event under Article 87(1)(b) is the manufacturer’s decision that a field action is needed. The process usually runs in these steps:
- Signal detection. Complaints, PMS data, clinical literature, or trend analysis surface a potential safety issue with a marketed device.
- Risk evaluation. The manufacturer runs a health hazard evaluation against its ISO 14971 risk management file to decide whether the risk is unacceptable and a field action is warranted.
- Decision and reporting. Once the decision is made, the manufacturer reports the FSCA to the competent authorities of every affected country, plus the authority where it or its Authorized Representative is based.
- Field Safety Notice. The FSN goes to users. Article 89(8) requires it to identify affected devices by UDI-DI, name the manufacturer with its Single Registration Number, explain the reason without downplaying the risk, and state the actions users must take.
- Execution and closure. The manufacturer carries out the action, tracks effectiveness, and submits a final report when the action concludes.
MDCG 2023-3 Rev.2, revised January 2025, is the working reference for edge cases. Vigilance reporting is moving into EUDAMED under Article 92 as the module comes online.
Common challenges and best practices
The most common mistake is treating the FSN as the trigger. Teams wait until the notice is drafted and logistics are arranged before starting the reporting clock, but the clock starts at the decision. Another frequent error is under-scoping the affected population, forcing a second, wider action later and damaging credibility with the competent authority.
Good practice ties the FSCA process directly to complaint handling and CAPA, so signals flow into risk evaluation without stalling. Strong teams pre-draft FSN templates, keep UDI and distribution records current so affected lots trace quickly, and settle reporting responsibilities across the manufacturer, Authorized Representative, importers, and distributors before an event happens. When unsure whether an action qualifies, they report; regulators expect a bias toward disclosure.
How SJML helps with Field Safety Corrective Action (FSCA)
SJML supports FSCA as part of its Compliance-as-a-Service post-market surveillance offering. Its QARA team helps manufacturers set up vigilance and complaints-handling systems, run root cause analysis and CAPA, and prepare the reports and Field Safety Notices a field action requires. That work connects to broader regulatory sustenance, including ISO 13485 and MDSAP quality systems, ISO 14971 risk files, and EUDAMED registration, so post-market obligations sit within one quality framework. SJML works with startups through large OEMs across Class I, II, and III devices.
Frequently asked questions
No. A recall is one type of FSCA, defined by physically retrieving devices from the field. An FSCA is the broader category and can also be a software update, a labeling change, a retrofit, a device exchange, or advice to users. Every recall is an FSCA, but many field safety corrective actions do not involve removing any product from the market.
The reporting obligation is triggered by the manufacturer’s decision to take a field action, not by its execution. Under Article 87(1)(b) of EU MDR 2017/745, the FSCA must be reported to the relevant competent authority, generally before or at the same time as users are notified. Timelines run on calendar days from the awareness date.
A Field Safety Notice is the communication a manufacturer sends to users or customers about an FSCA, defined in Article 2(69) of the EU MDR. Under Article 89(8), it must identify affected devices by UDI-DI, name the manufacturer and its Single Registration Number, explain the reason for the action without minimizing the risk, and state the actions users need to take.
They address the same situation but under different rules. FSCA is an EU MDR concept covering any field action to reduce serious-incident risk. In the US, the closest equivalents are recalls under 21 CFR Part 7 and reportable corrections and removals under 21 CFR Part 806. A manufacturer selling in both markets manages parallel reports with different forms and deadlines.
Related terms
- Vigilance Reporting
- Post-Market Surveillance (PMS)
- Corrective and Preventive Action (CAPA)
- Complaints Handling
- Medical Device Recall
