Relative Role Tagging
Feature Detail
Description
Relative Role Tagging assigns structured role labels to relatives, indicating their relationship to the primary contact. Supported roles include parent, sibling, guardian, next-of-kin, and primary caregiver, selected from a controlled vocabulary that prevents free-text inconsistency and enables filtering and reporting. The tag picker is presented during registration and is editable from the relative detail screen at any time. Organizations can configure additional role tags via the Admin Web Portal using the existing terminology override mechanism.
Sources & reasoning
The explicit enumeration of relative types (foreldre/parents, søsken/siblings, nærmeste omsorgsperson/primary caregiver) in §3.4 implies structured role classification is intrinsic to the feature. The blueprint models relative_roles as a dedicated table confirming this is distinct from registration. MVP target follows the Fase 1 MUST classification of the parent area confirmed in §7.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Structured role tagging transforms the relatives database into a semantically meaningful family model. Knowing that a person is the primary caregiver rather than a distant relative lets coordinators prioritize outreach and decide who must be involved in follow-ups. Role tags enable reporting - identifying how many cases involve single-parent households or how many caregivers have received follow-up - supporting internal quality assurance and funder reporting. The controlled vocabulary approach ensures data quality across all users and devices, a prerequisite for reliable aggregate reporting.
Role tags are stored in a relative_roles table linking relative_id to role_slug and display_label. The vocabulary is seeded with defaults (parent, sibling, guardian, next-of-kin, caregiver) and extensible via organization configuration using the existing terminology_overrides infrastructure. On mobile the Relative Role Picker is a multi-select chip widget using roles fetched from the API and cached offline via Drift. The backend exposes endpoints for vocabulary management and per-relative role CRUD. Riverpod provides a roles-per-relative stream with reactive updates. Vocabulary extension is administered from Organization Management in the Admin Web Portal.
Components (43)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.