Egypt's device registration doesn't clear a shipment

One law, one authority, ten years

Egypt's Medical Device Law No. 10 of 2003 is still the framework device registration runs under, but the authority administering it isn't the body the law originally named. Law No. 151 of 2019 created the Egyptian Drug Authority, EDA, folding Egypt's separate drug-control bodies into one regulator and, with them, the device-registration function that used to sit inside the health ministry's own structure. A foreign manufacturer without a direct Egyptian presence has to appoint a local representative — commonly called the Egyptian Registration Holder, or ERH — who files the registration dossier, carries the regulatory relationship with EDA going forward, and stays EDA's point of contact for whatever follows, including vigilance reporting if a problem surfaces later. Once granted, the device's own registration is valid for ten years, a standing term closer to Colombia's own decade-long Registro than to the five- and six-year cycles more common elsewhere.

A dossier built on someone else's evidence

The documentation a sponsor files to reach that ten-year registration typically includes a Certificate of Free Sale from the device's country of origin, an ISO 13485:2016 certificate, a Declaration of Conformity, and — described in EDA-facing guidance as strongly recommended rather than strictly mandatory — a CE certificate where one already exists. That's a dossier built substantially on evidence another regulator or certification body already produced, the same reliance this blog has already traced in markets that lean on a reference approval rather than reviewing a file from first principles. Where Egypt's own structure actually departs from that familiar pattern is what happens after the registration is granted, not what goes into earning it.

Registration opens the market; MeDevice opens the port

A valid EDA registration is what lets a device be sold in Egypt at all, but it isn't what lets any individual shipment of that device cross the border. EDA requires a separate import approval and customs-release request for each shipment, filed through the agency's own MeDevice platform — a digital system EDA's own published guidance describes as the route for exactly those two requests together. EDA's published timeline commits to a response, accepted, rejected, or suspended pending completion, within two working days of a request going in. A registration with years left on its own ten-year term says nothing about whether a specific shipment has cleared that separate approval; the registration is the standing credential, the per-shipment request is a recurring one layered on top of it.

The ERH answers for both, on different timetables

Because the ERH is the entity named on the registration and the point of contact with EDA, it's also the party filing each shipment's own MeDevice request and carrying the post-market obligations — vigilance reporting, recall coordination — that apply for as long as the registration stays active. A distribution agreement that treats the ten-year registration as the only date worth tracking has no mechanism to notice a shipment suspended on MeDevice over an incomplete customs-release request, because that failure doesn't touch the registration's own expiry at all. The registration can be in year three of ten and still not be enough, by itself, to move a given shipment through an Egyptian port.

Where this meets the file

An Egypt row in a cross-border registration tracker needs the ten-year registration date tracked separately from a shipment-level field recording each MeDevice import approval and its customs-release status, rather than one “Egypt: registered” status standing in for both the standing credential and the recurring one. A cross-border tracker built to carry that structure, alongside the launch catalog's other device-registration templates, is previewed there now. If your program has tracked EDA's two gates differently, the shelf takes that correction directly.