Field Safety Notice (FSN) is a written communication that a medical device manufacturer sends to users, customers, and distributors to explain a Field Safety Corrective Action (FSCA) for a device already on the market. It identifies the affected device, describes the risk, and states the actions recipients must take.
What is a Field Safety Notice (FSN)?
An FSN is the communication that carries the message of a Field Safety Corrective Action to the people who hold or use the device. Under EU Regulation 2017/745 (MDR), Article 2(69) defines it as a communication that the manufacturer sends to users or customers regarding an FSCA. In vitro diagnostics are defined in Article 2(72) of the IVDR.
An FSCA, as defined in Article 2(68) of the MDR, is the corrective action itself: a step taken for technical or medical reasons to prevent or reduce the risk of a serious incident involving a device already on the market. The FSN is the practical letter or bulletin that tells a hospital, clinician, or distributor what is wrong, what could happen, and what to do next.
Why a Field Safety Notice (FSN) Matters in Medical Device Development
A poorly handled FSN puts patients at risk and exposes the manufacturer to enforcement. Competent authorities review the notice, can demand changes, and often publish it. Under the MDR, FSCAs and their notices feed the EU vigilance system in Articles 87 to 92, and they are increasingly recorded in EUDAMED, where regulators, healthcare professionals, and the public can see them. Regulation (EU) 2025/1021 moves vigilance reporting to that platform in stages, thereby increasing the visibility of every field action a company takes.
The cost is not only reputational. A delayed or unclear notice can turn a contained correction into a wider recall, draw audit findings against the post-market surveillance system in ISO 13485, and trigger scrutiny from a Notified Body. For design and quality teams, the FSN is also a feedback signal. It points back to a design, manufacturing, or labeling gap that the risk file under ISO 14971 should have identified.
What a Field Safety Notice (FSN) Must Contain
Article 89(8) of the MDR sets out what an FSN must carry. At minimum, it includes:
- Clear identification of the affected device or devices, including the relevant UDI-DI (Unique Device Identification, Device Identifier).
- Identification of the manufacturer running the FSCA, including the Single Registration Number (SRN) where available.
- The reason for the FSCA, describing the malfunction and the associated risk to patients, users, or others, is stated plainly and without downplaying the hazard.
- The specific actions the recipient must take, with any deadline and any request to confirm receipt.
The European Commission publishes a standard FSN template. It is not mandatory, since the regulation does not require a fixed format, but authorities strongly encourage it for consistency. Guidance on vigilance vocabulary now sits in MDCG 2023-3, the Q&A on vigilance terms and concepts that replaced the older MEDDEV 2.12-1 guidance. The notice must be issued in the official language or languages of each Member State where the action is taken, so a single FSCA across several countries often needs several translations. In most cases, the manufacturer first submits a draft FSN to the coordinating competent authority, which may request edits before it goes out.
Common Challenges and Best Practices
Three problems show up repeatedly. Translation is the first. Teams underestimate how long qualified medical translation takes, and the FSN stalls while the corrective action waits. Build the language plan into the FSCA timeline, not after it.
Tone is the second. Writers soften the risk to protect the brand, but a notice that minimizes the hazard fails its purpose and invites the authority to reject it. State the risk plainly. Say exactly what to do.
The third is reach. An FSN only works if it lands with everyone holding the device, so distribution records and customer confirmation matter as much as the wording. Track who received the notice and who acted on it. Keep that evidence with the vigilance file. A clean FSN reads as a single instruction set: what happened, who is affected, and the steps to take, with a point of contact for questions.
The US picture is worth separating out. The FDA does not use the FSN term. In the United States, the equivalent customer letter accompanies a recall under 21 CFR Part 7. The correction or removal is reported to the FDA under 21 CFR Part 806, usually within 10 working days. The intent matches; the terminology and filing path differ.
How SJML Helps with Field Safety Notice (FSN)
SJML supports manufacturers throughout the vigilance and post-market activities surrounding a Field Safety Notice. The QARA team works on complaint intake and handling, root cause analysis with CAPA, and field safety corrective action planning. It also supports post-market surveillance planning, vigilance reporting to the competent authority, and EUDAMED workflows. The same team advises on regulatory strategy, technical documentation, and alignment with ISO 13485 and ISO 14971, so an FSN connects back to a controlled risk file and a defensible quality system. This can run as a managed service that scales with the situation.
Frequently Asked Questions
A manufacturer issues an FSN whenever it takes a Field Safety Corrective Action on a device already on the market, such as a recall, software update, retrofit, or use advice. The notice is sent to affected users, customers, and distributors without undue delay. In most cases, the manufacturer first shares a draft with the coordinating competent authority.
The FSCA is the action; the FSN is the message about it. A Field Safety Corrective Action is the corrective step a manufacturer takes to prevent or reduce the risk of a serious incident, such as returning or modifying a device. The Field Safety Notice is the written communication that tells users what the action is and what they must do.
No. The European Commission provides a standard FSN template, but it is not mandatory because the MDR does not prescribe a fixed format. Authorities strongly encourage its use for consistency across Member States. The content requirements in Article 89(8) of the MDR are mandatory, even though the layout is not. The substance matters more than the form.
No. The FSN term comes from EU device regulation. In the United States, manufacturers send a recall notification letter to customers under 21 CFR Part 7 and report the correction or removal to the FDA under 21 CFR Part 806, generally within 10 working days. The goal is the same; the names and filing routes differ.
Related Terms
- Field Safety Corrective Action (FSCA)
- Post-Market Surveillance (PMS)
- Adverse Event
- Vigilance Reporting
- Corrective and Preventive Action (CAPA)
