Can I Use My CE Mark Clinical Data for FDA 510(k)? Complete Guide
- Beng Ee Lim
- 3 days ago
- 13 min read
Sometimes. FDA may accept clinical data generated outside the United States, including data first collected for CE-marking work, in a 510(k) submission, but only if the study is well designed, well conducted, compliant with FDA’s foreign clinical data requirements under 21 CFR 812.28, and relevant to the U.S. substantial-equivalence case. The key issue is not whether the data came from Europe. It is whether the study supports the predicate-based questions FDA is actually asking. This comprehensive guide addresses the specific mechanics of transferring CE Mark clinical data to FDA 510(k) submissions: FDA's legal framework for accepting non-US data, technical requirements for trial design and documentation, common pitfalls that trigger FDA rejection, cost-benefit analysis, and strategic approaches for dual-market trial design.
Does FDA Accept Non-US Clinical Data for 510(k) Submissions?
Yes, FDA may accept clinical data generated outside the United States in a 510(k), but the key rule is 21 CFR 812.28. For foreign clinical investigations used in device marketing submissions, FDA expects the study to be well designed, well conducted, compliant with good clinical practice, and documented in a way that lets FDA validate the data through records review or onsite inspection if needed.
For a 510(k), that still is not enough by itself. The data also need to be relevant to the substantial-equivalence questions FDA is actually asking, including whether the evidence is applicable to the U.S. population and U.S. medical practice and whether it supports the intended use, technology, and comparison to a legally marketed U.S. predicate.
The practical takeaway is simple: FDA does not reject foreign clinical data just because it was generated outside the U.S. What matters is whether the study is credible, usable, and aligned with the 510(k) case.
What Are FDA’s Core Acceptance Criteria for CE Mark Clinical Data?
The governing rule is 21 CFR 812.28, which says FDA may accept data from a clinical investigation conducted outside the United States if the study is well designed, well conducted, conducted in accordance with good clinical practice, and documented in a way that lets FDA validate the data through records review or onsite inspection if needed.
In practice, the most important questions are these:
1. Was the study conducted in accordance with FDA’s GCP expectations?
For foreign device investigations, FDA focuses on good clinical practice, including ethics committee review, informed consent, and credible oversight of study conduct. European device studies structured around ISO 14155:2020 may align well with these expectations, but they do not qualify automatically.
2. Are the data applicable to the U.S. population and U.S. medical practice?
FDA looks at whether the patient population, clinical setting, and treatment context are relevant to how the device will actually be used in the United States. This is less about geography alone and more about whether the evidence can support a U.S. regulatory decision.
3. Do the study endpoints help answer the 510(k) substantial-equivalence question?
This is where many transfers get messy. EU clinical work is often designed to support MDR conformity and clinical evaluation, while FDA 510(k) is built around predicate comparison and substantial equivalence. Even when the underlying study is strong, the endpoints still need to be relevant to the FDA review question.
4. Can FDA validate the data if needed?
FDA expects the study records and supporting documentation to be strong enough for review and, if necessary, inspection. That means data quality, traceability, and study documentation matter, even when the clinical work was performed outside the U.S.
The practical takeaway is this: FDA is not asking whether the study was run in Europe. FDA is asking whether the study is credible, relevant, and usable for a U.S. 510(k). That is also why teams can get tripped up late. A CE-mark study may be clinically sound, but still answer the wrong regulatory question for FDA.
This is one of the places where Complizen can help, because once the likely product code, predicate set, and substantial-equivalence story are visible, it becomes much easier to judge whether existing clinical data are reusable or whether additional work is still needed.
CE Mark Clinical Evaluation vs FDA 510(k) Clinical Data: Key Differences
If you are planning one study for both Europe and the United States, the biggest risk is designing it for the wrong regulatory question.
Factor | CE Mark (EU MDR) | FDA 510(k) |
Regulatory purpose | Show the device conforms to applicable safety and performance requirements | Show the device is substantially equivalent to a legally marketed U.S. predicate |
Clinical evaluation / clinical data | Clinical evaluation required under Article 61 and Annex XIV | Clinical data required only in a minority of 510(k)s, generally less than 10 percent |
Comparator logic | No FDA-style predicate pathway | Predicate comparison is central |
Evidence emphasis | Device-specific safety, performance, and benefit-risk | Evidence that supports substantial equivalence |
Literature use | Literature may support the clinical evaluation where appropriate | Literature alone is usually not enough without the broader substantial-equivalence package |
Study design focus | Does the device perform as intended and support conformity? | Does the evidence support equivalence to the predicate? |
Endpoints | Outcomes tied to safety, performance, and clinical benefit | Outcomes relevant to the substantial-equivalence case |
Follow-up | Driven by device risk and evidence needs | Driven by what is needed to answer the 510(k) question |
Post-market evidence | PMCF may be required as part of ongoing clinical evidence generation | Post-market obligations exist, but the framework is different |
Core documentation | Clinical Evaluation Report, CER | 510(k) submission built around substantial-equivalence analysis |
The simplest way to think about it is this:
EU MDR asks: does this device conform to the applicable safety and performance requirements?
FDA 510(k) asks: does this evidence support substantial equivalence to a U.S. predicate?
That difference matters. A study designed only for MDR may still be clinically strong, but it can fall short for FDA if the endpoints, population, or analysis do not help answer the predicate-based question. This is why dual-market teams should think about the FDA product code, likely predicate set, and substantial-equivalence story early, not after the EU study is already finished. That is also one of the places where Complizen can help, by making it easier to connect likely predicates, standards, recalls, and source-linked FDA evidence before trial design gets locked in.
What Documentation Does FDA Need When You Submit CE-Mark Clinical Data in a 510(k)?
If you use non-U.S. clinical data in a 510(k), FDA will usually need more than a top-line study summary. The goal is not to prove that the study supported CE marking. The goal is to show that the study is credible, reviewable, and relevant to the 510(k) substantial-equivalence case.
In practice, the core documentation usually includes:
Study report and protocol materials, including enough detail on study design, endpoints, population, deviations, and results to let FDA assess the investigation
GCP-related documentation, showing the investigation was conducted in accordance with FDA’s foreign-clinical-data requirements under 21 CFR 812.28
Records that support data credibility and traceability, so FDA can review and, if necessary, validate the data
A clear explanation of U.S. relevance, especially whether the population and clinical setting are applicable to the U.S. population and U.S. medical practice
A substantial-equivalence bridge, showing how the study’s endpoints and findings support the 510(k) comparison to a legally marketed U.S. predicate
The most common mistake is treating the European study package as if it can be dropped into a 510(k) unchanged. It usually cannot. FDA is not reviewing the study through an MDR clinical-evaluation lens. FDA is reviewing it through a predicate-based substantial-equivalence lens. That means the submission should make the comparison logic explicit, not assume the reviewer will infer it.
When Does FDA Push Back on CE-Mark Clinical Data?
FDA does not reject foreign clinical data just because the study was run outside the United States. The real problem is usually that the study does not answer the 510(k) question FDA is actually asking. For a 510(k), the evidence has to support substantial equivalence to a legally marketed U.S. predicate, and FDA may push back when the clinical package is not strong enough, not relevant enough, or not documented well enough to carry that argument.
The most common problems usually fall into a few buckets:
1. The endpoints do not fit the 510(k) substantial-equivalence case
A study may be clinically valid and still miss the FDA review question. This happens when the trial was designed for MDR clinical evaluation, but the endpoints do not line up well with the intended use, labeling, or predicate-based comparison FDA needs for a 510(k).
2. The population or clinical setting is not clearly applicable to U.S. practice
FDA looks at whether the data are applicable to the U.S. population and U.S. medical practice. If the study population, treatment setting, or standard of care differs in a way that could change performance or safety, FDA may question how much weight the data should carry.
3. GCP or study-conduct documentation is too weak
For foreign clinical investigations, FDA expects compliance with good clinical practice, including ethics review, informed consent, and records that allow the agency to validate the study if needed. If the underlying documentation is incomplete or hard to trace, the value of the data drops fast.
4. The data package is not strong enough for the comparison being made
Sometimes the problem is not geography, it is evidentiary fit. The study may be underpowered, too short, missing the most relevant analysis, or otherwise not strong enough to support the specific substantial-equivalence claim being made in the 510(k).
The practical takeaway is simple: FDA usually pushes back on CE-mark clinical data when the study is credible clinically but weak regulatorily for a 510(k). That is exactly why teams should map the product code, likely predicate set, key endpoints, and evidence strategy early. This is also where Complizen can help, because once the likely 510(k) path is visible, it becomes easier to see whether an existing European study is genuinely reusable for FDA or whether it answers the wrong regulatory question.
Cost Impact: When Reusing CE-Mark Clinical Data Actually Helps
The economic case for reusing CE-mark clinical data is real, but it should be framed carefully. The biggest potential savings usually do not come from a regulator formally “crediting” prior European work. They come from avoiding or shrinking duplicative clinical work when FDA decides the existing foreign data are credible, relevant, and usable in the 510(k).
That matters because most 510(k)s do not require clinical data at all. FDA says it currently requests clinical data for less than 10 percent of 510(k) submissions. So the first question is not, “How much money can we save by transferring CE-mark data?” The first question is, “Do we need clinical data for this 510(k) in the first place?”
If the answer is yes, then existing CE-mark clinical data may help in three ways:
it may reduce the need for a new standalone U.S. study
it may narrow the gap to a smaller bridging or supplemental study
it may strengthen the overall substantial-equivalence package even if it does not carry the submission by itself
The real cost driver is usually not geography alone. It is whether the study answers the FDA review question. If the endpoints, population, documentation, and predicate logic line up, previously generated European data can reduce rework. If they do not, the study may still be clinically valuable but economically disappointing for a 510(k), because the manufacturer still has to generate new evidence or reanalyze the old evidence substantially.
That is also why the financial upside depends so heavily on planning. If a company understands its likely product code, predicate set, and substantial-equivalence argument early, it can design European evidence in a way that is more reusable later.
How to Design CE-Mark Clinical Work for Possible FDA Use
If a device is likely to need clinical evidence in both Europe and the United States, trial design should be planned with both regulatory questions in mind from the start.
The key is not to make the study “FDA-style” in a generic sense. The key is to make sure the study can later support the specific 510(k) substantial-equivalence case, if clinical data end up being needed. That usually starts with three things:
identify the likely FDA product code and predicate set early
make sure the study population and endpoints will still be meaningful in a U.S. predicate-based review
keep the study documentation, oversight, and data traceability strong enough to support FDA review if needed
In practice, that means:
review likely predicate devices before locking the protocol
choose endpoints that are useful not only for MDR clinical evaluation, but also for the substantial-equivalence argument
make sure the follow-up period is long enough for the device risk profile and the likely FDA comparison
document study conduct in a way that supports good clinical practice and later data validation by FDA if needed
This does not mean every dual-market manufacturer should automatically design a large FDA-driven trial. Most 510(k)s do not require clinical data at all. But if the device is likely to need clinical evidence, early alignment matters. A study designed only for MDR may still be clinically strong and still create extra work later if the endpoints, population, or analysis do not support the U.S. predicate story.
This is also one of the more practical places where Complizen can add value. Before a protocol is finalized, teams can use Complizen’s Product Code Finder and Predicate Intelligence to narrow the likely FDA path, review linked 510(k)s, and see whether the clinical strategy they are building is actually aligned with the likely predicate, standards, and evidence burden, instead of discovering that mismatch after the European study is already done.
What Real Transfer Looks Like in Practice
Instead of presenting unsupported “case studies,” this section is stronger as a set of practical scenarios. That keeps it useful without pretending to document public cases you cannot verify.
Scenario 1: The European study is already aligned with the FDA predicate story
This is the best-case version of transfer. The European study uses endpoints, follow-up, and a patient population that fit the likely U.S. predicate comparison well. In that situation, the existing clinical data may be usable in the 510(k) with limited additional work, mainly around documentation, U.S. applicability, and explicit substantial-equivalence framing. FDA allows foreign clinical data in 510(k)s when the investigation is well designed, well conducted, compliant with good clinical practice, and reviewable by FDA if needed.
Scenario 2: The European study is useful, but not enough on its own
This is probably the most realistic middle ground. The CE-mark study may be clinically strong but still leave one or two FDA questions unresolved, for example:
the study population is not clearly applicable to U.S. practice
the endpoints do not line up cleanly with the likely predicate
the follow-up period is shorter than what the FDA comparison really needs
In that situation, the European data may still shrink the problem. Instead of running a full new U.S. study, the manufacturer may only need a smaller bridging analysis, supplemental dataset, or targeted clinical add-on. The value is not that the EU study “transfers perfectly.” The value is that it may reduce how much new work is needed.
Scenario 3: The European study answers the wrong regulatory question
This is the failure mode teams underestimate. A study can be clinically solid and still be weak for FDA if it was designed only for MDR clinical evaluation and not with the 510(k) substantial-equivalence case in mind. This usually shows up in endpoint mismatch, population mismatch, or an inability to connect the study directly to a legally marketed U.S. predicate. In those cases, the European study may still be useful as background or supportive evidence, but it may not do much to reduce the core FDA evidence burden.
The real lesson
The lesson is not that CE-mark data always transfer well or that they rarely transfer. The lesson is that reusability depends on whether the study was built around the right FDA question early enough. That is one of the practical reasons Complizen can be valuable here. If a team can identify the likely product code, review likely predicates, compare linked 510(k)s, and scan relevant recall and adverse-event signals before trial design is locked, it becomes much easier to judge whether a European study is likely to support the U.S. strategy or just create false confidence.
The Fastest Path to Market
No more guesswork. Move from research to a defendable FDA strategy, faster. Backed by FDA sources. Teams report 12 hours saved weekly.
FDA Product Code Finder, find your code in minutes.
510(k) Predicate Intelligence, see likely predicates with 510(k) links.
Risk and Recalls, scan MAUDE and recall patterns.
FDA Tests and Standards, map required tests from your code.
Regulatory Strategy Workspace, pull it into a defendable plan.
👉 Start free at complizen.ai
Frequently Asked Questions
Can FDA use CE-mark clinical data if the study is more than five years old?
Sometimes. FDA does not set a simple age cutoff for foreign clinical data, but older studies may raise questions about whether the data still reflect the current device, current standard of care, and current U.S. medical practice. If the study is older, it helps to explain why it is still relevant and, where possible, support it with newer post-market or real-world evidence.
Can literature-based CE-mark clinical evaluation replace a prospective study for FDA 510(k)?
Usually not by itself. In a 510(k), FDA focuses on whether the evidence supports substantial equivalence to a legally marketed U.S. predicate. Literature may help, but it usually does not replace the broader performance and comparison package FDA expects.
What if my CE-mark trial used different endpoints than the FDA predicate?
That is one of the biggest transfer problems. FDA may still consider the study, but the submission has to explain how the endpoints support the substantial-equivalence question. In practice, that may mean reanalysis, additional justification, or supplemental data.
Can I submit CE-mark data if long-term follow-up is still ongoing?
Sometimes. FDA may consider the available data if they are already sufficient for the 510(k) question being asked, but the evidence still has to be strong enough for the device’s risk profile and the substantial-equivalence case. Ongoing follow-up does not automatically disqualify the study, but it also does not guarantee adequacy.
Do key CE-mark trial documents need to be in English for FDA?
In practice, yes. FDA has to be able to review the study materials clearly, so key records from a non-U.S. investigation should be translated well enough for FDA review and possible validation.
If FDA does not accept my CE-mark data as primary evidence, can I still submit it as supportive evidence?
Often, yes. A foreign study may still be useful as supporting context even when it does not fully carry the 510(k) substantial-equivalence case on its own. The key is to present its limitations honestly and explain how it fits with the rest of the evidence package.
Can CE-mark clinical data also support a De Novo submission?
Potentially, yes. FDA’s foreign clinical data framework applies to device marketing submissions more broadly, not just 510(k)s. But the evidentiary standard and review logic for De Novo are different, so the usefulness of the data depends on whether they support that specific regulatory case.
Does it matter if the trial was run outside Europe, such as in India or Brazil?
Not by itself. FDA focuses on good clinical practice, data quality, applicability to the U.S. population and U.S. medical practice, and the ability to validate the data if needed, not just the country where the study was conducted.
How does FDA check GCP compliance for foreign trials?
FDA can review the study records and, if needed, validate the data through records review or onsite inspection. The practical point is that the study must be documented well enough for FDA to assess credibility and traceability.
Can post-market or real-world evidence from CE-mark experience help in a 510(k)?
Sometimes. FDA has expanded its thinking around real-world evidence, but whether that evidence is useful depends on the quality, relevance, and reliability of the data for the specific regulatory decision.
What if my CE-mark study stopped early or missed enrollment targets?
FDA will look at whether the available evidence is still reliable and sufficient for the question being asked. A smaller or incomplete study is not automatically unusable, but it usually needs a careful explanation of its limitations and role in the overall evidence package.
Is an FDA Pre-Submission worth it before trying to use CE-mark data in a 510(k)?
Often, yes. The FDA Q-Submission program exists so sponsors can ask targeted questions before the main submission, including questions relevant to a planned 510(k). That can be especially useful when the team is unsure whether foreign clinical data will be enough.
