Relative Contact Registration

For Barnekreftforeningen this is an MVP-critical capability because their entire support model revolves around the family unit, not just the affected individual. Without first-class relative records, peer mentors cannot accurately document the people they actually support, leading to undercounted activity, broken Bufdir reporting, and missed follow-ups. Capturing relatives as distinct subjects also unlocks downstream value: targeted notifications, role-specific conversation tools, and accurate statistics on family-level engagement. For other organizations where the relative concept is less central, the module remains toggleable, keeping the core product lean while serving Barnekreftforeningen's specific need.

Implementation uses the Relative Form UI component backed by a Relative Service writing to a dedicated relatives table linked to the contacts table via foreign key. The form validates required fields (name, relationship type) and optional fields (phone, email, notes), with phone and name encrypted at application level (AES-256-GCM) before persistence per the subprocessor agreement. Offline-first storage via Drift + SQLCipher ensures field workers can register relatives without connectivity, queued for sync via the outbox pattern. Role-based access ensures only peer mentors and coordinators in organizations with the relatives-database module enabled can create relative records.