User and Healthcare Facility Reporting Through the MDAER in Ethiopia

1. Key takeaways

Ethiopia’s vigilance system is bidirectional. At one end stand the reporting obligations of manufacturers and licence holders (the three-tier deadlines of EFDA-GDL-090); at the other end stands a reporting channel for healthcare institutions and users: the authority provides a dedicated Medical Device Adverse Event Report form (MDAER) for healthcare institutions, users and the public to submit. The GRZAN regulatory team notes the decisive consequence: the existence of the MDAER means an event may reach EFDA before the manufacturer becomes aware of it, and companies cannot assume they will always be the first to know. The form is maintained by the authority itself, its fields are defined from the user’s perspective rather than the manufacturer’s, and its data flows into the same post-market information pool that feeds risk-based oversight. Understanding what the user side can file, and when, is therefore not peripheral knowledge but a structural input into the manufacturer’s own deadline management. In practice the two channels also serve different defensive purposes: the MDAER builds the public record of a hazard as seen from the field, while the manufacturer’s vigilance report builds the record of analysis and response. A company that monitors both records can detect discrepancies early, before they harden into conflicting accounts of the same event.

2. Legal basis

3. Expert insights

Insight 1: user reporting and manufacturer reporting are two independent channels, not two copies of the same material.

The MDAER addresses the user side, where the filer is concerned with what happened to a given device; the vigilance report addresses the regulatory side, where the submitter must explain why the event happened, how far its impact extends and what measures are being taken. The two differ in granularity, cannot substitute for each other, and the manufacturer’s reporting obligation is not discharged because a user has already filed a form. Treating a filed MDAER as evidence of compliance is one of the costliest misreadings of this system.

Insight 2: the three MDAER element groups map directly onto three fields of the corporate SOP.

The MDAER covers device information, event description and severity determination. If a company aligns its internal reporting template with these three fields of the official form, incoming user-side information can be mapped directly onto the vigilance report template, which shortens the interval between awareness and submission dramatically. The alignment costs little to implement once and then pays off at every event for the life of the product.

Insight 3: severity determination is the common difficulty on both sides.

User-side judgements of whether an event constitutes a serious public health threat tend to run either too conservative or too lenient relative to the three-tier standard of EFDA-GDL-090. The company should prepare a concise determination guide for users, delivered together with the device, that reduces misjudgements and the resulting mismatch of deadlines. Clear wording at delivery time prevents both over-reporting noise and under-reported genuine threats.

Insight 4: user reports can become a source of leads for official sampling and market surveillance.

MDAER data enters EFDA’s post-market information pool and feeds risk-based market surveillance and sampling. This means repeated user reports on the same model may trigger an official sample test of that product, rather than remaining a matter of handling single events. Monitoring the report history of each model is therefore part of exposure management, not only of complaint handling.

Insight 5: the local representative is the first recipient and must be able to translate.

Information filed by healthcare institutions usually arrives in local languages and local clinical context. The local representative must be able to translate those descriptions into vigilance terminology; this is precisely the practical setting in which item 9.2.3(f) of EFDA-GDL-046 requires both parties to jointly assume vigilance responsibility. Translation capability, contact routing and response deadlines should all be testable before the first real event arrives, for example through a scripted dry run between the field and the manufacturer’s vigilance team.

4. Practical recommendations

1. Obtain the current MDAER version and build the SOP on its fields: align the internal reporting template with the official form field by field.
2. Attach a how-to-report-adverse-events leaflet to the device documentation: state the reporting channels and the three elements the filer must provide.
3. Provide users with a concise severity determination guide: explain in plain wording which situations must be notified immediately to the manufacturer and to EFDA.
4. Make the local representative the first recipient and agree a translation deadline: user reports are forwarded to the manufacturer within 24 hours.
5. Build a repeat-event alert per model: when accumulated reports for one model reach the threshold within a defined period, start a trend assessment.
6. Archive user reports and vigilance reports separately: retain the original user filings and the corporate submissions to preserve a complete evidence chain.

5. Verification checklist

• □ Current official version of the MDAER obtained
• □ Internal reporting template fields aligned with the MDAER
• □ Adverse event reporting leaflet attached to the device documentation
• □ Severity determination guide provided to users
• □ Local representative set as first recipient with an agreed translation deadline
• □ Repeat-event alert threshold established per model
• □ User reports and vigilance reports archived separately

Regulatory information verified as of 29 October 2026. The user reporting requirements listed in this article follow the Medical Device Adverse Event Report form (MDAER) currently published by EFDA and the current text of EFDA-GDL-090; when the form is revised, its fields 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.