Field Safety Corrective Actions and Notices in Ethiopia: EFDA_GDL_037 Requirements

1. Key takeaways

A field safety corrective action (FSCA) is an action taken by the manufacturer to reduce the risk of death or serious deterioration in health status associated with a device already on the market. It includes recalls, returns, on-site modifications, software upgrades, device destruction, affixing warning labels, and notifying physicians, among other measures. The document through which the action is communicated to users is the field safety notice (FSN). Ethiopia has issued a dedicated guideline on FSCA (EFDA_GDL_037) and makes two points explicit: the action must be notified to EFDA before implementation, and corrective actions taken outside Ethiopia that implicate products already on the domestic market equally give rise to a notification obligation. Both elements differ from how many global recall procedures are currently written, because they impose a country-specific sequencing step and a country-specific distribution trigger that do not exist in markets where notification after launch is tolerated. Companies that adopt the Ethiopian requirements into the global procedure template, rather than bolting them on locally, avoid the recurring risk of a country case that starts out of sequence.

2. Legal basis

3. Expert insights

Insight 1: the FSCA and the FSN are two documents and cannot substitute for each other.

The FSCA describes what is done (the recall, modification, software upgrade or other action itself), while the FSN describes how it is communicated (the written notice addressed to users, healthcare institutions or the authority). Companies frequently describe the measures correctly in the FSN yet never form a separate internal FSCA decision and execution record. When the authority later asks why the measure was chosen, the decision-chain evidence is missing, and the company cannot demonstrate that the scope and timing of the action were the result of a documented risk assessment.

Insight 2: notification before implementation changes the scheduling logic of global recalls.

In a multi-market simultaneous recall, most companies proceed along the line of headquarters decision, then global simultaneous release. Ethiopia requires that EFDA be notified before implementation, which means this country cannot simply be folded into the global synchronised batch: a separate notification window must be reserved for it (practical estimate: the specific lead time follows the current text of EFDA_GDL_037). Recalls planned without this window risk starting in Ethiopia non-compliantly even when the global rollout is perfectly coordinated.

Insight 3: corrective actions taken abroad flow back as domestic obligations through the implication clause.

When an FSCA occurs outside Ethiopia and the same product is already on the Ethiopian market, the local notification obligation is triggered. The impact is most visible for manufacturers from the Chinese mainland: a recall executed in the Chinese mainland or the European Union directly creates reporting responsibilities in Ethiopia, yet this market is often absent from the distribution list of the global recall. Building Ethiopia into that list costs almost nothing at drafting time and prevents the most common cross-border omission.

Insight 4: recall responsibility is already anchored at the agency agreement level.

Item 9.2.3(d) of EFDA-GDL-046 requires the agency agreement to stipulate that, where fraud or unacceptable unexpected adverse events occur under normal conditions of use, both parties are jointly responsible for recalling the product from the market and providing evidence. The execution of an FSCA therefore cannot rest on the manufacturer alone: the local representative’s cooperation duty is a contractual clause, not a matter of goodwill, and it should be exercisable within defined timeframes.

Insight 5: the FSCA runs in parallel with the three vigilance tiers and is not exempted by the FSN.

The event that triggers an FSCA must still be reported under the 2 / 10 / 30 calendar day three-tier vigilance deadlines; issuing an FSN does not constitute a substitute for the vigilance report. Two parallel tracks therefore run simultaneously, one addressed to users through the FSN and one addressed to the authority through the vigilance report, and both must be evidenced with dates and recipients.

4. Practical recommendations

1. Create an FSCA decision record template: capture the triggering event, the risk assessment conclusion, the rationale for the chosen measure, the coverage scope and the effective time.
2. Prepare a separate FSN template: the notice to healthcare institutions and users must contain device identification, batch or serial range, risk description, the actions users must take immediately, and the contact details of the manufacturer and the local representative.
3. Add Ethiopia to the global recall distribution list: whenever an FSCA is initiated abroad, the Ethiopian notification assessment is triggered in the same cycle.
4. Reserve a pre-implementation notification window: complete the notification to EFDA before the measure takes effect, without hard-binding it to the global release date.
5. Write the recall cooperation mechanism into the agency agreement: covering market screening, product retrieval, user notification and the burden of proof.
6. File the vigilance report in parallel: when the FSCA is issued, submit the vigilance report within the corresponding tier deadline.

5. Verification checklist

• □ FSCA decision record and FSN notice templates established
• □ FSN contains device identification, batch range, risk description and user actions
• □ EFDA notified before implementation of the measure
• □ FSCA originating abroad assessed for implication of products on sale in Ethiopia
• □ Shared recall responsibility and cooperation mechanism written into the agency agreement
• □ Vigilance report submitted in parallel under the three-tier deadlines
• □ FSCA execution and closure records retained

Regulatory information verified as of 29 October 2026. The FSCA and FSN requirements listed in this article follow the current text of EFDA_GDL_037 and Section 3.4.1 of EFDA-GDL-090; when the guidelines are revised, the specific lead time for pre-implementation notification must be re-verified.

• Local resource in Ethiopia: GRZAN assists manufacturers from the Chinese mainland and overseas in engaging the Ethiopian Food and Drug Authority (EFDA) on marketing authorisation (MA), Certificate of Competency (CoC) and import licence applications, including local representative structuring and agreement review, SRA reliance rationales, UMDN coding and classification, technical documentation, and the setup of vigilance and post-market surveillance systems.
• Service capabilities: product attribute determination and risk classification (non-IVD Class I–IV / IVD Class A–D), marketing authorisation applications and re-registration, applicability assessment for the low-risk notification procedure, Essential Principles compliance arguments, labelling and instructions-for-use localisation (English), and vigilance reporting with field safety corrective action support.
• Contact: hito.lin@grzan.cn; website www.grzan.cn.