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

Requirements: Record Consent

Official URL: https://profiles.ihe.net/ITI/VHL/Requirements/RecordConsent Version: 0.0.2-current
Active as of 2025-09-19 Computable Name: RecordConsent

The VHL Sharer SHALL record the consent granted by a VHL Holder 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 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) profile. Specifically, the Sharer SHALL initiate the Access Consent - ITI-108 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.

Publisher IHE IT Infrastructure Technical Committee
Contact Email No contact email has been registered.
Jurisdiction
Statements Steps in the requirement:
  1. SHALL - Record Consent :

    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

  2. SHALL - Update Consent :

    VHL Sharer SHALL support updation of Consent by the VHL Holder, which may include even revocation of consent.
Derived from This requirement is not derived from another requriement.
Derivatives This requirement has the following derivatives:
Participating Actors