Relative Form
Component Detail
User Interface
medium complexity
mobile
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
Accessible form screen for registering and editing relatives such as parents, siblings, and primary caregivers. Captures identity fields, contact details, and relationship metadata while enforcing WCAG 2.2 AA requirements and offline-friendly validation feedback.
relative-form
Sources & reasoning
Source explicitly designates Pårørende-database as Fase 1 MUST for Barnekreftforeningen (line 332 and matrix line 111). Registration of relatives as distinct contact subjects is the foundational capability that all downstream relative features depend on, so it must ship in MVP.
-
docs/source/likeperson.md · line 77På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 111Pårørende database | ✓ | - | - | - | ✓ | MUST (Barnekreft) | 1
Responsibilities
- Render identity, contact, and relationship metadata fields with accessible labels and error states
- Validate input client-side before submission and surface field-level errors
- Submit registration and edit requests to the Relative Service
- Support keyboard navigation, screen reader announcements, and visible focus indicators
- Restore draft state when the user returns to the form after navigation or offline interruption
Interfaces
openRelativeForm(mode, relativeId?): void
submitRelativeForm(payload): Promise<RelativeRecord>
validateRelativeFields(payload): ValidationResult