A record of a healthcare consumer’s policy choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.

Unique identifier for this copy of the Consent Statement.

This identifier is identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.

Indicates the current state of this consent.

The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.

This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

A classification selector of the type of consents found in the statement. This element supports indexing and retrieval of consent statements. being presented: ADR, Privacy, Treatment, Research. This list is now extensible.

The patient/healthcare consumer to whom this A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent applies. statements.

Relevant time or time-period when The patient/healthcare consumer to whom this Consent is applicable. consent applies.

This can be a subset of Commonly, the period of patient the original statement. consent pertains to is the author, but for young and old people, it may be some other person.

When this Consent was issued / created / indexed.

This is not the time of the original consent, but the time that this statement was made or derived.

Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions.

Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.

The organization that manages the consent, and the framework within which it is executed.

The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document.

The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.

The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.

Entity or Organization having regulatory jurisdiction or accountability for  enforcing enforcing policies pertaining to Consent Directives.

The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.

This element is for discoverability / documentation, documentation and does not modify or qualify the policy rules.

A referece reference to the specific base computable regulation or policy.

Might be a unique identifier of a policy set in XACML, or other rules engine.

If the policy reference policyRule is not known, the resource cannot absent, computable consent would need to be processed. Where constructed from the reference is absent, there is no particular policy other than what is expressed directly in elements of the consent Consent resource.

The context of the activities Whether a user is taking - why the user is accessing treatment instruction (e.g. artificial respiration yes or no) was verified with the data - that are controlled by this consent. patient, his/her family or another authorized person.

Clinical or Operational Relevant period of time that bounds Has the data controlled by this consent. instruction been verified.

How Who verified the resource reference is interpreted when testing consent restrictions. instruction (Patient, Relative or other Authorized Person).

A reference to a specific resource that defines which resources are covered by this consent. Date verification was collected.

An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.

Action to take - permit or deny - when the exception rule conditions are met. Not permitted in root rule, required in all nested rules.

The timeframe in this exception rule is valid.

Who or what is controlled by this Exception. rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').

How the individual is involved in the resources content that is described in the exception.

The resource that identifies the actor. To identify a actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers').

Actions controlled by this Exception. Rule.

Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.

A set security label, comprised of 0..* security labels that label fields (Privacy tags), which define which resources are controlled by this exception. If more than one label is specified, all resources must have all the specified labels.

If the consent specifies a security label of "R" "R" then it applies to all resources that are labeled "R" "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. Not all When the purpose of use tag is on the security labels make sense for data, access request purpose of use in this element (may define a narrower value set?). shall not conflict.

The context of the activities a user is taking - why the user is accessing the data - that are controlled by this exception. rule.

E.g. if When the purpose of use tag is 'research', then the operational context must be research, in order for on the consent to apply. Not all data, access request purpose of the security labels make sense for use in this element (may define a narrower value set?). shall not conflict.

The class of information covered by this exception. rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to.

Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.

If this code is found in an instance, then the exception rule applies.

Typical use of this is a Document code with class = CDA.

Clinical or Operational Relevant period of time that bounds the data controlled by this exception. rule.

This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.

The resources controlled by this exception, rule if specific resources are referenced.

How the resource reference is interpreted when testing consent restrictions.

A reference to a specific resource that defines which resources are covered by this consent.

Rules which provide exceptions to the base rule or subrules.