An example of clinical trial operations as a governed process: agents do the 6 steps, and a person signs the gate before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
minctrl.process/v1 · hash 11e738384c1d…ea1b
Trial operations — eligibility screening, source-data verification, reg-doc assembly — are slow, manual and Part 11 / GCP-validated, gating the cost and speed of every study. Patients are screened and matched, data abstracted and deviations flagged, and reg packages assembled straight-through; the PI / medical monitor signs eligibility and safety decisions.
A minctrl.process/v1 document: the graph and the hash of the process it becomes.
Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.
Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.
Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.
Start from this example. Import the file in Processes, connect your own systems, and adapt the steps on the canvas. Agents run the reversible steps; every irreversible step waits at a gate for the role you choose. The example has 6 steps and 1 gate; you can change any of them.
Every run start, signature and change to the process is written to a hash-chained audit log your auditor can verify and export. The example is modelled on GCP; whether your process meets it is a decision for your compliance team.
No. Minctrl will not make a process runnable while an irreversible step can be reached without a human gate, and one person cannot sign two gates of the same run.