RBQM vs. RBDM: What’s the Difference, and Why It Matters for Your Data Team

Since the publication of ICH E6(R3), finalized in 2025, the conversation surrounding Risk-Based Quality Management (RBQM) has shifted. Pre-R3, much of the RBQM conversation has focused on applying risk-based approaches to specific areas of trial oversight, such as monitoring and data review. Along with the companion guidance in ICH E8(R1), ICH E6(R3) reinforced quality-by-design and cross-functional risk management, signaling a clear expectation that risk management be embedded into every aspect of how trials are planned, executed, and reviewed. That update has pushed RBQM back to the center of planning conversations, and in doing so, has surfaced a related but distinct term: Risk-Based Data Management, or RBDM. 

If your team has heard RBDM mentioned in a vendor pitch or a conference session and isn’t sure whether it’s a new framework, a rebrand of RBQM, or something else entirely, you’re not alone. Below, I explore Risk-Based Data Management and why it matters to your RBQM strategy. 

A Brief History of RBQM 

Risk-Based Quality Management, RBQM, is a systematic, proactive approach to identifying, assessing, monitoring, and mitigating risks to critical data and processes across a trial. Its predecessor, Risk-Based Monitoring emerged in response to growing trial complexity, rising data volume, and the recognition that uniform, one-size-fits-all oversight couldn’t scale and didn’t concentrate attention where risk actually lived. ICH E6(R2) then formalized that thinking into a broader quality management framework, embedding risk identification and governance into the trial lifecycle. E6(R3) and E8(R1) carried that further, tying risk management explicitly to how trials are designed from the outset. 

Read across those updates, the direction is consistent: risk management is meant to be embedded into planning, execution, and review. 

The cleanest way to distinguish between RBQM and RBDM is to think of it this way: RBQM operates at the level of trial-wide governance, monitoring design, and oversight planning. RBDM operates at the level of data operations, applying that same risk logic to what gets reviewed, how often, and by whom. 

It’s important to make this distinction because, despite broad agreement that not all data deserves equal scrutiny, day-to-day data review at many organizations still runs on largely exhaustive models: Teams apply the same review cadence and depth to all data, regardless of where the actual risk sits.  

Risk-Based Data Management is a strategic, holistic approach to managing clinical trial data that prioritizes what’s critical to quality, compliance, and efficiency. Where RBQM sets the risk strategy for a trial, RBDM is what determines whether that strategy shows up in a reviewer’s queue on a given afternoon. 

If your team only has language for RBQM, risk-based thinking tends to stop at the planning document. Risk tiers get assigned during protocol design and referenced in a monitoring plan, but the connection to actual review behavior — what a data manager prioritizes, tolerates, or escalates — is often reconstructed manually, inconsistently, or not at all. 

RBDM gives that connection a name and a set of expectations. Without that operational layer, teams can be technically correct in saying they practice RBQM while still running 100% review under a different label. For data management teams specifically, understanding the RBQM/RBDM distinction is the difference between inheriting a risk strategy and executing one. 

Building the Operational Layer 

Knowing the difference between RBQM and RBDM is the easy part. Translating this knowledge into a defined RBDM strategy is where most organizations get stuck. 

Download the white paper, Risk-Based Data Management: Bridging RBQM Strategy and Data Execution. The white paper lays out an RBDM Maturity Model across planning, execution and closeout, and oversight, along with a step-by-step guide for putting RBDM into practice. You can find the white paper here.

Vera Pomerantseva

Director of Product Management, RBQM, eClinical Solutions

Vera Pomerantseva is a clinical research and risk management leader with extensive experience in risk-based quality management (RBQM), clinical data analytics, and quality strategy. As Director of Product Management for RBQM at eClinical Solutions, she leads the vision and development of data-driven solutions that help life sciences organizations proactively identify risk, improve trial quality, and drive operational excellence. Vera brings deep industry experience from leadership roles at ZS, Bristol-Myers Squibb, and Novartis, and is widely recognized for her thought leadership in applying risk-based methodologies and quality-by-design principles to clinical development.