eSTAR did not remove the acceptance check

Pull a cleared 510(k) from openFDA today and it carries the same fields it carried in 2019: applicant, product code, decision code, the dates a filing was received and decided. What changed underneath, starting in October 2023, was not a field. It was where FDA’s completeness check happens — and nothing in the record says which way a given clearance went through.

The statute behind the format

Section 745A(b) of the FD&C Act — 21 U.S.C. § 379k-1(b), added by Section 207 of the FDA Reauthorization Act of 2017 — lets FDA require electronic format for device submissions, including 510(k)s, and specify that format in guidance rather than rulemaking. FDA used that authority to build eSTAR, an interactive PDF template, and to make it mandatory: for nearly every 510(k), starting October 2023; for De Novo requests, starting October 1, 2025. Waivers from the electronic-format requirement are not offered. A narrow set of submissions the CDRH Portal cannot technically accept still go to FDA by mail, on paper — the exception the rule was written to keep, not to create.

What eSTAR actually replaced

Before eSTAR, a submitted 510(k) went through Refuse to Accept review — an FDA staff check, run after the filing arrived, for whether the submission was complete enough to review at all. eSTAR is built around that same checklist, moved to the other side of the transaction: the template states, on its own first page, whether it is complete before an applicant can submit it, and FDA’s guidance is direct that a separate Refuse to Accept review is not conducted on an eSTAR submission the way it is on one that arrives without it. The check did not go away. It changed who runs it, and when.

The checklist did not disappear when eSTAR arrived. It moved to the other side of the submit button.

The record doesn’t say which way a clearance went through

openFDA’s 510(k) field reference — the same one this blog has already read for its decision codes, its third-party flag, its summary-or-statement choice — carries no field marking whether a clearance was filed on the eSTAR template or arrived the older way. A clearance decided in November 2022 and one decided in November 2023 read identically on every field the API returns. Only the decision date places it on one side of the mandate or the other, and only by inference — the record itself never says.

The practice

This matters most for the field a portfolio watch reads for pace: the gap between a 510(k)’s received and decided dates. Before October 2023, that gap could include time an FDA-run Refuse to Accept hold added to the clock. After it, for an eSTAR submission, that particular delay mostly happens before the filing is ever received as complete — off the clock the public record counts at all. Comparing receipt-to-decision gaps across that boundary, for the same product code, is comparing two different intake processes with no field to tell them apart; read a shorter modern gap as a change in intake mechanics before reading it as a product code getting easier at FDA. What a specific gap means for a specific competitor’s filing is a judgment for the regulatory professional holding that file — this is regulatory intelligence and method, about what one field can and cannot show, never regulatory advice about a submission of your own.

FDA Radar ingests decision code, third-party flag, and both dates on every clearance it pulls, exactly as openFDA publishes them; see what we monitor and how often. An eSTAR flag isn’t missing from that ingestion by omission. FDA has never published one to ingest.