Relative Case Linking

Without explicit case linking, relatives exist as disconnected records with no navigable relationship to the primary subject. Coordinators cannot see the complete family support picture in one place, making it impossible to verify which family members have been reached and which still need attention - directly undermining Barnekreftforeningen's care model. Case linking is also foundational for role tagging: roles are applied to case link records, not to relatives directly, meaning role tagging cannot exist without this join structure. Establishing the relationship model in MVP ensures all subsequent relatives-database capabilities build on a consistent data structure rather than retrofitting associations after launch.

A relative_case_links join table stores a many-to-many relationship between relatives and contacts, with columns for relative_id, contact_id, org_id, and case_role. The RelativeCaseLinkWidget renders as an embedded section on both ContactDetailScreen and RelativeDetailScreen with bidirectional navigation. Drift caches link records offline with sync queue support for link creation and deletion operations. The REST API validates that both the relative and the contact belong to the same organization before creating a link. Duplicate link detection returns 409 Conflict. The backend also cascades link deletion when a relative or contact is removed. All interactive link controls meet WCAG 2.2 AA: semantic action labels, visible focus indicators, and minimum 24px touch targets.