Guided demo — ~7 minutes
Demo Health System · A suggested path through the Surgical Intelligence Suite's three modules: descriptive → diagnostic → predictive → prescriptive → action, with data-trust and governance throughout.
Say: Frame it as a platform, not a point tool: three operational modules — exam rooms, OR placement & margin, and demand & workforce — on one shared spine.
Do: Show the three module cards with headline value, plus the suite-wide approved-value banner.
Say: Lead with value: recoverable capacity in dollars, utilization vs target, and the forecast for the next two weeks.
Do: Point out the $/yr recoverable, the weekly trend, and the 'clinics at risk next week' forecast.
Say: Drill into where utilization is leaking, then explain *why* — late starts, no-shows, turnover, template gaps — each with a recommended action.
Do: Open a chronically under-used clinic; on Diagnostics, click 'Propose action' to send it to the approval queue.
Say: Same spine, new use case — the OR, where idle minutes are the most expensive in the building. Headline is contribution margin, not visits.
Do: Use the header module switcher → Surgical Placement. Show margin by case type, then run a 'Cut OR turnover' scenario and Propose action.
Say: Now look forward: forecast surgical demand and ask whether we're *staffed* to meet it — surgeons by line, anesthesia, OR nursing.
Do: Switch to Demand & Workforce. Show coverage by role + the FTE gap; run 'Add staff' and a 'Demand surge' stress test.
Say: The platform continuously watches its own inputs — source freshness, pipeline health, reconciliation between feeds, and data-quality checks — so leaders know the numbers are current and trustworthy before acting.
Do: Acknowledge or resolve an alert to show the operational workflow.
Say: The agent recommends; a human approves. Approval routes to the right downstream system (Epic Cadence, OpTime, QGenda/UKG…) and creates a work order, with a full audit trail.
Do: Approve a pending item — watch the mock ticket and the decision log + value pipeline update.
Say: Ask grounded questions across any module; it won't invent numbers. The marquee moment: it refuses a PHI / patient-level request.
Do: Note the assistant tailors its starter questions to the active module. Ask the patient-level question to trigger the guardrail, then a real one.
Say: Change the hospital name and watch it cascade everywhere. Set targets. Review assistant usage + the decision log.
Do: Rename the hospital system and return to the suite overview to prove portability.
Tip: on a fresh deployment, use Admin → "Generate demo activity" first so the assistant usage, decision log, and value pipeline are populated.