Proxy Register Screen
Component Detail
User Interface
medium complexity
mobile
0
Dependencies
0
Dependents
2
Entities
0
Integrations
Description
Mobile screen used by coordinators to log an activity on behalf of a selected peer mentor. Mirrors the standard activity entry form but adds a peer mentor selector at the top and a visible proxy-registration indicator. Submits the entry attributed to the chosen peer mentor with a proxy flag for audit.
proxy-register-screen
Sources & reasoning
Matrix lists proxy-rapportering at SHOULD HAVE / Fase 2, and §2.4 names NHF+HLF+Barnekreft as primary drivers. Maps directly to the Proxy Register Screen + Proxy Reporting Service components in the blueprint.
-
docs/source/likeperson.md · line 50-51Koordinator kan rapportere på vegne av andre / bulkregistrering (NHF + HLF + Barnekreftforeningen) Ikke alle likepersoner vil eller kan bruke appen. Koordinatorer må ha mulighet til å registrere aktivitet på vegne av sine likepersoner
-
docs/source/likeperson.md · line 101Bulkregistrering / proxy-rapportering | ✓ | ✓ | - | ✓ | ✓ | SHOULD HAVE | 2
Responsibilities
- Present a searchable selector of peer mentors the coordinator is authorised to register on behalf of
- Render the activity entry form with contact, date, time, duration and activity type fields
- Display a clear visual indicator that the entry is being made as a proxy registration
- Validate input client-side and surface inline errors before submission
- Submit the proxy activity payload to the Proxy Reporting Service and confirm the result to the user
Interfaces
openProxyRegister(): void
selectPeerMentor(peerMentorId): void
submitProxyActivity(form): SubmissionResult
Related Data Entities (2)
Data entities managed by this component