{
  "$schema": "folio-library-entry/v1",
  "id": "who-2019-ncov-digital-certificates-vaccination-20211-eng",
  "blocks": [
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-front-matter",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Front matter",
      "pageStart": 1,
      "pageEnd": 18,
      "target": "../sections/sec-front-matter.md",
      "narrative": null,
      "content": "DDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021\nPage\nA\nSECTION 1\nIntroduction\nDigital Documentation \nof COVID-19 Certificates: \nVaccination Status\nTECHNICAL SPECIFICATIONS AND IMPLEMENTATION GUIDANCE\n 27 August 2021\nPage\nB\nDDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021\nIntroduction\nSECTION 1\nDigital Documentation \nof COVID-19 Certificates: \nVaccination Status\nTECHNICAL SPECIFICATIONS AND IMPLEMENTATION GUIDANCE\n 27 August 2021\nDigital Documentation of COVID-19 Certificates: Vaccination Status — Technical Specifications and \nImpleme",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p014-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 14,
      "pageEnd": 14,
      "target": "../images/img-p014-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p014",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 14,
      "pageEnd": 14,
      "target": "../figures/vfig-p014.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../images/img-p015-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-2",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../images/img-p015-2.png",
      "narrative": "draft",
      "content": "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'.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-3",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../images/img-p015-3.png",
      "narrative": "draft",
      "content": "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'.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-4",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../images/img-p015-4.png",
      "narrative": "draft",
      "content": "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'.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p015-5",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../images/img-p015-5.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p015",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 15,
      "pageEnd": 15,
      "target": "../figures/vfig-p015.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-000",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Introduction",
      "pageStart": 18,
      "pageEnd": 18,
      "target": "../sections/sec-000-1-introduction.md",
      "narrative": null,
      "content": "Coronavirus disease (COVID-19), caused by the severe acute respiratory \nsyndrome coronavirus 2 (SARS-CoV-2), was first identified in December \n2019 and has spread to become a global pandemic. The outbreak has \nforced curtailment of movement, curfews and adoption of preventative \nmeasures to try to halt transmission, lower the burden on health \nsystems, and reduce morbidity and loss of life. COVID-19 vaccines \nare being delivered at record speed, and countries need a way to \ngive individuals a record of their vaccination status. Ideally, digital \ntechnology can be leveraged to facilitate large-",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-001",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Purpose of this document",
      "pageStart": 18,
      "pageEnd": 19,
      "target": "../sections/sec-001-11-purpose-of-this-document.md",
      "narrative": null,
      "content": "This document lays out an approach for creating a signed digital version of a vaccination record for \nCOVID-19 based on a core data set of key information to be recorded, and an approach for the digital \nsignature. The document leverages existing free and open standards, and is driven by the ethics, \nuse cases and requirements for Digital Documentation of COVID-19 Certificates: Vaccination Status \n(DDCC:VS).\nSECTION\nIntroduction\n1 \nPage\n2\nDDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021\nIntroduction\nSECTION 1\nAs Member States are increasingly looking to adopt digi",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-002",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Target audience",
      "pageStart": 19,
      "pageEnd": 19,
      "target": "../sections/sec-002-12-target-audience.md",
      "narrative": null,
      "content": "The primary target audience of this document is national authorities tasked with creating or \noverseeing the development of a digital vaccination certificate solution for COVID-19. The document \nmay also be useful to government partners such as local businesses, international organizations, non-\ngovernmental organizations and trade associations, that may be required to support Member States in \ndeveloping or deploying a DDCC:VS solution.",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-003",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Scope",
      "pageStart": 19,
      "pageEnd": 20,
      "target": "../sections/sec-003-13-scope.md",
      "narrative": null,
      "content": "1.3.1.\tIn scope\nThis document specifically focuses on how to digitally document COVID-19 vaccination status and \nattest that an individual has received a vaccine (i.e. how to provide a signed digital vaccination \ncertificate). Two priority scenarios are described in Table 1: Continuity of Care and Proof of \nVaccination. This document describes a specification for a signed digital vaccination certificate, \nincluding:\n\t\n→ethical and legal considerations, and privacy and data protection principles for the design, \nimplementation and use of a DDCC:VS;\n\t\n→use cases arising from the two scenarios fo",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-004",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Assumptions",
      "pageStart": 20,
      "pageEnd": 22,
      "target": "../sections/sec-004-14-assumptions.md",
      "narrative": null,
      "content": "The technological specification for a DDCC:VS is intended to be flexible and adaptable for each Member \nState to meet its diverse public health needs as well as the diverse needs of individuals around the \nworld. It is assumed that there is no one-size-fits-all solution, and so the specification must remain \nflexible and software-agnostic, while minimizing the amount of digital infrastructure required. \nThe requirements outlined are intended to allow for DDCC:VS solutions to meet the needs of a \ncountry’s holistic public health preparedness and response plan, while still being usable in other",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-005",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Methods",
      "pageStart": 22,
      "pageEnd": 22,
      "target": "../sections/sec-005-15-methods.md",
      "narrative": null,
      "content": "Since the COVID-19 pandemic began, and as vaccines have shown signs of efficacy, the number \nof digital solutions for vaccination certificates has increased. For the WHO to remain software-\nagnostic, the Smart Vaccination Certificate Working Group was created, with the intention of being \na multisectoral working group focused on supporting development of key standards for digital \nvaccination certificates, sharing joint learnings, and supporting development of a governance model \nwith a national trust framework architecture to support the roll-out of COVID-19 vaccines nationally (5). \nFurtherm",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-006",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Additional WHO guidance documents",
      "pageStart": 22,
      "pageEnd": 22,
      "target": "../sections/sec-006-16-additional-who-guidance-documents.md",
      "narrative": null,
      "content": "Specific guidance on how or when DDCC:VS should be used can be found in the following WHO \nguidance documents.\n\t\n→Technical considerations for implementing a risk-based approach to international travel in the \ncontext of COVID-19: Interim guidance, 2 July 2021 (6)\n\t\n→Policy considerations for implementing a risk-based approach to international travel in the context \nof COVID-19  (7)\n\t\n→Interim guidance on considerations for implementing and adjusting public health and social \nmeasures in the context of COVID-19 (8)\nThe following WHO guidance documents also served as a baseline for this work.",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-007",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Other initiatives",
      "pageStart": 22,
      "pageEnd": 23,
      "target": "../sections/sec-007-17-other-initiatives.md",
      "narrative": null,
      "content": "DDCC:VS core data set guidance laid out in this document may be leveraged to generate artefacts \nconformant with other initiatives such as the International Civil Aviation Organization (ICAO) \nGuidelines on visible digital seals (“VDS-NC”) for travel-related health proofs (16) and the European \nUnion (EU) EU Digital COVID Certificate (17). Additional technical details can be found on the DDCC \nvaccination certificate implementation guide available at: WorldHealthOrganization.github.io/ddcc.\nPage\n6\nDDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-008",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Ethical considerations and data protection principles",
      "pageStart": 23,
      "pageEnd": 23,
      "target": "../sections/sec-008-2-ethical-considerations-and-data-protection-pri.md",
      "narrative": null,
      "content": "SECTION 2\nAs with any digital solution, there are ethical considerations, such \nas potential impacts on equity and on equitable access, and data \nprotection principles that need to inform the design of the technical \nspecifications, as well as provide guidance on how resulting solutions \ncan be ethically implemented. The following sections discuss some key \nethical considerations and data protection principles that Member \nStates are encouraged to – and, where they have legal obligations, must \n– include in their respective deployments of any DDCC:VS. These ethical \nconsiderations and data pro",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-009",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Ethical considerations for a DDCC:VS",
      "pageStart": 23,
      "pageEnd": 29,
      "target": "../sections/sec-009-21-ethical-considerations-for-a-ddccvs.md",
      "narrative": null,
      "content": "This section presents ethical considerations to take into account when designing, developing and \ndeploying a DDCC:VS as part of the response to the COVID-19 pandemic (which may be extended to \nother diseases). This document covers two priority scenarios of use for a DDCC:VS, which are: \n1.\t\nas a record to serve as the basis for continuing healthcare for that individual (Continuity of Care); \nand\n2.\t\nas a record documenting that an individual has received a vaccination (Proof of Vaccination).\nThis section therefore focuses on the ethical considerations relevant to these two use cases in a \nnat",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-010",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Data protection principles for a DDCC:VS",
      "pageStart": 29,
      "pageEnd": 32,
      "target": "../sections/sec-010-22-data-protection-principles-for-a-ddccvs.md",
      "narrative": null,
      "content": "This section presents fundamental data protection principles for the DDCC:VS as a prerequisite \nfor continuity of care and proof of vaccination. The principles are designed to provide guidance to \nthe national authorities tasked with creating or overseeing the development of the DDCC:VS. The \nobjectives are to encourage Member States to adopt or adapt their national laws and regulations, as \nnecessary, respect personal data protection principles, and ensure respect for the human rights and \nfundamental freedoms of individuals, in particular the right to privacy, in order to build trust in the",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-011",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "DDCC:VS design criteria",
      "pageStart": 32,
      "pageEnd": 32,
      "target": "../sections/sec-011-23-ddccvs-design-criteria.md",
      "narrative": null,
      "content": "Due to the ethical considerations and data protection principles outlined above, the following design \ncriteria were considered when formulating the requirements for implementing a DDCC:VS for the",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-012",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Continuity of Care scenario",
      "pageStart": 32,
      "pageEnd": 33,
      "target": "../sections/sec-012-3-continuity-of-care-scenario.md",
      "narrative": null,
      "content": "1.\t\nImplementation of the DDCC:VS should not increase health inequities or increase the digital \ndivide.\n2.\t\nEveryone who has been vaccinated to protect against COVID-19 has the right to obtain and hold a \nDDCC:VS. \n3.\t\nThe DDCC:VS needs to be in a format that can be accessible to all, for example, in paper and \ndigital formats. Any solution should also work in online and offline environments across multiple \nplatforms – paper and digital. \n4.\t\nIndividuals should not be treated differently or given different levels of trust due to the format of \nthe DDCC:VS they are using (e.g. there should be",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-013",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Key settings, personas and digital services",
      "pageStart": 33,
      "pageEnd": 35,
      "target": "../sections/sec-013-31-key-settings-personas-and-digital-services.md",
      "narrative": null,
      "content": "The Continuity of Care scenario is expected to involve the following settings, which can be in the same \nphysical location. \n1.\t CARE SITE: where the vaccination event takes place. Some examples of this include at a primary \nhealth-care facility, a temporary vaccination site, or a pharmacy, as determined by the Member \nState’s vaccine delivery plan. \n2.\t DATA ENTRY SITE: where the vaccination record is digitized. The record can be digitized at the care \nsite if the digital solution is available, or it can be done retroactively under the auspices of the \npublic health authority or health servic",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-014",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Continuity of Care workflows and use cases",
      "pageStart": 35,
      "pageEnd": 41,
      "target": "../sections/sec-014-32-continuity-of-care-workflows-and-use-cases.md",
      "narrative": null,
      "content": "The Continuity of Care scenario is summarized in Fig. 3. The workflow’s actors and settings, and its \nrelated high-level requirements, may be described as follows.\n1.\t A Subject of Care presents at a care site. The identity of the Subject of Care is established as per \nMember State processes and norms. The Subject of Care MAY present an existing DDCC:VS card to \ninform the care delivery process. The Vaccinator MAY retrieve existing health history data about \nthe Subject of Care if authorized to do so.\n2.\t A Vaccinator administers a COVID-19 vaccination.\n3.\t Elements of the DDCC:VS core data se",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p036",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 36,
      "pageEnd": 36,
      "target": "../figures/vfig-p036.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p038",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 38,
      "pageEnd": 38,
      "target": "../figures/vfig-p038.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p039",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 39,
      "pageEnd": 39,
      "target": "../figures/vfig-p039.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p040",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 40,
      "pageEnd": 40,
      "target": "../figures/vfig-p040.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-015",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Functional requirements for Continuity of Care scenario",
      "pageStart": 41,
      "pageEnd": 44,
      "target": "../sections/sec-015-33-functional-requirements-for-continuity-of-car.md",
      "narrative": null,
      "content": "scenario\nHigh-level functional requirements for the elements described in Fig. 3 are presented in Table 5 as \nsuggested features that any digital solutions that would facilitate DDCC:VS issue or usage may have. \nThese are written as guidance requirements only, to be used as a starting point for Member States or \nother interested parties who need to develop their own specifications for a DDCC:VS to take and adapt.\nNon-functional requirements are applicable to both scenarios of use (Continuity of Care and Proof of \nVaccination) and are included in Annex 5.\nTable 5\nFunctional requirements for the",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-016",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Proof of Vaccination scenario",
      "pageStart": 44,
      "pageEnd": 44,
      "target": "../sections/sec-016-4-proof-of-vaccination-scenario.md",
      "narrative": null,
      "content": "SECTION\nProof of \nVaccination \nscenario \n4 \nThis section describes the use cases and actors involved in using a \nDDCC:VS for Proof of Vaccination, as well as functional requirements \nfor a digital solution. The Proof of Vaccination scenario relies on the \nPHA having access to a trusted means of digitally signing an HL7 FHIR \ndocument, which represents the core data set for the DDCC:VS. It will \nbe up to Member States to define the purposes for which this scenario \nis applied and adapted to their own contexts and levels of digital \nmaturity, in compliance with their legal and policy frameworks.",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-017",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Key settings, personas and digital services",
      "pageStart": 44,
      "pageEnd": 46,
      "target": "../sections/sec-017-41-key-settings-personas-and-digital-services.md",
      "narrative": null,
      "content": "For the Proof of Vaccination scenario, there is one additional setting to consider: the verification \nsite, where it is necessary for people to prove their COVID-19 vaccination status (such as a care site, a \nschool, or an airport). How, when, where, and by whom the DDCC:VS can be verified should be defined \nby the Member State. The relevant policies, including data protection policies, should be put in place \naccordingly. \nThese key personas (see Table 6) are anticipated to interact with digital services (see Table 7). Not \nall of these digital services will have a user interface that the key",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p046",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 46,
      "pageEnd": 46,
      "target": "../figures/vfig-p046.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-018",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Proof of Vaccination workflows and use cases",
      "pageStart": 46,
      "pageEnd": 54,
      "target": "../sections/sec-018-42-proof-of-vaccination-workflows-and-use-cases.md",
      "narrative": null,
      "content": "In order to sign a digital document, PKI technology is required. Each Member State would be \nresponsible for managing its own PKI through its PHA or another national delegated authority. PKI is \ndescribed in further detail in section 6 and Annex 4. This document assumes that a PKI has already \nbeen deployed or is available within a country to support the DDCC:VS workflows described in this \nsection. This PKI supports the sharing of public keys that correspond to the private keys that have \nbeen used to cryptographically sign DDCC:VS and may support the sharing of public keys from trusted \nInte",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p048",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 48,
      "pageEnd": 48,
      "target": "../figures/vfig-p048.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p050",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 50,
      "pageEnd": 50,
      "target": "../figures/vfig-p050.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p051",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 51,
      "pageEnd": 51,
      "target": "../figures/vfig-p051.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p052",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 52,
      "pageEnd": 52,
      "target": "../figures/vfig-p052.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p053",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 53,
      "pageEnd": 53,
      "target": "../figures/vfig-p053.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-019",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Functional requirements for Proof of Vaccination scenario",
      "pageStart": 54,
      "pageEnd": 57,
      "target": "../sections/sec-019-43-functional-requirements-for-proof-of-vaccinat.md",
      "narrative": null,
      "content": "scenario\nHigh-level functional requirements for the activities described in Fig. 8 are presented in Table 9 as \nsuggested features that any digital solutions that would facilitate DDCC:VS verification may have. \nThese are written as guidance requirements only to be used as a starting point for Member States \nor other interested parties that need to develop their own specifications for a digital solution for \nDDCC:VS to take and adapt. \nGiven non-functional requirements are common to both scenarios (Continuity of Care and Proof of \nVaccination) (see Annex 5).\nTable 9\nFunctional requirements for",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-020",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "DDCC:VS core data set",
      "pageStart": 57,
      "pageEnd": 57,
      "target": "../sections/sec-020-5-ddccvs-core-data-set.md",
      "narrative": null,
      "content": "SECTION 5\nSECTION\nDDCC:VS \ncore data set \n5 \nThe DDCC:VS core data set includes data elements about the Subject \nof Care and vaccine administration events that are required for the \ntwo core scenarios of Continuity of Care and Proof of Vaccination. \nStakeholders and systems may use the DDCC:VS core data set as \ndefined, or they may continue to use their existing terminology with a \nmap to the DDCC:VS core data set, so long as it contains the required \ndata elements in the DDCC:VS core data set. The recommended \ncore data set is intended to include the critical data required for \ninteroperabili",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-021",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Core data set principles",
      "pageStart": 57,
      "pageEnd": 59,
      "target": "../sections/sec-021-51-core-data-set-principles.md",
      "narrative": null,
      "content": "To develop the core data set, data requirements under the International Health Regulations (15), WHO \nhome-based records guidance (13), WHO adverse events following immunization (AEFI) reporting \nrequirements (26) and WHO immunization programme monitoring guidance are considered (12). \nThe core data set has been further informed by analysis of existing digital vaccination certificates \ndeployed in some countries and by pre-existing standards for digital vaccination certificates.\nThe following key principles were used to guide the formulation of the core data set.\n\t\n→DATA MINIMIZATION. Aligned",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-022",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Core data elements",
      "pageStart": 59,
      "pageEnd": 65,
      "target": "../sections/sec-022-52-core-data-elements.md",
      "narrative": null,
      "content": "The three key sections of the core data set are: \n1.\t\nthe header \n2.\t\ndata elements for each vaccination event \n3.\t\nvaccination certificate metadata.\nThe header section data elements include the Subject of Care’s ID information (see Table 10). The \nheader section is intended to capture information about the vaccinated individual to allow for \ninformation on the vaccination event to be linked to a specific person. This data should remain the \nsame regardless of which vaccination a person has received; thus, it should only be collected once. \nTable 10\nHeader section of the DDCC:VS with preferred",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p064",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 64,
      "pageEnd": 64,
      "target": "../figures/vfig-p064.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p065",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 65,
      "pageEnd": 65,
      "target": "../figures/vfig-p065.png",
      "narrative": "draft",
      "content": "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).",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-023",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Signing a DDCC:VS",
      "pageStart": 65,
      "pageEnd": 66,
      "target": "../sections/sec-023-61-signing-a-ddccvs.md",
      "narrative": null,
      "content": "The process of signing a DDCC:VS is shown in the top row of Fig. 13 and involves three steps.\n1.\t The PHA generates a private and public key pair that serve as the “root certificate”. The private \nkey is kept highly secure (never revealed to another party, maintained in a disconnected location, \nstored on media that is itself password-protected, etc.); the public key will be widely disseminated.\n2.\t The PHA generates one or more DSC key pairs. DSC private keys are kept highly secure, and public \nkeys are widely disseminated. The DSC key pair is digitally signed by the root certificate’s privat",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-vfig-p066",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 66,
      "pageEnd": 66,
      "target": "../figures/vfig-p066.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-024",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Verifying a DDCC:VS signature",
      "pageStart": 66,
      "pageEnd": 67,
      "target": "../sections/sec-024-62-verifying-a-ddccvs-signature.md",
      "narrative": null,
      "content": "The verification process, shown in in the bottom row of Fig. 13 and further detailed in Fig. 15, reverses \nthe signing process to verify content in the signed DDCC:VS.\n1.\t A Verifier calculates its own hash (i.e. “calculated hash”) from the information in the DDCC:VS \nusing the same hashing algorithm as was used by the document signer. \n2.\t The DDCC:VS’s signed hash is read by a digital solution.\n3.\t The document signer’s public key is used to cryptographically transform the signed hash back to \nthe document hash. The Verifier can compare the document hash from step 2 to its own calculated \nha",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-025",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Trusting a DDCC:VS signature",
      "pageStart": 67,
      "pageEnd": 68,
      "target": "../sections/sec-025-63-trusting-a-ddccvs-signature.md",
      "narrative": null,
      "content": "The cryptographic strength of private–public key pairs is based on the mathematics of asymmetric \ncryptography, a process involving “one-way” mathematical functions, which are operations that are \neasy to compute in one direction but extremely hard to reverse. They provide a high level of security \nprovided the private key is not compromised and remains available only to the entity performing \nthe signing. Operationally, private keys are kept highly secure and public keys are broadly shared. \nProvided that a private key is not compromised and unintentionally revealed to another party, content",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-026",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "National governance considerations",
      "pageStart": 68,
      "pageEnd": 70,
      "target": "../sections/sec-026-7-national-governance-considerations.md",
      "narrative": null,
      "content": "SECTION\nNational \ngovernance \nconsiderations \n7 \nGovernance in the health sector is “a wide range of steering and \nrule-making related functions carried out by governments/decisions \nmakers as they seek to achieve national health policy objectives that \nare conducive to universal health coverage” (33). A national framework \nto govern the complex and dynamic health policy for implementing \nDDCC:VS should be tailored to meet the Member State’s needs, which \nvary. This section provides an overview of some key governance \nconsiderations for Member States implementing DDCC:VS solutions. \nHowever, i",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-027",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Implementation considerations",
      "pageStart": 70,
      "pageEnd": 71,
      "target": "../sections/sec-027-8-implementation-considerations.md",
      "narrative": null,
      "content": "SECTION\nImplementation \nconsiderations \n8 \nSince COVID-19 was declared a Public Health Emergency of \nInternational Concern under the IHR in January 2020, there has been a \nclear and urgent need for all Member States to effectively address the \nCOVID-19 pandemic. In the digital age, there has also been immediate \nacknowledgement that digital health solutions can effectively and \nimmediately be leveraged to support the public health response to \nthe pandemic (35). However, there are two distinct approaches that \nMember States can use to pursue the implementation of DDCC:VS, both \nof which have d",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-028",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Considerations before deploying",
      "pageStart": 71,
      "pageEnd": 73,
      "target": "../sections/sec-028-81-considerations-before-deploying.md",
      "narrative": null,
      "content": "Using the framework of essential components of a digital health implementation presented in \nthe WHO/ITU’s National eHealth Strategy Toolkit (36), and the guidance provided in the Digital \nimplementation investment guide (DIIG) (37), the following considerations and key questions should \nbe examined prior to deployment of a DDCC:VS solution.\nSTRATEGY AND INVESTMENT\n\t\n→Is the DDCC:VS solution intended to be a short-term solution or a long-term digital vaccination \ncertificate solution? \n\t\n→What are the potential benefits, risks and costs of implementing a DDCC:VS solution? These should \nbe asse",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-029",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Key factors to consider with solution developers",
      "pageStart": 73,
      "pageEnd": 74,
      "target": "../sections/sec-029-82-key-factors-to-consider-with-solution-develop.md",
      "narrative": null,
      "content": "If a PHA that is responsible for the delivery of a digital solution does not have the appropriate \ntechnology skills in-house, then it may want to look for one or more partners to provide that service. \nThe choice of a digital partner will ideally be subject to a competitive process. Multiple potential \nsuppliers will be considered to identify partners that represent the best fit for the work at the optimal \nprice, with consideration of the total cost of ownership, timeline and sustainability of the solution. The \napproach to inviting tenders for the work, assessing tenders, awarding a contrac",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-030",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Cost category considerations",
      "pageStart": 74,
      "pageEnd": 76,
      "target": "../sections/sec-030-83-cost-category-considerations.md",
      "narrative": null,
      "content": "Regardless of whether the intended DDCC:VS solution will be a short-term solution or a long-term \ndigital vaccination certificate solution, specific cost categories and related cost drivers will affect \nthe budget for this work. However, whether they will be incurred as a sunk cost of the pandemic (for \nshort-term solutions) or an investment for future digital health systems (long-term solutions) will \ndepend on the Member State’s implementation strategy. Table 13 provides a non-exhaustive list of \npossible cost drivers for implementing a DDCC:VS solution. \nPage\n58\nDDCC:VS - Technical Specific",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-031",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Additional resources to support implementation",
      "pageStart": 76,
      "pageEnd": 77,
      "target": "../sections/sec-031-84-additional-resources-to-support-implementatio.md",
      "narrative": null,
      "content": "Additional resources that can be leveraged to support the implementation of DDCC:VS include \nexamples of implementations already deployed, additional technical specifications for specific use \ncases, and general guidance on implementing digital health solutions. Note that the following is a non-\nexhaustive list of examples. WHO will be documenting in a clearinghouse software solutions that are \nconsistent with the DDCC:VS specifications.\nWHO INTEROPERABILITY STANDARD FOR DDCC:VS \n\t\n→\nDDCC:VS HL7 FHIR Implementation Guide\n\t\n→\nDDCC:VS core data dictionary, 27 July 2021\nEXAMPLE DDCC:VS IMPLEMENTA",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-032",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "References",
      "pageStart": 77,
      "pageEnd": 79,
      "target": "../sections/sec-032-references.md",
      "narrative": null,
      "content": "1.\t Diamond, D. ‘Ripe for fraud’: Coronavirus vaccination cards support burgeoning scams. In: The Washington Post \n[website]. USA: The Washington Post; 18 April 2021 (https://www.washingtonpost.com/health/2021/04/18/scams-\ncoronavirus-vaccination-cards/, accessed 9 August 2021).\n2.\t Siringi, S. Fake health certificate racket rife in Kenya. Lancet Infect Dis. 2002;2(8):454. doi:10.1016/s1473-3099(02)00357-2.\n3.\t Deguma MC, Deguma JJ. The possible threat of faking Covid-19 diagnostic tests and vaccination certifications: a call to an \nimmediate action. J Public Health (Oxf). 2021;43(2):e340–1. d",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Provides the numbered bibliography of 40 references cited throughout the DDCC:VS technical specifications and implementation guidance.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-033",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Annexes",
      "pageStart": 79,
      "pageEnd": 80,
      "target": "../sections/sec-033-annexes.md",
      "narrative": null,
      "content": "DDCC:VS - Technical Specifications and Implementation Guidance, 27 August 2021\nPage\n63\nAnnex 1",
      "truncated": false,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "text": "Presents the section divider and Annex 1 header introducing the annexes of the DDCC:VS guidance document.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p080-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 80,
      "pageEnd": 80,
      "target": "../images/img-p080-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-034",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Illustrative example of Digital Documentation of COVID-19 Certificates: Vaccination Status (DDCC:VS)",
      "pageStart": 80,
      "pageEnd": 81,
      "target": "../sections/sec-034-1-illustrative-example-of-digital-documentation.md",
      "narrative": null,
      "content": "Certificates: Vaccination Status (DDCC:VS)\nBelow is an illustrative example of a DDCC:VS intended to be printed on A6 paper and folded like a \nbooklet. This is not a template, nor are Member States required to adopt this design. Member States \nare encouraged to design a vaccination certificate (paper and/or digital) with the core data set \nrequirements, fraud prevention mechanisms and scenarios of use in mind.1\n1\t This illustrative example is adapted from the COVID-19 Paper Based Information System designed and developed by Sonder Design, which \ncan be accessed here: https://www.notion.so/COVI",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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).",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p081-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 81,
      "pageEnd": 81,
      "target": "../images/img-p081-1.png",
      "narrative": "draft",
      "content": "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'.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p081-2",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 81,
      "pageEnd": 81,
      "target": "../images/img-p081-2.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p081-3",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 81,
      "pageEnd": 81,
      "target": "../images/img-p081-3.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p081-4",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 81,
      "pageEnd": 81,
      "target": "../images/img-p081-4.png",
      "narrative": "draft",
      "content": "A white diamond with a black outline: the BPMN gateway symbol, a fork or decision point in a workflow, in Table A2.1.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-035",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Business process symbols used in workflows",
      "pageStart": 81,
      "pageEnd": 82,
      "target": "../sections/sec-035-2-business-process-symbols-used-in-workflows.md",
      "narrative": null,
      "content": "Table A2.1 provides an overview of the standardized notation for business process mapping that is \nused to depict the Continuity of Care use cases and Proof of Vaccination use cases. \nTable A2.1 \nBusiness process symbols used in workflows\nSymbol\nSymbol name\nDescription\nLane 1\nLane 2\nLane 3\nPool\nPool\nA pool consists of multiple “swim lanes” that depict all the \nindividuals or types of users that are involved in carrying out the \nbusiness process or workflow. \nLane 2\nLane 3\nPool\nLane 1\nSwim lane \nEach persona is assigned to a swim lane, a designated area for noting \nthe activities performed or e",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-036",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Guiding principles for mapping the WHO Family of International Classifications (WHO-FIC) and other classifications",
      "pageStart": 82,
      "pageEnd": 85,
      "target": "../sections/sec-036-3-guiding-principles-for-mapping-the-who-family.md",
      "narrative": null,
      "content": "International Classifications (WHO-FIC) and other \nclassifications\nMapping from classifications and terminologies used in existing systems to the International \nClassification of Diseases, 11th revision (ICD-11), and other WHO-FIC classifications should follow the \nprinciples listed below.1 \n1.\t\nEstablish use case(s) prior to developing the map – this involves identifying and formulating the \npurpose(s) for which the map will be used and describing the different types of users and how \nthey will process data using the map. \n2.\t\nClearly define the purpose, scope and directionality of the map.\n3",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-037",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "What is public key infrastructure (PKI)?",
      "pageStart": 85,
      "pageEnd": 89,
      "target": "../sections/sec-037-4-what-is-public-key-infrastructure-pki.md",
      "narrative": null,
      "content": "The solution discussed in this document involves applying digital signatures to information to provide \na guarantee that the information has been validated by an accredited authority. The proposed method \nis to employ a digital certificate using a private–public key pair, a common mathematical approach \nfor encryption and digital trust. The processes, systems, software and rules around the management \nof these certificates form a PKI – essentially, all the components that need to be in place for a trusted \nsolution to work.\nWHY IS A PKI NEEDED?\nVarious individuals and organizations, when prese",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p086-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 86,
      "pageEnd": 86,
      "target": "../images/img-p086-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-038",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Non-functional requirements",
      "pageStart": 89,
      "pageEnd": 94,
      "target": "../sections/sec-038-5-non-functional-requirements.md",
      "narrative": null,
      "content": "This section contains a suggested set of generic non-functional requirements (see Table A5.1). Along \nwith the functional requirements in sections 3.3 and 4.3, these non-functional requirements can be \nadapted when specifying a digital solution for the scenarios in this paper. Non-functional requirements \nexplain the conditions under which any digital solution must remain effective and are organized into \nthe following categories.\n\t\n→ACCESSIBILITY: The provision of flexibility to accommodate each user’s needs and preferences, along \nwith appropriate measures to ensure access to persons with di",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/prose-sec-039",
      "types": [
        "folio-assistant-core:Prose",
        "doco:Section"
      ],
      "kind": "prose",
      "title": "Open Health Information Exchange (OpenHIE)-based architectural blueprint",
      "pageStart": 94,
      "pageEnd": 99,
      "target": "../sections/sec-039-6-open-health-information-exchange-openhie-based.md",
      "narrative": null,
      "content": "architectural blueprint\nThis section illustrates how a standards-based health-data-sharing infrastructure could support point-\nof-care digital health solutions. If digital health solutions are employed in real time during the vaccine \nadministration event, it is anticipated that complementary digital health infrastructure, such as the \narchitectural elements described by the OpenHIE specification, could be leveraged. \nOpenHIE describes a reusable architectural framework that leverages health information standards, \nenables flexible implementation by country partners, and supports exchange of i",
      "truncated": true,
      "provenance": "ingested",
      "summary": {
        "status": "draft",
        "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.",
        "state": "draft",
        "draftedBy": {
          "kind": "agent",
          "id": "claude-code",
          "model": "not-disclosed"
        },
        "draftedAt": "2026-10-30"
      }
    },
    {
      "id": "library/who-2019-ncov-digital-certificates-vaccination-20211-eng/blocks/figure-img-p095-1",
      "types": [
        "folio-assistant-core:Figure",
        "doco:Figure"
      ],
      "kind": "figure",
      "title": "",
      "pageStart": 95,
      "pageEnd": 95,
      "target": "../images/img-p095-1.png",
      "narrative": "draft",
      "content": "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.",
      "truncated": false,
      "provenance": "ingested",
      "summary": null
    }
  ]
}
