How to Write Section 4 of an FDA eSTAR: Predicate Device Comparison

FDA's eSTAR (electronic Submission Template and Resource) replaced the traditional 510(k) format in 2023. Section 4 — Substantial Equivalence Comparison — is the heart of every eSTAR submission. It's where you make the legal case that your device is as safe and effective as the predicate you've chosen.

A well-written Section 4 anticipates FDA's questions before they're asked. A poorly written one generates a cycle of Additional Information (AI) requests that can add six months or more to your review timeline.

What Section 4 must contain

The eSTAR template structures Section 4 into three subsections:

1. 4.1 Predicate Device Identification — K-number, device name, applicant, clearance date, and a statement that the predicate is legally marketed in the US
2. 4.2 Intended Use Comparison — a side-by-side comparison of your device's intended use and the predicate's cleared intended use
3. 4.3 Technological Characteristics Comparison — a feature-by-feature comparison table identifying similarities and differences, with explanations for each difference

Each subsection has required fields in the eSTAR form. But the form is a minimum — the actual argument is built in the supporting documentation you attach.

4.1 — Getting predicate identification right

This seems straightforward but applicants make errors that slow review. Always verify:

• The K-number matches the device name — FDA's database has duplicates and near-matches
• The predicate has a "Substantially Equivalent" decision — not "Not Substantially Equivalent" or a withdrawn submission
• The predicate is still legally marketed — a recalled or discontinued device is still a valid predicate, but note this explicitly
• If using multiple predicates, list all of them and specify which supports intended use and which supports technological characteristics

4.2 — Intended use comparison: precision over persuasion

The intended use comparison is not a marketing exercise. You are not trying to convince FDA your device is better than the predicate — you are demonstrating it serves the same medical purpose.

Present the comparison as a two-column table: your device's intended use on one side, the predicate's cleared intended use (verbatim from the 510(k) summary) on the other. Then write a brief narrative explaining any differences and why they don't constitute a change in intended use.

Common mistakes in 4.2:

• Using marketing language ("superior accuracy," "next-generation") instead of regulatory language
• Quoting the predicate's website rather than its cleared 510(k) summary — these are often different
• Failing to address scope differences — if your device has a narrower indication, say so explicitly and explain why that doesn't affect equivalence
• Not acknowledging that the predicate's intended use language was updated in a subsequent 510(k) — always reference the specific K-number you're comparing against

4.3 — The technological comparison table

This is the section that determines whether FDA requires performance data. The comparison table should include every feature that could affect safety or effectiveness — not just the ones that are the same.

For each feature, you must state:

1. Whether it's the same, similar, or different compared to the predicate
2. If different, whether the difference raises a new question of safety or effectiveness
3. If it raises a new question, what data (bench, animal, clinical) addresses it — with a cross-reference to the relevant section of the submission

Features to include in a typical comparison table: materials (contact and non-contact), energy source or mechanism of action, design geometry, software (if any), sterility, single-use vs reusable, environmental conditions of use, user population, and any accessories or components.

Handling differences that raise new questions

When a technological difference does raise a new question of safety or effectiveness, the response is not to minimize the difference — it's to provide data that answers the question.

FDA reviewers are experienced. Arguing that a clearly novel material "does not raise new questions" without supporting data will generate an AI request asking for biocompatibility testing. Better to acknowledge the difference, cite the testing you've conducted, and cross-reference the results in your submission.

The language that works: "The use of [new material] differs from the predicate. This difference was evaluated through ISO 10993-1 biocompatibility assessment. Results are provided in Section 7.3 and demonstrate that the material is biocompatible for the intended contact duration and tissue type."

Preparing Section 4 before you write it

The comparison table in Section 4 is best built as a standalone document before you start the eSTAR. List every feature of your device, compare each to the predicate, and assess each difference for safety implications. This exercise will determine your testing plan — which means it should happen before testing, not after.

Regulatory consultants who use predicate research tools to review multiple cleared devices in the same product code — understanding what features FDA has accepted for each variant — build more defensible Section 4 comparisons than those who look at a single predicate in isolation.