Preview only — Changes in this demo stay in this browser until you sign in to a workspace.

Riverside Health System

72% ready

4 reviews queued

2 launch candidates

Admin

Step 2 of 2

Page guide

Approval settings walkthrough

See how the final approval gates are defined and maintained for all AI tools.

Your progress2/2

Why it matters

See how routing and approval rules are configured so governance stays consistent as you scale.

A quick guide to this page

See that approval criteria are standardized instead of ad hoc.
Review which gates are required versus advisory.
Connect these settings back to the approval record to see how policy becomes execution.

Follow the tour at your pace

Routing settings walkthrough

2Approval Settings

Approval settings walkthrough

Here

Approval

Approval Process Settings

Define the approval gates every AI tool must clear before final approval. Reviewers execute these gates on each tool's approval record.

Process definition

Gates applied to every AI tool that reaches approval.

Blocking gates

Required gates must be cleared before a final decision is allowed.

Tracked only

Advisory gates are tracked but do not block approval.

Edit the process

Loading approval gates…

Gate	Owner	What reviewers confirm
Gate 1 title	Gate 1 owner	Clinical Safety, Privacy, and IT Security each have required items that must be closed before final approval.
Gate 2 title	Gate 2 owner	SOC 2 has been received; HITRUST posture, subprocessor access, and PHI retention evidence remain under review.
Gate 3 title	Gate 3 owner	The vendor must confirm that model providers and infrastructure subprocessors are covered by BAA or equivalent terms.
Gate 4 title	Gate 4 owner	Training plan, pilot-unit launch plan, escalation workflow, and context-management handoff are drafted.
Gate 5 title	Gate 5 owner	Each monitoring commitment is tied to an approval KPI, with a first-month cadence and re-review triggers.