Production model configuration
Requires integrationProvider, model, prompt, fallback, latency, and evaluation choices are deployment decisions and are not represented as fixed production claims here.
Technical statusPrototype
What is live, what is prototype, and what requires integration.
This page is a buyer-facing implementation map. It separates current demo availability from prototypes, planned work, and customer-specific integration requirements.
It is not clinical validation, production readiness certification, model certification, EHR integration proof, or a PHIPA compliance determination.
Status snapshot
Browser demo paths
LiveCurrent public demos can show browser-based intake, scribe review, ER Admin OS, and Clinical Copilot review flows with sample data.
Structured draft generation
LiveDemo workflows can produce SOAP-style and structured draft artifacts for clinician review, not direct clinical use.
Clinician review gates
PrototypeReview prompts and approval boundaries are visible in demo paths; customer-specific policy and audit mapping still require pilot review.
Review logging and acceptance analytics
PlannedEdit deltas, reviewer identity, acceptance rates, retention, and audit reporting remain deployment-scoped work.
Status labels
LiveLive demo/page path is available; not a production-readiness or real-patient-use claim.
PrototypeReviewable workflow pattern that still needs pilot review.
PlannedRoadmap item or design target, not currently live.
Requires integrationDepends on customer systems, agreements, and deployment review.
Epic, FHIR, and EHR connectivity
Requires integrationSMART on FHIR reads, Epic FHIR R4 access, identity mapping, scopes, vendor authorization, and contracts are customer-specific integration work.
EHR writeback
Requires integrationWriting notes, orders, billing actions, messages, or referrals back into an EHR is not live by default and requires approved connectors plus human authorization.
Canada / PHIPA deployment review
Requires integrationVitruviana can support deployment-review materials, but does not certify or determine PHIPA compliance; final posture depends on customer legal, privacy, hosting, retention, subprocessor, access, and operational review.
Copy guardrails
Technical claims stay deployment-scoped.
The status labels are intentionally conservative so a demo page does not overstate platform implementation, EHR writeback, or compliance readiness.
Use sample data in public demos; do not enter PHI or real encounter audio.
Treat all generated clinical artifacts as drafts until a licensed clinician reviews and approves them.
Label platform and vendor claims as integration-dependent unless a current demo path actually implements them.
Keep model references deployment-scoped rather than presenting named providers as fixed production architecture.