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

• Narrative Content
• XML
• JSON
• TTL

: Integration Test Plan – Trust Establishment - XML Representation

Active as of 2026-03-13

Raw xml | Download

<TestPlan xmlns="http://hl7.org/fhir">
  <id value="TestPlan-TrustEstablishment"/>
  <url
       value="https://profiles.ihe.net/ITI/VHL/TestPlan/TestPlan-TrustEstablishment"/>
  <version value="0.0.2-current"/>
  <name value="TestPlan_TrustEstablishment"/>
  <title value="Integration Test Plan – Trust Establishment"/>
  <status value="active"/>
  <date value="2026-03-13T13:59:49+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="Integration test plan for the **Trust Establishment** workflow of the IHE ITI Verifiable Health
Links (VHL) profile.

Scope: validates multi-actor, cross-transaction scenarios that span ITI-YY1 (Submit PKI Material)
and ITI-YY2 (Retrieve Trust List) and cannot be covered by unit tests. Tests verify that a DID
Document submitted in YY1 is subsequently retrievable via YY2 in the same session, that both
the VHL Sharer and VHL Receiver can retrieve peer keys, that a full round-trip signature
verification succeeds, and that revocation propagates correctly across actors.

Actors exercised: VHL Sharer, Trust Anchor, VHL Receiver."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
    </coding>
  </jurisdiction>
  <scope>🔗 
    <reference value="ActorDefinition/VHLSharer"/>
  </scope>
  <scope>🔗 
    <reference value="ActorDefinition/TrustAnchor"/>
  </scope>
  <scope>🔗 
    <reference value="ActorDefinition/VHLReceiver"/>
  </scope>
  <testCase>
    <sequence value="1"/>
    <testRun>
      <narrative
                 value="Execute all scenarios in the Gherkin integration feature file
`integration-trust-establishment.feature`.

Scenario groups:
- **Group A – PKI Submission (YY1):** VHL Sharer and VHL Receiver each submit a DID Document;
  Trust Anchor validates and catalogs both.
- **Group B – Trust Retrieval by VHL Receiver (YY2):** VHL Receiver retrieves the newly
  registered VHL Sharer DID Document and all active DID Documents.
- **Group C – Trust Retrieval by VHL Sharer (YY2):** VHL Sharer retrieves its own DID Document
  and the VHL Receiver's DID Document to prepare for manifest authentication.
- **Group D – Round-trip Verification:** Verifies that the VHL Receiver can successfully verify
  a VHL Sharer signature using the public key retrieved in Group B/C; verifies rejection of
  signatures from unknown DIDs.
- **Group E – Revocation Propagation:** Verifies that a revoked DID Document is no longer
  returned by the Trust Anchor, and that the VHL Receiver's cache is invalidated.

These scenarios require shared state across ITI-YY1 and ITI-YY2 (e.g., a DID submitted in
YY1 must be retrievable in YY2 in the same test execution)."/>
      <script>
        <language>
          <coding>
            <system value="urn:ietf:bcp:13"/>
            <code value="text/x-gherkin"/>
          </coding>
          <text value="Gherkin"/>
        </language>
        <sourceReference>
          <reference
                     value="https://build.fhir.org/ig/IHE/ITI.VHL/integration-trust-establishment.feature"/>
          <display value="Integration – Trust Establishment"/>
        </sourceReference>
      </script>
    </testRun>
  </testCase>
</TestPlan>