Consent and DSAR Operations

Owner steps

The deployment Privacy Owner configures the research protocol context name, confirms that practitioner accounts belong to the correct organization, and trains operators to record consent before using subject-scoped analysis.

Practitioners record consent with POST /api/consents using the subject pseudonym, research context, status, and a reference to the signed source document. Withdrawal is recorded as a new withdrawn consent record; previous records remain immutable for audit traceability.

For subject access requests, the Privacy Owner verifies the requester identity, runs GET /api/dsar/export?subject_id=<subject-pseudonym> while logged in to the requester organization, reviews the returned consent and audit records, and stores the disclosure package in the deployment's controlled privacy register.

Legal placeholders

Legal sign-off is still required per deployment for the consent text, identity verification procedure, response deadline, and any redaction before disclosure. Do not treat the software export as legal approval to release records.