UDI systems were never built with a shared blueprint. Here's why chasing one universal source of truth creates more friction than it solves — and what to do instead.
Every medical device manufacturer eventually hits the same wall: the same product looks different depending on which system you ask. Your ERP has one version of a device record. Your PLM has another. EUDAMED wants a third shape entirely, and GUDID wants a fourth. None of them are wrong — they were each built for a different job, with different regulatory intentions, different governance rules, and different definitions of what "done" looks like. The traditional answer has been to chase a single source of truth: one master record that feeds everything downstream. In practice, this rarely survives contact with reality. Regulatory schemas change on their own timelines. GDSN recipients want different attributes than EUDAMED does. A field that's optional in one registry is mandatory in another the moment a device ships in more than one market. Trying to force all of that into one rigid structure just means someone, somewhere, is constantly patching exceptions. We think about it differently. Instead of one master record, treat your product data as a set of building blocks — granular, well-owned attributes that can be assembled and reassembled into whatever shape a given registry, trading partner, or internal process needs. A clinical size value doesn't need to "belong" to EUDAMED or GUDID specifically; it needs a clear owner, a clear format, and a clear set of rules about when it applies. From there, assembling a EUDAMED submission or a GDSN sync becomes a matter of composition, not reconciliation. This shift matters most in four areas: attribution (what the data actually is), context (what regulatory rules currently say about it), format (how each registry expects to receive it), and governance (who owns it and how changes get approved). Get those four right at the attribute level, and every downstream submission — remediation, new registry onboarding, GDSN sync — gets dramatically simpler, because you're no longer starting from scratch each time. If your team is staring down the EUDAMED deadline, or just tired of rebuilding the same mapping logic every time a new registry comes online, this is the conversation worth having before you buy another tool.