Skip to main content

​
Platform overview

For product vision, start with Veridian Motion. This page lists what is built today on the Lovable build (TanStack Start + Supabase), running on synthetic data. Treat capability as built / pre-production / rolling out until Veridian confirms activation for your facility — not generally available production.
Non-diagnostic. Programs teach self-care and organize the patient’s own data; a licensed clinician reviews before clinical materials reach a patient. HIPAA-aligned, not HIPAA-certified. Never claim IRB-approved or clinically proven.

​
What it is

Veridian Motion is a correctional wellness platform that delivers multiple licensed programs — not MSK triage alone. MSK Assessment & PT review remains the flagship; other programs are additive and feature-flagged. TanStack Start (React 19), installable PWA, USWDS-aligned UI, Supabase (Postgres, Auth, Storage) via Lovable Cloud.

​
Built today

​
Accounts, roles & security

  • Staff: email + password + TOTP MFA (enforced per deployment)
  • Patients: Patient ID + PIN (no self sign-up)
  • Roles: pt, admin, it_admin, officer, warden, bh_clinician, wellness_participant (see Role permissions)
  • RLS on every table; facility membership helpers
  • Append-only, hash-chained audit log; field-level PHI encryption (AES-256-GCM)
  • warden — operational visibility only (no clinical PHI) when multi-facility oversight is enabled

​
Programs (license-gated, feature-flagged)

Shared Programs & licensing: per-facility entitlements (seat cap + contract price), per-patient enrollments, access enforcement, monthly billing snapshots, invoice-support export. Contract-first — no credit cards. This is program licensing, not medical claims/CPT coding.

​
Operations

  • Admin console: Programs & Access, pricing calculator, bulk roster import (staff + patients), per-patient and bulk program enrollment, billing snapshots, legal-forms console
  • Terms & patient consent — required acceptance at first login (version + timestamp logged)
  • Secure messaging with safety screening and admin Communication Record (confirm activation per deployment)
  • Admin analytics — facility engagement reporting plus Usage & activity (aggregate only; measured vs clearly labeled estimated figures; no individual PHI)
  • Offline-capable where it matters (chess engine, puzzles, rehab) on locked facility networks

​
Rolling out

See Roadmap.

​
Design principles

  • Non-diagnostic — clinician review before clinical content reaches patients
  • Safety-gated — red-flag screens route worrying cases toward in-person sick call
  • Additive + flag-gated — modules ship behind flags, off until cleared
  • Offline where it matters — no external chess/rehab API calls required for core loops

​
What it is not (current public release)

  • Not a diagnosis tool
  • Not HIPAA-certified, CJIS-authorized, or FedRAMP-authorized
  • Not SSO, JMS, EHR, partner API, or live video — see Roadmap
  • Not medical claims / CPT coding (program seat licensing ≠ medical billing)
  • Not a public Behavioral Health product — BH remains gated pending legal clearance (Illinois WOPR Act); see Roadmap only
  • Not generally available production for real PHI until compliance migration

​
Compliance & synthetic data

Current Lovable builds use synthetic data only. Before a real pilot: owned Supabase (HIPAA add-on + BAA), compliant host, counsel-finalized Terms/MSA/BAA, IRB determination when required (program-evaluation framing), and clinical sign-offs. See Security overview.

​
What’s next

Programs & licensing

Entitlements and seats.

Roadmap

Rolling out and planned items.

Role permissions

Staff roles and RLS.