-
Type:
Task
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
Sprint 60
-
Platform
-
Dev
What this is
Save the patient's yes or no for each purpose, along with how consent was taken and the proof. Let screens read a patient's current consents.
APIs
- Save consent: POST /consent/v1/consents
- Get patient's consents: GET /consent/v1/principals/
{benRegId}
/consents
Steps
- Save a yes or no for each purpose, with the mode, proof, worker, device and time.
- Ask for the proof that matches the mode:
Mode Proof saved Self-read Notice version, language, text hash, time, device Read aloud Health worker ID + confirmation tick, audio played to end Voice clip 30 to 60 second recording + hash Witnessed Witness name and relationship Signature / thumb + photo Images + hash OTP OTP verified time, masked number Verbal on call Call ID + recording link - Save declined purposes as DENIED.
- If a mandatory purpose is declined, save it as DENIED and collect no data.
- Save consent in the language that was actually shown.
- For a child or a person with a disability, save consenting_party = GUARDIAN with the guardian link.
- If the same request is sent twice (double tap or retry), save only one record and send only one SMS.
- If the same patient is changed from two places at once, reject the second save so the user reloads and confirms.
- Send an SMS confirmation when consent is saved.
Done when
- Each purpose has its own saved decision.
- Each mode is refused without its matching proof.
- Sending the same request twice creates one record.
- The second of two saves at the same time is rejected.
Source: DPDPA Compliance Proposal v14, sections 3.1, 3.2.1, 3.2.2, 6 (C1, C2, C3, C6, C17, C18, C20)