Caregiver & Next-of-Kin
Feature Detail
Description
Caregiver & Next-of-Kin enables registration of family members, caregivers, and next-of-kin as distinct contact subjects linked to a primary case. Each record captures the person's relationship role (parent, sibling, primary caregiver) and is persisted in the relatives and relative_roles tables. This capability is a Phase 1 MUST for Barnekreftforeningen, which works primarily with families around children with cancer and requires the app to model the full family unit as addressable contacts within a single case rather than tracking only the affected individual.
Sources & reasoning
Line 121 gives the exact requirement verbatim: register family members as distinct contact subjects linked to the same case. Line 151 marks it MUST in the priority matrix for Barnekreftforeningen with Phase 1. Line 428 explicitly restates "Fase 1 MUST for Barnekreftforeningen." Phase 1 ordinal maps to MVP. Blueprint places this feature in the Contacts area, not a standalone area, so it correctly appears here.
-
docs/source/likeperson.md · line 121Pårørende-database: Barnekreftforeningen jobber primært med familier rundt barn med kreft, ikke kun med de berørte selv. Appen må støtte registrering av pårørende (foreldre, søsken, nærmeste omsorgsperson) som egne kontaktsubjekter knyttet til samme
-
docs/source/likeperson.md · line 151Pårørende database | ✓ | - | - | - | MUST (Barnekreft) | 1
-
docs/source/likeperson.md · line 428Pårørende-database er Fase 1 MUST for Barnekreftforeningen (se §4 matrisen).
Analysis
Barnekreftforeningen identified the pårørende database as a Phase 1 MUST (line 151), making this a launch blocker for that organization. Without caregiver linking, coordinators must maintain family relationships in external spreadsheets, creating fragmented records and missed follow-ups - a direct risk to care quality. The role-tagging system allows coordinators to immediately identify the correct family member to contact in sensitive situations, reducing cognitive load under stress. The feature also supports the contact_organization_memberships data model enabling multi-org family tracking as the platform grows to additional tenants.
Implemented via the relatives and relative_roles database tables. A CaregiverLinkWidget Flutter component renders as a collapsible section inside the contact detail screen, listing linked relatives with their role tags and providing add/edit/remove actions gated by coordinator role. A Riverpod RelativesRepository wraps Drift queries on the relatives table. Role tags are loaded from the relative_roles lookup table, allowing new relationship types to be added without schema changes. The role picker dropdown must be keyboard-navigable with a semantic label meeting WCAG 2.2 AA; all touch targets ≥24×24 px.
Components (46)
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.