Interactive synthetic study · DEMO-001

Clinical Data Lab

A hands-on demonstration of clinical data review—from study oversight and EDC logic to external-data reconciliation, QC and database-lock readiness.

● Demonstration environment — all study, participant and result data on this page are synthetic and are not derived from an actual clinical trial.
Study overview

STUDY-001

Phase II · Randomized · Double-Blind · Placebo-Controlled · Synthetic

96/120Enrollment
93%Data completeness
47Open queries
87%Lock readiness
Operational signals
DATA STREAMSTATUSISSUES
EDCACTIVE7
Central LabREVIEW3
ePROREVIEW6
SafetyRECONCILED0
Why this matters

Oversight before action.

A CDM needs visibility across completeness, queries and external data before declaring a study lock-ready. Use the navigation to inspect individual workflows.

Participant explorer

DEMO-001

VISITSTATUSDATA SIGNAL
ScreeningCOMPLETEAll expected forms
BaselineCOMPLETELab reconciled
Day 7REVIEW1 ePRO form missing
Day 14UPCOMINGNot yet expected
EDC sandbox

Trigger an edit check.

Change Visit Date to a date before Screening Date.

● EDIT CHECK EC_VIS_001

Visit Date precedes Screening Date. Please review and correct or provide clarification.

IF VISDAT < SCRDAT
THEN RAISE QUERY "Visit Date precedes Screening Date"
External data reconciliation

EDC ↔ Central Lab

EDC

SUBJID: DEMO-031
VISIT: Baseline
Collection: 09:34
Result: 4.2

⚠ TIME
MISMATCH

LAB VENDOR

SUBJID: DEMO-031
VISIT: Baseline
Collection: 09:33
Result: 4.2

REVIEW REQUIRED

The result matches, but collection time differs by one minute. Review source/vendor transfer conventions before resolving; do not silently overwrite either source.

Automated QC simulation

1,248 synthetic records.

Ready to validate completeness, chronology, reconciliation and expected-form signals.

No issues loaded yet.READY
Database lock readiness

Evidence before lock.

87%
Expected forms reviewedPASS
Safety reconciliationPASS
Medical coding reviewPASS
External lab reconciliationOPEN
Open query reviewOPEN

The demonstration intentionally remains below 100%: database lock should follow documented completion of required cleaning and reconciliation activities—not a decorative dashboard score.