Skip to content

Consent Families Value set

Canonicalhttps://fhir.apps.health/ValueSet/nexus-consent-families
Statusdraft · 1.33.0
SourceFSH · JSON

The Consent families this guide defines. Bound required from the family slice of Consent.category so that a consumer can discriminate before interpreting, and can reject a resource whose family it does not recognise rather than guess.

All 3 codes from this system, defined by this specification.

CodeDisplayDefinition
appApplication consentWhether the patient agreed to share their record with a named third-party application. `provision.type = permit` on the root is agreement, `deny` is refusal. Carried by the App Consent profile. Refusal used to be a nested deny and a grant the absence of one, which meant a truncated resource read as a grant.
itemItem consentThe patient's answer for one catalogue item -- email, SMS, AI scribe. `provision.type = permit` is yes, `deny` is no or withdrawn. Carried by the Item Consent profile. This family used to carry its answer in `status` alone, which is the divergence this guide removed: it made an active item consent mean permission while an active privacy directive means a restriction in force.
privacy-directivePrivacy directiveA standing patient restriction on the collection, use or disclosure of their personal health information -- what PHIPA calls a lockbox. `provision.type = deny` on the root is the restriction; `status = active` says only that the record is operative. Carried by the Privacy Directive profile.