OverviewArchitectureExplore

Demo / engineering overview: Metrics on this page reflect internal test harness runs and may change. Capability labels use Live, Prototype, Planned, and Requires integration. This is not clinical validation or medical advice. Please avoid entering identifying patient information.

Live

Implemented in a current demo path without implying production readiness or clinical validation.

Prototype

Exploratory workflow that is not production-ready clinical software.

Planned

Not implemented yet or not exposed in the current demo.

Requires integration

Depends on customer systems, vendor access, contracts, and deployment review.

Feature labels distinguish what is implemented in the demo, prototype-only, planned, or dependent on customer integration.

Technical status

Technical status by integration surface.

These labels are deployment review signals, not compliance certification or clinical validation. Production scope still depends on the pilot workflow, EHR, hosting, retention, consent, and security review.

Requires integration

Model and prompt configuration

Current demos label configured structured-draft and review-support paths without promising a fixed production model.

Any named model, prompt set, latency target, evaluation threshold, or fallback policy must be selected and validated during deployment review before production use.

Prototype

Draft workflow routing

Configured routing between structured-output and review-support workflow paths in the demo.

Deployment-selected model path, latency, and evaluation criteria must be locked through customer privacy and security review before production use.

Requires integration

EHR integration

Pilot scoping can start with browser review, copy/paste handoff, or integration discovery.

Any SMART on FHIR reads, vendor APIs, identity mapping, audit controls, and contracts depend on the customer EHR and are not live by default.

Requires integration

Epic FHIR R4 / SMART on FHIR integration

Pilot scoping can identify Epic FHIR R4 resources, SMART launch context, read scopes, and browser-only fallback paths.

Not live by default; requires Epic and customer authorization, FHIR endpoint access, identity mapping, audit controls, agreements, and deployment-specific privacy/security review.

Planned

FHIR sandbox discovery, vendor-specific access required

Sandbox-only FHIR discovery can support integration planning; production EHR, Epic FHIR R4, or SMART on FHIR access is not live by default.

Requires vendor access, customer authorization, contracts, identity mapping, and deployment-specific audit review.

Requires integration

EHR writeback

Current demos can prepare review-ready drafts and handoff artifacts.

Writing notes, messages, orders, or billing actions back into an EHR is not active by default and requires approved connectors, audit controls, and human authorization.

Live

WebRTC Voice demo path

Browser-based voice capture is available in current demo paths for supervised workflows.

Production use requires deployment-specific consent, retention, device, network, and privacy review.

Live

SOAP generation public demo

Demo paths can generate structured SOAP drafts and related packets for clinician review.

SOAP output is a draft artifact only and must be reviewed before any clinical use.

Prototype

Voice workflows

Dr. Vita Scribe and voice intake flows produce draft artifacts for clinician review.

Ambient listening, telephony, multilingual support, and clinical operations rollout require pilot verification before production use.

Requires integration

Canada / PHIPA-oriented deployment review planning

Pilot intake can scope applicable PHIPA and provincial privacy role mapping for health information custodian, agent, electronic service provider, or HINP roles only where customer counsel determines those roles apply, plus Canadian hosting/data residency, retention, access, audit logging, subprocessor, consent/disclosure, privacy impact, and security assessment inputs.

Readiness materials support customer-specific legal, privacy, security, and operational review only; they are not certification, legal advice, or a determination that a deployment satisfies PHIPA obligations.

Requires integration

Patient-language draft communications

Demo concepts can show patient-language summaries and follow-up prompts after clinician review.

Patient-facing communication requires approved workflow rules, clinician-reviewed source notes, and deployment-specific consent/disclosure review.

Planned

Review logging and acceptance analytics

The architecture describes edit deltas, acceptance rates, latency, and safety-trigger logging.

Review logging remains planned until customer workflow policy, audit retention, and reviewer identity mapping are configured.

Technical ArchitecturePrototype

Technical Details (Demo)

This page summarizes Vitruviana's architecture, workflow-routing approach, and internal evaluation notes for specialty demo workflows. It is an engineering overview and should not be interpreted as clinical validation.

Demo build
Vitruviana Engineering
Internal test harness
Technical trace sampleDemo trace: sample workflow
Input
Voice + text intake
Live
Safety gate
Clinician review required
Prototype
Escalation + routing
Workflow router
Workflow router with live/prototype status
Prototype
Review supportStructured
Artifacts
SOAP draft + structured packet
Live
Schema-checked demo draft outputs; not clinically validated
Trace previewPrototype
Step Atask.routestructured extraction
Step Bpath.selectstructured draft path
Step Cartifact.generatepacket + draft coding cues
System snapshot
Demo
Live
Engineering Overview
This page summarizes architecture + internal evaluation notes (not clinical validation).
Structured
Live
Outputs
Schema checks for consistent handoffs and clinician review.
Guardrails
Prototype
Safety posture
Explicit scope limits, risk flags, and clinician-in-the-loop review.
Router
Prototype
Workflow routing
Routes tasks to configured workflow paths for review-support vs structured generation.
Internal
Prototype
Test harness
Scenario-based regression checks; metrics vary by configuration and run.
Multi
Prototype
Specialties
Explored on representative internal harness samples across specialties.
System layers + contracts
Experience layer
Prototype
Mixed demo status across Dr. Vita Scribe, ER Admin OS, Clinical Copilot review, and supporting specialty demos. See per-surface labels.
Dr. Vita ScribeER Admin OSClinical Copilot reviewSpecialty demos
Workflow services
Prototype
Session orchestration, prototype safety review routing, and live-demo schema checks.
Session managerSafety review routing prototypeBasic schema checks
Workflow router
Prototype
Routes tasks to review-support vs structured generation paths.
Review-support path - prototypeStructured draft path - demoFallback rules
Clinical services
Requires integration
Draft insight, note, customer-workflow artifact, and billing-cue services.
Draft insightsNote draftsCustomer artifact mapping
Telemetry + QA
Planned
Review events, edit history, and audit trail capture.
Draft deltasSafety triggersReview history
Request-to-draft flow
Capture
Live
Voice/text intake or clinician context.
Normalize
Live
Schema checks and basic safety guards.
Route
Prototype
Draft workflow routing for task type.
Generate
Live
Demo draft outputs with source/context notes where available; not clinically validated.
Review logging
Planned
Edit and acceptance logging planned; clinician review remains required.
Draft workflow routing
Review-support workflow
Prototype
Prototype path - clinician-review prompts
Latency: Deployment-dependent • Use: Task-dependent
Structured draft path
Live
Implemented demo path - structured drafts
Latency: Demo-dependent • Use: Task-dependent
Routing studio
Structured extraction
Live
Convert transcripts into schema-checked packets.
Route: Structured draft path
Review-support prompts
Prototype
Synthesize review prompts and draft assessment context.
Route: Review-support prototype
Patient communication
Requires integration
Translate reviewed clinician notes into patient-language drafts.
Route: Structured draft path
Safety review routing
Prototype
Surface possible escalation cues for clinician review; no autonomous triage or disposition decision.
Route: Safety review path
Engineering checks
InsightEngine
Prototype
Evidence-linked draft insights in the internal demo harness
Internal harness note: Scenario pass • Harness sample • Review prompts
MedicationReconciliation
Prototype
Medication reconciliation review prompts in the internal harness
Internal harness note: Scenario pass • Harness sample • Interaction review
NoteGenerator
Live
Structured SOAP draft generation in internal harness samples with schema section checks
Internal harness note: Schema pass • Schema sample • SOAP sections
PreVisitInterviewer
Live
Demo intake flow for structured capture and clinician review
Internal harness note: Extraction pass • Extraction sample • Extraction check
Specialty coverage
Cardiology
Prototype
Internal harness sample
Pulmonology
Prototype
Internal harness sample
Emergency Medicine
Prototype
Internal harness sample
Primary Care
Prototype
Internal harness sample
Endocrinology
Prototype
Internal harness sample
Nephrology
Prototype
Internal harness sample
Psychiatry
Prototype
Internal harness sample
Oncology
Prototype
Internal harness sample
Public research references
Long-context
Requires integration
External research reference: long-context AI research
Google DeepMind / Google Research (public materials)
Multimodal
Requires integration
External research reference: multimodal medical AI research
Google Research
Large context
Requires integration
External research reference: large-context AI research
Google DeepMind
Healthcare models
Requires integration
External research reference: healthcare AI foundation-model research
Google for Developers
Want to see the workflows in action? Start with the labeled demos, then come back here for architecture details.
Explore product demosOpen Clinical Copilot
Engineering overview • not clinical validation