Consent Service
Component Detail
Service Layer
medium complexity
backend
0
Dependencies
0
Dependents
0
Entities
0
Integrations
Description
Backend service that orchestrates progressive digital consent workflows, validating consent submissions and linking them to assignments. Coordinates with the Consent Store for persistence and exposes APIs to drive the Consent Form and downstream assignment processing.
consent-service
Sources & reasoning
Source §3.1 calls for gradual digitalization of authorizations and medical summaries with manual fallback - the canonical area taxonomy maps this to Progressive Digital Consent inside Encrypted Data Assignments. The blueprint marks this feature as Growth & Engagement, matching the gradual/optional rollout framing in §5 Fase 3.
-
docs/source/likeperson.md · line 63Gradvis digitalisering av fullmakter og epikriser med manuelt fallback.
Responsibilities
- Validate consent submissions against assignment context and consent type
- Link consent records to assignments and dispatch state
- Manage paper-fallback workflow tracking when digital consent is not used
- Enforce versioning of consent text so historical decisions remain auditable
- Expose consent status queries to other backend services
Interfaces
recordConsent(assignmentId, consentPayload): ConsentRecord
getConsentStatus(assignmentId): ConsentStatus
registerPaperFallback(assignmentId, reason): FallbackRecord