Regulation (EU) 2024/1689 classifies AI systems by risk. Medical-device AI is generally treated as 'high-risk' and must meet AI Act requirements (data governance, transparency, human oversight, robustness, post-market monitoring) in addition to MDR/IVDR. The AI Act entered into force on August 1, 2024, with obligations phased in. For AI systems that are safety components of, or are themselves, devices requiring notified body assessment under the MDR or IVDR, high-risk obligations apply from August 2, 2028. The AI Act assessment is integrated into the existing MDR or IVDR conformity assessment, so one notified body can review both, as long as it is designated for the AI Act. Regulation (EU) 2026/1744 amended this timetable in July 2026.

Why it matters

Conformity assessment for medical AI is integrated with the existing Notified Body process. Phased application runs through 2027; manufacturers should align technical documentation now.

Common pitfalls

•Failing to integrate AI Act requirements into technical documentation early will lead to significant delays in market access.
•Assuming that MDR/IVDR compliance alone is sufficient for AI-powered medical devices is a critical error.
•Neglecting to establish robust post-market monitoring for AI systems will result in non-compliance and potential regulatory action.
•Misinterpreting the "high-risk" classification criteria for AI in medical devices can lead to inadequate conformity assessment.
•Overlooking the need for human oversight mechanisms in AI-driven medical devices will result in non-adherence to the Act.

Sources

EU AI Act (Reg. 2024/1689) · EUR-Lex
IMDRF - Software as a Medical Device · IMDRF
MDCG Software Guidance · MDCG
Regulation (EU) 2026/1744: amended AI Act application dates · EUR-Lex

Open full page

Select term B to compare.

Why compare MedTech terms side by side?

MedTech terminology is full of pairs that look interchangeable but carry very different regulatory, clinical, and commercial consequences. Picking the wrong framework, pathway, or standard early in a project can add months to a submission, invalidate clinical evidence, or trigger an audit finding. Side-by-side comparison is the fastest way to surface those differences before they become costly mistakes.

Each comparison on this page pulls from the same vendor-neutral, sourced definitions used throughout the MedTech Terms glossary. You see the one-line summary, the formal definition, why it matters in practice, common pitfalls, and the primary sources (FDA guidance, EU MDR/IVDR articles, ISO/IEC standards, MDCG documents, IMDRF principles) that back each entry. That makes the comparison defensible in regulatory strategy memos, design reviews, and submission narratives.

Common comparison patterns

Regulatory pathway choice - 510(k) vs PMA, 510(k) vs De Novo, Abbreviated vs Special 510(k).
Quality systems - QSR vs ISO 13485, QMSR vs QSR.
Software classification - SaMD vs SiMD, Locked vs adaptive AI.
EU frameworks - MDR vs IVDR, CE Mark vs UKCA.
Cybersecurity artifacts - SPDX vs CycloneDX SBOM, CVE vs CVSS.
Post-market actions - Recall vs field action, Removal vs correction.

How to use this tool

Pick term A and term B from the dropdowns, or click a preset above. The URL updates with both slugs so you can bookmark or share the exact comparison with a colleague, a notified body reviewer, or your regulatory consultant. Click Open full page on either side for the complete entry, including FAQs, related terms, and the full citation list. If you are not sure which term to start with, browse the Categories view or the A-Z index.

MedTech Terms is a vendor-neutral community resource sponsored by Blue Goat Cyber. Definitions are written for educational use and are not legal or regulatory advice.