Skip to content
OpenCorvus

Inspect the team before use

Active database publication

Clinical Trial Operations

Site readiness, participant-flow and conduct, data quality and monitoring, and safety/TMF/closeout evidence joined into a bounded clinical-trial operations review.

Install in OpenCorvusDownload this exact revisionTrust model

Opens the installed OpenCorvus desktop app. The client re-downloads and re-verifies this exact revision, then asks you for an install scope. No desktop app yet? Install OpenCorvus first

Bound execution graph

Workflow and handoffs

The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.

Bound revision · 1 workflows · 5 nodes · 5 Agents
Bound revisiond6700629
01Clinical Trial Operations Review5 nodes
  1. 01trial-startup-site-readiness-analystMaps approvals, essential documents, roles, training, delegation, facilities, systems, and activation dependencies.root
  2. 02trial-enrollment-conduct-analystReconciles participant-flow denominators, visit-window facts, discontinuations, and deviation evidence.root
  3. 03trial-data-quality-monitoring-analystMaps critical-to-quality risks, queries, missingness, reconciliation, and monitoring evidence.root
  4. 04trial-safety-tmf-closeout-analystMaps safety routing/reconciliation and TMF/closeout completeness evidence.root
  5. 05clinical-trial-operations-review-ownerJoins all branches into versioned issues, dependencies, escalation, and qualified approval gates.← trial-data-quality-monitoring-analyst + trial-enrollment-conduct-analyst + trial-safety-tmf-closeout-analyst + trial-startup-site-readiness-analyst
Evidence output1

Intended scope

Use for evidence-led clinical-trial operations review without participant, medical, regulatory, or release authority.

  • Product pillarswork
  • Agent roster5 declared roles
  • Declared workflows1 complete responsibility and dependency graphs
  • Full capability projection1 Skills · 3 tools · 0 MCP refs

Walkthrough pinned revision

Role and dependency walkthrough

This workflow explanation is pinned to the current package digest. It is not a running Agent session, timer, or generated language-model output. Real execution occurs in the OpenCorvus client.

builtin/clinical-trial-operations@2026.08.13.1package sha256:d6700629160bf967ccd3fd6276b393114cbf1edf082fbc09a8f9a3bde290ce3e

A node becomes schedulable only after its depends_on evidence is terminal. This page explains that contract and does not advance runtime state.

clinical-trial-operations-review

Clinical Trial Operations Review

  1. 01trial-startup-site-readiness-analystdepends_on: []
  2. 02trial-enrollment-conduct-analystdepends_on: []
  3. 03trial-data-quality-monitoring-analystdepends_on: []
  4. 04trial-safety-tmf-closeout-analystdepends_on: []
  5. 05clinical-trial-operations-review-ownerdepends_on: trial-data-quality-monitoring-analyst, trial-enrollment-conduct-analyst, trial-safety-tmf-closeout-analyst, trial-startup-site-readiness-analyst

Install handoff boundary

The OpenCorvus client owns the real scope choice when a later import is performed. This page only explains project and global behavior and does not submit an install itself.

The client requires an explicit scope

Project scopeApplies only inside the current project; the same package ID overrides a global installation.
User-global scopeAvailable to the current user, but never silently overrides a project installation.

The public page hands over one exact revision, or completes a signed bundle download. It never batch-installs or activates a team. The scope explanation describes client responsibility; it is not a web form that can be submitted.