RelativeRegistrationScreen
Component Detail
User Interface
medium complexity
mobile
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
A mobile form screen that allows peer mentors and coordinators to register a new relative contact for a support case. It collects contact details, relationship role, and case association, then submits the record via RelativeService. The screen validates required fields inline before submission.
relative-registration-screen
Sources & reasoning
Source lines 121-122 explicitly define the relative registration requirement as unique to Barnekreftforeningen. Line 161 (priority matrix) marks it MUST with Phase 1. Line 438 reconfirms Fase 1 MUST status. Phase 1 maps to MVP by ordinal. This is the foundational record-creation step the other two relatives features depend on.
-
docs/source/likeperson.md · line 121-122På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 161Pårørende database | ✓ | - | - | - | ✓ | MUST (Barnekreft) | 1
-
docs/source/likeperson.md · line 438Pårørende-database er Fase 1 MUST for Barnekreftforeningen
Responsibilities
- Render form fields for name, contact details, relationship role, and case association
- Validate required fields and show inline error messages before submission
- Invoke RelativeService to persist the new relative record
- Display success or error feedback after submission
- Navigate back to the contact list on successful registration
Interfaces
submitRelative(form: RelativeFormData): Promise<void>
validateForm(form: RelativeFormData): ValidationResult
onCaseSelect(caseId: string): void