Monitoring strategy that targets oversight resources to the highest-risk sites, processes, and data based on a documented risk assessment, replacing 100% source data verification.

Definition

Risk-Based Monitoring (RBM) is a clinical trial oversight approach that uses a documented risk assessment to direct monitoring resources to the trial elements (sites, processes, data points) most critical to subject safety and data integrity. Rather than performing 100% source data verification (SDV) at every site, sponsors combine centralized statistical monitoring (off-site analytics on EDC data), targeted on-site monitoring focused on critical data and processes, and remote source data review where feasible. The broader practice, Risk-Based Quality Management (RBQM), extends this approach to all quality oversight activities.

Why it matters

RBM became the default expectation under ICH E6(R2) addendum (2016) and is reinforced in E6(R3) (2023). For device IDE studies, sponsors implementing RBM must produce a documented risk assessment, defined Key Risk Indicators (KRIs) and Quality Tolerance Limits (QTLs), trigger-based monitoring procedures, and centralized monitoring analytics. FDA bioresearch monitoring inspections increasingly evaluate RBM implementation depth.

Common pitfalls

•Declaring RBM without a documented risk assessment, the assessment is the foundation; without it, RBM is just reduced SDV.
•Setting KRIs/QTLs without thresholds for action, KRIs that no one acts on add cost without benefit.
•Cutting on-site visits to zero, RBM redistributes monitoring, it doesn't eliminate it.

Sources

FDA Oversight of Clinical Investigations Guidance · FDA
ICH E6(R3) Good Clinical Practice · ICH
ClinicalTrials.gov · NIH

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.