-
Type:
Task
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
Platform
-
Dev
What this is
Two APIs. One tells registration and revisit screens whether a patient still needs to give consent. The other lets a patient change one preference.
APIs
- Pending actions: GET /consent/v1/principals/
{benRegId}/pending-actions
* Change preferences: POST /consent/v1/principals/{benRegId}/preferences
Steps
- Pending actions returns what is missing for the patient: consent missing, legacy consent, or re-consent due.
- Return nothing when consent is valid, so the visit goes ahead with no consent screen.
- Patients whose consent was taken before DPDP are marked LEGACY. Optional uses stay blocked until fresh consent is taken.
- Change preferences saves a new version for the changed purpose only. Other purposes stay the same.
Done when
- A patient with valid consent gets no pending actions.
- A patient with missing, legacy or re-consent-due consent gets a pending action.
- Changing one purpose creates a new version for that purpose only.
Source: DPDPA Compliance Proposal v14, sections 3.2.2, 6 (C4, C5, C10), 7 (H3, H4)