Progressive Digital Consent
Feature Detail
Description
Peer mentors and contacts provide informed digital consent for sensitive data processing - including power of attorney and medical summary sharing - directly within the app. Consent gates appear progressively before sensitive assignment data is accessed, with optional extended consents available at any time. A manual fallback path is preserved so organizations that cannot yet obtain digital consent can record paper-based consent through a coordinator override. Every consent event is logged with timestamp and version, providing a full audit trail for GDPR accountability and enabling coordinated version upgrades when consent templates change.
Sources & reasoning
Section 3.1 explicitly calls for progressive digitization of power of attorney and medical summaries with a manual fallback as a Blindeforbundet-unique requirement. This maps directly to the progressive-digital-consent feature in the blueprint. The feature belongs to the encrypted-assignments area and follows the same Fase 2 rollout, making v1.0 the correct target release per the phase-ordinal mapping (Fase 2 = second phase = v1.0).
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Processing sensitive health and personal data without explicit documented consent creates GDPR enforcement risk for all organizations using the encrypted assignment feature. Progressive digital consent replaces fragile paper-based collection with a verifiable, time-stamped digital record, reducing legal exposure and making compliance audits straightforward. The progressive model - presenting consent gates only when contextually relevant - reduces cognitive burden and increases valid consent rates compared to front-loading all consent at onboarding. The manual fallback preserves operational continuity for contacts who prefer paper, aligning with the platform's principle of incremental digitization and supporting parallel system operation during the rollout period.
Consent records are stored in assignment_consents with consent_type, version, granted_at, granted_by, and revoked_at columns. The mobile app checks the consent gate before rendering any assignment detail containing sensitive fields; if consent is absent a full-screen consent flow is presented before the content is decrypted and displayed. Consent template versions are managed server-side in organization_settings; when an org updates a template the API flags affected sessions and the app prompts re-consent on next access. A coordinator-only override marks consent as paper-collected with a mandatory audit note. GDPR-compliant withdrawal sets revoked_at and immediately hides associated sensitive data from the peer mentor's view until re-consent is granted.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.