How New Health Tech Actually Gets Approved
"Software as a medical device" is a real regulatory category now, not a loophole — and that's exactly why approval takes so much longer than a typical app launch.
Worth reading first: A Second Opinion, Not a Replacement
“Software as a medical device” sounds like a workaround someone invented to dodge oversight. It is the opposite — a real regulatory category built specifically because software started making the kind of decisions only hardware used to make, and it is exactly why approval takes so much longer than shipping a typical app.
Who actually approves a new piece of health tech
In the United States, the Food and Drug Administration reviews anything that meets the legal definition of a medical device before it can be marketed for a medical purpose — historically physical hardware like pacemakers and imaging machines, now extended to qualifying software as well. Most countries run an equivalent body; the specific name changes, the underlying idea does not.
Not everything health-adjacent needs this review. A general wellness app that tracks steps and never claims to diagnose or treat anything typically falls outside it entirely — the trigger is a specific claim about diagnosing, treating, or preventing a disease, not just the general subject matter of health.
"Software as a medical device" is a real category now
SaMDcovers software that performs a medical function on its own, without needing to run on a piece of dedicated hardware — an app that analyses a scan and outputs a diagnosis-relevant result, for instance, without itself being a scanner. The category exists because that kind of software makes exactly the sort of decision that used to require a physical device a regulator had already been reviewing for decades, and pretending it was “just an app” because it ran on a phone would have left a real gap in oversight.
Why approval takes longer than a typical app launch
A typical consumer app ships, gets user feedback, and iterates in public — bugs get patched after launch, not eliminated before it. A regulated medical device, software or not, has to demonstrate safety and effectiveness with real evidence before a single patient can be affected by it, and any meaningful change afterward can trigger a fresh review rather than a routine update.
Key takeaways
- A regulator like the FDA reviews software that makes a medical claim — diagnosing, treating, or preventing disease — before it can reach patients.
- A general wellness app that makes no such claim typically falls outside this review entirely, regardless of how health-adjacent its data feels.
- Software as a Medical Device is a real category built because qualifying software makes the same kind of decision a regulated physical device used to make alone.
- Regulated approval requires proving safety and effectiveness before launch, not iterating live in public the way a typical consumer app does.