← Back to insights

510(k), AccessGUDID or Registration & Listing: Which FDA Device Record Answers the Question?

Use the 510(k) database for a clearance decision, AccessGUDID for public UDI label identity, and Registration & Listing for establishment and listing records.

One medical-device claim routes separately to a 510(k) decision, public UDI identity and establishment listing record
#FDA#510(k)#AccessGUDID#Device Listing

Signals to watch

  • A group claim says FDA approved or registered a device but cites only one public database without naming its record type
  • Device name, 510(k) number, DI, product code, establishment or record date do not align across the cited sources
  • A supplier review, distribution decision or product-data repair has a date and needs a reproducible official-source check

Use the 510(k) Premarket Notification database to verify a substantial-equivalence clearance decision for a named submission. Use AccessGUDID to verify public Unique Device Identification label data for a Device Identifier (DI). Use Establishment Registration & Device Listing to verify the public establishment and listing record. None of the three proves by itself that a device is “FDA approved,” currently marketed by the group poster or compliant with every applicable requirement.

This routing matters to a medical-device market-intelligence analyst monitoring authorised manufacturer, distributor and regulatory-affairs groups. The useful Signal is a claim tied to a supplier review, distribution decision or product-data repair where the cited FDA record answers the wrong question. Seeing it one day late can mean a procurement or risk note has already repeated “approved” from a listing result, or a data-repair vendor has been selected before anyone identifies which record is actually inconsistent.

Definition: three official sources, three record objects

All three sources concern medical devices, but they describe different regulatory objects.

  • A 510(k) is a premarket submission used to demonstrate that a device is substantially equivalent to a legally marketed predicate device under the applicable framework. The public database records the submission and FDA decision.
  • GUDID, the Global Unique Device Identification Database, contains device-identification data submitted by labelers. AccessGUDID is the public interface provided through the National Library of Medicine in partnership with FDA. A DI is the fixed portion of a Unique Device Identifier that identifies a device version or model and labeler.
  • Registration & Listing records establishments registered with FDA and medical devices listed with FDA. It describes establishment and listing relationships, not a premarket approval decision.

The navigation question is therefore not “Which FDA database is authoritative?” It is “Is this claim about a premarket decision, label identity or establishment/listing relationship?”

Route the question before searching a name

Question to answerFirst official sourceFields that anchor the answerBoundary to retain
Did FDA clear this named 510(k) submission?510(k) databaseK number, device name, applicant, product code, decision and decision dateClearance for that submission is not PMA approval or proof about every later configuration
Which public UDI label record describes this version or model?AccessGUDIDPrimary DI, brand/device description, company/labeler and label attributesSubmitted label identity does not establish clearance, establishment registration or current commercial availability
Which establishment is publicly registered and which device is listed?Registration & ListingEstablishment/trade name, owner/operator, registration or FEI number, proprietary/classification name, product code, establishment typeFDA says registration and listing do not denote approval of the establishment or product

This is a question-to-record navigator, not a complete FDA market-status assessment. A device may use another premarket pathway, be exempt from a 510(k), have multiple DIs or involve several establishments. Start with the exact claim; add sources only when the claim requires them.

A 510(k) result answers the premarket-decision question

The FDA 510(k) clearances page explains the premarket-notification route used to support a substantial-equivalence clearance decision.

Use the K number as the strongest public anchor when available. Match the applicant, device name, product code and decision. A similar current brand name does not prove it is the same version or configuration reviewed in an older submission. The database can support “FDA cleared K123456 on this date.” It should not be rewritten as “FDA approved the whole company” or “every model sold under this brand is cleared.”

The distinction is especially important because other pathways—such as Premarket Approval (PMA), De Novo classification or exemptions—have different records. Absence from the 510(k) database alone does not prove a device is unlawfully marketed.

AccessGUDID answers the label-identity question

AccessGUDID is useful when the claim names a UDI, DI, labeler or product version. Compare the primary DI and the labeler-supplied device attributes instead of relying on a commercial name. Packaging levels and later device changes can create additional identifiers or records.

A public GUDID record says that specified device-identification data were submitted for that DI. It does not recreate the FDA review file, show that an establishment registration is current or confirm that every label in the market matches the record. If a group message says “it has a UDI, so it is FDA approved,” the source is being asked to prove a different noun.

Where a 510(k) and AccessGUDID result appear related, preserve both identifiers and the evidence connecting them. Do not join solely because both records contain “Series X.” Product code, company, model details and other available fields may support or weaken the match, but a human still decides whether the records describe the same marketed configuration.

Registration & Listing answers the establishment relationship

The FDA Device Registration and Listing page explains the establishment-registration and device-listing process and its record boundaries.

FDA places a direct warning on the database: registering an establishment, assigning a registration number or listing a device does not denote FDA approval of the establishment or its products. The public database also notes a delay between submitted updates and their public appearance. Record the retrieval date and do not use a temporarily absent public update as final proof that the establishment failed to act.

The database is appropriate for “Is this establishment publicly shown with this role and listing?” It is not the source for “Did FDA clear this 510(k)?” or “Which DI appears on the label?”

Example: “registered, UDI present, FDA approved”

The following is an illustrative composite, not a customer, real device or FDA determination:

“Supplier says the monitor is FDA approved. It is registered and the UDI comes up.”

“The K number on the brochure belongs to an older company name. Review meeting tomorrow.”

Open three separate records. Search the stated K number and preserve its applicant, device, product code, decision and date. Search the exact DI in AccessGUDID and preserve the labeler and model attributes. Search the relevant establishment and listing using legal names and identifiers. Then record whether the public fields support the claimed connection.

Several facts remain unknown: whether the brochure names the exact marketed configuration, whether corporate succession connects the older applicant to the current labeler, whether the establishment role is current, and whether another premarket record applies. Until those joins are evidenced, the accurate note is “three records were located but their relationship needs verification,” not “FDA approved the supplier’s monitor.”

Key facts that belong in the source note

  • A 510(k) supports the named substantial-equivalence clearance decision; call it cleared, not PMA-approved.
  • AccessGUDID provides public device-identification data submitted to GUDID; a DI is an identity anchor, not a universal market authorisation.
  • Registration & Listing records establishments and device listings, and FDA expressly says those records do not denote approval.
  • Public database dates and update cadence matter. Save the retrieval date and exact displayed fields.
  • Name similarity alone is a weak join. Preserve K number, DI, product code and establishment identifiers wherever available.
  • No single source proves current manufacturing, distribution authority, complete labelling, quality-system compliance or satisfaction of every postmarket duty.

The FDA import-status source-routing article applies the same principle to Import Alerts, refusals and entry-level ITACS states. For a broader method when a screenshot loses its original database link, use the official-source ladder. Cyber-device premarket evidence is a different record set explained in the section 524B evidence-chain article.

When the source mismatch becomes a useful Signal

A reproducible source mismatch deserves review when the exact device claim and decision date are known, at least one stable identifier is available, and the missing join blocks supplier qualification, distribution or data repair. A generic question about whether a company is “FDA registered” remains an incomplete search request.

TOP Prospect can find and group these fragments in Telegram groups a user deliberately connects and is authorised to access, preserve their wording, source and time, remove duplicates and explain why a mismatch deserves human source review. It cannot identify a device from an ambiguous name, access non-public FDA records, decide market legality, verify corporate succession, contact the poster or certify approval.

If authorised-group discovery supports the analyst’s workflow, review TOP Prospect plans. The tool can surface the record conflict; the analyst must make each claim no broader than the official source supporting it.

FAQ

Does a 510(k) record mean FDA approved the device?

A 510(k) record supports a substantial-equivalence clearance decision for the named submission. FDA distinguishes 510(k) clearance from premarket approval, so describe the decision accurately.

What does AccessGUDID verify?

AccessGUDID exposes public device-identification data submitted to GUDID, including the Device Identifier and labeler-supplied attributes. It does not by itself prove a 510(k) clearance, current establishment registration or complete market compliance.

Does FDA establishment registration or device listing denote approval?

No. FDA’s public Registration & Listing database expressly states that establishment registration, assignment of a registration number and device listing do not denote FDA approval of the establishment or its products.

What identifiers should be preserved when joining the three sources?

Preserve the exact device and proprietary names, 510(k) number, product code, applicant, decision date, primary Device Identifier, labeler, establishment and owner/operator identifiers, listing fields and retrieval date. Do not join on a shortened brand name alone.

Frequently asked questions

Does a 510(k) record mean FDA approved the device?

A 510(k) record supports a substantial-equivalence clearance decision for the named submission. FDA distinguishes 510(k) clearance from premarket approval, so describe the decision accurately.

What does AccessGUDID verify?

AccessGUDID exposes public device-identification data submitted to GUDID, including the Device Identifier and labeler-supplied attributes. It does not by itself prove a 510(k) clearance, current establishment registration or complete market compliance.

Does FDA establishment registration or device listing denote approval?

No. FDA’s public Registration & Listing database expressly states that establishment registration, assignment of a registration number and device listing do not denote FDA approval of the establishment or its products.

What identifiers should be preserved when joining the three sources?

Preserve the exact device and proprietary names, 510(k) number, product code, applicant, decision date, primary Device Identifier, labeler, establishment and owner/operator identifiers, listing fields and retrieval date. Do not join on a shortened brand name alone.

Sources and further reading

RESEARCH & DEFINITIONS

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.

Open the methodology and core definitions

START WITH ONE MONITORED GROUP

Try the workflow free for seven days.

Open the product, connect one authorized group, and describe the Signal you want to find. If you need help choosing the scope, ask us on Telegram.

Back to homepage