Today · v0.1 scripted demo
What’s actually running right now
- Curated, hand-authored response scripts mapped to a small set of representative patient questions.
- No live language-model inference. No retrieval. No citation. No memory.
- Surface the same look, tone, and chrome as the v1.0 product so you can evaluate the experience.
- Useful for: investor walkthroughs, design review, surgical-partner demos, internal QA.
- Not useful for: clinical decisions, real-world patient triage, anything that needs current pricing or current clinic availability.
Target · v1.0 production
What v1.0 will be
- Retrieval-grounded over a curated corpus: JetPatient clinic registry, procedure catalog, JCI accreditation reference, consensus surgical-tourism guidelines.
- Every clinical statement carries a citation back to the source.
- Explicit refusal contract: out-of-scope queries (diagnosis, prescribing, urgent-care triage, anything outside the procedure catalog) get a clear handoff.
- Server-side authz scoped to the signed-in patient’s Passport. No cross-patient leakage.
- Auditable session logs, retention configurable per BAA. Inference runs on JetPatient-managed infrastructure inside contracted BAA scope.
What the Navigator will and will not do at v1.0
Will do. Answer questions about specific clinics in the JetPatient network, procedure descriptions, recovery timelines from our catalog, what the bid process looks like, what HIPAA-aligned record-sharing covers, and how to read a JetPatient quality report. Always with a cited source.
Will not do. Diagnose a condition, recommend a specific surgeon over another in clinical terms, answer cancer or psychiatry questions, prescribe or modify medication, triage an emergency, or operate outside the JetPatient procedure catalog. Every refusal includes a documented handoff: a JetPatient nurse navigator, the patient's PCP, or in urgent cases, local emergency services.
The Navigator is a coordination tool, not a clinician. The clinical guardrails are tighter than a general-purpose chat product, by design. We’d rather refuse a question and route it to a human than confidently answer outside our scope.
Privacy and data handling (v1.0)
- Conversations are PHI when the signed-in user is a patient. Storage encrypted at rest under customer KMS keys; TLS 1.3 in transit.
- Default retention: 24 months from last message. Configurable per BAA.
- No third-party model providers see PHI in plaintext in production. Inference runs inside the contracted BAA scope.
- No training on customer conversations without explicit, separate, written opt-in.
- Patient-facing one-tap delete-my-history control, audit-logged.
Version log
- v0.1 · May 2026 · Scripted demo. Today’s chat returns curated responses. No live inference, no retrieval, no citation. Demo only.
- v1.0 · Target Q3 2026 · Retrieval-grounded production. Scoped to JetPatient catalog, full citation, refusal contract, audit logging. Subject to clinical advisory board sign-off before any patient-facing rollout.