The FDA Premarket Approval (PMA) database is the primary public record for Class III medical devices that received marketing authorization through the most stringent review pathway. You can search it through the CDRH web interface at accessdata.fda.gov, query it programmatically through the openFDA device PMA API, or download the monthly pma.zip file. Each method exposes different fields and update frequencies, so the right approach depends on whether you need a single approval order, a batch of decisions, or longitudinal tracking. This guide explains the named workflow, the technical decision points, and the evidence limitations you should account for before relying on a search result in a regulatory or reimbursement analysis.
Starting with the CDRH Web Search Form
The main search page at accessdata.fda.gov/scripts/cdrh/cfdocs/cfpma/pma.cfm presents a form with fields for Applicant, Product Code, Device, Decision Date, PMA Number, Expedited Review, Docket Number, Advisory Committee, Supplement Type, Center, and Predetermined Change Control Plan Authorized [1]. A Sort by control lets you order results by decision date, trade name, applicant name, or PMA number in ascending or descending sequence [1]. The page also links to a Help document and Download Files option, which is useful when you need to understand field definitions before constructing a query [1].
The form is best for targeted lookups when you already know an applicant name or PMA number. For example, entering a specific applicant and selecting Originals Only under Supplement Type narrows results to original approvals rather than panel-track or 180-day supplements [1]. The Advisory Committee dropdown includes panels such as Cardiovascular, Orthopedic, and Clinical Chemistry, which can help you isolate devices reviewed by a particular clinical specialty [1]. Because the page was last updated on 11/09/2026, the interface reflects current field options, but the underlying record completeness still varies by approval year [1].
Understanding What a PMA Record Contains
A PMA record is not a single clinical summary. The openFDA device PMA dataset describes it as containing details about specific products and sponsors, plus administrative and tracking information about applications, receipt dates, and decision dates [4]. An approved PMA application functions as a private license granted to the applicant for marketing a particular medical device [4]. This means the database is strongest for confirming applicant identity, device trade name, product code, and decision timing, but it does not by itself provide the full safety and effectiveness data underlying the approval.
FDA stopped publishing individual PMA approval notices in the Federal Register in 1998. Instead, the agency makes available a summary of the safety and effectiveness data through the Devices Approved page, and the 30-day period for administrative review petitions begins when that summary is placed on the internet [2]. For researchers, this creates a two-step workflow: first locate the PMA record in the database, then retrieve the linked summary document for substantive review. The database record alone cannot establish clinical performance or comparative safety.
A Suggested Workflow for Verifying a Class III Approval
Start on the CDRH PMA search form and enter the applicant name with Supplement Type set to Originals Only [1]. Sort by Decision Date Descending to see the most recent original approvals for that sponsor [1]. Note the PMA number and trade name from the result list. Then open the linked summary of safety and effectiveness data from the Devices Approved page, because the 30-day administrative review clock begins when that summary is posted online [2]. If you need to track post-approval obligations, query the PAS Database by applicant or device name [7]. For batch work across multiple sponsors, use the openFDA API with the pma_number and device_name fields, keeping in mind the monthly update cadence and the 1976-to-present coverage window [4]. This sequence separates record location from substantive review and avoids treating the database entry as the full approval file.
Using the openFDA API for Programmatic Queries
The openFDA device PMA API covers records from 1976 through 2026-10-19 and updates monthly [4]. It converts the original FDA records into JSON and annotates them with harmonized fields such as pma_number, device_name, device_class, and medical_specialty_description [4]. This harmonization is designed to make it easier to find the same device across different datasets, including 510(k), classification, event, recall, registration, and UDI records [4]. For teams that need to join PMA approvals with recalls or adverse event reports, the API is more practical than repeated manual web searches.
The API also exposes applicant-level comparisons. The openFDA page displays PMAs by applicant for approved status, listing sponsors such as Abbott Medical, Boston Scientific Corp, Medtronic Cardiac Rhythm Disease Management, Alcon Laboratories, Medtronic Neuromodulation, and Cochlear Americas [4]. This view can support market surveillance questions about which sponsors hold multiple approved PMAs. However, openFDA explicitly warns users not to rely on the data for medical care decisions and notes that access may be limited under its Terms of Service [4]. The API is a research tool, not a clinical decision system.
Download Files and Update Frequency
For bulk analysis, the FDA PMA Approvals page links to a zipped file, pma.zip, containing information about releasable PMAs [2]. These files are replaced monthly, usually on the 5th of each month, and are accompanied by a file description and an explanation of codes used in the file [2]. The same page points to the Product Code Classification Database, which contains medical device names and associated information [2]. If you need to map a three-letter product code to a device category, that classification database is the companion resource.
The openFDA PMA dataset page confirms a monthly update frequency with earliest data from 1976 and current coverage through the present [6]. The CDRH web search page itself shows a last updated date of 11/09/2026, while the simple search page shows 11/02/2026 [1][5]. These dates reflect interface maintenance rather than the underlying record timestamps. When you cite a PMA decision date, always pull it from the record itself, not from the page footer, because the footer only tells you when the search tool was last modified.
Related Databases for a Complete Approval Picture
The PMA database sits within a larger set of CDRH databases. The Medical Device Databases page lists Devices@FDA, which searches both Premarket Notifications (510(k)s) and Premarket Approvals (PMA) and includes links to device summary information, manufacturer, approval date, and user instructions [7]. The Post-Approval Studies (PAS) Database contains information about current post-approval studies that manufacturers must complete as a condition of approval, searchable by applicant or device information and updated weekly [7]. If a PMA approval carries a PAS requirement, that obligation will not appear in the core PMA record.
The same page describes the Premarket Approval (PMA) Summary Review Memos for 180-Day Design Changes, a pilot program under the CDRH Transparency Initiative that releases some summary review memos for 180-day PMA supplements relating to design changes [7]. This is a narrower resource than the main PMA database, but it can be the only public source for certain supplement-level review reasoning. Researchers should check whether the device of interest has a design-change supplement before concluding that no review documentation exists.
Sources & references
- Premarket Approval (PMA) - accessdata.fda.gov · www.accessdata.fda.gov
- PMA Approvals | FDA · www.fda.gov
- Premarket Approval (PMA) · www.accessdata.fda.gov
- Device premarket approval overview · U.S. Food and Drug Administration
- Premarket Approval (PMA) - FDA · www.accessdata.fda.gov
- About PMA · open.fda.gov
- Medical Device Databases | FDA · fda.gov