Apple’s New Medical Device Labels: A Step Forward… But Not Enough

Apple’s latest move to label “regulated medical device” apps in the App Store has been widely welcomed as a win for transparency. And at first glance, it is. Giving users clearer signals about which apps sit within formal regulatory frameworks is undeniably positive.

But when you look closer, this change highlights a deeper issue in digital health: visibility is not the same as validation.

What Apple has actually announced

Apple will now require certain health apps to declare whether they are classified as regulated medical devices, with this status displayed directly on App Store listings across the UK, EU and US.

• Developers must self-declare this status and provide supporting information such as:

• Regulatory identifiers (e.g. FDA or EU registration numbers)

• Intended use statements

• Safety information and instructions for use

Apps that fail to comply by early 2027 risk being unable to update.

On paper, this creates a clearer distinction between:

•  Apps operating within regulated medical frameworks

• Apps that are not

And that distinction matters.

The problem: Self-declaration is not assurance

Here’s the challenge... This system is fundamentally based on self-declaration.

Developers are responsible for determining whether their app qualifies as a regulated medical device and for providing the relevant information. While this may align with how regulation works in practice, it does not equate to independent validation.

Even if every developer acts in good faith, this still leaves gaps:

• No consistent, external verification layer for users

• No quality benchmark beyond regulatory classification

• No clear indication of clinical effectiveness or real-world impact

And crucially: being regulated does not mean something works, it only means it meets regulatory requirements.

That’s an important distinction that most users won’t fully understand.

A good start… But not market access clarity

Apple’s update is often framed as a step toward “regulating health apps.” It isn’t.

Apple is not setting new standards, it is surfacing existing ones.

What’s still missing is clarity on:

• What evidence is required for different use cases

• How requirements differ across countries

• What “good” looks like beyond minimum regulatory thresholds

   

For developers, this creates ongoing ambiguity around market entry requirements.

For users, it creates a false sense of certainty.

Why this matters more than ever

Digital health is scaling rapidly. Apps are increasingly:

• Diagnosing conditions

• Monitoring chronic diseases

• Influencing treatment decisions

At the same time, the line between wellness and medical continues to blur.

Apple’s label may help users distinguish between categories, but it doesn’t help them answer the more important question:

“Can I trust this?”

The ORCHA perspective: From transparency to trust

At ORCHA, we’ve long argued that transparency is only the first step.

What’s needed is:

• Independent assessment (like ORCHA Assured)

• Clear evidence standards

• Country-specific compliance mapping

• Ongoing monitoring of quality and safety

Because in digital health, trust isn’t declared, it’s demonstrated.

Final thoughts

Apple’s move is a good one. Anything that nudges the ecosystem toward greater accountability and gives users more information than before has to be a positive shift, however small, but it also reinforces a critical truth:

Badging something as “regulated” is not the same as proving it is safe, effective, or appropriate for the user that it’s being presented to.

For a market as complex, and as high stakes, as digital health, that distinction matters.

Read more about the update here: https://appleinsider.com/articles/26/03/27/apples-app-store-will-show-if-an-app-is-classified-as-a-regulated-medical-device