Progressive Digital Consent

Description

Progressive Digital Consent provides a digital workflow for capturing consents, authorizations, and medical-summary acknowledgements as part of assignment handling, with a manual paper-based fallback when digital capture is not yet feasible. The feature delivers a structured consent form, a service that records and versions consents, and a dedicated store that ties each consent to the user and to the originating assignment context. Progressive rollout means digital and manual flows coexist until digital adoption is mature.

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 63

Gradvis digitalisering av fullmakter og epikriser med manuelt fallback.

Analysis

Business Value

Blindeforbundet currently handles authorizations and medical-summary acknowledgements on paper, which slows assignment turnaround and creates physical evidence that is hard to audit, retrieve, or revoke. Moving consent capture into the app shortens the loop between dispatch and on-the-ground action, gives the organization a queryable record of who consented to what and when, and reduces the risk of lost paper. The progressive approach respects field reality: not every volunteer or contact is ready for fully digital flows from day one, so the manual fallback prevents the feature itself from blocking assignments. Over time the digital path becomes the default.

Implementation Notes

The Consent Form is a generic component-rendered form definition so new consent types can be added without code changes. The Consent Service writes immutable consent records (text version + signature/acknowledgement + timestamp) into the consents store and links them to the user_id and the originating assignment. A manual-fallback flag on each consent record marks paper-captured consents so reporting can distinguish digital from manual. Consent text is content-addressed (hash of the displayed text) so future amendments produce a new version rather than mutating history. Revocation is a new record, never a delete.