-
Type:
Task
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
Sprint 60
-
Platform
-
Dev
What this is
Keep the list of data uses (purposes) and the consent notice in every language, so every screen shows the right notice.
Steps
- Save each purpose with its legal basis, whether it is mandatory or optional, and how long it is valid.
- Save each notice as a version, with text and audio for each language.
- Record reviewer sign-off before a notice version is used.
- Let the Admin screens add and change purposes, notice versions, translations and audio.
- Give all screens the active notice through: GET /consent/v1/notices/active?context&lang
- When a new notice version adds a new purpose or recipient (a material change), mark the affected consents as RECONSENT_REQUIRED so patients are asked again at their next contact.
- When a new notice version only fixes a small error (like a typo), do not ask patients again.
Done when
- A screen asking for a context and language gets the latest approved notice.
- A material change marks affected consents as RECONSENT_REQUIRED.
- A small correction does not.
Waiting on: Grace period for re-consent (decision D-05).
Source: DPDPA Compliance Proposal v14, sections 3.1, 3.2.1, 3.2.2, 6 (C14, C15)