Module guide

Compliance

Governed operational lanes for consent, adverse events, sample accountability, and evidence-chain review.

2026-07-20Compliance operations/compliance

Runtime availability

Available in the customer workspace with organization-scoped ledgers and export actions.

Who uses this module

compliancemedicaladministratorsmanagers

What users can do

  • Review consent, adverse-event, and sample queues from one workspace.
  • Inspect SLA posture, evidence-chain entries, and escalation state.
  • Export governed registers for the active organization.

Access and approval limits

  • Each domain keeps its own review state and urgency; do not assume one queue closes another.
  • Exports stay organization-scoped and should be handled inside the granted lane.
  • Field capture shortcuts still point back to governed capture paths instead of bypassing compliance review.

Key workflows

These workflows describe how the visible customer workspace is intended to be used.

Resolve a regulated queue item

Review the queue item, confirm evidence, and close or escalate according to the domain state.

  1. 1Open Compliance in the active organization.
  2. 2Select the consent, adverse-event, or sample record that needs work.
  3. 3Review evidence-chain, state, and export needs before resolving the item.

Core concepts

Evidence chain

Evidence chain entries provide a visible audit trail for compliance events and decisions.

Reference

Covered screen

`/compliance`

Troubleshooting

A compliance record cannot be resolved.

  • Review the visible status and whether required evidence is still missing.
  • Check whether another queue, such as medical follow-up, is still open.

Escalate with the record ID, domain, and current visible status.

Connected modules

These areas usually carry the next action, source record, or downstream evidence.

Compliance | FieldOrchestrator