User Interface medium complexity mobile
0
Dependencies
0
Dependents
3
Entities
0
Integrations

Description

Shows the full decrypted contents of a single assignment to the peer mentor after authentication, including recipient name, address, and medical summary. Records a read confirmation event the moment the peer mentor opens the screen. Allows the peer mentor to acknowledge contact established and view dispatch metadata.

Feature: Encrypted Assignment Dispatch

assignment-detail-screen

Sources & reasoning

Source lines 94-95 directly specify end-to-end encrypted dispatch with delivery/read confirmation and a 10-day reminder. Line 153 classifies this MUST for Blindeforbundet in Fase 2 of the priority matrix, and line 345 repeats it as Fase 2 critical in the roadmap. Fase 2 normalises to v1.0. The feature is the core unlock for Blindeforbundet's digital workflow and cannot be deferred.

  • docs/source/likeperson.md · line 94-95
    Kryptert oppdragshåndtering: Sende sensitive personopplysninger (navn, adresse, epikrise) til likepersoner med leveringsbekreftelse og lesebekreftelse. Statusoversikt over åpne oppdrag. Automatisk påminnelse etter 10 dager dersom kontakt ikke er oppr
  • docs/source/likeperson.md · line 153
    Kryptert oppdragshåndtering | - | - | ✓ | - | ✓ | MUST (Blindeforbundet) | 2
  • docs/source/likeperson.md · line 345
    Kryptert oppdragsutsendelse med statussporing (Blindeforbundet-kritisk)

Responsibilities

  • Decrypt and render sensitive assignment fields on authenticated open
  • Trigger read confirmation event on first screen open
  • Display dispatch timestamp, coordinator identity, and assignment status
  • Provide contact-acknowledged action to update assignment state
  • Handle decryption failure with graceful error messaging

Interfaces

loadAssignment(assignmentId: string): Promise<DecryptedAssignment>
recordReadConfirmation(assignmentId: string): Promise<void>
acknowledgeContact(assignmentId: string): Promise<void>
onDecryptionError(error: CryptoError): void

Related Data Entities (3)

Data entities managed by this component