Unique Device Identification.

One FDA regime, three issuing agencies' grammars (GS1, HIBCC, ICCBBA), the DI/PI split, and CC0 enrichment with GMDN stripped.

The device label, blown out.

the standard's own seam rendered first: DI | PI — one identity, then its production facts. HIBCC and ICCBBA agency forms are not parsed this run; the engine answers a typed unrecognized naming the agency.

(01) 0084458800328 DI — device identifier the what — a GTIN-14 under the GS1 issuing agency, minus its check digit
8 check the DI's own check digit — mod10 pass
(17) 261231 PI — expires 31 Dec 2026
(10) LOT42 PI — batch the production identifiers decide instance vs lot grain
DI      0084458800328 · check 8
sum     0×3 + 0×1 + 8×3 + 4×1 + 4×3 + 5×1 + 8×3 + 8×1 + 0×3 + 0×1 + 3×3 + 2×1 + 8×3 = 112
check   (10  112 mod 10) mod 10 = 8   → mod10 pass

The row.

schemeudi.gs1
grammarOne regulatory regime, three issuing agencies, three grammars: GS1 (GTIN-14 as DI, AIs as PI), HIBCC (+$ conventions), ICCBBA (ISBT 128). The FDA UDI formats document is the umbrella grammar.
check digitPer agency: the GS1 form rides the mod-10 rail; structure per issuing agency's published format.
canonical formDI (device identifier) split from PI (production identifiers — lot, serial, expiry), each typed.
symbologiesGS1 DataMatrix and GS1-128 dominate; HIBCC and ICCBBA carriers per agency
enrichmentAccessGUDID / openFDA device (CC0) — GMDN-licensed columns stripped at ingest; the served record is free and clear by construction
join ruleThe DI is the what of a device event; the PIs decide instance vs lot grain, the same way AI 21/10 do for retail GTINs.
pinned digestudi.gs1 sha256:440db3e1c3ffcda1e8933b7cebc668e8647dcf334b624f70a21f4b134976d249
as data/schemes/udi.json

In practice.

AccessGUDID proved the multi-scheme resolver pattern at government scale — one endpoint answering three issuing agencies' grammars. The registry generalizes exactly that pattern to every scheme family in this table.

On the blog.

  • UDI: the FDA already runs a multi-scheme resolver, and it proves the architecture

    AccessGUDID accepts identifiers from three accredited issuing agencies — GS1, HIBCC, ICCBBA — detects the grammar, splits device identifier from production identifiers, and serves the answer from public-domain data. A working, government-scale precedent for a one-endpoint, every-scheme resolver.

  • Pharma already lives in 2027: DSCSA as the serialization precedent

    Every US prescription-drug package already carries a GS1 DataMatrix with GTIN, serial, lot, and expiry under DSCSA — the one US vertical where serialized 2D is universal at the unit level. Parsed live, with the NDC-inside-GTIN embedding shown, and the lessons a cross-vertical CTO can actually reuse.

Get an API key.

The local verbs run from npx barcoding.dev today with no key. A key opens the network half of the verb set.