Clinical evaluation is where many startups lose time (and confidence) because it feels like a black box.
But you don’t need to “solve clinical” in week one. You do need to make a few early decisions so you don’t build the wrong evidence plan, choose the wrong claims, or end up rewriting your strategy late.
If you’re still orienting yourself in MDR, start here:
And if you like the “roadmap” framing, this is the companion piece:
Clinical evaluation in plain English
Clinical evaluation is the structured way you show that your device:
- achieves its intended purpose
- is safe
- performs as claimed
…based on clinical data.
It’s not automatically “a clinical trial.” It’s a strategy + evidence package that can include literature, existing data, PMCF plans, and (sometimes) clinical investigations.
Why you should plan early (even if you’re pre-revenue)
If you delay clinical evaluation planning, you typically end up with:
- claims that are too broad (and impossible to support)
- a mismatch between intended purpose and evidence
- a late surprise that equivalence isn’t acceptable for your case
- a product roadmap that doesn’t generate the data you’ll need
Planning early keeps your product and regulatory strategy aligned.
The 6 early decisions that save you months
1) Your intended purpose + claims (keep them evidence-shaped)
Your clinical strategy starts with what you want to say.
If your intended purpose is still fuzzy, fix that first:
Startup rule:
- Write claims you can realistically support within 12–18 months.
2) Your device classification and risk profile
Clinical expectations scale with risk.
If you haven’t done classification yet, do that next:
3) Your “clinical pathway”: equivalence vs own data
Early question:
- Are you planning to rely on equivalence, or generate your own clinical data?
Under MDR, equivalence is often harder than startups expect (especially without access to the competitor’s technical documentation).
Planning early means you can avoid building a strategy that collapses later.
4) Your clinical evidence map (what you have vs what you need)
Make a simple table:
- Claim
- Clinical benefit / performance endpoint
- Evidence source (literature, bench, usability, clinical, RWE)
- Gap
- How you’ll close it
Definition of done:
- You can point to each claim and say: “This is the evidence we’ll use.”
5) Your PMS/PMCF logic (even before market)
Even pre-market, you should outline:
- how you’ll collect real-world feedback
- what triggers updates to your clinical evaluation
- what PMCF activities are proportionate for your risk class
This prevents the classic “we’ll do PMCF later” scramble.
6) Your timeline + decision gates
Clinical strategy isn’t just a document. It’s a set of decisions with deadlines.
Add gates like:
- claim freeze date
- equivalence feasibility decision
- first CER outline
- evidence gap review
- PMCF plan draft
This keeps clinical aligned with product releases.
What “startup-sized” clinical planning looks like
You don’t need a 120-page CER today.
A lean early package can be:
- 1-page clinical strategy summary
- evidence map table
- draft CER outline (headings + what will go where)
- PMS/PMCF outline
- a list of “make-or-break assumptions” (e.g., equivalence access)
Common mistakes (so you can avoid them)
- Writing marketing claims first, then trying to “find evidence” later
- Assuming equivalence will be easy
- Treating clinical as separate from intended purpose and risk management
- Not building data generation into the product roadmap
Want a clinical strategy sanity check in 60 minutes?
If you want a clear, proportionate clinical evaluation plan (that matches your intended purpose, risk class, and startup timeline), book a free 60-minute MDR Strategy Call.
Book here: https://calendly.com/niko-mangold-consultants/30min