Written and maintained by CASRAI Editorial Board
Last updated
What eSTAR actually is
eSTAR — the electronic Submission Template And Resource — is an interactive PDF form FDA’s Center for Devices and Radiological Health (CDRH) built to replace the old free-form 510(k)/De Novo submission binder. Instead of assembling a stack of separate documents against a checklist you interpret yourself, you fill in a structured PDF: sections expand or collapse based on the answers you give (a Special 510(k) hides irrelevant sections a Traditional 510(k) needs, for example), each section shows a red or green completion indicator, and the form runs a battery of built-in logic checks — required fields, internal consistency between answers, attachment presence — before you can submit.
The practical effect is that a properly completed eSTAR is designed to arrive at FDA already representing a complete submission, rather than a submission FDA’s staff has to first triage for missing pieces.
Which submission types use it, and since when
eSTAR coverage has expanded in stages rather than arriving all at once:
- Traditional, Special, and Abbreviated 510(k)s — eSTAR became mandatory for these on October 1, 2023 (with limited exemptions FDA lists on the eSTAR Program page). A paper or free-form electronic 510(k) submitted after that date is not an eSTAR compliance failure so much as a wrong-format submission — FDA’s technical screening (below) will not process it.
- De Novo classification requests — eSTAR became mandatory here later, on October 1, 2025, unless exempted.
- Q-Submissions (Pre-Submissions, Submission Issue Requests, Informational Meetings, Study Risk Determinations, PMA Day 100 Meetings, Accessory Classification Requests) — supported, but voluntary.
- IDE submissions and PMA 30-Day Notices — opened for voluntary eSTAR use in September 2025, with FDA signaling further expansion toward full PMA submission types (original PMAs, Panel Track/Real-Time/180-Day supplements) as that build-out continues.
Check the current exemption list and PMA rollout status directly against FDA’s own eSTAR Program page before treating a specific submission type as covered — this is an actively expanding programme, and a guide page is not the place to freeze a rollout date that FDA itself may update.
Technical screening, not Refuse to Accept
For a conventional 510(k), an incomplete submission gets kicked back through the Refuse to Accept (RTA) policy — FDA checks the submission against an RTA checklist within 15 calendar days and either accepts it for substantive review or refuses it outright, restarting the clock. eSTAR submissions are handled differently: because a properly built eSTAR is supposed to already be complete by construction, FDA does not run RTA against it. Instead, submissions go through a two-part technical screening:
- An automated virus scan and file-integrity check.
- A completeness screen against the eSTAR’s own built-in requirements.
If technical screening finds the eSTAR incomplete, FDA notifies the submitter by email identifying what’s missing, and the submission is placed on hold rather than refused outright. The submitter then has 180 days from the date of that deficiency notification to submit a complete replacement eSTAR. Miss that window and FDA considers the 510(k) withdrawn and closes it in the tracking system — functionally similar to an RTA refusal in consequence, but procedurally a different mechanism with a materially longer cure window than the RTA process’s own resubmission timelines.
Where attachment conventions cause real validation failures
Most eSTAR technical-screening holds trace back to a small set of recurring mistakes, not exotic content gaps:
- Editing the exported PDF by hand. eSTAR’s dynamic logic (the section show/hide behavior, the completion indicators) lives in the form’s underlying structure. Flattening the PDF, merging it with another document, or editing it in a general PDF tool after export can strip that structure even though the document still looks complete to a human reviewer — and a structurally broken eSTAR fails the automated completeness screen regardless of what the content says.
- Using an outdated template version. FDA revises eSTAR templates periodically; a submission built on a template version FDA has since retired can fail technical screening even with fully correct content, because the screening logic checks against the current template’s expected structure.
- Attachment naming and format mismatches. Each eSTAR attachment field expects a specific file type (typically PDF) and reasonable file naming — a spreadsheet or image dropped into a field expecting a formatted document, or a file name with characters the system rejects, is a common, entirely avoidable hold reason.
- Treating eSTAR as a wrapper around an old-format submission. Copy-pasting content built for a pre-eSTAR free-form 510(k) into the template’s text fields, without actually working through the template’s own branching questions, tends to leave required fields technically populated but substantively thin — which does not trip the automated completeness check but does invite substantive review questions later.
None of this is unique to any one device type — it’s a document-assembly discipline problem that shows up identically whether the underlying device is a Class II diagnostic or a Class I general-controls product.
How eSTAR fits into the device-pathway picture
eSTAR is a submission-format requirement, not a pathway decision — it doesn’t change whether a device needs a 510(k), a De Novo request, or a PMA; see 510(k) vs. PMA for how that pathway choice gets made. It sits downstream of that decision, governing how the chosen submission gets assembled and transmitted. It’s also worth distinguishing from the postmarket and quality-system obligations that follow clearance or approval — a Design History File documents how the device was developed, complaint handling and Field Safety Corrective Action processes govern what happens after the device is on the market, and none of those obligations run through eSTAR at all — eSTAR’s scope stops at the premarket submission itself. For devices that are software, Software as a Medical Device (SaMD) submissions go through the same eSTAR mechanics as hardware devices once a 510(k) or De Novo pathway applies. For sponsors also navigating the EU side of a submission, EU MDR technical documentation requirements are a structurally different (and non-overlapping) documentation regime — eSTAR has no EU equivalent or interoperability with it.
Frequently asked questions
Is eSTAR mandatory for every medical device submission?
No. It’s mandatory for Traditional, Special, and Abbreviated 510(k)s (since October 1, 2023) and for De Novo requests (since October 1, 2025), subject to FDA’s listed exemptions. It’s voluntary for Q-Submissions, IDE submissions, and PMA 30-Day Notices, and FDA has signaled further expansion toward full PMA submission types.
What happens if FDA finds my eSTAR incomplete?
It goes through technical screening rather than Refuse to Accept: FDA emails the submitter identifying the gap, places the submission on hold, and gives 180 days from that notice to submit a complete replacement eSTAR. Missing that window means FDA treats the 510(k) as withdrawn.
Does eSTAR replace the Refuse to Accept (RTA) policy?
For eSTAR submissions specifically, yes — RTA doesn’t apply to a properly formed eSTAR because the template’s own structure is designed to prevent an incomplete submission from being assembled in the first place. RTA still governs any 510(k) submission type that falls outside eSTAR’s mandatory scope.
Can I still submit a paper or free-form electronic 510(k)?
Not for the submission types eSTAR now covers as mandatory, outside FDA’s listed exemptions. Check the current exemption list on FDA’s eSTAR Program page before assuming a given submission qualifies.
