Skip to main content

When an FSCA is required

Regulatory basis

Field Safety Corrective Actions are addressed in Regulations 16–22 of the UK MDR 2002 and MHRA's adverse incident reporting guidance. The obligation to take an FSCA can arise from a serious incident investigation, a trend analysis, or from proactive identification of a safety issue before harm occurs.

What is an FSCA?​

A Field Safety Corrective Action (FSCA) is any action taken by a manufacturer to reduce the risk of death or serious deterioration in health associated with the use of a device that is already on the market. An FSCA may be:

  • A recall — removing devices from the market or from use
  • A device modification or retrofit — a software update, hardware change, or field repair
  • A labelling change — adding or modifying a warning, contraindication, or instruction
  • A restriction of use — limiting use to specific patient groups, device settings, or clinical contexts
  • A user communication — a letter, notice, or alert to healthcare professionals advising of a safety issue and required actions
  • Any combination of the above

An FSCA is always accompanied by a Field Safety Notice (FSN) — the communication sent to users, distributors, and healthcare facilities describing the issue and required action.

When must a manufacturer initiate an FSCA?​

A manufacturer must initiate an FSCA when they have determined (or have reasonable grounds to believe) that a device on the market:

  1. Is defective — has a design, manufacturing, labelling, or software fault
  2. Could present a risk of death or serious deterioration — for any user, patient, or third party
  3. Requires corrective action in the field to address that risk

The trigger for an FSCA can be:

TriggerExample
Serious incident investigation revealing a systemic device faultMultiple reports of catheter hub cracking — root cause: moulding defect affecting all units in a batch
Trend analysis identifying a safety signalStatistically elevated failure rate of a software alarm function across multiple sites
UKAB or MHRA notificationMHRA draws the manufacturer's attention to user complaints it has received
Proactive internal detectionInternal quality review identifies a manufacturing deviation that could affect device safety — before any adverse events reported
Information from an equivalent deviceA competitor's similar device recall identifies a hazard that may also affect your product
Post-market surveillance literature signalPublished study identifies a previously unrecognised risk with the device type

FSCA does not require confirmed patient harm​

A critical principle: a manufacturer does not need to wait for a patient to be harmed before initiating an FSCA. The trigger is a determination that the device could cause harm — the risk must be acted upon promptly.

Proactive FSCAs — initiated before harm occurs — are encouraged by MHRA and reflect well on a manufacturer's safety culture. Waiting for harm before acting is both ethically and legally problematic.

Decision process: should we initiate an FSCA?​

When a potential safety issue is identified, the manufacturer should:

  1. Gather facts — what is the failure mode? How many devices are affected? What is the probability and severity of harm?
  2. Assess risk — apply the ISO 14971 framework. Is the residual risk with the current device acceptable?
  3. Consider corrective options — what actions would reduce the risk to an acceptable level?
  4. Make a documented decision — record the rationale for initiating (or not initiating) an FSCA
  5. Notify MHRA — within 10 calendar days of deciding to initiate an FSCA
  6. Issue an FSN — communicate the issue and required actions to all affected parties

FSCA scope: what devices are affected?​

The FSCA must cover all devices that present the identified risk. Scope determination requires:

  • Affected device models — which specific models, configurations, or sizes are affected?
  • Affected batches or serial numbers — which specific units? All units, or only those within a production date range?
  • Geographic scope — which markets? (All GB-distributed affected devices must be included; if the same devices were also distributed to EU/NI, co-ordinate with the EU/NI regulatory process)
  • Affected customers — which distributors, hospitals, healthcare providers received the affected devices?

Distribution records must be sufficiently detailed to identify the affected population. Inadequate distribution records make FSCA implementation extremely difficult.

Notification to MHRA​

MHRA must be notified of an FSCA no later than 10 calendar days from the decision to initiate the FSCA. Notification is submitted via the MHRA Submissions portal and must include:

  • The FSCA reference number (assigned by the manufacturer)
  • Description of the safety issue
  • Devices affected (models, batch/lot numbers or serial number ranges)
  • Action being taken
  • Draft Field Safety Notice
  • Distribution list of affected customers
  • Timeline for completing the FSCA

MHRA reviews the notification and may request modifications to the FSCA scope or FSN content.

Official references​

ReferenceDescription
UK MDR 2002, Regulations 16–22FSCA and vigilance obligations
MHRA: Adverse incident reporting guidanceFSCA notification requirements
ISO 14971:2019Risk management — FSCA risk determination
IMDRF/NCAR/N18FINALInternational definitions for FSCAs