Confidentiality Declarations
Feature Detail
Description
Confidentiality Declarations provides a structured digital sign-off flow for peer mentors acting as drivers, requiring them to formally acknowledge confidentiality obligations before carrying out assignments involving individuals with sensitive health or personal information. Blindeforbundet requires this declaration for all driver peer mentors. The feature presents the declaration text in a scrollable view, records the peer mentor's explicit acknowledgement with a timestamp, and links the signed record to the associated activity. Coordinators can view declaration status per peer mentor from the Admin Web Portal to confirm compliance before dispatching sensitive assignments.
Sources & reasoning
Section 2.1 explicitly names confidentiality declarations as a Blindeforbundet requirement within the expense and reimbursement context alongside driver honoraria. Phase 2 placement in the priority matrix maps to target_release v1.0 per the ordinal normalization rule.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Peer mentors who transport individuals with sensitive conditions are legally and ethically required to acknowledge confidentiality obligations before each engagement. Relying on paper declarations creates compliance risk: records are lost, undated, or not linked to the specific assignment they cover - a potential GDPR exposure for the organisation. Digitising the sign-off flow ensures declarations are timestamped, versioned, and linked unambiguously to the relevant person and activity. This directly satisfies Blindeforbundet's driver workflow requirements and provides an auditable compliance record that coordinators can inspect at any time from the Admin Web Portal without manual record-keeping.
The declaration screen is presented as a conditional step in the expense flow when the selected expense type includes a driver honorarium component. Declaration content is stored server-side and versioned so that changes to the legal text are tracked; each `confidentiality_declarations` record includes the declaration version hash alongside user ID and timestamp. Flutter renders a scrollable declaration text with a mandatory confirmation checkbox that must be reached by scrolling before the submit action becomes active. Pending declarations are queued in the Drift mutation outbox for sync when connectivity is restored, ensuring the sign-off step works fully offline.
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.