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.

    Quality & Risk

    Risk Management

    In one line
    The lifecycle process defined by ISO 14971 for identifying, analyzing, evaluating, controlling, and monitoring risks associated with a medical device throughout its life cycle.
    Definition
    Risk management, as codified in ISO 14971:2019, Application of risk management to medical devices, is a systematic process manufacturers apply throughout a device's entire life cycle. The process includes risk analysis (identifying hazards, hazardous situations, and estimating associated risk), risk evaluation (comparing estimated risk against defined acceptability criteria), risk control (implementing measures such as inherent safety by design, protective measures, and information for safety, then verifying their effectiveness and evaluating any residual and newly introduced risks), overall residual risk evaluation and benefit-risk analysis, and collection and review of production and post-production information to confirm the risk management file remains valid. The output is a risk management file that a manufacturer must maintain and update throughout the device's commercial life.
    Why it matters
    Risk management is not a one-time design activity; ISO 14971 explicitly requires manufacturers to establish a system for actively collecting and reviewing production and post-production information (complaints, field data, literature, PMS/vigilance data) and feeding it back into the risk management file. Under MDR Article 10(2) and Annex I Section 3, and the equivalent IVDR provisions, risk management is a mandatory GSPR obligation, not merely good practice, and its output is reviewed by notified bodies as part of technical documentation assessment.
    Common pitfalls
    • •Treating risk management as a design-phase-only activity and failing to actively update the risk management file with post-market surveillance data.
    • •Setting risk acceptability criteria after the fact to justify an already-designed device, rather than defining criteria upfront per the ISO 14971 process.
    • •Conflating risk management with usability engineering or software lifecycle processes instead of properly interfacing them as ISO 14971, IEC 62366-1, and IEC 62304 each require.
    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.