Clinical and operational records
Patient charts, outcomes, dispatch notes, unit status, criminal-justice information, payroll, messages, attachments, and source-system content remain in their official systems.
A narrow launcher, not a new system of record.
Frontline organizes approved destinations and stops at the boundary of each official system. It does not frame, scrape, proxy, or monitor vendor systems after launch.
Current technical-readiness status
Frontline has implemented a launch-only architecture, server-side organization and role checks, protected mobile sessions, device-local Face ID and PIN options, bounded audit events, security headers, recovery procedures, and automated release checks. Important gates remain open: a formal HIPAA security risk analysis, required business associate agreements, independent penetration and tenant-isolation testing, production alert routing, a recorded database restore exercise, automated retention enforcement, and legal review. These controls reduce risk; they do not certify the service or authorize PHI.
What stays outside Frontline
Vendor credentials and activity
Frontline never asks for vendor passwords, MFA codes, cookies, or tokens and cannot observe what a member does after a destination opens.
Approved metadata only
Frontline stores the minimum identity references, organization configuration, tool IDs, member preferences, launch-request events, and administrative audit records required to operate the Hub.
Device protection
The native app uses operating-system protected storage for its renewable Frontline session. A member may require Face ID, a device-specific six-digit Frontline PIN, or both before that saved session is restored. The PIN is salted and derived before storage, is temporarily locked after repeated failures, and is not the member's WorkOS password or MFA factor.
Five production gates
- 01
Real authentication with MFA
Individual, revocable accounts with organization-approved identity and stronger protection for privileged access.
- 02
Server-enforced permissions
Every protected request is authorized from trusted session and organization data; browser controls never grant administrator access.
- 03
Organization separation
Users, destinations, preferences, configuration, and audit records are scoped to the authenticated organization.
- 04
Strict destination validation
Only administrator-approved HTTPS or verified mobile destinations can launch.
- 05
Auditing, monitoring, and recovery
Administrative changes are recorded; health checks, incident handling, backups, and restore exercises are part of release readiness.
Report a security concern
Do not include passwords, passkeys, MFA codes, patient information, dispatch data, or screenshots containing sensitive records. Contact fajardovictor@frontlineaccesshub.com with a concise description and safe reproduction steps.