From 510(k) to eSTAR: What MedTech Teams Must Know

Most medical device companies entering the U.S. market take the 510(k) route. As of October 1, 2023, the only way to submit a 510(k) for most devices is through the FDA’s eSTAR template.

As of October 1, 2025, the same is true for De Novo requests. The shift from open-format PDF submissions to a structured, validated electronic template is the most consequential change to FDA premarket submissions in a decade, and most MedTech teams are still adjusting to what it actually requires. 

This guide walks through what the 510(k) pathway is, what eSTAR is, how the two intersect, and what regulatory and product teams need to have in place before they ever open the template. 

The 510(k) Pathway in Brief 

A 510(k), formally called a Premarket Notification, is a submission to the FDA demonstrating that a medical device is substantially equivalent to a legally marketed predicate device. The 510(k) pathway applies primarily to Class II devices and a small subset of Class I and Class III devices that have not been exempted from premarket notification. 

A submission must establish that the new device shares the same intended use as its predicate, and that any differences in technological characteristics do not raise new questions of safety or effectiveness. That sounds straightforward in summary form. In practice, building a defensible substantial equivalence argument is where most submissions either succeed quickly or get caught in deficiency cycles for months. 

What Is eSTAR? 

eSTAR stands for electronic Submission Template And Resource. It is an interactive PDF template produced by the FDA that structures a premarket submission in the same order and format that CDRH reviewers use internally. eSTAR contains drop-down fields, conditional logic that shows or hides sections based on device characteristics, embedded forms (including the Indications for Use page and the Premarket Review Submission Cover Sheet), and automatic validation that flags incomplete or inconsistent information before submission. 

The current template is Version 6.1, updated in early 2026 to align with the FDA’s new Quality Management System Regulation and the December 2025 Real World Evidence guidance. eSTAR is mandatory for 510(k) and De Novo submissions, and it is available voluntarily for Investigational Device Exemption submissions, PMA 30-Day Notice supplements, Q-Submissions, and standard PMAs. 

All 510(k) and De Novo eSTAR submissions must be uploaded through the CDRH Customer Collaboration Portal. 

Why the Shift From Traditional Submissions to eSTAR Matters 

For decades, 510(k) submissions were essentially long-form documents organized however the submitter chose, subject only to the FDA’s Refuse to Accept (RTA) review. eSTAR replaces that model with three meaningful changes. 

First, structure is now imposed at the submission level. Reviewers receive content in a predictable order with predictable fields, which speeds technical screening and reduces variability in how submissions are interpreted. 

Second, validation moves upstream. eSTAR’s built-in checks catch missing attachments, inconsistent answers, and skipped sections before the file leaves the manufacturer’s hands. The traditional RTA correction loop is largely eliminated for eSTAR submissions, which is one of the program’s headline benefits. 

Third, the cost of an inaccurate answer has gone up. Drop-down fields and conditional logic mean a single wrong selection can hide entire sections from a reviewer or omit required documentation. The FDA has stated explicitly that inaccurate responses may lead to early holds in review. There is no graceful recovery if an eSTAR is signed and submitted with a structural error. 

How eSTAR Changes Submission Strategy 

The biggest strategic shift is that the work of building a 510(k) now happens almost entirely outside eSTAR. Once an eSTAR file is signed as complete, attachments and responses cannot be edited. Teams that try to draft inside the template tend to lose time, lose work, and sometimes lose entire revision cycles. 

The right approach is to treat eSTAR as a publishing layer. The submission itself, including the substantial equivalence rationale, performance testing summaries, risk management file, design history file, labeling, software documentation, biocompatibility evaluation, and sterilization validation, is built and reviewed in the team’s own document system. eSTAR is populated at the end, not at the beginning. 

This sequencing matters because eSTAR templates are revised every few months. Older versions become obsolete and cannot be uploaded. Teams that complete documentation outside the template avoid the rework that comes with mid-cycle template updates. 

What MedTech Teams Need Inside an eSTAR 510(k) 

A complete eSTAR 510(k) requires content across roughly twenty-one sections, depending on device characteristics. The high-impact areas for most teams are: 

1.Substantial Equivalence Documentation. 

Predicate device identification, side-by-side comparison tables, and a written rationale that addresses every difference in technological characteristics. 

2. Performance Testing. Bench testing, animal testing where applicable, and clinical data summaries, each cross-referenced to the relevant recognized consensus standards. 

3. Risk Management File (RMF). A complete risk management file conformant to ISO 14971, including hazard analysis, risk control measures, and residual risk evaluation. 

4. Design History File (DHF). Design inputs, design outputs, design verification, design validation, and design transfer documentation, traceable end to end. 

5. Software Documentation. For devices with software, documentation aligned with the FDA’s 2023 guidance on software in medical devices, including architecture, requirements, verification, and unresolved anomalies. 

6. Cybersecurity (Section Q). This is where submissions stall most often. Section Q references the FDA’s premarket cybersecurity guidance, currently the version dated February 2026, and requires a security architecture description, threat modeling using a structured framework such as STRIDE, and a Software Bill of Materials aligned with the NTIA Minimum Elements. 

7. Labeling. Indications for use, instructions for use, package labeling, and any patient-facing materials. 

8. Biocompatibility, Sterilization, and Shelf Life. Where applicable, with full test reports and rationales for any test waivers. 

Where Submissions Stall 

The deficiency patterns in eSTAR submissions are predictable. Substantial equivalence rationales that lean on assertion rather than evidence, software documentation prepared late and out of sync with verification activities, cybersecurity sections built from generic templates rather than device-specific architecture, and risk management files that document outcomes without traceability to design decisions. Each of these is a multi-week deficiency cycle waiting to happen. 

The structural answer is to build documentation as a connected system, not as a set of standalone deliverables produced for a single submission moment. Traceability across the design history file, risk management file, performance testing, and labeling is what holds up under FDA review. 

The QMSR Layer (Effective February 2, 2026) 

On February 2, 2026, the FDA’s Quality Management System Regulation replaced the longstanding Quality System Regulation. The QMSR incorporates ISO 13485:2016 by reference and embeds risk-based thinking across the entire quality management system, not only design controls. eSTAR Version 6.1 reflects this change in its quality system fields. 

For MedTech teams, the QMSR transition means three things in practical terms. Quality system documentation submitted via eSTAR must align with the ISO 13485:2016 structure. Terminology shifts to ISO 9000:2015 Clause 3 definitions. And on January 30, 2026, the FDA released a new compliance program manual, “Inspection of Medical Device Manufacturers” (CP 7382.850), replacing the QSIT guide that had governed inspections for decades. 

Teams that already operate under an ISO 13485-certified quality system will find the transition largely administrative. Teams that built quality systems against the old QSR will need to map their documentation to the new framework before their next submission. 

Building Submission-Ready Documentation Before You Open eSTAR 

The teams that move fastest through 510(k) review are not the ones that fill out eSTAR fastest. They are the ones whose documentation is already structured, traceable, and consistent before the template is opened. 

This is the core problem QualiVerse® was built to solve. QualiVerse is QMB’s Automated Regulatory Intelligence Infrastructure, built on a proprietary expert knowledge graph rather than a large language model. It produces deterministic, closed-loop regulatory outputs: predicate device identification, regulatory pathway analysis, regulatory strategy, and full document authorship across the design history file, risk management file, and twelve additional regulatory documents in the formats eSTAR expects. Smart Vault outputs are built to feed directly into the eSTAR template, with TBD placeholders for the device-specific data points only the manufacturer can supply. 

QualiVerse operates inside an ISO 13485 and ISO 27001 certified environment, which means the documentation it produces is generated under the same quality framework the QMSR now requires. For teams without an established QMS, QualiVerse provides a documented quality framework that can serve as the foundation rather than an afterthought. 

Frequently Asked Questions 

Is eSTAR mandatory for all 510(k) submissions? Yes, with limited exceptions. Since October 1, 2023, all 510(k) submissions must be made through eSTAR unless they fall within the FDA’s narrow waiver and exemption categories. 

Is eSTAR mandatory for De Novo requests? Yes. De Novo classification requests have required eSTAR since October 1, 2025. 

Does eSTAR replace the Refuse to Accept (RTA) review? For eSTAR submissions, the traditional RTA review is largely replaced by built-in validation. The FDA still verifies the accuracy of responses, however, and may place a submission on early hold if structural errors are found. 

Where are eSTAR submissions uploaded? 510(k) and De Novo eSTAR submissions are uploaded through the CDRH Customer Collaboration Portal. CBER-regulated submissions go through the FDA Electronic Submissions Gateway. 

Can an eSTAR submission be edited after signing? No. Once signed as complete, attachments and responses are locked. Additional information can be provided in response to FDA requests, but prior content cannot be changed. 

What software is needed to use eSTAR? A current version of Adobe Acrobat Pro is required for full eSTAR template functionality. 

How often is the eSTAR template updated? The FDA releases new versions every few months. The current version is 6.1, updated in early 2026 to align with the QMSR and updated Real World Evidence guidance. Older versions become obsolete and cannot be uploaded. 

What are the most common reasons eSTAR submissions stall? Cybersecurity documentation gaps in Section Q, weak substantial equivalence rationales, software documentation that is misaligned with verification activities, and risk management files that lack traceability to design decisions. 

Move at the Speed of Innovation 

eSTAR is not a fillable form. It is the FDA’s structured front door to premarket review, and the cost of an unstructured back end has never been higher. The teams moving fastest through review in 2026 are the ones treating eSTAR as a publishing layer, building documentation under an ISO 13485-aligned framework, and resolving traceability gaps before they reach the template. 

To see how QualiVerse® produces eSTAR-ready documentation across the design history file, risk management file, and the rest of the regulatory document set, [request a demo].