IDE Clinical Study Requirements

1. Key takeaways

The Investigational Device Exemption (IDE) is implemented under 21 CFR Part 812 and allows investigational devices to be used in clinical studies to collect the safety and effectiveness data needed to support a PMA application or a 510(k). Not every device requires a clinical study — whether one is needed depends on the pathway: a 510(k) typically relies on comparison evidence against a predicate, while a PMA generally requires clinical data.

• The significant risk / non-significant risk (SR / NSR) dividing line determines the procedural complexity of the study.
• Significant risk studies require both FDA approval and IRB approval; non-significant risk studies require IRB approval only.
• The IDE can serve as the front segment of a PMA program or as the evidence source for a 510(k).
• Where the sponsor cannot determine whether the study is SR or NSR, the Study Risk Determination Q-Sub lets FDA decide.
• PreSTAR is used for the original IDE and its supplements and amendments, but is not applicable to IDE reports.

2. Legal basis

The table below lists the regulations governing the IDE framework, the supporting human-subject protections, and the eSTAR/PreSTAR positioning of the IDE, verified in 2026.

3. Expert insights

Insight 1: The SR / NSR dividing line determines procedural complexity. 21 CFR 812 divides investigations into significant risk (SR) and non-significant risk (NSR) device studies. A significant risk study must obtain both FDA approval and IRB approval, while a non-significant risk study requires IRB approval only. This single distinction drives project time and resource commitments, so the risk determination belongs at the very front of study planning rather than somewhere in the middle of site selection.

Insight 2: The IDE can be the front segment of a PMA program or the evidence source for a 510(k). FDA’s official pages state that the IDE permits investigational devices to be used in clinical studies to collect safety and effectiveness data supporting a PMA application. For 510(k) programs, the IDE also comes into play where the substantial equivalence argument needs supplemental clinical data. Understanding both roles prevents the common error of assuming that clinical work is relevant only to PMA-class programs.

Insight 3: The IDE pairs with the Study Risk Determination Q-Sub. According to the FDA eSTAR Program page, the Q-Sub types include the Study Risk Determination. Where the sponsor cannot determine on its own whether the investigation is SR or NSR, this Q-Sub asks FDA to make the determination. Filing it promptly keeps the study schedule from stalling while the classification question remains open internally.

Insight 4: PreSTAR serves the original IDE but not IDE reports. According to the FDA eSTAR Program page, PreSTAR is used to submit the original IDE and its supplements and amendments, and is not applicable to IDE reports. Report submissions must therefore follow a separate, independently planned route, and assuming PreSTAR covers everything IDE-related is a filing error waiting to happen.

Read as a whole, the IDE framework rewards sponsors who sequence their decisions. The need for clinical data is a pathway question answered before development planning hardens; the SR or NSR determination is a procedural question answered before sites and budgets are fixed; and the submission channels are questions answered before any document is assembled. Each of these answers constrains the next, and reversing the order typically produces rework: studies launched before their risk status is settled, or dossiers built on a submission channel that turns out not to accept them. A short planning sequence, executed in the right order, removes most of the avoidable friction from an IDE program.

4. Practical recommendations

• Determine at project launch whether clinical data are actually needed, judged by the pathway, rather than defaulting to running a study.
• If clinical work is required, make the SR / NSR determination first; where uncertain, file the Q-Sub and ask FDA to determine.
• For significant risk studies, plan the FDA approval line and the IRB approval line in parallel from the outset.
• Use the current PreSTAR version for the original IDE and its supplements and amendments; submit IDE reports through a separately planned route.
• Implement the informed consent requirements of 21 CFR Part 50 and the IRB requirements of 21 CFR Part 56 in step with the study plan.

5. Verification checklist

• □ Determined whether a clinical study is necessary (judged by the marketing pathway).
• □ SR / NSR risk determination completed, or a Q-Sub filed to request the determination.
• □ If the study is SR, FDA and IRB approval processes both initiated.
• □ Original IDE prepared using the current PreSTAR version.
• □ 21 CFR Part 50 informed consent and 21 CFR Part 56 IRB requirements implemented.
• □ IDE report submission route planned separately (PreSTAR not used).
• □ Clinical study decision documented against the chosen pathway, with the rationale retained.

It is also worth remembering that the decision not to run a clinical study is itself a regulatory position that should be documented. Where the pathway comparison evidence is sufficient, stating the basis for that sufficiency in the project record protects the program against later second-guessing and gives reviewers a clear trail if the question resurfaces during review. Equally, where clinical data are required, the study objectives should be written so that each one maps to a specific claim in the eventual premarket submission, which keeps the dataset purpose-built rather than assembled after the fact.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, US Agent and local testing support for the United States market. Our team manages FDA establishment registration and listing, 510(k)/De Novo/PMA submissions, and supports post-market reporting obligations. Business enquiries: info@grzanglobal.com