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
| Active as of 2026-11-13 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="ReceiveTrustList"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements ReceiveTrustList</b></p><a name="ReceiveTrustList"> </a><a name="hcReceiveTrustList"> </a><p>These requirements apply to the following actors: </p><ul><li><a href="ActorDefinition-VHLSharer.html">VHL Sharer</a></li><li><a href="ActorDefinition-VHLReceiver.html">VHL Receiver</a></li></ul><p>These requirements derive from <a href="Requirements-EstablishTrust.html">Establish Trust</a></p><table class="grid"><tr><td><b><a name="cache-received-trust-list"> </a></b>Cache received Trust list</td><td>SHALL</td><td><div><p>Cache the received trust list or certificate material to reduce network and server load</p>
</div></td></tr><tr><td><b><a name="validate-digital-signatures"> </a></b>Validate digital signatures</td><td>SHALL</td><td><div><p>Validate digital signatures using the Trust Anchor public key established at onboarding, and validate that the certificate chain accompanying each key resolves back to a certificate verifiable against key material pre-shared with the trust network at onboarding, before the key is used.</p>
</div></td></tr><tr><td><b><a name="monitor-certificate-expiration"> </a></b>Monitor certificate expiration</td><td>SHALL</td><td><div><p>Monitor certificate expiration or revocation status where applicable</p>
</div></td></tr></table></div>
</text>
<url
value="https://profiles.ihe.net/ITI/VHL/Requirements/ReceiveTrustList"/>
<version value="1.0.0-comment"/>
<name value="ReceiveTrustList"/>
<title value="Receive Trust List"/>
<status value="active"/>
<date value="2026-11-13T03:15:18+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="A [VHL Sharer](ActorDefinition-VHLSharer.html) or [VHL Receiver](ActorDefinition-VHLReceiver.html), after receiving PKI material from a [Trust Anchor](ActorDefinition-TrustAnchor.html), SHALL validate and process the trust information for subsequent cryptographic operations.
A participant SHALL NOT treat a public key as trusted solely because it appears in a retrieved trust list. The certificate chain accompanying the key SHALL resolve back to a certificate verifiable against one of the public keys pre-shared with the trust network at the time of onboarding, before the key is used. Where the key material is self-generated, that chain is a single self-signed certificate, which is itself the material pre-shared at onboarding.
The participant verifies the cryptographic proof over a retrieved trust list using the Trust Anchor's public key, which is shared with the participant at the time of onboarding."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
</coding>
</jurisdiction>
<derivedFrom
value="https://profiles.ihe.net/ITI/VHL/Requirements/EstablishTrust"/>
<statement>
<key value="cache-received-trust-list"/>
<label value="Cache received Trust list"/>
<conformance value="SHALL"/>
<requirement
value="Cache the received trust list or certificate material to reduce network and server load"/>
</statement>
<statement>
<key value="validate-digital-signatures"/>
<label value="Validate digital signatures"/>
<conformance value="SHALL"/>
<requirement
value="Validate digital signatures using the Trust Anchor public key established at onboarding, and validate that the certificate chain accompanying each key resolves back to a certificate verifiable against key material pre-shared with the trust network at onboarding, before the key is used."/>
</statement>
<statement>
<key value="monitor-certificate-expiration"/>
<label value="Monitor certificate expiration"/>
<conformance value="SHALL"/>
<requirement
value="Monitor certificate expiration or revocation status where applicable"/>
</statement>
</Requirements>