Relative Role Tagging

Knowing that a contact is a parent rather than a sibling fundamentally changes how a peer mentor structures their approach and prioritizes follow-up. Without role tagging, all relatives are undifferentiated rows that require reading unstructured notes to understand family structure - error-prone and impossible to filter or aggregate in reports. For Barnekreftforeningen, distinguishing the primary caregiver from peripheral relatives is critical to directing limited peer mentor capacity toward the people most in need of support. Role tagging also enables coordinators to generate role-segmented views and statistics, improving visibility into the support landscape across multiple active family cases simultaneously.

Role tags are stored as an enum-backed string column on the relative_case_links table with a predefined value set (parent, sibling, caregiver, next_of_kin, other) enforced by a backend CHECK constraint. The RelativeRoleTagWidget renders as a segmented button selector or bottom sheet picker, meeting WCAG 2.2 AA touch target and contrast requirements. RelativeRoleService handles assignment validation and lookup. The Organization Labels system can override display strings for each role key without changing the underlying enum value, preserving data integrity across terminology changes. Drift caches available role options and current assignments for offline use. The backend returns 422 Unprocessable Entity for invalid role values, and the Flutter client prevents invalid selections through controlled input with server-side validation as a second layer.