Events, states and accountable action
Orchestrator
Connects the modules into one flow: validates an event, checks rules, proposes the next step and records human decisions.
Module purpose
Remove gaps between local systems and make the study route observable from data source to task closure.
Status
Public clinical and operational validation results and medical-device registration details have not been published. This module must not be treated as an approved medical device. Human approval remains mandatory for clinical, ethical and regulatory decisions.Public clinical and operational validation results and medical-device registration details have not been published. This module must not be treated as an approved medical device. Human approval remains mandatory for clinical, ethical and regulatory decisions.
Inputs
- Module events and statuses
- Versioned routing rules
- Roles, authority and deadlines
- Human confirmations
How it works
- Validates event source and completeness
- Matches state to a rule
- Creates a task, wait or escalation
- Records transition, rationale and owner
Outputs
- Proposed next action
- Task and deadline
- Escalation or checkpoint
- End-to-end state log
Human checkpoints
- Critical-transition approval
- Resolution of conflicting rules
- Exception closure by an authorised role
Automation boundaries
- Does not make clinical decisions
- Does not bypass authority
- Does not hide routing rationale
Module video
Trialeco Core: reviewable routing
The film explains the module with a synthetic example. It is not evidence of clinical effectiveness, validation, compliance or regulatory approval.
Open the full video series →