Researching FDA 30-day notice records begins with the agency's Premarket Approval database, where each original PMA lists its associated supplements, including 30-day notices. The records show applicant, device, supplement number, and decision outcome, but they do not expose the notice's internal validation summaries or agency correspondence. A useful search therefore combines the public database filters with the guidance documents that define what a 30-day notice must contain. Researchers should verify each record against 21 CFR 814.39 and the related guidance rather than treat a database entry as a complete regulatory history. The workflow below is for locating and reading records, not for deciding whether a manufacturer should have filed one.
One search begins in a surprising place
The FDA Premarket Approval search page is the primary public entry point for 30-day notice records, although the page does not label itself as a notice archive [6]. Its filter set includes a Supplement Type dropdown with an option for 30 Day Notice, alongside 135 Review Track for 30-Day Notification and other supplement types [6]. This filter exists inside the same interface used to locate original PMA applications, which can confuse researchers expecting a standalone system. The search page last updated on 11/09/2026, and users can sort results by decision date, trade name, applicant name, or PMA number [6]. A search restricted to the 30 Day Notice supplement type should therefore return only records where that designation applies, not the full universe of manufacturing-change filings.
In practice, researchers often enter a PMA number first and then inspect the associated supplement list rather than relying on the filter alone. The CASRAI guide to the PMA database explains that a record for an original application identifies the PMA number and that supplements are listed separately as S001, S002, and so on [8]. This means a 30-day notice record will typically appear beneath the original PMA it modifies, with its own supplement number and its own decision fields. Researchers should record the original PMA number for context. The record's supplement number is a distinct field in the PMA dataset, described as the FDA-assigned supplement number [5]. That number, not the original PMA number alone, is the key identifier when tracing a specific manufacturing change.
Why the supplement-type field is not enough
Filtering by 30 Day Notice narrows a dataset but does not reveal whether the change actually qualified as a 30-day notice. The PMA webpage on supplements and amendments states that modifications to manufacturing procedures or methods of manufacture affecting safety and effectiveness may be supported by a 30-day notice, but it also warns that changes to a manufacturing or sterilization site or to design or performance specifications do not qualify [2]. Those site and design changes belong in a different supplement category. The device PMA dataset documents a separate decision code field with values that capture whether FDA accepted or converted a submission, including LE30 for 30 day notice acceptance and APCV for conversion after approval [5]. A result listing 30 Day Notice is therefore a starting point, not proof of the underlying regulatory path.
The openFDA device PMA reference document explains that the supplement type field links to general criteria in 21 CFR Part 814 for determining when a PMA supplement or a 30-day notice is required [5]. The decision code field, not the supplement type field, carries the acceptance and conversion values such as LE30 and APCV [5]. But field metadata is a dictionary, not a record of each notice's content. Researchers who need to know whether a change met the 30-day notice criteria must return to the guidance document, which says the submission should include a summary of the completed validation study, acceptance criteria, statistical methods, and any deviations [1]. None of that detail appears in the PMA database record. The practical consequence is that database research answers a question about existence and disposition, while qualification analysis depends on a document FDA does not post alongside the record.
Search sequence for a first pass
Open the FDA Premarket Approval database and use the Supplement Type dropdown to select 30 Day Notice; add a PMA number, applicant, or product code if you have one [6]. Sort results by decision date or PMA number [6]. For each result, capture the original PMA number, the supplement number, the decision code, and any docket number shown on the record [5][8]. Cross-check the supplement type against the guidance: site changes, design changes, material specification changes, and operating software changes do not qualify as 30-day notices [1]. If the record's decision code field shows LE30, that indicates a 30 day notice acceptance decision made in 30 days or fewer; if it shows GT30, no decision was made in 30 days [5]. Use the openFDA device PMA dataset for bulk analysis, but note that field metadata explains coding definitions rather than each notice's content [5].
Reading the record without overreading
A useful way to read a record is to separate identity fields from decision fields. The device PMA field documentation lists advisory committee, applicant, device, product code, supplement number, supplement reason, and supplement type among the fields available [5]. The decision code, separate from those descriptive fields, identifies outcomes such as LE30 for 30 day notice acceptance with a decision made in 30 days or fewer, and GT30 for no decision made in 30 days [5]. The supplement type field itself links to the general criteria in 21 CFR Part 814 for determining when a PMA supplement or a 30-day notice is required, with values such as Subpart B and Subpart E [5]. Those coded values let a researcher determine at a glance whether a listed notice appears to have closed within the 30-day window. But the decision code reflects the record's disposition, not the manufacturer's compliance, and it should not be quoted as evidence of a manufacturing change's effect on device safety.
The CASRAI guide offers an illustrative layout field by field. In an example PMA record, the PMA number identifies the original application, while the date received and decision date show when FDA received and decided the submission [8]. Product codes appear alongside the applicant and device name, and a docket number may sit with the notice date [8]. That pattern applies to supplements as well, but the guide cautions that not every record carries every field or link [8]. Researchers should avoid treating a missing advisory committee or clinical trial field as meaningful. Absence in the public record is a data completeness issue, not an inference about the notice's substance. The record supports location and citation, not a conclusion about manufacturing method.
A suggested workflow with a concrete example
A practical demonstration can make the process concrete. Suppose a quality analyst at a Class III device manufacturer wants to identify 30-day notice records for a specific product code. The analyst opens the FDA Premarket Approval search page and selects the 30 Day Notice entry in the Supplement Type filter, then enters the three-letter product code if known [6][8]. If the search returns a supplement under an original PMA, the analyst copies the original PMA number and the supplement number. The next step is to confirm the decision code for that supplement in the downloaded dataset or record view, where LE30 would indicate a 30-day notice acceptance decision made in 30 days or fewer [5]. The supplement type field is a separate field that links to the general criteria in 21 CFR Part 814 [5]. This workflow is a suggestion for demonstration only; no source establishes that the agency publishes every 30-day notice record in the same condition.
The same workflow helps avoid a common mistake. If the analyst sees a manufacturing site change in the record, the guidance instructs that site changes do not qualify for a 30-day notice [2]. So an entry initially surfaced by the 30 Day Notice filter alongside a site change would need closer inspection. The guidance's list of non-qualifying changes includes manufacturing or sterilization site of a finished device, device design or performance specifications, material specifications, and device operating software [1]. If a record appears to combine those changes with a 30-day notice designation, the researcher should treat the discrepancy as a reason to check the supplement type and decision code again. The database answers one question; the regulation answers another.
What current primary documents leave unresolved
The available primary documents define the filing criteria and the record fields but do not provide a notice-by-notice content archive. The December 2019 guidance lists what a 30-day notice should contain, including a description of the device, the affected manufacturing facilities, the reason for the change, adverse events or field failures, and summaries of validation and statistical data [1]. That content exists in the notice itself, not in the database record. A researcher who locates a record and confirms a LE30 outcome still cannot read the validation acceptance criteria from the public record. The limitation matters for benchmarking or competitive analysis, where the question is often what change was made and how the manufacturer justified it. The public record answers who, when, and what status, not why or how conclusively.
There is also a timing ambiguity in how researchers should apply the decision codes. The device PMA documentation defines the decision code LE30 as a 30 day notice acceptance with a decision made in 30 days or fewer, while GT30 means no decision made in 30 days [5]. The difference is useful for measuring throughput, but it does not tell a researcher whether FDA later asked for additional information or whether a GT30 record simply reflects an administrative lag. The PMA supplements page acknowledges that if FDA finds a 30-day notice inadequate, it becomes a 135-day PMA supplement when the submission contains appropriate content [2]. That conversion depends on the notice's contents, which are not visible in the database. Researchers should report the observed decision code and stop short of attributing meaning beyond what the code defines.
Sources & references
- 30-Day Notices, 135-Day Premarket Approval (PMA) Supplements and 75- Day Humanitarian Device Exemption (HDE) Supplements for Manufacturing Method or Process Changes · www.fda.gov
- PMA Supplements and Amendments | FDA · www.fda.gov
- Computer Software Assurance for Production and Quality Management System Software · www.fda.gov
- 30-Day Notices, 135-Day Premarket Approval (PMA) Supplements and 75-Day Humanitarian Device Exemption (HDE) Supplements for Manufacturing Method or Process Changes | FDA · www.fda.gov
- Section Field Name Type Description This equates to the review division within CDRH in which the PMA would be reviewed, · open.fda.gov
- Premarket Approval (PMA) - accessdata.fda.gov · www.accessdata.fda.gov
- FDA’s PMA Supplements and Amendments: When and How to Use Each · www.greenlight.guru
- PMA Database: Search FDA Premarket Approvals — CASRAI · casrai.org