The Healthtech Regulatory Pathway, Explained for Founders

For first-time healthtech founders, the word "regulatory" can feel like a wall. It doesn't have to be. The pathway is well-defined, and understanding it early helps you build evidence as you go — rather than scrambling for it at the end. Here's the plain-English version.

This article is a general overview, not regulatory advice. Always confirm requirements with a qualified regulatory professional for your specific product.

First question: are you a medical device?

Not every healthtech product is a regulated medical device. The dividing line is intended purpose. If your product is intended to diagnose, prevent, monitor, treat, or alleviate a condition, it's likely a medical device. A general wellness app usually isn't.

This distinction drives everything that follows, so get it right early.

Classification: how much scrutiny applies

Medical devices are grouped by risk. The higher the risk, the more evidence regulators require:

• Class I — low risk (e.g. many basic apps and tools)
• Class IIa / IIb — medium risk
• Class III — high risk (e.g. implantables)

Software is increasingly its own category — Software as a Medical Device (SaMD) — with its own rules about updates, AI/ML changes, and clinical evaluation.

The evidence you'll need

Whatever your class, you'll need to demonstrate:

1. Safety — the product doesn't cause harm.
2. Performance — it does what you claim.
3. Clinical evaluation — evidence, appraised against the state of the art.

This is where clinical input stops being optional. Regulators want evidence grounded in real clinical use, appraised by people with relevant expertise.

UK and EU at a glance

Market	Marking	Oversight
Great Britain	UKCA	MHRA
European Union	CE	Notified Bodies under the MDR

If you're targeting both, plan for both from the start — the requirements overlap but aren't identical.

Where clinical experts fit in

Clinicians aren't just useful for product feedback — they're central to your regulatory evidence:

• Clinical evaluation needs qualified appraisal of your evidence.
• Usability and safety testing needs clinicians in realistic settings.
• Post-market surveillance benefits from ongoing clinical input.

Building relationships with the right specialists early means your evidence base grows alongside your product, instead of becoming a last-minute bottleneck. That's a core reason healthtech teams use Orbion Connect — and you can see it in our case studies, including a regulatory consultancy that needed a specialist with current policy knowledge fast.

The takeaway

The regulatory pathway rewards founders who start early. Understand your classification, build clinical evidence continuously, and treat clinicians as partners in your evidence base — not a box to tick before launch.