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.

FDA GUDID vs EUDAMED: One Device, Two Databases

If you sell the same device in the United States and the European Union, you register it twice, in the FDA's GUDID and in EUDAMED, under two regimes, with two sets of data that overlap but do not match.

None of that is a criticism of either regulator. It is simply a practical fact that costs manufacturers more time than the registrations themselves, because the work is not duplicated but nearly duplicated. Nearly is the expensive part.

What the two systems are

GUDID is the FDA's Global Unique Device Identification Database. It holds device identification information for devices marketed in the United States. Submissions are made by the labeler through the FDA's account system.

EUDAMED is the European database for medical devices under Regulation (EU) 2017/745 and the IVDR. It is broader in scope than GUDID: alongside UDI and device registration it covers actor registration, certificates, vigilance, clinical investigations and market surveillance.

That difference in scope matters more than it first looks. GUDID is a device identification database. EUDAMED is a device identification database inside a larger regulatory system.

What is shared

Both are built on the same underlying idea, and the issuing entities recognised on each side overlap: GS1, HIBCC and ICCBBA appear on both the FDA list and the EU list, and the EU also designates IFA. If you already carry a GS1 GTIN-based identifier, you are not starting from scratch on either side, but check each regime's assignment rules before assuming it carries over unchanged.

Both separate the device identifier from the production identifier. Both expect the identifier to appear on the label and, for certain devices, in a machine-readable form. Both require the record to be updated when the device changes.

So the identifier itself usually travels. What does not travel is the record around it.

Where they diverge

GUDID and EUDAMED compared, for one device sold in both markets
DimensionGUDID (United States)EUDAMED (European Union)
Entity registrationNo equivalent actor registry. Works through labeler accounts and the FDA's establishment registration.Economic operators register as actors and obtain an SRN. Manufacturers, authorised representatives and importers each have their own obligations, set out per role in EUDAMED for importers and distributors.
Grouping identifierNone. There is nothing in the US system to map a Basic UDI-DI to.The Basic UDI-DI ties together devices sharing the same intended purpose, risk class and essential design and manufacturing characteristics. It does not appear on the label.
NomenclatureGMDN.EMDN.
Data fieldsThe attribute set overlaps with the EU without being equal.Some fields have no GUDID counterpart, and several shared concepts use different vocabularies.
What the data is used forFeeds AccessGUDID for public lookup.The public side is part of a wider transparency regime that also covers certificates and vigilance.
Current pressure pointPhased in by risk class.28 November 2026, for devices first placed on the market before the mandatory date that are still being placed on the market after it (see the Commission's transition overview and what manufacturers must do before November 2026).

The regulation defines it in Annex VI:

"The Basic UDI-DI is the primary identifier of a device model. It is the DI assigned at the level of the device unit of use. It is the main key for records in the UDI database and is referenced in relevant certificates and EU declarations of conformity."

Annex VI, Part C of Regulation (EU) 2017/745. There is no US counterpart to quote against it, which is the whole difficulty.

Two of those rows cause most of the trouble. Teams coming from a GUDID-first process consistently underestimate the Basic UDI-DI, because there is nothing to map it to and regrouping after submission is painful. On the nomenclature, do not assume an authoritative one-to-one crosswalk between EMDN and GMDN exists; check what is current for your device types before you rely on one.

Where manufacturers actually lose time

Very little of it goes into the submissions themselves. It goes into keeping the two records from drifting apart. A device changes. A configuration is added, a label is revised, an accessory is discontinued. Somebody updates one registry. Three months later the two records describe slightly different devices, and nobody notices until an audit or a safety notice makes them compare.

The second loss is internal. Regulatory holds the registrations. Service holds what is actually in the field. Those are usually different systems with different identifiers, so the question "which registered configuration is this unit in Ohio running" needs a person rather than a query.

That second gap is the one worth fixing, because it is the same gap that makes a field safety corrective action slow. We wrote about what the identifier is worth once it reaches service in Beyond UDI.

A working approach for dual-market manufacturers

Keep one internal master, not two. Maintain the device data once, in your own system, and treat GUDID and EUDAMED as two outputs of it. Manufacturers who maintain the data inside each portal end up with two truths and no way to tell which is stale.

Map the fields once, in writing. Build the crosswalk between your master, the GUDID attributes and the EUDAMED attributes, including the nomenclature mapping. Give it an owner. It will need updating.

Treat the Basic UDI-DI as a structural decision. Decide how you group devices before you submit, not after. Regrouping later is painful.

Trigger updates from change control rather than from a calendar. The registry update should be a step in your engineering change process. If it is a quarterly review, you will have drift between reviews.

Tie the registered configuration to the units in the field. This is the step most companies skip. Knowing that configuration B is registered is regulatory work. Knowing how many units of configuration B are in service, where they are, and who operates them, is what you need on the day something goes wrong. That is an installed base question, and we set out how to evaluate tooling for it in our buyer's guide.

FAQs

Frequently asked questions.

01.

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.

02.

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.

03.

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.

04.

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.

05.

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.