Clinical Intelligence StandardsVersion 0.2

Functional standard / Governance / PatientInstance

Consent

Permission for one scope: treatment, data sharing, AI, procedure, communication, or research.

Kind
consent
Collection
/v1/consents
Initial state
requested
Classification
Operational

Scope and usage

Granted by the patient or by a guardian within the relationship's scopes. Sharing a document checks data_sharing. An agent checks ai.

Boundaries and relationships

Resource content

Elements this resource adds. It also carries the Instance, including patient_id.

NameCard.TypeFlagsDescription
consent_scope1..1codeBOne of the six scopes.
granted_by1..1codeBself or guardian.
guardian_id0..1id—Required in practice when granted_by is guardian.
document_id0..1id—Signed form, a ClinicalDocument.
valid_until0..1dateTime—Optional end.
details0..1string—What was explained.

State machine

requested → granted, refused. granted → withdrawn, expired.

Frozen: refused, withdrawn, and expired.

Terminology bindings

ElementStrengthValues
consent_scoperequiredtreatment | data_sharing | ai | procedure | communication | research

Invariants

Operations

MethodPathMeaning
GET/v1/consentsList consent. Filter by patient_id, status, and where the model has them, encounter_id or definition_key.
POST/v1/consentsCreate a consent. Body is the resource minus harness-owned elements.
GET/v1/consents/{id}Read one consent.
PATCH/v1/consents/{id}Update elements that are not immutable, frozen, or harness-owned.
POST/v1/consents/{id}/transitionMove status. Body is { to, reason }. A gated move returns 202 and an Approval.

Example

{ "patient_id": "pat_…", "consent_scope": "ai", "granted_by": "self" }