CONTINUOUS REAL TIME VALIDATION

EXPLAINED

VIEW DEMO

Regulatory Approved Process

QuBAS uses a unique system of CrtV which means no user validation process is required, even for GxP work. Each analysis report is created with its own full audit trail and real time validation record.

CrtV was originally developed by Quantics for in house use for GxP analysis. The MHRA inspection auditor described the process as “innovative and elegant” and fully accepted that traditional IQ, OQ, PQ is not required with this process.

Results are 100% QCd by QuBAS using Diverse Self Checking Pair Programing (DSCPP).

Traditional Validation

The process has to be repeated for every computer, upgrade and any change in other software / hardware.

Traditional Validation

Serious Flaws

The Traditional Process introduces some serious flaws

• Checks software on data supplied by manufacturer + some user-defined test sets
(“Answers” usually produced by the same software)

• Qualification performed at instillation – and intermittently thereafter
(Does not check it works with every data set in daily use)

• Does not check maths (apart from development)

• Assumes stable between validations if no changes to system

• Calculations may be system dependent
(Keep old software and hardware)

• Time consuming, costly and cumbersome
(Significant QA & QC input for every analysis)

QuBAS CtrV Process

The QuBAS Continuous real time Validation (CrtV) process uses Diverse Self-Checking Pair Programming (DSCPP)

QuBAS Validation Process
validation-qubas

Hidden within QuBAS, the imported data is analysed by 2 completely independent programs.

Independently written during development by two different statisticians, in different programming languages,  the results are compared, again using a DSCPP process and only if all agree is a report produced.

(As well as the calculations, QuBAS actually uses DSCPP for the audit trail, user inputs and report generation from the results.)

The process validates that Engine A is installed, performing and operating correctly (by comparing with Engine B) and vice versa. It does this using the actual data-set being analysed every time. With CrtV, validation is completed with every analysis, so there is no need for IQ, OQ or PQ because QuBAS takes care of this every time.