Quick Answer
eSTAR submission software should help medical device teams prepare, organize, validate, and quality-control the evidence that goes into FDA's eSTAR template. FDA requires eSTAR for 510(k) submissions as of October 1, 2023 and De Novo submissions as of October 1, 2025 unless exempted. Certain PMA, IDE, and Pre-Submission types can use eSTAR voluntarily. The software value is not replacing FDA's template; it is reducing missing content, inconsistent claims, weak attachments, and readiness problems before filing.
Key Takeaways
- eSTAR is FDA's electronic Submission Template And Resource for medical device submissions.
- eSTAR is mandatory for 510(k) and De Novo submissions unless exempted.
- PMA use is more limited: FDA allows voluntary eSTAR use for certain PMA application and supplement types.
- eSTAR submission software should focus on readiness, validation, evidence mapping, version control, and cross-reference consistency.
- A completed eSTAR can still be weak if predicate logic, risk analysis, performance evidence, or labeling support is incomplete.
- Medical device teams often treat eSTAR as a final filing template. That is too late. eSTAR changes how a submission is packaged, but the hard problems remain upstream: pathway choice, indications, predicate strategy, performance testing, risk controls, labeling, and attachment quality.
- The best eSTAR submission software does not pretend to replace FDA's eSTAR. It helps teams get the package ready before they enter the last-mile filing workflow.
- This guide explains what eSTAR software should do, where FDA requirements apply, and how to evaluate a readiness workflow for 510(k), De Novo, and PMA programs.
- Related guides:
- From QMSR to eSTAR
- Quality records for regulatory submissions
- Greenlight Guru alternative
- 510(k) submission guide
- De Novo submission guide
- PMA submission guide
- PMA vs 510(k) vs De Novo
- eSTAR Validation
What Is eSTAR?
eSTAR stands for electronic Submission Template And Resource. FDA describes eSTAR as an electronic template intended to support preparation of medical device submissions.
The template helps standardize content organization and prompts submitters for information needed for review. It does not remove the need for a complete regulatory strategy or complete evidence package.
Current eSTAR Requirement Snapshot
| Submission Type | eSTAR Status |
|---|---|
| 510(k) | Required as of October 1, 2023 unless exempted |
| De Novo | Required as of October 1, 2025 unless exempted |
| Certain PMA applications and supplements | Voluntary for certain types |
| IDE original and supplement submissions | Voluntary for certain types |
| Pre-Submissions | Voluntary for certain types |
| 513(g) requests | Voluntary through supported routes |
For CDRH submissions, FDA identifies the CDRH Customer Collaboration Portal as the online submission route. For CBER-led device submissions, FDA identifies the Electronic Submission Gateway for relevant eSTAR submissions.
What eSTAR Submission Software Should Actually Do
eSTAR software should not merely store a completed template. It should help a team answer the readiness questions that determine whether the eSTAR will survive FDA review.
| Capability | Why It Matters |
|---|---|
| Pathway mapping | Confirms whether the file is 510(k), De Novo, PMA, IDE, Pre-Sub, or another pathway |
| Required content tracking | Flags missing sections, attachments, and evidence categories |
| Evidence-to-claim mapping | Connects indications, labeling claims, and performance evidence |
| Predicate comparison support | Critical for 510(k) substantial equivalence |
| Risk and controls mapping | Critical for De Novo classification rationale |
| Attachment quality control | Checks whether files, reports, versions, and references align |
| Cross-reference validation | Reduces mismatches between summaries, reports, labeling, and attachments |
| Review history | Preserves decisions, comments, and readiness sign-offs |
| Standards mapping | Tracks recognized consensus standards and declarations where used |
| Export and filing discipline | Keeps final eSTAR package aligned with FDA submission route expectations |
The buyer should ask a basic question: does the software make the eSTAR easier to fill out, or does it make the submission more defensible?
eSTAR Readiness Starts Before the Template
The most common eSTAR problem is not that the team cannot find the right field. It is that the source evidence is not ready when the team reaches the field.
Before final template assembly, teams should confirm:
- The intended use and indications are consistent across the package.
- Predicate or De Novo rationale is supported by evidence.
- Performance testing matches the device description and claims.
- Risk controls are linked to verification or validation evidence.
- Software and cybersecurity documentation is current.
- Labeling does not introduce unsupported claims.
- Standards declarations match the evidence and device configuration.
- Attachments are final, approved, and correctly versioned.
Software can help by mapping evidence to sections early, so missing attachments and contradictory claims are found before the final filing week.
eSTAR Software for 510(k)
For 510(k), eSTAR readiness depends on substantial equivalence.
The software should help teams connect:
- Device description
- Indications for use
- Predicate device
- Substantial equivalence comparison
- Technological characteristics
- Performance testing
- Standards and declarations of conformity
- Labeling and claims
- 510(k) summary or statement
The strongest 510(k) readiness workflow catches contradictions before FDA does. For example, a labeling claim may imply a broader intended use than the predicate supports, or a performance test may not address a technological difference described in the comparison table.
For deeper filing guidance, see the 510(k) submission guide.
eSTAR Software for De Novo
For De Novo, eSTAR readiness depends on classification logic.
The software should help teams connect:
- Device novelty
- Absence of a suitable predicate
- Proposed Class I or Class II classification
- Probable risks and benefits
- Proposed general or special controls
- Performance evidence
- Labeling and risk mitigations
- Prior regulatory history
The De Novo package must explain why the device can be regulated without PMA. eSTAR helps structure the request, but the evidence must still support the classification decision.
For deeper filing guidance, see the De Novo submission guide.
eSTAR Software for PMA
PMA is different. FDA does not currently require eSTAR for all PMA submissions, but FDA allows voluntary eSTAR use for certain PMA application and supplement types.
PMA readiness software should not focus only on the eSTAR container. It should support:
- Clinical evidence organization
- Nonclinical evidence organization
- Manufacturing and quality information
- Labeling evidence support
- PMA supplement tracking
- Conditions of approval and lifecycle traceability
- Cross-reference consistency across large evidence packages
For PMA, the core FDA question is whether valid scientific evidence supports safety and effectiveness. eSTAR may help with structure where available, but the evidence logic remains the center of the filing.
For deeper filing guidance, see the PMA submission guide.
eSTAR Readiness Problems Software Should Catch
The most valuable eSTAR software catches problems that would otherwise appear during technical screening, acceptance review, or substantive review.
| Problem | Why It Matters |
|---|---|
| Missing attachment | FDA cannot review the claimed evidence |
| Inconsistent indication | Predicate, labeling, and evidence may not align |
| Weak predicate rationale | 510(k) substantial equivalence becomes vulnerable |
| Missing risk-control link | De Novo special controls may be unsupported |
| Unsupported labeling claim | FDA may request revisions or additional evidence |
| Stale document version | Reviewers may see conflicting information |
| Broken cross-reference | Submission credibility and review efficiency suffer |
| Wrong submission route | Filing logistics can delay receipt and review |
These are not cosmetic issues. They are submission readiness issues.
Quality Records That Often Feed eSTAR
eSTAR packages often depend on controlled records that originate in the QMS, design system, engineering tools, or document control system.
Common source records include:
- Design inputs, outputs, reviews, verification, and validation
- Risk analysis and risk-control verification
- Software requirements, architecture, testing, anomalies, and release records
- Cybersecurity documentation
- Biocompatibility, sterilization, electrical safety, performance, and bench testing reports
- Labeling, instructions for use, warnings, and promotional claim support
- Complaint, CAPA, and postmarket evidence where relevant
- Supplier, manufacturing, and quality system information where requested
The submission team should know which source record is authoritative. Copying uncontrolled PDFs into a folder may be fast, but it creates version risk and makes later questions harder to answer.
Workflow Controls to Look For
Useful eSTAR submission software should include controls around the readiness process:
- Section owner assignment
- Evidence owner assignment
- Required attachment tracking
- Review comments and resolution history
- Final readiness sign-off
- Version comparison for changed attachments
- Cross-reference checks between sections
- Export package review before filing
These controls do not replace regulatory judgment. They make regulatory judgment easier to apply consistently across a large package.
How Assyro Supports eSTAR Readiness
Assyro focuses on the readiness layer around medical device submissions. eSTAR Validation helps teams identify missing or inconsistent elements before filing, while medical device regulatory submission software supports broader submission preparation across 510(k), De Novo, and PMA workflows.
The practical value is catching whether the package is coherent: the pathway matches the device, the evidence supports the claims, the attachments are complete, and the final eSTAR is ready for FDA review.
No. FDA's eSTAR is the official submission template. eSTAR submission software should support preparation, validation, organization, and quality control around the evidence and attachments that go into the FDA template.
References
This guide reflects FDA eSTAR information current as of May 2026. Confirm the latest FDA eSTAR page, submission guidance, center routing, and review division feedback before filing.
About the author
Assyro Team
Expert regulatory operations consultants helping pharmaceutical companies navigate complex compliance challenges.
See Assyro in action
Catch eCTD and eSTAR errors before your FDA review cycle.
Book a 20-minute demo this week. We'll validate a sample of your submission live and show you exactly where Assyro catches what your current QC misses.