cms.bioaccessla.com

FDA Q-Submission: What to Send Before Your IDE Filing

Written by

Julio Martinez-Clark

in

A well-prepared FDA Q-Submission can save an IDE program months of back-and-forth with the agency. For MedTech startups operating on a 12–24 month financial runway, that difference is not abstract — it is the gap between hitting an investor milestone and missing it. Understanding what the Q-Submission process requires, and what to include before filing an Investigational Device Exemption (IDE), is one of the most practical investments a sponsor can make at the pre-submission stage.

This article covers what a Q-Submission is, when to use it, what to include in the package, and how to structure the interaction to get substantive FDA feedback rather than a generic acknowledgment.

What Is an FDA Q-Submission?

The Q-Submission program is FDA's formal mechanism for sponsors to request agency feedback before submitting a marketing application or an IDE. It replaced the older Pre-IDE and Pre-Submission meeting request processes and is governed by FDA's guidance on the Q-Submission program for device and radiation-emitting products.

Several subtypes exist, but for early-stage device sponsors, two are most relevant:

  • Pre-Submission (Pre-Sub): A written request for FDA feedback on a specific question, with or without a meeting. This is the workhorse of early IDE strategy.
  • Study Risk Determination: A request for FDA to classify a proposed study as significant risk or non-significant risk before enrollment begins.

When sponsors refer to an "FDA Q-Submission" in the context of IDE preparation, they almost always mean a Pre-Sub. The rest of this article focuses there.

Why File a Pre-Sub Before Your IDE?

Filing a Pre-Sub before an IDE is not required. Skipping it, though, is a common and expensive mistake.

An IDE filed without prior FDA alignment frequently returns with a "Disapproved" or "Approved with Conditions" determination, triggering a response cycle that can run 90 to 180 additional days. For a startup that has already activated sites and begun screening patients, that delay is a capital event.

A Pre-Sub lets sponsors test their clinical protocol design, proposed primary endpoint, statistical analysis plan, and risk classification assumptions against FDA's actual expectations before committing to them in a binding IDE submission. FDA's written feedback becomes part of the regulatory record and can be cited directly in the IDE to demonstrate alignment.

The practical payoff: sponsors who use Pre-Subs strategically tend to file cleaner IDEs, receive fewer major deficiencies, and move through the IDE review cycle faster.

When to File Your Pre-Sub

Timing matters. File too early and there will not be enough data to ask specific questions. File too late and the feedback arrives after the protocol is already locked.

The right window is after design freeze — once there is a defined clinical indication, a draft protocol structure, and at least a preliminary risk analysis. A finalized protocol is not required. Enough specificity to ask answerable questions is.

For a typical first-in-human (FIH) device program, the Pre-Sub should be filed 6 to 9 months before the intended IDE submission. FDA targets a 90-day response for written feedback requests and 70 days for meeting requests. Build those windows into the project plan, not the contingency buffer.

What to Include in Your Pre-Sub Package

This is where most sponsors underinvest. A Pre-Sub package that asks vague questions gets vague answers. The goal is to give FDA enough context to provide specific, citable feedback.

Device Description and Intended Use

Start with a technically precise description of the device: mechanism of action, materials, dimensions where relevant, and the proposed intended use statement. The intended use statement is not a marketing claim — it is a regulatory anchor that defines the scope of the IDE and, eventually, the 510(k) or PMA submission.

If predicate devices exist, identify them here. If they do not, say so explicitly and explain why a De Novo or PMA pathway is more appropriate.

Proposed Clinical Indication

State the specific patient population, the disease or condition being treated or diagnosed, and the clinical setting. Vague indications like "cardiovascular disease" are not useful. "Symptomatic severe mitral regurgitation in patients with NYHA Class III heart failure who are not candidates for open surgical repair" is the level of specificity FDA needs to give meaningful feedback on study design.

Draft Study Design and Protocol Outline

A complete protocol is not required — enough structure to ask specific questions is. Include:

  • Study type (FIH, early feasibility study, or pivotal)
  • Proposed study design (single-arm, randomized, controlled)
  • Primary and secondary endpoints
  • Sample size rationale, even if preliminary
  • Proposed follow-up duration
  • Key inclusion and exclusion criteria

For FIH and early feasibility studies, FDA generally expects a more flexible design with a focus on safety endpoints and a stopping rule framework. Spell out stopping rules explicitly — FDA reviewers look for them.

Risk Analysis Summary

Include a summary of the risk analysis, not the full document. Identify the top 5 to 10 device-related risks, severity and probability estimates, and the mitigations in place. Reference the applicable standard — ISO 14971 is the benchmark for device risk management.

If a Study Risk Determination is being requested, this section is the core of the submission. FDA will use it to assess whether the study qualifies as non-significant risk, which determines whether a full IDE is required at all.

Proposed Regulatory Pathway

State the intended US regulatory pathway clearly: IDE leading to 510(k), De Novo, PMA, or Humanitarian Device Exemption (HDE). If there is genuine uncertainty between pathways, say so and ask FDA directly. That is exactly the kind of question a Pre-Sub is designed to answer.

Your Specific Questions

This is the most important section of the package — and the most frequently mishandled. Do not submit open-ended questions like "What does FDA think of our study design?" Submit numbered, specific questions that FDA can answer with a yes, a no, or a defined condition.

Examples of well-formed Pre-Sub questions:

  • "Does FDA agree that the proposed primary safety endpoint of freedom from device-related serious adverse events at 30 days is appropriate for an early feasibility study of [Device Name]?"
  • "Does FDA agree that a proposed sample size of 10 subjects is adequate for an early feasibility study intended to characterize safety and preliminary performance?"
  • "Does FDA consider [Device Name] to be a significant risk device under 21 CFR 812.3(m), given the risk analysis summary in Section 4?"

Each question should be answerable in isolation. If FDA responds to question 3 but not question 2, the program should still be able to move forward on question 3.

Common Pre-Sub Mistakes That Delay IDE Filings

Submitting Without a Defined Regulatory Pathway

Sponsors sometimes file a Pre-Sub while still undecided between a 510(k) and a PMA pathway. FDA cannot give useful feedback on clinical study design if the evidentiary standard is undefined. Commit to a pathway before filing — or explicitly ask FDA to help choose between two specific options.

Asking Too Many Questions

FDA reviewers have limited time. A Pre-Sub with 15 questions is less likely to receive thorough responses than one with 5 focused questions. Prioritize questions where FDA disagreement would force a redesign of the study. Secondary questions can wait for a follow-up Pre-Sub or an IDE deficiency response.

Conflating OUS Data with IDE Exemption

Sponsors running early feasibility studies outside the United States sometimes assume that OUS data eliminates the need for an IDE. It does not. If OUS clinical data will be used to support a US IDE or marketing application, that data must be collected under standards FDA will accept — specifically ISO 14155 and structured per FDA 21 CFR 812.28. This is a critical point to address in the Pre-Sub if OUS data is part of the strategy.

Underestimating Meeting Preparation

If a meeting is requested alongside written feedback, the presentation should not simply repeat the submission package. Use the meeting to clarify ambiguous feedback, explore scenarios FDA raised in writing, and confirm understanding of any conditions. Bring clinical, regulatory, and statistical leads. FDA reviewers notice when a sponsor team is disorganized.

How OUS Early Clinical Data Fits Into Your Pre-Sub Strategy

For sponsors running first-in-human studies in Latin America before filing a US IDE, the Pre-Sub is the right place to establish FDA's acceptance of that data strategy.

Specifically, written confirmation is needed that:

  1. Data collected under ISO 14155 and structured per FDA 21 CFR 812.28 at OUS sites will be considered for the IDE application.
  2. The proposed OUS study design is consistent with the evidentiary requirements for the intended US pathway.
  3. FDA does not object to the proposed OUS countries or sites as the source of primary safety data.

Getting that confirmation before enrollment begins in Panama, Colombia, or Chile removes a significant risk from the program. It also gives the board and investors documented FDA alignment — which matters at Series A and beyond.

The enVVeno Medical program illustrates this well: early-stage OUS work in Latin America built the clinical foundation that ultimately supported the first-ever FDA IDE for a non-surgical replacement venous valve in 2026. The Cook Group's multi-site first-in-human artificial venous valve study in Colombia involved 142 or more INVIMA regulatory submissions managed in-country — the kind of regulatory depth that produces FDA-submissible data packages, not just local approvals.

The Pre-Sub to IDE Sequence in Practice

A well-run Pre-Sub to IDE sequence looks roughly like this:

  1. Design freeze completed; clinical indication defined
  2. Pre-Sub package drafted with specific questions on study design, risk classification, and regulatory pathway
  3. Pre-Sub submitted to FDA (Q-Sub number assigned within 15 days)
  4. FDA written feedback received (target: 70–90 days)
  5. Protocol finalized incorporating FDA feedback
  6. IDE package assembled: protocol, investigator brochure, risk analysis, informed consent template, clinical monitoring plan, device description, manufacturing information
  7. IDE submitted; FDA review clock begins (30 days for non-significant risk, up to 180 days for significant risk with deficiency cycles)

The Pre-Sub feedback from step 4 does not just inform step 5 — it becomes an exhibit in the IDE filing, demonstrating to the IDE reviewer that the study design was developed in dialogue with FDA. That alignment reduces the probability of a major deficiency.

For sponsors running OUS early feasibility studies in parallel, the same Pre-Sub package should address the data-bridging question explicitly. If Latin American FIH data will be submitted as part of the IDE, FDA needs to know that before the first patient is enrolled, not after.

What FDA Looks for in a Strong Pre-Sub Package

FDA reviewers are evaluating whether a sponsor understands the device, the patient population, and the evidentiary standard for the intended pathway. A strong package demonstrates:

  • Technical precision in the device description
  • A realistic risk profile that does not minimize known failure modes
  • A study design appropriately sized for the study type — FIH studies are not pivotal trials
  • Questions specific enough to generate actionable answers
  • Awareness of applicable standards: ISO 14971, ISO 14155, ICH E6 for drug-device combinations

A weak package reads as if the sponsor is asking FDA to design the study for them. That is not what the Pre-Sub program is for. FDA's role is to react to a specific proposal, not to generate one.

Connecting Pre-Sub Strategy to Your FIH Execution Plan

The Pre-Sub is a regulatory milestone, but it sits inside a larger operational sequence. For startups moving from IDE-readiness to first-in-human enrollment, the clinical operations infrastructure — site selection, Ethics Committee (EC) approval, patient recruitment, data management — needs to be in motion before the IDE is filed, not after it is approved.

In markets like Panama, El Salvador, Chile, and the Dominican Republic, ethics and regulatory approvals have been observed in 30 to 90 days, which means site activation can begin while the IDE review is still in progress. That parallel-path execution is only possible if OUS data collection standards are already aligned with FDA expectations — which is exactly what the Pre-Sub is designed to confirm.

The i-Lumen Scientific retinal therapy program demonstrates how early regulatory alignment in Latin America feeds directly into a US submission strategy. Sponsors who treat the Pre-Sub as an isolated regulatory task rather than the first step in a coordinated FIH execution plan tend to lose the time advantage that OUS execution is supposed to provide.

bioaccess® anchors FDA strategy from the first workstream of every FIH-12™ engagement. The Pre-Sub questions, the OUS study design, and the IDE submission package are built as a single coherent evidence strategy — not assembled retroactively.

Frequently Asked Questions

What is an FDA Q-Submission and how does it differ from an IDE?
A Q-Submission is a request for FDA feedback before a formal submission. A Pre-Submission (Pre-Sub) is the most common type, allowing sponsors to ask specific questions about study design, risk classification, or regulatory pathway before filing an IDE. An IDE is the formal application to begin a clinical investigation of a significant risk device in the United States. The Pre-Sub informs the IDE; the IDE authorizes the study.

How long does it take to get a response to a Pre-Sub?
FDA targets 70 days for meeting requests and 90 days for written-feedback-only requests. These are FDA performance targets, not statutory deadlines. Build the full 90-day window into the project timeline rather than assuming a faster response.

Do I need a finalized protocol to file a Pre-Sub?
No. A draft protocol outline with defined endpoints, sample size rationale, and key inclusion and exclusion criteria is sufficient. The goal is to give FDA enough specificity to answer the questions asked — not to lock every protocol detail before receiving feedback.

Can OUS clinical data collected in Latin America be used to support a US IDE?
Yes, if the data is collected under ISO 14155 and structured per FDA 21 CFR 812.28. The Pre-Sub is the right place to confirm FDA's acceptance of an OUS data strategy before enrollment begins. Getting that confirmation in writing protects the program if questions arise later in the IDE review.

What happens if FDA disagrees with the proposed study design in the Pre-Sub response?
FDA's feedback is not binding, but disagreement is a strong signal that the IDE will face a deficiency on the same point. Use the Pre-Sub response to revise the design before filing. If the concern appears to be based on a misunderstanding, a follow-up meeting can clarify the issue before the IDE is submitted.

How many questions should a Pre-Sub include?
Aim for 4 to 6 specific, answerable questions. More than that risks diluted responses. Prioritize questions where FDA disagreement would require a material change to the study design or regulatory pathway.

Is a Pre-Sub required before filing an IDE?
No. But for first-in-human and early feasibility studies — particularly those incorporating OUS data — it is strongly advisable. Sponsors who skip the Pre-Sub and file directly into an IDE review cycle often encounter deficiencies that a Pre-Sub would have surfaced and resolved in advance.

The Pre-Sub is not paperwork. It is the first substantive conversation a sponsor will have with FDA about the device, and the quality of that conversation shapes everything that follows. Invest in the package, ask specific questions, and use the feedback to build an IDE that reviewers recognize as the product of a well-organized sponsor team.

For sponsors planning to run first-in-human studies in Latin America as part of their IDE strategy, learn more about how bioaccess® structures FDA alignment from day one at bioaccessla.com.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

More posts