RBQM Guidance Evolved in ICH E6(R3). Is Technology Keeping Pace?

Over the past decade, Risk-Based Quality Management (RBQM) has become firmly embedded in regulatory guidance. What began as a shift away from uniform oversight under ICH E6(R2) has continued to evolve. ICH E6(R3) reinforces expectations for continuous, risk-based, and data-driven trial oversight—an approach that would be difficult to support through manual processes alone. The ability to operationalize RBQM now depends heavily on the technology used to enable it.

Technological advances in analytics, data integration, and centralized oversight have made RBQM as identified in ICH E6(R3) possible. But not all approaches to RBQM technology are designed to support the new regulatory expectations equally. Which types of solutions are best positioned to support the new regulatory guidance?

In this blog, we examine three common types of RBQM technology—point solutions, traditional clinical systems, and integrated RBQM platforms—and compare how effectively each supports the full RBQM lifecycle.

What ICH E6(R3) Requires in Practice

Before comparing solutions, it’s helpful to translate regulatory guidance into operational terms.

ICH E6(R3) reinforces several expectations that directly impact how RBQM must be executed. This includes:

• Continuous risk management: Risk is revisited throughout the study
• Focus on critical-to-quality factors: Oversight must prioritize what matters most to patient safety and data reliability
• Proportionate oversight: Activities should align with risk, not follow a fixed model
• Use of data and technology: Digital tools, analytics, and diverse data sources are expected to support decision-making

To execute RBQM in this manner requires technology that can aggregate and harmonize data across systems, detect signals in near real time, connect risks to actions, track outcomes, and provide traceability for decisions.

Three Approaches to RBQM Technology

1. Point Solutions: Strong Signal Detection, Limited Continuity

Point solutions have been central to the adoption of RBQM, particularly in areas such as centralized monitoring and statistical analysis. They are typically designed to address specific components of the RBQM process, most often focused on identifying and analyzing risk signals.

Strengths

Point solutions are particularly effective for identifying emerging risks and supporting centralized monitoring activities. They provide strong analytical capabilities, including:

• Advanced analytics and anomaly detection
• Robust support for KRIs, QTLs, and structured risk frameworks
• Increasing use of AI/ML to identify patterns in data

Challenges

Point solutions are often implemented alongside existing systems rather than replacing them. As a result:

• Data integration may be limited
• There may be less emphasis on integrated workflows for risk mitigation and action tracking
• Dependence on integration with external systems may impact speed to value

While point solutions are effective for specific components of RBQM, they may not fully support the end-to-end lifecycle expected in ICH E6(R3).

2. Traditional Clinical Platforms: Broad Capability, Fragmented Execution

Traditional clinical platforms are designed to support multiple aspects of trial execution. Many of these platforms have incorporated RBQM functionality and have RBQM capabilities integrated across existing modules.

Strengths

These systems are favored by organizations looking to extend existing systems rather than introduce new ones, and these platforms offer broad operational support, including:

• Moderate support for centralized monitoring capabilities
• Strong support for risk assessment frameworks aligned with regulatory requirements
• Existing infrastructure supporting multiple clinical trial functions

Challenges

Because RBQM capabilities within these platforms are often distributed across modules or layered onto legacy architectures, this can introduce challenges such as:

• Limited interoperability across systems, with inconsistent data flows
• Monitoring capabilities that are less real-time and dependent on system integration
• Workflow support that exists but lacks continuous, real-time tracking

While these platforms support multiple aspects of RBQM, execution often depends on coordination across systems rather than a single, connected environment.

3. Integrated RBQM Platforms: Enabling Continuous, Data-Driven Oversight

A newer category of RBQM solutions has emerged to address the limitations of fragmented approaches. These platforms are designed to support RBQM across the full trial lifecycle, bringing together risk assessment, centralized monitoring, and review within a more connected environment.

Strengths

Rather than focusing on individual components, these systems aim to enable continuous, data-driven oversight by integrating data, analytics, and workflows. They enable:

• More connected data environments that bring together clinical, operational, and quality data
• Real-time analytics and centralized monitoring to support ongoing risk detection
• Workflow-driven risk management that links signals to mitigation activities

Challenges

• Depending on the system, integration may still be dependent on multiple systems
• Workflow capabilities differ across platforms, especially in terms of automation and tracking

By connecting data, analytics, and workflows, integrated RBQM platforms are more closely aligned with the move toward continuous, risk-based oversight. While execution can still vary across solutions, this category is generally better positioned to support the lifecycle-based approach emphasized in ICH E6(R3).

When selecting an RBQM system, key considerations include:

• Data integration: The ability to bring together clinical, operational, and quality data into a unified view
• Lifecycle connectivity: Clear links between risk assessment, monitoring, mitigation, and review
• Real-time oversight: Continuous visibility into risk signals, rather than periodic or retrospective review
• Workflow alignment: The ability to connect identified risks directly to mitigation actions and track progress

Because ICH E6(R3) reinforces the need for RBQM to function as an ongoing, connected process, integrated RBQM platforms are best positioned to support these expectations, particularly where organizations are looking to operationalize RBQM across the full trial lifecycle.

View the RBQM solution comparison chart to see how each approach performs across key capabilities, and where elluminate RBQM stands out against the competition.