Consent-API: Purposes and Notices (list of data uses, notice versions per language)

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: High
    • 3.14
    • Affects Version/s: None

      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

      1. Save each purpose with its legal basis, whether it is mandatory or optional, and how long it is valid.
      2. Save each notice as a version, with text and audio for each language.
      3. Record reviewer sign-off before a notice version is used.
      4. Let the Admin screens add and change purposes, notice versions, translations and audio.
      5. Give all screens the active notice through: GET /consent/v1/notices/active?context&lang
      6. 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.
      7. 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)

              Assignee:
              Vanitha S
              Reporter:
              Shivani Garg
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: