Proxy Reporting Service
Component Detail
Service Layer
medium complexity
backend
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
Backend service that accepts proxy-registered activity submissions from coordinators and persists them attributed to the target peer mentor. Enforces that the submitting user holds the coordinator role and tags each record with proxy metadata for auditing and Bufdir reporting.
proxy-reporting-service
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
- Authorise that the caller has coordinator role and is allowed to register on behalf of the target peer mentor
- Persist the activity attributed to the peer mentor with a proxy_registered flag and the coordinator's id as registrar
- Reuse the standard activity validation rules so proxy entries match direct entries
- Emit audit log entries for every proxy submission for traceability
- Return the persisted activity record or structured validation errors to the caller
Interfaces
submitProxyActivity(coordinatorId, peerMentorId, activity): Activity
listEligiblePeerMentors(coordinatorId): PeerMentor[]
getProxyActivityAudit(activityId): AuditEntry