Relative Contact Registration

For Barnekreftforeningen, whose peer mentors support families affected by childhood cancer, registering relatives as independent contact subjects is foundational - without it the app cannot model the multi-person family unit central to their workflow. The feature enables coordinators to track follow-up actions across all family members, ensuring no one is missed during a crisis. From a platform perspective it future-proofs the data model for other organizations with family-centered support models, and structuring relatives as proper database entities ensures data quality for aggregate reporting.

A dedicated relatives table on the backend stores each relative with a FK to the parent contact. The Flutter UI reuses Contact form components adapted for relationship-specific fields, with a simplified mandatory set (name, role, phone) and optional extension fields. A REST endpoint at /api/v1/contacts/:id/relatives handles scoped CRUD. Drift mirrors the relatives table locally with mutation outbox support for offline creation. The Riverpod state layer manages relative lists per contact with optimistic mutations following the same pattern used by the contacts feature.