Consent

This topic describes information for the Consent resource.

To interact with the REST endpoints in the Consent resource, see Consent.

Overview

The Consent resource can be used to represent consents.

The Consent resource is currently limited to representing people who are authorized to view a patient's data. For this reason, consent type, scope, category, policy rule, actor role, action, and purpose are always set to values related to consent for electronic health record (EHR) sharing. The actors on the contract are the related people who are authorized to view the patient's data. An example is a consent authorizing a mother (actor) to view her child's data (patient).

Note:

The examples provided here are non-normative and replaying them in the public sandbox is not guaranteed to yield the results shown on the site.

Fields

• Consent ID

• Status

• Scope (Privacy Consent)

• Category (Patient Consent)

• Patient

• Policy Rule (Consent given for electronic record sharing (finding))

• Provision

• Type (Permit)

• Period

• Actor (RelatedPerson)

• Actor Role (Authorized Representative)

• Action (Access and Correct)

• Purpose (Purpose of Use)

Terminology Bindings

• Consent.status

  Description: Indicates the state of the consent.

  Details: Request Status

  System: http://hl7.org/fhir/consent-state-codes

• Consent.scope

  Description: The four anticipated uses for the Consent resource.

  Details: Request Scope

  System: http://terminology.hl7.org/CodeSystem/consentscope

• Consent.category

  Description: A classification of the type of consents found in a consent statement.

  Details: Request Category

  System: http://loinc.org

• Consent.policyRule

  Description: Regulatory policy examples.

  Details: Request PolicyRule

  System: http://snomed.info/sct

• Consent.provision.type

  Description: How a rule statement is applied, such as adding additional consent or removing consent.

  Details: Provision Type

  System: http://hl7.org/fhir/consent-provision-type

• Consent.provision.actor.role

  Description: How a rule statement is applied, such as adding additional consent or removing consent.

  Details: Provision Actor Role

  System: http://terminology.hl7.org/CodeSystem/contractsignertypecodes

• Consent.provision.action

  Description: Detailed codes for the consent action.

  Details: Provision Action

  System: http://terminology.hl7.org/CodeSystem/consentaction

• Consent.provision.purpose

  Description: The purposes of use that are controlled by this exception. If more than one label is specified, operations must have all the specified labels.

  Details: Provision Purpose

  System: http://terminology.hl7.org/CodeSystem/v3-ActReason