Jordan FSCA Recall and Notification Obligations to the JFDA

1. Key takeaways

Whenever a manufacturer initiates a field safety corrective action (FSCA) in any market where the device is sold — including a product recall, a safety alert or a product modification — the authorised representative must notify the JFDA without delay. The GRZAN conclusion is that the trigger is “initiated in any market”, not “initiated in Jordan”; this is a notification obligation with an extraterritorial trigger, and it applies even when the affected device never reaches Jordanian soil. For global manufacturers this is not a detail of drafting but a structural point: a recall decision taken on another continent starts a Jordanian clock at the same moment it starts anywhere else.

The second takeaway: the notification must contain four elements — a description of the problem and the risk to patients or users, the scope of the affected device in Jordan (batch numbers, serial numbers and quantities), the corrective action plan to be implemented, and the communication plan directed at the affected healthcare institutions and users. Each element answers a different question the authority needs answered before it can act.

The third takeaway: the JFDA retains the power to impose additional measures. Depending on the nature and severity of the problem, the JFDA may require additional corrective measures for the Jordanian market, which may go beyond what the global plan already provides. Companies should read this as the authority keeping a local lever even after a full global plan has been notified.

2. Legal basis

Clause numbers are subject to the Arabic originals published in the Jordanian Official Gazette and by the JFDA. The three instruments above form the frame within which recalls and corrective actions are notified, inspected and enforced; the precise clause numbering should be confirmed in the Arabic text before being cited formally.

3. Expert insights

Insight one: the extraterritorial trigger is the defining feature of FSCA notification in Jordan. Manufacturers often assume that notification is only required when a problem occurs in Jordan. Under the Jordanian design, an FSCA initiated in any market places the AR under a notification duty. This design allows the JFDA to act locally in step with global safety signals as soon as they emerge, instead of learning about a problem only when affected product shows up at the border or in a hospital.

Insight two: the four notification elements map onto the JFDA’s decision-making needs. The problem description and risk serve to judge severity; the Jordanian scope (batch numbers, serial numbers, quantities) serves to establish the extent of impact; the corrective action plan serves to assess adequacy; and the communication plan serves to confirm that local users will actually receive the information. If any element is missing, the JFDA cannot reach a judgement and will typically request supplementation, which costs time precisely when time matters most.

Insight three: the AR is the statutory notifying party. FSCA notification is performed by the AR, and the manufacturer cannot notify the JFDA directly on its own behalf. This makes it essential that the manufacturer agree with the AR on notification deadlines and cooperation duties in their contract, because the whole notification depends on a partner the manufacturer does not control day to day.

Insight four: the JFDA may add local measures. Depending on the nature and severity of the problem, the JFDA may require additional corrective measures targeting the Jordanian market. When designing a global FSCA plan, companies should leave room for such Jordanian add-ons, so that a locally imposed extra step does not force the entire global plan to be reworked. The safer design is a plan with per-market modules that can be tightened without touching the rest.

Insight five: this channel runs in parallel with vigilance reporting. Adverse event reporting addresses individual cases, while FSCA notification addresses systemic corrective action. A single event may trigger both channels simultaneously, and companies should not substitute one for the other: a vigilance report does not discharge the notification duty, and a notification does not replace case-level reporting.

4. Practical recommendations

First, embed a “Jordan notification trigger” in the quality system. Whenever a global FSCA decision is made, the Jordan notification process should start at the same time, without waiting for someone to remember it separately.

Second, prepare templates for the four notification elements in advance. Batch and serial number lists, Jordanian stock and distribution quantities, the corrective action plan and the communication plan should be capable of rapid generation when an FSCA occurs, so that the notification is not delayed by drafting from scratch.

Third, agree on FSCA notification deadlines with the AR in the contract. Quantify them in hours or working days rather than relying on vague wording such as “without delay”, which cannot be audited or enforced afterwards.

Fourth, keep the global plan flexible enough for JFDA add-ons. The global plan should allow adjustment by market, so that it does not conflict with locally imposed additional requirements.

5. Verification checklist

• □ A Jordan notification trigger for global FSCAs is embedded in the quality system
• □ Templates for the four notification elements (risk, scope, correction, communication) are prepared in advance
• □ FSCA notification deadlines for the AR are quantified in the agreement
• □ It is confirmed that FSCA notification is performed by the AR and not directly by the manufacturer
• □ Flexibility is reserved for additional corrective measures imposed by the JFDA
• □ Vigilance reporting and FSCA notification are treated as two separate channels, not substitutes
• □ Cited clause numbers are verified against the Arabic originals of the Official Gazette

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 Jordanian market. Our team manages adverse event reporting and recall coordination with the JFDA, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com