A PMA filing review only checks completeness

A PMA that clears FDA's 45-day filing review often gets read inside the sponsor's own file as if the science has already passed some kind of test. It hasn't. 21 CFR 814.42 asks a narrower question than that: is the application complete enough, on its face, to permit the substantive review that hasn't started yet. A filing letter is FDA agreeing to read the PMA, not agreeing with it — and a sponsor that treats the letter as an early verdict has confused the gate that opens a review with the review itself.

The 45-day clock decides whether review can start, not how it ends

Section 814.42(a) sets the mechanics plainly: within 45 days after FDA receives a PMA, the agency notifies the applicant whether the application has been filed. Filing, in the section's own terms, means FDA has made a threshold determination that the application is sufficiently complete to permit a substantive review — not that the device is safe, not that the data support approval, not even that the science is sound. Those questions belong to the review 814.44 governs once filing has already happened. A sponsor counting the 45 days as if it were a preview of the eventual outcome is reading a completeness check as a scientific one.

814.42(e) lists specific gaps, not a general quality judgment

What can actually stop a PMA from being filed is a named, narrow list, not FDA's open-ended sense that the application seems thin. Section 814.42(e) lets FDA refuse to file when the application doesn't contain the information required under section 515(c)(1)(A) through (G) of the FD&C Act; when it's missing an item 814.20 itself requires and the omission isn't adequately justified; when the applicant has a pending 510(k) on the same device and FDA hasn't yet decided whether that device actually falls within PMA's own scope under 814.1(c); when the application contains a false statement of material fact; or when it isn't accompanied by the certification or disclosure statement Part 54 requires for the clinical investigators behind the data. Every one of those is a presence-or-absence question — is the item there, is the statement attached — not a judgment about whether the evidence the item points to is any good.

A refused filing and a refused approval run on different clocks

Where FDA does refuse to file, the sponsor isn't left to guess at the reasons: the notice has to identify the specific deficiencies that kept the application from being filed, tied to 814.42(e)'s own list, and the applicant can request an informal conference with the director of the reviewing office within 10 working days of receiving that notice. That's a fast, narrow dispute path built for a fast, narrow question — whether a named item was missing or inadequately justified. It's a different proceeding entirely from what happens once a filed PMA reaches the end of substantive review and comes back not approvable: that outcome turns on the evidence itself, follows its own procedure under 814.44 and 814.45, and isn't something a 10-day conference request is built to resolve.

The same distinction, applied to the highest-tier submission

FDA runs a version of this same completeness-first gate at every premarket tier — a 510(k)'s acceptance review checks that the required sections are present before anyone reads the substance behind them, and the same logic underlies FDA's checks on other submission types. What's different about the PMA filing review is what sits on the other side of it: once a PMA is filed, it's the whole application FDA weighs in the substantive review that follows, and any later change to what gets approved runs through its own separate sorting logic under 814.39, not back through 814.42. Filing is the first gate a PMA passes through, not a preview of any of the gates that come after it.

Where this meets the file

A filing tracker that logs the 45-day notification date and stops there has recorded a milestone, not a status. What it should also carry is which of 814.42(e)'s specific grounds the application was checked against before submission — the 515(c)(1) elements, the 814.20 items, the Part 54 certification — so a refusal, if one comes, points back to a checklist the team already ran rather than a surprise. Once a PMA clears that gate, the conditions an eventual approval order can attach are a separate, later question entirely. A filing-readiness worksheet built around 814.42(e)'s own named grounds is previewed in the launch catalog. If your program checks for filing completeness differently, the shelf takes that correction directly.