Why Visual Verification?

Case Studies

The Problem: On the one hand we’ve got statistics. On the other hand, we’ve got human lives. Because of the latter, our hearts tend to have zero tolerance for errors in clinical trial data. How do we find the right level of risk and quality control (QC)?

Let’s tempt the wrath of risk assessors everywhere and look at the issue. What’s the real purpose of QC? To be sure, it is NOT to achieve perfection. On that most of us can wholeheartedly agree, including the FDA.

The question is how to decide how much and which types of QC will help ensure the acceptable error margins we’ve set for ourselves.

That’s a whole other kettle of fish.

The Solution: What we strive to produce is a quality management system that works as a whole. Over time, we add and subtract QC tasks until the right balance emerges—one that satisfies both the risk assessment model and the passion for correct data.

At Veracity Logic, one of the steps in our total QC package is a little bit of bother known as “visual verify”. We’ve reached down into the data management archives, pulled it out, dusted it off, and propped it up on the mantel, remembering a time when it was axiomatic that any single-entry act in the double entry world of quality control had to be independently reviewed. One can almost hear the wooden wagon wheels creaking….

Every data change (DCR) and configuration change (CCR) we’re asked to make in an active IRT project system is executed by a qualified project team member and then subjected to an independent visual confirmation by another qualified member of the team. Successful verification is signed off by the reviewer and becomes part of the project record. Only then is the DCR/CCR regarded as complete.

One almost wants to hum the theme song from ‘Somewhere In Time’…

Audit Trail and Access

Case Studies


Tom Smith, a Study Coordinator at Site A in your clinical study, retired from the project three months ago. Due to a communication snafu, your clinical staff forgot to remove Tom’s name from the roster of active system users of the project’s IRT system. Two months later, your company’s QA group discovers this fact during their bi-annual production audit of the IRT vendor. From a regulatory perspective (not that they don’t trust Tom, honest!), they have to be concerned about the potential for unauthorized data changes…and about the fact that someone no longer assigned to the project could continue to view production data. How to quickly put all issues and concerns to bed?

Veracity Logic’s IRT provides access to its robust audit trail in two ways: interactively, at the level of each item, and via a ‘global’ audit trail which maintains the cumulative record of all data changes that have occurred on a given project. The VLIRT® audit trail captures the old and new data, timestamp and date of change, user making the change, and a justification (required) for the change. A quick query of the global audit trail will reveal any data changes made by Tom Smith subsequent to his date of departure. The system also captures the last login date/time for Tom. QA can rest easy when it sees that Tom last logged into the system prior to his departure date.

Want to hear about other ways Veracity Logic’s IRT can help solve project problems?

Can Your IRT System Help You Manage Protocol Deviations?

Newsletter Archive

Your study has been suffering from slow enrollment. An excellent candidate, medically speaking, walks into Site 101 but there’s one problem: The minimum enrollment age for the clinical trial is 18. The age of the new potential candidate is 17 years, eight months. The Study Coordinator at the Site not only needs a quick decision, but one that protects the integrity of the protocol at the same time. What to do?

Solution: Authorization Codes
Veracity Logic’s IRT system provides Authorization Codes for just such occasions. Site users contact designated personnel to obtain a quick field decision as to whether the protocol deviation is advisable for the study. Authorization codes are held within the IRT system; available codes are easily accessed by the designated decision makers. A code documenting permission to register the subject is provided to the Site for entry into the IRT database. And all of this can be done within minutes! The fact that a protocol deviation has occurred, and the vital specifics of that deviation, can be easily tracked by Biostatisticians using Veracity Logic’s IRT.

Authorization codes can also be used to document authorized unblinding of subject treatment data—wherever there is an intersection between the need for a speedy decision and the need for protection of protocol integrity.

This is just one of the many ways Veracity Logic’s IRT meets real-life scenarios with real-life solutions.