Vigilance Reporting Timeframes for Medical Devices in Egypt under EDREX GL.CAP.Care.040

1. Key takeaways

Egypt’s medical device vigilance framework is set out in the Egypt Medical Device Vigilance System Guideline (EDREX: GL.CAP.Care.040 Version 1, published November 2025), which organises the manufacturer initial report (the MIR, Annex 7) into three severity-based timeframes. For a serious public health threat, reporting must be immediate and in any case not later than 2 calendar days after the manufacturer has established the causal relationship between the incident and its device. For death or a serious deterioration in a patient’s state of health that was unanticipated, reporting must be immediate and not later than 10 calendar days. For any other serious incident or near incident, the ceiling is 15 calendar days. All three clocks start from the point at which the manufacturer establishes the causal relationship, and the timeframes apply only to serious incidents that occur within Egypt.

2. Legal basis

The reporting timeframes and the surrounding obligations rest on the following instruments currently in force in Egypt.

3. Expert insights

Insight 1: the clock starts at establishment of the causal relationship, not at awareness of the event.

All three tiers use identical wording: after the manufacturer established the causal relationship between that incident and their device. This differs from the approach taken in other IMDRF-aligned systems, where the clock typically runs from the moment the manufacturer becomes aware of the event. The Egyptian formulation gives manufacturers an internal window in which to investigate causation, but it also demands traceable, written records of when the causal relationship was established. Without such documentation a company cannot demonstrate its start point to the regulator.

Insight 2: immediately, not later than, is a dual requirement rather than an N-day deadline.

Each tier is expressed as Immediately, not later than N calendar days. The word immediately means that reporting should begin as soon as causation is established; the N calendar days are an upper limit, not a target date. Companies should design their SOPs so that establishment of causation is the triggering action for report preparation, instead of planning submissions against the outer deadline.

Insight 3: the territorial limitation is written directly into the text.

Immediately before the timeframe table, the guideline states separately that only serious incident reports arising in Egypt are submitted to MDSU under these timeframes. This means that the reporting route and the clock for incidents occurring outside Egypt are handled separately and cannot automatically inherit the three-tier schedule. Global incident data must therefore be triaged by territory before any Egyptian submission decision is made.

Insight 4: 15 calendar days is the official figure, and it conflicts with some secondary sources that cite 30 days.

Several industry summaries describe the Egyptian timeframe for other serious incidents as 30 calendar days. As a practical estimate, that figure does not match the official EDREX guidance; the 15 calendar days stated in GL.CAP.Care.040 Version 1 governs. Discrepancies of this kind are precisely why checking the official original text is an irreplaceable step in any compliance programme.

Insight 5: initial reports must not be delayed to collect further information.

The guideline is explicit that the initial incident report should contain as much relevant detail as is available at the time, such as the device type, brand and model, and that reporting must not be delayed in order to gather more information. Supplementary details can be provided in subsequent follow-up submissions. Waiting for a complete investigation before reporting is therefore not a compliant strategy.

Insight 6: abnormal use is not reported through the adverse event procedure.

The guideline defines abnormal use in terms that can include off-label use, for example a healthcare professional using the device outside the intended purpose stated in the instructions for use on the basis of medical judgement. Abnormal use does not need to be reported by the manufacturer to the national competent authority under the adverse event reporting procedure; instead it is handled by healthcare institutions and the relevant regulatory authority through a dedicated mechanism.

Insight 7: the reporting duty forms a closed loop with registration and variation commitments.

Section 8 of GL.CAMD.002 requires companies applying for registration or re-registration to commit to reporting recalls, FSN or FSCA occurring worldwide as well as incidents monitored within Egypt. Section 6.2, item 4 of GL.CAMD.003 requires variation applicants to commit to reporting any regulatory measures related to device safety occurring globally or in Egypt (incidents, recalls, FSN, FSCA), within the timeframes and reporting requirements set by the vigilance guideline. Taken together, the three documents push vigilance obligations forward into the pre-market stage of the product lifecycle.

4. Practical recommendations

The following actions translate the three-tier schedule into day-to-day practice.

1. Create written determination records for causation: this is the evidentiary basis on which all three clocks start.
2. Write the SOP as report upon establishment, treating the 2/10/15 figures as ceilings rather than targets.
3. Separate in-Egypt from ex-Egypt incidents: only incidents occurring in Egypt are reported to MDSU under the three-tier timeframes.
4. Submit the initial report on known information first, and follow up with supplementary details later.
5. Route abnormal use through the dedicated healthcare facility and regulatory mechanism, keeping it out of the adverse event channel.
6. Mirror the vigilance commitments in registration and variation dossiers so the records stay synchronised.
7. Verify externally sourced figures against the official guideline and treat outdated 30-day claims with caution.

5. Verification checklist

• □ Three-tier timeframes written into SOPs: 2/10/15 calendar days
• □ The causation establishment date is set as the clock start and supported by written records
• □ Reporting routes are distinguished between incidents in Egypt and incidents occurring abroad
• □ The initial report template includes device type, brand, model and other immediately available details
• □ Abnormal use cases are handled through the dedicated mechanism and not mixed into adverse event reports
• □ Vigilance commitments in registration and variation dossiers are synchronised
• □ All timeframe figures have been checked against the original text of GL.CAP.Care.040 Version 1

Regulatory information verified as of October 29, 2026. The vigilance timeframes listed in this article follow the current text of EDREX: GL.CAP.Care.040 Version 1 (published November 2025).

• Egypt local support: GRZAN assists manufacturers from the Chinese mainland and overseas with EDA medical device registration, import approval and variation applications, including registration applicant pathway design (importing company, local factory, or Scientific Office), preparation for Scientific Committee evaluation, demonstration of free sale certificate routes from reference countries, Arabic labelling and instructions-for-use localization, and the setup of vigilance and periodic reporting systems.
• Service capabilities: product classification and risk grading (devices Class I–III, IVD Class A–D), registration and re-registration, applicability assessment for system registration and bundled registration, three-way variation classification, import approval and annual import plans, and support for vigilance reporting and field safety corrective actions.
• Contact: hito.lin@grzan.cn; website www.grzan.cn.