> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veridianhp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> Facility rollout checklist — from pilot setup through first inmate intake and PT review.

# Getting started

This checklist helps **administrators and IT** bring Veridian Motion online at
a jail or correctional facility. Complete items in order where dependencies
apply.

<Note>
  Use **synthetic or de-identified data** in pilot until BAAs and agency
  hosting requirements are satisfied.
</Note>

## Phase 1 — Contract and compliance

<Steps>
  <Step title="Execute agreements">
    Sign facility agreement with Veridian Health Partners. Execute a **BAA**
    before production PHI flows.
  </Step>

  <Step title="Confirm hosting posture">
    Decide whether the agency requires CJIS-aligned, FedRAMP, or GovCloud
    hosting. Veridian Motion runs on Lovable Cloud / Supabase; dedicated
    environments may be arranged under contract. The app is **not**
    CJIS-authorized or FedRAMP-authorized by itself.
  </Step>

  <Step title="Identify contacts">
    Designate agency contacts for clinical operations, IT, and security
    incident notification.
  </Step>
</Steps>

## Phase 2 — IT and kiosk setup

<Steps>
  <Step title="Network allowlist">
    Allow outbound **HTTPS (443)** to the Veridian Motion app host and Supabase
    endpoints. Block unnecessary egress per agency policy.
  </Step>

  <Step title="Install the PWA">
    On each kiosk device, install Veridian Motion via the browser **Add to
    Home Screen / Install** flow. See
    [Deployment and kiosk](/veridian-motion/deployment-and-kiosk).
  </Step>

  <Step title="Apply MDM lockdown">
    Configure agency **MDM** for single-app or supervised mode, disable
    external browsers, and assign physical supervision procedures. App-level
    hardening alone is not sufficient for custody kiosks.
  </Step>

  <Step title="Test connectivity">
    Run a test sign-in and photo capture with Veridian support before inmate
    use.
  </Step>
</Steps>

## Phase 3 — Staff accounts

<Steps>
  <Step title="Create staff accounts">
    An Veridian or agency **admin** provisions staff emails in the dashboard.
  </Step>

  <Step title="Enroll MFA">
    Each staff member completes **TOTP MFA** enrollment at `/mfa` on first
    login. MFA is mandatory for dashboard access.
  </Step>

  <Step title="Grant roles">
    At `/staff`, assign roles: `pt`, `admin`, `officer`, `warden`, `it_admin`
    as appropriate. See [Role permissions](/veridian-motion/role-permissions).
  </Step>
</Steps>

## Phase 4 — Clinical configuration

<Steps>
  <Step title="Configure allowlisted email (optional)">
    If using PDF email export with real PHI, configure **allowlisted
    addresses** and confirm a **BAA-covered email provider** is in place.
    Until then, use PDF download only within the secured dashboard.
  </Step>

  <Step title="Train PTs">
    Walk through [Provider dashboard](/veridian-motion/provider-dashboard) and
    [AI and clinical safety](/veridian-motion/ai-and-clinical-safety) —
    especially the **red-flag-first** review order and PT-review gate.
  </Step>

  <Step title="Train custody staff">
    Cover kiosk escort, PIN handoff, idle auto-reset, and when to interrupt for
    safety concerns. See [Inmate kiosk flow](/veridian-motion/inmate-kiosk-flow).
  </Step>
</Steps>

## Phase 5 — First live case

<Steps>
  <Step title="Enroll a patient">
    Admin uses **Enroll patient** → record **inmate number + initial PIN** →
    hand credentials to custody staff.
  </Step>

  <Step title="Inmate intake">
    Inmate signs in at `/inmate-login`, completes body map, complaint, and
    four photos, then submits.
  </Step>

  <Step title="Assign and review">
    Admin assigns the submission from the **unassigned queue** to a PT. PT
    reviews, edits plan, marks **reviewed**.
  </Step>

  <Step title="Confirm inmate release">
    Inmate opens **My plan / progress** and confirms **Reviewed** status shows
    the approved plan and any shared PT notes.
  </Step>
</Steps>

## After go-live

* Monitor the [status page](https://status.veridianhp.com) for service health
* Route issues through [Troubleshooting](/troubleshooting) and
  [support@veridianhp.com](mailto:support@veridianhp.com)
* Review audit logs periodically (`/audit` — role-scoped)

## What's next

<CardGroup cols={2}>
  <Card title="For evaluators" icon="clipboard-check" href="/veridian-motion/for-evaluators">
    One-page summary for decision-makers.
  </Card>

  <Card title="Status and workflow" icon="diagram-project" href="/veridian-motion/status-and-workflow">
    Status labels and who acts when.
  </Card>

  <Card title="Deployment and kiosk" icon="lock" href="/veridian-motion/deployment-and-kiosk">
    PWA, hardening, and MDM split.
  </Card>

  <Card title="FAQ" icon="circle-question" href="/faq">
    Common facility questions.
  </Card>
</CardGroup>