FSCA: The Closed Loop from Notification to Case Closure

1. Key takeaways

FSCA (Field Safety Corrective Action) is the core obligation under scope item 3 of MDS-REQ 11 V2.0, safety alerts and FSCA. It is not the same as sending customers a notification letter: a complete closed loop covers signal identification and assessment, the corrective action decision, notification to the SFDA, informing users through an FSN (Field Safety Notice), implementing the correction in the distribution channel, verifying the effectiveness of the correction, producing a closure report, and writing the results back into PMS and the PSUR. MDS-G030 V1.0 (2026-09-09) states in its post-market surveillance section that the IMDRF definitions and terminology on adverse events, FSCA and FSN are adopted, which means the Saudi FSCA concept shares the same origin as IMDRF member jurisdictions such as the EU and Australia; the same FSN skeleton can be reused across jurisdictions, but the notification recipients and language requirements still follow the local Saudi rules.

• FSCA is a closed loop from signal to closure, not a single letter.
• The SFDA actively monitors recalls and FSCAs published by recognised regulatory authorities, so passive notification surrenders the initiative.
• FSN language follows the layered rules of the implementing regulation: Arabic is mandatory for lay users.
• Closure rests on an evidence chain: receipts, recovery records, replacement proofs, patch deployment lists.
• The FSN distribution list is generated from the traceability ledger required by MDS-REQ 11.

2. Legal basis

The FSCA obligation sits inside the scope of MDS-REQ 11 and its reporting channels, while MDS-G030 anchors Saudi terminology to IMDRF definitions; the parent law and the implementing regulation supply the enabling provisions.

3. Expert insights

1. The SFDA actively watches regulatory actions abroad; passive notification means giving up the initiative. MDS-G030 states plainly in its post-market surveillance section that the SFDA continuously monitors recalls, FSCAs and other safety information published by recognised regulatory authorities (RRAs) for signal detection, risk prioritisation and follow-up regulatory decisions. For Chinese manufacturers holding approvals from the Australian TGA, Health Canada, the EU EEA, Japan PMDA, the UK MHRA or the US FDA, the practical meaning is that if the same device enters recall or FSCA in any RRA jurisdiction, the SFDA will very likely learn of it through signal monitoring. If the company has not notified in Saudi Arabia in parallel, the character of the event changes from a proactive company report to a regulator discovering it and demanding answers, and the downstream communication cost and loss of trust far exceed those of proactive notification. GRZAN binds the global recall ledger to the Saudi notification action: whichever jurisdiction triggers, a Saudi-side assessment starts within 24 hours.

2. The language and audience layering of the FSN decides whether the correction actually lands. FSN recipients cover three groups: healthcare facilities, distributors and end users, and the language requirements follow the layered rules of the implementing regulation: instructions for use and advertising aimed at lay users must be provided in Arabic, while text aimed at professional users may be in English or Arabic. In the FSCA context, the text sent to hospital equipment departments and clinical units can be primarily English, but wherever patients hold the device themselves (home blood glucose meters, home ventilators, contact lens care products), an Arabic version is essential. The FSN content must include device identification (model, UDI-DI, batch or serial number range), a description of the defect, the action users must take immediately, the manufacturer’s correction plan and contact details. A missing UDI-DI leaves a hospital unable to locate the affected batches in its inventory, and the correction never lands.

3. Closure rests on an evidence chain, not a declaration. The endpoint of an FSCA is not issuing the notice but proving the correction is complete. Verifiable evidence includes the distribution list and receipts of notices, recovery or rework records of affected devices, shipping proofs for replacements, version deployment lists for software patches, signed user confirmations, and quarantine and destruction records. The same data are inputs to the Final Report and the PSUR. Compared with EU FSCA practice, where competent authorities likewise require an effectiveness check, the Saudi difference is that effectiveness verification ties directly to the traceability system requirement of MDS-REQ 11: the supply and distribution information recorded in the company’s traceability ledger is exactly the data basis for determining the FSN distribution scope. An inaccurate ledger means an incomplete FSN; an incomplete FSN means closure lacks evidence.

The overall framework of post-market obligations is covered at https://www.grzan.cn/regulations/saudi/post-market-surveillance-ncmdr-and-saudi-vigilance-41 , and the effect of UDI data on distribution scope at https://www.grzan.cn/regulations/saudi/pms-and-udi-data-maintenance-47 .

4. Practical recommendations

• Maintain a global recall and FSCA ledger, and start a Saudi-side impact assessment within 24 hours whenever any RRA jurisdiction triggers.
• State the local execution responsibilities for FSCA in the AR agreement: receiving SFDA instructions, organising FSN distribution, collecting receipts and submitting closure materials.
• Fix seven fields in the FSN template: model, UDI-DI, batch or serial number range, defect description, user actions, correction plan and contact details.
• Prepare language versions layered by user type; text aimed at lay users must be provided in Arabic.
• Generate the FSN distribution list from the supply and distribution traceability ledger, collect receipts immediately after sending, and re-contact non-responders.
• Keep the original proofs of recovery, rework, replacement and patch deployment as supporting data for the Final Report and the PSUR.
• Complete the effectiveness check before submitting the closure report, and confirm the coverage rate of the correction in a written conclusion.
• Retain the acceptance receipts and timestamps of notifications submitted through NCMDR, Saudi Vigilance or call centre 19999.

5. Verification checklist

• □ The global recall ledger is bound to the Saudi notification action
• □ The AR agreement contains the FSCA local execution responsibility clause
• □ The FSN template contains the seven fixed fields
• □ The lay-user version has been prepared in Arabic
• □ The FSN distribution list is generated from the traceability ledger and is traceable
• □ The receipt collection and re-contact mechanism is running
• □ Recovery, rework, replacement and patch proofs have been archived
• □ The closure report contains the effectiveness check conclusion
• □ Notification acceptance receipts and timestamps have been retained

Regulatory information verified as of October 29, 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Saudi Arabian market. Our team manages adverse event reporting and recall coordination with the SFDA National Center, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com