Hospital IT & Privacy Overview
Patient files, model calibration, and weekly caseload scoring stay on your own clinic workstation or internal Windows server. No patient records are ever sent to external cloud vendors.
1. No Cloud Transmission of Patient Data
Reading historical CSV extracts, fitting session-by-session statistical models, scoring weekly active caseloads, and serving clinician dashboards all happen locally on your own Windows computer or internal clinic server behind your firewall. No Protected Health Information (PHI) is ever sent to external servers, third-party cloud databases, or SMS services.
2. Single-Install Clinic Server Mode (No Workstation Installs)
IT installs Outcomes Predictive Suite on one host computer inside your clinic or hospital network. Individual therapists (and supervisors on Enhanced & Premier) do not install software and never enter license keys. They open an internal browser link on their office workstation and sign in with their clinic account credentials (stored on the host using salted, hashed passwords).
3. Air-Gapped & Restricted-Network Ready
All fonts, icons, interactive charts, statistical libraries, and user manuals are bundled locally inside the installer, so nothing is fetched from external CDNs at runtime. For hospital networks that block outbound internet access completely, signed offline license keys validate locally with no external network traffic.
4. Server-Side Caseload Isolation
Caseload filtering happens on the local host server before records reach the browser. When a clinician signs in, the server returns only that clinician's assigned clients. Other providers' caseloads, clinic-wide setup menus, and historical calibration settings are never sent to a clinician account.
5. Compiled & Encrypted On-Premise Packaging
Production builds ship as a self-contained compiled Windows application with encrypted in-memory statistical execution, writing no plain-text scripts or unencrypted source files to disk or temporary folders. On clinic network interfaces, automatic per-IP rate limits also block repeated failed logins.
6. Works With Your Existing EHR via Scheduled CSVs
No custom HL7/FHIR integration build is required to start. Point Phase 2 Autopilot at a local network folder where your EHR (Epic, Cerner, SimplePractice, Credible, REDCap, or Qualtrics) exports scheduled CSV files, and open browser tabs update automatically.
Technical Summary for Hospital Security Review
| Deployment Environment | Local Windows 10/11 (64-bit) workstation or internal Windows Server VM behind clinic/hospital firewall |
| Installer Privileges & Runtime Isolation | Per-user installation supported (no system-wide elevation required); self-contained statistical runtime isolated from any other software on the host machine |
| Clinician Client Access | Standard internal web browser (Chrome, Edge, Safari) over clinic LAN/VPN; zero client-side installation |
| Patient Data Residency & HIPAA BAA | 100% customer-hosted behind your firewall; vendor never receives, stores, or processes PHI |
| Authentication & Access Control | Salted cryptographic password hashing with constant-time verification, loopback-only initial setup guard (custom passwords required on LAN), role-scoped session tokens (Director and Clinician in all four tiers, plus Supervisor on Enhanced & Premier), optional enterprise portal single sign-on, and per-IP failed-login throttling |
| HIPAA Screen-Lock & Host Uptime | Background host mode keeps LAN access and Autopilot folder scoring active while the monitor turns off and the Windows screen remains locked (Windows+L), with optional system-tray startup |
| External Network Dependencies | Zero required in signed offline license mode; anonymous token-only check in standard mode with 30-day (720-hour) offline tolerance (summary sheet available in the downloadable 2-page Hospital IT Brief below) |
| Input & Output Formats | Standard long-format UTF-8 .csv input; structured .csv and .json outputs, .md/.txt/.pdf calibration reports, and bundled offline .html Training Manual |