Caregiver & Next-of-Kin

Description

Registration and management of caregivers and next-of-kin associated with a primary contact. Peer mentors and coordinators can capture the relatives or carers who play a role in the contact's situation - parents, siblings, spouses, or designated emergency contacts - directly from the contact detail screen. Each caregiver record carries name, relationship, contact channels, and optional notes, and can be linked to one or more contacts. This is distinct from the broader Relatives Database area: this feature is the lightweight per-contact attachment used during everyday peer mentor work, while the Relatives Database handles cross-case linking and role tagging.

Sources & reasoning

Blueprint lists Caregiver & Next-of-Kin under the Contacts area as a distinct feature. It is the per-contact carer attachment (distinct from the Relatives Database area). Not in mobile MVP screens list, so target_release defaults to Core Product per resolution rule 3.

docs/source/likeperson.md · line 77

På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
docs/source/likeperson.md · line 353

contacts | Contacts | Contact List & Search, Contact Detail & Edit, Caregiver & Next-of-Kin
docs/source/likeperson.md · line 111

Pårørende database | ✓ | - | - | - | ✓ | MUST (Barnekreft) | 1

Analysis

Business Value

Many peer mentor interactions - especially in Barnekreftforeningen's family-centric model and Blindeforbundet's home visits - involve family members or carers rather than just the primary contact. Without a lightweight caregiver record attached to the contact, mentors resort to free-text notes, which fragments data, blocks reporting, and makes follow-up unreliable. Capturing caregivers as structured records enables proper follow-up workflows, ensures emergency contacts are reachable, and underpins the formalized home-visit report which references "veien videre" decisions that often involve family. It also feeds Bufdir-relevant counts of household reach and lays groundwork for the richer Relatives Database in later phases.

Implementation Notes

Add a `caregivers` table linked one-to-many from `contacts` (per the documented data model). On mobile, expose a "Caregivers" subsection on the contact detail screen with add/edit/delete actions; reuse the standard AppTextField widgets and the form validation patterns used by the contact edit form. Persistence follows the offline-first pattern via Drift, with mutations queued to the sync outbox. Backend exposes CRUD endpoints under `/api/v1/contacts/{id}/caregivers`. Display terminology should resolve through Organization Labels where applicable (e.g. "Pårørende"). All form fields meet WCAG 2.2 AA - semantic labels, 24x24 touch targets, keyboard navigation. Sensitive fields (phone, relationship) are flagged for the readout-warning system from the accessibility area.