Relative Contact Registration

Barnekreftforeningen's operational model centers on family-wide support, making it impossible to deliver their core service without tracking multiple family members per case. The priority matrix explicitly marks Pårørende-database as MUST for Barnekreftforeningen in Phase 1, confirming it is a launch-blocking requirement. Without this feature the organization cannot use the platform for its primary workflow. The relative database also reduces duplication risk by providing a single source of truth for family contacts, preventing conflicting records when multiple peer mentors serve the same family. This drives data quality and improves Bufdir reporting accuracy.

Relatives are modeled as a separate entity type in the relatives table, distinct from the main contacts table, with a foreign key to the organization and a linking table (relative_case_links) connecting them to primary contacts and cases. The Flutter UI uses a RelativeRegistrationScreen backed by RelativeService and RelativeRepository with Drift offline-first persistence and SQLCipher encryption. WCAG 2.2 AA compliance is mandatory: all form fields require semantic labels, minimum 24×24 touch targets, and full keyboard navigability. The REST API validates organization membership before allowing relative creation to enforce tenant isolation per the multi-tenancy architecture.