{
  "$schema": "folio-library-document/v1",
  "id": "who-2019-ncov-digital-certificates-vaccination-20211-eng",
  "title": "Digital documentation of COVID-19 certificates: vaccination status: technical specifications and implementation guidance, 27 August 2021",
  "variant": "pdf",
  "pages": 99,
  "tocSource": "inferred",
  "tocMethod": "contents",
  "toc": [
    {
      "level": 4,
      "title": "Page DDCC:VS - Technical Specifications and Implementation Guidance, 27 August",
      "number": null,
      "page": null,
      "pageLabel": null,
      "confidence": 0.5,
      "evidence": [
        "contents"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 3,
      "title": "Acknowledgements",
      "number": null,
      "page": null,
      "pageLabel": null,
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 3,
      "title": "Abbreviations",
      "number": null,
      "page": null,
      "pageLabel": null,
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 3,
      "title": "Glossary",
      "number": null,
      "page": null,
      "pageLabel": null,
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 2,
      "title": "Executive Summary",
      "number": null,
      "page": null,
      "pageLabel": null,
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 1,
      "title": "Page DDCC:VS - Technical Specifications and Implementation Guidance, 27 August",
      "number": null,
      "page": null,
      "pageLabel": null,
      "confidence": 0.5,
      "evidence": [
        "contents"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 1,
      "title": "Introduction",
      "number": "1",
      "page": 18,
      "pageLabel": "1",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-000-1-introduction"
    },
    {
      "level": 2,
      "title": "Purpose of this document",
      "number": "1.1",
      "page": 18,
      "pageLabel": "1",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-001-11-purpose-of-this-document"
    },
    {
      "level": 2,
      "title": "Target audience",
      "number": "1.2",
      "page": 19,
      "pageLabel": "2",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-002-12-target-audience"
    },
    {
      "level": 2,
      "title": "Scope",
      "number": "1.3",
      "page": 19,
      "pageLabel": "2",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-003-13-scope"
    },
    {
      "level": 2,
      "title": "Assumptions",
      "number": "1.4",
      "page": 20,
      "pageLabel": "3",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-004-14-assumptions"
    },
    {
      "level": 2,
      "title": "Methods",
      "number": "1.5",
      "page": 22,
      "pageLabel": "5",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-005-15-methods"
    },
    {
      "level": 2,
      "title": "Additional WHO guidance documents",
      "number": "1.6",
      "page": 22,
      "pageLabel": "5",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-006-16-additional-who-guidance-documents"
    },
    {
      "level": 2,
      "title": "Other initiatives",
      "number": "1.7",
      "page": 22,
      "pageLabel": "5",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-007-17-other-initiatives"
    },
    {
      "level": 1,
      "title": "Ethical considerations and data protection principles",
      "number": "2",
      "page": 23,
      "pageLabel": "6",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": "sec-008-2-ethical-considerations-and-data-protection-pri"
    },
    {
      "level": 2,
      "title": "Ethical considerations for a DDCC:VS",
      "number": "2.1",
      "page": 23,
      "pageLabel": "6",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-009-21-ethical-considerations-for-a-ddccvs"
    },
    {
      "level": 2,
      "title": "Data protection principles for a DDCC:VS",
      "number": "2.2",
      "page": 29,
      "pageLabel": "12",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-010-22-data-protection-principles-for-a-ddccvs"
    },
    {
      "level": 2,
      "title": "DDCC:VS design criteria",
      "number": "2.3",
      "page": 32,
      "pageLabel": "15",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-011-23-ddccvs-design-criteria"
    },
    {
      "level": 1,
      "title": "Continuity of Care scenario",
      "number": "3",
      "page": 33,
      "pageLabel": "16",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-012-3-continuity-of-care-scenario"
    },
    {
      "level": 2,
      "title": "Key settings, personas and digital services",
      "number": "3.1",
      "page": 33,
      "pageLabel": "16",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-013-31-key-settings-personas-and-digital-services"
    },
    {
      "level": 2,
      "title": "Continuity of Care workflows and use cases",
      "number": "3.2",
      "page": 35,
      "pageLabel": "18",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-014-32-continuity-of-care-workflows-and-use-cases"
    },
    {
      "level": 2,
      "title": "Functional requirements for Continuity of Care scenario",
      "number": "3.3",
      "page": 41,
      "pageLabel": "24",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-015-33-functional-requirements-for-continuity-of-car"
    },
    {
      "level": 1,
      "title": "Proof of Vaccination scenario",
      "number": "4",
      "page": 44,
      "pageLabel": "27",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-016-4-proof-of-vaccination-scenario"
    },
    {
      "level": 2,
      "title": "Key settings, personas and digital services",
      "number": "4.1",
      "page": 44,
      "pageLabel": "27",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-017-41-key-settings-personas-and-digital-services"
    },
    {
      "level": 2,
      "title": "Proof of Vaccination workflows and use cases",
      "number": "4.2",
      "page": 46,
      "pageLabel": "29",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-018-42-proof-of-vaccination-workflows-and-use-cases"
    },
    {
      "level": 2,
      "title": "Functional requirements for Proof of Vaccination scenario",
      "number": "4.3",
      "page": 54,
      "pageLabel": "37",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-019-43-functional-requirements-for-proof-of-vaccinat"
    },
    {
      "level": 1,
      "title": "DDCC:VS core data set",
      "number": "5",
      "page": 57,
      "pageLabel": "40",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": "sec-020-5-ddccvs-core-data-set"
    },
    {
      "level": 2,
      "title": "Core data set principles",
      "number": "5.1",
      "page": 57,
      "pageLabel": "40",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-021-51-core-data-set-principles"
    },
    {
      "level": 2,
      "title": "Core data elements",
      "number": "5.2",
      "page": 59,
      "pageLabel": "42",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-022-52-core-data-elements"
    },
    {
      "level": 1,
      "title": "National Trust Architecture",
      "number": "6",
      "page": 63,
      "pageLabel": "46",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": null
    },
    {
      "level": 2,
      "title": "Signing a DDCC:VS",
      "number": "6.1",
      "page": 65,
      "pageLabel": "48",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-023-61-signing-a-ddccvs"
    },
    {
      "level": 2,
      "title": "Verifying a DDCC:VS signature",
      "number": "6.2",
      "page": 66,
      "pageLabel": "49",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-024-62-verifying-a-ddccvs-signature"
    },
    {
      "level": 2,
      "title": "Trusting a DDCC:VS signature",
      "number": "6.3",
      "page": 67,
      "pageLabel": "50",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-025-63-trusting-a-ddccvs-signature"
    },
    {
      "level": 1,
      "title": "National governance considerations",
      "number": "7",
      "page": 68,
      "pageLabel": "51",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-026-7-national-governance-considerations"
    },
    {
      "level": 1,
      "title": "Implementation considerations",
      "number": "8",
      "page": 70,
      "pageLabel": "53",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-027-8-implementation-considerations"
    },
    {
      "level": 2,
      "title": "Considerations before deploying",
      "number": "8.1",
      "page": 71,
      "pageLabel": "54",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-028-81-considerations-before-deploying"
    },
    {
      "level": 2,
      "title": "Key factors to consider with solution developers",
      "number": "8.2",
      "page": 73,
      "pageLabel": "56",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-029-82-key-factors-to-consider-with-solution-develop"
    },
    {
      "level": 2,
      "title": "Cost category considerations",
      "number": "8.3",
      "page": 74,
      "pageLabel": "57",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-030-83-cost-category-considerations"
    },
    {
      "level": 2,
      "title": "Additional resources to support implementation",
      "number": "8.4",
      "page": 76,
      "pageLabel": "59",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-031-84-additional-resources-to-support-implementatio"
    },
    {
      "level": 3,
      "title": "References",
      "number": null,
      "page": 77,
      "pageLabel": "60",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-032-references"
    },
    {
      "level": 2,
      "title": "Annexes",
      "number": null,
      "page": 79,
      "pageLabel": "62",
      "confidence": 0.9,
      "evidence": [
        "contents",
        "body",
        "style"
      ],
      "source": "inferred",
      "section": "sec-033-annexes"
    },
    {
      "level": 1,
      "title": "Illustrative example of Digital Documentation of COVID-19 Certificates: Vaccination Status (DDCC:VS)",
      "number": "1",
      "page": 80,
      "pageLabel": "63",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": "sec-034-1-illustrative-example-of-digital-documentation"
    },
    {
      "level": 1,
      "title": "Business process symbols used in workflows",
      "number": "2",
      "page": 81,
      "pageLabel": "64",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-035-2-business-process-symbols-used-in-workflows"
    },
    {
      "level": 1,
      "title": "Guiding principles for mapping the WHO Family of International Classifications (WHO-FIC) and other classifications",
      "number": "3",
      "page": 82,
      "pageLabel": "65",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": "sec-036-3-guiding-principles-for-mapping-the-who-family"
    },
    {
      "level": 1,
      "title": "What is public key infrastructure (PKI)?",
      "number": "4",
      "page": 85,
      "pageLabel": "68",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-037-4-what-is-public-key-infrastructure-pki"
    },
    {
      "level": 1,
      "title": "Non-functional requirements",
      "number": "5",
      "page": 89,
      "pageLabel": "72",
      "confidence": 0.95,
      "evidence": [
        "contents",
        "body",
        "style",
        "number"
      ],
      "source": "inferred",
      "section": "sec-038-5-non-functional-requirements"
    },
    {
      "level": 1,
      "title": "Open Health Information Exchange (OpenHIE)-based architectural blueprint",
      "number": "6",
      "page": 94,
      "pageLabel": "77",
      "confidence": 0.8,
      "evidence": [
        "contents",
        "body",
        "number"
      ],
      "source": "inferred",
      "section": "sec-039-6-open-health-information-exchange-openhie-based"
    }
  ],
  "sections": [
    {
      "id": "sec-front-matter",
      "number": null,
      "title": "Front matter",
      "level": 1,
      "pageStart": 1,
      "pageEnd": 18,
      "labelStart": "A",
      "labelEnd": "1",
      "words": 4787,
      "summary": {
        "text": "Presents the front matter of the WHO interim guidance Digital Documentation of COVID-19 Certificates: Vaccination Status (DDCC:VS) — Technical Specifications and Implementation Guidance (27 August 2021, WHO/2019-nCoV/Digital_certificates/vaccination/2021.1), including copyright and licensing notices, the table of contents, acknowledgements, abbreviations, a glossary of technical and data-protection terms, and the Executive Summary. The Executive Summary defines the DDCC:VS as a digitally signed HL7 FHIR representation of COVID-19 vaccination events supporting two primary scenarios (Continuity of Care and Proof of Vaccination) across paper and digital formats without requiring a smartphone, and outlines the minimum policy, data, and service requirements (including Health Certificate Identifiers, a Generation Service, and a Registry Service).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "covid certificate",
          "heading": false
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "full ddcc",
          "heading": false
        },
        {
          "term": "paper certificate",
          "heading": false
        },
        {
          "term": "signed fhir",
          "heading": false
        },
        {
          "term": "vaccination card",
          "heading": false
        },
        {
          "term": "covid status",
          "heading": false
        },
        {
          "term": "certificate identifier",
          "heading": false
        }
      ],
      "extract": "DDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021 Page A SECTION 1 Introduction Digital Documentation of COVID-19 Certificates: Vaccination Status TECHNICAL SPECIFICATIONS AND IMPLEMENTATION GUIDANCE 27 August 2021 Page B DDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021 Introduction SECTION 1 Digital Documentation of COVID-19 Certificates: Vaccination Status",
      "extractCut": true,
      "blocks": [
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-front-matter",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p014-1",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p014",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-1",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-2",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-3",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-4",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-5",
        "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p015"
      ]
    },
    {
      "id": "sec-000-1-introduction",
      "number": "1",
      "title": "Introduction",
      "level": 1,
      "pageStart": 18,
      "pageEnd": 18,
      "labelStart": "1",
      "labelEnd": "1",
      "words": 184,
      "summary": {
        "text": "Introduces Section 1 by framing the global COVID-19 pandemic context and the need for countries to provide verifiable records of COVID-19 vaccination status that augment fraud- and loss-prone paper cards while respecting human rights, equity, ethical considerations, and data protection principles.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "coronavirus",
          "heading": false
        },
        {
          "term": "covid",
          "heading": false
        },
        {
          "term": "vaccination",
          "heading": false
        },
        {
          "term": "record",
          "heading": false
        },
        {
          "term": "document",
          "heading": false
        },
        {
          "term": "protection",
          "heading": false
        }
      ],
      "extract": "Coronavirus disease (COVID-19), caused by the severe acute respiratory syndrome coronavirus 2 (SARS-CoV-2), was first identified in December 2019 and has spread to become a global pandemic. The outbreak has forced curtailment of movement, curfews and adoption of preventative measures to try to halt transmission, lower the burden on health systems, and reduce morbidity and loss of life. COVID-19 vaccines are being",
      "extractCut": true
    },
    {
      "id": "sec-001-11-purpose-of-this-document",
      "number": "1.1",
      "title": "Purpose of this document",
      "level": 2,
      "pageStart": 18,
      "pageEnd": 19,
      "labelStart": "1",
      "labelEnd": "2",
      "words": 211,
      "summary": {
        "text": "States the purpose of the document in Section 1.1: to provide a software-agnostic baseline set of requirements, a core data set, and a digital-signature approach based on free and open standards so Member States can design, adapt, and deploy interoperable DDCC:VS solutions in paper-plus-barcode or digital formats.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "document",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "member states",
          "heading": false
        },
        {
          "term": "covid",
          "heading": false
        },
        {
          "term": "solution",
          "heading": false
        },
        {
          "term": "specifications",
          "heading": false
        },
        {
          "term": "requirements",
          "heading": false
        }
      ],
      "extract": "This document lays out an approach for creating a signed digital version of a vaccination record for COVID-19 based on a core data set of key information to be recorded, and an approach for the digital signature. The document leverages existing free and open standards, and is driven by the ethics, use cases and requirements for Digital Documentation of COVID-19 Certificates: Vaccination Status (DDCC:VS). SECTION",
      "extractCut": true
    },
    {
      "id": "sec-002-12-target-audience",
      "number": "1.2",
      "title": "Target audience",
      "level": 2,
      "pageStart": 19,
      "pageEnd": 19,
      "labelStart": "2",
      "labelEnd": "2",
      "words": 61,
      "summary": {
        "text": "Identifies the primary target audience in Section 1.2 as national authorities responsible for creating or overseeing COVID-19 digital vaccination certificate solutions, along with supporting government partners, international organizations, NGOs, local businesses, and trade associations.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "audience",
          "heading": true
        },
        {
          "term": "solution",
          "heading": false
        },
        {
          "term": "businesses",
          "heading": false
        }
      ],
      "extract": "The primary target audience of this document is national authorities tasked with creating or overseeing the development of a digital vaccination certificate solution for COVID-19. The document may also be useful to government partners such as local businesses, international organizations, non- governmental organizations and trade associations, that may be required to support Member States in developing or deploying",
      "extractCut": true
    },
    {
      "id": "sec-003-13-scope",
      "number": "1.3",
      "title": "Scope",
      "level": 2,
      "pageStart": 19,
      "pageEnd": 20,
      "labelStart": "2",
      "labelEnd": "3",
      "words": 429,
      "summary": {
        "text": "Defines the in-scope and out-of-scope boundaries in Section 1.3: in-scope elements cover ethical and data-protection principles, Continuity of Care and Proof of Vaccination use cases, the core data set, the HL7 FHIR implementation guide, and national trust framework considerations, whereas SARS-CoV-2 test and infection/recovery certificates, immunity-passport policy decisions, AEFI reporting, rollout monitoring, country-specific 2D barcode identity-binding algorithms, and selective disclosure functionality are out of scope.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "digital vaccination",
          "heading": false
        },
        {
          "term": "vaccination status",
          "heading": false
        },
        {
          "term": "signed digital",
          "heading": false
        },
        {
          "term": "digital documentation",
          "heading": false
        },
        {
          "term": "guidance document",
          "heading": false
        },
        {
          "term": "scope",
          "heading": true
        }
      ],
      "extract": "1.3.1. In scope This document specifically focuses on how to digitally document COVID-19 vaccination status and attest that an individual has received a vaccine (i.e. how to provide a signed digital vaccination certificate). Two priority scenarios are described in Table 1: Continuity of Care and Proof of Vaccination. This document describes a specification for a signed digital vaccination certificate, including:",
      "extractCut": true
    },
    {
      "id": "sec-004-14-assumptions",
      "number": "1.4",
      "title": "Assumptions",
      "level": 2,
      "pageStart": 20,
      "pageEnd": 22,
      "labelStart": "3",
      "labelEnd": "5",
      "words": 817,
      "summary": {
        "text": "Outlines the foundational assumptions in Section 1.4 regarding Member States' responsibilities in setting up and operating a DDCC:VS solution, including legal and human-rights compliance, preventing digital exclusion via paper-and-barcode support indexed by a Health Certificate Identifier (HCID), establishing a national Public Key Infrastructure (PKI) with root and document signer certificates (DSCs) not tied to individual health workers, and operating DDCC:VS Generation, Registry, and optional Repository services.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "sign ddcc",
          "heading": false
        },
        {
          "term": "paper card",
          "heading": false
        },
        {
          "term": "private keys",
          "heading": false
        },
        {
          "term": "member state",
          "heading": false
        },
        {
          "term": "document signer",
          "heading": false
        },
        {
          "term": "digital record",
          "heading": false
        },
        {
          "term": "pha",
          "heading": false
        },
        {
          "term": "vaccination card",
          "heading": false
        }
      ],
      "extract": "The technological specification for a DDCC:VS is intended to be flexible and adaptable for each Member State to meet its diverse public health needs as well as the diverse needs of individuals around the world. It is assumed that there is no one-size-fits-all solution, and so the specification must remain flexible and software-agnostic, while minimizing the amount of digital infrastructure required. The requirements",
      "extractCut": true
    },
    {
      "id": "sec-005-15-methods",
      "number": "1.5",
      "title": "Methods",
      "level": 2,
      "pageStart": 22,
      "pageEnd": 22,
      "labelStart": "5",
      "labelEnd": "5",
      "words": 106,
      "summary": {
        "text": "Describes the methods in Section 1.5 used to develop the guidance, highlighting the creation of the multisectoral Smart Vaccination Certificate Working Group and consultations with WHO Member States and partner organizations to ensure software-agnostic, globally implementable standards.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "vaccination certificates",
          "heading": false
        },
        {
          "term": "supporting development",
          "heading": false
        },
        {
          "term": "working group",
          "heading": false
        },
        {
          "term": "covid",
          "heading": false
        }
      ],
      "extract": "Since the COVID-19 pandemic began, and as vaccines have shown signs of efficacy, the number of digital solutions for vaccination certificates has increased. For the WHO to remain software- agnostic, the Smart Vaccination Certificate Working Group was created, with the intention of being a multisectoral working group focused on supporting development of key standards for digital vaccination certificates, sharing",
      "extractCut": true
    },
    {
      "id": "sec-006-16-additional-who-guidance-documents",
      "number": "1.6",
      "title": "Additional WHO guidance documents",
      "level": 2,
      "pageStart": 22,
      "pageEnd": 22,
      "labelStart": "5",
      "labelEnd": "5",
      "words": 214,
      "summary": {
        "text": "Lists related and baseline WHO guidance documents in Section 1.6 covering risk-based international travel, public health and social measures (PHSMs), International Health Regulations (2005) Emergency Committee statements, COVID-19 vaccination monitoring, home-based immunization records, and national vaccine deployment plans.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "guidance documents",
          "heading": true
        },
        {
          "term": "covid vaccination",
          "heading": false
        },
        {
          "term": "interim guidance",
          "heading": false
        },
        {
          "term": "coronavirus disease",
          "heading": false
        },
        {
          "term": "implementing risk-based",
          "heading": false
        },
        {
          "term": "international travel",
          "heading": false
        },
        {
          "term": "committee regarding",
          "heading": false
        }
      ],
      "extract": "Specific guidance on how or when DDCC:VS should be used can be found in the following WHO guidance documents. →Technical considerations for implementing a risk-based approach to international travel in the context of COVID-19: Interim guidance, 2 July 2021 (6) →Policy considerations for implementing a risk-based approach to international travel in the context of COVID-19 (7) →Interim guidance on considerations for",
      "extractCut": true
    },
    {
      "id": "sec-007-17-other-initiatives",
      "number": "1.7",
      "title": "Other initiatives",
      "level": 2,
      "pageStart": 22,
      "pageEnd": 23,
      "labelStart": "5",
      "labelEnd": "6",
      "words": 77,
      "summary": {
        "text": "Notes in Section 1.7 that the DDCC:VS core data set guidance can be used to generate artefacts conformant with other international initiatives, such as the ICAO Visible Digital Seals for Non-Constrained Environments (VDS-NC) guidelines and the EU Digital COVID Certificate, and points to the WHO DDCC FHIR Implementation Guide.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "certificate",
          "heading": false
        },
        {
          "term": "github",
          "heading": false
        }
      ],
      "extract": "DDCC:VS core data set guidance laid out in this document may be leveraged to generate artefacts conformant with other initiatives such as the International Civil Aviation Organization (ICAO) Guidelines on visible digital seals (“VDS-NC”) for travel-related health proofs (16) and the European Union (EU) EU Digital COVID Certificate (17). Additional technical details can be found on the DDCC vaccination certificate",
      "extractCut": true
    },
    {
      "id": "sec-008-2-ethical-considerations-and-data-protection-pri",
      "number": "2",
      "title": "Ethical considerations and data protection principles",
      "level": 1,
      "pageStart": 23,
      "pageEnd": 23,
      "labelStart": "6",
      "labelEnd": "6",
      "words": 104,
      "summary": {
        "text": "Introduces Section 2 by emphasizing that ethical considerations—such as equity and equitable access—and data protection principles must inform both the technical design criteria and national deployments of any DDCC:VS solution.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "protection principles",
          "heading": true
        },
        {
          "term": "ethical considerations",
          "heading": true
        },
        {
          "term": "data protection",
          "heading": true
        }
      ],
      "extract": "SECTION 2 As with any digital solution, there are ethical considerations, such as potential impacts on equity and on equitable access, and data protection principles that need to inform the design of the technical specifications, as well as provide guidance on how resulting solutions can be ethically implemented. The following sections discuss some key ethical considerations and data protection principles that",
      "extractCut": true
    },
    {
      "id": "sec-009-21-ethical-considerations-for-a-ddccvs",
      "number": "2.1",
      "title": "Ethical considerations for a DDCC:VS",
      "level": 2,
      "pageStart": 23,
      "pageEnd": 29,
      "labelStart": "6",
      "labelEnd": "12",
      "words": 3032,
      "summary": {
        "text": "Details the ethical considerations for designing and deploying a DDCC:VS in Section 2.1, examining public health objectives (promoting welfare, preventing health inequities and digital exclusion, and maintaining public trust), procedural values (transparency, inclusiveness, accountability, and responsiveness), ethical risks of 'health pass' uses amid scientific uncertainties and unequal vaccine access, and six core recommendations for domestic implementation.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "ethical considerations",
          "heading": true
        },
        {
          "term": "obtain ddcc",
          "heading": false
        },
        {
          "term": "covid vaccination",
          "heading": false
        },
        {
          "term": "covid vaccine",
          "heading": false
        },
        {
          "term": "health pass",
          "heading": false
        },
        {
          "term": "vaccination record",
          "heading": false
        },
        {
          "term": "vaccinated individuals",
          "heading": false
        }
      ],
      "extract": "This section presents ethical considerations to take into account when designing, developing and deploying a DDCC:VS as part of the response to the COVID-19 pandemic (which may be extended to other diseases). This document covers two priority scenarios of use for a DDCC:VS, which are: 1. as a record to serve as the basis for continuing healthcare for that individual (Continuity of Care); and 2. as a record",
      "extractCut": true
    },
    {
      "id": "sec-010-22-data-protection-principles-for-a-ddccvs",
      "number": "2.2",
      "title": "Data protection principles for a DDCC:VS",
      "level": 2,
      "pageStart": 29,
      "pageEnd": 32,
      "labelStart": "12",
      "labelEnd": "15",
      "words": 1458,
      "summary": {
        "text": "Establishes seven fundamental data protection principles for DDCC:VS in Section 2.2 to guide national authorities and safeguard privacy and human rights: lawful basis, legitimate use and fair processing; transparency; purpose limitation and specification; proportionality, necessity and data minimization; confidentiality and security (including breach notification); data subject rights, complaint and legal redress; and independent oversight and accountability.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "data protection",
          "heading": true
        },
        {
          "term": "protection principles",
          "heading": true
        },
        {
          "term": "data processed",
          "heading": false
        },
        {
          "term": "data breach",
          "heading": false
        },
        {
          "term": "personal data",
          "heading": false
        },
        {
          "term": "data subject",
          "heading": false
        },
        {
          "term": "subject rights",
          "heading": false
        }
      ],
      "extract": "This section presents fundamental data protection principles for the DDCC:VS as a prerequisite for continuity of care and proof of vaccination. The principles are designed to provide guidance to the national authorities tasked with creating or overseeing the development of the DDCC:VS. The objectives are to encourage Member States to adopt or adapt their national laws and regulations, as necessary, respect personal",
      "extractCut": true
    },
    {
      "id": "sec-011-23-ddccvs-design-criteria",
      "number": "2.3",
      "title": "DDCC:VS design criteria",
      "level": 2,
      "pageStart": 32,
      "pageEnd": 32,
      "labelStart": "15",
      "labelEnd": "15",
      "words": 27,
      "summary": {
        "text": "Introduces Section 2.3 by stating that the preceding ethical considerations and data protection principles directly informed the formulation of the DDCC:VS design criteria.",
        "status": "draft"
      },
      "keywords": [],
      "extract": "Due to the ethical considerations and data protection principles outlined above, the following design criteria were considered when formulating the requirements for implementing a DDCC:VS for the",
      "extractCut": false
    },
    {
      "id": "sec-012-3-continuity-of-care-scenario",
      "number": "3",
      "title": "Continuity of Care scenario",
      "level": 1,
      "pageStart": 32,
      "pageEnd": 33,
      "labelStart": "15",
      "labelEnd": "16",
      "words": 543,
      "summary": {
        "text": "Lists the 11 DDCC:VS design criteria (completing Section 2.3, including preventing inequities, online/offline paper and digital accessibility, non-discrimination across formats, zero cost to vaccinated individuals, open standards without vendor lock-in, environmental sustainability, health-system integration, data minimization, anti-fraud mechanisms, and manual paper verification fallback) and introduces Section 3 on the Continuity of Care scenario.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "care scenario",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "continuity",
          "heading": true
        },
        {
          "term": "member states",
          "heading": false
        },
        {
          "term": "solution",
          "heading": false
        },
        {
          "term": "policy frameworks",
          "heading": false
        },
        {
          "term": "verification",
          "heading": false
        },
        {
          "term": "built",
          "heading": false
        }
      ],
      "extract": "1. Implementation of the DDCC:VS should not increase health inequities or increase the digital divide. 2. Everyone who has been vaccinated to protect against COVID-19 has the right to obtain and hold a DDCC:VS. 3. The DDCC:VS needs to be in a format that can be accessible to all, for example, in paper and digital formats. Any solution should also work in online and offline environments across multiple platforms –",
      "extractCut": true
    },
    {
      "id": "sec-013-31-key-settings-personas-and-digital-services",
      "number": "3.1",
      "title": "Key settings, personas and digital services",
      "level": 2,
      "pageStart": 33,
      "pageEnd": 35,
      "labelStart": "16",
      "labelEnd": "18",
      "words": 534,
      "summary": {
        "text": "Defines the physical settings (Care Site and Data Entry Site), key personas (Table 2: Subject of Care, DDCC:VS Holder, Vaccinator, Data Entry Personnel, and Public Health Authority), and core digital services (Table 3: Digital Health Solution and DDCC:VS Generation Service) for the Continuity of Care scenario in Section 3.1.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "key personas",
          "heading": true
        },
        {
          "term": "digital services",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "vaccination event",
          "heading": false
        },
        {
          "term": "care scenario",
          "heading": false
        },
        {
          "term": "fhir document",
          "heading": false
        },
        {
          "term": "care site",
          "heading": false
        },
        {
          "term": "health solution",
          "heading": false
        }
      ],
      "extract": "The Continuity of Care scenario is expected to involve the following settings, which can be in the same physical location. 1. CARE SITE: where the vaccination event takes place. Some examples of this include at a primary health-care facility, a temporary vaccination site, or a pharmacy, as determined by the Member State’s vaccine delivery plan. 2. DATA ENTRY SITE: where the vaccination record is digitized. The",
      "extractCut": true
    },
    {
      "id": "sec-014-32-continuity-of-care-workflows-and-use-cases",
      "number": "3.2",
      "title": "Continuity of Care workflows and use cases",
      "level": 2,
      "pageStart": 35,
      "pageEnd": 41,
      "labelStart": "18",
      "labelEnd": "24",
      "words": 1637,
      "summary": {
        "text": "Describes the Continuity of Care workflows and use cases in Section 3.2 (illustrated in Figures 3–6 and Table 4), comparing three pathways—Paper First (UC001), Offline Digital (UC002), and Online Digital (UC003)—from care-site presentation and vaccine administration to paper-card HCID recording and HL7 FHIR digital certificate generation, and notes how the WHO DDCC FHIR Implementation Guide operationalizes these workflows.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "ddcc paper",
          "heading": false
        },
        {
          "term": "ddcc holder",
          "heading": false
        },
        {
          "term": "paper card",
          "heading": false
        },
        {
          "term": "continuity",
          "heading": true
        },
        {
          "term": "paper certificate",
          "heading": false
        },
        {
          "term": "paper record",
          "heading": false
        },
        {
          "term": "hcid barcode",
          "heading": false
        },
        {
          "term": "care scenario",
          "heading": false
        }
      ],
      "extract": "The Continuity of Care scenario is summarized in Fig. 3. The workflow’s actors and settings, and its related high-level requirements, may be described as follows. 1. A Subject of Care presents at a care site. The identity of the Subject of Care is established as per Member State processes and norms. The Subject of Care MAY present an existing DDCC:VS card to inform the care delivery process. The Vaccinator MAY",
      "extractCut": true
    },
    {
      "id": "sec-015-33-functional-requirements-for-continuity-of-car",
      "number": "3.3",
      "title": "Functional requirements for Continuity of Care scenario",
      "level": 2,
      "pageStart": 41,
      "pageEnd": 44,
      "labelStart": "24",
      "labelEnd": "27",
      "words": 1338,
      "summary": {
        "text": "Presents Table 5 in Section 3.3, specifying 36 high-level functional requirements (`DDCC.FXNREQ.001` through `DDCC.FXNREQ.036`) across the Paper First (UC001), Offline Digital (UC002), and Online Digital (UC003) Continuity of Care use cases, covering patient identification, paper card issuance and replacement, HCID barcode association, offline data capture and validation, and FHIR generation and digital signing.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "care scenario",
          "heading": true
        },
        {
          "term": "functional requirements",
          "heading": true
        },
        {
          "term": "fxnreq",
          "heading": false
        },
        {
          "term": "vaccination card",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "offline digital",
          "heading": false
        },
        {
          "term": "paper card",
          "heading": false
        },
        {
          "term": "vaccination registration",
          "heading": false
        }
      ],
      "extract": "scenario High-level functional requirements for the elements described in Fig. 3 are presented in Table 5 as suggested features that any digital solutions that would facilitate DDCC:VS issue or usage may have. These are written as guidance requirements only, to be used as a starting point for Member States or other interested parties who need to develop their own specifications for a DDCC:VS to take and adapt.",
      "extractCut": true
    },
    {
      "id": "sec-016-4-proof-of-vaccination-scenario",
      "number": "4",
      "title": "Proof of Vaccination scenario",
      "level": 1,
      "pageStart": 44,
      "pageEnd": 44,
      "labelStart": "27",
      "labelEnd": "27",
      "words": 99,
      "summary": {
        "text": "Introduces Section 4 on the Proof of Vaccination scenario, explaining that it relies on a Public Health Authority having a trusted means to digitally sign an HL7 FHIR document representing the DDCC:VS core data set for purposes defined by Member States in compliance with their legal and policy frameworks.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "vaccination scenario",
          "heading": true
        },
        {
          "term": "proof",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": false
        }
      ],
      "extract": "SECTION Proof of Vaccination scenario 4 This section describes the use cases and actors involved in using a DDCC:VS for Proof of Vaccination, as well as functional requirements for a digital solution. The Proof of Vaccination scenario relies on the PHA having access to a trusted means of digitally signing an HL7 FHIR document, which represents the core data set for the DDCC:VS. It will be up to Member States to",
      "extractCut": true
    },
    {
      "id": "sec-017-41-key-settings-personas-and-digital-services",
      "number": "4.1",
      "title": "Key settings, personas and digital services",
      "level": 2,
      "pageStart": 44,
      "pageEnd": 46,
      "labelStart": "27",
      "labelEnd": "29",
      "words": 675,
      "summary": {
        "text": "Defines the verification site setting, key personas (Table 6: DDCC:VS Holder, Verifier, National PHA, and International PHA), and digital services (Table 7: Health Certificate Identifier, Status Checking Application, DDCC:VS Generation Service, DDCC:VS Registry Service, and optional DDCC:VS Repository Service) for the Proof of Vaccination scenario in Section 4.1.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "key personas",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "national pha",
          "heading": false
        },
        {
          "term": "digital services",
          "heading": true
        },
        {
          "term": "fhir document",
          "heading": false
        },
        {
          "term": "vaccination scenario",
          "heading": false
        },
        {
          "term": "registry service",
          "heading": false
        },
        {
          "term": "vaccination status",
          "heading": false
        }
      ],
      "extract": "For the Proof of Vaccination scenario, there is one additional setting to consider: the verification site, where it is necessary for people to prove their COVID-19 vaccination status (such as a care site, a school, or an airport). How, when, where, and by whom the DDCC:VS can be verified should be defined by the Member State. The relevant policies, including data protection policies, should be put in place",
      "extractCut": true
    },
    {
      "id": "sec-018-42-proof-of-vaccination-workflows-and-use-cases",
      "number": "4.2",
      "title": "Proof of Vaccination workflows and use cases",
      "level": 2,
      "pageStart": 46,
      "pageEnd": 54,
      "labelStart": "29",
      "labelEnd": "37",
      "words": 1901,
      "summary": {
        "text": "Details the Proof of Vaccination service relationships (Figure 7) and verification workflows in Section 4.2 (Figures 8–12 and Table 8), comparing four verification use cases—Manual Verification (UC004), Offline Cryptographic Verification (UC005), Online Status Check for a National DDCC:VS (UC006), and Online Status Check for an International DDCC:VS (UC007)—and noting their operationalization in the WHO DDCC FHIR Implementation Guide.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "pha ddcc",
          "heading": false
        },
        {
          "term": "verifies ddcc",
          "heading": false
        },
        {
          "term": "ddcc holder",
          "heading": false
        },
        {
          "term": "cryptographic verification",
          "heading": false
        },
        {
          "term": "proof",
          "heading": true
        },
        {
          "term": "authorized pha",
          "heading": false
        },
        {
          "term": "international ddcc",
          "heading": false
        },
        {
          "term": "verifier verifies",
          "heading": false
        }
      ],
      "extract": "In order to sign a digital document, PKI technology is required. Each Member State would be responsible for managing its own PKI through its PHA or another national delegated authority. PKI is described in further detail in section 6 and Annex 4. This document assumes that a PKI has already been deployed or is available within a country to support the DDCC:VS workflows described in this section. This PKI supports",
      "extractCut": true
    },
    {
      "id": "sec-019-43-functional-requirements-for-proof-of-vaccinat",
      "number": "4.3",
      "title": "Functional requirements for Proof of Vaccination scenario",
      "level": 2,
      "pageStart": 54,
      "pageEnd": 57,
      "labelStart": "37",
      "labelEnd": "40",
      "words": 1157,
      "summary": {
        "text": "Presents Table 9 in Section 4.3, specifying functional requirements (`DDCC.FXNREQ.037` through `DDCC.FXNREQ.061`) across the four Proof of Vaccination verification use cases (UC004–UC007), covering anti-fraud markings on paper cards, barcode scanning, offline signature verification and logging, online registry queries, data minimization during verification, PKI and DSC maintenance, SMS-based checks, and cross-border PHA verification and fraud notification.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "vaccination scenario",
          "heading": true
        },
        {
          "term": "functional requirements",
          "heading": true
        },
        {
          "term": "offline verification",
          "heading": false
        },
        {
          "term": "verification request",
          "heading": false
        },
        {
          "term": "fxnreq",
          "heading": false
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "vaccination card",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": false
        }
      ],
      "extract": "scenario High-level functional requirements for the activities described in Fig. 8 are presented in Table 9 as suggested features that any digital solutions that would facilitate DDCC:VS verification may have. These are written as guidance requirements only to be used as a starting point for Member States or other interested parties that need to develop their own specifications for a digital solution for DDCC:VS to",
      "extractCut": true
    },
    {
      "id": "sec-020-5-ddccvs-core-data-set",
      "number": "5",
      "title": "DDCC:VS core data set",
      "level": 1,
      "pageStart": 57,
      "pageEnd": 57,
      "labelStart": "40",
      "labelEnd": "40",
      "words": 129,
      "summary": {
        "text": "Introduces Section 5 on the DDCC:VS core data set, explaining that it comprises the critical Subject of Care and vaccination-event data elements required for interoperability across the Continuity of Care and Proof of Vaccination scenarios, either used directly or mapped from existing terminologies, with a full data dictionary provided in Web Annex A.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "core data",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "data elements",
          "heading": false
        },
        {
          "term": "scenarios",
          "heading": false
        }
      ],
      "extract": "SECTION 5 SECTION DDCC:VS core data set 5 The DDCC:VS core data set includes data elements about the Subject of Care and vaccine administration events that are required for the two core scenarios of Continuity of Care and Proof of Vaccination. Stakeholders and systems may use the DDCC:VS core data set as defined, or they may continue to use their existing terminology with a map to the DDCC:VS core data set, so long",
      "extractCut": true
    },
    {
      "id": "sec-021-51-core-data-set-principles",
      "number": "5.1",
      "title": "Core data set principles",
      "level": 2,
      "pageStart": 57,
      "pageEnd": 59,
      "labelStart": "40",
      "labelEnd": "42",
      "words": 577,
      "summary": {
        "text": "Outlines the core data set principles in Section 5.1—data minimization, open standards, implementability on both paper and digital formats, and integration with broader immunization information systems (EIRs, DHIS2, Vigiflow)—and recommends HL7 FHIR (based on the International Patient Summary) and ICD-11 as the preferred open standard and terminology system, with ICD-10, ATC, and SNOMED CT GPS mappings supported.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "core data",
          "heading": true
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "data requirements",
          "heading": false
        },
        {
          "term": "data dictionary",
          "heading": false
        },
        {
          "term": "digital vaccination",
          "heading": false
        },
        {
          "term": "data content",
          "heading": false
        },
        {
          "term": "icd",
          "heading": false
        }
      ],
      "extract": "To develop the core data set, data requirements under the International Health Regulations (15), WHO home-based records guidance (13), WHO adverse events following immunization (AEFI) reporting requirements (26) and WHO immunization programme monitoring guidance are considered (12). The core data set has been further informed by analysis of existing digital vaccination certificates deployed in some countries and by",
      "extractCut": true
    },
    {
      "id": "sec-022-52-core-data-elements",
      "number": "5.2",
      "title": "Core data elements",
      "level": 2,
      "pageStart": 59,
      "pageEnd": 65,
      "labelStart": "42",
      "labelEnd": "48",
      "words": 1766,
      "summary": {
        "text": "Defines the DDCC:VS core data elements in Section 5.2 across three tables: Table 10 (header section identifying the Subject of Care: name, date of birth, unique identifier, and sex), Table 11 (vaccination event data for each dose: vaccine/prophylaxis, brand, manufacturer or market authorization holder, batch number, vaccination date, valid-from date, dose number, total doses, country, administering centre, health worker signature or ID, targeted disease, and next-dose due date), and Table 12 (certificate metadata: issuer, HCID, certificate validity dates, and schema version). It also introduces Section 6 on the National Trust Architecture and PKI chain of trust (Figure 13) for signing and verifying a DDCC:VS.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "data elements",
          "heading": true
        },
        {
          "term": "verifying ddcc",
          "heading": false
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "core data",
          "heading": true
        },
        {
          "term": "certificate valid",
          "heading": false
        },
        {
          "term": "optional recommended",
          "heading": false
        },
        {
          "term": "certificate metadata",
          "heading": false
        },
        {
          "term": "signer certificate",
          "heading": false
        }
      ],
      "extract": "The three key sections of the core data set are: 1. the header 2. data elements for each vaccination event 3. vaccination certificate metadata. The header section data elements include the Subject of Care’s ID information (see Table 10). The header section is intended to capture information about the vaccinated individual to allow for information on the vaccination event to be linked to a specific person. This data",
      "extractCut": true
    },
    {
      "id": "sec-023-61-signing-a-ddccvs",
      "number": "6.1",
      "title": "Signing a DDCC:VS",
      "level": 2,
      "pageStart": 65,
      "pageEnd": 66,
      "labelStart": "48",
      "labelEnd": "49",
      "words": 312,
      "summary": {
        "text": "Explains the three-step process for digitally signing a DDCC:VS in Section 6.1 (illustrated in Figure 14): generating a root certificate key pair, signing Document Signer Certificate (DSC) key pairs with the root private key, and hashing the vaccination data and signing the document hash with the DSC private key.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "signed hash",
          "heading": false
        },
        {
          "term": "document hash",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "dsc private",
          "heading": false
        },
        {
          "term": "signing",
          "heading": true
        },
        {
          "term": "dsc key",
          "heading": false
        },
        {
          "term": "pha generates",
          "heading": false
        },
        {
          "term": "key pair",
          "heading": false
        }
      ],
      "extract": "The process of signing a DDCC:VS is shown in the top row of Fig. 13 and involves three steps. 1. The PHA generates a private and public key pair that serve as the “root certificate”. The private key is kept highly secure (never revealed to another party, maintained in a disconnected location, stored on media that is itself password-protected, etc.); the public key will be widely disseminated. 2. The PHA generates",
      "extractCut": true
    },
    {
      "id": "sec-024-62-verifying-a-ddccvs-signature",
      "number": "6.2",
      "title": "Verifying a DDCC:VS signature",
      "level": 2,
      "pageStart": 66,
      "pageEnd": 67,
      "labelStart": "49",
      "labelEnd": "50",
      "words": 298,
      "summary": {
        "text": "Describes the four-step process for verifying a DDCC:VS digital signature in Section 6.2 (illustrated in Figure 15), where a Verifier computes the document hash, reads the signed hash, decrypts it using the DSC public key to confirm data integrity and signer authenticity, and validates the DSC signature using the PHA's root certificate public key.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "signed hash",
          "heading": false
        },
        {
          "term": "document hash",
          "heading": false
        },
        {
          "term": "calculated hash",
          "heading": false
        },
        {
          "term": "calculate hash",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "document signer",
          "heading": false
        },
        {
          "term": "signature",
          "heading": true
        },
        {
          "term": "verifier",
          "heading": false
        }
      ],
      "extract": "The verification process, shown in in the bottom row of Fig. 13 and further detailed in Fig. 15, reverses the signing process to verify content in the signed DDCC:VS. 1. A Verifier calculates its own hash (i.e. “calculated hash”) from the information in the DDCC:VS using the same hashing algorithm as was used by the document signer. 2. The DDCC:VS’s signed hash is read by a digital solution. 3. The document signer’s",
      "extractCut": true
    },
    {
      "id": "sec-025-63-trusting-a-ddccvs-signature",
      "number": "6.3",
      "title": "Trusting a DDCC:VS signature",
      "level": 2,
      "pageStart": 67,
      "pageEnd": 68,
      "labelStart": "50",
      "labelEnd": "51",
      "words": 234,
      "summary": {
        "text": "Explains the mathematical and operational basis for trusting a DDCC:VS signature in Section 6.3, noting how asymmetric cryptography guarantees authenticity and non-repudiation while PKI provides trusted public-key distribution and key revocation mechanisms.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "public keys",
          "heading": false
        },
        {
          "term": "private key",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "signed",
          "heading": false
        },
        {
          "term": "compromised",
          "heading": false
        },
        {
          "term": "pki",
          "heading": false
        },
        {
          "term": "holder",
          "heading": false
        }
      ],
      "extract": "The cryptographic strength of private–public key pairs is based on the mathematics of asymmetric cryptography, a process involving “one-way” mathematical functions, which are operations that are easy to compute in one direction but extremely hard to reverse. They provide a high level of security provided the private key is not compromised and remains available only to the entity performing the signing.",
      "extractCut": true
    },
    {
      "id": "sec-026-7-national-governance-considerations",
      "number": "7",
      "title": "National governance considerations",
      "level": 1,
      "pageStart": 68,
      "pageEnd": 70,
      "labelStart": "51",
      "labelEnd": "53",
      "words": 842,
      "summary": {
        "text": "Outlines national governance considerations in Section 7 for operating a DDCC:VS trust framework at the PHA and Member State levels, comparing Root Certificate Authority and Master List approaches for sharing authorized DSCs and specifying policy requirements for certificate issuance, verification rules, revocation and remedy procedures, and cross-border data management and privacy protection.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "issuing ddcc",
          "heading": false
        },
        {
          "term": "counterfeit ddcc",
          "heading": false
        },
        {
          "term": "governance considerations",
          "heading": true
        },
        {
          "term": "national governance",
          "heading": true
        },
        {
          "term": "root certificate",
          "heading": false
        },
        {
          "term": "verify ddcc",
          "heading": false
        },
        {
          "term": "trusted verifiers",
          "heading": false
        },
        {
          "term": "member state",
          "heading": false
        }
      ],
      "extract": "SECTION National governance considerations 7 Governance in the health sector is “a wide range of steering and rule-making related functions carried out by governments/decisions makers as they seek to achieve national health policy objectives that are conducive to universal health coverage” (33). A national framework to govern the complex and dynamic health policy for implementing DDCC:VS should be tailored to meet",
      "extractCut": true
    },
    {
      "id": "sec-027-8-implementation-considerations",
      "number": "8",
      "title": "Implementation considerations",
      "level": 1,
      "pageStart": 70,
      "pageEnd": 71,
      "labelStart": "53",
      "labelEnd": "54",
      "words": 313,
      "summary": {
        "text": "Introduces Section 8 on implementation considerations, contrasting two strategic approaches for Member States: deploying a short-term DDCC:VS solution with a defined sunset roadmap for the COVID-19 emergency versus building a long-term digital vaccination certificate infrastructure that supports routine immunization records and broader digital health initiatives.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "short-term ddcc",
          "heading": false
        },
        {
          "term": "covid pandemic",
          "heading": false
        },
        {
          "term": "implementation considerations",
          "heading": true
        },
        {
          "term": "member states",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "solution",
          "heading": false
        },
        {
          "term": "public health",
          "heading": false
        },
        {
          "term": "international concern",
          "heading": false
        }
      ],
      "extract": "SECTION Implementation considerations 8 Since COVID-19 was declared a Public Health Emergency of International Concern under the IHR in January 2020, there has been a clear and urgent need for all Member States to effectively address the COVID-19 pandemic. In the digital age, there has also been immediate acknowledgement that digital health solutions can effectively and immediately be leveraged to support the public",
      "extractCut": true
    },
    {
      "id": "sec-028-81-considerations-before-deploying",
      "number": "8.1",
      "title": "Considerations before deploying",
      "level": 2,
      "pageStart": 71,
      "pageEnd": 73,
      "labelStart": "54",
      "labelEnd": "56",
      "words": 1006,
      "summary": {
        "text": "Provides pre-deployment checklists and key questions in Section 8.1 organized by the WHO/ITU National eHealth Strategy Toolkit and Digital Implementation Investment Guide (DIIG) components: strategy and investment, infrastructure, legislation/policy/compliance, leadership and governance, workforce, services and applications, standards and interoperability, and evolving health content.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "implementing ddcc",
          "heading": false
        },
        {
          "term": "existing digital",
          "heading": false
        },
        {
          "term": "digital health",
          "heading": false
        },
        {
          "term": "technical specifications",
          "heading": false
        },
        {
          "term": "software models",
          "heading": false
        },
        {
          "term": "mobile phone",
          "heading": false
        },
        {
          "term": "phone adoption",
          "heading": false
        },
        {
          "term": "leveraged",
          "heading": false
        }
      ],
      "extract": "Using the framework of essential components of a digital health implementation presented in the WHO/ITU’s National eHealth Strategy Toolkit (36), and the guidance provided in the Digital implementation investment guide (DIIG) (37), the following considerations and key questions should be examined prior to deployment of a DDCC:VS solution. STRATEGY AND INVESTMENT →Is the DDCC:VS solution intended to be a short-term",
      "extractCut": true
    },
    {
      "id": "sec-029-82-key-factors-to-consider-with-solution-develop",
      "number": "8.2",
      "title": "Key factors to consider with solution developers",
      "level": 2,
      "pageStart": 73,
      "pageEnd": 74,
      "labelStart": "56",
      "labelEnd": "57",
      "words": 673,
      "summary": {
        "text": "Details key factors for Public Health Authorities to consider when procuring and partnering with external solution developers in Section 8.2, including clear terms of reference, fixed-price versus time-and-materials contracts, realistic phased timelines, single supplier versus consortium models, measurable KPIs, supplier expertise and project management track records, communication and cultural alignment, long-term partnership potential, and intellectual property and software licensing rights.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "solution",
          "heading": true
        },
        {
          "term": "digital solution",
          "heading": false
        },
        {
          "term": "supplier",
          "heading": false
        },
        {
          "term": "demonstrate solid",
          "heading": false
        },
        {
          "term": "work",
          "heading": false
        },
        {
          "term": "performance indicators",
          "heading": false
        },
        {
          "term": "developers",
          "heading": true
        },
        {
          "term": "contracts",
          "heading": false
        }
      ],
      "extract": "If a PHA that is responsible for the delivery of a digital solution does not have the appropriate technology skills in-house, then it may want to look for one or more partners to provide that service. The choice of a digital partner will ideally be subject to a competitive process. Multiple potential suppliers will be considered to identify partners that represent the best fit for the work at the optimal price, with",
      "extractCut": true
    },
    {
      "id": "sec-030-83-cost-category-considerations",
      "number": "8.3",
      "title": "Cost category considerations",
      "level": 2,
      "pageStart": 74,
      "pageEnd": 76,
      "labelStart": "57",
      "labelEnd": "59",
      "words": 729,
      "summary": {
        "text": "Examines cost categories and budget drivers for short- and long-term DDCC:VS implementations in Section 8.3, presenting Table 13 across six lifecycle phases: ongoing governance and staffing, development and technology setup, deployment (hardware, testing, training, roll-out, and outreach), integration and interoperability, scaling (printing, human resources, IT licensing, and IT scalability), and sustained operations.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "cost category",
          "heading": true
        },
        {
          "term": "cost drivers",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "licensing fees",
          "heading": false
        },
        {
          "term": "digital solution",
          "heading": false
        },
        {
          "term": "refresher training",
          "heading": false
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "key cost",
          "heading": false
        }
      ],
      "extract": "Regardless of whether the intended DDCC:VS solution will be a short-term solution or a long-term digital vaccination certificate solution, specific cost categories and related cost drivers will affect the budget for this work. However, whether they will be incurred as a sunk cost of the pandemic (for short-term solutions) or an investment for future digital health systems (long-term solutions) will depend on the",
      "extractCut": true
    },
    {
      "id": "sec-031-84-additional-resources-to-support-implementatio",
      "number": "8.4",
      "title": "Additional resources to support implementation",
      "level": 2,
      "pageStart": 76,
      "pageEnd": 77,
      "labelStart": "59",
      "labelEnd": "60",
      "words": 233,
      "summary": {
        "text": "Lists additional resources to support DDCC:VS implementation in Section 8.4, including the WHO DDCC:VS HL7 FHIR Implementation Guide and core data dictionary, example implementations and compatible software (EU Digital COVID Certificate and Gateway, OpenSRP FHIR Core, India's DIVOC, OpenHIE DDCC Transactions Mediator), ICAO VDS-NC and OpenHIE specifications, the WHO DIIG, and WHO international travel guidance.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "openhie ddcc",
          "heading": false
        },
        {
          "term": "fhir core",
          "heading": false
        },
        {
          "term": "fhir implementation",
          "heading": false
        },
        {
          "term": "digital covid",
          "heading": false
        },
        {
          "term": "covid certificate",
          "heading": false
        },
        {
          "term": "technical specifications",
          "heading": false
        },
        {
          "term": "vaccination certificates",
          "heading": false
        },
        {
          "term": "core smart",
          "heading": false
        }
      ],
      "extract": "Additional resources that can be leveraged to support the implementation of DDCC:VS include examples of implementations already deployed, additional technical specifications for specific use cases, and general guidance on implementing digital health solutions. Note that the following is a non- exhaustive list of examples. WHO will be documenting in a clearinghouse software solutions that are consistent with the",
      "extractCut": true
    },
    {
      "id": "sec-032-references",
      "number": null,
      "title": "References",
      "level": 3,
      "pageStart": 77,
      "pageEnd": 79,
      "labelStart": "60",
      "labelEnd": "62",
      "words": 1090,
      "summary": {
        "text": "Provides the numbered bibliography of 40 references cited throughout the DDCC:VS technical specifications and implementation guidance.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "accessed june",
          "heading": false
        },
        {
          "term": "covid vaccine",
          "heading": false
        },
        {
          "term": "covid vaccination",
          "heading": false
        },
        {
          "term": "organization news",
          "heading": false
        },
        {
          "term": "news item",
          "heading": false
        },
        {
          "term": "organization newsroom",
          "heading": false
        },
        {
          "term": "int news",
          "heading": false
        },
        {
          "term": "health organization",
          "heading": false
        }
      ],
      "extract": "1. Diamond, D. ‘Ripe for fraud’: Coronavirus vaccination cards support burgeoning scams. In: The Washington Post [website]. USA: The Washington Post; 18 April 2021 (https://www.washingtonpost.com/health/2021/04/18/scams- coronavirus-vaccination-cards/, accessed 9 August 2021). 2. Siringi, S. Fake health certificate racket rife in Kenya. Lancet Infect Dis. 2002;2(8):454. doi:10.1016/s1473-3099(02)00357-2. 3. Deguma",
      "extractCut": true
    },
    {
      "id": "sec-033-annexes",
      "number": null,
      "title": "Annexes",
      "level": 2,
      "pageStart": 79,
      "pageEnd": 80,
      "labelStart": "62",
      "labelEnd": "63",
      "words": 14,
      "summary": {
        "text": "Presents the section divider and Annex 1 header introducing the annexes of the DDCC:VS guidance document.",
        "status": "draft"
      },
      "keywords": [],
      "extract": "DDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021 Page 63 Annex 1",
      "extractCut": false
    },
    {
      "id": "sec-034-1-illustrative-example-of-digital-documentation",
      "number": "1",
      "title": "Illustrative example of Digital Documentation of COVID-19 Certificates: Vaccination Status (DDCC:VS)",
      "level": 1,
      "pageStart": 80,
      "pageEnd": 81,
      "labelStart": "63",
      "labelEnd": "64",
      "words": 139,
      "summary": {
        "text": "Presents Annex 1, showing an illustrative example (adapted from Sonder Design) of an A6 booklet-style paper DDCC:VS vaccination card featuring a Health Certificate Identifier (HCID), QR codes, and inside/outside layouts (Figures A1.1 and A1.2).",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "ddcc",
          "heading": true
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "vaccination card",
          "heading": false
        },
        {
          "term": "illustrative",
          "heading": true
        },
        {
          "term": "member states",
          "heading": false
        }
      ],
      "extract": "Certificates: Vaccination Status (DDCC:VS) Below is an illustrative example of a DDCC:VS intended to be printed on A6 paper and folded like a booklet. This is not a template, nor are Member States required to adopt this design. Member States are encouraged to design a vaccination certificate (paper and/or digital) with the core data set requirements, fraud prevention mechanisms and scenarios of use in mind.1 1 This",
      "extractCut": true
    },
    {
      "id": "sec-035-2-business-process-symbols-used-in-workflows",
      "number": "2",
      "title": "Business process symbols used in workflows",
      "level": 1,
      "pageStart": 81,
      "pageEnd": 82,
      "labelStart": "64",
      "labelEnd": "65",
      "words": 230,
      "summary": {
        "text": "Presents Annex 2 (Table A2.1), defining the standardized business process mapping symbols—pool, swim lane, start event, end event, activity/task, sequence flow, message flow, and gateway—used in the Continuity of Care and Proof of Vaccination workflow diagrams.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "swim lane",
          "heading": false
        },
        {
          "term": "business process",
          "heading": true
        },
        {
          "term": "event notes",
          "heading": false
        },
        {
          "term": "end event",
          "heading": false
        },
        {
          "term": "start event",
          "heading": false
        },
        {
          "term": "pool",
          "heading": false
        },
        {
          "term": "depict",
          "heading": false
        }
      ],
      "extract": "Table A2.1 provides an overview of the standardized notation for business process mapping that is used to depict the Continuity of Care use cases and Proof of Vaccination use cases. Table A2.1 Business process symbols used in workflows Symbol Symbol name Description Lane 1 Lane 2 Lane 3 Pool Pool A pool consists of multiple “swim lanes” that depict all the individuals or types of users that are involved in carrying",
      "extractCut": true
    },
    {
      "id": "sec-036-3-guiding-principles-for-mapping-the-who-family",
      "number": "3",
      "title": "Guiding principles for mapping the WHO Family of International Classifications (WHO-FIC) and other classifications",
      "level": 1,
      "pageStart": 82,
      "pageEnd": 85,
      "labelStart": "65",
      "labelEnd": "68",
      "words": 1088,
      "summary": {
        "text": "Presents Annex 3, setting out 15 guiding principles for mapping existing classifications and terminologies to ICD-11 and other WHO Family of International Classifications (WHO-FIC) standards, covering use-case definition, unidirectional single-purpose maps, transparent documentation, producer involvement, quality assurance and gold-standard usage validation, versioning and maintenance, manual and computational mapping workflows, equivalence and cardinality definitions, machine-readability, and mapping to the ICD-11 foundation component.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "who-fic classifications",
          "heading": true
        },
        {
          "term": "unidirectional maps",
          "heading": false
        },
        {
          "term": "mapping",
          "heading": true
        },
        {
          "term": "map specialists",
          "heading": false
        },
        {
          "term": "usage validation",
          "heading": false
        },
        {
          "term": "mapping process",
          "heading": false
        },
        {
          "term": "source terminology",
          "heading": false
        },
        {
          "term": "automated maps",
          "heading": false
        }
      ],
      "extract": "International Classifications (WHO-FIC) and other classifications Mapping from classifications and terminologies used in existing systems to the International Classification of Diseases, 11th revision (ICD-11), and other WHO-FIC classifications should follow the principles listed below.1 1. Establish use case(s) prior to developing the map – this involves identifying and formulating the purpose(s) for which the map",
      "extractCut": true
    },
    {
      "id": "sec-037-4-what-is-public-key-infrastructure-pki",
      "number": "4",
      "title": "What is public key infrastructure (PKI)?",
      "level": 1,
      "pageStart": 85,
      "pageEnd": 89,
      "labelStart": "68",
      "labelEnd": "72",
      "words": 1331,
      "summary": {
        "text": "Presents Annex 4, providing an accessible primer on Public Key Infrastructure (PKI), public–private key pairs, X.509 digital certificates, and how certificate authorities, Document Signer Certificates (DSCs), and the DDCC:VS Registry Service work together to sign and cryptographically verify vaccination certificates.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "public key",
          "heading": true
        },
        {
          "term": "pki",
          "heading": true
        },
        {
          "term": "certificate authority",
          "heading": false
        },
        {
          "term": "vaccination certificate",
          "heading": false
        },
        {
          "term": "digital certificate",
          "heading": false
        },
        {
          "term": "public keys",
          "heading": false
        },
        {
          "term": "private key",
          "heading": false
        },
        {
          "term": "verifier",
          "heading": false
        }
      ],
      "extract": "The solution discussed in this document involves applying digital signatures to information to provide a guarantee that the information has been validated by an accredited authority. The proposed method is to employ a digital certificate using a private–public key pair, a common mathematical approach for encryption and digital trust. The processes, systems, software and rules around the management of these",
      "extractCut": true
    },
    {
      "id": "sec-038-5-non-functional-requirements",
      "number": "5",
      "title": "Non-functional requirements",
      "level": 1,
      "pageStart": 89,
      "pageEnd": 94,
      "labelStart": "72",
      "labelEnd": "77",
      "words": 2759,
      "summary": {
        "text": "Presents Annex 5 (Table A5.1), specifying 64 generic non-functional requirements (`DDCC.NFXNREQ.001` through `DDCC.NFXNREQ.064`) for DDCC:VS digital solutions across 11 categories: accessibility, availability (SLAs), current and forecast capacity, disaster recovery/business continuity/resilience, performance/response time, security and privacy, regulation and compliance, reliability, horizontal and vertical scalability, supportability, usability, and data retention/archiving.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "non-functional requirements",
          "heading": true
        },
        {
          "term": "nfxnreq",
          "heading": false
        },
        {
          "term": "retention archiving",
          "heading": false
        },
        {
          "term": "disaster recovery",
          "heading": false
        },
        {
          "term": "ddcc",
          "heading": false
        },
        {
          "term": "archive operation",
          "heading": false
        },
        {
          "term": "business continuity",
          "heading": false
        },
        {
          "term": "digital solution",
          "heading": false
        }
      ],
      "extract": "This section contains a suggested set of generic non-functional requirements (see Table A5.1). Along with the functional requirements in sections 3.3 and 4.3, these non-functional requirements can be adapted when specifying a digital solution for the scenarios in this paper. Non-functional requirements explain the conditions under which any digital solution must remain effective and are organized into the following",
      "extractCut": true
    },
    {
      "id": "sec-039-6-open-health-information-exchange-openhie-based",
      "number": "6",
      "title": "Open Health Information Exchange (OpenHIE)-based architectural blueprint",
      "level": 1,
      "pageStart": 94,
      "pageEnd": 99,
      "labelStart": "77",
      "labelEnd": "82",
      "words": 836,
      "summary": {
        "text": "Presents Annex 6, illustrating an Open Health Information Exchange (OpenHIE)-based architectural blueprint (Figure A6.1) for point-of-care DDCC:VS issuance and describing how OpenHIE registries and repositories—Terminology Services, Client Registry, Facility Registry, Health Worker Registry, Product Catalogue, and Shared Health Record (SHR)—supply and persist DDCC:VS core data elements.",
        "status": "draft"
      },
      "keywords": [
        {
          "term": "openhie",
          "heading": true
        },
        {
          "term": "openhie specification",
          "heading": false
        },
        {
          "term": "health information",
          "heading": true
        },
        {
          "term": "openhie architecture",
          "heading": false
        },
        {
          "term": "worker registry",
          "heading": false
        },
        {
          "term": "facility registry",
          "heading": false
        },
        {
          "term": "client registry",
          "heading": false
        },
        {
          "term": "architectural",
          "heading": true
        }
      ],
      "extract": "architectural blueprint This section illustrates how a standards-based health-data-sharing infrastructure could support point- of-care digital health solutions. If digital health solutions are employed in real time during the vaccine administration event, it is anticipated that complementary digital health infrastructure, such as the architectural elements described by the OpenHIE specification, could be leveraged.",
      "extractCut": true
    }
  ],
  "checks": {
    "tocAlignment": {
      "listed_not_found": {
        "count": 2,
        "items": [
          "Page DDCC:VS - Technical Specifications and Implementation Guidance, 27 August",
          "Page DDCC:VS - Technical Specifications and Implementation Guidance, 27 August"
        ]
      },
      "found_not_listed": {
        "count": 13,
        "items": [
          "1 THE SCOPE OF USE OF A DDCC:VS SHOULD BE CLEARLY DEFINED.",
          "2 POTENTIAL BENEFITS, RISKS AND COSTS SHOULD BE ASSESSED BEFORE INTRODUCTION OF A DDCC:VS.",
          "3 OBTAINING AND USING A DDCC:VS SHOULD BE AS INCLUSIVE AND FAIR AS POSSIBLE.",
          "4 ALL NECESSARY MEASURES SHOULD BE PUT IN PLACE TO PROTECT PARTICIPANTS FOR CONTINUITY OF CARE.",
          "5 ALL COMMUNICATION SHOULD BE CLEAR AND TRANSPARENT.",
          "6 THE DDCC:VS SHOULD BE CONSTANTLY MONITORED FOR IMPACT AND ADJUSTED AS NECESSARY.",
          "1 LAWFUL BASIS, LEGITIMATE USE AND FAIR PROCESSING",
          "2 TRANSPARENCY",
          "3 PURPOSE LIMITATION AND SPECIFICATION",
          "4 PROPORTIONALITY, NECESSITY AND DATA MINIMIZATION",
          "5 CONFIDENTIALITY AND SECURITY",
          "6 DATA SUBJECT RIGHTS, COMPLAINT AND LEGAL REDRESS",
          "7 INDEPENDENT OVERSIGHT AND ACCOUNTABILITY"
        ]
      },
      "page_mismatch": {
        "count": 0,
        "items": []
      }
    },
    "figureSequenceGaps": [
      "table 1"
    ],
    "pageLabelConflicts": {
      "count": 0,
      "items": []
    }
  },
  "withheld": false,
  "keywords": [
    {
      "term": "ddcc vaccination",
      "heading": true
    },
    {
      "term": "pha ddcc",
      "heading": false
    },
    {
      "term": "ddcc paper",
      "heading": false
    },
    {
      "term": "signed ddcc",
      "heading": false
    },
    {
      "term": "signing ddcc",
      "heading": true
    },
    {
      "term": "ddcc holder",
      "heading": false
    },
    {
      "term": "international ddcc",
      "heading": false
    },
    {
      "term": "issued ddcc",
      "heading": false
    },
    {
      "term": "sign ddcc",
      "heading": false
    },
    {
      "term": "national ddcc",
      "heading": false
    },
    {
      "term": "verify ddcc",
      "heading": false
    },
    {
      "term": "verifying ddcc",
      "heading": true
    }
  ],
  "pageLabels": [
    {
      "physical": 1,
      "label": "A",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 2,
      "label": "B",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 3,
      "label": "i",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 4,
      "label": "ii",
      "source": "pdf-labels",
      "confidence": 0.7
    },
    {
      "physical": 5,
      "label": "iii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 6,
      "label": "iv",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 7,
      "label": "v",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 8,
      "label": "vi",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 9,
      "label": "vii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 10,
      "label": "viii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 11,
      "label": "ix",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 12,
      "label": "x",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 13,
      "label": "xi",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 14,
      "label": "xii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 15,
      "label": "xiii",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 16,
      "label": "xiv",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 17,
      "label": "xv",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 18,
      "label": "1",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 19,
      "label": "2",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 20,
      "label": "3",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 21,
      "label": "4",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 22,
      "label": "5",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 23,
      "label": "6",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 24,
      "label": "7",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 25,
      "label": "8",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 26,
      "label": "9",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 27,
      "label": "10",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 28,
      "label": "11",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 29,
      "label": "12",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 30,
      "label": "13",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 31,
      "label": "14",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 32,
      "label": "15",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 33,
      "label": "16",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 34,
      "label": "17",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 35,
      "label": "18",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 36,
      "label": "19",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 37,
      "label": "20",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 38,
      "label": "21",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 39,
      "label": "22",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 40,
      "label": "23",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 41,
      "label": "24",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 42,
      "label": "25",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 43,
      "label": "26",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 44,
      "label": "27",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 45,
      "label": "28",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 46,
      "label": "29",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 47,
      "label": "30",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 48,
      "label": "31",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 49,
      "label": "32",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 50,
      "label": "33",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 51,
      "label": "34",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 52,
      "label": "35",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 53,
      "label": "36",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 54,
      "label": "37",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 55,
      "label": "38",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 56,
      "label": "39",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 57,
      "label": "40",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 58,
      "label": "41",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 59,
      "label": "42",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 60,
      "label": "43",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 61,
      "label": "44",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 62,
      "label": "45",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 63,
      "label": "46",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 64,
      "label": "47",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 65,
      "label": "48",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 66,
      "label": "49",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 67,
      "label": "50",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 68,
      "label": "51",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 69,
      "label": "52",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 70,
      "label": "53",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 71,
      "label": "54",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 72,
      "label": "55",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 73,
      "label": "56",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 74,
      "label": "57",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 75,
      "label": "58",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 76,
      "label": "59",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 77,
      "label": "60",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 78,
      "label": "61",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 79,
      "label": "62",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 80,
      "label": "63",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 81,
      "label": "64",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 82,
      "label": "65",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 83,
      "label": "66",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 84,
      "label": "67",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 85,
      "label": "68",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 86,
      "label": "69",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 87,
      "label": "70",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 88,
      "label": "71",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 89,
      "label": "72",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 90,
      "label": "73",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 91,
      "label": "74",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 92,
      "label": "75",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 93,
      "label": "76",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 94,
      "label": "77",
      "source": "printed",
      "confidence": 1
    },
    {
      "physical": 95,
      "label": "78",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 96,
      "label": "79",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 97,
      "label": "80",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 98,
      "label": "81",
      "source": "printed",
      "confidence": 0.85
    },
    {
      "physical": 99,
      "label": "82",
      "source": "printed",
      "confidence": 0.85
    }
  ],
  "figures": [
    {
      "kind": "table",
      "number": "2",
      "title": "These key personas are anticipated to interact with the digital services outlined in Table 3, including digital services that might not have a user interface that the key personas interact with, but are critical building blocks of the reference architecture",
      "page": 34,
      "pageLabel": "17",
      "confidence": 0.7,
      "evidence": [
        "referenced"
      ]
    }
  ],
  "images": [
    {
      "id": "img-p014-1",
      "file": "images/img-p014-1.png",
      "page": 14,
      "narratives": {
        "en": "A small image of the cover of 'Digital Documentation of COVID-19 Certificates: Vaccination Status - Technical specifications and implementation guidance': a dark blue cover with an illustration of a circuit board joining vaccine vials, a syringe, a virus particle, a phone and a laptop, and the WHO logo. In Figure 1 it illustrates the DDCC: Vaccination Status guidance.",
        "fr": "Vignette de la couverture du document « Digital Documentation of COVID-19 Certificates: Vaccination Status - Technical specifications and implementation guidance » : une couverture bleu foncé ornée d'une illustration de circuit imprimé reliant des flacons de vaccin, une seringue, une particule virale, un téléphone et un ordinateur portable, accompagnée du logo de l'OMS. Dans la figure 1, elle illustre les orientations relatives au DDCC : statut vaccinal.",
        "es": "Imagen en miniatura de la portada de «Digital Documentation of COVID-19 Certificates: Vaccination Status - Technical specifications and implementation guidance»: una cubierta azul oscuro con la ilustración de una placa de circuito que conecta viales de vacuna, una jeringa, una partícula vírica, un teléfono y una computadora portátil, junto con el logotipo de la OMS. En la figura 1 ilustra la orientación sobre DDCC: estado de vacunación.",
        "ar": "صورة مصغرة لغلاف وثيقة «التوثيق الرقمي لشهادات كوفيد-19: حالة التطعيم - المواصفات التقنية وإرشادات التنفيذ» (Digital Documentation of COVID-19 Certificates: Vaccination Status - Technical specifications and implementation guidance): غلاف باللون الأزرق الداكن يتضمن رسماً توضيحياً للوحة دوائر إلكترونية تربط بين قوارير لقاح، ومحفنة، وجسيم فيروسي، وهاتف، وحاسوب محمول، مع شعار منظمة الصحة العالمية. وفي الشكل 1 توضح هذه الصورة إرشادات شهادة التوثيق الرقمي لحالة التطعيم (DDCC: Vaccination Status).",
        "ru": "Уменьшенное изображение обложки документа «Digital Documentation of COVID-19 Certificates: Vaccination Status - Technical specifications and implementation guidance»: темно-синяя обложка с иллюстрацией печатной платы, соединяющей флаконы с вакциной, шприц, вирусную частицу, телефон и ноутбук, а также логотип ВОЗ. На рисунке 1 оно иллюстрирует руководство по DDCC: прививочный статус.",
        "zh": "《COVID-19证书数字化记录：接种状态——技术规范与实施指南》（Digital Documentation of COVID-19 Certificates: Vaccination Status - Technical specifications and implementation guidance）封面的缩略图：深蓝色封面上绘有连接疫苗瓶、注射器、病毒颗粒、手机和笔记本电脑的电路板插图，并印有世卫组织标志。在图1中用于代表DDCC：接种状态指南。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p014",
      "file": "figures/vfig-p014.png",
      "page": 14,
      "shows": [
        "1"
      ],
      "narratives": {
        "en": "Figure 1, 'Guidance documents for DDCC'. Three boxes: DDCC: Vaccination Status, guidance on digitally documenting COVID-19 vaccination status, shown with the cover of this document; DDCC: SARS-CoV-2 Test Result, guidance on digitally documenting SARS-CoV-2 test results; and DDCC: History of SARS-CoV-2 Infection, guidance on digitally documenting history of SARS-CoV-2 infection."
      },
      "state": "draft"
    },
    {
      "id": "img-p015-1",
      "file": "images/img-p015-1.png",
      "page": 15,
      "narratives": {
        "en": "The front of the yellow International Certificate of Vaccination or Prophylaxis, with the WHO emblem and the title in English and French ('Certificat international de vaccination ou de prophylaxie') and a blank 'Issued to / Délivré à' line. In Figure 2 it is format 1, the yellow card.",
        "fr": "Le recto du Certificat international de vaccination ou de prophylaxie jaune, portant l'emblème de l'OMS et le titre en anglais et en français (« International Certificate of Vaccination or Prophylaxis / Certificat international de vaccination ou de prophylaxie ») ainsi qu'une ligne vierge « Issued to / Délivré à ». Dans la figure 2, il correspond au format 1, le carnet jaune.",
        "es": "El anverso del Certificado Internacional de Vacunación o Profilaxis amarillo, con el emblema de la OMS, el título en inglés y francés («International Certificate of Vaccination or Prophylaxis / Certificat international de vaccination ou de prophylaxie») y una línea en blanco «Issued to / Délivré à». En la figura 2 corresponde al formato 1, la tarjeta amarilla.",
        "ar": "الوجه الأمامي لشهادة التطعيم أو الاتقاء الدولية الصفراء، ويحمل شارة منظمة الصحة العالمية والعنوان باللغتين الإنجليزية والفرنسية («International Certificate of Vaccination or Prophylaxis / Certificat international de vaccination ou de prophylaxie») وسطراً فارغاً بعبارة «Issued to / Délivré à». ويمثل في الشكل 2 النسق 1، أي البطاقة الصفراء.",
        "ru": "Лицевая сторона желтого Международного свидетельства о вакцинации или профилактике с эмблемой ВОЗ, заголовком на английском и французском языках («International Certificate of Vaccination or Prophylaxis / Certificat international de vaccination ou de prophylaxie») и незаполненной строкой «Issued to / Délivré à». На рисунке 2 это формат 1 — желтая карта.",
        "zh": "黄色《国际预防接种或预防措施证书》封面，印有世卫组织徽章、英法双语标题（“International Certificate of Vaccination or Prophylaxis / Certificat international de vaccination ou de prophylaxie”）以及空白的“Issued to / Délivré à”（发给）栏。在图2中对应格式1，即黄皮书（黄卡）。"
      },
      "state": "draft"
    },
    {
      "id": "img-p015-2",
      "file": "images/img-p015-2.png",
      "page": 15,
      "narratives": {
        "en": "A drawing of a smartphone displaying a 'COVID-19 Vaccination Certificate' with the WHO emblem, two stacked entries dated 'COVID-19 | 21 May 2021' and 'COVID-19 18 June 2021', and a QR code. In Figure 2 it is format 5, a DDCC:VS held on a smartphone. On the rendered page the WHO emblem and title are covered by the label 'National COVID-19 Certificate'.",
        "fr": "Dessin d'un smartphone affichant un « COVID-19 Vaccination Certificate » avec l'emblème de l'OMS, deux entrées superposées datées « COVID-19 | 21 May 2021 » et « COVID-19 18 June 2021 », et un code QR. Dans la figure 2, il correspond au format 5, un certificat DDCC:VS conservé sur un smartphone. Sur la page rendue, l'emblème de l'OMS et le titre sont recouverts par le libellé « National COVID-19 Certificate ».",
        "es": "Dibujo de un teléfono inteligente que muestra un «COVID-19 Vaccination Certificate» con el emblema de la OMS, dos entradas apiladas con fechas «COVID-19 | 21 May 2021» y «COVID-19 18 June 2021», y un código QR. En la figura 2 corresponde al formato 5, un certificado DDCC:VS almacenado en un teléfono inteligente. En la página representada, el emblema de la OMS y el título están cubiertos por la etiqueta «National COVID-19 Certificate».",
        "ar": "رسم لهاتف ذكي يعرض «شهادة تطعيم ضد كوفيد-19» (COVID-19 Vaccination Certificate) مع شارة منظمة الصحة العالمية، وقيدين متتاليين مؤرخين «COVID-19 | 21 May 2021» و«COVID-19 18 June 2021»، ورمز استجابة سريعة (QR). ويمثل في الشكل 2 النسق 5، وهو شهادة التوثيق الرقمي لحالة التطعيم (DDCC:VS) المحفوظة على هاتف ذكي. وفي الصفحة المعروضة تُغطّى شارة منظمة الصحة العالمية والعنوان بتسمية «National COVID-19 Certificate».",
        "ru": "Рисунок смартфона, на экране которого отображается «COVID-19 Vaccination Certificate» с эмблемой ВОЗ, двумя расположенными друг над другом записями с датами «COVID-19 | 21 May 2021» и «COVID-19 18 June 2021» и QR-кодом. На рисунке 2 это формат 5 — сертификат DDCC:VS на смартфоне. На отрисованной странице эмблема ВОЗ и заголовок закрыты надписью «National COVID-19 Certificate».",
        "zh": "一部智能手机的示意图，屏幕显示带有世卫组织徽章的“COVID-19 Vaccination Certificate”（COVID-19接种证书）、两条上下排列的记录（日期分别为“COVID-19 | 21 May 2021”和“COVID-19 18 June 2021”）以及一个二维码。在图2中对应格式5，即保存在智能手机上的DDCC:VS证书。在渲染页面上，世卫组织徽章和标题被“National COVID-19 Certificate”标签覆盖。"
      },
      "state": "draft"
    },
    {
      "id": "img-p015-3",
      "file": "images/img-p015-3.png",
      "page": 15,
      "narratives": {
        "en": "A bilingual 'COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19' with the WHO emblem in English and French, a blank 'Issued to / Délivré à' line, a QR code and a red PDF icon. In Figure 2 it is format 4, a PDF print-out with a health certificate identifier or a 2D barcode. On the rendered page the WHO emblem and title are covered by the label 'National COVID-19 Certificate'.",
        "fr": "Certificat bilingue « COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19 » portant l'emblème de l'OMS en anglais et en français, une ligne vierge « Issued to / Délivré à », un code QR et une icône PDF rouge. Dans la figure 2, il correspond au format 4, une impression PDF munie d'un identifiant de certificat de santé ou d'un code-barres 2D. Sur la page rendue, l'emblème de l'OMS et le titre sont recouverts par le libellé « National COVID-19 Certificate ».",
        "es": "Certificado bilingüe «COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19» con el emblema de la OMS en inglés y francés, una línea en blanco «Issued to / Délivré à», un código QR y un icono rojo de PDF. En la figura 2 corresponde al formato 4, una impresión en PDF con un identificador de certificado sanitario o un código de barras 2D. En la página representada, el emblema de la OMS y el título están cubiertos por la etiqueta «National COVID-19 Certificate».",
        "ar": "شهادة ثنائية اللغة «COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19» تحمل شارة منظمة الصحة العالمية بالإنجليزية والفرنسية، وسطراً فارغاً بعبارة «Issued to / Délivré à»، ورمز استجابة سريعة (QR)، وأيقونة PDF حمراء. وتمثل في الشكل 2 النسق 4، أي مطبوعة بصيغة PDF تتضمن معرّف شهادة صحية أو رمزاً شريطياً ثنائي الأبعاد. وفي الصفحة المعروضة تُغطّى شارة منظمة الصحة العالمية والعنوان بتسمية «National COVID-19 Certificate».",
        "ru": "Двуязычный сертификат «COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19» с эмблемой ВОЗ на английском и французском языках, незаполненной строкой «Issued to / Délivré à», QR-кодом и красным значком PDF. На рисунке 2 это формат 4 — распечатка PDF-файла с идентификатором медицинского сертификата или двумерным штрихкодом. На отрисованной странице эмблема ВОЗ и заголовок закрыты надписью «National COVID-19 Certificate».",
        "zh": "英法双语“COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19”（COVID-19接种证书），带有世卫组织徽章、空白的“Issued to / Délivré à”栏、二维码及红色PDF图标。在图2中对应格式4，即带有健康证书标识符或二维条码的PDF打印件。在渲染页面上，世卫组织徽章和标题被“National COVID-19 Certificate”标签覆盖。"
      },
      "state": "draft"
    },
    {
      "id": "img-p015-4",
      "file": "images/img-p015-4.png",
      "page": 15,
      "narratives": {
        "en": "A bilingual 'COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19' with the WHO emblem in English and French, a blank 'Issued to / Délivré à' line and a QR code. In Figure 2 it is format 3, a handwritten paper certificate with a health certificate identifier or a 2D barcode. On the rendered page the WHO emblem and title are covered by the label 'National COVID-19 Certificate'.",
        "fr": "Certificat bilingue « COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19 » portant l'emblème de l'OMS en anglais et en français, une ligne vierge « Issued to / Délivré à » et un code QR. Dans la figure 2, il correspond au format 3, un certificat papier manuscrit muni d'un identifiant de certificat de santé ou d'un code-barres 2D. Sur la page rendue, l'emblème de l'OMS et le titre sont recouverts par le libellé « National COVID-19 Certificate ».",
        "es": "Certificado bilingüe «COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19» con el emblema de la OMS en inglés y francés, una línea en blanco «Issued to / Délivré à» y un código QR. En la figura 2 corresponde al formato 3, un certificado en papel rellenado a mano con un identificador de certificado sanitario o un código de barras 2D. En la página representada, el emblema de la OMS y el título están cubiertos por la etiqueta «National COVID-19 Certificate».",
        "ar": "شهادة ثنائية اللغة «COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19» تحمل شارة منظمة الصحة العالمية بالإنجليزية والفرنسية، وسطراً فارغاً بعبارة «Issued to / Délivré à»، ورمز استجابة سريعة (QR). وتمثل في الشكل 2 النسق 3، أي شهادة ورقية مكتوبة بخط اليد تتضمن معرّف شهادة صحية أو رمزاً شريطياً ثنائي الأبعاد. وفي الصفحة المعروضة تُغطّى شارة منظمة الصحة العالمية والعنوان بتسمية «National COVID-19 Certificate».",
        "ru": "Двуязычный сертификат «COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19» с эмблемой ВОЗ на английском и французском языках, незаполненной строкой «Issued to / Délivré à» и QR-кодом. На рисунке 2 это формат 3 — заполненный от руки бумажный сертификат с идентификатором медицинского сертификата или двумерным штрихкодом. На отрисованной странице эмблема ВОЗ и заголовок закрыты надписью «National COVID-19 Certificate».",
        "zh": "英法双语“COVID-19 Vaccination Certificate / Certificat de vaccination contre la Covid-19”（COVID-19接种证书），带有世卫组织徽章、空白的“Issued to / Délivré à”栏及二维码。在图2中对应格式3，即带有健康证书标识符或二维条码的手写纸质证书。在渲染页面上，世卫组织徽章和标题被“National COVID-19 Certificate”标签覆盖。"
      },
      "state": "draft"
    },
    {
      "id": "img-p015-5",
      "file": "images/img-p015-5.png",
      "page": 15,
      "narratives": {
        "en": "A photograph of a hand holding a blank CDC 'COVID-19 Vaccination Record Card', in English and Spanish, with fields for name, date of birth and patient number, and rows for 1st and 2nd dose COVID-19 and two 'Other' doses, each with product name/manufacturer and lot number, date, and healthcare professional or clinic site. In Figure 2 it is format 2, a national immunization home-based record.",
        "fr": "Photographie d'une main tenant une carte vierge des CDC intitulée « COVID-19 Vaccination Record Card », en anglais et en espagnol, comportant des champs pour le nom, la date de naissance et le numéro de patient, ainsi que des lignes pour les 1re et 2e doses contre la COVID-19 et deux doses « Other », chacune indiquant le nom du produit/fabricant et le numéro de lot, la date, ainsi que le professionnel de santé ou le centre de vaccination. Dans la figure 2, elle correspond au format 2, un carnet national de vaccination conservé à domicile.",
        "es": "Fotografía de una mano que sostiene una tarjeta de registro de vacunación en blanco de los CDC titulada «COVID-19 Vaccination Record Card», en inglés y español, con campos para el nombre, la fecha de nacimiento y el número de paciente, y filas para la 1.ª y la 2.ª dosis contra la COVID-19 y dos dosis «Other», cada una con nombre del producto/fabricante y número de lote, fecha y profesional sanitario o centro clínico. En la figura 2 corresponde al formato 2, un registro nacional de inmunización conservado en el hogar.",
        "ar": "صورة فوتوغرافية ليد تمسك ببطاقة سجل تطعيم فارغة صادرة عن مراكز مكافحة الأمراض والوقاية منها (CDC) بعنوان «COVID-19 Vaccination Record Card» باللغتين الإنجليزية والإسبانية، تتضمن حقولاً للاسم وتاريخ الميلاد ورقم المريض، وصفوفاً للجرعتين الأولى والثانية من لقاح كوفيد-19 وجرعتين إضافيتين («Other»)، يشمل كل منها اسم المنتج/الشركة المصنعة ورقم التشغيلة والتاريخ واسم أخصائي الرعاية الصحية أو موقع العيادة. وتمثل في الشكل 2 النسق 2، أي سجل التمنيع الوطني المحفوظ في المنزل.",
        "ru": "Фотография руки, держащей незаполненную карточку учета вакцинации CDC «COVID-19 Vaccination Record Card» на английском и испанском языках с полями для имени, даты рождения и номера пациента, а также строками для 1-й и 2-й доз вакцины против COVID-19 и двух доз «Other» (с указанием наименования препарата/производителя, номера серии, даты и медицинского работника или клиники). На рисунке 2 это формат 2 — национальная хранимая на дому карта профилактических прививок.",
        "zh": "一只手拿着空白的美国疾控中心（CDC）“COVID-19 Vaccination Record Card”（COVID-19接种记录卡）的照片，卡片为英西双语，设有姓名、出生日期和患者编号栏，以及第1剂、第2剂COVID-19疫苗和两行“Other”（其他）剂次的记录行，每行包含产品名称/生产商与批号、日期以及医护人员或诊所地点。在图2中对应格式2，即国家家用免疫接种记录。"
      },
      "state": "draft"
    },
    {
      "id": "vfig-p015",
      "file": "figures/vfig-p015.png",
      "page": 15,
      "shows": [
        "2"
      ],
      "narratives": {
        "en": "Figure 2, 'Different illustrative formats of DDCC:VS'. Two existing paper formats: 1, the International Certificate of Vaccination or Prophylaxis (the yellow card); 2, a national immunization home-based record, pictured as a COVID-19 vaccination record card. Then, grouped under Digital Documentation of COVID-19 Certificates: Vaccination Status: 3, a handwritten paper certificate with only an HCID that links to a DDCC:VS, or with a 2D barcode containing the full DDCC:VS core data set; 4, a PDF print-out certificate with only an HCID linking to a DDCC:VS, or with a 2D barcode containing the full core data set; 5, a DDCC:VS held on a smartphone. Formats 3-5 are pictured as a 'National COVID-19 Certificate' with a QR code."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p036",
      "file": "figures/vfig-p036.png",
      "page": 36,
      "shows": [
        "3"
      ],
      "narratives": {
        "en": "Figure 3, 'Continuity of Care scenario': the vaccine is administered, the core data set is recorded on the DDCC paper certificate, and the record is then made available in digital form. Four lanes: subject of care, vaccinator, data entry personnel, DDCC holder. (1) The subject of care arrives at the care site; (2) the vaccinator vaccinates and (3) records core data set elements on a paper certificate, which the holder receives as Point A, a paper record of DDCC:VS. Is there a digital health solution at the care site? If no, (5) data entry personnel record the elements in a digital health solution. If yes, (4) the vaccinator records them in one; then, does the care site have Internet connectivity? Yes leads directly, and no via step 5, to Point B: the record of vaccination status is available in a digital form. End."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p038",
      "file": "figures/vfig-p038.png",
      "page": 38,
      "shows": [
        "4"
      ],
      "narratives": {
        "en": "Figure 4, 'Continuity of Care scenario: Paper First use case (UC001)'. The Figure 3 workflow with one path highlighted: arrival (1), vaccination (2), recording on the paper certificate (3) which gives Point A, then no digital health solution at the care site, so data entry personnel record the data in a digital health solution (5), reaching Point B, the record available in digital form. Step 4 and the connectivity decision are greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p039",
      "file": "figures/vfig-p039.png",
      "page": 39,
      "shows": [
        "5"
      ],
      "narratives": {
        "en": "Figure 5, 'Continuity of Care scenario: Offline Digital use case (UC002)'. The Figure 3 workflow with one path highlighted: arrival (1), vaccination (2), paper recording (3) giving Point A; a digital health solution is at the care site, so the vaccinator records the data in it (4); the site has no Internet connectivity, so data entry personnel record the data (5), reaching Point B. The direct 'no digital solution' and 'connected' branches are greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p040",
      "file": "figures/vfig-p040.png",
      "page": 40,
      "shows": [
        "6"
      ],
      "narratives": {
        "en": "Figure 6, 'Continuity of Care scenario: Online Digital use case (UC003)'. The Figure 3 workflow with one path highlighted: arrival (1), vaccination (2), paper recording (3) giving Point A; a digital health solution is at the care site and the vaccinator records the data in it (4); the site has Internet connectivity, so the record goes directly to Point B, available in digital form. Step 5 by data entry personnel is greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p046",
      "file": "figures/vfig-p046.png",
      "page": 46,
      "shows": [
        "7"
      ],
      "narratives": {
        "en": "Figure 7, 'The relationships between digital services for Proof of Vaccination'. A digital health solution submits a vaccination event to the DDCC:VS generation service, which returns a DDCC:VS. The HCID is provided by an existing national system or issued by the generation service. The generation service registers the DDCC:VS with the DDCC:VS registry service and may optionally store it in a DDCC:VS repository. Optional dashed links: an online status check between the registry service and the repository, and online verification of a DDCC:VS between an optional status checking application and the registry service. A note explains that the HCID, the unique identifier in a DDCC:VS, is used throughout these services and lets verifiers search for and retrieve a DDCC:VS."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p048",
      "file": "figures/vfig-p048.png",
      "page": 48,
      "shows": [
        "8"
      ],
      "narratives": {
        "en": "Figure 8, 'Proof of Vaccination scenario': verification of a claim of vaccination. Four lanes: DDCC holder, verifier, national PHA, international PHA. (1) The holder presents the DDCC:VS; (2) the verifier receives the claim. Is cryptographic verification required? No leads straight to Point C, the decision on the verification. Yes: (3) the verifier uses a status checking application; perform check online? No leads to Point C. Yes: (4) the national PHA performs an online check with its DDCC registry service; check with international PHA? If yes, (5) the international PHA performs an online check with its registry service; either way (6) results are communicated back to the verifier, then Point C and End."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p050",
      "file": "figures/vfig-p050.png",
      "page": 50,
      "shows": [
        "9"
      ],
      "narratives": {
        "en": "Figure 9, 'Proof of Vaccination scenario: Manual Verification use case (UC004)'. The Figure 8 workflow with one path highlighted: the holder presents the DDCC:VS (1), the verifier receives the claim (2), no cryptographic verification is required, and the verifier goes directly to Point C, the decision on the claim. All the status-checking and PHA steps are greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p051",
      "file": "figures/vfig-p051.png",
      "page": 51,
      "shows": [
        "10"
      ],
      "narratives": {
        "en": "Figure 10, 'Proof of Vaccination scenario: Offline Cryptographic Verification use case (UC005)'. The Figure 8 workflow with one path highlighted: presentation (1), receipt of the claim (2), cryptographic verification required, the verifier uses a status checking application (3) and does not check online, going to Point C. The online PHA checks are greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p052",
      "file": "figures/vfig-p052.png",
      "page": 52,
      "shows": [
        "11"
      ],
      "narratives": {
        "en": "Figure 11, 'Proof of Vaccination scenario: Online Status Check (National DDCC:VS) use case (UC006)'. The Figure 8 workflow with one path highlighted: presentation (1), receipt (2), cryptographic verification required, status checking application (3), online check performed by the national PHA against its DDCC registry service (4), no international check, results communicated back to the verifier (6), Point C. The international PHA step is greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p053",
      "file": "figures/vfig-p053.png",
      "page": 53,
      "shows": [
        "12"
      ],
      "narratives": {
        "en": "Figure 12, 'Proof of Vaccination scenario: Online Status Check (International DDCC:VS) use case (UC007)'. The Figure 8 workflow with one path highlighted: presentation (1), receipt (2), cryptographic verification required, status checking application (3), national PHA online check (4), check with the international PHA, which performs an online check with its DDCC registry service (5), results communicated back to the verifier (6), Point C. The manual and offline branches are greyed out."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p064",
      "file": "figures/vfig-p064.png",
      "page": 64,
      "shows": [
        "13"
      ],
      "narratives": {
        "en": "Figure 13, 'The chain of trust'. Three linked boxes: CSCA (country signing certificate authority) and DSC (document signer certificate), each with a private and a public key, and DDCC (Digital Documentation of COVID-19 Certificate), marked with a QR code. Above, 'Signing and issuing a DDCC' runs in steps 1-3 from CSCA through DSC to DDCC. Below, a dotted 'Verifying a DDCC' arc runs in steps 1-3 the other way, from DDCC back to CSCA."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p065",
      "file": "figures/vfig-p065.png",
      "page": 65,
      "shows": [
        "14"
      ],
      "narratives": {
        "en": "Figure 14, 'How digital signatures work', under the heading Document Signing. A signer starts from a document (vaccination data); a hash is calculated from the document, giving the document hash; the hash is digitally signed with a private key, giving the signed hash; the signed hash is added to the document, giving a document with a digitally signed hash (the DDCC:VS)."
      },
      "state": "draft"
    },
    {
      "id": "vfig-p066",
      "file": "figures/vfig-p066.png",
      "page": 66,
      "shows": [
        "15"
      ],
      "narratives": {
        "en": "Figure 15, 'How digital signature verification works'. The upper panel, Document Signing, repeats Figure 14: document, document hash, signed with the private key, signed hash added to the document to make the DDCC:VS. The signer sends the digitally signed document and the public key to the verifier. The lower panel, Document Validation: the verifier calculates a hash from the document and, using the public key, obtains the hash from the signed hash; the two values are compared, and a matching hash indicates a valid document, one that contains the information that was signed with the private key."
      },
      "state": "draft"
    },
    {
      "id": "img-p080-1",
      "file": "images/img-p080-1.png",
      "page": 80,
      "narratives": {
        "en": "A QR code printed on the illustrative paper vaccination certificate in Annex 1 (Figures A1.1 and A1.2), where the text calls it the digital scanned code of the vaccination card. Its content was not decoded.",
        "fr": "Code QR imprimé sur le certificat de vaccination papier illustratif de l'annexe 1 (figures A1.1 et A1.2), où le texte le désigne comme le code numérique scanné de la carte de vaccination. Son contenu n'a pas été décodé.",
        "es": "Código QR impreso en el certificado de vacunación en papel ilustrativo del anexo 1 (figuras A1.1 y A1.2), donde el texto lo denomina código digital escaneado de la tarjeta de vacunación. Su contenido no fue decodificado.",
        "ar": "رمز استجابة سريعة (QR) مطبوع على شهادة التطعيم الورقية التوضيحية في المرفق 1 (الشكلان A1.1 وA1.2)، حيث يصفه النص بأنه الرمز الرقمي الممسوح ضوئياً لبطاقة التطعيم. ولم يُفكَّ ترميز محتواه.",
        "ru": "QR-код, напечатанный на иллюстративном бумажном сертификате вакцинации в приложении 1 (рисунки A1.1 и A1.2), где в тексте он назван цифровым сканируемым кодом прививочной карты. Его содержимое не декодировалось.",
        "zh": "印在附件1（图A1.1和图A1.2）示例性纸质接种证书上的二维码，正文称之为接种卡的数字化扫描码。其内容未予解码。"
      },
      "state": "draft"
    },
    {
      "id": "img-p081-1",
      "file": "images/img-p081-1.png",
      "page": 81,
      "narratives": {
        "en": "An empty rounded rectangle with a black outline: the BPMN symbol for an activity, process, step or task in Table A2.1, 'Business process symbols used in workflows'.",
        "fr": "Rectangle vide aux coins arrondis avec un contour noir : le symbole BPMN représentant une activité, un processus, une étape ou une tâche dans le tableau A2.1, « Business process symbols used in workflows ».",
        "es": "Rectángulo vacío de esquinas redondeadas con contorno negro: el símbolo BPMN para una actividad, proceso, paso o tarea en el cuadro A2.1, «Business process symbols used in workflows».",
        "ar": "مستطيل فارغ مستدير الزوايا ذو إطار أسود: رمز نمذجة العمليات التجارية (BPMN) الذي يمثل نشاطاً أو عملية أو خطوة أو مهمة في الجدول A2.1، «رموز العمليات التجارية المستخدمة في مخططات سير العمل» (Business process symbols used in workflows).",
        "ru": "Пустой прямоугольник со скругленными углами и черным контуром: символ BPMN, обозначающий действие, процесс, шаг или задачу в таблице A2.1 «Business process symbols used in workflows».",
        "zh": "黑框空白圆角矩形：表A2.1“工作流中使用的业务流程符号”（Business process symbols used in workflows）中表示活动、流程、步骤或任务的BPMN符号。"
      },
      "state": "draft"
    },
    {
      "id": "img-p081-2",
      "file": "images/img-p081-2.png",
      "page": 81,
      "narratives": {
        "en": "A solid black line ending in a filled arrowhead: the BPMN symbol for a sequence flow, the direction from one process step to the next, in Table A2.1.",
        "fr": "Ligne noire continue se terminant par une pointe de flèche pleine : le symbole BPMN d'un flux de séquence, indiquant la direction d'une étape de processus à la suivante, dans le tableau A2.1.",
        "es": "Línea negra continua terminada en una punta de flecha rellena: el símbolo BPMN de flujo de secuencia, que indica la dirección de un paso del proceso al siguiente, en el cuadro A2.1.",
        "ar": "خط أسود متصل ينتهي برأس سهم مصمت: رمز BPMN لتدفق التسلسل، أي الاتجاه من خطوة عملية إلى الخطوة التي تليها، في الجدول A2.1.",
        "ru": "Сплошная черная линия, заканчивающаяся закрашенным наконечником стрелки: символ потока операций (sequence flow) в нотации BPMN, показывающий направление перехода от одного шага процесса к следующему, в таблице A2.1.",
        "zh": "末端带实心箭头的黑色实线：表A2.1中表示顺序流（即从一个流程步骤到下一个流程步骤的方向）的BPMN符号。"
      },
      "state": "draft"
    },
    {
      "id": "img-p081-3",
      "file": "images/img-p081-3.png",
      "page": 81,
      "narratives": {
        "en": "A dashed black line starting at a small open circle and ending in an open arrowhead: the BPMN symbol for a message flow, the flow of data or information between processes, in Table A2.1.",
        "fr": "Ligne noire en tirets partant d'un petit cercle ouvert et se terminant par une pointe de flèche ouverte : le symbole BPMN d'un flux de message, représentant la circulation de données ou d'informations entre processus, dans le tableau A2.1.",
        "es": "Línea negra discontinua que parte de un pequeño círculo abierto y termina en una punta de flecha abierta: el símbolo BPMN de flujo de mensaje, que representa el flujo de datos o información entre procesos, en el cuadro A2.1.",
        "ar": "خط أسود متقطع يبدأ بدائرة صغيرة مفرغة وينتهي برأس سهم مفرغ: رمز BPMN لتدفق الرسائل، أي تدفق البيانات أو المعلومات بين العمليات، في الجدول A2.1.",
        "ru": "Пунктирная черная линия, начинающаяся с маленького незакрашенного кружка и заканчивающаяся незакрашенным наконечником стрелки: символ потока сообщений (message flow) в нотации BPMN, обозначающий передачу данных или информации между процессами, в таблице A2.1.",
        "zh": "始于空心小圆圈、终于空心箭头的黑色虚线：表A2.1中表示消息流（即流程之间数据或信息流动）的BPMN符号。"
      },
      "state": "draft"
    },
    {
      "id": "img-p081-4",
      "file": "images/img-p081-4.png",
      "page": 81,
      "narratives": {
        "en": "A white diamond with a black outline: the BPMN gateway symbol, a fork or decision point in a workflow, in Table A2.1.",
        "fr": "Losange blanc avec un contour noir : le symbole de passerelle (gateway) BPMN, représentant un embranchement ou un point de décision dans un flux de travail, dans le tableau A2.1.",
        "es": "Rombo blanco con contorno negro: el símbolo de compuerta (gateway) BPMN, que representa una bifurcación o punto de decisión en un flujo de trabajo, en el cuadro A2.1.",
        "ar": "معين أبيض ذو إطار أسود: رمز البوابة (gateway) في BPMN، ويمثل نقطة تفرع أو اتخاذ قرار في سير العمل، في الجدول A2.1.",
        "ru": "Белый ромб с черным контуром: символ шлюза (gateway) в нотации BPMN, обозначающий развилку или точку принятия решения в рабочем процессе, в таблице A2.1.",
        "zh": "黑框白色菱形：表A2.1中表示工作流分支或决策点的BPMN网关（gateway）符号。"
      },
      "state": "draft"
    },
    {
      "id": "img-p086-1",
      "file": "images/img-p086-1.png",
      "page": 86,
      "narratives": {
        "en": "A screenshot of the PuTTY Key Generator window, given as an example of a key generation tool (Figure A4.2). The Key panel shows a highlighted RSA public key for pasting into an OpenSSH authorized_keys file, a key fingerprint beginning 'ssh-rsa 2048', and the key comment 'rsa-key-20210701', with empty passphrase fields. Actions offer Generate, Load, Save public key and Save private key; the parameters select an RSA key of 2048 bits.",
        "fr": "Capture d'écran de la fenêtre PuTTY Key Generator, présentée comme exemple d'outil de génération de clés (figure A4.2). Le panneau Key affiche en surbrillance une clé publique RSA à coller dans un fichier authorized_keys d'OpenSSH, une empreinte de clé commençant par « ssh-rsa 2048 » et le commentaire de clé « rsa-key-20210701 », avec des champs de phrase secrète vides. La section Actions propose les boutons Generate, Load, Save public key et Save private key ; les paramètres sélectionnent une clé RSA de 2048 bits.",
        "es": "Captura de pantalla de la ventana de PuTTY Key Generator, presentada como ejemplo de herramienta de generación de claves (figura A4.2). El panel Key muestra resaltada una clave pública RSA para pegarla en un archivo authorized_keys de OpenSSH, una huella digital de clave que comienza por «ssh-rsa 2048» y el comentario de clave «rsa-key-20210701», con los campos de frase de contraseña vacíos. La sección Actions ofrece Generate, Load, Save public key y Save private key; los parámetros seleccionan una clave RSA de 2048 bits.",
        "ar": "لقطة شاشة لنافذة برنامج PuTTY Key Generator، تُقدَّم كمثال على أداة لتوليد المفاتيح (الشكل A4.2). تعرض لوحة المفتاح (Key) مفتاحاً عاماً من نوع RSA مظللاً للصقه في ملف authorized_keys الخاص بـ OpenSSH، وبصمة مفتاح تبدأ بـ «ssh-rsa 2048»، وتعليق المفتاح «rsa-key-20210701»، مع حقول فارغة لعبارة المرور. وتوفر قسم الإجراءات (Actions) خيارات التوليد (Generate) والتحميل (Load) وحفظ المفتاح العام (Save public key) وحفظ المفتاح الخاص (Save private key)؛ وتحدد المعلمات مفتاح RSA بطول 2048 بت.",
        "ru": "Снимок экрана окна программы PuTTY Key Generator, приведенный в качестве примера средства генерации ключей (рисунок A4.2). В панели Key показаны выделенный открытый ключ RSA для вставки в файл authorized_keys OpenSSH, отпечаток ключа, начинающийся с «ssh-rsa 2048», и комментарий к ключу «rsa-key-20210701» с пустыми полями парольной фразы. В разделе Actions доступны кнопки Generate, Load, Save public key и Save private key; в параметрах выбран ключ RSA длиной 2048 бит.",
        "zh": "作为密钥生成工具示例给出的PuTTY Key Generator窗口截图（图A4.2）。Key（密钥）面板显示一段高亮的RSA公钥（用于粘贴到OpenSSH的authorized_keys文件中）、以“ssh-rsa 2048”开头的密钥指纹以及密钥注释“rsa-key-20210701”，通行短语字段为空。Actions（操作）区域提供Generate（生成）、Load（加载）、Save public key（保存公钥）和Save private key（保存私钥）按钮；参数选择2048位RSA密钥。"
      },
      "state": "draft"
    },
    {
      "id": "img-p095-1",
      "file": "images/img-p095-1.png",
      "page": 95,
      "narratives": {
        "en": "Figure A6.1, the OpenHIE architecture. The OpenHIE component layer holds business domain services (logistics management information service, shared health record, health management information service, finance and insurance service) and registry services (terminology services, client registry, facility registry, health worker registry, product catalogue). Below it the interoperability services layer is a green 'Interoperability Layer' band with authentication, interlinking service and entity mapping. Along the bottom, point-of-service systems: mobile system, electronic medical record, health management information system, lab system, pharmacy system, logistics management information system, and finance and insurance system. Credited 'OpenHIE 2020-05-28; CC BY 4.0'. The page's footnote says orange boxes mark the registries and repositories relevant to DDCC:VS; no orange marking is visible in this extracted image.",
        "fr": "Figure A6.1, l'architecture OpenHIE. La couche des composants OpenHIE regroupe les services de domaine métier (service d'information de gestion logistique, dossier de santé partagé, service d'information de gestion sanitaire, service des finances et de l'assurance) et les services de registres (services terminologiques, registre des clients, registre des établissements, registre des agents de santé, catalogue de produits). En dessous, la couche des services d'interopérabilité est représentée par une bande verte « Interoperability Layer » comprenant l'authentification, le service d'interconnexion et la mise en correspondance des entités. Au bas du schéma figurent les systèmes de point de service : système mobile, dossier médical électronique, système d'information de gestion sanitaire, système de laboratoire, système de pharmacie, système d'information de gestion logistique et système des finances et de l'assurance. Crédit : « OpenHIE 2020-05-28; CC BY 4.0 ». La note de bas de page indique que des encadrés orange signalent les registres et dépôts pertinents pour le DDCC:VS ; aucun marquage orange n'est visible dans cette image extraite.",
        "es": "Figura A6.1, la arquitectura OpenHIE. La capa de componentes de OpenHIE contiene servicios de dominio de negocio (servicio de información de gestión logística, historia clínica compartida, servicio de información de gestión sanitaria, servicio de finanzas y seguros) y servicios de registro (servicios terminológicos, registro de clientes, registro de establecimientos, registro de trabajadores sanitarios, catálogo de productos). Debajo de ella, la capa de servicios de interoperabilidad es una franja verde «Interoperability Layer» con autenticación, servicio de interconexión y mapeo de entidades. En la parte inferior aparecen los sistemas en el punto de atención: sistema móvil, historia clínica electrónica, sistema de información de gestión sanitaria, sistema de laboratorio, sistema de farmacia, sistema de información de gestión logística y sistema de finanzas y seguros. Crédito: «OpenHIE 2020-05-28; CC BY 4.0». La nota al pie de la página indica que los recuadros naranjas marcan los registros y repositorios pertinentes para DDCC:VS; en esta imagen extraída no se observa ningún marcado naranja.",
        "ar": "الشكل A6.1، بنية OpenHIE المعمارية. تضم طبقة مكونات OpenHIE خدمات مجال الأعمال (خدمة معلومات إدارة اللوجستيات، والسجل الصحي المشترك، وخدمة معلومات الإدارة الصحية، وخدمة التمويل والتأمين) وخدمات السجلات (خدمات المصطلحات، وسجل المراجعين، وسجل المرافق، وسجل العاملين الصحيين، ودليل المنتجات). وتحتها تظهر طبقة خدمات التشغيل البيني على هيئة شريط أخضر بعنوان «Interoperability Layer» يشمل المصادقة وخدمة الربط البيني ومواءمة الكيانات. وعلى امتداد الجزء السفلي تصطف أنظمة نقاط الخدمة: النظام المحمول، والسجل الطبي الإلكتروني، ونظام معلومات الإدارة الصحية، ونظام المختبر، ونظام الصيدلية، ونظام معلومات إدارة اللوجستيات، ونظام التمويل والتأمين. المصدر: «OpenHIE 2020-05-28; CC BY 4.0». وتشير حاشية الصفحة إلى أن المربعات البرتقالية تميّز السجلات والمستودعات ذات الصلة بشهادة التوثيق الرقمي لحالة التطعيم (DDCC:VS)؛ غير أنه لا يظهر أي تمييز برتقالي في هذه الصورة المستخرجة.",
        "ru": "Рисунок A6.1 — архитектура OpenHIE. Уровень компонентов OpenHIE включает сервисы предметной области (информационную службу управления логистикой, общую медицинскую карту, информационную службу управления здравоохранением, финансово-страховую службу) и реестровые сервисы (терминологические сервисы, реестр пациентов, реестр медицинских учреждений, реестр медицинских работников, каталог продукции). Под ним расположен уровень сервисов интероперабельности в виде зеленой полосы «Interoperability Layer» с функциями аутентификации, службы связывания и сопоставления сущностей. Вдоль нижнего края показаны системы в точках оказания услуг: мобильная система, электронная медицинская карта, информационная система управления здравоохранением, лабораторная система, аптечная система, информационная система управления логистикой и финансово-страховая система. Источник: «OpenHIE 2020-05-28; CC BY 4.0». В сноске на странице указано, что оранжевыми рамками выделены реестры и репозитории, относящиеся к DDCC:VS; на данном извлеченном изображении оранжевое выделение отсутствует.",
        "zh": "图A6.1，OpenHIE架构图。OpenHIE组件层包含业务领域服务（物流管理信息服务、共享健康档案、卫生管理信息服务、财务与保险服务）和注册库服务（术语服务、客户注册库、机构注册库、卫生工作者注册库、产品目录）。其下方的互操作性服务层为绿色“Interoperability Layer”（互操作性层）横带，内含身份认证、互联服务和实体映射。底部排列着服务点系统：移动系统、电子病历、卫生管理信息系统、实验室系统、药房系统、物流管理信息系统以及财务与保险系统。署名：“OpenHIE 2020-05-28; CC BY 4.0”。页面脚注说明橙色框标出了与DDCC:VS相关的注册库和存储库；但在该提取图像中未见橙色标记。"
      },
      "state": "draft"
    }
  ],
  "coverage": [
    {
      "kind": "contents",
      "state": "found",
      "count": 47,
      "note": "inferred"
    },
    {
      "kind": "sections",
      "state": "found",
      "count": 41,
      "note": "3 levels"
    },
    {
      "kind": "figures",
      "state": "found",
      "count": 28
    },
    {
      "kind": "tables",
      "state": "not-extracted",
      "note": "1 captioned in the text"
    },
    {
      "kind": "references",
      "state": "not-extracted",
      "note": "a references section is in the text (p77); its entries are not extracted"
    },
    {
      "kind": "glossary",
      "state": "not-extracted",
      "note": "a glossary section is in the text (p1); its entries are not extracted"
    },
    {
      "kind": "footnotes",
      "state": "not-extracted"
    },
    {
      "kind": "summaries",
      "state": "found",
      "count": 41,
      "note": "41 of 41 sections"
    }
  ],
  "links": {
    "repo": "litlfred/who-iris",
    "branch": "main",
    "dir": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng"
  }
}
