Summary: Unique Device Identification (UDI) programs in major markets require device manufacturers to mark products and packaging with standardized identifiers that regulators and hospitals can trace. In practice, GS1 Data Matrix (or allowed alternatives per jurisdiction) encodes the DI (device identifier) and PI (production identifier) in a dense 2D symbol that survives sterilization pouches, curved instruments, and high-speed hospital scanning.
Unlike promotional QR codes, UDI carriers are validated against formal grammars: wrong application identifier order or an illegal character can block import or trigger field corrections worth millions in delayed kits.
EU MDR / IVDR and FDA UDI: shared pressure, different portals
Both ecosystems push manufacturers toward machine-readable labels and central registries (EUDAMED in the EU, GUDID in the US). The label is still the legal front line: if the Data Matrix is unreadable at receiving, the ERP line stops even when the cloud record is perfect.
Batch label systems must tie each print job to a released master data revision. “We regenerated codes overnight” is not an acceptable root cause for a recall rehearsal.
Printing and verification checklist
- Match X-dimension to ISO/IEC 16022 grades your notified body or QA SOP cites.
- Run verification (not just decode) on samples from start, middle, and end of a lot.
- Log who approved the CSV row set that fed the batch exporter—UDI audits ask.
Broader lesson
Healthcare is the sharp end of “batch QR” discipline: no vanity URLs, no manual Excel fixes on the factory floor. The same rigor increasingly applies to pharma serialization and high-risk consumer goods.
Official references
- FDA: Unique Device Identification System
- EU: GS1 UDI resources (cross-border implementation guidance).