When a field safety corrective action (FSCA) is required
Regulatory basis - MDR Art. 2(68) and Art. 89 / IVDR Art. 2(70) and Art. 84. An FSCA is any corrective action taken by a manufacturer to reduce a risk of death or serious deterioration in health associated with a device already placed on the market. FSCAs must be notified to NCAs.
Disclaimer - This site provides general information only and does not constitute legal or regulatory advice. Always consult the official regulation text and a qualified regulatory professional.
Definition of an FSCA
A field safety corrective action (FSCA) is any corrective action taken by a manufacturer for technical or medical reasons to:
- Prevent or reduce the risk of death or serious deterioration in the state of health associated with the use of a medical device or IVD that is already placed on the market
FSCAs include actions taken outside the manufacturer's premises — i.e., actions affecting devices already in distribution, in stock at distributors, or in use at healthcare institutions.
What triggers an FSCA?
An FSCA is required when a manufacturer becomes aware of a risk of death or serious deterioration in health associated with a marketed device and determines that corrective action in the field is necessary to reduce that risk. Triggers include:
| Trigger | Example |
|---|---|
| Serious incident investigation reveals systemic defect | Root cause analysis identifies a manufacturing defect in all units of a particular batch |
| PMS data reveals safety signal | Elevated complaint rate for a specific failure mode suggests a class-wide issue |
| Post-market clinical/performance data reveals new risk | Long-term clinical follow-up data reveals a previously unknown complication |
| NCA or third-party report | NCA or a foreign regulator identifies a safety issue and notifies the manufacturer |
| Vigilance data from equivalent devices | Competitor device recall reveals a class-effect risk applicable to the manufacturer's device |
| Internal quality audit finding | Design or manufacturing non-conformance identified that affects marketed devices |
Types of FSCA
| FSCA type | Description |
|---|---|
| Device recall | Device removed from the market or from service with customers/patients |
| Device modification | Modification of the device in the field (firmware update, component replacement) |
| Labelling update | New or amended warnings, contraindications, or IFU distributed to users |
| Advice to users | Healthcare professionals or patients advised to change how they use the device without product return |
| Device inspection | Users advised to inspect the device for specific defects before use |
| Device destruction | Affected devices must be destroyed rather than returned |
The FSCA decision process
When a potential safety issue is identified, the manufacturer must:
- Assess the risk: using the ISO 14971 risk management framework — what is the probability and severity of harm?
- Determine whether the risk is acceptable: compare against the benefit-risk assessment in the technical documentation
- If risk is unacceptable: determine what FSCA is needed and its scope (which lots, which markets, which users)
- Notify NCAs: before implementation where possible (see Reporting timeframes)
- Implement the FSCA: execute the recall/modification/communication
- Issue a Field Safety Notice (FSN): communicate the FSCA to all affected customers and users
- Track effectiveness: confirm the FSCA has reached all intended recipients and the risk has been adequately reduced
Scope of an FSCA — determining affected devices
Defining the scope correctly is critical:
- Too narrow: unaffected users remain at risk → ineffective FSCA; regulatory non-compliance
- Too broad: unnecessary disruption to clinical care; economic loss; loss of user confidence
Scope definition requires:
- Identification of the root cause — is this a batch-specific issue or a class-wide design problem?
- Traceability data — UDI distribution records to identify which lots/serial numbers went to which customers
- Risk stratification — are all affected devices equally at risk, or only those meeting certain use conditions?
FSCAs vs. voluntary recalls vs. mandatory recalls
| Action | Who initiates | Legal basis |
|---|---|---|
| Voluntary FSCA/recall | Manufacturer | MDR Art. 89 — manufacturer's own risk assessment |
| Mandatory recall (NCA-ordered) | NCA | MDR Art. 95 — competent authority market surveillance power |
| Commission safeguard action | European Commission | MDR Art. 97 — where national actions are insufficient |
The vast majority of recalls in the EU are manufacturer-initiated FSCAs — NCAs rarely need to order recalls if manufacturers respond promptly to safety signals.
FSCA effectiveness verification
After an FSCA is implemented, the manufacturer must verify its effectiveness:
- Confirm that all affected devices have been accounted for (returned, modified, or users contacted)
- Confirm the corrective action has been implemented at all affected sites
- Track the proportion of affected lots/units where the FSCA has been completed
- Report outcomes to NCAs
Related pages
- Field safety notices
- Recall classifications & coordination
- Competent authority-initiated actions
- What must be reported
- Reporting timeframes
Official references
| Reference | Description |
|---|---|
| MDR Art. 2(68) | FSCA definition |
| MDR Art. 89 | FSCA reporting obligation |
| IVDR Art. 84 | IVDR FSCA requirements |
| MDR Art. 95 | NCA power to order recalls |
| MDCG 2022-14 | FSCA guidance |
| EN ISO 14971:2019 | Risk management — used to assess FSCA need |
Complete the final section:
Scope of an FSCA — determining affected devices Defining the scope correctly is critical:
Too narrow: unaffected users remain at risk → ineffective FSCA; regulatory non-compliance Too broad: unnecessary disruption to clinical care; economic loss; loss of user confidence
Scope definition requires:
- Identification of the root cause — is this a batch-specific issue or a class-wide design problem?
- Traceability data — UDI distribution records to identify which lots/serial numbers went to which customers
- Risk stratification — which devices pose genuine risk and which are unaffected?
- Market and patient population — does the risk apply to all geographies or only specific regions or patient populations?
Once scope is defined, it must be clearly communicated in the FSN and justified in the NCA notification. Narrower scopes require stronger evidence that unaffected devices do not carry the risk.