# Record Consent - Verifiable Health Link v0.0.2-current

* [**Table of Contents**](toc.md)
* [**Artifacts Summary**](artifacts.md)
* **Record Consent**

## Requirements: Record Consent 

| | |
| :--- | :--- |
| *Official URL*:https://profiles.ihe.net/ITI/VHL/Requirements/RecordConsent | *Version*:0.0.2-current |
| Active as of 2026-03-12 | *Computable Name*:RecordConsent |

 
The [VHL Sharer](ActorDefinition-VHLSharer.md) SHALL record the consent granted by a [VHL Holder](ActorDefinition-VHLHolder.md) to authorize the sharing of their health data via a Verified Health Link (VHL). This consent confirms that the Holder agrees to the creation of a VHL and its use by authorized [VHL Receivers](ActorDefinition-VHLReceiver.md) to access specific health documents. 
In this requirement, the VHL Sharer acts as a Consent Recorder, as defined in the [Privacy Consent on FHIR (PCF)](https://profiles.ihe.net/ITI/PCF/index.html) profile. Specifically, the Sharer SHALL initiate the [Access Consent - ITI-108](https://profiles.ihe.net/ITI/PCF/ITI-108.html) transaction to formally capture the Holder's consent. 
The ITI-108 transaction SHOULD be invoked as part of the actions triggered by a Generate VHL request, particularly when legal, jurisdictional, or organizational policy requires explicit, recorded consent prior to enabling document sharing. 
This requirement enables lawful, transparent sharing of personal health information across organizations and trust domains. 

* Statements: Contact Email
  * Steps in the requirement:1. ** [ SHOULD ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Use ITI 108 **:ITI-108 Transaction is invoked by VHL Sharer.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Record Consent **:Record consent as a FHIR Consent resource that documents
* the data subject(VHL Holder)
* The purpose of use
* The authorized data recipients (i.e., permitted VHL Receivers)
* The scope of data (e.g., specific documents or resource types)
* The duration or validity period of the consent

1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Update Consent **:VHL Sharer SHALL support updating of Consent by the VHL Holder, which may include even revocation of consent.: No contact email has been registered.
* Statements: Jurisdiction
  * Steps in the requirement:1. ** [ SHOULD ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Use ITI 108 **:ITI-108 Transaction is invoked by VHL Sharer.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Record Consent **:Record consent as a FHIR Consent resource that documents
* the data subject(VHL Holder)
* The purpose of use
* The authorized data recipients (i.e., permitted VHL Receivers)
* The scope of data (e.g., specific documents or resource types)
* The duration or validity period of the consent

1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Update Consent **:VHL Sharer SHALL support updating of Consent by the VHL Holder, which may include even revocation of consent.: 
* Statements: Derived from
  * Steps in the requirement:1. ** [ SHOULD ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Use ITI 108 **:ITI-108 Transaction is invoked by VHL Sharer.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Record Consent **:Record consent as a FHIR Consent resource that documents
* the data subject(VHL Holder)
* The purpose of use
* The authorized data recipients (i.e., permitted VHL Receivers)
* The scope of data (e.g., specific documents or resource types)
* The duration or validity period of the consent

1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Update Consent **:VHL Sharer SHALL support updating of Consent by the VHL Holder, which may include even revocation of consent.: This requirement is not derived from another requriement.
* Statements: Derivatives
  * Steps in the requirement:1. ** [ SHOULD ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Use ITI 108 **:ITI-108 Transaction is invoked by VHL Sharer.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Record Consent **:Record consent as a FHIR Consent resource that documents
* the data subject(VHL Holder)
* The purpose of use
* The authorized data recipients (i.e., permitted VHL Receivers)
* The scope of data (e.g., specific documents or resource types)
* The duration or validity period of the consent

1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Update Consent **:VHL Sharer SHALL support updating of Consent by the VHL Holder, which may include even revocation of consent.: This requirement has the following derivatives:
* Statements: Participating Actors
  * Steps in the requirement:1. ** [ SHOULD ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Use ITI 108 **:ITI-108 Transaction is invoked by VHL Sharer.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Record Consent **:Record consent as a FHIR Consent resource that documents
* the data subject(VHL Holder)
* The purpose of use
* The authorized data recipients (i.e., permitted VHL Receivers)
* The scope of data (e.g., specific documents or resource types)
* The duration or validity period of the consent

1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Update Consent **:VHL Sharer SHALL support updating of Consent by the VHL Holder, which may include even revocation of consent.: * [VHL Sharer](ActorDefinition-VHLSharer.md)


