DRIVE SHIFT 360 app formation 1
The document defines the functional specification for the Drive Shift 360 platform, a NFC‑based driver wellness management system. It outlines a five‑layer architecture (NFC card → Android staff app → secure cloud → dashboards → driver record) and a strict workflow: driver identification, baseline (T0) physiological and cognitive assessment, optional multimodal intervention, post‑intervention (T1) reassessment, change analysis, and departure status. The system is deliberately positioned as a wellness screening tool, not a medical‑diagnosis or employment‑disciplinary engine. Key components include: detailed data structures for each visit, NFC card lifecycle management, multi‑tenant company isolation, configurable dashboards (driver, company, central), follow‑up handling, granular consent and privacy tracking, mandatory security controls (AES NFC, TLS, RBAC, 2FA, audit trail), offline roadside mode with secure sync, a phased device‑integration roadmap, report generation, extensible research‑module forms, media capture, and a driver‑controlled digital health card with emergency‑access safeguards. The specification emphasizes that no sensitive health data is stored on the NFC card, that T1 must not be estimated if the session is incomplete, and that all status decisions are configurable and must be approved by qualified professionals.
Topics
Five‑Layer System Architecture & NFC Token Design
Defines the end‑to‑end stack: NFC driver card, Android staff app, secure cloud backend, company/authority dashboards, and driver record/report generation.
Driver Journey & Baseline (T0) Assessment Workflow
Step‑by‑step process from NFC tap, driver identification, journey metadata capture, to physiological and cognitive baseline measurements.
Multimodal Intervention Decision Logic
Two pathways (accept or decline) with configurable physical, visual‑sensory, and cognitive‑autonomic interventions, including timing and staff logging.
Post‑Session (T1) Reassessment & Change Score Generation
Mandatory repeat of T0 measures after intervention, automated before‑after comparison, and generation of a non‑diagnostic progress score.
Handling Incomplete Sessions & Non‑Verified Post‑Assessment
Rules for when a driver leaves without completing the session; T1 is left null, and the system records ‘post‑session condition not verified’.
Departure Status Categorisation & Configurable Escalation
Defines status codes (routine wellness, reassessment advised, professional evaluation, urgent escalation, not verified) that are admin‑configurable and not binary fit/unfit.
Comprehensive Visit Data Model
Full list of database fields for each Drive Shift 360 visit, covering driver, journey, assessments, interventions, consent, device, audit, and sync metadata.