Pilot-intro intake

Pilot intro request

Share the workflow, output, and deployment questions that matter so the first intro starts with the right pilot owner.

Vitruviana is a healthcare intelligence OS: Dr. Vita Scribe and ER Admin OS are the two primary surfaces, while Clinical Copilot is the review layer for drafts, evidence, and approval gates.

Required routing details: name, email, organization/clinic, country/province/state, role, workflow interest, current EHR/tools, desired outputs, pilot timeline, and notes. Optional context can cover current pain, contact preference, data residency, privacy review, and success criteria.

01
Route the intro
Identify the buyer, jurisdiction, role, and workflow lane.
02
Scope the pilot
Name the systems, desired output, and timeline for evaluation.
03
Protect the channel
Keep the request demo-safe and free of patient-identifying information.
Request Pilot Intro by workflow

Choose the pilot lane first, then complete the intake below. Do not include patient-identifying information.

Dr. Vita ScribeRequest Pilot Intro →Clinician scribe, SOAP templates, referral letters, and approval workflow.ER Admin OSRequest Pilot Intro →Facility operations, staffing gaps, compliance tasks, and action ownership.Clinical CopilotRequest Pilot Intro →Draft review layer, evidence anchors, known/unknowns, and audit workflow.Patient IntakeRequest Pilot Intro →Guided intake, escalation copy, consent language, and clinician handoff.Revenue/RCMRequest Pilot Intro →Denials, payer sources, claim status, worklists, and reconciliation outputs.Trust / Security ReviewRequest Pilot Intro →PHIPA/HIPAA scoping, hosting, retention, subprocessors, audit logs, and review materials.Technical / Research ReviewRequest Pilot Intro →Architecture, implementation status, integration boundaries, APIs, and test artifacts.
Serious pilot packet

The required fields give enough context to route an intro to product, clinical, operations, and deployment review.

Live
Required
  • Name
  • Work email
  • Organization / clinic
  • Country / province / state
  • Role
  • Workflow interest
  • Current EHR / tools
  • Desired outputs
  • Pilot timeline
  • Notes
Optional context
  • Pilot trigger
  • Care setting
  • Estimated volume
  • Preferred contact method
  • Budget / stage
  • Privacy / security review needs
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.
Designed for Canada / PHIPA deployment-review planning

Vitruviana can support Canada / PHIPA-oriented deployment-review preparation for customer-specific pilots, including Ontario PHIPA review where applicable. Canada / PHIPA deployment-review planning here means readiness materials for review, not certification or a compliance determination. Canada / PHIPA deployment review preparation means the review can scope hosting, data residency, retention/deletion, subprocessors, agreements, role mapping, safeguards, audit logging, and clinic operating policies before production use.

Final compliance depends on hosting, data retention, subprocessors, agreements, 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, jurisdiction-specific requirements, access model, safeguards, audit logging, and clinic operating policies.

Readiness language is deployment-review preparation, not certification, legal advice, or a PHIPA compliance determination. Do not include identifying patient information in this public form.

Pilot intake

Organization/clinic, country/province/state, role, and the right pilot owner help route the intro quickly.

This public form validates pilot-scoping details only. It does not create storage, CRM records, or external delivery; keep the request free of patient-identifying information.

Who should receive scheduling and pilot-scoping follow-up.

Use an email address where we can follow up on pilot scoping.

Clinic, group, hospital, or health system evaluating Vitruviana.

Include the jurisdiction for privacy, hosting, and deployment review.

Your role helps match the intro to the right level of pilot detail.

Workflow interest

Select one or more workflow interests. Dr. Vita Scribe and ER Admin OS are the primary demo paths.

Primary surfaces
Review layer and secondary interests

Optional: describe the workflow pain, clinical documentation gap, ER operations issue, or revenue problem that should drive the intro.

List the EHR, intake, billing, scheduling, spreadsheet, or other systems involved.

Describe the artifact, dashboard, letter, report, or workflow output your team wants to evaluate.

Family medicine, urgent care, ER operations, specialty clinic, hospital group, or another setting.

Approximate visits, providers, facilities, claims, or reviews that matter for the pilot.

Optional: clinician, ER operator, safety/compliance reviewer, technical evaluator, or executive sponsor.

Optional: browser-only demo, CSV/API import, EHR/FHIR review, SSO/security review, or production integration planning.

Share the timing you are targeting for evaluation.

Optional: budget approved, discovery, active pilot planning, or not sure yet.

Optional: email, phone, Teams, or another preferred way to coordinate the pilot intro. Defaults to email.

Optional phone number, Teams handle, or scheduling contact if different from email.

For example: Canada region preferred, U.S. HIPAA/BAA review if applicable, or browser-only pilot first.

Optional contact for privacy, security, PHIPA/HIPAA, or vendor-review questions.

List Canada / PHIPA role-mapping questions, U.S. HIPAA/BAA questions, hosting/data residency, retention/deletion, subprocessors, identity, safeguards, or audit-log needs.

Describe what would make the pilot successful enough to continue.

Add anything that helps route the request. Do not include patient-identifying information.

Compare demos