Category: Uncategorized

  • How bioaccess® works for a startup FIH trial in Latin America

    What to expect when you partner with bioaccess® for a first-in-human trial

    The goal of this guide is straightforward: walk you, a MedTech, Biopharma, or Radiopharma startup founder or clinical leader, through every stage of a first-in-human (FIH) trial engagement with bioaccess®, from the first conversation to the moment your first patient is enrolled.

    bioaccess® has operated as a specialist contract research organization (CRO) focused exclusively on FIH and early-feasibility trials since its co-founding in 2010. Headquartered at 1200 Brickell Ave, Miami, FL, the team has served 50+ client companies, operates across 19 Latin American and Caribbean countries, and maintains a network of 50+ pre-qualified clinical trial sites. The model is designed for one job: generate submission-ready human clinical evidence faster than is typically achievable in the U.S., while keeping that evidence anchored to U.S. Food and Drug Administration (FDA) strategy.

    Latin American ethics committees routinely review FIH protocols on a timeline set by each committee’s meeting schedule, compared with 6 to 12 months in the U.S. (bioaccessla.com/first-in-human-cro). On the regulatory side, in-country approvals commonly land in 1 to 3 months versus 3 to 12 months in the U.S. First patient enrolled runs 4 to 8 months in LATAM versus 12 to 18 months in comparable U.S. programs (bioaccessla.com/costs-and-timelines). These are published experience-based benchmarks, not guarantees for any single program.

    The engagement runs through bioaccess®’s FIH-12™ program: a 9-component clinical development methodology with a 12-month timeline guarantee. FIH-12™ covers U.S. regulatory strategy and pre-submission planning; parallel ethics and regulatory filings; pre-qualified site activation; accelerated patient enrollment; real-time remote monitoring; streamlined data management; and FDA bridge data package preparation.

    You’ll own certain decisions throughout. bioaccess® owns execution. The sections below map exactly who does what at every handoff.

    Step 1: Gather your documents before the intake call

    The pre-engagement goal is to convert whatever your startup currently has into a submission-ready dossier. The sooner you assemble these materials, the sooner bioaccess® can deliver a Pre-Sub Gap Analysis (within 48 hours of intake) and an FIH Budget and Timeline Blueprint.

    Sponsor readiness intake checklist

    Technical and protocol inputs:

    • Device or therapy description (name, mechanism of action, intended use, indication)
    • Protocol draft or study design outline (even a concept document is useful)
    • Investigator Brochure (IB) or equivalent technical file
    • Risk/benefit narrative or safety rationale summary
    • Any prior clinical use data, bench testing, or animal study summaries

    Nonclinical inputs:

    • Preclinical package summary (in vitro, in vivo, biocompatibility as applicable)
    • Supporting rationale for first-in-human dosing or device operating parameters
    • Any regulatory correspondence already received (e.g., FDA feedback, prior Pre-Sub responses)

    Regulatory and evidence strategy inputs:

    • Your intended U.S. pathway: Investigational Device Exemption (IDE), Pre-Submission (Pre-Sub), Investigational New Drug (IND), 510(k), De Novo, Premarket Approval (PMA), or Humanitarian Device Exemption (HDE). If you haven’t committed, share your current thinking.
    • Whether you’re targeting an Early Feasibility Study (EFS) under the FDA’s EFS Program or a standard FIH design

    Operational inputs:

    • Target countries or regions (Colombia/INVIMA, Panama/MINSA, El Salvador, other LATAM markets)
    • Intended site types (hospital, ambulatory, academic center)
    • Investor or board milestone pressure: dates that create hard constraints

    What happens at the handoff

    You deliver the materials above. bioaccess® produces: a Pre-Sub Gap Analysis (48-hour turnaround), an FIH Budget and Timeline Blueprint, and a country and pathway recommendation.

    Checkpoint: If you can’t provide a preclinical safety summary or a defined U.S. pathway intent, bioaccess® can still initiate a discovery plan and gap analysis. Submission timelines will extend, though. Resolve both items before you commit to an ethics submission date.

    Step 2: Lock in the U.S.-anchored regulatory strategy

    Running a trial in Latin America doesn’t mean building data that only matters in Latin America. The evidence generated through bioaccess® is structured to support subsequent FDA-related pathways, whether that’s an IDE application, a Pre-Sub package, or a broader regulatory dossier.

    FDA acceptance of foreign clinical data is governed by 21 CFR 812.28 (devices) and 21 CFR 312.120 (drugs and biologics). bioaccess® builds what it calls an “812.28-Ready Data Room” for device programs under ISO 14155 Good Clinical Practice (GCP), designed so the data structure and quality are consistent with FDA eligibility requirements. Whether FDA accepts any specific submission is FDA’s decision on a case-by-case basis. The design intent, however, is set at the start.

    Work through these four steps inside this stage

    1. Confirm your target U.S. pathway. You finalize the intended route (IDE, PMA, De Novo, 510(k), IND, or equivalent). bioaccess® needs this to architect the protocol and evidence package correctly.

    2. Complete the gap assessment. bioaccess® reviews your intake documents against the evidence requirements for your stated pathway and identifies missing elements: preclinical gaps, protocol deficiencies, IB gaps, or missing device description components.

    3. Align protocol architecture and evidence requirements. bioaccess® authors or co-authors the protocol (ISO 14155-compliant for devices; ICH E6/GCP-aligned for drugs), aligns the IB, and sets the standard operating procedures (SOPs) that will govern trial conduct.

    4. Prepare sponsor-side contributions for local submissions. You’ll need to review and sign off on the technical content of the dossier. bioaccess® handles documentation architecture and submission execution; you own accuracy of the underlying technical information.

    Who does what: You provide truthful technical content, approve final filings, and make yourself available for clarification questions with a defined turnaround time. bioaccess® handles strategy alignment, document structuring, and submission mechanics.

    Checkpoint: Before moving to ethics submission, confirm the data room structure is in place and that both sides agree on the evidence package approach for the stated 21 CFR 812.28 or 21 CFR 312.120 framing.

    Step 3: Submit to the ethics committee and manage the review

    In each target country, the FIH protocol and all subject-facing materials must pass review by a local Institutional Review Board (IRB) or ethics committee before enrollment can begin. This step runs in parallel with in-country regulatory submission wherever the jurisdiction allows it, which is one of the structural advantages that FIH-12™ exploits to compress timelines.

    The ethics submission sequence

    1. bioaccess® builds the local ethics dossier: translated and localized protocol, informed consent form (ICF), subject-facing documents, and supporting materials.
    2. bioaccess® submits the complete dossier to the ethics committee.
    3. Ethics committee query responses are managed by bioaccess®, with a defined sponsor response window for any questions requiring your technical input.
    4. Approval letter received.
    5. Proceed to national regulatory submission (where required sequentially) and site activation.

    As published on bioaccessla.com/first-in-human-cro, Latin American ethics committees commonly review FIH protocols on a timeline set by each committee’s meeting schedule. For reference, ethics timing in Colombia (INVIMA pathway) and Panama (MINSA/CNBI) also follows each committee’s meeting schedule. Under Executive Decree 21 of 2026, MINSA also registers the study in RESEGIS (receipt within 3 business days, Art. 86) and, for high-risk research, runs a technical review in parallel with the ethics review that must be resolved before the committee’s final decision (Arts. 88–91); the DNFD pharmacy review applies where Art. 95 says so. El Salvador carries a published 30-day startup benchmark.

    Where delays actually come from

    Three issues slow ethics reviews more than anything else: incomplete or inconsistently localized ICF content, protocol amendments submitted without version control, and missing principal investigator signatures or institutional authorizations. bioaccess® tracks all committee queries, manages document versioning, and flags any item that needs sponsor input on the same day it arrives.

    Checkpoint: Ethics approval letter in hand is the gate to site activation and first-patient preparation. Don’t start activation logistics before this document is received.

    Step 4: Select and activate your clinical site

    Choosing the right investigator and center matters as much as the regulatory route. For FIH and early-feasibility work, the site needs to have safety infrastructure, qualified investigators with device- or therapy-relevant experience, and the operational capacity to onboard quickly.

    bioaccess® maintains 50+ pre-qualified sites across 19 LATAM and Caribbean countries. Site activation is built into FIH-12™ and runs in parallel with late-stage ethics review wherever possible.

    Site activation sequence

    1. Run feasibility checks. bioaccess® screens candidate sites against your protocol’s inclusion/exclusion criteria, required equipment, and investigator qualifications. You review the shortlist and confirm.

    2. Build the activation plan. Contracting, budget agreements, and required institutional sign-offs are coordinated by bioaccess®. You provide device handling requirements, shipping and storage specifications, and any technical documentation the site team needs.

    3. Complete contracting and approvals workflow. Site contracts and Clinical Trial Agreements are executed. You review and approve financial terms.

    4. Conduct start-up training. bioaccess® trains the site team on the protocol, data collection systems, device handling (for device studies), and safety reporting procedures.

    5. Hold the investigator and study team kickoff. The principal investigator, sub-investigators, coordinators, and bioaccess® monitors align on the enrollment start plan.

    Who does what: You supply device or investigational medicinal product (IMP) handling requirements and technical documentation. bioaccess® coordinates site readiness, manages activation logistics, and runs the training program.

    Checkpoint: Site activation is complete and site team is trained before the first subject is screened. Both items must be confirmed in writing.

    If your first-choice site stalls: bioaccess® maintains backup sites in the same country and in alternate countries within the network. Parallel feasibility work across two sites during the ethics phase is the most reliable way to avoid a single-site bottleneck.

    Step 5: Screen, enroll, and manage the study through first patient

    First patient enrolled (FPE) is the operational milestone that converts planning into evidence. From this point, the study runs under bioaccess®’s ongoing monitoring and data management infrastructure.

    Enrollment sequence

    1. Confirm screening readiness. Site team confirms patient identification processes are active. bioaccess® verifies data capture systems are live.
    2. Execute the patient recruitment and retention plan. bioaccess® supports accelerated enrollment through site-level recruitment planning; you confirm any sponsor-specific eligibility constraints.
    3. Complete first implantation or dose administration. The principal investigator performs the procedure. bioaccess® monitors in real time.
    4. Activate ongoing monitoring. Real-time remote monitoring begins at first patient. Data flow, safety reporting, and query management run through bioaccess®’s systems.

    For context, one published device FIH study in Colombia secured regulatory approval in 5 weeks, completed first-in-human implantations, validated a safety profile in human subjects, and generated clinical data for FDA submission planning.

    Who does what post-activation: You remain available for safety and medical questions, approve any protocol amendments, and review interim data packages. bioaccess® runs monitoring, data management, safety data flow, and study execution oversight. Monthly board-ready progress reports are standard deliverables.

    Checkpoint: First patient enrolled, first data point collected, and milestone reporting cadence established. These three items confirm the study is live.

    Sponsor responsibilities and communication cadence

    The faster you respond, the faster the timeline moves. Delays in sponsor-side approvals are the most common source of onboarding slippage across all CRO engagements.

    What you own throughout the engagement:

    • Accuracy of all technical content submitted to any authority
    • Timely review and sign-off on localized materials (ICF, protocol, site contracts)
    • Response to ethics and regulatory queries requiring technical input (defined turnaround window agreed at kickoff)
    • Availability for safety decisions and protocol amendment approvals during conduct

    What bioaccess® owns:

    • Regulatory anchoring strategy and Pre-Sub/IND/IDE planning inputs
    • Ethics and in-country regulatory submission management
    • Site activation coordination across the LATAM network
    • Enrollment execution support, real-time remote monitoring, and data management
    • Assembly and delivery of the submission-supporting evidence package (812.28-Ready Data Room for devices)

    Communication structure

    Set this up before the first submission:

    • Weekly milestone review calls during the pre-submission and ethics phases
    • 24- to 48-hour sponsor response SLA for ethics or regulatory queries requiring your input
    • A named regulatory or clinical point of contact on your side who can answer technical questions quickly
    • An escalation path (to your CEO or CMO) if sign-offs lag and timeline risk accumulates

    Checkpoint: Before any document is submitted to an ethics committee or regulatory authority, confirm named document owners, distribution lists, and agreed response turnaround times are documented and shared.

    For the full phase-by-phase picture, from protocol synopsis to first patient, with durations and each country’s review order, see our guide to clinical trial site activation timelines in Latin America.

    Sample milestone timeline and readiness checklists

    Text-based onboarding milestone map

    Week 1–2: Sponsor intake documents received
                 bioaccess® delivers Pre-Sub Gap Analysis (48-hour turnaround)
                 FIH Budget & Timeline Blueprint issued
    
    Week 2–4: U.S. regulatory strategy confirmed
                 Protocol architecture and evidence package aligned
                 Ethics dossier built and localized
    
    Week 4–8: Ethics submission (LATAM ethics committees commonly review on a timeline set by each committee's meeting schedule)
                 Parallel in-country regulatory submission where jurisdiction allows
                 Site feasibility checks and backup site work running in parallel
    
    Week 8–12: Ethics approval received (gate)
                 Site activation and investigator training
                 Regulatory approval received (LATAM range: 1–3 months)
    
    Week 10–16+: Site activation confirmed (gate)
                 First patient screened
                 First patient enrolled (LATAM experience-based range: 4–8 months from program start;
                 actual timing depends on country, dossier completeness, and enrollment criteria)
    

    Country examples: ethics review in Colombia (INVIMA) and Panama (MINSA/CNBI) depends on each committee’s meeting schedule, with MINSA’s RESEGIS registration (receipt within 3 business days) and, for high-risk research, a parallel MINSA review that must be resolved before the committee’s final decision (Executive Decree 21 of 2026, Arts. 86 and 88–91; DNFD pharmacy review where Art. 95 applies); El Salvador has a 30-day startup benchmark. Chile charges no regulator fee, while Costa Rica adds a 3% CONIS levy, the only such levy in Latin America. For budgets, see the bioaccess® sample budget at bioaccessla.com/sample-budget-fih-trial-latin-america (illustrative, not a quote).

    Sponsor readiness checklist (self-validate before your first call)

    • Protocol draft or study design concept document exists
    • Device description or therapy description written and current
    • Investigator Brochure or technical file available (even in draft form)
    • Preclinical safety summary available or in preparation
    • Target U.S. regulatory pathway identified (IDE, Pre-Sub, IND, 510(k), De Novo, PMA, or HDE)
    • Target countries or preferred LATAM jurisdictions identified
    • Localized informed consent content status known (not yet started, in draft, or complete)
    • Named regulatory or clinical point of contact confirmed internally
    • Decision-makers available for document sign-offs within 48 hours

    Onboarding milestone gates

    • Gate 1: Dossier completeness confirmed by bioaccess® before ethics submission
    • Gate 2: Ethics dossier submission complete and confirmation received from committee
    • Gate 3: Ethics approval letter received
    • Gate 4: Site activation complete and site team trained
    • Gate 5: First patient enrolled and data collection active

    When things don’t go as planned

    Ethics questions arrive later than expected. bioaccess® flags the incoming query on the same day and categorizes it as sponsor-response-required or bioaccess®-answerable. If it’s yours, respond within the agreed SLA. A query that sits unanswered for a week is the fastest way to push a milestone gate by two.

    Site activation stalls. If the primary site hits a contract or institutional delay, bioaccess® moves to the pre-identified backup site in the same country. Parallel feasibility work started during the ethics phase means the backup is already partially qualified, not starting from zero.

    Enrollment lags because screening criteria are too tight. Review inclusion/exclusion criteria with the principal investigator and bioaccess® medical team. Overly restrictive criteria are typically identifiable during the protocol alignment step (Step 2), but if they surface at enrollment, a protocol amendment may be faster than waiting for a site with a different patient population.

    The path from initial consultation to first patient is predictable when every document handoff, milestone gate, and responsibility boundary is clear before work starts. bioaccess® has run this process for 50+ client companies across 19 markets. The infrastructure, pre-qualified site network, and regulatory anchoring methodology are already built.

    Book a strategy call to map your FIH onboarding timeline and get your Pre-Sub Gap Analysis within 48 hours.

  • Early feasibility vs. pivotal trial: which comes first?

    For novel medical devices, an early feasibility study (EFS) generally comes before a pivotal trial. That sequence isn’t arbitrary, it reflects the difference in what each study is actually built to answer.

    An early feasibility study is a limited clinical investigation conducted early in device development, typically enrolling a small number of subjects to generate initial clinical safety and feasibility data (FDA, EFS Program, May 2022). A pivotal study, by contrast, is designed to collect definitive evidence of a device’s safety and effectiveness for a specified intended use (NIH Clinical Center, IDE overview). One answers “does this work safely in humans at all?” The other answers “does this work well enough to support marketing authorization?”

    Getting the order wrong costs money. Launching a statistically powered pivotal study before you’ve validated basic human safety and device function is a common way to burn runway on a program that wasn’t ready for definitive endpoints.

    Why sequencing is a strategic decision

    The choice between EFS-first and direct pivotal isn’t just regulatory, it shapes your investor milestones, your time to first human data, and what evidence you’ll be able to use in a U.S. submission. These are the four decision nodes that determine the right path.

    Four decision nodes to determine your path

    Node 1: Device risk class and study significance

    Higher-risk, implantable, or novel-mechanism devices carry greater uncertainty about first-in-human (FIH) safety. When your device is first-in-class or involves a mechanism never tested clinically, nonclinical data alone rarely justifies enrolling subjects in a definitive effectiveness study. An Investigational Device Exemption (IDE) under 21 CFR Part 812 is required for significant-risk device studies in the U.S.; FDA’s EFS Program is specifically designed to support IDE-based early clinical evaluation that provides proof of principle and initial clinical safety data (FDA, September 2018).

    Node 2: Preclinical maturity and design finality

    Ask yourself two questions: Is your GLP/bench/animal package complete enough to characterize the primary safety risks? Is the device design frozen, or are you still iterating on the core mechanism? If either answer is “not yet,” EFS-first is the appropriate path. A pivotal study requires stable endpoints, a fixed device design, and enough preclinical grounding to power a statistical hypothesis. If you’re still learning what the right endpoint even is, a pivotal protocol will be mis-scoped.

    Node 3: Funding runway and time-to-milestone

    Pivotal studies require statistical powering, which means larger enrollment, longer timelines, and more operational complexity. If your current runway needs to produce human evidence that supports your next financing round, an EFS can deliver proof-of-principle data in a fraction of the time and cost of a full pivotal program. This is a planning estimate, not a guarantee, but the structural difference in enrollment size and study duration is real.

    Node 4: Intended U.S. regulatory pathway and evidence role

    Connect the study type to what you’ll actually need for your 510(k), De Novo, or PMA submission. EFS evidence doesn’t replace definitive effectiveness data, but a well-designed EFS can refine endpoint selection, validate risk controls, and inform the statistical assumptions your pivotal study will be powered on. That’s the “bridge”, not an automatic transfer of evidence, but a structured plan for how EFS findings feed your later U.S. program.

    Sequencing flowchart: EFS-first vs direct pivotal

    Work through these questions in order:

    1. Is the primary remaining uncertainty clinical safety, function, or feasibility, and is the design still evolving?

      • Yes → EFS-first. Minimum deliverables: preclinical package gap analysis, IDE/EFS pre-submission outline, IRB (Institutional Review Board) plan under 45 CFR Part 46.
      • No, proceed to question 2.
    2. Is your device design stable, and does your GLP/nonclinical package address primary safety risks with enough rigor to support definitive endpoints?

      • Yes → Consider direct pivotal path. Minimum deliverables: statistical analysis plan (SAP) draft, endpoint specification, and protocol architecture.
      • No → Return to EFS-first.
    3. Can your current budget and timeline support a multi-year, statistically powered study?

      • No → EFS-first is the practical route. Use EFS to generate investor-grade proof-of-principle and refine assumptions for future pivotal planning.
      • Yes, and nonclinical support is sufficient → Direct pivotal may be appropriate.

    One caution: EFS-first isn’t appropriate when nonclinical evidence already resolves the clinical unknowns and the device design is fully mature. In that case, adding an EFS stage delays marketing authorization without generating meaningfully new information.

    Three scenarios with checkpoints

    Scenario 1: Startup with a limited budget and tight runway

    Decision nodes: Novel device mechanism (Node 1 = high risk/uncertainty), preclinical package partially complete (Node 2 = design iterating), limited runway insufficient for multi-year pivotal (Node 3), targeting a future PMA (Node 4).

    Recommended path: EFS-first. A small-enrollment EFS in a jurisdiction with faster ethics approval timelines can generate FIH proof-of-principle while preserving capital for the pivotal phase.

    Checkpoint: Preclinical package gap list completed; evidence role for EFS documented in protocol architecture; ethics/IRB plan scope validated.

    Scenario 2: High-risk implant (e.g., novel cardiovascular device)

    Decision nodes: Class III or equivalent (Node 1 = requires IDE, significant risk), GLP studies done but design still being refined based on animal data (Node 2 = not design-final), multi-year runway may be available but FIH safety validation is the immediate unknown (Node 3), PMA pathway intended (Node 4).

    Recommended path: EFS-first. The clinical safety and device function gap must be closed before a pivotal study can be responsibly scoped. What must be true in preclinical maturity before EFS: biocompatibility testing complete, primary failure mode characterized in animals, and device delivery/implant procedure validated in bench/animal model.

    Checkpoint: Risk control validation complete; EFS protocol drafted with explicit evidence role for later pivotal SAP assumptions; ethics submission package ready.

    Scenario 3: Lower-risk device with a stable design

    Decision nodes: Class II equivalent (Node 1 = lower risk), bench and animal testing complete, design frozen (Node 2 = mature), adequate runway (Node 3), 510(k) or De Novo pathway (Node 4).

    Recommended path: Direct pivotal (or a smaller traditional feasibility study if some clinical uncertainty remains). The nonclinical package may be sufficient to support definitive effectiveness endpoints without requiring a separate FIH proof-of-principle stage.

    Checkpoint: Statistical hypothesis and primary endpoint specified; protocol architecture drafted; site selection criteria defined.

    How EFS evidence can support later U.S. submissions

    If your EFS is conducted outside the U.S., the data can potentially be considered by FDA under 21 CFR 812.28, which governs acceptance of foreign clinical data to support an IDE or marketing application. FDA acceptance is determined per submission, there’s no automatic pathway.

    To improve defensibility, conduct the study under ISO 14155, the international standard for good clinical practice in medical device clinical investigations. Align documentation from day one: protocol, informed consent forms, monitoring and QA records, and a clinical study report (CSR) built to submission-ready standards with clear data traceability.

    Operationally, this means building your “evidence drawer” at study start, not after. Every source document category that a regulatory reviewer might request should be planned before enrollment opens.

    Documentation checklist to align at study start:

    • Protocol with explicit evidence role statement
    • Informed consent forms compliant with applicable IRB/ethics requirements (45 CFR Part 46 for U.S. sites)
    • Monitoring and QA plan with deviation tracking
    • Data management plan with traceability to source documents
    • CSR-ready output structure and statistical analysis framework
    • Data room architecture for post-study regulatory submissions

    bioaccess® structures its FIH-12™ program around exactly this approach: FDA-anchored strategy combined with ISO 14155 protocol architecture and CSR/evidence package delivery as a single accountable output across nine workstreams. In selected Latin American jurisdictions, ethics and regulatory approvals have been observed in 30 to 90 days (a planning range based on experience, not a guarantee), which can support an earlier first-patient date than U.S. timelines typically allow.

    What you’ve accomplished and where to go next

    Working through the four decision nodes and the flowchart above gives you a defensible, documented rationale for your sequencing choice. That rationale matters to investors, to ethics committees, and to FDA reviewers who will eventually evaluate your submission.

    Your immediate next steps:

    1. Complete the decision checklist (all four nodes documented with your current answers).
    2. Identify preclinical readiness gaps before committing to a study type.
    3. Draft the evidence role statement: what you need this study to do for your next regulatory or financing milestone.
    4. Map the sequencing decision to your intended U.S. pathway with a team that has executed this before.

    Talk with bioaccess® about whether an early feasibility study (EFS) or a pivotal path fits your device and runway.

  • CRF Medical Abbreviation: What It Means in Device Trials

    CRF Medical Abbreviation: What It Means in Device Trials

    Category: General

    A case report form sits at the center of every clinical trial, yet the CRF medical abbreviation still trips up founders and clinical operations leads who are new to regulated research. If you are preparing for a first-in-human (FIH) study or structuring data for an IDE submission, understanding what a CRF is, how it is designed, and what standards govern it is not optional. It is the foundation on which your entire evidence package rests.

    This article explains the CRF from first principles, covers the distinction between paper and electronic formats, walks through the regulatory standards that apply specifically to medical device trials, and addresses the design decisions that most affect data quality at submission.


    What Does CRF Stand For in Clinical Research?

    CRF stands for Case Report Form. It is a structured data collection instrument used in clinical trials to record every observation, measurement, and event specified in the study protocol for each individual participant. The form captures data at defined time points — from screening through the final follow-up visit — and serves as the primary record that flows into the clinical database.

    The CRF is not the same as a source document. Source documents are the original records created at the point of care: hospital charts, lab printouts, imaging reports. The CRF is a transcription of the relevant data points from those source documents into a standardized format that can be verified, audited, and submitted to a regulatory authority.

    That distinction matters for device trials in particular. Under FDA 21 CFR 812 and ISO 14155, every CRF entry must be traceable back to a source document. If a field in the CRF cannot be reconciled with a source record, that data point is at risk during an FDA inspection.


    Paper CRF vs. Electronic CRF (eCRF)

    Early clinical trials used paper CRFs: multi-part carbon forms completed by hand at the investigator site and couriered to the sponsor for manual entry. The format was slow, error-prone, and difficult to audit.

    Electronic case report forms — eCRFs — are now standard practice. Hosted within an Electronic Data Capture (EDC) system, they allow real-time data entry, automated range checks, and immediate query generation when an entry falls outside protocol-specified parameters. For a device startup running a lean FIH study, the eCRF also eliminates the transcription layer, cutting one common source of data errors before they reach the database.

    The regulatory expectations are the same regardless of format. Whether a CRF is paper or electronic, it must satisfy the ALCOA+ attributes: data must be Attributable, Legible, Contemporaneous, Original, and Accurate — and in the extended ALCOA+ framework, also Complete, Consistent, Enduring, and Available. An eCRF system that enforces mandatory fields, timestamps entries, and logs every change with an audit trail makes ALCOA+ compliance structurally easier to demonstrate.


    Regulatory Standards That Govern CRF Design in Device Trials

    ICH E6 and ISO 14155

    For drug trials, ICH E6(R2) and its successor ICH E6(R3) set the GCP framework governing CRF requirements. For medical device trials, ISO 14155 is the governing standard. It defines the clinical investigation requirements for medical devices intended for human subjects and specifies that the CRF must be designed to collect all protocol-required data in a manner that supports data integrity and regulatory review.

    When a device trial is run outside the United States, FDA 21 CFR 812.28 provides the framework for how foreign clinical data can be used in a U.S. IDE or IND submission. Data collected under ISO 14155 and structured per 21 CFR 812.28 is eligible for use in those submissions. That eligibility depends, in part, on CRF design: if the form does not capture the fields the FDA expects to see in a submission-ready evidence package, the data cannot fill the regulatory gap — regardless of how well the study was executed.

    CDASH and Standardization

    The Clinical Data Acquisition Standards Harmonization (CDASH) model, maintained by CDISC, provides a standard set of data collection fields and their definitions. CDASH-aligned CRFs make it significantly easier to convert collected data into CDISC SDTM format for regulatory submission. For device startups preparing an IDE package, building CDASH alignment into the CRF at the protocol development stage avoids a costly, time-consuming data mapping exercise later.


    CRF Design: What Gets It Right and What Gets It Wrong

    Field Design and Data Integrity

    Most data quality problems originate at the field design level. Ambiguous labels, free-text fields where coded responses should be used, and missing visit windows all generate queries that slow database lock and delay submission.

    A 2026 guide published by ccrps.org identifies 30 high-impact CRF fields that must be captured cleanly to ensure trial data integrity. The implication for device sponsors is direct: field-level decisions made during protocol development determine whether the database locks on schedule or whether the trial team spends months resolving queries before submission.

    For device trials specifically, the CRF must include fields that drug trial templates simply do not cover: device identification (lot number, serial number, version), implant and explant dates, device malfunctions, and any unanticipated adverse device effects (UADEs). These fields are required under ISO 14155 and must be present in the CRF design before the first patient is enrolled.

    Lean CRF Design Without Losing Required Data

    There is a real tension in CRF design between capturing everything the protocol requires and keeping the form manageable for investigators at busy clinical sites. Overloaded CRFs increase site burden, slow data entry, and generate more queries — not fewer.

    A 2019 report from hfcollaboratory.com documented this directly in the context of heart failure device trials: a lean case report form reduced the number of distinct data items from 176 to 75 baseline items without compromising the data required for the primary endpoint. The lesson is not that shorter is always better. Every field in the CRF should be justified by the protocol's endpoints and the regulatory submission requirements — nothing more, nothing less.

    Screening and Randomization Fields

    The fields governing eligibility are among the most consequential in the entire CRF. Incomplete or inconsistently captured inclusion and exclusion criteria produce protocol deviation findings that can affect the integrity of the intent-to-treat population. For a small FIH study where every patient in the safety cohort counts, a protocol deviation at screening is not a minor administrative issue.


    CRFs in First-in-Human Device Trials: What Changes at This Stage

    FIH studies are not Phase III trials with hundreds of patients and a powered primary endpoint. They are typically small safety and feasibility studies designed to demonstrate that a device can be used in humans without unacceptable risk and to generate preliminary performance data. The CRF reflects that purpose.

    The form must capture safety data comprehensively: adverse events, serious adverse events, device malfunctions, and UADEs at every visit. It must also capture the performance endpoints specified in the protocol — in a device trial, those often include procedural success criteria, imaging or functional assessments, and patient-reported outcomes. Because the FIH dataset will anchor the IDE or IND submission, the CRF must be designed with the submission endpoint in mind from the start, not retrofitted after data collection is complete.

    This is where CRO experience with the regulatory submission pathway matters. A CRO that has structured CRFs for IDE submissions knows which fields the FDA will scrutinize, which data points support the Pre-Sub strategy, and how CRF design connects to the statistical analysis plan. A generic template borrowed from a drug trial or an earlier-generation device study is unlikely to capture the device-specific fields a submission reviewer will look for.


    Automated CRF Filling: Where NLP and LLMs Are Heading

    One area of active development in clinical data management is the automated population of CRF fields from unstructured clinical notes using natural language processing (NLP) and large language models (LLMs). The appeal is straightforward: if a model can read a clinical note and extract the relevant data points directly into the CRF, it reduces transcription burden and the queries that come from manual entry errors.

    Research published in 2026 by ACL Anthology on a two-stage LLM pipeline for CRF filling reported a macro F1 score of 0.56 for both English and Italian in the CRF Filling Shared Task 2026. A separate 2026 dataset described by lrec-conf.org for dyspnea assessment included 134 medical items with predefined value sets, illustrating the complexity of mapping free-text clinical language to structured CRF fields at scale.

    These results are promising but not yet at the accuracy threshold required for unreviewed regulatory submission. For device sponsors in 2026, automated CRF filling tools are worth monitoring — particularly for high-volume data entry tasks — but human verification remains a regulatory requirement for data submitted to the FDA.


    How CRF Quality Affects the Submission-Ready Evidence Package

    A well-designed CRF is not just a data collection tool. It is the instrument that converts clinical observations into a regulatory submission. When the CRF is built around the protocol's endpoints, aligned to CDASH, and structured to capture the device-specific fields required under ISO 14155, the path from database lock to submission-ready evidence package is direct.

    When it is not, the path is anything but. Queries accumulate, database lock is delayed, data mapping to CDISC formats requires manual intervention, and the submission timeline extends. For a startup with a 12-month financial runway and an investor milestone tied to IDE submission, a CRF design problem discovered at database lock is a serious operational risk.

    This is one reason bioaccess® builds CRF design into the protocol development workstream of the FIH-12™ program, rather than treating it as a downstream data management task. The FIH-12™ program covers all nine workstreams from FDA strategy alignment through delivery of the submission-ready evidence package, with CRF design anchored to the sponsor's specific IDE or IND pathway from day one.

    Case studies published at bioaccessla.com/case-studies/cook-group and bioaccessla.com/case-studies/celonova-biosciences illustrate how CRF architecture integrates with multi-site FIH execution under INVIMA and other Latin American regulatory frameworks. The ClarVista Medical case study shows how a well-structured evidence package — built from a CRF designed for submission — supported a clinical program that ultimately led to acquisition by Alcon.

    If you are at the stage of designing your FIH protocol and want to understand how CRF design connects to your FDA Pre-Sub strategy and submission timeline, the bioaccess® FIH-12™ program overview is the starting point.


    Frequently Asked Questions

    What does CRF stand for in medical and clinical trial contexts?
    CRF stands for Case Report Form. It is the structured instrument used in clinical trials to record protocol-specified data for each participant, from screening through final follow-up. Every data point submitted to a regulatory authority in a clinical evidence package originates from the CRF.

    How is a CRF different from a source document?
    A source document is the original record created at the point of care — a hospital chart, lab report, or imaging file. The CRF is a transcription of the relevant data points from those source documents into a standardized format. Under FDA 21 CFR 812 and ISO 14155, every CRF entry must be traceable back to a source document.

    What regulatory standards govern CRF design in medical device trials?
    ISO 14155 is the primary standard for medical device clinical investigations. ICH E6(R2) and ICH E6(R3) govern GCP requirements more broadly. When foreign clinical data is intended for use in a U.S. IDE or IND submission, FDA 21 CFR 812.28 applies. CDASH alignment is the standard approach for structuring CRF fields to support CDISC SDTM conversion at submission.

    What are ALCOA+ attributes and why do they matter for CRF data?
    ALCOA+ is the data integrity framework applied to clinical trial records. It requires that data be Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, and Available. An eCRF system with mandatory fields, audit trails, and timestamped entries makes ALCOA+ compliance structurally easier to demonstrate during an FDA inspection.

    What device-specific fields must a CRF include that drug trial templates typically omit?
    Device CRFs must capture device identification data (lot number, serial number, software version), implant and explant dates, device malfunctions, and unanticipated adverse device effects (UADEs). These fields are required under ISO 14155 and must be present before the first patient is enrolled.

    Can CRFs be automatically filled using AI or large language models?
    Research published in 2026 by ACL Anthology on an LLM pipeline for CRF filling reported a macro F1 score of 0.56, indicating meaningful but imperfect performance. Automated tools can reduce transcription burden for high-volume tasks, but human verification of CRF entries remains a regulatory requirement for data submitted to the FDA.

    How does CRF design affect the timeline for IDE submission?
    A CRF that is not aligned to the protocol's endpoints, not built to CDASH, or missing device-specific required fields will generate queries at database lock that delay submission. For a startup with a milestone tied to IDE filing, a CRF design problem discovered late in the trial is both an operational and financial risk. Building CRF design into protocol development — rather than treating it as a downstream task — is how that outcome is avoided.


    The CRF Is a Submission Instrument, Not a Paperwork Exercise

    Every field in your CRF is either supporting your IDE submission or creating a problem for it. The design decisions made during protocol development determine which outcome you get. For device startups running FIH studies in Latin America under ISO 14155 and targeting FDA submission under 21 CFR 812.28, the CRF is the connective tissue between clinical execution and regulatory approval.

    Treat it as a submission instrument from the first draft. Build it around your endpoints, align it to CDASH, capture every device-specific field ISO 14155 requires, and verify that every entry can be traced to a source document. That discipline at the design stage is what makes the path from database lock to submission-ready evidence package a straight line.

    Learn more at bioaccessla.com.

  • ISO 14155 Explained: What MedTech Sponsors Must Know

    ISO 14155 Explained: What MedTech Sponsors Must Know

    Meta description: ISO 14155 governs medical device clinical investigations worldwide. Learn what the 2026 edition requires, what changed, and how to structure your FIH trial data for FDA and CE submissions.

    Category: Navigating Regulatory Landscapes in Latin America


    If you are planning a first-in-human (FIH) medical device trial, ISO 14155 is the standard that governs how that investigation must be designed, conducted, and documented. It defines Good Clinical Practice (GCP) for medical device clinical investigations and serves as the foundation regulators in the EU, Latin America, and the United States use to determine whether your clinical data is credible and submission-ready.

    This article covers what ISO 14155 requires, what changed in the 2026 edition, how it connects to FDA 21 CFR 812.28 and EU MDR, and what MedTech sponsors need to act on now to keep their programs compliant.


    What ISO 14155 Is and Why It Applies to Your Trial

    ISO 14155 is the international standard for GCP in clinical investigations of medical devices for human subjects. It defines the responsibilities of sponsors, investigators, and Ethics Committees; establishes requirements for clinical investigation plans (CIPs), informed consent, adverse event reporting, and data integrity; and provides the framework regulators use to determine whether foreign clinical data is acceptable for market authorization.

    Any sponsor running a device study intended to support a CE mark, an FDA Investigational Device Exemption (IDE), or a market registration in Latin America should treat ISO 14155 compliance as non-negotiable. Regulatory authorities in Colombia (INVIMA), Brazil (ANVISA), Panama (MINSA/CNBI), and Chile (ISP/MINSAL) all reference it when evaluating clinical evidence packages.

    The standard has been revised several times since its original publication. According to qservegroup.com, ISO 14155 was first published in 1996 and has since been revised in 2003, 2011, and 2020.


    ISO 14155:2026 — The Current Edition

    The standard entered a new phase in 2026. As reported by specculo.com, ISO 14155:2026 was published on 23 March 2026 and replaces ISO 14155:2020. Greenlight.guru confirms that this fourth edition supersedes the third edition from 2020.

    The practical implication is direct: if your protocol, CIP, or quality system references ISO 14155:2020, it references a withdrawn standard. That is not a minor administrative detail. Regulators and notified bodies reviewing your clinical evidence package will check which version you followed.

    One important nuance for EU-based programs: according to greenlight.guru, the 2020 edition plus a 2024 amendment remained the version harmonized under the EU Medical Device Regulation (MDR) as of the time of that reporting. Sponsors operating under EU MDR should confirm the current harmonization status directly with their notified body, because harmonization timelines for EN ISO 14155:2026 may differ from the ISO publication date.


    Is There a Transition Period?

    This is one of the most common questions sponsors ask, and the answer is less comfortable than most would prefer. According to mdxcro.com, there is no defined transition period for ISO 14155:2026. Nimonik notes that while many ISO standards offer a 3-year transition period, the updates in ISO 14155:2026 are immediately applicable.

    Sponsors cannot assume they have financial runway to migrate at their own pace. If you are launching a new study, your CIP and supporting documentation should be written to the 2026 edition from the start. If you have an ongoing study written to the 2020 edition, a gap assessment is the first practical step — not a deferred one.


    What Changed in the 2026 Edition

    The 2026 revision is not a cosmetic update. Several areas of the standard received substantive changes that affect how sponsors structure their programs.

    Risk Management: Separating Device Risk from Procedural Risk

    One of the most operationally significant changes is the clearer separation of device-related risks from procedure-related risks. Earlier editions addressed risk management at a higher level of abstraction. The 2026 edition expects sponsors to distinguish between risks inherent to the investigational device itself and risks that arise from the clinical procedure used to implant or apply it.

    For sponsors writing their CIPs, this means your risk file and your clinical investigation plan need to speak to each other explicitly. A risk that appears in your device risk management file should have a corresponding monitoring or reporting mechanism in the CIP.

    Clinical Events Committees and Data Monitoring Committees

    The 2026 edition provides more structured guidance on when Clinical Events Committees (CECs) and Data Monitoring Committees (DMCs) are expected. The threshold is not simply study size — it is study risk profile. If your device addresses a serious or life-threatening indication, or if your primary endpoint involves events that require independent adjudication to avoid bias, the standard now provides clearer language that supports — and in some contexts expects — independent oversight structures.

    For early feasibility studies with small patient populations, this does not automatically mean every study requires a full DMC. Sponsors should document their rationale for the oversight structure they choose, because that rationale will be reviewed.

    The 2026 edition strengthens requirements around informed consent documentation and the process of re-consenting subjects when the investigation changes materially. Consent forms must more explicitly address the distinction between investigational procedures and standard-of-care procedures, and the subject's right to withdraw must be framed in language that is unambiguous even to non-specialist readers.

    For sponsors running trials across multiple countries — including Latin American sites where language and literacy levels vary across patient populations — this has direct implications for how consent documents are translated, back-translated, and reviewed by local Ethics Committees (ECs).

    The delineation between sponsor responsibilities and investigator responsibilities is sharper in the 2026 edition. Sponsors cannot delegate oversight by pointing to the investigator. The standard expects sponsors to have documented processes for monitoring, deviation management, and escalating safety signals — regardless of whether those processes are executed by in-house staff or a contract research organization.

    This is particularly relevant for under-resourced MedTech startups that rely on a single CRO to manage all operational workstreams. The sponsor remains accountable. The CRO executes. That distinction matters when a regulatory authority reviews your trial master file.


    How ISO 14155 Connects to FDA 21 CFR 812.28

    For US-based sponsors, the connection between ISO 14155 and FDA submissions is direct. Under 21 CFR 812.28, the FDA accepts foreign clinical data from investigations conducted under ISO 14155 to support IDE applications and subsequent premarket submissions. The data is not automatically approved — it is accepted as meeting the FDA's standard for foreign clinical evidence when the investigation was conducted in compliance with ISO 14155.

    This is the regulatory bridge that makes Latin American FIH trials viable for US-bound programs. A study run in Panama, Colombia, or Chile under ISO 14155 protocol architecture, with data structured per FDA 21 CFR 812.28, can support an IDE submission. The clinical evidence package does not need to be regenerated in the United States.

    bioaccess® builds every FIH-12™ program on ISO 14155 protocol architecture from the outset. The nine-workstream engagement covers protocol development, site activation, patient enrollment, data management, and delivery of a submission-ready clinical evidence package — structured to satisfy both ISO 14155 and FDA 21 CFR 812.28 requirements simultaneously.


    ISO 14155 in Practice: What Sponsors Need to Update First

    If you are preparing a new FIH study or reviewing an ongoing one, the practical migration sequence looks like this:

    Clinical Investigation Plan (CIP): The CIP is the primary document that must reference ISO 14155:2026. If your CIP was written to the 2020 edition, conduct a gap assessment against the 2026 requirements before your next EC submission. Pay particular attention to risk management language, oversight structures, and the consent process description.

    Informed Consent Forms: Review all consent documents against the 2026 requirements for clarity of language, explicit separation of investigational and standard-of-care procedures, and withdrawal rights. For multi-country studies, this review must happen at each site.

    Sponsor SOPs: Any standard operating procedure that references ISO 14155:2020 needs to be updated — including monitoring plans, deviation management procedures, and adverse event reporting processes.

    Investigator's Brochure and Risk File Alignment: The 2026 edition's clearer risk separation requirements mean your risk file and investigator's brochure need to be reviewed together, not in isolation. Risks identified in the device risk management file should be traceable to monitoring procedures in the CIP.

    Oversight Structure Documentation: If your study does not include a CEC or DMC, document why. The 2026 edition does not mandate these structures for every study, but it expects sponsors to have a defensible rationale.


    ISO 14155 and Latin American Regulatory Submissions

    Latin American regulatory authorities reference ISO 14155 when evaluating clinical evidence packages for device approvals. INVIMA in Colombia, ANVISA in Brazil, MINSA/CNBI in Panama, and ISP/MINSAL in Chile all operate within frameworks that recognize ISO 14155-compliant clinical data.

    This alignment is what makes the 30-to-90-day ethics and regulatory approval timelines observed in Panama, El Salvador, Chile, and the Dominican Republic achievable without sacrificing data quality. The standard is the same. The approval infrastructure is faster.

    The Cook Group case study illustrates this in practice: a multi-site FIH study in Colombia, with 142-plus INVIMA regulatory submissions managed, built on ISO 14155-compliant protocol architecture. The Envveno Medical program followed a similar path — LATAM FIH execution anchored to the sponsor's US FDA strategy, resulting in the first-ever FDA IDE for a non-surgical replacement venous valve. The ClarVista Medical program ran FIH studies through Latin America and ultimately resulted in an acquisition by Alcon — a clinical and regulatory strategy that worked because the data was structured to travel.

    The CeloNova BioSciences COBRA PzF coronary stent study is another example of ISO 14155-compliant execution in Latin America supporting a global evidence strategy for a polymer-free drug elution device.


    Practical Takeaways for MedTech Sponsors

    ISO 14155:2026 is the current standard. There is no transition period. If you are writing a new CIP, it should reference the 2026 edition. If you have an ongoing study, a gap assessment is not optional — it is the first step in protecting the integrity of your clinical evidence package.

    The standard's requirements around risk separation, oversight structures, and informed consent are more precise than in prior editions. That precision is an asset for sponsors who build their programs correctly from the start, and a liability for those who treat the standard as a documentation formality.

    For sponsors planning FIH trials in Latin America, ISO 14155 compliance is not an additional requirement layered on top of regional regulations. It is the shared framework that makes clinical data generated in Panama, Colombia, or Chile acceptable to the FDA under 21 CFR 812.28 and to EU notified bodies under MDR.

    If you are at the pre-submission or IDE-ready stage and want to understand how ISO 14155-compliant FIH execution in Latin America fits your regulatory strategy, learn more at bioaccessla.com.


    Frequently Asked Questions

    What is ISO 14155 and who needs to follow it?
    ISO 14155 is the international standard for Good Clinical Practice in medical device clinical investigations. Any sponsor conducting a clinical study to support CE marking, FDA IDE or premarket submissions, or regulatory approvals in markets that recognize ISO 14155 — including Colombia, Brazil, Panama, and Chile — must design and conduct their investigation in compliance with its requirements.

    What is the current version of ISO 14155?
    The current edition is ISO 14155:2026, the fourth edition, published on 23 March 2026. It replaces ISO 14155:2020. According to specculo.com, the previous European version was also withdrawn when ISO 14155:2026 was adopted at the European level as EN ISO 14155:2026.

    Is there a transition period for ISO 14155:2026?
    According to mdxcro.com, there is no defined transition period for ISO 14155:2026. Nimonik notes that while many ISO standards offer a 3-year transition period, ISO 14155:2026 updates are immediately applicable. Sponsors should treat the 2026 edition as the operative standard for any new or ongoing study.

    How does ISO 14155 connect to FDA submissions?
    Under FDA 21 CFR 812.28, the FDA accepts foreign clinical data from investigations conducted under ISO 14155 to support IDE applications and premarket submissions. A FIH study run in Latin America under ISO 14155 protocol architecture can generate data accepted for US regulatory submissions — it does not need to be replicated in the United States.

    What are the most important changes in ISO 14155:2026 versus the 2020 edition?
    The 2026 edition introduces clearer separation of device-related risks from procedure-related risks, more structured guidance on when Clinical Events Committees and Data Monitoring Committees are expected, strengthened informed consent requirements, and sharper delineation of sponsor versus investigator responsibilities.

    Does ISO 14155 apply to FIH trials run in Latin America?
    Yes. Regulatory authorities including INVIMA (Colombia), ANVISA (Brazil), MINSA/CNBI (Panama), and ISP/MINSAL (Chile) recognize ISO 14155-compliant clinical data. Running a FIH study in Latin America under ISO 14155 protocol architecture does not reduce the scientific or regulatory standing of the data — it is the same standard applied in a faster-approval environment.

    What should sponsors update first when migrating to ISO 14155:2026?
    Start with the Clinical Investigation Plan — it is the primary document referencing the standard and the one most likely to be reviewed by an Ethics Committee or regulatory authority. Follow with informed consent forms, sponsor SOPs, and a documented rationale for your oversight structure (CEC/DMC or absence thereof). Risk file and investigator's brochure alignment should be reviewed together, not separately.

  • ANVISA device clinical trial submission guide for Brazil

    What ANVISA actually authorizes (and what it doesn’t)

    ANVISA, Brazil’s Agência Nacional de Vigilância Sanitária, is the federal health authority responsible for authorizing clinical investigations of medical devices conducted on Brazilian territory. Its jurisdiction covers the investigation itself: the protocol, the device, the risk controls, the investigator qualifications, and the conditions under which the device may be imported for study purposes. What ANVISA does not grant is marketing authorization or commercial registration. Getting a clinical investigation approved and getting a device registered for sale in Brazil are two entirely separate regulatory acts, governed by different processes and different rules.

    This distinction matters more than most early-stage sponsors expect. An ANVISA “anuência” (authorization) for a clinical investigation tells you the agency reviewed your Dossiê de Investigação Clínica de Dispositivos Médicos (DICD) and found sufficient grounds to permit the study. It says nothing about the device’s commercial status and cannot substitute for ANVISA registration if the sponsor later intends to commercialize the device in Brazil.

    The governing regulation for device clinical investigations is Resolução da Diretoria Colegiada (RDC) nº 837, issued December 13, 2023. RDC 837/2023 replaced previous frameworks and sets the current rules for how clinical investigations must be designed, documented, submitted, and conducted. Every sponsor working in Brazil needs this document as a primary reference, not a secondary one.

    Under RDC 837/2023, whether ANVISA authorization is required depends on a combination of device risk class and study purpose. Higher-risk devices (generally Class III and IV under the Brazilian classification system) intended to support regulatory outcomes in Brazil require formal DICD submission and ANVISA anuência before any human use. Lower-risk studies or studies using already-registered devices may qualify for exemption from ANVISA authorization in some circumstances. But exemptions from ANVISA review do not exempt sponsors from the ethical approval pathway, which runs in parallel through Brazil’s CEP/CONEP system and is non-negotiable regardless of device risk class.

    Deciding whether you need a formal DICD submission

    Use this decision logic before you file anything:

    1. Is the device registered in Brazil for the intended indication? If yes and the study uses standard care parameters, a reduced pathway may apply. Confirm against RDC 837/2023 exemption criteria.
    2. Is the study intended to generate evidence for ANVISA registration, a de novo assessment, or Brazilian regulatory outcomes? If yes, full DICD submission is required.
    3. Is the device unregistered in Brazil and implantable or life-sustaining? Full DICD and ANVISA anuência are required regardless of registration status abroad.
    4. Is this a first-in-human (FIH) or early feasibility study (EFS)? Almost without exception, FIH/EFS programs for novel devices require full DICD submission. The rationale is straightforward: ANVISA needs to see the preclinical safety package, risk controls, and monitoring plan before human exposure begins.

    Even if you conclude that ANVISA authorization isn’t required for a specific study, Brazilian law (Resolução CNS nº 466/2012, December 12, 2012) mandates ethical review for any research involving human subjects. The CEP/CONEP pathway runs regardless of ANVISA’s involvement.

    For FIH/EFS sponsors specifically: don’t underestimate this sequencing challenge. Getting ANVISA anuência and CEP/CONEP approval to land at roughly the same time takes deliberate planning. A gap between the two creates an “activation dead” period where you have one approval but can’t legally start.

    DICD dossier checklist: what goes into your submission

    ANVISA’s official “Guia de Investigação Clínica de Dispositivos Médicos” (Guia 30, published on gov.br) provides the structured framework for organizing your DICD. Follow it precisely. Reviewers expect documents in the structure the guide specifies.

    Core documents every DICD must include:

    • Clinical investigation protocol (versioned, dated, signed by principal investigator and sponsor representative)
    • Investigator’s Brochure or equivalent investigator information document, summarizing the device’s preclinical and prior clinical evidence
    • Informed consent materials (TCLE – Termo de Consentimento Livre e Esclarecido), in Portuguese, covering the specific risks and procedures described in the protocol
    • Device technical file: includes device description, specifications, classification justification, applicable standards, and manufacturing information
    • Risk management documentation, aligned to ISO 14971 or equivalent, showing identified hazards and mitigations
    • Preclinical evidence package: bench, animal, or simulation data proportionate to the device’s risk profile
    • Adverse event reporting plan and monitoring strategy
    • Investigator qualifications (CVs, certifications relevant to the device type and procedures involved)
    • Site qualification documentation for each clinical site

    Evidence alignment check (do this before you file):

    The most common reason DICD submissions receive pendencies is internal inconsistency, not missing documents. Build a cross-walk table:

    • Protocol endpoints → Does the IB present data that supports those specific endpoints?
    • Risk controls in the risk management file → Are the same risks reflected in the consent form (TCLE)?
    • Monitoring frequency in the protocol → Is it consistent with the adverse event reporting plan?
    • Device version in the technical file → Does it match the device version referenced in the protocol?

    If any cell in that cross-walk is blank or inconsistent, fix it before filing.

    Document control warning: Every document must carry the same version number and date across both the ANVISA submission and the ethics submission to CEP/CONEP. Version drift between the two dossiers is a documented source of pendencies at both ends.

    Local representation requirements

    Foreign sponsors cannot submit directly to ANVISA without an in-country presence or a designated local representative. Under RDC 837/2023 and ANVISA’s broader regulatory framework, the sponsor of record for a device clinical investigation in Brazil must either be a Brazilian legal entity or must appoint a qualified local representative (sometimes referred to in the sponsor/ORPC context) with legal authority to sign submissions, receive official communications, and respond to pendencies.

    Action steps:

    1. Before preparing the dossier, confirm who will serve as the sponsor of record in Brazil and ensure they have an active CNPJ (Brazilian tax identifier).
    2. Confirm the designated individual or entity who will manage ANVISA portal access and sign the petitions.
    3. Document the authority chain clearly. ANVISA may issue pendencies requiring responses within fixed windows; whoever receives those communications must have decision authority to act quickly.

    Submitting the DICD: portal, petition code, and fees

    ANVISA clinical investigation submissions are handled through the electronic petitioning system on the gov.br/ANVISA portal. The specific petition subject for the DICD authorization is classified under “Produtos para a saúde,” with the petition type described as “Anuência em Processo do Dossiê de Investigação Clínica de Dispositivos Médicos (DICD),” subject code 80104 in ANVISA’s Documentos de Instrução system.

    The submission workflow proceeds in this sequence:

    1. Prepare the complete DICD dossier (protocol-ready, versioned, cross-walked)
    2. Register or confirm the legal entity on ANVISA’s portal
    3. Open the petition under subject code 80104, attach all required documents per the Documentos de Instrução checklist
    4. Pay the applicable Taxa de Fiscalização de Vigilância Sanitária (TFVS) fee via GRU (Guia de Recolhimento da União). The exact fee is calculated based on company size and economic class. ANVISA publishes the fee schedule; confirm the current amount directly with ANVISA or through the petitioning portal at the time of filing. Do not assume a fee amount from third-party sources, as the schedule can change.
    5. Monitor the petition for validation/triage outcome (ANVISA confirms whether the dossier is technically acceptable for review)
    6. Respond to any pendencies within the specified window
    7. Receive the formal anuência (authorization) document
    8. Activate the study only after both ANVISA anuência and CEP/CONEP approval are in hand

    Practical tips for faster technical acceptance: use descriptive, standardized file names (protocol_v1.0_date.pdf, not “final_final2.pdf”), stay within the portal’s file size limits per attachment, and submit in Portuguese where required. Dossiers that arrive without a matching Documentos de Instrução checklist or with mismatched file naming conventions frequently bounce at validation before they reach technical review.

    What to expect on timeline

    No fixed date can be promised, but the milestone model below reflects what sponsors typically encounter:

    Milestone Typical range
    Dossier preparation (complete, cross-walked) 8–16 weeks
    ANVISA validation/triage 2–4 weeks after filing
    Technical review period 30–90 days (may be extended if pendencies are issued)
    Pendency response cycle 30–60 days per cycle
    CEP site review (local ethics committee) 30–60 days
    CONEP review (if triggered) Additional 60–90 days
    First patient enrolled after all approvals Subject to site activation and import clearance

    The CEP/CONEP and ANVISA tracks run in parallel but must both resolve before the study starts. Submit to CEP at the same time you’re finalizing the ANVISA DICD, or as close to simultaneously as your dossier state allows. Waiting for one before starting the other wastes months.

    For FIH/EFS programs: sponsors running structured 12-month-to-first-patient timelines (similar to the FIH-12 model bioaccess® uses for programs in other Latin American jurisdictions) need to build pendency cycles into the timeline, not treat them as exceptions. A single pendency cycle can add 6–8 weeks if response is delayed.

    Import authorization for investigational devices is also tied to the anuência. The device cannot legally enter Brazil for clinical use until the authorization is granted. Import planning (logistical route, customs documentation, cold chain if applicable, device labeling for investigational use) should begin in parallel with the submission process, not after approval arrives.

    CEP and CONEP: the ethics pathway in practice

    Brazil’s ethics oversight for human research research runs through a two-tier system. Local Research Ethics Committees (CEPs, Comitês de Ética em Pesquisa) review studies at the institution level. The National Research Ethics Commission (CONEP, Comissão Nacional de Ética em Pesquisa) provides a second layer of review for specific categories of research.

    CONEP review is triggered for certain study types including, but not limited to: studies involving novel devices with no prior human use (FIH studies), multi-center studies, and research involving specific vulnerable populations. If your study qualifies, budget additional time. CONEP review adds to the overall timeline and runs through Plataforma Brasil, the national platform for research protocol management.

    What you submit to CEP/CONEP:

    • The complete protocol (same version as in the ANVISA DICD)
    • TCLE (informed consent form, in Portuguese, per Resolução CNS nº 466/2012 formatting requirements)
    • Investigator qualifications and site documentation
    • Sponsor authorization documents
    • Device information consistent with what’s in the DICD technical file

    What you receive: a Parecer Consubstanciado (formal opinion document) from CEP, and if required, a supplementary opinion from CONEP. These are the artifacts you need to activate the study at site level.

    The single most common ethics pendency for device studies is a consent form that doesn’t accurately reflect the risks described in the protocol or the device’s risk management file. A reviewer comparing the TCLE to the protocol who finds discrepant risk language will issue a pendency. Prevent it with the cross-walk table described in the dossier checklist section above.

    Top DICD rejection traps and how to prevent them

    Missing or thin device technical documentation. ANVISA reviewers need to see a device description that goes beyond marketing language. Include materials, dimensions, intended use, operating principles, applicable standards, and classification rationale. FIH sponsors sometimes submit an abbreviated technical file appropriate for a pre-submission meeting but not for a formal DICD. That’s a structural error.

    Investigator’s Brochure not aligned to the protocol. If the IB summarizes preclinical data from an earlier device iteration and the protocol uses a modified version, the discrepancy will generate a pendency. The IB must describe the exact device version in the protocol.

    Unclear stopping rules and monitoring plan. ANVISA’s review of FIH dossiers focuses closely on how the sponsor will identify and respond to safety signals. A protocol that defines primary endpoints but doesn’t specify data safety monitoring board membership, stopping criteria, or adverse event escalation paths will not pass technical review without pendencies.

    Protocol endpoints not matching the safety rationale. If your primary endpoint is a feasibility measure (e.g., delivery success rate) but your device risk management identifies a serious potential harm, ANVISA reviewers will expect to see safety endpoints that address that harm. They won’t accept a protocol where the formal evidence plan ignores a documented risk.

    Consent form inconsistencies. The TCLE must describe risks in language that matches the risk management file and the protocol. Minor differences in risk terminology between documents cause pendencies at both CEP and ANVISA.

    Fast approval prep checklist:

    • Complete internal QC gate: have someone outside the authoring team read the entire dossier for internal consistency before filing
    • Build and review the Protocol/IB/Risk Management/Consent cross-walk table
    • Run a regulatory/ethics reconciliation meeting: confirm the version submitted to ANVISA matches what goes to CEP on the same day
    • Confirm file naming and format compliance against ANVISA’s Documentos de Instrução for subject code 80104

    When ANVISA issues pendencies: Don’t panic, but don’t delay either. Triage the pendency notice immediately to determine whether it’s a document request (provide a revised document), a clarification request (provide a written response), or a substantive concern (may require protocol amendment). Track every response with a version number and maintain a response log. Send responses through the portal as structured submissions, not informal emails.

    How your Brazil ANVISA data can support later FDA work

    Running a device clinical investigation under RDC 837/2023 doesn’t generate FDA acceptance by default. But a well-structured Brazil study can produce evidence that supports later U.S. submissions when the study is conducted under Good Clinical Practice (GCP) standards, the protocol is designed with U.S. regulatory endpoints in mind, and the clinical study report (CSR) meets the documentation standards FDA expects.

    21 CFR 812.28 addresses IDE applications that incorporate foreign clinical data. The principle: foreign clinical data supporting investigational applications must come from studies conducted in accordance with GCP and must be submitted in a format that allows FDA to assess the data’s reliability. A Brazil DICD conducted under ISO 14155 (the international GCP standard for device investigations) and documented with a full, audit-ready CSR meets this foundational standard.

    bioaccess® explicitly structures its FIH programs to produce FDA-aligned evidence packages from studies conducted in Latin America, anchoring regulatory strategy to U.S. pathways while executing in jurisdictions with faster trial activation timelines. The evidence produced from a Brazil or other Latin American investigation can feed directly into FDA pre-submission strategy, IDE applications, and 510(k) or PMA evidence packages, provided the study design, endpoints, and documentation meet the bar.

    Data package translation checklist for sponsors:

    • Clinical Study Report (CSR) structured to ICH E3 or equivalent device format
    • Device description and version confirmation matching final commercial specifications
    • Risk management update incorporating clinical findings
    • Safety signal summary with adverse event narratives
    • Protocol deviation log with impact assessments
    • Monitoring artifacts and audit trail documentation

    One warning worth repeating: the ANVISA anuência for clinical investigation is not a marketing authorization. It doesn’t accelerate or substitute for ANVISA device registration. It also doesn’t constitute FDA clearance, approval, or any equivalent determination. Sponsors who conflate investigational authorization with commercial authorization create serious downstream problems for their regulatory strategies.

    How COFEPRIS, ANMAT, and Panama MINSA compare

    For sponsors asking about process differences across Latin American jurisdictions, here’s a focused comparison of the key variables:

    COFEPRIS (Mexico): Mexico’s health authority uses a “permiso” (permission) for clinical investigation with medical devices. The submission is structured similarly to Brazil’s in that it requires a technical dossier, protocol, and ethics approval, but the ethics pathway runs through Mexico’s COFEPRIS-recognized IRBs or CEIs (Comités de Ética en Investigación), not a CONEP-equivalent national tier. Timeline expectations differ; sponsors commonly report faster validation cycles in Mexico for well-prepared dossiers.

    ANMAT (Argentina): Argentina’s Administración Nacional de Medicamentos, Alimentos y Tecnología Médica governs device clinical investigation authorizations. The process involves submission of a clinical trial authorization request (similar in structure to Brazil’s DICD concept) with device technical documentation, protocol, and ethics approval from a recognized CEIC (Comité de Ética Independiente de Investigación Clínica). Multi-center studies require coordinated ethics review across sites. ANMAT’s review has its own timeline characteristics separate from ANVISA’s.

    Panama MINSA: Panama is frequently selected for FIH/EFS programs because its authorization timelines are among the shortest in the region. Panama MINSA’s regulatory pathway for clinical research falls under “Regulación de Investigación para la Salud,” with clinical trial protocols registered through the RESEGIS platform. Bioethics review is coordinated through the national committee ecosystem under CNBI/SENACYT. The speed advantage is real for sponsors who prepare complete submissions; incomplete submissions face the same pendency dynamics as any other jurisdiction.

    Across all four jurisdictions, the pattern is consistent: complete, internally consistent submissions get faster approvals. The regulatory framework varies; the preparation discipline required does not.

    Official resources for sponsors

    Use these sources directly. Don’t rely on summaries.

    • RDC 837/2023: Available on AnvisaLegis (legislacao.anvisa.gov.br). Search “RDC 837” to access the full text.
    • Guia de Investigação Clínica de Dispositivos Médicos (Guia 30): Published on gov.br/anvisa. Search “Guia 30 dispositivos médicos” or navigate to the clinical research section under “Produtos para a Saúde.”
    • Perguntas e Respostas – Pesquisa Clínica com Dispositivos Médicos: ANVISA’s official Q&A page, updated to align with RDC 837/2023. Available at gov.br/anvisa under the clinical research / medical devices section.
    • Documentos de Instrução for DICD (subject 80104): Accessible through ANVISA’s electronic petitioning system (peticionamento.anvisa.gov.br). Search under “Produtos para a saúde” for the DICD anuência petition type.
    • CEP/CONEP system: Plataforma Brasil (plataformabrasil.saude.gov.br) is the national system for submitting research protocols to CEP and CONEP. Registration and submission guidance is available at conep.saude.gov.br.
    • Resolução CNS nº 466/2012: Full text available at conselho.saude.gov.br. This is the foundational Brazilian ethics regulation for research with human subjects.
    • Panama MINSA research regulation: gov.pa/minsa under “Regulación de Investigación para la Salud.” RESEGIS platform for protocol registration is linked from MINSA’s research section.

    If you’re preparing a first-in-human or early feasibility study for Brazil or another Latin American jurisdiction and need a submission-ready dossier structure that’s already mapped to both local regulatory requirements and U.S. FDA planning, contact bioaccess® to discuss how to sequence ANVISA authorization, CEP/CONEP ethics review, and import logistics for your specific device program.

  • SAE in Medical Device Trials: Reporting Obligations Explained

    SAE in Medical Device Trials: Reporting Obligations Explained

    A serious adverse event (SAE) in a medical device trial is not a paperwork formality. It is one of the most consequential safety signals your study will generate, and the speed, completeness, and accuracy of your response directly shapes your regulatory standing, your trial timeline, and the integrity of your eventual FDA submission.

    This article covers the regulatory definition of an SAE, how it differs from an ordinary adverse event and a UADE, the reporting timelines that apply under FDA 21 CFR 812 and ICH-GCP, and the specific obligations that fall on sponsors when an SAE occurs during a medical device study — including trials conducted in Latin America.


    The Regulatory Definition of a Serious Adverse Event

    The FDA defines a serious adverse event as any untoward medical occurrence in a clinical trial participant that results in one or more of the following outcomes:

    • Death
    • Life-threatening condition (the patient was at immediate risk of death at the time of the event, not that the event might theoretically cause death later)
    • Inpatient hospitalization or prolongation of existing hospitalization
    • Persistent or significant disability or incapacity
    • Congenital anomaly or birth defect
    • Important medical event that, based on appropriate medical judgment, may jeopardize the patient and may require medical or surgical intervention to prevent one of the outcomes listed above

    That sixth category is intentionally broad. It exists to capture events that do not technically satisfy the first five criteria but are clinically significant enough to warrant reporting. Regulatory reviewers and Ethics Committees (ECs) expect sponsors to apply judgment here — not just run through a checklist.

    The ICH-GCP E6(R2) guideline uses the same framework. That consistency matters for sponsors running first-in-human (FIH) studies outside the United States: whether your trial operates under an IDE in the US or under a protocol governed by ISO 14155 in Panama, Colombia, or Chile, the seriousness criteria are the same.


    SAE vs. Adverse Event: Understanding the Distinction

    An adverse event (AE) is any unintended medical occurrence in a clinical trial participant, regardless of whether it is related to the investigational device. It does not have to be serious to be documented. Every AE goes into the case report form.

    An SAE is a subset of adverse events that meets one or more of the seriousness criteria above. Every SAE is an adverse event, but not every adverse event is an SAE. That distinction triggers different documentation requirements, different reporting timelines, and different regulatory notifications.

    A third category applies specifically to device trials: the unanticipated adverse device effect (UADE). Under FDA 21 CFR 812, a UADE is any serious adverse effect on health or safety, or any life-threatening problem or death caused by or associated with a device, where that effect, problem, or death was not previously identified in nature, severity, or degree of incidence in the investigational plan or application. UADEs carry stricter reporting obligations than standard SAEs and require immediate action from both the investigator and the sponsor.

    A practical example

    A patient in a cardiovascular device trial develops a minor rash at the implant site. That is an adverse event. It gets documented in the case report form, but it does not trigger an expedited SAE report.

    Three days later, the same patient is hospitalized with a suspected device-related infection requiring surgical intervention. That hospitalization, combined with the need for surgical management, meets the SAE threshold. Reporting obligations activate immediately. If the infection was not identified as a potential risk in the investigational plan, the event may also qualify as a UADE — which triggers an even shorter reporting clock.


    Who Is Responsible for SAE Reporting?

    Responsibility is shared, but it is not equal.

    The principal investigator (PI) at the clinical site is responsible for identifying the event, completing the initial SAE report form, assessing causality, and notifying the sponsor within the timeframe specified in the protocol — typically within 24 hours of becoming aware of the event.

    The sponsor then evaluates the event, determines whether it meets expedited reporting thresholds, and submits the appropriate report to the FDA and, where applicable, to the Ethics Committee and local health authority. In a multi-site trial, the sponsor is also responsible for notifying all other active investigators of any SAE that could affect the safety of their patients.

    In a first-in-human study, the sponsor is often a lean startup team. That makes the CRO's role in SAE management especially important. A CRO that owns the pharmacovigilance workstream should have established standard operating procedures (SOPs) for SAE intake, causality assessment, narrative writing, and regulatory submission before the first patient is enrolled — not after the first event occurs.


    SAE Reporting Timelines for Medical Device Trials

    Timelines differ depending on the regulatory framework governing your study. Getting these wrong is one of the most common compliance failures in early-stage device trials.

    FDA 21 CFR 812: IDE Studies

    Under FDA 21 CFR 812, the sponsor must report a UADE to the FDA and all reviewing IRBs or ECs within 10 working days of first receiving notice of the effect. For device malfunctions that could cause or contribute to a serious injury if they were to recur, the same 10-working-day window applies.

    SAEs that are not UADEs are generally reported in the annual progress report unless the IDE protocol specifies expedited reporting for certain event types. Many sponsors build protocol language requiring expedited SAE reporting for all serious events regardless of UADE status — a defensible and recommended approach for first-in-human studies.

    FDA 21 CFR 312: IND Studies (Biopharma Context)

    For drug and biopharma trials under an IND, the FDA requires expedited reporting of unexpected serious adverse reactions within 7 calendar days if fatal or life-threatening, and within 15 calendar days for other unexpected serious adverse reactions. This distinction matters for combination product sponsors, who must determine which regulatory framework governs their primary mode of action.

    ICH-GCP E6(R2) Baseline

    ICH-GCP E6(R2) requires the investigator to report all SAEs to the sponsor immediately — defined in most protocols as within 24 hours of awareness. The sponsor then has its own clock for regulatory authority notification. This baseline applies across all ICH-member jurisdictions and is the standard incorporated into ISO 14155, the international standard for medical device clinical investigations.


    What Sponsors Must Do When an SAE Occurs

    A structured SAE response process is not optional. The following steps reflect the obligations that apply under FDA and ICH-GCP frameworks.

    Step 1: Receive and Timestamp the Initial Report

    The moment the sponsor receives an SAE report from the investigator, the regulatory clock starts. Document the date and time of receipt. This timestamp is the reference point for every subsequent reporting deadline.

    Step 2: Assess Causality and Expectedness

    Causality assessment determines whether the event is related to the investigational device or procedure. Expectedness assessment determines whether the event was previously identified in the investigational plan. Both assessments drive the reporting pathway.

    Causality is typically assessed on a scale: unrelated, unlikely, possible, probable, or definite. For device trials, the PI's causality assessment is primary, but the sponsor has the right and obligation to form an independent medical judgment.

    Step 3: Determine Whether Expedited Reporting Is Required

    If the event is a UADE, the 10-working-day clock under 21 CFR 812 is already running. If the event is an SAE that is not a UADE but is unexpected and possibly device-related, review your protocol language to determine whether expedited reporting applies. When in doubt, report expeditiously. Regulatory reviewers treat proactive reporting as a sign of sponsor competence.

    Step 4: Notify the FDA and Ethics Committee

    For IDE studies, UADEs go to the FDA via MedWatch Form 3500A or the equivalent electronic submission pathway. The reviewing IRB or EC must receive notification simultaneously. For multi-site studies, all other investigators must also be notified of any SAE that could affect patient safety across sites.

    For Latin American trials, local health authority notification requirements vary by country. In Colombia, INVIMA has its own pharmacovigilance reporting requirements. In Brazil, ANVISA maintains a national pharmacovigilance system. In Panama, notifications go through MINSA/CNBI. Sponsors running multi-country studies need country-specific SAE notification SOPs — not a single global template.

    Step 5: Prepare the SAE Narrative

    The SAE narrative is the written account of the event: the patient's relevant medical history, the sequence of events, the clinical management, the outcome, and the sponsor's causality and expectedness assessment. It must be clear, factual, and free of speculation. Regulatory reviewers read these narratives carefully. A narrative that contradicts the case report form data is a significant audit finding.

    Step 6: Follow Up Until Resolution

    An SAE report is not closed at initial submission. The sponsor must follow up with the investigator until the event resolves or stabilizes and submit follow-up reports as new information becomes available. Unresolved SAEs at study close must be addressed in the clinical study report.

    Step 7: Update the Investigational Plan or Device Description If Warranted

    If an SAE reveals a risk that was not previously identified, the sponsor must evaluate whether the investigational plan, informed consent documents, or device description require amendment. In some cases, a protocol amendment and re-consent of enrolled patients will be required before the study can continue.


    SAE Documentation in the Trial Master File

    Every SAE must be documented in the Trial Master File (TMF) in a way that allows a regulatory reviewer to reconstruct the full timeline of events from initial report to resolution. Required documents include:

    • The completed SAE report form from the investigator
    • The sponsor's causality and expectedness assessment
    • All regulatory authority notifications and acknowledgments
    • Ethics Committee notifications and responses
    • The SAE narrative and any follow-up narratives
    • Correspondence with the investigator related to the event
    • Any protocol amendments or informed consent updates triggered by the event

    For sponsors planning an IDE or IND submission, the SAE section of the clinical study report is one of the most scrutinized components. Gaps in TMF documentation, missing follow-up reports, or inconsistencies between the narrative and the case report form data are among the most common deficiencies cited in FDA review letters.


    SAE Reporting in Latin American Trials

    Running a first-in-human study in Latin America does not change the FDA's SAE reporting requirements for the sponsor. Data collected under ISO 14155 and structured per FDA 21 CFR 812.28 is accepted for US IDE and IND submissions. The SAE reporting obligations that apply to your IDE remain in force regardless of where the study is conducted.

    What changes is the addition of local reporting obligations. Each country where the study is active has its own pharmacovigilance requirements, and those requirements must be built into the protocol and the CRO's SAE management SOPs before the first patient is enrolled.

    In Colombia, INVIMA requires sponsors to report serious adverse events through its national pharmacovigilance system, with timelines that align broadly with ICH-GCP but include country-specific form requirements. In Brazil, ANVISA's pharmacovigilance framework requires notification of serious adverse reactions to investigational products within defined timeframes. In Panama, MINSA/CNBI governs trial oversight, and SAE notifications must go through the appropriate ministry channel.

    For a sponsor running a multi-country Latin American FIH study, the practical implication is that your CRO needs active, working relationships with each of these regulatory bodies — not just knowledge of the rules. bioaccess® maintains live regulatory authority integrations with MINSA/CNBI in Panama, ISP/MINSAL in Chile, and SRS/CNEIS in El Salvador, which means SAE notification pathways are established before the study opens, not built in response to an event.

    The Cook Group multi-site FIH study in Colombia illustrates what this looks like in practice: a complex, multi-site program with 142-plus INVIMA regulatory submissions managed, requiring disciplined safety reporting infrastructure across an extended enrollment period. Similarly, the Avantec Vascular multi-country LATAM FIH program involved coordinated regulatory management across multiple Latin American jurisdictions, where SAE reporting obligations ran in parallel across country-specific frameworks.

    One important note for sponsors: the 30-to-90-day ethics and regulatory approval window observed in participating Latin American countries reflects the time to study activation, not a compressed safety standard. Once a study is active, the same rigorous SAE reporting obligations apply as in any FDA-regulated trial.


    SAE Reporting Across Device Types and Trial Phases

    SAE reporting obligations apply from first-in-human through pivotal trials, but the risk profile and reporting volume typically differ by phase and device type.

    In a first-in-human or early feasibility study (EFS), the patient population is small, the device is unproven in humans, and every SAE carries heightened significance. Regulators expect more conservative causality assessments and lower thresholds for protocol amendments in early-phase studies. The Establishment Labs LATAM clinical program, which generated clinical evidence supporting FDA PMA approval, demonstrates that a rigorous safety reporting infrastructure in early Latin American studies can translate directly into a submission-ready evidence package.

    For implantable and long-term devices, SAE follow-up obligations extend well beyond the active treatment period. Sponsors must define in the protocol how long post-procedure follow-up continues and what constitutes a reportable event during that window.

    For combination products, sponsors must determine at the outset which regulatory framework governs SAE reporting. A device with a drug or biologic component may trigger both 21 CFR 812 and 21 CFR 312 obligations, and the timelines differ.

    Radiopharmaceutical trials involving compounds such as Lu-177, Ac-225, or Ga-68 add another layer: radiation exposure events and dosimetry deviations may require reporting under both device and drug frameworks and radiation safety regulations, depending on the jurisdiction.


    Common SAE Reporting Mistakes Sponsors Make

    These are the patterns that generate FDA deficiency letters and audit findings most often in early-phase device trials.

    Missing the timestamp on receipt. The regulatory clock starts when the sponsor receives the report — not when the sponsor decides to act on it. Sponsors that cannot demonstrate when they received the initial SAE report have no defensible basis for their reporting timeline.

    Conflating causality with expectedness. These are two separate assessments. An event can be device-related (causality: probable) but expected (listed in the investigational plan). An event can be unexpected but unrelated to the device. Conflating the two leads to incorrect reporting pathway decisions.

    Closing SAE reports before resolution. Regulators expect follow-up reports until the event resolves or the sponsor can document a stable, chronic outcome. SAE reports closed at initial submission with no follow-up documentation are a common audit finding.

    Using a single global SAE template for multi-country studies. Country-specific pharmacovigilance requirements in Colombia, Brazil, Panama, and other Latin American markets differ from each other and from the FDA's requirements. A single template that satisfies one authority may not satisfy another.

    Failing to notify all investigators in multi-site studies. When an SAE occurs at one site and could affect patient safety at other active sites, all investigators must be notified. Treating SAE notification as a bilateral exchange between sponsor and reporting site does not meet the obligation.

    Delayed narrative preparation. The SAE narrative is often treated as a post-hoc documentation task. In practice, it should be drafted as close to the event as possible, while clinical details are current and the investigator is available for follow-up questions. Narratives written weeks after the event are more likely to contain inconsistencies.

    Not updating the informed consent after a new risk is identified. If an SAE reveals a risk not previously disclosed to patients, the sponsor must evaluate whether re-consent is required. Failing to do so is both a regulatory violation and an ethical one.


    How a CRO Manages SAE Obligations in FIH Studies

    For a startup sponsor running its first clinical study, the SAE management workstream is one of the highest-risk operational areas. The obligations are time-sensitive, technically complex, and span multiple regulatory authorities simultaneously in a multi-country study.

    A CRO that owns this workstream end-to-end should have: established SAE intake SOPs with documented receipt timestamps; trained clinical monitors who can assess causality in real time; regulatory affairs staff with direct relationships with each country's health authority; and a narrative writing process that produces clean, consistent documentation ready for the TMF and the eventual clinical study report.

    bioaccess® structures all studies under ISO 14155 and FDA 21 CFR 812.28 so that safety data collected in Latin American trials is accepted for US IDE and IND submissions without rework. The Hasten/Ampcare program in Mexico, which navigated the COFEPRIS-04-050 abbreviated pathway, illustrates how country-specific regulatory relationships and established SOPs reduce the operational burden on a startup sponsor when safety events require rapid regulatory action.

    For sponsors planning a first-in-human study, understanding your SAE reporting obligations before the protocol is finalized is not just good practice. It is the difference between a study that generates a submission-ready evidence package and one that generates a deficiency letter. Learn more about how bioaccess® structures FIH programs for FDA-submissible outcomes at bioaccessla.com.


    FAQs

    What is a serious adverse event (SAE) in a medical device trial?
    A serious adverse event is any untoward medical occurrence in a trial participant that results in death, a life-threatening condition, inpatient hospitalization or prolongation of hospitalization, persistent or significant disability, a congenital anomaly, or an important medical event requiring intervention to prevent one of those outcomes. The definition applies under FDA 21 CFR 812 and ICH-GCP E6(R2).

    What is the difference between an SAE and a UADE?
    An SAE is defined by the seriousness of the outcome to the patient. A UADE (unanticipated adverse device effect) is defined by whether the effect was previously identified in the investigational plan. A UADE is always serious, but an SAE is not automatically a UADE. UADEs carry a 10-working-day reporting deadline to the FDA under 21 CFR 812, which is stricter than the standard SAE reporting timeline for IDE studies.

    How quickly must a sponsor report an SAE to the FDA in a device trial?
    For UADEs under an IDE, the sponsor must notify the FDA and all reviewing IRBs or Ethics Committees within 10 working days of first receiving notice of the effect. For SAEs that are not UADEs, the protocol typically governs the timeline, though many sponsors build expedited reporting requirements into their protocols for all serious events.

    Do SAE reporting obligations change when a trial is conducted in Latin America?
    The FDA's SAE reporting requirements for the sponsor remain the same regardless of where the study is conducted. What changes is the addition of local pharmacovigilance reporting obligations in each country where the study is active. Colombia (INVIMA), Brazil (ANVISA), Panama (MINSA/CNBI), and other Latin American jurisdictions each have their own notification requirements and timelines that must be addressed in the protocol and CRO SOPs.

    Is Latin American SAE data accepted by the FDA for IDE and IND submissions?
    Yes, provided the data is collected under ISO 14155 and structured per FDA 21 CFR 812.28. Data collected under these standards in Latin American trials is accepted for US IDE and IND submissions without rework.

    Who is responsible for SAE reporting in a CRO-managed trial?
    The principal investigator at the site is responsible for identifying the event and notifying the sponsor, typically within 24 hours. The sponsor is responsible for causality and expectedness assessment, regulatory authority notification, Ethics Committee notification, and follow-up reporting until resolution. In a CRO-managed study, the CRO typically owns the SAE management workstream on the sponsor's behalf, but the sponsor retains ultimate regulatory responsibility.

    What happens if an SAE reveals a risk not previously identified in the investigational plan?
    The sponsor must evaluate whether the investigational plan, informed consent documents, or device description require amendment. If a new risk is identified, a protocol amendment and re-consent of enrolled patients may be required before the study can continue. The event may also qualify as a UADE, triggering the 10-working-day FDA notification requirement.


    Conclusion

    SAE reporting in a medical device trial is a time-sensitive, multi-authority obligation that begins the moment the sponsor receives the initial report and does not close until the event resolves. For startup sponsors running first-in-human studies in Latin America, that obligation runs in parallel across the FDA and each country's local pharmacovigilance framework.

    Getting this right requires established SOPs, active regulatory relationships, and a CRO that treats SAE management as a core workstream — not an afterthought. Structure your safety reporting infrastructure before the first patient is enrolled. The evidence package you submit to the FDA will reflect every decision you made along the way.

  • FDA Breakthrough Device: Does Your MedTech Qualify?

    FDA Breakthrough Device: Does Your MedTech Qualify?

    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.

  • FDA IDE Approval: Steps After You Submit Your Application

    FDA IDE Approval: Steps After You Submit Your Application

    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 FDA’s decision (FDA must respond within 30 days of receipt under 21 CFR 812.30, and deficiency rounds can extend it) 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

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

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

    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.

  • Investigator-Initiated Studies: What Sponsors Need to Know

    Investigator-Initiated Studies: What Sponsors Need to Know

    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.


    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.