FDA's UDI system is a backstop, not a choice

This blog has already covered how 21 CFR 830.20 pairs a device identifier with a production identifier on the label, without covering where the device identifier itself comes from. Part 830 answers that with a structure most UDI files skip past entirely: FDA doesn't run the system that issues device identifiers — three accredited private organizations do — and FDA's own identifier-issuing role only switches on when that system has a gap, not as a fourth option sitting alongside the other three.

Three agencies, one accreditation standard

21 CFR 830.100 doesn't ask an applicant to build a numbering scheme to FDA's own specification; it asks the applicant to already be running a system capable of assigning device identifiers that meet Part 830's own requirements, and to be accredited by FDA against that standard before issuing a single one. Three organizations currently hold that accreditation: GS1, based in New Jersey; HIBCC, the Health Industry Business Communications Council, based in Arizona; and ICCBBA, the International Council for Commonality in Blood Banking Automation, based in California. A labeler doesn't apply to FDA for a device identifier at all — it applies to one of these three, and the choice among them is the labeler's own, not an assignment FDA makes on the labeler's behalf.

Accreditation is a file, not a formality

21 CFR 830.110 routes an applicant's initial request through CDRH itself — a notification of intent to seek accreditation, followed by an application FDA reviews against 830.100's criteria. Accreditation isn't indefinite once granted, either: an accredited agency has to notify FDA of its intent to renew at least nine months before its current accreditation expires. A UDI program that treats “accredited” as a permanent label, checked once and never revisited, has missed that the agency behind a device's own identifiers is carrying a renewal clock of its own.

What staying accredited requires

21 CFR 830.120 sets four ongoing duties an issuing agency has to keep meeting, not just clear once at the application stage: operate a device-identifier assignment system that continues to meet 830.20's own requirements; make information about that system publicly available; maintain a list of the labelers using its system and give FDA an electronic copy of that list by December 31 of every year; and, on request, tell FDA which agency's system a specific labeler is using. That last duty is why FDA can always trace a given device identifier back to the labeler behind it, even though FDA never issued the identifier itself — the accountability is built into the accreditation, not into the numbering.

Accreditation can end, on four named grounds

21 CFR 830.130 lets FDA suspend or revoke an issuing agency's accreditation, after notice and an opportunity for an informal hearing, on grounds the rule names specifically: misrepresentation or a failure to disclose required information in obtaining accreditation in the first place; a failure to fulfill the 830.120 responsibilities above; a failure to protect against conflicts of interest that could compromise a fair, neutral identifier system; or engaging in anticompetitive activity to restrain trade. None of those four grounds is a judgment call FDA makes about the numbers an agency assigns — each one is about whether the agency is still running the accredited system the way accreditation required.

FDA's own role is the exception, not a fourth agency

21 CFR 830.200 gives FDA its own authority to act as an issuing agency, and it names exactly two circumstances that switch it on: any period during which no accredited issuing agency exists at all, or a determination that the fees required by every accredited agency would substantially and adversely affect a significant number of small businesses. Neither condition is something a labeler gets to decide for itself by preferring FDA's system over an accredited agency's — 830.210 sets its own eligibility rule for who can actually use FDA's system, separate from the three agencies' own enrollment terms. And FDA's own service isn't permanent by default either: 830.220 lets FDA end it once the conditions that justified starting no longer hold and ending the service wouldn't likely bring those conditions back. Ending the service doesn't strand a device identifier already assigned under it — a labeler can keep using that identifier until 830.50 requires a new one, the same continuity rule that protects a device identifier issued under any of the three accredited systems.

Where this meets the file

A UDI system-selection record needs to name which of the four possible sources issued a given device identifier — GS1, HIBCC, ICCBBA, or FDA's own fallback system under 830.200 — and track that source's accreditation or eligibility status as its own field, rather than treating “UDI-compliant” as a single fact that never needs revisiting. A UDI governance worksheet built around that structure is previewed in the launch catalog. If your program tracks issuing-agency status differently, the shelf takes that correction directly.