Choose your player tap a card to open their quest board
Route Builder opted-in neighbors build the schedule: 60 min AM + 60 min PM is the goal
Neighbor names and addresses stay in this app for the route only. They are never included in CSV exports or CoreTrack Nexus sync.
Progress per-goal prompt levels: this is your quarterly report data
StaffSide Duet staff earn points for every documented session
Setup
👥 Players (residents)
🗺️ Quests (ISP goals)
🔗 CoreTrack Nexus
⚠ Linking Nexus IDs connects this device data to real resident records: treat the device as PHI-adjacent once linked (BAAs, device security, MFA on CoreTrack). Sync stays off until you configure it.
🔐 Access PINs
When set, the app locks on open and roles limit what is visible: Play (quests only) → Staff (+ progress, exports) → Admin (everything).
PINs are a deterrent, not encryption. Device passcode and full-device encryption are the real safeguard.
🛡️ Device Security
Condition of use: device passcode, device encryption, auto-lock of 5 minutes or less, and the device stays in facility control. In-app PINs are supplemental, not encryption.
🧩 Modules
Future add-on modules plug into the same quest engine and data model.
📄 Privacy & compliance
QuestLife is designed to support HIPAA compliance: device-local, de-identified-leaning data, sync off by default. Software cannot be HIPAA compliant on its own; organizations comply.
Initials are not Safe Harbor de-identification. In a small group home, initials plus goal data can identify a person to anyone with context. Treat all QuestLife data as PHI-adjacent.