US MedTech teams ask this after the first OUS patient is enrolled, which is already too late. The useful version of the question is not “will FDA accept foreign data?” It is “did we generate the kind of early feasibility evidence an IDE reviewer can actually use?”
FDA can use outside-US clinical data. What it will not do is retrofit a poorly designed FIH into an IDE package because the sponsor later decided the US path needed it.
What FDA is looking for in early OUS data
For a novel device, an IDE conversation is about whether the next US study is justified and whether the risk controls are real. Early feasibility is allowed to be small and iterative. It is not allowed to be sloppy. The files that travel are the protocol, the monitoring plan, the endpoint definitions, the informed-consent process, and a clean accounting of every device deficiency and adverse event.
If those pieces were written to a local ethics committee’s minimum and never mapped to FDA’s early feasibility thinking, the OUS cohort becomes a narrative, not a dataset.
The three failure modes I see
- Protocol drift. The OUS site “adapted” inclusion criteria, imaging, or follow-up to what the hospital already does. That is enrollment speed purchased with comparability.
- Monitoring that cannot be reconstructed. Source documents in a language and format nobody planned to reconcile. When the IDE questions arrive, you cannot show who saw what, when.
- Wrong use of the patients. Treating FIH as a mini-pivotal. Early feasibility is supposed to answer design and procedure questions. If you burned the accessible patients on a protocol that cannot iterate, you have neither a learning study nor an IDE-ready one.
How to design the OUS FIH so it can travel
Write the protocol once, for the evidence you need FDA to accept, then choose the country that can run that protocol. Colombia, Panama, or another LATAM site is a tactic. Australia is a tactic. The evidence plan is the strategy.
That means core-lab or at least standardized imaging, a single adverse-event dictionary, device accountability that survives import and explant, and a statistical plan that is honest about sample size. It also means the importer of record and the ethics packet are on the critical path from week one, not after first-patient-in slips.
What “support an IDE” actually looks like
Support is not automatic clearance. Support is a briefing package where the OUS series explains why the US early feasibility or pivotal design is the right next study, what changed in the device or procedure, and why residual risk is understood. Sponsors who get that far usually decided the FDA use-case before they picked the country, not after the first implant went well.
If you are already in follow-up and asking this question, inventory the protocol deviations, the imaging completeness, and the consent language before you book the pre-sub. Those three files tell you whether you have an IDE argument or a case series.
Leave a Reply