Objective: Build Consent-API, a new microservice that becomes the single source of truth for patient consent in AMRIT. No other service stores or decides consent; all services ask Consent-API.
Scope: Service skeleton, consent tables in db_identity, and APIs for purposes, notices, consent capture, consent check, withdrawal, evidence, access requests, audit log, rights requests, and scheduled jobs.
Priority rationale: Statutory DPDP Act obligation. Current system saves consent as "Yes" regardless of patient action (section 2). All other DPDPA epics depend on this one.
Dependencies: Decision on evidence file storage location; validity and retention periods; legal review of clause references.