Governance Workbench

Start without an integration#

Governance Workbench is the public no-code environment for exploring supported policy behavior. Guided scenarios let you compare a fixed teaching input with its governed handling. Custom JSON lets you inspect supported evaluation using synthetic or non-sensitive content.

The canonical route is /workbench. Older Sandbox and playground links redirect there. The name change does not expand runtime scope or convert public demonstration activity into a private customer workspace.

Read the result in order#

Identify the scenario and mode, selected policy, findings, engine decision and final outcome. Compare the raw diagnostic example with the governed output, then inspect the corresponding evidence. Expected fixture labels teach a scenario; the observed engine and enforcement result determine what actually happened.

A transformed result should show the supported transformed artifact. A blocked or held result should not expose the protected output as though it were released. A raw fixture diagnostic view exists for the documented teaching scope; it does not authorize raw production diagnostics.

Recognize simulated connector behavior#

The Epic/FHIR demonstration includes explicitly SIMULATED behavior. Simulated adapters make no provider, token or FHIR calls. Override draft, approval and continuation views are teaching exercises, not real clinical approvals or production release authority.

Separately configured real Epic sandbox read/search is a distinct integration requiring dedicated authorization and credentials. The Workbench UI must not imply that selecting a scenario establishes that integration.

Use telemetry within its publication scope#

Governance Telemetry shows allowed demonstration activity with its source and period. Missing or stale data remains visible as such. A signed-in visitor's private history is not merged into the public feed. For an application-level technical evaluation, move to Developer Evaluation and verify the private evidence path.