Relative Role Tagging
Feature Detail
Description
This feature lets peer mentors and coordinators tag each relative with their specific family role - parent, sibling, grandparent, closest caregiver, or other configurable role types defined per organization. The Role Tag Picker presents an organization-aware list of available relative roles (configurable via the terminology system) and stores the selected role on the relative record. Role tags drive downstream filtering, statistics segmentation, and role-specific conversation tools, allowing more nuanced family support workflows than a flat relatives list could provide.
Sources & reasoning
Source line 77 enumerates specific relative role types (foreldre/parents, søsken/siblings, nærmeste omsorgsperson/closest caregiver), indicating the system must distinguish between them. Role tagging is the mechanism to capture this distinction and falls within the Fase 1 Pårørende-database MUST scope.
-
docs/source/likeperson.md · line 77registrering av pårørende (foreldre, søsken, nærmeste omsorgsperson) som egne kontaktsubjekter
-
docs/source/likeperson.md · line 111Pårørende database | ✓ | - | - | - | ✓ | MUST (Barnekreft) | 1
Analysis
Role tagging unlocks the segmentation that makes the relatives database actionable rather than just a list. Peer mentors can quickly identify whether they are speaking with a parent versus a sibling, which materially changes the conversation approach and resource recommendations. Coordinators can pull statistics on how many parents versus siblings the organization supports, informing program design and funding applications. The configurable tag set respects the organization labels system, so each tenant can use the terminology that matches their domain (e.g., 'nærmeste omsorgsperson' for Barnekreftforeningen) without code changes.
Implementation adds a role field to the relatives table (or a separate relative_roles lookup table for normalized configuration) populated via the Role Tag Picker UI. Available role values are read from organization configuration via the existing terminology/labels system, allowing per-tenant customization without code changes. The Relative Role Service exposes CRUD operations gated by role-based access control. Offline cache holds the current tag set so peer mentors can tag relatives in the field without connectivity. Migration considerations include a default 'unspecified' tag for legacy records to avoid breaking validation.
Quality Assurance
No QA section has been generated for this feature yet.
Components (4)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.