Skip to main content
[email protected]
Menu
Language
Appearance

UDI and DME Billing: Why Device Identifiers Aren’t (Yet) on Your Medicare Claims

ATAzHeC Technology Council
August 15, 2026
5min read
WhatsAppEmail

Arizona practices that bill for durable medical equipment already juggle HCPCS codes, standard written orders, and payer-specific documentation rules. A newer question is starting to surface in billing departments: does the FDA’s Unique Device Identification (UDI) system have anything to do with how a claim gets paid? The short answer is not yet — but the direction of travel matters for any practice that dispenses or bills for devices, and getting ahead of it beats scrambling later.

This is worth untangling carefully, because UDI, the FDA’s device database, and Medicare’s claim requirements are three separate systems that are only starting to connect.

What the GUDID Actually Tracks

The FDA’s Global Unique Device Identification Database, commonly called GUDID (pronounced "Good ID"), is a central catalog the FDA administers to store identifying information for medical devices that carry a UDI. It exists to improve patient safety, streamline recalls, and support post-market surveillance — not to process payment.

Specifically, GUDID stores the Device Identifier (DI) portion of a device’s UDI: a mandatory, fixed segment that identifies the device’s labeler and its specific version or model. The DI is effectively the lookup key into the database. GUDID does not store the Production Identifier (PI) — the variable data like lot number, serial number, or expiration date that appears on a device’s label — but it does flag which PI attributes are present so a device can be matched correctly during a recall. The public-facing search tool, AccessGUDID, lets anyone look up a device identifier and see the device name, labeler, and related premarket submission numbers. For a practice trying to confirm a recalled lot or verify a device’s registration before ordering it, AccessGUDID is the practical entry point.

Why UDI Isn’t Required on DME Claims Today

Here is the part that surprises billing staff: even though UDI has been mandatory on device labels for years, there is currently no explicit requirement to include a device’s UDI on a Medicare DME claim. Current DME claim requirements center on the standard written order (SWO) from the treating practitioner, which must include the beneficiary’s name or Medicare Beneficiary Identifier, the order date, a general description of the item (which can be satisfied by a plain description, a HCPCS code, a HCPCS code narrative, or a brand name and model number), and the practitioner’s name or NPI with signature. A brand name or model number can stand in for a fuller device description, but nothing in that requirement set currently calls for the UDI itself.

That gap is exactly why industry groups, the HHS Office of Inspector General, and the FDA have been pushing CMS to bring UDI data into the claims pipeline. The argument is straightforward: linking reimbursement to a specific device, rather than just a device category, would improve cost transparency, reduce overpayments, and make it considerably harder to bill Medicare or Medicaid twice for the same physical item.

Where the Rulemaking Is Actually Heading

Movement is happening, but it is narrower than the headlines about "UDI on claims" sometimes suggest. In April 2026, CMS issued a proposed rule — developed with the FDA — that would establish a UDI measure under the Medicare Promoting Interoperability Program. As proposed, it would require eligible hospitals to attest whether they used certified electronic health record technology to capture the complete UDI for implantable devices. That is a hospital-side EHR attestation requirement for implantables, not a DME billing form requirement, and the distinction matters for any practice trying to figure out what actually applies to it right now.

Still, CMS’s broader posture is that reliance on UDI data is expected to grow, particularly for Class II devices, as a fraud-and-abuse control. A device identifier that ties a specific claim to a specific physical unit closes a loophole that generic HCPCS coding leaves open.

What This Means for a Practice’s Billing Workflow Today

Even without a hard requirement, there are reasons to build UDI awareness into billing operations now rather than waiting for a mandate:

Data pointRequired on a DME claim today?Where it comes from
Beneficiary name / MBIYesStandard written order
HCPCS code or general item descriptionYesStandard written order
Practitioner name/NPI and signatureYesStandard written order
Brand name or model numberOptional, can satisfy the description requirementStandard written order
Full UDI (device identifier)Not currently required on DME claimsAccessGUDID / device packaging

The practical steps worth taking: keep a record of the UDI or device identifier for higher-value or recall-prone equipment at the point of dispensing, even if the claim form doesn’t ask for it, and know how to search AccessGUDID quickly if a recall notice comes through. A practice that already has this habit in place won’t be scrambling if CMS finalizes a broader UDI claims requirement, and it also has a faster answer ready the next time a patient or a payer asks whether a specific device was ever subject to a recall.

The Bigger Picture

UDI, GUDID, and DME billing sit at an intersection that most practices never think about until a recall notice or an audit forces the issue. Getting the documentation habits right early — and knowing which vendors, whether for billing operations or health-IT infrastructure, actually understand this intersection — is a small operational investment that pays off the day a device identifier question actually lands on someone’s desk. As CMS continues to formalize UDI’s role in claims and quality reporting, practices that treat device identification as routine documentation, not an afterthought, will have the easier transition.