The Consent Service stores patient consent documents and answers policy decisions for FHIR reads, research exports and portal features.
Hot reload
Portal consent updates reload policy without redeploying gateways or pausing ingestion.
Could not build diagram for model "example-healthcare".
Persists patient consent documents.
Evaluates access requests against consent.
New consent lands in the Consent Repository.
The Policy Engine answers allow/deny for each purpose of use.
FHIR Consent Check and de-id pipeline consult the same engine.
Consent CRUD and policy evaluation endpoints are documented on the Overview tab.
Contract
Consent versions are immutable; updates create a new version row.