Verifiable Health Link
0.0.2-current - ci-build

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

## : Integration Test Plan – QR Code Generation and Validation Flow - JSON Representation

Active as of 2026-03-12

Raw json | Download

    {
      "resourceType" : "TestPlan",
      "id" : "TestPlan-QRCodeFlow",
      "url" : "https://profiles.ihe.net/ITI/VHL/TestPlan/TestPlan-QRCodeFlow",
      "version" : "0.0.2-current",
      "name" : "TestPlan_QRCodeFlow",
      "title" : "Integration Test Plan – QR Code Generation and Validation Flow",
      "status" : "active",
      "date" : "2026-03-12T12:40:14+00:00",
      "publisher" : "IHE IT Infrastructure Technical Committee",
      "contact" : [
        {
          "telecom" : [
            {
              "system" : "url",
              "value" : "https://www.ihe.net/ihe_domains/it_infrastructure/"
            }
          ]
        },
        {
          "telecom" : [
            {
              "system" : "email",
              "value" : "iti@ihe.net"
            }
          ]
        },
        {
          "name" : "IHE IT Infrastructure Technical Committee",
          "telecom" : [
            {
              "system" : "email",
              "value" : "iti@ihe.net"
            }
          ]
        }
      ],
      "description" : "Integration test plan for the **QR Code Generation and Validation Flow** of the IHE ITI\nVerifiable Health Links (VHL) profile.\n\nScope: validates multi-actor, cross-transaction scenarios that span ITI-YY3 (Generate VHL),\nITI-YY4 (Provide VHL), and ITI-YY5 (Retrieve Manifest). Tests verify that the QR code\ngenerated in YY3 can be decoded in YY4, that the decoded SHL payload's manifest URL is used\ncorrectly in YY5, and that the full end-to-end pipeline including passcode handling, signature\nverification, and VHL authorization succeeds.\n\nActors exercised: VHL Holder, VHL Sharer, VHL Receiver.",
      "jurisdiction" : [
        {
          "coding" : [
            {
              "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
              "code" : "001"
            }
          ]
        }
      ],
      "scope" : [
        {
          🔗 "reference" : "ActorDefinition/VHLHolder"
        },
        {
          🔗 "reference" : "ActorDefinition/VHLSharer"
        },
        {
          🔗 "reference" : "ActorDefinition/VHLReceiver"
        }
      ],
      "testCase" : [
        {
          "sequence" : 1,
          "testRun" : [
            {
              "narrative" : "Execute all scenarios in the Gherkin integration feature file\n`integration-qrcode-flow.feature`.\n\nScenario groups:\n- **Group A – VHL Generation (YY3):** VHL Holder requests VHL; VHL Sharer generates a valid\n  HCERT-signed QR code; SHL payload URL is verifiable; passcode is retained by VHL Holder.\n- **Group B – QR Presentation and Decoding (YY4):** VHL Receiver decodes the QR code\n  generated in Group A using the trust list; COSE signature verified; decoded manifest URL\n  matches the YY5 endpoint; passcode is obtained from VHL Holder when P flag is present.\n- **Group C – Manifest Retrieval (YY5):** VHL Receiver uses the decoded folder ID and URL\n  to send an authenticated HTTP POST; VHL Sharer verifies the receiver's signature using the\n  trust list; correct passcode results in HTTP 200 Bundle; incorrect passcode results in 422.\n- **Group D – Full End-to-End:** Complete flow from YY3 generation through YY4 decode to YY5\n  manifest retrieval succeeds; passcode-protected variant succeeds end-to-end.\n- **Group E – Expired and Revoked VHL Rejection:** VHL Receiver rejects an expired QR code at\n  YY4 without proceeding to YY5; VHL Sharer returns 403 for a revoked VHL at YY5.\n\nThese scenarios require pipeline state: the QR code from YY3 feeds YY4, and the decoded\npayload from YY4 feeds YY5.",
              "script" : {
                "language" : {
                  "coding" : [
                    {
                      "system" : "urn:ietf:bcp:13",
                      "code" : "text/x-gherkin"
                    }
                  ],
                  "text" : "Gherkin"
                },
                "sourceReference" : {
                  "reference" : "https://build.fhir.org/ig/IHE/ITI.VHL/integration-qrcode-flow.feature",
                  "display" : "Integration – QR Code Generation and Validation Flow"
                }
              }
            }
          ]
        }
      ]
    }