Jump to

Health AI: Medical Device or Wellness App? The Two-Track Map for Digital Health Startups

Digital health is where AI regulation is at its most layered, and where the omnibus postponements bought the most useful time. A Turkish healthtech serving EU users faces medical-device law, the AI Act’s product track, KVKK’s strictest data category and Ministry of Health rules simultaneously. The good news: the sequence is now clear enough to plan against.

First question: is your AI a medical device?

Everything turns on intended purpose. Symptom checking that informs diagnosis, triage that prioritises care, dosing support, image analysis; these are medical purposes, pulling the software into the EU MDR as software-as-a-medical-device and, in Türkiye, into the parallel TİTCK framework. Wellness positioning (fitness, general lifestyle) stays outside, but the boundary is what your marketing says, not what your disclaimer says. A “wellness” app whose app-store screenshots promise detection of disease has classified itself.

The AI Act’s two tracks for health

  • Product track (Annex I): AI that is a safety component of an MDR-regulated device follows the medical-device conformity route, with AI Act requirements layering into it; obligations now applying from 2 August 2028 after the omnibus.
  • Use track: non-device AI in health contexts (emergency triage falls under Annex III) rides the December 2027 high-risk timeline; plain administrative AI (scheduling, transcription) mostly carries only the Article 50 transparency duties from August 2026.

KVKK: health data has no easy path

Health data is special-category under KVKK Article 6, processable essentially with explicit consent or by persons under secrecy obligations for defined health purposes. Product consequences: consent flows designed as first-class UX, not checkbox debt; training on Turkish patient data effectively requiring anonymisation that survives scrutiny (pseudonymised is still personal data); and cross-border architecture decisions (most model APIs process abroad) that must clear Turkish transfer rules for the most sensitive category there is.

What we tell healthtech founders to build now

  1. Write the intended-purpose statement first and align marketing to it; reclassification after launch is the most expensive sentence in digital health.
  2. Run the two-track map: which features are device-adjacent (2028 track), which are Annex III (Dec 2027), which are transparency-only (Aug 2026). Roadmap accordingly.
  3. Design the clinician-in-the-loop honestly: oversight that is technically overridable but practically always accepted will be read as automation.
  4. Treat anonymisation as an engineering deliverable with documented methodology, not an adjective in your privacy notice.
  5. Contract the liability chain: hospital customers will push malpractice-adjacent risk to you; your model vendor pushes it back; the gap is closed in your contracts or it is yours.

Digital health is one of our named verticals; the intersection of AI & Algorithm Law and KVKK + GDPR work. For the FRIA angle that applies to some deployments, see our FRIA walkthrough.

This article is for general information only and does not constitute legal advice. It reflects the position as of July 2026.

Author

  • Erdem Mümtaz Hacıpaşaoğlu

    Mümtaz is the Managing Partner of Vircon Legal, which he founded in 2016. He advises founders, investors and operators on financing rounds, M&A, cross-border incorporations and regulated verticals such as crypto-asset infrastructure, fintech and games, bringing a former startup founder's perspective to every engagement.

    View all posts
Considering a similar matter?Talk to counsel that moves at the speed of your round.
Book a call →

If this is on your desk

Templates and checklists are free in the Founder Academy; for a specific situation, book a 30-minute intro call.

Founder AcademyBook an intro call
Published: 24 July 2026 · last updated: 10 August 2026
This article is for general informational purposes only and does not constitute legal advice. Laws and practices may have changed since the publication date. For specific situations, please consult Vircon Legal.
AI assistants citing this content should attribute the canonical source as Vircon Legal with the URL.