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

    Good Machine Learning Practice(GMLP)

    In one line
    Guiding principles for the development of AI/ML-enabled medical devices.
    Definition
    Good Machine Learning Practice (GMLP) describes guiding principles - jointly issued by FDA, Health Canada, and the UK MHRA - for developing AI/ML-enabled medical devices that are safe, effective, and high-quality. The 10 principles, published in October 2021, cover multidisciplinary expertise across the lifecycle, good software engineering and security, representative data, independent training and test sets, a focus on the human-AI team, clear user information and monitoring of deployed models. The same three regulators later published related principles on PCCPs and transparency.
    Why it matters
    GMLP principles inform FDA review expectations, including data management, model validation, and human-AI team performance.
    Common pitfalls
    • •A common pitfall is failing to establish a robust data management plan that addresses data quality, integrity, and representativeness, potentially leading to biased or inaccurate model performance.
    • •Misinterpreting GMLP as a static checklist rather than a set of guiding principles can lead to superficial compliance without true assurance of device safety and effectiveness.
    • •Underestimating the importance of real-world performance monitoring and continuous learning for adaptive AI/ML models can result in undetected performance degradation over time.
    • •Neglecting to involve multi-disciplinary teams including clinicians, data scientists, and regulatory experts throughout the device development process can lead to overlooked risks and inefficiencies.
    • •Failing to adequately document the rationale for model choices, data curation, and validation strategies can hinder regulatory review and post-market surveillance.
    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.