Verifiable Health Links
1.0.0-comment - ballot
Verifiable Health Links, published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.0-comment 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
| Official URL: https://profiles.ihe.net/ITI/VHL/Requirements/RespondtoRequestVHLDocuments | Version: 1.0.0-comment | |||
| Active as of 2026-11-20 | Computable Name: RespondtoRequestVHLDocuments | |||
The VHL Sharer SHALL respond to a manifest request from a VHL Receiver that presents a previously issued Verifiable Health Link (VHL), returning only those documents the VHL authorizes.
Before any manifest content is released, the Sharer SHALL establish that the VHL presented is valid and authorizes what is being requested.
Authentication of the requesting Receiver is a separate and optional control, provided by the three Sign Manifest Request Options. Where the Sharer claims one of them it authenticates the Receiver against the trust network using PKI material published by the Trust Anchor before releasing any manifest content. Where it does not, release of the manifest follows from a valid VHL and, where the P flag is set, the correct passcode.
Optional behaviors:
These requirements apply to the actor VHL Sharer
| Authenticate the Receiver | MAY | Where one of the Sign Manifest Request Options is supported, authenticate the requesting VHL Receiver against the trust network before releasing any manifest content, and reject the request where the Receiver cannot be authenticated |
| Authorize the request | SHALL | Confirm that the presented VHL is valid, unexpired and not revoked, that any required passcode is satisfied, and that the VHL authorizes the documents requested |
| Return the manifest | SHALL | Return a FHIR searchset Bundle containing only those documents the VHL authorizes, applying any consent-based filtering in force |
| Record audit event | MAY | Record an audit event documenting the access, in accordance with the Audit Event – Accessed Health Data requirement |