Verifiable Health Link
0.0.2-current - ci-build International flag

Verifiable Health Link, published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.2-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.VHL/ and changes regularly. See the Directory of published versions

: Record Consent - XML Representation

Active as of 2025-09-19

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="RecordConsent"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements RecordConsent</b></p><a name="RecordConsent"> </a><a name="hcRecordConsent"> </a><p>These requirements apply to the actor <a href="ActorDefinition-VHLSharer.html">VHL Sharer</a></p><table class="grid"><tr><td><b><a name="record-consent"> </a></b>Record Consent</td><td>SHALL</td><td><div><p>Record consent as FHIR Consent resource that records the data subject, purpose of use, authorized data recipients, scope of data, duration or validity period of the consent</p>
</div></td></tr><tr><td><b><a name="update-consent"> </a></b>Update Consent</td><td>SHALL</td><td><div><p>VHL Sharer SHALL support updation of Consent by the VHL Holder, which may include even revocation of consent.</p>
</div></td></tr></table></div>
  </text>
  <url value="https://profiles.ihe.net/ITI/VHL/Requirements/RecordConsent"/>
  <version value="0.0.2-current"/>
  <name value="RecordConsent"/>
  <title value="Record Consent"/>
  <status value="active"/>
  <date value="2025-09-19T17:04:40+00:00"/>
  <publisher value="IHE IT Infrastructure Technical Committee"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="https://www.ihe.net/ihe_domains/it_infrastructure/"/>
    </telecom>
  </contact>
  <contact>
    <telecom>
      <system value="email"/>
      <value value="iti@ihe.net"/>
    </telecom>
  </contact>
  <contact>
    <name value="IHE IT Infrastructure Technical Committee"/>
    <telecom>
      <system value="email"/>
      <value value="iti@ihe.net"/>
    </telecom>
  </contact>
  <description
               value="The [VHL Sharer](ActorDefinition-VHLSharer.html) SHALL record the consent granted by a [VHL Holder](ActorDefinition-VHLHolder.html) 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.html) 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 resulting `Consent` resource SHALL document:
* 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

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."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
    </coding>
  </jurisdiction>
  <actor value="https://profiles.ihe.net/ITI/VHL/ActorDefinition/VHLSharer"/>
  <statement>
    <key value="record-consent"/>
    <label value="Record Consent"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Record consent as FHIR Consent resource that records the data subject, purpose of use, authorized data recipients, scope of data, duration or validity period of the consent"/>
  </statement>
  <statement>
    <key value="update-consent"/>
    <label value="Update Consent"/>
    <conformance value="SHALL"/>
    <requirement
                 value="VHL Sharer SHALL support updation of Consent by the VHL Holder, which may include even revocation of consent."/>
  </statement>
</Requirements>