Dashboard
Post-discharge follow-up

Demo scenario

A guided click path for showing how a health-system engineering team drafts, governs, invokes, signs off, and audits an AI agent without rebuilding the regulated plumbing.

Begin demo
1

Draft the agent

Open the Agents page, draft the post-discharge follow-up agent from English, and review its tools, schemas, guardrails, and signoff roles.

Start with English draft
2

Inspect the governed spec

Show the versioned definition, declared runtime tools, strict PHI settings, schemas, and nurse/admin signoff policy.

Inspect the demo agent
3

Review a run

Open the synthetic patient-message run, inspect the structured output, tool calls, and approve or reject the signoff state.

Review the awaiting-signoff run
4

Verify auditability

Load the demo hash chain to show tamper-evident audit entries for invoke, tool calls, and awaiting-signoff state.

Verify the audit chain
5

Show tenant isolation

Close with the tenant posture view: usage, isolation boundary, and operational activity are visible to platform admins.

Show tenant posture

Build clinical workflow apps on top of this layer.

TheraSyn can support a full clinical workflow app, but the platform wedge should stay clear: the workflow app is a reference or customer solution built on the governed runtime, not a replacement for the runtime itself.