Searching the FDA 510(k) database begins with identifying how your device is classified, because the product code is the most dependable filter for finding comparable cleared predicates. FDA guidance states that searching by product code is usually the most effective approach, leaving other fields blank [1]. The Premarket Notification database at accessdata.fda.gov accepts queries by 510(k) number, applicant name, device name, product code, panel, and other criteria [2]. The openFDA API exposes much of the same information in a machine-readable format, with updates occurring monthly [5]. Each pathway retrieves original application information, not later ownership changes or marketing status, so users should not expect a single search to answer every commercial or regulatory question.
Start with the Product Code Classification Database
Before entering the 510(k) database, FDA recommends locating the product code that corresponds to your device type. The Product Code Classification Database supplies the classification panel, common name, product code, and CFR regulation when a device type has received final classification [1]. For example, an arthroscope falls under 21 CFR 888.1100, and that citation plus the associated product code becomes the anchor for subsequent searches [1]. Skipping this step often produces scattered results across panels and device families.
The classification record also helps separate device categories that share a generic name but differ in intended use or technology. FDA notes that useful predicate information includes traded names, manufacturers, marketing status, 510(k) numbers, and classification details [1]. Collecting these identifiers in one place reduces the need to guess at spelling variants or applicant names later. A firm claiming a preamendments device must demonstrate that the device was labeled, promoted, and distributed in interstate commerce for an unchanged intended use [1].
Querying the Premarket Notification Database
The main web search form, titled 510(k) Premarket Notification, offers fields for 510(k) number, application type, product code, center, applicant name, device name, panel, third-party review status, decision, decision date range, and sort order [2]. FDA advises completing only one box per search, with product code preferred for predicate research [1]. Manufacturer-name searches may require testing hyphen or space combinations because formatting differences can return no records even when the applicant exists in the database [1].
Results display a structured record that includes device classification name, regulation number, 510(k) number, device name, applicant, contact, product code, date received, decision date, decision, advisory committees, and a summary or statement indicator [4]. A SUMMARY entry means safety and effectiveness information is available from FDA; a STATEMENT entry means that information may be obtained from the 510(k) applicant [4]. The database also identifies traditional, special, and abbreviated submission types, along with rescissions and whether a third party reviewed the file [4].
A Minimal Working Search Sequence
For a first pass, open the Product Code Classification Database, confirm the code for your device, then enter only that code in the 510(k) Premarket Notification form [1][2]. If no records appear, try the applicant name with and without spaces or hyphens before changing device-name terms [1]. For bulk retrieval, issue an openFDA query such as api.fda.gov/device/510k.json?search=product_code:YOURCODE&limit=100, adjusting the field name against the searchable-fields list [3]. Record the query date because openFDA updates monthly, and note whether each result is a SUMMARY or STATEMENT before requesting further information [4][5].
Using the openFDA 510(k) Endpoint
The openFDA API offers an alternative for researchers who need to query many records or integrate results into an internal system. A query begins with the base endpoint api.fda.gov/device/510k.json, and searches use the syntax search=field:term [3]. Unless a limit parameter is specified, the API returns one matching record; the maximum permitted limit for a single call is 1000 [3]. Users can call the API from a web browser without a key, though openFDA recommends obtaining a key for regular use [3].
The dataset covers 510(k) clearances from 1976 to the present and is refreshed monthly [5]. openFDA annotates the original records with harmonized fields and converts the data to JSON [5]. The endpoint includes administrative and tracking information, such as receipt and decision dates, and details about the original sponsors of premarket notification applications [5]. This is the same original-applicant limitation present in the web database: ownership changes after clearance are not reflected [1].
A Concrete Predicate Search Example
Consider a firm preparing a 510(k) for an arthroscopic visualization system. The first step is to search the Product Code Classification Database and confirm the product code tied to 21 CFR 888.1100 [1]. The firm would then enter that product code alone in the Premarket Notification database and review cleared devices with the same code, noting decision dates and whether each record shows a SUMMARY or STATEMENT [4]. FDA guidance describes this product-code-first method as the usual best practice [1].
A parallel openFDA query might use the same product-code field with a limit parameter to retrieve a larger set of records in JSON for comparison [3]. The firm could then group results by applicant and decision date, but should not treat a recent clearance as confirmation of current market availability. FDA states that an applicant may claim substantial equivalence to a device that is no longer being marketed in the U.S., which means database results are a starting point for regulatory analysis, not a live commercial inventory [1].
Evidence Limitations and Data Boundaries
The 510(k) database contains original application information only, including the original applicant name and original trade name [1]. A device that has changed ownership or been renamed may therefore appear under identifiers that no longer match current labeling. FDA also notes that hyphens or spaces in applicant names can alter search results, so negative results do not prove that no relevant clearance exists [1]. Users should run multiple field combinations and document which searches produced each record.
The openFDA platform carries explicit limits on responsible use. The terms state that openFDA should not be relied on to make decisions regarding medical care, and that access may be restricted under the Terms of Service [3]. The same medical-care disclaimer appears on the dataset overview [5]. Because the data are updated monthly, a clearance posted to the web database during the current interval may not yet appear in the API [5]. These constraints make the API suitable for research and monitoring, but not for time-critical clinical or legal determinations.
Sources & references
- How to Find and Effectively Use Predicate Devices | FDA · www.fda.gov
- 510(k) Premarket Notification · www.accessdata.fda.gov
- How to use the API · open.fda.gov
- Search the Releasable 510(k) Database | FDA · www.fda.gov
- Device 510(k) overview · U.S. Food and Drug Administration
- 510(k) Clearances | FDA · www.fda.gov
- openFDA · open.fda.gov