What Is UDI Validation? A Guide to GS1 DataMatrix Data and Print Quality Checks

UDI validation is a layered process for checking that a medical-device identifier belongs to the correct device, uses a valid data structure, matches the human-readable text and relevant database record, and is printed at the required quality level. It is more than proving that a phone or handheld scanner can decode the symbol once.

A reliable workflow evaluates the data, label, database record, and physical symbol independently.

1. The Four Layers of UDI Validation

A. Master Data Validation

• The UDI-DI / GTIN must be assigned to the correct device model and packaging level.
• Brand, model, catalogue number, device status, and package data should agree with the manufacturer's controlled master data.
• Packaging levels must be assessed individually; a unit package and a case should not reuse a DI without confirming the applicable assignment rules.

B. GS1 Data Structure Validation

• A GS1 DataMatrix must be encoded as a GS1 symbol with FNC1 in the first position.
• (01) must contain a 14-digit GTIN with a valid Modulo-10 check digit.
• Manufacturing date (11) and expiration date (17) use the GS1 YYMMDD data format.
• Lot (10) and serial number (21) are variable-length fields. An appropriate FNC1 group separator is required when another element follows one of these fields.
• Encoded production identifiers should reflect the production controls that actually apply to the device.

C. Label and Database Consistency

• Decoded machine-readable data and the HRI (human-readable interpretation) must present the same DI and PI values.
• For the US market, compare the DI with its GUDID/AccessGUDID record. For the EU market, confirm the relevant UDI-DI and Basic UDI-DI relationship in EUDAMED.
• The EU Basic UDI-DI supports regulatory documentation and device grouping; it is not the UDI-DI printed on the product label.
• A successful database submission does not correct a poor symbol, and a high-quality symbol does not make inaccurate master data valid.

D. Physical Symbol Quality

• Keep the GS1 DataMatrix quiet zone clear on all four sides; its minimum width is 1X.
• Select X-dimension, symbol size, placement, and target grade from the relevant GS1 application standard.
• Evaluate contrast, axial non-uniformity, grid non-uniformity, fixed-pattern damage, and print growth on the final printed label.
• Printed 2D symbol quality is measured under ISO/IEC 15415 with suitable, calibrated verification equipment. Direct part marking also requires the applicable DPM quality method to be considered.

2. Scanning, Data Validation, and Verification Are Different

• Scan test: Shows whether one reader can decode the symbol. It is a useful go/no-go check.
• Data validation: Checks GTIN check digits, AI structure, field length, date format, FNC1 separators, and business rules.
• Barcode verification: Grades print quality under standardized lighting, aperture, and measurement conditions.
• Regulatory review: Assesses the label and database content against current FDA, MDR/IVDR, and local market requirements.

None replaces the others. A controlled UDI process includes all four and retains results for the relevant product, printer, material, and production line.

3. Checking a Sample GS1 UDI String

Example HRI:

(01)09506000134352(11)260904(17)290904(10)LOT9876(21)SN54321

Use this sequence:

1. Confirm that AI (01) contains 14 digits and that the final digit matches the GTIN check-digit calculation.
2. Check that AI (11) and AI (17) contain six-digit GS1 dates and agree with controlled production records.
3. Compare lot (10) and serial (21) values with the ERP/MES or batch-release record.
4. Decode the barcode and inspect field boundaries without confusing transmitted FNC1/group-separator characters with the parentheses used in HRI.
5. Compare the decoded payload with the HRI, approved label artwork, and applicable DI database record.
6. Print using production printer, ribbon, substrate, and speed settings; then verify the result with ISO/IEC-compliant equipment.

4. Common UDI Validation Failures

• A valid-looking but incorrect GTIN: A correct check digit does not prove that the number belongs to the intended model or packaging level.
• Confusing Data Matrix with GS1 DataMatrix: A readable symbol is not necessarily encoded with the GS1 FNC1 structure.
• Missing a variable-field separator: Data may merge when another element follows a variable-length lot or serial field.
• Mismatch between HRI and encoded data: Manual text can be updated while the barcode still carries an older value.
• Testing only the screen image: Qualification must cover the actual label material and production conditions.
• Testing with one reader only: A successful read does not guarantee reliable performance in an open scanning environment.

5. A Pre-validation Workflow in UDImaker

1. Enter GTIN (01), manufacturing date (11), expiration date (17), lot (10), and serial (21) in the GS1 DataMatrix fields.
2. Review built-in checks for GTIN length and check digit, date format, and supported field lengths.
3. Compare the generated GS1 payload and HRI with your approved production source.
4. Export at the intended size as PDF/SVG or a 300 DPI image and print at 100% / Actual Size.
5. Decode the printed symbol with UDImaker for a quick content-oriented pre-check.
6. Before production approval, test the final label with a calibrated ISO/IEC-compliant barcode verifier and compare it with the target-market database record.

UDImaker's field checks and decoder can help find design-stage errors early; they do not provide regulatory approval, database registration, or an ISO/IEC barcode quality certificate. Final compliance remains part of the manufacturer's quality and regulatory process.