FSCA and Recall Reporting to HSA in Singapore

1. Key takeaways

A Field Safety Corrective Action (FSCA) must be notified to HSA before it is implemented. According to industry compilations — with the specific timelines subject to official HSA guidance — an FSCA should be notified to HSA at least 24 hours before implementation, and an initial report detailing the FSCA should be submitted within 24 hours; a recall notice stating the device hazard and the corrective action taken must be distributed to consumers; and the final recall report must be submitted to HSA within 21 days. These three movements sit on top of, and cannot replace, the adverse event reporting tiers.

• FSCA is a pre-implementation notification; adverse event reporting is a post-event obligation.
• HSA classifies voluntary recalls and is notified of them according to severity.
• One field problem can trigger three independent obligations: AE report, FSCA notification and recall reports, and a registration change notification under GN-21.
• An unclosed FSCA blocks the expedited registration routes under GN-15.

2. Legal basis

The FSCA framework operates under the Health Products Act 2007, Part VIII, alongside the adverse event reporting regime and the change notification route. The elements are summarised below; the 24-hour and 21-day figures come from industry compilations of HSA requirements and are marked as such, with HSA official guidance and the conditions on approval documents prevailing in any conflict.

Note: specific timelines such as 24 hours and 21 days come from industry compilations of HSA requirements; the HSA official guidance and the conditions stated on approval documents prevail.

3. Expert insights

Five points distinguish companies that manage recalls cleanly from those that stumble.

Insight 1: prior notification is the biggest difference between FSCA and AE reporting. An AE report is filed after an event has occurred; an FSCA is notified before the action is launched. Companies handling a field problem frequently complete the AE report and forget the FSCA notification — they are two different tracks, with different triggers, and completing one does not discharge the other.

Insight 2: one event can trigger three independent movements. A single field problem may simultaneously require an adverse event report (under the 48-hour / 10-day / 30-day tiers), the FSCA notification and recall reports (prior notification plus the 21-day final report), and a registration change notification if the product itself changes, routed through GN-21. The three differ in purpose, timeline and channel and cannot substitute for one another. When we build systems for clients we require all of them to be managed in the same controlled case record, while each procedure is separately fulfilled.

Insight 3: an unclosed FSCA blocks the expedited registration routes. Under GN-15, one condition of the Immediate route and other fast tracks is having no unclosed FSCA. This means a recall that lingers open affects the future registration strategy for that product, and may even affect filings for other products of the same manufacturer (Annex 4, Part 2 requires disclosure of FSCA history). Closing an FSCA promptly is not only a compliance requirement but a commercial one.

Insight 4: the recall notice is for consumers, not for HSA. Both must be done: notify and report to HSA, and distribute a recall notice to consumers stating the hazard and the corrective action taken. The notice reaches the people who actually hold or use the device and gives them the information needed to stop using it safely; the HSA filings reach the regulator. Cases where only one side is completed are not rare in practice, and each half-finished track carries its own exposure.

Insight 5: all records must enter the QMS. Both HSA expectations and industry practice require that reports, correspondence with HSA, investigations and effectiveness checks are captured in the quality management system records. This is the foundation for later audits and for tracing any recurrence of the same event. Where records live in email threads or personal drives instead, reconstructing what happened and when becomes slow and unreliable exactly when it matters most.

4. Practical recommendations

We recommend embedding the following controls so that FSCA handling becomes routine rather than improvisation.

1. Make FSCA notification a mandatory gate before launch: no recall action starts without the notification being completed.
2. Manage the three tracks of one event in parallel: AE plus FSCA plus change notification, under one case record with separate accounts.
3. Close the FSCA promptly to avoid affecting future registration route eligibility.
4. Prepare the consumer recall notice and the HSA reports separately: different content, different audiences.
5. Bring all records into the QMS, including correspondence and effectiveness checks.

Regulatory information verified as of: 26 October 2026

Source level: Tier 2 (official HSA vigilance and recall information; GN-21 R7), Tier 3 (industry compilation of specific timelines such as 24 hours and 21 days, marked as subject to official HSA texts)

5. Verification checklist

• □ The FSCA notification was completed before implementation
• □ The initial report was submitted within the required timeline
• □ The recall notice was distributed to consumers and states the hazard and corrective action
• □ The final report was submitted within 21 days
• □ The AE report for the same case was filed under the three-tier timelines
• □ If the product itself changed, the GN-21 change notification has been assessed
• □ All records have been entered into the QMS

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including Singapore. Our team prepares dossiers to ASEAN CSDT structure, manages submissions and deficiency responses with HSA, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com