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: Request VHL Document

Official URL: https://profiles.ihe.net/ITI/VHL/Requirements/RequestVHLDocument Version: 0.0.2-current
Active as of 2025-06-16 Computable Name: RequestVHLDocument

The VHL Receiver SHALL initiate a request to retrieve a single health document from a VHL Sharer, using a previously received and validated Verified Health Link (VHL).

This transaction SHALL be conducted over a mutually authenticated TLS (mTLS) channel. Both the Receiver and Sharer SHALL validate each other's participation in the trust network using PKI material published by the Trust Anchor.

Optional behaviors:

  • The VHL Receiver MAY verify the digital signature of the returned health document to confirm its authenticity, integrity, and provenance, as defined in the Verify Document Signature requirement.
  • The VHL Sharer MAY record an audit event documenting the access request by the Receiver, in accordance with the Audit Event – Received Health Data requirement.

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

    Initiate a request to retrieve a single health document from a VHL Sharer, using a previously received and validated Verified Health Link (VHL)

  2. MAY - Verify digital signature :

    Verify the digital signature of the returned health document to confirm its authenticity, integrity, and provenance, as defined in the Verify Document Signature requirement

  3. MAY - Record audit event :

    Record an audit event documenting the access request by the Receiver, in accordance with the Audit Event – Received Health Data requirement
Derived from This requirement is not derived from another requriement.
Derivatives This requirement has the following derivatives:
Participating Actors