eSTAR is a guided, structured submission template that performs automated content checks. It is mandatory for 510(k) submissions and supported for De Novo submissions to FDA's CDRH. eSTAR is an interactive PDF template that guides submitters through each required section, with built-in logic that shows or hides questions based on device type and automated checks for missing content. It has been mandatory for most 510(k) submissions since October 1, 2023, and is also available for De Novo requests. Submissions are sent electronically through the CDRH Portal.

Why it matters

As of October 1, 2023, eSTAR is mandatory for all 510(k) submissions (except for dual and CBER-led submissions). It is voluntary but supported for De Novo, and FDA is expanding eSTAR to PMA in phases. eSTAR uses a guided PDF template (Adobe Acrobat) with automated content validation: mandatory fields, conditional logic, integrated FDA guidance links, and eCopy replacement. Using eSTAR bypasses the traditional RTA review for 510(k) because the template's automated checks perform the acceptance validation up front. Vendors increasingly build internal tools that map QMS records (design outputs, verification, validation, labeling, cybersecurity artifacts) directly to eSTAR sections.

Common pitfalls

•Using an outdated eSTAR template. FDA updates eSTAR regularly; using a previous version causes submission rejection.
•Missing embedded attachments. eSTAR expects supporting documents to be attached inline; external references or missing PDFs fail validation.
•Ignoring the cybersecurity section for cyber devices. eSTAR has dedicated cybersecurity fields aligned with Section 524B; leaving them incomplete triggers deficiencies even without a formal RTA.
•Trying to submit eSTAR on non-Adobe PDF readers. eSTAR relies on Adobe-specific JavaScript; other readers break the template.

Sources

FDA eSTAR Program · FDA
eSTAR for Medical Device Submissions · FDA
RAPS Regulatory Focus · RAPS

Open full page

Select term B to compare.

Why compare MedTech terms side by side?

MedTech terminology is full of pairs that look interchangeable but carry very different regulatory, clinical, and commercial consequences. Picking the wrong framework, pathway, or standard early in a project can add months to a submission, invalidate clinical evidence, or trigger an audit finding. Side-by-side comparison is the fastest way to surface those differences before they become costly mistakes.

Each comparison on this page pulls from the same vendor-neutral, sourced definitions used throughout the MedTech Terms glossary. You see the one-line summary, the formal definition, why it matters in practice, common pitfalls, and the primary sources (FDA guidance, EU MDR/IVDR articles, ISO/IEC standards, MDCG documents, IMDRF principles) that back each entry. That makes the comparison defensible in regulatory strategy memos, design reviews, and submission narratives.

Common comparison patterns

Regulatory pathway choice - 510(k) vs PMA, 510(k) vs De Novo, Abbreviated vs Special 510(k).
Quality systems - QSR vs ISO 13485, QMSR vs QSR.
Software classification - SaMD vs SiMD, Locked vs adaptive AI.
EU frameworks - MDR vs IVDR, CE Mark vs UKCA.
Cybersecurity artifacts - SPDX vs CycloneDX SBOM, CVE vs CVSS.
Post-market actions - Recall vs field action, Removal vs correction.

How to use this tool

Pick term A and term B from the dropdowns, or click a preset above. The URL updates with both slugs so you can bookmark or share the exact comparison with a colleague, a notified body reviewer, or your regulatory consultant. Click Open full page on either side for the complete entry, including FAQs, related terms, and the full citation list. If you are not sure which term to start with, browse the Categories view or the A-Z index.

MedTech Terms is a vendor-neutral community resource sponsored by Blue Goat Cyber. Definitions are written for educational use and are not legal or regulatory advice.