Consent-API: Scheduled jobs (expiry, renewal reminders, turning 18, retention clean-up, audit-log check)

XMLWordPrintable

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

      What this is
      Background jobs (Quartz) that run on their own inside Consent-API.

      Steps

      1. Expiry: End consents and doctor access when their end date passes.
      2. Renewal reminder: Remind the patient before a consent ends. If renewed, save a new version. If not, set it to EXPIRED so the check says no.
      3. Turning 18: Run daily. When a child turns 18, end the guardian link, set the status to RECONSENT_REQUIRED, and ask the patient for their own consent at the next contact.
      4. Retention clean-up: Clean up data when its retention period ends.
      5. Audit-log check: Check that the audit log has not been changed.

      Done when

      • Expired consent and access stop working.
      • A reminder goes out before the end date.
      • A child turning 18 is marked RECONSENT_REQUIRED.
      • The audit-log check reports any change.

      Waiting on: Retention periods (Legal decision, section 13).

      Source: DPDPA Compliance Proposal v14, sections 3.2.1, 6 (C9, C16)

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

                Created:
                Updated: