Relative Case Linking

Barnekreftforeningen coordinates care across entire family units, not just the primary patient. Without case linking, relative records are orphaned data with no operational utility - coordinators cannot see which relatives belong to which family case, and peer mentors cannot understand the support context during a visit. Linking also prevents double-counting in activity reporting by anchoring all family-related activities to a single case record, maintaining clean Bufdir-reportable data. This feature is what makes the relatives database operationally valuable rather than merely a contact directory.

Case linking is implemented via the relative_case_links junction table, which holds foreign keys to both relatives and contacts with an optional link_type field. The RelativeCaseLinkWidget is a Flutter widget rendered inside the ContactDetailScreen to show and manage linked relatives inline. CaseLinkService handles the business logic for creating, removing, and querying links, delegating persistence to the RelativeRepository. Offline support is handled by Drift with optimistic mutation and outbox sync. The API endpoint enforces that both the relative and the contact belong to the same organization before creating a link, preventing cross-tenant data leakage.