The most direct method is to use the FDA Premarket Approval database and set the Supplement Type field to “Originals Only” [1]. That filter isolates the parent applications rather than later submissions filed under them. A supplement record does not itself always display the originating PMA number in a prominent place, so the workflow often runs the other way: identify the approved device or applicant, retrieve the original application, confirm its product code and approval order, then verify which supplements attach to that number [3]. The openFDA monthly dataset provides an alternative download route when a records-level query is needed [4]. The central challenge is less about finding a search page and more about proving that the record you retrieve is the legal parent application, not a similarly named filing.
Why the filter choice matters more than the keyword
The PMA search page offers separate fields for Applicant, Device, Product Code, PMA Number, Docket Number, Decision Date, Advisory Committee, and Supplement Type [3]. The Supplement Type options include Originals Only, Normal 180 Day Track, Panel Track, Real Time Process, 30 Day Notice, and other submission categories [1]. Choosing “Originals Only” prevents the database from returning every panel-track supplement or 30-day notice associated with a device family, which is important when the same trade name or generic name appears across years of filings [1][3].
A consequences-aware reading of the record is still required. An original PMA can itself be supplemented many times, and those supplements are separate submissions with their own review tracks [6]. FDA states that PMA supplements are required for changes that affect safety and effectiveness, except modifications to manufacturing procedures or methods, which go through a different mechanism [6]. A researcher who finds a record marked “Normal 180 Day Track” has likely found a supplement, not the parent, even though the device name matches the one in the original filing [3].
Reading the record fields to verify the parent filing
Each retrieved PMA record contains specific fields: the application number, the applicant, the device trade name and generic name, product codes, the date FDA received the application, the decision date, the docket number, advisory committee, clinical trial links, expedited review flag, combination product flag, and an approval order statement [3]. The approval order statement is the most reliable field for confirming the approved use, because it is FDA’s own wording rather than a vendor summary [3]. Product codes, which are three-letter codes, allow reuse in new searches to find related devices and associated submissions [3].
The original application number is the stable identifier to record once confirmed. FDA’s FAQ describes situations where a new owner must obtain a complete copy of the PMA, including amendments, supplements, and reports, which shows that the PMA number functions as a container for the full submission history rather than a single dated document [5]. A change in manufacturing or sterilization site and certain changes to device labeling or packaging require prior FDA approval through a PMA supplement, so tracing the original number is also the route to assembling the complete regulatory record [5].
Suggested lookup template for original PMA confirmation
The following is a proposed internal worksheet format, not a claim that all fields are equally available in every record. Fields to capture when confirming a parent application include: original PMA number, applicant, device trade name and generic name, product code, docket number, received date, decision date, advisory committee if listed, and the exact approval order statement text [1][3]. In the workflow column, the review step is to set Supplement Type to “Originals Only” and then verify that the retrieved record is not a 180-day or 30-day supplement by checking the supplement type and decision date range [1][3].
For cases where the original number is known from a supplement label, enter the PMA number in the search field and retrieve the associated record directly, then cross-check the applicant and device against the supplement’s stated parent [1][3]. Where the original number is not visible, the alternative is to search by product code and applicant with Originals Only, then narrow using decision dates [3]. The collected fields form a chain of evidence: number, applicant, device, dates, and approval order.
A repeatable retrieval sequence for supply-chain and regulatory staff
A defensible workflow begins with the FDA database rather than a manufacturer’s public materials page. Start by entering the product code or the applicant name and setting Supplement Type to “Originals Only,” then sort results by decision date to narrow the list [1][3]. Once the candidate record appears, confirm the received and decision dates, read the approval order statement, and record the original PMA number from the application number field [3]. The generic name and product code should match the device under review before any claim of traceability is made.
The search page does not resolve ambiguity about which record is the parent when a manufacturer holds multiple similar original applications. In that case, the docket number and notice date offer cross-reference points, and the advisory committee field can distinguish device classes reviewed under different panels [1][3]. Because the database is a regulatory decision record, it does not show price, stock, availability, or endorsement status, and it is not a substitute for the underlying summary of safety and effectiveness data [3].
What the public database will not show
The public interface is not a complete document repository. Before FDA approves or disapproves a pending PMA, the agency will not disclose the existence of the application unless it has already been publicly acknowledged, and data in the file are not available for public disclosure during that period [5]. Even after approval, the available material is limited to releasable information after deletion of trade secrets, confidential commercial or financial information, and clearly unwarranted personal privacy material [5]. A public record confirms decision dates and administrative facts; it does not provide the raw application file.
Written requests for safety and effectiveness summaries can be made to the Dockets Management Branch, and the agency discontinued individual PMA approval publication in the Federal Register as of January 30, 1998 [2]. Monthly downloadable files of releasable PMAs are typically replaced on the fifth of each month, according to FDA’s approval page [6]. Anyone using openFDA should treat that API as a search and analytics tool, not as a basis for medical care decisions or as a complete device record [4].
A documented example of confirming one original
CASRAI’s public guide uses FDA record P160013 as an illustration, showing an application received on 04/28/2016 and a decision rendered on 03/22/2018, along with a docket reference and an NCT link for a registered clinical study [3]. That record structure demonstrates how the original application number sits at the top of the record while the received and decision dates anchor the filing timeline [3]. The example also shows that a single record can link to clinical trial registration, which is useful when a reviewer needs to connect the approval to trial documents [3].
The same guide confirms that the approval order statement, not marketing copy, is the field to read for the approved use [3]. For a reviewer comparing a supplement against its original, the practical check is whether the supplement’s device, product code, and applicant match the parent record and whether the supplement type is consistent with a change that would require a supplement filing [3][6].
Sources & references
- Premarket Approval (PMA) - accessdata.fda.gov · www.accessdata.fda.gov
- PMA Approvals | FDA · fda.gov
- PMA Database: Search FDA Premarket Approvals — CASRAI · casrai.org
- About PMA · open.fda.gov
- PMA Frequently Asked Questions | FDA · www.fda.gov
- PMA Approvals | FDA · www.fda.gov
- 21 CFR Subpart B—Premarket Approval Application (PMA) · www.ecfr.gov
- 21 CFR § 814.20 Application. · www.ecfr.gov