Skip to main content

​
Summary

A Field Safety Notice Form is an urgent communication template used to notify users, patients, and healthcare professionals about safety issues with your medical device that require immediate action. You use this form when you identify risks that could cause serious harm and need to implement Field Safety Corrective Actions (FSCA) to protect users.

​
Why is the Field Safety Notice Form important?

Field Safety Notice Forms serve as your primary tool for rapid and standardized risk communication when post-market surveillance reveals safety concerns. They enable you to quickly inform users about hazards, provide protective instructions, and coordinate corrective actions before serious incidents occur using a consistent format. FSN forms demonstrate regulatory compliance, protect patient safety, and maintain stakeholder trust during crisis situations. Without timely and effective FSN forms, safety issues can escalate into widespread harm, regulatory sanctions, and permanent market withdrawal.

​
Regulatory Context

Under 21 CFR Part 806 (Medical Device Correction and Removal):
  • Manufacturers must notify FDA within 10 working days of initiating a correction or removal
  • Device recalls must be reported immediately if they could cause serious health consequences
  • FSNs must reach all affected users and include specific corrective actions
  • Follow-up reports required to document effectiveness of corrective actions
Special attention required for:
  • Class I recalls requiring immediate FDA notification
  • Software updates that address safety-critical vulnerabilities
  • Devices used in life-supporting or life-sustaining applications
  • Coordination with FDA’s MedWatch safety alert system

​
Guide

​
When to Use the Field Safety Notice Form

Use the FSN form template immediately when you identify device-related risks that could cause death, serious injury, or serious public health threats. This includes software malfunctions, hardware failures, labeling errors, or use-errors that compromise safety. Don’t delay for complete investigations - use the preliminary FSN form based on initial risk assessments and follow up with additional information as your investigation progresses. The goal is rapid risk mitigation, not perfect information.

​
FSN Form Content Requirements

Risk description must clearly explain the hazard, its likelihood, and potential consequences for users and patients using the structured form fields. Use plain language that non-technical users can understand while providing sufficient detail for healthcare professionals to make informed decisions. Corrective actions should be specific, actionable, and time-bound using the form template. Specify exactly what users must do, by when, and how to confirm completion. Include contact information for questions and support during implementation. Device identification must enable users to determine if their devices are affected using the form’s device information section. Include UDI-DI numbers, software versions, serial number ranges, and manufacturing dates as applicable.

​
Distribution and Follow-up

Reach all affected users through multiple channels including direct mail, email, website postings, and professional networks using the completed form. Maintain distribution lists and track delivery confirmation to ensure comprehensive coverage. Monitor implementation by tracking user responses, measuring corrective action completion rates, and assessing residual risk levels. Document effectiveness and prepare follow-up communications as needed. Coordinate with authorities by submitting completed FSN forms to competent authorities simultaneously with user distribution. Provide regular updates on implementation progress and effectiveness measurements.

​
Integration with Quality Management

Connect your FSN form process to your incident management system for rapid response to emerging safety signals. Link to your CAPA system to address root causes and prevent recurrence. Update your risk management file to reflect new hazards and control measures identified through FSN activities.

​
Example

Scenario: Your cardiac monitoring app experiences a critical software bug that causes false arrhythmia alarms in 2% of users, leading to unnecessary emergency room visits. Post-market surveillance data shows this affects version 3.2.1 released three weeks ago. You must immediately issue an FSN to prevent further incidents while developing a software fix.

​
Example Field Safety Notice Form

FSN Number: FSN-2024-001
Date: March 20, 2024 URGENT FIELD SAFETY NOTICE CardioWatch Pro Mobile App For the Attention of: All CardioWatch Pro users, cardiologists, and healthcare facilities using our cardiac monitoring system Contact Details of Local Representative: CardioWatch Support Team
Email: safety@cardiowatch.com
Phone: +49-30-12345678
Address: Medizintechnik Straße 15, 10115 Berlin, Germany

​
Device Information

​
Risk Information

​
Action Information

Follow-up FSN: A follow-up notice will be issued within 30 days to report on update completion rates and any additional corrective actions if needed.

​
Q&A

Distribute FSNs immediately upon identifying safety risks - within 24-48 hours of risk confirmation. Don’t wait for complete investigations. Issue preliminary notices and follow up with additional information as it becomes available.
FSNs must be provided in the local language of each market where your device is distributed. For EU markets, this typically means translating into the official language(s) of each member state where you have users.
Maintain comprehensive user databases with multiple contact methods. Use direct mail, email, website postings, professional networks, and distributor channels. Track delivery confirmation and follow up with non-responders through alternative channels.
Issue follow-up FSNs when you have significant new information about the risk, when initial corrective actions prove insufficient, or when you need to report on implementation effectiveness. Regular follow-ups may be required until the safety issue is fully resolved.
Implement escalating communication strategies including repeat notices through different channels, direct phone contact for high-risk situations, and coordination with healthcare providers. Document all attempts and consider additional regulatory reporting for non-responsive users in critical situations.