Ten minutes inside Lakeview General Hospital
Community hospital · Ontario · 420 beds (synthetic profile). A fictional hospital, a real product: every screen in this tour runs Nexus's own scoring, eligibility, and audit logic over synthetic inputs. Ten minutes, no account.
The ten minutes
Follow the numbered journey in order, or jump to any stop. The progress bar at the top of every demo page keeps your place.
- See
Minute 1: What Nexus is
Private AI governance and intelligence for healthcare: one product that tells you what is changing, where you are exposed, which AI is allowed, and whether you can prove what happened.
Platform overview → - See
Minute 2: Current healthcare intelligence
Seven live feeds. Each card separates the source fact from Nexus analysis and the review it should trigger.
Open the AI Governance feed → - See
Minute 3: Why an intelligence event matters
An Ontario regulation comes into force. Nexus links it to the three assessment controls it changes for Lakeview.
See the linkage below → - Assess
Minute 4: A healthcare readiness gap
Lakeview's assessment: controls, findings, critical gaps, actions, evidence, regulatory mappings, versions, and history.
Open the critical gaps → - Govern
Minute 5: AI model eligibility
Four synthetic models, three requests. The real evaluator decides who may touch PHI — and says why.
Run the eligibility matrix → - Govern
Minute 6: Alice: BLOCK · REVIEW · ALLOW
A clinical summary request for PHI aimed at an external cloud model is blocked; a sovereign alternative is offered. Then open Alice itself: agents, autonomy envelopes, and a full day of decisions.
Open Alice's command center → - Prove
Minute 7: Evidence
Model card, policy decision, control mapping, remediation record, approval — each hashed, each linked to what it supports.
Inspect the evidence chain → - Prove
Minute 8: Trust Receipt
The artifact a CISO hands an auditor: decision ID, purpose, classification, model requested and selected, verdict, reason code, reviewer, audit integrity.
Read the BLOCK receipt → - Act
Minute 9: Remediation and action
Findings become recommendations with owners, due dates, evidence, and closure — one open, one completed.
See the action lifecycle → - Act
Minute 10: “Show me my organization.”
Everything here is synthetic. Signing in shows the same surfaces for your own hospital.
Request access →
Minute 3 · Why an intelligence event matters
Intelligence is only useful when it changes what you do. Here is one item from the live AI Governance feed and how Nexus connects it to Lakeview's own controls.
Ontario Regulation 51/26 is in force: prescribed hospitals must operate a documented cyber-security program, run maturity assessments, and report incidents on prescribed timelines.
Lakeview is a prescribed entity. AI systems in clinical workflows sit inside the program's scope, so the inventory (GOV-01), incident reporting (SEC-03), and vendor oversight (VEN-01) controls now carry a binding deadline rather than a best practice.
Confirm the AI inventory is complete, map incident reporting for AI-involved events to the regulation's timelines, and verify the scribe vendor's obligations in the contract.
The four experiences
Nexus Intelligence
What is changing? Seven feeds, live, with FACT / INFERENCE / FORECAST labels and a documented threat-level method.
Nexus Readiness
Where are we exposed? 49/100 · Foundational · 3 critical blockers. Readiness estimate, not certification.
Nexus Governance
Which AI is allowed and why? Deterministic eligibility with reason codes. Today: 2 allowed · 1 held · 1 blocked.
Nexus Trust
Can we prove what happened? BLOCK Clinical summarization of a patient chart — sealed in a verified hash chain.
Ready to see your own organization?
Everything above is synthetic. Signing in shows your organization's own assessment, risks, policies, recommendations, and Trust Receipts. Access follows a confidential discussion and a signed NDA.
Journey map: What Nexus is → Current intelligence → Why it matters → Readiness gap → Model eligibility → BLOCK · REVIEW · ALLOW → Evidence → Trust Receipt → Remediation → My organization.
Every record on this page is synthetic and belongs to a fictional hospital. Nothing here is a customer, a patient, or a production measurement. The scoring, eligibility, and audit logic are the real Nexus engines running over the synthetic inputs.