SpecsModelExploreRequirements
SpecsModelExploreRequirements
Consent Service
Overview
Guide
Consent Service API
Twin streams
Links and Communications
IDproduct.governance.consent_service
DescriptionConsent records and policy decisions.
Keyconsent_service
Typemicroservice:service
Statusactive
TeamGovernance & Audit
Owner
governance@healthcare.example
TechnologiesGo, PostgreSQL, OpenSearch
Tags
Table of contents
Guide
Consent Service
Internal structure
Components
Decision path
Evaluate
Enforce
API
Related workflow
Consent Service API
Links and Communications
Requirements

Attributes

defaultdeny research
reloadhot

Guide

Consent Service

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.

Internal structure

Could not build diagram for model "example-healthcare".

Components

Consent Repository

Persists patient consent documents.

Policy Engine

Evaluates access requests against consent.

Decision path

Store

New consent lands in the Consent Repository.

Evaluate

The Policy Engine answers allow/deny for each purpose of use.

Enforce

FHIR Consent Check and de-id pipeline consult the same engine.

API

Consent CRUD and policy evaluation endpoints are documented on the Overview tab.

Contract

Consent versions are immutable; updates create a new version row.

Related workflow

Consent Service API

Links and Communications

1 workflow

Related Workflows(1)

WorkflowModelParticipant idParticipant label
Consent update

governance.consent-update

example-healthcareproduct.governance.consent_serviceConsent service

Requirements