• What Counts as a Serious Adverse Event
• The Sponsor's Core Obligations
  • 1. Receiving and Acknowledging Reports from Sites
  • 2. Assessing Causality and Expectedness
  • 3. Reporting to the FDA
  • 4. Reporting to Ethics Committees and Local Authorities
• SAE Reporting Timelines at a Glance
• What a Well-Structured SAE Report Contains
• Common Mistakes Sponsors Make
• SAE Reporting in First-in-Human Trials: Specific Considerations
• Building an SAE Reporting Plan Before Your Trial Starts
• FAQs

Serious adverse events are a reality of clinical research. How your team responds in the hours and days after one occurs can determine whether your trial stays on schedule, whether your regulatory submission holds up, and whether your relationship with the FDA remains intact.

For startup sponsors running first-in-human studies, the stakes are especially high. You may not have a dedicated safety pharmacovigilance team. Your CRO may be managing the reporting workflow on your behalf. Either way, the sponsor remains legally accountable for every SAE report that goes to the FDA, the ethics committee, and the host country authority.

This article covers what an SAE is, what triggers reporting obligations, what the timelines look like, and what a well-run SAE process actually requires.

What Counts as a Serious Adverse Event

An adverse event is any untoward medical occurrence in a trial participant. An SAE is a specific subset, defined by outcome criteria. Under FDA definitions and ICH-GCP standards, an adverse event qualifies as serious if it results in any of the following:

• Death
• A life-threatening condition
• Inpatient hospitalization or prolongation of existing hospitalization
• Persistent or significant disability or incapacity
• A congenital anomaly or birth defect
• A medically important event that may not meet the above criteria but could jeopardize the participant and require medical or surgical intervention to prevent one of the above outcomes

That last category — "medically important events" — is where sponsor judgment gets tested. It requires real clinical and regulatory expertise to assess correctly, and errors in either direction create problems. Under-reporting exposes you to regulatory action; over-reporting can signal poor protocol design or weak site management.

The Sponsor’s Core Obligations

Sponsors bear primary responsibility for SAE reporting, even when a CRO is handling day-to-day trial operations. FDA regulations under 21 CFR Part 812 (for devices) and 21 CFR Part 312 (for drugs and biologics) make this unambiguous.

Sponsor obligations generally fall into four categories.

1. Receiving and Acknowledging Reports from Sites

Investigators are required to report SAEs to the sponsor promptly — typically within 24 hours of becoming aware of the event. Your trial protocol should define the exact reporting pathway: who the investigator contacts, what form or system they use, and what information must be included in the initial report.

A missing or delayed investigator report does not relieve the sponsor of its own reporting obligations. You are expected to have systems in place to capture SAEs regardless of whether sites report on time.

2. Assessing Causality and Expectedness

Once you receive an SAE report, your medical monitor or safety team must assess two things: whether the event is reasonably related to the investigational product or device, and whether it was anticipated based on the current risk profile documented in your Investigator's Brochure or device description.

An unexpected serious adverse device effect (SADE) in a medical device trial, or an unexpected serious adverse reaction (USAR) in a drug trial, triggers expedited reporting requirements. Expected SAEs still require documentation and submission — just on a different timeline.

3. Reporting to the FDA

For investigational device exemption (IDE) trials, sponsors must report unanticipated adverse device effects (UADEs) to the FDA and all reviewing IRBs within 10 working days of first receiving notice of the effect.

For IND-covered drug and biologic trials, unexpected fatal or life-threatening suspected unexpected serious adverse reactions (SUSARs) must be reported within 7 calendar days. All other unexpected SUSARs go to the FDA within 15 calendar days.

These are not soft targets. Missing a reporting window is a protocol deviation that must itself be documented and may trigger an FDA inquiry.

4. Reporting to Ethics Committees and Local Authorities

Beyond FDA reporting, you must notify the IRB or ethics committee that approved the study. Local requirements in the country where the trial is being conducted also apply.

For trials running in Latin American jurisdictions, this means notifying the relevant national authority alongside the ethics committee. In Panama, that involves MINSA/CNBI. In Chile, ISP/MINSAL. In El Salvador, SRS/CNEIS. Each authority has its own SAE reporting format and timeline requirements — all of which need to be built into your safety management plan before the trial starts.

SAE Reporting Timelines at a Glance

These timelines run from the date the sponsor first becomes aware of the event — not from when the investigator first observed it. The clock starts the moment information reaches your organization.

What a Well-Structured SAE Report Contains

An incomplete SAE report is nearly as problematic as a late one. The FDA and ethics committees expect the following elements in an expedited report:

• Patient identifiers (coded, not personally identifiable)
• Event description: onset date, duration, severity, and outcome
• Causality assessment: the sponsor's determination of whether the event is related to the investigational product
• Expectedness assessment: whether the event was anticipated based on current risk documentation
• Action taken: whether the protocol was modified, the participant discontinued, or the device retrieved
• Investigator's narrative: the site-level account of what happened
• Sponsor's narrative: the sponsor-level analysis, including any signal implications for the broader study population

For device trials following ISO 14155 architecture, the report structure also needs to align with risk management documentation. An SAE that reveals a failure mode not previously identified in your risk analysis requires a formal update to that analysis — not just a safety report.

Common Mistakes Sponsors Make

Most SAE reporting failures follow a small number of patterns.

Delayed internal escalation. Sites report to the CRO, but internal routing takes two days before the sponsor's medical monitor sees the event. By then, the reporting window is already compressed.

Causality assessed too narrowly. Sponsors sometimes default to "unrelated" assessments to avoid expedited reporting obligations. Regulatory reviewers are experienced at identifying patterns across a trial population, and a string of "unrelated" SAEs that share a mechanism will draw scrutiny.

Inadequate follow-up reporting. An initial expedited report is not the end of the obligation. Follow-up reports must be submitted as new information becomes available, until the event resolves or the outcome is confirmed. Sponsors who file an initial report and then go quiet on a case create audit flags.

Inconsistent definitions across sites. If your protocol does not define SAE criteria precisely, different investigators will apply different thresholds — and you end up with inconsistent safety data that complicates your eventual submission.

No pre-defined escalation path for ambiguous events. Medical monitors need a documented decision tree for events that sit at the boundary of the SAE definition. Without one, each ambiguous case becomes an ad hoc discussion, which slows reporting and introduces inconsistency.

SAE Reporting in First-in-Human Trials: Specific Considerations

First-in-human studies carry a higher baseline uncertainty than later-phase trials. The safety profile of the device or compound is, by definition, not yet established in humans — which means your SAE reporting infrastructure needs to be especially robust from day one.

A few things matter more at the FIH stage than they do later.

Your Investigator's Brochure or device description must be current. Expectedness assessments depend on what your IB documents as known or anticipated risks. An out-of-date IB means you may misclassify expected events as unexpected, or miss the significance of something that should have been flagged.

Your DSMB or Safety Review Committee needs clear SAE triggers. Define in advance what event types or frequencies will prompt an unscheduled safety review or a protocol hold recommendation. Leaving this to judgment in the moment creates delays and inconsistency.

Your evidence package must capture SAE data in a submission-ready format. If your goal is an IDE, 510(k), or PMA submission, the safety data from your FIH study needs to be organized so that FDA reviewers can evaluate it efficiently. An SAE narrative that reads well in a site file but isn't structured for regulatory review will slow your submission.

For sponsors running trials in Latin American jurisdictions, the SAE data also needs to meet FDA's requirements for foreign clinical data under 21 CFR 812.28. That means the safety reporting process must be designed with FDA acceptance in mind from the start — not retrofitted after the trial closes.

bioaccess® structures all FIH-12™ program safety workflows around this requirement. The nine-workstream engagement includes data management and final evidence package delivery specifically designed to produce a submission-ready safety record for the sponsor's next FDA regulatory step — whether that is an IDE, 510(k), De Novo, or PMA. You can learn more at bioaccess®.

Building an SAE Reporting Plan Before Your Trial Starts

The time to design your SAE reporting process is during protocol development — not after your first event occurs. A functional SAE reporting plan addresses the following:

• Definitions: Exact criteria for what constitutes an SAE in your specific trial, including the "medically important events" category
• Reporting pathways: How investigators report to the sponsor, what system or form they use, and what the acknowledgment process looks like
• Internal routing: Who in the sponsor organization receives the report, who performs the causality assessment, and who signs the expedited report to FDA
• Timeline tracking: A system that logs the date the sponsor first became aware of each event and tracks the reporting deadline automatically
• Local authority requirements: Country-specific reporting formats and timelines for each jurisdiction where the trial is running
• Follow-up procedures: Who is responsible for obtaining outcome information and filing follow-up reports
• Annual safety reporting: How individual SAE data rolls up into the annual progress report or Development Safety Update Report (DSUR)

Getting this infrastructure in place before enrollment starts is not a bureaucratic exercise. It protects your participants, protects your data, and protects your regulatory pathway.

FAQs

What is the difference between an adverse event and a serious adverse event?
An adverse event is any untoward medical occurrence in a trial participant, regardless of severity. A serious adverse event meets at least one of a defined set of outcome criteria: death, life-threatening condition, hospitalization, significant disability, congenital anomaly, or a medically important event requiring intervention to prevent a serious outcome. Not all adverse events require expedited reporting; SAEs do.

Who is responsible for SAE reporting in a sponsored clinical trial?
The sponsor holds primary legal responsibility for SAE reporting to the FDA and ethics committees, even when a CRO manages day-to-day operations. The investigator is responsible for reporting SAEs to the sponsor promptly — typically within 24 hours. The sponsor then assesses the event and files the required regulatory reports within the applicable deadlines.

What is the FDA reporting deadline for an unanticipated adverse device effect in an IDE trial?
Sponsors must report unanticipated adverse device effects (UADEs) to the FDA and all reviewing IRBs within 10 working days of first receiving notice of the effect.

Does SAE reporting work the same way in Latin American trial jurisdictions as it does in the US?
The FDA reporting obligations remain the same regardless of where the trial is conducted. In addition, sponsors must comply with the SAE reporting requirements of each host country's national authority. In Panama, Chile, and El Salvador, separate notifications to MINSA/CNBI, ISP/MINSAL, and SRS/CNEIS respectively are required. A well-designed safety management plan accounts for both sets of obligations simultaneously.

Can foreign clinical trial SAE data be used in a US regulatory submission?
Yes, provided the data is collected and documented in accordance with FDA's requirements for foreign clinical data. For device trials, 21 CFR 812.28 governs the acceptance of foreign data. The safety record must be structured to meet FDA review standards — which requires intentional design from the start of the trial, not after the fact.

What happens if a sponsor misses an SAE reporting deadline?
Missing a reporting deadline is a protocol deviation that must be documented and reported. Depending on the severity of the event and the length of the delay, the FDA may issue a clinical hold, request a corrective action plan, or flag the deviation during a pre-submission review. Repeated reporting failures can jeopardize the entire trial program.

How should sponsors handle SAEs that are ambiguous about whether they meet the "serious" threshold?
Your protocol should include a pre-defined decision process for ambiguous events, including escalation to a medical monitor or safety officer. When in doubt, the default should be to treat the event as serious and report it. Over-reporting a borderline event is a far smaller regulatory risk than under-reporting one that later proves significant.

SAE reporting is not a back-office compliance task. It is a core part of how you demonstrate that your trial is being conducted with scientific rigor and participant safety as the priority. Build the infrastructure before your first patient is enrolled, train your sites on the process, and make sure your CRO's safety workflows are designed to produce data that will hold up in a regulatory submission.

If you are planning a first-in-human study and want to understand how SAE reporting fits into a structured trial program, bioaccess® manages the full safety workflow as part of the FIH-12™ engagement.

• Why Sequencing Matters More Than Speed Alone
• Understand Your FDA Pathway First
  • The Five Core Pathways
• The FDA Framework That Makes LATAM Data Count
• Choosing the Right LATAM Jurisdiction for Your Device
  • Fast-Approval Jurisdictions
  • What Drives Jurisdiction Selection
• How to Sequence the Two Tracks
  • Phase 1: FDA Strategy Alignment (Months 1 to 2)
  • Phase 2: Protocol Development and Jurisdiction Selection (Months 2 to 3)
  • Phase 3: Site Activation and Enrollment (Months 3 to 8)
  • Phase 4: Evidence Package Assembly (Months 8 to 12)
• The Startup-Specific Consideration: Runway and Milestones
• Common Sequencing Mistakes to Avoid
• How bioaccess® Structures This for Sponsors
• FAQs
• Where to Start

WordPress Category: Navigating Regulatory Landscapes in Latin America

Most MedTech founders treat regulatory strategy as a linear problem: get FDA clearance, then figure out the rest. That framing costs time and money. The smarter approach treats your FDA pathway and your first-in-human data strategy as a single sequenced plan — not two separate workstreams running independently.

If you're a startup CEO or CSO sitting on an IDE approval or approaching a Series A close, this article walks through how to think about that sequence, why Latin American regulatory jurisdictions belong in your plan, and how to structure the evidence you generate so it holds up at every step.

Why Sequencing Matters More Than Speed Alone

Speed is the obvious reason founders look at Latin America. Ethics and regulatory approvals in jurisdictions like Panama, El Salvador, Chile, and the Dominican Republic take 30 to 90 days, compared to 6 to 12 months in the US. That gap alone can determine whether you have first human data before your next funding round closes — or after it.

But speed without regulatory alignment creates its own problem. If your LATAM trial isn't structured to FDA's foreign clinical data requirements from day one, the data you generate may not be usable for your IDE, 510(k), De Novo, or PMA submission. You'll have spent the time and the budget, and FDA will ask for more.

The goal isn't just to run a trial fast. It's to generate a submission-ready evidence package that bridges directly to your next FDA step.

Understand Your FDA Pathway First

Before you select a country, a site, or a protocol design, you need to know which FDA pathway your device is targeting. That determination shapes everything downstream.

The Five Core Pathways

IDE (Investigational Device Exemption): Required for significant risk devices entering US clinical investigation. LATAM FIH data can support the IDE application or inform the protocol for the US pivotal study that follows.

510(k): Clearance through substantial equivalence to a predicate device. First-in-human data from a LATAM feasibility study can strengthen a 510(k) by demonstrating clinical performance in a controlled setting.

De Novo: For novel low-to-moderate risk devices with no predicate. The clinical evidence standard is higher than 510(k), and a well-documented LATAM FIH study can serve as the primary clinical evidence basis.

PMA (Premarket Approval): For high-risk Class III devices. LATAM FIH and early feasibility data typically forms the foundation for a subsequent US pivotal study. The quality of your early data directly affects how FDA evaluates your pivotal protocol.

HDE (Humanitarian Device Exemption): For rare disease devices affecting fewer than 8,000 US patients annually. Early clinical data from a LATAM feasibility study can satisfy the probable benefit standard.

Knowing your pathway tells you what evidence FDA will need — which tells you what your LATAM protocol must produce.

The FDA Framework That Makes LATAM Data Count

Under FDA 21 CFR 812.28 (see FDA's official page on Acceptance of Data from Clinical Investigations for Medical Devices), data from foreign clinical investigations of medical devices may be accepted in support of an IDE or marketing submission, provided the study was conducted in accordance with Good Clinical Practice, including review and approval by an independent ethics committee, and the sponsor can verify data quality and integrity.

This isn't a loophole. It's a documented, established framework. What it requires is that your LATAM study be designed and executed to the same quality standard you'd apply to a US study — ISO 14155 protocol architecture, ICH-GCP compliance, independent ethics review, and an audit-ready data room.

If any of those elements are missing or inconsistently applied, the data's usability for FDA submissions becomes uncertain. This is exactly why protocol design and regulatory strategy must be aligned before enrollment begins, not after.

Choosing the Right LATAM Jurisdiction for Your Device

Not every Latin American country offers the same regulatory environment. For a startup, the practical distinction comes down to approval timeline and regulatory body predictability.

Fast-Approval Jurisdictions

Panama (MINSA/CNBI): Consistently among the fastest ethics and regulatory approval timelines in the region. Well-suited for first-in-human feasibility studies across a broad range of device classes.

El Salvador (SRS/CNEIS): Regulatory approvals in the 30-to-90-day range. A strong option for sponsors who need to move quickly and have a straightforward device profile.

Dominican Republic: Comparable approval timelines, with a growing clinical research infrastructure.

Chile (ISP/MINSAL): A slightly more structured process, but still substantially faster than US timelines. Well-regarded for cardiovascular and interventional device studies.

Colombia: An established clinical research ecosystem with experienced investigator networks, particularly for complex device categories.

What Drives Jurisdiction Selection

Three factors should drive your choice: the device class and indication (some jurisdictions have deeper investigator experience in specific specialties), the regulatory body's familiarity with your device category, and your target FDA pathway. A device heading toward De Novo has different evidence requirements than one supporting a PMA, and those differences affect which jurisdiction and site network best fits your protocol.

How to Sequence the Two Tracks

Here's a practical sequencing framework for a startup that is IDE-ready or approaching that milestone.

Phase 1: FDA Strategy Alignment (Months 1 to 2)

Before any country selection or protocol drafting, align your LATAM study design to your FDA pathway. That means defining the primary and secondary endpoints your submission will need, confirming the study design (feasibility vs. pivotal), and identifying what a Pre-Submission meeting with FDA should accomplish before you enroll the first patient.

If you haven't had a Pre-Sub meeting yet, this is the time. The output of that meeting shapes your protocol. Running a LATAM study without it is a sequencing error that's difficult to correct after the fact.

Phase 2: Protocol Development and Jurisdiction Selection (Months 2 to 3)

With FDA alignment in place, develop your protocol under ISO 14155 architecture. Select your LATAM jurisdiction based on device class, indication, and approval timeline requirements, then submit to the relevant ethics committee and regulatory authority.

In Panama, El Salvador, and the Dominican Republic, ethics and regulatory approvals typically come back within 30 to 90 days of a complete submission. That window is your planning horizon for site activation.

Phase 3: Site Activation and Enrollment (Months 3 to 8)

Activate pre-qualified sites, enroll patients, and collect data under ICH-GCP standards with audit-ready documentation at every step.

The quality of your data management during this phase determines how clean your evidence package will be. Errors in data collection that seem minor during enrollment tend to become significant problems during FDA review.

Phase 4: Evidence Package Assembly (Months 8 to 12)

Compile your clinical study report, statistical analysis, and organized data room structured for your specific FDA next step. Whether that's an IDE application, a 510(k) submission, or the clinical evidence section of a PMA, the deliverable should be organized to FDA's expectations — not just internally coherent.

The Startup-Specific Consideration: Runway and Milestones

For a seed-to-Series-B startup, the regulatory strategy question is inseparable from the capital question. Your investors have a milestone schedule. Your board has a timeline. Your next round has a closing date.

A US CRO timeline of 18 to 24 months for first human data doesn't fit inside a typical startup runway. A LATAM FIH study structured for FDA bridgeability can deliver a submission-ready evidence package within 12 months under the right program structure. That difference is often the difference between having data for your Series B and not having it.

This isn't an argument to cut corners on quality. It's an argument to select the regulatory jurisdictions and execution model that match your actual timeline constraints — without compromising the standards that make the data usable.

Common Sequencing Mistakes to Avoid

Starting protocol development before confirming your FDA pathway. If you don't know whether you're targeting a De Novo or a PMA, you can't write the right protocol. The evidence standard is different, and rewriting a protocol after enrollment has started is expensive.

Selecting a jurisdiction for speed alone. A fast approval timeline only matters if the site network in that jurisdiction has genuine experience with your device category and can execute to ISO 14155 standards. Speed and quality aren't mutually exclusive, but they require deliberate site selection.

Treating the LATAM study as separate from the FDA strategy. Every decision in your LATAM trial — from endpoint selection to data collection procedures — should be made with your FDA submission in mind. The two tracks are one plan.

Underestimating the data room requirement. FDA reviewers expect organized, auditable data. A clinical study report that's internally coherent but not structured for FDA review creates unnecessary friction at submission. Build the data room to FDA's expectations from the start.

How bioaccess® Structures This for Sponsors

bioaccess® is a CRO that manages first-in-human clinical trials for MedTech, Biopharma, and Radiopharma startups through exactly this kind of sequenced approach. The FIH-12™ program covers all nine workstreams — from FDA strategy alignment and protocol development through site activation, patient enrollment, data management, and delivery of a submission-ready clinical evidence package — within 12 months.

One accountable team manages all nine workstreams across a network of 50-plus pre-qualified sites in Panama, Colombia, El Salvador, Chile, and the Dominican Republic. Every study is anchored to the sponsor's intended FDA pathway from day one, and the final deliverable is a clinical study report and organized data room structured for the sponsor's next FDA step.

Intake is limited to a maximum of eight new programs per quarter — worth factoring into your planning timeline.

FAQs

Does FDA actually accept clinical data from Latin American trials?
Yes. Under FDA 21 CFR 812.28, data from foreign clinical investigations of medical devices may be accepted in support of IDE and marketing submissions, provided the study was conducted in accordance with Good Clinical Practice and the sponsor can verify data quality and integrity. The key requirement is that the study is designed and executed to the same standards FDA would expect from a US study.

How long do regulatory approvals take in Panama, El Salvador, and the Dominican Republic?
Ethics and regulatory approvals in these jurisdictions typically take 30 to 90 days from a complete submission. That refers to the approval process specifically, not the overall trial duration.

What is the difference between a feasibility study and a pivotal study in this context?
A feasibility study evaluates the preliminary safety and performance of a device in a small patient population. A pivotal study generates the primary clinical evidence for a marketing submission. For most startups, the LATAM FIH study is a feasibility study that informs and supports the subsequent US pivotal study.

Can LATAM FIH data support a 510(k) submission directly?
In some cases, yes. If the 510(k) requires clinical data to demonstrate substantial equivalence, a well-documented LATAM feasibility study conducted under ISO 14155 and ICH-GCP standards can serve as that clinical evidence. The specific requirements depend on the device class and the predicate.

What is ISO 14155 and why does it matter for FDA submissions?
ISO 14155 is the international standard for Good Clinical Practice in clinical investigations of medical devices. FDA recognizes it as the applicable GCP standard for medical device trials, and studies conducted under its framework are structured to meet FDA's foreign clinical data acceptance requirements under 21 CFR 812.28.

When should a startup begin thinking about LATAM regulatory strategy?
Ideally, before protocol development begins. The earlier you align your LATAM study design to your FDA pathway, the less rework you'll face later. For most startups, the right entry point is at or shortly after an IDE approval or Series A close, when both the capital and the regulatory authorization to proceed are in place.

What happens if the LATAM jurisdiction doesn't have experienced investigators for my device category?
This is a real risk — and a reason why jurisdiction selection should be based on more than approval timelines alone. Site networks with documented experience in your device category reduce protocol execution risk. Evaluating investigator experience and site qualification before finalizing your jurisdiction is an important part of the planning process.

Where to Start

Sequencing LATAM approvals with your FDA pathway isn't complicated in principle. It requires knowing your FDA pathway before you design your protocol, selecting jurisdictions based on both approval timelines and site capability, and building your evidence package to FDA's expectations from the first day of enrollment.

If you're approaching that planning window, the bioaccess® FIH-12™ program is structured specifically for this sequence. Learn more at bioaccessla.com.

• Why EDC Selection Looks Different for FIH Studies
• The Core Requirements for a FIH-Ready EDC
  • 21 CFR Part 11 Compliance
  • ISO 14155 Compatibility for Medical Device Trials
  • Fast Configuration and Startup
  • Multi-Site and Multi-Country Data Collection
  • Regulatory Submission Export Formats
• What to Evaluate Beyond the Feature List
  • Vendor Experience with Early-Phase Studies
  • Data Management Support Model
  • Integration with Your CRO's Workflow
• Platforms Commonly Used in Early-Phase Trials
• The Biggest Mistakes Sponsors Make with EDC Selection
• How EDC Fits Into a FIH Program
• FAQs

Your electronic data capture system isn't a back-office detail when you're running a first-in-human trial. It's the infrastructure that determines whether your dataset is FDA-submittable or a rework project. Pick the wrong platform and you'll spend months cleaning data that should have been clean from day one.

This guide covers what actually matters when selecting an EDC for a FIH study — not a 200-site Phase III, but an early-feasibility or first-in-human trial where your team is lean, your timeline is tight, and the data package you generate needs to hold up under FDA scrutiny.

Why EDC Selection Looks Different for FIH Studies

Most EDC comparisons are written for large-scale trials with dedicated IT teams, established data management departments, and long build timelines. FIH studies operate under different conditions.

You're typically working with a small investigator team, a limited subject count, and a protocol that may still be evolving close to site activation. You need a platform that configures quickly, doesn't require months of validation work before you can collect a single data point, and produces outputs that map cleanly to your regulatory submission format — whether that's an IDE, a 510(k) package, or an IND.

The compliance bar doesn't change. ICH-GCP standards apply regardless of study size. If your trial runs outside the US, FDA 21 CFR 812.28 governs how that foreign clinical data is accepted. Your EDC needs to support audit trails, access controls, and data integrity standards that will survive a regulatory review.

The Core Requirements for a FIH-Ready EDC

21 CFR Part 11 Compliance

This is non-negotiable. Any EDC used in a trial intended to support an FDA submission must meet 21 CFR Part 11 requirements for electronic records and electronic signatures — audit trails for every data entry and modification, role-based access controls, and validated software with documented testing.

If a vendor can't provide a current validation package and a 21 CFR Part 11 compliance statement, move on.

ISO 14155 Compatibility for Medical Device Trials

Medical device FIH studies follow ISO 14155, the international standard for clinical investigation of medical devices. Your EDC needs to support data collection structures that align with this standard: adverse event capture, device accountability, protocol deviation tracking, and investigator assessments that map to the endpoints defined in your clinical investigation plan.

Not every EDC vendor has experience with device trials. Many are built primarily for drug studies, where the data architecture looks different. Ask specifically about ISO 14155 support and request examples of prior device study builds.

Fast Configuration and Startup

A FIH study on a 12-month timeline cannot absorb a 16-week EDC build. The best platforms for early-phase device and biopharma studies offer library-based form building, pre-validated study templates, and configuration timelines measured in weeks. Look for vendors who can demonstrate how quickly they activate a study from a finalized protocol — and get a realistic timeline in writing before you sign.

Multi-Site and Multi-Country Data Collection

If your trial runs across sites in Panama, Colombia, El Salvador, Chile, or the Dominican Republic, your EDC needs to support multi-language data entry, local time zone handling, and site-level access controls. Data collected across different regulatory jurisdictions still needs to flow into a single, clean, centralized database.

This is especially relevant when site staff are working in Spanish and your data management team is reviewing in English. The platform needs to handle that workflow without introducing transcription risk.

Regulatory Submission Export Formats

Your EDC should export data in CDISC CDASH and SDTM formats — the standards FDA expects for data submissions. If it can't produce clean SDTM datasets, your data management team will be doing manual conversions, which adds time, cost, and the risk of errors entering your submission package. Confirm the export formats before you commit to a platform.

What to Evaluate Beyond the Feature List

Vendor Experience with Early-Phase Studies

A vendor's reference list matters. Ask how many FIH or Phase I studies they've supported, and specifically whether any involved medical devices or international sites. A platform built primarily for large Phase III oncology trials may not have the configuration flexibility or support model that works for a 15-subject FIH feasibility study.

Data Management Support Model

Some EDC vendors sell software only. Others offer managed data management services alongside the platform. For a startup running its first FIH trial, a fully managed model often makes more sense than purchasing a license and building out your own DM team. Understand what's included in the contract and what's billed separately before you sign.

Integration with Your CRO’s Workflow

If you're working with a CRO that manages data management as part of its engagement, your EDC selection may be partially dictated by that CRO's existing infrastructure. This is worth discussing early. A CRO with validated workflows built around a specific EDC platform will execute faster and with fewer errors than one adapting to an unfamiliar system mid-study.

At bioaccess®, data management is one of the nine workstreams covered under the FIH-12™ program. EDC setup, data monitoring, and preparation of the final evidence package are handled by the same team managing your protocol, your sites, and your regulatory submissions — not handed off to a separate vendor.

Platforms Commonly Used in Early-Phase Trials

This isn't an exhaustive market review, and the right choice depends on your specific protocol, budget, and CRO relationship. That said, a few platforms appear consistently in early-phase and FIH study contexts.

Medidata Rave is the most widely deployed EDC in clinical research globally. It has strong 21 CFR Part 11 compliance infrastructure and broad regulatory acceptance. The tradeoff is configuration complexity and cost — it's better suited to sponsors with experienced data management teams or CROs with deep Medidata expertise.

REDCap is widely used in academic and early-phase settings for its low cost and fast setup. It can be configured for 21 CFR Part 11 compliance, but that requires careful validation work. It's not a commercial EDC and lacks some of the enterprise support features larger trials need. For a lean FIH study with a strong data management team, it can work — but the validation burden needs to be managed carefully when the data is intended to support an FDA submission.

Veeva Vault EDC has gained adoption in recent years, particularly in biopharma. It integrates well with other Veeva modules and has strong audit trail and compliance features. Configuration is generally faster than Medidata for straightforward protocols.

Castor EDC is built specifically for early-phase and academic trials, with a faster setup model and strong multi-language support. It's used in international studies and has a compliance framework that supports 21 CFR Part 11. For FIH studies with international sites, it's worth evaluating.

OpenClinica has a strong compliance pedigree, particularly in studies requiring CDISC output. It has both a commercial and an open-source version; the commercial version includes the validation documentation needed for regulatory submissions.

The Biggest Mistakes Sponsors Make with EDC Selection

Selecting based on price alone. The cheapest platform often carries the highest total cost once you factor in configuration time, data cleaning, and conversion work at submission. A platform that produces clean SDTM output from day one is worth more than one that requires manual post-processing.

Treating EDC as a standalone decision. Your EDC choice affects your CRO, your data management team, your regulatory timeline, and your submission package. Make the decision in context, not in isolation.

Underestimating the validation requirement. Every EDC used in a regulated trial needs to be validated. If the platform isn't already validated for your use case, that work takes time and costs money. Build it into your timeline from the start.

Locking in a platform before your protocol is finalized. EDC configuration is driven by your data collection requirements, which come from your protocol. Starting the build before the protocol is stable leads to expensive amendments and delays.

How EDC Fits Into a FIH Program

A FIH study generates the foundational dataset your entire regulatory pathway depends on. The EDC is the system that captures, validates, and stores that data. Set it up correctly and your final data package is clean, audit-ready, and formatted for submission. Get it wrong and you're looking at data remediation that can delay your IDE or 510(k) by months.

The most efficient path is to select your EDC as part of your overall FIH program design — not as a separate procurement. When your CRO manages data management as an integrated workstream alongside protocol development, site activation, and regulatory submissions, the EDC configuration is built to match the protocol from the start.

That integration is part of what makes a structured FIH program different from assembling vendors independently. If you're evaluating CRO options, it's worth understanding how each handles data management and what EDC infrastructure they bring to the engagement.

FAQs

What is an EDC system in clinical trials?
An electronic data capture (EDC) system is software used to collect, manage, and store clinical trial data in a structured, validated digital format. It replaces paper case report forms and provides the audit trail and access controls required for regulatory submissions.

Does my EDC need to be 21 CFR Part 11 compliant for a FIH study?
Yes. Any EDC used in a trial intended to support an FDA submission must comply with 21 CFR Part 11, which governs electronic records and electronic signatures. This includes audit trails, role-based access, and validated software with documented testing.

Can I use REDCap for a trial intended to support an FDA submission?
REDCap can be configured to meet 21 CFR Part 11 requirements, but it requires careful validation work that the sponsor or CRO must manage. It doesn't come with built-in regulatory validation packages the way commercial platforms do, so the compliance burden is higher.

How long does EDC configuration typically take for a FIH study?
For a straightforward FIH protocol, commercial EDCs with template libraries can typically be configured in four to eight weeks. More complex protocols or custom builds take longer. Factor this into your overall study startup plan.

What data export formats does FDA expect for EDC submissions?
FDA expects CDISC-compliant formats — specifically CDASH for data collection standards and SDTM for submission datasets. Your EDC should produce these formats directly. If it can't, your data management team will need to perform conversions, which adds time and risk.

Does the EDC need to support multiple languages for international FIH studies?
If your trial runs at sites where staff work in a language other than English, multi-language data entry support is important. For studies conducted in Latin American countries, site staff typically work in Spanish. Clean data collection in the local language reduces transcription errors and simplifies data review.

How does EDC selection affect my FDA submission timeline?
A well-configured EDC that produces clean, CDISC-compliant data shortens the time between last patient visit and a submission-ready data package. A poorly configured one can add months of cleaning and reformatting. EDC selection is a direct input to your regulatory timeline — not a separate operational decision.

Choosing the right EDC for a FIH study comes down to one question: will this platform produce a clean, FDA-submittable dataset within your timeline? Get the compliance infrastructure right, align the platform with your protocol and your CRO's workflow, and treat EDC selection as part of your overall program design from day one.

If you're planning a first-in-human trial and want to understand how data management fits into a structured FIH program, bioaccess® manages all nine workstreams under one engagement — including EDC setup and data management — across its network of sites in Panama, Colombia, El Salvador, Chile, and the Dominican Republic.

• What the FDA Is Actually Asking
• The 510(k) Pathway: Substantial Equivalence
  • What "substantially equivalent" means in practice
  • Timeline and workload
• The PMA Pathway: Valid Scientific Evidence
  • What a PMA clinical program looks like
  • Timeline and investment
• Key Differences at a Glance
• The De Novo Pathway: A Third Option Worth Knowing
• How Pathway Choice Shapes Your FIH Study
• Aligning FIH Trial Design to Your Pathway
• Practical Questions to Ask Before You Choose
• When Founders Get This Wrong
• FAQs

Choosing between a 510(k) and a Premarket Approval (PMA) is one of the most consequential decisions a medical device founder makes. Get it right early, and your clinical strategy, budget, and investor timeline all line up. Get it wrong, and you may spend 18 months collecting data that doesn't satisfy the evidentiary standard your pathway actually requires.

This article breaks down the core differences between the two pathways, how to determine which applies to your device, and what that choice means for your first-in-human trial design.

What the FDA Is Actually Asking

Both pathways exist to answer the same fundamental question: is this device safe and effective enough to be on the US market? The difference lies in how much evidence the FDA needs to reach that answer — and that requirement flows directly from how your device is classified.

The FDA assigns every medical device to one of three classes based on patient risk.

• Class I devices carry low risk. Most are exempt from premarket review entirely.
• Class II devices carry moderate risk. Most reach market through the 510(k) pathway.
• Class III devices carry the highest risk — typically because they sustain or support life, are implanted, or present an unreasonable risk of illness or injury. These require PMA.

Your device's classification is the starting point for everything else.

The 510(k) Pathway: Substantial Equivalence

A 510(k) submission asks the FDA to clear your device by demonstrating substantial equivalence to a legally marketed predicate. You're not proving safety and effectiveness in isolation — you're showing your device performs comparably to something already on the market.

What “substantially equivalent” means in practice

Your device must share the same intended use as the predicate and either the same technological characteristics, or different characteristics that don't raise new safety or effectiveness questions. That framing matters because it shapes what kind of clinical data — if any — you actually need to collect.

Many 510(k) submissions rely primarily on bench testing, biocompatibility data, and performance testing. When clinical data is required, it's typically a focused study rather than a full pivotal trial.

Timeline and workload

The FDA's standard review period for a 510(k) is 90 days from acceptance, though total elapsed time often runs longer when the agency issues additional information requests. For a device with a clear predicate and strong bench data, the 510(k) can be a relatively fast path to market.

The risk is predicate selection. A weak or distant predicate invites a Not Substantially Equivalent determination — which can push you toward De Novo or PMA territory without warning.

The PMA Pathway: Valid Scientific Evidence

A PMA requires you to demonstrate reasonable assurance of safety and effectiveness through valid scientific evidence. There's no predicate to point to. The FDA evaluates your device on its own merits, which means your clinical dataset needs to stand alone.

This is the pathway for Class III devices: implantable cardiac devices, certain neurological implants, high-risk diagnostics, and others where failure could cause serious harm.

What a PMA clinical program looks like

A PMA typically requires at least one well-controlled pivotal trial — often with a statistically powered sample size, defined primary endpoints, and a comparator arm. The FDA's review of that data is rigorous, and the agency may convene an advisory panel for high-profile submissions.

The IDE (Investigational Device Exemption) is the mechanism that allows you to collect pivotal data in the first place. Before you enroll a single patient in a significant-risk device study, you need an approved IDE. That application itself requires preliminary safety data — which is exactly where a first-in-human or early feasibility study fits in.

Timeline and investment

PMA is a longer, more expensive process than 510(k). Total development timelines from first-in-human to PMA approval can run five to ten years for complex devices. The clinical program alone typically spans multiple phases: an early feasibility study to establish safety signals, followed by a pivotal trial to generate primary effectiveness data.

For a startup, that timeline has direct implications for how you structure your FIH study and what evidence you need before your next funding round.

Key Differences at a Glance

The De Novo Pathway: A Third Option Worth Knowing

If your device is genuinely novel, poses low to moderate risk, and has no valid predicate, De Novo is worth serious consideration. It creates a new device classification and, once granted, establishes your device as a predicate for future 510(k) submissions.

De Novo is not a shortcut. It requires more documentation than a standard 510(k), and the FDA's review period is longer. But for a first-of-kind device that doesn't belong in Class III, it's the appropriate route — and it avoids the burden of a full PMA.

How Pathway Choice Shapes Your FIH Study

Your regulatory pathway determines the evidentiary standard your clinical data must meet. That standard, in turn, determines what your first-in-human study actually needs to accomplish.

For a 510(k) device, your FIH study is often a relatively small early feasibility study designed to confirm safety signals and support predicate comparisons. Endpoints are narrower, enrollment targets are smaller, and the study can typically be completed faster.

For a PMA device, your FIH study is the first step in a longer clinical program. The FDA will evaluate it as part of the overall evidence package, and the data needs to be structured to support the IDE application for your pivotal trial. Endpoints, patient population, and follow-up duration all have to be designed with that pivotal study in mind from day one.

This is why FDA strategy alignment can't be an afterthought. Design your FIH study without anchoring it to your intended pathway, and you risk collecting data that doesn't move your program forward.

Aligning FIH Trial Design to Your Pathway

At bioaccess®, every study in the FIH-12™ program begins with FDA strategy alignment as the first of nine workstreams. The protocol is built around the sponsor's intended pathway — whether that's IDE, 510(k), De Novo, PMA, or HDE — so the clinical evidence package that comes out of the program is structured for the submission it needs to support.

Trials run in Panama, Colombia, El Salvador, Chile, and the Dominican Republic, where ethics and regulatory approvals are observed in 30 to 90 days, compared to 6 to 12 months in the US. That speed matters when your runway is finite and your next funding milestone depends on having human data in hand.

The FIH-12™ program delivers a submission-ready evidence package within 12 months. All data is structured for FDA acceptance under 21 CFR 812.28, which governs the use of foreign clinical data in US submissions.

Practical Questions to Ask Before You Choose

Before committing to a pathway, work through these with your regulatory team:

What is your device's intended use, and does it match an existing predicate? If yes, 510(k) is likely your starting point. If no, you're looking at De Novo or PMA.

What risk class does the FDA assign to devices with your intended use? The FDA's product classification database is the first place to check. If your device type is consistently Class III, PMA is your pathway regardless of predicate availability.

Have you had a Pre-Submission (Q-Sub) meeting with the FDA? A Pre-Sub is the most direct way to get the agency's early read on your classification and pathway. It's not binding, but it significantly reduces the risk of a wrong-pathway investment.

What does your clinical evidence need to show? For 510(k), you need to demonstrate comparability. For PMA, you need to demonstrate safety and effectiveness. These are different evidentiary standards that require different study designs.

What is your funding timeline? If you have 18 months of runway and need human data before a Series B closes, a PMA pivotal trial isn't achievable in that window. But a well-designed early feasibility study that supports your IDE application can be.

When Founders Get This Wrong

The most common mistake is assuming a 510(k) pathway because a similar device exists on the market. Predicate selection is more nuanced than it looks. A device with the same intended use but meaningfully different technology may not qualify as substantially equivalent — and a Not Substantially Equivalent determination late in the process is expensive.

The second common mistake is under-designing the FIH study for a PMA pathway. Founders sometimes treat the early feasibility study as a standalone safety check rather than as the foundation for a pivotal trial. When the pivotal trial IDE application reaches the FDA, gaps in the early data create delays that could have been avoided.

Both mistakes come down to the same root cause: regulatory strategy that starts too late.

FAQs

What is the main difference between a 510(k) and a PMA?
A 510(k) clears a device by showing it is substantially equivalent to a legally marketed predicate. A PMA approves a device based on valid scientific evidence of safety and effectiveness, without relying on a predicate. PMA applies to Class III devices and requires a full clinical program; 510(k) applies primarily to Class II devices and often requires limited or no clinical data.

Does a 510(k) device need clinical trials?
Not always. Many 510(k) submissions rely on bench testing, biocompatibility data, and performance testing. Clinical data is required when bench testing alone can't establish substantial equivalence, or when the device's intended use involves a clinical performance claim that needs human data to support it.

What is an IDE and when do you need one?
An Investigational Device Exemption (IDE) is FDA authorization to use an investigational device in a clinical study. You need an IDE for any significant-risk device study conducted in the United States. For PMA devices, the IDE is the mechanism that allows you to collect the pivotal trial data the FDA requires for approval.

Can a Class II device require PMA?
In rare cases, yes. The FDA can require a Class II device to go through PMA if it determines that general and special controls aren't sufficient to provide reasonable assurance of safety and effectiveness. This is uncommon but worth confirming for novel device types.

What is the De Novo pathway and how does it differ from 510(k) and PMA?
De Novo is a classification pathway for novel, low-to-moderate-risk devices with no valid predicate. It creates a new device type and establishes the device as a predicate for future 510(k) submissions. It requires more documentation than a standard 510(k) but is less burdensome than PMA — making it the right route for genuinely first-of-kind devices that don't pose Class III risk.

How does my FDA pathway choice affect my first-in-human study design?
Your pathway determines the evidentiary standard your clinical data must meet. A 510(k) FIH study typically needs to confirm safety and support predicate comparisons, with narrower endpoints and smaller enrollment. A PMA FIH study is the first step in a longer clinical program and must be designed with the pivotal trial in mind from the start — including endpoints, patient population, and follow-up duration.

How long does PMA approval typically take compared to 510(k)?
The FDA's standard review period for a 510(k) is 90 days from acceptance, though total elapsed time is often longer. For PMA, the FDA has 180 days from filing acceptance to act, but the full development timeline from first-in-human to PMA approval for complex devices can span several years — including the time required to complete a pivotal trial.

Pathway selection is a regulatory decision with clinical, financial, and strategic consequences. The earlier you align your FIH study design to your intended submission, the less time and capital you spend collecting data that doesn't move your program forward.

If you're mapping your device's regulatory strategy and want to understand how a structured FIH program fits into that plan, learn more at bioaccessla.com.