UDI Label Data Field Reference (DI, PI and GS1 Application Identifiers)
Getting UDI label data right means knowing which fields are fixed, which change with every lot, and which only live in a database. This reference lists the elements people ask about most, with GS1 application identifiers and formats.
| Element | Group | GS1 AI | Format | Label and data note |
|---|---|---|---|---|
UDI | Overview | n/a | DI plus PI | A UDI is made of a device identifier (DI) and, where applicable, a production identifier (PI). |
Device identifier (UDI-DI) | DI | (01) | 14 digits (GTIN) | Fixed part. Identifies the labeler and the specific version or model. Changes when a change affects the label or the device. |
Lot or batch number | PI | (10) | Variable, up to 20 alphanumeric | Include in the PI when the label shows a lot or batch. |
Serial number | PI | (21) | Variable, up to 20 alphanumeric | Include in the PI when the label shows a serial number. |
Manufacturing date | PI | (11) | YYMMDD, 6 digits | Include in the PI when the label shows a manufacturing date. |
Expiration date | PI | (17) | YYMMDD, 6 digits | Include in the PI when the label shows an expiration date. Day 00 is allowed in GS1 when no day applies. |
Basic UDI-DI (EU MDR) | EU | (8013) GMN | Up to 30 characters | Not printed on the label. Used in EUDAMED, certificates and the declaration of conformity to group devices. |
Human readable interpretation (HRI) | Label | n/a | Text beside the barcode | The plain text form of the UDI is required alongside the machine readable form. |
Automatic identification and data capture (AIDC) | Label | n/a | Linear barcode or 2D symbol | The machine readable form of the UDI, for example GS1-128 or GS1 DataMatrix. |
Issuing agency | Governance | n/a | GS1, HIBCC, ICCBBA | FDA accredits issuing agencies. Use the coding scheme of one agency for each UDI. |
HIBCC format | Governance | n/a | Starts with + | HIBCC labeler identification code and product data follow the plus sign. |
Package level DI | DI | (01) | 14 digits (GTIN) | Each package configuration, such as unit, box and case, needs its own DI. |
Labeler | GUDID | n/a | Company name and DUNS number | The labeler submits the device record to the FDA GUDID database. |
Brand name | GUDID | n/a | Text | GUDID attribute on the device record. |
Version or model number | GUDID | n/a | Text | GUDID attribute that distinguishes versions and models. |
Catalog number | GUDID | n/a | Text | GUDID attribute when the device has a catalog number. |
Direct marking | Label | n/a | Permanent mark on device | Devices intended for more than one use and reprocessed before each use must carry a permanent UDI on the device, subject to rule exceptions (see 21 CFR 801.45). |
Device description | GUDID | n/a | Text | GUDID attribute describing the device. |
Packaging quantity | GUDID | n/a | Number | GUDID attribute giving how many lower level units a package holds. |
Reference only. Confirm details against the current FDA UDI rule, EU MDR Article 27 and Annex VI, and the GS1 General Specifications for your symbology. Other markets add their own rules.
Check label data against ERP master data
Optional: a short review of automated checks between your ERP item and lot data and your UDI labels.
Optional. The tool and every export work without this. No spam.
How to use this reference
Search for an element such as lot, expiry or serial and read its GS1 application identifier and format. Use the table when you design a label template, write a barcode string, map ERP fields to label fields or prepare a GUDID submission. Export the table to Excel to share it with packaging, regulatory and IT teams so everyone works from the same list.
- DI is fixed per version or model; PI changes with production
- Dates in GS1 use six digits in YYMMDD order
- Print both the human readable text and the barcode
- Use one issuing agency scheme for each UDI
DI, PI and the database record
The UDI has two parts. The device identifier tells you what the device is. The production identifier tells you how this unit was made, using lot, serial, manufacturing date or expiration date, whichever apply. The data about the device lives in a regulator database, GUDID in the United States and EUDAMED in the European Union. The label links to the record through the DI, so a wrong DI breaks the link even if the barcode scans correctly.
ERP and label system notes
Most ERPs store the GTIN on the item master and the lot and expiry dates on the inventory lot record. Label printing then combines them into the GS1 string. Check that the lot field length in your ERP does not exceed 20 characters, that expiry dates print as YYMMDD, and that a change to the item revision triggers a label review. Missing a DI change after a design change is one of the more common audit findings.
Common mistakes
Typical errors include printing the lot in the wrong application identifier, using a date format other than YYMMDD, forgetting a package level DI, leaving the human readable text off a small label, and not updating the GUDID record when a version changes. Test every label design by scanning the barcode with a verifier and comparing the decoded string against the item and lot data.
Frequently Asked Questions
What is the difference between UDI-DI and UDI-PI?
The DI is the fixed identifier for a device version or model. The PI is the variable part that can include lot, serial number, manufacturing date and expiration date. The label shows the PI elements that apply to that device.
Which GS1 application identifier is the expiry date?
Application identifier 17 carries the expiration date in YYMMDD format. Identifier 10 carries the lot or batch, 21 the serial number and 11 the manufacturing date.
Is the Basic UDI-DI printed on the label?
No. In the EU the Basic UDI-DI is used in EUDAMED, in certificates and in the declaration of conformity to link devices to a group. It is separate from the UDI-DI that appears on the label.
Do I need a GTIN for every package level?
Each package configuration with its own contents needs its own DI. A single unit, a box of ten and a case of one hundred each get their own identifier, with the package relationships recorded in the database.
If your item, lot and expiry data sit in an ERP, Netray can help build checks that compare label data to ERP master data, running on your own infrastructure.
Related Tools
Device History Record (DHR) Template
Build a device history record for one lot or serial number: quantities, dates, labeling, acceptance and release sign-off. Exports to PDF or Word.
Engineering & PLMDesign History File Index Template
An editable index of the records that make up a medical device design history file, with status, owner and review date for each document.
Quality & InspectionMedical Device Complaint Handling Form Template
A complaint intake and investigation form for medical devices, covering product details, event description, reportability assessment and closure.
Quality & InspectionISO 13485 Internal Audit Checklist
A clause-organized checklist for auditing a medical device quality management system against ISO 13485:2016, with critical items flagged.
More Compliance & Contracts tools
See all- Medical Device Recall Cost Estimator
- Medical Device Standards Reference Table (ISO, IEC, ASTM)
- SAP SoD Residual Risk Score Calculator
- SAP Firefighter ID Usage Review Log
- IBM i (AS/400) User Profile Access Review Worksheet
- SyteLine Security and User Access Audit Checklist
- Infor XA (MAPICS) User Access Review Worksheet
- China ERP Data Security and Compliance Assessment
- ERP Vendor Data Processing Agreement Outline