Trust your clinical research data? The new SAS Viya Clinical Acceleration Repository (CAR).

Why Trust?

The one issue that persist with any manipulated data output is trust.

In an interesting article I read recently, published by Caltech Science Exchange, the question of Trust came in in context of AI. (Can we trust artificial intelligence)

According to this author, one of the big impactful events influencing trust is Data and amongst other issues, the Bias it contains. And their fix, make sure every data set used to answer any question is scrutinized to determine its ‘motivation, composition, collection process, recommended uses and so on’

So What?

Essentially, moving back into the safety of single version of the data truth will show us the picture of whence our intelligence is derived.

- Results are easily manipulated if there is no single version of data for everyone.
- Results can be skewed where there is no oversight, no process, no checks and balances to ensure auditability and traceability.

In other words, if you want trust, we need to build a world where even under data torture and/or duress, this singular data version will provide repeatable, reliable ‘truths’ if the same questions are asked by whoever.

Enter SAS Clinical Acceleration Repository (CAR).

SAS CAR lets you easily integrate large and diverse data sets such as electronic data capture (EDC) systems, in-house clinical data management systems (CDMS), labs and contract research organizations (CROs).

The CAR Solution from SAS is helping you trust your version of the truth. Some of its primary features includes but are not limited to:

Centralized global repository. It consolidates clinical information into a single, secure, centralized global repository
Data Tracing. It traces data pedigree back to the origin.
Data Security.
- Defines data check-in/check-out processes.
- Maintains audit trails (see number 4 below).
- Provide you with Electronic Signatures, so the individuals that touch data must make themselves known.
- Supports versioning; and allows for role-based privileges (I’ll show how easy this is to set up a bit later).
Audit Trails. Let’s you readily determine what audit changes were made, when and by whom for all the content stored in the repository.
Secure Logins. Controls all information and research team access via secure logins.
Regulatory Compliance. Enables compliance with the FDA’s Title 21 CFT part 11 requirements, as well as other industry regulations.
CDISC compliance. Complies with CDISC and its initiatives – dataset-JSON and CDISC CORE.
Medical Device Reporting. Supports integration with MDR.