Every medical device that reaches a U.S. clinic or hospital today is supposed to carry a barcode that says, unambiguously, what it is. That barcode is built on a standard most administrators have never had to think about directly — GS1's Global Trade Item Number, or GTIN — and it sits at the center of a federal rule that quietly reshaped how practices order, receive, and track medical supplies. For a small or mid-size practice, understanding the basics of GS1/UDI barcoding is no longer optional trivia; it determines whether inventory systems, EHR integrations, and distributor ordering portals talk to each other cleanly or generate constant reconciliation headaches.
What the FDA's UDI Rule Actually Requires
The FDA issued its final Unique Device Identifier (UDI) rule on September 24, 2013, and phased in compliance by device class over the following years, with deadlines running from September 24, 2014 through September 24, 2020. The rule requires most medical devices sold in the U.S. to carry a UDI on their label and packaging, in both human-readable text and a machine-readable format such as a barcode. Devices meant for multiple uses and reprocessing must also have the UDI marked directly on the device itself.
A UDI has two parts. The Device Identifier (DI) is the fixed portion — it identifies the labeler (the manufacturer or distributor of record) and the specific device model or version. The Production Identifier (PI) is the variable portion attached to individual units: lot or batch number, serial number, manufacturing date, or expiration date, depending on the device. The DI is submitted to and searchable in the FDA's Global Unique Device Identification Database (GUDID), which launched in December 2013; the public search portal, AccessGUDID, went live in May 2015. The PI is not stored in GUDID itself, though GUDID flags which PI elements a given device's UDI includes.
Where GS1 Fits Into the Barcode
The FDA does not issue UDI numbers itself. It accredits a small number of standards organizations to assign the identifiers, and GS1 is one of three FDA-accredited issuing agencies for UDIs in the United States. In practice, this means the GTIN — the same GS1 identifier used across retail and grocery supply chains — frequently serves as the Device Identifier portion of a medical device's UDI. The barcode symbol most commonly used to carry that data on device packaging is the GS1 DataMatrix, a compact two-dimensional barcode that can encode both the DI and the PI (lot number, expiration date, and so on) in a single scan.
GS1 also supplies the plumbing that gets device data into GUDID in the first place: manufacturers use the Global Data Synchronization Network (GDSN), a GS1-maintained standard, to electronically share standardized product data with the FDA's database rather than submitting it manually. For a practice, none of that submission process is your responsibility — but the barcode it produces is what your receiving desk, your inventory software, and your ordering vendor all have to be able to read correctly.
Why This Matters at the Practice Level, Not Just for Manufacturers
It is tempting to treat UDI compliance as a manufacturer-side regulatory issue that has nothing to do with day-to-day practice operations. That view misses where the actual friction shows up. Scanning a GS1 DataMatrix barcode at receiving lets a practice automate inventory counts, track a device or supply lot from delivery to point of use, and reduce manual data entry errors that otherwise creep into spreadsheets and paper logs. Captured correctly, that same scan feeds directly into electronic health records, creating a record of exactly which lot or serial number was used for which patient — which matters enormously if a manufacturer later issues a recall and the practice needs to identify affected patients quickly rather than guessing from purchase-order history.
The inverse is also true: when a practice's ordering system, inventory platform, and EHR do not consistently capture GTIN/UDI data, the result is duplicate stock nobody can locate, expired lots that get missed, and reconciliation work that falls on whichever staff member has the least time for it. None of this requires a hospital-scale materials-management department to fix — but it does require systems that were actually configured to read and use the barcode data that is already printed on the box.
The Two Halves of a UDI, at a Glance
| Component | What It Identifies | Where It Lives |
|---|---|---|
| Device Identifier (DI) | Labeler and specific device model/version — fixed for that product | Submitted to and searchable in FDA's GUDID / AccessGUDID |
| Production Identifier (PI) | Lot or batch number, serial number, manufacturing date, expiration date — varies by unit | Encoded in the barcode; not stored in GUDID (only flagged as present) |
Getting the Data Flow Right Without an In-House Health-IT Team
Most practices do not have, and do not need, a dedicated health-IT department to handle GS1/UDI compliance — the manufacturers and distributors have already done the labeling work. What a practice does need is confidence that its inventory-management system, its supply-ordering workflow, and its EHR are actually configured to capture and use that barcode data consistently, rather than treating it as decorative. That is typically a vendor-configuration problem: choosing an inventory or ordering platform that reads GS1 DataMatrix symbols correctly, and making sure whoever sets it up understands the difference between a DI and a PI well enough to map the fields properly.
This is exactly the kind of narrow, technical vendor-selection question that benefits from a neutral referral point rather than a sales pitch from a single software vendor. A practice evaluating inventory or supply-ordering systems should ask any prospective vendor directly whether their platform supports GS1 GTIN and UDI capture out of the box, and whether that data flows through to the EHR or stays trapped in a separate inventory tool.
The Bottom Line
GS1's GTIN standard and the FDA's UDI rule were built for very different audiences — one for global supply chains, the other for device safety — but for a medical practice they show up as the same barcode on the same box. Getting comfortable with what that barcode actually encodes, and making sure the systems around it can read it, is a small operational investment that pays off every time a shipment arrives, an order gets placed, or a recall notice lands in the inbox.