Predicate Devices and Substantial Equivalence, Explained for Medical Software

A predicate device is a device already legally on the market that a new device points to and says, in effect, this new thing is close enough to that cleared thing that it should be allowed too. Substantial equivalence is the finding that the new device has the same intended use and the same basic technology as its predicate, or that any differences do not raise new questions of safety or effectiveness. This route lets many devices reach patients without a fresh clinical trial, which is efficient for well-understood hardware, but it demonstrates likeness to a prior product rather than direct proof of benefit, and software as a medical device stretches the whole idea. This is an educational article about regulation, not medical advice, and for your own care you should speak with a clinician who knows your history.

I approach this from the regulatory side of my work. My background here includes FDA Clinical Investigator training and training in medical device regulations from KTH covering EU MDR, IVDR, FDA pathways, and software as a medical device, and I have co-developed clinical software that had to answer these questions in practice. What follows is how the mechanism works, stated neutrally, and where its logic wears thin.

What substantial equivalence actually asks

The comparison rests on two pillars. First, does the new device have the same intended use as the predicate, meaning the same clinical purpose in the same setting for the same kind of patient. Second, does it carry the same technological characteristics, or, if the technology differs, is there evidence that the differences do not raise new questions about safety and effectiveness. A device that clears this bar can be marketed on the strength of the comparison rather than a standalone trial.

Notice what the question is and is not. It asks whether the new device is enough like something already trusted. It does not ask, on its own, whether either device improves a health outcome. That earlier trust was often established years ago, sometimes by a chain of devices each cleared against the one before it. The logic is comparative, and comparison is only as strong as the thing you compare against.

Why the pathway exists at all

There is a real rationale here, and it deserves a fair hearing. Most medical devices are iterations, not inventions. A new infusion pump, a new catheter, a new blood pressure cuff sits in a mature category where the failure modes are known and the engineering standards are settled. Forcing a full clinical trial for every incremental version would slow useful improvements, raise costs, and rarely teach anyone anything new about a well-characterized technology. Equivalence lets regulators concentrate scrutiny where the novelty and the risk are highest. Used within its intended range, on physical devices in understood categories, it is a defensible piece of engineering governance.

What a predicate proves, and what it quietly does not

Here is the distinction that matters most for readers trying to judge a cleared device. Clearance through equivalence tells you the device resembles a lawful predicate closely enough that regulators did not require new safety questions to be answered. It does not tell you the device was shown, in a trial, to help patients. Those are different claims, and they are easy to blur.

Two limits deserve attention. The first is what I would call comparison drift. If device C is cleared against device B, and B was cleared against A, the newest product can end up several steps removed from any original body of clinical evidence, with each hop introducing small differences that were individually reasonable but collectively meaningful. Nothing in a single equivalence decision looks at the whole chain.

The second limit is the predicate itself. Equivalence inherits the strengths and the weaknesses of the thing it points to. If a predicate was cleared on thin grounds, or was later found to have problems, the devices that leaned on it do not automatically get re-examined. A common trap in reading a clearance is to treat it as a grade for the product when it is really a statement about a relationship between two products.

Why software strains the concept

The equivalence framework was built for objects you can hold, and software as a medical device pulls at several of its assumptions at once.

Start with sameness. Two catheters can be compared on materials, dimensions, and mechanical behavior. A pair of clinical algorithms that share an intended use, by contrast, can work in entirely different ways inside, one a simple rule set, the other a model trained on data whose contents shape every output. Calling them technologically equivalent because they take similar inputs and produce similar outputs skips the question of how each reaches its answer, and for software the internals are much of the safety story.

Then there is the moving-target problem. A physical predicate is fixed once it ships. Software changes. It gets retrained, retuned, connected to new data sources, and updated on a schedule that hardware never had. A device judged equivalent at one moment can behave differently after an update, which means the original comparison describes a version that may no longer be the one in use. I have written elsewhere on my blog about why a software medical device is not finished at launch, and equivalence at the front door does little to address what happens after.

Population fit is the third strain. A model can be genuinely equivalent to its predicate on the data it was tested against and still drift badly on a group underrepresented in that data. Equivalence checks likeness to another product, not adequacy for the full range of people who will meet the software. Two systems can match each other and both miss the same population.

What this means for evaluating a cleared tool

None of this makes the pathway illegitimate. It makes clearance a floor, not a ceiling, and a narrow floor for software. When I assess a digital health tool, I read the intended use statement first, because that single sentence bounds everything the clearance covers, and real-world use often wanders past it. Then I ask what evidence exists beyond the equivalence finding: prospective testing, external validation on a population that looks like the intended users, and a plan for monitoring performance over time. A cleared status answers a regulatory question. Whether the tool earns clinical trust is a separate inquiry, and it is the one that should drive how anyone relies on it.

The honest summary is this. Substantial equivalence is a sensible tool for stable hardware and a stretched one for adaptive software. Knowing which situation you are in changes how much a clearance should reassure you.