Europe's AI Act and MDR Collide, and MedTech Wants a Rewrite

Two regimes, one product

European life sciences companies building AI-enabled devices are now answering to two regulatory systems that were never designed to sit on top of each other. MDR and IVDR set the safety and performance bar for the device itself. The EU AI Act layers a separate risk-classification and conformity regime on top of any AI component. The MedTech sector is now actively lobbying to revise how the AI Act’s Digital Omnibus provisions and MDR interact, arguing the current stack is unworkable in practice healthcare.digital.

That is not a technical footnote. It is a structural problem for any compliance function trying to plan a CE-marking timeline, because two agencies, two documentation trails, and two definitions of “high risk” now apply to the same software.

Why the industry is pushing back now

The stated concern driving the lobbying effort is migration risk. Industry groups are warning that if the overlapping requirements stay this heavy, AI-enabled device development moves to the US or Asia instead of Europe, and EU regulatory bodies are reportedly accelerating some form of EU-level response to head that off healthcare.digital.

That is a familiar pattern in EU tech regulation. Industry pressure plus a credible exit threat tends to produce either a genuine simplification or a delay dressed up as one. Compliance leaders have seen this movie before with GDPR implementation timelines and with the AI Act’s own phased rollout. The lesson each time has been the same: the underlying risk logic rarely softens as much as the lobbying implies, even when deadlines slip.

What this means for the compliance calendar

For a regulated buyer building or licensing AI diagnostics, imaging tools, or clinical decision support in Europe, the practical decision is not whether to wait for the Digital Omnibus revision. It is whether to design a compliance architecture now that satisfies the stricter of the two current regimes, so that whatever the revision produces is a simplification of your existing documentation rather than a scramble to backfill it.

That means treating MDR technical files and AI Act conformity assessments as one integrated evidence set from the start, mapped to a single risk classification logic even if the frameworks formally require two. It means version-controlling model changes the way MDR already requires you to version-control device changes, so an AI Act audit and an MDR audit can draw from the same source of truth. And it means building this into ISO 42001-aligned governance now, since that standard is increasingly the common language auditors on both sides of the Atlantic are converging toward.

The bet regulators are making

Brussels is betting it can loosen the stack enough to keep AI development onshore without lowering the actual safety bar. That is a narrow needle to thread, and the timeline for threading it is not yet public. Building your compliance program to the current, harder combination is the only version of this bet that pays off no matter which way the revision lands.

---

Board record

This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.

Seat	Reviewer	Finding
Chair · Editorial Judgment	Claude	cleared. The core argument—that dual MDR/AI Act compliance creates structural problems and that building to the stricter standard hedges regulatory risk—is coherent and logically sound, but the claim that ‘the
Source & Claim Verification	Qwen · local	cleared. All factual claims are supported by citations, but the article could benefit from more diverse sources to strengthen the claims.
Regulatory & Framework Fidelity	Mistral	cleared. The briefing accurately reflects the regulatory tension between the EU AI Act and MDR/IVDR but lacks explicit cross-referencing to specific clauses in ISO 42001, FDA guidelines, or the AI Act’s risk-c
Technical Accuracy	Llama	cleared. The article accurately describes the regulatory complexities arising from the overlap between the EU AI Act and MDR for AI-enabled medical devices, and provides practical advice for compliance.
Bias, Balance & Hype Control	Gemini	cleared. The briefing effectively identifies and addresses industry lobbying efforts and potential vendor hype by framing them within a historical context of regulatory negotiations and emphasizing the need fo
Novelty & Non-Duplication	Grok	held. The briefing largely repackages one secondary healthcare.digital roundup on long-known AI Act–MDR overlap and familiar industry-lobbying dynamics, adding only evergreen compliance advice rather than a
Validation	DeepSeek	cleared. The central claim that the MedTech sector is actively lobbying for a revision of the overlapping AI Act and MDR regimes is validated by the cited source, which reports on industry warnings and a poten

Sources cited: 11. Validation challenges: 0. Review cost: about $0.04. Learn how these briefings are written and verified.