🏠 Overview › 🎯 Features ›🎯 Encrypted Assignment Dispatch & Tracking

Encrypted Assignment Dispatch & Tracking

Feature Detail

high complexity extracted Encrypted Assignment Management Confidence: 100%
7
Components
58
Shared
0
User Stories
Yes
Analyzed

Description

This feature enables coordinators to securely dispatch sensitive assignment information — including personal details such as name, address, and medical summaries — to peer mentors via end-to-end encrypted messaging. The system tracks assignment status through the full lifecycle from dispatch to completion, providing read and delivery confirmations. It consolidates encrypted assignment dispatch, assignment status tracking, and sensitive data messaging into a single cohesive workflow that meets Norwegian data protection requirements.

User Flow

Encrypted Assignment Dispatch & Tracking user flow
Click to expand

Analysis

Business Value

Blindeforbundet requires the ability to transmit sensitive personal data — including epikrise excerpts and home addresses — to peer mentors for home visit preparation. Doing this via email or phone is insecure and non-compliant with GDPR. End-to-end encrypted dispatch with delivery and read confirmation ensures accountability, auditability, and legal compliance. Coordinators gain real-time visibility into which assignments have been received and acknowledged, eliminating manual follow-up calls and reducing the risk that peer mentors begin visits without fully reading the assignment brief. This is a hard blocker for Blindeforbundet adoption.

Implementation Notes

End-to-end encryption must be implemented using a proven asymmetric key exchange protocol (e.g., X25519 + AES-GCM) with per-user key pairs stored in secure device storage. The Flutter client encrypts messages locally before transmission; the backend stores only ciphertext and metadata. Push notification infrastructure delivers assignment alerts without exposing content in the notification payload. The assignment_status_logs table tracks state transitions (dispatched → delivered → read → acknowledged). Read confirmation is implemented via a mandatory in-app acknowledgement action, not passive read receipt, ensuring the peer mentor has consciously reviewed the assignment before the coordinator is notified.

Components (65)

User Interface (4)

ui Assignment Compose Screen high ui Assignment Detail Screen high ui Assignment List Screen medium ui Read Confirmation Widget medium

Service Layer (2)

service Assignment Status Tracker medium service Encrypted Messaging Service high

Data Layer (1)

data Assignment Repository medium

Shared Components

These components are reused across multiple features

Infrastructure (20)

infrastructure JWT Infrastructure medium Shared infrastructure JWT Infrastructure low Shared infrastructure Auth Middleware medium Shared infrastructure Report API Middleware low Shared infrastructure Report Access Guard low Shared infrastructure Approval Audit Logger low Shared infrastructure End-to-End Encryption Infrastructure high Shared infrastructure Email Delivery Infrastructure low Shared infrastructure Invitation Token Infrastructure medium Shared infrastructure Signed URL Provider low Shared infrastructure Multi-Tenancy Infrastructure high Shared infrastructure Calculator Export Infrastructure medium Shared infrastructure Request & Response Interceptors high Shared infrastructure Design Token System medium Shared infrastructure Semantic Labels Infrastructure medium Shared infrastructure Connectivity Infrastructure low Shared infrastructure Local Database Infrastructure high Shared infrastructure Secure Storage Infrastructure medium Shared infrastructure Connection Pool Infrastructure medium Shared infrastructure Database Migration Infrastructure medium Shared

User Stories

No user stories have been generated for this feature yet.