Category: Uncategorized

• What the FDA Breakthrough Devices Program Actually Is
• The Two Eligibility Criteria Your Device Must Meet
  • Criterion 1: Serious or Life-Threatening Condition
  • Criterion 2: More Effective Than Available Alternatives
• When to Apply and What to Submit
• What Breakthrough Designation Actually Gets You
• The Gap Between Designation and Authorization
• How Breakthrough Designation Connects to Your FIH Strategy
• Common Reasons Designation Requests Are Denied
• After Designation: Keeping the Benefits Active
• Frequently Asked Questions
• Build the Evidence Package Your Designation Demands

The FDA Breakthrough Device designation can change the trajectory of a medical device program. For a startup racing toward a first-in-human milestone, it signals to investors, partners, and the agency itself that your technology addresses a genuine unmet need. But the program is selective, the criteria are specific, and designation alone does not guarantee authorization. This article covers exactly what qualifies, how to apply, and what breakthrough status actually means for your clinical development timeline.

---

What the FDA Breakthrough Devices Program Actually Is

The Breakthrough Devices Program is a voluntary FDA program that gives certain medical devices and device-led diagnostics priority interaction and review. Established under the 21st Century Cures Act and formalized in FDA guidance, it was designed to accelerate the development and review of devices that provide more effective treatment or diagnosis of serious or life-threatening conditions.

The program does not create a separate regulatory pathway. Devices still go through 510(k), De Novo, or PMA review. What changes is the speed and depth of FDA engagement along the way: more frequent interactions, earlier access to senior reviewers, and a commitment to timely review once a premarket submission arrives.

The scale of the program reflects genuine industry demand. According to the U.S. Food and Drug Administration, 1,246 breakthrough device designations had been granted from the program's launch through December 31, 2025. Of those, 185 had received marketing authorization. That conversion rate matters — and is addressed in detail below.

---

The Two Eligibility Criteria Your Device Must Meet

Qualifying for breakthrough designation requires satisfying two conditions simultaneously. Both must be present. Meeting only one is not sufficient.

Criterion 1: Serious or Life-Threatening Condition

Your device must be intended to treat or diagnose a disease or condition that is serious or life-threatening. The FDA interprets "serious" broadly — conditions do not have to be immediately fatal to qualify. Chronic conditions that cause substantial impairment, irreversible morbidity, or significant reduction in daily function can meet this threshold.

Conditions that have historically qualified include heart failure, treatment-resistant depression, advanced-stage cancers, severe neurological disorders, and conditions with no adequate alternative therapy. The core question is whether the condition imposes a meaningful burden on patients and whether current options fall short.

Criterion 2: More Effective Than Available Alternatives

This is where most applications succeed or fail. Your device must provide for more effective treatment or diagnosis of the condition compared to currently available alternatives. The FDA evaluates this on one or more of the following grounds:

• Represents a breakthrough technology with no approved or cleared alternatives
• Offers significant advantages over existing approved or cleared alternatives, including improved diagnosis, treatment, or monitoring
• Availability is in the best interest of patients, particularly when the condition is serious and no alternative exists

"More effective" does not require clinical proof at the time of designation. Preclinical data, mechanism-of-action arguments, and a credible scientific rationale can support the request. The FDA is making a preliminary judgment about potential — not a final determination about efficacy.

---

When to Apply and What to Submit

Sponsors can request breakthrough designation at any point in the development process, including before an Investigational Device Exemption (IDE) is in place. Early application is generally advisable because the benefit of enhanced FDA interaction is most valuable before your protocol is finalized and your trial is underway.

The designation request is submitted as a separate administrative submission — not as part of a Pre-Sub or IDE. It should include:

• A description of the device and its intended use
• The serious condition the device addresses
• The basis for believing the device meets the "more effective" criterion, supported by available preclinical or clinical data
• A description of the current standard of care and why it is inadequate

The FDA has 60 calendar days to respond. In practice, the agency either grants designation, denies it with explanation, or requests additional information. Denial does not close the door permanently; sponsors can reapply with additional supporting data.

---

What Breakthrough Designation Actually Gets You

Designation is a process benefit, not a regulatory shortcut. Here is what it concretely provides:

Increased interaction with FDA. Designated devices receive priority access to FDA staff for meetings, written feedback, and dispute resolution. This matters most during protocol design, when early alignment on endpoints and study design can prevent costly amendments later.

Timely review commitment. Once a premarket submission is filed, the FDA commits to a review timeline faster than standard pathways. For PMA applications, the target review time for breakthrough devices is shorter than the standard 180-day target.

Senior staff involvement. Breakthrough programs bring senior FDA reviewers into the process earlier, which can reduce the back-and-forth that extends standard reviews.

Potential for rolling review. Sponsors can submit completed sections of a PMA as they become available rather than waiting to compile the full package — compressing the overall submission-to-decision timeline.

What designation does not provide: guaranteed approval, relaxed safety standards, or exemption from the clinical evidence requirements that apply to your device class. The FDA still expects rigorous, well-controlled clinical data.

---

The Gap Between Designation and Authorization

This is the number that deserves more attention than most articles give it. A 2025 report published on pubmed.ncbi.nlm.nih.gov analyzed FDA data from January 1, 2016 through September 30, 2024, covering 1,041 breakthrough designations and 127 marketing authorizations during that period. The authorization rate was 12.2%.

That figure does not mean the program fails 87.8% of devices. Many designated devices are still in active development, and the pipeline takes years to move from designation to submission. But the number does underscore that designation is a starting point, not a finish line.

The same 2025 report found that among the 127 authorized breakthrough devices in that dataset, 75 were therapeutic devices — representing 59.1% of all authorized breakthrough products. Diagnostics and monitoring devices made up the remainder. If your device is therapeutic, you are working in the category that has produced the most authorizations under this program.

---

How Breakthrough Designation Connects to Your FIH Strategy

For a pre-IDE startup, breakthrough designation and first-in-human execution are parallel tracks, not sequential ones. You can pursue designation while your clinical program is being structured. The FDA interactions that come with designation are most useful when your protocol is still being designed — which is precisely when you can act on them.

This is where the choice of CRO and clinical geography matters directly. The FDA accepts foreign clinical data under 21 CFR 812.28 when it is collected under ISO 14155 architecture and submitted with appropriate documentation. First-in-human studies conducted in Latin America, structured to that standard, generate data that supports a U.S. IDE, 510(k), De Novo, or PMA submission.

bioaccess® builds every protocol to ISO 14155 architecture and structures data per FDA 21 CFR 812.28. The FIH-12™ program delivers a submission-ready clinical evidence package within a 12-month structured timeline, with ethics and regulatory approvals in Panama, El Salvador, Chile, and the Dominican Republic observed in 30 to 90 days. For a startup that has just received breakthrough designation and needs first human data before the next funding round, that timeline is the relevant comparison point against the 6 to 12 months that U.S. or EU site approvals typically require.

The Axoft case study illustrates this directly: a Panama first-in-human program that preceded a $55M Series A. enVVeno Medical used a LATAM FIH foundation to build the evidence base for the first-ever FDA IDE for a non-surgical replacement venous valve. These are documented programs, not hypothetical outcomes.

For device sponsors working through coronary or vascular indications, the CeloNova BioSciences COBRA PzF stent program and the ClarVista Medical program — which ended in an Alcon acquisition — show how Latin America-executed clinical evidence supports the full regulatory arc from first-in-human through commercial exit.

---

Common Reasons Designation Requests Are Denied

Understanding why requests fail is as useful as understanding the criteria. The most frequent reasons include:

Inadequate characterization of the condition. If the submission does not clearly establish that the target condition is serious or life-threatening, the FDA has no basis to grant designation. This is as much a writing and framing problem as a scientific one.

Weak differentiation from existing alternatives. If approved or cleared alternatives exist and the submission does not explain specifically how the device is more effective, the FDA will deny the request. "Novel technology" is not sufficient without a mechanism-based or data-supported argument for superiority or advantage.

Indication scope mismatch. Requests that describe a broad indication when the clinical data supports only a narrow one create credibility problems. Narrowing the intended use to match available evidence often strengthens a request.

Premature submission without supporting data. Preclinical data can be sufficient, but a request with no scientific rationale beyond the device description is unlikely to succeed. Even early bench or animal data that speaks to mechanism or safety profile strengthens the argument.

---

After Designation: Keeping the Benefits Active

Breakthrough designation does not expire, but the benefits depend on active engagement. Sponsors who fail to schedule interactions with FDA, miss the opportunity to align on study design early, or submit a premarket application without taking advantage of rolling review are leaving the program's value on the table.

The FDA can also withdraw designation if the device no longer meets the criteria — for example, if a new alternative receives clearance that addresses the same unmet need. Monitoring the competitive landscape and maintaining regular FDA communication protects the designation's value over time.

---

Frequently Asked Questions

What is the FDA Breakthrough Devices Program?
The FDA Breakthrough Devices Program is a voluntary program that provides priority interaction and review for medical devices intended to treat or diagnose serious or life-threatening conditions more effectively than currently available alternatives. It does not create a separate regulatory pathway but accelerates FDA engagement throughout development and review.

What conditions qualify a device for breakthrough designation?
The target condition must be serious or life-threatening, which includes conditions causing substantial impairment, irreversible morbidity, or significant reduction in daily function. Conditions do not need to be immediately fatal to qualify.

Does a device need clinical data to apply for breakthrough designation?
No. Sponsors can apply at any stage of development, including before an IDE is in place. Preclinical data, mechanism-of-action arguments, and a credible scientific rationale are sufficient to support a designation request. Clinical proof is not required at the time of application.

How long does the FDA take to respond to a breakthrough designation request?
The FDA has 60 calendar days to respond. The agency will either grant designation, deny it with explanation, or request additional information.

What is the authorization rate for breakthrough-designated devices?
A 2025 report published on pubmed.ncbi.nlm.nih.gov found that between January 2016 and September 2024, 12.2% of designated devices had received marketing authorization. Many designated devices remain in active development, so this figure reflects the pipeline's stage distribution, not program failure.

Can first-in-human data from Latin America support a US breakthrough device submission?
Yes. The FDA accepts foreign clinical data under 21 CFR 812.28 when collected under ISO 14155 architecture with appropriate documentation. First-in-human studies conducted in Latin America through a program structured to those standards generate data accepted for U.S. IDE, 510(k), De Novo, and PMA submissions.

When should a startup pursue breakthrough designation relative to its FIH program?
Designation and FIH execution can run in parallel. Applying before your protocol is finalized is advisable because the enhanced FDA interaction is most valuable during study design. A CRO with FDA Pre-Sub experience can help align both tracks so the designation benefits directly inform the FIH protocol.

---

Build the Evidence Package Your Designation Demands

Breakthrough designation opens the door to faster FDA engagement. What you bring through that door is a clinical evidence package. The quality, structure, and FDA-readiness of that package determine whether designation translates into authorization.

bioaccess® structures FIH programs specifically to produce submission-ready evidence under ISO 14155 and FDA 21 CFR 812.28, with observed ethics and regulatory approval timelines of 30 to 90 days across Panama, El Salvador, Chile, and the Dominican Republic. For startups with a breakthrough designation and a funding clock running, that combination of speed and FDA-accepted rigor is the relevant operational question.

Learn more at bioaccessla.com.

• What Happens Immediately After Submission
• The 30-Day Review Window
• Conditional Approval: What It Means and What to Do Next
• IDE Amendments and Protocol Changes
• Site Activation After IDE Approval
• FDA IDE Approval and the OUS Clinical Strategy
• Reporting Obligations That Begin at Approval
• What the IDE Approval Letter Does Not Cover
• Using the IDE Approval Window Productively
• After Approval: The Path to First Patient Enrolled
• Frequently Asked Questions
• What Comes Next

You filed your Investigational Device Exemption application. The submission is in FDA's hands. Now what?

FDA IDE approval is not a single event — it's a structured review sequence that begins the moment your application reaches the Center for Devices and Radiological Health (CDRH). Most first-time sponsors underestimate how many distinct steps follow submission. Understanding each one lets you plan site activation, manage investor expectations, and avoid the delays that derail early-stage programs before they start.

This article walks through every stage of the post-submission process — from the initial administrative screening to the conditions that often accompany approval — and explains how experienced sponsors use that window to prepare for first-in-human execution.

---

What Happens Immediately After Submission

FDA's review clock starts at receipt. Under 21 CFR 812, the agency has 30 calendar days to approve the IDE, disapprove it, or allow it to take effect by default if no action is taken. That 30-day window sounds fast. In practice, it rarely plays out that cleanly.

The first step is an administrative completeness check. Reviewers confirm that all required sections are present: the investigational plan, risk analysis, device description, manufacturing information, investigator agreements, IRB status, and marketing history. If anything is missing, FDA may place the application on hold or issue a deficiency letter before substantive review even begins.

This administrative phase typically takes 5 to 10 business days. An incomplete submission can cost a sponsor weeks before the scientific review starts.

---

The 30-Day Review Window

Once the application clears administrative screening, CDRH assigns it to a review division based on device type. The assigned reviewer evaluates the scientific and clinical content: study design, endpoints, patient selection criteria, risk-benefit analysis, and the preclinical evidence supporting the proposed first-in-human use.

FDA may contact the sponsor with questions during this period. Those informal communications don't stop the 30-day clock — but they do require fast responses. A sponsor who takes 10 days to answer a reviewer's question effectively compresses whatever review time remains.

Three outcomes are possible at the end of the window:

• Approval: FDA issues a written approval letter. The IDE is effective, and the sponsor may proceed under the approved protocol.
• Disapproval: FDA issues a written disapproval with specific reasons. The sponsor may request reconsideration or submit an amended application.
• Conditional approval: FDA approves the IDE subject to specific conditions the sponsor must satisfy before or during the study. This is the most common outcome for first-in-human device studies.

Default approval — where FDA takes no action within 30 days and the IDE is deemed approved — does occur. Sponsors should not plan around it. Proceeding on a default approval without written confirmation creates regulatory risk.

---

Conditional Approval: What It Means and What to Do Next

Conditional approval is not a partial win. It is a full IDE approval with attached requirements. FDA may require protocol amendments, additional preclinical data, modified informed consent language, enhanced safety monitoring, or specific reporting intervals. Each condition carries its own compliance obligation.

Read the approval letter carefully. Some conditions must be satisfied before the first patient is enrolled. Others apply throughout the study. Misreading a pre-enrollment condition as an ongoing obligation — or vice versa — can put the program out of compliance from day one.

Common pre-enrollment conditions include:

• Submission of a final, IRB-approved protocol incorporating FDA's requested modifications
• Confirmation of investigator qualifications at each site
• Submission of a clinical trial insurance policy
• Updated device labeling reflecting the approved indications

Once conditions are satisfied, the sponsor typically notifies FDA in writing. FDA does not issue a separate "conditions cleared" letter in most cases — documenting and maintaining compliance is the sponsor's responsibility.

---

IDE Amendments and Protocol Changes

IDE approval does not lock the protocol in place. Sponsors frequently need to amend after approval — to add investigators, modify sites, adjust inclusion/exclusion criteria, or update the device design following design freeze confirmation.

Under 21 CFR 812.35, significant changes to the investigational plan, the device, or informed consent require a supplemental IDE submission. FDA reviews significant amendments under the same 30-day framework. Non-significant changes require sponsor notification but not prior FDA approval.

The line between significant and non-significant isn't always obvious. When in doubt, submit. An unapproved significant change can invalidate data collected under the modified protocol — a serious problem if that data is intended for a future PMA or 510(k) submission.

---

Site Activation After IDE Approval

IDE approval does not authorize patient enrollment. Each investigational site must also receive IRB approval before enrollment begins. In the US, that IRB review runs in parallel with or after the IDE process and adds weeks to the activation timeline.

Site activation involves several parallel workstreams: executing investigator agreements, completing site qualification visits, confirming device importation logistics, training the site team on the protocol and GCP requirements, and verifying that the site's patient population matches the study's eligibility criteria.

For multi-site studies, site activation is often the longest phase between IDE approval and first patient enrolled. A site that passes qualification but takes 8 weeks to complete IRB review and staff training effectively delays the entire program.

This is one reason some sponsors run early feasibility studies outside the US first, using data collected under ISO 14155 and structured per FDA 21 CFR 812.28 to support a subsequent US IDE submission. The enVVeno Medical case study illustrates this path directly: OUS early clinical execution in Latin America generated the evidence package that supported the first-ever FDA IDE for a non-surgical replacement venous valve.

---

FDA IDE Approval and the OUS Clinical Strategy

For many MedTech startups, IDE approval isn't the starting point for first-in-human data — it's the destination. OUS studies generate the preclinical-to-clinical bridge data that makes the IDE application credible in the first place.

Under FDA 21 CFR 812.28, data from foreign clinical investigations may be accepted in support of an IDE if the studies were conducted under conditions comparable to FDA requirements and the data is submitted in a format FDA can evaluate. ISO 14155 provides the protocol architecture that satisfies this comparability standard.

Running an early feasibility study in Panama, Chile, El Salvador, or the Dominican Republic — where ethics and regulatory approvals are observed in 30 to 90 days — compresses the time between design freeze and first human data by months compared to initiating a US study from scratch. That compression matters when a startup's financial runway is measured in quarters, not years.

The Cook Group multi-site study in Colombia demonstrates what structured OUS execution looks like at scale: 142-plus INVIMA regulatory submissions managed across a multi-site first-in-human artificial venous valve program, with data architecture designed to support US regulatory use.

---

Reporting Obligations That Begin at Approval

IDE approval activates a set of ongoing reporting obligations that sponsors must maintain throughout the study. These are not optional and are not triggered only by adverse events.

Annual progress reports must be submitted to FDA within 30 days of the IDE anniversary. The report covers enrollment status, adverse events, protocol deviations, and any changes to the investigational plan.

Unanticipated adverse device effects (UADEs) must be reported to FDA and all reviewing IRBs within 10 business days of the sponsor's first receipt of information about the effect. This is a hard deadline. Sponsors who lack a functioning safety monitoring and reporting system before enrollment begins routinely miss it.

IDE withdrawal or termination requires a final report within 30 days. If the study ends early — for any reason — the reporting obligation does not end with it.

Building these reporting workflows before the first patient is enrolled is not administrative overhead. Gaps in IDE reporting history can complicate future submissions.

---

What the IDE Approval Letter Does Not Cover

A few things sponsors sometimes assume the IDE approval letter addresses — but doesn't:

It does not authorize commercial distribution. An IDE permits clinical investigation only. Selling or distributing the device outside the approved study is a violation of 21 CFR 812, regardless of what the IDE says.

It does not constitute FDA endorsement of the device's safety or effectiveness. Approval means FDA found the proposed study acceptable to proceed — not that the device is safe or effective. This distinction matters for investor communications and for informed consent language.

It does not guarantee a clear path to PMA or 510(k). The study design approved under the IDE must be executed as approved. Data collected under a protocol that deviates from the approved IDE may not be accepted in a subsequent marketing application.

It does not replace IRB approval at each site. IDE approval and IRB approval are both necessary before enrollment. They are separate, parallel requirements.

---

Using the IDE Approval Window Productively

The period between IDE submission and approval — typically 4 to 8 weeks for a complete, well-prepared application — is not dead time. Sponsors who use it well arrive at approval ready to activate.

During this window, experienced sponsors complete site qualification visits, finalize investigator agreements, confirm device manufacturing readiness, and brief the IRB on the expected protocol. If conditional approval is likely, sponsors can anticipate common conditions and prepare responsive documentation in advance.

For programs that ran OUS early feasibility studies before the IDE submission, this window is often used to close out the OUS data package and prepare FDA-bridging documentation under 21 CFR 812.28. The i-Lumen Scientific retinal therapy program reflects how OUS execution and US regulatory strategy can be sequenced to minimize total time to first US enrollment.

---

After Approval: The Path to First Patient Enrolled

IDE approval is a regulatory milestone, not a clinical one. The distance between approval and first patient enrolled depends entirely on how well the sponsor managed parallel workstreams during the review period.

Programs that arrive at IDE approval with sites qualified, IRB submissions in progress, and device inventory staged typically enroll their first patient within 8 to 12 weeks of the approval letter. Programs that treat IDE approval as the trigger to begin site activation routinely add 4 to 6 months to that timeline.

The FIH-12™ program at bioaccess® is structured around this reality. Nine workstreams — covering FDA strategy alignment, protocol development, site activation, patient enrollment, data management, and submission-ready evidence package delivery — run in parallel, not in sequence. That parallel architecture is what makes a 12-month protocol-to-evidence-package timeline achievable for programs that would otherwise take 18 to 24 months under a sequential approach.

---

Frequently Asked Questions

What is FDA's timeline for reviewing an IDE application after submission?
FDA has 30 calendar days from receipt to approve, disapprove, or take no action on an IDE application. Most complete applications receive a written response within that window, though administrative deficiencies can delay the start of substantive review.

What does conditional IDE approval mean?
Conditional approval means FDA has approved the IDE subject to specific requirements the sponsor must satisfy before or during the study. Common conditions include IRB-approved protocol amendments, updated device labeling, or additional preclinical data. The study may not proceed until pre-enrollment conditions are met.

Can I enroll patients immediately after receiving IDE approval?
No. IDE approval authorizes the study but does not replace IRB approval at each investigational site. Each site must receive independent IRB approval before enrolling patients. Site activation, investigator agreements, and staff training must also be completed first.

What reporting obligations does IDE approval trigger?
Sponsors must submit annual progress reports within 30 days of the IDE anniversary, report unanticipated adverse device effects (UADEs) to FDA and reviewing IRBs within 10 business days, and submit a final report within 30 days if the study is terminated.

Can data from OUS studies support an IDE application?
Yes. Under FDA 21 CFR 812.28, data from foreign clinical investigations conducted under conditions comparable to FDA requirements may be accepted in support of an IDE. Studies structured under ISO 14155 satisfy the comparability standard FDA applies.

What happens if I make changes to the protocol after IDE approval?
Significant changes to the investigational plan, the device, or informed consent require a supplemental IDE submission and FDA approval before implementation. Non-significant changes require sponsor notification only. Implementing a significant change without prior FDA approval can invalidate data collected under the modified protocol.

How long does site activation typically take after IDE approval?
Sponsors who begin qualification visits and IRB submissions during the IDE review period typically enroll their first patient within 8 to 12 weeks of approval. Sponsors who begin activation only after receiving the approval letter often add 4 to 6 months to that timeline.

---

What Comes Next

FDA IDE approval is a milestone you earn through preparation, not one you wait for. The quality of your application determines how quickly FDA can review it. The work you do during the review period determines how quickly you can enroll after approval. And the data architecture you establish before the first patient is enrolled determines whether the evidence package you generate will support a US marketing application.

For sponsors building that architecture from the ground up, visit bioaccess® to understand how the FIH-12™ program structures each workstream — from Pre-Sub alignment through submission-ready evidence delivery — to keep your program on the timeline your investors and board are counting on.

---

WordPress Category: Navigating Regulatory Landscapes in Latin America

• What Is an FDA Q-Submission?
• Why File a Pre-Sub Before Your IDE?
• When to File Your Pre-Sub
• What to Include in Your Pre-Sub Package
  • Device Description and Intended Use
  • Proposed Clinical Indication
  • Draft Study Design and Protocol Outline
  • Risk Analysis Summary
  • Proposed Regulatory Pathway
  • Your Specific Questions
• Common Pre-Sub Mistakes That Delay IDE Filings
  • Submitting Without a Defined Regulatory Pathway
  • Asking Too Many Questions
  • Conflating OUS Data with IDE Exemption
  • Underestimating Meeting Preparation
• How OUS Early Clinical Data Fits Into Your Pre-Sub Strategy
• The Pre-Sub to IDE Sequence in Practice
• What FDA Looks for in a Strong Pre-Sub Package
• Connecting Pre-Sub Strategy to Your FIH Execution Plan
• Frequently Asked Questions

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.

• What Defines an Investigator-Initiated Study
• Why Sponsors Support Investigator-Initiated Studies
• The Regulatory Accountability Gap
• Data Ownership and Intellectual Property
• Protocol Design and Endpoint Alignment
• When Investigator-Initiated Studies Work Well
• Investigator-Initiated Studies in Latin America
• Sponsor-Initiated vs. Investigator-Initiated: A Practical Comparison
• What Sponsors Should Require Before Supporting an IIS
• The Role of a CRO in Investigator-Initiated Programs
• Frequently Asked Questions
• Conclusion

Investigator-initiated studies occupy a distinct corner of clinical research that sponsors often misunderstand until a regulatory question forces the issue. When a principal investigator (PI) conceives, designs, and sponsors a study using their own protocol, the accountability structure shifts in ways that affect every downstream decision — from data ownership to FDA submission eligibility. If your device or therapeutic is the subject of an investigator-initiated study, or if you are considering supporting one, the implications for your IDE or IND pathway deserve careful attention before the first patient is enrolled.

This article explains how investigator-initiated studies work, where they fit in early-phase development, what sponsors need to control to protect their regulatory position, and how Latin American execution can change the cost and timeline calculus for both sponsor-initiated and investigator-initiated programs.

---

What Defines an Investigator-Initiated Study

An investigator-initiated study (IIS) is one in which the investigator — rather than a commercial sponsor — holds the IND or IDE and takes regulatory accountability for the study. The investigator designs the protocol, selects endpoints, and manages the submission to the relevant regulatory authority.

This is distinct from a sponsor-initiated trial, where a company submits the IDE or IND and retains full control over protocol design, data, and regulatory correspondence. In an IIS, the investigator is simultaneously the PI and the regulatory sponsor. That dual role carries significant operational consequences.

The distinction matters most when the data generated is intended to support a future regulatory submission. If a device company wants to reference an IIS in its IDE or PMA application, that data must meet the same evidentiary standards as sponsor-generated data — ISO 14155 protocol architecture, GCP compliance, and documentation structured under FDA 21 CFR 812.28 for studies conducted outside the United States.

---

Why Sponsors Support Investigator-Initiated Studies

Commercial sponsors fund or supply devices for investigator-initiated studies for several legitimate reasons.

Academic investigators often have access to patient populations and clinical expertise that a startup cannot replicate independently. A PI with 20 years of implant experience and an established patient registry can generate early feasibility data that a company's own clinical team would take years to build.

IIS programs can also generate independent clinical evidence. Data produced without direct sponsor control carries a different kind of credibility with payers, guideline committees, and, in some contexts, regulators. For a device seeking reimbursement pathways or clinical society endorsement, investigator-generated evidence carries weight that sponsor-generated data sometimes does not.

For early-stage companies with limited operational infrastructure, supporting an IIS can be a way to generate proof-of-concept data without building out a full clinical operations function. The investigator handles Ethics Committee (EC) submissions, site management, and regulatory filings.

The tradeoff is control — and that tradeoff has direct consequences for how the data can be used.

---

The Regulatory Accountability Gap

When an investigator holds the IDE or IND, the sponsor's ability to direct protocol amendments, access source data, or correct deviations is limited by whatever the agreement between the parties specifies. If the investigator makes a protocol change without notifying the sponsor, the sponsor may not learn about it until data review — at which point the deviation is already in the record.

FDA's foreign clinical data framework under 21 CFR 812.28 requires that data submitted to support an IDE or IND be collected under conditions the sponsor can verify. If an IIS was not conducted under GCP, or if source data cannot be audited, FDA may not accept it as supporting evidence.

This is not a theoretical risk. Sponsors who have attempted to incorporate IIS data into regulatory submissions have encountered requests for information that the investigator — not the sponsor — controls. Retrieving that documentation after the fact is time-consuming and sometimes impossible.

The practical implication: if you intend to use IIS data in a regulatory submission, the agreement with the investigator must specify data access rights, audit rights, protocol amendment procedures, and GCP compliance obligations before the study starts. Retrofitting these provisions after enrollment has begun rarely works.

---

Data Ownership and Intellectual Property

In most academic settings, ownership of data generated in an investigator-initiated study defaults to the investigator's institution. The sponsor's rights to that data depend entirely on what the agreement says.

If the agreement is silent on data ownership, the sponsor may have no right to include the data in a regulatory submission without the investigator's permission. If the investigator moves institutions, retires, or the relationship deteriorates, access to the data can become contested.

For a startup whose entire regulatory strategy depends on early feasibility data, this is a material risk. The agreement should specify:

• Who owns the raw data and case report forms
• What rights the sponsor has to reference, publish, or submit the data
• What happens to data access if the investigator leaves the institution
• Whether the sponsor can audit source documents independently

These provisions are standard in well-structured clinical trial agreements. They are often missing in agreements drafted by academic legal offices more accustomed to grant-funded research than commercial development.

---

Protocol Design and Endpoint Alignment

Investigator-initiated studies are designed to answer the investigator's scientific question — which may not align with the endpoints FDA will require for an IDE or IND submission.

A PI interested in a device's mechanism of action may design a study around exploratory biomarker endpoints. A sponsor preparing for a pivotal trial needs safety data, device performance metrics, and adverse event documentation structured to ICH-GCP and ISO 14155 standards. These are not always the same study.

Before supporting an IIS, sponsors should evaluate whether the proposed primary and secondary endpoints will generate data that is directly usable in a regulatory submission. Misaligned endpoints mean the sponsor may fund a study that produces scientifically interesting but regulatorily insufficient evidence.

This is where a Pre-Submission (Pre-Sub) meeting with FDA becomes valuable. A Pre-Sub allows the sponsor to confirm which endpoints and data formats FDA will accept before the study is designed, not after. Structuring the IIS protocol to satisfy those requirements — even if the investigator retains regulatory sponsorship — protects the sponsor's downstream regulatory position.

---

When Investigator-Initiated Studies Work Well

Not every IIS is a regulatory liability. When the structure is right, investigator-initiated studies can accelerate early-phase development in ways that sponsor-initiated programs cannot match.

The conditions under which IIS programs work well include:

• The investigator has deep domain expertise and an established patient population
• The sponsor has negotiated data access, audit rights, and IP provisions upfront
• The protocol endpoints are aligned with FDA's early feasibility study (EFS) guidance
• The study is conducted under ISO 14155 and GCP, with documentation sufficient for regulatory submission
• The sponsor is not relying solely on IIS data for its IDE or IND, but using it as supplementary evidence alongside sponsor-controlled studies

In this configuration, the IIS generates independent clinical evidence while the sponsor runs a parallel, fully controlled early feasibility study. The combination is often more persuasive to FDA than either dataset alone.

---

Investigator-Initiated Studies in Latin America

Latin American academic medical centers run investigator-initiated studies under the same general framework as their US counterparts, but the regulatory environment introduces additional variables sponsors need to understand.

In Colombia, a study conducted under INVIMA oversight requires ethics committee approval from an institutional committee recognized by the national authority. If an investigator-initiated study is conducted without proper INVIMA registration, the data cannot be used in a Colombian regulatory filing — and its admissibility in a US IDE submission becomes questionable.

The same principle applies across the region. Studies conducted in Panama under MINSA/CNBI oversight, in Chile under ISP/MINSAL, or in El Salvador under SRS/CNEIS must follow the applicable national regulatory framework to generate data that is defensible in a US submission.

This is where the distinction between a well-structured IIS and an informal academic study becomes critical. An investigator at a Latin American academic center may have excellent clinical skills and a relevant patient population, but if the study is not registered, if the EC approval is not documented, and if source data is not maintained to GCP standards, the data is not usable for regulatory purposes.

Sponsors supporting IIS programs in Latin America should require the same documentation standards they would require of a sponsor-initiated study. The Cook Group's multi-site first-in-human study in Colombia — which involved 142-plus INVIMA regulatory submissions — illustrates the documentation depth that a properly structured Latin American clinical program requires. That level of regulatory rigor applies whether the sponsor or the investigator holds the IDE.

---

Sponsor-Initiated vs. Investigator-Initiated: A Practical Comparison

The choice between supporting an IIS and running a sponsor-initiated early feasibility study has direct implications for timeline, cost, data quality, and regulatory risk.

Sponsor-initiated studies give the company full control over protocol design, endpoint selection, data management, and regulatory correspondence. The sponsor can structure the study to satisfy FDA's Pre-Sub feedback and ensure every data element is collected in a format that supports the IDE submission. The tradeoff is that the sponsor bears the full operational burden.

Investigator-initiated studies offload operational responsibility to the investigator but introduce data access risk, endpoint misalignment risk, and IP risk. They work best as supplementary evidence — not as the primary dataset for a regulatory submission.

For seed-to-Series-B MedTech companies with 12 to 24 months until first human data is needed, the operational burden of a sponsor-initiated study is often more manageable than the regulatory risk of relying on IIS data. A structured FIH program run by an experienced in-country CRO — with single-team accountability across protocol development, site activation, patient enrollment, and data management — eliminates the data access and endpoint alignment risks that IIS programs introduce.

The i-Lumen Scientific retinal therapy program and the CelonOva Biosciences coronary stent study are examples of sponsor-initiated early feasibility programs where full control over protocol design and data management produced submission-ready evidence packages. The difference in regulatory certainty compared to a loosely structured IIS is substantial.

---

What Sponsors Should Require Before Supporting an IIS

If you decide to support an investigator-initiated study, the following provisions should be non-negotiable in the clinical trial agreement.

Data access and audit rights. The sponsor must have the right to access source documents, case report forms, and adverse event records at any time during or after the study. This right should survive the investigator's departure from the institution.

Protocol amendment notification. Any amendment to the protocol must be communicated to the sponsor before submission to the ethics committee or regulatory authority. The sponsor should have the right to review and comment on amendments that affect primary endpoints or safety reporting.

GCP compliance obligations. The agreement should specify that the study will be conducted under ICH-GCP and, for device studies, ISO 14155. The investigator should agree to allow GCP audits by the sponsor or a designated third party.

Intellectual property provisions. The agreement should specify who owns the data, who has the right to publish, and what rights the sponsor has to reference the data in regulatory submissions.

Regulatory submission rights. The sponsor should have an explicit right to reference the IIS data in its IDE, IND, or PMA submission without requiring additional consent from the investigator or the institution at the time of submission.

Adverse event reporting. The agreement should specify how serious adverse events are reported to the sponsor and what the sponsor's obligations are under 21 CFR 812 or 21 CFR 312 upon receiving that information.

---

The Role of a CRO in Investigator-Initiated Programs

A contract research organization can add meaningful value to an investigator-initiated study in ways that protect the sponsor's regulatory position without displacing the investigator's scientific leadership.

A CRO can review the protocol to ensure the study design is consistent with FDA's early feasibility study guidance and that data collection instruments will generate submission-ready evidence. It can provide GCP training to the investigator's site team, implement electronic data capture systems that meet 21 CFR Part 11 requirements, and conduct ongoing monitoring visits to identify and correct deviations before they become regulatory problems.

In Latin America, where regulatory frameworks vary by country and the documentation requirements for INVIMA, MINSA, ISP, and other authorities differ from US norms, CRO oversight of an IIS is particularly valuable. An investigator with strong clinical skills may not have the regulatory infrastructure to maintain documentation to the standard required for a US IDE submission. An in-country CRO with established regulatory expertise can fill that gap.

bioaccess® structures all studies under ISO 14155 and FDA 21 CFR 812.28 — whether sponsor-initiated or investigator-supported — across a network of 50-plus pre-qualified clinical trial sites in 19 Latin American and Caribbean markets. Ethics and regulatory approvals in Panama, El Salvador, Chile, and the Dominican Republic have been observed in 30 to 90 days, which changes the timeline calculus for sponsors who need early feasibility data before their next funding round. Learn more at bioaccessla.com.

---

Frequently Asked Questions

What is an investigator-initiated study?
An investigator-initiated study is one in which the PI, rather than a commercial company, holds the IND or IDE and takes regulatory accountability for the study. The investigator designs the protocol, manages the regulatory submission, and is responsible for GCP compliance. A commercial sponsor may fund or supply devices for the study but does not hold the regulatory sponsorship.

Can data from an investigator-initiated study be used in an FDA IDE submission?
Yes, but only if the data was collected under conditions that meet FDA's standards. For foreign clinical data, this means the study must have been conducted under ISO 14155 and structured per FDA 21 CFR 812.28. The sponsor must also have documented access to source data and audit rights. Data from an IIS that lacks GCP documentation or audit trails is unlikely to be accepted by FDA as supporting evidence.

What are the main risks of supporting an investigator-initiated study?
The primary risks are data access limitations, endpoint misalignment, and IP disputes. If the clinical trial agreement does not specify the sponsor's rights to access data, audit the study, and reference the data in regulatory submissions, the sponsor may find that data it funded cannot be used in its regulatory program.

How does an investigator-initiated study differ from a sponsor-initiated early feasibility study?
In a sponsor-initiated study, the company holds the IDE or IND, controls the protocol, and owns the data. In an IIS, the investigator holds the regulatory sponsorship and the institution typically owns the data by default. Sponsor-initiated studies carry more operational burden but eliminate the data access and endpoint alignment risks that IIS programs introduce.

What should a clinical trial agreement for an IIS include?
At minimum: data access and audit rights that survive the investigator's departure, protocol amendment notification procedures, GCP compliance obligations, IP and data ownership provisions, explicit regulatory submission rights for the sponsor, and adverse event reporting procedures aligned with 21 CFR 812 or 21 CFR 312.

Can investigator-initiated studies be run in Latin America for FDA submissions?
Yes. Studies conducted in Latin American countries under the applicable national regulatory framework — with GCP compliance and documentation structured per ISO 14155 and 21 CFR 812.28 — can support US IDE and IND submissions. The key is ensuring the investigator's institution has the regulatory infrastructure to maintain documentation to the required standard, which often requires in-country CRO oversight.

When is a sponsor-initiated study preferable to supporting an IIS?
When the sponsor's regulatory strategy depends on the data, a sponsor-initiated study is almost always the stronger choice. Full control over protocol design, endpoint selection, data management, and regulatory correspondence eliminates the risks that IIS programs introduce. For seed-to-Series-B MedTech companies with a defined FDA milestone, a structured FIH program with single-team CRO accountability is typically the more reliable path to a submission-ready evidence package.

---

Conclusion

Investigator-initiated studies can generate valuable early clinical evidence, but their utility for regulatory submissions depends entirely on how the agreement is structured before the study starts. Data access rights, GCP compliance obligations, and endpoint alignment are not administrative details. They determine whether the data you fund can be used in your IDE or IND application.

If your development timeline requires first human data within 12 to 24 months and your regulatory strategy depends on that data, a sponsor-initiated early feasibility study with full protocol control and CRO oversight is the more defensible path. If you choose to support an IIS, treat the clinical trial agreement as a regulatory document — not an administrative formality — and engage CRO expertise to ensure the data meets submission standards from day one.

• What Altasciences Does
• What bioaccess® Does
• Altasciences vs bioaccess®: A Direct Comparison
• Why the Distinction Matters for Device Sponsors
• The Geography Question
• The Cost Structure
• Radiopharmaceuticals: A Specific Differentiator
• Which CRO Fits Which Sponsor
• Frequently Asked Questions
• Conclusion

Before any side-by-side comparison of Altasciences and bioaccess® makes sense, one detail needs to be on the table: Altasciences operates a site branded "Altasciences LA" — and that LA stands for Los Angeles, not Latin America. These two organizations serve different sponsor profiles, operate in different geographies, and are built around fundamentally different regulatory strategies. What follows breaks down where each CRO fits, what each actually delivers for device sponsors, and how they compare on the dimensions that matter most to a startup working within a $1 million to $5 million FIH budget with a funding milestone approaching.

---

What Altasciences Does

Altasciences is a Canadian-founded CRO with North American operations, including a clinical pharmacology unit in Los Angeles. Its core business is early-phase drug and molecule work: Phase I pharmacokinetics, bioavailability, bioequivalence, and first-in-human dosing studies for pharmaceutical and biotech sponsors.

The organization has built a solid reputation in small-molecule and biologic Phase I work. Its clinical pharmacology units are designed for controlled, single-site drug administration studies where the primary endpoint is a PK or PD measurement.

For medical device sponsors, that creates a structural mismatch. Device FIH trials require a different operational model entirely: multi-site enrollment, implant or procedure-based endpoints, Ethics Committee (EC) review under ISO 14155, and a data package structured for FDA 21 CFR 812.28 or IDE submission. Altasciences' infrastructure is built around drug metabolism — not device implantation or procedure-based evidence generation. The company has no documented LatAm FIH capability, no 30-to-90-day regulatory approval positioning, and no published device-specific trial network in Latin America.

That is not a criticism. It is simply a description of what Altasciences is built to do. Device FIH is not it.

---

What bioaccess® Does

bioaccess® is a Miami-headquartered CRO built specifically for medical device, biopharma, and radiopharmaceutical sponsors running first-in-human and early feasibility studies. Its primary service, the FIH-12™ program, is a nine-workstream, 12-month engagement covering FDA Pre-Sub and IDE/IND pathway alignment, protocol development, site activation, patient enrollment, data management, and delivery of a submission-ready clinical evidence package.

Clinical execution runs across a network of 50-plus pre-qualified sites in 19 countries across Latin America and the Caribbean. Ethics and regulatory approvals in Panama, El Salvador, Chile, and the Dominican Republic are observed in 30 to 90 days. Per-patient costs in Panama range from $12,000 to $22,000 — compared to six-figure equivalents in the United States. All data is collected under ISO 14155 and structured per FDA 21 CFR 812.28, the framework governing acceptance of foreign clinical data in U.S. IDE and IND submissions.

bioaccess® also offers the LATAM Launch Subscription: an in-country holder and Importer of Record registration service for devices already FDA-cleared (510(k) or PMA) or CE-marked, covering ANVISA (Brazil), INVIMA (Colombia), COFEPRIS (Mexico), ANMAT (Argentina), ISP (Chile), DIGEMID (Peru), and other regional authorities. The two service lines address different moments in a device's lifecycle — FIH-12™ for pre-market evidence generation, LATAM Launch for post-clearance market entry.

Clinical operations are ACRP-certified under NCCA accreditation. Regulatory authority integrations are confirmed with MINSA/CNBI in Panama, ISP/MINSAL in Chile, and SRS/CNEIS in El Salvador.

---

Altasciences vs bioaccess®: A Direct Comparison

The table below covers the dimensions most relevant to a MedTech startup evaluating CRO options for a device FIH program.

Dimension	Altasciences	bioaccess®
Primary focus	Drug/molecule Phase I	Medical device FIH and early feasibility
Latin America FIH capability	None documented	19-country network, 50-plus pre-qualified sites
Regulatory approval timeline	U.S./Canadian timelines	30 to 90 days observed in Panama, El Salvador, Chile, Dominican Republic
Per-patient cost benchmark	Not publicly available; U.S. site-based	$12,000 to $22,000 in Panama
ISO 14155 / 21 CFR 812.28 framework	Not positioned for device IDE submissions	Core operating standard; all data structured for FDA IDE/IND
Single-team accountability	Multi-vendor model typical for device work	Nine workstreams, one team, 12-month structured program
Radiopharmaceutical capability	Drug-focused; no dedicated device radiopharma	Lu-177, Ac-225, Ga-68 trial capability
LATAM market registration	Not offered	ANVISA, INVIMA, COFEPRIS, ANMAT, ISP, DIGEMID across 19 markets
Intake capacity	Not publicly disclosed	Capped at 8 new programs per quarter

---

Why the Distinction Matters for Device Sponsors

A startup preparing for a first-in-human device study is not shopping for a clinical pharmacology unit. The evidence package FDA reviewers expect for an IDE submission is built on implant or procedure data, safety endpoints from device-patient interaction, and a protocol architecture aligned with ISO 14155. That is a different science, a different site type, and a different regulatory conversation than a Phase I PK study.

The practical consequence of routing a device FIH program through a drug-focused CRO is a patchwork of vendors — none of whom own the full accountability chain. A sponsor with fewer than 50 employees and no dedicated clinical operations staff cannot absorb that coordination overhead. The time cost alone can push a 12-month evidence timeline past 18 to 24 months, which is precisely the scenario that exhausts startup runway before a pivotal trial begins.

bioaccess® addresses this directly. The FIH-12™ program assigns a single team across all nine workstreams — from FDA Pre-Sub alignment through protocol development, site activation, enrollment, and the final submission-ready package. The sponsor does not manage handoffs between a regulatory consultant, a site management organization, and a data management vendor. One team owns the outcome.

The Avantec Vascular case study illustrates the model: a multi-country Latin American FIH program for the Sangria™ Venous Remodeling System, executed under a single coordinated engagement with bioaccess® managing the full workstream chain. The ClarVista Medical program followed the same structure and concluded with ClarVista's acquisition by Alcon — a result that reflects what a clean, FDA-bridgeable evidence package can enable at the next stage of a device's commercial life.

---

The Geography Question

The "Altasciences LA" branding creates genuine confusion in search results. Sponsors looking for a LatAm-capable CRO may encounter Altasciences LA and assume a geographic overlap that does not exist. The Los Angeles unit is a clinical pharmacology site. It has no operational presence in Panama, Colombia, Chile, or anywhere else in Latin America.

For device sponsors, the geography of trial execution is not incidental. It determines the approval timeline, the per-patient cost, the site capabilities, and whether the resulting data package will satisfy FDA's foreign clinical data requirements under 21 CFR 812.28. Running a device FIH in the United States means navigating an IRB and FDA IDE process that typically takes 18 to 24 months before the first patient is enrolled. Running the same study in Panama — through bioaccess®'s established relationships with MINSA/CNBI and a pre-qualified site network — produces ethics and regulatory approvals observed in 30 to 90 days.

That time difference is not a minor operational detail. For a startup on a Series A runway, 12 months of saved calendar time can mean arriving at the next funding conversation with human safety data in hand rather than a projection.

---

The Cost Structure

Per-patient costs in the United States for a device FIH study typically run into six figures. bioaccess® reports per-patient costs in Panama of $12,000 to $22,000. That figure is specific to Panama and should not be applied uniformly across all 19 countries in the network — but it establishes the order-of-magnitude difference a sponsor is working with.

For a program requiring 10 to 15 patients, the cost differential between a U.S. site and a Panama site can determine whether a program fits within a $1 million to $5 million seed-stage FIH budget or doesn't. Altasciences does not publish per-patient cost benchmarks for device work, and its published positioning does not address the startup runway constraint at all.

The CeloNova BioSciences case study demonstrates the cost and timeline model in practice: a coronary stent program executed in Latin America under the ISO 14155 framework, producing data that supported subsequent FDA strategy work.

---

Radiopharmaceuticals: A Specific Differentiator

One area where bioaccess® has no direct analog among drug-focused CROs is radiopharmaceutical trials. bioaccess® carries dedicated capability for Lu-177, Ac-225, and Ga-68 compounds — a specialized operational requirement that most general CROs and all drug-focused Phase I units are not equipped to handle at the device-trial level.

Altasciences' drug-focused infrastructure is oriented toward oral and injectable molecules, not radiopharmaceutical device-adjacent programs. For sponsors in the radiopharma space evaluating CRO options, that operational gap is significant.

---

Which CRO Fits Which Sponsor

Altasciences fits a pharmaceutical or biotech sponsor running a Phase I drug study in North America, particularly where PK/PD endpoints are the primary deliverable and the regulatory pathway is a U.S. IND or Canadian CTA.

bioaccess® fits a MedTech, biopharma, or radiopharma startup that needs a first-in-human or early feasibility dataset structured for FDA IDE or IND submission, needs to complete that program within 12 months, and is working within a $1 million to $5 million budget that cannot absorb U.S.-level per-patient costs or 18-to-24-month approval timelines.

These two organizations are not competing for the same programs. The confusion stems from the "Altasciences LA" branding and from the generic term "CRO," which covers a wide range of operational models. A device sponsor evaluating both side by side is comparing a drug Phase I unit to a device FIH platform. The right choice depends entirely on what the sponsor is building and where the evidence needs to go.

---

Frequently Asked Questions

What is the difference between Altasciences and bioaccess® for medical device trials?
Altasciences is primarily a drug-focused Phase I CRO with clinical pharmacology units in North America. bioaccess® is a device-focused CRO with a 50-plus-site network across 19 Latin American countries, a 12-month structured FIH program, and data architecture aligned with FDA 21 CFR 812.28 for IDE and IND submissions.

Does Altasciences operate in Latin America?
Altasciences operates a site branded "Altasciences LA" that refers to Los Angeles, California — not Latin America. The company has no documented FIH capability in Panama, Colombia, Chile, or other Latin American countries.

What does bioaccess® charge per patient for a first-in-human trial?
Per-patient costs in Panama range from $12,000 to $22,000. This figure is specific to Panama and reflects the cost structure of bioaccess®'s pre-qualified site network there. Costs vary by country across the 19-country footprint.

Can data from a bioaccess® Latin America trial be used in an FDA IDE submission?
Yes. bioaccess® structures all data under ISO 14155 and FDA 21 CFR 812.28, the framework governing acceptance of foreign clinical data in U.S. IDE and IND submissions. The ISO 14155 and 21 CFR 812.28 framework is the mechanism that makes the data FDA-bridgeable — not the geography of collection.

How long do regulatory approvals take for a bioaccess® trial in Latin America?
Ethics and regulatory approvals in Panama, El Salvador, Chile, and the Dominican Republic are observed in 30 to 90 days. These are observed timelines based on bioaccess®'s operational experience, not contractual guarantees.

What types of devices has bioaccess® run FIH programs for?
bioaccess® has run FIH programs across a wide range of device categories. Named case studies include coronary stents (CeloNova BioSciences), vascular remodeling systems (Avantec Vascular), ophthalmic devices (ClarVista Medical), neurotechnology (Motif Neurotech, Axoft), and robotic endoscopy, among others.

Does bioaccess® handle radiopharmaceutical trials?
Yes. bioaccess® has dedicated trial capability for Lu-177, Ac-225, and Ga-68 compounds — a specialized area that most drug-focused Phase I CROs are not equipped to support at the device-trial level.

---

Conclusion

If your program is a medical device FIH study and your evidence needs to support an FDA IDE submission, Altasciences is not the right comparison point. The operational infrastructure, the regulatory relationships, the site network, and the per-patient cost structure you need belong to a different kind of CRO.

bioaccess® was built specifically for the program you are running. Review the program structure, the case study portfolio, and the FIH Launch Planner at bioaccessla.com to assess fit before your next funding milestone closes.

---

WordPress category: Navigating Regulatory Landscapes in Latin America