Blog

An FDA Pre-Sub meeting is a voluntary Q-Submission interaction that gives medical device sponsors non-binding written feedback before a marketing submission. Submitting a well-structured package with focused questions can save 6 to 18 months of development time, and the FDA targets a written response within 75 days of receipt. That window's value depends almost entirely on how the request package is prepared. Sponsors who treat the Pre-Sub as a formality, submitting vague questions or incomplete context, get hedged answers that move nothing forward. This guide covers how to prepare a focused package and write questions that produce specific, actionable answers.

What Is an FDA Pre-Sub Meeting and Why Does It Matter?

The Pre-Submission program is a formal channel through which medical device and combination product sponsors can request written feedback from the FDA before filing a 510(k), PMA, De Novo, or IDE application. The agency reviews the package, consults internally, and issues a written response. Sponsors may also request a meeting to discuss that response directly with the review team.

The program is voluntary. No regulation requires a sponsor to file a Pre-Sub before submitting a marketing application. The practical case for using it is strong, though: early clarity on testing requirements, regulatory classification, and clinical study design can prevent sponsors from generating 6 to 18 months of data the agency will not accept.

The Q-Submission program covers several distinct interaction types, and choosing the right one matters.

Pre-Submission (Pre-Sub) is the most commonly used format. It allows sponsors to ask broad questions about regulatory strategy, bench testing protocols, clinical study design, and software documentation requirements. The FDA provides formal written feedback and, when requested, schedules a meeting with the relevant review division. Feedback is advisory; it is not legally binding on the agency.

Study Risk Determination (SRD) is a narrower format with a faster turnaround. Sponsors use it to ask a single focused question: does the FDA consider the planned clinical study to be significant risk, nonsignificant risk, or exempt? That determination controls whether the sponsor needs a full Investigational Device Exemption (IDE) application or only Institutional Review Board (IRB) oversight. Because the SRD's scope is limited, the FDA can process it more quickly than a full Pre-Sub.

Other Q-Sub types include the Submission Issue Request (SIR), used to resolve a specific deficiency in a pending submission, and informational meetings, which allow sponsors to brief the agency on a technology without asking formal questions.

Most early-stage sponsors preparing for a first-in-human (FIH) study or an IDE application will use the Pre-Sub as their primary tool. The SRD is a useful complement when the risk classification of a planned study is genuinely uncertain. Knowing which format fits your situation before drafting a single question saves time and shapes the entire preparation process.

The FDA's pre-submission guidance, published and updated by the Center for Devices and Radiological Health (CDRH), describes the program's procedures, content expectations, and response commitments in detail. That document is the authoritative reference; this guide translates its requirements into a practical preparation sequence.

How Does the FDA Pre-Sub Meeting Timeline Work?

The FDA targets scheduling a Pre-Sub meeting within 75 days of receipt and typically confirms the meeting date within 15 days of receiving the request. That 75-day window is a target, not a contractual guarantee. Review division workloads, submission volume, and the complexity of the questions submitted can all affect the actual timeline.

For planning purposes, treat 75 days as the expected minimum from submission to meeting. Add time for internal preparation, package assembly, and any back-and-forth with the FDA's document receipt staff, and the realistic horizon from decision to meeting is closer to three to four months.

The sequence runs as follows. The sponsor submits the Pre-Sub package through the FDA Q-Submission portal. The agency acknowledges receipt and assigns a tracking number. Within approximately 15 days of receipt, the review division confirms a meeting date within the 75-day target window, which is the same target cited above. The FDA then prepares its written response, which the sponsor receives before the meeting so there is time to review it and prepare follow-up discussion points. The meeting itself, which can be held online, by teleconference, or in person, typically runs 60 to 90 minutes.

For an online FDA Pre-Sub meeting, the FDA uses its standard teleconference infrastructure. Sponsors do not need to travel to Silver Spring. The agency has conducted the majority of Pre-Sub meetings virtually since 2020, and that format is now standard practice.

If the FDA does not hold a meeting within the target window, sponsors can follow up through the review division's project manager. The agency's written response still carries value even without a live meeting, and sponsors should plan to act on the written feedback regardless of whether a meeting occurs.

One practical implication: if your IDE application or 510(k) submission has a hard internal deadline, work backward from that date. A Pre-Sub submitted too late to receive a response before your submission window closes provides limited benefit. Build the Pre-Sub into your development calendar at least five to six months before your planned marketing or IDE submission date.

Step-by-Step: How to Prepare Your FDA Pre-Sub Package

A complete Pre-Sub package gives the FDA enough context to answer your questions accurately and enough specificity to make those answers actionable. The steps below follow the order in which sponsors should build the package, from device description through final formatting.

1. Describe the device's mechanism of action and current development status. Start with a concise summary of what the device does, how it works, and where it stands in development. Include the intended use, the target patient population, and the current prototype or design iteration. This section orients the review team before they reach your questions [S5].

2. Detail the regulatory history and proposed classification pathway. State the device's proposed product code, predicate device (if applicable), and the regulatory pathway you intend to pursue: 510(k), De Novo, PMA, or IDE. If the device has any prior FDA interaction history, summarize it here [S4].

3. Draft a numbered list of specific questions focused on no more than four major topics. Each question should be answerable on its own, without requiring the reviewer to infer context from elsewhere in the package. Group related questions under a topic heading. Limit the total question count to the range the FDA finds workable, and keep each question to a single issue. Compound questions ("Is our bench testing adequate, and if not, what additional testing would you recommend?") are harder for reviewers to answer cleanly and often produce partial responses [S3].

4. Include draft protocols and bench testing data to provide context. If you are asking about the adequacy of a test protocol, include the draft protocol. If you are asking whether your bench data supports a particular claim, include the data. The FDA cannot evaluate what it cannot see. Attaching supporting data does not commit you to that protocol; it gives the agency something concrete to respond to rather than answering in hypotheticals [S2].

5. Propose at least three potential meeting dates 60 to 75 days in the future. This step is administrative but affects scheduling. Offering a range of dates in the correct window prevents delays caused by the FDA having to request alternatives. Place the proposed dates in the cover letter or the meeting request section of the package, clearly labeled [S1].

6. Package the submission using the eCopy format or the eSTAR electronic template. The FDA accepts Pre-Sub packages in eCopy format, which follows CDRH's electronic submission guidance. Some sponsors also use the eSTAR electronic template, an interactive tool that guides users through the data and documentation fields required for FDA submissions and helps ensure the package meets acceptance criteria. The eSTAR template is appropriate for Pre-Submissions and marketing submissions such as 510(k)s, but it is not required for all Pre-Sub packages. Confirm the current format requirements in the FDA's pre-submission guidance before finalizing the package. Submit through the FDA Q-Submission portal, which is the agency's standard electronic gateway for Q-Sub interactions [S6].

A package built in this sequence gives the review team a clear picture of the device, a defined regulatory context, and a focused set of questions they can answer with specificity. The goal is not to impress the FDA with documentation volume. It is to make their job easy enough that the written response addresses exactly what you need to know.

How Do You Write FDA Pre-Sub Meeting Questions That Get Useful Answers?

The quality of the FDA's written response depends directly on the quality of the questions you submit. Vague or overly broad questions produce hedged answers that leave sponsors no better informed than before the submission.

The FDA suggests limiting a Pre-Sub request to no more than four major topics and a maximum of 7 to 10 questions total. That constraint is not arbitrary. Reviewers across multiple FDA divisions coordinate to prepare a single written response, and a package with 20 questions spread across six topics forces that coordination to break down. The result is a response that addresses some questions thoroughly and others only in passing. Staying within the suggested range keeps the review team focused and increases the likelihood that every question receives a substantive answer.

Topic scoping comes before question drafting. Before writing a single question, identify the four decisions in your development program that carry the most regulatory risk. Common candidates include: the adequacy of your bench testing protocol for a specific performance claim, the clinical study design and patient population for an IDE application, the predicate device strategy for a 510(k), and the software documentation requirements for a device with a software component. Once those four topics are fixed, every question should map to one of them. Questions that fall outside the four topics get cut or saved for a subsequent Pre-Sub.

Phrasing determines whether a question is answerable. The FDA cannot respond usefully to a question that asks for a general opinion. Compare these two versions:

Unproductive: "Does the FDA have any concerns with our device?"

Productive: "Does the proposed bench testing protocol in Attachment B, specifically the fatigue testing methodology described in Section 3.2, meet the performance testing requirements for a Class II cardiovascular device under product code DQO?"

The first version gives the reviewer nothing to anchor a response to. The second names a specific document, a specific section, a specific product code, and a specific regulatory standard. The reviewer can either confirm adequacy, identify gaps, or recommend an alternative standard. All three outcomes are actionable.

A few additional practices improve question quality. First, write each question so it stands alone. The reviewer should not need to read three paragraphs of background text to understand what is being asked. Second, avoid compound questions. If you need answers to two related issues, write two separate questions. Third, where your question involves a protocol or dataset, reference the attachment by name and section number in the question itself. That cross-reference prevents the reviewer from answering in hypotheticals.

Questions about clinical study design benefit from one additional element: state the study population, the primary endpoint, and the follow-up duration in the question body, not just in the attached protocol. Reviewers who can see the key parameters without leaving the question page tend to give more precise answers about what the FDA will and will not accept.

One category of question to avoid entirely is the approval-seeking question. Asking "Will the FDA clear our device if we complete this testing?" is not something the Pre-Sub program can answer. The program provides non-binding feedback on strategy and methodology. It does not pre-authorize a submission outcome. Framing questions around what the agency will accept, rather than what it will guarantee, keeps the interaction within the program's actual scope.

What Should You Do Before, During, and After the FDA Pre-Sub Meeting?

The written response the FDA sends before the meeting is the core deliverable of the Pre-Sub process. The meeting itself is an opportunity to clarify that response, not a substitute for it.

**Before the meeting, ** read the written response carefully and identify any answer that is conditional, incomplete, or uses language that could be read more than one way. Prepare a short list of clarifying questions for each ambiguous point. Share the response with your regulatory counsel, your principal investigator if a clinical study is involved, and any engineering leads whose work is directly addressed. The meeting runs 60 to 90 minutes, and that time goes quickly. Arriving without a prepared agenda wastes it.

Also confirm the logistics. An online FDA Pre-Sub meeting uses the agency's standard teleconference platform. The FDA project manager assigned to your submission will send connection details in advance. Test the connection before the meeting day. Designate one person on your team as the primary speaker for each topic area so the discussion does not stall on internal coordination during the call.

**During the meeting, ** take verbatim notes or record the session with the FDA's permission. The written response is the official record, but the meeting discussion often adds context that the written document does not capture. Note any point where an FDA reviewer qualifies or expands on the written answer. If the FDA raises a concern that was not addressed in your questions, ask whether it can be addressed in a follow-up Q-Sub rather than trying to resolve it on the spot.

Do not treat the meeting as a negotiation. The FDA's feedback is non-binding, and the agency is not in a position to commit to a clearance or approval outcome during a Pre-Sub discussion. The goal is clarity, not agreement.

**After the meeting, ** update your development plan to reflect the FDA's written answers and any clarifications from the discussion. Document which questions received clear answers, which received conditional answers, and which remain open. Open items should drive the agenda for any follow-up Pre-Sub or SRD. If the FDA's response contradicts an assumption that was built into your testing plan or clinical protocol, revise those documents before proceeding. Acting on feedback promptly is what keeps the development program on track and prevents the rework that stalls submissions.

Pre-Sub Question and Package Checklist

Use this checklist to audit your Pre-Sub package before submission. A package that clears every item gives the FDA the context it needs to provide specific, actionable written feedback.

Device description and development status

• Concise description of the device's mechanism of action and intended use
• Current development stage (concept, prototype, bench-tested, etc.)
• Target patient population and clinical indication
• Investigational device disclaimer included where applicable

Regulatory history and pathway

• Proposed product code and device classification
• Intended regulatory pathway: 510(k), De Novo, PMA, or IDE
• Summary of any prior FDA interactions, submissions, or correspondence
• Predicate device identified (for 510(k) submissions)

Questions

• No more than four major topic areas, with a total of 7 to 10 questions across them
• Total question count within the 7 to 10 question range
• Each question is numbered and maps to a single topic
• Each question is self-contained and does not require surrounding context to interpret
• No compound questions (one issue per question)
• Supporting attachments referenced by name and section number within each relevant question
• No approval-seeking questions that fall outside the Pre-Sub program's scope

Supporting documentation

• Draft bench testing protocols attached for any question about testing adequacy
• Relevant bench data included where the question concerns data sufficiency
• Draft clinical protocol attached if questions address study design or patient population

Meeting request and logistics

• At least three proposed meeting dates, each 60 to 75 days from the planned submission date
• Preferred meeting format stated (online teleconference is standard)
• Primary contact name and information included

Package format

• Submission formatted as an eCopy or using the eSTAR electronic template per current CDRH guidance
• Cover letter includes the Q-Sub request type (Pre-Sub, SRD, or other) and a brief statement of the program's purpose
• Package submitted through the FDA Q-Submission portal

When Does It Make Sense to Use a CRO for FDA Pre-Sub and IDE Pathway Alignment?

Sponsors with in-house regulatory affairs staff experienced in CDRH submissions can often manage Pre-Sub preparation internally. The process is documented, the format is defined, and the FDA's pre-submission guidance spells out what the agency expects. If your team has prepared Pre-Subs before and understands how to scope questions for a specific review division, the internal route is reasonable.

The case for outside support is stronger when the device is novel, the regulatory pathway is genuinely uncertain, or the sponsor is simultaneously managing IDE pathway planning alongside the Pre-Sub. A first-in-human study adds clinical protocol development, study risk determination, and site selection to the workload at the same time the Pre-Sub package is being built. Running those workstreams in parallel without dedicated regulatory and clinical operations experience is where programs lose months, not days.

bioaccess® drafts Pre-Sub questions aligned with the IDE strategy and structures the supporting documentation to produce answers the development team can act on. That coordination matters most when the Pre-Sub questions directly affect the clinical protocol, which is common in FIH programs where bench data and early clinical design are developed together.

bioaccess® is a Miami-headquartered CRO serving MedTech, biopharma, and radiopharma sponsors. Its FIH-12™ program covers FDA Pre-Sub and IDE/IND pathway alignment as part of a nine-workstream, 12-month engagement that runs from initial regulatory strategy through delivery of a submission-ready clinical evidence package. For sponsors who need Pre-Sub preparation integrated with protocol development and site activation, that end-to-end structure removes the coordination burden from an internal team that may not yet have the bandwidth to carry it.

If your team does not have the regulatory depth or bandwidth to prepare a focused Pre-Sub package while advancing the rest of the development program, contact bioaccess® to discuss your pathway and what a structured Pre-Sub and IDE engagement would cover.

Prices and plan limits verified as of October 2026.

FAQs

What is the difference between a Pre-Sub and a Q-Submission?

A Q-Submission is the umbrella program the FDA uses for all pre-submission interactions, including Pre-Subs, Study Risk Determinations, Submission Issue Requests, and informational meetings. A Pre-Submission, or Pre-Sub, is one specific type of Q-Sub. When sponsors say they are filing a Pre-Sub, they mean a Q-Submission request for formal written feedback and, optionally, a meeting with the relevant FDA review division before filing a marketing or IDE application.

Is a Pre-Sub meeting required before submitting a 510(k) or PMA?

No. The Pre-Submission program is voluntary. No regulation requires a sponsor to file a Pre-Sub before submitting a 510(k), PMA, De Novo, or IDE application. Sponsors choose to use it because early written feedback on testing requirements, regulatory classification, and clinical study design can prevent costly rework later in the development program.

Can a Pre-Sub meeting be held virtually or online?

Yes. The FDA has conducted the majority of Pre-Sub meetings by teleconference since 2020, and virtual meetings are now standard practice. Sponsors do not need to travel to the FDA's Silver Spring campus. The agency's project manager assigned to the submission sends connection details in advance. Sponsors should confirm the format preference in the meeting request section of the Pre-Sub package.

What happens if the FDA does not respond within 75 days?

The 75-day window is a target, not a contractual guarantee. If the FDA has not confirmed a meeting date or provided a written response within that window, the sponsor can follow up through the review division's assigned project manager. The written response remains the primary deliverable even if a meeting is delayed, and sponsors should plan to act on it regardless of whether the live meeting occurs on schedule.

How many questions can you ask in a single Pre-Sub request?

Keeping the question list to four major topics and a focused set of questions per topic is the single most effective way to get complete written answers. Questions that fall outside the four core topics are better saved for a follow-up Pre-Sub rather than added to the current package.

Conclusion

An FDA Pre-Sub meeting gives sponsors non-binding written feedback that can redirect a development program before months of work are committed to a path the agency will not accept. The 75-day response target is a planning asset, but only if the package that triggers it is specific and focused enough to produce answers the team can act on.

Start by identifying the four regulatory decisions in your program that carry the most risk, then build every question around those topics. Assemble the supporting documentation before you draft the questions, not after. If your team is also managing IDE pathway planning or clinical protocol development at the same time, consider whether outside regulatory and clinical operations support would protect more development time than it costs.

• What Each Pathway Covers
  • IDE: The Medical Device Route
  • IND: The Drug and Biologic Route
• The Risk-Tier Fork: A Key Difference in the Device Pathway
• Review Timelines and the 30-Day Default
• Downstream Marketing Pathways: Why the Starting Point Matters
• When Both an IDE and an IND Apply
• When an IDE Is Not Required
• How This Decision Affects Your FIH Strategy in Latin America
• Making the IDE vs IND Decision: A Practical Framework
• FAQs
• Conclusion

If you are building a medical device and preparing for first-in-human testing, one of the earliest regulatory decisions you face is whether your clinical program falls under an Investigational Device Exemption (IDE) or an Investigational New Drug (IND) application. The IDE vs IND question shapes everything downstream: which FDA center reviews your submission, how long that review takes, what risk classification applies, and which marketing pathway you are ultimately building toward.

Getting this wrong early is costly. Sponsors who structure their clinical evidence under the wrong framework can face submission rejections, protocol redesigns, or data packages that do not support their intended U.S. clearance or approval pathway. This article explains the core differences between IDE and IND, walks through the decision logic, and covers the scenarios where both apply simultaneously.

---

What Each Pathway Covers

IDE: The Medical Device Route

An IDE allows a medical device that has not yet received FDA clearance or approval to be used in a clinical study on human subjects. As ora.research.ucla.edu noted in its 2021 report, a medical device is considered investigational if it is not approved for marketing in the U.S. or is being clinically evaluated for a new indication. The IDE framework is governed by 21 CFR Part 812 and reviewed by the Center for Devices and Radiological Health (CDRH).

The IDE pathway exists to generate the clinical evidence a sponsor needs to support a downstream 510(k), De Novo, PMA, or Humanitarian Device Exemption (HDE) submission. The clinical data collected under an IDE is the foundation for those marketing applications.

IND: The Drug and Biologic Route

An IND application covers investigational drugs, biologics, and certain gene therapies. It is governed by 21 CFR Part 312 and reviewed by either the Center for Drug Evaluation and Research (CDER) or the Center for Biologics Evaluation and Research (CBER), depending on the product type. Radiopharmaceuticals, for example, typically fall under CDER or CBER depending on their intended use and mechanism.

The IND pathway leads downstream to a New Drug Application (NDA) or Biologics License Application (BLA). Clinical development is phase-based: Phase 1 for safety and dose-finding, Phase 2 for efficacy signals, Phase 3 for pivotal evidence.

---

The Risk-Tier Fork: A Key Difference in the Device Pathway

One of the most consequential distinctions between IDE and IND is the risk-tiering step that exists only in the device pathway. According to CASRAI, the medical device pathway requires a classification of significant-risk (SR) or non-significant-risk (NSR) — a step with no equivalent in the drug pathway.

This classification determines how much FDA oversight your study carries.

Significant-Risk (SR) devices require a full IDE application submitted to and approved by FDA before the study begins. SR devices are those that present a potential for serious risk to health, safety, or welfare — implantable devices, devices that support or sustain human life, and devices used in diagnosing or treating serious conditions all fall into this category.

Non-Significant-Risk (NSR) devices do not require a formal IDE submission to FDA. Instead, the sponsor obtains approval from an Institutional Review Board (IRB) or Ethics Committee (EC) and proceeds under an abbreviated IDE. Informed consent, proper labeling, and study monitoring are still required — but the FDA review step is replaced by IRB oversight.

This fork matters enormously for startup planning. An NSR determination can compress your pre-study timeline substantially. An SR determination puts you in a formal FDA review cycle before a single patient is enrolled.

---

Review Timelines and the 30-Day Default

For IND applications, CASRAI notes that FDA uses a 30-day default review period, after which a sponsor may proceed unless a clinical hold is issued. If FDA does not respond within 30 days, the sponsor is cleared to begin the study.

The IDE review process works differently. FDA has 30 days to review an IDE application, but for SR devices, FDA must affirmatively approve the IDE before the study begins. There is no default-to-proceed mechanism for a full IDE. That distinction is operationally significant: an IND sponsor can plan around a 30-day window with reasonable confidence, while an IDE sponsor for an SR device must wait for explicit approval.

Both pathways also require IRB or EC approval at the site level, running in parallel to the FDA review. In the U.S., that parallel process can add weeks to months depending on the institution.

---

Downstream Marketing Pathways: Why the Starting Point Matters

The pathway you enter at the investigational stage determines the marketing application you will file later. This is not a technicality — it defines the evidence standard your clinical data must meet from day one.

Starting Pathway	Governing Regulation	Reviewing Center	Downstream Application
IDE	21 CFR Part 812	CDRH	510(k), De Novo, PMA, HDE
IND	21 CFR Part 312	CDER or CBER	NDA, BLA

If you are a device company pursuing a 510(k) or PMA, your clinical data must be structured under the IDE framework and ISO 14155 to be accepted in that submission. Data collected under an IND structure will not substitute for IDE-governed device evidence in a CDRH review. The reverse is equally true.

This is why regulatory strategy alignment at the Pre-Sub stage is not optional. The FDA's Pre-Submission (Q-Sub) program exists precisely to resolve pathway questions before a sponsor commits resources to a clinical program.

---

When Both an IDE and an IND Apply

Combination products — those that combine a device component with a drug or biologic component — can require both an IDE and an IND. Drug-eluting stents, implantable drug delivery systems, and devices incorporating a biologic agent are all examples where both frameworks may apply.

In these cases, FDA assigns a primary mode of action (PMOA) to determine the lead reviewing center. If the device function is primary, CDRH leads. If the drug or biologic function is primary, CDER or CBER leads. The non-lead center still reviews the submission, but the lead center sets the standards and timelines.

Radiopharmaceutical developers face a version of this complexity. Compounds like Lu-177, Ac-225, and Ga-68 involve both a device delivery mechanism and a drug or biologic component, which means the regulatory strategy must account for both centers from the outset.

---

When an IDE Is Not Required

Not every device study requires an IDE. FDA exempts certain categories of device studies from the IDE requirement entirely:

• Studies of devices that are already legally marketed, when the study is not intended to determine safety or effectiveness for a new indication
• Diagnostic device studies that meet specific criteria, including no significant risk to subjects and use of cleared devices within their labeled indications
• Consumer preference studies that do not involve any risk to subjects
• Studies involving devices exempt under 21 CFR 812.2(c)

Whether your study qualifies for an exemption is part of the Pre-Sub conversation with FDA. Sponsors who assume an exemption applies without confirming it are exposed to significant compliance risk.

---

How This Decision Affects Your FIH Strategy in Latin America

For MedTech startups running first-in-human studies outside the U.S., the IDE vs IND determination has direct implications for how clinical data is structured and whether it will be accepted in a U.S. submission.

Data collected under ISO 14155 and structured per FDA 21 CFR 812.28 is accepted for U.S. IDE and IND submissions when properly structured. That qualifier matters. A study run in Panama, Colombia, or Chile under a CRO that does not anchor its protocol architecture to the sponsor's U.S. regulatory pathway will generate data that may not survive CDRH or CDER review.

bioaccess® anchors every FIH program to the sponsor's intended U.S. pathway from day one. Whether that pathway is IDE toward a PMA, IND toward a BLA, or a combination product strategy, the FIH-12™ program structures the protocol, data collection, and evidence package to meet the applicable FDA standard. FDA Pre-Sub and pathway alignment is the first of 9 workstreams — not an afterthought.

This approach has produced FDA-submissible evidence packages for sponsors across a range of device categories. The enVVeno Medical case study illustrates how a LATAM first-in-human program was structured to support what became the first-ever FDA IDE for a non-surgical replacement venous valve. The Cook Group case study documents a multi-site FIH program in Colombia with 142-plus INVIMA regulatory submissions managed, all structured for U.S. submission readiness.

Ophthalmic device sponsors can see a similar approach in the ClarVista Medical case study, where LATAM first-in-human data supported a program that ended in a ClarVista acquisition by Alcon. For sponsors in retinal therapy, the i-Lumen Scientific case study covers a novel device program for age-related macular degeneration run through the same framework.

The speed advantage in Latin America — where ethics and regulatory approvals have been observed in 30 to 90 days in Panama, El Salvador, Chile, and the Dominican Republic — only produces value if the data generated meets the FDA standard your downstream application requires. Pathway clarity before the study starts is what makes that speed useful rather than just fast.

---

Making the IDE vs IND Decision: A Practical Framework

Before filing anything, work through these questions in order.

1. What is your product? If it is a drug, biologic, or gene therapy with no device component, you are in IND territory. If it is a device with no drug or biologic component, you are in IDE territory. If it combines both, you need a PMOA determination.

2. What is your downstream marketing application? Targeting 510(k), De Novo, PMA, or HDE means your clinical data must be structured under the IDE framework. Targeting NDA or BLA means it must be structured under IND.

3. What is the risk classification of your device? SR or NSR — this determines whether you need a full IDE submission to FDA or can proceed under an abbreviated IDE with IRB approval.

4. Does your study qualify for an IDE exemption? Confirm with FDA through a Pre-Sub if there is any ambiguity.

5. Where are you running the study? If outside the U.S., confirm that your CRO structures data collection under ISO 14155 and 21 CFR 812.28 to ensure FDA acceptability.

---

FAQs

What is the difference between an IDE and an IND?
An IDE (Investigational Device Exemption) governs clinical studies of unapproved medical devices under 21 CFR Part 812, reviewed by CDRH. An IND (Investigational New Drug) governs clinical studies of drugs and biologics under 21 CFR Part 312, reviewed by CDER or CBER. The pathway you enter determines the downstream marketing application you can file and the evidence standard your clinical data must meet.

Which FDA center reviews IDE applications?
CDRH reviews IDE applications. IND applications are reviewed by CDER (drugs) or CBER (biologics), depending on the product type.

What is the difference between a significant-risk and non-significant-risk device?
A significant-risk (SR) device presents a potential for serious risk and requires a full IDE submission with FDA approval before the study begins. A non-significant-risk (NSR) device does not require a formal FDA submission; the sponsor proceeds under an abbreviated IDE with IRB or Ethics Committee approval.

Can a clinical study require both an IDE and an IND?
Yes. Combination products that include both a device component and a drug or biologic component may require both an IDE and an IND. FDA assigns a primary mode of action to determine the lead reviewing center, but both centers review the submission.

How long does FDA take to review an IDE application?
FDA has 30 days to review an IDE application. For significant-risk devices, FDA must affirmatively approve the IDE before the study begins — there is no default-to-proceed mechanism, unlike IND applications, where a sponsor may proceed after 30 days if no clinical hold is issued.

Does data collected in Latin America satisfy FDA IDE or IND requirements?
Data collected under ISO 14155 and structured per FDA 21 CFR 812.28 is accepted for U.S. IDE and IND submissions when properly structured. The critical factor is that the CRO managing the study anchors its protocol architecture and data collection to the sponsor's specific U.S. regulatory pathway from the start of the program.

When is an IDE not required for a device study?
IDE requirements do not apply to studies of legally marketed devices used within their cleared indications, certain diagnostic device studies meeting specific criteria, consumer preference studies without subject risk, and categories specifically exempted under 21 CFR 812.2(c). Sponsors should confirm any exemption claim through an FDA Pre-Submission before proceeding.

---

Conclusion

The IDE vs IND decision is not administrative paperwork. It is the regulatory foundation your entire clinical program is built on. Get it right before the protocol is written, before the CRO is engaged, and before a single patient is screened. A misclassified pathway, a misstructured data package, or an unconfirmed exemption assumption are expensive and time-consuming to correct.

If you are at the pre-clinical to IDE/IND-ready stage and need to map your pathway before your next funding milestone, bioaccess® builds that strategy into the first workstream of every FIH-12™ program. Visit bioaccessla.com to get your FIH roadmap.