-
Type:
Story
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
FLW Mobile App
-
All
What this is
Make the FLW app check consent before it reads or writes beneficiary data.
Steps
- Find each FLW screen and FLW API call that reads or writes beneficiary data (household, beneficiary, child, ANC/PNC, immunisation and other modules). [TBD/CLARIFICATION REQUIRED] Final list of modules to be confirmed by the FLW team.
- Add the consent check (AMM-2508) to each, so the purpose is checked before data is shown or saved.
- If not allowed, show the reason to the FLW user (CONSENT_NOT_FOUND, CONSENT_DENIED, CONSENT_WITHDRAWN, CONSENT_EXPIRED, RECONSENT_REQUIRED, GUARDIAN_REQUIRED) and do not show or save the data.
- Reminders and notifications run the consent check before every send, so they stop the moment consent is withdrawn.
Done when
- Every FLW screen and API that reads or writes beneficiary data has the consent check.
- Without consent, the data is not shown or saved and the reason is shown.
- No reminder or notification is sent after consent is withdrawn.
Dependencies: AMM-2508 (consent check API and library), AMM-2529.
Open questions: [TBD/CLARIFICATION REQUIRED]
- Decision D-04: what happens when Consent-API is down (block optional uses, allow treatment, flag it)? How does this work in the FLW app?
- Which purposes apply to which FLW modules?
Source: DPDPA Compliance Proposal v14, section 4. Mirrors AMM-2531.