Question 1

What is eSTAR validation software?

Accepted Answer

eSTAR validation software checks an FDA eSTAR submission package for completeness, structural integrity, attachment coverage, and internal consistency before submission through CDRH Portal. FDA's eSTAR template has built-in PDF-level validation that catches missing signatures and broken cross-references, but it does not check for semantic completeness (is the performance testing summary consistent with the indications for use?) or for product-code-specific attachment requirements. Dedicated validation software adds those content-level checks on top of the eSTAR's built-in validation.

Question 2

What causes a 510(k) Refuse to Accept (RTA)?

Accepted Answer

FDA's Acceptance Review checklist for 510(k) evaluates submission completeness against specific elements: device description, intended use, predicate information, substantial equivalence comparison, performance testing, labeling, and administrative items. Missing any of these typically triggers an RTA notice within 15 calendar days, adding 30-60 days to clearance timeline. eSTAR's built-in validation catches some but not all RTA triggers. Assyro's validation focuses specifically on the RTA checklist so the submission passes acceptance on first review.

Question 3

How is eSTAR validation different from eSTAR authoring?

Accepted Answer

Authoring is the process of building the eSTAR content (predicate comparisons, testing summaries, labeling, etc.). Validation is the process of checking the finished eSTAR for completeness and consistency before submission. Both happen in Assyro in the same workspace, but validation runs as a continuous layer across the authoring process, not as a one-time end-of-cycle gate. Teams that treat validation as a final step tend to discover gaps too late; continuous validation surfaces them while authoring is still in progress.

Question 4

What does Assyro check that eSTAR itself doesn't?

Accepted Answer

eSTAR's built-in validation covers PDF-level checks: required fields completed, attachments present, digital signatures applied, cross-references resolved within the PDF. Assyro adds content-level checks: indication statement consistency between the device description, substantial equivalence section, and labeling; performance testing coverage against FDA recognized consensus standards; attachment completeness mapped to the specific product code; biocompatibility testing adequacy for contact duration and tissue type; software documentation coverage for moderate and major level of concern software.

Question 5

Is eSTAR validation only for 510(k) submissions?

Accepted Answer

No. eSTAR covers 510(k) (Traditional, Abbreviated, Special) and De Novo classification requests. FDA has extended eSTAR to De Novo submissions and may extend it further to other CDRH submission types in the future. Assyro validates all current eSTAR-enabled submission types. PMA submissions do not use eSTAR and have a different readiness framework.

Question 6

Does validation help with Additional Information (AI) requests?

Accepted Answer

Yes, indirectly. FDA typically issues an AI request when the submission is substantively incomplete in a way that blocks review. By catching completeness gaps pre-submission, validation reduces the AI request rate. It does not prevent all AI requests — some are content-quality issues that only emerge during FDA review — but it eliminates the preventable ones. Teams using rigorous pre-submission validation typically see AI request rates drop 30-50% compared to their baseline.

Question 7

Can we run validation on a partial eSTAR in progress?

Accepted Answer

Yes. Validation runs continuously from the first content added. Early in drafting, the validation report will show many incomplete items because the work is still in progress — that's expected and not a defect. As the team fills in content, the gap list shrinks. By T-7 the validation report should show zero structural gaps and only substantive review items remaining. The point is to see the gap list evolve across the cycle, not to validate only at the end.

Question 8

How does this compare to free FDA tools?

Accepted Answer

FDA provides the eSTAR template itself and the CDRH Premarket Review Submission Cover Sheet tool, both free. These are creation tools, not validation tools — they help you fill in the submission, they don't tell you if the submission is complete against FDA's acceptance criteria. Assyro's validation is additive: teams still use the FDA eSTAR template (they must), but Assyro provides the content-level readiness check that FDA tools don't. Most teams adopt both because they solve different problems.

eSTAR Validation Software

How eSTAR Validation Fits the Submission Workflow

Check eSTAR Completeness Continuously, Not at T-2

Catch the Broken Cross-References Before FDA Does

Flag Missing Attachments by Product Code

Close the Gap Between 'Thinks It's Ready' and 'Actually Ready'

Controls and Traceability for eSTAR Validation

Keep eSTAR Validation Audit-Ready

Scale Across Programs Without Adding Complexity

Questions About eSTAR Validation

See eSTAR Validation in a Live Submission Workflow.