Searching AccessGUDID by device identifier begins with separating the DI from the rest of the unique device identifier. AccessGUDID documentation advises that when a full UDI includes application identifiers or concatenated production data, the searcher should submit only the DI portion, as in searching for 51022222233336 from a longer GS1 string [1]. The reason sits in the database design: GUDID contains only the device identifier portion, which FDA guidance describes as the key used to obtain device information, while production identifiers are not submitted to or stored in the database [4][5]. The practical task is therefore not simply typing a barcode into a box; it is recognizing which characters constitute the DI, handling format-specific edge cases, and verifying that the returned record matches the physical device in hand. This guide presents that workflow using the current National Library of Medicine interface documentation and the FDA GUDID guidance issued December 17, 2024 [4][5].
Separate the DI from the Full UDI
The first decision point is format recognition. AccessGUDID help gives three worked examples. A UDI that looks like (01) 51022222233336 (11)141231(17)150707(10)A213B1(21)1234 should be searched using only 51022222233336 because the parenthetical application identifiers and later fields represent production data [1]. A concatenated HIBCC-style example, +H123PARTNO1234567890120 /$$420020216LOT123456789012345/SXYZ4567890123 45678/16D20130202C, similarly requires searching for H123PARTNO1234567890120 only [1]. The documentation presents these as label-instruction examples rather than universal parsing rules, so labelers that use other issuing agencies may require consulting the applicable UDI format source.
A further edge case concerns numeric-only DIs. The help page instructs that a device identifier printed as 614141987658 should have an asterisk added to the start before searching: *614141987658 [1]. The source states this without explaining the underlying search behavior, so treat the wildcard as a documented input convention rather than a general rule for all numeric identifiers. FDA guidance reinforces that production identifiers remain outside the GUDID, with the database retaining only flags that indicate which PI attributes appear on the label [4][5]. For a researcher receiving only a scanned UDI, the correct first step is to strip conditionally variable segments and retain the static device identifier.
Run the Basic Search and Read the Limit
Basic Search accepts any device attribute, including device identifier, company name, brand name, common name, and version or model, with a minimum term length of three alphabetic or numeric characters [1]. The search bar appears on any page for desktop users, while mobile users reach it from the home page or a magnifying glass icon [1]. A search returns no more than 1,000 records [1]. That ceiling matters when a short or generic DI fragment matches many records; the interface does not, in the retrieved documentation, provide a mechanism for paging beyond the first thousand results.
Boolean and truncation syntax extends the basic workflow. The complex query guide documents that stent OR heart finds devices containing either word, stent AND heart requires both, and plain terms separated by spaces default to OR behavior [7]. Quotation marks create an exact phrase, and the operators OR, AND, and NOT must be capitalized [7]. Wildcards are documented as having accuracy only when the attached term contains three or more characters [7]. These operators are about terms inside device identifier records, but the help material does not state whether DI searches support the same Boolean combinations at the field level, so users should test rather than assume equivalence.
A Suggested Workflow for an Unlabeled Implant Log
Suppose a supply chain analyst is given a concatenated string beginning with + and containing part numbers and lot segments. One defensible suggestion, based on the AccessGUDID format examples, is to isolate the initial alphanumeric DI segment before the production fields, submit only that portion in basic search, and record the result count [1]. If the returned record identifies a device class, product code, MRI safety status, or combination product flag, those values should be compared to the device record rather than treated as clinical conclusions [2][3]. When the DI is purely numeric and returns no result, the analyst can retry with a leading asterisk as documented [1].
If ambiguity remains, the analyst could repeat the search in Advanced Search using a company name in the builder, keeping in mind that conditionally populated fields may exclude records from the query pool [6]. For single-record verification, the Device Lookup API with di= can return a public device record key that supports later audit [2][3]. GUDID does not contain production identifiers, so expiration or lot values embedded in the original string cannot be checked against the database [4][5]. The workflow should end with a note recording the issuing agency and the parsing decision, since the published help pages do not supply a universal extraction grammar.
Use Advanced Search for Constrained Queries
Advanced Search offers a query builder with per-field controls for matching all terms, exact phrases, terms that contain, terms that begin with, or terms that end with a value, combined by AND, OR, or NOT [6]. The page states that JavaScript is required for the tool [6]. Asterisk-marked fields are optional or conditionally required, and the documentation warns that not all device records hold values for those fields, meaning a search based on them will not query all AccessGUDID records [6]. This is a material limitation: a missing optional field is invisible to the search rather than simply empty in the result set.
The dagger-marked fields are generated by the National Library of Medicine from information in the device record and are not explicitly present in the device data [6]. An implantable filter, for example, returns devices whose FDA product code is associated with implantable devices, systems, and accessories [6]. For DI-driven research, this search mode is most useful when the DI is partial, poorly segmented, or needs to be combined with a company name to disambiguate. The documentation does not show a dedicated exact-DI field, so users may still need to compare raw basic search output against advanced query results.
Retrieve and Verify the Device Record
A submitted query returns a device record containing data elements required by 21 CFR 830.310 plus ancillary administrative data [4]. GUDID contains only the static device identifier; PI flags indicate whether lot or batch, serial number, expiration date, or manufacturing date appear on the label [4][5]. The FDA public page states that AccessGUDID offers the most recent information submitted to FDA and is updated daily [8]. No account is required to search or download the data [8]. For a researcher, the practical verification step is checking that identifier type, issuing agency, brand name, version or model, and company name match the physical product.
The Device Lookup API provides a programmatic route for single-record retrieval. A GET request to /devices/lookup requires either a di, a udi, or a record_key, and returns the record in JSON or XML [2][3]. The documented example uses /api/v2/devices/lookup.json?di=08717648200274 and returns publicDeviceRecordKey, publicVersionStatus, deviceRecordStatus, identifiers, brandName, versionModelNumber, companyName, deviceDescription, MRISafetyStatus, productCode, deviceName, and deviceClass [2][3]. A UDI request percent-encodes the full string and parses it through the Parse UDI API, returning normalized manufacturing and expiration dates, lot, serial, and issuing agency in headers [2][3].
Sources & references
- Basic Search - AccessGUDID - NIH · accessgudid.nlm.nih.gov
- AccessGUDID - Device Lookup API · accessgudid.nlm.nih.gov
- Device Lookup API - AccessGUDID - NIH · accessgudid.nlm.nih.gov
- Global Unique Device Identification Database (GUDID) - Guidance for Industry and Food and Drug Administration Staff · www.fda.gov
- Global Unique Device Identification Database (GUDID) | FDA · www.fda.gov
- Advanced Search - AccessGUDID - NIH · accessgudid.nlm.nih.gov
- AccessGUDID - Manually Writing Complex Queries · accessgudid.nlm.nih.gov
- AccessGUDID: Device Identification Information · U.S. Food and Drug Administration