clinik.consents namespace manages FHIR Consent resources — patient agreements to privacy policies, treatment plans, research participation, and advance directives. Each consent records the scope of agreement, the policy it references, optional verification details, and provision rules that specify what is permitted or denied.
sign
Record a new consent.patientId, scope, and category are required. This method is equivalent to create but uses the domain-specific name to reflect the consent-gathering workflow.
ID of the patient granting or denying consent.
Scope of the consent. Accepted values:
patient-privacy, research, treatment, adr (advance directive).Consent category code, for example
hipaa-notice, treatment-consent, research-participation. Accepts a single string or an array.Consent status. Accepted values:
draft, proposed, active, rejected, inactive. Defaults to active.ISO 8601 datetime when consent was given or denied.
ID of the practitioner or patient who is agreeing.
ID of the custodian organization.
URI of the policy the consent references.
Verification details:
verified (boolean), verifiedWith (patient or practitioner ID), and verificationDate (ISO 8601).Provision rules that qualify the consent. Includes
type (permit or deny), optional period, and purpose codes.Examples
Consent scopes
| Scope | Description |
|---|---|
patient-privacy | Privacy and data-sharing policies (HIPAA notices) |
research | Research study participation |
treatment | Authorization for treatment or procedures |
adr | Advance directive (living will, DNR, etc.) |
read
Fetch a single consent by ID.update
Partially update a consent. Commonly used to revoke active consents or update verification records.Examples
delete
Permanently delete a consent record.search
Search consents with optional filters and cursor pagination.Filter by patient.
Filter by consent status.
Return consents dated on or after this date.
Return consents dated on or before this date.
Results per page. Maximum is
100.Pagination cursor from a previous response.