FDA GUDID vs EUDAMED: One Device, Two Databases
Selling the same medical device in the US and EU means managing two registry records. Learn how FDA GUDID and EUDAMED differ, where UDI requirements overlap, and how to keep both records aligned without losing sight of devices in the field.

Frequently asked questions.
Do we need separate UDIs for the US and the EU?
Often not. A GS1, HIBCC or ICCBBA identifier can usually be reused on both sides, subject to each regime's assignment and change rules. What differs is the surrounding record: the attribute sets, the nomenclature and, in the EU, the additional Basic UDI-DI layer.
What is the Basic UDI-DI and does GUDID have one?
The Basic UDI-DI is an EU concept that groups devices sharing the same intended purpose, risk class and essential design and manufacturing characteristics. It does not appear on the label and is the main key for regulatory documentation. GUDID has no direct equivalent, which is why manufacturers coming from the US system often miss it.
Which nomenclature does each system use?
EUDAMED uses EMDN. The US side relies on GMDN. Check whether a current, authoritative crosswalk exists for your device types before relying on one, and give your own classification in both systems an owner.
Is EUDAMED just the European GUDID?
No. GUDID is a device identification database. EUDAMED covers device and UDI registration plus actor registration, certificates, vigilance, clinical investigations and market surveillance. The scope is considerably wider.
How do we keep both registrations in sync?
Maintain one internal master record and treat both registries as outputs of it, with the update triggered by your engineering change control process rather than by a periodic review. Maintaining data separately inside each portal is the most common cause of drift.




