medium complexity extracted Encrypted Data Assignments Confidence: 100%
3
Components
4
Shared
0
User Stories
Yes
Analyzed

Description

Progressive Digital Consent presents peer mentors with contextual consent prompts at the moment they are about to access sensitive assignment data, rather than requiring a single upfront blanket agreement. Each consent step is scoped to the specific data category being disclosed-personal identifiers, health records, address information-so peer mentors understand precisely what they are agreeing to. Consent records are stored server-side with timestamps and a reference to the exact consent text version shown. A manual fallback path supports cases where digital consent cannot be obtained, preserving Blindeforbundet's gradual digitization approach.

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 101
    Gradvis digitalisering av fullmakter og epikriser med manuelt fallback.
  • docs/source/likeperson.md · line 94
    Kryptert oppdragshåndtering: Sende sensitive personopplysninger (navn, adresse, epikrise) til likepersoner med leveringsbekreftelse og lesebekreftelse.
  • docs/source/likeperson.md · line 153
    Kryptert oppdragshåndtering | - | - | ✓ | - | ✓ | MUST (Blindeforbundet) | 2

Analysis

Business Value

Norwegian GDPR implementation and health data regulations require explicit, informed consent before sensitive personal information such as medical summaries can be shared with peer mentors. A progressive, context-driven consent model improves both legal defensibility and user comprehension compared to a monolithic terms-and-conditions flow that users routinely skip-read. For Blindeforbundet, this feature is the legal gateway that makes encrypted assignment dispatch permissible: without a valid consent record, assignments cannot be lawfully transmitted. Contextual consent also reduces the risk of peer mentors inadvertently consenting to broader data access than they intend, strengthening trust in the platform among users who may have limited digital literacy.

Implementation Notes

Before the encrypted assignment detail renders, the client queries the backend for an active consent record covering the relevant data categories. If no valid record exists, a consent screen is presented with plain-language Norwegian copy, explicit accept and decline actions, and a reference to the full privacy policy. On acceptance the client posts a signed consent record (peer mentor ID, consent version hash, timestamp) to the server. The consent gate integrates as middleware in the assignment detail navigation path in Flutter so it cannot be bypassed. Consent withdrawal must invalidate the stored record and prevent further assignment access until reconsent. The entire consent UI must pass WCAG 2.2 AA including screen reader semantic labels, given Blindeforbundet's visually impaired users. A manual fallback flag on the assignment record allows coordinators to mark paper-based consent obtained outside the app.

User Stories

No user stories have been generated for this feature yet.