ConsentScreen
Component Detail
Description
Presents contextual consent prompts to peer mentors immediately before they access sensitive assignment data. Each prompt is scoped to a specific data category such as personal identifiers, health records, or address information, so the mentor understands exactly what they are agreeing to. Also renders a manual fallback path for cases where digital consent cannot be completed.
consent-screen
Sources & reasoning
Line 101 explicitly calls out gradual digitization of mandates (fullmakter) and medical summaries with a manual fallback, which maps directly to progressive consent. Line 94 establishes that epikrise (medical summaries) are transmitted-a category requiring explicit GDPR consent. The area sits in Fase 2 per line 153, normalising to v1.0. Consent is a legal prerequisite for the encrypted-assignment-dispatch feature and cannot be deferred.
-
docs/source/likeperson.md · line 101Gradvis digitalisering av fullmakter og epikriser med manuelt fallback.
-
docs/source/likeperson.md · line 94Kryptert oppdragshåndtering: Sende sensitive personopplysninger (navn, adresse, epikrise) til likepersoner med leveringsbekreftelse og lesebekreftelse.
-
docs/source/likeperson.md · line 153Kryptert oppdragshåndtering | - | - | ✓ | - | ✓ | MUST (Blindeforbundet) | 2
Responsibilities
- Display data-category-specific consent prompt with the exact consent text version
- Render accept and decline actions with clear labeling of what data will be accessed
- Show manual fallback flow UI when digital consent is unavailable
- Navigate forward to assignment data view upon confirmed consent
- Display previously recorded consent history for a given assignment
Interfaces
renderConsentPrompt(dataCategory: DataCategory, consentTextVersion: string): void
onConsentAccepted(consentId: string): void
onConsentDeclined(): void
showManualFallback(assignmentId: string): void