# Generate a VHL Authorization Mechanism Based on Query Parameters - Verifiable Health Link v0.0.2-current

* [**Table of Contents**](toc.md)
* [**Artifacts Summary**](artifacts.md)
* **Generate a VHL Authorization Mechanism Based on Query Parameters**

## Requirements: Generate a VHL Authorization Mechanism Based on Query Parameters (Experimental) 

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

 
The [VHL Sharer](ActorDefinition-VHLSharer.md) SHALL generate a Verified Health Link (VHL) to be issued to a [VHL Holder](ActorDefinition-VHLHolder.md). 
The Sharer SHALL conduct all necessary tasks to prepare the content referenced by the VHL. These tasks MAY be further defined by applicable content profiles or implementation guides, and MAY include: 
* Generation of new documents in real time;
* Querying for existing documents (e.g., IPS, CDA, FHIR Bundles) associated with the VHL Holder; or
* Creation of digital signatures on one or more documents.
 
Once content preparation is complete, the Sharer SHALL construct the VHL payload and sign it to produce a cryptographically verifiable authorization mechanism. 
**Optional behaviors:** 
* The Sharer MAY record consent in accordance with the [Record Consent](Requirements-RecordConsent.md) requirement.
* The Sharer MAY log an audit event describing the VHL issuance, in accordance with the [Audit Event – Accessed Health Data](Requirements-AuditEventAccess.md) requirement.
 

* Statements: Contact Email
  * Steps in the requirement:1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Collect Content **:Collect any pre-existing content and/or generate any necessary content that will be referenced as part of the VHL.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Generate VHL Payload **:Generate the payload for the VHL in accordance with the applicable content profile.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Sign VHL **:Sign the VHL payload to produce a verifiable and cryptographically bound artifact.: No contact email has been registered.
* Statements: Jurisdiction
  * Steps in the requirement:1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Collect Content **:Collect any pre-existing content and/or generate any necessary content that will be referenced as part of the VHL.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Generate VHL Payload **:Generate the payload for the VHL in accordance with the applicable content profile.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Sign VHL **:Sign the VHL payload to produce a verifiable and cryptographically bound artifact.: 
* Statements: Derived from
  * Steps in the requirement:1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Collect Content **:Collect any pre-existing content and/or generate any necessary content that will be referenced as part of the VHL.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Generate VHL Payload **:Generate the payload for the VHL in accordance with the applicable content profile.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Sign VHL **:Sign the VHL payload to produce a verifiable and cryptographically bound artifact.: This requirement is not derived from another requriement.
* Statements: Derivatives
  * Steps in the requirement:1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Collect Content **:Collect any pre-existing content and/or generate any necessary content that will be referenced as part of the VHL.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Generate VHL Payload **:Generate the payload for the VHL in accordance with the applicable content profile.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Sign VHL **:Sign the VHL payload to produce a verifiable and cryptographically bound artifact.: This requirement has the following derivatives:
* Statements: Participating Actors
  * Steps in the requirement:1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Collect Content **:Collect any pre-existing content and/or generate any necessary content that will be referenced as part of the VHL.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Generate VHL Payload **:Generate the payload for the VHL in accordance with the applicable content profile.
1. ** [ SHALL ](https://hl7.org/fhir/R5//codesystem-conformance-expectation.html#content) - Sign VHL **:Sign the VHL payload to produce a verifiable and cryptographically bound artifact.: * [VHL Sharer](ActorDefinition-VHLSharer.md)


