Compare

    Two terms, side by side

    Pick any two terms to see definitions, context, pitfalls, and sources in parallel.

    Curated comparison tables

    In-depth, attribute-by-attribute tables for the most common MedTech term pairs. Each row is sourced from the linked term pages.

    Software & AI

    Foundation Model (Healthcare)

    In one line
    Large pretrained model adaptable to many downstream clinical tasks via fine-tuning or prompting.
    Definition
    Healthcare foundation models - for medical imaging, pathology, EHR text, multi-modal patient records - are trained on broad datasets and then specialized. They blur traditional boundaries between intended use and raise novel validation questions. Because the same base model can be adapted to many tasks, a clear intended use and task-specific validation remain essential for any device built on one. Manufacturers also need to manage dependencies on third-party models they do not control, including version changes. The EU AI Act includes separate obligations for providers of general-purpose AI models, which apply alongside high-risk requirements for a device built on top of them.
    Why it matters
    FDA, MHRA, and Health Canada have flagged foundation models as a regulatory frontier - neither pure SaMD nor pure platform.
    Common pitfalls
    • •A common misconception is treating a specialized foundation model as a standalone SaMD without considering the regulatory implications of its underlying general-purpose capabilities.
    • •Failing to document the full lifecycle of a foundation model, including its initial pre-training, fine-tuning, and deployment, can lead to compliance issues.
    • •Underestimating the resources required for continuous monitoring and validation of a deployed foundation model's performance in clinical settings is a significant pitfall.
    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

    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.