🏠 Overview › 🧩 Components ›🧩 CaregiverSection

CaregiverSection

Component Detail

User Interface medium complexity mobile
0
Dependencies
0
Dependents
0
Entities
0
Integrations

Description

Renders the caregiver list within the contact detail screen as a dedicated collapsible section. Displays each caregiver's name, relationship type, and contact details with add, edit, and delete actions gated by role. Applies tenant-specific Organization Label terminology (e.g. Pårørende, Foresatte) without code changes.

Feature: Caregiver & Next-of-Kin

caregiver-section

Sources & reasoning

Lines 121, 161, and 438 form a clear provenance chain: the requirement is stated (121), marked MUST in Phase 1 (161), and explicitly restated as Phase 1 MUST (438). Blueprint places this in Contacts (not Relatives Database) because it concerns caregivers linked to existing contacts, not a standalone relatives registry. Phase 1 = MVP by ordinal mapping.

  • 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 sak.
  • PĂĄrørende database | âś“ | - | - | - | âś“ | MUST (Barnekreft) | 1
  • PĂĄrørende-database er Fase 1 MUST for Barnekreftforeningen

Responsibilities

  • Render list of caregivers for the active contact with name, relationship, and contact info
  • Show add/edit/delete action controls only to roles with write permission
  • Display Organization Label terminology from tenant configuration for section and field labels
  • Handle empty state and loading state during sync
  • Emit user actions (add, edit, delete) to CaregiverService

Interfaces

render(contact: Contact, caregivers: Caregiver[], userRole: Role): void
onAddCaregiver(): void
onEditCaregiver(caregiverId: string): void
onDeleteCaregiver(caregiverId: string): void