Verifiable Health Links
1.0.0-comment - ballot International flag

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

: Initiate Submit PKI Material Request - XML Representation

Active as of 2026-11-13

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="InitiateSubmitPKIMaterialRequest"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements InitiateSubmitPKIMaterialRequest</b></p><a name="InitiateSubmitPKIMaterialRequest"> </a><a name="hcInitiateSubmitPKIMaterialRequest"> </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="generate-private-public-key-pair"> </a></b>Obtain Trust Network Key Material</td><td>SHALL</td><td><div><p>Obtain one or more sets of key material for use within the VHL trust network, either by generating private-public key pairs directly or by obtaining certificates issued under a Certificate Authority recognized by the trust framework. Key material SHOULD be scoped to specific usage contexts (e.g., signing, encryption, or secure channels) and MAY be categorized by business domain or participant role.</p>
</div></td></tr><tr><td><b><a name="prepare-submission-metadata"> </a></b>Prepare Submission Metadata</td><td>SHALL</td><td><div><p>Include relevant metadata to support validation and categorization. This MAY include:</p>
<ul>
<li>Intended key usage</li>
<li>Organizational identifier or participant reference</li>
<li>Certificate validity period</li>
<li>Trust path information (e.g., issuing CA)</li>
</ul>
</div></td></tr><tr><td><b><a name="submit-to-trust-anchor"> </a></b>Submit to Trust Anchor</td><td>SHALL</td><td><div><p>Submit the public key material and associated metadata to the <a href="ActorDefinition-TrustAnchor.html">Trust Anchor</a> using the designated secure channel for validation and trust list inclusion.</p>
</div></td></tr><tr><td><b><a name="support-future-distribution"> </a></b>Support Future Distribution</td><td>SHALL</td><td><div><p>Ensure that the submitted PKI material can be validated, signed, and distributed by the Trust Anchor to other trust network participants.</p>
</div></td></tr></table></div>
  </text>
  <url
       value="https://profiles.ihe.net/ITI/VHL/Requirements/InitiateSubmitPKIMaterialRequest"/>
  <version value="1.0.0-comment"/>
  <name value="InitiateSubmitPKIMaterialRequest"/>
  <title value="Initiate Submit PKI Material Request"/>
  <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="When a [VHL Sharer](ActorDefinition-VHLSharer.html) or [VHL Receiver](ActorDefinition-VHLReceiver.html) obtains new key material for use within the VHL trust network, they SHALL submit the corresponding public key material to the [Trust Anchor](ActorDefinition-TrustAnchor.html) for validation and inclusion in the trust list.

Key material is obtained by one of two paths, as determined by the governing trust framework:

* **Self-generated** or
* **Certificate Authority (CA) issued**

The submission MAY include metadata to support categorization of key usage (e.g., digital signatures, encryption, secure channels) and business or operational context."/>
  <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="generate-private-public-key-pair"/>
    <label value="Obtain Trust Network Key Material"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Obtain one or more sets of key material for use within the VHL trust network, either by generating private-public key pairs directly or by obtaining certificates issued under a Certificate Authority recognized by the trust framework. Key material SHOULD be scoped to specific usage contexts (e.g., signing, encryption, or secure channels) and MAY be categorized by business domain or participant role."/>
  </statement>
  <statement>
    <key value="prepare-submission-metadata"/>
    <label value="Prepare Submission Metadata"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Include relevant metadata to support validation and categorization. This MAY include:
* Intended key usage
* Organizational identifier or participant reference
* Certificate validity period
* Trust path information (e.g., issuing CA)"/>
  </statement>
  <statement>
    <key value="submit-to-trust-anchor"/>
    <label value="Submit to Trust Anchor"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Submit the public key material and associated metadata to the [Trust Anchor](ActorDefinition-TrustAnchor.html) using the designated secure channel for validation and trust list inclusion."/>
  </statement>
  <statement>
    <key value="support-future-distribution"/>
    <label value="Support Future Distribution"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Ensure that the submitted PKI material can be validated, signed, and distributed by the Trust Anchor to other trust network participants."/>
  </statement>
</Requirements>