The Label Changed, but Which GUDID Field Should Move?
Scope a GUDID correction by comparing the published primary DI record with controlled label evidence, packaging levels, version/model and production-identifier flags.
Signals to watch
- AccessGUDID displays a company, brand or version/model that does not match the currently controlled device label
- A team asks to replace the primary DI without explaining whether the device is a new version or model
- A package DI or production-identifier flag is missing while the source label and account authority remain unavailable
Do not begin a GUDID correction by typing over the public field. Freeze the current Global Unique Device Identification Database record, identify its primary Device Identifier (DI), and compare every proposed value with the controlled device label and package configuration. Then decide whether the mismatch is an editable data correction, evidence of a new device version or model that needs a new DI, or a problem that requires an authorised FDA help-desk or account action.
This is the actionable intake for a medical-device UDI data-service lead monitoring authorised regulatory-affairs, label-operations, master-data and distributor Telegram groups. A day late can leave a catalogue, distributor check or launch file using conflicting identities. The message is a possible service request, not proof that the public record is wrong.
Save the public record before asking what is wrong
An illustrative request might read:
“AccessGUDID has old model info and the carton DI is missing. Label was updated. Need fixed before distributor review.”
It does not identify the labeler, primary DI, issuing agency, device version/model, carton configuration, publication state, controlled-label revision, effective date or submitter authority. “Old” may describe a stale public field, a new device version, an old label still in distribution or a search result for a different package.
Export or capture the exact AccessGUDID record with retrieval time. Record the primary DI, company or labeler name, brand and device description, version/model, commercial-distribution status, package DIs, production-identifier flags and any public update date. Preserve the URL and search query so another reviewer can reproduce the starting point.
Build a before-and-after row for one field
Do not open with “update all fields.” Create one row per claimed mismatch:
| Field | Published value | Proposed value | Controlled source | Effective date | Change decision |
|---|---|---|---|---|---|
| Version/model | Series A | Series A2 | Approved label revision | Unknown | Test whether this is a new version/model requiring a new DI |
| Package DI | No carton level shown | DI not yet supplied | Carton artwork and packaging specification | Unknown | Verify package configuration and identifier assignment |
| Serial-number flag | No | Yes | Primary-label UDI format | Unknown | Correct the flag; do not submit serial-number values |
The entries are examples, not real device data. A usable row names the document owner and revision, not merely a screenshot forwarded in a group.
GUDID holds the DI portion of the Unique Device Identifier and labeler-supplied device attributes. It does not store individual production-identifier values such as actual lot, serial, manufacture or expiration data. It records whether specified production identifiers appear on the label. A request to “upload all serials to GUDID” therefore describes the wrong data object.
Protect the primary DI as the identity anchor
Under 21 CFR Part 830, a DI identifies a specific version or model of a device and its labeler. Section 830.50 requires a new DI when a change results in a new version or model. Each higher package level also generally has its own DI, subject to the rule’s exceptions.
That means a changed identifier is not an ordinary spelling correction. First ask whether the label shows the wrong DI, whether GUDID displays a DI different from the controlled label, or whether the product itself became a new version/model. Do not transform the record for one device identity into another simply to make a search result look current.
The correction receipt should state one of three results:
- the primary DI stays and specified editable attributes are corrected from controlled evidence;
- a new version/model or packaging configuration requires a new DI and connected record work; or
- the team lacks account authority or the requested system action and must use an authorised escalation route.
Do not claim that every field can or cannot be edited without checking the current GUDID account interface and FDA instructions. Publication state and the nature of the field matter.
Reconcile packaging as a hierarchy, not a list
Draw the packaging relationship from the base device to each box, carton or case that carries a UDI. For each level, capture quantity, package type, DI, containing DI and controlled artwork. A missing carton result may be a submission omission, an incorrect relationship, a search issue or evidence that the requested level was never assigned.
Then compare device-count and package-status fields with the label. Do not infer a packaging relationship because two DIs share the same brand. The labeler’s controlled packaging specification and identifier assignment are the native evidence.
Publication, label control and account authority close the job
A clean correction file has three owners. Regulatory or quality owns the device and change assessment. Label operations owns approved artwork and effective dates. The authorised GUDID account role owns the submission. The service provider should not receive borrowed credentials or assume the message author can approve the change.
After an authorised update, retrieve the public record again and compare it with the approved before-and-after rows. Preserve submission or support references, publication time and remaining discrepancies. AccessGUDID is the public verification surface; it is not proof of FDA clearance, current establishment registration or complete compliance.
Use the EUDAMED, GUDID and MHRA source router when the target market or database is still unclear. The FDA device-record navigator separates AccessGUDID data from 510(k) and establishment-listing claims. The pricing page covers TOP Prospect subscriptions, not GUDID submission fees or regulatory services.
TOP Prospect can surface and deduplicate relevant fragments from authorised Telegram groups connected by the user, preserving original text, source, time and review context. Saving a matching target only stores configuration and does not automatically run or create candidates. The product cannot access GUDID accounts, read controlled labels, assign DIs, submit corrections or verify FDA compliance.
Key facts
- GUDID contains DI data and labeler-supplied device attributes, not unit-level production-identifier values.
- The primary DI identifies a device version or model and labeler; a new version or model requires a new DI.
- Higher packaging levels generally need their own DIs and explicit relationships.
- A correction request needs a field-level current value, proposed value, controlled source, effective date and authorised owner.
- AccessGUDID verifies the published UDI record, not FDA clearance or establishment registration.
- Published status and field type must be checked before promising an edit route.
FAQ
Does GUDID store serial numbers, lot numbers or expiration dates?
No. It stores DI data and indicates which production-identifier types appear on the label, but it does not store the actual unit or lot values.
Can a published primary DI simply be edited into another DI?
Treat the primary DI as the record’s identity anchor. If the identifier or device version/model changed, assess whether a new DI and record are required instead of overwriting the identity.
Does an AccessGUDID record prove FDA clearance or approval?
No. It is a public UDI label-data record. Clearance, approval, establishment registration and other compliance evidence come from separate sources.
What evidence should accompany a correction request?
The current record, exact field, proposed value, controlled label or package evidence, effective date, account authority and documented new-DI assessment.
Editorial review completed 21 August 2026 against FDA’s current GUDID and UDI pages, AccessGUDID and 21 CFR Part 830. The labeler and qualified regulatory and quality reviewers must approve actual identifier and submission decisions.
Frequently asked questions
Does GUDID store serial numbers, lot numbers or expiration dates?
GUDID contains Device Identifier data and flags indicating which production identifiers appear on the label; it does not contain the production-identifier values for individual units or lots.
Can a published primary DI simply be edited into another DI?
Treat the published primary DI as the identity anchor for that device version or model. If the identifier or version/model changed, determine whether a new DI and record are required rather than rewriting one device identity into another.
Does an AccessGUDID record prove FDA clearance or approval?
No. It displays public UDI label data submitted to GUDID. Premarket decisions, establishment registration and complete market compliance belong to other evidence.
What evidence should accompany a correction request?
Preserve the current record, exact field, proposed value, controlled label or packaging evidence, effective date, labeler account authority and the reason the change does or does not require a new DI.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
