Sites Active
6 sites
Clinical sites open and enrolling across Phase II and III cohorts
▲ +2 added this quarter
Power BI · Life Sciences
Clinical Trial Enrollment Dashboard
Patient enrollment, site performance, and safety signals -- in one GCP-compliant Power BI dashboard for multi-site trials.
Built for clinical operations teams, CROs, and biotech sponsors running Phase II and III trials who need real-time enrollment tracking, screen fail root-cause analysis, and protocol deviation monitoring across all sites.
Powered by Power BI, connected to EDC systems (Medidata Rave, Veeva Vault CTMS, Oracle Clinical), GCP-compliant data access.
Trusted by teams across 15+ countries
100+
Clients Served
300+
Dashboards Delivered
50,000+
Hours Saved
5.0★
Rating · 15 Reviews
Trusted by teams at
Audience
Who This Dashboard Is For
Ideal For
- CROs managing multi-site Phase II and Phase III trials with enrollment targets and weekly site calls
- Biotech and pharma sponsors who need real-time enrollment visibility without waiting for CRO weekly reports
- Clinical data managers responsible for EDC data quality, protocol deviations, and query resolution
- Medical monitors tracking adverse event distribution and severity across all sites in real time
- Regulatory affairs and clinical operations leadership reviewing trial progress for data cutoff planning
Not Ideal For
- Phase I first-in-human trials -- the multi-site enrollment funnel and site comparison design is optimized for Phase II/III
- Sponsors without EDC systems -- a minimum electronic data capture foundation is required
- Pure safety database reporting -- this dashboard focuses on enrollment and operational metrics, not full pharmacovigilance
By the numbers
Trial KPIs That Drive Enrollment Decisions
Four indicators every clinical operations manager and CRO tracks weekly -- pulled automatically from your EDC and CTMS and updated each morning before the site management call.
Patients Enrolled
859
Total patients enrolled and randomized across all active sites and phases
▲ +83 vs prev month
Screen Fail Rate
13.1%
Percentage of screened patients who did not meet eligibility criteria
▲ -1.2 pts QoQ
Protocol Deviations
12 open
Open protocol deviations across all sites -- reviewed by medical monitor weekly
▲ Within threshold
The problem we solved
From Disconnected EDC Exports to a Real-Time Trial Command Center
Clinical operations teams at Austin-area CROs and biotech sponsors are managing multi-site trials with enrollment data living in Medidata Rave, site visit reports in SharePoint, and adverse event logs in a separate safety database -- with no unified view of trial health.
The challenge
A Phase III oncology trial with six sites across Texas and the Northeast was reconciling weekly enrollment numbers from Medidata Rave EDC exports, screen fail logs from site coordinators in Excel, and protocol deviation reports from the medical monitor in a Word document. The sponsor's clinical operations team spent 6 hours before every data review meeting reconciling numbers that were 3-5 days stale by the time they arrived.
- Medidata Rave EDC reported enrollment at patient level; CTMS tracked site-level targets -- no automatic comparison
- Screen fail root cause data lived in individual site coordinator spreadsheets, not the EDC
- Protocol deviation counts differed between the CRO's tracking sheet and the sponsor's quality system
- Adverse event severity was tracked in a separate safety database with no connection to enrollment data
Our approach
We built a Power BI semantic model that ingests Medidata Rave EDC patient data (via REST API), CTMS site targets, and the safety database AE extract. All three sources are joined on Subject ID and Site ID, giving one row per patient with enrollment status, screen fail reason, deviations, and AE severity visible on the same canvas.
- Medidata Rave API (dataset-based extract) used for patient-level enrollment -- no EDC query builder required
- CTMS site target data loaded via scheduled Excel export until API access was provisioned
- Screen fail root cause mapped from EDC entry field to a standardized taxonomy (Eligibility / Withdrawal / Other)
- Protocol deviation severity (Major / Minor / Administrative) classified per ICH E6 R2 definitions in the semantic model
What we achieved
Enrollment dashboard updated daily at 6 AM before morning site management calls
Data review meeting prep time reduced from 6 hours to 45 minutes
Screen fail rate by site and eligibility criterion identified two sites with protocol misunderstanding within 3 weeks
Protocol deviation trending caught a site with rising minor deviations before it triggered a CAPA
Sponsor medical monitor now reviews AE severity distribution weekly -- without requesting a manual safety report
Results verifiedRead full case study
FAQ
Common Questions
Questions we hear from clinical operations teams and CROs before starting a trial analytics engagement.
We connect to Medidata Rave (via dataset-based REST API), Veeva Vault CTMS, Oracle Clinical, and OpenClinica. For sponsors using SAS-format data exports (CDISC CDASH/SDTM), we ingest via scheduled dataset drops to Azure Blob Storage. CTMS integrations include Veeva Vault eTMF, Parexel Informatics, and SharePoint-based site tracking workbooks. The exact connector set is confirmed during scoping and depends on your existing system landscape.
From Lets Viz
Ready to Unify Your Trial Enrollment Data?
Most clinical operations teams are 10-14 business days away from a real-time trial command center. Book a free scoping call and we will confirm your EDC system, CTMS, and safety data sources.
NDA-safe · No obligation · Clear delivery timeline