Vigilance Responsible Person and Report Types in Ethiopia Under EFDA-GDL-090

1. Key takeaways

Ethiopia’s vigilance system is built on two axes: people and report types. The first axis is the Vigilance Responsible Person, who must be designated in writing by the organisation and acts as the fixed liaison point between EFDA and the licence holder. The second axis divides reports into four types: initial reports, follow-up reports, final reports and trend reports, alongside a periodic summary safety report whose submission cycle is usually agreed with EFDA. A company must therefore satisfy two conditions at the same time: someone is accountable, and a matching report type is available for every stage of an event. Neither condition can compensate for the absence of the other. A named person without report templates delays submissions; complete templates without a designated person leave EFDA with no authoritative counterpart. Experience in this market shows that authorities test both conditions during inspections and during the review of vigilance documentation submitted with re-registration files, so the designation and the templates should be verifiable on demand rather than reconstructed under time pressure.

2. Legal basis

3. Expert insights

Insight 1: the written designation is the compliance starting point of this market’s vigilance system.

Section 3.1 requires the organisation to designate a Vigilance Responsible Person in writing. The substance of this requirement is to personalise the vigilance duty: EFDA does not need to determine who is authorised to represent the company at each event, but can simply check the designation document. Where the designation is missing or outdated, every subsequent report can be rendered ineffective at the working level, because the authority has no evidence of who stood behind the submission when it was filed.

Insight 2: the four report types form one complete timeline, not a menu from which to pick one.

The initial report opens the event; follow-up reports supplement the progress of the investigation; the final report closes the event and states the conclusion and the measures taken; the trend report steps outside the single event and addresses a statistically significant increase in the frequency or severity of similar events. The most common corporate gap is to produce initial and final reports only, leaving follow-up and trend reporting empty. That gap is visible to the authority, because a final report without any intermediate follow-up suggests the investigation was never actually tracked.

Insight 3: the trend report is a proactive obligation and is triggered even without an EFDA notification.

The distinctive feature of the trend report is that it asks not for the reporting of a single occurrence, but for proactive reporting once an abnormal increase has been observed. This requires a company to hold a statistical baseline: without a baseline there is no way to determine what counts as an increase. The day-to-day accumulation of post-market surveillance data is therefore the precondition for triggering trend reports on time, and companies that only start collecting data when an event occurs will never meet this duty.

Insight 4: the cycle of the periodic summary safety report is negotiable.

Under Section 3.4, the cycle of the periodic summary safety report is usually determined through agreement between the licence holder and EFDA (practical estimate: the specific cycle and template follow the current EFDA guideline and the arrangement reached with the authority). This means the company should confirm the cycle and the format with EFDA before the first submission, rather than setting its own cycle and later being asked to recompile the report in a different structure.

Insight 5: the duties of the Responsible Person and the local representative must be aligned at the agreement level.

Item 9.2.3(f) of EFDA-GDL-046 requires the manufacturer and the local representative to jointly assume vigilance and post-market reporting responsibilities. If the Vigilance Responsible Person is designated by the overseas manufacturer while events are received by the local representative, the boundary between the two roles must be written into the agency agreement and the SOPs. Otherwise a vacuum appears in which each party assumes the other has already reported, and the deadline passes with nobody accountable.

4. Practical recommendations

1. Issue a written designation document: state the name, position, contact details, scope of authority and effective date of the Vigilance Responsible Person, and retain it together with the registration dossier.
2. Build templates for the four report types: one set each for initial, follow-up, final and trend reports, with fields matching the EFDA forms.
3. Establish a trend baseline: track complaint and incident rates by product family, and set trigger thresholds and review cycles.
4. Confirm the periodic summary report cycle with EFDA in advance: obtain written confirmation of cycle and format before the first submission (practical estimate).
5. Write the division of duties into the agency agreement: who receives, who triages, who submits, who archives, and the maximum internal forwarding time.
6. Archive by re-registration scope: keep the Responsible Person’s report history ready for the year-5 re-registration and the one-year evidence submission for high-risk products.

5. Verification checklist

• □ Vigilance Responsible Person designated in writing and the designation document retained
• □ Designation document states name, position, contact details and scope of authority
• □ Templates built for the four report types: initial, follow-up, final and trend
• □ Statistical baseline and trigger thresholds established for trend determination
• □ Cycle of the periodic summary safety report confirmed with EFDA (practical estimate)
• □ Vigilance division of duties and internal forwarding time written into the agency agreement
• □ Report records archived against the re-registration scope

Regulatory information verified as of 29 October 2026. The Vigilance Responsible Person and report type requirements listed in this article follow the current text of Sections 3.1, 3.2.4 and 3.4 of the Medical Device Vigilance Guideline EFDA-GDL-090; when the guideline is revised, the verification must be repeated.

• 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.