Category: Uncategorized

  • Clinical trial contract: what every key clause covers

    Clinical trial contract: what every key clause covers

    A clinical trial contract (CTA) is the legally binding agreement between a sponsor, a CRO, and an investigative site that governs how a study is run. Its key clauses cover confidentiality, intellectual property, indemnification, subject-injury coverage, and publication rights, each allocating risk and responsibility before a single patient is enrolled.

    Negotiating a CTA is one of the most time-intensive steps in study startup. Missing or poorly drafted clauses create regulatory and financial exposure that surfaces at the worst possible moment, often mid-enrollment. This article covers the five clause areas most likely to cause delays or disputes so you can spot gaps in a draft before they become problems.

    How long does clinical trial contract negotiation actually take?

    Longer than most sponsors budget for. According to The Contract Network's 2025 industry report, average CTA negotiations now exceed 90 days. A study of 78 sites found the median time to reach a fully signed CTA in EU countries reaches 183 days.

    The main drivers of delay are misaligned indemnification language, unresolved IP ownership, and budget disputes that require protocol-level changes. Each of those issues traces back to a clause that was left vague or skipped in the first draft.

    Before you open negotiations, use a clinical trial cost calculator to model per-patient costs and timeline milestones. Having those figures in hand before you sit down with a site keeps budget discussions grounded and shortens the back-and-forth on payment terms.

    Note: the 183-day figure above reflects EU site contracting specifically. US and Latin American timelines vary and depend on site experience, regulatory pathway, and sponsor preparedness.

    Step 1: Define the preamble and identify all contracting parties

    The preamble establishes the trial agreement meaning: who is bound, under what authority, and for what study. It names the sponsor, the CRO (if one is acting as the sponsor's agent), and the investigative site, and it recites the study protocol number and title.

    A common drafting error is omitting a sub-CRO or a site management organization that will perform material obligations. If that entity is not named in the preamble and listed in the definitions section, you cannot enforce performance obligations against it directly. Every entity that will handle study data, manage patients, or submit regulatory documents should appear as a named party or a defined third-party contractor with explicit obligations attached.

    The definitions section, which follows the recitals, should also define "confidential information," "study data," "background IP," and "foreground IP" before those terms appear in substantive clauses. Leaving them undefined forces later interpretation disputes.

    Step 2: Set confidentiality and non-disclosure boundaries

    Confidentiality clauses in a CTA go beyond a standard NDA. They must specify which categories of information are protected, how long the obligation runs, and what happens to data when the agreement ends.

    For cross-border trials, data-transfer clauses require additional language. A study running in Panama, Chile, or Colombia that sends patient data to a US sponsor must address the applicable data-protection rules of each country. That means naming the transfer mechanism, specifying data formats, and stating who acts as data controller versus data processor. Without that language, a site's ethics committee may flag the agreement before approval.

    Survival is the other critical issue. Confidentiality obligations must explicitly survive termination. State the survival period in years (five years is common for study data; indefinite for trade secrets), and list the specific obligations that continue: record retention, data destruction or return procedures, and restrictions on publication of confidential methodology.

    Step 3: Allocate intellectual property rights for study data and inventions

    Sponsors typically claim ownership of all study data and any foreground inventions arising from the trial. Sites and investigators typically retain rights to their background IP, meaning the methods, tools, and knowledge they brought into the study. The CTA must draw that line clearly.

    Background IP should be defined by reference to a schedule attached to the agreement, listing what the site or investigator owns going in. Foreground IP, anything created during the study using sponsor resources or sponsor data, should vest in the sponsor automatically, with a license-back to the site for non-commercial academic use if the site requires it.

    Investigator-initiated trials complicate this split. When the investigator originates the hypothesis and the sponsor only funds execution, ownership of the resulting data and any patentable invention is actively contested. The CTA must specify whether the sponsor receives an exclusive or non-exclusive license, whether that license is royalty-bearing, and how inventorship disputes are resolved. Leaving this to a handshake creates litigation risk at the point of commercialization.

    Step 4: Differentiate indemnification from subject-injury coverage

    These two clauses address different risk pools and should never be merged into a single provision.

    Indemnification covers third-party claims arising from a party's negligence or breach. The sponsor typically indemnifies the site for claims arising from the protocol design; the site indemnifies the sponsor for claims arising from the investigator's conduct. Each indemnity should state its trigger, its cap (or confirm it is uncapped), and its notice and cooperation requirements.

    Subject-injury coverage is separate. It addresses what happens when a trial participant is harmed, regardless of fault. Good clinical practice standards require that subjects receive medical treatment for trial-related injuries without cost to them. The CTA must state who pays for that treatment, whether a clinical-trial insurance policy is in place, and what the policy limits are. The CTA must name the sponsor's and site's monitoring and safety responsibilities explicitly rather than defaulting to "as required by applicable law," so that liability can be assigned if something goes wrong.

    Country-specific frameworks add further requirements. Some national regulators require specific indemnification language or mandatory insurance minimums as a condition of ethics committee approval. According to Pennington's Law's 2026 analysis, the average combined regulatory and ethical review in the UK has decreased to 41 days, partly because standardized indemnification templates have reduced negotiation cycles. The lesson applies broadly: pre-agreed indemnification language speeds approval regardless of jurisdiction. For a deeper look at liability structures in cross-border device trials, see International Clinical Trial Liability for a Medical Device FIH.

    Step 5: Define publication rights and mandatory hold periods

    Publication clauses protect the sponsor's ability to file patents and review data before results go public, while preserving the investigator's academic freedom. Both interests are legitimate. The clause must balance them explicitly.

    A standard structure includes:

    1. Notification period. The investigator notifies the sponsor at least 30 to 60 days before submitting a manuscript or abstract.
    2. Sponsor review window. The sponsor has a defined period, typically 30 to 45 days, to review for confidential information and patentable inventions.
    3. Hold period for patent filing. If the sponsor identifies a patentable invention, the publication is delayed by an additional period, commonly 60 to 90 days, to allow a patent application to be filed.
    4. Removal of confidential information. The sponsor may require deletion of confidential methodology but may not suppress negative results or alter scientific conclusions.
    5. Survival. Publication obligations survive contract termination. State this explicitly, including the duration of the hold period after termination.

    For an accelerated clinical trial agreement, sponsors sometimes negotiate a compressed review window of 15 to 20 days in exchange for pre-approving a publication plan at contract execution. That trade-off works when the protocol is narrow and the IP landscape is well-mapped in advance.

    When does a CRO help you negotiate and close a clinical trial contract faster?

    A CRO with established site relationships can compress contracting timelines significantly. Sites that have already executed a master agreement with a CRO often accept work orders rather than full CTAs for each new study, cutting negotiation cycles from months to weeks. According to ZipDo's 2026 industry data, the average CRO fee for a phase III trial runs approximately 12% of total budget, presented here as an industry reference point rather than a fixed rate, and not applicable to first-in-human or early-feasibility studies where scope differs substantially.

    bioaccess® is a Miami-headquartered CRO serving MedTech, biopharma, and radiopharma sponsors. Its FIH-12™ program covers the full nine-workstream engagement from FDA Pre-Sub and IDE/IND pathway alignment through protocol development, site activation, patient enrollment, data management, and delivery of a submission-ready clinical evidence package, all within a 12-month structure.

    Median phase III recruitment reached 11.2 months in 2023, according to ZipDo's data, which underscores why site contracting speed matters: delays in executing CTAs directly compress the enrollment window. To compare CRO options for your study type and geography, see the CRO comparison guide and the Best CROs for First-in-Human Device Trials in Latin America.

    FAQs

    A clinical trial contract is a legal agreement between institutional parties, the sponsor, CRO, and site, that governs operations, liability, IP, and data. An informed consent form (ICF) is a participant-facing document that discloses study risks, procedures, and rights to the individual subject. The two documents serve different legal functions and are negotiated separately. The CTA governs the parties; the ICF governs the participant relationship.

    What clauses must survive termination of a clinical trial contract?

    At minimum, confidentiality obligations, record retention duties, subject-injury coverage for enrolled participants, IP ownership provisions, and publication hold periods must survive termination. State each surviving clause by name in a dedicated survival section rather than relying on a general "provisions that by their nature survive" catch-all, which courts interpret inconsistently.

    How does an accelerated clinical trial agreement differ from a standard CTA?

    An accelerated CTA uses pre-negotiated master terms, compressed review windows, and pre-approved publication plans to reduce the time from first draft to fully executed agreement. It works best when the sponsor and site have an existing relationship, the protocol is narrow in scope, and IP ownership is straightforward. Without those conditions, compressing timelines often shifts risk rather than eliminating it.

    What is the role of a CRO in site contract negotiation?

    A CRO with established site relationships can negotiate work orders against a pre-existing master agreement, bypassing full CTA redlines for each site. The CRO also ensures that indemnification language, insurance requirements, and data-transfer provisions meet both the sponsor's standards and the site's regulatory obligations. For first-in-human studies in Latin America, a local CRO with in-country legal knowledge is particularly valuable because national data-protection and insurance requirements vary by country.

    What payment and budget terms belong in a clinical trial contract?

    Payment clauses should specify the per-patient visit fee schedule, milestone-based payments tied to protocol events, and a holdback amount released after the final data lock. The agreement should also state the invoicing cycle, the currency, and the process for handling protocol amendments that change the agreed budget. Leaving payment terms to a separate letter of intent rather than the CTA itself creates disputes when scope changes mid-study.

    What termination and wind-down provisions should a CTA include?

    The termination section should cover both for-cause and convenience termination, stating the notice period for each. It must also address wind-down obligations: who completes ongoing patient visits, how site staff are paid for work performed after notice, and how study materials and data are returned or destroyed. A clear wind-down procedure prevents enrolled participants from losing access to care and limits the sponsor's financial exposure when a site exits mid-study.

    Conclusion

    A clinical trial contract allocates risk before a single patient is enrolled. Getting the preamble, confidentiality, IP, indemnification, and publication clauses right in the first draft shortens negotiation cycles and prevents the disputes that stall studies mid-execution.

    Audit your current draft against the five clause areas covered here: preamble and party identification, confidentiality and data transfer, IP ownership, indemnification and subject-injury coverage, and publication rights. If any clause is missing or defers entirely to "applicable law" without naming specific obligations, flag it for redline before the agreement goes to the site. For first-in-human or early-feasibility studies in Latin America, confirm that country-specific insurance requirements and data-transfer rules are addressed before submitting to an ethics committee.

  • Contract Research Organization Companies: How to Compare Them

    Contract Research Organization Companies: How to Compare Them

    The leading contract research organization companies include IQVIA, ICON plc, Thermo Fisher Scientific (PPD), Parexel, Syneos Health, Fortrea, TFS HealthScience, PharmaLegacy Research, and WuXi AppTec. The sections below profile each firm and cover four selection variables, with guidance on when a regional specialist outperforms a global firm.

    The CRO market is substantial. Member companies of the Association of Clinical Research Organizations generated $89.4 billion in revenue in 2025, reflecting how central outsourced clinical operations have become to drug and device development. Sponsors now face a real choice: a global full-service firm with operations across dozens of countries, or a specialty or regional partner with deeper expertise in a specific phase, therapeutic area, or geography. The right answer depends on your program, not on which name appears most often in industry rankings.

    Top Contract Research Organization Companies at a Glance

    The nine CROs below represent the most commonly evaluated options across global, mid-size, and specialty segments. Pricing is not publicly listed for any of them; cost structures vary by scope, phase, and geography.

    CRO Primary Focus Geographic Reach
    IQVIA Clinical research, lab services, analytics 100+ countries
    ICON plc Biotech-focused clinical research, digital measurement 93 countries
    Thermo Fisher Scientific (PPD) End-to-end clinical development, 20 therapeutic areas Global lab and logistics network
    Parexel International Global clinical trials, AI-assisted trial prediction Global
    Syneos Health Integrated clinical-to-commercial 110+ countries
    Fortrea Phase I, IV clinical research execution Global
    TFS HealthScience Customized trials, strategic resourcing 50 countries
    PharmaLegacy Research Non-clinical lab services, drug discovery U.S.-based facilities
    WuXi AppTec Integrated research, development, manufacturing Global

    Global Full-Service CROs: IQVIA, ICON, PPD, Parexel, and Syneos Health

    The largest global CROs offer therapeutic breadth, deep site networks, and integrated technology platforms. They suit large Phase II and IV programs that require simultaneous enrollment across multiple continents.

    IQVIA operates in more than 100 countries and carries a large committed backlog, reflecting the scale of its pipeline. The company rebranded its lab services division as IQVIA Laboratories in 2024. Its analytics and technology layer suits sponsors who need real-world data alongside trial execution.

    ICON plc was identified as the most used CRO for new study starts in 2024, with operations across 93 countries and a particular emphasis on biotech sponsors and digital measurement tools. In 2026, ICON disclosed an audit investigation indicating minor revenue overstatements in prior years, which sponsors should factor into due diligence.

    Thermo Fisher Scientific (PPD) covers 20 therapeutic areas and draws on Thermo Fisher's global lab and logistics infrastructure following its acquisition of PPD in 2021. Sponsors running studies that require complex sample analysis alongside clinical execution benefit from that integration.

    Parexel International applies AI to predict trial success probabilities and is backed by EQT and Goldman Sachs following a private buyout. That private structure gives it operational flexibility, though it also means less public financial disclosure than listed peers.

    Syneos Health runs an integrated clinical-to-commercial model across more than 110 countries. Taken private in 2023, it no longer publishes audited financial results, so sponsors evaluating financial stability will need to request that information directly.

    Specialty and Mid-Size CROs: Fortrea, TFS HealthScience, PharmaLegacy, and WuXi AppTec

    Specialty and mid-size CROs are worth considering when a sponsor needs focused expertise, a more accessible cost structure, or a tighter operational relationship than a global firm typically offers.

    Fortrea was spun off from Labcorp as a standalone CRO and has since sold non-core units to concentrate exclusively on Phase I through IV clinical research execution. That narrowed focus means sponsors work with a team whose entire operation is built around trial delivery, not lab services or manufacturing.

    TFS HealthScience supports more than 150 indications across oncology, neuroscience, and other key areas in 50 countries. Its governance model gives sponsors direct access to executive leadership, which matters on programs where fast decisions reduce timeline risk.

    WuXi AppTec covers research, development, and manufacturing on a single integrated platform. Sponsors who need to move from early-phase clinical work into manufacturing without switching vendors find that breadth useful.

    PharmaLegacy Research focuses on non-clinical laboratory services, drug discovery, and in vitro assays, with support for more than 600 IND applications and 380,000 square feet of facility space. FDA inspections in 2025 cited deficiencies in quality assurance and equipment maintenance, per biolegacyresearch.com, so sponsors should review current inspection records before engaging.

    How Do You Choose the Right CRO for Your Program?

    Selecting a CRO comes down to matching four variables: financial capacity, therapeutic expertise, technology, and geographic access. Working through them in order keeps brand recognition from distorting the decision.

    A structured approach helps. Comparing CROs across these dimensions before issuing an RFP surfaces mismatches early and saves time downstream.

    Step 1: Evaluate financial stability. A CRO that cannot sustain your program through a 24-month trial is a liability. Review revenue trends, backlog figures, and ownership structure. Private firms with no public reporting require direct disclosure requests [S1].

    Step 2: Verify therapeutic and phase expertise. A large CRO with a broad oncology network may have few sites qualified for first-in-human or medical device work, which extends activation timelines on early-phase programs. Ask for case examples specific to your indication and phase, including site counts and prior activation times [S2].

    Step 3: Assess technology integration. AI-assisted site selection, electronic data capture, and decentralized trial tools affect both timeline and data quality. Ask how the CRO's platform integrates with your existing systems [S3]. According to Technavio's 2026 report, the right CRO partnership can cut trial startup times by more than 25%. That advantage is largest when the CRO already holds active ethics committee approvals and pre-qualified sites in your target country.

    Step 4: Review geographic reach. Site network depth in your target countries drives enrollment speed. Ask each CRO candidate for site counts in your target country, the number of those sites with active ethics committee approvals, and median activation timelines for your indication. Phase III trials average 0.84 patients per site per month, according to Nature Reviews Drug Discovery, a benchmark that highlights how site selection directly affects enrollment pace. A CRO with pre-qualified sites and existing ethics committee relationships in your target region compresses that timeline compared to one entering the market for the first time [S4].

    When Is a LATAM-Focused Regional CRO the Better Choice?

    A regional LATAM CRO outperforms a global firm in three specific scenarios: first-in-human and early feasibility studies where speed and per-patient cost matter most, programs targeting FDA IDE or IND submissions that need OUS data collected under ISO 14155, and device market entry across multiple Latin American countries where in-country regulatory expertise is non-negotiable.

    Global CROs carry overhead structures that make them expensive for early-phase programs. A regional specialist with pre-qualified sites, standing Ethics Committee relationships, and in-country regulatory staff can activate studies faster and at lower per-patient cost.

    bioaccess® is a Miami-headquartered contract research organization serving MedTech, biopharma, and radiopharma sponsors through two service lines. The FIH-12™ program is a nine-workstream, 12-month engagement covering FDA Pre-Sub and IDE/IND pathway alignment, protocol development, site activation, patient enrollment, data management, and delivery of a submission-ready clinical evidence package. The LATAM Launch Subscription handles in-country holder and Importer of Record registration for FDA-cleared (510(k) or PMA) or CE-marked devices across ANVISA, INVIMA, COFEPRIS, ANMAT, ISP, DIGEMID, and other regulators across 19 markets.

    Prices and plan limits verified as of October 2026.

    FAQs

    Who is the largest contract research organization in the world?

    IQVIA is widely cited as the largest CRO by revenue, with operations in more than 100 countries and a large committed backlog. ICON plc ranks among the top tier as well, identified as the most used CRO for new study starts in 2024. Scale matters for large Phase III and IV programs, but it is not the primary selection criterion for early-phase or regionally focused work.

    What is the difference between a full-service CRO and a functional service provider?

    A full-service CRO manages the entire trial from protocol design through data submission. A functional service provider (FSP) delivers a defined subset of services, such as data management or site monitoring, under the sponsor's operational oversight. FSP models suit sponsors with internal clinical teams who need specific capacity; full-service models suit sponsors who want a single accountable partner for the whole program.

    How long does it typically take to activate a clinical trial site?

    At cancer centers, median activation timelines decreased to 250 days in 2024, per aaci-cancer.org, though that figure reflects oncology-specific conditions. Timelines vary by country, therapeutic area, and whether the CRO holds pre-existing ethics committee and regulatory relationships.

    What does GCP compliance mean when evaluating a CRO?

    Good Clinical Practice (GCP) compliance means the CRO conducts trials according to ICH E6 guidelines, which govern trial design, conduct, monitoring, recording, and reporting to protect participant safety and data integrity. For medical device trials, ISO 14155 is the applicable standard. Data collected under these standards is accepted for U.S. FDA IDE and IND submissions. Ask any CRO candidate for recent audit records and inspection history.

    How do per-patient costs vary between regions?

    Per-patient costs are substantially lower in Latin America than in the United States or Western Europe. That difference can extend a sponsor's financial runway on early-phase programs where enrollment is limited and every dollar of capital affects the path to a next funding milestone.

    Conclusion

    Selecting among contract research organization companies is a matching exercise, not a ranking exercise. Global full-service firms offer therapeutic breadth and multinational site networks suited to large, late-phase programs. Specialty and regional CROs offer focused expertise, faster activation, and more accessible cost structures for early-phase and geographically specific work.

    Start by defining your program's phase, therapeutic area, target countries, and submission pathway. Evaluate each CRO candidate against those four variables before reviewing price. A CRO with the right regulatory relationships and pre-qualified sites in your target region will almost always outperform a larger firm entering that market for the first time.

  • FDA Pre-Sub Meeting: How to Get the Most From Your Q-Sub Response

    FDA Pre-Sub Meeting: How to Get the Most From Your Q-Sub Response

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

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

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

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

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

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

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

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

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

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

    How Does the FDA Pre-Sub Meeting Timeline Work?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    Pre-Sub Question and Package Checklist

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

    Device description and development status

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

    Regulatory history and pathway

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

    Questions

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

    Supporting documentation

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

    Meeting request and logistics

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

    Package format

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

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

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

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

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

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

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

    Prices and plan limits verified as of October 2026.

    FAQs

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

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

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

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

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

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

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

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

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

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

    Conclusion

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

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

  • IDE vs IND: Which FDA Pathway Does Your Device Need?

    IDE vs IND: Which FDA Pathway Does Your Device Need?

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

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


    What Each Pathway Covers

    IDE: The Medical Device Route

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

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

    IND: The Drug and Biologic Route

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

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


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

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

    This classification determines how much FDA oversight your study carries.

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

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

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


    Review Timelines and the 30-Day Default

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

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

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


    Downstream Marketing Pathways: Why the Starting Point Matters

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

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

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

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


    When Both an IDE and an IND Apply

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

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

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


    When an IDE Is Not Required

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

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

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


    How This Decision Affects Your FIH Strategy in Latin America

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

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

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

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

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

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


    Making the IDE vs IND Decision: A Practical Framework

    Before filing anything, work through these questions in order.

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

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

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

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

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


    FAQs

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

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

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

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

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

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

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


    Conclusion

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

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

  • Medical Device Regulatory Consulting: When to Hire a Specialist

    Medical Device Regulatory Consulting: When to Hire a Specialist

    WordPress Category: Navigating Regulatory Landscapes in Latin America

    Medical device regulatory consulting sits at the intersection of science, law, and clinical strategy — and knowing when to bring in a specialist can determine whether your program reaches first-in-human data on schedule or stalls for a year waiting on approvals. For startup founders and CSOs managing a $1M to $5M FIH budget, that distinction is not academic. It is the difference between hitting an investor milestone and missing it.

    This article maps out the decision points where specialist regulatory guidance pays for itself, what to look for in a consultant versus a full-service CRO, and how the regulatory consulting function fits inside a broader FIH execution strategy.


    What Medical Device Regulatory Consulting Actually Covers

    Regulatory consulting for medical devices is not a single service. It spans at least five distinct functional areas, and most sponsors need different combinations depending on their stage.

    Pre-submission strategy. Before you file anything with the FDA, a Pre-Sub (formerly Pre-IDE) meeting can clarify the agency's expectations on study design, endpoints, and the evidence threshold for an IDE or 510(k). A regulatory consultant helps you structure that meeting, draft the questions, and interpret the FDA's written response in a way that shapes your protocol — not just files it away.

    IDE and IND pathway navigation. For investigational devices, the IDE application is the gateway to human studies in the United States. A consultant maps out whether your device requires a significant-risk or non-significant-risk determination, what the IDE application must contain, and how study design decisions made now will affect your eventual 510(k) or PMA submission.

    Protocol and study design alignment. The protocol is not just a clinical document — it is a regulatory artifact. Every endpoint, inclusion criterion, and follow-up interval either supports or complicates your future submission. Regulatory consultants who understand FDA expectations can pressure-test a protocol before it reaches an Ethics Committee (EC) or Institutional Review Board (IRB).

    International regulatory dossier preparation. If your FIH study will run outside the United States — in Colombia, Panama, Chile, or another Latin American market — you need country-specific regulatory dossiers. INVIMA in Colombia, MINSA/CNBI in Panama, and ISP/MINSAL in Chile each have distinct submission requirements. A consultant with in-country experience knows what each authority expects and how to sequence submissions to avoid delays.

    Post-market and registration strategy. Once a device is FDA-cleared or CE-marked, entering Latin American markets requires separate registrations with ANVISA (Brazil), COFEPRIS (Mexico), ANMAT (Argentina), DIGEMID (Peru), and others. This is a distinct regulatory workstream from clinical trial approval, and it requires a different kind of specialist.


    The Four Moments That Signal You Need a Specialist

    Most MedTech startups underestimate how early regulatory consulting should begin. The four clearest triggers are:

    1. You Are Approaching Design Freeze

    Design freeze is the point at which your device's specifications are locked for verification and validation. Changes after that point carry significant regulatory cost. A regulatory consultant engaged before design freeze can confirm that your intended indication, device classification, and predicate strategy are coherent — before the engineering team locks anything in.

    Waiting until after design freeze to engage regulatory counsel is one of the most common and expensive mistakes in early-stage MedTech development.

    2. You Are Preparing a Pre-Sub or IDE Application

    The FDA Pre-Sub process is structured but not simple. A poorly framed Pre-Sub question can produce a response that is technically accurate but operationally unhelpful. A specialist knows how to frame questions so the agency's answers give you actionable guidance on study design, sample size, and endpoint selection.

    For IDE applications, the consultant's role is to ensure the application is complete, that the risk analysis is defensible, and that the clinical protocol meets 21 CFR 812 requirements. An incomplete IDE triggers a deficiency letter — and that can add months to your timeline.

    3. Your FIH Study Will Run in Latin America

    Running a first-in-human study in Latin America requires regulatory expertise that most US-based consultants do not carry. Each country's health authority has its own submission format, language requirements, and review timelines. Ethics Committee approvals and ministry-of-health approvals to conduct the studies are separate processes that must be sequenced correctly.

    In Panama, El Salvador, Chile, and the Dominican Republic, ethics and regulatory approvals are observed in 30 to 90 days when submissions are prepared correctly. That speed advantage disappears quickly if the dossier is incomplete or formatted incorrectly for the receiving authority.

    This is where the distinction between a pure regulatory consultant and a full-service CRO becomes important. A consultant can prepare the dossier. A CRO with in-country regulatory infrastructure can prepare the dossier, manage the submission, respond to authority queries, and activate the clinical site — all within the same accountability structure.

    4. You Are Preparing for Market Registration After FDA Clearance

    If your device has received 510(k) clearance or PMA approval and you are targeting Latin American markets, you need a specialist in each country's registration process. ANVISA's registration pathway in Brazil differs substantially from COFEPRIS in Mexico or INVIMA in Colombia. Timelines, required documentation, and in-country holder requirements vary by country and device class.

    Attempting these registrations without country-specific expertise typically results in incomplete submissions, requests for additional information, and delays that push market entry back by 12 to 18 months.


    Regulatory Consultant vs. Full-Service CRO: Where the Line Is

    A regulatory consultant advises. A full-service CRO executes. For early-stage sponsors, the practical question is which one your program actually needs at a given point.

    A standalone regulatory consultant is appropriate when your primary need is strategic guidance: Pre-Sub preparation, IDE pathway analysis, classification review, or a gap assessment of your technical file. The output is a document or a recommendation. Execution stays with your internal team.

    A full-service CRO with regulatory capabilities is appropriate when execution is the bottleneck. If you need regulatory dossiers filed in three countries, Ethics Committee submissions managed, sites activated, patients enrolled, and data collected to ISO 14155 and FDA 21 CFR 812.28 standards — all within a 12-month window — a consultant relationship is structurally insufficient. You need a team that owns the process end to end.

    The risk of using a consultant when you need a CRO is diffuse accountability. The consultant delivers a strategy document. Who files the INVIMA submission? Who manages the EC query response? Who ensures the data management system produces an FDA-submissible dataset? When those questions have no clear owner, timelines slip.


    What FDA Data Bridging Requires from Your Regulatory Setup

    A common concern among US-based sponsors considering OUS early clinical studies is whether data collected outside the United States will hold up with the FDA. The answer depends entirely on how the study is structured and documented.

    Data collected under ISO 14155 and structured per FDA 21 CFR 812.28 is accepted for US IDE and IND submissions. That is not a LatAm-specific rule — it is the standard the FDA applies to any international clinical data submitted in support of a US application. The regulatory consultant or CRO you engage must have explicit experience building evidence packages to this standard, not just running compliant trials in their home jurisdiction.

    This is a non-negotiable qualification when evaluating regulatory partners for an OUS FIH study. Ask specifically: has the team prepared an FDA-submissible evidence package from a LatAm study? What was the submission type, and what was the FDA's response?


    How bioaccess® Integrates Regulatory Consulting Into FIH Execution

    bioaccess® operates as a Miami-headquartered CRO with a site network spanning more than 50 pre-qualified sites across 19 Latin American and Caribbean markets. The FIH-12™ program structures regulatory execution as one of nine workstreams inside a 12-month engagement — covering FDA Pre-Sub and IDE/IND pathway alignment, country-specific dossier preparation, Ethics Committee submissions, and ministry-of-health approvals to conduct the studies.

    The regulatory workstream does not operate in isolation. Protocol development, site activation, patient enrollment, data management, and submission-ready evidence package delivery are managed by the same team. That single-team accountability model addresses the diffuse accountability problem that arises when regulatory consulting and clinical execution are split across separate vendors.

    For sponsors who have already achieved FDA clearance or CE marking, the LATAM Launch Subscription provides in-country holder and Importer of Record registration across ANVISA, INVIMA, COFEPRIS, ANMAT, ISP (Chile), DIGEMID (Peru), and other regional authorities — a distinct regulatory workstream managed through the same operational infrastructure.

    The Cook Group program illustrates what integrated regulatory execution looks like at scale. In the multi-site first-in-human artificial venous valve study in Colombia, bioaccess® managed more than 142 INVIMA regulatory submissions across a complex multi-site engagement. That volume of regulatory activity requires more than advisory capacity — it requires in-country infrastructure and dedicated regulatory operations staff.

    ClarVista Medical's program demonstrates how regulatory execution inside a structured FIH engagement can support a commercial outcome. The ClarVista first-in-human program in Latin America produced the clinical evidence that supported the company's eventual acquisition by Alcon. The regulatory pathway was built to produce FDA-bridgeable data from the outset.

    For sponsors at the market-registration stage, the CryoConcepts COFEPRIS registration program in Mexico shows how a structured in-country regulatory engagement handles the Histafreezer STAT device registration and regulatory transition — a process that requires country-specific expertise that general regulatory consultants rarely carry.


    Questions to Ask Before Engaging Any Regulatory Specialist

    Before signing an engagement with a regulatory consultant or CRO, these questions will surface gaps in capability or fit:

    • Have you prepared regulatory dossiers for submission to INVIMA, MINSA/CNBI, ISP/MINSAL, or other LatAm authorities? For what device types?
    • Can you produce an evidence package structured to FDA 21 CFR 812.28 from an OUS study? What submissions have you supported with that package?
    • Who owns the regulatory submission process end to end — the consultant, a subcontractor, or in-country staff?
    • What is your observed timeline for ethics and ministry-of-health approvals in the countries you operate in?
    • How do you handle authority queries during the review period? What is your average response time?
    • Do you have experience with the specific device classification or indication relevant to our program?

    The answers will tell you whether you are engaging an advisor or an operator — and whether that distinction matters for your current stage.


    Regulatory Consulting Across the Device Development Lifecycle

    Regulatory consulting needs shift as a device program matures. A rough map:

    Pre-clinical to IDE-ready: Classification review, Pre-Sub strategy, IDE application preparation, protocol pressure-testing against FDA expectations.

    IDE-approved to FIH: Country selection for OUS studies, regulatory dossier preparation, Ethics Committee submissions, ministry-of-health approvals, site qualification.

    FIH data to US submission: Evidence package structuring to 21 CFR 812.28 and ISO 14155, FDA Pre-Sub follow-up, IDE supplement or 510(k)/PMA preparation.

    Post-clearance to LatAm market entry: ANVISA, INVIMA, COFEPRIS, ANMAT, ISP, DIGEMID registrations, in-country holder designation, Importer of Record setup.

    Each phase requires a different depth of regulatory expertise. A consultant who is strong on Pre-Sub strategy may have no infrastructure for INVIMA submissions. A CRO strong in FIH execution may not carry the post-market registration capability you need 18 months later.

    The Envveno Medical program illustrates this lifecycle in practice. The LATAM FIH execution built the clinical foundation that supported the first-ever FDA IDE for a non-surgical replacement venous valve. Regulatory strategy and clinical execution were not separate workstreams — they were built together from the start.


    Frequently Asked Questions

    What does a medical device regulatory consultant do?
    A medical device regulatory consultant advises sponsors on FDA classification, Pre-Sub strategy, IDE and 510(k) pathway selection, and international regulatory dossier requirements. The scope is advisory; execution typically remains with the sponsor's internal team or a CRO.

    When should a MedTech startup hire a regulatory consultant?
    The clearest triggers are approaching design freeze, preparing a Pre-Sub or IDE application, planning an OUS first-in-human study, or preparing for market registration in Latin American countries after FDA clearance. Engaging before design freeze is almost always more cost-effective than engaging after.

    What is the difference between a regulatory consultant and a CRO?
    A regulatory consultant provides strategic guidance and prepares documents. A CRO executes the clinical and regulatory program — filing submissions, managing Ethics Committee and ministry-of-health approvals, activating sites, enrolling patients, and delivering a submission-ready evidence package. When execution is the bottleneck, a CRO with integrated regulatory capability is the appropriate choice.

    Will data from a Latin American FIH study be accepted by the FDA?
    Data collected under ISO 14155 and structured per FDA 21 CFR 812.28 is accepted for US IDE and IND submissions. The study must be designed and documented to those standards from the outset — this is not automatic. It requires a regulatory partner with explicit experience building FDA-submissible evidence packages from OUS studies.

    How long do regulatory approvals take in Latin American countries?
    In Panama, El Salvador, Chile, and the Dominican Republic, ethics and regulatory approvals are observed in 30 to 90 days when submissions are prepared correctly. These are observed ranges, not guarantees, and they depend on complete, correctly formatted dossiers submitted to the right authorities in the right sequence.

    What regulatory bodies govern medical device trials in Latin America?
    Key authorities include INVIMA (Colombia), MINSA/CNBI (Panama), ISP/MINSAL (Chile), SRS/CNEIS (El Salvador), ANVISA (Brazil), COFEPRIS (Mexico), ANMAT (Argentina), and DIGEMID (Peru). Each has distinct submission requirements, review timelines, and in-country holder rules.

    Can a single partner handle both FIH regulatory execution and post-market registration in Latin America?
    Yes, if the partner has both clinical trial infrastructure and post-market registration capability across the relevant countries. bioaccess® covers both through the FIH-12™ program for clinical execution and the LATAM Launch Subscription for in-country holder and Importer of Record registration across ANVISA, INVIMA, COFEPRIS, ANMAT, ISP, DIGEMID, and other regional authorities.


    The Right Specialist at the Right Stage

    Medical device regulatory consulting is not a single engagement type. It is a set of capabilities that your program needs at different intensities across the development lifecycle. The question is not whether to hire a specialist — it is which kind, at which stage, and with what accountability structure.

    For programs at the FIH stage targeting Latin American execution, the regulatory workstream cannot be separated from clinical operations without creating accountability gaps that cost time and capital. The sponsor's financial runway rarely accommodates those gaps.

    To understand how bioaccess® structures regulatory execution inside a 12-month FIH program, visit bioaccessla.com.

  • Serious Adverse Event Definition: How FDA Classifies Harm

    Serious Adverse Event Definition: How FDA Classifies Harm

    If you are preparing a first-in-human study, understanding the serious adverse event definition is not optional. It shapes your protocol, your data management plan, your reporting obligations, and ultimately the quality of the evidence package you submit to FDA. A single misclassified event can delay your IDE or IND review, trigger a clinical hold, or create a credibility problem with the agency that is difficult to recover from.

    This article explains exactly how FDA defines a serious adverse event (SAE), how that definition maps onto ISO 14155 and ICH E6 standards used in Latin American clinical trials, what the reporting obligations look like in practice, and why the classification decision matters far more than most early-stage sponsors anticipate.


    What Is a Serious Adverse Event?

    An adverse event (AE) is any undesirable experience that occurs in a patient during a clinical trial, whether or not it is considered related to the investigational device or drug. An SAE is a specific subset of adverse events that meets at least one of a defined set of severity criteria.

    Under FDA regulations, an adverse event is classified as serious if it results in any of the following:

    • Death
    • A life-threatening condition (meaning the patient was at immediate risk of death at the time of the event — not that the event might have caused death if it had been more severe)
    • Inpatient hospitalization or prolongation of existing hospitalization
    • Persistent or significant disability or incapacity
    • A congenital anomaly or birth defect
    • A 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 (sometimes called "important medical events")

    That last criterion — important medical events — is the one that most commonly generates classification disputes in early-stage trials. It requires clinical judgment, and the standard is not whether an intervention was actually performed, but whether one might have been necessary to prevent a serious outcome.


    SAE vs. Unanticipated Adverse Device Effect

    For medical device trials specifically, FDA introduces a second classification layer alongside the SAE definition: the Unanticipated Adverse Device Effect (UADE).

    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, if that effect, problem, or death was not previously identified in nature, severity, or degree of incidence in the investigational plan or application. It also includes any other unanticipated serious problem associated with a device that relates to the rights, safety, or welfare of subjects.

    The distinction matters operationally. An SAE may or may not be device-related. A UADE, by definition, carries an implied or assessed causal relationship to the device and was not anticipated in the protocol. UADEs carry the most urgent reporting timeline under 21 CFR Part 812 — the sponsor must report to FDA and all reviewing Institutional Review Boards (IRBs) or Ethics Committees (ECs) within 10 working days of first receiving notice.


    FDA Reporting Requirements for SAEs

    For device trials operating under an Investigational Device Exemption (IDE), the reporting framework is governed by 21 CFR Part 812. The principal obligations break down as follows.

    Unanticipated Adverse Device Effects: Report to FDA and all reviewing IRBs/ECs within 10 working days.

    Withdrawal of IRB/EC approval: Report to FDA within 5 working days if approval is withdrawn for reasons related to subject safety.

    Annual progress reports: Include a summary of adverse device effects, an updated risk-benefit analysis, and enrollment data.

    Final report: Submitted within 6 months of study completion or termination, including a complete accounting of all adverse events and device effects.

    For drug and biologic trials under an Investigational New Drug (IND) application, the governing framework shifts to 21 CFR Part 312. Unexpected fatal or life-threatening suspected unexpected serious adverse reactions (SUSARs) must be reported within 7 calendar days. All other unexpected serious suspected adverse reactions must be reported within 15 calendar days.

    The practical implication for sponsors running first-in-human studies: your data management plan and site monitoring procedures must be built around these timelines from day one. A site that identifies a potential UADE on a Friday afternoon cannot wait until Monday to begin the reporting chain.


    How ISO 14155 Aligns with the FDA SAE Framework

    ISO 14155 is the international standard governing Good Clinical Practice for clinical investigations of medical devices in human subjects. For sponsors running trials in Latin America with the intention of submitting data to FDA, ISO 14155 is the protocol architecture standard that makes that data bridgeable.

    ISO 14155 uses the same core SAE criteria as FDA — death, life-threatening, hospitalization, disability, congenital anomaly, important medical events — and adds specific requirements for device-related adverse events and device deficiencies. A device deficiency under ISO 14155 is any inadequacy of a medical device with respect to its identity, quality, durability, reliability, safety, or performance, including malfunctions, use errors, and inadequate labeling. Device deficiencies that could have led to a serious adverse event must be reported even if no SAE actually occurred.

    This is a meaningful addition for early-stage device sponsors. Site staff must be trained to recognize and document not just clinical events in patients, but device performance anomalies — and to connect those observations to the SAE reporting chain where appropriate.

    Under FDA 21 CFR 812.28, foreign clinical data collected under ISO 14155 is accepted for IDE submissions, provided the data meets the standard's requirements and the sponsor can demonstrate that the study was conducted consistently with FDA's own GCP expectations. This is the regulatory bridge that makes Latin American first-in-human data directly usable in a U.S. submission.


    SAE Classification in Practice: Where Sponsors Make Mistakes

    Classification errors in early-stage trials tend to cluster around three scenarios.

    The "important medical event" judgment call. A patient presents with a symptom that resolves without intervention. The site coordinator, uncertain whether the event qualifies, codes it as a non-serious AE. If FDA later determines that medical intervention was warranted — or that the event pattern across multiple patients signals a safety concern — the under-reporting becomes a compliance problem. When in doubt, classify as serious and let the causality assessment determine the reporting pathway.

    Conflating relatedness with seriousness. Seriousness and relatedness are independent assessments. An SAE can be unrelated to the device — a patient breaks an arm in a car accident while enrolled. A device-related event can be non-serious. The protocol and case report forms must capture both dimensions separately. Combining them in the data architecture creates analysis problems that are difficult to untangle during FDA review.

    Delayed recognition at the site level. Sites that are not trained specifically for the device type and indication being studied sometimes fail to recognize that a clinical presentation meets the SAE threshold. This is particularly common in first-in-human studies where the investigational device is novel and the expected adverse event profile is not well characterized. Rigorous site qualification and ongoing training are not administrative formalities — they are the mechanism by which classification accuracy is maintained across the study.


    SAE Reporting in Latin American Clinical Trials

    When a trial is conducted in Latin America under a regulatory framework like INVIMA (Colombia), MINSA/CNBI (Panama), ISP/MINSAL (Chile), or SRS/CNEIS (El Salvador), SAE reporting obligations run in two directions simultaneously: to the local regulatory authority and Ethics Committee, and to the sponsor for onward reporting to FDA.

    Each country has its own SAE reporting timelines and formats, which may differ from FDA's requirements. A well-structured clinical operations plan accounts for both sets of obligations and builds reporting workflows that satisfy the more stringent timeline of the two. Failing to report an SAE to the local EC within the required window can jeopardize the study authorization in that country — even if the FDA reporting obligation was met on time.

    This dual-reporting complexity is one reason sponsors benefit from working with a CRO that has established relationships with local regulatory bodies and experienced site staff who understand both the local and FDA-facing obligations. The Cook Advanced Technologies multi-site study in Colombia, which involved 142-plus INVIMA regulatory submissions, illustrates how complex the regulatory management layer becomes in a multi-site, multi-event study — and why operational infrastructure matters as much as protocol design.


    Why SAE Classification Affects Your FDA Submission

    The SAE data collected during a first-in-human or early feasibility study becomes part of the clinical evidence package submitted to FDA as part of an IDE or IND application. FDA reviewers use that data to assess the risk-benefit profile of the investigational device or drug, to determine whether the proposed pivotal study design is appropriate, and to evaluate whether the sponsor has demonstrated adequate safety monitoring.

    An evidence package with well-classified, consistently reported SAE data signals that the sponsor has clinical operations discipline. Gaps, inconsistencies, or apparent under-reporting signal the opposite — and can result in a request for additional information, a study hold, or a more intensive FDA review.

    For sponsors running trials under ISO 14155 in Latin America, the SAE data in the submission must be accompanied by documentation demonstrating that the trial was conducted under GCP-compliant conditions and that the data meets the standards of 21 CFR 812.28. This is not a paperwork exercise. It is the mechanism by which foreign clinical data earns the same evidentiary weight as U.S.-generated data in FDA's review.

    The Envveno Medical study, which resulted in the first-ever FDA IDE for a non-surgical replacement venous valve, demonstrates what a complete, submission-ready evidence package built on Latin American first-in-human data can achieve when the regulatory architecture is correctly structured from the start.


    How bioaccess® Manages SAE Infrastructure in FIH Programs

    bioaccess® builds SAE classification training, dual-reporting workflows, and data management protocols into the FIH-12™ program from workstream one. Site staff across the 50-plus pre-qualified sites in the 19-country network are trained on the specific device type and indication before enrollment begins, reducing the risk of classification errors at the point of event recognition.

    The data management workstream structures SAE data per FDA 21 CFR 812.28 requirements throughout the study — not as a post-hoc exercise before submission. The evidence package delivered at the end of the 12-month program is organized for FDA review from the first event recorded.

    For sponsors who have already completed a first-in-human study and are preparing their IDE submission, the SAE data in that package will be among the first things FDA reviewers examine. Classification inconsistencies or reporting gaps are substantially easier to address before submission than after a deficiency letter arrives.

    The i-Lumen Scientific retinal therapy study and the Hasten/Ampcare COFEPRIS registration both reflect the kind of regulatory precision that comes from building compliance infrastructure into the program design rather than retrofitting it at the end.


    Frequently Asked Questions

    What is the formal serious adverse event definition under FDA regulations?
    An adverse event is classified as serious if it results in death, a life-threatening condition, inpatient hospitalization or prolonged hospitalization, persistent or significant disability or incapacity, a congenital anomaly or birth defect, or an important medical event that requires intervention to prevent one of those outcomes. These criteria apply to both device and drug trials, though the specific reporting frameworks differ between 21 CFR Part 812 (devices) and 21 CFR Part 312 (drugs and biologics).

    What is the difference between an SAE and a UADE?
    A serious adverse event is any adverse event meeting the severity criteria above, regardless of whether it is related to the investigational device. A UADE (Unanticipated Adverse Device Effect) is a serious adverse effect that was not previously identified in nature, severity, or incidence in the investigational plan, and carries an implied causal relationship to the device. UADEs carry a 10-working-day reporting deadline to FDA and all reviewing IRBs or Ethics Committees.

    How does ISO 14155 handle SAE reporting for medical device trials?
    ISO 14155 uses the same core SAE criteria as FDA and adds requirements for device deficiencies — inadequacies in device performance that could have led to an SAE even if no patient harm occurred. For sponsors intending to submit Latin American trial data to FDA, ISO 14155 compliance is the standard that makes that data eligible under 21 CFR 812.28.

    What happens if an SAE is misclassified as non-serious?
    Under-reported or misclassified SAEs create compliance problems that can surface during FDA review of an IDE or IND submission. Reviewers may issue a deficiency letter, request additional data, or place the study on clinical hold. Consistent, accurate classification from the first event is substantially easier to defend than a post-hoc reclassification exercise.

    Do SAE reporting obligations differ in Latin American countries compared to FDA requirements?
    Yes. Each country has its own SAE reporting timelines and formats for local regulatory authorities and Ethics Committees. A sponsor running a trial in Panama, Colombia, or Chile must satisfy both the local reporting requirements and FDA's requirements simultaneously. The more stringent timeline governs. A CRO with established local regulatory relationships and trained site staff is essential to managing both reporting tracks without gaps.

    Can SAE data from a Latin American first-in-human study be used in a U.S. FDA submission?
    Yes, provided the trial was conducted under ISO 14155 protocol architecture and the data is structured per FDA 21 CFR 812.28 foreign clinical data standards. Data collected under these conditions carries the same evidentiary weight as U.S.-generated data in an IDE or IND review.

    What is an "important medical event" in the context of SAE classification?
    An important medical event is one that, based on appropriate medical judgment, may jeopardize the patient and may require medical or surgical intervention to prevent death, a life-threatening condition, hospitalization, disability, or a congenital anomaly. The standard is whether intervention might have been necessary — not whether it was actually performed. This criterion requires clinical judgment and is the most common source of classification disputes in early-stage trials.


    Conclusion

    The serious adverse event definition is one of the most operationally consequential concepts in clinical trial management. Classification accuracy, reporting timeliness, and data structure all flow from how well the sponsor and site team understand and apply the FDA criteria from the first day of enrollment.

    For MedTech and biopharma sponsors preparing a first-in-human study in Latin America, getting the SAE infrastructure right is not a compliance checkbox — it is the foundation of an FDA-bridgeable evidence package. If you are building that program now, the FIH Launch Planner at bioaccessla.com is a practical starting point for mapping your regulatory route, timeline, and evidence package requirements before you commit to a CRO or a country.

  • Clinical Trial Protocol Template: Key Sections for FIH Devices

    Clinical Trial Protocol Template: Key Sections for FIH Devices

    A solid clinical trial protocol template is the foundation of every first-in-human (FIH) study. Get it right, and your Ethics Committee submission, regulatory dossier, and site activation all move in sequence. Get it wrong, and you face amendment cycles that burn weeks you cannot recover.

    This article walks through every section a FIH medical device protocol must contain, explains why each section exists from a regulatory standpoint, and flags the decisions that most often stall approval at MINSA/CNBI (Panama), ISP/MINSAL (Chile), SRS/CNEIS (El Salvador), and other Latin American regulatory authorities.


    Why the Clinical Trial Protocol Template Matters for FIH Studies

    A protocol is not a formality. Under ISO 14155 and FDA 21 CFR 812.28, it defines what data will be collected, how it will be collected, and why that data is sufficient to support a U.S. Investigational Device Exemption (IDE) or Investigational New Drug (IND) submission.

    For a startup running its first FIH study, the protocol also functions as the single source of truth that aligns your FDA Pre-Sub strategy, your Ethics Committee (EC) submission, your principal investigator (PI) briefing, and your data management plan. A protocol written for one purpose and retrofitted for another creates gaps that reviewers find immediately.

    The template structure below is organized in the order most Latin American regulatory authorities expect to see it, with notes on where FDA requirements add or modify those expectations.


    Section 1: Title Page and Protocol Identification

    The title page establishes the document's identity in the regulatory record. It must include:

    • Full study title and protocol number
    • Version number and date (version control is audited)
    • Sponsor name, address, and regulatory contact
    • Investigational device name and description
    • Coordinating investigator name and institution
    • Intended study countries and sites

    Version control is not optional. Ethics committees in Panama and Chile routinely reject submissions that arrive with "v0.1" or undated drafts. Use a format such as "Protocol v1.0, [date]" and maintain a version history table on the following page.

    The investigational device disclaimer belongs here as well. Standard language: "[Device name] is investigational; nothing here implies FDA clearance, approval, CE marking, or commercialization."


    Section 2: Background and Rationale

    This section answers one question for the reviewer: why does this study need to happen, and why now?

    For FIH devices, the background must cover:

    • The clinical problem the device addresses
    • Current standard of care and its limitations
    • Summary of preclinical data (bench testing, animal studies, computational modeling)
    • Regulatory history, including any FDA Pre-Sub correspondence or IDE status
    • Justification for the proposed first-in-human dose, exposure, or implant parameters

    Latin American ethics committees read this section carefully. They are not simply deferring to the FDA — they want to see that the sponsor has done the preclinical work and that the risk-benefit calculation is defensible in their jurisdiction. Sparse background sections are the single most common reason for EC requests for additional information.


    Section 3: Study Objectives and Endpoints

    State the primary objective in one sentence. Then define the primary endpoint with enough specificity that a data manager can build the case report form (CRF) from it without a follow-up question.

    For FIH device studies, objectives typically fall into three categories:

    • Safety and feasibility: Assess the safety profile and procedural feasibility of the device in the target patient population
    • Performance: Evaluate device performance against a defined technical or clinical benchmark
    • Dose or exposure finding: Establish the safe operating range (relevant for energy-delivery devices, radiopharmaceuticals, or drug-device combinations)

    Secondary endpoints follow the same specificity rule. Every endpoint you list will require a corresponding data collection instrument, a statistical analysis plan entry, and a follow-up visit that captures it. Endpoints that cannot be collected within the study's visit schedule should be removed before submission.


    Section 4: Study Design

    This section describes the architecture of the trial. For FIH studies, the design is almost always:

    • Single-arm, open-label, prospective
    • First-in-human or early feasibility study (EFS) designation
    • Single-center or small multi-center (2 to 5 sites for FIH)

    Specify the design elements explicitly: number of subjects, enrollment sequence, follow-up duration, and whether the study includes a run-in phase or cohort expansion. If the design includes a stopping rule or a Data Safety Monitoring Board (DSMB) review at an interim point, describe it here.

    The study design section is also where you document the regulatory framework. For studies intended to support U.S. IDE submissions, state explicitly that the study is conducted under ISO 14155 and structured per FDA 21 CFR 812.28. That language matters when FDA reviewers need to confirm the study was designed to their evidentiary standard.


    Section 5: Subject Selection Criteria

    Inclusion and exclusion criteria define the study population. For FIH devices, these criteria are more conservative than they will be in a pivotal trial. The goal is to enroll patients with the clearest possible risk profile so that any adverse events can be attributed to the device rather than confounded by comorbidities.

    Write each criterion as a single, testable statement. Avoid compound criteria that combine two conditions with "and" — reviewers will ask which condition takes precedence if they conflict.

    Common FIH inclusion criteria:

    • Age range (adults 18 and older, or a defined range for the target indication)
    • Confirmed diagnosis relevant to the device indication
    • Ability to provide written informed consent
    • Willingness to comply with the follow-up schedule

    Common FIH exclusion criteria:

    • Pregnancy or breastfeeding
    • Active infection or immune compromise
    • Prior device implantation that could confound assessment
    • Contraindications specific to the device mechanism
    • Participation in another interventional study within a defined window

    The exclusion criteria should be tight enough to protect subjects but not so restrictive that enrollment becomes impossible. Overly narrow criteria are a common cause of enrollment delays at sites in Panama and Colombia.


    Section 6: Study Procedures and Visit Schedule

    This is the operational core of the protocol. It describes what happens to each subject at each visit, in sequence.

    Structure it as a visit schedule table followed by narrative descriptions of each visit. The table format makes it easy for site coordinators to build the study calendar and for ethics committees to confirm that follow-up is adequate for the risk profile.

    For a typical FIH device study, the visit schedule includes:

    • Screening visit: Eligibility confirmation, informed consent, baseline assessments
    • Procedure visit: Device implantation or application, immediate post-procedure monitoring
    • Early follow-up visits: 24 hours, 7 days, 30 days (timing varies by device and indication)
    • Extended follow-up visits: 90 days, 6 months, 12 months
    • Early termination visit: Procedures for subjects who exit the study before completing all visits

    Each visit description should specify who performs the assessment (PI, co-investigator, or study coordinator), what instruments or equipment are required, and what data is recorded in the CRF.


    Section 7: Investigational Device Description and Accountability

    This section describes the device in enough technical detail for the regulatory reviewer to understand what is being studied, without disclosing proprietary manufacturing information.

    Required elements:

    • Device name, model, and intended use
    • Physical description and mechanism of action
    • Sterility and shelf life
    • Storage and handling requirements
    • Device accountability procedures (receipt, dispensing, return, and destruction)
    • Instructions for use (IFU) reference or attachment

    Device accountability is audited at every GCP inspection. The protocol must specify how the site will track each unit from receipt to use or return. A device accountability log template is typically included as a protocol appendix.

    For radiopharmaceutical studies involving compounds such as Lu-177, Ac-225, or Ga-68, this section expands to include radiopharmaceutical handling procedures, decay and disposal protocols, and radiation safety officer (RSO) requirements at each site.


    Section 8: Concomitant Medications and Treatments

    Define which concomitant medications are permitted, which are prohibited, and which require documentation without restriction. For device studies, this section is often shorter than in drug trials — but it is not optional.

    Specify the washout period for prohibited medications and the documentation requirement for permitted ones. Ethics committees in Chile and El Salvador frequently flag protocols that omit this section entirely, treating the omission as evidence of incomplete study planning.


    Section 9: Assessment of Safety

    This is one of the most scrutinized sections in any FIH protocol. It must define:

    • How adverse events (AEs) are identified, graded, and reported
    • How serious adverse events (SAEs) are distinguished from non-serious AEs
    • Reporting timelines to the sponsor, EC, and regulatory authority
    • Device deficiency definitions and reporting requirements under ISO 14155
    • Stopping rules for individual subjects and for the study as a whole

    Under ISO 14155, device deficiencies that could have led to a serious injury must be reported even if no injury occurred. This is a stricter standard than many sponsors expect from their drug-trial experience. Build the reporting workflow into the protocol itself, not just into the site's standard operating procedures.

    Post-procedure safety monitoring is an area where digital tools have reduced the administrative burden on sites. Adverse event tracking platforms that support Individual Case Safety Report (ICSR) compliance and pharmacovigilance workflows — such as AE Connect at aeconnect.io — can help sites manage reporting obligations without creating bottlenecks in the data flow.


    Section 10: Statistical Considerations

    FIH studies are not powered for statistical significance in the traditional sense. Sample size is determined by safety and feasibility objectives, not by a power calculation against a primary efficacy endpoint.

    The statistical section must still include:

    • Rationale for the planned sample size (typically 10 to 30 subjects for FIH)
    • Definition of the analysis populations (intent-to-treat, per-protocol, safety)
    • Descriptive statistics plan for safety and performance endpoints
    • Handling of missing data
    • Interim analysis plan, if applicable

    FDA reviewers reading an IDE submission expect to see this section. A protocol that omits statistical considerations signals that the sponsor has not thought through how the data will be analyzed and reported.


    Section 11: Data Management

    This section describes how data flows from the site to the sponsor and ultimately into the submission-ready evidence package.

    Key elements:

    • Electronic data capture (EDC) system or paper CRF specification
    • Data entry timelines and query resolution procedures
    • Source data verification (SDV) plan
    • Database lock and audit trail procedures

    For studies intended to support U.S. IDE submissions, data must be structured per FDA 21 CFR 812.28. That means the data management plan needs to be designed with the submission package in mind from the start — not retrofitted after data collection is complete.


    Section 12: Ethics and Regulatory Compliance

    This section documents the regulatory and ethical framework governing the study. For multi-country studies in Latin America, it must address each jurisdiction separately.

    Required elements:

    • ICH-GCP compliance statement
    • ISO 14155 compliance statement
    • List of regulatory authorities and ethics committees with jurisdiction over the study
    • Informed consent process and documentation requirements
    • Subject confidentiality and data protection procedures
    • Insurance and indemnification coverage (clinical-trial insurance policy)

    For studies running in Panama, the relevant authority is MINSA/CNBI. In Chile, it is ISP/MINSAL. In El Salvador, it is SRS/CNEIS. Name each authority explicitly. Generic references to "local regulators" are not acceptable in a submission-ready protocol.


    The informed consent section describes the process, not the document itself. The consent form is typically attached as a protocol appendix.

    The section must specify:

    • Who obtains consent (PI or delegated qualified investigator)
    • When consent is obtained relative to any study procedures
    • Process for re-consent if the protocol is amended
    • Procedures for subjects who lack capacity to consent independently

    Ethics committees in Latin America review the consent process as carefully as the consent document. Protocols that describe consent as a single event with no provision for questions or reconsideration are frequently flagged.


    Section 14: Amendments and Deviations

    Define the amendment process before the study starts. This section should specify:

    • What constitutes a substantial amendment requiring regulatory and EC re-approval
    • What constitutes a non-substantial amendment requiring notification only
    • How protocol deviations are documented, assessed, and reported
    • Corrective and preventive action (CAPA) procedures for recurring deviations

    Amendment management is an area where single-team accountability pays dividends. When one team manages all nine workstreams from FDA strategy through data management, an amendment that affects the statistical analysis plan, the CRF, and the site monitoring plan can be coordinated without version conflicts across separate vendors.


    Section 15: Publication and Data Sharing Policy

    State the sponsor's policy on publication of study results, authorship, and data sharing. Most ethics committees require this section, as do some Latin American regulatory authorities.

    For startup sponsors, this section also protects intellectual property. Specify the review period the sponsor retains before any publication is submitted, and define what constitutes confidential information that cannot be disclosed.


    Putting the Template to Work in Latin America

    A protocol structured under ISO 14155 and FDA 21 CFR 812.28 is the right starting point for submissions to MINSA/CNBI, ISP/MINSAL, and SRS/CNEIS. The regulatory frameworks are compatible, and ethics and regulatory approvals in Panama, El Salvador, Chile, and the Dominican Republic have been observed in 30 to 90 days when the protocol package is complete and well-structured on first submission.

    That timeline matters for startup founders managing a 12 to 24 month runway to first human data. A protocol that requires two or three amendment cycles before approval can add months to a schedule that was already tight.

    The Axoft FIH study in Panama is a concrete example of what a well-executed protocol and regulatory submission can produce: a first-in-human study that generated the clinical evidence supporting a $55M Series A. The Cook Group multi-site study in Colombia demonstrates the same discipline applied to a more complex multi-center design, with 142-plus INVIMA regulatory submissions managed across the program. The ClarVista Medical program shows how a rigorous FIH evidence package can support not just regulatory approval but a full acquisition by Alcon.

    Protocol quality is not separate from business outcomes. It is the mechanism by which clinical evidence becomes investor-grade proof.


    Frequently Asked Questions

    What is a clinical trial protocol template for FIH devices?
    A clinical trial protocol template for first-in-human (FIH) devices is a structured document framework that defines every section a FIH protocol must contain — from the title page and background rationale through subject selection, safety assessment, statistical considerations, and data management. It ensures the protocol meets ISO 14155 and FDA 21 CFR 812.28 requirements for U.S. IDE submissions.

    How many sections does a FIH device protocol need?
    A complete FIH device protocol typically contains 14 to 16 core sections, covering study identification, background and rationale, objectives and endpoints, study design, subject selection criteria, visit schedule, device description, safety assessment, statistical considerations, data management, ethics and regulatory compliance, informed consent, amendment procedures, and publication policy. Additional appendices cover the consent form, device accountability log, and CRF templates.

    Does a protocol written for Latin American regulatory authorities satisfy FDA requirements?
    Yes, when structured under ISO 14155 and FDA 21 CFR 812.28. Data collected under these standards in Latin American studies is accepted for U.S. IDE and IND submissions. The key is designing the protocol with the FDA submission package in mind from the start, not adapting it after data collection.

    How long does ethics and regulatory approval take in Latin America for a FIH protocol submission?
    In Panama, El Salvador, Chile, and the Dominican Republic, ethics and regulatory approvals have been observed in 30 to 90 days when the protocol package is complete on first submission. These are observed outcomes, not guaranteed minimums. Incomplete submissions or amendment cycles extend that window.

    What is the most common reason a FIH protocol is rejected or sent back for revision?
    Incomplete background and rationale sections, missing device accountability procedures, and sparse informed consent process descriptions are the most frequent causes of EC requests for additional information in Latin American jurisdictions. Protocols that omit statistical considerations or concomitant medication policies are also flagged regularly.

    Can a single protocol template cover multiple Latin American countries?
    A single protocol can cover multiple countries, but the ethics and regulatory compliance section must address each jurisdiction's specific regulatory authority by name. Generic references to "local regulators" are not accepted. For a multi-country study, the protocol should name MINSA/CNBI for Panama, ISP/MINSAL for Chile, SRS/CNEIS for El Salvador, and the relevant authority for each additional country.

    Where can I get help developing a FIH protocol for a Latin American study?
    bioaccess® manages protocol development as one of nine workstreams in its FIH-12 program, a 12-month engagement that delivers a submission-ready clinical evidence package. The FIH Launch Planner at bioaccessla.com generates a preliminary country route, timeline range, and evidence package estimate based on six questions about your program.


    Conclusion

    A clinical trial protocol template for FIH devices is not a fill-in-the-blank exercise. Each section carries regulatory weight, and the decisions made in the design phase determine how quickly your EC submission clears, how cleanly your data is collected, and how directly your evidence package supports an IDE or IND filing.

    Build the protocol to the standard the submission requires. Name every regulatory authority explicitly. Design the data management plan for the FDA reviewer who will read it last. That discipline, applied consistently across all 15 sections, is what separates a protocol that clears in 30 to 90 days from one that spends that time in amendment cycles.

    For a structured path from protocol development to submission-ready evidence package, visit bioaccessla.com.


    Category: Navigating Regulatory Landscapes in Latin America

  • What Is In Vivo vs Ex Vivo Testing in Medical Device Trials

    What Is In Vivo vs Ex Vivo Testing in Medical Device Trials

    Medical device sponsors mapping their preclinical-to-clinical pathway encounter the in vivo vs ex vivo distinction early and often. The choice between these two testing approaches shapes protocol design, regulatory documentation, and the evidence package you will eventually submit to the FDA. Getting the terminology right matters before you write a single line of your Pre-Submission meeting request.

    This article explains what each method means, how they differ from in vitro work, where each fits in the device development sequence, and what the distinction means for your first-in-human (FIH) program.


    Defining the Terms: In Vivo, Ex Vivo, and In Vitro

    The three Latin prefixes do the heavy lifting here.

    In vivo means "within the living." Testing is performed inside a living organism — an animal model during preclinical work, or a human subject during a clinical trial. The device, drug, or intervention interacts with a complete, functioning biological system in real time.

    Ex vivo means "outside the living." Biological material — tissue, an organ, or cells — is removed from a living organism and kept viable in a controlled environment. The device is then tested against that material outside the body. The tissue is real and biologically active, but the systemic context of a whole living organism is absent.

    In vitro means "within the glass." Testing occurs entirely in an artificial environment: a cell culture, a bench-top fluid model, or a synthetic tissue analog. No living organism is involved.

    These three methods are not interchangeable. Each answers a different class of question, and each carries a different weight in a regulatory submission.


    In Vivo Testing in Medical Device Development

    In vivo testing is the gold standard for understanding how a device behaves inside a complete physiological environment. Blood flow dynamics, immune response, tissue remodeling, and systemic tolerability can only be observed when the full biological system is present and active.

    In preclinical programs, in vivo studies typically use animal models selected for anatomical or physiological similarity to the human target. A cardiovascular device might be evaluated in a porcine model because swine coronary anatomy closely resembles human anatomy. A spinal implant might use an ovine or caprine model for bone density comparability.

    The outputs of a well-designed in vivo animal study feed directly into the IDE application and the Pre-Submission package. FDA reviewers expect in vivo biocompatibility data, fatigue performance under physiological loading, and — for implantable devices — histopathology from explanted tissue. The ISO 10993 series governs the biological evaluation framework; ISO 14155 governs clinical trial conduct once you cross into human subjects.

    In vivo human studies, meaning clinical trials, are the endpoint of the entire development sequence. The first-in-human study is the first in vivo human test of the device. That distinction is worth stating plainly: every prior in vivo test, however rigorous, was a model. The FIH study is the real thing.


    Ex Vivo Testing in Medical Device Development

    Ex vivo testing occupies a useful middle ground. It is more physiologically relevant than in vitro bench work because the tissue or organ retains its biological structure and cellular activity. It is also less complex than a full animal study — no systemic immune response, no circulatory pressure variation, no anesthesia protocol to manage.

    Common ex vivo applications in device development include:

    • Valve and vascular testing: Excised porcine or bovine hearts are perfused with fluid to simulate cardiac conditions. A transcatheter valve or endovascular device can be deployed and evaluated under realistic tissue conditions without a live animal study.
    • Soft tissue and wound closure: Excised skin or muscle tissue allows evaluation of suture pull-out strength, staple integrity, or adhesive performance against real biological material.
    • Orthopedic and spinal implants: Cadaveric bone specimens provide realistic bone density, cortical thickness, and trabecular structure that synthetic bone analogs cannot replicate.
    • Ophthalmic devices: Excised porcine or bovine eyes are used extensively to test intraocular lenses, surgical instruments, and drug delivery systems before animal or human studies.
    • Radiopharmaceutical dosimetry: Ex vivo tissue samples can be used to measure radiolabeled compound uptake and retention at the cellular level before proceeding to in vivo dosimetry studies.

    The regulatory value of ex vivo data depends on how well the model is characterized. FDA and notified bodies will scrutinize the tissue source, the preservation method, the temperature and perfusion conditions, and the duration of the test. An ex vivo study that is poorly documented provides limited regulatory credit even when the results are favorable.


    How In Vivo and Ex Vivo Data Fit Into the Regulatory Submission

    FDA's framework for IDE applications under 21 CFR Part 812 requires a body of preclinical evidence sufficient to support the safety of the proposed human study. That evidence package typically combines in vitro bench data, ex vivo functional testing, and in vivo animal data. The weight given to each depends on the device classification, the intended use, the implant duration, and the contact type.

    For a significant-risk device pursuing an IDE, the preclinical section of the submission must demonstrate that the device performs as intended under conditions that approximate clinical use. In vivo animal data carries the most weight because it reflects systemic response. Ex vivo data supports specific performance claims — particularly for mechanical or functional endpoints that are difficult to isolate in a live animal. In vitro data establishes baseline material and design characterization.

    Data collected under ISO 14155 protocol architecture and structured per FDA 21 CFR 812.28 is accepted for US IDE and IND submissions when the clinical study is conducted outside the United States. That pathway is directly relevant to sponsors who conduct their FIH study in Latin America and intend to use that data to support a US pivotal trial or marketing submission.

    The Cook Group's multi-site first-in-human artificial venous valve study — managed by bioaccess® in Colombia, with more than 142 INVIMA regulatory submissions handled — is one example of how in vivo human data generated outside the US feeds a US regulatory strategy. Program details are available in the Cook Advanced Technologies first-in-human venous valve case study.


    Where Ex Vivo Testing Ends and In Vivo Testing Begins

    The boundary between ex vivo and in vivo is not always obvious in practice. A few clarifying scenarios help.

    A device tested in an excised porcine heart on a bench — even one being actively perfused — is ex vivo. The moment that same device is implanted in a living pig under anesthesia, the study is in vivo. A cell culture assay using primary human cells derived from a biopsy is ex vivo at the tissue level but in vitro at the study-design level. The distinction matters for how you categorize the study in your regulatory submission and how you describe it in your clinical investigation plan.

    For gene therapy and cell therapy products, the ex vivo/in vivo distinction carries additional regulatory weight. Ex vivo gene modification involves removing cells from a patient, modifying them outside the body, and reinfusing them. In vivo gene delivery introduces the vector directly into the patient. Medical device sponsors working on combination products that include a biological component — such as a scaffold seeded with autologous cells — need to address both modes in their preclinical package.

    The Envveno Medical program, which pursued the first-ever FDA IDE for a non-surgical replacement venous valve, required a preclinical evidence package addressing device performance across multiple testing modalities before proceeding to human subjects. The Envveno Medical LATAM FIH case study illustrates how that evidence sequence translates into a submission-ready package.


    Practical Implications for First-in-Human Program Design

    When building the preclinical plan that will support your IDE application and FIH protocol, the in vivo vs ex vivo distinction has direct scheduling and budget implications.

    Ex vivo studies are generally faster and less expensive than in vivo animal studies. They do not require IACUC approval, do not involve animal husbandry costs, and can often be completed at a contract testing laboratory on a shorter timeline. For sponsors managing financial runway carefully, front-loading ex vivo work to de-risk the design before committing to a GLP animal study is a sound strategy.

    In vivo animal studies take longer to plan, execute, and report. GLP compliance, histopathology processing, and veterinary oversight all add time. But they are not optional for most significant-risk implantable devices. FDA expects in vivo data for implant duration, tissue response, and systemic tolerability — endpoints that ex vivo models cannot provide.

    The ClarVista Medical program, which proceeded from first-in-human to an Alcon acquisition, demonstrates how a well-sequenced preclinical and clinical evidence strategy supports both regulatory approval and commercial outcomes. The ClarVista Medical LATAM success story provides a concrete reference for how that sequence plays out.

    Once in vivo animal data supports the safety case, the FIH study is the next in vivo step. The testing environment shifts from an animal model to a human subject, and the regulatory framework shifts from preclinical standards to ISO 14155 and the IDE regulations.


    In Vivo vs Ex Vivo in Radiopharmaceutical Trials

    The distinction carries specific meaning for radiopharmaceutical developers working with Lu-177, Ac-225, or Ga-68 compounds. Ex vivo biodistribution studies — where a radiolabeled compound is administered to an animal and tissues are harvested and counted after sacrifice — are a standard preclinical method for characterizing tissue uptake and clearance. These studies are technically in vivo at the administration stage and ex vivo at the measurement stage. Regulatory submissions for radiopharmaceutical INDs typically distinguish between the two phases explicitly.

    In vivo imaging studies, such as PET or SPECT scans in animal models or human subjects, measure biodistribution without tissue harvest. These are fully in vivo and provide dynamic data that ex vivo counting cannot replicate.

    For sponsors developing targeted radiopharmaceuticals, the preclinical package typically includes both ex vivo biodistribution data and in vivo imaging data before proceeding to a Phase 0 or Phase I human study. The CelonOva BioSciences COBRA PzF coronary stent program, which involved polymer-free drug elution evaluation, required a similarly layered preclinical evidence approach. The CelonOva BioSciences case study reflects how that evidence architecture supports a submission-ready package.


    Choosing the Right Testing Sequence for Your Device

    No single testing sequence fits every device type. The right approach depends on your device classification, the intended patient population, the implant duration, the contact type, and the specific safety questions your IDE reviewer will need answered.

    A general framework for early-stage device sponsors:

    1. In vitro bench testing establishes design characterization, material properties, and dimensional verification.
    2. Ex vivo functional testing evaluates performance under realistic tissue conditions and surfaces design issues before animal studies.
    3. In vivo animal studies under GLP conditions demonstrate biocompatibility, systemic tolerability, and implant-duration response.
    4. First-in-human clinical study, conducted under ISO 14155 and structured per FDA 21 CFR 812.28, generates the human safety and performance data that supports the IDE and subsequent pivotal trial.

    Each stage informs the next. Gaps in the sequence create questions that FDA reviewers will surface in their Pre-Submission response or IDE review letter — and addressing those gaps before submission is far less costly than responding to a deficiency letter after the fact.

    If your program is approaching the FIH stage and you need a submission-ready evidence package within a defined timeline, bioaccess® structures that process through the FIH-12™ program. Learn more at bioaccessla.com.


    Frequently Asked Questions

    What is the difference between in vivo and ex vivo testing in medical devices?
    In vivo testing is performed inside a living organism, capturing the full systemic biological response. Ex vivo testing uses biological material removed from a living organism and kept viable outside the body — more physiologically relevant than synthetic bench models, but without the complexity of a full animal study.

    Is ex vivo testing considered preclinical or clinical?
    Ex vivo testing is preclinical. It does not involve human subjects and does not require an IDE or IND. It generates supporting evidence for the preclinical section of a regulatory submission, not clinical data under ISO 14155 or FDA 21 CFR Part 812.

    Can ex vivo data replace in vivo animal studies in an IDE submission?
    Generally, no. FDA expects in vivo animal data for significant-risk implantable devices to address systemic tolerability, tissue response, and implant-duration endpoints that ex vivo models cannot replicate. Ex vivo data supports specific functional or mechanical performance claims but does not substitute for GLP in vivo studies.

    How does in vivo data from a Latin American FIH study support a US IDE?
    Data collected under ISO 14155 protocol architecture and structured per FDA 21 CFR 812.28 is accepted for US IDE and IND submissions. A first-in-human study conducted in Panama, Colombia, Chile, or another Latin American country under that framework generates human safety and performance data that FDA will accept as part of a US submission package.

    What is the difference between in vivo and in vitro testing?
    In vivo testing occurs inside a living organism. In vitro testing occurs entirely in an artificial environment — a cell culture or bench-top fluid model — with no living organism involved. In vitro data is the least physiologically representative of the three methods but is the fastest and least expensive to generate.

    When should a device sponsor run ex vivo studies versus proceeding directly to animal studies?
    Ex vivo studies are most useful when you need to evaluate device performance against real biological tissue before committing to the cost and timeline of a GLP animal study. They are particularly valuable for vascular, cardiac, orthopedic, and ophthalmic devices where tissue interaction is central to the performance claim. They are not a substitute for in vivo animal studies when systemic response data is required.

    What regulatory standards govern in vivo clinical testing of medical devices?
    ISO 14155 governs the conduct of clinical investigations of medical devices in human subjects. FDA 21 CFR Part 812 governs IDE applications and the conduct of investigational device studies in the United States. For foreign clinical data to be accepted in a US submission, the study must be structured per FDA 21 CFR 812.28.


    Understanding the in vivo vs ex vivo distinction is foundational work. It shapes how you design your preclinical package, how you sequence your development program, and how you frame the evidence in your IDE submission. Getting that foundation right before you engage with FDA reviewers or select a CRO saves time that most early-stage sponsors cannot afford to lose.

  • Clinical Trial Budget Drivers Every Device Startup Should Track

    Clinical Trial Budget Drivers Every Device Startup Should Track

    Written by Julio Martinez-Clark in Uncategorized

    Clinical Trial Budget Drivers Every Device Startup Should Track

    Updated October 5, 2026

    A clinical trial budget for a first-in-human medical device study spans eight interconnected workstreams: regulatory strategy, ethics and regulatory approvals, site activation, per-patient costs, enrollment and screen failures, data management, safety monitoring, and the clinical study report. Each driver interacts with the others, and underestimating any one creates overruns that compress the runway available for the next funding milestone. This guide breaks down each cost driver, explains how the drivers interact, and shows how geography and program structure decisions made early either compound or contain the total. Use it to build a budget before you issue an RFP, not to rationalize one after the fact.

    Most founders anchor their clinical trial budget on a single number and build everything else around it. That framing fails before the first patient is screened. Knowing what each driver costs, and how it interacts with the others, is what lets you catch overruns before they happen.

    Why FIH Clinical Trial Budgets Are Hard to Estimate Early

    The most common anchoring mistake is treating the CRO management fee as the budget. The management fee is one component. Regulatory strategy, ethics approvals, site activation, enrollment, data management, safety monitoring, and submission preparation are separate cost centers that together typically exceed the management fee. A founder who prices only the CRO fee and estimates everything else as a rounding error will run out of money before hitting the enrollment target.

    The second structural problem is workstream interaction. These eight cost drivers do not sit in parallel. They compound. An approval delay does not just push the timeline out by one month. It adds a month of overhead across every active workstream: staff salaries, device inventory carrying costs, site readiness maintenance, and sponsor operations. A screen failure rate that is higher than modeled does not just add a few screening visits. It extends the enrollment window, which extends every downstream cost that scales with time.

    The third problem is benchmark selection. U.S. and EU trial infrastructure is built for large pharma programs: multi-site Phase III studies with enterprise data systems, centralized ethics review boards, and site networks sized for hundreds of patients. When a startup with a lean FIH budget receives a quote built on that infrastructure, the numbers rarely fit, and neither does the timeline. Using U.S. infrastructure as the default benchmark leads to either sticker shock that kills the program or a scope reduction that produces data FDA cannot use.

    Understanding where cost actually accumulates, and how each driver interacts with the others, is the prerequisite for building a budget that survives contact with reality.

    The Eight Cost Drivers in a Medical Device FIH Study

    1. Regulatory Strategy and Pre-Submission Work

    Before a single patient is enrolled, you need a clear FDA pathway and a protocol that will generate data FDA will accept. That means FDA Pre-Sub meetings, IDE preparation where applicable, and protocol architecture aligned to your intended 510(k), De Novo, PMA, or HDE route.

    Regulatory strategy is consistently underbudgeted because it feels like planning rather than execution, but a protocol misalignment forces mid-study amendments that cost both time and money. A protocol rework after site activation can set a program back by months, which in startup terms means another quarter of overhead without data.

    Solid regulatory strategy at the front end is one of the most cost-efficient investments in the entire budget. bioaccess® anchors regulatory strategy to the sponsor's intended U.S. FDA pathway from day one, across all nine workstreams of the FIH-12™ program, so the evidence package is submission-ready without rework at the end.

    2. Ethics and Regulatory Approval Timelines

    Approval timelines directly affect burn rate. Every month a study sits in a regulatory queue is a month of overhead: staff salaries, device inventory carrying costs, site readiness maintenance, and deferred data.

    In the U.S. and EU, ethics and regulatory approvals typically take 6 to 12 months. In Panama, El Salvador, Chile, and the Dominican Republic, the same approvals are observed in 30 to 90 days. That gap is not a logistics preference. It is a material budget variable. A startup maintaining a standing team while waiting on approvals accumulates overhead that reduces the capital available for actual clinical execution.

    3. Site Activation and Investigator Fees

    Site activation covers site qualification, contract negotiation, Ethics Committee submissions at the site level, and investigator training. For a multi-site study, these costs multiply.

    Investigator fees vary by country and specialty. Device trials requiring surgical implantation or specialized procedural skills command higher per-procedure fees than simpler interventional studies. Budgeting accurately here requires knowing your device category, the investigator profile your protocol demands, and the site's patient volume in your target indication.

    Working with a network of pre-qualified sites reduces activation time and lowers the cost of feasibility work. bioaccess® operates across 50-plus pre-qualified sites in 19 Latin American and Caribbean markets, which means that infrastructure does not need to be rebuilt from scratch for each new sponsor. That translates directly into lower activation cost and faster time to first patient.

    4. Per-Patient Costs

    Per-patient cost is the line item that most clearly separates U.S. and EU trial execution from Latin American execution. In the U.S., per-patient costs for a FIH device study routinely reach six figures when you include site fees, investigator fees, protocol-required diagnostics, and patient management. That cost structure is incompatible with a lean FIH budget unless your sample size is very small.

    In Panama, per-patient costs under the FIH-12™ program cover the clinical work at the site level and reflect the cost structure of a pre-qualified site operating under ISO 14155 and FDA 21 CFR Part 812.28. Costs vary across other markets in the 19-country network.

    5. Patient Enrollment and Screen Failure Rates

    Enrollment is where most FIH budgets experience their largest unplanned overruns. The primary causes are overly optimistic enrollment rate assumptions and underestimated screen failure rates.

    Eligibility criteria in medical device FIH studies tend to be narrow. You may need a specific anatomical profile, a defined disease severity range, or a prior treatment history. Screen failure rates of 30 to 50 percent are common in device studies. If your budget assumes a one-to-one screening-to-enrollment ratio, you will run out of money before hitting your sample size.

    Enrollment costs include patient stipends, screening visits, protocol-required diagnostics, and site staff time per patient contact. Site selection decisions made at the protocol design stage, not after site activation, are the most effective lever for managing enrollment cost.

    6. Data Management and Electronic Data Capture

    Electronic data capture (EDC) setup, data entry, query resolution, and database lock are both fixed and variable costs that scale with protocol complexity and visit count. A lean protocol with fewer endpoints and fewer visits costs less to manage than a heavily instrumented study.

    This is worth considering at the protocol design stage. Every additional data collection point adds EDC configuration time, site training time, and query volume. A protocol with 40 data fields per visit costs meaningfully more to manage than one with 20, and that difference compounds across every patient and every visit.

    Data collected under ISO 14155 and structured per FDA 21 CFR Part 812.28 is accepted for U.S. IDE and IND submissions. That standard matters for budget planning because it determines whether data collected in Latin America can go directly into your FDA submission package or requires rework. Re-formatting, re-validating, or re-collecting data that was not captured to the right standard is an unplanned cost that can derail a submission timeline.

    7. Safety Monitoring and Adverse Event Reporting

    Safety monitoring is a fixed operational cost that scales with patient count and protocol risk classification. A Data Safety Monitoring Board (DSMB), if required, adds both direct fees and coordination overhead. Adverse event reporting obligations under GCP and ISO 14155 require trained clinical operations staff at the site level and sponsor level.

    Underestimating safety monitoring costs is common in early-stage budgets because founders focus on clinical execution and treat safety infrastructure as a compliance checkbox. In practice, a serious adverse event that is not managed correctly, reported late, documented incompletely, or escalated through the wrong channel, can trigger a clinical hold or a regulatory inquiry that costs far more than the monitoring infrastructure would have.

    8. Clinical Study Report and Submission Package

    The clinical study report (CSR) and supporting submission package are the deliverables that justify the entire budget. A CSR that does not meet FDA's expectations for format, completeness, or statistical presentation will require revision, and revision cycles at the submission stage are expensive in both fees and time added to your regulatory timeline.

    Budgeting for a submission-ready evidence package from the start, rather than treating the CSR as a post-study add-on, changes how you scope the data management and medical writing workstreams. The FIH-12™ program structures the submission package as a defined deliverable within the 12-month engagement, not a separate project that begins after database lock.

    How Much Does a First-in-Human Medical Device Trial in Panama or El Salvador Cost Compared with the United States?

    Per-patient costs in Panama under the FIH-12™ program cover clinical work at pre-qualified sites operating under ISO 14155 and FDA 21 CFR Part 812.28. U.S. per-patient costs for a comparable FIH device study routinely reach six figures when site fees, investigator fees, and protocol-required diagnostics are included. For a startup with a lean FIH budget, that difference is the deciding factor in whether the program is executable at all.

    That approval gap, 30 to 90 days in Panama and El Salvador versus 6 to 12 months in the U.S. and EU, is the single largest carrying-cost variable in the budget. Every month in that queue adds overhead across the full program: staff, device inventory, site readiness, and sponsor operations.

    The critical qualifier is data bridgeability. Running a study in Latin America only saves money if FDA accepts the data for your U.S. submission. Data collected under ISO 14155 and structured per FDA 21 CFR Part 812.28 meets that standard. The Establishment Labs case study, where LATAM clinical evidence supported FDA PMA approval for Motiva® implants, is a documented example of that pathway working at the PMA level. ClarVista Medical's trajectory, from first-in-human to Alcon acquisition, followed the same logic: FIH execution in Latin America, FDA-bridgeable data, and a clinical evidence package that supported the downstream commercial outcome.

    For a deeper breakdown of how these cost differences play out across budget scenarios by device class, see How Much Does a First-in-Human Trial Cost in Latin America vs the United States? When selecting a CRO for this work, see Contract Research Organization Companies: How to Compare Them for a framework on evaluating vendors. Sponsors working in specific markets may also find these registration guides useful: How to register a medical device in the Dominican Republic with DIGEMAPS and How to register a medical device in Uruguay with MSP (single Local Holder).

    How Program Structure Affects Your Clinical Trial Budget

    The structure of your CRO engagement affects total cost as much as geography does. A fragmented model, where regulatory strategy, site operations, data management, and medical writing are handled by separate vendors, introduces coordination overhead, version control risk, and accountability gaps that inflate both cost and timeline.

    When the team managing your FDA Pre-Sub is not the same team managing site activation and data collection, protocol amendments travel through a multi-vendor change order process. Each handoff adds time and cost. Discrepancies between what the regulatory consultant specified and what the data management vendor configured require reconciliation meetings, revised scope documents, and, in some cases, data re-collection. None of that work appears in the original budget.

    Single-team accountability across all workstreams removes that overhead. Single-team accountability removes coordination overhead: amendments are handled internally, version control is a single-team problem, and discrepancies between regulatory specs and data configuration do not require cross-vendor reconciliation. That structural efficiency has a direct effect on how much of your budget reaches patient care versus administrative coordination.

    The Cook Group multi-site FIH study, which involved 142-plus INVIMA regulatory submissions managed across Colombia, illustrates what operational scale looks like when site relationships and regulatory infrastructure are already in place. That infrastructure does not need to be built from scratch for each new sponsor, and the cost of not having to build it shows up directly in the budget.

    For a full overview of how the nine-workstream engagement model is structured from protocol development through submission, the first-in-human trials guide covers the complete execution framework.

    What Is the FIH-12 Program from bioaccess and Is It Right for Your Device Program?

    The FIH-12™ program is a nine-workstream, 12-month engagement from bioaccess® that covers FDA Pre-Sub and IDE/IND pathway alignment, protocol development, site activation, patient enrollment, data management, and delivery of a submission-ready clinical evidence package. The program is designed for MedTech, biopharma, and radiopharma sponsors who need to move from regulatory strategy through first-in-human execution and arrive at a complete FDA submission package within a single, defined engagement.

    The nine workstreams run in parallel rather than sequentially, which is how the program fits a 12-month window. Regulatory strategy and protocol development begin simultaneously. Site activation starts while Pre-Sub alignment is underway. Data management infrastructure is configured before the first patient is enrolled, not after. That parallel structure compresses the timeline without compressing the work.

    The program is a full-program delivery structure, from first regulatory contact through database lock and CSR, for sponsors preparing for an FDA Pre-Sub meeting who need IDE or IND pathway alignment and a submission-ready evidence package at the end of execution.

    The FIH-12™ program's defining characteristic is single-team accountability across all nine workstreams, which removes the coordination overhead that fragmented vendor models introduce. The submission package is a defined deliverable within the engagement, not a separate project scoped after data collection ends.

    Intake is capped at eight new programs per quarter. That is a capacity constraint, not a marketing position. Sponsors whose IDE approval or Series A close is approaching should factor that constraint into their planning timeline. For timeline and protocol-to-LPLV detail, see the FIH-12™ protocol-to-LPLV timeline.

    Common Budget Mistakes Device Startups Make

    Six mistakes account for most FIH budget overruns. Each one is avoidable if it is identified before the budget is finalized.

    1. Anchoring on the CRO fee alone. The management fee is one line item. Regulatory approvals, site activation, enrollment, data management, safety monitoring, and submission preparation are separate cost centers that together typically exceed the management fee.

    2. Assuming U.S. approval timelines in a Latin American study. Approval speed is country-specific. A 30-to-90-day window applies in Panama, El Salvador, Chile, and the Dominican Republic. If your CRO's site network is not in those countries, that timeline does not apply to your program.

    3. Using a one-to-one screening-to-enrollment ratio. Screen failure rates in device FIH studies are consistently higher than founders model. Budget for the screening visits, not just the enrolled patients.

    4. Treating the CSR as a post-study project. Medical writing and submission preparation take time and cost money. If they are not scoped into the original budget, they become an unplanned cost that delays your filing.

    5. Ignoring carrying costs during the approval queue. Every month between protocol finalization and first patient enrolled costs money across the full program. Staff, device inventory, site readiness, and sponsor overhead do not pause while approvals are pending.

    6. Fragmenting vendors across workstreams. Coordination overhead between a regulatory consultant, a site management organization, a data management vendor, and a medical writer adds cost and risk that a single-team engagement avoids.

    Building a Clinical Trial Budget That Fits Your Capital Cycle

    A FIH budget that fits your capital cycle is not the cheapest budget you can build. It is the one that delivers a submission-ready evidence package within the runway your next funding milestone requires. Those are different optimization targets, and conflating them is how programs arrive at database lock with no capital left for the CSR.

    Building that budget requires working through five decisions in order:

    1. Model the full cost stack before you issue an RFP. Regulatory strategy, approval timeline carrying costs, site activation, per-patient costs at realistic screen failure rates, data management, safety monitoring, and submission preparation all need line items. A budget that accounts for only the CRO management fee and per-patient costs will be wrong before the first site is activated.

    2. Choose geography on cost and data standards together, not cost alone. A per-patient cost advantage disappears if the data collected cannot go directly into your FDA submission package. Confirm that your CRO collects data under ISO 14155 and structures it per FDA 21 CFR Part 812.28 before you model any geographic savings.

    3. Model approval timelines as a carrying-cost variable. Take the number of months between protocol finalization and expected first patient enrolled, multiply by your monthly program overhead, and add that figure to your budget. If that number is large, geography selection becomes a budget decision, not just an operational one.

    4. Structure your CRO engagement for single-team accountability. Scope the submission package as a defined deliverable within the engagement, not a separate project. Confirm that the team managing regulatory strategy is the same team managing data collection.

    5. Time the engagement against your next funding milestone. Map the 12-month FIH-12™ engagement window against your Series A close or IDE approval date. If those dates are close, factor in the eight-program-per-quarter intake cap when you plan your outreach. For a detailed look at how device class and protocol complexity affect the full cost picture, see Medical device clinical trial cost (2026): FIH and EFS pricing benchmarks.

    FAQs

    What is a clinical trial budget for a medical device FIH study?

    A clinical trial budget for a first-in-human medical device study is a comprehensive cost plan covering all eight workstreams from protocol development through FDA submission: regulatory strategy and Pre-Sub work, ethics and regulatory approvals, site activation, per-patient costs, enrollment and screen failures, data management, safety monitoring, and clinical study report preparation. The CRO management fee is one component of that plan, not a proxy for the total.

    Is data collected in Latin America accepted by FDA for IDE and IND submissions?

    Yes, when collected under ISO 14155 and structured per FDA 21 CFR Part 812.28. That standard governs foreign clinical data acceptance for U.S. submissions. The Establishment Labs case study, where LATAM clinical evidence supported FDA PMA approval for Motiva® implants, is a documented example of that pathway working at the PMA level.

    How do ethics and regulatory approval timelines affect a FIH clinical trial budget?

    Directly, through carrying costs. Every month between protocol finalization and first patient enrolled is a month of overhead across the full program: staff, device inventory, site readiness, and sponsor operations. In Panama, El Salvador, Chile, and the Dominican Republic, ethics and regulatory approvals are observed in 30 to 90 days. In the U.S. and EU, the same approvals typically take 6 to 12 months. For a startup maintaining a standing team during that wait, the gap is a material budget variable.

    What screen failure rate should a device startup budget for in a FIH study?

    Eligibility criteria in device FIH studies tend to be narrow, requiring specific anatomical profiles, defined disease severity ranges, or prior treatment histories. A one-to-one screening-to-enrollment assumption will produce an enrollment cost that is significantly lower than what the study actually requires, and the shortfall shows up mid-study when there is no budget left to address it.

    How many programs does bioaccess accept per quarter?

    Intake for the FIH-12™ program is capped at eight new programs per quarter. This is a capacity constraint that reflects the operational demands of single-team accountability across nine workstreams. Sponsors whose IDE approval or Series A close is within the next two quarters should factor that constraint into their outreach timeline.

    Conclusion

    A clinical trial budget fails when it is built around one number. The eight workstreams in a FIH device study interact: an approval delay extends carrying costs across every active workstream, a higher-than-modeled screen failure rate extends enrollment and every downstream cost that scales with time, and a CSR scoped as an afterthought delays the submission it was meant to support. Geography and program structure are the two largest controllable variables, and both decisions need to be made before the budget is finalized, not after the RFP goes out.

    The most useful next step is to map your full cost stack against your next funding milestone. Start with approval timeline carrying costs, because that figure is often the largest unmodeled variable in early-stage FIH budgets. Then confirm that your CRO engagement structure assigns single-team accountability across all workstreams and treats the submission package as a defined deliverable. Those two decisions, geography chosen on cost and data standards together, and a single-team engagement scoped through CSR, determine whether your clinical trial budget survives contact with reality.

  • 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. or Europe, while keeping that evidence anchored to U.S. Food and Drug Administration (FDA) strategy.

    Latin American ethics committees routinely review FIH protocols in 4 to 8 weeks, 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. or EU. 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 in 4 to 8 weeks. For reference, Colombia (INVIMA pathway) typically runs 4 to 6 weeks for ethics; Panama (MINSA/CNBI) commonly runs 3 to 5 weeks with no Ministry of Health review required. 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, PAVmed’s PortIO device FIH study executed through bioaccess® 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 (bioaccessla.com/case-studies/pavmed).

    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.

    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 in 4–8 weeks)
                 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-specific examples from bioaccess®’s published data: Colombia (INVIMA) commonly runs $15,000–$25,000 per patient with 4–6 week ethics; Panama (MINSA/CNBI) runs $18,000–$30,000 per patient with 3–5 week ethics and no Ministry of Health review; El Salvador carries a 30-day startup benchmark at $15,000–$28,000 per patient. A 10-patient FIH device study through bioaccess® in LATAM carries published CRO fee benchmarks of $300,000–$500,000, compared with $750,000–$1,500,000 for a comparable U.S. program.

    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.